Hi,
I have a Mate 10 ALP-L29 8.0.0.132 (C636), unlocked bootloader, rooted with magisk. I would like to update the phone to Android 9.
After reading lots of posts, I think following procedure may give what I want.
0. downloading current stock firmware from here:
https://pro-teammt.ru/en/online-firmware-database/?firmware_model=alp-l29c636b132&firmware_page=0
1. downloading Android 9 official stock firmware from here:
https://pro-teammt.ru/en/online-fir..._model=ALP-L29C636E2R1P12B159&firmware_page=0
2. flashing back stock RAMDISK.img and RECOVERY_RAMDIS.img from stock 8.0.0.132 firmware
https://forum.xda-developers.com/mate-10/how-to/guide-extracting-stock-firmware-files-t3756733
3. Simply waiting for OTA or Using SD card method to update Mate 10 to Android 9.
see: https://huaweiadvices.com/flash-stock-firmware-huawei-honor-phones/
I would appreciate it if someone answer/confirm my following questions:
Will the procedure work?
Is step 2 really necessary?
Will my user data be erased? I don't really mind if I have to re-install my apps.
root will be lost after updating. Is it right?
Thanks.
zagzzig said:
Hi,
I have a Mate 10 ALP-L29 8.0.0.132 (C636), unlocked bootloader, rooted with magisk. I would like to update the phone to Android 9.
After reading lots of posts, I think following procedure may give what I want.
0. downloading current stock firmware from here:
https://pro-teammt.ru/en/online-firmware-database/?firmware_model=alp-l29c636b132&firmware_page=0
1. downloading Android 9 official stock firmware from here:
https://pro-teammt.ru/en/online-fir..._model=ALP-L29C636E2R1P12B159&firmware_page=0
2. flashing back stock RAMDISK.img and RECOVERY_RAMDIS.img from stock 8.0.0.132 firmware
https://forum.xda-developers.com/mate-10/how-to/guide-extracting-stock-firmware-files-t3756733
3. Simply waiting for OTA or Using SD card method to update Mate 10 to Android 9.
see: https://huaweiadvices.com/flash-stock-firmware-huawei-honor-phones/
I would appreciate it if someone answer/confirm my following questions:
Will the procedure work?
Is step 2 really necessary?
Will my user data be erased? I don't really mind if I have to re-install my apps.
root will be lost after updating. Is it right?
Thanks.
Click to expand...
Click to collapse
With EMUI 8 i think that flashing the stock ramdisk would be enough, but it won't hurt flashing the recovery_ramdisk too (in case you have twrp installed).
After that you should receive several OTAs, i don't think it will update directly to EMUI 9.
In case you don't receive any OTA, try with Hisuite on PC.
P. S. Installing the official OTAs is the safest way.
Pretoriano80 said:
With EMUI 8 i think that flashing the stock ramdisk would be enough, but it won't hurt flashing the recovery_ramdisk too (in case you have twrp installed).
After that you should receive several OTAs, i don't think it will update directly to EMUI 9.
In case you don't receive any OTA, try with Hisuite on PC.
P. S. Installing the official OTAs is the safest way.
Click to expand...
Click to collapse
Hi Pretoriano80,
Thanks for your reply. cheers.
Pretoriano80 said:
With EMUI 8 i think that flashing the stock ramdisk would be enough, but it won't hurt flashing the recovery_ramdisk too (in case you have twrp installed).
After that you should receive several OTAs, i don't think it will update directly to EMUI 9.
In case you don't receive any OTA, try with Hisuite on PC.
P. S. Installing the official OTAs is the safest way.
Click to expand...
Click to collapse
Just to update my progress so far.
above procedure worked
all my date remain unchanged.
I lost my root.
however, I got EMUI 9 though OTA!. I kept getting OTA updates after flashed back stock RAMDISK.img and RECOVERY_RAMDIS.img. Here is the list of OTA update I have got.
OTA 8.0.0.143 1.08G, Google Security path Aug, Sept, Oct.
OTA 9.0.0.159 3.88G, ALP-L29 9.0.0.159(C636E2R1P12).
OTA 9.0.0.159(C636E2R1P12patch01), a small 3.8M update on NFC
OTA 9.1.0.300(C636E2R1P12), 3.83G EROFS and GPU turbo 3.0; Security path July 2019
OTA 9.1.0.321(C636E5R1P13), 4.01G Security path Oct 2019
PS. I am in Australia.
I heard the good news that EMUI 10 has been rolled out :fingers-crossed:. Let's just wait...
Related
Just checked and received a ota update on mine for the January security update and few fixes. Anyone else get it?
Just got it, it was fast update, rebooted and everything is okay
Quick question; I have the KIW-L24 model with TWRP and root by SuperSU, on a stock ROM though. I received the notification for the quick OTA update, but I'm worried it might brick my phone. Is it safe for me to download and uninstall it like the system suggests me to?
It sure took them long enough for this but I also got it updated only yesterday after reverting back to Stock via the UPDATE.APP in Dload folder method and pressing all 3 side buttons and letting it do it's thing.
It actually seems the Honor 5X runs better now but am not exactly sure what changed that yet.
Update.app got installed!
RE: I know this is old but...
GrimReaper24 said:
Just checked and received a ota update on mine for the January security update and few fixes. Anyone else get it?
Click to expand...
Click to collapse
Can you share the file, I am on l24 EMUI 4.0 MM 6.0.1 but no ota received.
I installed RROS on my honor 9 (STF-L09C432 from 3 UK) a few weeks ago, however due to many issues with it I decided to go back to EMUI. I eventually managed this using the rebrand guide, but just flashing without rebrand. I flashed B120 firmware as many people said this is the only rom where the torch and capacitive keys work if you are flashing from a non-EMUI OS.
The flash went perfectly and everything works, except I cannot OTA, software update is listing me as being on the latest firmware, but I know it isnt from firmware finder. If I try to upgrade via firmware finder, it all works till the phone restarts, then the recovery just throws an error, and says it can't be installed.
Fastboot says FRP and bootloader are unlocked onscreen however trying to flash anything, or run the rebrand script on a newer firmware just gets command not allowed. I suspect I need to try unlocking the bootloader again, however I don't want to factory reset, as while I can backup app data with huawei backup I preferably need as little downtime as possible
Although the phone passes safety net, I get a error message saying device can't be verified on boot, and huawei apps warn my my phone is insecure.
Does anyone have any other ideas to get it to update, as especially as oreo is rolling out I would like OTA to work?
killmeplease69 said:
I eventually managed this using the rebrand guide, but just flashing without rebrand. I flashed B120 firmware (...) If I try to upgrade via firmware finder, it all works till the phone restarts, then the recovery just throws an error, and says it can't be installed.
Click to expand...
Click to collapse
From C432B120 without ota working I've be able to update straight to 'B183 full ota approved by imei' with Firmware Finder.
I then normal updated with ota from C432B183 to B360.
Tough, it was just a downgrade I did to get back to B120, not a rebrand.
After the downgrade my phone and frp status were both locked.
I think I unlocked them again only once on B183 and thet stay that way after updated to B360. Flash and capacitives button are still working.
oslo83 said:
From C432B120 without ota working I've be able to update straight to 'B183 full ota approved by imei' with Firmware Finder.
I then normal updated with ota from C432B183 to B360.
Tough, it was just a downgrade I did to get back to B120, not a rebrand.
After the downgrade my phone and frp status were both locked.
I think I unlocked them again only once on B183 and thet stay that way after updated to B360. Flash and capacitives button are still working.
Click to expand...
Click to collapse
Thank you, I'm now running B183, I was trying to upgrade one by one by OTA in firmware finder because my internet is appallingly slow, but doing a full B183 flash worked. Just waiting for approved B360 now
I have a verizon model SM-G965U (Snapdragon). A few weeks ago, I was able to follow this upgrade sequence to get Pie:
G965USQU3BRI9 to G965USQU3BRJ5
G965USQU3BRJ5 to G965USQU3ZRJ8
So now I am currently stuck on G965USQU3ZRJ8. I am attempting to upgrade it to the latest Pie release which is G965USQU3CRKD (November 19 2008). However, when I try to update the firmware via download mode / adb sideload update.zip, it fails because it expects the BRJ5 model.
So, my only option it seems to sideload the update is to first downgrade back down to BRJ5. How can I downgrade this firmware, or would it be easier to flash the latest updates via odin another way? I am clueless, please help a disgruntled user stuck in the wrong version of Pie.
cmcjacob said:
I have a verizon model SM-G965U (Snapdragon). A few weeks ago, I was able to follow this upgrade sequence to get Pie:
G965USQU3BRI9 to G965USQU3BRJ5
G965USQU3BRJ5 to G965USQU3ZRJ8
So now I am currently stuck on G965USQU3ZRJ8. I am attempting to upgrade it to the latest Pie release which is G965USQU3CRKD (November 19 2008). However, when I try to update the firmware via download mode / adb sideload update.zip, it fails because it expects the BRJ5 model.
So, my only option it seems to sideload the update is to first downgrade back down to BRJ5. How can I downgrade this firmware, or would it be easier to flash the latest updates via odin another way? I am clueless, please help a disgruntled user stuck in the wrong version of Pie.
Click to expand...
Click to collapse
You may install the required Android Oreo build first, and then update using ADB sideload to Pie.
This may help you - Download Galaxy S9 Pie.
itskapil said:
You may install the required Android Oreo build first, and then update using ADB sideload to Pie.
This may help you - Download Galaxy S9 Pie.
Click to expand...
Click to collapse
That does not help at all. It simply repeats the steps I have already taken. If it were as easy as reversing these steps I would not post this topic. It was easy to upgrade, but downgrading is not as simple.
I already have Pie, I don't want vague upgrade instructions. I specifically want to go back to Oreo.
Use Odin to downgrade to Oreo. It's been covered many times in the beta thread. There should be a link in there for a lower version then you'll need to patch to BRJ5 and then the latest Beta.
https://forum.xda-developers.com/showpost.php?p=77970099&postcount=121
Hi !
I just got a brand new Mate 10 Pro, and managed to get a bootloader unlock code since I haven't updated the phone yet. I plan on unlocking it and then updating it to the latest version of Android.
I spent quite some time trying to figure out in which cases the device could brick, but since it seems that it can brick pretty easily I haven't found a complete answer.
Eventually, I would like to know if there a risk of bricking the device when updating with the official OTA after unlocking the bootloader ? I know that every bit of tinkering could potentially brick a device, but I have not found a similar case to this one. This is not totally related, but I also plan on rooting the device with Magisk once I successfully update it so feel free to tell me if there is something I should be aware of.
Thanks a lot XDA !
Unlocking
Pouni said:
Hi !
I just got a brand new Mate 10 Pro, and managed to get a bootloader unlock code since I haven't updated the phone yet. I plan on unlocking it and then updating it to the latest version of Android.
I spent quite some time trying to figure out in which cases the device could brick, but since it seems that it can brick pretty easily I haven't found a complete answer.
Eventually, I would like to know if there a risk of bricking the device when updating with the official OTA after unlocking the bootloader ? I know that every bit of tinkering could potentially brick a device, but I have not found a similar case to this one. This is not totally related, but I also plan on rooting the device with Magisk once I successfully update it so feel free to tell me if there is something I should be aware of.
Thanks a lot XDA !
Click to expand...
Click to collapse
Depends on what version of the Mate 10 you have, the US version (BLA-A09) supposedly bricks very easily. Since Huawei stopped providing unlock codes in July I'm wondering where you get a valid unlock code. Also, unlocking voids your warranty, as does any modifications to the software. Also be advised the once you root you will no longer be getting any updates OTA and will have to manually flash updated system images (drastically increasing you risk of bricking your device with every update)
revjamescarver said:
Depends on what version of the Mate 10 you have, the US version (BLA-A09) supposedly bricks very easily. Since Huawei stopped providing unlock codes in July I'm wondering where you get a valid unlock code. Also, unlocking voids your warranty, as does any modifications to the software. Also be advised the once you root you will no longer be getting any updates OTA and will have to manually flash updated system images (drastically increasing you risk of bricking your device with every update)
Click to expand...
Click to collapse
There are multiple sources for valid unlock codes, though all are paid. (OP probably used DC as he said he didn't update phone yet)
Rooting does not disable OTA. You will still receive them. Only problem is installing them... It should go fine if you flash back stock ramdisk and recovery_ramdisk, this will remove both Magisk and TWRP.
However, if you have modified any other partition it may not install anyway, in that case you can try going to menu in System Update and select Download latest full package. This would install FullOTA rather than regular OTA.
Or you can use HuRUpdater to install firmware using TWRP.
One way to hard-brick right now is to downgrade from a firmware using new bootloader to one using old bootloader. This will give you a black screen.
ante0 said:
There are multiple sources for valid unlock codes, though all are paid. (OP probably used DC as he said he didn't update phone yet)
Rooting does not disable OTA. You will still receive them. Only problem is installing them... It should go fine if you flash back stock ramdisk and recovery_ramdisk, this will remove both Magisk and TWRP.
However, if you have modified any other partition it may not install anyway, in that case you can try going to menu in System Update and select Download latest full package. This would install FullOTA rather than regular OTA.
Or you can use HuRUpdater to install firmware using TWRP.
One way to hard-brick right now is to downgrade from a firmware using new bootloader to one using old bootloader. This will give you a black screen.
Click to expand...
Click to collapse
The plan is to update to a stable and recent version using OTA (from BLA-L29 8.0.0.120(C432) to BLA-L29 8.0.0.157(C432)-FULL) and then root this version. Once I have root on this latest version, I plan on using it as long as the phone works, so updating to newer versions in the future and risking to brick the device shouldn't be a problem. I just want a functional root with a decent version of stock EMUI. Would updating from stock locked 120 to 157 and then unlocking + rooting be safe ? Thanks for the valuable info !
revjamescarver said:
Depends on what version of the Mate 10 you have, the US version (BLA-A09) supposedly bricks very easily. Since Huawei stopped providing unlock codes in July I'm wondering where you get a valid unlock code. Also, unlocking voids your warranty, as does any modifications to the software. Also be advised the once you root you will no longer be getting any updates OTA and will have to manually flash updated system images (drastically increasing you risk of bricking your device with every update)
Click to expand...
Click to collapse
I used DC Unlocker since my device was still on an old version, as Ante0 said ! I think that if I ever want to update, I'll remove root (getting back to stock) and then update with OTA. Thanks for the warning, I haven't rooted nor unlocked a device since 2 years and things have changed with the new methods (Magisk etc...).
Pouni said:
The plan is to update to a stable and recent version using OTA (from BLA-L29 8.0.0.120(C432) to BLA-L29 8.0.0.157(C432)-FULL) and then root this version. Once I have root on this latest version, I plan on using it as long as the phone works, so updating to newer versions in the future and risking to brick the device shouldn't be a problem. I just want a functional root with a decent version of stock EMUI. Would updating from stock locked 120 to 157 and then unlocking + rooting be safe ? Thanks for the valuable info !
Click to expand...
Click to collapse
Yes, that should be fine. You could just unlock bootloader right away and then update, if you wanted to.
Just be cautious, do not downgrade past B146 on C432 (if you ever plan to downgrade), that was the first build with the new bootloader so going to B145 or lower will result in a brick.
ante0 said:
Yes, that should be fine. You could just unlock bootloader right away and then update, if you wanted to.
Just be cautious, do not downgrade past B146 on C432 (if you ever plan to downgrade), that was the first build with the new bootloader so going to B145 or lower will result in a brick.
Click to expand...
Click to collapse
Thanks again for the valuable information. Now I'm debating whether I should unlock now or after the update I don't plan on downgrading, except if I have problems after updating and HAVE to downgrade. Last question if I may: I plan on using Magisk (latest version, I guess) to root once I update to BLA-L29 8.0.0.157(C432)-FULL. But I've seen that Magisk/TWRP doesn't necessarily work on the latest versions for some people when using the "basic" way of installing it, I tried to search for an up-to-date guide to rooting but didn't find anything, is the "old" way still good ?
Edit: When I said "basic/old" way of installing Magisk, I meant that it seems impossible to get it to work by installing TWRP and flashing Magisk through TWRP, but that it seems to work by finding a patched "ramdisk.img" with Magisk. Is the latest option a reliable way to get root on BLA-L29 157(C432), considering that I would not have TWRP to restore a backup if using this method ?
Edit 2: Tried the usual way (flashing Magisk zip through TWRP) and it seems to work ! Thank you !
Hello!
I have updated to pie .161 using the erecovery method via FF. Now if i use the erecovery normally on my phone it just say "Getting package info failed".
This isnt normalt right? There should always be a possibility to restore my phone via this erecovery right? Whats going on?
Have I messed up my phone now?
Cloudstrife said:
Have I messed up my phone now?
Click to expand...
Click to collapse
Erecovery can not mess up your phone.
Erecovery can only recover to the latest available firmware. I guess one reason why you used erecovery is because you have not received the official ota yet. Obviously it cannot recover to Emui 8 easily and emui9 is not officially pushed to your device yet. Result: erecovery cannot find a firmware to recover yet. Though it should be able to discover the 161 build later. It should be the point of time when you would have received the official ota if you had not upgraded yet manually.
The irony :laugh:
Cloudstrife said:
Hello!
I have updated to pie .161 using the erecovery method via FF. Now if i use the erecovery normally on my phone it just say "Getting package info failed".
This isnt normalt right? There should always be a possibility to restore my phone via this erecovery right? Whats going on?
Have I messed up my phone now?
Click to expand...
Click to collapse
The very same thing happened with me when i update my phone through FunkyHuawei. Erecovery stopped working. Then i roll back to Oreo and then install OTA update. Everhthing is working perfectly fine again. Always use the offcial method.
Same thing happened to me but I used the hicare method so it should be official ota but still broke kt
eyeb said:
Same thing happened to me but I used the hicare method so it should be official ota but still broke kt
Click to expand...
Click to collapse
You cannot break the phone by using either FF or erecovery (if your phone is (re)locked and you install approved firmware). That is a fact.
Erecovery is like official OTA. If the firmware is faulty not approved or otherwise not meant to be installed it will only download but fail to verify and install.
It has been reported by fh though that a factory reset on emui 9 beta builds stopped erecovery from working. That is why they came up with the hisuite method for downgrading/updating on emui9.
0alfred0 said:
You cannot break the phone by using either FF or erecovery (if your phone is (re)locked and you install approved firmware). That is a fact.
Erecovery is like official OTA. If the firmware is faulty not approved or otherwise not meant to be installed it will only download but fail to verify and install.
It has been reported by fh though that a factory reset on emui 9 beta builds stopped erecovery from working. That is why they came up with the hisuite method for downgrading/updating on emui9.
Click to expand...
Click to collapse
I downgraded using hisuite, :/ guess I'm back on android 8, but I don't mind so much since I didn't like android 9 that much. I didn't see any improvements overall so going back to 8 was something I thought about before. Now I have a reason to fix this erecovery thing
Found this interesting, after downgrade to 8, I kept the wireless projection function from Android 9 after I restored the backup.
Edit NVM it was the mirrorcasting