Bricked Honor 5c NEM-L51 ? - Honor 5C Questions & Answers

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.

Related

VIE-L29C636 half-bricked. Help needed

Earlier I upgraded my phone to VIE-L29C636B362 but there was huge battery drain so I decided to rollback to Android 6.
What I did:
- Flashed the rollback package -- successfully.
- Flashed B202, the latest ROM that I used without problem and the battery drain was modest -- successfully. I used the 'dload' map and three-button-push method. I had to flash two package; the big update app from the 'update.zip' and the content of 'update_data_full_hwspcseas.zip'. (It was strange that the second package was flashed very quickly, but seemingly all went well.)
- I checked: I got a VIE-L29C636B202 ROM. The phone worked but its behavior was a little bit strange. E.g. I could not change the icon set in Themes, every theme showed the same icons, most of them stock Android design.
- That is why I flashed the content of 'update_data_full_hwspcseas.zip' again, maybe from another package, obtained via Firmare Finder. I am not sure.
- Since then the phone does not boot, it always shows the Huawei eRecovery (see picture).
- I tried to flash from SD Card the B202 main update.app again, but the error message said it is wrong package. I tried to escape from the situation forward and flashed the B362. It started normally but after 37% aborted.
I don't know what to do now. The phone has NO root, NO TWRP, it is in factory state. The Bootloader is closed.
The Huawei eRecovery tried to download a package to repair the system but reported back that could not find any.
I get the same issue with icons remaining stock Street any flash as well.
Assuming you get back to running 202, you need to find the hwt file you want (should be links here on xda) and and copy it to root>data>hw_init>system>themes then reboot. You may also need a copy in HWThemes folder on internal storage.
I never need to flash anything other than the 202 file
Unfortunately I can't help with the brick issue.
Thanks for the advice, I'll use it but first I should revive my phone...
How long did you run 362? before you decide to rollback..?
Did you do an FR after update to 362?
ppl often panic when battery going crazy in the beginning of an update, that's why i ask.
to solve this issue you need to unlock bootloader , flash twrp then flash update.zip and hw_spcseas_data.zip then reboot , after reboot done just force flash update.app in dload folder by 3 button method then everthing will return to full stock state.
itongx said:
to solve this issue you need to unlock bootloader , flash twrp then flash update.zip and hw_spcseas_data.zip then reboot , after reboot done just force flash update.app in dload folder by 3 button method then everthing will return to full stock state.
Click to expand...
Click to collapse
OK, I tend to try it. But which version's update.zip should I flash with TWRP? B202? It was the last working version on the phone, so I guess I have to use B202 again. Am I right?
ctibor said:
OK, I tend to try it. But which version's update.zip should I flash with TWRP? B202? It was the last working version on the phone, so I guess I have to use B202 again. Am I right?
Click to expand...
Click to collapse
any version you have just to make sure use correct version of twrp if you are on emui4 use twrp for emui4 then flash any version for emui4 , can do same thing if youare running emui5
Problem solved.
Finally the DC Phoenix (PC software) helped. I could flash B202 from scratch and I got back to the same status where I began. Working system but no Huawei themes. So I went to Nougat again: flashed the B370 ROM. Everything works well now. (Certainly I still don't evaluate the battery drain, it needs more time.)

Unable to boot into Nougat 7.0 or MM, NEM-l22

Bootloader : Unlocked
Recovery : Revolution Nougat Recovery for p9 lite
Device : GT3 NMO-L22 (NEM-L22 oeminfo flashed)
So I've soft bricked my phone pretty much, I have tried plenty of methods to try and rollback to MM but have had absolutely no luck. I have been able to flash boot images, recovery images and system image files extracted from nougat update.app files and marshmallow update.app files but the phone will hang on "device is now booting" .
Either the dload method will keep giving errors or the extracted files wont work I have tried flashing some roms but still nothing. sort of dont know what to do but would flashing another devices oem info help to install update.app files via dload method ?
Any help would be greatly appreciated cheers
take image files from b100 update.App
Hi i got exactly same problem as your, i tried everything for like 8 hours and nothing successful, then i tried "Huawei Multiool" and flash recovery for honor 5c emui 5.0 then i rebooted my phone and it works i was ****ing happy because twrm not work for me
Sorry for my english
btw it doesnt depend whats your model there are also custom recoveries for p9 lite
links please Ive found links for both suggestions but not sure if Ive found the right ones thanks
Update : Okay so I need help still guys and didnt want to start another thread but I still have been unable to find an update package that will install using dload method. Please help I've tried everything including extracted img files using huawei update extractor. like i said in the op i dont know which update to download as I have tried alot and none of them seem to be doing the trick. please any help would be much appreciated
Edit : Have also tried the recommended fixes but none have made a difference unless im downloading the wrong files of course every single update file gives me the same error using dload method "incompatibiltiy with current version please download the correct update package"
so after what i thought would be an impossible fix i've finally found my solution, I dont know if this will work for everyone else but its definitely the easiest method I found through trial and error and trying way to many other methods i was hoping would work but here it goes.
Through the twrp 3.0.2 recovery recommended above I flashed hw_EU.zip recommended by user DRUGER in another thread for changing firmware to EU NEM-L51
after that I simply downloaded both the update.zip and update_data_full_hw_eu.zip for NEM-l51C432B120 and extracted only the update.zip file and placed the update.app file in a dload folder on the root of my SD card
I then wiped every partition apart from internal storage, oeminfo and sd card.
After that I tried to flash the update.zip giving me error 7 but I ignored it and then went on to flash the update_data_full_hw_eu.zip after that I wiped the cache and powered off the phone.
After that I used the 3 button method to go through to the update mode and for the first time ever I was able to install the update with no hitches, I am now on B130 build and honestly couldn't be happier I tried so many different firmware recommended everywhere but this was the only method that worked for me, It may not be the original model firmware and it may not work for other people but it worked for me so Im glad.
Also I may have made some unnecessary steps along the way but its better to include everything I did in case someone else decides to give this a try Im just happy to have a working phone again
Hey I need Nem L22 OEM can you please share here?
Fixed your device?
Just the device with proper OEM you can dload with proper update. App of yours oem.
After dload, not booting, all you need is to reboot to stock recovery and giving it a factory reset.

Problems with Honor 5C/7 Lite/Nem-L21, bootloop and more

Hi
I have searched through just about every thread and tried just about every trick in the book to make my Honor 5c/7 Lite/NEM-L21 to work again but nothing works for my problem. I'll try to describe what I did, what I have tried and what I am able to do with it.
What I did
Unlocked bootloader the official way with code from Huawei.
Flashed twrp recovery
Installed SuperSU from twrp and rooted the phone
Tried to install some custom roms and some stock roms, eventually I tried to install something that apparently wasn't for my specific model and twrp started to throw errors at me
The main error whenever I tried to do something in twrp was "can't mount /cust.." and some more error message which I can't remember
After that I tried to reboot my phone and hoping that it would somehow heal magically, which, of course, it didn't
What I did not do
Take a backup before I started to mess with my phone, stupid, yes I know, but tell me if you have to
What I am still able to do
E-recovery: can boot into E-recovery and connect to wifi and search for package info but then it fails with an error message stating that something is wrong with the package
Stock recovery dload method: Starting to install the package but halts at 5% and then the phone reboots and boots with error stating that I should update again, not sure about what package is loading since I think I have a dload folder both on the internal and the external sd card, but I cant see the internal sd card anywhere (loading the external sd card through another phone)
Fastboot: can boot into fastboot with volume- and power button and do almost all the fastboot commands, but adb does not detect my phone.
What I have tried
Googled, looking here and searching deep inside myself for answers (without any luck, needles to say)
Tried downloading a stock rom NEM-L21***B132, Android 6.x Emui 4.1 and extracting boot.img, system.img, recovery.img and cust.img and while boot and recovery flashes fine with this extracted images everything goes ape**** when trying to flash cust and system, with cust I get a partition error while writing and with system I get a sparse flash write failure, I have no idea why this rom fails while I'm able to flash above mentioned files perfectly fine with a stock nougat rom (Nougat is the reason I started this adventure to begin with). When I flashed all the files fine and try to dload the whole update.app I get nowhere anyway, just a bootloop.
Tried to erase and reformat cust and system but when I try that in fastboot I get a remote: command not allowed.
Tried to flash twrp recovery and the flashing succeeds but I cant boot into it, tried several different versions designed for both 'nougat and marshmallow.
What I need
Someone to point me in the right direction because I am totally lost and almost going crazy after trying everything.
All the help and tips I can get from you guys is much appreciated, I'm willing to try everything you throw at me and answer any questions regarding my issue!
Thanks in advance, Jeremias
dload method, use B100 package.
thelous said:
dload method, use B100 package.
Click to expand...
Click to collapse
Thanks for your fast reply, I do have a few questions for you:
1. Do you have any idea where I can find the B100 package? Tried googling but no luck so far, lowest I can find i B130.
2. Should I just put it on the external SD card and try to get it to update or do I need to extract the *.img and flash them in?
3. Could it be a problem that I might have a dload folder on the internal SD card with a different package?
Thanks again.
jerre84 said:
Thanks for your fast reply, I do have a few questions for you:
1. Do you have any idea where I can find the B100 package? Tried googling but no luck so far, lowest I can find i B130.
2. Should I just put it on the external SD card and try to get it to update or do I need to extract the *.img and flash them in?
3. Could it be a problem that I might have a dload folder on the internal SD card with a different package?
Thanks again.
Click to expand...
Click to collapse
i think somewhere in xda theres B100. all you need is update.app file in dload folder on external SD card (recovery wonr read internal memory since it could be corrupted etc...)
thelous said:
i think somewhere in xda theres B100. all you need is update.app file in dload folder on external SD card (recovery wonr read internal memory since it could be corrupted etc...)
Click to expand...
Click to collapse
Found it, crossing my fingers that it will work this time.
Unfortunately I can't get it to update with the B100 package and the dload method. I can start the stock recovery and the update starts but it freezes at 5% and then the phone reboots with no error message and the bootloop continues.
Any more ideas?
Still no luck for me, anyone got any ideas?
jerre84 said:
Still no luck for me, anyone got any ideas?
Click to expand...
Click to collapse
what was your phone build number before all these? EMUI 4 or 5?
shashank1320 said:
what was your phone build number before all these? EMUI 4 or 5?
Click to expand...
Click to collapse
It was EMUI 4. The reason for all this was that I could not get the Nougat-update in any way.
I think that I might be on EMUI 5 now because I can't get the stock recovery from the B100/B132 package to boot but when I flash the recovery from B351 or similar it can boot but I'm, still not able to get any update to work.
jerre84 said:
It was EMUI 4. The reason for all this was that I could not get the Nougat-update in any way.
I think that I might be on EMUI 5 now because I can't get the stock recovery from the B100/B132 package to boot but when I flash the recovery from B351 or similar it can boot but I'm, still not able to get any update to work.
Click to expand...
Click to collapse
I had same issue on mine. I updated to nougat manually with few bugs and then flashed custom arsenic ROM

[SOLVED] EVA-L19 "Software Install Failed" when updating

Hi everyone,
Just taking my chances if anyone in here encountered the same issue. I'm currently on EVA-L19C636B381 and the System Updater is asking me to update to B390. However, I've tried downloading the update several times but keep on getting the "Software Install Failed" error message. Any ideas on how I can update the firmware and ensure that updates will be installed seamlessly moving forward?
Note that the bootloader was unlocked before and it used to have TWRP. Now I've relocked the bootloader and installed the stock recovery.
Thanks!
Clarification:
Version: EVA-L19C636B381 (everything's stock: BOOT, RECOVERY, RECOVERY2, SYSTEM)
Would like to update to: B390
Issue: Getting "Software install failed" error message after downloading through System Update
** Used to have TWRP and root. Flashed stock IMGs
Update:
Issue solved! Please see last post for the update/solution.
thedarkinvader said:
Hi everyone,
Just taking my chances if anyone in here encountered the same issue. I'm currently on EVA-L19C636B381 and the System Updater is asking me to update to B390. However, I've tried downloading the update several times but keep on getting the "Software Install Failed" error message. Any ideas on how I can update the firmware and ensure that updates will be installed seamlessly moving forward?
Note that the bootloader was unlocked before and it used to have TWRP. Now I've relocked the bootloader and installed the stock recovery.
Thanks!
Click to expand...
Click to collapse
If you had TWRP, maybe you also rooted - root will also block OTA (you had to unroot in that case).
Btw, unlocked bootloader does not prevent/affect OTA
zgfg said:
If you had TWRP, maybe you also rooted - root will also block OTA (you had to unroot in that case).
Btw, unlocked bootloader does not prevent/affect OTA
Click to expand...
Click to collapse
Hi zgfg!
Thanks for the response. Yeah, if I'm not mistaken, it used to be rooted. However, I've installed stock B381 and stock recovery already, and still getting the error message. Checked with Root Checker and it says that there's no root access.
thedarkinvader said:
Hi zgfg!
Thanks for the response. Yeah, if I'm not mistaken, it used to be rooted. However, I've installed stock B381 and stock recovery already, and still getting the error message. Checked with Root Checker and it says that there's no root access.
Click to expand...
Click to collapse
Rooting affects Boot partition, it must be flashed back to stock. And it's recommended to Hard reset then, before OTA. For OTA, go to Settings, and choose Full upgrade
zgfg said:
Rooting affects Boot partition, it must be flashed back to stock. And it's recommended to Hard reset then, before OTA. For OTA, go to Settings, and choose Full upgrade
Click to expand...
Click to collapse
Yeah, that's what I did. Basically, everything's stock already. That's why I don't understand why I'm still getting the error message.
You can try downloading the full stock rom package and manually update with the dload method.
noalt said:
You can try downloading the full stock rom package and manually update with the dload method.
Click to expand...
Click to collapse
Hi noalt! Thanks for the response.
Yeah, kinda wondering if that'll work. For the dload method, does it really require an SD card? Also, for the dload method, it is okay to get the latest full package instead? (Upon checking using Firmware Finder, the latest one is B395 or B396)
Any steps that I can follow to do a sort of "clean install"? As in free of any modifications? In short, some kind of steps as alternative for using System Update (which I can't use due to the error message I'm getting)?
You can use any stock rom you like. If it is the same or higher build, you may not need to do a rollback. The dload method only works from sd-card. It will be a clean install.
I think the dload method is the safest. Alternatives are flashing images indiviually through fastboot but I have no experience with that, except for the recovery.img
noalt said:
You can use any stock rom you like. If it is the same or higher build, you may not need to do a rollback. The dload method only works from sd-card. It will be a clean install.
I think the dload method is the safest. Alternatives are flashing images indiviually through fastboot but I have no experience with that, except for the recovery.img
Click to expand...
Click to collapse
I see. Regarding the dload method, if by sd-card you're referring to the internal memory, I'm afraid I've tried that (creating a dload folder and putting nothing else but the UPDATE.APP file inside) and I'm getting a Software Install Failed error message as well. :crying:
No, I mean a micro sd card. You can put one in the tray next to your sim card. And then you have to shut down you phone and boot it holding vol+ vol- and power until you get into the updater.
noalt said:
No, I mean a micro sd card. You can put one in the tray next to your sim card. And then you have to shut down you phone and boot it holding vol+ vol- and power until you get into the updater.
Click to expand...
Click to collapse
Ah yes, that's the one that I have yet to try (as I don't have an SD card, the other spare phone that I have is a 5s).
UPDATE:
I eventually was able to install EVA-L19C363B395!
Initially, I was having issues with the partitions (as I tinkered around a bit with TWRP) and was stuck with the Huawei logo and not proceeding with the booting. So what I did was I flashed BOOT.img, SYSTEM.img, RECOVERY.img, and RECOVERY2.img from the stock B381 (use the Huawei Update Extractor to get it from the UPDATE.APP file from the update.zip (the large file), do some Googling to find it here in XDA . Then I was still experiencing the said issue so I used the stock recovery's features: "Wipe data/factory reset" and "Wipe cache partition" to sort of repair the issues with the partitions (didn't know how to properly do it in TWRP.
Then B381 booted and was able to access USB debugging (initially had issues with this as well, after flashing images, Settings app kept on crashing when trying to access Security and Developer options).
And then finally followed the HWOTA procedure made by @Atarii. Make sure that you're going to use the proper recovery file for your version (L09, L19, etc). According to the steps, being rooted is also required so I used @zgfg's SuperSU 2.82 permissive (https://mega.nz/#F!w41RmZKB!IG53JadhjUKgFK8anbctIw). Make sure to flash it before flashing the nocheck recovery file.
And voila! That should do it. Based on what I'm seeing, root has been removed after doing the HWOTA procedure, same goes for TWRP, and bootloader's locked again.
Thanks to all of those who responded and credit goes to @Atarii and @zgfg for the procedure and file/link.

{SOLVED}PLEASE READ Bricked My phone. A help please **URGENT**

**URGENT** i have my p20 pro 6/128 with 9.0 last version ROOTED somehow i found a article.. the root was success. Tried to flash official twrp with twrp app and then everything was like HELL.
If i let my phone boot says error! func no: 10 boot image. error no :2 load failed. i faced something simillar when trying to get into recovery sometimes.
I can get into erecovery cant format or download official firmware. I can get into fastboot, download mode. I am gonna tell you everything . every program i tried AND FAILED!
TRIED: multi tool for huawei ( i download a version i think its 165 something when i press flash selected the program closed)
TRIED: to FLASH like 10 times ramdisks, recoverys, CANT FIND BOOT.IMG.
TRIED: Re-flash 9.0 says missing zip files THATS IMPOSIMPLE NOTHING IS MISSING I AM SURE
TRIED: a guide that said to download firmware and i would find a folder named DLOAD. i did everything. COULDNT FLASH SOMETHING ON DOWNLOAD SAYS ERROR
TRIED: ALMOST EVERYTHING
PLEASE HELP ME, HOW TO FIX IT? its very important for me and for everyone who is facing the same problem
Phone infos From Multi tool program http://prntscr.com/min398
and the firmwares i tried 1) http://prntscr.com/min3tn
2) http://prntscr.com/min40j
SEE SOME POSTS BELLOW TO SEE HOW I FIXED IT SUCCESS AFTER MANY ERRORS
1 found this post, and flashed all of them BUT there is not ramdisk on the files. i looked on two different firmwares which should i flash over ramdisk which doesnt exist?
first i run the command fastboot flash kernel kernel.img and i could boot into TWRP for first time. now i cant.
there are not errors for now. only if i boot my phone says phone keeping booting.
when i got to twrp and tried to reboot into system said there is no OS.
How and which os i should flash? since Multi tool program kicks me
HELP
https://forum.xda-developers.com/honor-9/help/help-softbricked-h9-oreo-t3750282
So you're typing a little erratic.
Can you get to eRecovery? This is your best option..
If not then you'll need to reflash all the parts of the OS back to the phone manually..
Beyond that you'll need a recovery method, not sure if it's a device of a program but it can usually help, depends on what is borked.
dladz said:
So you're typing a little erratic.
Can you get to eRecovery? This is your best option..
If not then you'll need to reflash all the parts of the OS back to the phone manually..
Beyond that you'll need a recovery method, not sure if it's a device of a program but it can usually help, depends on what is borked.
Click to expand...
Click to collapse
i can get into erecovery i cannot download the official and flash it throught there says error.. what else i can do
I cant understand what yyou saying here Beyond that you'll need a recovery method, not sure if it's a device of a program but it can usually help, depends on what is borked.
I get into Erecovery if i press download latest version and recovery after some times when i put the wifi pass says error. Error i got also on HIsUite when i tried to format from there and download the latest versio. So we go manually but HOW? i tried almost everything
i tried this https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
success all command went trhough the phone
the problem is i cannot flash twrp
my phone has unlocked bl
well i did a lot of search if you ask me i download 5-7 different programs that can flash stock firmware. ONE seems to be legit for 9.0 RE-flash 9.0 which has commands on its script like this guy says and he helped me too
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
also if someone cant boot into twrp after the frist steps and see the erecovery just format everything from erecovery and then it will boot to twrp.
also now says installing update.
i hope imeis serial numbers etc wont lost..
Thats the script i found i dont remeber where
http://prntscr.com/mitvum
but i can upload somewhere the files
if you run FLASH.bat and says MISSING ZIPS then remove the update."zip" {ZIP PREFIX FROM THE NAME OF THE FILES ONLY} and run again the bat
the procedure may take 10-30 mins
What about the otg method?
Also I would never use a tool like this.
StonebridgeGr said:
**URGENT** i have my p20 pro 6/128 with 9.0 last version ROOTED somehow i found a article.. the root was success. Tried to flash official twrp with twrp app and then everything was like HELL.
If i let my phone boot says error! func no: 10 boot image. error no :2 load failed. i faced something simillar when trying to get into recovery sometimes.
I can get into erecovery cant format or download official firmware. I can get into fastboot, download mode. I am gonna tell you everything . every program i tried AND FAILED!
TRIED: multi tool for huawei ( i download a version i think its 165 something when i press flash selected the program closed)
TRIED: to FLASH like 10 times ramdisks, recoverys, CANT FIND BOOT.IMG.
TRIED: Re-flash 9.0 says missing zip files THATS IMPOSIMPLE NOTHING IS MISSING I AM SURE
TRIED: a guide that said to download firmware and i would find a folder named DLOAD. i did everything. COULDNT FLASH SOMETHING ON DOWNLOAD SAYS ERROR
TRIED: ALMOST EVERYTHING
PLEASE HELP ME, HOW TO FIX IT? its very important for me and for everyone who is facing the same problem
Phone infos From Multi tool program http://prntscr.com/min398
and the firmwares i tried 1) http://prntscr.com/min3tn
2) http://prntscr.com/min40j
SEE SOME POSTS BELLOW TO SEE HOW I FIXED IT SUCCESS AFTER MANY ERRORS
Click to expand...
Click to collapse
dladz said:
What about the otg method?
Also I would never use a tool like this.
Click to expand...
Click to collapse
like i said in the first post the otg method with the dload folder failed.
Why you wouldnt try it?
StonebridgeGr said:
like i said in the first post the otg method with the dload folder failed.
Why you wouldnt try it?
Click to expand...
Click to collapse
Because I've got no need to mate, manual is always safer.
Have you asked in the thread where you got the tool?
I'm not sure what else to suggest pal
dladz said:
Because I've got no need to mate, manual is always safer.
Have you asked in the thread where you got the tool?
I'm not sure what else to suggest pal
Click to expand...
Click to collapse
now everything is fine but i cant root..
StonebridgeGr said:
now everything is fine but i cant root..
Click to expand...
Click to collapse
Everything is fine? What did you do?
With root Judy follow the instructions that have worked for other people. Don't rush things.
dladz said:
Everything is fine? What did you do?
With root Judy follow the instructions that have worked for other people. Don't rush things.
Click to expand...
Click to collapse
i post i early post a link that helped me a little bit i think i edited the .bat script
also i made a video and post about rooting and everything is fine.
the problem is you can have twrp and magisk root both:/
either you have root and not twrp or either you have twrp and not root

Categories

Resources