OMJ
Bazinga
are you getting the stock recovery or SPRecovery when you reboot into recovery?
You can try this update.zip update.zip its an older version of superuser but it will work just fine
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Guide to Rooting 2.2 for Windows and Linux
- Thread starter OMJ
- Start date
-
- Tags
- motorola droid
are you getting the stock recovery or SPRecovery when you reboot into recovery?
You can try this update.zip update.zip its an older version of superuser but it will work just fine
Ah, I'm in the stock recovery... I hold 'x' and it boots to the triangle with exclamation point... I figured you meant press up volume and picture button to go to recovery... should it boot to something else? This is the result of the ./sbf_flash on linux, did it install correctly?:
./sbf_flash -r --recovery SPRecovery_ESE81.sbf
SBF FLASH 1.08 (mbm)
Droid found.
CG63 0xC0000000-0xC001FFFF mbmloader.img
CG30 0xC0020000-0xC00BFFFF mbm.img
CG55 0xC00C0000-0xC015FFFF mbmbackup.img
CG31 0xC0160000-0xC01BFFFF cdt.bin
CG38 0xD01CE000-0xD0359FFF pds
CG34 0xC035A000-0xC03BCFFF lbl
CG57 0xC03BD000-0xC041FFFF lbl_backup
CG41 0xC0400000-0xC057FFFF sp
CG42 0xC0580000-0xC061FFFF logo.bin
CG44 0xC0620000-0xC067FFFF misc
CG35 0xC0680000-0xC09FFFFF boot
CG47 0xC0A00000-0xC0E7FFFF recovery
CG39 0xD0EF4000-0xD9FB6FFF system
CG40 0xD9FB7000-0xDFF3BFFF cache
CG37 0xDFF3C000-0xF0D29FFF userdata
CG53 0xDFD40000-0xDFF3FFFF kpanic
Index[1]: Unexpected chip 16
Index[2]: Unexpected chip 16
=== SPRecovery_ESE81.sbf ===
00: RDL03 0x80500000-0x8054CFFF FE66 AP
01: CG35 0xC0680000-0xC08E37FF ABCB AP boot
02: CG47 0xC0A00000-0xC0D5C7FF 02C0 AP recovery
Skipping CG35 0xC0680000-0xC09FFFFF
>> waiting for phone: Droid found.
>> uploading RDL03
Uploading: 100% OK
>> verifying ramloader
-- OK
>> executing ramloader
Droid found.
>> sending erase
>> uploading CG47
Uploading: 100% OK
>> verifying CG47
-- OK
>> rebooting
OMJ
Bazinga
If you are still at stock recovery it didnt work although that output sure looks like it did. I am at work and dont have linux here but I am going to pm you my gchat and I can try to help you figure it out when I get home in an hour or so.
Just an update, OMJ figured it out. Right after running sbf_flash on linux when it says 'rebooting' in terminal, hold down the 'x' key on droid phone and it will boot into SPRecovery. Otherwise, if you let the phone boot up into the OS, it will revert back to stock recovery.
Thanks OMJ
Thanks OMJ
morgan_allstar
Newbie
any help: i got to the final step and it was installing but i never had the chance to reboot, the screen just went black. now i can't turn on the phone or anything....tried pulling the batter, unplugging the phone from the usb and back again......did i just destroy my phone?
Scottmc
Member
I'm also having this issue. Everything went fine up to this point though. I was able to flash the recovery with no errors on the output.
Code:
SBF FLASH 1.08 (mbm)
Droid found.
CG63 0xC0000000-0xC001FFFF mbmloader.img
CG30 0xC0020000-0xC00BFFFF mbm.img
CG55 0xC00C0000-0xC015FFFF mbmbackup.img
CG31 0xC0160000-0xC01BFFFF cdt.bin
CG38 0xD01CE000-0xD0359FFF pds
CG34 0xC035A000-0xC03BCFFF lbl
CG57 0xC03BD000-0xC041FFFF lbl_backup
CG41 0xC0400000-0xC057FFFF sp
CG42 0xC0580000-0xC061FFFF logo.bin
CG44 0xC0620000-0xC067FFFF misc
CG35 0xC0680000-0xC09FFFFF boot
CG47 0xC0A00000-0xC0E7FFFF recovery
CG39 0xD0EF4000-0xD9FB6FFF system
CG40 0xD9FB7000-0xDFF3BFFF cache
CG37 0xDFF3C000-0xF0D29FFF userdata
CG53 0xDFD40000-0xDFF3FFFF kpanic
Index[1]: Unexpected chip 16
Index[2]: Unexpected chip 16
=== SPRecovery_ESE81.sbf ===
00: RDL03 0x80500000-0x8054CFFF FE66 AP
01: CG35 0xC0680000-0xC08E37FF ABCB AP boot
02: CG47 0xC0A00000-0xC0D5C7FF 02C0 AP recovery
Skipping CG35 0xC0680000-0xC09FFFFF
>> waiting for phone: Droid found.
>> uploading RDL03
Uploading: 100% OK
>> verifying ramloader
-- OK
>> executing ramloader
Droid found.
>> sending erase
>> uploading CG47
Uploading: 100% OK
>> verifying CG47
-- OK
>> rebootingI hit the 'X' key right after running sbf_flash and boot into the SPRecovery no problem. I navigate to the proper choice (as explained in your tut) and my output is:
-- Install from sdcard...
Finding update packages...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
I've tried about 15 times now - with multiple tries each time I flash (I'm OCD so that helps
) with no luck.I have stock Froyo which I got OTA'd about a week ago. I have a Motorola Droid (original, no X and no II). Thanks for any help you can provide.
-- Edit: Forgot to add that I tried both update.zip's that you have linked in this thread. Both give the same error.
OMJ
Bazinga
I'm also having this issue. Everything went fine up to this point though. I was able to flash the recovery with no errors on the output.
Code:SBF FLASH 1.08 (mbm) Droid found. CG63 0xC0000000-0xC001FFFF mbmloader.img CG30 0xC0020000-0xC00BFFFF mbm.img CG55 0xC00C0000-0xC015FFFF mbmbackup.img CG31 0xC0160000-0xC01BFFFF cdt.bin CG38 0xD01CE000-0xD0359FFF pds CG34 0xC035A000-0xC03BCFFF lbl CG57 0xC03BD000-0xC041FFFF lbl_backup CG41 0xC0400000-0xC057FFFF sp CG42 0xC0580000-0xC061FFFF logo.bin CG44 0xC0620000-0xC067FFFF misc CG35 0xC0680000-0xC09FFFFF boot CG47 0xC0A00000-0xC0E7FFFF recovery CG39 0xD0EF4000-0xD9FB6FFF system CG40 0xD9FB7000-0xDFF3BFFF cache CG37 0xDFF3C000-0xF0D29FFF userdata CG53 0xDFD40000-0xDFF3FFFF kpanic Index[1]: Unexpected chip 16 Index[2]: Unexpected chip 16 === SPRecovery_ESE81.sbf === 00: RDL03 0x80500000-0x8054CFFF FE66 AP 01: CG35 0xC0680000-0xC08E37FF ABCB AP boot 02: CG47 0xC0A00000-0xC0D5C7FF 02C0 AP recovery Skipping CG35 0xC0680000-0xC09FFFFF >> waiting for phone: Droid found. >> uploading RDL03 Uploading: 100% OK >> verifying ramloader -- OK >> executing ramloader Droid found. >> sending erase >> uploading CG47 Uploading: 100% OK >> verifying CG47 -- OK >> rebooting
I hit the 'X' key right after running sbf_flash and boot into the SPRecovery no problem. I navigate to the proper choice (as explained in your tut) and my output is:
-- Install from sdcard...
Finding update packages...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
I've tried about 15 times now - with multiple tries each time I flash (I'm OCD so that helps
I have stock Froyo which I got OTA'd about a week ago. I have a Motorola Droid (original, no X and no II). Thanks for any help you can provide.
-- Edit: Forgot to add that I tried both update.zip's that you have linked in this thread. Both give the same error.
are you getting into SPRecovery or are you getting the triangle with the !
Scottmc
Member
I'm booting into SPRecovery. The problem was I missed the step that said to select Allow Update.zip (or something like that). I clicked in while I was in there and it started working. So then I thought, hey, that step wasn't in the tut. So I went back, and sure enough it was there so my bad 
.
I finally did get it to work and then I ran into many problems. I got into a constant reboot cycle with Force Close popping up every 2 minutes. My droid would just sit there and reboot on it's own every couple of minutes. I had no signal it wouldn't even recognize the USB cable. I thought I was toast but then I read how to unroot and I was able to get a stock image using RDSLite (thank God for that tool, even though I had to boot up my dusty windoze image to use it).
After I flashed the stock image everything was fine - but I lost all my settings. A small price to pay to not have a $400 paperweight. Now that I know how easy it is to get back I might try again when 2.2 is a little more mature. The update.zip that is linked in this thread causes many problems with my phone.
.I finally did get it to work and then I ran into many problems. I got into a constant reboot cycle with Force Close popping up every 2 minutes. My droid would just sit there and reboot on it's own every couple of minutes. I had no signal it wouldn't even recognize the USB cable. I thought I was toast but then I read how to unroot and I was able to get a stock image using RDSLite (thank God for that tool, even though I had to boot up my dusty windoze image to use it).
After I flashed the stock image everything was fine - but I lost all my settings. A small price to pay to not have a $400 paperweight. Now that I know how easy it is to get back I might try again when 2.2 is a little more mature. The update.zip that is linked in this thread causes many problems with my phone.
OMJ
Bazinga
I'm booting into SPRecovery. The problem was I missed the step that said to select Allow Update.zip (or something like that). I clicked in while I was in there and it started working. So then I thought, hey, that step wasn't in the tut. So I went back, and sure enough it was there so my bad
I finally did get it to work and then I ran into many problems. I got into a constant reboot cycle with Force Close popping up every 2 minutes. My droid would just sit there and reboot on it's own every couple of minutes. I had no signal it wouldn't even recognize the USB cable. I thought I was toast but then I read how to unroot and I was able to get a stock image using RDSLite (thank God for that tool, even though I had to boot up my dusty windoze image to use it).
After I flashed the stock image everything was fine - but I lost all my settings. A small price to pay to not have a $400 paperweight. Now that I know how easy it is to get back I might try again when 2.2 is a little more mature. The update.zip that is linked in this thread causes many problems with my phone.
Honestly Im not quite sure what happened but the update.zip is not the source of your problems. All it does is push the su binary and superuser.apk
Just so you know you can use sbf_flash to flash stock images you just would use the -r --recovery designation. It would look like
./sbf_flash VZW_A855_ESE81_QSC6085BP_C_01.3E.03P_SW_UPDATE_02. sbf
Scottmc
Member
Thanks for the sbf_flash info - that alone is worth the price of admission. Now windoze can gather more mothballs
Yeah, I'm not quite sure what happened either. It was user error, I'm sure. I do have some more confidence, however, after seeing how easy it is to recover from a total eff up.
About the superuser.apk, does that have any OS version specific hooks? In other words, if I push an update.zip up to the wrong os version (2.2 vs 2.01 for eaxmple) would that cause system instability? Maybe I grabbed the wrong version for my OS?
Oh, I did use RDSLite to flash recovery, not sure if that would cause the problem. I couldn't get SPRecovery to run unless I hit 'X' right after sbf_flash runs. After flashing with RDSLite I was able to boot into SPRecovery at will. It was then that I finally found the Enable Update.zip menu choice (which I missed when reading the tut) and was able to finally push the update.zip up.
So two variables there, not sure if either one has any impact. I'll probably try again though.
OMJ
Bazinga
Thanks for the sbf_flash info - that alone is worth the price of admission. Now windoze can gather more mothballs
Yeah, I'm not quite sure what happened either. It was user error, I'm sure. I do have some more confidence, however, after seeing how easy it is to recover from a total eff up.
About the superuser.apk, does that have any OS version specific hooks? In other words, if I push an update.zip up to the wrong os version (2.2 vs 2.01 for eaxmple) would that cause system instability? Maybe I grabbed the wrong version for my OS?
Oh, I did use RDSLite to flash recovery, not sure if that would cause the problem. I couldn't get SPRecovery to run unless I hit 'X' right after sbf_flash runs. After flashing with RDSLite I was able to boot into SPRecovery at will. It was then that I finally found the Enable Update.zip menu choice (which I missed when reading the tut) and was able to finally push the update.zip up.
So two variables there, not sure if either one has any impact. I'll probably try again though.
The versions of superuser that I have posted will work for 2.0 and up. So in terms of the droid they are not os specific.
If you ended up using rsd lite to flash the SPRecovery.sbf then thats the source of the issue. The linux instructions and windows instructions are actually quite different due to the added features that sbf_flash has.
deadpoolkilla
Newbie
Anyone have any comments on this:
Verizon Pushing Out "Full FRG01B" FroYo Update For Rooted Droid Devices | WWWery.com
Scottmc
Member
I actually fell back to the windows instructions after I failed with spf_flash and didn't realize all I had to do was hold down 'X' right after spf_flash runs - you might want to add that to the instructions, just for the simple fact that you won't get asked as many questions.
So sequence of events
Follow Linux instructions
Neglect to press 'X'
Finally figure out pressing 'X' right after sbf_flash takes me to SPRecovery
Failed installing update.zip
Try with second update.zip that you linked in thread (your notes say an older file but still usable)
Still no go
Give up Linux instructions
Follow Windows instructions
Finally notice the Allow Update.zip (or whatever) in SPRecovery menu
I click that
I click install sdrom/update.zip (deprecated)
Install succeeds
I proceed to crap my pants as my phone boots up with no signal, no cable detection, a big red line through the battery, constant reboot cycles and Force Closes.
I find the unroot instructions (that I think you may have written or at least had a part in).
I thank God for RSDLite (and now realize sbf_flash would have worked too) as I reflash the stock verizon image onto my phone.
I take the OTA update and finally get a few hours of sleep in what night I have left.
I have 2.2 stock on my droid and I am confused. I have downloaded SP Recovery and md5sum to my windows desktop and RSDLite is installed. I'm confused where it says download SPRecovery to C: root directory (C:\) and then place md5sum in c:\windows\system32 and then the
6.) Run command prompt (Start->Run then type "cmd" and hit enter)
7.) Change directories to your C:\ root directory (cd c:\)
8.) Type in "md5sum SPRecovery_ESE81.sbf"
9) Make sure the sum of the image is EXACTLY 9b6a336cd8f067d4487935468c758d89
I may be a complete newbie at this cause I've read over and over and it still is confusing to me. Can anyone spell this out for me since I seem to be slow or something.
Thanks for any help
Scottmc
Member
Those are pretty clear instructions but what he is saying - to paraphrase, maybe that might help - is to take the md5sum program (it's an executable) and run it from a command prompt. Use the SPRecovery filename you downloaded earlier as parameters to the command. Like this:
c:> md5sum SPRecovery_ESE81.sbf
The whole point of copying to win32 and your root is to make it easier for you. I personally wouldn't put anything in win32 and would just place both files in the same directory (some sub directory off of root) and execute it there. In fact, that's exactly what I did and it worked like a champ.
Forgot to add - his last line is just saying to compare the output of the MD5 program with what is expected. Don't proceed unless they match!
Ok, so I got the command to work and it showed d41d8cd98f00b204e9800998ecf8427e
That does not match description.
Scottmc
Member
I can't see what would be wrong - unless your md5 program isn't correct for some reason. I'm assuming you typed the command exactly as the tut author showed (and I showed as well).
I just downloaded two different md5 programs. MD5 is an algorithm, so if implemented correctly will give identical results with identical inputs even if a different program is implementing it. I ran both md5 programs on 3 vms and my box at work - all without issue. I am running XP at work (yeah, I know, but it pays the bills) and ran it in XP VMs (XP Professional SP3 all with latest and greatest updates). Still no issues.
Check connectivity and make sure no errors occurred while downloading the md5 program. Sometimes Spybot and Virus checking programs can reach into the files you are reading or writing. I've seen that cause issues as well.
frankwright
Lurker
Anyone know this?? after doing this what do we do when the second froyo update hits?
Was having the same problem as Grid but like he said nvm kept hitting it and rebooted my droid again and worked fine 2nd time around
Hey guys, I used this method (Windows) 2 weeks ago to root my Moto Droid (1) and all went fine. Was rooted for 3 days then my screen went black and I'm getting replacement through warranty (hopefully they won't be able to boot it to see it's rooted..or will they?).
My question is, is there possibly anyway that when Verizon tried to send/or check to send 2.2 it saw root and bricked me? I know its a conspiracy theory but I also read about the technology on the newer droids that can do that and wondered if it was something in the ROM. Isn't there an app that blocks Verizon from forcing an update or is that just something you need if you are NOT rooted?
thanks
My question is, is there possibly anyway that when Verizon tried to send/or check to send 2.2 it saw root and bricked me? I know its a conspiracy theory but I also read about the technology on the newer droids that can do that and wondered if it was something in the ROM. Isn't there an app that blocks Verizon from forcing an update or is that just something you need if you are NOT rooted?
thanks
OMJ
Bazinga
If verizon could brick our phones there would be a lot of bricked droids out there. You have to agree to install updates on your phone. It doesnt happen without you pressing install.
OMJ
Bazinga
yea it works on FRG01B