Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About crawler9

  • Rank

Profile Information

  • Your Current Device(s)
    Nexus One
  1. Mine just reset on me too. It wouldn't stop. I didn't want to bother getting my case off so I just hooked it up to my computer and issued adb reboot. One thing I found interesting is that despite nothing seeming to work, programs in the background must've been loaded still. While it was showing the boot animation, my SD was automatically mounted to my computer with "Dual Mount SD", an app that mounts the SD on both the phone and computer at the same time.
  2. I'm glad to hear it all worked out for you!
  3. No problem at all. I had a lot of help when I first started out with my Nexus. Try downloading the FRG33 files in image format, renaming it PASSIMG.zip making sure not to name it PASSIMG.zip.zip. In Windows, by default, file extensions are hidden and this file already has a zip extension. Once you've renamed it, copy it to the root of your SD card and power off your phone. Download theuniversal update to GRI40, rename it "update.zip" and copy it also to the root of your SD card. Power your phone off, then turn it on while holding volume-down. It should prompt you "update", really meaning it'll restore your phone to stock FRG33. Confirm. It may or may not reboot after the second step of flashing it, depending on the bootloader version you have. If it does reboot, repeat the process again. You should now be on stock FRG33 (Froyo). Reboot into recovery, and tap volume-up and the power button at the same time to show the menu. click the option that says something about flashing "update.zip." and your phone will be updated to the official Gingerbread.
  4. Would you like to update to the newest completely stock gingerbread ROM or are in interested in a custom ROM? Also, do you have any information already on your phone with which you can't part? The easiest way to get you to a stock ROM would include wiping it completely.
  5. About your bootloader, when you turn on the phone, the splash screen indicates a locked or unlocked bootloader. Also, when you enter recovery, what does it say? It would say somewhere ClockworkMod or Amon Ra or if its the stock recovery, it'd say something like (3e) at the top
  6. Is your bootloader unlocked? Do you know if your recovery is stock or custom?
  7. You should probably have made a new topic but I'll answer anyway. The easiest way would be to find and download the a stock ROM available in PASSIMG format also known as image format . I know FRG33 works, but I think I remember having issues with FRG83 images. You can get them from http://android.modaco.com/content/google-n...-root-insecure/. After you download it, rename it PASSIMG.zip and place it on the root of your SD card. Reboot while holding the volume down button and follow the prompts to "update". Your phone will be wiped and everything including your recovery image will be replaced with the stock version. You can then get OTA updates to the latest version.
  8. Supposedly, an SMS misdirection bug was fixed. I never experienced this bug before. I've read that there are other small bug fixes as well, but nothing else worth mentioning.
  9. You can fastboot flash the recovery image from the stock build over a custom recovery to revert back, if your bootloader is unlocked.
  10. I've been running this for about 2 days. I think I prefer fitsnugly's nightly cm7 builds but MM is by no means bad. It's a great mostly stock experience.
  11. Upgrade to the latest version of the custom ROM. You don't need to wipe and the update nag will stop.
  12. Though only certain applications can be moved to SD without modifying settings through terminal. Also, the official Google apps2sd uses your standard SD partition which isn't mounted until after calls to widgets have already been made thus anything with a widget would need to be kept on the phone's internal memory for proper function and any apps stored on the SD through this official method will not show up on the phone at any point when you're connected as a mass storage device to your computer. None of these limitations are present in apps2ext.
  13. 1. Although exploits could be patched, you can always go back and unlock the bootloader even if you hold off for now. If you root without unlocking the bootloader, you lose fastboot functions. That's all. You can still flash a custom recovery image and flash any rom you like if you use adb and flash_image or rom manager to install your custom recovery for you. I personally just didn't like the lock that shows up when the bootloader is unlocked, so after sending my device in for repair and receiving it with a relocked bootloader and stock rom, I left the bootloader locked. 2. Not sure ^-^ sry. 3. If you're on an old build with support for Androot, you can temp root to install a custom recovery and back it up. Or you could just root, install a custom recovery, and take a backup of your stock rom w/ root. You can always go back to stock with a PASSIMG anyway. 3a. http://android.modaco.com/content/google-n...-root-insecure/ 4. Not sure... I've asked that question a few times and never gotten a response. 4a. I don't know a whole lot about this, but I haven't heard of any disadvantages of using himem... I don't think anything is being made without himem now, even officially. 4b. Installing OTA updates will remove root (if it even installs properly). I'd assume a new superboot for the new version would work, but usually, Paul has a repack for custom recoveries of new updates before OTA updates even hit my phone, and his repacks include root permissions by default. That's the best way to go IMO. 5. For the above reason, I almost never use OTA updates. I don't think they're important. Also, about a "full and function[ing] nandroid backup": I don't use them... I suppose it's probably a safe move... but I've done some system modding and removed some stuff. Never had any issue except for once when I accidentally removed the camera app. Solved that by downloading a 3rd party camera app from the market until I had the time to reflash the rom i was using at the time If I ever decide to go back, I just use the stock signed PASSIMG files to revert to stock. I guess what that all means to me is that backups could potentially save some time, but aren't worth the space they take on my SD card as they aren't absolutely essential for anything. 6. I'm not exactly sure what you're asking here. You shouldn't have to do much with the radios at all. There might be a radio upgrade that is required for certain OS milestones. For example, when moving from Eclair to Froyo, a radio update was required. I don't know if the official Gingerbread will include a new radio update or not, or whether it'll be required. If I decide to change radios, I use zipped radio files in custom recovery. It's generally considered safer to flash radios through fastboot, but I've always used recovery without issue. As long as you make sure your zip file isn't corrupted, you shouldn't have any problem. 7. I haven't read anything about a2sd scripts in rooted stock roms, but I don't think it'd work. I know that DarkTremor apps2sd requires busybox which isn't present in a stock rom. You might be able to download and install the busybox stuff, but that sounds like more trouble than it's worth to me. If you want a custom rom with close to stock feel, I highly recommend Paul's custom roms. Hope this helps.
  14. Titanium backup is a great application. It can save you a lot of time when you do have to start over. Anyway I don't think you would have to wipe to install r24.
  15. As you have a custom ROM and recovery, you can not install a OTA update. Gingerbread will be coming soon, but if you can't wait and want to upgrade to the latest version available now, you could update to MoDaCo Custom ROM r24 which is based on the latest OTA update. That will stop any OTA update notifications.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.