Related
hello, i will try to explain my problem :
My honor was bricked by an error of flash.
I have "repair" it by a way found here on xda : flash boot.img, cust, recovery, system, and after i have could make the update by dload.
Then all was ok under the firmware LO9C432B131.
But now, i can't update to B360...
Before my brick, i had the ota update to B360... but now i have nothing....
If i try the update by dload, it says : "problem compatibility"
I have downgraded to B120 and ota update was good for B131. But nothing for B360
If someone can explain me...thank you so much (actually the phone is no rooted and relocked)
Hi there. Go through the entire rollback procedure and you will be fine: https://forum.xda-developers.com/honor-8/how-to/guide-downgrading-unlocked-rooted-twrpd-t3549281
Put the update.app file in a folder called dload on a SD card. If you haven't got one, flash twrp in fastboot and when in twrp you'll be able to transfer them to internal storage from your pc. Then follow the instruction above. That's how I unbricked mine. Good luck.
sysak said:
Hi there. Go through the entire rollback procedure and you will be fine: https://forum.xda-developers.com/honor-8/how-to/guide-downgrading-unlocked-rooted-twrpd-t3549281
Put the update.app file in a folder called dload on a SD card. If you haven't got one, flash twrp in fastboot and when in twrp you'll be able to transfer them to internal storage from your pc. Then follow the instruction above. That's how I unbricked mine. Good luck.
Click to expand...
Click to collapse
I don't think you understood what OP is saying. He successfully rolled back to MM but he cant go to Nougat anymore.
takichiman said:
I don't think you understood what OP is saying. He successfully rolled back to MM but he cant go to Nougat anymore.
Click to expand...
Click to collapse
Yes, but I believe the issue comes from manual flashing of partitions. I have also tried that when my phone was dead and the recovery and eRecovery always threw "package incompatible" error. I think restoring the entire file system to factory condition (which happens during the rollback process) is the sure best way to fix all issues.
Thanks for your answers,
I finally got the update with the charlie app...(not easy this method !)
But now i don't know if ota will be ok...
I will perhaps do the rollback as you said to restore the entire file system...
Hi everyone.
I am facing a LOT of troubles with my phone (as stated in this thread).
Anyway now I have again unlocked bootloader, installed TWRP 3.1.1, rooted but I have a strange ROM installed by a service tech shop after the phone became unusable.
The problem is that this ROM does not show an update option in settings so I am stuck at 1st march security patches.
Here attached my actual Build Prop file.
The ROM seems to be a BLN-L21C900B300 (never heard of this and not even found on Firmware Finder) and the fingerprints show a "test keys" rom:
device: HWBLN-H
Display: BLN-L21C900B300
Fingerprint: Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave04010520/:user/test keys
If I try to flash via TWRP a BLN-L21C432B360 (which was my previous stock ROM) it does not work and on TWRP appears the following:
......
write radio image
check_write_data_to_partition
write data error
E; unknown command (errno)
update_huawei_pkg_from_ota_zip: update package from zip failed
updater process ended with ERROR: 7
error installing zip file '/external_sd/update_full_BLN-L21_hw_eu_zip'
I cannot flash the FULL zip file with the core of the ROM but I can luckily flash the data, so I could get back Radio Fm and possibility to install themes....
To make the story short: is there someone who knows what this error is? Maybe I can get a solution.
Moreover: maybe this strange "device: HWBLN-H Display: BLN-L21C900B300 Fingerprint: Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave04010520/:user/test keys" is preventing me to flash?
Changing build prop file can be useful?
Thanks to all.
Diamantes said:
Hi everyone.
I am facing a LOT of troubles with my phone (as stated in this thread).
Anyway now I have again unlocked bootloader, installed TWRP 3.1.1, rooted but I have a strange ROM installed by a service tech shop after the phone became unusable.
The problem is that this ROM does not show an update option in settings so I am stuck at 1st march security patches.
Here attached my actual Build Prop file.
The ROM seems to be a BLN-L21C900B300 (never heard of this and not even found on Firmware Finder) and the fingerprints show a "test keys" rom:
device: HWBLN-H
Display: BLN-L21C900B300
Fingerprint: Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave04010520/:user/test keys
If I try to flash via TWRP a BLN-L21C432B360 (which was my previous stock ROM) it does not work and on TWRP appears the following:
......
write radio image
check_write_data_to_partition
write data error
E; unknown command (errno)
update_huawei_pkg_from_ota_zip: update package from zip failed
updater process ended with ERROR: 7
error installing zip file '/external_sd/update_full_BLN-L21_hw_eu_zip'
I cannot flash the FULL zip file with the core of the ROM but I can luckily flash the data, so I could get back Radio Fm and possibility to install themes....
To make the story short: is there someone who knows what this error is? Maybe I can get a solution.
Moreover: maybe this strange "device: HWBLN-H Display: BLN-L21C900B300 Fingerprint: Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave04010520/:user/test keys" is preventing me to flash?
Changing build prop file can be useful?
Thanks to all.
Click to expand...
Click to collapse
U should use dload method
Sent from my BLN-L22 using Tapatalk
arshilhonor6x said:
U should use dload method
Click to expand...
Click to collapse
I forgot to mention: dload not working. Always error.
That's why I think TWRP is the only solution
B300 (at least for the BLN-L24) is the first of two update packages to rollback from Nougat to MM. The first update will take you from the latest firmware to B300 and then the second update will complete the rollback to your device's stock firmware.
dload this package to complete the rollback then do a factory reset and wipe cache partition in stock recovery. After that download and update to the latest firmware and proceed to unlock BL and flash twrp and you should be good to go.
Dazed No More said:
B300 (at least for the BLN-L24) is the first of two update packages to rollback from Nougat to MM. The first update will take you from the latest firmware to B300 and then the second update will complete the rollback to your device's stock firmware.
dload this package to complete the rollback then do a factory reset and wipe cache partition in stock recovery. After that download and update to the latest firmware and proceed to unlock BL and flash twrp and you should be good to go.
Click to expand...
Click to collapse
but you mean that I have to downgrade from Nougat to MM again?
And before doing it I have to flash the stock recovery?
My phone was, we can say, flashed in some way by the tech shop to this strange version of Nougat and with the "test keys" fingertips.
With the files you provide I should "dload"?
I do not understand your post.
please explain better.
Thanks.
Diamantes said:
but you mean that I have to downgrade from Nougat to MM again? Yes
And before doing it I have to flash the stock recovery? No
My phone was, we can say, flashed in some way by the tech shop to this strange version of Nougat and with the "test keys" fingertips. Like I said they did half of the rollback process which is why you are on B300 firmware that you cant find available for download
With the files you provide I should "dload"? Yes
I do not understand your post.
please explain better.
Thanks.
Click to expand...
Click to collapse
Download the zip I linked above from Huawei website. Extract the update.app and put it in dload folder on your external SD card and force flash (power vol - vol +). It will flash all the stock images and return your phone to factory firmware android 6.0 EMUI 4.1. It might bootloop after this but booting into stock recovery (power vol +) and perform factory reset followed by wipe cache partition will get you booting. Then you can OTA update to latest firmware and root again.
Well, I will try this weekend. Now the risk to stay without phone during working days is too high
Ah, BTW, thanks for suggestion.
Dazed No More said:
Download the zip I linked above from Huawei website. Extract the update.app and put it in dload folder on your external SD card and force flash (power vol - vol +). It will flash all the stock images and return your phone to factory firmware android 6.0 EMUI 4.1. It might bootloop after this but booting into stock recovery (power vol +) and perform factory reset followed by wipe cache partition will get you booting. Then you can OTA update to latest firmware and root again.
Click to expand...
Click to collapse
Well, I changed my mind and tried anyway now. I was just too curious.
result:
Software install failed.
Incompatibility with current version.
please download the correct update package.
As usual. Huawei sucks. Full stop.
Diamantes said:
Well, I changed my mind and tried anyway now. I was just too curious.
Click to expand...
Click to collapse
Haha I know the feeling. First time I went to rollback i jumped the gun and said screw it only to have my phone brick and no access to adb/fastboot until the next morning.
As usual. Huawei sucks. Full stop.
Click to expand...
Click to collapse
I agree 100%
Since you have nothing to lose right now just try the whole rollback process. Here is the update that the service center used to get your phone to BLN-L21C900B300. You can try flashing that again through dload or skip to trying to flash this. There are two different firmwares listed as the 2nd part of the rollback and you already said the last one I gave you failed so give this one a shot. Let me know how it works out for you:good:
Dazed No More said:
Haha I know the feeling. First time I went to rollback i jumped the gun and said screw it only to have my phone brick and no access to adb/fastboot until the next morning.
I agree 100%
Since you have nothing to lose right now just try the whole rollback process. Here is the update that the service center used to get your phone to BLN-L21C900B300. You can try flashing that again through dload or skip to trying to flash this. There are two different firmwares listed as the 2nd part of the rollback and you already said the last one I gave you failed so give this one a shot. Let me know how it works out for you:good:
Click to expand...
Click to collapse
nothing mate.
I tried, gives me always error after entering erecovery. Same as above,
Software install failed.
Incompatibility with current version.
please download the correct update package.
Will try another method suggested in another thread.
Will keep you updated just for your curiosity...
Cheers
Diamantes said:
nothing mate.
I tried, gives me always error after entering erecovery. Same as above,
Software install failed.
Incompatibility with current version.
please download the correct update package.
Will try another method suggested in another thread.
Will keep you updated just for your curiosity...
Cheers
Click to expand...
Click to collapse
Have you tried the Team MT huawei multitool to flash the images from the firmware? Use the Huawei update extractor tool to get the boot,cust,recovery,system and userdata.img from the firmware you tried to flash and then put them in the unbrick folder in the multi tool. Put phone in fastboot and run the Multi tool and use the unbrick option. I know your phone is not bricked but this way it will flash all 5 images in order through fastboot. You could actually try and flash the most current firmware with this method and avoid having to system update from MM to Nougat.
yes, exactly, I am trying with multitool . another bro suggested me how to do it even if with a slightly different method.
"You need flash the oeminfo via multi tool and then same firmware file for your current version via dload. It should be fixed".
WTF....never sweat so much for a phone. And never had those problems flashing samsung... and I was flashaholic
Yes, I have learned so much about this phone and the flashing/brick/unbrick process in the last 2 weeks.
Diamantes said:
yes, exactly, I am trying with multitool . another bro suggested me how to do it even if with a slightly different method.
"You need flash the oeminfo via multi tool and then same firmware file for your current version via dload. It should be fixed".
WTF....never sweat so much for a phone. And never had those problems flashing samsung... and I was flashaholic
Click to expand...
Click to collapse
Thats me i guess :silly:
---------- Post added at 08:13 AM ---------- Previous post was at 08:12 AM ----------
Dazed No More said:
Yes, I have learned so much about this phone and the flashing/brick/unbrick process in the last 2 weeks.
Click to expand...
Click to collapse
I am still learning and everytime its different result . Someitmeit works and sometimes it doesn't
Dazed No More said:
Yes, I have learned so much about this phone and the flashing/brick/unbrick process in the last 2 weeks.
Click to expand...
Click to collapse
When I go to multitool "unbrick", it asks for custom.img, but in no update.app of my firmware is present.
Moreover now I just can enter erecovery. It does not boot. I can enter fastboot only. Multitool is now not recognizing the phone. Do you know how to proceed?
I put in dload the firmware .app, but it says "software install failed"
Pheew...I managed to have again that fuc..ng C900B300.
I entered fastboot and repeated the unlock bootloader process. That way the phone got a hard reset and started over. Believe me when I say I tried all the methods I knew.
I think there is something locked somewhere in my partitions (I am not an expert of course) that prevent me to do deep modifications. Now I just can TWRP data but not the core. And again I have no update option. I think I am stuck forever at this stage with 1st march patches and nougat 7.0.
I do not think I will be ever able to have Oreo.
Amen. I am really tired to waste my time with this s**t. Next phone will be again a Samsung or One+. Full stop. Stop chinese brands.
Where are you located, Europe?
Yes
Ok bro I really hope this is it. Full firmware BLN-L21C432B151. I already downloaded it myself and checked with extractor tool it has all the images you need. Since you have fastboot back use the multi tool unbrick again and now that you have all the necessary images cross your fingers it will work.
And I agree with you about the phone. Made up my mind im giving this turd to my sister and getting the OP5T in a few weeks.
Thanks. I will do it this weekend. Today I spent 5 hours to get back my configuration after the hard reset with the apps I use for work. Cannot risk again tomorrow.
In another thread, sashank suggested to change OEM file because probably phone doesn't recognize the firmware I want to install.
It didn't work and lead me to start from scratch with the same strange build.
I will try your method but first I must study better the procedure because I don't want to mess up everything and risking to throw the phone in the garbage (where it belongs in the end...).
Thanks.
So I got an honor 6x that I can't do anything with. I can't flash any ROMs or firmware here's the weird part of it.
Its on some version of EMUI that I can't have the system update menu and it has a button for app twin. It says BLN-L24C567B366 as the model number. Speakers don't work. I can't play videos on it and I can't use the camera in any app.
Here's the really weird part:. If I wipe all partitions and try to flash a room it boots to the same EMUI firmware not the custom rom I can't do anything to change what the rom is. It's like it's stuck in that weird Frankenstein EMUI firmware that I don't even know how I got. I tried restoring anback up cause I formatted my data partition on accident causing it not to boot or something and the backup I restored was not the backup that I made . The backup I made was a stock backup onto an SD card. When I restore it it's rooted and has some downloaded apps on it. And a different launcher. Not what I backed up originally.
I'm at a loss here. What do I do? Ihave full access to adb to flash with fastboot and can get into twrp or stock recovery. No ROMs I flash will work. In twrp it says it was successful. Ut when I boot it doesn't boot to that room, it boots to the weird emui os I can't get rid of.
Has anyone run into this issue or know how to fix it?
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
All my update.app files get stuck at 5% too. And I know honor/Huawei won't repair it cause the warranty is void or if they can they would charge you.
Honestly get the Moto G5s plus. Get the unlocked version at best buy if you're in the states. It's 239 for the 32gb/3gb. Ram model and 299 for 64gb and 4gb. Best budget phone you can get and dual cameras. The ROM support isn't as big as the honor but it is easy to unlock the bootloader and do things. My only ROM issue I've had with this was trying to update magisk the phone had to reboot to install and after that, I had a lock screen set up btw, when I went to enter the pin the screen would go black, the phone would buzz, and go back to the lock screen. And I tried restoring a backup I made but the phone wouldn't boot stuck at the boot logo before the animation.
But the stock firmware I acquired on XDA along with the steps to flash in adb every file in the stock firmware fixed it with no problems at all so at least there's an easy way to restore the stock firmware for my new phone. It's way better than the honor 6x
Seriously tho check out the Moto G5s plus. Out of the box it has Android 7.1.1 mostly stock without all of Google's bloatware. Front mounted fingerprint sensor that you can you for the home, recent apps and back button, and can lock the screen with it if you have fingerprint set up and activate the Google assistant. It also has a notification light that you need root to use. But it has this cool "always on display" type thing that shows a clock and notifications when you move the phone or get a notification. It isn't an AMOLED display tho. It's. 1920x1080p one. Ips good viewing angles. Honestly this is the best phone I've ever used. And it has a Motorola turbocharger in the box. It's really worth it
TurtlePwr82 said:
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
Click to expand...
Click to collapse
i think it could be an issue with the kernel cause the eliteRom has a custom kernel in it.. i have the update.app file for the BLN-L24C567B366 ad B365 files that i can extract and give you all the images that they have and maybe try to get the stock kernel somehow that might help?
TurtlePwr82 said:
The exact same thing has been happening to me. The only OS that will boot up completely is the EliteRom that I attempted on my first flash after bootloader unlocking. I'm almost at my wit's end on how to resolve the issue, as I have tried the guide to roll back to stock posted here at XDA to a tee, with three different update.app files, and each one fails on install package step at 5%.
Hopefully someone with more experience than I will come along and can help us, but I did want to let you know you are not alone with this issue. At this rate, I'll have to get a backup phone to use.
Click to expand...
Click to collapse
Try flashing every single update version until one of them works. Once youve found one that works follow this guide: https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
I had somewhat the same issue, I dload always had an error in 5%, try to flash B360 with dload, that did the job for me.
As for the apps that dont show like the updater(yes, its a system app and is stored in /data) flash the other zips that come with the update.zip
My procedure was:
-Wipe /system and /data
-TWRP flash alternative zips that come with update.zip
-dload B360
That should bring you back to factory stock, In case you still dont have updater and other system apps:
-unlock bootloader(again)
-install TWRP
-DO NOT WIPE ANYTHING
-TWRP flash alternative zips that come with update.zip
-dload B360
xinoxkai said:
I had somewhat the same issue, I dload always had an error in 5%, try to flash B360 with dload, that did the job for me.
As for the apps that dont show like the updater(yes, its a system app and is stored in /data) flash the other zips that come with the update.zip
My procedure was:
-Wipe /system and /data
-TWRP flash alternative zips that come with update.zip
-dload B360
That should bring you back to factory stock, In case you still dont have updater and other system apps:
-unlock bootloader(again)
-install TWRP
-DO NOT WIPE ANYTHING
-TWRP flash alternative zips that come with update.zip
-dload B360
Click to expand...
Click to collapse
I'll give that a try. When you say flash alternative zips that have update.zip do you mean "stock" firmwares off firmware finder?
xSpartacusx said:
I'll give that a try. When you say flash alternative zips that have update.zip do you mean "stock" firmwares off firmware finder?
Click to expand...
Click to collapse
Yes, firmware finder showed me 3 zips, update.zip, update_data_full_public.zip and update_full_BLN-L24_hw_usa.zip, the later 2 are the "alternative zips". Just TWRP flash them.
Also, update_full_BLN-L24_hw_usa.zip might throw an error when flashing it, don't worry, by the stage it fails in its script it already did what it was expected to do and you will not have further problems.
do i need the stock recovery flashed in order to do dload?
well i followed the first half of your guide and it successfully "updated" but my storage is encrypted
xSpartacusx said:
do i need the stock recovery flashed in order to do dload?
Click to expand...
Click to collapse
Not really, I did it when I had TWRP installed
well so far so good now to do the other part also my build number is stil B366 camera and everything works now no updater or anything like that
xSpartacusx said:
well so far so good now to do the other part also my build number is stil B366 camera and everything works now no updater or anything like that
Click to expand...
Click to collapse
Yeah, my build number never changed from B366, the only thing is that when I finished everything even though I'm in B366, EMUI stays in 5.0 and not 5.0.1 as it should be... But that is the only difference and I didn't notice any difference really
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
xinoxkai said:
Yeah, my build number never changed from B366, the only thing is that when I finished everything even though I'm in B366, EMUI stays in 5.0 and not 5.0.1 as it should be... But that is the only difference and I didn't notice any difference really
Click to expand...
Click to collapse
xSpartacusx said:
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
Click to expand...
Click to collapse
Maybe at this point to fix the build number that remains another even if you're in a previous build, it could be sufficient to flash through TWRP a version.img extracted from your ACTUAL build. You can extract it from the update.zip of your actual firmware with Huawei Update Extractor and then flash it as image through TWRP
RedSkull23 said:
Maybe at this point to fix the build number that remains another even if you're in a previous build, it could be sufficient to flash through TWRP a version.img extracted from your ACTUAL build. You can extract it from the update.zip of your actual firmware with Huawei Update Extractor and then flash it as image through TWRP
Click to expand...
Click to collapse
xSpartacusx said:
okay got the stock apps back updater is back everything is fine!! one thing i noticed.. before i started flashing roms, i had an update to EMUI 5.0.1 and i dont have an update for it anymore...?
Click to expand...
Click to collapse
Today I fixed that issue, it showed me that I had B366 but the security patch was on march 2017 and EMUI 5.0 instead of 5.0.1.
What I did was install B366 with the proxy method with Firmware Finder, I made it download the full package from the Huawei Updater (it was around 2.4gb) after it finished the update I had B366, EMUI 5.0.1 and november security patch so all is fine now! :victory:
xinoxkai said:
Today I fixed that issue, it showed me that I had B366 but the security patch was on march 2017 and EMUI 5.0 instead of 5.0.1.
What I did was install B366 with the proxy method with Firmware Finder, I made it download the full package from the Huawei Updater (it was around 2.4gb) after it finished the update I had B366, EMUI 5.0.1 and november security patch so all is fine now! :victory:
Click to expand...
Click to collapse
Good one dude, maybe FF proxy method could help xSpartacusx to solve his issue too!
Hello, guys. I bought two of these phones. BLN-AL30 VERSION is the one that I was using for a while. I tried to unlock its bootloader and it was a complete success. I remember that my phone said BLL-L22 in its about device section and not BLN-AL30 though. I proceeded to install TWRP and rooted it, I also backed up all the partitions so I decided to go for the elite version (TWRP, for I wanted to install their room). Everything was ok. I installed the elite rom which I thought was cool and I used it for a while. Then I decided to switch into slim ROM. I had made the proper back up also and still have them files. I backed up everything because I realized the elite ROM asked for a complete wiping. The next thing I realized was that my phone wouldn't be able to install the slim rom because I had this error:
Unable to wipe vendor /vendor command not allowed.
It also happened with product and version partition. And sometimes it said unable to mount /vendor. (The same for product, version)...
Now, I can't install any other room because of that. And I have downloaded many update.app files to recover and heal my phone as stock but it seems impossible. I have bought another honor 6x and it's coming the next month because I loved this phone but also because if bricked but unrecoverable I'd like to have its parts in case of some repair needed. Is there anyway to recover it? it's so sad. I never thought elite rom would do that to my phone. I assure I followed every single step from its thread. Thanks in advance. Hope you can help.
try to formate data then go to main main screen reboot to recovery now wipe everything. if it is not working then try previous version of elite TWRP or Berlin TWRP. if nothing works then u need to do dload. but u r saying dload is also not working still u have two solutions. download oem info of another region and flash it via TWRP u can try oem info for bln-l22c675b340 https://forum.xda-developers.com/honor-6x/how-to/guide-debranding-to-india-variant-bln-t3679402 now Google for bln-l22c675b340 firmware download it then unzip update app file. now Flash oem info file in TWRP then using sd card flash update app by pressing 3 buttons. this time it will install for sure. if oem file failed to install then extract the oem file then download srk tool put both files in restore folder connect your phone in fastboot restore oem info will work for sure. there is no way to brick honor 6x lot of rescue methods available if this fails still you can use hwota8 method to upgrade oreo.
Thank I'm going to try that
Where can I find the Oreo update thing?. Thanks
evjgl said:
Where can I find the Oreo update thing?. Thanks
Click to expand...
Click to collapse
once it is ready for your model. its in beta phase in China and not released for public yet.
I've somehow bricked my 6X.
I have an EU version successfully debranded to India variant BLN-L22 and upgraded to EMUI 8.0, unencrypted and rooted with Magisk.
Something went wrong during the flash of AEX for hi6250 devices (which is reported to be 6X compatible ): I was mainly stuck in a bootloop except for two times when the phone booted, but internal storage wasn't recognized properly (in settings I was able to see the correct percentage of available space but in default file manager I wasn't able to access it and also downloading files to internal storage was impossible, as if my it was full - which isn't true since I was able to move file there through TWRP file manager).
At that point I was pretty pissed, I've forced fastboot and used update.bat to flash stock Oreo again and here things screwed up.
I took a full TWRP backup before experimenting with AEX and copied it to my pc; I'm able to push it to internal storage through adb, but then TWRP isn't able to restore it, dunno why.
My phone is in these condition now:
fastboot is available, commands from pc are working here
bootloader is unlocked
FRP is unlocked
I have a working TWRP recovery (askuccio 3.2.3) which I can access and use; I'm able to replace it with Elemental 3.2.1, with the one provided in the "update.bat" thread (which is another 3.2.1 version) or with stock recovery
if I replace TWRP with stock recovery and boot into it, it shows the update screen and it freeze at 5%, then reboot; no factory reset option there
when I'm into TWRP I can push files from pc to internal memory through adb
pretty sure my phone is still decrypted, dunno if it's still rooted tho
eRecovery is gone
I have no idea how eRecovery gone missing since I never touched that partition; trying to flash ERECOVERY_RAMDISK.img through fastboot using "fastboot flash erecovery_ramdisk erecovery_ramdisk.img" which fails (remote: command not allowed) and "fastboot flash recovery2 erecovery_ramdisk.img" which fails (remote: partition length get error) as well as through Multi Tool (the size or path does not match the file system markup); if I try to boot into eRecovery I get error mode screen: Func NO : 11 (recovery image) Error No : 2 (load failed) and I have no idea how to try to restore it in another way (pretty sure all I need is to factory reset through it and then reflash the firmware for unbrick my phone).
Atm I've tried only Multi Tool: I can successfully flash everything in the unbrick section but it doesn't solve my problem (guess it's due to my missing eRecovery).
I still need to try Image Download method (which I would like to keep it as last resource since it requires to disassemble my device and since I have a working fastboot and TWRP), HuRu and dload (I don't have a micro SD big enough atm, only 2GB - dunno if it can can work from internal storage the same).
Thank you for any help.
@player615 @shashank1320 @vovan1982 @RedSkull23
I would say the safest option you have is to restore to Nougat via dloading the b340 image which you might have used for debranding. You should be able to restore easily.
shashank1320 said:
I would say the safest option you have is to restore to Nougat via dloading the b340 image which you might have used for debranding. You should be able to restore easily.
Click to expand...
Click to collapse
How do I do that?
I mean, flash OEMINFO and Custom Bin and then dload method as per debranding guide or HWOTA7, since I'm on Oreo/Emui8 now?
You already debrnaded to Indian version and then updated to Oreo right?
shashank1320 said:
You already debrnaded to Indian version and then updated to Oreo right?
Click to expand...
Click to collapse
Exactly. I was on BLN-L21 Nougat (EU), debranded to BLN-L22 (Indian) through fast method (flash oem and cust bin, dload, update through system update) and then upgraded to Oreo through HWOTA8_BLN - script method.
Multi Tool list my device as BLN-L22 8.0.0.510(C675).
Just dload b340 indian variant. You should be fine
I restored my device countless times with HuRUpdater, the best tool I used on Huawei devices. It always go fine, but a microSD of at least 3GB is required (files to flash are usually 2,70GB). Probably the device won't boot with stock recovery because as you pointed out, it needs to format first before booting since that you was decrypted. HuRUpdater needs to be executed from microSD because it flashes files from there to internal storage, so flashing from there isn't allowed due obvious reasons.
Looks like you'll need to dload, as my friend Shashank1320 said. You need to start again with a fully working system before going elsewhere and at the moment things look bad. The rest is always obtainable again (TWRP, ecc.)
shashank1320 said:
Just dload b340 indian variant. You should be fine
Click to expand...
Click to collapse
RedSkull23 said:
Looks like you'll need to dload, as my friend Shashank1320 said. You need to start again with a fully working system before going elsewhere and at the moment things look bad. The rest is always obtainable again (TWRP, ecc.)
Click to expand...
Click to collapse
dload doesn't work, I guess it's because I miss eRecovery.
If I hold vol+ vol- and power my phone boot into TWRP; I've tried replacing it with stock recovery but it freeze at 5%.
Any way to flash eRecovery from fastboot or as a zip from TWRP?
Gonna get a SD and for HuRu if I won't be able to solve it differently.
Edit: managed to boot into dload screen, but it states "software install failed".
AleNonsense said:
Edit: managed to boot into dload screen, but it states "software install failed".
Click to expand...
Click to collapse
That message is because the package you picked is wrong. What was your build number, BLNL22C636B510CUST..? (Don't remember if this is the build of first Indian Oreo build dated June/July 2018)
RedSkull23 said:
That message is because the package you picked is wrong. What was your build number, BLNL22C636B510CUST..? (Don't remember if this is the build of first Indian Oreo build dated June/July 2018)
Click to expand...
Click to collapse
I'm not sure since I don't have my device at hand atm: yesterday I got a 16GB SD and tried with HuRU but without success (trying to flash the zip returned me an error with every version of the package), so I contacted the assistance since I still have some months of warranty. I've tried to restore it as stock as possible before handling them the phone so I hope they won't make me trouble and fix it :angel:
Anyway I've always used firmware provided by shashank, both to debrand to indian variant and to upgrade to Oreo, so you may recover build number from those threads for scientific purposes!
AleNonsense said:
I'm not sure since I don't have my device at hand atm: yesterday I got a 16GB SD and tried with HuRU but without success (trying to flash the zip returned me an error with every version of the package), so I contacted the assistance since I still have some months of warranty. I've tried to restore it as stock as possible before handling them the phone so I hope they won't make me trouble and fix it :angel:
Anyway I've always used firmware provided by shashank, both to debrand to indian variant and to upgrade to Oreo, so you may recover build number from those threads for scientific purposes!
Click to expand...
Click to collapse
For me HuRUpdater never failed a shot, you just have to choose the correct build and rename the zips as per instructions in OP. Usually the zips are three, by the way. "BLN-L22HNC675CUSTC675D1B510 (8.0.0.510)" is the correct build number for Oreo India, if you use HuRU with the three zips included in this build the successful flash is guaranteed (done it personally many, many times).
Now, if you contacted assistance and you can take advantage of remaining months of warranty wait and see what they say. Good luck!
Reflash EMUI 8 with Hwota 8, but first wipe data partition with TWRP.
player615 said:
Reflash EMUI 8 with Hwota 8, but first wipe data partition with TWRP.
Click to expand...
Click to collapse
Wait: wiping /data with TWRP makes it visible through custom recoveries since that it removes encryption, but when you flash whole EMUI 8 on system stock recovery_ramdisk is reflashed on the recovery partition too, and it forces to reformat /data before booting because if not it'll say that OS is seriously corrupted bla bla bla... EMUI 8 doesn't have to run encrypted?
By the way HuRU is faster, easier and leaves bootloader unlocked.
RedSkull23 said:
If you use HuRU with the three zips included in this build the successful flash is guaranteed (done it personally many, many times).
Click to expand...
Click to collapse
Nope: don't get me wrong, but I'm here since 2012 and I'm pretty used to this kind of stuff.
I can assure you I haven't picked wrong packages nor any other noobish error: in fact I wouldn't even had to post here if I had encountered just some standard problem lol... my device wasn't fixable through usual ways, or else I would have been able to
RedSkull23 said:
Now, if you contacted assistance and you can take advantage of remaining months of warranty wait and see what they say. Good luck!
Click to expand...
Click to collapse
Just heard back from assistance and they are waiting for a new motherboard since there was nothing to do, good to me I was still covered by warranty.
Now it would be nice to know what screwed up my device so bad, since I hadn't any problem till the flash of AEX for hi6250 devices (so 6X compatible) and even in the case it wasn't flashing a wrong rom has never fked up a motherboard in my experience, but whatever.
My only trouble is I'm pretty sure I won't be able to unlock bootloader when my phone will be back, now
Also, thank you to everyone who tried to help!
try this
i had issues also until i found this step by step, i named everything just as he has pictured and made sure to just add the .zips all 3 needed, got correct FW from FW finder and also be sure to put the actual HuRuUpdater.zip in the same folder with the FW files and name the parent folder just like the pic on post shows...poof working stock FW and did not relock my BL....Honor 8 FRD-L04 reverted from no OS to stock 7.0 on EMUI 5 https://www.getdroidtips.com/hurupdater-tool/#comment-109621
RedSkull23 said:
For me HuRUpdater never failed a shot, you just have to choose the correct build and rename the zips as per instructions in OP. Usually the zips are three, by the way. "BLN-L22HNC675CUSTC675D1B510 (8.0.0.510)" is the correct build number for Oreo India, if you use HuRU with the three zips included in this build the successful flash is guaranteed (done it personally many, many times).
Now, if you contacted assistance and you can take advantage of remaining months of warranty wait and see what they say. Good luck!
Click to expand...
Click to collapse