Go Back   Android Forums > Android Phones > Motorola Droid > Droid - All Things Root
Droid - All Things Root Rooting, ROMS, Overclocking, etc.

Like Tree1Likes

test: Reply
 
LinkBack Thread Tools
Old May 5th, 2010, 11:59 PM   #1 (permalink)
Member
Thread Author (OP)
 
Join Date: Jun 2009
Posts: 314
 
Device(s):
Carrier: Verizon

Thanks: 6
Thanked 8 Times in 4 Posts
Default If you get "Failed Flashing process. (0x7100)" in RSD Lite

I just had this problem and I've seen other people having the same issue. I found the solution, at least for me, so I thought I'd share it. I was trying to flash the SPrecovery spf file using RSD Lite, but it would fail immediately. I found someone else on another forum who discovered that the file had to be in the root of his C: drive for this to work. I gave it a shot and it worked with no problems. This seems really strange. I think he was running Vista. I'm running Vista 64-bit. I was already running RSD Lite as administrator, so that alone didn't help. Moving the file to the root of C: was the fix.

Hope that helps...

Advertisements
johninbigd is offline  
Reply With Quote
The Following 5 Users Say Thank You to johninbigd For This Useful Post:
DroidAddict (May 8th, 2010), johnlgalt (February 24th, 2011), mbrooks537 (July 30th, 2010), proud2bawesome (June 25th, 2010)
sponsored links
Old May 17th, 2010, 11:45 AM   #2 (permalink)
New Member
 
Join Date: May 2010
Posts: 7
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

I couldnt even start the process until I had moved the .sbf file to the root of my C drive. I can click start now but it fails immediately every time.
jive495 is offline  
Reply With Quote
Old May 17th, 2010, 11:47 AM   #3 (permalink)
Member
Thread Author (OP)
 
Join Date: Jun 2009
Posts: 314
 
Device(s):
Carrier: Verizon

Thanks: 6
Thanked 8 Times in 4 Posts
Default

Quote:
Originally Posted by jive495 View Post
I couldnt even start the process until I had moved the .sbf file to the root of my C drive. I can click start now but it fails immediately every time.
What OS? Are you running RSD Lite as administrator?
johninbigd is offline  
Reply With Quote
Old May 17th, 2010, 12:01 PM   #4 (permalink)
New Member
 
Join Date: May 2010
Posts: 7
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Im running Win7 and yes
jive495 is offline  
Reply With Quote
Old May 17th, 2010, 12:30 PM   #5 (permalink)
Member
 
Nicks88's Avatar
 
Join Date: Nov 2009
Location: Dallas/Ft. Worth, TX by way of Long Island, NY
Posts: 337
 
Device(s): HTC Incredible
Carrier: Not Provided

Thanks: 5
Thanked 59 Times in 36 Posts
Default

Make sure you have updated to the latest versions of the drivers and RSD Lite. I kept having the same issues until I upgraded to RSD Lite 4.6. Windows 7 here as well. I was so frustrated, but it will work! Keep at it!

Edit: I also tried moving the file around as well at first, but when I upgraded, it didn't matter.
Nicks88 is offline  
Reply With Quote
Old May 22nd, 2010, 03:04 AM   #6 (permalink)
New Member
 
Join Date: May 2010
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

I have been experiencing this same issue. I have tried renaming the .sbf. I have moved the .sbf from my desktop to my root drive. I have tried every USB port my Win7 machine has. I have verified the drivers. And I have tried to force a flash using command line code.

Unfortunately, I have had 'FAIL' at every turn. Any help would be greatly appreciated!

Thanks!
purplejokr is offline  
Reply With Quote
Old May 25th, 2010, 12:21 AM   #7 (permalink)
SJW
New Member
 
Join Date: Nov 2009
Posts: 9
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

I had the same problem, and putting the .sbf file to the root of my C drive didn't help. Finally, I put the file in my "My Documents" folder, and it finally ran. I have no idea why, but it worked for me. I'm running Windows 7 x64.
Hope this helps.
SJW is offline  
Reply With Quote
Old May 30th, 2010, 03:07 PM   #8 (permalink)
New Member
 
Join Date: May 2010
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by SJW View Post
I had the same problem, and putting the .sbf file to the root of my C drive didn't help. Finally, I put the file in my "My Documents" folder, and it finally ran. I have no idea why, but it worked for me. I'm running Windows 7 x64.
Hope this helps.
I tried that and I get the same result. One .sbf won't even let me start it because the button is grayed out while the other .sbf fails every time.
purplejokr is offline  
Reply With Quote
Old May 30th, 2010, 07:51 PM   #9 (permalink)
Member
 
Join Date: Nov 2009
Posts: 120
 
Device(s):
Carrier: Not Provided

Thanks: 10
Thanked 2 Times in 2 Posts
zim2704@gmail.com
Default

Had the problem with greyed out start and failing to run. Even though I was logged in as the admin with vista, I had to go into c:/ - program files - motorola - RSD Lite - and right click on SDL and select run as admin. In order for it to work. Hope this helps.
zim2704 is offline  
Reply With Quote
Old June 17th, 2010, 07:49 PM   #10 (permalink)
New Member
 
Join Date: May 2010
Location: Orange County, CA
Posts: 11
 
Device(s): Moto Droid...Chevy's Simply Stunning w/ ulv 1.25
Carrier: Not Provided

Thanks: 0
Thanked 2 Times in 2 Posts
Default Still not working!!!

I have tried everything suggested above: file in multiple locations (on root of c:\ is the only place RSDLite see's the properties of the file), tried 4.2 driver, updated to the 4.6 driver on Moto site, right clicked an admin, xp compat mode, multiple usb ports....nothing is working!

Here is the error log if anyone can offer any more advice:

17:39:39, June 17, 2010
Line: 865
ERROR: \\?\c:\sprecovery_ese81.sbfu­,eqrurrup was not found.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashFi leIO.cpp
17:39:39, June 17, 2010
Line: 542
ERROR: The superfile specified does not exist
File: X:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
megah1tz is offline  
Reply With Quote
sponsored links
Old June 17th, 2010, 08:02 PM   #11 (permalink)
OMJ
Bazinga
 
OMJ's Avatar
 
Join Date: Nov 2009
Location: Pennsylvania
Posts: 3,288
 
Device(s): Thunderbolt, Fascinate, Nook
Carrier: Not Provided

Thanks: 37
Thanked 831 Times in 456 Posts
OMJ.Droid@gmail.com
Default

are you sure you are using the correct drivers ie 32bit or 64bit? I know it sounds simple but could be the problem
OMJ is offline  
Reply With Quote
Old June 17th, 2010, 08:15 PM   #12 (permalink)
New Member
 
Join Date: May 2010
Location: Orange County, CA
Posts: 11
 
Device(s): Moto Droid...Chevy's Simply Stunning w/ ulv 1.25
Carrier: Not Provided

Thanks: 0
Thanked 2 Times in 2 Posts
Default

Quote:
Originally Posted by OMJ View Post
are you sure you are using the correct drivers ie 32bit or 64bit? I know it sounds simple but could be the problem
Yes....64 bit drivers are the correct ones. I'm not new to "rooting" as I wore my Eris out and have been around here since around Feb., just lurking and learning, but new to the Moto Droid as I decided to upgrade last week!

Anyhow...disregard the issue as I tried on a different computer (same Win7 64 bit OS) and it worked with no issue. Unsure what the hell is up with that!!!
megah1tz is offline  
Reply With Quote
Old June 17th, 2010, 08:23 PM   #13 (permalink)
OMJ
Bazinga
 
OMJ's Avatar
 
Join Date: Nov 2009
Location: Pennsylvania
Posts: 3,288
 
Device(s): Thunderbolt, Fascinate, Nook
Carrier: Not Provided

Thanks: 37
Thanked 831 Times in 456 Posts
OMJ.Droid@gmail.com
Default

Quote:
Originally Posted by megah1tz View Post
Yes....64 bit drivers are the correct ones. I'm not new to "rooting" as I wore my Eris out and have been around here since around Feb., just lurking and learning, but new to the Moto Droid as I decided to upgrade last week!

Anyhow...disregard the issue as I tried on a different computer (same Win7 64 bit OS) and it worked with no issue. Unsure what the hell is up with that!!!
yea I wasnt trying to insinuate that you didnt know what you were doing but its something easily overlooked.

RSD is crazy finicky with win 7 64bit I dont know why but for me it works perfect and others never get it to work at all. Strange
OMJ is offline  
Reply With Quote
Old June 17th, 2010, 11:47 PM   #14 (permalink)
New Member
 
Join Date: Jun 2010
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default Well...

Well i am having the exact same problem, i have also noticed that RSD lite if the phone is on it will recognize IMEI, rom version like this :
IMEI: 355923020356501
Technology: UMTS 3G
Software Version: Blur_Version.0.14.501.MB200.AmericaMovil.en.MX
Flex Version: USAMORTELMXLA020.0R
Bootloader Version: 1446
DRM Version: N/A

... everything, but under the blue screen bootloader i will only see this

IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000515
DRM Version: N / A
Phone Type: Engineering (E100000000000000000000000000)

it fails hen it goes to bootloader screen
i am no expert but i think the easiest way would be to FOrce flash but how and with what program???

please help!!!
batman4u is offline  
Reply With Quote
Old June 18th, 2010, 12:02 AM   #15 (permalink)
Junior Member
 
Join Date: Dec 2009
Posts: 74
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

I had the exact same problem. All I did was move the file into "My Documents" then load it from there and it worked. I also had it in my C drive to begin with, but that change seemed to have made all the difference.
Wazoo is offline  
Reply With Quote
Old June 18th, 2010, 01:24 AM   #16 (permalink)
New Member
 
Join Date: Jun 2010
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

did it just now and letting you know that BEFORE posting a reply i actually read what you said, but still, DRIVERS, LOCATION, PROGRAM is all good and i do have the correct ones... ADMIN running... just cant FLASH!!! i moved it to my documents, even moved my documents to c: (since i had it in d NOT WORKING

thanks for helping but i am really getting frustated for this
batman4u is offline  
Reply With Quote
Old June 18th, 2010, 01:30 AM   #17 (permalink)
New Member
 
Join Date: Jun 2010
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

maybe some drivers or some kind of force flashing... i read Flashrec... what about that? will it work o DEXT/CLIQ? sines its 1.5

BRAINSTORM!!!! get ideas since evryone and alot are stuck with this error oh and for somebody who knows more than i do heres the log file... thanks in advanced and sorry for getting so annoying but more than 2 weeks figuring this out someones has to know

01:17:39, June 18, 2010
Line: 563
ERROR: Phone[0000]: Error sending JUMP command Device API Error: 0xE0030040 Address: 0xB00000 Command: JUMP
File: X:\test_dev_usb\flash\code\flashdll\RDLOp.cpp
Device ID: 0
01:17:39, June 18, 2010
Line: 318
ERROR: Phone[0000]: Error jumping to RAM Downloader
File: X:\test_dev_usb\flash\code\flashdll\RDLOp.cpp
Device ID: 0
01:17:39, June 18, 2010
Line: 1182
ERROR: Phone[0000]: Flash failed.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashTh read.cpp
Device ID: 0
01:17:39, June 18, 2010
Line: 587
ERROR: Flash failure: Phone[0000]: Error sending JUMP command Device API Error: 0xE0030040 Address: 0xB00000 Command: JUMP (Error Code: e0030040),
Detailed Error Details: Direction of the Error=2000, Command Value=500000, Code Group Number=No Codegroup
File: X:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
01:17:54, June 18, 2010
Line: 1492
ERROR: Error getting subscriber unit information.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashTh read.cpp
01:18:09, June 18, 2010
Line: 1492
ERROR: Error getting subscriber unit information.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashTh read.cpp
01:19:13, June 18, 2010
Line: 1492
ERROR: Error getting subscriber unit information.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashTh read.cpp
batman4u is offline  
Reply With Quote
Old June 18th, 2010, 03:07 AM   #18 (permalink)
New Member
 
Join Date: May 2010
Location: Orange County, CA
Posts: 11
 
Device(s): Moto Droid...Chevy's Simply Stunning w/ ulv 1.25
Carrier: Not Provided

Thanks: 0
Thanked 2 Times in 2 Posts
Default

try it on a different computer...tried every combination known to mankind on my laptop and it simply didn't work. Moved to my desktop with same OS & apps and worked 1st time...
megah1tz is offline  
Reply With Quote
Old June 18th, 2010, 07:09 AM   #19 (permalink)
OMJ
Bazinga
 
OMJ's Avatar
 
Join Date: Nov 2009
Location: Pennsylvania
Posts: 3,288
 
Device(s): Thunderbolt, Fascinate, Nook
Carrier: Not Provided

Thanks: 37
Thanked 831 Times in 456 Posts
OMJ.Droid@gmail.com
Default

Quote:
Originally Posted by batman4u View Post
maybe some drivers or some kind of force flashing... i read Flashrec... what about that? will it work o DEXT/CLIQ? sines its 1.5
are you trying to flash a droid SBF file on the CLIQ? If so you are lucky the flash is failing cause it would most likely brick your phone otherwise.
OMJ is offline  
Reply With Quote
Old June 25th, 2010, 08:50 PM   #20 (permalink)
New Member
 
Join Date: Jun 2010
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by johninbigd View Post
I just had this problem and I've seen other people having the same issue. I found the solution, at least for me, so I thought I'd share it. I was trying to flash the SPrecovery spf file using RSD Lite, but it would fail immediately. I found someone else on another forum who discovered that the file had to be in the root of his C: drive for this to work. I gave it a shot and it worked with no problems. This seems really strange. I think he was running Vista. I'm running Vista 64-bit. I was already running RSD Lite as administrator, so that alone didn't help. Moving the file to the root of C: was the fix.

Hope that helps...
Dude, I just now joined this forum for the sole purpose to say thank you. YOU ARE THE EFFING MAN
proud2bawesome is offline  
Reply With Quote
sponsored links
Old July 3rd, 2010, 08:53 AM   #21 (permalink)
Member
 
Join Date: Jan 2010
Posts: 106
 
Device(s):
Carrier: Not Provided

Thanks: 2
Thanked 2 Times in 2 Posts
Default

i had a similar problem, except my button was grayed out. I had to download a .bat patch (available under moto milestone rooting guide). but in order for this to work, i need the sbf in the same folder as rsd lite. I've tried many locations, but in the end it finally worked under desktop! (using vista 32bit).

so what i did was, copied the entire contents of rsd lite and dumped it in the desktop.ugh.
chyau.00 is offline  
Reply With Quote
Old July 6th, 2010, 07:33 PM   #22 (permalink)
Member
 
Join Date: Jul 2010
Posts: 262
 
Device(s):
Carrier: Not Provided

Thanks: 28
Thanked 58 Times in 46 Posts
Default

I just signed up so I could post the solution to this highly annoying problem. For those getting this error as I was for the last 20 minutes, put the sbf file on C:\ and shut off UAC temporarily. Reboot, run RSD Lite and apply the sbf file, and you're good to go. I hope this helps. It also explains the "I did it on another computer" stuff...yea, they probably didn't have UAC running.
SamuriHL is offline  
Reply With Quote
Old July 17th, 2010, 02:49 AM   #23 (permalink)
New Member
 
Join Date: Jul 2010
Location: Santa Ana/Tustin
Posts: 12
 
Device(s): Motorolla Droid
Carrier: Not Provided

Thanks: 2
Thanked 1 Time in 1 Post
Default

I have tried everything listed above.. i've actually been working on my phone for the past 2 hours because of this cursed fail error... but, I am doing this all on my laptop. is it safe to assume that i NEED to root on a desktop???
adr3nalin3 is offline  
Last edited by adr3nalin3; July 17th, 2010 at 02:49 AM. Reason: forgot about language filter! sorry :(
Reply With Quote
Old July 17th, 2010, 10:43 AM   #24 (permalink)
Member
 
Join Date: Jan 2010
Posts: 106
 
Device(s):
Carrier: Not Provided

Thanks: 2
Thanked 2 Times in 2 Posts
Default

nope, mines a laptop. vista 32bit .
chyau.00 is offline  
Reply With Quote
Old July 17th, 2010, 11:52 AM   #25 (permalink)
New Member
 
Join Date: Jul 2010
Location: Santa Ana/Tustin
Posts: 12
 
Device(s): Motorolla Droid
Carrier: Not Provided

Thanks: 2
Thanked 1 Time in 1 Post
Default

arg.... Then I am at a loss for what to try next.

*edit
my friend suggested that i use ROM Manager and flash Clockwork Recovery. Does anyone have insight on this method?
adr3nalin3 is offline  
Last edited by adr3nalin3; July 17th, 2010 at 01:24 PM.
Reply With Quote
Old July 19th, 2010, 03:33 PM   #26 (permalink)
New Member
 
Join Date: Jul 2010
Location: Santa Ana/Tustin
Posts: 12
 
Device(s): Motorolla Droid
Carrier: Not Provided

Thanks: 2
Thanked 1 Time in 1 Post
Default

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.sbfug8f‚qnurnug was not found.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashFi leIO.cpp

13:37:17, July 19, 2010
Line: 542
ERROR: The superfile specified does not exist
File: X:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
adr3nalin3 is offline  
Last edited by adr3nalin3; July 19th, 2010 at 03:40 PM.
Reply With Quote
Old July 20th, 2010, 10:22 AM   #27 (permalink)
New Member
 
Join Date: May 2010
Location: Orange County, CA
Posts: 11
 
Device(s): Moto Droid...Chevy's Simply Stunning w/ ulv 1.25
Carrier: Not Provided

Thanks: 0
Thanked 2 Times in 2 Posts
Default

Do you not have another computer to try it on? Some of the info in this thread is misleading...
megah1tz is offline  
Reply With Quote
Old July 20th, 2010, 10:57 AM   #28 (permalink)
New Member
 
Join Date: Jul 2010
Location: Santa Ana/Tustin
Posts: 12
 
Device(s): Motorolla Droid
Carrier: Not Provided

Thanks: 2
Thanked 1 Time in 1 Post
Default

Yeah, I asked my friend to bring his laptop over later today, so i'm hoping that will solve my problems
adr3nalin3 is offline  
Reply With Quote
Old July 22nd, 2010, 12:02 AM   #29 (permalink)
New Member
 
Join Date: Mar 2010
Posts: 11
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 0 Times in 0 Posts
Default

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?
jayhawk_j is offline  
Reply With Quote
Old July 26th, 2010, 07:21 PM   #30 (permalink)
New Member
 
Join Date: Jul 2010
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

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.
mrmuskrat is offline  
Reply With Quote
sponsored links
Old July 26th, 2010, 10:55 PM   #31 (permalink)
New Member
 
Join Date: Mar 2010
Posts: 11
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 0 Times in 0 Posts
Default

When I change the DeviceId to automatic it won't even recognize my phone.
jayhawk_j is offline  
Reply With Quote
Old July 31st, 2010, 03:21 PM   #32 (permalink)
New Member
 
Join Date: Jul 2010
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 30 Times in 1 Post
Default

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‚qawrawi was not found.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashFileIO.cpp
then you are experiencing this same bug that I had (looks like adr3nalin3 had this problem too). For those fellow programmers out there, looks like they are copying the filename into uninitialized memory and not explicitly adding the NULL terminator, meaning it's pure luck whether the filename is recognized or not. Since the uninitialized memory produces random results, this explains why people have had it work after restarting their computer, trying several times, using a different computer, etc. Hopefully if you follow my instructions below, you will be able to make it work right away.

So the work around for this problem is to rename the file so that the real filename overwrites all the unwanted junk characters at the end. These junk characters are random, and they are likely to change each time you open RSD Lite.

Here are step by step instructions:
  1. Go to the folder where you installed RSD Lite
  2. Delete any files that start with "FlashErrorLog"
  3. Right click on "SDL.exe" and click "Run As Administrator"
  4. Move your recovery file to the root C:\ directory
  5. Rename the recovery file to something short, like "r.sbf", so that you will have space left for the filename to overwrite the junk characters
  6. Try flashing the file with RSD Lite - it will most likely fail, don't worry (if it works then good job, you are lucky )
  7. In the RSD Lite folder, open the newly created FlashErrorLog... file
  8. Count the number of junk characters after the real filename - for example if you have this error:

    Code:
    ERROR: \\?\c:\r.sbfqawra was not found.
    then the junk characters are "qawra" and there are 7 of them, so we are going to add 7 extra letters to the real filename
  9. Rename the file to add the same number of letters/numbers as junk characters in the log file. In this case, we need to add 7, so change the filename to something like "r1234567.sbf" - make sure you add the characters BEFORE the file extension (".sbf"), not after!
  10. Point RSD Lite to the renamed file, click Start, and it should work!

Note that some of the junk characters can't be displayed in the log, so there might actually be 8 of them when you can only see 7, etc. Just repeat the process from step 6, adding 1 character at a time (don't remove any), and it should work after a few tries.

Note that just making the filename really long won't work, you need to be precise so that you only overwrite the extra stuff, nothing more and nothing less.
themib likes this.
rezo is offline  
Last edited by rezo; August 2nd, 2010 at 03:01 PM. Reason: update instructions to note that the extension shouldn't be changed
Reply With Quote
The Following 30 Users Say Thank You to rezo For This Useful Post:
aldo (December 5th, 2010), bsdmom44 (April 15th, 2011), chinkster (July 6th, 2011), cultldr (March 11th, 2011), FoxtrotUniform (August 31st, 2010), GrandMasterB (December 20th, 2010), hannaxbear (July 14th, 2011), johnlgalt (February 24th, 2011), limo (January 4th, 2011), luca992 (January 1st, 2011), m924 (July 14th, 2011), mariaCarolina9 (April 18th, 2011), nevergonnauseth (December 20th, 2010), Nino313 (April 19th, 2011), nycrem91101 (March 24th, 2011), OMJ (August 5th, 2010), One20One (April 17th, 2011), pERUVIANeDDIE (August 20th, 2010), poconopixie (December 15th, 2010), PsyberEMT (December 31st, 2010), schreibman (November 23rd, 2011), sqldroidx (May 19th, 2011), SubtleC (July 12th, 2011), tgadd (December 15th, 2010), theineffablebob (September 6th, 2010), thetomas (November 19th, 2010), tmushy (December 19th, 2010), vatoed (December 21st, 2010), zse45tgb (September 11th, 2011), ztravis (August 16th, 2010)
Old July 31st, 2010, 06:06 PM   #33 (permalink)
New Member
 
Join Date: Mar 2010
Posts: 11
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 0 Times in 0 Posts
Default

I'll give it a shot tonight and I'll post if it works.
jayhawk_j is offline  
Reply With Quote
Old August 1st, 2010, 01:03 AM   #34 (permalink)
New Member
 
Join Date: Mar 2010
Posts: 11
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 0 Times in 0 Posts
Default

When I rename the file RSD Lite will no longer recognize it.
jayhawk_j is offline  
Reply With Quote
Old August 1st, 2010, 01:49 PM   #35 (permalink)
New Member
 
Join Date: Aug 2010
Posts: 8
 
Device(s):
Carrier: Not Provided

Thanks: 6
Thanked 0 Times in 0 Posts
Default

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?
madmike20 is offline  
Reply With Quote
Old August 2nd, 2010, 03:00 PM   #36 (permalink)
New Member
 
Join Date: Jul 2010
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 30 Times in 1 Post
Default

Quote:
Originally Posted by jayhawk_j View Post
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.

Quote:
Originally Posted by 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?
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.
rezo is offline  
Reply With Quote
Old August 5th, 2010, 09:42 AM   #37 (permalink)
New Member
 
Join Date: Aug 2010
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

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.
indyandrew is offline  
Reply With Quote
Old August 5th, 2010, 09:46 AM   #38 (permalink)
OMJ
Bazinga
 
OMJ's Avatar
 
Join Date: Nov 2009
Location: Pennsylvania
Posts: 3,288
 
Device(s): Thunderbolt, Fascinate, Nook
Carrier: Not Provided

Thanks: 37
Thanked 831 Times in 456 Posts
OMJ.Droid@gmail.com
Default

Quote:
Originally Posted by rezo View Post
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.sbfwtyoqawrawi was not found.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashFileIO.cpp
then you are experiencing this same bug that I had (looks like adr3nalin3 had this problem too). For those fellow programmers out there, looks like they are copying the filename into uninitialized memory and not explicitly adding the NULL terminator, meaning it's pure luck whether the filename is recognized or not. Since the uninitialized memory produces random results, this explains why people have had it work after restarting their computer, trying several times, using a different computer, etc. Hopefully if you follow my instructions below, you will be able to make it work right away.

So the work around for this problem is to rename the file so that the real filename overwrites all the unwanted junk characters at the end. These junk characters are random, and they are likely to change each time you open RSD Lite.

Here are step by step instructions:
  1. Go to the folder where you installed RSD Lite
  2. Delete any files that start with "FlashErrorLog"
  3. Right click on "SDL.exe" and click "Run As Administrator"
  4. Move your recovery file to the root C:\ directory
  5. Rename the recovery file to something short, like "r.sbf", so that you will have space left for the filename to overwrite the junk characters
  6. Try flashing the file with RSD Lite - it will most likely fail, don't worry (if it works then good job, you are lucky )
  7. In the RSD Lite folder, open the newly created FlashErrorLog... file
  8. Count the number of junk characters after the real filename - for example if you have this error:

    Code:
    ERROR: \\?\c:\r.sbfqawra was not found.
    then the junk characters are "qawra" and there are 7 of them, so we are going to add 7 extra letters to the real filename
  9. Rename the file to add the same number of letters/numbers as junk characters in the log file. In this case, we need to add 7, so change the filename to something like "r1234567.sbf" - make sure you add the characters BEFORE the file extension (".sbf"), not after!
  10. Point RSD Lite to the renamed file, click Start, and it should work!

Note that some of the junk characters can't be displayed in the log, so there might actually be 8 of them when you can only see 7, etc. Just repeat the process from step 6, adding 1 character at a time (don't remove any), and it should work after a few tries.

Note that just making the filename really long won't work, you need to be precise so that you only overwrite the extra stuff, nothing more and nothing less.
Great Post thanks Rezo
OMJ is offline  
Reply With Quote
Old August 9th, 2010, 02:13 PM   #39 (permalink)
Member
 
Join Date: Nov 2009
Posts: 318
 
Device(s):
Carrier: Not Provided

Thanks: 5
Thanked 12 Times in 11 Posts
Default

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
deftdrummer is offline  
Reply With Quote
Old August 9th, 2010, 09:04 PM   #40 (permalink)
New Member
 
Join Date: Aug 2010
Posts: 5
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 2 Times in 1 Post
Default

Ugh...

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


Quote:
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_FlashTh read.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!
dominodreams is offline  
Last edited by dominodreams; August 9th, 2010 at 11:13 PM.
Reply With Quote
The Following 2 Users Say Thank You to dominodreams For This Useful Post:
BigJim94 (August 23rd, 2010), Zaxxon (July 26th, 2011)
sponsored links
Old August 20th, 2010, 11:14 AM   #41 (permalink)
New Member
 
Join Date: Aug 2010
Posts: 10
 
Device(s):
Carrier: Not Provided

Thanks: 5
Thanked 3 Times in 1 Post
Default

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!
luca992 is offline  
Reply With Quote
Old August 20th, 2010, 08:55 PM   #42 (permalink)
New Member
 
Join Date: Aug 2010
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

You are the man, this totally worked for me! DX
pERUVIANeDDIE is offline  
Reply With Quote
Old August 20th, 2010, 08:56 PM   #43 (permalink)
New Member
 
Join Date: Aug 2010
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

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‚qawrawi was not found.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashFi leIO.cpp
then you are experiencing this same bug that I had (looks like adr3nalin3 had this problem too). For those fellow programmers out there, looks like they are copying the filename into uninitialized memory and not explicitly adding the NULL terminator, meaning it's pure luck whether the filename is recognized or not. Since the uninitialized memory produces random results, this explains why people have had it work after restarting their computer, trying several times, using a different computer, etc. Hopefully if you follow my instructions below, you will be able to make it work right away.

So the work around for this problem is to rename the file so that the real filename overwrites all the unwanted junk characters at the end. These junk characters are random, and they are likely to change each time you open RSD Lite.

Here are step by step instructions:
Go to the folder where you installed RSD Lite
Delete any files that start with "FlashErrorLog"
Right click on "SDL.exe" and click "Run As Administrator"
Move your recovery file to the root C:\ directory
Rename the recovery file to something short, like "r.sbf", so that you will have space left for the filename to overwrite the junk characters
Try flashing the file with RSD Lite - it will most likely fail, don't worry (if it works then good job, you are lucky )
In the RSD Lite folder, open the newly created FlashErrorLog... file
Count the number of junk characters after the real filename - for example if you have this error:

Code:
ERROR: \\?\c:\r.sbfqawra was not found.
then the junk characters are "qawra" and there are 7 of them, so we are going to add 7 extra letters to the real filename
Rename the file to add the same number of letters/numbers as junk characters in the log file. In this case, we need to add 7, so change the filename to something like "r1234567.sbf" - make sure you add the characters BEFORE the file extension (".sbf"), not after!
Point RSD Lite to the renamed file, click Start, and it should work!

Note that some of the junk characters can't be displayed in the log, so there might actually be 8 of them when you can only see 7, etc. Just repeat the process from step 6, adding 1 character at a time (don't remove any), and it should work after a few tries.

Note that just making the filename really long won't work, you need to be precise so that you only overwrite the extra stuff, nothing more and nothing less.
pERUVIANeDDIE is offline  
Reply With Quote
The Following User Says Thank You to pERUVIANeDDIE For This Useful Post:
Foxgguy2001 (September 1st, 2010)
Old August 21st, 2010, 03:23 PM   #44 (permalink)
Junior Member
 
Join Date: Jul 2010
Posts: 36
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 8 Times in 5 Posts
Default

Quote:
Originally Posted by OMJ View Post
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!
__________________
www.BreakAndMake.com
Check out my website. Read articles. Check reviews. Discovery new technology. Build a fence!
My @DroidLanding Story. How I won the Droid X.
BlakeDC is offline  
Reply With Quote
Old August 21st, 2010, 09:55 PM   #45 (permalink)
New Member
 
Join Date: Dec 2009
Posts: 8
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Thumbs up

Quote:
Originally Posted by rezo View Post
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.sbfwtyoqawrawi was not found.
File: X:\test_dev_usb\flash\code\flashdll\PST_FP_FlashFileIO.cpp
then you are experiencing this same bug that I had (looks like adr3nalin3 had this problem too). For those fellow programmers out there, looks like they are copying the filename into uninitialized memory and not explicitly adding the NULL terminator, meaning it's pure luck whether the filename is recognized or not. Since the uninitialized memory produces random results, this explains why people have had it work after restarting their computer, trying several times, using a different computer, etc. Hopefully if you follow my instructions below, you will be able to make it work right away.

So the work around for this problem is to rename the file so that the real filename overwrites all the unwanted junk characters at the end. These junk characters are random, and they are likely to change each time you open RSD Lite.

Here are step by step instructions:
  1. Go to the folder where you installed RSD Lite
  2. Delete any files that start with "FlashErrorLog"
  3. Right click on "SDL.exe" and click "Run As Administrator"
  4. Move your recovery file to the root C:\ directory
  5. Rename the recovery file to something short, like "r.sbf", so that you will have space left for the filename to overwrite the junk characters
  6. Try flashing the file with RSD Lite - it will most likely fail, don't worry (if it works then good job, you are lucky )
  7. In the RSD Lite folder, open the newly created FlashErrorLog... file
  8. Count the number of junk characters after the real filename - for example if you have this error:

    Code:
    ERROR: \\?\c:\r.sbfqawra was not found.
    then the junk characters are "qawra" and there are 7 of them, so we are going to add 7 extra letters to the real filename
  9. Rename the file to add the same number of letters/numbers as junk characters in the log file. In this case, we need to add 7, so change the filename to something like "r1234567.sbf" - make sure you add the characters BEFORE the file extension (".sbf"), not after!
  10. Point RSD Lite to the renamed file, click Start, and it should work!
Note that some of the junk characters can't be displayed in the log, so there might actually be 8 of them when you can only see 7, etc. Just repeat the process from step 6, adding 1 character at a time (don't remove any), and it should work after a few tries.

Note that just making the filename really long won't work, you need to be precise so that you only overwrite the extra stuff, nothing more and nothing less.

This worked for me Thanks so much
y2k2 is offline  
Reply With Quote
Old August 22nd, 2010, 11:13 AM   #46 (permalink)
New Member
 
Join Date: Jul 2010
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

I finally got it to work by renaming the file as r.sbf
whitehme is offline  
Reply With Quote
Old September 5th, 2010, 01:58 AM   #47 (permalink)
Junior Member
 
Join Date: Feb 2009
Posts: 23
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default Failed failed failed!!!

I tried everything and it doesn't work...... bah
misdirection is offline  
Reply With Quote
Old September 5th, 2010, 01:58 AM   #48 (permalink)
Junior Member
 
Join Date: Feb 2009
Posts: 23
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

Quote:
Originally Posted by whitehme View Post
I finally got it to work by renaming the file as r.sbf
Didn't work.
misdirection is offline  
Reply With Quote
Old September 5th, 2010, 01:58 AM   #49 (permalink)
Junior Member
 
Join Date: Feb 2009
Posts: 23
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

Quote:
Originally Posted by y2k2 View Post
This worked for me Thanks so much
Didn't work at all
misdirection is offline  
Reply With Quote
Old September 5th, 2010, 02:22 AM   #50 (permalink)
Junior Member
 
Join Date: Feb 2009
Posts: 23
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

rquru

That works.
misdirection is offline  
Reply With Quote
The Following User Says Thank You to misdirection For This Useful Post:
abrick (April 22nd, 2011)
Reply


Go Back   Android Forums > Android Phones > Motorola Droid > Droid - All Things Root

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 07:55 PM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.