I had previously rooted my Moto G4 Plus and used multiple custom ROMs before switching back to Stock firmware.
Now, I'm unable to flash TWRP on my device. Any attempts to flash TWRP ends up with the following error:
Code:
reboot bootloader
mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12530 KB)...
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.608s
Any further tries to reboot via adb commands results in the following:
Code:
adb reboot recovery
error: device not found
adb reboot
error: device not found
adb reboot bootloader
error: device not found
The device says the bootloader is unlocked while rebooting. the ID field shows 'bad key'(I feel this is weird).
Can someone please help me with this?
Thanks
unknown_geek said:
I had previously rooted my Moto G4 Plus and used multiple custom ROMs before switching back to Stock firmware.
Now, I'm unable to flash TWRP on my device. Any attempts to flash TWRP ends up with the following error:
Code:
reboot bootloader
mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12530 KB)...
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.608s
Any further tries to reboot via adb commands results in the following:
Code:
adb reboot recovery
error: device not found
adb reboot
error: device not found
adb reboot bootloader
error: device not found
The device says the bootloader is unlocked while rebooting. the ID field shows 'bad key'(I feel this is weird).
Can someone please help me with this?
Thanks
Click to expand...
Click to collapse
It has got flashed correctly as you got "OKAY" at end of command. Try to boot into recovery and tell us what happens.
1) That TWRP message of 'Image not signed or corrupt' is normal, since the TWRP custom recovery is not signed. After you see the [OKAY], reboot to recovery directly to fix the TWRP, else the stock recovery will overwrite it. Afterwards, you can boot as normal.
2)If you're still in the bootloader on your device, adb commands do not work - you need to use fastboot commands, or use your device volume keys to select 'Start' (to boot to system) or 'Recovery mode' (to boot to recovery) and press the power key to select. Of course, in this case, after flashing TWRP, you'll want to select 'Recovery Mode' in your bootloader and press the power key. This should then boot into TWRP.
If you find yourself in the bootloader in the future, then 'fastboot reboot' or 'fastboot continue' (both commands to be used without quotes, in the ADB terminal) may get your device rebooting to system.
3)ID Bad key is normal with an unlocked bootloader, on subsequent boots this may change to ID:N/A
echo92 said:
1) That TWRP message of 'Image not signed or corrupt' is normal, since the TWRP custom recovery is not signed. After you see the [OKAY], reboot to recovery directly to fix the TWRP, else the stock recovery will overwrite it. Afterwards, you can boot as normal.
2)If you're still in the bootloader on your device, adb commands do not work - you need to use fastboot commands, or use your device volume keys to select 'Start' (to boot to system) or 'Recovery mode' (to boot to recovery) and press the power key to select. Of course, in this case, after flashing TWRP, you'll want to select 'Recovery Mode' in your bootloader and press the power key. This should then boot into TWRP.
If you find yourself in the bootloader in the future, then 'fastboot reboot' or 'fastboot continue' (both commands to be used without quotes, in the ADB terminal) may get your device rebooting to system.
3)ID Bad key is normal with an unlocked bootloader, on subsequent boots this may change to ID:N/A
Click to expand...
Click to collapse
Hi @echo92,
Thanks for pointing out what I was doing wrong. I now realize that the TWRP recovery was being overwritten by stock recovery and I didn't know adb commands don't work while still in bootloader mode.
I did boot into recovery mode from the bootloader (using the volume buttons from the phone) and it worked.
And the ID: bad key is also gone and now it shows ID: N/A.
Thanks again for your help!
Regards
____Mdd said:
It has got flashed correctly as you got "OKAY" at end of command. Try to boot into recovery and tell us what happens.
Click to expand...
Click to collapse
Hi @____Mdd,
I rebooted into recovery right after flashing TWRP and it worked fine. Now, I'm able to boot into TWRP recovery.
Thanks for your response.
Regards.
Im Facing this issue while flashing TWRP
C:\adb>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (12644 KB) OKAY [ 0.422s]
Writing 'recovery' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
vaibhavhr2010 said:
Im Facing this issue while flashing TWRP
Click to expand...
Click to collapse
Pre flash validation errors suggest that your bootloader is locked (i.e. you have not unlocked your bootloader, or it has been re locked). Can you confirm your bootloader is unlocked, e.g. if there is a warning screen on boot saying your device is unlocked?
echo92 said:
Pre flash validation errors suggest that your bootloader is locked (i.e. you have not unlocked your bootloader, or it has been re locked). Can you confirm your bootloader is unlocked, e.g. if there is a warning screen on boot saying your device is unlocked?
Click to expand...
Click to collapse
Thank You for the Reply!
Yes I have already unlocked the Bootloader.
The device status in Bootloader shows Device is Unlocked, Status Code: 3
vaibhavhr2010 said:
Thank You for the Reply!
Yes I have already unlocked the Bootloader.
The device status in Bootloader shows Device is Unlocked, Status Code: 3
Click to expand...
Click to collapse
Thanks, what device are you trying to flash TWRP to and which TWRP image are you using?
echo92 said:
Thanks, what device are you trying to flash TWRP to and which TWRP image are you using?
Click to expand...
Click to collapse
I'm Flashing my Moto G4 using the twrp-3.0.2-3-titan.
vaibhavhr2010 said:
I'm Flashing my Moto G4 using the twrp-3.0.2-3-titan.
Click to expand...
Click to collapse
That TWRP won't work, if it's for Titan. The codename for Moto G4/plus is athene, only TWRP images specifying athene in their name will work.
https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206 or https://eu.dl.twrp.me/athene/ give these a try instead
Related
Hello and thanks in advance to everyone,
I am trying to root my moto g4 but I am stuck on installing a recovery. I did unlock the bootloader and when I turn on the phone i am greeted with"this device is unlocked and can't be trusted"
Yet when i try to flash the recovery it states that it failed to install since the package is unsigned:
C:\Users\Jelle\Desktop\Nieuwe map>mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12496 KB)...
OKAY [ 0.405s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.344s]
finished. total time: 0.748s
Re-entering my unlock code also does not work as it gives me this message:
C:\Users\Jelle\Desktop\Nieuwe map>fastboot oem unlock NYRTWS*************
...
(bootloader) invalid boot state
OKAY [ -0.000s]
finished. total time: -0.000s
Does someone have any idea on what the issue is, am I missing something?
Thank you in advance!
Twrp is for motog4 plus aka athene. Make sure your device is the same.
Just reboot to recovery after you flash twrp using fast boot. Do not reboot your device to your home screen as your recovery partition will be rewritten with the stock recovery.
Do not worry about the message. It doesn't say that flashing failed. It only gives you a warning that it's not signed. That message is displayed even if you flash the stock recovery using fast boot.
Sent from my Moto G (4) using Tapatalk
Silesh.Nair said:
Twrp is for motog4 plus aka athene. Make sure your device is the same.
Just reboot to recovery after you flash twrp using fast boot. Do not reboot your device to your home screen as your recovery partition will be rewritten with the stock recovery.
Do not worry about the message. It doesn't say that flashing failed. It only gives you a warning that it's not signed. That message is displayed even if you flash the stock recovery using fast boot.
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
that totally worked! thank you very much
same problem mentioned above but after recovery mode my devicxe says no command.
help mw plzzz
sauravchandela95 said:
same problem mentioned above but after recovery mode my devicxe says no command.
help mw plzzz
Click to expand...
Click to collapse
If you're getting a screen with 'no command', that's the stock recovery on your device.
Are you rebooting to the recovery straight after flashing TWRP? Do you have an unlocked bootloader and what version of TWRP are you flashing? What commands are you using to flash?
You may wish to try booting with TWRP first:
1)On a device with an unlocked bootloader, boot to the bootloader screen.
2)Connect your device to your computer via a high quality USB data cable or the original USB cable.
3)Ensure your TWRP image is copied to your ADB folder.
4)Open an ADB terminal. Verify your device is communicating with your computer by typing 'fastboot devices' without quotes. Press Enter. You should get a serial number response.
5)If so, then type 'fastboot boot twrp.img' without quotes. Replace twrp.img with the actual full file name of your TWRP image in your ADB folder including the file extension. For example, if your TWRP image file name is shreps_twrp_3_1_1.img, the full command would be fastboot boot shreps_twrp_3_1_1.img You can type the first few letters of the file name and press Tab on your keyboard to automatically complete the file name if you so wish.
6)Press Enter, and your device should download TWRP and boot to TWRP.
For the last week I have been trying to root and install TWRP on my Huawei p8 Lite ALE21. Sofar every attempt has failed.
Steps taken:
Get Bootloader Code
Unlock bootloader with "fastboot oem unlock"
Flash TWRP with "fastboot flash recovery recovery.img"
Result:
When booting into recovery the default "Huawei eRecovery" opens, not TWRP
No app can detect root
Additional info:
TWRP form here: http://forum.xda-developers.com/p8lite/development/testing-twrp-2-8-7-x-huawei-p8lite-qcom-t3187758
Trying to debug the problem, I entered
Code:
fastboot getvar all
this returned
Code:
getvar:all FAILED (remote: Command not allowed)
Additional I have tried to downgrade to android 5.0 again, but after copying the Firmware to the "dload" folder and holding the Volume-Up and Down and Power buttons, the phone wouldn't do anything but show the huawei logo and turn off.
Any help would be very appreciated!
Thank you in advance,
Oisin
Oisins said:
For the last week I have been trying to root and install TWRP on my Huawei p8 Lite ALE21. Sofar every attempt has failed.
Steps taken:
Get Bootloader Code
Unlock bootloader with "fastboot oem unlock"
Flash TWRP with "fastboot flash recovery recovery.img"
Result:
When booting into recovery the default "Huawei eRecovery" opens, not TWRP
No app can detect root
Additional info:
TWRP form here: http://forum.xda-developers.com/p8lite/development/testing-twrp-2-8-7-x-huawei-p8lite-qcom-t3187758
Trying to debug the problem, I entered
Code:
fastboot getvar all
this returned
Code:
getvar:all FAILED (remote: Command not allowed)
Additional I have tried to downgrade to android 5.0 again, but after copying the Firmware to the "dload" folder and holding the Volume-Up and Down and Power buttons, the phone wouldn't do anything but show the huawei logo and turn off.
Any help would be very appreciated!
Thank you in advance,
Oisin
Click to expand...
Click to collapse
In order to boot in twrp recovery you should first remove your usb cable,once is done,press and hold volume up and power button,once you see huawei logo,release power button but keep press on volume up,about firmware witch build number do you have on your phone,share more info if you want a quick help
"No app can detect root"
TWRP isn't root
"fastboot flash recovery recovery.img"
Any error?
"....(remote: Command not allowed)"
i think you have to unlock bootloader
Thank you for you quick response!
Running "fastboot flash recovery recovery.img" returns
Code:
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.880s]
writing 'recovery'...
OKAY [ 2.084s]
finished. total time: 2.967s
I checked if the bootloader is unlocked with "fastboot oem get-bootinfo"
Code:
(bootloader) unlocked
OKAY [ 0.003s]
finished. total time: 0.003s
I also tried booting into recovery without the cable plugged it, but it still just booted into "eRocovery"
More info
Product: ALE-L21
Serial: W3D4C16916992523
Build: ALE-L21C432BB574
just try this:
1) (re) boot normally
2) attach to pc with usb cable
3) reboot into recovery using adb command: adb reboot recovery
ItalianWolf said:
just try this:
1) (re) boot normally
2) attach to pc with usb cable
3) reboot into recovery using adb command: adb reboot recovery
Click to expand...
Click to collapse
The phone reboots, shows the HUAWEI logo and then turn off again.
Sorry, i didn't read the post linked.
You need twrp 3.0.2 for B5xx, i was thinking you had the right one (2.8.7 works on kk and maybe lollipop), so here you are: http://forum.xda-developers.com/p8lite/general/twrp-3-0-0-0-p8-lite-kirin-t3343320
ItalianWolf said:
Sorry, i didn't read the post linked.
You need twrp 3.0.2 for B5xx, i was thinking you had the right one (2.8.7 works on kk and maybe lollipop), so here you are: http://forum.xda-developers.com/p8lite/general/twrp-3-0-0-0-p8-lite-kirin-t3343320
Click to expand...
Click to collapse
It worked! Thank you very very much! I spend sooo much time on this... wow thanks!
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
frohro said:
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
Click to expand...
Click to collapse
How are you trying to boot into download mode, are you trying to do it via fastboot or the hardware buttons?
frohro said:
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
Click to expand...
Click to collapse
im having the same problem, i dont have download more or twrp now, all i have is fastboot
i am going to assume going into download mode through fastboot is the only option for the two people posting for help here. from what i see from the posts, both hardware buttons sequence , or the plug in & down volume are the ONLY way to get to fast boot.
and fast boot is the only thing available on the phone.
i have labeled that a soft brick .
i asume one of the two help seekers have used the magisk 20.2 trap?
the release proved to be a problem , there is a tutorial on how to fix it.
i will go look for that and try to edit it into my responce later.
for now, are the two seekers already acomplished in this procedure?
TWRP Installation Tutorial for Linux Mint and Ubuntu users ยป AndroidGuru.eu
TWRP (Team Win Recovery Project) is an open-source custom recovery image for Android devices. It is a replacement for the stock recovery mode that is installed on most Android devices by the manufacturer. TWRP provides various advanced features and options that are not available in the stock...
www.androidguru.eu
20.2 problem notes and fix
Magisk 20.2 Kills LG V20 (All variants) Boot partition. Reverting to 20.1 fixes issue
So over in the LG V20 forum a lot of people are finding out that installing Magisk 20.2 throws the phone into Fastboot mode. https://forum.xda-developers.com/v20/help/direct-installing-magisk-update-wiped-t4028705...
forum.xda-developers.com
frohro said:
Hi All,
I just followed the instructions to root my h918 and then successfully updated to h91820h. I then used the TWRP app to flash twrp, and the Magisk app to update Magisk. After that I rebooted from the Magisk app, and now my phone is stuck in a bootloop. I cannot get into download mode, or recovery mode, or the system. I can get into fastboot mode by trying to go into download mode (holding the volume down and plugginto a USB port ot the laptop.
It seems that T-mobile removed any commands from fastboot that will help me. If I try to "fastboot reboot emergency", it just bootloops. If I try fastboot boot a twrp image, I get:
Code:
fastboot boot twrp-3.4.0-1-h918.img
downloading 'boot.img'...
OKAY [ 0.667s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.686s
The command "fastboot reboot bootloader" boots to fastboot. The bootloader is indeed unlocked, but it looks like I'm stuck, because the LG fastboot doesn't allow anything to fix the brick.
Code:
$ fastboot getvar unlocked
unlocked: yes
finished. total time: 0.020s
I'm not finding any hope or help on Google. It seems if I can't boot into twrp or download mode, I'm toast, and I can't figure out how to boot into anything but the bootloader.
Does anyone have any suggestions on how to bring this phone back from the dead?
Thanks,
Rob
Click to expand...
Click to collapse
ok i found a way to get into twrp (if ever installed)
1- turn off your phone
2- hold Volume Down + Power button until you see the LG logo
3- When you see the Logo release the power button while still holding the volume down and immediately after release press power button 3 times.
4- you will see a factory reset screen, press yes twice and it will go to twrp.
NOW WE NEED TO FIND A WAY TO FLASH A WORKING ROM THRU TWRP
My main rooted v20 phone got bumped and now is stuck in a bootloop. I can enter fastboot (some commands working) but can't access TWRP recovery using either VOL + UP and USB cable or VOL DOWN + POWER. I believe the phone is on 10j or 10k if I remember correctly. Bootloader and carrier are unlocked.
Is there a way to just reflash TWRP safely and attempt data recovery and ROM installation without factory reset?
My goal is to attempt recovery first. If that is not an option, I would like to flash to 10p so I can start the rooting process using Lafsploit.
DirtyBreakz said:
My main rooted v20 phone got bumped and now is stuck in a bootloop. I can enter fastboot (some commands working) but can't access TWRP recovery using either VOL + UP and USB cable or VOL DOWN + POWER. I believe the phone is on 10j or 10k if I remember correctly. Bootloader and carrier are unlocked.
Is there a way to just reflash TWRP safely and attempt data recovery and ROM installation without factory reset?
My goal is to attempt recovery first. If that is not an option, I would like to flash to 10p so I can start the rooting process using Lafsploit.
Click to expand...
Click to collapse
Sure, to flash twrp in fastboot mode you do this.
Download latest twrp
With the phone off hold vol down plug USB into phone and computer.
type on your computer:
fastboot flash recovery twrp-3.6.2_9-0-h918.img
fastbboot reboot
take battery out
put back in
go into twrp by doing a factory reset. How to factory reset the Lgv20
U
Darnrain1 said:
Sure, to flash twrp in fastboot mode you do this.
Download latest twrp
With the phone off hold vol down plug USB into phone and computer.
type on your computer:
fastboot flash recovery twrp-3.6.2_9-0-h918.img
fastbboot reboot
take battery out
put back in
go into twrp by doing a factory reset. How to factory reset the Lgv20
Click to expand...
Click to collapse
Unfortunately no joy. I tried fastboot boot and flash commands and even tried renaming the img file. I tried with 3 different versions of twrp. This was the result:
PS C:\Users\User\NexusTools> fastboot boot twrp-3.6.2_9-0-h918.img
Sending 'boot.img' (24948 KB) OKAY [ 0.771s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
PS C:\Users\User\NexusTools> fastboot flash recovery twrp.img
Sending 'recovery' (23512 KB) OKAY [ 0.854s]
Writing 'recovery' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
I've searched the forums and internet for hours and not coming up with anything. Any other ideas?
Just a note when trying to cold boot to twrp using 'UP VOLUME + CONNECT USB' that the screen flashes download mode for a split second and then reboots.
DirtyBreakz said:
U
Unfortunately no joy. I tried fastboot boot and flash commands and even tried renaming the img file. I tried with 3 different versions of twrp. This was the result:
I've searched the forums and internet for hours and not coming up with anything. Any other ideas?
Just a note when trying to cold boot to twrp using 'UP VOLUME + CONNECT USB' that the screen flashes download mode for a split second and then reboots.
Click to expand...
Click to collapse
That's so odd I have never seen this issue before.
You can try flashing the twrp image to the boot partition.
fastboot flash boot twrp.img
fastboot reboot
Should boot rite into twrp then because the twrp image is on the boot partition. Sounds to be like there may be a hardware problem with this phone.
Darnrain1 said:
That's so odd I have never seen this issue before.
You can try flashing the twrp image to the boot partition.
fastboot flash boot twrp.img
fastboot reboot
Should boot rite into twrp then because the twrp image is on the boot partition. Sounds to be like there may be a hardware problem with this phone.
Click to expand...
Click to collapse
Well unfortunately the flash boot command failed also. I'm guessing because it shows the boot partition size is 0. Any possible way around this?
I'm hoping not but I think you might be right about a possible hardware issue...
PS C:\Users\User\NexusTools> fastboot flash boot twrp.img
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 24076288).
Sending 'boot' (23512 KB) OKAY [ 0.817s]
Writing 'boot' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
DirtyBreakz said:
Well unfortunately the flash boot command failed also. I'm guessing because it shows the boot partition size is 0. Any possible way around this?
Click to expand...
Click to collapse
I think it's a hardware issue with the ram. I cant think of anything else.
Do a search online for the error message.
Writing 'boot' FAILED (remote: 'unknown command')
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.