I have two droid 3's and I rooted them both and went to install a blue theme on one of them from the rom manager app and it worked great, so I did it on my second one, too. When it was in the reboot process it never finished bootoing and it stopped at the red M. All it shows is the boot logo, not the boot animation. I have tried flashing it with rsd lite, but it always fails. Is there any other ideas as to what I should do?
You need to get rsdlite working(does it work on the other phone?). Get the drivers installed from motohelper (or reinstall) if needed, get the phone into ap fastboot and sbf to stock and go from there. Check this thread on users with the same issue.
Willis111 said:
You need to get rsdlite working(does it work on the other phone?). Get the drivers installed from motohelper (or reinstall) if needed, get the phone into ap fastboot and sbf to stock and go from there.
Click to expand...
Click to collapse
Yes, the theme works on the other phone. I will get the drivers and try again and will get back to you. Thanks for the help so far.
RaTTeDH said:
Yes, the theme works on the other phone. I will get the drivers and try again and will get back to you. Thanks for the help so far.
Click to expand...
Click to collapse
I meant rsdlite, have you ever used it with either phone without having an issue? I edited my previous post, added a link you might want to check out.
Instead of RSD Lite, I'd suggest using the quick unbricking script. It works for XT862 (maybe why Willis didn't recommend it). I have a mirror of it below. It's a ~450MB .zip file that is NOT flashable from the phone, but must be unzipped onto your desktop where you then boot into AP Fastboot, connect with the stock cable, and run a batch file from the download and it'll restore the phone's software to box stock in about 5 minutes.
http://minus.com/mB0zknQrL/
I have never used RSDLite before. So I do not know if it works. But when I am flashing it with the stock 5.6.890 it fails at step 5. It reboots the bootloader. But it fails always at step 5. Let me try the other replys...
redsox985 said:
Instead of RSD Lite, I'd suggest using the quick unbricking script. It works for XT862 (maybe why Willis didn't recommend it). I have a mirror of it below. It's a ~450MB .zip file that is NOT flashable from the phone, but must be unzipped onto your desktop where you then boot into AP Fastboot, connect with the stock cable, and run a batch file from the download and it'll restore the phone's software to box stock in about 5 minutes.
Click to expand...
Click to collapse
I have downloaded this and tried this. When I run the application moto.fastboot.exe it takes like 30 seconds and when I run the batcch file it immediately finishes and says moto fastboot is not recognized as an internal or external command, operable file or command. And finishes immediately. Sigh.
redsox985 said:
Instead of RSD Lite, I'd suggest using the quick unbricking script. It works for XT862 (maybe why Willis didn't recommend it). I have a mirror of it below. It's a ~450MB .zip file that is NOT flashable from the phone, but must be unzipped onto your desktop where you then boot into AP Fastboot, connect with the stock cable, and run a batch file from the download and it'll restore the phone's software to box stock in about 5 minutes.
http://minus.com/mB0zknQrL/
Click to expand...
Click to collapse
The unbrick script will flash a vzw rom to your xt860 and have you stuck at the M logo anyways so I wouldn't suggest trying that. If you haven't used rsdlite before and are having trouble with it now you probably need to install the drivers from the motohelper software.
1./ download the drivers (from motorola)
2./ shutdown phone and turn it on by hold m + power
3./ select ap fastboot mode, enter and plug your phone into the computer ignoring any add new hardware
4./ start the driver install and follow it through
5./ unplug and replug your phone with computer leaving it fastboot mode.
Rsdlite should show your device under listed devices when you start it up at this point and allow you to flash w/e rom. I would suggest using the iucell or brazil retail fastboot files from the xt860 fastboot thread to get your phone up.
I fixed it using CMD in Windows flashing some stuff. Thanks guys!
Related
Hey.
Ive just tried to upgrade my milestone to G.O.T's Froyo rom.
When i tried to flash the sbf with the rsd lite i just couldnt hit start.
I had the same problem with the vulnerable rom but when i renamed it to something shorterd it worked.
I tried to do the same again but it didnt worked , i tried another sbf but it didnt worked either.
I already have the drivers.
Any one knows whats the problem is?
rename the sbf file into a short name and put it into a short path.
eg:
Code:
C:\haha.sbf
it will help you
EDIT: Wrong thread sorry.
sir_shady said:
rename the sbf file into a short name and put it into a short path.
eg:
Code:
C:\haha.sbf
it will help you
Click to expand...
Click to collapse
i still cant click the start button :\
this happened to me before. not sure what caused it but if you are in bootloader, reboot and let the phone boot normally then plug it into rsd and it should work.
now it say's FAIL and on the botton there is:
"fail flashing process. (0x7100); phone connected"
I had an issue with my RSD Lite, here is what i did to solve it.
1) took the sbf out of any directory and put it straight onto the c drive
2) upgraded rsdLite to 4.6
3) opened RSD Lite and loaded the SBF -> previously i was connecting the phone first and then trying to load the SBF, apparently the order here matters.
4) connected my phone
5) hit start when I saw my phone appear in RSD Lite.
Hope this helps,
Jonathan
it works for me,thanks.
I will donate to the individual that unbricks my bionic...Plz a lil desperate!!
Hmm.. Maybe some more info. What were you doing when you bricked it? Any of the leaked updates installed?
djr4x4 said:
Hmm.. Maybe some more info. What were you doing when you bricked it? Any of the leaked updates installed?
Click to expand...
Click to collapse
i was back on 886 with updated kernel and radio. wanted to flash the ota but kept failing due to kernel. tried flashing the ota in stock recovery then in cwm to no avail. decided to format somethings in advanced just to see if it would help flash ota but no. after that i rebooted and bam! bricked. thing is i have been in this situatuation before and nothing would restore me except released and 4ever root but now nothing works. no phone going on 24 hours now...
Did the same thing. Used this method. if you can get to the fast boot by holding power and vol down (or power and volume up and down, then selecting fast boot) it will work
http://www.addictivetips.com/mobile/unbrick-motorola-droid-bionic-with-rsd-lite-5-5-guide/
netslum said:
Did the same thing. Used this method. if you can get to the fast boot by holding power and vol down (or power and volume up and down, then selecting fast boot) it will work
http://www.addictivetips.com/mobile/unbrick-motorola-droid-bionic-with-rsd-lite-5-5-guide/
Click to expand...
Click to collapse
rsd didnt work for me ever...i want to try it again but it says that the file is not supported...
got it but still a no go. it fails everytime right away
Is there anyway to flash the fxz file without rsd??maybe fastboot??but it needs to be in IMG format right? anybody?
You can flash individual files from that pacjage in fastboot. Try this.
Fastboot flash /system system.img
Make sure those files are in same folder as fastboot, you have the right drivers and ur in fastboot mode on phone. Do this for every file it will let u. keep ur money tho if this works im not on this forim to get paid. Worse comes to worse pm me a phone number and ill step u thru it over phone.
Sent from my DROID BIONIC using XDA App
Here's some general tips for making RSD Lite work for you. RSD Lite is the only tool that knows how to manipulate FXZ files, as it's Motorola's proprietary file format.
(1) All the files you should need (Either RSD Lite or Fastboot) will come from here: http://briefmobile.com/droid-bionic-receives-fastboot-recovery-files
(2) Running the 32-bit version of the Motorola drivers is recommended. RSD Lite is a native 32-bit app and has a better chance of playing nice if 32-bit Motorola drivers are installed.
(3) When running RSD Lite on Windows Vista or Windows 7, it is also recommended that when you open it that you right-click and choose "Run As Administrator".
(4) After installing the drivers and RSD Lite, reboot and then plug in your Bionic AFTER opening RSD Lite.
From there, you make sure that you start your Bionic in bootloader (aka fastboot) mode and then RSD Lite shouldn't have a problem detecting the device so you can flash in the FXZ file. The best version to use in your situation is the full one that's 685MB.
This is what you need. I personally don't use rsdlite.
http://forum.xda-developers.com/showthread.php?t=1279825
You will boot your phone into fastboot mode then flash it using this utility. Option 1 is what you need to use.
You can also try this: http://droidmodderx.com/bionic/too-easy-unbrick-bionic-with-oneclick-fastboot-restore/
Sent from my DROID BIONIC using Tapatalk
Remember to hit the "Thanks" button when someone helps you!
Terri M said:
You can also try this: http://droidmodderx.com/bionic/too-easy-unbrick-bionic-with-oneclick-fastboot-restore/
Sent from my DROID BIONIC using Tapatalk
Remember to hit the "Thanks" button when someone helps you!
Click to expand...
Click to collapse
i have tried all of those and still no luck. all i can think of is to flash the whole fxz file in fastboot. but it needs to be in .IMG format.
follow the steps in the first post of this thread. should get you back going.
http://www.mydroidworld.com/forums/droid-bionic-forum/9800-how-get-your-phone-back-upgrade-path.html
rgb2448 said:
follow the steps in the first post of this thread. should get you back going.
http://www.mydroidworld.com/forums/droid-bionic-forum/9800-how-get-your-phone-back-upgrade-path.html
Click to expand...
Click to collapse
did this multiple times but heck ill try it again...
brandonaspencer said:
did this multiple times but heck ill try it again...
Click to expand...
Click to collapse
Can you get in fastboot mode? Does it say flash failed? What did you format?
i tried to flash the ota. no go. formatted webtop. stuck in ap mode. says flash failure. at the bottom says invalid sp data and invalid cg webtop. wont flash anything...
You need to use the moto-fastboot.exe and flash the stock webtop partition back to your phone. That is a hacked version of fastboot that supports larger than 256MB partition sizes and will restore your webtop so the phone can boot.
You finally gave enough information about what you actually deleted/formatted and the exact error was so that you could be helped...congrats!
Hint: "moto-fastboot flash webtop grfs.img" from a directory that contains the moto-fastboot.exe and the 2 required .dll files and the grfs.img from the original FXZ.
cellzealot said:
You need to use the moto-fastboot.exe and flash the stock webtop partition back to your phone. That is a hacked version of fastboot that supports larger than 256MB partition sizes and will restore your webtop so the phone can boot.
You finally gave enough information about what you actually deleted/formatted and the exact error was so that you could be helped...congrats!
Hint: "moto-fastboot flash webtop grfs.img" from a directory that contains the moto-fastboot.exe and the 2 required .dll files and the grfs.img from the original FXZ.
Click to expand...
Click to collapse
THank you!
http://dl.dropbox.com/u/7632904/moto-fastboot-win32.zip
That is the moto-fastboot.exe and dll files you need.
I already gave you the syntax to use it above and you already have the FXZ so just put them all together in a folder with the grfs.img and navigate to that folder from command prompt once the phone is booted in fastboot mode and use the command above.
It will proceed to flash the grfs.img in 5 256MB chunks and a 6th smaller chunk and then use moto-fastboot reboot and it should boot normally if you haven't messed up anything else in the meantime.
Good luck!
cellzealot said:
http://dl.dropbox.com/u/7632904/moto-fastboot-win32.zip
That is the moto-fastboot.exe and dll files you need.
I already gave you the syntax to use it above and you already have the FXZ so just put them all together in a folder with the grfs.img and navigate to that folder from command prompt once the phone is booted in fastboot mode and use the command above.
It will proceed to flash the grfs.img in 5 256MB chunks and a 6th smaller chunk and then use moto-fastboot reboot and it should boot normally if you haven't messed up anything else in the meantime.
Good luck!
Click to expand...
Click to collapse
Sir you are a genuis and a scholar! you know there are two different fastboot recoveries?? I needed exactly what you said, so where can I send you the $25?
brandonaspencer said:
Sir you are a genuis and a scholar! you know there are two different fastboot recoveries?? I needed exactly what you said, so where can I send you the $25?
Click to expand...
Click to collapse
Keep it! Learn how to ask better questions with more complete information and tell everyone else to do likewise and you will save us all far more valuable time and effort...seriously.
Happy holidays!
Oh and also share the knowledge you get with others and use the thanks button...it's what this forum is for.
Thanks for the offer, but I'd really rather you just did as I suggested and enjoy your phone and learn to understand it better.
Win, win!
I slept in late or I would have answered, but Cellzealot definitely explained it well.
Hi, my best friend she had a HD phone, one day got stuck into the M logo, the only thing I can do is get into the fastboot, no recovery no nothing.. So i try to reinstall the rom, have download several tools but i cant do anything, after several intents to install roms i hace in AP fastboot flash mode, device is unlocked status code 1fastbookt Reason sticky bit factoy_fastboot. for a 2nd time but i can install roms, I dont know if phone bootloader unlock and cant check... I dont know if phone is usb debugging cause it wont load the system. I dont see any internal files from phone I also try rsd lite, but the same it says that it start doing the process but nothing else happen.. any ideas on how to get a rom install there..
thanks
SAME thing..
Please do help us...No recovery...No debugging...stuck at logo..!!
If you don't have an unlocked bootloader, I don't think you can use Myth or RSD to flash an ICS rom over a JB rom.
Did you load the latest Motorola USB drivers? When you connect the phone, run adb to list the devices. Does your phone appear?
not for me doesnt show any devices... and while trying to do other commands always get stuck ad *daemond started succesfully* but doesnt do anything.. also when trying to use motorola device manager it says it will update and never connect to server and close the app.
if i do fastboot commands like reboot-loader it does work it reboots the phone, but if i try to flash something doesnt it doesnt do anything.. i try using mfastboot also and the same happen.
Is there a way to flash a rom or something so i can fix this phone or it is dead?
On the Fastboot screen, if it says UNLOCKED in capitals next to "Device Status:" , then this problem is easily fixable.
Download RSD Lite from here: http://forum.xda-developers.com/showthread.php?t=2231249
Download Motorola Stock Firmwares:
Stock Jellybean for AT&T: http://sbfdownload.droid-developers...MB886_NII_TA-2-16-release-keys-NII-MX.xml.zip
Stock Jellybean for Bell Canada: http://sbfdownload.droid-developers...FFW-11-4-release-keys-BellMobility-CA.xml.zip
Open up your zip file and replace the .xml with the new XML you will download from this link: https://www.box.com/s/num1eshkf0c2or2h4160 You really can't forget to do this!
Launch RSD, connect device to PC, make sure RSD recognizes it. Navigate to your firmware file, select it, and press the start button. Sit back, relax, and let it do its work. It will take around 5-10 minutes. Do not unplug the cable, and do not attempt if you are in a situation in which you think you may lose power (especially if running from a desktop PC).
If RSD Lite won't work, then this thread will show you how to manually flash your stock firmware: http://forum.xda-developers.com/showpost.php?p=40929335
Basically, you repeat all the instructions I just gave you and then manually input some lines in Command Prompt.
X1053, rooted and unlocked bootloader on T Mob US
Tried to install a new kernel but it failed. Wiped cached (factory reset in twrp) and now it won't boot past the animation logo.
As its not booted into the OS, windows won't recognize it as a device so i can't install a new rom to try again. Windows 8 'bings' when I connect it but it won't load as a drive.
I CAN get into AP Fashboot Flash Mode If I then go to Recovery, it still takes me to twrp. But there are not zip files to install that work and I can't work out how to copy them over without windows recognizing the device?
Thanks in advance
You'll maybe need to flash the same stock firmware version you're on now...4.4 or 4.4.2 or whatever version you were on. Then root again.
This will help you...
http://forum.xda-developers.com/showthread.php?t=2603358
Good luck!
kj2112 said:
You'll maybe need to flash the same stock firmware version you're on now...4.4 or 4.4.2 or whatever version you were on. Then root again.
This will help you...
http://forum.xda-developers.com/showthread.php?t=2603358
Good luck!
Click to expand...
Click to collapse
Thanks for the reply. the problem is I can't connect to the phone to transfer a new firmware on. It 'bings' on USB plug but won't open as a USB drive. I can't get the phone to boot, can only get it to recovery. i tried reinstalling the motorola drivers again but still no luck.
When it was running Ok, I could plug it in (when it used to load into the android OS OK) and it would appear as a USB drive in Windows 8. I also tried on a different laptop.
emailrob said:
Thanks for the reply. the problem is I can't connect to the phone to transfer a new firmware on. It 'bings' on USB plug but won't open as a USB drive. I can't get the phone to boot, can only get it to recovery. i tried reinstalling the motorola drivers again but still no luck.
When it was running Ok, I could plug it in (when it used to load into the android OS OK) and it would appear as a USB drive in Windows 8. I also tried on a different laptop.
Click to expand...
Click to collapse
When you boot into bootloader, does the phone itself recognize that it is connected via USB? If so, you have to obtain the current SBF of your phone and flash over the files via fastboot.exe and mfastboot.exe.
There are plenty of guides throughout this site. Take your time and read everything before you make your first move.
Cyphir said:
When you boot into bootloader, does the phone itself recognize that it is connected via USB? If so, you have to obtain the current SBF of your phone and flash over the files via fastboot.exe and mfastboot.exe.
There are plenty of guides throughout this site. Take your time and read everything before you make your first move.
Click to expand...
Click to collapse
OK panic nearly over! I managed to get it flashed using RDS lite. 4.4 is back on now, although I lost my root Not sure I want to go down the whole downgrade to 4.2.2 etc but I'll see. Thanks again
Just adding a reply in case anyone has a similar issue.
RSDLite managed to get the firmware back on. It lost root, but what actually happened is the recovery got deleted / corrupted.
So i went back through the rooting guide which started by adding twrp and then flashing. Rebooted, and SuperSU tells me all is OK and root is there.
:laugh:
Is your phone recognized by fastboot or adb?
Since your bootloader is unlocked, manually flash the 4.4.2 firmware files, then TWRP, then boot into recovery, use adb to push SuperSU or whichever root program you prefer to /sdcard, then use TWRP to flash it.
nhizzat said:
Is your phone recognized by fastboot or adb?
Since your bootloader is unlocked, manually flash the 4.4.2 firmware files, then TWRP, then boot into recovery, use adb to push SuperSU or whichever root program you prefer to /sdcard, then use TWRP to flash it.
Click to expand...
Click to collapse
Its all working OK now thanks. I just flashed 4.4 again and re-installed TWRP.
Help! My Motorola RAZR I XT890 cannot be "unbricked" and I tried several methods...
Hello!
I unlocked the bootloader successfully, then I tried to root my phone using The Razr guy method and I used the "RAZRi_Root_Windows" file, while rooting my phone went to the "warning bootloader unlocked" screen and it just loops forever from that screen, the bat file, showed that it successfully rooted my phone. I tried to fix it using rsd lite, but it never detects my phone, so I searched for a way to make my pc able to detect it, so I found I could use Intel xFSTK, installed it but still nothing it doesn't appear as shown in the tutorial, I even downloaded the dll file that it needed to run, but after running the xFSTK DLDR or something like that, the application is completely empty, and I saw it should show some tools to download something. Also tried using Linux Zorin, but it only says that my XT890 cannot be accessed and shows an usb error code.
I am able to enter the fastboot screen, the one you get by pressing POWER and VOLUME DOWN, also it charges my batter completely normal. Also my pc is able to show that the XT890 is connected, but only before installing the drivers and it shows the CD installer for the Motorola Device Manager and some other files (all this while looping), and if I enter the fastboot flash mode, it appears as "fastboot smi S", with a yellow triangle and an exclamation sign while in Windows device manager. It has Jelly Bean update from telcel (mexico), and I already have the xml.zip file to reinstall it.
I use windows 8.1 , and as mentioned Linux Zorin on my PC.
Could some help me with it...if you now how to fix it please list every single step on how to do it T_T, THANKS IN ADVANCE!!!!
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Hazou said:
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Click to expand...
Click to collapse
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
weird_user said:
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
Click to expand...
Click to collapse
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Thanks again!!!
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
I am able to enter RECOVERY MODE NOW (I installed CWM, before this I was only able to see the android lying on the floor ans saty dead right there, I was supposed to press Volume + and - and the camera button at the same time, but nothing happened), it seems to be easier to unbrick it this way, but now the problem is that after I follow the steps to reinstall the original ROM, it aborts installation. I read this may be caused due to a file on the zip file, I looked for it, but nor the Folder META-INF, whic is supposed to contain a "update-script" file, nor that file is anywhere in the ROM folder...
I've even tried cyanogenmod (after first trying Telcel original ROM and then the retail GB ROM) cuz it actually contains the folder previously mentioned and the file is in a different path, but it is there, I modified it, but got a "Can't open tmd/update.zip (bad) Installation aborted" error...I don't know what else to do T_T...
Note: I also used sideload and CWM to install it, but the same thing happens. Also checked some other post about this issue, but none has helped me...
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Hazou said:
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Click to expand...
Click to collapse
It's done! Thanks!
I actually used another computer with windows 10, also I used RSD Lite and it worked just fine, now I have the stock ROM from Telcel and it it is working almost normal. The only abnormality I've seen is that my phone turns itself off when battery is at 20%, I searched info about that problem and it says I may re calibrate the battery, so it may work fine again, but now I need to root again to be able to do that T_T, hope it works this time...
THANKS! again!