What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[HACKS] Root Droid 1 - regardless of OS version

You need to copy this file to the root of your phone's SD card and then rename it to update.zip.

how do u do this???
Two options. Install Astro, download it directly to your phone, navigate to it in Astro (it's in the download folder), rename it "update" without the quotes, then copy/paste it to the sdcard folder when you open Astro. Second involves mounting your phone's SD card to the PC. Plug the USB cable in, select USB Mass Storage on the phone, tell it to mount the SD card, and copy the file to the SD card, but don't put it in a folder. Once it's there rename the file update -- if you get some kind of warning about changing the file extension then select cancel and rename it update.zip before turning USB Mass Storage off on the phone.

I realize this might not be the most clear. If you still need help, we'll do what we can.

I think this has been answered before in the thread, though, so if you need more help there might be an answer buried somewhere. :) Good luck!
 
I just rooted my Droid yesterday and have loaded with some guidance from furbearingmammal , the CyanogenMod 6.0.0, loaded the app pak, then after a short time all free apps I had redownloaded and my phone is kinda back to what I had on the stock phone, will run this for a few days see how she responds...thanks furbearingmammal..

Bob
 
i am doing pretty good until i get to Install /sdcard/update.zip
the error code i get is
E: can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(no such file or directory)
E: can't mount sdcard.update.zip
installation aborted
i have read through your fei, and faq. i have selected all the correct settings i have uninstalled and replaced the update.zip file (via drag and drop cant understand the adb yet) several times. please help --jp
 
^are you sure the update.zip is named update.zip and not update.zip.zip ?

This will cause the system to not recognize it and it is an easy mistake to make
 
@travelingp: I have been following this thread and there have been just a few with your problem. One solution that has been posted in this thread is to repeatedly reboot into recovery until the phone will 'see' your update.zip file. It seems as though there are some phones that having a problem mounting the card while in recovery. It might be as simple as waiting a bit after the phone boots into recovery, as my phone takes a bit to finish mounting the sd card while it's booting up.

Another solution would be to manually install su, busybox, and superuser.apk but that pretty much requires adb shell to be installed and working on your computer. I have sent MotoCache1 a pm about that final method of finishing off the rooting for those with your problem.

Now, I gotta go through my guides and notes to find the steps . . .

good luck
 
Last edited:
Question for MotoCache...

If I flash your recovery.sbf onto my phone, catch the boot, let it "Pass", reboot in your custom recovery, do a full backup (all boxes checked), and then install the update.zip ("Complete_Root_V1.1"), I am fully rooted. Then if I restore back to that first full backup (before your updates) and let it boot into the stock rom with the FRS enabled, will it "unroot" my phone and restore the stock recovery system? I'm assuming it will because once I restore my backup, I will no longer have FRS disabled, no busybox, and no superuser. Also, is there a way for verizon to know the recovery system has been changed?
 
Question for MotoCache...

If I flash your recovery.sbf onto my phone, catch the boot, let it "Pass", reboot in your custom recovery, do a full backup (all boxes checked), and then install the update.zip ("Complete_Root_V1.1"), I am fully rooted. Then if I restore back to that first full backup (before your updates) and let it boot into the stock rom with the FRS enabled, will it "unroot" my phone and restore the stock recovery system? I'm assuming it will because once I restore my backup, I will no longer have FRS disabled, no busybox, and no superuser. Also, is there a way for verizon to know the recovery system has been changed?
Not unless you tell them/show them/send it in for service without unrooting. To do what you propose will wipe out all your personal data and whatnot, probably not what you want if you're unrooting unless you're sending it in for service.

The best way to unroot is to install the master FRG22D OTA update. It'll wipe out your recovery and unroot the OS, as well as putting the phone back to Stock FRG22D for the techies to mess with. Less chance of bricking your Droid by far compared to using SBF files.
 
So allowing the phone to rebuild the stock recovery service will erase all personal data? So after flashing MotoCaches sbf, when you have to catch the boot, if you don't and it boots into the os, you'll be greeted with a google account login screen?
 
If you don't catch the boot to root the phone it will be exactly like nothing happened at all. Your phone won't lose or gain anything. I was talking restoring a backup you made of the stock system -- it's just easier and takes up a LOT less space to unroot via the master FRG22D OTA file. Plus you'll have the added benefit of not losing every change you've made to your phone since you made the backup.
 
Oh I see. And that Master OTA file can be applied as an update.zip? The backup takes up about 300mb so it would be good to avoid that.
 
ok here is another question. i am attempting to put a custom rom on my droid. so i try to do a nandroid backup first. i get error 31?
 
I got an error 31 once, when I went to do an advanced backup. I named the advanced backup and then backed out and decided to do a regular backup and it gave me the error 31. I just rebooted into recovery and never happened again.
 
I got an error 31 once, when I went to do an advanced backup. I named the advanced backup and then backed out and decided to do a regular backup and it gave me the error 31. I just rebooted into recovery and never happened again.
unfortunately, i have attempted this several times always getting the same result
 
Back
Top