Maxx stuck boot looping - Droid Ultra Q&A, Help & Troubleshooting
Hey Guys,
I rooted my device a while ago and everyday had to dismiss the OTA update for the last few months. The other night I accidentally accepted the OTA and know my phone is stuck in a bootloop when connected to power. I'm occasionally able to get into Fastboot mode for RSD to see the phone, ADB will not see the phone. When I attempt to select Recovery or Factory the phone bootloops. I have also tried House of Moto and that didn't work.I have tried flashing all the files located at sbf with no luck. In Fastboot the Device is listed as UNLOCKED with a Status Code: 1.
Any help will be greatly appreciated.
When I flash using House of Moto I get an error for the following:
gpt.bin
motoboot.img
logo.bin
boot.img
recovery.img
system.img
NON-HLOS.bin
uniqueflips said:
Hey Guys,
I rooted my device a while ago and everyday had to dismiss the OTA update for the last few months. The other night I accidentally accepted the OTA and know my phone is stuck in a bootloop when connected to power. I'm occasionally able to get into Fastboot mode for RSD to see the phone, ADB will not see the phone. When I attempt to select Recovery or Factory the phone bootloops. I have also tried House of Moto and that didn't work.I have tried flashing all the files located at sbf with no luck. In Fastboot the Device is listed as UNLOCKED with a Status Code: 1.
Any help will be greatly appreciated.
When I flash using House of Moto I get an error for the following:
gpt.bin
motoboot.img
logo.bin
boot.img
recovery.img
system.img
NON-HLOS.bin
Click to expand...
Click to collapse
Does it ever actually boot up and then just restarts? Or are you never getting to the homescreen?
no home screen
Hi,
It won't even boot loop unless it's connected to power. When it is it just boot loops, tried everything but can't get past the boot loop. Spent countless hours trying to make any progress.
try flashing TWRP from fastboot
Code:
fastboot erase recovery
fastboot flash recovery name.img
if you get into recovery try restoring a nandroid
if that doesnt work, make sure you are flashing the appropriate SBF from the update you were in teh process of taking. My bet is somehow your device got partially updated (bootloader) so you are now unable to flash the SBF you were prevously on. ie. you were on 4.2.2, and took the 4.4 update, you need to flash the SBF for 4.4, not 4.2.2
Once you get back up and running, make sure you disable the Moto OTA app using titanium or the like. That should prevent the phone from trying to take an update again.
Still no luck
Thanks everyone for the suggestions, I'm not sure which firmware it was trying to install so I installed all the firmwares available via House of Moto and still no luck. Tried performing a Full and Keep Data and still the phone will continue to boot loop. One thing I did notice during the install using House of Moto I see the following error multiple times:
(bootloader) Variable not supported!
I got this error on all 5 firmwares.
Any ideas...
uniqueflips said:
Thanks everyone for the suggestions, I'm not sure which firmware it was trying to install so I installed all the firmwares available via House of Moto and still no luck. Tried performing a Full and Keep Data and still the phone will continue to boot loop. One thing I did notice during the install using House of Moto I see the following error multiple times:
(bootloader) Variable not supported!
I got this error on all 5 firmwares.
Any ideas...
Click to expand...
Click to collapse
what version of android were you on prior to this happening. What version was the OTA attempting to update you to?
I think I was on Android 4.4 Blur_Version.19.5.3.obake_verizon.Verizon.en.US, not 100% sure what it was trying to install 4.4.4 or 4.4 19.6.3.
Tried House of Moto again and on the 4.2.2 12.15.15 and 4.4.4 I don't get the (bootloader) Variable not supported! error. The phone still boot loops.
uniqueflips said:
I think I was on Android 4.4 Blur_Version.19.5.3.obake_verizon.Verizon.en.US, not 100% sure what it was trying to install 4.4.4 or 4.4 19.6.3.
Tried House of Moto again and on the 4.2.2 12.15.15 and 4.4.4 I don't get the (bootloader) Variable not supported! error. The phone still boot loops.
Click to expand...
Click to collapse
have you tried with the latest version of RSD lite?
If so make sure you edit the XML file to remove the part about erasing userdata
lets try this too... go to sbf.droid-developers.org and download this file for the maxx "Android 4.4.4
Blur_Version.21.11.21.obake_verizon.Verizon.en.US"
Install the latest moto device manager and RSD lite, then try flashing (might erase userdata)
If that does not work, you can manually flash each file in fastboot, lmk if any of that works
last Q, do you have a motorola factory cable?
Tried with and without removing the getvar file and no luck, still stuck in an endless boot loop when connected to power. ADB still doesn't see the device even in Fastboot mode. Never flashed each file in fastboot individual doesn't that require ADB?
uniqueflips said:
Tried with and without removing the getvar file and no luck, still stuck in an endless boot loop when connected to power. ADB still doesn't see the device even in Fastboot mode. Never flashed each file in fastboot individual doesn't that require ADB?
Click to expand...
Click to collapse
no you dont use adb from fastboot, you use "fastboot"
Lets see if we can get you booted to a recovery. Download this file, save it as recovery.img in your ADB directory.
boot to fastboot and run this command to determine fastboot sees the device
Code:
fastboot devices
If you see your device, then run the next command
Code:
fastboot flash recovery recovery.img
then try to boot to recovery. post result (make sure when you highlight "recovery" in fastboot you use volume up to select it. I just made the mistake of using power and my phone wouldnt boot to recovery)
Related
[Q] Official Stock Images Don't Load
Tried to return my wif xoom to stock with the official images and ran into a problem. Followed the steps : adb reboot bootloader fastboot flash boot boot.img < this flashed Ok fastboot flash system system.img < adb stuck waiting for xoom .. had to manual reboot the xoom. Never got to the remaing steps. Tried several times with the same result, almost. One time after manual reboot came up with "RSD mode support 3". Had to do a hard reset to recover. I ended up flashing Tiamet v1.4.0 again. Maybe I'm doing something wrong here.
RSjagman said: Tried to return my wif xoom to stock with the official images and ran into a problem. Followed the steps : adb reboot bootloader fastboot flash boot boot.img < this flashed Ok fastboot flash system system.img < adb stuck waiting for xoom .. had to manual reboot the xoom. Never got to the remaing steps. Tried several times with the same result, almost. One time after manual reboot came up with "RSD mode support 3". Had to do a hard reset to recover. I ended up flashing Tiamet v1.4.0 again. Maybe I'm doing something wrong here. Click to expand... Click to collapse Are you sure it froze up I mean the system.img does take longer to do than the boot.img. Have tried RSDLite 5.0? You might want to look into it.
I waited about 10 minutes before the manual reboot. Is 'adb' required before the flash command? The 1st step took about 14sec and based on the size of the files, the system image should flash in less than a minute. I'll research RSDLite 5.0. Thanks. UPdate: Today I tried it again and was successful, Xoom now stock and locked. For info: boot.img took 15sec to flash system.img 17 minutes Recovery.img 20sec Userdata.img 4 min erase cache 1.5s Hope this helps someone.
[Q] XOOM - Update Issues with 3.x moved to ICS
My Xoom has had an odd problem. When I got it new, I unlocked the bootloader and rooted. However, any pushed updates from Moto such as HLK55 caused my Xoom to boot and show the unhappy !Android icon. I had to shut down cold, and reboot. In other words, it never updated properly. Now that ICS is out, I have Kang 1/15 running but have some non-crash issues. I'd like to flash to try to update to the factory ICS push file but fear that my XOOM won't complete as well. Any ideas?
So long as you flash back to complete stock using the Motorola files you should be able to upgrade your way up to ICS (via 3.1 and 3.2). Get the files from http://developer.motorola.com/products/software/ And as on that page, get ADB running and make sure it detects your device then run these commands. fastboot flash boot boot.img fastboot flash system system.img fastboot flash recovery recovery.img fastboot flash userdata userdata.img fastboot erase cache fastboot oem lock Make sure you get the right version for your device.
Problems with booting process on my Xoom
Hello I have a Motorola Xoom from Verizon, and this is the issue. When I turn on, the tablet it's stuck in M logo screen, I already read almost any information about this issue, but still I can't use my xoom. I already done this: the bootloader is already unlock a) Files From MZ600 HRI39 fastboot flash boot boot.img fastboot flash system system.img fastboot flash recovery recovery.img fastboot flash userdata userdata.img fastboot erase cache b) used RSD method c) used recovery method too I had used every method on this forum to recover my Xoom, and nothing seems to work, at this time I don't know what else do. adb commands doesn't work for me, only with fastboot and RSD is visible my device. At this time I accept any sugestions, Since apply a factory reset, or install a new Android version
[Q] [URGENT][Help needed][Moto G failed to validate boot image]
HI I was flashing the GPe image on my XT1033 and while flashing the boot.img and logo.bin i got an error - out of memory , but rest of the parts like system.img etc flashed properly and now my phone won't boot giving me the error "failed to validate boot image'. I am stuck at the bootloader screen and now neither can i flash some other image since my phone isn't being recognized anymore with cmd showing the message 'waiting for device' Can someone please provide a solution?
Hello. I faced the same problems when installing the 4.4.4 br firmware and trying to revert to my original firmware. This happens because you have a locked bootloader and/or maybe you flashed a wrong boot.bin and you can't reflash boot.img because the bootloader is locked! What I did is unlock the bootloader and all my problems vanished.. -_- reflash all the files using mfastboot, if it gives you errors on gpt.bin and motoboot.img dont worry and go on with the rest. Oh, and one strange thing that I luckily figured out, is that to get the device recognized by the PC in the fastboot mode you got to enter fastboot MANUALLY. THat is, press volume down 3 seconds and then power on. It's gotta say: Fastboot reason: Volume-down key pressed. If you try to boot and it enters fast boot and gives you the error, for some reason doesn't recognize.
Updating to 6.0....and bricked
Stock, unrooted xt1540. Got the update notification this morning, so excited. After updating, it's boot looping and the M logo is the furthest it can go. Tried to fastboot flash back to old 5.1.1 factory image, "image validation failed". Maybe because boot loader got updated and won't roll back? All I can think of now is to wait for the 6.0 factory image and try that again, but I may end up waiting for it too long. Any suggestions? Thanks!
What about the images at http://forum.xda-developers.com/2015-moto-g/general/ota-moto-g3-marshmallow-ota-links-t3284308
Try in fastboot clear the cache and data ...
have you tried using twrp to just install a cm rom or something similar? worst case scenario you can use twrp to force the soak test images onto their respective partitions. if your bootloader was updated the soak test will run...even if it bootloops for any reason, then at least you've taken one step forward again.
MrTooPhone said: What about the images at http://forum.xda-developers.com/2015-moto-g/general/ota-moto-g3-marshmallow-ota-links-t3284308 Click to expand... Click to collapse I wish I could resume the OTA, even manually, but right now I can only go to bootloader, not even the stock recovery....Thanks for the idea, though! Really appreciate it.
hp420 said: have you tried using twrp to just install a cm rom or something similar? worst case scenario you can use twrp to force the soak test images onto their respective partitions. if your bootloader was updated the soak test will run...even if it bootloops for any reason, then at least you've taken one step forward again. Click to expand... Click to collapse I just tried flash in the twrp.img, got declined by bootloader again... Now is there factory images for the soak test? Thanks!!
lexer98 said: Try in fastboot clear the cache and data ... Click to expand... Click to collapse clearing cache went through, but clearing data failed. Rebooting to bootloader mode and try returning to stock again, still no go...
In fastboot mode, I can flast logo, fsg, NON-HLOS, bootloader, recovery -- all from 5.1.1 factory image, but when I tried to flash boot or system chunks, it says: D:\Desktop\g\Mfastboot>fastboot flash system system.img_sparsechunk.0 target reported max download size of 268435456 bytes sending 'system' (262141 KB)... OKAY [ 10.573s] writing 'system'... (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 11.042s Is my only option to wait for the MM factory image....
alvin612 said: I just tried flash in the twrp.img, got declined by bootloader again... Now is there factory images for the soak test? Thanks!! Click to expand... Click to collapse Well....yes and no. http://forum.xda-developers.com/201...-devs-moto-g3-xt1540-soak-test-files-t3255643 The images all flash in fastboot except the system one, which requires using adb shell while booted to twrp. You have to use a dd command to force the system.img into the correct partition.
Earlier today I had to give up on this osprey because of limited bandwith for fix. Thanks again for everyone's help!!
My phone got bricked after trying to downgrade from MM to LP Hello, yesterday I was trying to downgrade from MM to LP using Fastboot and by mystake I flashed "fastboot flash partition gpt.bin" and it failed, the others commands failed as well, after that I was unable to turn on my device, it only let me access to Bootloader Mode and also shows the battery charging, cannot access to recovery, and it shows black screen when I try to turn it on. My phone is completely stock, It has neve been rooted, stock recovery. Its a Moto G XT1540. the Bootloader is locked. Is there a way to bring my phone back to life? What can I do?
JulesSDK said: Hello, yesterday I was trying to downgrade from MM to LP using Fastboot and by mystake I flashed "fastboot flash partition gpt.bin" and it failed, the others commands failed as well, after that I was unable to turn on my device, it only let me access to Bootloader Mode and also shows the battery charging, cannot access to recovery, and it shows black screen when I try to turn it on. My phone is completely stock, It has neve been rooted, stock recovery. Its a Moto G XT1540. the Bootloader is locked. Is there a way to bring my phone back to life? What can I do? Click to expand... Click to collapse I contacted Motorola. Warranty covers my situation. Going to ask for a replacement.
JulesSDK said: Hello, yesterday I was trying to downgrade from MM to LP using Fastboot and by mystake I flashed "fastboot flash partition gpt.bin" and it failed, the others commands failed as well, after that I was unable to turn on my device, it only let me access to Bootloader Mode and also shows the battery charging, cannot access to recovery, and it shows black screen when I try to turn it on. My phone is completely stock, It has neve been rooted, stock recovery. Its a Moto G XT1540. the Bootloader is locked. Is there a way to bring my phone back to life? What can I do? Click to expand... Click to collapse Unlock the bootloader and then try flashing. I was in a similar situation once, was getting failed messages when trying to flash official signed factory images. Unlocked the bootloader and then tried to flash and voila, everything flashed smoothly. No harm in trying unless you are worried about warranty.