Database Develop

Honor 4x factory reset and recovery menu not work

Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.

If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).

oppili said:
If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).
Click to expand...
Click to collapse
Yes, im sure. On bootloader mode is in red color - Phone unlocked, but i not using Linux, im on Windows 7 and this not help me....

Try fastboot oem unlock - command again.
If still not works, try fastboot erase of that *.img file before flashing that new img file.

oppili said:
Try fastboot oem unlock - command again.
When i try this command...
c:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.004s]
finished. total time: 0.006s
If still not works, try fastboot erase of that *.img file before flashing that new img file.
Click to expand...
Click to collapse
I know about this but im above when i try erase all after this fastboot send me "Failed..." and i will be have dead phone, tell me - when i try erase command for all partitions - will be phone work wit fastboot after this??
THX

Are you the only user in pc ? Do you have admin rights ?
or
try any other pc
or
use Ubuntu OS

Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked

thilak devraj said:
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked
Click to expand...
Click to collapse
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....

Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
then you should take it to the service center. the only best thing you can do now..

Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
erase cache command is blocked by huawei in fastboot irrespective of locked or unlocked state. somewhere i read unlock lost permissions after update. if you have not tried unlock after update try it. driver can also be an issue, install hisuite it comes with drivers.

Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down

shady143 said:
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down
Click to expand...
Click to collapse
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?

Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.

zzztidurvirus said:
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.
Click to expand...
Click to collapse
First...many thanks for your interest!
Look, about bootloader, on boot mode is in red PHONE UNLOCKED, i try this command in fastboot:
C:\Minimal ADB and Fastboot>adb reboot bootloader
C:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Minimal ADB and Fastboot>fastboot oem backdoor info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ -0.000s]
finished. total time: -0.000s
so what is FB Lockstate??Is my bootloader unlocked or locked??
Here is another command which i try....
C:\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
Cant derermine partition type - is this problem?
I also try this....
C:\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 524288000 bytes
sending 'recovery' (25034 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 1.033s]
finished. total time: 1.831s
C:\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
It seems that fastboot write recovery (with your help i need use admin rights now this work) but i still cant boot to recovery no matter how...
I can also flash and backup boot and recovery via Flashify or Rashr and when i open backup with HEX editor it seems that i succesfully upload TWRP but still cannot acess TWRP recovery....
This is all what i try in this time, of course i read your help words about Huawei extractor etc. but not try at this time, i hope i explain more detailed my problem. Look im not a newbie, i allready flash etc. my Lenovo and P9 lite what i have here but not understand where can be problem in this Honor 4x, it seems like corrupted recovery partition or can be problem in read only/write partition - i play with this option before....
anyway - run as admin - this help me a lot i think, THX and wait your answer.
EDIT: one thing, you think that when i try flash stock recovery (i can, no problem of course) it will be work?
Update: Big success, i just try flash stock recovery B064b and now im in stock recovery menu, im surprised but what now? I want update to Marshmallow 6.0....?
But in stock recovery is: phone and the data cannot be recovered. Continue?
Oh sorry, this is about "not sd card inserted" problem
What will now progress? I have inside B130 firmware and want Marshmallow, also TWRP recovery must i flash now especially for B130 firmware for work?
Update: Yes, all working now, factory reset, recovery etc. you help me a lot, only if you can tell me what number of firmware must i upload for Marshmallow, thx
Last update: So finally, coz im too hurry and dont want wait for your answer :angel:, i just upload from local update first Android 5.1.1. after this 6.0 and all is perfect and working!
My big thanks and kisses goes to you zzztidurvirus, im lucky and still cant beleive that all works, again thx!!

I did once on Win to revert back to Stock from CM12.1 by using img from update.app file. For my case, it's the MM update.app not working, I couldn't flash img files into phone, then I tried to flash files from LP, it worked. I boot into LP ROM and update from there to MM.

Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?

Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
I had faced same issue but get back by using the that method.

Sumea said:
Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?
Click to expand...
Click to collapse
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...

Lulu_568 said:
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...
Click to expand...
Click to collapse
Sadly not, as I tried both running ADB fastboot as admin from administrator command line and I tried three different recovery images from huawei, 6.0 (because the flash went bad during attempt to flash a 4.1EMUI with 6.0 B506 ROM for CHE2-L11) - And it keeps denying the write attempt with the same message. More info on the flash: I tried to TWRP flash from 5.1 rom to the EMUI4.1 6.0 ROM following guide someone made with updateappflasher.zip or something, during the flash the phone just crashed 60% in the bar and after that the phone is boot looping into recovery but it can't do anything. Like said any attempt to flash a stock rom even if a recovery seems to exist when booting VOL+ & POWER at the same time, but it will fail if attempting to do wipe data/factory reset in 40% mark. Forced updater can also be accessed but again, thanks to the firmware situation the phone is in it does not flash anything beyond 5% without crashing and being stuck or just giving an error message outright.
Only thing I might have not have is the right kind of ADB drivers but googling about CHE2-L11 I really cannot find a ADB drivers for this phone for life of me and dealing with windows 10 these days makes it worse. At least it used to be that I was with windows 7, back when I myself unlocked the bootloader of the phone and rooted it myself, I have some memory of that being harsh to deal with too, as I had hard time getting drivers that worked right with the phone etc.
I will check into this... At this point my friend bought a new phone already but I still will try to fix the phone for him since I feel personally pretty bad for pretty big mess I made.
I will also try this with a windows XP machine I have still, it is meant entirely for different things but at times like these it is somewhat nice to have a XP around. At least the darn driver problems are not a problem.
UPDATES:
I unbricked the phone. The stock recovery was intact enough for just a normal dload install of a update.app from huawei - why it did not initially work was probably the USB connection to computer and/or 64gig microSD card my friend had, not being compatible with Huawei's recovery updater. I myself had a 8gig card around which worked and I restored the phone ultimately to a 6.0 official ROM. I also went ahead to root it - and final find really was that the reason why recovery etc. would not flash, was because I wrote "fastboot flash RECOVERY twrp.img" - instead of "fastboot flash recovery twrp.img" - the latter works, and the all caps for "RECOVERY" results in illegal command error - and it was no bigger than that.
Meanwhile even after sorting this all out my friend already ended up buying a new phone so it hurts but I hope some other people find some info here useful.

[GUIDE] Unlock Moto G5S Plus Bootloader [NOOB-FRIENDLY]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Warnings
Doing this will void your warranty.
Your phone will be wiped.
I am not responsible for anything that happens to your phone.
Prerequisites
Your phone
USB Cable
Minimal ADB and Fastboot (Download and install it from here)
A working human brain.
Steps To Unlock Bootloader
First, enable Developer Options. To do this, go to Settings>About Phone> Tap on Built Number multiple times until the toast You are a developer now appears.
Now go to Developer Options in Settings and find and enable OEM Unlock by sliding the button. A warning will appear, just confirm that.
Turn off Your smartphone.
Press Volume Down Button and Power button simultaneously and hold it for few seconds. This will boot your device into fastboot mode.
Double-Click the Minimal ADB and Fastboot icon on your desktop.
Connect your device via USB cable. ( Stock Motorola Cable recommended )
Now go to this website. Read the information given if you wish and click on next button to proceed.
The Page will ask you to sign in, complete the process by signing with your Motorola account or Google Account.
Now go the Command Prompt and type fastboot oem get_unlock_data.
Now a new serial code will appear in your command prompt screen you have to copy the entire code.
Now open this link and copy the code in the tool. Then select the entire code and paste that code in point 6 on Moto require Unlock Tool Website.
Now Click on the I Agree Button a Get Unlock Code will appear on the screen.
Click on the button.
An Unlock Code will appear or will be emailed to you.
Now again go to the Command Prompt screen and type fastboot oem unlock ************. (“************” will replace your unique key)
A warning screen will appear in command just retype the same command and hit enter.
Type fastboot reboot and your phone will reboot.
Done! Your bootloader has been unlocked.

I am getting bad id on bootup. No issues afaik but can someone point out the cause of this?

You forgot 'WINDOWS PC"... or can it be done from Ubuntu?

@edilebe: Certainly you can:
Code:
sudo apt update
sudo apt install android-tools-adb android-tools-fastboot
And then in a terminal:
To access adb :
Code:
adb devices
To access fastboot :
Code:
fastboot devices
Rest of the commands go on as usual.
Broadcasted from Zeta Reticuli

Can i relock the Bootloader without warning boot screen?

Get also Bad Key on Bootscreen but its working

Will doing this disable OTA updates?

I apparently did some step wrong, Id: Bad Key shows on Bootscreen and I can't seem to install TWRP recovery, I get the following error
Code:
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
Also when I run ""fastboot getvar unlocked" I get:
Code:
(bootloader) unlocked: not found
getvar:unlocked FAILED (remote failure)
Maybe I put the wrong key, and now I can't try to unlock it again, what should I do?
I'll greatly appreciate some help

Tewisp said:
I apparently did some step wrong, Id: Bad Key shows on Bootscreen and I can't seem to install TWRP recovery, I get the following error
Code:
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
Also when I run ""fastboot getvar unlocked" I get:
Code:
(bootloader) unlocked: not found
getvar:unlocked FAILED (remote failure)
Maybe I put the wrong key, and now I can't try to unlock it again, what should I do?
I'll greatly appreciate some help
Click to expand...
Click to collapse
It says Your bootloader is locked
u may try from beginning to unlock the bootloader

I dud try to unlock it again, but it won't let me do it, i get a invalid state error
...
(bootloader) invalid boot state
I tried to lock it again just in case, installed factory rom but got the same message.
Is there a way to reset the boot state so i could try again to unlock it?
Thanks for answering by the way, I really appreciate it!

Schrotty35 said:
Get also Bad Key on Bootscreen but its working
Click to expand...
Click to collapse
same here as well. but seems to work fine.
need to proceed to root.

bradleyw801 said:
Will doing this disable OTA updates?
Click to expand...
Click to collapse
I would also like to know the answer. Today I will receive a brand new G5S Plus.
If I unlock the bootloader, install TWRP, decrypt data, and install Magisk, will I still receive OTA updates (including in a few months Oreo)?

gewe said:
I would also like to know the answer. Today I will receive a brand new G5S Plus.
If I unlock the bootloader, install TWRP, decrypt data, and install Magisk, will I still receive OTA updates (including in a few months Oreo)?
Click to expand...
Click to collapse
Installing TWRP will certainly prevent you from getting OTAs. Not sure whether simply unlocking the bootloader will disqualify you as well.

revengineer said:
Installing TWRP will certainly prevent you from getting OTAs. Not sure whether simply unlocking the bootloader will disqualify you as well.
Click to expand...
Click to collapse
I like to have my phone rooted (for things like backup, adblocker).
Since the data partition has to be decrypted for TWRP and Magisk, would the following order make OTA possible?
Create backup
Uninstall Magisk
Flash stock bootloader
Reboot
Let OTA install do its work
Reinstall TWRP
Decrypt data partition
Reinstall Magisk
Restore data partition

gewe said:
I like to have my phone rooted (for things like backup, adblocker).
Since the data partition has to be decrypted for TWRP and Magisk, would the following order make OTA possible?
Create backup
Uninstall Magisk
Flash stock bootloader
Reboot
Let OTA install do its work
Reinstall TWRP
Decrypt data partition
Reinstall Magisk
Restore data partition
Click to expand...
Click to collapse
You need original recovery for sure. Flashing bootloader alone is not sufficient. I believe you also need to lock the bootloader. What I do not know is whether you need signed images of bootloader and/or recovery. The firmware floating around here does not included signed images.

revengineer said:
You need original recovery for sure. Flashing bootloader alone is not sufficient. I believe you also need to lock the bootloader. What I do not know is whether you need signed images of bootloader and/or recovery. The firmware floating around here does not included signed images.
Click to expand...
Click to collapse
At the moment I am trying to create a backup of everything in the state directly after unlocking the bootloader.
I booted TWRP without flashing it, so I can create a backup. However, the backup freezes. I could create a backup of all partitions, except system. When I include system, the backup freezes. I tried three times. It froze at 13%, 21% and 1% (posted this here).

revengineer said:
You need original recovery for sure. Flashing bootloader alone is not sufficient. I believe you also need to lock the bootloader. What I do not know is whether you need signed images of bootloader and/or recovery.
Click to expand...
Click to collapse
You don't need signed images, and you don't need a locked bootloader to install OTA.
Signed images are only necessary for locking bootloader. Nothing else should be concerned.
Locked bootloader is only necessary for passing SafetyNet. Alternative is using Magisk, which pretends to the verifying routine the bootloader would have been locked. Then you should pass SafetyNet again, until the checks SafetyNet do are modified. Then it fails, until Magisk is updated to circumvent these checks also ... it is a cat-and-mouse game, and the author of Magisk (topjohnwu) is a fast one. But there probably always will be times where neither PokemonGo nor Android Pay are running fine. If you want root (my personal belief is, if you own a device, you should have the right to access and modify all data on it), you need to deal with it.
OTA update checks some things (system, recovery, boot, oem, maybe some more) are not modified. Mounting system r/w may suffice to mark the partition as changed and prevent installation of OTA. Failed OTA usually reverts to previous state and gives an error message, then you may read the logs to see what went wrong. Your device stays in a usable state in most cases, at least that's my experience.
Disclaimer: I don't own a G5S Plus, but I'm usually recommending it if I'm asked which mobile is currently a good one to buy. What I write here is to the best of my knowledge applying to many Android, at least most Moto devices. Some behaviours may change when Oreo arrives. Always do a complete backup before any action, and don't forget to treat /data/media in a special way if using Nandroid in twrp.

I can't even unlock the bootloader...:crying:, let alone flashing twrp and rooting my device..... I have no idea where i am going wrong, i followed every step you mentioned. i tried running this command:
c:\adb>fastboot oem get_unlock_data
but it did not work, it showed me an error
---
FAILED < command write failed <No error>>
finished. total time: 0.003s
c:\adb>
Can anyone tell why is this happening? I must have done something wrong otherwise it would not happen.

Unable to unlock Bootloader
Phone is unable to boot and ends up on fastboot screen.
Phone has a locked oem. It says software as modified in fastboot screen. Unable to load bootloader.
While trying to get unlock oem data throws data block read error. What can be done? Is there an alternate way to to get device ID so as to get oem unlock code from Motorola website?
This happened all of a sudden. It was running stock, nothing ever altered.

[GUIDE] UN-BRICK Huawei P8 Lite 2017 (And maybe other devices)

THIS IS NOT GUARANTEED TO WORK! If it does not work, feel free to let me know here and i will do what i can to help, but remember I probably can't help everyone.
IMPORTANT: ON XDA-LABS APP THIS POST IS KINDA BROKEN IDK WHY SO LOAD IT IN BROWSER!!!!
If the guide worked for you, please hit thanks button! If you are generous and want to donate pm me
What this can fix:
When booting, you get this error:
Func NO : 10 (boot image)
Error NO : 2 (load image)
When booting to recovery, you get this error:
Func NO : 11 (recovery image)
Error NO : 2 (load image)
Bootloops
Can't boot into fastboot
Can't boot into recovery for other reasons
Can't boot to system for other reasons
ETC...
First thing first, there really isnt a way to keep your data so expect it all to be gone, unless it is saved on an external sd card. Also, this guide is specifically for the PRA-LX1 model, however it might work with other p8 lite 2017 models and a similar method may work with other huawei phones.
Requirements:
The device boots in to fastboot mode. (If it does not, scroll down to problem 1)
You have a pc with a usb port and fastboot/adb installed
You have a micro usb to usb cable.
Unlocked bootloader and oem unlock.
Micro sd card
Problem 1: Can't boot into fastboot?
Try this:
1. Make sure device is fully powered off
2. Connect device to any pc.
3. Press and hold volume- and power button at the same time until your screen turns on.
If this doesn't work then unfortunately i can't help...
Problem 2: Only fastboot boots, but not recovery or os:
Lets start by flashing TWRP...
If your device was on android nougat (7.x.x) or the rom you were flashing was nougat based then do this:
Download this file:
https://drive.google.com/file/d/1TjNHI9FNdwQS2HphsjGfQCHKephibiKn/view
Boot into fastboot on your phone and open fastboot on your pc
Type: fastboot flash recovery *Nameofrecovery.img*
-----------------------------------------------------------------------------------------------------------------
If your device was on android oreo (8.x.x) or the rom you were flashing was oreo based then do this:
Download this file: https://drive.google.com/file/d/190zqju8ZmwZCzI4WXtujgKLFXvvuWTk8/view?usp=sharing
Boot into fastboot on your phone and open fastboot on your pc
Type: fastboot flash recovery_ramdisk *Nameofrecovery.img*
https://www.mrviking.co.uk/440246340
Problem 3: You can only boot into fastboot and TWRP recovery:
Thats OK! Heres how to restore the phone:
IMPORTANT: THE FILES LINKED HERE ARE ONLY FOR PRA-LX1 DEVICES! If your device has a different model number, or these files did not work for you, follow this guide to get files for your device: https://www.mrviking.co.uk/440246340
This will also update your device to android oreo!
Put the micro sd card in your pc.
On your pc download these files:
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279 (Download 0.3)
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1194/g104/v148634/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...altice_all/update_full_PRA-L11_altice_all.zip
http://update.hicloud.com:8180/TDS/...34/f1/full/public/update_data_full_public.zip
Now Rename update_full_PRA-L11_altice_all.zip to update_all_hw.zip
Also rename update_data_full_public.zip to update_data_public.zip
Put all four files: update.zip, update_all_hw.zip, update_data_public.zip and HuRUpdater_0.3.zip into one folder on the external sdcard.
Take sdcard out of pc and put it into phone.
Boot into twrp tap on mount and select all partitions
Make sure 'mount system read only' is NOT checked.
Go back to twrp home
Go to install, find the huruupdater zip file
Flash ONLY hurupdater, DO NOT FLASH ANY OTHER ZIPS.
Follow instructions on screen.
Reboot to system and wait for the device to boot.
If it didnt boot, dont worry:
Go back to fastboot mode on your phone and pc, and download this file: https://drive.google.com/file/d/1daIos0yagHk9Kg-5hXLDwNYDHjP_N0EM/view?usp=sharing
Flash it with fastboot using:
fastboot flash recovery_ramdisk *Nameofrecovery.img*
now boot into recovery wipe cache wipe date/factory reset reboot to system
If none of this worked, try this last resort. (Likely won't work but it is worth a shot)
Firstly, place your micro sdcard into your pc. Create a folder called 'dload' in the root of it.
Now, locate the firmware files you downloaded from firmware finder.
Open the main update.zip file and extract the 'UPDATE.APP' file to the 'dload' folder in your sdcard.
Place sdcard back in phone
Make sure phone is powered off. (Can't power it off? Unplug anything connected (charger, pc, etc...) and hold the power button until screen goes black)
Hold all three function keys (VOL+,VOL- and POWER) until screen turns on.
Hope it works and wait
If it worked, please hit thanks button! If you want to donate pm me.
If it DID NOT work, post a reply here and either me or someone else will try and help.
Thanks!

tringo24 said:
I've got the same problem - I can boot to TWRP and bootloader.
I've wiped Dalvik/ART Cache, Cache, Data, System and formatted Data
When I try to flash HuRUpdater_0.4.zip I get:
Error finding input device
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/HuRUpdater_0.4.zip'
I've tried copying UPDATE.APP to 'dload' folder on external SD card, and EMUI hangs at 5%.
Is there anything else I can try? What does "Updater process ended with ERROR: 1" actually mean? I've googled it but haven't found anything useful.
Any help would be really appreciated!
Click to expand...
Click to collapse
Top tip - always follow all of the instructions. the version of TWRP listed in the instructions is the only one to use. I was using an incomaptible version. My phone if fixed!

tringo24 said:
I've got the same problem - I can boot to TWRP and bootloader.
I've wiped Dalvik/ART Cache, Cache, Data, System and formatted Data
When I try to flash HuRUpdater_0.4.zip I get:
Error finding input device
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/HuRUpdater_0.4.zip'
I've tried copying UPDATE.APP to 'dload' folder on external SD card, and EMUI hangs at 5%.
Is there anything else I can try? What does "Updater process ended with ERROR: 1" actually mean? I've googled it but haven't found anything useful.
Any help would be really appreciated!
Click to expand...
Click to collapse
Always use TWRP from OP
And if its not working, try Flashing Stock recovery and boot it and do tap some options e.g. reset/ clear cache etc. ( I got my mobile fixed via this method as Internal Memory got corrupted because of incompatible TWRP )

For problem 1 fix : Fully shutdown , connect the phone to via usb to pc , and fast hold down the volume - . Cheers
Edit : or the same : usb , power and volume - till you see the huawei logo , then just hold volume -

Frp and boot locked. dload/UPDATE.APP in fat32 formatted sd still error At 5%. Any way to recovery?

Thank you !!!
You saved my phone :victory:

lupastro82 said:
Frp and boot locked. dload/UPDATE.APP in fat32 formatted sd still error At 5%. Any way to recovery?
Click to expand...
Click to collapse
Force shut down the device (Hold power button) if it is on.
Connect to a pc
Hold down POWER and VOL- buttons untill screen turns on
If you see a screen with an android robot saying FASTBOOT at the top let me know, if not tell me that :good:

MrViking said:
Force shut down the device (Hold power button) if it is on.
Connect to a pc
Hold down POWER and VOL- buttons untill screen turns on
If you see a screen with an android robot saying FASTBOOT at the top let me know, if not tell me that :good:
Click to expand...
Click to collapse
yes, i've.
phone relocked and frp lock. really bad state.
all caused after a magisk installation via magisk manager (this brick my boot).
my giant error, test to install without verify if frp still unlocked and this has caused a giant brick :/
i need a way to bypass-removed frp, and unlock again bootloader.
then, reinstall twrp and recovery my system.
all is in standby cause frp
yes, i know, exist some windows (i use debian) pay app, but 19€ for "just a click" to a device that atm cost about 130€ ... i think isn't a great price.
i really cannot understood why huawei cannot make a real recovery tool.
----
edit, thanks to dc unlocker and some test, now i've bootloader unlocker, but frp remain locked - then, i still cannot fix.
any help? :|

lupastro82 said:
yes, i've.
phone relocked and frp lock. really bad state.
all caused after a magisk installation via magisk manager (this brick my boot).
my giant error, test to install without verify if frp still unlocked and this has caused a giant brick :/
i need a way to bypass-removed frp, and unlock again bootloader.
then, reinstall twrp and recovery my system.
all is in standby cause frp
yes, i know, exist some windows (i use debian) pay app, but 19€ for "just a click" to a device that atm cost about 130€ ... i think isn't a great price.
i really cannot understood why huawei cannot make a real recovery tool.
----
edit, thanks to dc unlocker and some test, now i've bootloader unlocker, but frp remain locked - then, i still cannot fix.
any help? :|
Click to expand...
Click to collapse
I'm exactly in ur same situation
I need ****ing help to unlock frp then i can solve the rest by my own.

lupastro82 said:
yes, i've.
phone relocked and frp lock. really bad state.
all caused after a magisk installation via magisk manager (this brick my boot).
my giant error, test to install without verify if frp still unlocked and this has caused a giant brick :/
i need a way to bypass-removed frp, and unlock again bootloader.
then, reinstall twrp and recovery my system.
all is in standby cause frp
yes, i know, exist some windows (i use debian) pay app, but 19€ for "just a click" to a device that atm cost about 130€ ... i think isn't a great price.
i really cannot understood why huawei cannot make a real recovery tool.
----
edit, thanks to dc unlocker and some test, now i've bootloader unlocker, but frp remain locked - then, i still cannot fix.
any help? :|
Click to expand...
Click to collapse
Have you tried flashing stock recovery img from fastboot?

MrViking said:
Have you tried flashing stock recovery img from fastboot?
Click to expand...
Click to collapse
i can try, but i think cannot work if frp is locked :/
atm, now, on boot i see advice for unlocked bootloader, then access to erecovery (but also if i fix dns with firmware finder dns and check firmware, still failed - and no reset etc).
if i reboot/power on with volume down > green robot with:
Code:
Attention!
Please update system again
Error NO : 10 (boot image) / or
Error NO : 2 (load failed)
if i reboot/power on with both volume button, check dload recovery, but still failed (damned huawei!!!).
now i check to work via fastboot. thanks.
---
[email protected]:~$ sudo $(which fastboot) flash recovery ./Scrivania/twrp-3.2.1-0-twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (4690 KB)...
OKAY [ 0.152s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.158s
[email protected]:~$ sudo $(which fastboot) oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
[email protected]:~$
[email protected]:~$ sudo $(which fastboot) flash recovery_ramdisk ./Scrivania/recovery.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (11204 KB)...
OKAY [ 0.362s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.369s
[email protected]:~$ sudo $(which fastboot) boot ./Scrivania/recovery.img
downloading 'boot.img'...
OKAY [ 0.378s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.381s
[email protected]:~$
Click to expand...
Click to collapse

lupastro82 said:
i can try, but i think cannot work if frp is locked :/
atm, now, on boot i see advice for unlocked bootloader, then access to erecovery (but also if i fix dns with firmware finder dns and check firmware, still failed - and no reset etc).
if i reboot/power on with volume down > green robot with:
Code:
Attention!
Please update system again
Error NO : 10 (boot image) / or
Error NO : 2 (load failed)
if i reboot/power on with both volume button, check dload recovery, but still failed (damned huawei!!!).
now i check to work via fastboot. thanks.
---
Click to expand...
Click to collapse
Wow thats a pretty bad brick. First try to boot to recovery like this:
1. Make sure phone is off.
2. Hold power and volume up until screen goes on.
3. When screen goes on quickly take fingers off buttons.
If it does not work, I think your only hope is to use funky huawei.
Do what this guy did (read the bottom of the first post)
https://forum.xda-developers.com/honor-7x/development/frp-lock-help-to-unbrick-honor-7x-t3769345

lupastro82 said:
yes, i've.
phone relocked and frp lock. really bad state.
all caused after a magisk installation via magisk manager (this brick my boot).
my giant error, test to install without verify if frp still unlocked and this has caused a giant brick :/
i need a way to bypass-removed frp, and unlock again bootloader.
then, reinstall twrp and recovery my system.
all is in standby cause frp
yes, i know, exist some windows (i use debian) pay app, but 19€ for "just a click" to a device that atm cost about 130€ ... i think isn't a great price.
i really cannot understood why huawei cannot make a real recovery tool.
----
edit, thanks to dc unlocker and some test, now i've bootloader unlocker, but frp remain locked - then, i still cannot fix.
any help? :|
Click to expand...
Click to collapse
Can you update to stock through erecovery via wifi? I had my phone frp locked + bl locked + bricked system. eRecovery was the only way out to get into a working system.
The unlock tool that costs too much is b.s and only works if it was locked because of Google Play account (tried it, did not unlock my frp).
After erecovery update and having a system, google play account was also locked because of stock firmware, this time I used the unlock tool. I used firmware finder afterwards for forcing an oreo update (because bl unlocking was grayed out). After oreo update, i enabled bl unlock from dev options and unlocked my bl again through fastboot. frp got unlocked along the way, i forgot when.

i can access in eRecovery, but when i check to download by wifi i still receive: "Getting package info failed" :/
-
via dload (8gb sd in fat 32 with only dload folder and old release UPDATE.APP inside it - but tested with more...) stuck for minuts at 5%, then reboot!

lupastro82 said:
i can access in eRecovery, but when i check to download by wifi i still receive: "Getting package info failed" :/
-
via dload (8gb sd in fat 32 with only dload folder and old release UPDATE.APP inside it - but tested with more...) stuck for minuts at 5%, then reboot!
Click to expand...
Click to collapse
Did you try what I mentioned?
MrViking said:
i can try, but i think cannot work if frp is locked :/
atm, now, on boot i see advice for unlocked bootloader, then access to erecovery (but also if i fix dns with firmware finder dns and check firmware, still failed - and no reset etc).
if i reboot/power on with volume down > green robot with:
Wow thats a pretty bad brick. First try to boot to recovery like this:
1. Make sure phone is off.
2. Hold power and volume up until screen goes on.
3. When screen goes on quickly take fingers off buttons.
If it does not work, I think your only hope is to use funky huawei.
Do what this guy did (read the bottom of the first post)
https://forum.xda-developers.com/honor-7x/development/frp-lock-help-to-unbrick-honor-7x-t3769345
Click to expand...
Click to collapse

sure yes, ill try, and enter in dload mode (but still fail) :/

MrViking said:
THIS IS NOT GUARANTEED TO WORK! If it does not work, feel free to let me know here and i will do what i can to help, but remember I probably can't help everyone.
If the guide worked for you, please hit thanks button! If you are generous and want to donate pm me
What this can fix:
When booting, you get this error:
Func NO : 10 (boot image)
Error NO : 2 (load image)
When booting to recovery, you get this error:
Func NO : 11 (recovery image)
Error NO : 2 (load image)
Bootloops
Can't boot into fastboot
Can't boot into recovery for other reasons
Can't boot to system for other reasons
ETC...
First thing first, there really isnt a way to keep your data so expect it all to be gone, unless it is saved on an external sd card. Also, this guide is specifically for the PRA-LX1 model, however it might work with other p8 lite 2017 models and a similar method may work with other huawei phones.
Requirements:
The device boots in to fastboot mode. (If it does not, scroll down to problem 1)
You have a pc with a usb port and fastboot/adb installed
You have a micro usb to usb cable.
Unlocked bootloader and oem unlock.
Micro sd card
Problem 1: Can't boot into fastboot?
Try this:
1. Make sure device is fully powered off
2. Connect device to any pc.
3. Press and hold volume- and power button at the same time until your screen turns on.
If this doesn't work then unfortunately i can't help...
Problem 2: Only fastboot boots, but not recovery or os:
Lets start by flashing TWRP...
If your device was on android nougat (7.x.x) or the rom you were flashing was nougat based then do this:
Download this file:
https://drive.google.com/file/d/1TjNHI9FNdwQS2HphsjGfQCHKephibiKn/view
Boot into fastboot on your phone and open fastboot on your pc
Type: fastboot flash recovery *Nameofrecovery.img*
-----------------------------------------------------------------------------------------------------------------
If your device was on android oreo (8.x.x) or the rom you were flashing was oreo based then do this:
Download this file: https://drive.google.com/file/d/190zqju8ZmwZCzI4WXtujgKLFXvvuWTk8/view?usp=sharing
Boot into fastboot on your phone and open fastboot on your pc
Type: fastboot flash recovery_ramdisk *Nameofrecovery.img*
https://www.mrviking.co.uk/440246340
Problem 3: You can only boot into fastboot and TWRP recovery:
Thats OK! Heres how to restore the phone:
IMPORTANT: THE FILES LINKED HERE ARE ONLY FOR PRA-LX1 DEVICES! If your device has a different model number, or these files did not work for you, follow this guide to get files for your device: https://www.mrviking.co.uk/440246340
This will also update your device to android oreo!
Put the micro sd card in your pc.
On your pc download these files:
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279 (Download 0.3)
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1194/g104/v148634/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...altice_all/update_full_PRA-L11_altice_all.zip
http://update.hicloud.com:8180/TDS/...34/f1/full/public/update_data_full_public.zip
Now Rename update_full_PRA-L11_altice_all.zip to update_all_hw.zip
Also rename update_data_full_public.zip to update_data_public.zip
Put all four files: update.zip, update_all_hw.zip, update_data_public.zip and HuRUpdater_0.3.zip into one folder on the external sdcard.
Take sdcard out of pc and put it into phone.
Boot into twrp tap on mount and select all partitions
Make sure 'mount system read only' is NOT checked.
Go back to twrp home
Go to install, find the huruupdater zip file
Flash ONLY hurupdater, DO NOT FLASH ANY OTHER ZIPS.
Follow instructions on screen.
Reboot to system and wait for the device to boot.
If it didnt boot, dont worry:
Go back to fastboot mode on your phone and pc, and download this file: https://drive.google.com/file/d/1daIos0yagHk9Kg-5hXLDwNYDHjP_N0EM/view?usp=sharing
Flash it with fastboot using:
fastboot flash recovery_ramdisk *Nameofrecovery.img*
now boot into recovery wipe cache wipe date/factory reset reboot to system
If none of this worked, try this last resort. (Likely won't work but it is worth a shot)
Firstly, place your micro sdcard into your pc. Create a folder called 'dload' in the root of it.
Now, locate the firmware files you downloaded from firmware finder.
Open the main update.zip file and extract the 'UPDATE.APP' file to the 'dload' folder in your sdcard.
Place sdcard back in phone
Make sure phone is powered off. (Can't power it off? Unplug anything connected (charger, pc, etc...) and hold the power button until screen goes black)
Hold all three function keys (VOL+,VOL- and POWER) until screen turns on.
Hope it works and wait
If it worked, please hit thanks button! If you want to donate pm me.
If it DID NOT work, post a reply here and either me or someone else will try and help.
Thanks!
Click to expand...
Click to collapse
Cheers Bruh Thank u so MUCH

Blackblock92 said:
Cheers Bruh Thank u so MUCH
Click to expand...
Click to collapse
No problem! Glad to hear it works

I've made a tutorial 1 day before you ^^
Hello i've made a tutorial on my thread for my solution to unbrick it so if you need to unbrick your phone with a different method
you can use my tutorial it has worked perfecty on my p8 lite 2017 and now he's on oreo
my phone personnaly was totaly broken i flashed some random things on my phone etc this is working 100% cause you are about to clear all the old android system for the new oreo one so for the peoples who got the same problem than me and got stuck
on the fastboot&rescue mode when VOLUME- + POWER for like 5 seconds with the phone off
(for the peoples who can't power off your device you can download the "universal fastboot and ADB tool" app and then click on reboot phone in the fastboot part)
the solution is to :
-Download the rom stock Oreo android 8.0 stechguide.com/huawei-p8-lite-2017-b370-oreo-firmware/
-exctract all files from the HuaweiUpdateExtractor find it on google it's easy just download update.zip
-extract and put the UPDATE.APP in the HuaweiUpdateExtractor
-run srk tool for huawei
-type 000 and press enter
-and now you have to flash all partitions that you have received from HUE commands are here:
[dont worry if some of theese are not working it's because certains commands are not allowed to use and certains commands are out of date :/ but dont worry the phone will boot correctly after ]
Code:
fastboot flash cache CACHE.img
fastboot flash crc CRC.img
fastboot flash curver CURVER.img
fastboot flash dts DTS.img
fastboot flash efi EFI.img
(i'm not putting erecorery imgs cause we cannot touch them it's an ultimate security from os :) )
fastboot flash fastboot FASTBOOT.img
fastboot flash hifi HIFI.img (only if you are the wifi is not working ;) )
fastboot flash kernel KERNEL.img
fastboot flash modem_fw MODEM_FW.img
fastboot flash modemnvm_update MODEMNVM_UPDATE.img
fastboot flash odm ODM.img
fastboot flash package_type PACKAGE_TYPE.img
fastboot flash product PRODUCT.img
fastboot flash ramdisk RAMDISK.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
fastboot flash recovery_vendor RECOVERY_VENDOR.img
fastboot flash sensorhub SENSORHUB.img
fastboot flash system SYSTEM.img
fastboot flash teeos TEEOS.img
fastboot flash trustfirmware TRUSTFIRMWARE.img
fastboot flash vbmeta VBMETA.img
fastboot flash vendor VENDOR.img
fastboot flash verlist VERLIST.img
fastboot flash xloader XLOADER.img
Now you have loader all partitions of an huawei p8 lite 2017 android 8.0 gg !
you just have to make a fastboot reboot to reboot your phone and enjoy !
notes:Everything is working properly after 3 day of use not any missing data some calls bugs but nothing hard
you will loose your TWRP recovery mode AND DO NOT INSTALL ONE OF THEM FOR NOW they are outdated for oreo wait some months (september on some sources)
you will loose all your data and the root (some sites prupose root methods for oreo p8 lite 2017 (and soft root this time :laugh:
idk about the bootloader but i keeped my imei number ^^
Thanks for your time and if anyone got questions i'm still here ^^
RedFiredu29!
btw that my first tutorial tell me if it's good ^^

RedFiredu29 said:
Hello i've made a tutorial on my thread for my solution to unbrick it so if you need to unbrick your phone with a different method
you can use my tutorial it has worked perfecty on my p8 lite 2017 and now he's on oreo
my phone personnaly was totaly broken i flashed some random things on my phone etc this is working 100% cause you are about to clear all the old android system for the new oreo one so for the peoples who got the same problem than me and got stuck
on the fastboot&rescue mode when VOLUME- + POWER for like 5 seconds with the phone off
(for the peoples who can't power off your device you can download the "universal fastboot and ADB tool" app and then click on reboot phone in the fastboot part)
the solution is to :
-Download the rom stock Oreo android 8.0 stechguide.com/huawei-p8-lite-2017-b370-oreo-firmware/
-exctract all files from the HuaweiUpdateExtractor find it on google it's easy just download update.zip
-extract and put the UPDATE.APP in the HuaweiUpdateExtractor
-run srk tool for huawei
-type 000 and press enter
-and now you have to flash all partitions that you have received from HUE commands are here:
[dont worry if some of theese are not working it's because certains commands are not allowed to use and certains commands are out of date :/ but dont worry the phone will boot correctly after ]
Now you have loader all partitions of an huawei p8 lite 2017 android 8.0 gg !
you just have to make a fastboot reboot to reboot your phone and enjoy !
notes:Everything is working properly after 3 day of use not any missing data some calls bugs but nothing hard
you will loose your TWRP recovery mode AND DO NOT INSTALL ONE OF THEM FOR NOW they are outdated for oreo wait some months (september on some sources)
you will loose all your data and the root (some sites prupose root methods for oreo p8 lite 2017 (and soft root this time :laugh:
idk about the bootloader but i keeped my imei number ^^
Thanks for your time and if anyone got questions i'm still here ^^
RedFiredu29!
btw that my first tutorial tell me if it's good ^^
Click to expand...
Click to collapse
That's interesting, never heard of that method!
However there are many good working twrps for oreo, especially the one by Dil3mm4.

MrViking said:
That's interesting, never heard of that method!
However there are many good working twrps for oreo, especially the one by Dil3mm4.
Click to expand...
Click to collapse
Yes i love searching for new solutions on this device but i never heard good unbrick methods for this phone
until our methods ^^

If you read this on XDA labs then please load it in the browser as for some reason lots of text is missing in xda labs.
Thanks ?

XZ3 unlock bootloader [Failed: Command did not succeed] someone resolved?

has anyone solved this problem by unlocking the bootloader? with error: Failed: Command did not succeed
I tried the following bulds:
52.0.A.3.202
52.0.A.8.14
52.0.A.8.25
52.0.A.8.50
Thanks
Bibi
small update:
after updating to 52.0.A.8.50, I made "factory settings" to reset it to the old version.
But when I restart without wifi, I find build 52.0.A.8.50 again
And now the OEM unlock option, which was usable before, has turned gray !! Mystery for me.
Obviously he wants me to update to 52.0.A.8.85 !!!
SOLVED INFORMATION:
I was wrong in writing IMEI of my device, and I put a wrong IMEI in SONY's selector, on its official page, which happens to have given its unlock code all quiet.
then the problem FAILED (remote: 'Command did not succeed')
can be translated as "I don't have the exact unlock code for your phone"
I did this to version 52.0.A.8.131 that I had installed before.

bibibabi said:
has anyone solved this problem by unlocking the bootloader? with error: Failed: Command did not succeed
I tried the following bulds:
52.0.A.3.202
52.0.A.8.14
52.0.A.8.25
52.0.A.8.50
Thanks
Bibi
Click to expand...
Click to collapse
Try .131 vor wait for September
For wait for Q, maybe Sony will remove more DRM TA protection like it did with P

if it was for 2 or 3 days it is not a problem.
but I can't wait until late September.
Let's say that I bought it to be root .. and if I can't do it .. maybe I'll send it back.
Sorry, but are you telling me that they haven't solved even after almost a year?
nobody rooted?
The 3.131 where I can find it and flash arla.
if I find it on XFIRM, what program do I use to put it in my phone?
among other things to set it to factory settings he left me at 52.0.A.8.50, even without wifi.
And nice surprise .. OEM unlock is now deactivated !!!!
it leaves me very mulble

bibibabi said:
if it was for 2 or 3 days it is not a problem.
but I can't wait until late September.
Let's say that I bought it to be root .. and if I can't do it .. maybe I'll send it back.
Sorry, but are you telling me that they haven't solved even after almost a year?
nobody rooted?
The 3.131 where I can find it and flash arla.
if I find it on XFIRM, what program do I use to put it in my phone?
among other things to set it to factory settings he left me at 52.0.A.8.50, even without wifi.
And nice surprise .. OEM unlock is now deactivated !!!!
it leaves me very mulble
Click to expand...
Click to collapse
OEM unlock needs internet via a simcard and a phone restart
There ate many unlocked users using magisk and twrp.
I would recommend to follow the Sony unlocking instructions

MartinX3 said:
OEM unlock needs internet via a simcard and a phone restart
There ate many unlocked users using magisk and twrp.
I would recommend to follow the Sony unlocking instructions
Click to expand...
Click to collapse
Then:
if I do a factory reboot and I don't put the wifi in the first cellphone settings, the OEM unlock option remains gray.
If I do it and I put the wifi in the meantime that is imposed then OEM unlock is usable and therefore can be activated. Correct?
(not that it makes much sense)
However I am installing updates one after the other, and for every update I try the command. (what's also coming to 52.0.A.8.131 which has been expanding in August 2019 (practically these days) and text as MartinX3 advised.

bibibabi said:
Then:
if I do a factory reboot and I don't put the wifi in the first cellphone settings, the OEM unlock option remains gray.
If I do it and I put the wifi in the meantime that is imposed then OEM unlock is usable and therefore can be activated. Correct?
(not that it makes much sense)
However I am installing updates one after the other, and for every update I try the command. (what's also coming to 52.0.A.8.131 which has been expanding in August 2019 (practically these days) and text as MartinX3 advised.
Click to expand...
Click to collapse
It's forced by the mobile providers to check if the simcard allows unlocking
Sony isn't alone here
Unlocking factory resets the phone, too
I did check the unlock box and followed only the Sony instructions and used my generated IMEI code.

MartinX3 said:
It's forced by the mobile providers to check if the simcard allows unlocking
Sony isn't alone here
Unlocking factory resets the phone, too
I did check the unlock box and followed only the Sony instructions and used my generated IMEI code.
Click to expand...
Click to collapse
wait MartinX3,
aren't you saying that you need a simcard inserted in the cell to unlock it right? just the wifi I hope to activate the option.
Look, I followed Sony's directions (which are basically 4 things on the cross)
But it gives me that error: FAILED (remote: 'Command did not succeed')
LIST OF WHAT I DID:
-I do All the appropriate procedures:
-I received the unlock code from the official Sony site
- Platform-tool download and driver
-on the phone sets it basic, active developer commands
- USB DEBUG and UNLOCK OEM tip on the mobile phone menu
- I turn off the phone
-Attack the mobile in fastboot mode (blue light)
-then in the devices and printers, which appears in new one when I plug in the cel in fastboot mode, I update the driver of the device appeared, android studio).
-I do the ADB command -> fastboot devices
**and ai read the model serial
- Then enter the code to unlock the phone: fastboot oem unlock 0xCODESEIAL
**and I get this: FAILED (remote: 'Command did not succeed')
----------------------------------------------------------------------------
(I tried the .107, now I try with .131 as you recommended me)
UPDATE:
badly wrong, even with the 52.0.A.8.131 DOES NOT, same identical error.
Sony in his guide makes it so easy, but neither does he make the possible mistakes.
And that I can't find an explanation for this specific error.

bibibabi said:
wait MartinX3,
aren't you saying that you need a simcard inserted in the cell to unlock it right? just the wifi I hope to activate the option.
Look, I followed Sony's directions (which are basically 4 things on the cross)
But it gives me that error: FAILED (remote: 'Command did not succeed')
LIST OF WHAT I DID:
-I do All the appropriate procedures:
-I received the unlock code from the official Sony site
- Platform-tool download and driver
-on the phone sets it basic, active developer commands
- USB DEBUG and UNLOCK OEM tip on the mobile phone menu
- I turn off the phone
-Attack the mobile in fastboot mode (blue light)
-then in the devices and printers, which appears in new one when I plug in the cel in fastboot mode, I update the driver of the device appeared, android studio).
-I do the ADB command -> fastboot devices
**and ai read the model serial
- Then enter the code to unlock the phone: fastboot oem unlock 0xCODESEIAL
**and I get this: FAILED (remote: 'Command did not succeed')
----------------------------------------------------------------------------
(I tried the .107, now I try with .131 as you recommended me)
UPDATE:
badly wrong, even with the 52.0.A.8.131 DOES NOT, same identical error.
Sony in his guide makes it so easy, but neither does he make the possible mistakes.
And that I can't find an explanation for this specific error.
Click to expand...
Click to collapse
Sadly I'm out of ideas
Hoping here or at https://talk.sonymobile.com/t5/Xper...er-Failed-Command-did-not-succeed/m-p/1387453 someone will answer you

MartinX3 said:
Sadly I'm out of ideas
Hoping here or at https://talk.sonymobile.com/t5/Xper...er-Failed-Command-did-not-succeed/m-p/1387453 someone will answer you
Click to expand...
Click to collapse
I found out!
then:
turn and turn, and check IMEI of the cell I used.
I was wrong in writing IMEI, and I put the wrong IMEI in SONY's selector, on its official page, which happens to have given its unlock code all quiet.
then the problem FAILED (remote: 'Command did not succeed')
can be translated as "I don't have the exact unlock code for your phone"
I did this to version 52.0.A.8.131 that I had installed before.
well OTHER PROBLEM!
it doesn't flash me twrp
with this error:
Sending 'recovery' (34192 KB) OKAY [0.737s]
Writing 'recovery' FAILED (remote: 'No such partition.')
I'm looking at guides.

bibibabi said:
I found out!
then:
turn and turn, and check IMEI of the cell I used.
I was wrong in writing IMEI, and I put the wrong IMEI in SONY's selector, on its official page, which happens to have given its unlock code all quiet.
then the problem FAILED (remote: 'Command did not succeed')
can be translated as "I don't have the exact unlock code for your phone"
I did this to version 52.0.A.8.131 that I had installed before.
well OTHER PROBLEM!
it doesn't flash me twrp
with this error:
Sending 'recovery' (34192 KB) OKAY [0.737s]
Writing 'recovery' FAILED (remote: 'No such partition.')
I'm looking at guides.
Click to expand...
Click to collapse
Nice that it worked
Oh, the error is easy
It indicates "you didn't read the instructions' [emoji14]

MartinX3 said:
Nice that it worked
Oh, the error is easy
It indicates "you didn't read the instructions' [emoji14]
Click to expand...
Click to collapse
No means I'm blind as a mole, for a number
But now, following the instructions of the root of the zx3 H8416, they don't work

bibibabi said:
No means I'm blind as a mole, for a number
But now, following the instructions of the root of the zx3 H8416, they don't work
Click to expand...
Click to collapse
"Fastboot flash recovery twrp.IMG" aren't definitely the instructions dear blind mole

MartinX3 said:
"Fastboot flash recovery twrp.IMG" aren't definitely the instructions dear blind mole
Click to expand...
Click to collapse
Leave me pending? this is the command they say they use.
HTML:
fastboot flash recovery twrp.img
I know you can flash even with androxyed flash, but when you do ... it doesn't start anymore (the white sony script remained) ...
and I went a bit panicked !!!!
doing the Flash of the original firware it has been restored, but returned to the point of before. Install twrp.twp or superSU in short, activate the ROOT
the writing that says that the bootloader is corrupt, at start each time the cell terrifies me every time I see it. BRRRR

bibibabi said:
Leave me pending? this is the command they say they use.
HTML:
fastboot flash recovery twrp.img
I know you can flash even with androxyed flash, but when you do ... it doesn't start anymore (the white sony script remained) ...
and I went a bit panicked !!!!
doing the Flash of the original firware it has been restored, but returned to the point of before. Install twrp.twp or superSU in short, activate the ROOT
the writing that says that the bootloader is corrupt, at start each time the cell terrifies me every time I see it. BRRRR
Click to expand...
Click to collapse
If you corrupted the firmware, please use xperifirm & newflasher from XDA to reflash the firmware
Instructions are in the ROM section of the xz3 on XDA

MartinX3 said:
If you corrupted the firmware, please use xperifirm & newflasher from XDA to reflash the firmware
Instructions are in the ROM section of the xz3 on XDA
Click to expand...
Click to collapse
yes yes, I know that with the flash mode they can reinstall the official system.
there is also the official sony flastool called EMMA. which I have to say is not bad.
Now the system is ok, official.
I'm looking for ways to install root or twrp from a phone

bibibabi said:
yes yes, I know that with the flash mode they can reinstall the official system.
there is also the official sony flastool called EMMA. which I have to say is not bad.
Now the system is ok, official.
I'm looking for ways to install root or twrp from a phone
Click to expand...
Click to collapse
Should be impossible without a computer for initial installation

MartinX3 said:
Should be impossible without a computer for initial installation
Click to expand...
Click to collapse
yes, it's like you say.
Looking at the guides, I think the right solution for me is an official firmware kernel that has both twrp and magikic inside.
I found a guide of 2017, but the official firmware files have changed, I do not find myself in the guide.
Can't you recommend something to me, or the keywords to look for on this theme?
I wanted to learn to change the firmware for future root myself.

bibibabi said:
yes, it's like you say.
Looking at the guides, I think the right solution for me is an official firmware kernel that has both twrp and magikic inside.
I found a guide of 2017, but the official firmware files have changed, I do not find myself in the guide.
Can't you recommend something to me, or the keywords to look for on this theme?
I wanted to learn to change the firmware for future root myself.
Click to expand...
Click to collapse
I have sadly no time to do it and can only recommend the ROM section for the XZ3 in XDA (twrp)

MartinX3 said:
I have sadly no time to do it and can only recommend the ROM section for the XZ3 in XDA (twrp)
Click to expand...
Click to collapse
Each has its own spaces. do not worry. Meanwhile, I've made progress !!!
You know that after unblock I had problems installing TWRP.Practically the command gave error.
I found the solution around.
The guides say:
HTML:
fastboot flash recovery twrp.img
but I have this error:
HTML:
FAILED (remote: 'No such partition.')
basically in the version of android 9 they created 2 partitions and practically the recovery was divided into recovery ramdisck, recovery ...
They explain it HERE
In practice some new systems (I did not understand if the kelner or just the boot), do not have the active recovery partition and then flash the recovery, it is like doing it on a folder that does not exist.
So they recommend starting the mini twrp operating system via adb.
And through this active twrp (but not installed), install twrp itself, and then the apps for the root.
So, I use the new command that starts twrp without installing it:
HTML:
fastboot boot twrp.img
then it takes 3 minutes with the word sony and then I see twrp
I make a twrp backup for security
then from there I install .img used for the command and moved to the phone while twrp is active and I do install, install img and select partition recovery ramdisck.
I tried to install also in the boot partition, which shows in the list.
and apparently the cell works correctly anyway.
In the guides they never say in which partition to put.
Meanwhile there are install magisk 18.1 (and a zip called permissive; I don't know what it is but from the name it seems useful).
Well, everything is smooth and without errors.
Restart, I use the twrp access commands (which in the case of xz3 are volume DOWN + prower simultaneously while the phone is still off).
And the recovery is there, but it has the usual tuoch problem that doesn't work.
I see the twrp main screen, which seems to work correctly, but the touch ...
I then checked the root, via the app downloadable on the cell from the magisk manager repository and marks the correct root.
Obviously I don't update anything about 19.3, which you wrote in other places that is corrupt.
: Sciocco: NOW! I just have to fix twrp and my epic quest will be over.
(although I'm worried about flashing a hypothetical Q that's coming out)
can you give me some inspiration for the touch that doesn't work twrp?

bibibabi said:
Each has its own spaces. do not worry. Meanwhile, I've made progress !!!
You know that after unblock I had problems installing TWRP.Practically the command gave error.
I found the solution around.
The guides say:
HTML:
fastboot flash recovery twrp.img
but I have this error:
HTML:
FAILED (remote: 'No such partition.')
basically in the version of android 9 they created 2 partitions and practically the recovery was divided into recovery ramdisck, recovery ...
They explain it HERE
In practice some new systems (I did not understand if the kelner or just the boot), do not have the active recovery partition and then flash the recovery, it is like doing it on a folder that does not exist.
So they recommend starting the mini twrp operating system via adb.
And through this active twrp (but not installed), install twrp itself, and then the apps for the root.
So, I use the new command that starts twrp without installing it:
HTML:
fastboot boot twrp.img
then it takes 3 minutes with the word sony and then I see twrp
I make a twrp backup for security
then from there I install .img used for the command and moved to the phone while twrp is active and I do install, install img and select partition recovery ramdisck.
I tried to install also in the boot partition, which shows in the list.
and apparently the cell works correctly anyway.
In the guides they never say in which partition to put.
Meanwhile there are install magisk 18.1 (and a zip called permissive; I don't know what it is but from the name it seems useful).
Well, everything is smooth and without errors.
Restart, I use the twrp access commands (which in the case of xz3 are volume DOWN + prower simultaneously while the phone is still off).
And the recovery is there, but it has the usual tuoch problem that doesn't work.
I see the twrp main screen, which seems to work correctly, but the touch ...
I then checked the root, via the app downloadable on the cell from the magisk manager repository and marks the correct root.
Obviously I don't update anything about 19.3, which you wrote in other places that is corrupt.
: Sciocco: NOW! I just have to fix twrp and my epic quest will be over.
(although I'm worried about flashing a hypothetical Q that's coming out)
can you give me some inspiration for the touch that doesn't work twrp?
Click to expand...
Click to collapse
Please use the August .131 firmware and my matching stock twrp

P9 Lite [VNS-l31] [HARD BRICKED] [CORRUPT PARTITIONS] EDL UNBRICKING

Hi,
Hoping to get some help from the Huawei Dev community here on XDA.
POPPING MY CHERRY - 1st HARD-BRICKED DEVICE
Doesn't feel very good!!!!
So I was trying to upgrade my old VNS-L31 from Android 6 to 7 or install a custom ROM due to some apps no longer having support for Android 6.
Dload method failed.
Was on C16 somehow (supposed to be on C185). Tried to flash new OEM_info which is where the problems started. Initially my DATA partition got corrupted, not sure exactly where it happend but I suspect it happend while I was trying to fastboot flash the newer Android 7 stock system cust etc images.
No TWRP posted here on XDA worked - tried 9 of em NON WORKED
So I was stuck at 3.0.2-0 that worked from SRKToolkit way back when I first rooted it.
After the data partition get corrupted it all went down hill. Nothing worked to fix the partition.
No Dload method worked (finding stock roms for this thing proved a massive challenge so I was stuck with trying what I could find)
After flashing new C432 oem_info and custom.bin I I got bootloop and tried the following stock roms with dload
- C4432B172
- C432B413
- C432B130
- C432B172
Non worked, complaining about incompatible versions.
Stock recovery also couldn't fix the data partition
eRecovery couldn't find a ROM ( I think cuz huawei doesn't have the ROMs on their servers anymore (neither C185, C16 or C432 got a ROM on eRecovery).
With no other options remaining I was forced to try and fix the data partition manually ( this is where the device got hard bricked ).
So I used parted and deleted the userdata partition -> re-created it and added it to the /etc/fstab.
Using this post as a reference: [DEV][ Expand System Partition To 4GB - P9 Lite ]
Note: parted said the primary GPT partition table was corrupt. It said the backup GPT partition table would be used.
As soon as I rebooted from TWRP I got black screen everywhere and the only mode the phone would go into was fastboot.
Tried everything there to get the device back but with a corrupt partition table I knew I was farting into the wind.
After that failed I knew this device was basically dead and the ONLY, ONLY way to unbrick it would be to try EDL test points.
Ok so I got the phone open and got into EDL Qualcomm HS-USB QDLoader 9008 mode (OLD mode it seems -> No storage device detected).
PotatoNV detects the device now as a EVA-L19C432B166 (I have no idea how that happend, I have no ROMs that has that BUILD).
I have QPST and QFIL but lack the programmer file and basic knowledge of how this type of flashing works.
So this is where I'm at - I think I might as well throw this thing in the trash bin but since I got the opportunity now to work with QFIL and try everything to unbrick this thing and gain some knowledge about how EDL mode works I'm thinking I might as well play around with it.
Any advise/Help with this would be GREATLY appreciated.
PS: interestingly PotatoNV generated a NEW unlock code for me now - cant believe I payed DC-unlocker to get me an unlock code for this phone.
So PotatoNV generated a new code not the old I had - and it worked to unlock the bootloader
@-Alf-

gh0stza said:
Hi,
Hoping to get some help from the Huawei Dev community here on XDA.
POPPING MY CHERRY - 1st HARD-BRICKED DEVICE
Doesn't feel very good!!!!
So I was trying to upgrade my old VNS-L31 from Android 6 to 7 or install a custom ROM due to some apps no longer having support for Android 6.
Dload method failed.
Was on C16 somehow (supposed to be on C185). Tried to flash new OEM_info which is where the problems started. Initially my DATA partition got corrupted, not sure exactly where it happend but I suspect it happend while I was trying to fastboot flash the newer Android 7 stock system cust etc images.
No TWRP posted here on XDA worked - tried 9 of em NON WORKED
So I was stuck at 3.0.2-0 that worked from SRKToolkit way back when I first rooted it.
After the data partition get corrupted it all went down hill. Nothing worked to fix the partition.
No Dload method worked (finding stock roms for this thing proved a massive challenge so I was stuck with trying what I could find)
After flashing new C432 oem_info and custom.bin I I got bootloop and tried the following stock roms with dload
- C4432B172
- C432B413
- C432B130
- C432B172
Non worked, complaining about incompatible versions.
Stock recovery also couldn't fix the data partition
eRecovery couldn't find a ROM ( I think cuz huawei doesn't have the ROMs on their servers anymore (neither C185, C16 or C432 got a ROM on eRecovery).
With no other options remaining I was forced to try and fix the data partition manually ( this is where the device got hard bricked ).
So I used parted and deleted the userdata partition -> re-created it and added it to the /etc/fstab.
Using this post as a reference: [DEV][ Expand System Partition To 4GB - P9 Lite ]
Note: parted said the primary GPT partition table was corrupt. It said the backup GPT partition table would be used.
As soon as I rebooted from TWRP I got black screen everywhere and the only mode the phone would go into was fastboot.
Tried everything there to get the device back but with a corrupt partition table I knew I was farting into the wind.
After that failed I knew this device was basically dead and the ONLY, ONLY way to unbrick it would be to try EDL test points.
Ok so I got the phone open and got into EDL Qualcomm HS-USB QDLoader 9008 mode (OLD mode it seems -> No storage device detected).
PotatoNV detects the device now as a EVA-L19C432B166 (I have no idea how that happend, I have no ROMs that has that BUILD).
I have QPST and QFIL but lack the programmer file and basic knowledge of how this type of flashing works.
So this is where I'm at - I think I might as well throw this thing in the trash bin but since I got the opportunity now to work with QFIL and try everything to unbrick this thing and gain some knowledge about how EDL mode works I'm thinking I might as well play around with it.
Any advise/Help with this would be GREATLY appreciated.
PS: interestingly PotatoNV generated a NEW unlock code for me now - cant believe I payed DC-unlocker to get me an unlock code for this phone.
So PotatoNV generated a new code not the old I had - and it worked to unlock the bootloader
@-Alf-
Click to expand...
Click to collapse
Hello,
in fastboot mode (if possible) run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post results.

-Alf- said:
Hello,
in fastboot mode (if possible) run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post results.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Product model should be VNS-L31 - And it was before the partition got corrupted
EVA-L19 I think is the plain P9
Vendor country was C16 and then I flashed C432 (hw/eu) through TWRP
Ah **** ... just realized the OEMInfo I flashed was the L19 ( attaching it ) - the device worked after the flash though but it couldn't have helped with the dload version mismatch.
L19c432b182-oeminfo-custom.bin_flash.zip

gh0stza said:
View attachment 5723589
Product model should be VNS-L31 - And it was before the partition got corrupted
EVA-L19 I think is the plain P9
Vendor country was C16 and then I flashed C432 (hw/eu) through TWRP
Ah **** ... just realized the OEMInfo I flashed was the L19 ( attaching it ) - the device worked after the flash though but it couldn't have helped with the dload version mismatch.
L19c432b182-oeminfo-custom.bin_flash.zip
Click to expand...
Click to collapse
Try the following:
1. Download vns-l31c432b370
Link (2 .zip files - update.zip and update_data_full_VNS-L31_hw_eu.zip)
2. Download oeminfo l31c432
Link
3. Install TWRP 3.0.2.0, flash C432 oeminfo.zip file, DON'T REBOOT, go back in TWRP menu, flash update.zip , go back again and flash update_data_full_VNS-L31_hw_eu.zip.
4. In TWRP select Reboot recovery and do Factory reset.
I can't give you any better advice.

-Alf- said:
Try the following:
1. Download vns-l31c432b370
Link (2 .zip files - update.zip and update_data_full_VNS-L31_hw_eu.zip)
2. Download oeminfo l31c432
Link
3. Install TWRP 3.0.2.0, flash C432 oeminfo.zip file, DON'T REBOOT, go back in TWRP menu, flash update.zip , go back again and flash update_data_full_VNS-L31_hw_eu.zip.
4. In TWRP select Reboot recovery and do Factory reset.
I can't give you any better advice.
Click to expand...
Click to collapse
And I really appreciate it but I only have black screen rememeber...
No recovery, no eRecovery, no TWRP no nothing. The PC detects a fastboot device and I can send fastboot commands but that's it, apart from the EDL mode.
So whatever fix, it has to happen either in fastboot or EDL.
I need a programmer firehose file and some advise on how to use QFIL properly, or a solution in fastboot ( which I think is unlikely )
Thanks @-Alf=

gh0stza said:
And I really appreciate it but I only have black screen rememeber...
Click to expand...
Click to collapse
My bad, sorry

-Alf- said:
My bad, sorry
Click to expand...
Click to collapse
But ur spot on with those files man.
Wish I spoke to you before I bricked the damn thing.
This is all on me ( and a little bit on Huawei for making an easy-brickable-device )
I knew messing around with the partition table would be dangerous, but I had no other options left after the primary GPT partition table got corrupt. Or atleast I thought I had no other choice, in retro-spect I would have tried a thousand other things before I modified the partition table directly.
Let this be a lesson for anyone else stumbling unto this thread...
It just feels like such a waste... There is nothing physically wrong with the device but almost zero chance of reviving it without the programmer files from huawei ( which I will prob never get )
PS: Maybe I can use some other firehose file...
Take a look at this site I found: https://www.leakite.com/?s=Qualcomm+Programmer
Maybe one of these programmer files are similar enough to use???
Anyone got an idea?

gh0stza said:
and a little bit on Huawei for making an easy-brickable-device
Click to expand...
Click to collapse
Huawei devices seem to be fairly indestructible, as long as the Bootloader is open, imo. If you don't mix apples and oranges, of course .

-Alf- said:
Huawei devices seem to be fairly indestructible, as long as the Bootloader is open, imo. If you don't mix apples and oranges, of course .
Click to expand...
Click to collapse
Well interestingly, almost every time I dload'ed some firmware (even though it failed) it relocked my bootloader.
If I didn't have a bootloader unlock key, I would have had troubles much earlier.
Note: This is why I am very sceptical about paying DC-Unlocker a bunch of money to unlock my bootloader without giving me a key (That's the only way according to them on the P20 Pro - I assume they use some exploit on android 7-9; 10+ they say is not possible).
Then again... after I opened it up and used test points (for the first time, mind you) I discovered this model's bootloader is soooooo damn easy to crack with PotatoNV. Even HARD-BRICKED PotatoNV still gave me an unlock key.
Plus the back cover basically just pops right off -> 8 screws and 2 connectors later and it's unlocked
Credit to: Andrey Smirnoff
This makes me wonder if the P20 Pro would be just as easy ( I have one of those too, that I haven't been able to unlock yet )

I've messed around with the system partition table the first time and also messed up. Then tried to repair it by flashing the stock firmware, thinking it would reconstruct/replace my bad changes to /system and it only made it lock the bootloader. Thankfully PotatoNV indeed came to the rescue. So after flashing some different firmwares/twrp eventually it booted to the stock rom and I was then able to expand the system partition and rock the LOS on the vns-l31.
So I indeed feel for you when you're going down this lane. Unfortunately, I don't have much to add but I'm genuinely curious how you can fix the phone out of this situation. If you ever find a solution that wasn't posted here I'd appreciate if you could then give us an update on how you solved it. This is the kind of stuff I'd love to learn.

Phantom Thief said:
I've messed around with the system partition table the first time and also messed up. Then tried to repair it by flashing the stock firmware, thinking it would reconstruct/replace my bad changes to /system and it only made it lock the bootloader. Thankfully PotatoNV indeed came to the rescue. So after flashing some different firmwares/twrp eventually it booted to the stock rom and I was then able to expand the system partition and rock the LOS on the vns-l31.
So I indeed feel for you when you're going down this lane. Unfortunately, I don't have much to add but I'm genuinely curious how you can fix the phone out of this situation. If you ever find a solution that wasn't posted here I'd appreciate if you could then give us an update on how you solved it. This is the kind of stuff I'd love to learn.
Click to expand...
Click to collapse
Hi Phantom,
Thnx for the suggestion, will try flashing a couple img's later and hope for the best.
Else I'm still convinced I can fix it through EDL.
Will give updates here if I can achieve anything.
If you get any info on flashing through EDL, do let me know please.

gh0stza said:
This makes me wonder if the P20 Pro would be just as easy ( I have one of those too, that I haven't been able to unlock yet )
Click to expand...
Click to collapse
As usual with my luck: https://en.wikipedia.org/wiki/Huawei_P20
The P20 Pro(CLT-L09) has a Kirin 970 SoC, not supported by PotatoNV.
So HCU-Client it is...
Which also means downgrading from EMUI 12.0.0 - here we go again!

-Alf- said:
Try the following:
1. Download vns-l31c432b370
Link (2 .zip files - update.zip and update_data_full_VNS-L31_hw_eu.zip)
2. Download oeminfo l31c432
Link
3. Install TWRP 3.0.2.0, flash C432 oeminfo.zip file, DON'T REBOOT, go back in TWRP menu, flash update.zip , go back again and flash update_data_full_VNS-L31_hw_eu.zip.
4. In TWRP select Reboot recovery and do Factory reset.
I can't give you any better advice.
Click to expand...
Click to collapse
Thank you very much