Related
Hi
I am a newbie here, dont know much about phones. I just got a P9 , it was EVA-L09C900B136, and i decided to update my P9 to EMUI 5.0 (i mean nougat) i tried many update.app by dload on sdcard but always fail, then i started to read this forum and i spent 2 days to understand what i shall have to do with my P9 EVA-L09C900B136, so i come across to this thread and i used SRK tool to
Unlock bootloader
Twrp recovery
root
oem and cust change to c432
return to stock recovery
all these were done successfully, now my fone shows EVA-C432B136, but i am still unable to STOCK ROM EVA-C432B136 via dload method update , no OTA in the Updater , i have tried many version of Nougat like EVA-C432B182 ,Eva-C432B322, 360, 361 via dload but my Phone stuck at EMUI update 5% and show message "Software install failed !
Failed to check the update package
please download the package again."
Reboot system now, i am hell tired and tense that what i am doing wrong. Please guide and Help
Regards
hi guys,
yesterday i installed the oreo beta on my VTR-L29 but then i brickedd it *cry*. unfortunateley the unbrick methods found here in the forum don't work because the oreo update made some changes in the system file structure...
has anyone an idea what to do?
maybe someone can provide me a recovery image for twrp? (one for oreo, otherwise it wont work) so i can give this a try...
after over 10 hours of fiddeling around a found a really easy solution:
most of you know HWOTA helps with this, but the "normal" version wont work after flashing oreo. but this version is flashed via twrp and is still working!
but you will need a oreo compatible twrp, which you can find here
i know the links are to mate 9 software, but since the p10 and mate 9 are nearly identical, it works on the p10 as well
can you post the step by step guide?
i am on oreo 8.0.0.046 and want to flash another version, or downgrade to nougat because few things don't work on this version
i dont know if downgrading works, i just reflashed the latest oreo.
accordingly to the first link it should work, just flash the TWRP from the second link and then follow the instructions from the first link.
johdost said:
i dont know if downgrading works, i just reflashed the latest oreo.
accordingly to the first link it should work, just flash the TWRP from the second link and then follow the instructions from the first link.
Click to expand...
Click to collapse
failed install twrp- error find twrp 3.0.3, and i replaced to oero mate 9 recovery....
EDIT: success - problem was on the computer
johdost said:
i dont know if downgrading works, i just reflashed the latest oreo.
accordingly to the first link it should work, just flash the TWRP from the second link and then follow the instructions from the first link.
Click to expand...
Click to collapse
i did sucsses to install twrp but on the second step, when i press on install on twrp, the phone restart to erocovey and failed to find the files. what am i doing wrong?
i think that i am stuck with that version forever....
if you reboot to erecovery, you have not successfully installed twrp. you have to install it with "fastboot flash recovery_ramdisk <path to twrp>"
johdost said:
if you reboot to erecovery, you have not successfully installed twrp. you have to install it with "fastboot flash recovery_ramdisk <path to twrp>"
Click to expand...
Click to collapse
you misunderstood me.
i do have twrp, i created HWOTA8 folder on sd card, copied hwota8 update zip, MHA_RECOVERY8 No check and the 3 files that i renamed as it said. after that, from twrp i clicked on hwota8 update zip and begin flash, the phone reboot to stock recovery and failed to install - "files don't found".
please help me fegure out what's the problem.
thanks
t.h.i said:
you misunderstood me.
i do have twrp, i created HWOTA8 folder on sd card, copied hwota8 update zip, MHA_RECOVERY8 No check and the 3 files that i renamed as it said. after that, from twrp i clicked on hwota8 update zip and begin flash, the phone reboot to stock recovery and failed to install - "files don't found".
please help me fegure out what's the problem.
thanks
Click to expand...
Click to collapse
EDIT : the process is sucsses, but its the same version.... 8.0.0.046
Bricked, no TWRP access, any ideas?
Hi.
I know this about a P10, I have a P10 Plus (VKY-L29C605), but the process should be similar, I think.
I bricked my phone after succesfully upgrading from B174 to B321 using HWOTA. After which I decided, since I was at it, to flash the Hyperplus Kernel. This led to a bootloop. To fix it I decided to just go ahead and HWOTA B321 all over again and get over it, and would have probably gone just fine, except I decided to rebrand (C605 > C432) while I was doing that, silly (no, stupid) mistake. This led to the brick I am currently expriencing, I have no recovery access, erecovery or TWRP.
So now I am left trying to unbrick the phone. I extracted the UPDATE.APP for both update_all_hw.zip and update.zip using the Huawei Extractor Tool with no difficulty, except unbricking methods ask for boot.img, which I could not find, so I went along without it and flashed: cust.img, recovery_ramdisk.img (using fastboot recovery_ramdisk command for Oreo), and system.img. All of the commands completed succesfully, but no shebang, still bricked and no recovery access. I figure this has to do with the rebrand as the result after executing the command "fastboot getvar vendorcountry" shows the rebrand pulled through (hw/eu 432).
I am currently downloading HWOTA8.zip (3GB worth of download) to see if I can do something it. I am also downloading the L29C432B360 OTA-FULL, since I believe I am not getting any progress becuase I used the updates for L29C605B321.
The kind people at funkyhuawei told me they could fix it with their tool, but I don't have the money for that right now.
I will post updates, but any ideas would be greatly appreciated.
Many of us have posted over this in the last couple of days. Seems like Funky Huawei unbrick tool was the mehtod to get it work for me. You could try that!
or use dc-phoenix for me it worked (= in the moment i try to capture the usb ports kommunikation so i have the tool with the aktual firmware longer for 3 days :silly:
would first give dc a try 20 bucks for 3 days is ok i think (=
johdost said:
hi guys,
yesterday i installed the oreo beta on my VTR-L29 but then i brickedd it *cry*. unfortunateley the unbrick methods found here in the forum don't work because the oreo update made some changes in the system file structure...
has anyone an idea what to do?
maybe someone can provide me a recovery image for twrp? (one for oreo, otherwise it wont work) so i can give this a try...
Click to expand...
Click to collapse
Must download some software for your phone, unzip update.zip, decompile UPDATE.APP to .iso files, (like recovery.iso, system, iso, vendor iso, boot iso) use fastboot and 10 minuts job, I brik my device over 10 thimes, and repair it.
So I was able to get the C432B360 firmware and I flashed it, but no I can't enter recovery mode because the battery is low (red lightning bolt/red led flash). Anybody know how to charge or force recovery mode boot from fastboot?
If anyone needs, can use my DC-Phoenix account, I don`t need it anymore.
Your username is: cesedy
Your password is: dnL4eHEm
Greting
ure3808 said:
Must download some software for your phone, unzip update.zip, decompile UPDATE.APP to .iso files, (like recovery.iso, system, iso, vendor iso, boot iso) use fastboot and 10 minuts job, I brik my device over 10 thimes, and repair it.
Click to expand...
Click to collapse
Greeting,
Can you explain the procedure of how to do it?
Thank you
Hi everyone! I f'ed my phone today.
It's an EVA-L19C636, that was still on B170 and never received any updates. So I tried to install the next higher build number found via Firmware Finder (IMEI check was successful).
It failed after 5% progress and since then it will only boot into eRecovery. Trying to repair it using WiFi ends with "Getting package info failed".
-3-button-flash is working
-Stock recovery is working
-Fastboot is working
-Phone is locked
-FRP lock is on
I tried to flash stock firmware via dload, but every attempt fails immediately after verifying the update (5% again).
Tested with:
-B190
-B158
Everytime it says: "Incompatibility with current version. Please download the correct update package." The builds have all been for EVA-L19C636.
Then I tried to reflash B170 using Huawei Updater, but HiSuite doesn't support recovery for EVA-L19.
Eventually I even wanted to give B361 a try, but with that update on the SD the phone doesn't even go into flash mode but gets stuck at the Huawei boot logo.
Does anybody have a link for EVA-L19C636 B170, so I could try this using dload?
Or is there any other firmware or method around that might give me my phone back?
Thanks for any idea!
lostbetweenbits said:
Hi everyone! I f'ed my phone today.
It's an EVA-L19C636, that was still on B170 and never received any updates. So I tried to install the next higher build number found via Firmware Finder (IMEI check was successful).
It failed after 5% progress and since then it will only boot into eRecovery. Trying to repair it using WiFi ends with "Getting package info failed".
-3-button-flash is working
-Stock recovery is working
-Fastboot is working
-Phone is locked
-FRP lock is on
I tried to flash stock firmware via dload, but every attempt fails immediately after verifying the update (5% again).
Tested with:
-B190
-B158
Everytime it says: "Incompatibility with current version. Please download the correct update package." The builds have all been for EVA-L19C636.
Then I tried to reflash B170 using Huawei Updater, but HiSuite doesn't support recovery for EVA-L19.
Eventually I even wanted to give B361 a try, but with that update on the SD the phone doesn't even go into flash mode but gets stuck at the Huawei boot logo.
Does anybody have a link for EVA-L19C636 B170, so I could try this using dload?
Or is there any other firmware or method around that might give me my phone back?
Thanks for any idea!
Click to expand...
Click to collapse
Could you fix it?
TitanKnight said:
Could you fix it?
Click to expand...
Click to collapse
Yep, DC Phoenix.
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.
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.