• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root SBF Recovery issue with frg01b

rollo

Newbie
Aug 7, 2010
10
1
I have moto droid with latest OTA update FRG01B on the phone. Wanted to go back to root so was going to install SBF recovery.

Tried to install SPFRecovery_ESE81.sbf both from linux and window$ but failed on both machines. Also tried Peter's SPFRecovery_FRG01B.sbf but failed to install from linux but haven't tried with window$.
I'm not home but have the output for linux when failed but not for RSDlite as I did that on friends pc. The md5sum was good for the ESE81 but didn't find md5sum for peters frg01b.sbf .

Would like to root from here but if have to follow OMJ's guide to get back to stock 2.1 then root from there so be it.

Any help is appreciated and thanks in advance.
 
At what time is it "failing"? If it fails in the middle, your phone shouldnt work. If it fails at the very end, that is normal. Is your phone not down to 2.1?

also, try downgrading to 2.0.1 then rooting. See if that helps:

Step 1, go to stock 2.0.1
http://www.mediafire.com/?o2jetlnyn34[file link removed]

Step 2, download to root. ONLY on 2.0.1!
http://synaintel.com/droid/update.zip

Then, begin your rooting.
 
  • Like
Reactions: rollo
Upvote 0
At what time is it "failing"? If it fails in the middle, your phone shouldnt work. If it fails at the very end, that is normal.
It seems from the beginning in window$ and linux. Phone still functions normally and stock recovery is still functioning. Linux completed the task but recovery didn't stick, but near beginning said something (panic or error) but can't remember exactly what .

Is your phone not down to 2.1?

also, try downgrading to 2.0.1 then rooting. See if that helps:

Step 1, go to stock 2.0.1
http://www.mediafire.com/?o2jetlnyn34[file link removed]

Step 2, download to root. ONLY on 2.0.1!
http://synaintel.com/droid/update.zip

Then, begin your rooting.
No, phone is updated to FRG01B. Sorry must have stated incorrectly before. Was trying to root from here but said if I had to go back to stock 2.1 ,like before using OMJ's guide I would, then root from there. Unless your saying I won't be able to root from stock 2.1 Jedii?


Also, VERY important. Update all of your Motorola Drivers!
Drivers are up to date on the window$ pc.

And update your RSDLite - the one at Pete's is version 4.7, elsewhere you find 4.6
Now this I haven't done so will have to update RSDlite to latest.

Thank you both for such quick responses. Really good site and members. I will have to wait till get off work tonight to downgrade to stock 2.1 then root. Wish I would've left phone alone now when from when I manually updated an rooted frg22 per OMJ's tutorial.
 
Upvote 0
Code:
1st time tring to install just sbf recovery

bash-3.1$ sudo ./sbf_flash -r --recovery SPRecovery_ESE81.sbfSBF 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
Code:
2nd time - tried to flash stock 2.1 sbf

sudo ./sbf_flash -r --recovery VZW_A855_ESE81_QSC6085BP_C_01.3E.03P_SW_UPDATE_02.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

Data[4]: start_addr incorrect
=== VZW_A855_ESE81_QSC6085BP_C_01.3E.03P_SW_UPDATE_02.sbf ===
00: RDL03 0x80500000-0x8054CFFF 62D6 AP
01: RDL01 0x00150000-0x001FFFFF 88CB BP
02:  CG03 0x00000000-0x008C25BF 4A29 BP
03:  CG31 0xC0160000-0xC01637FF F15F AP cdt.bin
04:  CG34 0xC0340000-0xC03437FF 8F6F AP lbl
05:  CG35 0xC0680000-0xC08E3FFF DA2C AP boot
06:  CG37 0xDFF3C000-0xDFF3D07F F6CE AP userdata
07:  CG39 0xD0EF4000-0xD86879FF 4E73 AP system
08:  CG42 0xC0580000-0xC05BFFFF 73E3 AP logo.bin
09:  CG47 0xC0A00000-0xC0CA17FF 43F3 AP recovery

Skipping CG31 0xC0160000-0xC01BFFFF
Skipping CG34 0xC0340000-0xC039FFFF
Skipping CG35 0xC0680000-0xC09FFFFF
Skipping CG37 0xDFF3C000-0xF0D29FFF
Skipping CG39 0xD0EF4000-0xD9FB6FFF
Skipping CG42 0xC0580000-0xC061FFFF
 >> 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
Code:
This time I tried in window$
MODEL = SE Flash OMAP3430 MI
PORT = 1
PORT TYPE = USB
IME/ESN/MEID= N/A
STATUS = failed flashing process. failed flashing process. Phone(0000): phone did not re-enumerate after RAM -downloader was sent (0x703E)
: phone disconnected, 
PROGRESS = executed 100% 
RESULT = fail
I did notice after trying to flash with linux that (by mistake) pressing the "x" during reboot after flash it would go into SBF Recovery so tried to update but failed. If I allowed phone to reboot then power down and then back on while pressing "x" per instructions it would go to stock recovery (triangle with exclamation point). The update.zip is in the root of sdcard.

I updated to RSDLite 4.7 and made sure drivers were updated in window$ (XP Pro SP2 ). I tried both as user and admin in XP. The .sbf file is in the C:/ folder/directory. In windows the fail came at the end of process. Phone is still functioning fine but still have stock FRG01B.
 
Upvote 0
Thank you OMJ for the leg work you're doing with the Linux tut., I hope the output will help you and others with this issue, but maybe just user error lol.

I never got sbf recovery installed on the phone, I rooted using Universal Androot. Worked great on my moto droid with OTA update FGR01B. I get to try using the 2.0 or 2.0.1 SBF's but some say must use them for froyo, not sure.

The tut's you have stickied worked great for me the other times I tried them before I updated OTA to FRG01B.

I definitely like using Linux over window$ for anything. If it helps I use Slackware 12.0 .

Thanks to all!!!

Edit: Here's the guide I used with Universal Androot .
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones