Hey guys I am pretty experienced with bricking and unbricking this device BLN-L24 and even wrote a quick guide on it but I'm currently stumped and think the phone may not be recoverable. I had given the device to my sister unrooted but unlocked and twrp installed. She requested I return it to stock once and for all so she could get OTA and this is where it all went to hell.
I flashed stock recovery and boot image then relocked bootloader but the phone wouldn't boot past the Honor logo so I did the rollback and the phone would boot after that. Then I did the dload to stock BLN-L24C567B110 firmware and the phone once again failed to boot so I used the multi tool to unbrick and the phone was good on stock firmware. The phone then downloaded the BLN-L24C567B360 firmware through updater and upon restarting the phone no longer had the Honor splash screen and boot animation but instead was the Huawei logo I had never seen before, and build was now test keys so still could not update.
I figured I would just rollback again and try it all over so I dload the rollback again and it says update successful but fails to reset after it restarts, and phone is stuck on "your device is now booting" screen. I have erecovery but it fails, I've tried dloading every firmware I can find for BLN-L24C567 and they all fail and say incompatible. I have no recovery but I do have fastboot. I can flash twrp and it says successful but I cannot get to it and I cannot boot the twrp image from fastboot so that I can flash the oeminfo.zip. I can manually flash boot.img, recovery.img and userdata.img, but cust and system.img fail. This leads me to believe that somehow the oeminfo and region data are messed up which is why every C567 firmware for my region says incompatible. Is there anything I can do that I haven't done already?
@shashank1320 really hoping you got some ideas here bro....this is crazy that doing something as simple as updating through the stock OS can do this. Gotta love Huawei :silly:
Edit: I have tried dloading the update.app from every single firmware for this device.
BLN-L24C567B110 - failed incompatible
BLN-L24C567B342 - failed incompatible
BLN-L24C567B360 - failed incompatible
BLN-L24C567B365 - failed incompatible
BLN-L24C567B366 - failed incompatible
BLN-L24C900B300 - successful update, phone restarts and data reset fails
After flashing C900B300 I can access stock recovery and can wipe cache partition but wipe data/factory reset fails at 6%. If I flash twrp recovery in fastboot it says successfull yet I can't access it and instead goes to erecovery which also fails to find or install package. I am so stumped.
Since all the firmware for this model says incompatible except the rollback package I figured it might have a problem with cust but when I try to flash cust.img it fails and says partition error.
Checking buddy. Will see what best we can do to restore the phone
Thank you bro. What Huawei devices use this boot animation? After the device took the BLN-L24C567B360 OTA update and went to test keys this was the boot animation, and the
keyboard was one I had only ever seen on on Elite ROM where it rebrands the device as a P9 Lite or something. It was default on the Huawei Swype which is never default on the BLN-L24 its always google keyboard.
Its almost as if the device took an OTA for BLL-LXX or soemthing like that. That would explain why all firmware for my model are incompatible, but what is strange is when build was test keys the model still said BLN-L24 even though it was nothing like I had ever seen the device in the many times I had reset it.
Are there any Honor 6X variants that have the Huawei boot animation I posted in addition to the Huawei Swype keyboard enabled by default? Im trying to narrow down possible models of firmware I can try to flash and recover the device...as of now its not like I can screw the device up anymore than it already is.
Just when I was about to write the device off as unrecoverable and throw it in the trash, I decided to try flashing Elite modded TWRP and surprisingly I was able to boot into twrp. I then found a long forgotten about full backup of B360 firmware that I was able to restore and get the phone to boot. Even though I restored a backup of BLN-L24C567B360, the model was listed as generic_a15, build was BLN-L24C900B300 and processor said octacore 2.1ghz instead of Kirin 955. I had no audio and twrp showed my product partition as 0mb.
So to get it back to stock I dload B110 firmware successfully, stuck on Honor logo so boot to recovery and wipe cache and factory reset, still won't boot past Honor screen. Unlock bootloader and use Huawei multi tool unbrick followed by another dload of B110 and phone finally boot. Updated successfully to B360 and then again to B365.
Now the phone is stock, locked and will never be modded again. These damn phones are just too finnicky but just goes to show even when all hope is lost you still might be able to save a phone from being a paper weight
Dazed No More said:
Now the phone is stock, locked and will never be modded again. These damn phones are just too finnicky but just goes to show even when all hope is lost you still might be able to save a phone from being a paper weight
Click to expand...
Click to collapse
All solved bro?
shashank1320 said:
All solved bro?
Click to expand...
Click to collapse
Yep all solved. For the life of me I cannot understand why flashing the modded twrp allowed me to boot to TWRP on the first try today. I kid you not I flashed openkirin twrp image successfully probably 30 times over the past few days and everytime would boot to erecovery. What saved me was finding that backup folder with a couple backups in it, I thought I deleted them long ago.
Im still lost as to what happened to the phone when it took the OTA and why boot animation and keyboard were both changed to Huawei. Have you ever seen an Honor phone switch animations like that?
Dazed No More said:
Yep all solved. For the life of me I cannot understand why flashing the modded twrp allowed me to boot to TWRP on the first try today. I kid you not I flashed openkirin twrp image successfully probably 30 times over the past few days and everytime would boot to erecovery. What saved me was finding that backup folder with a couple backups in it, I thought I deleted them long ago.
Im still lost as to what happened to the phone when it took the OTA and why boot animation and keyboard were both changed to Huawei. Have you ever seen an Honor phone switch animations like that?
Click to expand...
Click to collapse
Yes happened on me when debrandesr to L21. But came back to L22 and all good.
Trust me Huawei is difficult to deal sometimes
shashank1320 said:
Yes happened on me when debrandesr to L21. But came back to L22 and all good.
Trust me Huawei is difficult to deal sometimes
Click to expand...
Click to collapse
You were debranding....I took an official update from an OTA :cyclops:
Dazed No More said:
You were debranding....I took an official update from an OTA :cyclops:
Click to expand...
Click to collapse
hehe, played with debranding many time by now
Yes but some changes modifies the boot animation to Huawei
Yep I have dealt with unbricking too many times now and this was the final one. It's not even my phone any more I gave it to my sister over a month ago when I got a 5T. Tomorrow I will post a picture that's on the work computer to show you how screwed up the phone got from a simple OTA....I wouldn't wish that on anyone.
@shashank1320
here's one I have on my phone from earlier....how does the product partition get wiped by an OTA lol.
Edit: Added the pic I was talking about...this was from a BLN-L24C567B360 backup. generic_a15, no name, octa core 2.1ghz, C900B300?? lol huawei :silly::silly:
Dazed No More said:
Yep I have dealt with unbricking too many times now and this was the final one. It's not even my phone any more I gave it to my sister over a month ago when I got a 5T. Tomorrow I will post a picture that's on the work computer to show you how screwed up the phone got from a simple OTA....I wouldn't wish that on anyone.
@shashank1320
here's one I have on my phone from earlier....how does the product partition get wiped by an OTA lol.
Edit: Added the pic I was talking about...this was from a BLN-L24C567B360 backup. generic_a15, no name, octa core 2.1ghz, C900B300?? lol huawei :silly::silly:
Click to expand...
Click to collapse
Huawei is beyond my understanding now ..I have seen many different behavior for same action and even give up sometime...but yeah, just a will to revive the phone takes a lot of effort for me sometime.
Related
Hello forum! My mate 8 underwent a strange update. Before the update I was rooted on SU and had TWRP installed on my NXT-L29. After said update, my mate 8 has changed from an NXT-L29 to just NEXT. Before i was on EMUI 4.0 now its 4.1 on version NXT-C00B323. My phone has lost its own identity, refuses to root or allow TWRP to be installed and is unrecognized by the Rayglobe Knife tool. I have no idea what to do. Im stuck on some strange firmware that added a lot of Huawei stock apps. The google app does not work in general and is replaced by basically a chinese version of google now on tap. I dont speak chinese and that is the only way the app works. I cannot even replace it with google now. Ive tried using ADB to install TWRP and it always boots into stock recovery which is completely worthless btw. All stock recovery does is turn on wifi only to tell me that getting "package info" has failed. I have 2 TWRP backups on my SD card. Is there a way i can restore them by force? or is there something else i can do?
um it sounds like u flashed a chinese AL10 firmware onto your L29 device. u make it sound like it "just happened" on its own. are u sure about that? what exactly did u do?
Sent from my Huawei Mate 8 NXT-AL10
i tried using the recovery on the HiSuite program to restore a previous version of the L-29 firmware line and this happened instead.
Now you try dload firmware of.your region
wow thats great
now you cant flash any img with fastboot ?
if you cant use fastboot
then your are doomed like me
I actually have never tried flashing an img with fastboot. Ill look up how to do so and try it
UPDATE: I cant seem to get to recovery mode whatsoever. So no, i cannot flash anything anymore. My phone is bricked sort of but it still works 100% i cannot use any sort of features like root or Rayglobe knife and i cannot even use fastboot as the phone refuses to go to the appropriate screens or respond to button presses during bootup to get to the white recovery screen. Never buying Huawei again, was a fan but even Huawei doesn't support the Mate 8. its not even listed on their website in troubleshooting, recovery, help guides or even support. It's like it is an enigma to its own manufacturer.
jbmc83 said:
um it sounds like u flashed a chinese AL10 firmware onto your L29 device. u make it sound like it "just happened" on its own. are u sure about that? what exactly did u do?
Sent from my Huawei Mate 8 NXT-AL10
Click to expand...
Click to collapse
Managed to fix the phone and flash a new custom slim rom. Didnt turn out so well at first as some drives refused to mount but i made due and all drives were mounted and a i completely wiped android from it and reinstalled it manually. Works better than before. Battery life is significantly improved but that may just be the rom.
I flashed TWRP and unlocked bootloader, I am on mha-l29c636b158. How can I return to completely stock? I want to receive updates via ota because I read that there is a new update to fix the touch screen not being responsive. Or is there a flashable stock zip update I can flash?
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656/page31
Jaimesco12 said:
I flashed TWRP and unlocked bootloader, I am on mha-l29c636b158. How can I return to completely stock? I want to receive updates via ota because I read that there is a new update to fix the touch screen not being responsive. Or is there a flashable stock zip update I can flash?
Click to expand...
Click to collapse
I spent that past two days rooting and flashing the one rom I could. Had to ignore some Chinese. I am USA 567B167. Got into trouble a number of times. This phone is funky compared to all the rooting I have done. I booted into erocovery, downloaded stock 2GB, wiped and was back to current stock without issue. It bootlooped if I didn't hard reset and wipe cache.
gm007 said:
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656/page31
Click to expand...
Click to collapse
Will I be able to receive otas?
rndchef said:
I spent that past two days rooting and flashing the one rom I could. Had to ignore some Chinese. I am USA 567B167. Got into trouble a number of times. This phone is funky compared to all the rooting I have done. I booted into erocovery, downloaded stock 2GB, wiped and was back to current stock without issue. It bootlooped if I didn't hard reset and wipe cache.
Click to expand...
Click to collapse
So you just booted to erecovery and from there it automatically downloaded the stock firmware?
You can return stock by use dload update.
Jaimesco12 said:
So you just booted to erecovery and from there it automatically downloaded the stock firmware?
Click to expand...
Click to collapse
yes. I did it twice. that is how many times I got into trouble and was the only solution. It worked great as it gives you the ability to log into wifi with a keyboard present to put in the password, then downloads the stock current rom and flashes it. You have to format data and wipe cache yourself.
Miss Wugfresh root tool. Get you out of any trouble.
It says getting package info failed in erecovery
rndchef said:
yes. I did it twice. that is how many times I got into trouble and was the only solution. It worked great as it gives you the ability to log into wifi with a keyboard present to put in the password, then downloads the stock current rom and flashes it. You have to format data and wipe cache yourself.
Miss Wugfresh root tool. Get you out of any trouble.
Click to expand...
Click to collapse
any ideas?
Jaimesco12 said:
any ideas?
Click to expand...
Click to collapse
Erecovery only work for Chinese firmware.
Use the guide above and yes you can receive ota.
I also received the same message. Getting into recovery was inconsistent for me even with TWRP. Sometimes it would do the auto downloaded and fail thing and other times it would go into TWRP. You need to get where you have three choices and pick erocovery and push the start button. This brings up the restore ability. Worked perfect on the USA model.
rndchef said:
I also received the same message. Getting into recovery was inconsistent for me even with TWRP. Sometimes it would do the auto downloaded and fail thing and other times it would go into TWRP. You need to get where you have three choices and pick erocovery and push the start button. This brings up the restore ability. Worked perfect on the USA model.
Click to expand...
Click to collapse
Do you say that you recovered your phone from erecovery? For usa model?
gm007 said:
Do you say that you recovered your phone from erecovery? For usa model?
Click to expand...
Click to collapse
Yes. Twice. Once to get off of HRT rom that was wonky and another to remove root because I lost Google apps. All accidents and was grateful to discover erecovery put me back on the current B167 version stock.
rndchef said:
Yes. Twice. Once to get off of HRT rom that was wonky and another to remove root because I lost Google apps. All accidents and was grateful to discover erecovery put me back on the current B167 version stock.
Click to expand...
Click to collapse
Are you sure ur not using a paid service?
That's a good news, that was only possible for Chinese firmware,hope they extend it to all regions.
gm007 said:
Are you sure ur not using a paid service?
That's a good news, that was only possible for Chinese firmware,hope they extend it to all regions.
Click to expand...
Click to collapse
Completely positive. It happened by accident because I got in a bad place with HRT rom. Came out completely stock and current when no upgrade need. Then I rooted stock and somehow lost gapps including keyboard. Did it again and back to stock. All in erecovery. No other programs or files. It did a 2.5GB download, flashed in Emui and rebooted like when I bought it.
rndchef said:
Completely positive. It happened by accident because I got in a bad place with HRT rom. Came out completely stock and current when no upgrade need. Then I rooted stock and somehow lost gapps including keyboard. Did it again and back to stock. All in erecovery. No other programs or files. It did a 2.5GB download, flashed in Emui and rebooted like when I bought it.
Click to expand...
Click to collapse
Sorry for the no noob question: I just got my mate 9 and unlocked bootloader and rooted it. Recovery is TWRP 3.0.2-2.
Where do i find this erecovery? Couldn't see any download option in TWRP and even Google didn't know that term. Could anybody please explain step by step how to revert to stock (for the only sake of getting OTAs) once the phone has unlocked bootloader and is rooted using the method from xda with modified boot.img?
Or is it even possible to take OTAs while being rooted with system read only? On my previous phone, the Asus Zenfone 2 this was possible.
Thanks a lot
itenos said:
Sorry for the no noob question: I just got my mate 9 and unlocked bootloader and rooted it. Recovery is TWRP 3.0.2-2.
Where do i find this erecovery? Couldn't see any download option in TWRP and even Google didn't know that term. Could anybody please explain step by step how to revert to stock (for the only sake of getting OTAs) once the phone has unlocked bootloader and is rooted using the method from xda with modified boot.img?
Or is it even possible to take OTAs while being rooted with system read only? On my previous phone, the Asus Zenfone 2 this was possible.
Thanks a lot
Click to expand...
Click to collapse
Connect ur phone to usb,and boot ur phone while holding volume up.
Please report back if erecovery recovered ur phone.
gm007 said:
Connect ur phone to usb,and boot ur phone while holding volume up.
Please report back if erecovery recovered ur phone.
Click to expand...
Click to collapse
Thanks for the quick answer. Let me clearify what I understood : this erecovery is available only on the PC?
So basically I wait in rooted state until I receive the next OTA, don't take it but switch off the phone.
Then connect it to the PC and boot it up by holding the volume up + power key.
Then what happens exactly?
Sent from my MHA-L29 using Tapatalk
itenos said:
Thanks for the quick answer. Let me clearify what I understood : this erecovery is available only on the PC?
So basically I wait in rooted state until I receive the next OTA, don't take it but switch off the phone.
Then connect it to the PC and boot it up by holding the volume up + power key.
Then what happens exactly?
Click to expand...
Click to collapse
Booting the phone while plugged and with volume up will take you to erecovery on ur phone.
There you connect to wifi and the firmware get downloaded into ur phone
gm007 said:
Booting the phone while plugged and with volume up will take you to erecovery on ur phone.
There you connect to wifi and the firmware get downloaded into ur phone
Click to expand...
Click to collapse
Ah ok, this erecovery is still available on my phone even if I already flashed a custom recovery, right?
Then after downloading the firmware, erecovery will flash it and overwrite root and lock my bootloader again, correct?
Sent from my MHA-L29 using Tapatalk
I already wrote something like this in a similar thread, but for another device (read the device name wrong), so I thought i should post it in the right place.
I have been playing too much with stuff that i probably shouldn't have been so hasty about. So i have finally arrived here on the ERROR MODE (with unstoppable boot loop), which looks exactly like the bootloader only it says ERROR MODE instead of whatever, where i can't get into any other type of recovery or fastboot mode, no matter what button combinations i do. I previously could get to the fastboot mode, but i was still stuck so..... I made the very wise choice of relocking (since i hadn't tried that) my device, and now I can't even access fastboot (nothing. tried every button combination i can think of). So I am sitting here wondering if this is the end of the journey with my... relatively new phone... So, yes. No way of accessing anything and my phone is in a reboot loop i can't stop. Only thing is the error code i get "ERROR!":
"Func NO : 16 (lpm3 image)"
"Error NO : 1 (security verify failed!)"
Is there hope? or no?
Also noticed the light flashes green 3 times then red 1, then continues this pattern. Idk if that's useful or not.
Here's a pic.
It doesn't seem to have fastboot connection here, either.
OP were you ever able to fix this issue?
@Kimuchuu its not clear from OP had you relocked your bootloader if yes then you cant modify your system you need to have unlocked bootloader inorder to perform system modifications.
Ah. Yes, unfortunately I relocked it. I ended up sending it to service with no hopes of getting it back working, but they sent me a brand new one. So that's that.
I guess I was lucky, but really there was not a single thing I could do at that state.
You can be really happy that they sent you a new one, but it's not a unique case, in CZ there were few people who had same or similar issue and Repair service gave them new phone too.
Kimuchuu said:
Ah. Yes, unfortunately I relocked it. I ended up sending it to service with no hopes of getting it back working, but they sent me a brand new one. So that's that.
I guess I was lucky, but really there was not a single thing I could do at that state.
Click to expand...
Click to collapse
You got lucky they sent you a new one considering that you messed up the previous one. Take good care this time.
Sent from my Honor 8 using XDA Labs
Kimuchuu said:
Ah. Yes, unfortunately I relocked it. I ended up sending it to service with no hopes of getting it back working, but they sent me a brand new one. So that's that.
I guess I was lucky, but really there was not a single thing I could do at that state.
Click to expand...
Click to collapse
thats nice to hear ,man you are lucky
How exactly did you reach out to the service center?
I'm in the same situation and right now im typing the e-mail.
Im wondering what to write in the hope of getting a new one, too.
oberfeldwedler said:
How exactly did you reach out to the service center?
I'm in the same situation and right now im typing the e-mail.
Im wondering what to write in the hope of getting a new one, too.
Click to expand...
Click to collapse
In which country do you live? Just go to the nearest authorized Huawei service center. You can find them in Google.
Sent from my Honor 8 using XDA Labs
I also had this problem, trying to screw around and force a ota update via flash fire onto a modified system... Reached rhe same sddor mode, luckily I was able to manually flash all the partitions back to stock using ADB and finally once all partitions were back in order it allowed me to enter recovery mode and download and install system software threw recovery... Took me about 4 days of non stop tinkering to finally get it working again, I had all but lost hope in all honesty... Thankfully I was persistent and all is well now!
BigBrad75 said:
I also had this problem, trying to screw around and force a ota update via flash fire onto a modified system... Reached rhe same sddor mode, luckily I was able to manually flash all the partitions back to stock using ADB and finally once all partitions were back in order it allowed me to enter recovery mode and download and install system software threw recovery... Took me about 4 days of non stop tinkering to finally get it working again, I had all but lost hope in all honesty... Thankfully I was persistent and all is well now!
Click to expand...
Click to collapse
A guide how you solved your problem would help others who screwed their device to solve their problem
Update: I let the battery drain completly in this error mode and after plugging it in the Huawei eRecovery appeared...
i think i can dLoad it and get it back to work...
---------- Post added at 11:41 AM ---------- Previous post was at 11:35 AM ----------
BigBrad75 said:
I also had this problem, trying to screw around and force a ota update via flash fire onto a modified system... Reached rhe same sddor mode, luckily I was able to manually flash all the partitions back to stock using ADB and finally once all partitions were back in order it allowed me to enter recovery mode and download and install system software threw recovery... Took me about 4 days of non stop tinkering to finally get it working again, I had all but lost hope in all honesty... Thankfully I was persistent and all is well now!
Click to expand...
Click to collapse
But your bootloader wasn't locked i guess...
oberfeldwedler said:
Update: I let the battery drain completly in this error mode and after plugging it in the Huawei eRecovery appeared...
i think i can dLoad it and get it back to work...
Click to expand...
Click to collapse
But did you try the first option in erecovery?
Sent from my Honor 8 using XDA Labs
adriansticoid said:
But did you try the first option in erecovery?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
No success
Then i tried to unlock my bootloader but got ERROR MODE again...
I'm letting the battary drain so i can enter eRecovery. Hopefully dLoad works.
By the way does anyone know whats the difference between Recovery.img an recovery2.img?
I remember flashing one of them before relocking my bootloader.
oberfeldwedler said:
No success
Click to expand...
Click to collapse
Then dload is your next choice.
Sent from my Honor 8 using XDA Labs
oberfeldwedler said:
No success
Then i tried to unlock my bootloader but got ERROR MODE again...
I'm letting the battary drain so i can enter eRecovery. Hopefully dLoad works.
By the way does anyone know whats the difference between Recovery.img an recovery2.img?
I remember flashing one of them before relocking my bootloader.
Click to expand...
Click to collapse
Recovery is the one which installs ota updates . Erecovery is an emergency recovery. It can help u restore ur phone to previous version by flashing full original firmware
I got it back to work....
I dloaded the rollback update.app
and then the real stock software
I think the thing that saved me was that i flashed stock recovery before having the glorious idea of relocking the bootlaoder.
So for anybody:
If ur device is not working DO NOT LOCK YOUR BOOTLOADER
oberfeldwedler said:
I got it back to work....
I dloaded the rollback update.app
and then the real stock software
I think the thing that saved me was that i flashed stock recovery before having the glorious idea of relocking the bootlaoder.
So for anybody:
If ur device is not working DO NOT LOCK YOUR BOOTLAODER
Click to expand...
Click to collapse
Well , great that unbricked and your last line , it is to be in bold . Thanks for it. Headsup:victory:
oberfeldwedler said:
I got it back to work....
I dloaded the rollback update.app
and then the real stock software
I think the thing that saved me was that i flashed stock recovery before having the glorious idea of relocking the bootlaoder.
So for anybody:
If ur device is not working DO NOT LOCK YOUR BOOTLAODER
Click to expand...
Click to collapse
yup thats the main point if you are not fully stock and soft bricked you are not advised to lock your bootloader. Once you locked your bootloader you can no more modify your system.
I'm gifting my father in law an Honor 6X. I already unlocked the bootloader and rooted, but I'd like for him to be able to install updates when they're released. If I uninstall all the bloatware while rooted and then relock the bootloader, will root be retained? Will TWRP be removed? Will OTA updates be allowed? This is all on the stock ROM.
Superorb said:
I'm gifting my father in law an Honor 6X. I already unlocked the bootloader and rooted, but I'd like for him to be able to install updates when they're released. If I uninstall all the bloatware while rooted and then relock the bootloader, will root be retained? Will TWRP be removed? Will OTA updates be allowed? This is all on the stock ROM.
Click to expand...
Click to collapse
I believe you should be able to receive updates with the bootloader unlocked. The OTA might relock the bootloader and will most likely remove root. In order to update you will need to also have stock recovery installed so there would be no way for him to root again without unlocking the bootloader and flashing twrp.
BakedOnSomeSour said:
I believe you should be able to receive updates with the bootloader unlocked. The OTA might relock the bootloader and will most likely remove root. In order to update you will need to also have stock recovery installed so there would be no way for him to root again without unlocking the bootloader and flashing twrp.
Click to expand...
Click to collapse
Ok. He's clueless when it comes to even using stock phones, so I'll probably completely return the phone to stock and call it a day. Is there a thread floating around here to do relock, unroot, and completely return to stock?
Superorb said:
Ok. He's clueless when it comes to even using stock phones, so I'll probably completely return the phone to stock and call it a day. Is there a thread floating around here to do relock, unroot, and completely return to stock?
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
BakedOnSomeSour said:
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
Click to expand...
Click to collapse
That says it's for after you've flashed custom ROMs. I've never flashed a ROM on mine, only unlocked and rooted. Haven't even uninstalled any apps yet. Is there a quick way to relock and unroot?
Superorb said:
That says it's for after you've flashed custom ROMs. I've never flashed a ROM on mine, only unlocked and rooted. Haven't even uninstalled any apps yet. Is there a quick way to relock and unroot?
Click to expand...
Click to collapse
Its also if you flashed twrp not only custom roms. You can uninstall root in the superSU app when selecting full unroot in the settings. I believe a factory reset can do it too. The next step would be to download the firmware for the phone and using fastboot to flash a boot and recovery image and then to lock the bootloader. Those steps are all in the link. That is the quickest way.
BakedOnSomeSour said:
Its also if you flashed twrp not only custom roms. You can uninstall root in the superSU app when selecting full unroot in the settings. I believe a factory reset can do it too. The next step would be to download the firmware for the phone and using fastboot to flash a boot and recovery image and then to lock the bootloader. Those steps are all in the link. That is the quickest way.
Click to expand...
Click to collapse
Damn, I was hoping it would be as easy as "fastbook oem lock" and be done with it.
Superorb said:
Damn, I was hoping it would be as easy as "fastbook oem lock" and be done with it.
Click to expand...
Click to collapse
Same. if you need any additional help with the process just let me know.
BakedOnSomeSour said:
Same. if you need any additional help with the process just let me know.
Click to expand...
Click to collapse
Thanks! Where can I find the EMUI 5.0.1 image? Mine is BLN-L24.
Superorb said:
Thanks! Where can I find the EMUI 5.0.1 image? Mine is BLN-L24.
Click to expand...
Click to collapse
There's a PC application called firmware finder. https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
You can download firmware finder on your phone too and download the files from there. It's on the play store.
BakedOnSomeSour said:
There's a PC application called firmware finder. https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
You can download firmware finder on your phone too and download the files from there. It's on the play store.
Click to expand...
Click to collapse
Ok, downloaded the Firmware finder and I have no idea how to use it. Directions don't make any sense and I have no idea what I'm doing after entering in my phone model.
I'm trying, but this phone is so different from my old LG G2 to play around with.
Superorb said:
Ok, downloaded the Firmware finder and I have no idea how to use it. Directions don't make any sense and I have no idea what I'm doing after entering in my phone model.
I'm trying, but this phone is so different from my old LG G2 to play around with.
Click to expand...
Click to collapse
When you get into the Firmware Finder(PC) app youll notice your on a tab labeled "Main Page". Click on the tab labeled "common base" and type BLN-L24 into the search bar at the top right and then click on FIND. A list of firmware will pop up. Find the one that matches your build number and then click on the link under the "filelist" section. There will be two or three different zips you need to download. When you have the three downloaded let me know.
BakedOnSomeSour said:
When you get into the Firmware Finder(PC) app youll notice your on a tab labeled "Main Page". Click on the tab labeled "common base" and type BLN-L24 into the search bar at the top right and then click on FIND. A list of firmware will pop up. Find the one that matches your build number and then click on the link under the "filelist" section. There will be two or three different zips you need to download. When you have the three downloaded let me know.
Click to expand...
Click to collapse
Ok, I've downloaded all 3 zip files from my build at over 2gigs.
Superorb said:
Ok, I've downloaded all 3 zip files from my build at over 2gigs.
Click to expand...
Click to collapse
Ok now extract the files from the update.zip folder. Then take the UPDATE.app from the extracted files and open it with update extractor: https://forum.xda-developers.com/showthread.php?t=2433454
After that your ready to follow the steps on the other guide.
So I screwed up. Before you posted I unrooted via unSU flashable zip. Then I fastboot flashed boot and recovery to the stock one from the update.app file. Now it's got some verification error on power on and OTA updates fail. I tried moving the update.app to a dload folder on sdcard, but when it starts up it fails at 5% when restoring from the sdcard.
ETA: Tried the 360 FW which updated successfully. Booted and asked for password. After panicking shutdown and copied the HW contents to Sdcard and did the update again which succeeded. Booted and asked for password again and I panicked again. Pulled the Sdcard and booted into stock recovery. Wiped everything and then restarted crossing fingers. Started up like normal, no password request! So it looks like the phone is back on totally stock EMUI 5.0. I'll hope for the update and will try with fingers and toes crossed. Thanks for your help. I may be back, but hopefully not.
ETA2: There's no update option above the last About option in settings... How do I get the update option?
Superorb said:
So I screwed up. Before you posted I unrooted via unSU flashable zip. Then I fastboot flashed boot and recovery to the stock one from the update.app file. Now it's got some verification error on power on and OTA updates fail. I tried moving the update.app to a dload folder on sdcard, but when it starts up it fails at 5% when restoring from the sdcard.
ETA: Tried the 360 FW which updated successfully. Booted and asked for password. After panicking shutdown and copied the HW contents to Sdcard and did the update again which succeeded. Booted and asked for password again and I panicked again. Pulled the Sdcard and booted into stock recovery. Wiped everything and then restarted crossing fingers. Started up like normal, no password request! So it looks like the phone is back on totally stock EMUI 5.0. I'll hope for the update and will try with fingers and toes crossed. Thanks for your help. I may be back, but hopefully not.
ETA2: There's no update option above the last About option in settings... How do I get the update option?
Click to expand...
Click to collapse
Edit: Before trying below steps. Just put the files from "BLN-L24_hw_usa"(b360) into dload folder and flash with dload. It might update the version.img without the needs for the steps below. if that brings the build number back to b360 use the hisui(PC) application to connect to the phone and update
Ok i forgot to mention something. The reason you dont have a update option is because you are on b360 which never had a button. Your build number on your phone will say b366 but thats incorrect. You cant receive an ota automatically because the phone thinks its already on the latest version. You need to take the UPDATE.APP from the "BLN-L24_hw_usa" (b360) folder and extract the VERSION.IMG file. It needs to be flashed with TWRP because fastboot wont work for some reason. That file will fix the build number and change it back to b360 so you can receive the OTA which will also restore the missing apps and features. That means you have to unlock the bootloader. Flash twrp. Flash the vendor.img with twrp and then do the dload method.
You have all the files and have done it already so this time will be easier. Ive done this way too many times with this phone. Sorry i forgot the mention the one step
Build number on my phone is already 360, and it has never been 366. Tried flashing the 360 like you said via dload and nothing seems to have changed.
Also the SIMtray eject tool seems to just go into the phone without ejecting the tray. A paperclip worked, but man this phone is really frustrating.
Superorb said:
Build number on my phone is already 360, and it has never been 366. Tried flashing the 360 like you said via dload and nothing seems to have changed.
Also the SIMtray eject tool seems to just go into the phone without ejecting the tray. A paperclip worked, but man this phone is really frustrating.
Click to expand...
Click to collapse
Oh ok my build number always got stuck at b366. Try connecting with the HiSuite program and getting an OTA. And yes this is the strangest, most difficult phone to work with that ive ever owned.
BakedOnSomeSour said:
Oh ok my build number always got stuck at b366. Try connecting with the HiSuite program and getting an OTA. And yes this is the strangest, most difficult phone to work with that ive ever owned.
Click to expand...
Click to collapse
Wife made me box it up and ship to her dad, so I no longer have the phone. I did install the HiSuite when I first powered on the phone and it was never able to connect and see the phone, so who knows what's going on.
Thanks for all your help. I have another one, but I'm just going to sell it and be done with it. No idea what other phone I can get with the same specs for the same price that's not so difficult to flash, but I'll keep looking I guess.
Superorb said:
Wife made me box it up and ship to her dad, so I no longer have the phone. I did install the HiSuite when I first powered on the phone and it was never able to connect and see the phone, so who knows what's going on.
Thanks for all your help. I have another one, but I'm just going to sell it and be done with it. No idea what other phone I can get with the same specs for the same price that's not so difficult to flash, but I'll keep looking I guess.
Click to expand...
Click to collapse
Its not difficult. In order to connect to hisuite you need to enable developer settings and allow usb debugging or type hisuite in the settings search bar and click "allow HiSuite to use HDB". I got this phone for christmas and i already know a ton about it. It may seem complicated now but its really nothing.
My phone did its overnight update last night (wasn't charging) and it seems to have been doing a restart loop since. When I checked it this morning, the battery was at 7%. It'll successfully boot into my homescreen, but restarts at about a minute in.
I just did a hard reset and it is still the same. Can't even get through all of the setup screen before the phone restarts. Anything I can do at all?
Edit: No root, no bootloader unlock. Stock.
Might have to get into Recovery Mode and do a wipe
cash2387 said:
Might have to get into Recovery Mode and do a wipe
Click to expand...
Click to collapse
Already did that, but it's still restarting itself even going through setup screen. Worst still it's asking me to login to my Google Account, which requires 2FA, which was the phone. Also, it's not reading my SIM at all so the SMS 2FA option isn't viable either...
Manusia said:
My phone did its overnight update last night (wasn't charging) and it seems to have been doing a restart loop since. When I checked it this morning, the battery was at 7%. It'll successfully boot into my homescreen, but restarts at about a minute in.
I just did a hard reset and it is still the same. Can't even get through all of the setup screen before the phone restarts. Anything I can do at all?
Edit: No root, no bootloader unlock. Stock.
Click to expand...
Click to collapse
I think I had something similar to that happen to my phone. I have an unlocked bootloader and I forced update using the HWOTA8 method. What I think happens is the phone could have downloaded a corrupted or impartial update. The phone will need to downgrade to a lower update or try to see if you can downgrade the phone back using firmware but I dont think you can downgrade on a locked bootloader. Whatever you try to do just don't panic and format all your partitions try to backup all your contacts and data if you can. If you can reinstall the .373 update try doing that again and if that will help it from freezing up.
vang2k said:
I think I had something similar to that happen to my phone. I have an unlocked bootloader and I forced update using the HWOTA8 method. What I think happens is the phone could have downloaded a corrupted or impartial update. The phone will need to downgrade to a lower update or try to see if you can downgrade the phone back using firmware but I dont think you can downgrade on a locked bootloader. Whatever you try to do just don't panic and format all your partitions try to backup all your contacts and data if you can. If you can reinstall the .373 update try doing that again and if that will help it from freezing up.
Click to expand...
Click to collapse
Adding to this, try Download Latest from eRecovery. It should find B373 as it's approved for you.
ante0 said:
Adding to this, try Download Latest from eRecovery. It should find B373 as it's approved for you.
Click to expand...
Click to collapse
Well....... that was simple.
My Google skills clearly failed me. I tried the dload method to no avail. At no point did my search returned 'eRecovery'. Even brought the phone in to 2 repair shops and one said they needed days to figure it out, the other said to send it to Huawei.
And now I have a S9+. Time to figure out which to keep. Thanks a lot!