Related
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!
I followed youtube video (sorry I am not allowed to post URL)
The title of the video is: How to Install TWRP in LeEco Mobiles | Without ROOT | Simple and Riskless 2018
(1) Disable phone password, pin, fingerprint
(2) Boot phone to fastboot mode(hold Power+Volume Down button), connect to PC
(3) C:\adb>fastboot oem unlock-go （success）
(4) C:\adb>fastboot boot twrp-3.2.3-1-zl1.img
It enter TWRP and ask for password (Mount, Decrypt Data)
Did some research, seems I also need to erase userdata before reboot.
Can you help me post the sequence of commands here, or I should use a different version of TWRP?
I also tried
fastboot oem unlock-go
fastboot flash recovery twrp-3.2.3-1-zl1.img
fastboot reboot
It will boot into EUI instead of TWRP.
Then I tried
fastboot oem unlock-go
fastboot flash recovery twrp-3.2.3-1-zl1.img
Then hold Power+Volume UP button instead of run "fastboot reboot", it reboot, BUT enter a black screen.
Please help me to get TWRP work, thanks!
I tried a different version of TWRP, twrp-3.2.1-0-zl1.img. It worked.
This is what I did:
fastboot oem unlock-go
fastboot format userdata
fastboot boot twrp-3.2.1-0-zl1.img
Then in TWRP, I tried
(1) backup,
(2) wipe (advanced wipe, select system, data, dalvik/ART cache, cache)
(3) Restore using backup created in step 1
After restore and reboot, the phone back to original.
Then I did:
1. Enable the Developer Option.
2. Enable OEM Unlocking and USB Debugging
3. ReBoot Phone to fastboot mode (Volume Down + Power button) and connect to PC.
4. fastboot oem unlock-go
Weird, this time I got error:
C:\adb>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.006s
How can this happen? How to fix it???
Thanks!
rogerxda2018 said:
I followed youtube video (sorry I am not allowed to post URL)
The title of the video is: How to Install TWRP in LeEco Mobiles | Without ROOT | Simple and Riskless 2018
(1) Disable phone password, pin, fingerprint
(2) Boot phone to fastboot mode(hold Power+Volume Down button), connect to PC
(3) C:\adb>fastboot oem unlock-go （success）
(4) C:\adb>fastboot boot twrp-3.2.3-1-zl1.img
It enter TWRP and ask for password (Mount, Decrypt Data)
Did some research, seems I also need to erase userdata before reboot.
Can you help me post the sequence of commands here, or I should use a different version of TWRP?
I also tried
fastboot oem unlock-go
fastboot flash recovery twrp-3.2.3-1-zl1.img
fastboot reboot
It will boot into EUI instead of TWRP.
Then I tried
fastboot oem unlock-go
fastboot flash recovery twrp-3.2.3-1-zl1.img
Then hold Power+Volume UP button instead of run "fastboot reboot", it reboot, BUT enter a black screen.
Please help me to get TWRP work, thanks!
Click to expand...
Click to collapse
rogerxda2018 said:
I tried a different version of TWRP, twrp-3.2.1-0-zl1.img. It worked.
This is what I did:
fastboot oem unlock-go
fastboot format userdata
fastboot boot twrp-3.2.1-0-zl1.img
Then in TWRP, I tried
(1) backup,
(2) wipe (advanced wipe, select system, data, dalvik/ART cache, cache)
(3) Restore using backup created in step 1
After restore and reboot, the phone back to original.
Then I did:
1. Enable the Developer Option.
2. Enable OEM Unlocking and USB Debugging
3. ReBoot Phone to fastboot mode (Volume Down + Power button) and connect to PC.
4. fastboot oem unlock-go
Weird, this time I got error:
C:\adb>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.006s
How can this happen? How to fix it???
Thanks!
Click to expand...
Click to collapse
I can help you with issue, But, lets keep it within one thread.
So my phone booted into the stock recovery (no TWRP installed) when I accidentally selected the wrong update method in magisk. It kept on rebooting to the recovery even after selecting reboot device and tried clearing cache. Even after that it booted back to the recovery. Then I turned off the phone. And now when the phone turns on it goes to bootloader even after selecting recovery mode. And in the bootloader "Bootloader Version" and "Baseband Version" are blank. This is what it shows;
Fastboot Mode
PRODUNT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - "Serial number available"
SECURE BOOT - yes
DEVICE STATE - unlocked
PC doesn't recognize it either.
Under device manager it says "Unknown USB Device (Device Descriptor Request Failed)
I'm having 6T 6GB RAM (International)
Bootloader unlocked
Any idea as to why this happens and how to solve it?
Thanks
PC recognized the phone after trying a different USB port. And even detects fastboot.
What should I do to get this booted into the system?
fastboot boot twrp-3.2.3-2-fajita.img gave below error.
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Still selecting "Recovery Mode" reboots to Bootloader
dushan90 said:
PC recognized the phone after trying a different USB port. And even detects fastboot.
What should I do to get this booted into the system?
fastboot boot twrp-3.2.3-2-fajita.img gave below error.
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Still selecting "Recovery Mode" reboots to Bootloader
Click to expand...
Click to collapse
Use MSM Tool to recover the device. That's the easiest option.
Does it wipes the device?
Also I was on 9.0.13. And I could find only MSM Tool 9.0.12.
Alright. So this is how I solved my problem.
First entered
Code:
fastboot --set-active=b
And that solved FAILED (remote: Failed to load/authenticate boot image: Load Error) error.
After that I managed to boot to twrp by
Code:
fastboot boot twrp-3.2.3-0-fajita.img
At first, the phone got stuck at Oneplus logo.
Pressing Vol Up + Power for about 10 seconds turned off the phone. Pressing Power button for a few more seconds turned it back on to bootloader. Enterd the previous code once again booted it to TWRP.
Sideloaded 9.0.13 downloaded from Oneplus site and rebooted.
Problem solved. Everything was saved.
dushan90 said:
Alright. So this is how I solved my problem.
First entered
Code:
fastboot --set-active=b
And that solved FAILED (remote: Failed to load/authenticate boot image: Load Error) error.
After that I managed to boot to twrp by
Code:
fastboot boot twrp-3.2.3-0-fajita.img
At first, the phone got stuck at Oneplus logo.
Pressing Vol Up + Power for about 10 seconds turned off the phone. Pressing Power button for a few more seconds turned it back on to bootloader. Enterd the previous code once again booted it to TWRP.
Sideloaded 9.0.13 downloaded from Oneplus site and rebooted.
Problem solved. Everything was saved.
Click to expand...
Click to collapse
Beast mode nice job and thanks for sharing your fix
Sent from my [device_name] using XDA-Developers Legacy app
I have the same issue..
Is it possible to restore the baseband version by entering this commands?
In my situation, I already wiped and boot into the system.
dushan90 said:
Alright. So this is how I solved my problem.
First entered
Code:
fastboot --set-active=b
And that solved FAILED (remote: Failed to load/authenticate boot image: Load Error) error.
After that I managed to boot to twrp by
Code:
fastboot boot twrp-3.2.3-0-fajita.img
At first, the phone got stuck at Oneplus logo.
Pressing Vol Up + Power for about 10 seconds turned off the phone. Pressing Power button for a few more seconds turned it back on to bootloader. Enterd the previous code once again booted it to TWRP.
Sideloaded 9.0.13 downloaded from Oneplus site and rebooted.
Problem solved. Everything was saved.
Click to expand...
Click to collapse
I get this error by trying your solution:
```$ sudo fastboot --set-active=b
error: Device does not support slots.```
```$ sudo fastboot --set-active=b
Setting current slot to 'b'...
FAILED (remote: unknown command)
finished. total time: 0.000s```
Also tried the other option without better results:
```$ sudo fastboot --set-active=a
error: Device does not support slots.```
```$ sudo fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: unknown command)
finished. total time: 0.000s```
Maybe it's because I'm using OnePlus 6 instead 6T?
how was this fixed?
Hello to all gurus here
my Redmi Note 7 had a screen broken...I can only hardy recognize when it's in fastboot or recovery.... Touch not working.
The bootloader is locked, I am not sure if USB Debugging was enabled, but I suppose it was not because I get the following:
C:\MyDocs\TEMP\Varie\platform-tools>fastboot oem unlock
FAILED (remote: 'Token Verify Failed, Reboot the device
')
fastboot: error: Command failed
In this terrific scenario, is there any way on earth to recover my data?
I can only see my device in fastboot mode for what I can say...
On the other hand I could probably install a TWRP (which should already have debugging enabled) using fastboot but it seems to me it should clear all my user data.
Any way out?
Thanks in advance
unlocking bootloader requires bonded mi account in developer options and can only unlocked from miunlock tool. btw that will erase userdata during unlock for security reasons
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.