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

Root RSDLite on Windows 7x64 Problems and Solutions

I purposefully did not have links to the sbf since there are too many posts with bad links as it is. Also, I believe it is against the forum rules (I know it is for leaks, not sure about sbf) to post them. Motorola doesn't like either one.

I added links to the OP eventually to guide users in the right direction to help them find an sbf for this reason and I would appreciate it if direct links were not added to this thread. Those threads always end up being way too many posts of:

Those links are dead
Try these
Those are dead too

After all, this thread is for RSDLite support as an application.

Thank you for your help
 
ok well i got the start button to show up... but the file information is still blank
I moved the file to the root of my C drive, that didnt do it, so I renamed the file to X.sbf and ran the SDL as an administrator and now the start button isnt grayed out anymore but no information shows up in the file properties box...
and yeah I am using RSD 4.8
any thoughts on this?
 
Right-click... run as administrator is the fix for a lot of issues with Vista or Win7. Also can right-click on the icon and change to run as admin under compatibility so it always runs that way.

Latest Motorola drivers installed (4.7.1 I think)?
Debug mode turned on (in phone)? Should say in status bar.
USB Connection (in phone) set to PC mode. Again, in status bar.
Browse for sbf file. (I get file properties and MB810 on bottom and says "connected").
If I click on the MB810 on the bottom, I get device properties and it's ready to flash.


IF that doesn't work, install RSD Lite 4.9. Note password is alabama. You'll also need to use that PW to extract the files. Then open the User Manual (PDF) and use that to trouble shoot. I'm hoping it's just a misunderstanding of how the pgm works.
 
ECFfighter7232 said:
ok well i got the start button to show up... but the file information is still blank
I moved the file to the root of my C drive, that didnt do it, so I renamed the file to X.sbf and ran the SDL as an administrator and now the start button isnt grayed out anymore but no information shows up in the file properties box...
and yeah I am using RSD 4.8
any thoughts on this?
Click to expand...

If nothing is showing up in the File properties, I wonder if the file is corrupt. I would download again or try another sbf version just to see if it shows the file information.

If the file info still doesn't show up, you could try to run it to see if it gives an error. It couldn't make it worse than it already is since it does not update the bootloader and that is all you need to flash your phone.
 
GregTard said:
If nothing is showing up in the File properties, I wonder if the file is corrupt. I would download again or try another sbf version just to see if it shows the file information.

If the file info still doesn't show up, you could try to run it to see if it gives an error. It couldn't make it worse than it already is since it does not update the bootloader and that is all you need to flash your phone.
Click to expand...

yeah the file is good cause its the same one I use on the xp machine... its probably just windows being difficult lol. thanks for your help
 
Still can't get my machine to find my phone, even though its showing up as a flash device under my device manager. <<<frustrating>>>
 
ECFfighter7232 said:
yeah the file is good cause its the same one I use on the xp machine... its probably just windows being difficult lol. thanks for your help
Click to expand...

Make sure the security permissions are right on the file. Set at least your user (or temporarily set Everyone) to have full control.

Of course it is Windows being difficult... that is the purpose of the thread :)
 
flashing through rsd passes with 100% but when i try to boot into recovery it just runs the bootloader again. cant get anything but bootloader. please help!
 
You're probably flashing an incompatible SBF file. You need to use the SBF file that is either equivalent or greater than your current system version. So if you were on 2.2, you can't flash the 2.1 SBF - only the 2.2 or 2.2.1 SBF. If you are on 2.2.1, you can't flash the 2.2 or 2.1 SBF.

Does it say something like "Err ## ## ## ##" (where ## are numbers/letters)? That's the symptom of flashing an incompatible SBF file.
 
YES! i found that on another site but thank you very much!

to anyone else that's having problems, if you had the 2.2 and are trying to flash you cannot do it with the 2.1 SBF. moto changed the keys. but thank god people have posted the 2.2 sbf all over!

i was able to flash it. phone booted right up no problems! oh and i got the 2.2.1 update :D which is what initiated my phone bricking in the first place :mad:

all is well now! back to the unrooted 2.2.1 DX for now at least haha.

Huge thanks to everyone on this thread!!
 
So I have had consistent problems with win 7 64bit any time I've tried to flash my X. Always had the latest version of RSD lite, always had the latest motorola drivers, ran as administrator...all the right things.

My problem was running into an error when I was 99% done with the process but then:

Line: 589
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x150000 Command: ADDR (Error Code: e0030009),
Detailed Error Details: Direction of the Error=1000, Command Value=200000, Code Group Number=257
File: D:\GitProjects\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0

In the past I have had this error, and the phone has been able to reboot itself, but the sbf had not completed. I would then move to my 32bit windows laptop and perform the same procedure. It would be successful. With the most recent sbf released for the leak, I once again had to do this for my own experimental purposes, and was still having problems with the flash, except this time, the phone would not even reboot, it would freeze at the sw update in the bootloader and then fail to reboot and remain unsuccessful. I would then be semi bricked to the bootloader "code corrupt" screen. Pretty much a royal pain in my a$$. I went through this process at least 4 times to confirm I had been doing everything I was supposed to be doing.

SO, I eventually stumbled on this thread, but my errors had not been mentioned. I tinkered around with a few things, but eventually came to this conclusion. Setting compatibility mode to Windows XP SP3 and reflashing the sbf allowed my phone to successfully flash. So I think this may help as well as running as administrator. Just my thoughts
 
"Flash process fails immediately with error "Failed Flashing process. (0x7100)"

That last section saved my hind end and I am extremely thankful that you put all that together. Helped me un-brick the rooted phone I just got in the mail that immediately auto updated and bricked. Many thanks for taking the time to put this info up!
 
bcals0087 said:
Line: 589
ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x150000 Command: ADDR (Error Code: e0030009),
Detailed Error Details: Direction of the Error=1000, Command Value=200000, Code Group Number=257
Click to expand...

Exact same error I have been getting. Running as admin made no difference. Setting compatibility mode made no difference. After trying 4+ times (including once running a VMWare WinXP instance that bombed) I eventually threw caution to the wind and did the factory reset anyway. Just went through the reactivation so I'm hoping all went well and that last 1% was a fluke....
 
JoelR said:
Exact same error I have been getting. Running as admin made no difference. Setting compatibility mode made no difference. After trying 4+ times (including once running a VMWare WinXP instance that bombed) I eventually threw caution to the wind and did the factory reset anyway. Just went through the reactivation so I'm hoping all went well and that last 1% was a fluke....
Click to expand...

Yeah I also had the RAM issue. Factory reset doesnt do sht. In fact, after the first reboot after factory reset, it loaded up apps I had installed prior to factory reset. Have you tried SBF'ing on a true win xp machine?
 
I have tried all of these solutions and it still will not recognize my phone. I need help badly. thanks

Reinstalled all my drivers and switched to rsd 4.8 and it worked fine. Hope this helps someone in my situation
 
hunterwrot said:
I have tried all of these solutions and it still will not recognize my phone. I need help badly. thanks

Reinstalled all my drivers and switched to rsd 4.8 and it worked fine. Hope this helps someone in my situation
Click to expand...

Sorry, have not updated OP in a while with new information for RSDLite version and sbf versions. I will update it.
 
hello I'm stuck on my droid bionic it says 0a.78 low battery cannot program invalid so data cg 0x004e cg system is there a way to fix this
 
You must log in or register to reply here.
Back
Top Bottom