Database Users

Help! cant flash stock sbf!

i am tryint to flash the updated sbf for the atrix and the start button on RSD is greyed out. it does the same thing with the older retail version as well. is there something wrong with the drivers or something?

graemegb said:
i am tryint to flash the updated sbf for the atrix and the start button on RSD is greyed out. it does the same thing with the older retail version as well. is there something wrong with the drivers or something?
Click to expand...
Click to collapse
Make sure you put the. Sbf in the rsd lite folder, I had the same problem.
Sent from my MB860 using Tapatalk

like in the install folder?

ok, i got the start button to work, but now i get an error. "Failed flashing process. failed flashing process. (0x7100); phone connected"

You have the phone in rsd mode? I had a problem where my main laptop wouldn't flash it for some reason but when I used another I had it worked.
Sent from my MB860 using Tapatalk

Clienterror said:
You have the phone in rsd mode? I had a problem where my main laptop wouldn't flash it for some reason but when I used another I had it worked.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
yeah its in rsd mode. maybe if i bood in to windows with driver signing disabled?

i have the same error flashing the stock sbf and not the first leaked sbf

just found this guide. and it worked! http://groups.google.com/group/shadowmodbr/browse_thread/thread/e0a19659f5fb7683?pli=1

Cwm recovery issues

Hey guys, i have a few weeks experience flashing and all that leet stuff, but it seems i have a problem! I started to modify my ATRIX on 2.3.4, i unlocked sim, rooted, unlocked bootloader, and flashed custom recovery. I played around with a few roms, then i decided to update my fw to 2.3.6, well before i could do that i had to undo all mods so i ended up flashing a stock 2.3.4 fw and upgraded OTA. Im pretty sure that was my mistake... i may have needed an unlocked 2.3.6 sbf.. i re-rooted, and flashed cwm with rom manager, now when i go to boot in recovery mode i get failed to boot 2 starting rsd protocol. Everything is fine i just need to know where i messed up and how to get cwm running again. P.S. ive also been having an issue with my camera! I open the cam app and i get black screen, factory reset does NOT fix! Ive seen post's saying that the module is bad if that does not work BUT, when using flashlight app the flash lights up for a sec and then shuts off. When i switch to front camera it will stop responding, i'll click wait and after a min it will show image and i can take a pic(only with front cam). If i could get both issues solved i would be very grateful! If any other info is needed ill be sure to respond asap! Thank you in advanced for reading and assisting with my issues!
Sent from my MB860 using XDA

Get the cwm recovery img & flash with Fastboot and that should fix your recovery.
Sent from my MB860 using Tapatalk 2

Thanks for a reply but I did that as well and ended up getting an error. "Failed to process command flash:recovery error(0x180002)". I tried this method at first, received that error then tried to flash cwm through rom manager and recieved failed to boot2 starting rsd protocol.
Sent from my MB860 using XDA

Try unlocking bootloader again just to make sure ... Maybe that factory firmware closed hole on you when flashed.. Then flash cwm image ....

xRawwRRRRx said:
Thanks for a reply but I did that as well and ended up getting an error. "Failed to process command flash:recovery error(0x180002)". I tried this method at first, received that error then tried to flash cwm through rom manager and recieved failed to boot2 starting rsd protocol.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
XRange said:
Try unlocking bootloader again just to make sure ... Maybe that factory firmware closed hole on you when flashed.. Then flash cwm image ....
Click to expand...
Click to collapse
+1. You'll always need to re-flash pudding BL after using an .sbf.

ghost_og said:
+1. You'll always need to re-flash pudding BL after using an .sbf.
Click to expand...
Click to collapse
Would you happen to have the file? 2.3.6
Sent from my MB860 using XDA

xRawwRRRRx said:
Would you happen to have the file? 2.3.6
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Think what you seek lies here in Puddling thread..
http://forum.xda-developers.com/showthread.php?t=1136261

XRange said:
Think what you seek lies here in Puddling thread..
http://forum.xda-developers.com/showthread.php?t=1136261
Click to expand...
Click to collapse
adding to this: the automatic unlocker should work for you too. I had to re-unlock my phone after Motorola upgraded it when it was out for repairs. Worked like a charm.
(IF you're on AT&T)

ghost_og said:
adding to this: the automatic unlocker should work for you too. I had to re-unlock my phone after Motorola upgraded it when it was out for repairs. Worked like a charm.
(IF you're on AT&T)
Click to expand...
Click to collapse
Thank you soo much! I had to "re-unlock" bootloader! Now i have my custom recovery! One more thing have you or any other reader out there figured out a solution to my camera problem?
Sent from my MB860 using XDA

Try one custom roms see if that fixes camera, if not you might have carry phone for bad camera...

[Q] Motorola XPRT stuck at Motorola Logo

Motorola XPRT stuck at Motorola Logo.
I'm trying to flash it with this firmwares:
1FF-p3_kronos_cdma_kronos-user-2.2.2-KRNS-X4-1.1.10-110916-release-keys-Sprint-US.sbf
1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-KNS-29-BST-15-18-release-keys-signed-Boost-US.sbf
If I use RSDLite, I get error (with any firmware):
and Code Corrupt in bootloader.
When I use sbf_flash on linux,
1FF-p3_kronos_cdma_kronos-user-2.2.2-KRNS-X4-1.1.10-110916-release-keys-Sprint-US.sbf - bootloader error(Mem Map Blank)
1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-KNS-29-BST-15-18-release-keys-signed-Boost-US.sbf - stuck at Motorola Logo.
Any suggestions?

Simple but always good to check. Make sure the sbf checksums are correct to ensure they were downloaded correctly.
Sent from my MB612 using xda app-developers app

Checksums of my files:
CRC32
1FF-p3_kronos_cdma_kronos-user-2.2.2-KRNS-X4-1.1.10-110916-release-keys-Sprint-US.sbf 7A4A4AF2
1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-KNS-29-BST-15-18-release-keys-signed-Boost-US.sbf 74A272C6
MD5
517739312695ec87e0668c50987dccdd *1FF-p3_kronos_cdma_kronos-user-2.2.2-KRNS-X4-1.1.10-110916-release-keys-Sprint-US.sbf
315d553a44a058ef6b662fa59280020e *1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-KNS-29-BST-15-18-release-keys-signed-Boost-US.sbf
SHA1
34197f6aee01746a4993017f9763166fa2e68bf0 *1FF-p3_kronos_cdma_kronos-user-2.2.2-KRNS-X4-1.1.10-110916-release-keys-Sprint-US.sbf
6b7657609e29323c38ee68401977b1618c855582 *1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-KNS-29-BST-15-18-release-keys-signed-Boost-US.sbf
Where i can find correct checksums for comparison?

Hmm. I thought I saw them on the download pages. When I get home today I will check the checksum of my boost sbf. Just to compare. I don't have the sprint one though.
Sent from my MB612 using xda app-developers app

I have the same problem, please help me!

After falshing, Turn off your mobile. press R + M + Power key. you will get into motorola recovery. Do a data wipe/factory reset and reboot again... It always bootloop whenever i flash the sbf also. It should fix it.

just flash bootloader BL_0402_cdma_kronous_HS_generic_signed_Consumer_replacer.sbf
https://docs.google.com/file/d/0BwQkFb0zEZ3iRUMwLTFtdXJSX28/edit?usp=sharing
it always helps

rongsang said:
After falshing, Turn off your mobile. press R + M + Power key. you will get into motorola recovery. Do a data wipe/factory reset and reboot again... It always bootloop whenever i flash the sbf also. It should fix it.
Click to expand...
Click to collapse
nonono666 said:
just flash bootloader BL_0402_cdma_kronous_HS_generic_signed_Consumer_replacer.sbf
https://docs.google.com/file/d/0BwQkFb0zEZ3iRUMwLTFtdXJSX28/edit?usp=sharing
it always helps
Click to expand...
Click to collapse
I've been doing it all, but in result i get after few minutes logo M error in bootloader
Bootloader
04.02
Err:1B,00,02,00,00
Battery OK
OK to Programm
Connect USB
Data Cable
Click to expand...
Click to collapse

Janushkevich said:
I've been doing it all, but in result i get after few minutes logo M error in bootloader
Click to expand...
Click to collapse
You cannot flash 2.2.2 after you have flashed 2.3.5.
After flashing 2.3.5 get into recovery and do a data/factory reset.
Sent from my MB612 using xda app-developers app

http://www.mediafire.com/?077aa2bbe3kxg63
1FF-p3_kronos_cdma_kronos-user-2.3.5-4.5.1-110-KNS-46-49-test-keys-signed-Sprint-US.sbf
yes, always do full wipe from recovery
then get root and flash rongsangs cm7

Janushkevich said:
I have the same problem, please help me!
Click to expand...
Click to collapse
today i had a bootloop
but when i insert microsd back, it worked

I had the same boot load error. You have to use 2.3.5 since you have already flashed to it once, you cannot back up to froyo.
Is your phone a boost or sprint?
Sprint can be flashed with either the sprint sbf or the boost sbf, But Boost can only be used with the boost mobile.
Reflash 2.3.5 and do a full wipe on the phone and it should fix the problem.

[q] help!!! Seriously bricked razr m!!!

Let's start from the top. I have a razr m running the leaked 4.1.1 jb rom with the modified root that uses SuperSu instead of superuser. I went into the filesystem and swapped out my build.prop with the one from a Google galaxy nexus thinking it would allow me to download more apps from the play store. (Google wallet, etc) the phone wouldnt boot, it just locked on the motorola logo, so i went into recovery and wiped data as well as cache and tried to reinstall the jb leak, it failed because the build.prop didnt match. I fired up RSD lite and tried to fastboot back to ICS but it keeps failing on step 17/22 where its flashing the system.image.ext4. Because of the partial fastboot now the phone wont even boot to recovery, it just goes straight to the fastboot menu. If anyone could help all posts would be greatly appreciated! Thank you!

Your phone is repeatedly booting into fast boot because of the failed flash. This is normal and will continue until you have a successful flash. What version of RSD are you using? What does it say when it fails?
Sent from my XT907 using xda app-developers app

I am running RSD lite V5.7 on a windows XP SP3 machine. it says FAIL in the result box and ity fails system.image.ext4 because "phone returned FAIL"

Try RSD 6.1.4 and/or I seem to remember some people having to run as admin on XP if I'm not mistaken.
Sent from my XT907 using xda app-developers app

Incydeu said:
Try RSD 6.1.4 and/or I seem to remember some people having to run as admin on XP if I'm not mistaken.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
That did it perfectly, so glad i came to XDA before going to the verizon store and begging them not to rape my wallet! you saved my life man, youll be getting a thanks from me!

[Q] usb came unplugged durring sbf flash

My friends purchased a Droid Pro with CM9 already loaded onto it. He asked for my help because he was experiencing bugs and wanted to go back to a stock ROM.
I installed the Motorola drivers.
I put the phone into clockwordmod recovery and cleared all the caches and battery stats.
I then restarted into the Bootloader and started up a current version of RSD lite on my Win7x64 installation.
Next I got the SBF file loaded up in RSD lite and started flashing.
As it was nearing completion I picked up the phone to "catch the boot" and in the process bumped the USB cable just enough to terminate the connection and the process failed.
Now I can't get passed the Bootloader which says Code Corrupt.
I have spent hours upon hours scouring the internet trying different fixes to fix this problem.
Now when I try to flash it again with RSD lite it gets stuck when switching the phone to PB pass through and FAILS with the error 0x70be because it can't find the driver for MDM6600 and my system labels it as an unknown device.
I have since installed WinXPx84 on my system and tried the SBF process over and over in different ways hoping that it will take.
Any insight is greatly appreciated.
Thank you,
PEZ

PEZ Dispenser said:
My friends purchased a Droid Pro with CM9 already loaded onto it. He asked for my help because he was experiencing bugs and wanted to go back to a stock ROM.
I installed the Motorola drivers.
I put the phone into clockwordmod recovery and cleared all the caches and battery stats.
I then restarted into the Bootloader and started up a current version of RSD lite on my Win7x64 installation.
Next I got the SBF file loaded up in RSD lite and started flashing.
As it was nearing completion I picked up the phone to "catch the boot" and in the process bumped the USB cable just enough to terminate the connection and the process failed.
Now I can't get passed the Bootloader which says Code Corrupt.
I have spent hours upon hours scouring the internet trying different fixes to fix this problem.
Now when I try to flash it again with RSD lite it gets stuck when switching the phone to PB pass through and FAILS with the error 0x70be because it can't find the driver for MDM6600 and my system labels it as an unknown device.
I have since installed WinXPx84 on my system and tried the SBF process over and over in different ways hoping that it will take.
Any insight is greatly appreciated.
Thank you,
PEZ
Click to expand...
Click to collapse
Woah woah woah. Windows x84?
Sent from my Nexus 7 using xda app-developers app

BlackFire27 said:
Woah woah woah. Windows x84?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
x84 is just another way of saying 32 bit

I think it is x86. Back on topic. So, try downloading another sbf that is from before 4.7.8 Try sbfing that
Sent from my Amazon Kindle Fire using Tapatalk HD

Vlasp said:
I think it is x86. Back on topic. So, try downloading another sbf that is from before 4.7.8 Try sbfing that
Sent from my Amazon Kindle Fire using Tapatalk HD
Click to expand...
Click to collapse
Ah, my bad, yes x86. Like I said I've spent hours and hours on this and missed some sleep.
I will look into and try other SBFs however I have been having trouble locating good links considering the age of the device. Know of any resources?
What do you mean by 4.7.8? I can't find any information on that. The SBF files that I have tried flashing are 2.26.20 and another one I found for the Droid Pro that is just labeled 3087.sbf

PEZ Dispenser said:
Ah, my bad, yes x86. Like I said I've spent hours and hours on this and missed some sleep.
I will look into and try other SBFs however I have been having trouble locating good links considering the age of the device. Know of any resources?
What do you mean by 4.7.8? I can't find any information on that. The SBF files that I have tried flashing are 2.26.20 and another one I found for the Droid Pro that is just labeled 3087.sbf
Click to expand...
Click to collapse
my bad 4.7.3. Try that one by searching on google.
Sent from my Amazon Kindle Fire using Tapatalk HD

Vlasp said:
I think it is x86. Back on topic. So, try downloading another sbf that is from before 4.7.8 Try sbfing that
Sent from my Amazon Kindle Fire using Tapatalk HD
Click to expand...
Click to collapse
ah, I see, 4.7.8 is the blur version. Downloading 4.6.8 now. Hopefully that works.

Have I permanently bricked a phone for the first time?
Ok, so now I have tried 4.6.8, 4.7.3, 4.7.8 and probably also a couple others by now with no luck.
All of them get error switching phone to PB pass through mode (0x07BE). My system cannot find the driver for MDM 6600 and my systems will only see it as an unknown device after RSD light trys to do the PB mode switch. I have tried installing the driver pack after the PB switch, which doesn't work. Extracting the drivers to a location that I then direct device manager to and that doesn't work.
Any other ideas on how to get this good hardware back and going again?
I will try the process on a completely different computer tomorrow, maybe the OS switch wasn't enough and there is a conflict with my machine. I doubt it though because I have used this machine to work on my D3.

PEZ Dispenser said:
Ok, so now I have tried 4.6.8, 4.7.3, 4.7.8 and probably also a couple others by now with no luck.
All of them get error switching phone to PB pass through mode (0x07BE). My system cannot find the driver for MDM 6600 and my systems will only see it as an unknown device after RSD light trys to do the PB mode switch. I have tried installing the driver pack after the PB switch, which doesn't work. Extracting the drivers to a location that I then direct device manager to and that doesn't work.
Any other ideas on how to get this good hardware back and going again?
I will try the process on a completely different computer tomorrow, maybe the OS switch wasn't enough and there is a conflict with my machine. I doubt it though because I have used this machine to work on my D3.
Click to expand...
Click to collapse
now lets go 1 step back on rsd lite and downgrade to the second latest version. and install the Motorola bootloader drivers or normal drivers with that. quick question. can you boot past the error screen into the recovery? It is R and Q and Power button. when the M screen is present.
Sent from my Amazon Kindle Fire using Tapatalk HD

Vlasp said:
now lets go 1 step back on rsd lite and downgrade to the second latest version. and install the Motorola bootloader drivers or normal drivers with that. quick question. can you boot past the error screen into the recovery? It is R and Q and Power button. when the M screen is present.
Sent from my Amazon Kindle Fire using Tapatalk HD
Click to expand...
Click to collapse
I'm using RSD lite 6.1.5, so you say I should try 6.1.4 or another older version?
What is the difference between Motorola bootloader drivers and normal drivers?
I thought it was R and M and the Power button to get into recovery. Anyway, I tried R and Q which does not work either. Doesn't look like I can get into recovery. Can I flash a recovery system onto it with RSD lite and then fix it from there?
Thank you Vlasp for taking the time to help me out with this.

PEZ Dispenser said:
I'm using RSD lite 6.1.5, so you say I should try 6.1.4 or another older version?
What is the difference between Motorola bootloader drivers and normal drivers?
I thought it was R and M and the Power button to get into recovery. Anyway, I tried R and Q which does not work either. Doesn't look like I can get into recovery. Can I flash a recovery system onto it with RSD lite and then fix it from there?
Thank you Vlasp for taking the time to help me out with this.
Click to expand...
Click to collapse
I am getting all of my facts mixed up. It is R and M, and there are no bootloader drivers. and regarding the rsdlite, try the 6.1.4 or something.
Sent from my Amazon Kindle Fire using Tapatalk HD

You can flash the bootloader update, and then try flashing again... 4.04 or something like that... I cant check as my phone got stolen last week, but I think it may solve your problem

donlloreda said:
You can flash the bootloader update, and then try flashing again... 4.04 or something like that... I cant check as my phone got stolen last week, but I think it may solve your problem
Click to expand...
Click to collapse
I haven't been able to find any information on this or any other bootloader update. Can you maybe point me in the right direction?

try turning off firewall and flash it again
Sent from my Motorola MB612 using xda app-developers app

Hot-dog007 said:
try turning off firewall and flash it again
Sent from my Motorola MB612 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure how that is supposed to help and the firewall was already disabled anyway.
When RSD lite finishes flashing and wants to switch the phone to PB pass through mode the system sees my phone as an unknown device and won't install the correct driver correctly. I do have the option to select which driver to install and can find Motorola from the menu but then I am faced with about 10 different options on what specific device driver to install. One of them is Motorola PB interface, one of them is Motorola Flash interface, etc etc. I've tried the PB interface driver and it seems like it installs but it still shows up as an unknown device on my system and the flashing fails.

try sbf_flash using linux