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

Root HELP!! SBF Failed

Battery got too low. It's plugged in right now so I'll have to try it later

Sorry to tell you, but your battery is not going to charge.

You are going to have to end up going to verizon and see if they will charge it for you, or do the a trick with a spliced up usb cable. Unless you have a friend with a DX, you could use his/her charged up battery.

Post #17 here if you are up to it:

http://androidforums.com/droid-x-all-things-root/270129-i-think-my-droid-x-goner.html
 
dang it....you guys always get to deliver the bad news....whens it my turn? :D:eek:
 
Alright... it took til Monday, but I'm back with a charged battery. Tried the latest sbf file you gave me (the_gift2, VRZ_MB810_2.3.15_1FF_01) and I still get a fail.

Phone still says:

Bootloader
30.01

Code Corrupt

Battery OK
OK to Program
Transfer Mode: USB

I'm using the Motorola 32 bit drivers v4.6. I have Windows Vista on my computer. I have RSD Lite v4.8. What am I missing?????
 
Alright... it took til Monday, but I'm back with a charged battery. Tried the latest sbf file you gave me (the_gift2, VRZ_MB810_2.3.15_1FF_01) and I still get a fail.

Phone still says:

Bootloader
30.01

Code Corrupt

Battery OK
OK to Program
Transfer Mode: USB

I'm using the Motorola 32 bit drivers v4.6. I have Windows Vista on my computer. I have RSD Lite v4.8. What am I missing?????

Maybe try the latest drivers too, they're at 4.9.0 now I believe.
 
Here's a quick log I tried to type up while it was running.

VRZ_MB810_1.13.6.2_1FF_01.sbf

Phone(0000): Creating Image File.
something to quick to read
Interface AP-OS: Flashing Code Group
Interface AP-OS: Flashing Code Group 33
Interface AP-OS: Flashing Code Group 39
(Phone changes to SW Update In progress...)
Interface AP-OS: Flashing Code Group 66
Interface AP-OS: Flashing Code Group xx checksums match
Interface AP-OS: Flashing Code Group 35 checksums match
Interface AP-OS: Flashing Code Group 65 checksums match
Phone(oooo): Switching device to BP passthrough mode
Interface BP: Switching to bootloader
Interface BP: Flashing Code Group 3
Phone(0000): Phone is being rebooted
Finished. Result = Pass

Phone still says Err:A5,70,70,00,1F
 
I'm just wondering, are you using one of the usb ports on the front of the computer or a usb port on the actual motherboard? I've heard of people having problems when not using usb ports on the actual motherboard.
 
I'm using one of the USB ports on the right side of my Lenovo T60. There's also one on the left, but I typically use the ones on the right side.
 
Oh, you're using a laptop, I don't that should be an issue then; I've never used my laptop to sbf, but I'm sure others have though.

Did you install the drivers before you started doing stuff to your phone; did you make sure the everything was working correctly (all drivers installed correctly, prior to attempting any sbf'ing), usb debugging, etc.
 
After "failing" with 1.13 but getting to the phone rebooting, which is farther than I had made it before, I went ahead and tried the 2.3.15 file. I'm successfully SBFed now. Thank you to everyone who took the time to respond and try to help!
 
After "failing" with 1.13 but getting to the phone rebooting, which is farther than I had made it before, I went ahead and tried the 2.3.15 file. I'm successfully SBFed now. Thank you to everyone who took the time to respond and try to help!

What sbf were you trying before? Were you trying 2.3.320? I'm pretty sure that requires you to be on at least bootloader 30.03, and you are/were on 30.01, therefore the sbf was not working.

You should now be on bootloader 30.03 after sbf'ing to 2.3.15, and can now do the newly released 2.3.340 sbf.

Check your bootloader version by:

Pressing and holding both volume keys, while still holding down the volume keys, press the power button and your phone will go into bootloader mode and tell you what bootloader version you have.

Anyway, glad you were able to sbf and get your phone going again.
 
I had tried several versions of 2.3.15 and that 1.13 before. Don't know why it decided to actually work this last time, but I'm glad I did.

Can I not OTA upgrade to 2.3.340 instead of SBFing? I thought I should be able to go at it that way now. Do I need to do the 320 SBF before the 340?
 
I had tried several versions of 2.3.15 and that 1.13 before. Don't know why it decided to actually work this last time, but I'm glad I did.

Can I not OTA upgrade to 2.3.340 instead of SBFing? I thought I should be able to go at it that way now. Do I need to do the 320 SBF before the 340?

Yeah, you could do that too (OTA) :D

No need to use 2.3.20 anymore now that 2.3.340 full sbf is out.
 
If you get the ota, you do NOT want to sbf with 2.3.15 or anything less than 2.3.32, or you'll be in a similar mess.
 
Hi I have the same issue as droidxuser.

My droid x's bootloader is 30.04

I am using 2.3.32 sbf.

I am usin RSD Lite v 4.9 and used the latest drivers from motorola.

I am using VMWare Fusion and running Windows 7 32 bit on my macbook.

I put the sbf file into my documents and renamed it to simply r.sbf because i read from another post that it would be easier for RSD to find it.

I used the ghetto usb method of charging my phone but I have no idea if it is 50 percent or not. According to another guide (the one where i learned about the ghetto usb method), the user charged his for 6-7 minutes. Is that all you need or do you need at least 50 percent for it to work?

I have the same results as droidxuser's log except it failed instead of passing.

Phone(0000): Creating Image File.
something to quick to read
Interface AP-OS: Flashing Code Group
Interface AP-OS: Flashing Code Group 33
Interface AP-OS: Flashing Code Group 39
(Phone changes to SW Update In progress...)
Interface AP-OS: Flashing Code Group 66
Interface AP-OS: Flashing Code Group xx checksums match
Interface AP-OS: Flashing Code Group 35 checksums match
Interface AP-OS: Flashing Code Group 65 checksums match
Phone(oooo): Switching device to BP passthrough mode
Failed flashing process. Failed flashing process. Phone [0000]: Error switching phone to BP Pass through mode (0x70BE); phone disconnected.

I'm going crazy over this thing man.

Is there anything else I need to do or what am I doing wrong?? Any help would be highly appreciated.
 
Hi I have the same issue as droidxuser.

My droid x's bootloader is 30.04

I am using 2.3.32 sbf.

I am usin RSD Lite v 4.9 and used the latest drivers from motorola.

I am using VMWare Fusion and running Windows 7 32 bit on my macbook.

I put the sbf file into my documents and renamed it to simply r.sbf because i read from another post that it would be easier for RSD to find it.

I used the ghetto usb method of charging my phone but I have no idea if it is 50 percent or not. According to another guide (the one where i learned about the ghetto usb method), the user charged his for 6-7 minutes. Is that all you need or do you need at least 50 percent for it to work?

I have the same results as droidxuser's log except it failed instead of passing.

Phone(0000): Creating Image File.
something to quick to read
Interface AP-OS: Flashing Code Group
Interface AP-OS: Flashing Code Group 33
Interface AP-OS: Flashing Code Group 39
(Phone changes to SW Update In progress...)
Interface AP-OS: Flashing Code Group 66
Interface AP-OS: Flashing Code Group xx checksums match
Interface AP-OS: Flashing Code Group 35 checksums match
Interface AP-OS: Flashing Code Group 65 checksums match
Phone(oooo): Switching device to BP passthrough mode
Failed flashing process. Failed flashing process. Phone [0000]: Error switching phone to BP Pass through mode (0x70BE); phone disconnected.

I'm going crazy over this thing man.

Is there anything else I need to do or what am I doing wrong?? Any help would be highly appreciated.
ok try to use rsd 4.8 that has worked for many others for some reason and there is no reason to be using the 2.3.32 sbf when you can esily use the 2.3.340 full sbf ,here is a link for that sbf
Full 2.3.340 Official sbf

those links should still work:D
 
Just chiming in here because I have this exact issue with one of my pc's when I try to sbf, but I am lucky I have multiple pc's and it seems to be a problem with the usb port, or the pc, not sure because I just finished using the same sbf that previously failed on my laptop and it finished successfully.

if you don't have another pc, how about at work?

hope this helps.

g.

Hi I have the same issue as droidxuser.

My droid x's bootloader is 30.04

I am using 2.3.32 sbf.

I am usin RSD Lite v 4.9 and used the latest drivers from motorola.

I am using VMWare Fusion and running Windows 7 32 bit on my macbook.

I put the sbf file into my documents and renamed it to simply r.sbf because i read from another post that it would be easier for RSD to find it.

I used the ghetto usb method of charging my phone but I have no idea if it is 50 percent or not. According to another guide (the one where i learned about the ghetto usb method), the user charged his for 6-7 minutes. Is that all you need or do you need at least 50 percent for it to work?

I have the same results as droidxuser's log except it failed instead of passing.

Phone(0000): Creating Image File.
something to quick to read
Interface AP-OS: Flashing Code Group
Interface AP-OS: Flashing Code Group 33
Interface AP-OS: Flashing Code Group 39
(Phone changes to SW Update In progress...)
Interface AP-OS: Flashing Code Group 66
Interface AP-OS: Flashing Code Group xx checksums match
Interface AP-OS: Flashing Code Group 35 checksums match
Interface AP-OS: Flashing Code Group 65 checksums match
Phone(oooo): Switching device to BP passthrough mode
Failed flashing process. Failed flashing process. Phone [0000]: Error switching phone to BP Pass through mode (0x70BE); phone disconnected.

I'm going crazy over this thing man.

Is there anything else I need to do or what am I doing wrong?? Any help would be highly appreciated.
 
I am using VMWare Fusion and running Windows 7 32 bit on my macbook.

Just chiming in here because I have this exact issue with one of my pc's when I try to sbf, but I am lucky I have multiple pc's and it seems to be a problem with the usb port, or the pc, not sure because I just finished using the same sbf that previously failed on my laptop and it finished successfully.

if you don't have another pc, how about at work?

+1

Running a virtual machine on a non-windows computer is not an optimal environment. It might work, but if you're having trouble, I'd try a Windows computer.
 
Back
Top Bottom