Database Info

OTA downloaded, and captured... It begins || update 5/7/16

ADDED INSTRUCTIONS AT END OF POST*****
Got it.... Rooted, twrp, the whole deal. On 6.0. I'll post instructions in the middle of the week for everybody.
Unfortunately if you already did the other method, you are screwed for now. Because the method I used required me to flash a stock 5.1.1.
Standby
_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|_|
So there I am sitting on my computer last night, when a notification pops up on my V10 .... The old "congratulations, you've won first prize in an update contest!"
Lo and behold, the MM update had downloaded (at record speeds I might add).
Without wasting a minute, I navigated to the cache partition and copied it to my internal folder (see attachment), then backed it up on drive.
So... We'll just skip to the good part...
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
I'll save you all the curiosity and let you know that I am going to look into this option to flash the OTA this weekend. I'm going to assemble a compatibility analysis and if everything checks out, I'll flash it.
Standby for carnage.
****INSTRUCTIONS
OK... I really owe everybody here an apology for taking so long to get an official instruction up. Work has been crazy this week. But I wanted to be able to take some time to do this. So here we go...
But wait... Before we even start, please for the love of God do your homework here. Please go read through chains thread about his app, how it works, etc. The interface is straight forward enough, but there are other things to understand. Please just understand what you are doing, and please verify checksums of anything you download. This is very important.
And thank chainfire, not me.
PRE-FLASH REQUIREMENTS:
1. First and foremost, you MUST be on the latest version of MM TWRP. There is a thread in the development section for this, with instruction on how to flash it, find that thread. Get it installed. This is a must. You must also verify adb and fastboot are working fully on your device.
2. You must be 100% Stock (but rooted) on the latest TMO V10 5.1 1 firmware and ROM, no custom kernels, nothing. Stock, with the exception of working root, and the latest 3.0.2.0 Marshmallow TWRP. When I say stock I mean no deodex, no system apps removed, this is an absolute requirement. The reason for this is mostly to avoid the update.zip from aborting as it does checks for presence of apps within system, etc. If you have to flash a stock ROM before doing this, don't do it as an "in line" queue before you flash the OTA in flashfire. Do it separate.
3. You must have the official OTA downloaded and on your internal SD card. Also, put the latest superSU version 2.67 on an external card, and remove the SD card from the device. The md5 for the OTA is 280ad51eb96457df097df5a088a535af9
Once you have checked those 3 boxes. You are ready to proceed.
4. Install flashfire. I was on version 32.
5. Open flashfire, grant it root
6. Go into the setting of the app, check the "Flash boot loaders" and "Freeload" box.
7. Find the OTA package, queue it up with "flash zip or ota" (small + sign at the bottom right of the screen)
It is important to note that after the flashing process completes, you will want to power off the device, and boot it into fastboot mode to unlock the boot loader.
8. Execute the update.
9. After it finishes, power off the device.
10. Boot into fastboot by holding down the volume down button, and with the button held down, plug the USB cable into your computer.
11. Once in fastboot, type the following command and hit enter:
Code:
fastboot oem unlock
Let it run for a bit, it is going to wipe your data.
12. After it completes (your terminal should give you a time displayed for the operation).... Unplug the phone, and yank the battery.
13. Pop in your Micro SD card (with superSU 2.67 flashable on it) then manually boot the phone into recovery mode. You are going to flash superSU again as a sanity check. I did this because if for some reason FF didn't flash superSU, and then the system wrote over your recovery during your first boot... You'd be absolutely dicked stuck on stock MM with no way of getting root back for now. I like verification...
To boot the v10 into recovery mode manually, simply have the device powered off, then hold the volume down and power button at the same time. AS SOON as you see the boot screen (not to be confused by the boot animation) released the power button for just a little less than a second then press and hold it again (keep the volume down button pressed the whole time). It may or may not be absolutely critical that you don't screw this part up. You need to get into recovery at this point to validate root being installed.
This should take you into 2 sequential screens, both asking about clearing data, select yes for both (don't worry, it won't, it will take you into TWRP.
Once in twrp... Mount your SD card in the twrp settings, and flash superSU.
Reboot afterwards. Done.
After you do this, you will be in 100% stock, rooted MM.
You might need to flash twrp again (do it the normal way, you are done with flash fire now), but root, you will have, and full functionality, you will also have, with everything working.

Dont do it. No root for MM at the moment.

Double0EK said:
Dont do it. No root for MM at the moment.
Click to expand...
Click to collapse
Unless you use Eliminator74's rooted rom which is the official MM update from T-Mobile.
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

what he's considering guys is flashing the ota.zip via flashfire which can with some devices maintain root and recovery.

markbencze said:
what he's considering guys is flashing the ota.zip via flashfire which can with some devices maintain root and recovery.
Click to expand...
Click to collapse
I'm debating that myself
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

Standing by!
Sent from my pretty nifty brand new LG V10

Ok. Im actually interested in the outcome.

I think a lot of us are curious to see if it works. For all we know this is the solution that we've had the entire time. the question is, is anyone brave/crazy/foolish enough to try it? It might work great, but then again it could brick your phone given LG devices are untested trying this. there are several devices that were also untested that it did work on so who knows. But the app does have the capabilities to flash a stock update.zip and maintain boot root and recovery. I would think you'd have to reunlock your bootloader after flashing though in order to boot.

anyone know where exactly update.zip downloaded to? mine just downloaded and I don't see anything large in /cache

In for results

dimm0k said:
anyone know where exactly update.zip downloaded to? mine just downloaded and I don't see anything large in /cache
Click to expand...
Click to collapse
Mine is in my cache folder. It says update.zip and it is 1.03 GB
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

A think tank.
If the update is zip, can the flash be done with TWRP plus superSU?!

truckerdewd said:
Mine is in my cache folder. It says update.zip and it is 1.03 GB
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!
Click to expand...
Click to collapse
interesting... everyone's seems to be there, but after running a search of the filesystem I see /data/data/com.google.android.gms/app_download/update.zip

truckerdewd said:
Mine is in my cache folder. It says update.zip and it is 1.03 GB
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!
Click to expand...
Click to collapse
so is mine

dimm0k said:
interesting... everyone's seems to be there, but after running a search of the filesystem I see /data/data/com.google.android.gms/app_download/update.zip
Click to expand...
Click to collapse
That's weird. Wonder why your's went there?
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

See OP... got it.

warBeard_actual said:
See OP... got it.
Click to expand...
Click to collapse
Got what? Is in you used Flashfire and updated via ota and were able to retain root and TWRP? Sorry, I"m running g on almost no sleep cause my truck broke down and is in the shop and it's hard to sleep in the customer lounge of a Freightliner dealership.
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

Can't wait for that guide @warBeard_actual. You are one brave soul for taking the risk. Props.

crashnova said:
Can't wait for that guide @warBeard_actual. You are one brave soul for taking the risk. Props.
Click to expand...
Click to collapse
I couldn't agree more. Noe just need to get the time to do it on my phone.
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!

truckerdewd said:
I couldn't agree more. Noe just need to get the time to do it on my phone.
Sent from my wickedly awesome LG V10 using my fingers. Duh!!!
Click to expand...
Click to collapse
I woke up to the OTA this morning. I find it odd tho because i thought OTAs were disabled on siraltus rom. I would try FF but don't eant to risk bricking until OP shares the steps he took.

[GUIDE] Debranding to C432 and updating to B361 (Nougat) for EVA-L09

Like many people here, I was eager to get onto Android 7 but the issue I faced was the fact that I got a branded phone and a long wait till I officially get the Android 7 update. Looking through this forum I was very put off on manually updating it to Android 7 with so many threads about bricked phones. However, the urge to get onto Android 7 was too great so ultimately, I decided to do my research and just do it. I am not new to flashing and custom roms but I am new to Huawei but I had confidence that I will recover if I do brick my new P9. In the end (after a few bricks and a couple of mild heart attacks), I got there and to get there, I needed to grab information from multiple threads. So I have decided to put together this guide so people have a singular guide to debrand and get onto Android 7. Below are steps and threads I took to debrand my C34 to C432 and update it to B361.
What listed below is what I did to get onto Android 7, this may or may not work for you so use this guide at your own risk.
Using this Guide - Please read through this guide BEFORE attempting it. There is a lot of large files to download so I recommend that you download everything you need before you make a start and a fast and reliable internet is strongly recommended.
Prep Work
- Backup all your data because your phone will get wiped.
- Make sure you have the stock recovery already flashed and make sure your phone is not rooted (may not be necessary but this was the state my phone was in).
- Get yourself a bootloader code from Huawei. Go to http://www.emui.com/en/plugin/hwdownload/download, you will need to create a Huawei ID if you haven't already done so. Click on the Unlock Bootloader link and fill out the form, you should get a bootloader code almost instantly after submitting the form.
- Download and install HiSuite (http://consumer.huawei.com/minisite/HiSuite_en/index.html).
- Download the SRK Tool from here: https://forum.xda-developers.com/showpost.php?p=66737472&postcount=2
Now lets make a start.
1. Download and flash the dload-huawei-p9-eval09-eva-b136.zip from this thread: https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818. Instructions on how to flash this is in the first post. After flashing, you should be on the L09C900B136 firmware. NOTE: If it boots up to a white screen asking you to enter password, reboot into recovery by holding volume up when you powering up your phone, do a wipe partition and factory reset. You may need to reboot your phone a number times before the phone boots up correctly.
2. After flashing and booting into the L09C900B136 firmware, you will need to unlock your bootloader and install TWRP. You can use the SRK Tool to do this, please have a look at this thread (https://forum.xda-developers.com/showpost.php?p=66737472&postcount=2) and watch the video on how to do this. NOTE: You only need to unlock bootloader and install the TWRP recovery.
3. After your phone has been unlocked with TWRP recovery installed, download oeminfo-huawei-p9-eval09-c432.zip from this thread: https://forum.xda-developers.com/p9/development/c432-oeminfo-flash-twrp-t3384903 and flash it via TWRP. To get into TWRP, power off your phone and go into recovery by powering up your phone while holding volume up.
4. Once you flashed the oeminfo file via TWRP, power off your phone and repeat step 1. So you need to flash the dload-huawei-p9-eval09-eva-b136.zip file again via the dload method (power on the phone while holding volume up and volume down). NOTE: When you flash this firmware again, it will lock your bootloader (Fastboot will tell you that the phone is unlocked but I assure you, your bootloader is locked) and restore to stock recovery.
5. Once your phone has booted back up, go into the phone settings and you should see that your phone is now on the EVA-L09C432B136 firmware. To test that the firmware is working as intended, go into the phone settings and go into Updater, updater should pick up the B182 firmware and you should be able to update it to B182 without an issue.
UPDATE: A number of people has reported that they are getting the B166 update instead of B182, if this happes, do a wipe partition and a factory reset after updating to B166. When you get back in, you should be able to update to B182 via Updater in the Settings menu. If this method does not work, you can manually update to B182 by following the steps here: http://www.carbontesla.com/2016/11/download-huawei-p9-b182-marshmallow-update-europe/
6. After your phone has rebooted and you are on the B182 firmware, you need to now update the firmware to B361 via Huawei Updater 2.0 using this guide: https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2.
After all that is done, you should now have a debranded UK C432 P9 running EMUI 5.0.
Special thanks to @paulobrien, @somboons and @KrAzYtHeBoY for their guide, tools, files and video to make this update possible.

Props to you sir. I will try this when I get back. I don't have any doubts now after reading this guide.

Does debranding will affect warranty of the device? Mine is quite new.

zoold3vil said:
Does debranding will affect warranty of the device? Mine is quite new.
Click to expand...
Click to collapse
Its very likely that debranding will void your warranty since you will need to unlock the bootloader and flash a firmware that is not the same as your original model.

Z-Blade said:
Its very likely that debranding will void your warranty since you will need to unlock the bootloader and flash a firmware that is not the same as your original model.
Click to expand...
Click to collapse
Thanks for the feedback!

Thanks for the guide. I've recently been battling away trying to go from C34 to C636 - still never got to the bottom of it.
Is that a typo in your post for your original model number - C43? Or did you come from Optus AU C34?
Either way - have you had any network issues in Australia with the new firmware?
Cheers.

halliday77 said:
Thanks for the guide. I've recently been battling away trying to go from C34 to C636 - still never got to the bottom of it.
Is that a typo in your post for your original model number - C43? Or did you come from Optus AU C34?
Either way - have you had any network issues in Australia with the new firmware?
Cheers.
Click to expand...
Click to collapse
Yep, its a typo, thanks for pointing it out. I have no issues what so ever, everything works perfectly fine and there has been no drop in cellular reception, wifi reception, GPS accuracy and etc. Apart from the build saying L09C432, you wouldnt be able to tell the difference.

Z-Blade said:
Yep, its a typo, thanks for pointing it out. I have no issues what so ever, everything works perfectly fine and there has been no drop in cellular reception, wifi reception, GPS accuracy and etc. Apart from the build saying L09C432, you wouldnt be able to tell the difference.
Click to expand...
Click to collapse
Legend. Appreciate the reply - it was tough to find experienced Aussies on the same starting build/carrier.
Now I just wish I hadn't wasted the time going for the Asia Pacific variant!
Will get stuck into it this evening.
Thanks!

Great guide! Reading through it seems easier for it to be managed through hisuite/windows but I have a big issue. For some reason my computer won't recognize my phone! I installed the beta and am on build number EMUI-A168-L09C900B040SP11-log and since doing this stupid move I have been unable to connect to a computer nor install other builds or rollbacks directly on the device so I just feel like smashing it and claiming the insurance. Is there any advise that could be offered to maybe force a firmware upgrade?

Nawor81 said:
Great guide! Reading through it seems easier for it to be managed through hisuite/windows but I have a big issue. For some reason my computer won't recognize my phone! I installed the beta and am on build number EMUI-A168-L09C900B040SP11-log and since doing this stupid move I have been unable to connect to a computer nor install other builds or rollbacks directly on the device so I just feel like smashing it and claiming the insurance. Is there any advise that could be offered to maybe force a firmware upgrade?
Click to expand...
Click to collapse
How did you get onto that build? Have you tried following the guide I put up?

Ha I don't have a clue how I ended up with that build but I've regretted my decision to install a beta version of the nougat every day since. I will try this method this afternoon and see how I go!

Nawor81 said:
Ha I don't have a clue how I ended up with that build but I've regretted my decision to install a beta version of the nougat every day since. I will try this method this afternoon and see how I go!
Click to expand...
Click to collapse
I cant promise you that the guide I put together will work for you. If its a Nougat beta firmware then you would be technically doing a rollback to MM. Just a bit of a warning, a lot of people who try to roll back to MM, usually encounter problems, annoying problems. Unfortunately, I dont have much experience with this phone or how Huawei does things so I cant help you much. If I am in your shoes, I wouldn't attempt to debrand and flash Nougat using this guide.

Z-Blade said:
I cant promise you that the guide I put together will work for you. If its a Nougat beta firmware then you would be technically doing a rollback to MM. Just a bit of a warning, a lot of people who try to roll back to MM, usually encounter problems, annoying problems. Unfortunately, I dont have much experience with this phone or how Huawei does things so I cant help you much. If I am in your shoes, I wouldn't attempt to debrand and flash Nougat using this guide.
Click to expand...
Click to collapse
That's not the news I wanted to hear! I guess I'll keep this guide in mind and do some more research, hopefully find someone in love with Huawei that might be able to assist. Thanks

SmartPhonesFan said:
Hi z-blade I flashed B136 but it didn't put icons and themes back .. I flashed B182 and STILL didn't put icons and themes back
BUT only B166 gave me proper theme and icons back.. ! After that I flashed I had to flash B182 and so on.. B166 is the key important
Click to expand...
Click to collapse
I got theme and icon on mine but it may have came through when I flash B361. I went from a full factory reset on B136 to B182 to B361, not once did I stop to check to make sure all of the apps are installed, I only started setting up my phone and have a browse once I was on EMUI 5.0. It may be un-necessary to flash B166 if flashing B361 give you themes and icons.
If someone could double check on this when following this guide and report in, that would be great. I am not willing to test it out by rolling back to mushmellow.

Nawor81 said:
Ha I don't have a clue how I ended up with that build but I've regretted my decision to install a beta version of the nougat every day since. I will try this method this afternoon and see how I go!
Click to expand...
Click to collapse
Are you on an unbranded device?
If so, the official Huawei support page offers a rollback package if you updated to the Nougat beta.
Make sure you go to the page specific to your country.
---------- Post added at 02:42 AM ---------- Previous post was at 02:34 AM ----------
Z-Blade said:
I got theme and icon on mine but it may have came through when I flash B361. I went from a full factory reset on B136 to B182 to B361, not once did I stop to check to make sure all of the apps are installed, I only started setting up my phone and have a browse once I was on EMUI 5.0. It may be un-necessary to flash B166 if flashing B361 give you themes and icons.
If someone could double check on this when following this guide and report in, that would be great. I am not willing to test it out by rolling back to mushmellow.
Click to expand...
Click to collapse
Broken themes/icons seem to be caused by missing assets in the /CUST/ partition. I managed to get around it on my broken C900 firmware by separately flashing the /hw/normal/ package specific to the build. These can be found in the filelist.xml in the [WAREHOUSE] post - but you need to change the URL manually to grab the file.

SmartPhonesFan said:
So B361 will? Didn't know that.. Didn't want to risk it it took ages to download.. I had 3 folders in B136 but I flashed it via dial pad options.. Not 3btn..maybe if I would flash via 3btn it will give it back then and I wouldn't need B166..
Cannot be bothered.. It's done now..
Nougat best..
Click to expand...
Click to collapse
It makes no difference if you use the 3 button method or via the dial menu, both does exactly the same thing. I am only assuming that Themes could be installed when I flashed B361, I was not paying attention to the apps that was installed but I think this may be the case because I believe the Theme app was updated for EMUI 5.0, again all assumptions here.

Can I jump directly from b136 to b361?
Thanks in advance.

halliday77 said:
Are you on an unbranded device?
If so, the official Huawei support page offers a rollback package if you updated to the Nougat beta.
Make sure you go to the page specific to your country.
Click to expand...
Click to collapse
It's from Vodafone unfortunately

I've followed the guide as far as step 5. When I got there, I ended up getting an update for L09C432B166 which installed fine, but I'm not getting the B182 update. Anyone else run into an issue like this?

trouble2000 said:
Can I jump directly from b136 to b361?
Thanks in advance.
Click to expand...
Click to collapse
No you cant, you need to get to B182 before flashing B361.
d_mouse81 said:
I've followed the guide as far as step 5. When I got there, I ended up getting an update for L09C432B166 which installed fine, but I'm not getting the B182 update. Anyone else run into an issue like this?
Click to expand...
Click to collapse
Try wiping partition and a factory rest and see if you get the B182 update. If not, you can download the B182 update and flash it via dload but if that does not work, you can try doing it via the Hisuite and Updater method.

BLN-L24 stuck at your device is now booting (Solved!!)

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.

Locking bootloader removes root? Also more Questions. [Phone Gone Now]

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.

Mate 9 keeps restarting itself after latest update MHA-L29 8.0.0.373 (C567)

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!