I accepted the 5.1 OTA, it seemed to download fine, rebooted to install it, and it failed at around 20% or so with this log:
Code:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/app/ConfigUpdater/ConfigUpdater.apk" has unexpected contents.
E:Error in cache/update.zip
(Status 7)
Installation aborted.
Since then, that's all I get when I boot it up. I don't have ADB Debugging enabled, so I figured the easiest way to fix it was to flash back to stock, but I can't get it the bootloader to unlock. I can get to the bootloader, and fastboot recognizes it with the correct serial number, but fastboot oem unlock keeps failing with this:
Code:
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 2.640s
I've tried all the USB ports on my computer and several different cables, but the result is the same. I've been banging my head against the wall for a couple weeks now on this, tried a couple different tools, but it all keeps failing at the same spot because the bootloader just won't unlock. Is there any hope of fixing this, or am I in the market for a new tablet?
Can you try opening ADB/Command Prompt with administrative rights and retrying the unlock of the bootloader?
Fobos531 said:
Can you try opening ADB/Command Prompt with administrative rights and retrying the unlock of the bootloader?
Click to expand...
Click to collapse
All right, gave that a shot, but still getting the same results.
I had my N7 go belly up too while doing the update. What got things back to normal was to use the "flash-all.bat" file that comes with all the updates (it's in the zip file from Google. Caution!!! ****Each flash-all.bat is unique to each Android version****. Make sure you use the proper .bat file. ). First I had to go back to 4.4.4 (for some unknown reason). After that, I did the same (ran the "flash-all.bat" file that came with 5.1) and bingo, everything went fine.
I was about to toss my N7 in the garbage, but after getting this suggestion from XDA member "Fobos531", gave it it go and it worked.
Look over here:
http://forum.xda-developers.com/nexus-7/help/thank-google-bricking-nexus-7-t3082379
Also make sure to take a look at this thread, I thought it might be relevant: http://forums.androidcentral.com/go...s-bootloader-failed-remote-invalid-state.html
phillip - Unfortunately (or maybe fortunately), since I can't get the bootloader unlocked, I haven't been able to get far enough to screw it up by flashing the wrong thing. Using the flash-all.bat starts by failing to unlock the same way, then not flashing anything at all because the bootloader is still locked.
Phobos - My tablet shows 4.23 installed. Since the last successful system update was the LRX22G OTA, is it then likely I have the invalid version? And if so, any clue how I would go about fixing that with the bootloader still locked?
Maybe bootloaders can be flashed while being locked? Try flashing this one using fastboot(the link is from this site:http://www.wugfresh.com/google-changes-nakasi-and-nakasig-factory-packs/) : https://www.androidfilehost.com/?fid=95916177934550135 Make sure the md5 checksum is valid: it has to be df53028033c9eccf4fe5ba7bc198ce24). Afterwards flash it using "fastboot flash bootloader name-of-bootloader-file.img (i think this is the right command).
Note: Everything you do, you do on your own risk.
Good luck!
EDIT: In the WugFresh page it says that your bootloader must already be unlocked, but I just don't have any idea on how to fix the adb error you are getting.
Hi I have the XT1570, running unlocked and with rooted but stock 5.1.1. I have run in to some issues with the recovery part.
Firstly I wanted to go back to the recovery and flash a stock recovery so I could get the OTA for MM, i did that using fastboot, and the flash worked fine according to fastboot, however once i rebooted into recovery it would not load, got an error message, I forget now something about dumping back to bootloader.
Anyway i fixed it got TWRP back on again, then tried a different stock recovery, same thing same error, so i thought I would easily get back to TWRP by the same method, flash again. I was wrong, now fastboot told me , target reported max download size of 536870912 bytes
error: cannot load 'twrp-2.8.7.1-clark': No error
Remember this is the exact same TWRP image i have just flashed not 5 mins before.
So i thought ok then, maybe an old image is in there taking up space or something.
C:\Users\David\Desktop\Mfastboot\Mfastboot>fastboot erase recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.017s]
finished. total time: 0.019s
Now I get the message:
Invalid boot image header.
Error:failed to load kernel
Boot up failed.
I presume I have deleted everything in the recovery partition, and so messed it up good, but I dont know how to fix it at this point.
I also erased the cache along the way (via fastboot) as I tried to get the OTA update to work anyway just to see what would happen, so I had to erase the cache to cancel updates
I must reiterate, I can boot into Android and use my phone no issues, at all, just I have no recovery at all and this means updates arent going to work, also i cant seem to find a reliable source for a stock recovery.
Some step by step help would be appreciated, as I am not an expert by any means on this.
Thank you.
Also my device was bought in China as that is where I am, it does indeed have the code name XT1570, dual sim, I would assume it is basically the same as the XT1572 asian. I do also have an original backup of the phone after unlocking bootloader, before root, which was my next port of call after changing the recovery back to stock.
fixed it i was just being foolish, someone delete this thread it is of no use.
Can you explain how you fixed it? I too have deleted the recovery in an attempt to flash twrp, but now neither twrp nor the stock recovery are there?
Tapatalk'd from my Twisted, Racing Nexus 5
Ahh, hind sight is a wonderful thing.
After trying to use kingroot to get root access, it failed. And a few days later after rebooting.
I'm now stuck at bootup with Start Up Failed.
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
I've now tried lot's of different things, over the last few hours.
RSDLite (show device brings no thing up)
Unlock bootloader (request key, but error regarding OEM unlock not being set - no access to now set it LOL)
Downloaded stock X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip, and tried using various guides on fastboot but keep getting remote failed.
I'm on stock recovery (obviously still locked).
Any thoughts, or hope from anyone?
Obviously, not sure what support Motorola would provide for what is essentially my own fault?
Have you tried manually flashing each bit of the stock firmware/image. That might help. There's a good guide here which I followed to unbrick my device. Just follow the instructions http://theunlockr.com/2015/09/22/how-to-unroot-the-motorola-moto-x-play/
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
sharebubbles said:
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
Click to expand...
Click to collapse
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
DTLblaze said:
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
Click to expand...
Click to collapse
I run the unlock command, with my unique key but I get ..
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.013s
And since I can't get into the phone, I can't therefore check the "allow OEM unclock"
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
DTLblaze said:
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
Click to expand...
Click to collapse
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Sickaxis79 said:
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Click to expand...
Click to collapse
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
sharebubbles said:
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Click to expand...
Click to collapse
That really does sound like you bricked the device. If you where on lollipop software you wouldn't have the issue with check bootloader OEM unlock. If it was me I would either contact Motorola or go to a repair shop and have a motd experienced person take a look at it.
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
sharebubbles said:
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
Click to expand...
Click to collapse
Strange. This is the tool I used to unlock my bootloader.
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
I've ben used the latest rom so far why trying to flash (and failing) when I look at recovery I have a LPD23.118-10 number that matches to an earlier 5.1.1 rom (I had been upgraded to 6.0.1 via OTA updates) - do I therefore take that LPD ID to mean that I should actually use the 5.1.1 rom - I'm in the UK, so I'm assuming I'd use the UK one rather than Europe (I'm looking at roms on https://github.com/motoxplay/stock).
Thanks
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
And also never try kingroot.
sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
Most in the threads suggesting using rsdlite or manual flash/root and you decided to use kingroot,haha.
Welcome back.
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
---------- Post added at 05:26 AM ---------- Previous post was at 05:14 AM ----------
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
Tried restoring it, deleted everything and the phone is still on bootloader (LOCKED) and i dont even know how to fix it, I know nothing on how to root, friend suggested it, downloaded it, installed it, didnt work and then i restarted my phone and now its stuck on bootloader screen and the screen has the message "Start up failed: your device didnt start up successfully. Use the software repair assisstant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant." <- Downloaded it, tried it and it was stuck on 6% on repairing, left it over night and it was still on 6%.
ALSO under the message "AP Fastboot Flash Mode(Secure) is there)
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
pravin kkr said:
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
Click to expand...
Click to collapse
Download and flash this firmware
https://mega.nz/#!H5YlDCrD!T8tAAW7nHVS-erizRiqg5-Yp_p23hKParMjjHD4diQA credits @kumeipark
Use RSD lite to flash the firmware
http://rsdlite.com/rsd-lite-download/
Moto drivers
http://motorola-mobility-en-in.custhelp.com/app/answers/detail/a_id/88481
If you have problems installing device drivers using Windows 8.1 or Windows 10 follow this guide
https://www.youtube.com/watch?v=gmw86KplqmU
And don't post your contact no. in public forums for everyone to see.
what is the decryption key for the mega link
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
provide the decryption key
My bootloader is off the rocker right know and I can't seem to get anything done.
Cant access recovery, multiple bootloops, etc. EVEN after flashing stock images from the Dump thread.
Now I cant even do that because nothing wants to flash to the partitions, e.g.
Code:
FAILED (remote: Error flashing partition.)
Code:
c:\tools>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.000s
I'm at a loss here, is there anyway I can fix this?
Thanks guys
jAm-0 said:
My bootloader is off the rocker right know and I can't seem to get anything done.
Cant access recovery, multiple bootloops, etc. EVEN after flashing stock images from the Dump thread.
Now I cant even do that because nothing wants to flash to the partitions, e.g.
I'm at a loss here, is there anyway I can fix this?
Thanks guys
Click to expand...
Click to collapse
I'm sure you've already tried this but, what about the other USB ports? I had this very same issue and it took me about an hour to get my phone to recognize "fastboot -w" again.
If I recall correctly, I had to power off the PC and phone, then downgraded my Minimal ADB and Fastboot and everything started working again surprisingly, commands were recognized and I could wipe and flash with no issues.
Welcome to the club. There are a few of us now. I had this happen when trying to flash TWRP after installing the 8.1 beta. AFAIK there's nothing you can do. I've tried every combination of USB port, cable and OS. Its either a hardware error or somethings ****ed with the bootloader. Essential isn't claiming any responsibility and its just offering a $200 out of warranty replacement to US customers.
I was asked yesterday to install LineageOS on someone's phone. It's been a few years, and I screwed some stuff up and now I need help. I'll go through what I did first and then I'll go through my current problems.
Enabled USB debugging and OEM unlock in the phone's settings.
Used ADB to reboot ot bootloader (adb reboot bootloader)
Verified the device's existence with adb.
Used Motorola's website to unlock the phone's bootloader. Process went fine.
Restarted the phone. Got the message that the bootloader was unlocked.
Went back to developer settings to re-enable USB debugging.
Rebooted to fastboot.
Typed in "fastboot flash boot twrp.img" (the file name was longer, but I'll abbreviate for the sake of brevity).
Wiped data.
Formatted data
Now, this is where the problems started. With the data formatted, I couldn't sideload anything, mounting didn't work, and the TWRP file manager showed literally nothing on the phone. No file system or anything, it looked like. This was done on a Linux computer (which also turned two of my MicroSD cards into read only. Thanks Fedora.
Anyway, I figured I should go back to fastboot to fix things. This was probably a mistake, because now I can't do anything. I can't flash TWRP, I can't boot into it, nothing. For example, when I type in
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
I get this:
(bootloader) is-logical:recovery: not found
Sending 'recovery' (27096 KB) OKAY [ 0.802s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
I Googled around. Some people said I might need to flash partitions from gpt.bin, but that didn't work either. Every time, I get "invalid partition name xxx."
What can I do?
Thanks you in advance.