[HELP THREAD] Ask any questions [NOOB FRIENDLY] - Honor 4x Questions & Answers

Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!​
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing

Honor 4x hanged (in some Indian kitkat version, not rooted) and after restart it is in bootloop. Honor logo appears then blue light starts to appear then restart.
Recovery mode and dload update not working.
After unlocking bootloader tried fastboot -w, still in bootloop.
Extracted Lollipop, Marshmallow, Kitkat - B161, B126 and flashed in fastboot. Possible to flash only recovery, boot, userdata & system. For others - failed : remote command not allowed. After flashing no change, still in bootloop.
Tried to boot to recovery from fastboot boot
- for lollipop and marshmallow recoveries it says "dtb not found"
- others including twrp, cm it is in bootloop.
Out of warranty.
Need help.

oppili said:
Honor 4x hanged (in some Indian kitkat version, not rooted) and after restart it is in bootloop. Honor logo appears then blue light starts to appear then restart.
Recovery mode and dload update not working.
After unlocking bootloader tried fastboot -w, still in bootloop.
Extracted Lollipop, Marshmallow, Kitkat - B161, B126 and flashed in fastboot. Possible to flash only recovery, boot, userdata & system. For others - failed : remote command not allowed. After flashing no change, still in bootloop.
Tried to boot to recovery from fastboot boot
- for lollipop and marshmallow recoveries it says "dtb not found"
- others including twrp, cm it is in bootloop.
Out of warranty.
Need help.
Click to expand...
Click to collapse
Oh ****, that seems like a frustrating situation. What made the device mess up so much? Have you gone to service centres?
Regards,
PoseidonKing

Not tried to flash or root. It just hanged while using.
Service centre said board gone (as always). MTK devices have a factory mode through which we can check working of all board parts. I did not find any way for this.

oppili said:
Not tried to flash or root. It just hanged while using.
Service centre said board gone (as always). MTK devices have a factory mode through which we can check working of all board parts. I did not find any way for this.
Click to expand...
Click to collapse
Sorry bro, can't help you out over here in this situation.... Best of Luck regarding your device. I would suggest pm'ing a forum moderator for your issue
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing

HELP.!!Back to Stock Rom ????
I am struggling like anything to go back to stock rom. I am using Honor 4x Che1-L04 snapdragon. Pls send a link where can i find the instructions to do this. Or Better U expain.
EDIT:
Roll back to EMUI 4.0 success. Used the Hauwei update extractor and used CMD. Anyhow THANKS

NEW Problem:
How to enable ADOPTED STORAGE in honor 4x che1-L04 snapdragon edition.
In Xda they mentioned only about the kirin processor version.
Help!!!!!!!!!!

balongc52b311 after failing kangvip 6.7.1
hey there. will tell you my experience with failing to flashing kangvip 6.7.1 due to wiping problem
i wiped my cache, data, system even internal storage and yet failed to flashing kangvip 6.7.1 4 custom rom due to "cust" folder unable to mount giving me this:
error 1 can't mount /cust (Invalid argument)
so after failing to mount that folder and even deleting it by mistake,i got a new error:
error 1 can't mount cust no such file or directory
i lost hope and let my my honor 4x normally boot but it took too long and i was determined its stuck on bootloop :cyclops:
i woke up today finding it on 5% battery and giving me that first time setup as if all i did was a factory format BUT all in chinese. checked the build number and it was balongc52b311.
i tried mounting "cust" folder to r/w and rebooted into bootloader but it gave me the same first error. i tried deleting the folder and then rebooting into recovery and it gave me the 2nd error. created the folder "/cast" and then rebooted into recovery and it gave me the same first problem that the folder can't mount EVENTHO it was mounted successfully right before i rebooted into recovery (did this 3 times to make sure)
did some researching and found a solution for honor 4c http://forum.xda-developers.com/honor-4x/help/huawei-honor-4x-balong-hi6210sft-fixed-t3324335 or two BUT both for lolllipop and i'm marshmallow.
i'm already halfway at the method i mentioned above but i stopped after i realized it was for lollipop. i rooted my mobile and changed my build number to "Che2-L11C636B330". worth to mention that my model number remained already the same "Che2-L11".
the cust folder error is still there whenever i go to the bootloader
now i have no idea what to do, what firmware to download and if i have to downgrade first to lollipop and then upgrade to marshmallow again...
my marshmallow version was the middle east final version before this balong happened: Che2-L11C185B561 and i would like to go back to it again.. thank you in advance ( :
###*UPDATED BELOW*
fixed my problem trying the method here http://forum.xda-developers.com/honor-8/help/honor-8-rooted-twrp-modaco-rom-unable-t3462039/page2
>>>>worth to mention that i flashed my oeminfo for my UPDATE.APK REGION before flashing the extracted files from UPDATE.APP "wasn't mentioned in that method"
now i'm back to my original marshmallow version "middle east". good luck people.

abdurrahmanzaki said:
hey there. will tell you my experience with failing to flashing kangvip 6.7.1 due to wiping problem
i wiped my cache, data, system even internal storage and yet failed to flashing kangvip 6.7.1 4 custom rom due to "cust" folder unable to mount giving me this:
error 1 can't mount /cust (Invalid argument)
so after failing to mount that folder and even deleting it by mistake,i got a new error:
error 1 can't mount cust no such file or directory
i lost hope and let my my honor 4x normally boot but it took too long and i was determined its stuck on bootloop :cyclops:
i woke up today finding it on 5% battery and giving me that first time setup as if all i did was a factory format BUT all in chinese. checked the build number and it was balongc52b311.
i tried mounting "cust" folder to r/w and rebooted into bootloader but it gave me the same first error. i tried deleting the folder and then rebooting into recovery and it gave me the 2nd error. created the folder "/cast" and then rebooted into recovery and it gave me the same first problem that the folder can't mount EVENTHO it was mounted successfully right before i rebooted into recovery (did this 3 times to make sure)
did some researching and found a solution for honor 4c http://forum.xda-developers.com/honor-4x/help/huawei-honor-4x-balong-hi6210sft-fixed-t3324335 or two BUT both for lolllipop and i'm marshmallow.
i'm already halfway at the method i mentioned above but i stopped after i realized it was for lollipop. i rooted my mobile and changed my build number to "Che2-L11C636B330". worth to mention that my model number remained already the same "Che2-L11".
the cust folder error is still there whenever i go to the bootloader
now i have no idea what to do, what firmware to download and if i have to downgrade first to lollipop and then upgrade to marshmallow again...
my marshmallow version was the middle east final version before this balong happened: Che2-L11C185B561 and i would like to go back to it again.. thank you in advance ( :
###*UPDATED BELOW*
fixed my problem trying the method here http://forum.xda-developers.com/honor-8/help/honor-8-rooted-twrp-modaco-rom-unable-t3462039/page2
>>>>worth to mention that i flashed my oeminfo for my UPDATE.APK REGION before flashing the extracted files from UPDATE.APP "wasn't mentioned in that method"
now i'm back to my original marshmallow version "middle east". good luck people.
Click to expand...
Click to collapse
Thanks on the update about your success on restoring your phone. Surely some poor soul will get along the same problem and your post will help him out. Sorry for the late reply btw.
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing

How to Root my honor 4x Che2-L11?
Hi everyone, I'm noob, so I need a step to step guide if there's such a thing
my android version is 6.0 and EMUI 4.0
I have bootloader code for unlocking the phone, thanks in advance guys, also happy new year :good:

Phone Honor 4x (che1-L04) Stuck in fastboot mode
My phone is stuck in fastboot mode. Couldn't get the bootloader unlock key online as it requires the product id which can be obtained by dialing a number which isn't possible. I have requested directly from the customer care number and the official chat portal as well but its been more than a week and still they are asking for 24 working hours. Is there any alternative method of getting the key or atleast the Product ID?
Model name :Che1-L04
Stuck in Fastboot & Rescue mode with the bootloader locked.

I got unlock key after 12 days. Honor 4x hanged after restart it is in bootloop.
3 button sd card update not working ?

oppili said:
I got unlock key after 12 days. Honor 4x hanged after restart it is in bootloop.
3 button sd card update not working ?
Click to expand...
Click to collapse
No the update.app isnt working I guess because I have already flashed the CM13 recovery image with the bootloader locked. However, I recieved the bootloader key yesterday from the email but when I tried unlocking by the fastboot command it said it is an invalid or wrong key. Is there any other way to take my phone back to stock condition atleast without actually unlocking the Bootloader?

Princeshubh said:
No the update.app isnt working I guess because I have already flashed the CM13 recovery image with the bootloader locked. However, I recieved the bootloader key yesterday from the email but when I tried unlocking by the fastboot command it said it is an invalid or wrong key. Is there any other way to take my phone back to stock condition atleast without actually unlocking the Bootloader?
Click to expand...
Click to collapse
1. Try "fastboot continue" it will directly boot without going to recovery.
2. If fastboot flash works flash recovery of the firmware installed in phone before bootloop.
3. If still not works flash boot, system, recovery (in this order) of firmware installed before bootloop.
Confirm unlock key with customer care if it is still locked.

I wanna know is there any other method to install xposed framework since the normal installation is not working for me.
Using Honor 4x Che1-l04 running on (stock ROM) Android marshmallow 6.0.1, have TWRP custom recovery and is rooted.

SumitGupta2442 said:
I wanna know is there any other method to install xposed framework since the normal installation is not working for me.
Using Honor 4x Che1-l04 running on (stock ROM) Android marshmallow 6.0.1, have TWRP custom recovery and is rooted.
Click to expand...
Click to collapse
no other way, unfortunatly.. one way or the other, you have to flash the zip...
ps: if you are on emui, first boot after flashing xposed will take a really long time.. mine took around 25 minutes to boot.. so dont consider it a boot loop, wait untill 30 minutes and you will be profitted

Mine was in boot screen for around 3 minutes and then rebooted into recovery. Same thing was happening again and again. So at last did the restore process from TWRP.

oppili said:
1. Try "fastboot continue" it will directly boot without going to recovery.
2. If fastboot flash works flash recovery of the firmware installed in phone before bootloop.
3. If still not works flash boot, system, recovery (in this order) of firmware installed before bootloop.
Confirm unlock key with customer care if it is still locked.
Click to expand...
Click to collapse
Its not working. Please help me I am still stuck....any way of installing the stock ROM back via fastboot mode with the phone showing 'Phone Locked'

Restoring TOO MUCH with twrp?
Can restoring too much with TWRP damage my phone?

jwalker9715 said:
Can restoring too much with TWRP damage my phone?
Click to expand...
Click to collapse
not really..

Related

Hard Bricked P9 Lite

Hi, i have a big problem: my phone isn't starting up anymore. Yesterday i upgraded to Nougat, and all was fine. Then i decided to install Revolution ROM, so i flashed twrp for 7.0 and then flashed the ROM. Phone started up correctly but then i decided to wipe data so i can have a "clean" installation. So i rebooted into twrp and formatted data. After this, phone get into bootloop. Just after that, i couldn't boot into twrp, and when i tried to boot in, it stuck in the yellow text "Your phone is booting up...". Then i downloaded b160, extracted it with Huawei Update Extractor and flashed all(system, boot, cust and recovery). This didn't work, i was stuck in the 3 choices menu with text "Your phone is booting up...", can't even see Huawei's logo. 1 hour ago i installed from sd (3 buttons way) b160, installation successful and now i can see Huawei's logo, but after that black screen . I tried to reboot into bootloader but i don't see anymore yellow "unlocked phone" text. I can just boot into eRecovery. Right now i'm trying to download b100 and trying to see if i can fix it by myself :fingers-crossed:. If u can, please help me, i really need help to get this phone working again.
(Sorry for my bad english )
Edit: i posted in wrong section, sorry xD
Edit 2: i finally boot into bootloader, but "PHONE Locked" . How can i unlock bootloader again? I don't have that code anymore and i can't boot into system..
xDavi01 said:
Hi, i have a big problem: my phone isn't starting up anymore. Yesterday i upgraded to Nougat, and all was fine. Then i decided to install Revolution ROM, so i flashed twrp for 7.0 and then flashed the ROM. Phone started up correctly but then i decided to wipe data so i can have a "clean" installation. So i rebooted into twrp and formatted data. After this, phone get into bootloop. Just after that, i couldn't boot into twrp, and when i tried to boot in, it stuck in the yellow text "Your phone is booting up...". Then i downloaded b160, extracted it with Huawei Update Extractor and flashed all(system, boot, cust and recovery). This didn't work, i was stuck in the 3 choices menu with text "Your phone is booting up...", can't even see Huawei's logo. 1 hour ago i installed from sd (3 buttons way) b160, installation successful and now i can see Huawei's logo, but after that black screen . I tried to reboot into bootloader but i don't see anymore yellow "unlocked phone" text. I can just boot into eRecovery. Right now i'm trying to download b100 and trying to see if i can fix it by myself :fingers-crossed:. If u can, please help me, i really need help to get this phone working again.
(Sorry for my bad english )
Edit: i posted in wrong section, sorry xD
Edit 2: i finally boot into bootloader, but "PHONE Locked" . How can i unlock bootloader again? I don't have that code anymore and i can't boot into system..
Click to expand...
Click to collapse
Try dload method
Ww222 said:
Try dload method
Click to expand...
Click to collapse
I've alredy tried with 2 different firmwares: b130 and b120 but both say that they're incompatible.. Right now i'm downloading b100
(btw, my phone model is L-21 dual-sim)
Edit: I've tried to install b100 without any success. Everytime i try to install a firmware it says "Software installation failed! Incompatibility with current version. Please download the correct update package"
I heard about "oeminfo.img", because before having theese problems i was in 7.0 and to rollback you need to flash this oeminfo.img, but i can't flash anything .
Please help me, i'm alredy losing hope to repair my device... What should i do?
xDavi01 said:
I've alredy tried with 2 different firmwares: b130 and b120 but both say that they're incompatible.. Right now i'm downloading b100
(btw, my phone model is L-21 dual-sim)
Edit: I've tried to install b100 without any success. Everytime i try to install a firmware it says "Software installation failed! Incompatibility with current version. Please download the correct update package"
I heard about "oeminfo.img", because before having theese problems i was in 7.0 and to rollback you need to flash this oeminfo.img, but i can't flash anything .
Please help me, i'm alredy losing hope to repair my device... What should i do?
Click to expand...
Click to collapse
What is your region and model?
Ww222 said:
What is your region and model?
Click to expand...
Click to collapse
Europe, VNS-L21 and C432 if i remember correctly
xDavi01 said:
Europe, VNS-L21 and C432 if i remember correctly
Click to expand...
Click to collapse
Download this:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v66051/f1/full/update.zip
Ww222 said:
Download this:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v66051/f1/full/update.zip
Click to expand...
Click to collapse
Thank you for helping me, i really apprecciate it . Later i'll download it and install and i'll let you know if this works
same here. I'm downloading the update.
---------- Post added at 10:17 PM ---------- Previous post was at 09:41 PM ----------
Ok so I've installed an update but I got a black screen. All I had to do is to clear cache and wipe data etc (in recovery option), then reboot to "dload mode" and... well, it works !

PRA-LX1 I want to install stock firmware.

I want to flash my phone with stock firmware, but I cannot find it anywhere.
I am looking for PRA-LX1C738B123.
I own Huawei p8 lite 2017
I wiped my system because I wanted to install other rom, it didn't work so I want to go back to the original.
Unfortunately I wasn't smart enough to do a backup before so I am stuck atm. The bootloader is unlocked and flashing works, I can boot into huawei eRecovery and TWRP. (eRecovery gives the getting package info failed error) I have tried the dload method with other app files, it fails at 5% every time tho.
I tried using Huawei Update Extractor and Firmware Finder but I cannot find the exact firmware.
Could someone help me with installing my firmware? Oh and I am kinda new and it would be nice to get some guides,
Thanks.
I have the same problem but with a different firmware.. now only thing i can do is use dc-phoenix paid software (15$ for 72h of use). I will try that tomorrow as i also can't find exact same firmware it was on my phone.
MobileTechArena said:
I have the same problem but with a different firmware. now only thing i can do is usedc-phoenix paid software (15$ for 72h of use). I will try that tomorrow as i also can't find exact same firmware it was on my phone.
Click to expand...
Click to collapse
Thanks for reply. I will take that into consideration, but from what I see you were looking for PRA-LX1C432B106 and they indeed have the c432 roms there, however they don't seem to have the ones that I have been looking for. They have a list of firmwares online. Anyway good luck.
barnabaXXX said:
Thanks for reply. I will take that into consideration, but from what I see you were looking for PRA-LX1C432B106 and they indeed have the c432 roms there, however they don't seem to have the ones that I have been looking for. They have a list of firmwares online. Anyway good luck.
Click to expand...
Click to collapse
Yes, but any PRA-LX1C432 i tried doesn't work for me, flashing by fastboot. I believe any PRA-LX1 should work on this phone, but i will need to use that dc phoenix software to flash it.
MobileTechArena said:
Yes, but any PRA-LX1C432 i tried doesn't work for me, flashing by fastboot. I believe any PRA-LX1 should work on this phone, but i will need to use that dc phoenix software to flash it.
Click to expand...
Click to collapse
Thanks for making it clear. Please tell me if it worked or not. Thanks.
barnabaXXX said:
I want to flash my phone with stock firmware, but I cannot find it anywhere.
I am looking for PRA-LX1C738B123.
I own Huawei p8 lite 2017
I wiped my system because I wanted to install other rom, it didn't work so I want to go back to the original.
Unfortunately I wasn't smart enough to do a backup before so I am stuck atm. The bootloader is unlocked and flashing works, I can boot into huawei eRecovery and TWRP. (eRecovery gives the getting package info failed error) I have tried the dload method with other app files, it fails at 5% every time tho.
I tried using Huawei Update Extractor and Firmware Finder but I cannot find the exact firmware.
Could someone help me with installing my firmware? Oh and I am kinda new and it would be nice to get some guides,
Thanks.
Click to expand...
Click to collapse
Hello ! I think I could be of some help since I encountered the exact same problem !
edit: well I just realized I can't find your ROM with firmware finder either, sorry for the failed attempt
In your case I'd try with each firmware until one would work or a I tried them all.
You need some utilities first :
- Firmware Finder
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
It will allow you to find the stock ROM that fits your model
-Huawei UPDATE extractor
https://forum.xda-developers.com/showthread.php?t=2433454
It will allow you to extract the .img files from the firmware previously downloaded.
-fastboot and adb
https://forum.xda-developers.com/showthread.php?t=2317790
The programs that will allow you to flash the .img files.
Now:
1. Find your ROM using firmware finder (the model is usually on the box you received the android in).
2.Extract the necessary .img files : system.img, boot.img, recovery.img.
3.Reboot into the bootloader, connect your device to your computer, open a cmd exe (powershell in my case) by holding shift+right click on the folder containing the .img files and flash each .img file, e.g. for the system file:
"fastboot flash system system.img"
4.then use "fastboot reboot" and after that shutdown your device
(in my case even after flashing the .img files I was greeted by a blank screen, so I shutdown my device holding the power button).
5. Boot into recovery holding vol up + power buttons (be sure to disconnect your device before shutting down and powering it up again) and choose factory reset.
It should then reboot into ROM installation procedure where you will have to follow the same steps as when you booted your device for the first time.
edit: formatting
Also, as far as my limited knowledge goes, there is no custom ROM officially supported for our dear device.
JStrel said:
Hello ! I think I could be of some help since I encountered the exact same problem !
edit: well I just realized I can't find your ROM with firmware finder either, sorry for the failed attempt
In your case I'd try with each firmware until one would work or a I tried them all.
You need some utilities first :
- Firmware Finder
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
It will allow you to find the stock ROM that fits your model
-Huawei UPDATE extractor
https://forum.xda-developers.com/showthread.php?t=2433454
It will allow you to extract the .img files from the firmware previously downloaded.
-fastboot and adb
https://forum.xda-developers.com/showthread.php?t=2317790
The programs that will allow you to flash the .img files.
Now:
1. Find your ROM using firmware finder (the model is usually on the box you received the android in).
2.Extract the necessary .img files : system.img, boot.img, recovery.img.
3.Reboot into the bootloader, connect your device to your computer, open a cmd exe (powershell in my case) by holding shift+right click on the folder containing the .img files and flash each .img file, e.g. for the system file:
"fastboot flash system system.img"
4.then use "fastboot reboot" and after that shutdown your device
(in my case even after flashing the .img files I was greeted by a blank screen, so I shutdown my device holding the power button).
5. Boot into recovery holding vol up + power buttons (be sure to disconnect your device before shutting down and powering it up again) and choose factory reset.
It should then reboot into ROM installation procedure where you will have to follow the same steps as when you booted your device for the first time.
edit: formatting
Also, as far as my limited knowledge goes, there is no custom ROM officially supported for our dear device.
Click to expand...
Click to collapse
Thanks for help! I tried but i dont' have factory reset option. All I have is Shutdown, reboot and "Download leastest version and recovery" and after I click that all it does is wants internet connection. I logged in to my wifi but it didn't work and I ended up with "getting package info failed screen".
barnabaXXX said:
Thanks for help! I tried but i dont' have factory reset option. All I have is Shutdown, reboot and "Download leastest version and recovery" and after I click that all it does is wants internet connection. I logged in to my wifi but it didn't work and I ended up with "getting package info failed screen".
Click to expand...
Click to collapse
Yes I had the exact same problem, but once I did what I described, by rebooting into recovery (without twrp), I finally had the option to restore factory settings.
I believe the issue is in the fact you don't have access to the stock ROM for your model.
JStrel said:
Yes I had the exact same problem, but once I did what I described, by rebooting into recovery (without twrp), I finally had the option to restore factory settings.
I believe the issue is in the fact you don't have access to the stock ROM for your model.
Click to expand...
Click to collapse
I got rom that allows me to do a factory reset, it's stuck at 99% for like 2 hours now, is it normal? If not what should I do?
barnabaXXX said:
I got rom that allows me to do a factory reset, it's stuck at 99% for like 2 hours now, is it normal? If not what should I do?
Click to expand...
Click to collapse
Unfortunately I can't help you further than what I already posted.
But keep updating in case someone more knowledgeable peeks in.
similar problem....I was fairly good but play store was stuck in pending download....
I did a wipe in TWRP, and ended with a black screen...
I can boot to eRecovery, but it fails.and also to TWRP.
when attached to PC it keeps being seen and unseen as if its stuck in a power on cycle
Any help would be greatly appreciated.
Already Tested
JStrel said:
Hello ! I think I could be of some help since I encountered the exact same problem !
edit: well I just realized I can't find your ROM with firmware finder either, sorry for the failed attempt
In your case I'd try with each firmware until one would work or a I tried them all.
You need some utilities first :
- Firmware Finder
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
It will allow you to find the stock ROM that fits your model
-Huawei UPDATE extractor
https://forum.xda-developers.com/showthread.php?t=2433454
It will allow you to extract the .img files from the firmware previously downloaded.
-fastboot and adb
https://forum.xda-developers.com/showthread.php?t=2317790
The programs that will allow you to flash the .img files.
Now:
1. Find your ROM using firmware finder (the model is usually on the box you received the android in).
2.Extract the necessary .img files : system.img, boot.img, recovery.img.
3.Reboot into the bootloader, connect your device to your computer, open a cmd exe (powershell in my case) by holding shift+right click on the folder containing the .img files and flash each .img file, e.g. for the system file:
"fastboot flash system system.img"
4.then use "fastboot reboot" and after that shutdown your device
(in my case even after flashing the .img files I was greeted by a blank screen, so I shutdown my device holding the power button).
5. Boot into recovery holding vol up + power buttons (be sure to disconnect your device before shutting down and powering it up again) and choose factory reset.
It should then reboot into ROM installation procedure where you will have to follow the same steps as when you booted your device for the first time.
edit: formatting
Also, as far as my limited knowledge goes, there is no custom ROM officially supported for our dear device.
Click to expand...
Click to collapse
Hello did you already test ???
Here is the solution for every PRA-LX1: [http : // www . htcmania . com / showthread . php ? t=1326478] (sorry for the spaces, but I don't have enough posts written to post external links )
Unfortunately, it's from a spanish forum. I didn't found any problem to follow this tutorial, but maybe for someone it could be a little difficult.
Anyway, it works!
MobileTechArena said:
Yes, but any PRA-LX1C432 i tried doesn't work for me, flashing by fastboot. I believe any PRA-LX1 should work on this phone, but i will need to use that dc phoenix software to flash it.
Click to expand...
Click to collapse
Where did you find the C432 firmware? I can't succees to find it
Flashing to a completely empty phone via DC phoenix or manual via fastboot still didnt got my device started. Sometimes I end up in the eRecovery and sometimes its just stuck at boot.
I tried different version from the hicloud but none so far did the trick. Maybe someone can point me into the right direction so i can finally rescue this phone?
EDIT:
PRA-LX1C432
Sorry cant link to these files since i don't got 10 posts. Maybe PM ?
Copied the Mega TWRP backup (B100) to SD card
Flashed TWRP via fastboot
Disconnected the USB cable
Boot into TWRP
Restored TWRP backup
Restarted phone into fastboot
OEM unlocked it
Got booted into TWRP since no stock recovery there
Booted into fastboot again
flashed stock recovery
Android started to work!
Tried to update to B164 and failed
Reboot
Now it offered B110 and I tried to update to B110. Success.
Iocere said:
Flashing to a completely empty phone via DC phoenix or manual via fastboot still didnt got my device started. Sometimes I end up in the eRecovery and sometimes its just stuck at boot.
I tried different version from the hicloud but none so far did the trick. Maybe someone can point me into the right direction so i can finally rescue this phone?
EDIT:
PRA-LX1C432
Sorry cant link to these files since i don't got 10 posts. Maybe PM ?
Copied the Mega TWRP backup (B100) to SD card
Flashed TWRP via fastboot
Disconnected the USB cable
Boot into TWRP
Restored TWRP backup
Restarted phone into fastboot
OEM unlocked it
Got booted into TWRP since no stock recovery there
Booted into fastboot again
flashed stock recovery
Android started to work!
Tried to update to B164 and failed
Reboot
Now it offered B110 and I tried to update to B110. Success.
Click to expand...
Click to collapse
Yeah, that's the way! It worked for me too!
juanmemo said:
Yeah, that's the way! It worked for me too!
Click to expand...
Click to collapse
Also i noticed everytime a OTA fails you get the full version offered on next boot. So you should get a full B164 aswell after it failed
JStrel said:
Yes I had the exact same problem, but once I did what I described, by rebooting into recovery (without twrp), I finally had the option to restore factory settings.
I believe the issue is in the fact you don't have access to the stock ROM for your model.
Click to expand...
Click to collapse
how can you boot into recovery ? i can only boot into twrp or fastboot & rescue or if i plug the huawei to the pc erecovery ???
---------- Post added at 12:16 AM ---------- Previous post was at 12:13 AM ----------
i have an huawei pra-lx1 c530 it used to boot into pra-lx1c530b111 rooted and twrp but now it doens't boot anymore, i'd like to flash to c530b160 but i can't find the firmware images
tiagoggama said:
Hello did you already test ???
Click to expand...
Click to collapse
Thanks men
I CONFIRM IT WORK PERFECTLY
For the second part go to this link for more detail :
https://boycracked.com/2016/03/14/h...-unbrick-firmware-any-huawei-android-devices/

How many people bricked their phone while Rebranding/OTA and what solutions used ?

How many people bricked specifically hardbricked their phone after 2018-04-16 updates,while OTA or rebranding using any tool and choose which methods you tried to solve.
we need to show how many people we are,and seek for solution or encourage BOX groups to do something for this matter.
Even huawei may help us if they see we are bunch of people.
Edit: Just comment only if you solved the issue with this tool or any other tool that is not mentioned,here we are seeking help.
reza6d said:
How many people bricked specifically hardbricked their phone after 2018-04-16 noxloader updates,while OTA or rebranding using any tool and choose which methods you tried to solve.
we need to show how many people we are,and seek for solution or encourage BOX groups to do something for this matter.
Even huawei may help us if the ysee we are bunch of people.
Click to expand...
Click to collapse
The only versions that will brick (so far anyway) are BLA-L29C636B137 and ALP-L29C636B134 from 16/4, neither is a noxloader version.
Bricks occur when you update/downgrade/rebrand FROM those 2 firmwares.
ante0 said:
The only versions that will brick (so far anyway) are BLA-L29C636B137 and ALP-L29C636B134 from 16/4, neither is a noxloader version.
Bricks occur when you update/downgrade/rebrand FROM those 2 firmwares.
Click to expand...
Click to collapse
maybe i recall wrong but after first time seeing these noxloaders,somethings changed,anyway i edited the post.thanks.
My BLA-L29 is still on the black screen and I can not even revert to DC-Phoenix. After upgrading to 138.
Used funky
mikaole said:
Used funky
Click to expand...
Click to collapse
i think your phone was in fastboot or bootloop,we are talking about hardbrick bro,black screen not even charge led in our devices.
I bricked my Huawei Mate 10 too
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Carnage! said:
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Click to expand...
Click to collapse
did you tried huawei pc app (hisuite)?
your problem maybe is because magisk, try to install in twrp "magisk uninstaller". or try to install via twrp, recovery_ramdisk.img, kernel.img and ramdisk.img from the last rom of android 8 (extract with huaweiupdateextractor), then install via twrp with hrupdater 0,4 the same update.zip that you extract the kernel.img, recovery and the other img that I told you.
look at the guides of the preocesses that I told you, if you have any question let me know
durc12 said:
did you tried huawei pc app (hisuite)?
your problem maybe is because magisk, try to install in twrp "magisk uninstaller". or try to install via twrp, recovery_ramdisk.img, kernel.img and ramdisk.img from the last rom of android 8 (extract with huaweiupdateextractor), then install via twrp with hrupdater 0,4 the same update.zip that you extract the kernel.img, recovery and the other img that I told you.
look at the guides of the preocesses that I told you, if you have any question let me know
Click to expand...
Click to collapse
Yes, I tried hisuite but it says my device isn't supported. I will try your suggestion and will get back to you if I have questions
Carnage! said:
Yes, I tried hisuite but it says my device isn't supported. I will try your suggestion and will get back to you if I have questions
Click to expand...
Click to collapse
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Pretoriano80 said:
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Click to expand...
Click to collapse
I see. I only tried flashing the recovery_ramdisk and system.img. I will try it later and I will let you know if it worked.
Pretoriano80 said:
If the update process didn't even started, you need to flash stock Pie kernel, recovery_ramdisk and system, using fastboot.
This should get you back to a working OS.
Click to expand...
Click to collapse
as far as I can read, I think he wants to come back to OREO, so he has to install first recovery_ramdisk.img, kernel.img and ramdisk.img from 8.0.0.143 (extracting those files with huaweiextractorupdate) and then flashing those files via fastboot or your twrp version. Then, he has to use hrupdater 0.4 to install 8.0.0.143
Am I right Pretoriano80?
please, fell free to correct me if i have commited any mistake
PD: MANDATORY TO HAVE UNLOCKED BOOTLOADER FOR THE PROCESS
durc12 said:
as far as I can read, I think he wants to come back to OREO, so he has to install first recovery_ramdisk.img, kernel.img and ramdisk.img from 8.0.0.143 (extracting those files with huaweiextractorupdate) and then flashing those files via fastboot or your twrp version. Then, he has to use hrupdater 0.4 to install 8.0.0.143
Am I right Pretoriano80?
please, fell free to correct me if i have commited any mistake
PD: MANDATORY TO HAVE UNLOCKED BOOTLOADER FOR THE PROCESS
Click to expand...
Click to collapse
No, first he has to recover the current OS, and my advise was only for that.
Then he will need to use a TWRP + NoCheck combo, to get back to Oreo.
HuRUpdater can't get you back to Oreo so you guys should stop using that with Pie.
Mate 10 Pro BLA-L09
I also installed the EMUI 9.0 on my device using the HWOTA8 method which was successful. The EMUI 9.0 (9.0.0.108). I didn't have any issues too. After a while I decided to switch back to EMUI 8.0. using also HWOTA8 I put three zip files with EMUI8 (update.zip .....). Update ended with error. That's it.
I only have fastboot working but I am able to flash only few partitions System.img, Recovery_ramdisk.img, Kernel.img. I tried to flash them many times - nothing.
Couple months ago I messed up with my phone and I had to buy and use DC-Phoenix. It worked for me then. This time did not because DC-Phoenix only support EMUI 8. They refunded me money I paid for - that's good thing but my phone is still bricked.
Then I've found MultiTool for Huawei
https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
It shows that
https://gyazo.com/70820957c6638e27bfe79418dfb07e3e
(Firmware 9.0.0.108,device bla-l09,no serial number, no IMEI and battery status 0)
HiSuite says device is not supported.
Is there any way to force HiSuite to recover not supported device?
Anyone knows the solution?
I booked my phone for repair with Huawei Service.
diowil4 said:
I also installed the EMUI 9.0 on my device using the HWOTA8 method which was successful. The EMUI 9.0 (9.0.0.108). I didn't have any issues too. After a while I decided to switch back to EMUI 8.0. using also HWOTA8 I put three zip files with EMUI8 (update.zip .....). Update ended with error. That's it.
I only have fastboot working but I am able to flash only few partitions System.img, Recovery_ramdisk.img, Kernel.img. I tried to flash them many times - nothing.
Couple months ago I messed up with my phone and I had to buy and use DC-Phoenix. It worked for me then. This time did not because DC-Phoenix only support EMUI 8. They refunded me money I paid for - that's good thing but my phone is still bricked.
Then I've found MultiTool for Huawei
https://forum.xda-developers.com/honor-8/development/tool-huawei-multi-tool-team-mt-t3523923
It shows that
https://gyazo.com/70820957c6638e27bfe79418dfb07e3e
(Firmware 9.0.0.108,device bla-l09,no serial number, no IMEI and battery status 0)
HiSuite says device is not supported.
Is there any way to force HiSuite to recover not supported device?
Anyone knows the solution?
I booked my phone for repair with Huawei Service.
Click to expand...
Click to collapse
It should be possible to recover your phone.Tried to flash Pie B108 recovery_ramdisk, kernel and system with fastboot?
Pretoriano80 said:
It should be possible to recover your phone.Tried to flash Pie B108 recovery_ramdisk, kernel and system with fastboot?
Click to expand...
Click to collapse
I have tried. I flashed Pie 9.0.0.108 - nothing, 9.0.0.112 (chinese ver) - nothing. I tried BLA-L09 8.0.0.148(SP1C432) - nothing.
After flashing recovery_ramdisk, kernel and system of all above firmware there is no change only fastboot is working.
The problem is that downgrade process from Pie to Oreo went to 95% ( I thing - I don't remember exactly but for sure it was 90 something). It could have changed most of partitions to Oreo but left one or few unchanged (like verlist.img, xloadr.img, vendor.img, product.img).
From fastboot I am able to change (flash) only few partitions.
Do you gays know any other tools like dc-phoenix to force to flash all partitions. (Couple months ago when I used DC Phoenix with Emui 8 it used backdoor to flash difficult partitions.)
Example:
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...OK
diowil4 said:
I have tried. I flashed Pie 9.0.0.108 - nothing, 9.0.0.112 (chinese ver) - nothing. I tried BLA-L09 8.0.0.148(SP1C432) - nothing.
After flashing recovery_ramdisk, kernel and system of all above firmware there is no change only fastboot is working.
The problem is that downgrade process from Pie to Oreo went to 95% ( I thing - I don't remember exactly but for sure it was 90 something). It could have changed most of partitions to Oreo but left one or few unchanged (like verlist.img, xloadr.img, vendor.img, product.img).
From fastboot I am able to change (flash) only few partitions.
Do you gays know any other tools like dc-phoenix to force to flash all partitions. (Couple months ago when I used DC Phoenix with Emui 8 it used backdoor to flash difficult partitions.)
Example:
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Writing XLOADER partition with file X:\Install\Telefony\Huawei_Mate_10_pro\DC_Phoenix_v50\XLOADER.img
XLOADER partition UPDATE ...OK
Click to expand...
Click to collapse
I think you should use my TWRP + NoCheck recovery and try to flash the Pie beta again.
Pretoriano80 said:
I think you should use my TWRP + NoCheck recovery and try to flash the Pie beta again.
Click to expand...
Click to collapse
After flashing It cannot boot to recovery.
diowil4 said:
After flashing It cannot boot to recovery.
Click to expand...
Click to collapse
So you can only boot to fastboot, no matter what?
Pretoriano80 said:
So you can only boot to fastboot, no matter what?
Click to expand...
Click to collapse
Yes.

soft brick? error [Func NO : 11 (recovery image) Error NO : 2 (load failed!)

Hi guys. I tried to see other threads but I haven't fint anything. Probably there is but I'm beginner and I don't understand so much Anyway this is the problem:
model LLD-L31
build number LLD-L31 8.0.0.133(C432)
FPR unlocked
bootloader unloced
I tried to install root(Magisk-v16.4) in my device. So I unlocked bootloader, installed TWPR(Pretorian80 2.3.1) successfully but this error "Failed to unmount '/system'(Device or resource busy)" appeared. So I try to format data by recovery hoping that it could be able to read partitions after that. I couldn't yet flash file.Zip so I tried to upgrade Twpr in latest version installing it in recovey ramdisk.
After that I'm not able anymore to get into twpr cause this error appered:
[Func NO : 11 (recovery image) Error NO : 2 (load failed!)
Now, I fortunatly turn on the phone, using it with no problems. I can enter in fastboot and eRecovery. I tried to swipe data/reset but the same error appears.
Can I fix it easily? Tell me if you have any tips, thank you:good:
scugnizz said:
Hi guys. I tried to see other threads but I haven't fint anything. Probably there is but I'm beginner and I don't understand so much Anyway this is the problem:
model LLD-L31
build number LLD-L31 8.0.0.133(C432)
FPR unlocked
bootloader unloced
I tried to install root(Magisk-v16.4) in my device. So I unlocked bootloader, installed TWPR(Pretorian80 2.3.1) successfully but this error "Failed to unmount '/system'(Device or resource busy)" appeared. So I try to format data by recovery hoping that it could be able to read partitions after that. I couldn't yet flash file.Zip so I tried to upgrade Twpr in latest version installing it in recovey ramdisk.
After that I'm not able anymore to get into twpr cause this error appered:
[Func NO : 11 (recovery image) Error NO : 2 (load failed!)
Now, I fortunatly turn on the phone, using it with no problems. I can enter in fastboot and eRecovery. I tried to swipe data/reset but the same error appears.
Can I fix it easily? Tell me if you have any tips, thank you:good:
Click to expand...
Click to collapse
Hi, Not familiar with that Version of TWRP, can you link please?
Failure to unmount system usually means you have system set as "read only", try to change within twrp (when you get a working version flashed).
You say you tried to update TWRP to latest edition, exactly what edition did you flash?
Anyway eRecovery will rescue the phone back to when first turned on.
Sparkrite said:
Hi, Not familiar with that Version of TWRP, can you link please?
Failure to unmount system usually means you have system set as "read only",try to change within twrp (when you get a working version flashed).
You say you tried to update TWRP to latest edition, exactly what edition did you flash?
Anyway eRecovery will rescue the phone back to when first turned on.
Click to expand...
Click to collapse
Hi man thank you for your answer.
I flashed this versionhttps://dl.twrp.me/surnia/twrp-3.2.3-0-surnia.img.html
,try to change within twrp (when you get a working version flashed).
Click to expand...
Click to collapse
I can't enter anymore within TWPR, only in stock recovery.
What made you flash that version, where does it say its for the H9L ?
Try either of these, I use V.01 :-
https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
Make sure you use the following command "fastboot flash recovery_ramdisk NAME.img"
When flashed, issue "fastboot reboot" while holding down Vol+, when bootloader page blanks immediately remove USB lead and continue to hold Vol+ until TWRP appears.
TWRP may stall for a while on LOGO page, be patient.
What made you flash that version, where does it say its for the H9L ?
Click to expand...
Click to collapse
I'm dumb man that's all:silly:
Anyway it's fixed now, I love you (thanks put, at least).
Failure to unmount system usually means you have system set as "read only",try to change within twrp
Click to expand...
Click to collapse
Last thing if you can..
On mount section the option mount system partition read-only is disactivated but, at opening, error appears in the same way so I don't know how to disable it definitively
Try formatting Data and then reboot to TWRP (recovery).
Man I'm a disaster:crying:
I formatted but I also had the brilliant idea to delete the whole system, without creating any backup by twpr, obviously. So now I have no OS in my device:good:
I had look for stock firmware with Firmware Finder and I have find one whit these files(bottom photo). Which have I to download?
Then I'll probably follow this thread(https://forum.xda-developers.com/9-lite/help/os-installed-t3787136) to continue. Is it right??
At this stage you are probably better off using eRecovery to bring your phone back to full stock.
From off press and hold Vol Up and connect USB, wait for eRecovery and select "Download latest version and recovery".
Needs WiFi.
savior
scugnizz said:
savior
Click to expand...
Click to collapse
Ah Great, good to hear.
Now, go and flash TWRP and Magisk, but follow the instructions EXACTLY !

Bricked Honor 5c NEM-L51 ?

Hi, I think i've kinda bricked my honor 5C (nem-l51), and I really need help :
A few years ago I rooted my phone to make otg work.
It worked a little while, but then a system update came up, could not update because of the twrp, so I tried to unroot it (from supersu) to do the update, and the twrp stayed after the unroot.
I stayed with the phone like this, twrp installed and update pending (still trying to install the update from time to time) and then I had to use OTG again and tried to re-root my phone.
I tried to flash the supersu files I used the first time, but, even when the flashing worked, I couldn't see the supersu app on the phone, still unrooted.
Then I tried to change the twrp (via fastboot) and I realised that I couldn't : I get the "command not allowed" failure when the recovery should get written. I tried with numerous twrp versions, and stock recovery.
So my twrp right now is the twrp-3.1.1-0-venus "OpenKirin edition" one.
The phone says it's unlocked and the frp is locked, but I can't remember if it was already the case or not when I first rooted.
I unfortunately don't have anymore the bootloader unlock code that huawai gave me originally. I have no idea how to get it again, to try to re-lock/unlock the bootloader.
Back then when I first rooted my phone, I made a back up, so I tried to restore that back up. It failed, first with "cannot wipe the cust partition". Then I tried to restore without restoring the cust partition, and I got "extracttarfork() process ended with error 255" while the system was restoring.
After that, the phone wouldn't boot into android anymore. It would be stuck at the unlocked bootloader warning message and then reboot after a few minutes.
So, lastly, I tried to install the unofficial lineageOS port from here : https://forum.xda-developers.com/honor-5c/development/rom-lineageos-14-1-honor-5c-t3713911 with my twrp.
The installation went well, but the phone is stuck while first booting in lineageOS (I let it overnight, restarted it, re-installed it, tried with the first release, nothing).
TL;DR: My phone isn't booting and I can't flash any new recovery.
Please, help me to get my phone working again
Give me the
old build number on emui
Update build you received..
Twrp working?
Fastboot?
Erecovery?
I got access to erecovery, even if the "download latest version and recovery" doesn't work. (erecovery connects to wifi, and the first thing it tries to check/download fails)
I can boot into fastboot but can't flash recovery from there because of the command not allowed problem.
I can boot into twrp, but the back up I tried to restore and the lineageos rom I tried to install both failed, so maybe the twrp has a problem?
I'm sorry I'm not sure about the build number, I'm pretty sure I was on EMUI 5.0 and android 7.x, and I think I remember comparing current build number vs the update, and it was something like B350 or B351 for the current, and B355 or B375 for the update.
I've found this in my backup file 'recovery.log' ro.omni.version=6.0.1-20160703-nemo-HOMEMADE and ro.build.id=MOB30M . So, that mean that I had android 6.x when I did the backup, way back at the beginning.
I thought the update never got installed because each time the phone would reboot to complete installation, it would reboot into twrp. But I've still updated from android 6 to android 7 somehow ?
NEM-L51C432 or NEM-L51C10 ?
NEM-L51C432 and I'm sure of that ^^
Zhyrclew said:
NEM-L51C432 and I'm sure of that ^^
Click to expand...
Click to collapse
Flash this via twrp
http://update.hicloud.com:8180/TDS/...-L51_hw_eu/update_data_full_NEM-L51_hw_eu.zip
Once done, boot to twrp and flash this
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1581/g104/v82938/f1/full/update.zip
Reboot.
If you are unable to flash the 2nd link then just use the dload method to flash this. If you are not aware of dload method, link is given in my signature.
Note, this 2nd firmware will replace your twrp with stock recovery. You should boot to b350 version and it will be full stock. Reason for flashing data file first is it doesn't replace the recovery to stock but just flashes your data, settings, apps. And 2nd link is main full firmware which will replace your boot, recovery, vendor everything and should boot.
Good luck
I flashed the first one, no error.
The second one had multiple errors :
"[...]
write radio image...
32k crc checked failure
E:unknown command [errno]
update_huawai_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/update.zip'
Updating partition details...
...done
"
So I tried the dload method, and the installation started and ended at 5% with this error :
"Software install failed!
Incompatibility with current version.
Please download the correct update package."
I guess it's because I couldn't tell you the exact build number, I'm sorry for not taking note of it.
If there is a way for me to get the build number despite the status of the phone, i'm ready to do it.
If not, I'm ready to try as many versions as it takes to find the good one.
PS: I've still access to the twrp, thank god ! That was my biggest fear, because I can't flash any recovery in the current state.
Zhyrclew said:
I flashed the first one, no error.
The second one had multiple errors :
"[...]
write radio image...
32k crc checked failure
E:unknown command [errno]
update_huawai_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/update.zip'
Updating partition details...
...done
"
So I tried the dload method, and the installation started and ended at 5% with this error :
"Software install failed!
Incompatibility with current version.
Please download the correct update package."
I guess it's because I couldn't tell you the exact build number, I'm sorry for not taking note of it.
If there is a way for me to get the build number despite the status of the phone, i'm ready to do it.
If not, I'm ready to try as many versions as it takes to find the good one.
PS: I've still access to the twrp, thank god ! That was my biggest fear, because I can't flash any recovery in the current state.
Click to expand...
Click to collapse
You may try other higher versions like 360, 370 etc and see your luck. Twrp will be replaced only if the installation os successful for the main firmware. Its just a trial and error for you now but I am 99% sure you should be able to revive the phone via dload method
Thank you, it's reassuring. I will not give up until I test all the versions ^^
Could you help me a little bit to find other versions, please ? The only place I know where there is update packages for my phone is there : https://forum.xda-developers.com/ho...lota-upgrade-packages-models-nem-l51-t3473110 and there is only two versions.
Zhyrclew said:
Thank you, it's reassuring. I will not give up until I test all the versions ^^
Could you help me a little bit to find other versions, please ? The only place I know where there is update packages for my phone is there : https://forum.xda-developers.com/ho...lota-upgrade-packages-models-nem-l51-t3473110 and there is only two versions.
Click to expand...
Click to collapse
Firmware finder website
Wow, thank you, I downloaded the firmware finder software, it has everything.
Should I flash the firmware in two steps like you first made me, or should I just try with only the dload method with the fullOTA firmware ?
Zhyrclew said:
Wow, thank you, I downloaded the firmware finder software, it has everything.
Should I flash the firmware in two steps like you first made me, or should I just try with only the dload method with the fullOTA firmware ?
Click to expand...
Click to collapse
Check dload guide in my signature. You can follow that now. Good luck
I tried b355, b361, b375, b377, nothing changes, same error.
I noticed that I have something related to an update in my sd card AND internal storage->HwOUC->140783->( update.zip[1.32GB], update_data_full_public.zip[344MB], update_full_NEM-L51_hw_eu.zip[412MB] )
I don't know whether these files were there before I did all these attempted updates.
Could it be that my phone is not trying to install the files I put in sdcard->dload, because he finds these files in the internal memory first, and each time try to install these ?
Should I delete them, move them, unzip them in dload folder ?
Zhyrclew said:
I tried b355, b361, b375, b377, nothing changes, same error.
I noticed that I have something related to an update in my sd card AND internal storage->HwOUC->140783->( update.zip[1.32GB], update_data_full_public.zip[344MB], update_full_NEM-L51_hw_eu.zip[412MB] )
I don't know whether these files were there before I did all these attempted updates.
Could it be that my phone is not trying to install the files I put in sdcard->dload, because he finds these files in the internal memory first, and each time try to install these ?
Should I delete them, move them, unzip them in dload folder ?
Click to expand...
Click to collapse
Copy them on PC and then try dload of files you downloaded from Firmware finder website.
These are files your phone downloaded for OTA update but as you were on twrp, they never installed it amd stays there
I copied the updates my phone downloaded on PC and then deleted them both on internal storage and sd card.
Then I tried dload method with b355,b375&b377 from firmware finder, and also with the update.zip I found in the updates my phone downloaded.
Nothing worked, all of them got the error "Incompatibility with current version. Please download the correct update package."
Should I try even more firmware versions, or should I try something else ?
Btw, I noticed my phone, when connected to my PC, is labeled as huawei-P9-lite, and I don't think it was always like that, but it's probably just because the twrp-3.1.1-0-venus.img is originally for the P9 lite.
I came accross this thread, where somebody recommends to flash stuff from fastboot.
I have not tried it yet, I only tried to flash recovery from fastboot, and it is failing with the "command not allowed". But maybe I could try to flash some other things ? Any advice ?
For now, despite all my attempts to install stock OTA via dload method, the phone is still trying to boot into lineageOS, and failing.
I came across the "current" firmware version with a check with DC-unlocker : "NEM-L51C432B120"
So I downloaded full OTA firmware b120 on firmware finder software, and the dload method worked !
The installation went well, and after a few minutes of the first boot, I got into phone configuration.
I have one last problem, though : the phone configuration is looping.
There is only 4 languages to choose, so I have to choose english(US), then there is a weird list of countries, none in the EU, where I feel i have to choose united states, then after some steps I have to register to huawei ID thing.
If I try to skip it, it loops to the language selection.
If I try to log in to my original account, it says "device not supported for your location" and then loops to languages. (my original account is in french/France)
If I try to create a new account with new address mail, it works but then at the end says again that "device not supported for your location" and then loops to languages.
I tried with other countries it still loops.
The other languages seems to be Chinese and Japanese, but the configuration is looping too if I choose them.
I tried with/without sim, with/without wifi connected...
Dload the next firmware now and see if it works. Then set the phone
I downloaded and installed with dload method (by removing sd card and copying directly on it the files, because I don't know how to have access to the phone internal & external memory now) the next firmware (b130 version)
The phone booted, it launched a "system optimization" that was a few minutes long, and then the EMUI configuration poped up and looped through language selection, region(country), wifi connection (successful), terms and conditions, and WLAN+(switch between wlan and mobile data automatically).
I feel like the phone is working, the notification led is even blinking when I receive sms, but I have access to nothing because of this damned configuration.
Note: the connection to huawei ID isn't prompted again in the loop once I log in, from the original or the new account. In order to be prompted again to log in to the huawei ID, I have to go to erecovery and reset to factory the phone.

Categories

Resources