Database Develop

Need Boot Help

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!

[Q] Bricked razr i help - locked bootloader

Well, this is embarrassing...
Current Status:
After a factory wipe and reinstalling (phone was OK after that) and an OTA, i managed to nearly brick my razr.
Currently every time i start it lands in fastboot (according to RSD Lite mode S) with the message fastboot reason: flash failed
after 'fastboot reboot-bootloader' i can operate the menus but only changing the console type and power off work, everything else results in a freeze.
Reflashing CFC_signed_customer_8.7.1I-110_IFW-DE-32_O2DE.xml.zip or 31 is not possible, since the OTA update apparently changed boot[1], gpt[2], and few other things to version "8.7.1I-110_IFW-DE-39" (the only thing i can flash from those are the recovery partitions and from the new one the gpt.bin)
Custom fastboot also does not work, since i'm not eligible according to Motorola ( tis was my first thought to check the custom boots & finally unlock the bl *g*)
I already ordered the factory adapter (hey, you never know, when you're gonna need one) & My Battery still has ~3.9v left, so i think a few tries should not hurt that much : >
TL;DR, Here's my question:
1) is it possible to patch the images provided in CFC_signed_customer_8.7.1I-110_IFW-DE-32_O2DE.xml.zip with the binary patches from Blur_Version.81.5.32002.XT890.O2.en.DE (updates to: 8.7.1I-110_IFW-DE-39_O2DE) and then maybe re-flash them to get my razr back from the near death zone?
2) should i hope and pray that Motorola announces JB upgrade and provides us with the full system images within the next few days?
3) can anyone find a full system image / full update with the version: 8.7.1I-110_IFW-DE-39_O2DE ?
References:
[1]: from update-script:
assert(apply_patch("MTD:boot:11534336:affeb8868070f6e6f061143b662e03b5bf65b2f3:11534336:19bf404a393a50d08a809affd45df5692e36e1db",
"-", 19bf404a393a50d08a809affd45df5692e36e1db, 11534336,
affeb8868070f6e6f061143b662e03b5bf65b2f3, package_extract_file("patch/boot.img.p")));
[2]: There is a brand new gpt.bin file within the OTA package
Cheerio,
Andy

The Problem is, without unlocking your Bootloader, you can't downgrade the Boot. img.
I would suggest you to grap the 39002 O2 Homemade Fastboot from Mattlgroff and flash only the Boot. img out of it. If you're an lucky guy, you're able to boot after that.
An Guy from my Home Forum tried the downgrade from 40002 today with an locked boot loader. RSD stopped @ point 1 GPT. His solution to boot his phone again was to flash the gpt.bin out of the 40002 OTA .zip.
So your only chance to get your phone back is to find flashable Images from the 39002 or 40002 because of the secure Level.
The easiest way is to unlock the device, I can downgrade to any FW. Or you'll have to wait for an updated Fastboot File to flash with RSD.

Hokay, apparently i had a typo yesterday when i tried to unlock the bootloader
But, now after trying the custom fastboot, i still land in fastboot with reason: Sticky bit fastboot
and all other menus still cause a freeze : /

If you're now unlocked, get an EU FW, regardless what Version. Open the XML with Notepad + or any similar Programm and delete ONLY the complete Line that contains MOTOBOOT. Save the XML and start RSD 6.1.4.
After that you should be good to go.

HSD-Pilot said:
If you're now unlocked, get an EU FW, regardless what Version. Open the XML with Notepad + or any similar Programm and delete ONLY the complete Line that contains MOTOBOOT. Save the XML and start RSD 6.1.4.
After that you should be good to go.
Click to expand...
Click to collapse
Purrrrfect, i owe you a bottle of wine.
Problem solved : >

Yeah, I'm glad I could help you out... RazR I Nr. 8 > Strike

bricked
hi guys the same thing happen to me i cant use rsd or fastboot because it says stigki bit fastboot.and in rsd it fails tryin to flash boot. im in mexyco i was using the new ota for 30006 that would be 40002. i just try to erASE THE BOOT LINE AND IT DIDNT WORKIT SAID THE SAME. HELP

So you're on 40002 and tried to flash back with RSD and your Bootloader is locked?
RSD failed on step one, right?

brick
Yes sir. Iwas on 40002 and with the rsd i was trying to go back to stock 30006,but on step 3 it says fail. Then i try to fastboot 40002 but it tqkes me again to fastboot and its freezes when i try to open a command like normal boot or recovery. I tried to eras the lineinside of motoboot where it says motoboot like the guy you just helped. But in my case still gets stuck on step 3in the rsd. So could you send me images of how erase the line of motoboot on text editor?? Im boot unlocked.

You mean 31006...Here ya go (unpack it > i can't attach an .xml)

Thank u sir. So i flash this on rsd,right? Vause i think that this is the one i have.the last digits are 31 on mine an starts cfc . Something else. I cant really tell u cause im at work but tonight i'll try ur method. Hope it works.

http://www.mediafire.com/download.php?ud9kowzk1uw2bcb
Use RSD 6.1.4 and copy the xml into the fastbootfolder. That's all...BTW: Charge your battery if possible or hope you got enough juice!

unbricked
thank you sir. everything like new!!!!!!!!
i"ll buy u some beers.

my razr i is workin now but i cant update the ota for the 31006 thats going to take me to 40002??

You're trying to update regular over the Phone or the manual over the leaked Update.zip? If you're trying it over the leaked zip, than beware. There's one if you're coming from 31006 and one from 32002.
Sent from my XT890

I go into software update, then i download the file, its like 50mb. Then it goes into rwcovery but the android dies and says aborted. So then i tried in recovery mode to flash zip blur ota 310006 but it happen the same. So i decided to stay in mis rom the 31006 from sept. But i was wondering if now i could flash in fastboot another rom like 40002? I saw u guy have the ota update for that rom.
---------- Post added at 03:04 PM ---------- Previous post was at 02:07 PM ----------
I go into software update, then i download the file, its like 50mb. Then it goes into rwcovery but the android dies and says aborted. So then i tried in recovery mode to flash zip blur ota 310006 but it happen the same. So i decided to stay in mis rom the 31006 from sept. But i was wondering if now i could flash in fastboot another rom like 40002? I saw u guy have the ota update for that rom.

Thank you - you're the best
HSD-Pilot said:
If you're now unlocked, get an EU FW, regardless what Version. Open the XML with Notepad + or any similar Programm and delete ONLY the complete Line that contains MOTOBOOT. Save the XML and start RSD 6.1.4.
After that you should be good to go.
Click to expand...
Click to collapse
My RAZR i works again thanks to HSD-Pilot. You saved my life.
THANK YOU
Roman

how found fastbootfolder me friend, sorry im newbie and me phone is death, please help

Razr i black screen after update phone not getting on
After i have unlock bootloader and root the phone....i have to do a fresh update to last Jelly Bean....phone have got turno of for starting insatll the update....and have rest like that...............When i press Power or Power and Vol Down is just doinf a short vibrate and the Notification led stay On for 10 sec after led OFF and a short vibrate.....>>Connecting to PC no getting any device on RSD or Fastboot and in Windows detect as a MEDFIELD device for wich no driver i found anywhere.........Phone was having 100% POWER before doing all this....adn i have try on several Pc with diferent Windows and diferent 32 or 64 bit with all RSD, drivers Sdk, etc installled and same results.....if anyone have a ideea how to repair will be a really expert on this modding devices....thank you and ...HELP

[Q] atrix hd stuck in M logo

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.

Help! My Motorola RAZR I XT890 cannot be "unbricked" and I tried several methods...

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!

[MOTO X1 - BRICKED] I think I got the master level bricked.

Ok, this is only for the Jedi masters.
I have a Moto X (1st gen - XT1058) bricked. However I think I got the master level bricked.
I was using the ROM Retail BR 4.4.4 and I upgraded to version 5.1 via OTA. All went quiet until the unit began to catch on and off yourself. I reinstalled version 5.1 via RSD Lite smoothly. The device worked for a few weeks but after some time the same problems again.
Until the phone died. Do not leave the boot screen.
I thought it was something not too bad, because I could still access the Fastboot (AP Fastboot Flash Mode (S) 30.BE). However I can not get into Recovery mode and something else I do return with errors involving:
Failed to read signature is aboot partition
Boot up failed
The solutions I found on the internet I've tried:
Reinstall the original ROM by RSD Lite (and earlier also suppressing gpt.bin)
- Always fails when the application tries to apply flash partition gpt.bin. If I delete this line in the XML file, the failure persists, but the next line of execution.
Use original gpt.bin files, boot.img, system.img and recovery.img and try to install them through the mfastboot fastboot command and Windows Terminal 7 (32 and 64bit).
Use a file blankflash & the qflash.exe ... command from the Windows terminal. Can install the drives and recognize the specific port of the device, but the process does not continue.
Does anyone have any light around? Something different than I've ever tried?
My daughter is missed to watch Pocoyo in Youtube. It was the only thing that calms my little child.
Help me! :crying: