Root If you get "Failed Flashing process. (0x7100)" in RSD Lite

theineffablebob · Sep 6, 2010

adrianvfx · Sep 7, 2010

To be perfectly honest I get this error every time, even after reformats on two of my PC's. My other two never have an issue, and have identical installations on them.
My fix is simply, try it on another computer until you find one that works.

FYI, Running all comps with Intel CPU's, NVDIA GPU'S, WIN 7 64Bit Ultimate, and SSD's all with the same cases and EVGA mboards.

1324356565 · Sep 22, 2010

I turned the phone back on out of bootloader and tried the flash from the :c drive.It worked.

WACOMalt · Oct 11, 2010

You sir, are a badass.

Thank you so much!

fir3dp · Oct 15, 2010

sorry if i brought up an old post. my error shows "error sending jump command device"

any idea?

DEVICE
IMEI: 352296030092249
Technology: UMTS
Software Version: STR_U2_01.1E.23GSMEPU91A_U_91.07.5DI
Flex Version: UCASHLSTABB1B4DEMA039.0R
Bootloader Version: 8089
DRM Version: N/A

FILE

Filename: r.sbf
Creation Date: 08/22/2010 17:59:43
File size: 3428390
RAM DL Version: v0x008098
Bootloader Version: -------------
Platform: 4G OMAP
HAB Type: Signed Production

dogtag · Oct 20, 2010

hapathetical · Oct 28, 2010

Hey! I'm brand new to the forums and just had this same problem with RSD Lite.
I created this account solely to thank rezo. He just saved the life of my beloved Q9H, which had been plagued with corrupt firmware.

But as an ADDITIONAL NOTE TO HIS TIP: PAY CLOSE ATTENTION TO THE JUNK CHARACTERS. Often times, I have found that one of the junk characters is a blank character that takes up zero space. In other words, it is pretty much impossible to see just by looking at the text. Make sure you use the arrow keys or use backspace/delete to make sure there are no hidden characters.

And thank you once again, rezo. It is knowledgeable and insightful people like you who bring value to forums and the internet.

GregTard · Oct 29, 2010

You are the greatest person in the world. I swear I have been trying to find a solution everywhere for weeks for this. Every time I needed to sbf, I would just do it on XP which worked every time. I tried every other thing I could think of and just noticed the junk characters in the log tonight. I searched with that knowledge and found this post. There are so many posts with the same issue that it hard to find this one. None of the others have this solution.

Thanks

harshlad · Dec 6, 2010

I got it.

If U use over Windows Vista ( e.g. Windows 7 ), U'll have to set up following ways.

1. Plz rename sbf file into simple filename. ( e.g. "r.sbf" )
2. Plz replace sbf file into c:\ or d:\

after this, Hmm.. I cannot express exact description because I use Windows 7 Korean Edition.

3. Right click over sbf files and select Property(P) ( maybe. In Korean, "속성(R)" )
4. Select description tab
5. Click " Remove Property and Individual Information " ( maybe. In Korean, "속성 및 개인 정보 제거" )
6. Rename filename into sim... yes, that is.

Okay, that's all. Let's go. :-)

P.S : I'm Korean and My english is so poor. Thx.

tgadd · Dec 15, 2010

tmushy · Dec 19, 2010

Rezo you are the best!!!! Solved my issue

vatoed · Dec 21, 2010

Rezo for Prez!!!!
Smart people are cool.....

DanGarion · Dec 31, 2010

You sir are awesome. I was having a path not found error instead of file not found, but the same thing fixed it. I was able to get my bricked phone reinstalled with the proper sbf. Awesome, no $400 paperweight.

PsyberEMT · Dec 31, 2010

Registered on the forums JUST so I could thank Rezo! Moto...seriously...get ur head in the game with your software...having to edit an errorlog to get firmware to flash!?! Sounds like working on a 70's VW beetle to me LOL. Put pliers here, hold this closed WHILE you try to start it WHILE rolling down a hill WITH a tailwind :-D

lilblack94gt · Jan 2, 2011

I am having this problem trying to root my replacement droid. I am using RSD Lite 4.6. I am currently running 2.2 software and would like to root it. I think my issue is that I am using the wrong .sdf file, but I can't seem to find a newer .sdf file to use.

This is the error log from RSD Lite:

11:09:18, January 02, 2011
Line: 1654
ERROR: Platform is not defined for CDMA_TYPE-OMAP_CHIPSET.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0

11:09:18, January 02, 2011
Line: 1654
ERROR: Platform is not defined for CDMA_TYPE-MSM6800_CHIPSET.
File: D:\test_dev_usb\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0

Any help would be greatly appreciated!

MrDonBonJovi · Jan 14, 2011

this! thank you!

kalel3038 · Jan 19, 2011

but i am runniig into this problem when i put the sbf. file into c: drive can some one help??

15:40:35, January 19, 2011
Line: 868
ERROR: \\?\c:\z.sbfp

tyler1976 · Feb 12, 2011

It helped, definitely!
Tnx!

hiquality · Feb 22, 2011

Thank you rezo! I registered just to thank you...I don't even own an android phone... just updated my linux os on my motorola V8 thanks to you!

Now to be of some help myself:

For those that can't start the updating process after loading the sbf file( the start button is grayed out) try this:

1.Delete the non working sbf file from the disk (the one that you've extracted from the archive)
2.Right click on the archive containing the sbf file and select Properties, then go to general tab and click on Unlock (bottom-right corner).
3.After this has been done extract the sbf file again to a new location(if you previously extracted it somewhere)
4.Load it in RSD Lite and it should work(if it still doesn't work copy the file elsewhere and retry)

Hope it helps someone!
Happy updating!

johnlgalt · Feb 25, 2011

I finally managed to brick my phone somehow. I'm glad I remembered where to find this thread. My solution was to use a small OS partition on the HD that was not protected - the C:\ drive is protected and requires admin privileges. Some hardware will have this, depending upon Trusted Platform version installed, and it may interfere with the process, even with RSDLite running as admin, as I found out in the last hour.

Thanks again OP and Rezo and everyone else.

kruheh · Mar 5, 2011

Hi there,

I'm another one of those who registered just to say thanks! This really nailed it! Thank you!

H9S · Mar 15, 2011

I think just put it simple.

After RSD detect but cant start (*Grey) , just rename the sbf to " XXXXXXXX.SBF" and put it at C: Root.

and start

xakaipandax · Mar 15, 2011

i tried the suggestion and this is my error log, can anyone help me out?

20:34:08, March 15, 2011
Line: 517
ERROR: AP Die ID: 04d0000d25680304000000000400

20:34:08, March 15, 2011
Line: 524
ERROR: BP Die ID: 0000000000000000000000000000

20:34:08, March 15, 2011
Line: 531
ERROR: AP Public ID: ffffffffffffffffffffffffffffffffffffffff

20:34:08, March 15, 2011
Line: 538
ERROR: BP Public ID: 0000000000000000000000000000000000000000

20:40:15, March 15, 2011
Line: 1834
ERROR: Phone[0000]: Error switching phone to BP Pass through mode
File: X:\test_dev_usb\flash\code\flashdll\FlashOp.cpp
Device ID: 0

20:40:26, March 15, 2011
Line: 692
ERROR: Phone[0000]: The "Motorola_Flash" Interface could not be found.

The super-file is not secure and for re-flash;

the phone needs a super-file that is not secure and for reflash.
File: X:\test_dev_usb\flash\code\flashdll\MIFlash.cpp
Device ID: 0

20:40:26, March 15, 2011
Line: 587
ERROR: Flash failure: Phone[0000]: Error switching phone to BP Pass through mode (Error Code: be),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=257
File: X:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0

20:54:48, March 15, 2011
Line: 517
ERROR: AP Die ID: 04d0000d25680304000000000400

20:54:48, March 15, 2011
Line: 524
ERROR: BP Die ID: 0000000000000000000000000000

20:54:48, March 15, 2011
Line: 531
ERROR: AP Public ID: ffffffffffffffffffffffffffffffffffffffff

20:54:48, March 15, 2011
Line: 538
ERROR: BP Public ID: 0000000000000000000000000000000000000000

21:00:54, March 15, 2011
Line: 1834
ERROR: Phone[0000]: Error switching phone to BP Pass through mode
File: X:\test_dev_usb\flash\code\flashdll\FlashOp.cpp
Device ID: 0

21:01:05, March 15, 2011
Line: 692
ERROR: Phone[0000]: The "Motorola_Flash" Interface could not be found.

The super-file is not secure and for re-flash;

the phone needs a super-file that is not secure and for reflash.
File: X:\test_dev_usb\flash\code\flashdll\MIFlash.cpp
Device ID: 0

21:01:05, March 15, 2011
Line: 587
ERROR: Flash failure: Phone[0000]: Error switching phone to BP Pass through mode (Error Code: be),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=257
File: X:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0

6Xxbc · Apr 3, 2011

Re: the junk characters. I had a problem where the maximum length of the filename + path was longer than the number of junk characters (i.e. start button would not enable when I had sorted out the junk characters).
I found the best way to solve this was to shorten my filename to one character (+extension i.e. x.spf), try to use it, then quit and restart RSD Lite several times until a 'null' randomly occurred with only about 5-6 junk characters after my existing file name. Then I could add additional characters (as described above) without going over the total path+file name length limit, whereas previously the null had been too far along the string for this to work.
And massive thanks to johninbigd
In short:
Call your file x.spf and put it in the root of C: (or another such drive)
Try to use it
Check the log, and if there is more than 27 junk characters after your filename, restart RSD Lite and try again. (the 27 junk characters is based on my experience that the maximum path+filename length RSD Lite would accept was 35; C:\x.spf is 8 characters, leaving you with 27 to play with).

Cheers to rezo, whose post saved my a$$.

dagoek · Apr 8, 2011

Root If you get "Failed Flashing process. (0x7100)" in RSD Lite

Android Enthusiast

Newbie

Member

Newbie

Lurker

Lurker

Lurker

Well-Known Member

Lurker

Member

Member

Lurker

Lurker

Lurker

Lurker

Member

Newbie

Lurker

Lurker

Antidisestablishmentarian

Lurker

Lurker

Lurker

Lurker

Lurker