I can't boot my phone normally and in recovery mode.
I can boot only in fastboot mode. I don't know why it appens...
The problem is that I can't flash radio, system etc. beacuse I have this error
"signature verify fail"
Is there anything that I can do?
Thank you for helping me...
What radio, hboot version is shown on the fastboot screen and what carrier was the phone originally on (ie carrier brand on the phone, this may or may not be your current mobile carrier)
The signature error is an indication of an s=off spl.. but I need more info to tell you the easiest way to proceed.
I have the samve problem,
I had:
fastboot earse system -w
---------------> ok
fastboot earse recovery
---------------> ok
fastboot flash recovery recovery.img
---------------> failed:
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOsignature checki
FAILED (remote: signature verify fail)
Now i only enter to fastboot mode
i think the reason is S-On but i don't know how to change to S-off when i can't enter both system or recovery mode Help me, please!!!!
HBOOT-1.33.0013d
RADIO-2.22.27.08
( sorry if my english is not good ).
i tried : fastboot boot recovery
but it still not work too.
downloading 'boot.img'... OKAY
booting...
Click to expand...
Click to collapse
forever
sunnyboy256 said:
i tried : fastboot boot recovery
but it still not work too.
forever
Click to expand...
Click to collapse
you are on a perfected SPL (1.33.0013d) where you have only a limited number of fastboot commands available. You should look here and read the OP, than you should be able to find a solution for your problem.
Thank you a lot! Sloved!
Related
Error in CACHE: recovery/log (No space left on device) ...
After trying to flashing MTD pathes.... ****.... What i should to do?
I can't falsh any rom now. always had Error in CACHE: recovery/log (No space left on device) ...
try to wipe all, try to fastboot erase system -w...
Always the same result
i can log on Fastboot and Recovery RA 1.7 all fine
****... now i try
fastboot erase recovery
fastboot flash recovery C:/recovery.img
and get
sending 'recovery' <4594kb>... OKAY [ 1.734s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
finished. total time: 3.125
....agrrrrrrrrrrrr
after this reboot in recovery... and logo of my phone i see only... in left upper side of screen line: FASTBOOT USB
after this i try :
fastboot erase recovery
got > erasing 'recovery'....
and stack... about 10 minutes i wait... scary.... what i should to do?
i can power off my phone? (battery)
ANtiHazarD said:
Error in CACHE: recovery/log (No space left on device) ...
After trying to flashing MTD pathes.... ****.... What i should to do?
I can't falsh any rom now. always had Error in CACHE: recovery/log (No space left on device) ...
try to wipe all, try to fastboot erase system -w...
Always the same result
i can log on Fastboot and Recovery RA 1.7 all fine
Click to expand...
Click to collapse
ANtiHazarD said:
****... now i try
fastboot erase recovery
fastboot flash recovery C:/recovery.img
and get
sending 'recovery' <4594kb>... OKAY [ 1.734s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
finished. total time: 3.125
....agrrrrrrrrrrrr
Click to expand...
Click to collapse
ANtiHazarD said:
after this reboot in recovery... and logo of my phone i see only... in left upper side of screen line: FASTBOOT USB
after this i try :
fastboot erase recovery
got > erasing 'recovery'....
and stack... about 10 minutes i wait... scary.... what i should to do?
i can power off my phone? (battery)
Click to expand...
Click to collapse
I had the same thing yesterday happen but before freaking out I left my phone connected to my pc in recovery with the error on the screen and used ADB to flash a new recovery right over the old one and it worked try that. Boot phone into recovery (if you still can after everything you have done) with your phone connected to your PC, open up ADB and flash the recovery file that way.
i can't boot recovery now... when USB connected and when i try to boot recovery i see only first bootscreen (Orange MTN logo)
and in left upper side of screen "FASTBOOT USB"
and that's all....... =(
coz now i don't have any recovery... only HBOOT...
ANtiHazarD said:
i can't boot recovery now... when USB connected and when i try to boot recovery i see only first bootscreen (Orange MTN logo)
and in left upper side of screen "FASTBOOT USB"
and that's all....... =(
Click to expand...
Click to collapse
Anti I am not trying to be mean but thats cause you freaked out when you saw something you never have before instead of taking a breath and asking first.
If you can hold down the back button and power on your phone and get into the fastboot menu you should still be good. you can flash the recovery image from fastboot. Follow the instructions on amons page to do it.
thx... i trying to flash via fastboot... but always got fast line :
FAILED <remote: signature verify fail>
ANtiHazarD said:
thx... i trying to flash via fastboot... but always got fast line :
FAILED <remote: signature verify fail>
Click to expand...
Click to collapse
I dont really use fastboot much, so I cant help you there but you should be able to flash the recovery. try a different recovery, try Cyanogens recovery file. All I do know is it has to be in the tools folder.
okey! thx, now will try!
ANtiHazarD said:
okey! thx, now will try!
Click to expand...
Click to collapse
No Problem, let me know how it turns out.
=(( it's crazy..
can i flash any rom via Fastboot mode???
Any rom! But for NoneDanger SPL...
ANtiHazarD said:
=(( it's crazy..
can i flash any rom via Fastboot mode???
Any rom! But for NoneDanger SPL...
Click to expand...
Click to collapse
Not that I know of. I could be mistaken but that all has to be done through recovery. But maybe somebody else will chime in on the conversation. If fastboot isnt fixing recovery then, I am sorry to say it but you might just be SOL and you might want to see if your phone is under warranty still. haha
So in CMD on windows you are typing this in:
Copy recovery-RA-dream-v1.7.0.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img
and its not working? And you placed the recovery img in the tools folder where your sdk is right.
i don't understand what is it:
Boot your G1 into fastboot mode (boot while holding BACK)
I boot into fastbook like this:
Camera+Power, then press SEND
and i got FASTBOOT USB
it is not right?
and all other steps is right!
fastboot devices :
HT94XNG01269
than :
fastboot flash recovery recovery-RA-dream-v1.7.0.img
got:
sending recovery 'recovery' <4602kb>... OKAY [1.750s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verify fail>
finished. total time: 3.141s
Click to expand...
Click to collapse
MD5 sum FINE!...
It's scary... what i should to do... i don't know...
ANtiHazarD said:
i don't understand what is it:
Boot your G1 into fastboot mode (boot while holding BACK)
I boot into fastbook like this:
Camera+Power, then press SEND
and i got FASTBOOT USB
it is not right?
Click to expand...
Click to collapse
I am just going to ask a simple question is your G1 Rooted? with your phone off hold the back button which is the button at the bottom with the arrow then hit the power button you should get a white screen with a little android at the top.
my G1 is rooted... and have NoneDanger SPL. I can't find information about it (HBOOT 1.42.0000, DREA20000)
when i press BACK+POWER i got first boot logo screen and thats all... orange color background and the MTN logo in i square in the middle of the screen.
I got 3 android skaters when press camera+power... only like this...
maybe i can use this:
fastboot flash system rom.zip
Click to expand...
Click to collapse
?
as i remember here http://developer.htc.com/adp.html
file - signed-dream_devphone_userdebug-ota-14721.zip
flash official 1.6 android rom and standart htc recovery....
Maybe i'll try this? how u think?
ANtiHazarD said:
my G1 is rooted... and have NoneDanger SPL. I can't find information about it (HBOOT 1.42.0000, DREA20000)
when i press BACK+POWER i got first boot logo screen and thats all... orange color background and the MTN logo in i square in the middle of the screen.
I got 3 android skaters when press camera+power... only like this...
Click to expand...
Click to collapse
See I am running Danger just like most people, thats the difference in the fastboot access. the 3 android skaters is the proper screen. So you are in the right spot. You should have also menu options like hit menu to reboot etc...I cant remember the others. But still its right. So if you are doing the fastboot commands as posted and it still gives you an error then it was something to do with when you did all those remove commands.
I think you pretty much have a nice heavy paperweight sorry bro. Only thing I think of is keep trying the fastboot command or maybe see if there is a way to flash stuff through fastboot. I dont think there is but you can look and see. Good luck, let me know how it turns out. If I was you I would just go get a slide or the new Galaxy S
ANtiHazarD said:
maybe i can use this:
?
as i remember here http://developer.htc.com/adp.html
file - signed-dream_devphone_userdebug-ota-14721.zip
flash official 1.6 android rom and standart htc recovery....
Maybe i'll try this? how u think?
Click to expand...
Click to collapse
That looks promising you can try that. good luck
so i unlocked my bootloader using the htcdev guide. this updated my hboot to 1.02.000 and when i try to flash CWM i get this error.
Code:
sending 'recovery' (1685 KB)... OKAY
writing 'recovery'... FAILED (remote: image error! (BootMagic check fail))
The Usual Suspect said:
so i unlocked my bootloader using the htcdev guide. this updated my hboot to 1.02.000 and when i try to flash CWM i get this error.
Code:
sending 'recovery' (1685 KB)... OKAY
writing 'recovery'... FAILED (remote: image error! (BootMagic check fail))
Click to expand...
Click to collapse
how (which method) are you trying to flash the recovery?
Here's the quick guide
Install hTc drivers successfully on pc.
Remove hTc sync and other related apps.
Now download clockworkmod recovery(whichever you want) and fastboot+adb kit on pc.
Open fastboot.
Connect ur phone. Load the bootloader and then fastboot. Fastboot mode(something like that) should be on your phone. Paste recovery and boot image in fastboot folder.
Type fastboot devices
Type fastboot flash boot boot.img(boot.img can be found in ur stock ruu )
Type fastboot flash recovery 'recoveryname'.zip
After that disconnect ur phone.
Select recovery.
(If u dont see anything, it was unsuccessful, hold vol up+power to see default recovery.)
Now install roms like this(http://forum.xda-developers.com/showthread.php?t=1851096):p(my rom) via recovery.
Hit Thanks.
You are done
Note:s off is not required for flashing a custom rom, however an unlocked bootloader is.
help needed.
hey der. i have rooted my phone with s-on. but i am facing the same problem as i cannot boot in cwm recovery mode and hence cannot install a custom rom. i am no developer. so please can you elaborate your above method step by step. sorry i am a noob here.
thanx anywayz
Have you managed to install cwm?
Hi everyone,
I have an HTC Magic 32B (SFR/Vodafone FR).
I updated hboot from 1.33.0013 to 1.33.0014G (*1) to be able to unlock the bootloader with htcdev unlock.
I unlocked it successfully using HTC official instructions.
Now I want to boot or install a custom recovery (recovery-RA-sapphire-v1.7.0G.img) and it doesn't work.
My hboot boot says :
Code:
*** UNLOCKED ***
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0014G (SAPP10000)
CPLD-10
RADIO-2.22.28.25
Jan 31 2012,14:43:52
HBOOT
<BACK> FastBoot Mode
From fastboot (when I hit Return) I have the "FASTBOOT USB" string, from fastboot if I try :
1)
Code:
C:\android\downloads>[B]fastboot boot recovery-RA-sapphire-v1.7.0G.img[/B]
downloading 'boot.img'...
OKAY [ 1.712s]
booting...
[B]FAILED (remote: not allow)[/B]
finished. total time: 1.733s
2)
Code:
C:\android\downloads>[B]fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img[/B]
sending 'recovery' (4520 KB)...
OKAY [ 1.712s]
writing 'recovery'...
[B]FAILED (remote: not allow)[/B]
finished. total time: 1.738s
After reading htc instructions to flash img, I also tried from RUU mode using "fastboot oem rebootRUU", that gives me RUU USB on the phone and on the computer :
Code:
C:\android\downloads>fastboot oem rebootRUU
...
OKAY [ 0.012s]
finished. total time: 0.016s
Then I try :
1)
Code:
C:\android\downloads>[B]fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img[/B]
sending 'recovery' (4520 KB)...
OKAY [ 1.718s]
writing 'recovery'...
[B]FAILED (remote: image type not support)[/B]
finished. total time: 1.749s
2)
Code:
C:\android\downloads>[B]fastboot boot recovery-RA-sapphire-v1.7.0G.img[/B]
downloading 'boot.img'...
OKAY [ 1.714s]
[B]booting...[/B]
Here it hangs, I must enter a fastboot reboot to regain the control on the device.
I don't know what's wrong here. Either from fastboot (usb) or ruu (usb) it don't work even if the bootloader is unlocked.
amonra recovery should install and work on this phone right ?
Currently I don't want to root or S-OFF the phone because I like to apply not too much modification on it.
Can you help me ?
Thanks for the attention, and even more if you can help
(*1) 1.33.0013 cannot be htcdev unlocked because it don't accept "fastboot oem get_identifier_token", that's why I updated to 1.33.0014G.
The update was given by htcdev.com through an RUU that didn't work because I started it from adp (phone started normally with usb debugging on) and for an unkown reason adp reboot bootloader didn't work, I made it work be starting RUU exe from fastboot directly.
I think my problem/solution may be related to the error : "remote: image type not support" when I try to flash recovery being in RUU mode.
From the official updates files (official ruu and fota) I've found that some images are not of the img format but the nb0 format. Maybe I need to flash an image that is of this format (nb0), the problem is that I have no idea how to find or convert amonra recovery image to this format...
If it is the problem, it is lame not to be able to flash img files ...
Also, one idea I had is that I have to flash files through an update.zip file rather than a single img. But it is a lot more complex to figure out (making a valid update.zip package)...
I'm quite lost and decieved about the HTC "unlock" (I think I'm not the first one to be) ... (And I don't want to brick my phone)
superbob56 said:
I think my problem/solution may be related to the error : "remote: image type not support" when I try to flash recovery being in RUU mode.
From the official updates files (official ruu and fota) I've found that some images are not of the img format but the nb0 format. Maybe I need to flash an image that is of this format (nb0), the problem is that I have no idea how to find or convert amonra recovery image to this format...
If it is the problem, it is lame not to be able to flash img files ...
Also, one idea I had is that I have to flash files through an update.zip file rather than a single img. But it is a lot more complex to figure out (making a valid update.zip package)...
I'm quite lost and decieved about the HTC "unlock" (I think I'm not the first one to be) ... (And I don't want to brick my phone)
Click to expand...
Click to collapse
hi, i have same problem on my HTC Magic, from hboot 1.33.0014 i can`t do enything (flash new recovery or new rom or make RUU)
did u resolved that problem?
I must admit I've given up.
I recently bought myself a fresh Nexus 5...
Gold luck to you if you try to go on with the HTC Magic !
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
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.