Database Users

P10 Lite [WAS-LX1A] bricked! Please Help

Hello,
My Huawei P10 lite Single Card (WAS-LX1A) bricked after i tried to Update from 8.0 to 8.1,
now it just boots to fastboot and i cant Flash anything.
(Idk why but somehow it just boots fastboot when its connected to the pc and i have to change the cable in fastboot since the one i boot it with doesnt detect fastboot, and the cable works with fastboot doesnt boot it up.)
When i try to install an recovery it works, but when i try to boot my phone it just gives me the error screen, trying to install anything else just gives me the following Errors:
"Partition length error" or
"command not allowed" Bootloader is unlocked.
Please help me
not even the "dload" method works since this one isnt starting too.

dload won't work since you have upgraded to EMUI 8 and you can only use B181 to dload install, which is EMUI 5.1. Try HwOTA8 to downgrade to Android 7:
https://forum.xda-developers.com/p10-lite/development/hwota-huawei-p10-lite-t3776186
Use the guide in the post.
But before that, in bootloader under "bootloader unlocked", you have to check if there is "frp lock" or "frp unlock". If it's lock, you can't flash anything and you have to unlock it. If you have frp lock, write here and I will try to find a zip file I've seen in the forum for frp unlocking.
Also, can you tell me which ROM you tried to flash? I didn't know there is Android 8.1 for this phone, can you send me a link?

Stiliyan said:
dload won't work since you have upgraded to EMUI 8 and you can only use B181 to dload install, which is EMUI 5.1. Try HwOTA8 to downgrade to Android 7:
https://forum.xda-developers.com/p10-lite/development/hwota-huawei-p10-lite-t3776186
Use the guide in the post.
But before that, in bootloader under "bootloader unlocked", you have to check if there is "frp lock" or "frp unlock". If it's lock, you can't flash anything and you have to unlock it. If you have frp lock, write here and I will try to find a zip file I've seen in the forum for frp unlocking.
Also, can you tell me which ROM you tried to flash? I didn't know there is Android 8.1 for this phone, can you send me a link?
Click to expand...
Click to collapse
Both unlocked but i tried to install EMUI 8.1 (8.0 worked tho) i got 8.1 on xda just like i did with 8.0
not exactly which…
but could it be that the cable Transfers files wrong? its a bit damaged
it
(when i try to Flash a recovery as example)

I don't know, try another cable if you have at home, if still not working try if HwOTA8 can flash the required recoveries.

Stiliyan said:
I don't know, try another cable if you have at home, if still not working try if HwOTA8 can flash the required recoveries.
Click to expand...
Click to collapse
Yeah i will try HWOTA 8 and already ordered a new cable

ShadowForceHD said:
Yeah i will try HWOTA 8 and already ordered a new cable
Click to expand...
Click to collapse
HWOTA did not work and this is the message i get when booting:
Error!
Func NO : 11 (reovery image)
Error NO : 2 (load failed!)
this is the command i use and the message i get when i install twrp:
C:\Windows\system32>fastboot flash recovery_ramdisk C:\Users\my name\Downloads\twrp_3.2.1-0_Oreo_V3.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (16506 KB)...
OKAY [ 0.423s]
writing 'recovery_ramdisk'...
OKAY [ 0.125s]
finished. total time: 0.548s
i dont know what to do anymore

ShadowForceHD said:
HWOTA did not work and this is the message i get when booting:
Error!
Func NO : 11 (reovery image)
Error NO : 2 (load failed!)
this is the command i use and the message i get when i install twrp:
C:\Windows\system32>fastboot flash recovery_ramdisk C:\Users\my name\Downloads\twrp_3.2.1-0_Oreo_V3.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (16506 KB)...
OKAY [ 0.423s]
writing 'recovery_ramdisk'...
OKAY [ 0.125s]
finished. total time: 0.548s
i dont know what to do anymore
Click to expand...
Click to collapse
update:
i just noticed something....
when i got bricked my device said that frp and bootloader was unlocked but this wasn't the case, bootloader was locked and i could use oem "unlock code" just like it was never unlocked even when it said that bootloader is unlocked.....
may this be the same case with my FRP? this is was dc unlocker says:
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
but i got no money for this program to unlock my frp or try to do it...someone got a similiar program?
you should check it too if you had a similiar problem just like me

did you found solution ?
ShadowForceHD said:
update:
i just noticed something....
when i got bricked my device said that frp and bootloader was unlocked but this wasn't the case, bootloader was locked and i could use oem "unlock code" just like it was never unlocked even when it said that bootloader is unlocked.....
may this be the same case with my FRP? this is was dc unlocker says:
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
but i got no money for this program to unlock my frp or try to do it...someone got a similiar program?
you should check it too if you had a similiar problem just like me
Click to expand...
Click to collapse

Fastboot "Command not allowed" + FRP Locked (With bootloader unlocked) [System.img]

Fastboot "Command not allowed" + FRP Locked (With bootloader unlocked) [System.img]
I messed up trying to manually update magisk and my huawei p8 lite 2017 (PRA-LX1ITAC555B172) is stuck on bootloop
I have TWRP installed, the bootloader unlocked ("Phone Unlocked, FRP Locked")
I got the update.app for my device and tried to flash boot.img and system.img with fastboot, with no success:
Code:
D:\Desktop\platform-tools>fastboot flash system SYSTEM.img
Sending sparse 'system' 1/7 (460796 KB) OKAY [ 11.992s]
Writing 'system' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
This error was the same for boot.img too
I then tried to flash both images with TWRP
I managed to flash boot.img, tried to restart the phone and now instead of rebooting to the os it just goes into eRecovery (where i cannot do anything because it gives me the "Getting package info failed" error)
When i tried to flash system.img via twrp, it gave me this error "E:Cannot flash images to file systems"
So now i'm stuck and i've been trying to find another way to flash IMGs with no luck
I'm guessing that the "Command not allowed" error from fastboot is caused by FRP being locked, so how do i unlock this? Do i need the same unlock code i used to unlock the bootloader or do i need a different one? (p.s. I unlocked the phone a while ago and i don't have the code anymore, is there any way i can get it back, considering that the bootloader is unlocked, or do i have to pay for one?)
To anyone that actually reads this, THANK YOU and sorry for being an absolute moron

Cant Install TWRP on Xperia F5321

Hello
i have followed all the guides in order to install the latest version of TWRP in mi X Compact in order to Magisk, but im having this issue on the fastboot comand:
Sending 'recovery' (21552 KB) OKAY [ 0.724s]
Writing 'recovery' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
i have serched for solutions but nothing seems to work, its the first time i try to install TWRP on this phone so its never been rooted (Bootloader is not unlocked) and everyting has alredy been updated to the latest version, any help?
Thanks in advance!

i just unlocked the bootloader, and still gives me the "FAILED (remote: Command not allowed)" error when flashin TWRP trough fastboot HELP PLEASE

Black Swift said:
i just unlocked the bootloader, and still gives me the "FAILED (remote: Command not allowed)" error when flashin TWRP trough fastboot HELP PLEASE
Click to expand...
Click to collapse
Try fastboot boot twrp.img

just tried it, i got a message on my phone screen:
"your device has failed verification and will not work properly"
then phone restarts
in the windows power shell i get this message:
FAILED (Status read failed (Too many links))
I just seem to be unable to install TWRP on this phone :C

Help please!!!

i just tried a different cable, im still getting the "comand not allowed" message, can anyone help me please??

OEM Locked and greyed out with BL Unlocked & FRP Locked

I'm trying to root my Huawei P8 Lite 2017 PRA-LX1 (running on EMUI 5.0.3 Android 7.0). But I'm getting stuck :
My BootLoader is unlock, but my FRP is locked when I access the fastboot mode.
The option Allow OEM unlock is turned off and greyed out in the dev settings.
It prevents me from doing any command with fastboot, except "fastboot devices" and "fastboot oem get-bootinfo". All other commands return me :
Code:
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
I'm worried cause it looks like I no longer have a recovery img : when I boot with Vol UP + Power, I got a screen with the Android guy saying :
Code:
ERROR MODE
Attention !
Please Update system again
Error
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Each time I boot, I have a black screen with white and yellow writtings saying
"your devices has been unlocked and cannot be trusted"
From there I can boot normaly to the standard OS (EMUI 5.0.3 ; Android 7.0).
I can also enter the eRecovery mode to download latest version and recovery. But it fails and say "Getting package info failed".
When I try the factory reset from the settings, I get the same error as the one I got when trying to access the recovery more :
Code:
ERROR MODE
Attention !
Please Update system again
Error
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
To get to this situation, I tried to follow this guide :
[GUIDE] Unlock bootloader, root the device and install any custom ROM! (ALE-L23/21)
Hi all! So, you have a P8 lite in your pocket and you hate EMUI? Well, that was my case too, it's uncustomizable, ugly, and removes plenty of features from android stock. I do not like it one bit, and I like even less the fact that this phone is...
forum.xda-developers.com
I was not able to flash any OS with the dload/ procedure.
So I followed this guide :
[UPDATED GUIDE] [BOOTLOADER UNLOCK] Huawei p8 lite 2017 (pra-lx1)
This guide is the only one made and tested personally by me, I am not responsible for malfunctions or any damage to the device, carefully read every single step and everything will be successful [ATTENTION]: Before proceeding, save all your...
forum.xda-developers.com
and was able to correctly unlock my bootloader.
Then, I got back to the first guide to Install TWRP. The command fastboot flash recovery was working well :
Code:
$ fastboot flash recovery twrp-3.6.2_9-0-prague.img
Sending 'recovery' (14998 KB) OKAY [ 0.430s]
Writing 'recovery' OKAY [ 0.370s]
Finished. Total time: 0.828s
But I never managed to enter the TWRP recovery.
The Vol UP + Power reboot was getting me the eRecovery mode (to install the standard OS).
I tried to enter TWRP with fastboot :
Code:
$ fastboot boot twrp-3.6.2_9-0-prague.img
Sending 'boot.img' (14998 KB) OKAY [ 0.420s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Trying to solve this situation have made the things worse and worse.
I would like to follow this tutorial
[Solution]BL unlocked&FRP Locked-Fastboot FAILED (remote: Command not allowed)
Note: THIS IS NOT A SOLUTION TO BYPASS FRP! I am not responsible if you are dumb dumb and break your phone This Solution is written in under 10 minutes AND WORKS ONLY AND ONLY FOR STOCK people with no experience stay away This is not a...
forum.xda-developers.com
but since I cannot do a factory reset (first step tutorial) and I don't have a recovery img working, I'm a bit timorous.
Do you think I can upgrade my OS (from my OS settings menu) without a recovery img ? Will that solve the issue with my recovery img ?
Any thoughts on the situation would be much appreciated.
Thanks for reading me !

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

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

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

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

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

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

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

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

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

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

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