Database Info

[Guide] Huawei P9 & P9 Plus Refurbish Guide

!!!WARNING!!!
IN THE HUAWEI ANDROID N BETA FIRMWARE, DOWNGRADE IS UNAVAILABLE.
I HAVE TESTED IT ON MY PHONE, IF YOU TRYING TO DOWNGRADE, IT WILL TOLD YOU FIRMWARE VERIFICATION ERROR.
This thread will change to a small guide of my tool.
[FOR REFURBISH PURPOSE / WITH Official Recovery]
Requirement:
Computer and P9 connected to the same WiFi network (locally accessable).
Step:
1. Run the tool, select firmware version and press [Start]
2. On your phone, set proxy IP to your computer's IP, and the proxy port to 41279
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Enter Settings -> Update -> Menu -> Download latest full package
(This tool cannot get incremental update package, so it would not give you any update info before click 'Download latest full package')
4. Then, you will get a update around 1.70 GB - 1.80GB, that is the regular size for full rom with pre-installed data.
(If the update package is aroung 1.50GB that means the customize version is incorrect for your device)
5. After fully flash in recovery, you can press Volume Up + Power enter official recovery and do a Factory Reset.
[FOR UNBRICK PURPOSE / WITHOUT Official Recovery]
Due to the limitation of Huawei HiSuite, It would NOT flash the pre-installed data, like themes or icons.
So, following procedure is for unbrick ONLY. If you want fully flash the firmware, you need to follow next reply.
Requirement:
1. Your device can enter FASTBOOT.
(If that partition was broken, this tools cannot help you anymore.)
2. Huawei HiSuite (Click Here to Download)
3. A computer that have a stable internet connection.
Step:
1. Start the tool, select correct firmware version, and click [Start]
2. Start HiSuite, Set proxy IP to 127.0.0.1, proxy port to 41279
3. Click [System Recovery] in the right bottom corner of HiSuite
4. Follow the procedure provided by Huawei to make your devices into FASTBOOT Mode.
(Power off -> Connect your device to the computer running HiSuite -> Hold Volume Down + Power button till it enter FASTBOOT)
5. Waiting for HiSuite to recover your Huawei P9.

Changed Thread Purpose

Change thread purpose.

Hello can you make it compatible with P9 Plus

Steve2016 said:
Hello can you make it compatible with P9 Plus
Click to expand...
Click to collapse
I will trying to do that tomorrow. Thanks for your support.
Sent from my EVA-L09 using XDA-Developers mobile app

The version B 166 is not the latest available? Where came the B170?

Could you please make this for the P9 lite?
many thanks
Paul
---------- Post added at 11:47 PM ---------- Previous post was at 11:44 PM ----------
Or other huawei devices? I have the honor 5c and im trying to port/apply to P9 lite rom onto it, they are pretty much the same phone/spec
thanks again
Paul
---------- Post added at 11:47 PM ---------- Previous post was at 11:47 PM ----------
Or other huawei devices? I have the honor 5c and im trying to port/apply to P9 lite rom onto it, they are pretty much the same phone/spec
thanks again
Paul

Alex91Sc said:
The version B 166 is not the latest available? Where came the B170?
Click to expand...
Click to collapse
As I tested before, that version may during internal testing for release and that build, SafetyNet related function (like Android Pay) may not working properly.

Can I with "How to fully reflash" method change the brand of the phone ? Actually I'm running EVA-L09C55B141 and I've no update to do

Shocker580 said:
Can I with "How to fully reflash" method change the brand of the phone ? Actually I'm running EVA-L09C55B141 and I've no update to do
Click to expand...
Click to collapse
Actually, you need change oeminfo partition first, to make the Updater can fetch the oem data files correctly.
Currently, you can follow this thread or SRK Tool to change the oeminfo from C55 to C432, and flash other firmware.
If you want change to other country and/or operator's brand, I'll write a guide later depend on my experience.

Alex91Sc said:
The version B 166 is not the latest available? Where came the B170?
Click to expand...
Click to collapse
Currently, My tool only provide the full firmware flash option, because the OTA package may depend on different version. It may support force OTA in the future.

Steve2016 said:
Hello can you make it compatible with P9 Plus
Click to expand...
Click to collapse
It has been done. You can find it at HERE

hajuuk said:
Actually, you need change oeminfo partition first, to make the Updater can fetch the oem data files correctly.
Currently, you can follow this thread or SRK Tool to change the oeminfo from C55 to C432, and flash other firmware.
If you want change to other country and/or operator's brand, I'll write a guide later depend on my experience.
Click to expand...
Click to collapse
Hi man, thanks for you reply.
So what I've to do is: 1. unlock bootloader 2. flash a special recovery 3. root the phone 4. flash the new oem data 5. flash the new firmware (compatible with the oem) and restore recovery + bootloader ?
Am I right ?
In all this, will I lose the warranty ?

Shocker580 said:
Hi man, thanks for you reply.
So what I've to do is: 1. unlock bootloader 2. flash a special recovery 3. root the phone 4. flash the new oem data 5. flash the new firmware (compatible with the oem) and restore recovery + bootloader ?
Am I right ?
In all this, will I lose the warranty ?
Click to expand...
Click to collapse
Only one thing is incorrect , Step 5, using my tool + HiSuite restore to official firmware.
As I tested before, follow unbrick method, will automatically flash official recovery and restore the lock status.
As far as I know, that would not avoid the warranty.

Thanks for the tool man. Works great

Thanks a lot for work!
Hi man, I had c02 and I debranded to c432 using oem. Now I've c432b170 received by official ota. If I want rollback to c02b133( is it the latest official update for vodafone?) is it enough to use your software ore I'd to use oem again?

Luke74125 said:
Hi man, I had c02 and I debranded to c432 using oem. Now I've c432b170 received by official ota. If I want rollback to c02b133( is it the latest official update for vodafone?) is it enough to use your software ore I'd to use oem again?
Click to expand...
Click to collapse
Yep, it is enough to use my tool to go back. Due to my tool only have full firmware listed, the C133 might not be the newest version. If not, the OTA is waiting after flash.[emoji14]
However, you need restore the oeminfo first for full restore, because you phone would get oem data partition based on it when you download latest full package with my tool.
Due to TWRP is essential for changing oeminfo, flash twice is essential for full refurbish. Firstly, use HiSuite to flash official system and recovery. Then, use the phone itself to restore one data.
Sent from my EVA-L09 using XDA-Developers mobile app

Thanks a lot again!
Sorry i'm new user so i can't quote discussion for 10 reply):
I'd like to roll back to c02b133 from c432b170
So let's see if I've understood : flash vodafone firmware using your tool - unlock bootloader - install twrp - flash oeminfo and reset system..

Luke74125 said:
Thanks a lot again!
Sorry i'm new user so i can't quote discussion for 10 reply):
I'd like to roll back to c02b133 from c432b170
So let's see if I've understood : flash vodafone firmware using your tool - unlock bootloader - install twrp - flash oeminfo and reset system..
Click to expand...
Click to collapse
No, the correct step is, unlock your phone -> flash recovery -> restore oeminfo -> flash firmware by HiSuite (it will lock your phone and flash official recovery automatically) -> flash again by phone for full restore oem data partition.
After all the steps, you can fully go back to stock firmware.
Format system to clean it is optional.
Cheers
Sent from my EVA-L09 using XDA-Developers mobile app

Sorry but do not understand...
Correct steps : unlock your phone (unlock bootloader?) - flash recovery (install twrp?) - restore oeminfo ( flash oeminfo.zip by twrp?) - flash firmware by hisuite ( connect usb my phone to pc hisuite without your tool? ) - flash again by phone for full restore oem data partition ( what do i flash ? vodafone firmware by your tool?).
Excuse for my poor English and thanks again for patience

[GUIDE]Rollback From Oreo

HWOTA won't work with OREO, so we need to rollback manually with ADB.
this guide (more like just code memo) is for people who didn't backuped before update,
or can't go back to B183 directly by any reason (like dead capacitive keys).
What You Need to Read
[STF-L09C432] How to install Oreo on your H9
https://forum.xda-developers.com/honor-9/how-to/stf-l09c432-how-to-install-oreo-h9-t3707729
[GUIDE][REBRAND] Honor 9 [ANY REGION]
https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719/post75439859#post75439859
What You Need to Download
HWOTA (Windows tool)
Firmware Finder (Windows tool)
ADB and Fastboot (Windows tool)
C432B120 Firmware File
Stock NoCheck Oreo Recovery
What You Need to Have
unlocked bootloader and superuser, ADB.
adb push won't work, so you will need microSD card.
exFAT may not work on some ROMs (like Treble AOSP 8.0), so format it to FAT32.
What You Need to Do
1.
download B432C120 from Windows Version Firmware Finder and rename it (check [REBRAND] Honor 9 Thread).
why B120? bcuz it's the only firmware that leave capacitive keys and flashlights alive.
put them into microSD card root, with NoCheck Oreo Recovery .img (check How to install Oreo Thread).
insert microSD card to your phone and connect the phone to your PC and open ADB.
first of all,
Code:
adb shell
su
let's change recovery with NoCheck one first.
Code:
dd if=/storage/sdcard1/STF_RECOVERY_OREO_NoCheck.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
dd if=/storage/sdcard1/STF_RECOVERY_OREO_NoCheck.img of=/dev/block/bootdevice/by-name/erecovery_ramdisk
note that 'sdcard1' maybe different, like 'E1F2-A123', base on your ROM. It's your sdcard's name.
We'll put Firmware into recovery cache and make stock recovery to flash it.
Code:
echo --update_package=/sdcard/update.zip > /cache/recovery/command
echo --update_package=/sdcard/update_data_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/update_all_hw.zip >> /cache/recovery/command
reboot recovery
note that 'sdcard' is not 'sdcard1', so you don't have to change it to sth like E6F3-A496.
your phone will reboot 2, 3 times and will suggest low level format and download new firmware.
now go to fastboot and unlock the bootloader.
this will do low level format.
2.
now your phone is something like EMUI 8.0 Android 7.0, with broken build number.
do HWOTA (no need to do rebrand, just do firmware flash with update option) with C432B120 we downloaded before.
This will make your phone Stock C432B120.
3.
Let's Go back to B183, the newest Nougat ROM.
download Firmware Finder for Huawei app at Play Store.
choose C432B183 and update it with proxy.
maybe you got 'yet approved' error,
but there are quite numerous C432B183 so check every single one of it.
There is one that is flash-able.
4.
TADA, now you rollbacked your phone.

I think you can also rollback with Hisuite on PC, I did a few times to rollback from beta.

I don't like your guide because :
-You're flashing a B120 firmware which is not to rollback from oreo when there is already a B183 oreo's rollback available for this on FF.
-You have to flash it 2 times to fix your build version issue (maybe because it's not a rollback firmware).
Please note that your step 1 & 2 are the same, you just did hwota manually on step 1.
-You then updated from B120 to B150 when you could have directly updated to B183 not for oreo's rollback on FF.
Sorry.

nednapalm said:
I think you can also rollback with Hisuite on PC, I did a few times to rollback from beta.
Click to expand...
Click to collapse
Never tried that, but it would be much more simple and clear. This Thread will become useless though lol.
oslo83 said:
I don't like your guide because :
-You're flashing a B120 firmware which is not to rollback from oreo when there is already a B183 oreo's rollback available for this on FF.
-You have to flash it 2 times to fix your build version issue (maybe because it's not a rollback firmware).
Please note that your step 1 & 2 are the same, you just did hwota manually on step 1.
-You then updated from B120 to B150 when you could have directly updated to B183 not for oreo's rollback on FF.
Sorry.
Click to expand...
Click to collapse
1. isn't that rollback for beta B321 and disables capacitive keys and Flash lights with B360a?
2. that's the point of this guide, since HWOTA is not properly working with oreo. you can just change the strings inside the hwota.sh if you want to.
3. no you can't jump to B183 directly from B120, shows approve error. any other firmware except B150 shows the error, same to B183 from B150.
Thx for the opinions though.

TASON42 said:
1. isn't that rollback for beta B321 and disables capacitive keys and Flash lights with B360a?
Click to expand...
Click to collapse
Nope, it's a rollback from oreo B3xx.
It's still has to be tested if rolling back from B3xx to B183 mess with capacitives keys.
TASON42 said:
2. that's the point of this guide, since HWOTA is not properly working with oreo. you can just change the strings inside the hwota.sh if you want to.
Click to expand...
Click to collapse
...
TASON42 said:
3. no you can't jump to B183 directly from B120, shows approve error. any other firmware except B150 shows the error, same to B183 from B150.
Click to expand...
Click to collapse
Sorry but you are wrong : by using FF on B120, I can guarantee you that YOU CAN update to approved B183 using the full ota update ( the B183 one that is not to rollback).
TASON42 said:
Thx for the opinions though.
Click to expand...
Click to collapse
You're welcome, I didn't want to let bad guides posted without telling so.

oslo83 said:
Nope, it's a rollback from oreo B3xx.
It's still has to be tested if rolling back from B3xx to B183 mess with capacitives keys.
...
Sorry but you are wrong : by using FF on B120, I can guarantee you that YOU CAN update to approved B183 using the full ota update ( the B183 one that is not to rollback).
You're welcome, I didn't want to let bad guides posted without telling so.
Click to expand...
Click to collapse
With this you can do whatever you think is the only problem that is in Russian. http://4pda.ru/forum/index.php?showt...ost&p=69940847
---------- Post added at 07:53 PM ---------- Previous post was at 07:49 PM ----------
letterio said:
With this you can do whatever you think is the only problem that is in Russian. http://4pda.ru/forum/index.php?showt...ost&p=69940847
Click to expand...
Click to collapse
https://4pda.ru/forum/index.php?showtopic=833645&st=2400#entry69940847

I found out that We do can OTA to B183 directly, so I changed the GUIDE + some minor change.

2. now your phone is something like EMUI 8.0 Android 7.0, with broken build number. d
I didn't get this point. i mean with hwota (link you put in) we have just 2 options. update and rebrand. we have no choice for just flashing. sorry for my bad understanding.

ImHonor said:
I didn't get this point. i mean with hwota (link you put in) we have just 2 options. update and rebrand. we have no choice for just flashing. sorry for my bad understanding.
Click to expand...
Click to collapse
do update.

which version of B183 are we supposed to take? I choose the last one: 116404
but I'm not sure it's the correct one. (changelog tell it's a rollback firmware)
seems the good one is the 111176 (changelog is not about rollback)

Don't follow this outdated OP and thread which were never right in the first place.
For rollback use HiSuite or HuRUpdater.

[Tool] [HuRUpdater] [0.4] [Flash official firmware in recovery

Here I present my tool to flash Honor stock firmware in TWRP recovery. I have tested it on all currently available firmwares for Honor 9 STF but still this tool is beta.
HuRUpdater
Huawei Recovery Updater​
Flash official firmware zip files
Can detect if firmware locks bootloader
Can detect if firmware wipes data
Download:
HuRUpdater_0.4.zip
Tested up to STF-L09C432B369
HuRUpdater_0.3.zip
HuRUpdater_0.2.zip
Tested up to STF-L09C432B362
It's recommended to use a proper custom recovery (with running oeminfo_nvm_server service) like for example my version of TWRP.
How to use:
Warning: Make sure you know what you are doing and do not flash firmware from other devices.
Download firmware files (for official firmware use Huawei Firmware Finder).
Put files you want to flash in a seperate folder on sdcard.
Supported zip files to flash are (name must match):
update.zip (use FullOTA file)
update_all_hw.zip
update_data_public.zip
Optional: Put recovery.img in same folder if you want to keep custom recovery.
Put HuRUpdater zip in same folder. Example:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Select only HuRUpdater to flash in custom recovery.
Follow instructions on screen. Flashing can take multiple minutes.
Problems:
If firmware includes factory reset
Factory reset is not supported by custom recovery. Therefore HuRUpdater will flash stock recovery before launching factory reset. After flashing firmware and doing factory reset, you need to flash recovery manually.
Supported devices:
Honor 9
Honor View 10 (confirmed* by Rommco05)
Huawei P9 Lite (confirmed* by Tecalote)
Huawei P9 (confirmed* by Tecalote)
Huawei P Smart (confirmed* by flibblesan)
Huawei Mate 9 (confirmed* by ante0)
Huawei Mate 10 (confirmed* by Tecalote)
Huawei P20 (confirmed* by realz88)
Honor 8 (confirmed* by [email protected])
Huawei P8 Lite (2017) (confirmed* by neverdies)
Honor 6X (confirmed* by siddhrsh)
Huawei Mediapad M5 (confirmed* by ZeuseZ)
Other Huawei/Honor? Try and let me know
* first confirmation
Bugreport:
Post full /tmp/recovery.log file in comments
Thanks to all testers who report new devices working. Especially big thanks to @Tecalote who provided me with extensive testing / logs and found bugs.
XDA:DevDB Information
HuRUpdater for Honor, Tool/Utility for the Honor 9
Contributors
zxz0O0
Version Information
Status: Beta
Created 2018-03-27
Last Updated 2018-09-23

Reserved
Changelog:
0.4
Add static busybox
Update installer binary
0.3
Fix set_metadata (do not abort)
Add own busybox for recoveries with bugged version
Rename zip files to match HWOTA names
Click to expand...
Click to collapse

very good,
only a question: recovery.img that have put in directory, have to be Stock recovery image orTwrp?

angelobiz said:
very good,
only a question: recovery.img that have put in directory, have to be Stock recovery image orTwrp?
Click to expand...
Click to collapse
Stock recovery.

angelobiz said:
very good,
only a question: recovery.img that have put in directory, have to be Stock recovery image orTwrp?
Click to expand...
Click to collapse
Custom recovery. When you flash stock firmware, the recovery is overwritten. By placing a recovery.img of TWRP in the folder, it will be automatically flashed after stock firmware. Therefore you will keep custom recovery.

Sorry for my bad english.
I'm on Oreo B360 with root and custom twrp (0.2).
Can i use this tool to downgrade to Nougat?
I would like to go back to B183 version...
Inviato dal mio STF-L09 utilizzando Tapatalk

lalaspdn said:
Sorry for my bad english.
I'm on Oreo B360 with root and custom twrp (0.2).
Can i use this tool to downgrade to Nougat?
I would like to go back to B183 version...
Inviato dal mio STF-L09 utilizzando Tapatalk
Click to expand...
Click to collapse
Yes it should work. Downgrading to 183 will format data so make a backup.

Wonderful! It also solves the problems with bricked Honor 9

This tool is amazing. It should be a sticky post. You've no idea how many people will be saved by this tool. Dude, you rock amazingly. Be proud of yourself! It saved me countless hours of flashing, after many hours trying to recover a bricked honor 9... You should post this tool on Reddit with relevant information. It's an amazing tool.

can i use it for flash the stock fw on top the RRoS(android 7.1)?

Amazing tool that will delight more than one

realz88 said:
after many hours trying to recover a bricked honor 9...
Click to expand...
Click to collapse
If you can load to or flash and load to twrp your device is NOT bricked! )) It is very easy to flash zip's of official ROM in this case with or without this tool. This tool is very good by 2 reasons: 1) Can detect if ROM wipes data. 2) Can detect if ROM locks bootloader. It is very convinient! Good job.
PS Your device is bricked if you have error 2 and error 11 when trying to boot. It is not also a problem if you can still reach erecovery.

@zxz0O0 I'm on B360 and want to update to B362 but FF says it's not authorized (all versions say that), so I'd like to know what version you used and what is the danger (if any) of flashing an unauthorized firmware version.

JBolho said:
@zxz0O0 I'm on B360 and want to update to B362 but FF says it's not authorized (all versions say that), so I'd like to know what version you used and what is the danger (if any) of flashing an unauthorized firmware version.
Click to expand...
Click to collapse
Risk of flashing an unauthorized firmware:
None, that's just the relase method Huawei choose https://en.wikipedia.org/wiki/Phased_adoption
Risk of flashing a firmware:
Same as with official way, you could brick / destroy your device if you for example power off during fw flashing.

Rommco05 said:
Hi, this tool is based on nocheck recocery? Im just curious if will work on another devices. Still can't test...
edit: also can be flashed small OTA update instead full OTA?
Click to expand...
Click to collapse
No it's not based on nocheck recovery. I have never tried small OTA files but it could work maybe.

@zxz0O0 Flashed latest B362 (dated March 28th) with no issues, thank you.
By the way, that March 23rd release of B362 has apparently been removed from server (that's what FF was saying on mine)

Great, works fine on Mate 9 (Although got E: Unknown command []] 2 times).
Updated from C432B366 to C432B367-SP1, mainly to test because B367-SP1 is some test firmware.

ante0 said:
Great, works fine on Mate 9 (Although got E: Unknown command []] 2 times).
Updated from C432B366 to C432B367-SP1, mainly to test because B367-SP1 is some test firmware.
Click to expand...
Click to collapse
Thanks for feedback. This error is actually caused on how TWRP interprets the output of the flashable zip. It can be ignored.

Rommco05 said:
Succesfully installed two updates in order BKL-L09C432B140 > BKL-L09C432B141 (both FULL OTA). This is amazing! Just small output, script detect bootloader will be locked but after installation wasn't. Very quick installation.
Click to expand...
Click to collapse
Did you used my version of TWRP for Honor 10?

Rommco05 said:
Yes, v0.3
Click to expand...
Click to collapse
Thank you, that's great! The 0.4 should also work.

How to downgrade firmware?

I have a new SHT-AL09 with 172 firmware and a locked bootloader.
This firmware prohibits DC-Unlocker from reading the bootloader unlock code.
How do I downgrade to a previous firmware?

Try HuRUpdater: https://forum.xda-developers.com/mediapad-m5/how-to/unbrick-mediapad-m5-install-otas-t3856312
You should be able to install TWRP even with locked bootloader. Download the full OTA and follow the HuRUpdater instructions.

Has anyone tried it yet?
Don't want to be the first, since I do not feel too comfortable and I am awqy for a few days

kev1807 said:
Has anyone tried it yet?
Don't want to be the first, since I do not feel too comfortable and I am awqy for a few days
Click to expand...
Click to collapse
I think there is very little risk. Even when the downgrade fails, you should be able to just flash 172 again with HuRUpdater to restore back the original state. Don’t try to rollback too far, install the last version prior to 172 and try dc unlocker again.

I asked on a german Forum and got the response that TWRP cannot be installed with locked BL - which I find somewhat logical - however, I am reaching for the unlikely event that I can get an open Bootloader somehow....

I am a little confused by the instructions. I have to put the TWRP.img in the folder on the SD Card together with the HuRUpdater.zip file and the firmware zip files. But then what? How do I flash anything?

konradsa said:
Try HuRUpdater: https://forum.xda-developers.com/mediapad-m5/how-to/unbrick-mediapad-m5-install-otas-t3856312
You should be able to install TWRP even with locked bootloader. Download the full OTA and follow the HuRUpdater instructions.
Click to expand...
Click to collapse
I cannot flash TWRP with my locked bootloader. I get an error FAILED (remote: Command not allowed) when I try this when the M5 is in fastboot mode: fastboot flash recovery_ramdisk twrp.img
Found this on the last page of the HuRUpdater thread:
Absolute prerequisite: unlocked bootloader
I don't have this so is there another way to downgrade the firmware?

OK, bummer. You can try the dload method, not sure if that works for downgrades though: dload

konradsa said:
OK, bummer. You can try the dload method, not sure if that works for downgrades though: dload
Click to expand...
Click to collapse
I tried that already. It starts installing but at 5% it stops with an error: Software install failed

Flavio said:
I tried that already. It starts installing but at 5% it stops with an error: Software install failed
Click to expand...
Click to collapse
Firmware finder is probably your best bet: https://forum.xda-developers.com/honor-6x/help/to-bln-l21c185-t3578790

konradsa said:
Firmware finder is probably your best bet: https://forum.xda-developers.com/honor-6x/help/to-bln-l21c185-t3578790
Click to expand...
Click to collapse
Firmware Finder apparently does not work with EMUI8 anymore.
And there is no rollback package available for the M5.
I have always found a solution for these kind of problems on XDA (and I have had a bricked device or two) but for the moment I am at a loss.
Guess I will have to learn to live without root and with the stock Huawei firmware...

Flavio said:
I tried that already. It starts installing but at 5% it stops with an error: Software install failed
Click to expand...
Click to collapse
Flavio said:
Firmware Finder apparently does not work with EMUI8 anymore.
And there is no rollback package available for the M5.
I have always found a solution for these kind of problems on XDA (and I have had a bricked device or two) but for the moment I am at a loss.
Guess I will have to learn to live without root and with the stock Huawei firmware...
Click to expand...
Click to collapse
Sorry mate, tough luck. ? I think the hardware of the device is pretty nice, but the stock firmware is so full of crap and spyware, totally unacceptable.

when downgrading using dload, check for xloader version first.
https://forum.xda-developers.com/showthread.php?t=2433454
I jut downgraded my M5 AL19-CMR 8.0.0.172 back to 8.0.0.161 without any problems.
I used the firmware file from https://androidhost.ru/ I used the 8.0.0.161 dated 17.07.2018, I am in Germany and have as it seems the european version of the tablet!

kev1807 said:
when downgrading using dload, check for xloader version first.
https://forum.xda-developers.com/showthread.php?t=2433454
I jut downgraded my M5 AL19-CMR 8.0.0.172 back to 8.0.0.161 without any problems.
I used the firmware file from https://androidhost.ru/ I used the 8.0.0.161 dated 17.07.2018, I am in Germany and have as it seems the european version of the tablet!
Click to expand...
Click to collapse
For my SHT-AL09 there is no older firmware on androidhost.ru than B172.
I have downloaded the B163 and B152 firmware through Huawei Firmware Finder and I can extract it with HuaweiUpdateExtractor but then what?

Flavio said:
I have a new SHT-AL09 with 172 firmware and a locked bootloader.
This firmware prohibits DC-Unlocker from reading the bootloader unlock code.
How do I downgrade to a previous firmware?
Click to expand...
Click to collapse
From my latest findings:
Bootloader need to be unlocked for DOWNGRADE to sucess in firmware mode with a working dload service repair firmware.
With locked bootloader you'll only be able to DOWNGRADE in eRecovery mode with the latest firmware approved (It will be a downgrade only if said version is the latest approved fetched in eRecovery and inferior to yours current)
I did not find yet how the latest firmware shown/available in eRecovery is fetched into eRecovery. I think it happens in normal mode sometimes when you're connected online. You'll then have to reboot later to eRecovery to be shown...
Now, for your SHT-AL09 B172 with august 2018 secutity patches, the only way to downgrade is to get your unlock code and vice&versa.
Luckyly, third-party sellers are just starting to provide working bootloader's unlock code online for around 30~50€.
New devices are supported.
You just pay, gave them Model ID, IMEI1, Serial, Product ID and you'll get your code within the next hours.
You just pay, gave them Model ID, IMEI1, Serial, Product ID and you'll got it within the next hours. I already tested it on few devices.
FunkyHuawei does it for 130€ per device with other services included.

Flavio said:
For my SHT-AL09 there is no older firmware on androidhost.ru than B172.
I have downloaded the B163 and B152 firmware through Huawei Firmware Finder and I can extract it with HuaweiUpdateExtractor but then what?
Click to expand...
Click to collapse
I am also interested in rooting M5. Where you able to downgrade the tablet from B172 to B161?

No

I am also looking for a way to downgrade my Mediapad M5.
I have Hauwei MediaPad M5 CMR-AL09 (C432) currently running 8.0.0.192. dc-unlocker does not work with this version so I can not unlock bootloader.
This is what I have done:
* Format external sdcard into exfat. I used my Ubuntu Linux computer for this, sudo mkfs.exfat /dev/sdx1.
* Put the empty sdcard into the tablet.
* Download android app "Firmware Finder for Huawei" and I choose CMR-AL09C432B161 (8.0.0.161) FullOTA-MF. Downloaded that into update.zip file.
* I use android app FX File Explorer to get read/write access to the mediacard and to create the dload folder.
* I used android app FX File Explorer to extract only UPDATE.APP file into mediacard and the dload folder. The file is around 4.2GB in size when extracted. I also tried to put all files into dload folder but with the same result below.
* Open dialer and type in *#*#2846579#*#*. Go to software upgrade and choose SDCard upgrade. The tablet will now restart and do the downgrade.
* Problem now is that it goes into 5% and then fails.
Am guessing there is some protection to downgrade into 8.0.0.161 version.
Guys.. Let's solve this. :crying:

Blinkiz said:
I am also looking for a way to downgrade my Mediapad M5.
I have Hauwei MediaPad M5 CMR-AL09 (C432) currently running 8.0.0.192. dc-unlocker does not work with this version so I can not unlock bootloader.
This is what I have done:
* Format external sdcard into exfat. I used my Ubuntu Linux computer for this, sudo mkfs.exfat /dev/sdx1.
* Put the empty sdcard into the tablet.
* Download android app "Firmware Finder for Huawei" and I choose CMR-AL09C432B161 (8.0.0.161) FullOTA-MF. Downloaded that into update.zip file.
* I use android app FX File Explorer to get read/write access to the mediacard and to create the dload folder.
* I used android app FX File Explorer to extract only UPDATE.APP file into mediacard and the dload folder. The file is around 4.2GB in size when extracted. I also tried to put all files into dload folder but with the same result below.
* Open dialer and type in *#*#2846579#*#*. Go to software upgrade and choose SDCard upgrade. The tablet will now restart and do the downgrade.
* Problem now is that it goes into 5% and then fails.
Am guessing there is some protection to downgrade into 8.0.0.161 version.
Guys.. Let's solve this. :crying:
Click to expand...
Click to collapse
Hmhm. I downgraded my Mediapad M5 Pro from 8.0.0.172 to 8.0.0.161
This is what I did:
https://www.android-hilfe.de/forum/...uer-huawei-mediapad-m5-ab-08-2018.892304.html
(short paraphrase of my downgrade-"guide" at android-hilfe.de)
1) check xloader-version
2) Download the potential downgrade from androidfilehost.ru (this worked for me, again, M5 PRO (CMR-AL19), Europe! https://androidhost.ru/byu )
2.1) The structure inside is firmware-name>software>dload
2.2) copy dload onto your SD (root directory)
3)The downgrade-process
3.1) power off the device
3.2) Volume up AND down AND Power Button for some seconds
3.3) Downgrade should start! If folder is not recognized, a Pink screen will appear - just do it from the start.
After rebooting, you should then have the version you wanted to downgrade to.
I have done this several times ( accidently updated once or twice )and it worked without any trouble.
The 5% thing: it stayed at 5% for quite some time. But it always went on after some time, at least for me
I read somewhere, sometime ago that with Firmware Finder the security check that is somewhere included in the file is not removed and therefore you cannot use those files. It seems imperative to me that one uses androidhost.ru (no guarantee that this information is right - so feel free to correct me )
ah, sorry only now I realized that you specified CMR-AL09, we had someone do it for SHT-AL-09, sorry :-/
but why don't you try the files from androidhost.ru (download the correct firmware! I linked the one for the M5 Pro! )

Thanks kev1807 for the input.
I tried the firmware you linked to for Huawei MediaPad M5 CMR-AL09 (C432) version 8.0.0.161. It did not work.
I found the version 8.0.0.190 on androidfilehost.ru and that worked. So I have now downgraded from 8.0.0.192 to 8.0.0.190 but that will not help me much. Downgrading into 8.0.0.161 still does not work.
I was on 8.0.0.192 and manage to use the file
"Huawei MadiaPad M5 CMR-AL19 hw eu Cameron-AL09A 8.0.0.190(C432) Firmware 8.0.0 r1 EMUI8.0 05014XYB [androidhost.ru]"
I have tried these packages but they have not worked.
Huawei MadiaPad M5 CMR-AL09 hw ru Cameron-AL09A 8.0.0.181(C10)Firmware8.0.0r1EMUI8.005014YQD [androidhost.ru]
Huawei MadiaPad M5 CMRCameron-AL19B 8.0.0.161(C432) Firmware Android 8.0 EMUI 8.0 05014XYC androidhost.ru

[ROOT] [UNLOCK] [ANE-LX1/L01/L21] [Stock EMUI 8/9] P20 Lite

Today I will be giving a tutorial on how to root the Huawei P20 Lite using STOCK ROM (ANE-LX1 ANE-L01 ANE-L21)
If you need bootloader unlock code
----------------------------------------
You can use dc-unlocker but, only if you can rollback to 8.0.0.146 or lower (i was on 8.0.0.46 when i used dc-unlocker).
You can try to use PotatoNV, but that will require testpoint access (haven't tested yet).
You can use HCU client with a 3day account pass, which is quite expensive (I have not actually tested this yet).
Rollback EMUI 9 to EMUI 8
-----------------------------
This is where my frustrations with this phone began.
You can try to use dload method, but in my experience this DOES NOT WORK when you're on EMUI 9.
It will just give you an error about incompatible version, every time.
Forced dload was also a complete bust for me, 24 hours wasted
I was finally able to rollback from HiSuite 11. I was on 9.1.0.200 when I had the option to rollback and it rolled me back to 8.0.0.163.
From 8.0.0.163 I could use normal dload to rollback further until I could use dc-unlocker.
I made the mistake of upgrading to EMUI 9 after I unlocked my bootloader. My advise: if you can manage to get to 8, stay there. It's less bloated and feels smoother. I have not received the option to rollback after I re-upgraded to 9 since. And I have not found AANNYY method to rollback to 8 since then, I pretty much gave up and stayed on EMUI 9.
EMUI 8
---------
copy magisk23.zip to sdcard
flash twrp to recovery_ramdisk.img
Code:
fastboot flash recovery_ramdisk "twrp-3.2.1-0.img"
EDIT: ***NEW official TWRP version*** TWRP 3.6.2.0_9-0
Code:
fastboot flash recovery_ramdisk "twrp-official-3.6.2_9-0-anne.img"
Code:
fastboot reboot recovery
Once in twrp install the magisk23.zip file.
This will patch the boot.img from recovery_ramdisk.img with magisk v23
Reboot -> System
Once in android you will get the usual magisk app, open and allow to perform additional tasks like installing the manager app.
Pretty straight forward
EMUI 9
---------
While still on stock firmware, update your android to the highest possible firmware (HiSuite or on phone -> Settings -> System ....)
1. When your back in android power off phone.
2. Go into fastboot (USB cable plugged in -> Power + Vol Down)
3. Flash twrp into recovery_ramdisk
Code:
fastboot flash recovery_ramdisk twrp-3.2.1-0.img
Code:
fastboot reboot recovery
Now In TWRP
4. Install Image -> twrp-3.2.1-0.img into eRecovery partition
5. Install Image -> magisk23_patched-ane.img into Recovery Partition
6. Reboot -> Recovery
Note: So booting into recovery mode gives you a ROOTED environment and System Mode gives you NON-ROOTED.
EDIT: *** With the new TWRP 3.6.2.0_9-0 you will have to boot into recovery (by holding Vol Up + Power till the screen comes on) every time you boot the phone or it will boot into normal system where the root environment isn't present ***
That's it. Now you should have root access.
You can still use twrp, but you have to access it like you would access eRecovery. So from power off (coldstart) -> Hold Vol Up while plugging in the USB Cable, continue to hold Vol Up, till you get the twrp logo.
Caution: This overwrites eRecovery, this can be dangerous, as eRecovery is the only thing standing between you can a hard brick if twrp wont boot anymore. This is due to fastboot not being able to flash eRecovery. You can only flash eRecovery from twrp. This is particularly dangerous if your data partition gets corrupted, this can happen when formatting data through twrp 3.4.0 and above. When your data partition is corrupt, twrp will freeze on the loading logo, leaving you no way to flash the original eRecovery.
Note: I think you can flash the eRecovery_ramdisk.img over the normal recovery_ramdisk in case of a brick situation. Though I haven't tested that idea yet, im just planning on going that route if I run into such a scenario. The eRecovery is particularly usefull as it can recover almost any situation by using wifi to download a stock rom and full flash that entire rom.
This way is robust, no need for key combo's when restarting the device etc.
All Downloads (GDrive):
Gdrive
After the root, you might find yourself needing safetynet attest pass.
This can be achieved by:
1. Open Magisk and setup MagiskHide ( Search on XDA if you don't know how to do this )
2. Magisk Modules -> Install Riru
3. Magisk Modules -> Install from storage -> Select safetynet-fix-v2.1.0.zip
note: If PropsConfig is installed, remove it first and reboot
If you need to use Smali then it's once again kinda straight forward.
1. Copy /system/framework to sdcard (anywhere u can copy it from)
2. Copy the framework folder onto pc
3. Open SmaliPatcher.exe -> Select the framework folder -> select patch options and patch
4. Copy the created magisk module zip file onto sdcard
5. Install magisk module -> Magisk -> Modules -> Install from storage
Hope you have a smooth experience rooting this device.
External links:
Tested custom recoveries from -Alf-
Source of rooting and flashing information by -Alf-
Credits:
@-Alf- for the magisk patched image. I only repatched his recovery_ramdisk from magisk v21 to v23
And also for the twrp recovery 3.2.1-0 GAGUGA Edition

RESERVED

gh0stza said:
And I have not found AANNYY method to rollback to 8 since then,
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-85379393
gh0stza said:
eRecovery is the only thing standing between you can a hard brick if twrp wont boot anymore
Click to expand...
Click to collapse
there is one more thing - Service ROM aka 'full stock ROM' & dload method
gh0stza said:
your data partition gets corrupted, this can happen when formatting data through twrp.
Click to expand...
Click to collapse
Can happen only with TWRP 3.4.0 and above.
Regards

No matter what I did, dload failed, I must have downloaded 30 roms and tried every which way with dload. Nothing worked!!!!!
dload only worked on same EMUI. So nope sorry dude dload was a no go for me. Maybe it works for someone else, which is why I mentioned it.
And yes, TWRP 3.4.0 and above. I was using a twrp(3.5.2_9-0) from official twrp repository for ANE-LX1 when I formatted my data partition. However, that's not the point.
Someone else is absolutely BOUND to fall into this trap too, and as I said that TWRP came from the official chain.
So my only intention is to warn the next guy who might just be using that version or for whatever other reason twrp doesn't start anymore. I'm just saying - BE CAREFUL

gh0stza said:
No matter what I did, dload failed, I must have downloaded 30 roms and tried every which way with dload. Nothing worked!!!!!
dload only worked on same EMUI. So nope sorry dude dload was a no go for me. Maybe it works for someone else, which is why I mentioned it.
And yes, TWRP 3.4.0 and above. I was using a twrp(3.5.2_9-0) from official twrp repository for ANE-LX1 when I formatted my data partition. However, that's not the point.
Someone else is absolutely BOUND to fall into this trap too, and as I said that TWRP came from the official chain.
So my only intention is to warn the next guy who might just be using that version or for whatever other reason twrp doesn't start anymore. I'm just saying - BE CAREFUL
Click to expand...
Click to collapse
this is why we have this article here: https://forum.xda-developers.com/t/recommended-and-tested-twrp-recovery.4199099/

-Alf- said:
this is why we have this article here: https://forum.xda-developers.com/t/recommended-and-tested-twrp-recovery.4199099/
Click to expand...
Click to collapse
Shiet dude, 3 full days rooting this device and I didn't come upon this post once. Now I'm gonna have to try to downgrade again with HuRUpdater and that twrp.
That's a nice post - thanks

gh0stza said:
Shiet dude, 3 full days rooting this device and I didn't come upon this post once. Now I'm gonna have to try to downgrade again with HuRUpdater and that twrp.
That's a nice post - thanks
Click to expand...
Click to collapse
What is your regional variant?

-Alf- said:
Oreo and Pie Stock & Custom ROMs:
3.2.1-0 by pretoriano80 (data decryption on Android 8 ) - on Pie use this TWRP e.g. if you want to downgrade to Oreo via HuRupdater.
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
Click to expand...
Click to collapse
Are you saying I should try to use this TWRP to use HuRUpdater to downgrade to 8?
I plan on using the HiSuite downloaded firmware ANE-LX1 8.0.0.163(C185) with HuRUpdater.
Current folder stucture:
ANE-LX1 8.0.0.163(C185)\full\update.zip
ANE-LX1 8.0.0.163(C185)\full\ANE-L01_hw_meafnaf\update_full_ANE-L01_hw_meafnaf.zip
Planned folder structure after renames:
ANE-LX1 8.0.0.163(C185)\full\update.zip
ANE-LX1 8.0.0.163(C185)\full\update_all_hw.zip
ANE-LX1 8.0.0.163(C185)\full\HuRUpdater_0.4.zip
Then flash HuRUpdater_0.4.zip in twrp 3.2.1-0 by pretoriano80 like the quoted text suggests?
Am I getting this right?
PS: The twrp I am using now -> 3.2.1-0 GAGUGA Edition (Also the one in my download hyperlink)
EDIT: I am on 9.1.0.355(C185) now. But, it is still trying to give me OTA update of the exact same build, so dunno what thats about

gh0stza said:
The twrp I am using now -> 3.2.1-0 GAGUGA Edition (
Click to expand...
Click to collapse
Read carefully bro: https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-85380241
You need 3 .zip files - update, hw and data
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

gh0stza said:
Are you saying I should try to use this TWRP to use HuRUpdater to downgrade to 8?
Click to expand...
Click to collapse
Bingo!

Then I have a problem.
Not one single downloaded firmware anywhere gave me 3 files. It's always just the update.zip (or update_sd.zip for dload) and the hw update.
How can HiSuite flash that firmware then? I just need to flash this 163 rom. But nothing works
***EDIT***
Know what, doesn't matter. I'm pretty fed up with this phone and how Huawei implemented this phones partitioning style and just everything.
I mean where is Odin for Huawei? And just how they withdrew support to get unlock code, limited fastboot command etc.
Just everything about huawei....
I got my ANE-LX1 to a stable root with everything I need working perfectly, so Imma call it a win and move on.
But, you've been great dude and basically almost all useful information I got either came from you ( @-Alf- ) or XDA, so thnx everyone

gh0stza said:
Then I have a problem.
Not one single downloaded firmware anywhere gave me 3 files. It's always just the update.zip (or update_sd.zip for dload) and the hw update.
How can HiSuite flash that firmware then? I just need to flash this 163 rom. But nothing works
***EDIT***
Know what, doesn't matter. I'm pretty fed up with this phone and how Huawei implemented this phones partitioning style and just everything.
I mean where is Odin for Huawei? And just how they withdrew support to get unlock code, limited fastboot command etc.
Just everything about huawei....
I got my ANE-LX1 to a stable root with everything I need working perfectly, so Imma call it a win and move on.
But, you've been great dude and basically almost all useful information I got either came from you ( @-Alf- ) or XDA, so thnx everyone
Click to expand...
Click to collapse
Try this way out...
Flash via dload
https://androidhost.ru/1lsA
and try downgrade via HiSuite.

-Alf- said:
Try this way out...
Flash via dload
https://androidhost.ru/1lsA
and try downgrade via HiSuite.
Click to expand...
Click to collapse
Ok, download started
First thing tomorrow morning, even though I just got everything just right with EMUI 9.
You think it's worth it?

gh0stza said:
I made the mistake of upgrading to EMUI 9 after I unlocked my bootloader. My advise: if you can manage to get to 8, stay there.It's less bloated and feels smoother.
Click to expand...
Click to collapse
gh0stza said:
You think it's worth it?
Click to expand...
Click to collapse

dunno how to respond to that....
I'll keep it in my back pocket, when i'm bored some time this week I might try it.
Else screw it, to hell with you huawei.
PS: Still better then the LG G6, which is unrootable (short of opening it up) due to the total inablility to get unlock code.

so do we run this to keep the stock eRecovery?
Install Image -> twrp-3.2.1-0.img into eRecovery partition
coz i got stuck in a situation where the phone would boot to twrp only and nothing else, somehow managed to get back to stock

khal_nayak said:
Install Image -> twrp-3.2.1-0.img into eRecovery
Click to expand...
Click to collapse
this is only necessary if you want to have both Magisk root and TWRP on board at the same time. (on EMUI 9.1 ramdisk is
included in the recovery_ramdisk).
If you don't need TWRP, just flash magisk_patched_recovery in fastboot mode.

ok but i was trying to remove bloatware i caused the rom to bootloop and then tried factory reset from twrp and now other than twrp nothing boots, where can i get factory image from to get it back to working?
all i need is root with magisk and want to keep the stock erecovery.
if there are better custom roms with volte etc all working then im willing to try it out

khal_nayak said:
tried factory reset from twrp
Click to expand...
Click to collapse
That was not a good idea. On Huawei phones, you can only perform a factory reset from stock recovery.
khal_nayak said:
where can i get factory image from to get it back to working
Click to expand...
Click to collapse
Depends on your build number - model, EMUI version, region variant (Cxxx). What is your b.number?
khal_nayak said:
custom roms with volte etc all working
Click to expand...
Click to collapse
All Treble GSI ROMs on Huawei have common bugs - no VoLTE, no offline charging, no native call recording...

since now i can only boot to twrp and fastboot mode how do i know the model and region?
i bought the phone as nova3e in UAE and currently was on emui 9.1, if i can just get the erecovery back then can make it download the firmware and flash it