Database Users

Huawei Software installing Loop!

Hey, i tried to install the android 6.0 beta from this forum, but i was rooted, now its stuck in a loop where it turns off, turns on and tries to install it and fails at 0%, and again. I can enter Fastboot/rescue mode and thats it. I tried to flash recovery boot and system.img in adb and fastboot, but it shows this:
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 1.265s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.265s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.858s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.874s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash system.img
unknown partition 'SYSTEM.img'
error: cannot determine image filename for 'SYSTEM.im
C:\Program Files\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 471859200 bytes
Help pls. I tried everything...

System.img flash failed after 2 mins now too. Still no idea.

Looks like you've used the KingRoot method to root your phone.
Flashing via fastboot requires the fastboot to be unlocked.
The message "FAILED (remote: Command not allowed)" indicates, that the script tried to execute the command, but because the bootloader is still locked, it cannot do such thing.
There are 2 solutions:
Download the original firmware and try to update to it via the "dload" method. (sdCard>dload>UPDATE.APP)
Try to unlock the bootloader. But for unlocking, you'll need the Product ID, which as of now, only obtainable, when the phone is able to boot up.
I really recommend trying to download the firmware, and give the "dload" method a shot, because without an unlocked bootloader, nothing you can do at home.
Right, it's almost nothing. There's this site called DC-Unlocker, and with a fast runthrough, it should be able to unlock the bootloader, but I haven't tried, or tested it in any way. Still an interesting program, though.
Edit:
Just saw your post under the other similar topic.
You should try to do a Factory Reset, by hand, via fastboot, and then updating with the "dload" method again.
The commands are:
fastboot erase cache
fastboot erase userdata
Maybe this helps.

daviddosa said:
Looks like you've used the KingRoot method to root your phone.
Flashing via fastboot requires the fastboot to be unlocked.
The message "FAILED (remote: Command not allowed)" indicates, that the script tried to execute the command, but because the bootloader is still locked, it cannot do such thing.
There are 2 solutions:
Download the original firmware and try to update to it via the "dload" method. (sdCard>dload>UPDATE.APP)
Try to unlock the bootloader. But for unlocking, you'll need the Product ID, which as of now, only obtainable, when the phone is able to boot up.
I really recommend trying to download the firmware, and give the "dload" method a shot, because without an unlocked bootloader, nothing you can do at home.
Right, it's almost nothing. There's this site called DC-Unlocker, and with a fast runthrough, it should be able to unlock the bootloader, but I haven't tried, or tested it in any way. Still an interesting program, though.
Click to expand...
Click to collapse
Ive got all the informations for getting the bootloader unlock code, but when i type it in the thing by huawei to get the unlock code it tells me that its wrong... I could get it here if you could help me with it?

Hello,
I'd like to request a bootloader unlock code for my Huawei device
Information:
Product: HUAWEI ALE-L21
SN:
IMEI:Nvm
Product IDups.
Thank you!
So, this is the e-mail i sent to Huawei, they couldnt help me. Everything here is directly from the phone itself, so i dont think its wrong.

With the Product ID, you can get the code, but the details above are wrong, more precisely one of them, which is the Phone Name
Try it without the HUAWEI, it should look like this: "ALE-L21" (without the " of course).
If it somehow would not work for you, I sent you a PM with your unlock code in it.
Note: I recommend not to publish your information like this. The phone is blockable with the IMEI remotely by the service providers or the police. Please remove them for your own safety.

Tried the update again, now flashing doesnt even work.

Blasted kingroot - bricked my phone?

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

[GUIDE] Update with fastboot

Guide for installing new security update with fastboot and with a bootloader-unlocked Pixel XL.
This is basically the same thing as usual but with the new structure.
If you have modified a little the stock android (hosts file, root, kernel, etc.), you may experience a fail in OTA update;
If you have a bootloop/soft brick/not sure of the state of your android system;
This is the solution.
This WILL NOT delete your data and apps. This will remove your custom kernel/root/hosts/recovery through (which is a good thing because it will be clean then).
I assume you already have anything to do fastboot command. If not, see this good thread.
1) Download your system image for Marlin (Pixel XL) on google website.
For November update, there are 3 versions:
NDE63U Europe
NDE63V US, except Verizon
NDE63X Verizon
2) Unzip the file marlin-nde63v-factory-a66866ba.zip
3) Unzip inside the new directory (marlin-nde63v) the image-marlin-nde63v.zip
4) Reboot into bootloader
Code:
adb reboot bootloader
5) Execute fastboot commands (assuming the bin is on your PATH)
Code:
fastboot flash bootloader bootloader-marlin-*.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
Here we go, you have a fresh unrooted vanilla android with latest security patch.
6) To add TWRP and Root:
Code:
fastboot boot /path/to/twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip
Root thread for more information.
TWRP thread for more information.

** Reserved **

cam30era said:
@firewave,
Thanks for posting the guide. Just like Nexus devices except for the slot files. After unzipping the factory image, I do notice 15 additional files (other than boot, system, vendor, etc) that I've never seen before on a Nexus device. Do you happen to know what those are for, and why we don't flash them if doing a manual fastboot flash?
Thanks, in advance....
Click to expand...
Click to collapse
Other files are more for complete reset. There are for example, time-zones data, default crypto key, default /sdcard, bootlocker state, etc.
Only aboot.img is obscure for me. I'm at work so I can't dig into it, but I updated my pixel xl without issue that way.
I'm also add EX kernel and root again without issue.

firewave said:
Other files are more for complete reset. There are for example, time-zones data, default crypto key, default /sdcard, bootlocker state, etc.
Only aboot.img is obscure for me. I'm at work so I can't dig into it, but I updated my pixel xl without issue that way.
I'm also add EX kernel and root again without issue.
Click to expand...
Click to collapse
aboot is actually part of the bootloader.

death2all110 said:
aboot is actually part of the bootloader.
Click to expand...
Click to collapse
yep, it's why I'm unsure what to do with. Probably nothing.
I will loopmount the file at home and see.

Will this FDR the phone or just apply the update? I am currently on a Verizon Pixel XL Rooted/Unlocked and on the P build. Thanks for any information.

wx9kvh said:
Will this FDR the phone or just apply the update? I am currently on a Verizon Pixel XL Rooted/Unlocked and on the P build. Thanks for any information.
Click to expand...
Click to collapse
In the op in bold, he said it will not erase your data or apps

C:\android>fastboot flash bootloader bootloader-marlin-*.img
error: cannot load 'bootloader-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.105s
C:\android>fastboot flash radio radio-marlin-*.img
< waiting for any device >
error: cannot load 'radio-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.048s
C:\android>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (26405 KB)...
FAILED (command write failed (No error))
finished. total time: 0.001s
C:\android>fastboot flash system system.img
< waiting for any device >
target reported max download size of 536870912 bytes
I am getting the above error but it proceeds to do all other commands. Then I get hung up at the Google screen. Any suggestions? I can get into the bootloader. I've tried the fastboot commands twice now...same result

dablitzkrieg said:
C:\android>fastboot flash bootloader bootloader-marlin-*.img
error: cannot load 'bootloader-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.105s
C:\android>fastboot flash radio radio-marlin-*.img
< waiting for any device >
error: cannot load 'radio-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.048s
C:\android>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (26405 KB)...
FAILED (command write failed (No error))
finished. total time: 0.001s
C:\android>fastboot flash system system.img
< waiting for any device >
target reported max download size of 536870912 bytes
I am getting the above error but it proceeds to do all other commands. Then I get hung up at the Google screen. Any suggestions? I can get into the bootloader. I've tried the fastboot commands twice now...same result
Click to expand...
Click to collapse
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.

chapelfreak said:
In the op in bold, he said it will not erase your data or apps
Click to expand...
Click to collapse
That was not in the original post. I screenshot the OP, the part about adding a kernel or custom ROM at the bottom was also added. But thanks for the update.

wx9kvh said:
That was not in the original post. I screenshot the OP, the part about adding a kernel or custom ROM at the bottom was also added. But thanks for the update.
Click to expand...
Click to collapse
That makes sense, our posts are an hour apart or so.

Scott said:
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.
Click to expand...
Click to collapse
I appreciate the help. The link you provided me, I've downloaded it, but for some reason cant launch the app after I unzip the file. I've been at this for like 4 hours. I've tried so many different things and can't get past the Google screen. Please help

I was able to utilize the old tool. I'm all set. Thanks

chapelfreak said:
That makes sense, our posts are an hour apart or so.
Click to expand...
Click to collapse
Lol. No big deal haha.

Scott said:
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.
Click to expand...
Click to collapse
Scott...can I flash the radio.img from V to the Verizon X. This radio is horrible

ADB Sideload Works too
Alternatively, use the instructions found on this page followed by a re-flash of your preferred kernel and a fastboot boottoroot to regain root.
https://developers.google.com/android/nexus/ota

So i just followed all of these instructions, and when going into about phone, it shows that i am now on an N build and still with the October security patch. What did i miss?
Update :
I believe I fixed the issue. The little window with the commands in it for some reason had scrolled up and I missed the flashing the "bootloader-marlin-*" step.
Update 2 :
I am now on X with the November security update. GREAT GUIDE!

Followed it to a T and soft bricked mine so now trying to find a way to fix or toss it out the windows haha. Just a heads up guys.
Ended up using the skipsoft tool and pushing a factory update same results but lost data/apps no biggie.

This is odd i followed the instructions trying to flash X to my phone coming from NDE63P and somehow ended up on NDE63N (Ignore this i missed a command)

What steps do I need to add if I want to completely restore back to factory settings (format userdata)? Or would it be the same to just factory reset through the newly restored stock recovery?

Yet Another Bootloop Thread

Hello,
So I decided to unlock and root my Pure today. Originally I was going to flash Lineage, but I later decided not to. Anyway, I was following the instructions here.
So I unlocked and installed TWRP succesfully. Then I decided to root. And that's where I screwed up.
Following these instructions, I now have a phone that won't boot past the "M" logo. Apparently my mistake was not using the current SU version.
I have been Googling for an hour now, but almost every solution I've come across has involved plugging the phone into the computer. My issue is that my computer isn't recognizing the phone when I plug it in, so my knowledge of how to fix this is limited (and my expertise in this topic was minimal to begin with...). I can get to recovery mode, and have tried a factory reset. No dice. I also put the latest official factory image from Motorola on the SD card, but when I went to install it, it wouldn't show up.
As you can tell I am quite stuck here. I haven't tried to root a phone since my Incredible back in the day. Any help would be greatly appreciated.
Thanks!

Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.

jason2678 said:
Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.
Click to expand...
Click to collapse
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?

bootloopohgod said:
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?
Click to expand...
Click to collapse
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps

Sagar_1401 said:
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps
Click to expand...
Click to collapse
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.

bootloopohgod said:
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.
Click to expand...
Click to collapse
ignore that partition error
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
make sure
while flashing NON-HLOS.bin you might get error
dont worry
when you reach that step do type it again when you see that error and it'll successful flash the NON-HLOS.bin which is your main step for your modem
im sure this will 100% work
edit: all the files have different no of system system.img_sparsechunk
if you are flashin sept patch it should have 8 i assume but if you just type system system.img_sparsechunk.9 it'll say file not found u won't encounter any error by that

[HELP] Z00TD/ZE551KL soft-bricked? No recovery mode, no OS, locked bootloader.

Hey guys, I need help with this Asus Zenfone 2 Laser that:
Cannot boot to any OS (asus logo pops up, freezes, and then a blue screen flashes for a really short period, before it powers off, see video here.)
Can't download the unlock app to unlock bootloader
Can't access ADB
Cannot access Recovery mode
Can't "factory reset", apply update over ADB, etc.
Bootloader is locked
Can't flash custom recovery, boot TWRP, or really anything...
See fastboot reference below for more info
Code:
$ fastboot boot twrp-3.7.0_9-0-Z00T.img
Sending 'boot.img' (31066 KB) OKAY [ 0.987s]
Booting FAILED (remote: 'unlock device to use this command')
fastboot: error: Command failed
$ fastboot flash recovery twrp-3.7.0_9-0-Z00T.img
Sending 'recovery' (31066 KB) OKAY [ 0.987s]
Writing 'recovery' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flash boot boot.img # (Original boot.img from factory image)
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 17980722).
Sending 'boot' (17559 KB) OKAY [ 1.478s]
Writing 'boot' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
$ fastboot oem device-info
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.003s]
Finished. Total time: 0.003s
As someone who has only worked with Google Pixel phones in the past, I'm very frustrated for a few reasons.
Firstly, why the hell is the ONLY WAY to unlock a bootloader through an app that was released in such a clandestine, under-the-table way?
Second, why is the manufacturer gatekeeping the recovery files? The only way I was able to find the stock recovery.img is through a comment on a Reddit post (ironically posted by an ASUS Employee).
Third, I've been scouring the internet for many, many days trying to find any kind of emergency recovery method, but every single tutorial acts on the assumption that the bootloader is unlocked, and that boot.img, recovery.img, etc. can be flashed.
Enough about the frustration. Now let's talk about what I've tried so far.
I tried ASUS Flash Tool (Finding ADB drivers was a whole different fiasco for this device), and came up empty handed, as it doesn't detect the device when in fastboot mode.
I tried using fastboot to flash boot, recovery, system, fastboot, and dnx/ifwi, to no avail.
I tried booting into recovery via `fastboot reboot recovery`, `fastboot reboot-recovery`, `fastboot oem reboot-recovery`, and by holding Vol Down while booting up. They all give the same result, which is just an instant (<1 second) reboot. My best guess is that recovery.img is either missing or badly corrupt, so the bootloader just gives up and exits immediately.
Please help. I don't want an expensive paperweight sitting in my drawer just because of a bootloop that wasn't my fault (seriously this device just bootlooped itself one day, I didn't flash a custom rom, root or anything like that).
Any help is appreciated,
Thanks in advance

you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417

alecxs said:
you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417
Click to expand...
Click to collapse
Probably a dumb question, but how can I put my device into EDL mode?
I've tried many key combinations in conjunction with plugging it into the computer, and I've tried connecting it without a battery.

if nothing else works you need to figure out test points
https://forum.xda-developers.com/t/...ed-to-unlock-bootloader.4531349/post-87944673

you still have fastboot? try this for EDL mode.
Code:
fastboot oem enter-dload

Good news and bad news. Good news is: I was able to enter EDL mode.
Bad news is, apparently my entire partition scheme was messed up, and upon running "edl w gpt gptboth0.bin", fastboot no longer works.
I have tried flashing aboot using edl ("edl w aboot emmc_appsboot.mbn") and it's not working.
Not to mention that it is almost impossible to find the firmware file with all the factory files such as "emmc_appsboot.mbn". The place where I got my file seemed very sketchy and I'm not surprised if the reason it's not working is because it's the wrong file.
Once again, this is a result of ASUS gatekeeping their recovery files to service centers to drive up repair sales.
If anyone has a link, or would like to provide a donor file, it would be VERY much appreciated.

what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios

alecxs said:
what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios
Click to expand...
Click to collapse
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...

OS were
sj-dan said:
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...
Click to expand...
Click to collapse
So we're you able to find a fix in any way? I find myself in just about the same situation tho for different reasons. I have a radiant max 5g att device i moronicaly tried to download a gsi using the dsu updater, but forgot to unlock bootloader or even enable USB debugging before attempt. So OS system is crashing an saying 'device corrupted' on boot attempt. Recovery mode gets the same result. Was able to use the bugjaegar app to connect ad run the bootloader but every repair attempt is blocked by the fact the USB debugging isn't on. To make matters worse I accidentky hit boot fastbootd command instead of normal and whatever that did wiped out my ability to even connect with bootloader so I'm kind of stuck.

faisaliteb said:
Mod. edit: spammer gone. alecxs
I found many tutorials about fixing bootloops on the Nexus but they all seem to require an unlocked bootloader.
The bootloader on the device is locked. I can see the device in fastboot devices but I can't unlock it.
Any idea how to repair this? Can I somehow flash a factory image onto the device even though OEM unlock is disabled? There is no data on the device that would need to be preserved. I'm ideally looking for a Linux-based solution. more info... ***
Click to expand...
Click to collapse
Yeah man I've been looking at this problem for over a week now and can't find much online at all to help. Except for this EDLmode some devices can boot into, and apparently you can flash a locked system using this emergency download mode. I dunno still researching.