I was on MIUI Global 12.0.2 Stable. I tried to flash Pig's latest Lineage (2020.07.21) from TWRP. The flash failed with an "Error 7". When I tried to reboot, the device went to "fastboot" mode.
After that, every attempt of a reboot ended in fastboot mode. So I tried to flash TWRP.img. Flashing went OK. But "fastboot boot twrp.img" gave the error "FAILED (remote: Failed to load/authenticate boot image: Load Error)". The result was same with "fastboot oem reboot-recovery" command.
So I was stuck in fastboot mode with the risk of battery depletion. Below is the commands I ran to flash the TWRP.
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.016s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 2.179s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.016s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 2.046s
C:\adb>
Click to expand...
Click to collapse
SOLUTION: One needs to flash the fastboot ROM in MiFlash.
My situation had an extra issue as there were no fastboot ROM for MIUI Global 12.0.2. So, I downloaded MIUI 11.0.5 Global Fastboot ROM and flashed it. One needs to keep in mind about the "Anti-Rollback Protection" (https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/) and take necessary steps to avoid an anti-rollback brick.
If anti-rollback compatible ROM not available, then just delete first lines in all .bat files (.bat for Windows; .sh for Linux) up to the first line that starts with "fastboot %* getvar product..." of the available fastboot ROM. Those lines are the anti-rollback check. After than you can flash it via MiFlash.
Stillness said:
So I try to flash TWRP.img. Flashing goes OK. But "fastboot boot twrp.img" gives this error "FAILED (remote: Failed to load/authenticate boot image: Load Error)"
Click to expand...
Click to collapse
There is a Fastboot command to reboot to recovery (TWRP if you previously flashed it):
>> fastboot oem reboot-recovery
zgfg said:
There is a Fastboot command to reboot to recovery (TWRP if you previously flashed it):
>> fastboot oem reboot-recovery
Click to expand...
Click to collapse
Thanks for the reply. I tried that command too, but ended with the same error.
Now, downloading the 11.0.5 Global Fastboot ROM since no 12.0.2 Fastboot available. My plan is to just delete first lines in .bat files of the ROM to avoid 'rollback protection' and flash via MiFlash before the battery goes zero. According to google, it seems flashing the full Fastboot ROM is the only solution
SOLVED
Solved. Edited the OP.
zgfg said:
There is a Fastboot command to reboot to recovery (TWRP if you previously flashed it):
>> fastboot oem reboot-recovery
Click to expand...
Click to collapse
Wow, thank you so much for pointing this out!
I just had a close to two hour journey through all emotions after trying to restart my phone and suddenly ending up in a seemingly inescapable fastboot hell...
I've tried booting different recoveries, all failing with
Code:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
and was already at the point of giving up getting my system back, just trying to save my data if possible. Flashing seemed to work, but
Code:
fastboot reboot recovery
just threw me back into fastboot, which I assumed to be due to the phone rejecting the flashed recoveries just as it was rejecting them when I tried to boot them directly.
When I saw this comment I wondered whether Xiaomi implemented rebooting directly to the recovery differently (as it turns out, it doesn't seem to be standardized) and
Code:
fastboot oem reboot-recovery
worked perfectly! After reflashing my ROM from TWRP I was booted back up into my system with everything intact, as if nothing has happened.
Related
Ive got an i9505G and Ive already done "fastboot oem unlock" to unlock the bootloader. I'm able to "fastboot boot recovery.img" using clockworkmod-touch recovery image. However, I am unable to boot even the stock boot.img with "fastboot boot ...". It appears to try and do it, but the transfer happens really fast, and then the phone just hangs there forever.
Code:
$ fastboot boot /home/j/android/galaxy_s4_ge/boot.img.stock
downloading 'boot.img'...
OKAY [ 0.568s]
booting...
OKAY [ 0.019s]
finished. total time: 0.587s
My boot.img matches the one which is only the phone and boots up fine.
Code:
# md5sum `pwd`/boot
abcf2780adcaa939e29474162ea8a637 /dev/block/platform/msm_sdcc.1/by-name/boot
$ md5sum /home/j/android/galaxy_s4_ge/boot.img.stock
abcf2780adcaa939e29474162ea8a637 /home/j/android/galaxy_s4_ge/boot.img.stock
Is there some trickery needed to get fastboot to launch the stock boot.img? Or is everybody just flashing the kernel and booting it to test it and then using recovery to fix it after testing?
I am not sure when or how this happened, but I have installed Magisk and Xposed a while back (about a month ago) and had no issues. Today I was looking at kernels to install and decided to go into TWRP to do a backup, only to find the stock recovery on my device. Following Rooting Your Essential this time, I was greeted with the error
target reported max download size of 536870912 bytes
sending 'recovery' (45048 KB)...
OLAY [ 1.385s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 1.405s
Click to expand...
Click to collapse
So there is no recovery partition on my phone currently, but I can still boot to stock recovery
th3 game said:
I am not sure when or how this happened, but I have installed Magisk and Xposed a while back (about a month ago) and had no issues. Today I was looking at kernels to install and decided to go into TWRP to do a backup, only to find the stock recovery on my device. Following Rooting Your Essential this time, I was greeted with the error
So there is no recovery partition on my phone currently, but I can still boot to stock recovery
Click to expand...
Click to collapse
Its likely a dodgy lead or try a different usb port!
I had it before and had to reboot my laptop that was all
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
th3 game said:
I am not sure when or how this happened, but I have installed Magisk and Xposed a while back (about a month ago) and had no issues. Today I was looking at kernels to install and decided to go into TWRP to do a backup, only to find the stock recovery on my device. Following Rooting Your Essential this time, I was greeted with the error
So there is no recovery partition on my phone currently, but I can still boot to stock recovery
Click to expand...
Click to collapse
This should be in the "Help" forum.
There is no recovery partition.
The boot partition holds the recovery.
tech_head said:
This should be in the "Help" forum.
There is no recovery partition.
The boot partition holds the recovery.
Click to expand...
Click to collapse
My apologies, I thought I had it in that section. Thanks!
Also having trouble ..I can't flash return to stock .no boot partition also .. can flash twrp but from there I'm not sure what to do now .. any help would be great thanks
Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
i did that and couldn't boot my phone
Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
WOW!!! Really appreciate that!
@Somcom3X life savor, thank you
Djcall11 said:
i did that and couldn't boot my phone
Click to expand...
Click to collapse
If you flash TWRP (twrp-mata_11.img) to the boot partition, that's true. You can only go in recovery. Once you're in TWRP, you need to rewrite the boot image.
Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
Thanks...this fixed an issue I had as well rolling back to a Beta version.
Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
im having this issue. is the <filename>.image you are flashing just the boot.img from the system image zip?
sruel3216 said:
im having this issue. is the <filename>.image you are flashing just the boot.img from the system image zip?
Click to expand...
Click to collapse
Thanks that worked. Rooted on elementalX now!
I did that, but nothing happens
kfhughes said:
If you flash TWRP (twrp-mata_11.img) to the boot partition, that's true. You can only go in recovery. Once your in TWRP, you need to rewrite the boot image.
Click to expand...
Click to collapse
I'm using a Pixel XL 2, so sorry for the post in the wrong forum, but I lucklily found the post so thought to send the query which was already ongoing here. Nothing still happens and Im stuck, it shows the logo of teamwin recovery porject 3.2.3.1 and it's stuck there. I've no clue how to proceed further.
Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
alright, so I did this now I can't get back to twrp.. can you help?
Update: I opened a new thread here: https://forum.xda-developers.com/oneplus-6/help/screwed-flashing-twrp-t3846690
Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
Interesting, I did
Code:
fastboot flash [U][B]boot[/B][/U] stock.img
Sending 'boot__b' (20769 KB) OKAY [ 0.559s]
Writing 'boot__b' FAILED (remote: 'No such partition.')
then did
Code:
fastboot flash [B][U]boot_b[/U][/B] stock.img
Sending 'boot_b' (20769 KB) OKAY [ 0.557s]
Writing 'boot_b' OKAY [ 0.831s]
Any idea why it does the double underscore when not specifying
Code:
__b
....and the single underscore when specifying?
Code:
_b
Very odd behavior. Either way, thanks for the tip!
New Issue after this solution
Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
So I did this and it worked to get twrp booted up, but now a new issue has come up. TWRP is stuck on the splash screen, and I can no longer boot up my phone since this overwrote my boot partition. So I ****ed up and tried to unplug and reboot, but when I did that I reset my USB debugging. So now I can't even get to my phone through adb or fastboot. I can boot into the bootloader, but other than that and starting at the TWRP screen I'm stuck. Any Ideas or solutions? I'm hoping I get lucky and TWRP boots up after a while, but so far it's not looking good.
Recovery Done But Not boot in Recovery
Recovery is successfully finished but device not boot in recovery
C:\Users\HitMer\Desktop\one plus 7 pro>fastboot flash boot test-twrp-3.3.1-2-guacamole.img
target reported max download size of 805306368 bytes
sending 'boot' (55976 KB)...
OKAY [ 1.242s]
writing 'boot'...
OKAY [ 0.161s]
finished. total time: 1.412s
C:\Users\HitMer\Desktop\one plus 7 pro>fastboot boot test-twrp-3.3.1-2-guacamole.img
downloading 'boot.img'...
OKAY [ 1.233s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.262s
Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
Thanking you in 2019! :laugh::good:
there is a reason guides tell you to use
fastboot getvar current-slot
fastboot set_active other
because the device will flip flop between active slots depending on OTA
if you simply just specify a slot with fastboot flash boot boot_*
you could flash the wrong slot, which is bad
you do not want to overwrite your current active slot with twrp or you won't be-able to boot
once again the steps are
fastboot getvar current-slot
fastboot set_active other
fastboot flash boot yourtwrpimagehere.img
reboot normally it will boot to twrp
then if your touch screen is not working
adb shell
twrp sideload
adb sideload twrp-installerzip
newbie to a oneplus 2. I acquired this phone locked and with OOS 3.61. been doing some searches but apparantly not enough and not getting very far.
Actions performed so far
set oem unlocking in dev-options to enabled.
rebooted to fastboot
"fastboot oem unlock" was succesful and rebooted and completed setup
rebooted to fastboot
from fastboot installed twrp "fastboot flash recovery recovery.img" (recovery.img being twrp-3.2.1-0-oneplus2.img)
results:
C:\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22180 KB)...
OKAY [ 0.624s]
writing 'recovery'...
OKAY [ 1.310s]
finished. total time: 1.934s
:end results
then boot directely to twrp with "fastboot boot recovery.img"
performed nandroid backup.
rebooted device and tried booting to recovery but still has oem recovery.
any ideas? would like twrp native not via fastboot only.
thanks in advance.
Update solved:
booted twrp from .img file and installed su.zip and installed twrp.apk and used the app to install twrp. works now. not sure why it was saying it was working from from fastboot and writing but hope this helps someone else.
TWRP 3.2.1 doesn't work properly yet on the OnePlus 2 for some reason. I can assume that you wanted root so I can give you 2 options:
1) If you want to stay on stock OxygenOS 3.6.1 or a custom rom Nougat or lower, then flash TWRP 3.1.1
2) If you want to have an Oreo rom, then you have to get your hands on the unofficial TWRP from anupritaisno1. The download link for that on his forum doesn't work so if you want, I can link my Google Drive.
This is my first time trying to root my android and I am having the same problem with my oneplus 2 3.6.1 OOS. I have successfully unlocked oem but can't seem to flash twrp.
I have downloaded twrp 3.2.1 on my desktop and renamed it to "recovery".
I used the same command "fastboot flash recovery recovery.img" but it just says "error: cannot open 'recovery.img' "
Can you please tell me how you managed to install twrp and root your android?
you need to downgrade the OOS to ver 3.002 or 3.1, then you re-unlock the bootloader then flash twrp recovery.
Finally flash your phone with root of your liking.
rp201 said:
newbie to a oneplus 2. I acquired this phone locked and with OOS 3.61. been doing some searches but apparantly not enough and not getting very far.
Actions performed so far
set oem unlocking in dev-options to enabled.
rebooted to fastboot
"fastboot oem unlock" was succesful and rebooted and completed setup
rebooted to fastboot
from fastboot installed twrp "fastboot flash recovery recovery.img" (recovery.img being twrp-3.2.1-0-oneplus2.img)
results:
C:\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22180 KB)...
OKAY [ 0.624s]
writing 'recovery'...
OKAY [ 1.310s]
finished. total time: 1.934s
:end results
then boot directely to twrp with "fastboot boot recovery.img"
performed nandroid backup.
rebooted device and tried booting to recovery but still has oem recovery.
any ideas? would like twrp native not via fastboot only.
thanks in advance.
Update solved:
booted twrp from .img file and installed su.zip and installed twrp.apk and used the app to install twrp. works now. not sure why it was saying it was working from from fastboot and writing but hope this helps someone else.
Click to expand...
Click to collapse
dear,
do you mind sharing the twrp.img you used?
Thank you
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
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.