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!
Related
I was trying to flash a custom rom onto my sisters droid x. I'm not new to androids and have pretty good knowledge but coming from a atrix it was a bit different. Anyway I flashed the rom and the phone got stuck on the moto sign. So I tried loading back to stock via rsdlite. It finished and phone rebooted. Then got stuck again on the moto sign. Don't know where to go from here. Any help would be greatly appreciated. She needs her phone asap for work soon. Thanks.
Try SBFing again using RSD Lite, or use the Linux live cd--which is much easier.
Be sure you are using the correct SBF, also. Should say version .602.
Sent from my DROIDX using XDA App
thx got it to work via rsdlite. now running newest cm7. had a panic attack.
stevehkim said:
thx got it to work via rsdlite. now running newest cm7. had a panic attack.
Click to expand...
Click to collapse
Hey man - been there done that The SBF_FLASH utility you can download and use in LINUX (you can boot with the Ubuntu Live CD like the guy above suggested) is MUCH better. It "just works". Never had it error and RSDLITE failed so many times my battery went dead (before). I don't even bother with it now I just go straight to sbf_flash.
always remember to wipe wipe wipe... thats y u got stuck at the moto after rsd...
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
So i bricked my friends droid x and its currently stuck in bootloader.
Bootloader
30.04
Err: A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
ok to Program
Transfer mode: USB
Ive been googling around and i havent seen anything. I wanted to know if there is anything.
There is a very easy way to fix it, but before I tell you, I need to know how this happened?
(Eg. installing an OTA update)
Sent from my DROIDX using Tapatalk 2
Have u tried to sbf?
This is were I would get my proper sbf and use Linux to reflash the phone as stock. Then data reset it. Reboot and start over. You'll get it. If IT's boot up problem occurs after reboot from flash then try different from that one is not working for you or directions not proper
Sent from my DROIDX using xda premium
Like mike said, sbf time. Its pretty easy, just download the Motorola drivers, SBF file, and RSD Lite. Can be done on windows or linux.
I would recommend using the .605 sbf file rather then .621, as .621 can't be easily rooted or sfb'd.
Link with step-by-step: ugh, im a new user so it wont let me post outside links. Its stickied on Droid X forums>Rescue Squad>Droid X SBF
Sent from my DROIDX using XDA
Just realized its stickied on this forum as well
Sent from my DROIDX using XDA
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
So I tried to use the revised root option for the ota. It hit a snag since I was using a virtual machine, and didn't complete. Now when I shut down the phone it stops in Fastboot and I choose an option like recovery and it finishes the boot. Do Mt question is, should I retry the rooting using a fully installed PC, or would this just become worse.
*edit* what about using rsd to flash boot.img?
Sent from my XT907 using XDA Premium 4 mobile app
I came across this same issue a few days ago. Going back into fastboot and restoring with Matt's Utility 1.20 fixed it for me.
Edit: I should mention that mine was caused by trying to do "fastboot flash system system.img", which failed for some reason, even though I was running the command natively under Linux Mint. I had the same problem afterwards where it always booted into fastboot first though.
Gotcha, yeah my mint install did not want to work with the program, so are you saying the older version, not the slightly updated for the ota?
Sent from my XT907 using XDA Premium 4 mobile app
So i wanted to go back to 4.1.2 on my droid razr m that was currently on 4.4.2, Personal Issues and lags were the problem.
I followed instructions on this site and now my phone turns on and everything now the touch is unresponsive it used to work before this stupid procedure. The link to the forum is http://forum.xda-developers.com/showthread.php?t=2786016. Please help me when i did the steps it said flash failed on Ap Fastboot Mode. I would say that the Software got corrupted so Please reply back asap. With help.
:crying::crying::crying::crying:
Your boot loader is unlocked correct?... I would say rsd back to official 4.4.2... Then try the downgrade again if touch returns...
Sent from my XT907 using XDA Premium 4 mobile app
No i didnt unlock the phone and my touch hasent work since i tried to downgrade i know the digitizer isnt loose. any solutions. Please help me and how do i use RSD
Download 4.4.2 and rsd 6.1.6 just boot your phone to fastboot menu then on your PC open rsd plug your phone into the PC with in rsd select the 4.4.2 zip and flash it... Then root using towelroot and unlock your boot loader... Then downgrade if you want..... Hopefully the fresh install of 4.4.2 will return touch if not then you may have a hardware issue... But idk this guy (I believe) tried a root method that if i remember correctly pretty much downgrades you(which you can't do on a locked boot loader) so you can root an older root method and is in the same boat
Sent from my XT907 using XDA Premium 4 mobile app
Droidddd
ok i will try that soon.
ezknives said:
Download 4.4.2 and rsd 6.1.6 just boot your phone to fastboot menu then on your PC open rsd plug your phone into the PC with in rsd select the 4.4.2 zip and flash it... Then root using towelroot and unlock your boot loader... Then downgrade if you want..... Hopefully the fresh install of 4.4.2 will return touch if not then you may have a hardware issue... But idk this guy (I believe) tried a root method that if i remember correctly pretty much downgrades you(which you can't do on a locked boot loader) so you can root an older root method and is in the same boat
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
am i supposed to be extracting the software files because i think that is what i did wrong.
ezknives said:
Download 4.4.2 and rsd 6.1.6 just boot your phone to fastboot menu then on your PC open rsd plug your phone into the PC with in rsd select the 4.4.2 zip and flash it... Then root using towelroot and unlock your boot loader... Then downgrade if you want..... Hopefully the fresh install of 4.4.2 will return touch if not then you may have a hardware issue... But idk this guy (I believe) tried a root method that if i remember correctly pretty much downgrades you(which you can't do on a locked boot loader) so you can root an older root method and is in the same boat
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Open rsd and choose the extract and install or which ever option is very similar to that I don't remember what the option is... What you did wrong was try to downgrade with a locked boot loader
Sent from my XT907 using XDA Premium 4 mobile app
It worked thank you
Sent from my XT907 using XDA Free mobile app
No problem happy you got it working... Now go ahead make sure you unlock the boot loader...
Sent from my XT907 using XDA Premium 4 mobile app
ezknives said:
No problem happy you got it working... Now go ahead make sure you unlock the boot loader...
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lmao no it is hardbricked follow the new methods that are getting released soon.
Sent from my SM-T320 using XDA Free mobile app