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
Related
hi The Atrix has been my first official Android phone, i had a HTC TILT 2, which i flashed to 2.3. But this Atrix is very confusing. The first thing i haven't been able to flash any sbf file since i have gotten the phone. I wanted to go back to stock because my webtop hack wasn't working through adb or gingerblur bloatware.zip in cwm. So extracted the SBF to the root of my c: drive,unzipped, renamed SBF, waited for connection, then it extracts 100%then fails and gives and error but it never restarted. But last night i ran rsd with the sbf from this link http://bandbinnovations.com/xda/OLYF..._1g_1FF.sbf.g[/url], and ran the sbf properly, but after it executed 100%, then started running the phone commands, but while running commands it stopped @86% and gave a error "switching device to bp pass error", i tried to flash this same file a second time but each time it stopped and gave the same error at 86%, and RDS completely stopped. so i unplugged the usb from my computer, and it was stuck at the M logo screen(all night). So i freaked out and thought it was bricked, because no sbf i have tried has worked for me, and my battery was getting low flashing SBF so many times. and almost called att warranty this morning. But this morning i turned my Atrix on and boom it was back to stock 1.2.6?Dont know how i did it,or how do it again properly, but glad im back to stock. But that was extremly confusing and frustrating!
Nice! What are the odds you and someone else have the same story and posted at the same time with the same login name? Musta been excited to post this story.
Clienterror said:
Nice! What are the odds you and someone else have the same story and posted at the same time with the same login name? Musta been excited to post this story.
Click to expand...
Click to collapse
Gotta raise post count somehow! Lol
Sent from WinBorg 4G using XDA Premium App
CaelanT said:
Gotta raise post count somehow! Lol
Ya that's it man. Sorry if I kinda in a hurry to get my phone working again. And I don't know how delete the other post or how I did it 2 times.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
which VERSION of RSD were you used?
RSD 5.0 or RSD 5.3.1 is OK for flash AT&T 1.26 or 1.5.7 or 1.8.3 SBF.
I flashed my ATT Atrix with RSD 5.0 many times, there's no issue every time.
jenhore said:
which VERSION of RSD were you used?u
RSD 5.0 or RSD 5.3.1 is OK for flash AT&T 1.26 or 1.5.7 or 1.8.3 SBF.
I flashed my ATT Atrix with RSD 5.0 many times, there's no issue every time.
Click to expand...
Click to collapse
I was using RSD 5.0 and trying to flash 1.2.6. On att. I don't know if its my computer or what, but I have tries it on 4 different sbf files on 3 computers. It finally went back to stock but I don't know how because it was bricked the night before.
Sent from my MB860 using XDA Premium App
Need help, I bricked my Defy Green lense.
Some how after trying to flash a miui rom, it went to bootloader after I pressed the "reboot device now" in the clockworkmod recovery. So I tried to flash my sbf, but in the reboot, the phone just turned off, an haven't been able to turn it on, I already tried the Mc Giver method to charge the phone, (as it worked before) but the phone does nothing,
Any help would be thanked...
Sent from my PC36100 using Tapatalk 2
Use RSDLite and an original SBF to flash it back to normal operation.
Questions go in the Q&A section
That Android you put on it?
You must try to put exactly the last ROM haved one Defy ...
ScYcS said:
Use RSDLite and an original SBF to flash it back to normal operation.
Click to expand...
Click to collapse
I was flashing the original SBF with RSD Lite, right after, during the reboot, it turned it self off, an from then on, I haven't been able to Even Turn It On, it shows no activity what so ever...
Sent from my PC36100 using Tapatalk 2
Try it again maybe with a different SBF and flash it again with RSDLite?
ScYcS said:
Try it again maybe with a different SBF and flash it again with RSDLite?
Click to expand...
Click to collapse
Thanks but I can't even get it to the bootloader screen, that's why I thought it didn't have battery and tried to charge it the normal way, an since nothing happened, I tried the McGiver way an it didn't work either...
Sent from my PC36100 using Tapatalk 2
USE This and careful defy SBF Or Defy+ SBF
http://forum.xda-developers.com/showthread.php?t=966537
OR this For Downgrade to eclair If Flashed 2.3.x
http://www.4shared.com/rar/xzT3dMXv/JORDN_U3_972151.html
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
i'm trying to sbf flash a phone, but i keep getting a checksum error at code group 33. File: 0x1abc Phone: 0x4805 is the error. Also the code is corrupt so i cant get passed the bootloader screen. Is there any way to adb into my phone while it's in the bootloader screen? How does RSD connect to our phone?
Codeseven said:
i'm trying to sbf flash a phone, but i keep getting a checksum error at code group 33. File: 0x1abc Phone: 0x4805 is the error. Also the code is corrupt so i cant get passed the bootloader screen. Is there any way to adb into my phone while it's in the bootloader screen? How does RSD connect to our phone?
Click to expand...
Click to collapse
How are you able to flash using RSD without being in bootloader mode? You should be able to get into bootloader with a message code corrupt by pressing power+volume up. Try DFP-231, it may work.
hotdog125 said:
How are you able to flash using RSD without being in bootloader mode? You should be able to get into bootloader with a message code corrupt by pressing power+volume up. Try DFP-231, it may work.
Click to expand...
Click to collapse
I never said I wasn't in bootloader mode. I'm stuck in bootloader mode. I can't get passed it.
Codeseven said:
I never said I wasn't in bootloader mode. I'm stuck in bootloader mode. I can't get passed it.
Click to expand...
Click to collapse
Try DFP-231.
Sent from my Nexus 7 using Tapatalk
hotdog125 said:
Try DFP-231.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
My phone is originally a 525, will this work since it's for a 526?
Codeseven said:
My phone is originally a 525, will this work since it's for a 526?
Click to expand...
Click to collapse
It worked for thekguy, try it, it may fix the code corrupt problem.
Sent from my Nexus 7 using Tapatalk
try with a wipe in stock recovery before flashing .sbf
dfp-231 didn't work. i think my phone has hardware issues. is there anyway to interface with my phone the same way sbf_flash and rsd lite do?
If dfp 231 failed at code corrupt, its definitely a hardware problem
Sent from my MB526 using Tapatalk 4
thekguy said:
If dfp 231 failed at code corrupt, its definitely a hardware problem
Sent from my MB526 using Tapatalk 4
Click to expand...
Click to collapse
Yes, I've been well aware of this. Which is why i'm asking "is there any way to access my defy at the bootloader screen?" We know RSD lite and sbf_flash can interface with our phones, but how does it connect? What commands does it use? etc etc.
No, that interface is not accesible by us till now. I think it is some kind of signed fastboot interface, except that its not fastboot
Sent from my MB526 using Tapatalk 4
So basically I'm trying to get my phone to work. I tried flashing and I wiped my data/factory reset my phone. And I attempted to flash a custom rom. However my signature failed. I realized that I needed CWM but I cannot install anyway because my recovery is e3 and the signature fails. I tried resetting back to stock by using RSDLite/SBF to get back to normal. However my device will not read on my computer. I've attempted to make sure my drivers are correct, and that my cables/usb ports are working fine. I'm basically in a dilemma and I'm not sure what else I can really do. Is there another workaround? I'd love it if someone can help a brother out!
I think the reason it isn't reading in my computer is because it is Windows 8 if that helps.
Eatthisnx4 said:
So basically I'm trying to get my phone to work. I tried flashing and I wiped my data/factory reset my phone. And I attempted to flash a custom rom. However my signature failed. I realized that I needed CWM but I cannot install anyway because my recovery is e3 and the signature fails. I tried resetting back to stock by using RSDLite/SBF to get back to normal. However my device will not read on my computer. I've attempted to make sure my drivers are correct, and that my cables/usb ports are working fine. I'm basically in a dilemma and I'm not sure what else I can really do. Is there another workaround? I'd love it if someone can help a brother out!
I think the reason it isn't reading in my computer is because it is Windows 8 if that helps.
Click to expand...
Click to collapse
You need to download and install the Motorola drivers to connect the phone to RSD to SBF it. Just search for Motorola drivers on Google.
Then you can install the D2 Bootstrap, boot into recovery, and install your ROM.
Forgot to add: Root using Framaroot before installing Bootstrap.
VitaTaf said:
You need to download and install the Motorola drivers to connect the phone to RSD to SBF it. Just search for Motorola drivers on Google.
Then you can install the D2 Bootstrap, boot into recovery, and install your ROM.
Forgot to add: Root using Framaroot before installing Bootstrap.
Click to expand...
Click to collapse
I've done that already. And they are "installed" but it doesn't seem to appear as anything other than unspecified :/
Eatthisnx4 said:
I've done that already. And they are "installed" but it doesn't seem to appear as anything other than unspecified :/
Click to expand...
Click to collapse
Can you verify root using Root Checker? If you are on the stock Gingerbread ROM, z4root will not root your device.
VitaTaf said:
Can you verify root using Root Checker? If you are on the stock Gingerbread ROM, z4root will not root your device.
Click to expand...
Click to collapse
The problem with that is I wiped/deleted everything off my phone, as I cannot even access anything besides recovery/bootloader.
Eatthisnx4 said:
The problem with that is I wiped/deleted everything off my phone, as I cannot even access anything besides recovery/bootloader.
Click to expand...
Click to collapse
Can you try flashing this: http://goo.im/devs/wizard0f0s/Hijacked_Bootmenu/CM7
After that, press the volume down key when/if the blue LED lights up (after reboot on the red M logo). You should be able to access an updated recovery from there.
That would be a good idea. however I get the signature verification failure thing. :/
Eatthisnx4 said:
That would be a good idea. however I get the signature verification failure thing. :/
Click to expand...
Click to collapse
Unfortunately, the only option is to do an SBF. If using Windows doesn't work, you might want to try using Ubuntu.
By the way, I am using Windows 8 too and I do not have any problems with RSD Lite.
VitaTaf said:
Unfortunately, the only option is to do an SBF. If using Windows doesn't work, you might want to try using Ubuntu.
By the way, I am using Windows 8 too and I do not have any problems with RSD Lite.
Click to expand...
Click to collapse
I'm gonna attempt to use a different computer to fix my problem. Wish me luck man.
Thanks for your input.
Eatthisnx4 said:
I'm gonna attempt to use a different computer to fix my problem. Wish me luck man.
Thanks for your input.
Click to expand...
Click to collapse
No problem, good luck on fixing your problem.
Troubles with RSD lite try
DX (MB810) ezSBF & Root 2.3.4/4.5.621
Sent from my XT862 using Tapatalk
sd_shadow said:
Troubles with RSD lite try
DX (MB810) ezSBF & Root 2.3.4/4.5.621
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
Good idea. The problem is I cannot get my computer to recognize my device properly. :/ But Once I find a way to do it I will use that way!
Eatthisnx4 said:
Good idea. The problem is I cannot get my computer to recognize my device properly. :/ But Once I find a way to do it I will use that way!
Click to expand...
Click to collapse
ezSBF doesn't need drivers installed, so if it's a drivers issue try ezSBF
---------- Post added at 12:02 PM ---------- Previous post was at 11:41 AM ----------
just need
1. windows, linux, or mac computer
2. blank cd-r, dvd-r, or flash drive (thumb, stick, sd card...)