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

[adr3nalin3]

is it possible that a program on my computer or app on my phone may be preventing the flashing process? or is it simply an issue with RSDLite? please helpp!!!!!


edit*

No matter what I do, I get this error in the log file in my RSDLite folder. I have moved the SPRecovery file almost everywhere on my hardrive, run RSDLite in every compatibility mode offered, and ran it as an administrator on all of them...


13:37:17, July 19, 2010
Line: 865
ERROR: \\?\c:\sprecovery_ese81.sbfug8

 

[megah1tz]

Do you not have another computer to try it on? Some of the info in this thread is misleading...

 

[adr3nalin3]

Yeah, I asked my friend to bring his laptop over later today, so i'm hoping that will solve my problems

 

[jayhawk_j]

I'm running windows 7 x64 and keep getting the same error as well. I've tried the .sbf in the C: root, My Docs, etc, UAC is off, and I'm running as admin. The only way for me to even click start is to have the .sbf in the C: root. Anyone know anything else I can try?

 

[mrmuskrat]

I was having the 0x7100 error on Win7 64 bit. I first upgraded to the 4.6.5 drivers but that didn't help. I then changed the DeviceId options so that it used automatic DeviceId mode and it was able to apply the update.

 

[jayhawk_j]

When I change the DeviceId to automatic it won't even recognize my phone.

 

[rezo]

Computer engineer here. Registered so I could post this and hopefully help a few of you guys out

I was running into the same problem, with Win7 x64, RSD Lite 4.6, latest drivers. Did some investigation into the error log and looks like I found a bug in their programming. Go into the directory you installed RSD Lite (for Win7 x64 the default is C:\Program Files (x86)\Motorola\RSD Lite\) and look for a file that starts with "FlashErrorLog". Open it, and if you see something like this:

Line: 865
ERROR: \\?\c:\SPRecovery_ESE81.sbfwtƒyo

 

[jayhawk_j]

I'll give it a shot tonight and I'll post if it works.

 

[jayhawk_j]

When I rename the file RSD Lite will no longer recognize it.

 

[madmike20]

brand new to the forums and totally new to rooting. downloaded rsd lite, the .sbf. the drivers. flashed the sbf with rsd lite and it went through this long process of installing then failed at the end. freaked out and turned my phone on and 2.0.1 is installed.(had to sign into my google account) phone seems to run fine even though it said flashing failed. should i be worried and do it again?

 

[rezo]

When I rename the file RSD Lite will no longer recognize it.

Don't change the file extension - only add characters before the ".sbf". Changing the file name to "r.sbf1234" will cause it to be not recognized by RSD Lite. You need to change it to something like "r1234.sbf". Let me know if it works out for you.

brand new to the forums and totally new to rooting. downloaded rsd lite, the .sbf. the drivers. flashed the sbf with rsd lite and it went through this long process of installing then failed at the end. freaked out and turned my phone on and 2.0.1 is installed.(had to sign into my google account) phone seems to run fine even though it said flashing failed. should i be worried and do it again?

If the part it failed at was "trying to communicate with phone", then you are fine and it probably installed correctly. The reason it says there is an error here is because after it flashes and reboots, your phone loads the normal image but RSD Lite is expecting it to go into the boot loader. So you most likely are fine and can continue with your rooting/ROM loading guide.

 

[indyandrew]

I had the same problem read through this thread and finally rezo's instructions worked.

Thanks, luckily I didn't have to work at it for too long but I would have drove myself crazy trying to figure it out if I hadn't found this.

 

[OMJ]

Computer engineer here. Registered so I could post this and hopefully help a few of you guys out

I was running into the same problem, with Win7 x64, RSD Lite 4.6, latest drivers. Did some investigation into the error log and looks like I found a bug in their programming. Go into the directory you installed RSD Lite (for Win7 x64 the default is C:\Program Files (x86)\Motorola\RSD Lite\) and look for a file that starts with "FlashErrorLog". Open it, and if you see something like this:

Line: 865
ERROR: \\?\c:\SPRecovery_ESE81.sbfwt

 

[deftdrummer]

Just for the record, it is important to drag and drop the pst_flash.ini file that comes with the RSDLite download into the RSDLite folder in the program files. I had the same error y'all did until I did this. It makes sense that the file is related to flashing the rom right?

BTW I am running an unrooted Droid X

 

[dominodreams]

Ugh...

I installed the right driver - 32-bit - and I've followed every instruction to the "t"... But this is what I get:

Line: 235
ERROR: Phone[0000]: Phone is not compatible with multi-interface super-file.
File: D:\test_dev_usb\flash\code\flashdll\MIFlash.cpp
Device ID: 0

21:49:28, August 09, 2010
Line: 1183
ERROR: Phone[0000]: Flash failed.
File: D:\test_dev_usb\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0

21:49:28, August 09, 2010
Line: 587
ERROR: Flash failure: Phone[0000]: Phone is not compatible with multi-interface super-file. (Error Code: 3b),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=No Codegroup
File: D:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0

What gives??

EDIT: Lawl...
I answered my own question, but in case anyone else runs into this problem, you'll probably feel as silly as I do...

The "pst_flash.ini" file that comes in the RSDLite-4.7 zip file is the patch. It needs to replace the pst_flash.ini that the installer loads in the program files.

I couldn't figure out why the instructions would say to put the file in there if it was already in there.... Yes, I am blonde. But at least I figured it out eventually...

DX just rebooted. It didn't touch my apps or my settings! Score!

 

[luca992]

I have windows 7 x64 and i couldn't get it to work initially. Since the start was grayed out when I put the file in the my documents folder like someone said earlier. I just moved the file to the public documents folder and it worked fine!

 

[pERUVIANeDDIE]

You are the man, this totally worked for me! DX

 

[pERUVIANeDDIE]

This was the post I was saying thank you


Computer engineer here. Registered so I could post this and hopefully help a few of you guys out

I was running into the same problem, with Win7 x64, RSD Lite 4.6, latest drivers. Did some investigation into the error log and looks like I found a bug in their programming. Go into the directory you installed RSD Lite (for Win7 x64 the default is C:\Program Files (x86)\Motorola\RSD Lite\) and look for a file that starts with "FlashErrorLog". Open it, and if you see something like this:

Code:
Line: 865
ERROR: \\?\c:\SPRecovery_ESE81.sbfwtƒyo

 

[BlakeDC]

Great Post thanks Rezo

EPIIIIIIC victory. I was working with the Droid X and the effer would not flash. RSD wouldn't even read the sbf file in the file properties box. i used this, and renamed my file to 4 characters in length, and it populated all the file properties and it let me execute i'm at 63% done right now.
Thank you for being epic!

 

[y2k2]

Computer engineer here. Registered so I could post this and hopefully help a few of you guys out

I was running into the same problem, with Win7 x64, RSD Lite 4.6, latest drivers. Did some investigation into the error log and looks like I found a bug in their programming. Go into the directory you installed RSD Lite (for Win7 x64 the default is C:\Program Files (x86)\Motorola\RSD Lite\) and look for a file that starts with "FlashErrorLog". Open it, and if you see something like this:

Line: 865
ERROR: \\?\c:\SPRecovery_ESE81.sbfwt

 

[whitehme]

I finally got it to work by renaming the file as r.sbf

 

[misdirection]

I tried everything and it doesn't work...... bah

 

[misdirection]

I finally got it to work by renaming the file as r.sbf

Didn't work.

 

[misdirection]

This worked for me Thanks so much

Didn't work at all

 

[misdirection]

rq