Hi all,
I have managed to install the following vanilla ROM on my Huawei P20 lite.
ColtOS-v5.4-10-Unofficial-20200103-arm64-ab-vanilla.img
So far it's going good but I've got 3 issues that I can't get info on with this ROM.
As far as I could see Android 10 OS has changed file systems. So my exFAT SD card won't work (needs to be formatted?). This card is only a couple of months old so it's not broken. It was working when I had EMUI 9.1 running yesterday. The OS says "there is an issue with your SD card". I go into the menu and it asks me to format said card. I have done this 4 times already but nothing changes. After the format the OS still gives the error that the SD card is faulty. Also when I connect my phone to my Win 10 PC only the Internal storage is picked up, not the SD card at all.
Then the other issue I have is getting TWRP to run. I have the following TWRP image that I tried to flash. When I do flash it and I reboot nothing happens and the phone boots to normal eRecovery.
TWRP image:
twrp-3.4.0-0-anne.img
Latly I have read read on the Colt OS XDA forum that one can not report errors of the OS if you are running Magisk. Is Magisk supported at all with this OS? Can I use SuperSU maybe instead of Magisk to get root working maybe?
For anyone who is going to respond, I say thank you
MayhemIam said:
Hi all,
I have managed to install the following vanilla ROM on my Huawei P20 lite.
ColtOS-v5.4-10-Unofficial-20200103-arm64-ab-vanilla.img
So far it's going good but I've got 3 issues that I can't get info on with this ROM.
As far as I could see Android 10 OS has changed file systems. So my exFAT SD card won't work (needs to be formatted?). This card is only a couple of months old so it's not broken. It was working when I had EMUI 9.1 running yesterday. The OS says "there is an issue with your SD card". I go into the menu and it asks me to format said card. I have done this 4 times already but nothing changes. After the format the OS still gives the error that the SD card is faulty. Also when I connect my phone to my Win 10 PC only the Internal storage is picked up, not the SD card at all.
Then the other issue I have is getting TWRP to run. I have the following TWRP image that I tried to flash. When I do flash it and I reboot nothing happens and the phone boots to normal eRecovery.
TWRP image:
twrp-3.4.0-0-anne.img
Latly I have read read on the Colt OS XDA forum that one can not report errors of the OS if you are running Magisk. Is Magisk supported at all with this OS? Can I use SuperSU maybe instead of Magisk to get root working maybe?
For anyone who is going to respond, I say thank you
Click to expand...
Click to collapse
Try Magisk-phh :
https://androidfilehost.com/?fid=4349826312261812699
You can try also SuperSu:
https://mega.nz/#!Zgc3VaBZ!K6_N35ex3HiNp6UAPq7nz_h3EDuuVQcLpYR0-kg56bQ
And TWRP by Askuccio:
https://mega.nz/#!EsdTgYqZ!2QX9wgAhA653Dp2MkDTLPHa3tmFdNqmC5CDDHB-7f5Y
-Alf- said:
Try Magisk-phh :
https://androidfilehost.com/?fid=4349826312261812699
You can try also SuperSu:
https://mega.nz/#!Zgc3VaBZ!K6_N35ex3HiNp6UAPq7nz_h3EDuuVQcLpYR0-kg56bQ
And TWRP by Askuccio:
https://mega.nz/#!EsdTgYqZ!2QX9wgAhA653Dp2MkDTLPHa3tmFdNqmC5CDDHB-7f5Y
Click to expand...
Click to collapse
Hi Alf man!
Thank you for the suggested links. I tried flashing the TWRP provided but nothing happens.
I have gone back to EMUI 9.1 and I can pickup the sd card. So I have no idea why it keeps telling me the sd card is corrupt Alf.
From what I have read, there are 2 partitions, one active the other not, for easier upgrading etc. So it seems I have to specify which partition to flash the provided TWRP? Is there a post on xda that I am missing in trying to install TWRP on Android 10?
MayhemIam said:
Hi Alf man!
Thank you for the suggested links. I tried flashing the TWRP provided but nothing happens.
I have gone back to EMUI 9.1 and I can pickup the sd card. So I have no idea why it keeps telling me the sd card is corrupt Alf.
From what I have read, there are 2 partitions, one active the other not, for easier upgrading etc. So it seems I have to specify which partition to flash the provided TWRP? Is there a post on xda that I am missing in trying to install TWRP on Android 10?
Click to expand...
Click to collapse
Well after flashing back to EMUI 9.1 I tried again, this time flashing TWRP first (twrp-3.4.0-0-anne.img) ....the other TWRP you suggested booted into TWRP but then it would reboot shortly after. Then I formated my sd card to fat32. After that I flashed Colt OS, then I reinstalled stock recovery, rebooted and ColtOS was working but it was installed on my SD card and not my main storage?
So now I am back on EMUI 9.1 but I can't access my storage on my PC. If I switch to "transfer file" only a cd-rom pops up in My Computer on Win 10. So I managed to screw up my entire storage :crying:
Well EMUI 9.1 is running though. My internal storage is encrypted
MayhemIam said:
Well after flashing back to EMUI 9.1 I tried again, this time flashing TWRP first (twrp-3.4.0-0-anne.img) ....the other TWRP you suggested booted into TWRP but then it would reboot shortly after. Then I formated my sd card to fat32. After that I flashed Colt OS, then I reinstalled stock recovery, rebooted and ColtOS was working but it was installed on my SD card and not my main storage?
So now I am back on EMUI 9.1 but I can't access my storage on my PC. If I switch to "transfer file" only a cd-rom pops up in My Computer on Win 10. So I managed to screw up my entire storage :crying:
Well EMUI 9.1 is running though. My internal storage is encrypted
Click to expand...
Click to collapse
Hi, just a few notes:
- As I wrote earlier, availability of custom ROMs for Kirin devices is scarce.
- Note that the "AB" in GSIs is not the same thing as physically having AB partitions .
"AB" in GSIs means SAR - system-as-root ( P20 lite which runs on EMUI 9.1).
A common misconception is that having Project Treble support and A/B partition support are related to one another, but that’s not actually the case. Having one does not imply the other. P20 Lite supports Project Treble AB, yet is an A-only device ( does not support Seamless Updates).
- if your phone is running Oreo, install a-only version.
-Alf- said:
Hi, just a few notes:
- I gave you in P.M. TWRP tips but you are still using 3.4.0-0 . Okay, it 's your choice.
- As I wrote earlier, availability of custom ROMs for Kirin devices is scarce. Some GSI Custom roms on Huawei devices require the .img file to be installed from fastboot :
fastboot erase userdata
fastboot flash system Colt-xxxx-xxxx.img
- Note that the "AB" moniker in GSIs is not the same thing as physically having AB partitions .
AB" in GSIs means system-as-root.
A common misconception is that having Project Treble support and A/B partition support are related to one another, but that’s not actually the case. Having one does not imply the other. P20 Lite supports Project Treble, yet is an A-only device ( does not support Seamless Updates).
- Install Service ROM and recover your phone (don't wait until it's too late ).
Click to expand...
Click to collapse
Ok thank you very much for your insight Alf.
I was having issues with that specific TWRP, that's why I tried a different one. But per your instructions, I will 100% go ahead and install Service ROM as suggested!
Thank you so very much Alf! Now I understand a bit more one the partitions.
-Alf- said:
Hi, just a few notes:
- I gave you in P.M. TWRP tips but you are still using 3.4.0-0 . Okay, it 's your choice.
- As I wrote earlier, availability of custom ROMs for Kirin devices is scarce. Some GSI Custom roms on Huawei devices require the .img file to be installed from fastboot :
fastboot erase userdata
fastboot flash system Colt-xxxx-xxxx.img
- Note that the "AB" moniker in GSIs is not the same thing as physically having AB partitions .
AB" in GSIs means system-as-root.
A common misconception is that having Project Treble support and A/B partition support are related to one another, but that’s not actually the case. Having one does not imply the other. P20 Lite supports Project Treble, yet is an A-only device ( does not support Seamless Updates).
- Install Service ROM and recover your phone (don't wait until it's too late ).
Click to expand...
Click to collapse
Hi Alf,
So I tried to follow your advice. I downloaded the following .zip file mentioned in your earlier post.
ANE-L01 8.0.0.136(C432) Firmware Android 8.0.0 EMUI 8.0.0 05014YXX.zip
I unzipped that file, and afterwards I tried flashing it first with the dload method, which only gave an error exclamation on eRecovery. I know I need to downgrade first from 9.1.0 and I have looked through XDA posts now but I haven't managed to do it. I have also tried via HiSuite and it gives me the option to downgrade, which I did, and then the phone restarted into TWRP recovery ( it seems I did not flash stock recovery before the HiSuite downgrade).
Ok...it seems I have to relock my bootloader before I try and downgrade to EMUI 8. If there are any steps I am missing please help.
Thank you!
MayhemIam said:
I know I need to downgrade first from 9.1.0 .
Click to expand...
Click to collapse
Where did you get this information ??? If you are running EMUI 9.1, you have to flash Service ROM for EMUI 9.1. Don't try downgrade to Oreo using Oreo Service ROM, it may brick your phone.
Download links (Service ROMs for C432 EMUI 9.1):
https://androidhost.ru/Xch
https://androidhost.ru/Xc1
https://androidhost.ru/Xar
It doesn't matter which one you choose.
-Alf- said:
Where did you get this information ??? If you are running EMUI 9.1, you have to flash Service ROM for EMUI 9.1. Don't try downgrade to Oreo using Oreo Service ROM, it may brick your phone.
Download links (Service ROMs for C432 EMUI 9.1):
https://androidhost.ru/Xch
https://androidhost.ru/Xc1
https://androidhost.ru/Xar
It doesn't matter which one you choose.
Click to expand...
Click to collapse
Ok thank you Alf, I will try with the provided info. Thank you! I was reading through XDA but couldn't find a answer. After I tried to do a downgrade via HiSuite and it failed as well as the dlaod method, I tried again to do a downgrade via HiSuite and the info in the app stated that my phone should not be unlocked.
Thank you for the help Alf!
Ok, I tried flashing via dload method as well as the service menu Alf. Didn't work. So I flashed it manually via fastboot. It installed the service ROM as you suggested I do.
The one I flashed was
Huawei P20 Lite ANE-LX1 ANE-L21 hw eu HLRCF Anne-L21 9.1.0.278(C432E6R1P7T8) Firmware EMUI9.1.0 05014YWN.zip
Current build number 9.1.0.278(C432E6R1P7)
What is the next step Alf? What makes a service ROM special? I tried looking on interwebs but couldn't find any info.
MayhemIam said:
Ok, I tried flashing via dload method as well as the service menu Alf. Didn't work. So I flashed it manually via fastboot. It installed the service ROM as you suggested I do.
The one I flashed was
Huawei P20 Lite ANE-LX1 ANE-L21 hw eu HLRCF Anne-L21 9.1.0.278(C432E6R1P7T8) Firmware EMUI9.1.0 05014YWN.zip
Current build number 9.1.0.278(C432E6R1P7)
What is the next step Alf? What makes a service ROM special? I tried looking on interwebs but couldn't find any info.
Click to expand...
Click to collapse
Ok, got a post on XDA, you need Service ROM to go back to Android 8.
The dload method, does it matter what the sd card's name is in the OS? Must it be sd_card?
OK the dload method does not work. I see that once you properly load a Service ROM, your device locks automatically and then one can proceed to flashing back to Oreo. I take it when the Service ROM is loaded correctly and one boot into fastboot mode the device should say "Phone Locked" "FRP Unlock"?
MayhemIam said:
Ok, got a post on XDA, you need Service ROM to go back to Android 8.
Click to expand...
Click to collapse
Dude it's you choice. As I said, downgrade to lower EMUI version via dload method may brick your phone. it's possible (and safely!) via HiSuite (with locked bootloader) only, or using HuRupdater 0.4 & TWRP .
Our conversation is useless, it's time to end it. Good Luck!
-Alf- said:
Dude it's you choice. As I said, downgrade to lower EMUI version via dload method may brick your phone. it's possible (and safely!) via HiSuite (with locked bootloader) only, or using HuRupdater 0.4 & TWRP .
Our conversation is useless, it's time to end it. Good Luck!
Click to expand...
Click to collapse
Thank you Alf. You were very helpful!
Related
Hello,
I've unlocked my bootloader and subsequently had installed TWRP (months ago).
Not long after, I decided to go back to stock for a while, and went back to CM a month ago.
However, I realized back then that I was loading into stock recovery even after taking the steps to install TWRP (http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190)
During these steps, there were no errors (fastboot/adb logs show all things were done successfully).
However, some funky quirk (that I don't remember) got me loaded with TWRP once, which gave me the window to install CM (I remember it involving having to be connected to the PC).
Now I'm trying to install a new CM build, but I can't get it loading TWRP.
I've downloaded the TWRP Manager App, which tells me that I have TWRP 3.0.0.0, but when I reboot to recovery, I am given the stock EMUI recovery.
Does anyone know what is happening in this case? Has anyone experienced a similar issue?
Thank you!
undesputed said:
Hello,
I've unlocked my bootloader and subsequently had installed TWRP (months ago).
Not long after, I decided to go back to stock for a while, and went back to CM a month ago.
However, I realized back then that I was loading into stock recovery even after taking the steps to install TWRP (http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190)
During these steps, there were no errors (fastboot/adb logs show all things were done successfully).
However, some funky quirk (that I don't remember) got me loaded with TWRP once, which gave me the window to install CM (I remember it involving having to be connected to the PC).
Now I'm trying to install a new CM build, but I can't get it loading TWRP.
I've downloaded the TWRP Manager App, which tells me that I have TWRP 3.0.0.0, but when I reboot to recovery, I am given the stock EMUI recovery.
Does anyone know what is happening in this case? Has anyone experienced a similar issue?
Thank you!
Click to expand...
Click to collapse
Reinstallt it try this TWRP http://www.mediafire.com/download/15g5i63gke9ddgp/kiwi_twrp_3-21_recovery.img its version 3.0.2.0 (Most recent)
The most recent is 5-14 (also based on v3.0.2.0 ).
TWRP 5.14
3-21 was built on March 21, and 5-14 on May 14.
mooms said:
The most recent is 5-14 (also based on v3.0.2.0 ).
TWRP 5.14
3-21 was built on March 21, and 5-14 on May 14.
Click to expand...
Click to collapse
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Arobase40 said:
Do you mean 3.0.2.0 is newer and supports more partitions than 5-14 ???
Click to expand...
Click to collapse
Their both 3.0.2.0 the one I just posted has more features
Sent from my SM-N920T using Tapatalk
clsA said:
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Click to expand...
Click to collapse
@clsA
frp is labeled as "UNLOCK" as oppsed to bootloader labeled as "UNLOCKED".
If it's just about removing my google account, will this be resolved the next time I do a factory reset?
Nevertheless, thank you so much for the command fastboot boot twrp.img, I realized that that was what I had used the last time.
I'm currently able to boot into TWRP this way. Awesome!
@clsA
Thanks for the link & infos.
Can you tell which features are added in this new TWRP ? name of the partitions ?
Thanks.
mooms said:
@clsA
Thanks for the link & infos.
Can you tell which features are added in this new TWRP ? name of the partitions ?
Thanks.
Click to expand...
Click to collapse
it would be much easier to just install it and test it for yourself
I did find a bug it would not backup to my OTG stick
clsA said:
it would be much easier to just install it and test it for yourself
I did find a bug it would not backup to my OTG stick
Click to expand...
Click to collapse
I don't use all the features, so i will maybe miss the changes.
Never used OTG to made a backup (I use ext_SD), I don't know if it works with other builds of TWRP.
mooms said:
I don't use all the features, so i will maybe miss the changes.
Never used OTG to made a backup (I use ext_SD), I don't know if it works with other builds of TWRP.
Click to expand...
Click to collapse
USB-OTG works flawlessly on the 5-14 version I was not able to use it with the newer one @yuweng posted in his guide
the screen shots show all the partitions it's able to work with
Arobase40 said:
I thought 3.0.2.0 was just an interim version between twrp_2-27 and twrp_5-14... ^^
Click to expand...
Click to collapse
your confusing TWRP versions with TWRP release dates
2-27 and 5-14 are release dates where as 3.0.2.0 is the version of TWRP not the date
the first version of TWRP for this device was actually 2.8.7.0 and was released on 2-16-2016
Same issue
Hey so I have the same exact issue umm did you ever resolve this problem becuSe I can't seem to crack it and it's a bit frustrating cuz by no means am I a pro but coming from using the OnePlus one the OnePlus 2 the OnePlus x and the Nexus 6 rooting them and restoring them after many failed attempts resulting in bricking my phone and even eventually unbrick them I do know a thing or two and I am stumped please help you are the only other person in this world other then my self that seems to be having this issue if you don't mind would you be so kind and email gmail me cuz I don't use or check this forum often thanks millerfamily805
clsA said:
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Click to expand...
Click to collapse
Can it be used with other honor devices?
Got my answer... Thanks...
Sent from my PLK-L01 using XDA Labs
It depend on the device
This thread applies to Huawei Mate 9 Pro only (model LON*, as M9Pro below). For Mate 9 (model MAH*) please go to the corresponding forum.
-----
Disclaimer:
I won't be responsible for bricked phone. Proceed with your own risk, make sure you know what you are doing.
This thread can be seen as a guide if your phone has exactly the same model and build version as mine. Otherwise please consider it as a description of my experiences for unlocking, flashing and rooting the phone.
SUPPORTED DEVICES:
LON-L29
LON-AL00
-----
As a start, this phone is great and I feel that it doesn’t need to be unlocked and rooted for a stable and long lasting daily use. However, unlock and root is almost a religion if you use Android phones
As a piece of info, big thanks to @raimondomartire, there is a thread for unlock, flash TWRP and root in the Mate 9 forum https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976, which is however according to my experience not totally applicable for the M9Pro anymore. There are also several other threads on the Mate 9 forum. Many things can be shared between both phones, but not always. Be careful about what you are doing!
-----
General info and attentions:
- My phone is M9Pro LON-AL00 (All net version from Chinese Mainland); LON-L29 (International version) should also work.
- This thread applies for build LON-AL00C00B213. Can be also applicable for similar builds, but I couldn’t test. Please report.
- None of the current builds of TWRP (up to 3.1.0) can decrypt data partition by default, which means you could only format the data partition in TWRP in order to access it in recovery (for backup to and install from internal storage etc.). But after formatting, you have to flash Huawei’s special stock data back to data partition (/data/hw_init), otherwise several functions of Huawei ROM won’t work. Refer to this (https://forum.xda-developers.com/showpost.php?p=71302827&postcount=627) or this (https://forum.xda-developers.com/showpost.php?p=72497328&postcount=204). Thanks to @gm007 and @ante0
- There are several root methods which handles encrypted or decrypted data partition. I didn’t format the data partition, i.e. data is still encrypted. If you want to format the data partition, please refer to this thread: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986. Thanks to @eddmecha
- If you need stock ROM, refer to useful links below. Use Huawei Update Extractor to extract the individual partitions from the ROM: https://forum.xda-developers.com/showthread.php?t=2433454
-----
Unlock bootloader:
There is enough info in the internet about unlocking M9Pro’s bootloader. Just a few points to mention:
- Generally, you can follow the steps in @raimondomartire thread (https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976). But unlike he describes in his thread, there is no OEM Unlock options in the developer options anymore. Just use ADB to unlock.
- FRP unlock is not required!
- Huawei enables now a 14-day limitation, where you can officially get the bootloader unlock code 14 days after you first activate your Huawei ID on your phone and have logged in using your Huawei ID 14 CONSECUTIVE days.
- To go around this limitation, you can use dc-unlocker to get the bootloader code immediately. Google yourself
-----
Flash TWRP:
- Still, you can follow the steps in @raimondomartire thread (https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976).
- The image from this thread is 3.0.3, which has some bugs built in, especially when flashing SuperSU.
- You could use TWRP 3.1.0-1 from https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617, but this one seems to have problem to be recognized as ADB device in recovery.
- There is a version 3.0.2 for Mate 9, which seems to have problem mounting USB-OTG.
- If your data partition is encrypted, you can only use ADB sideload or USB-OTG to install anything.
- If you want to do data wipe in TWRP, you have to flash Huawei’s special stock data back to data partition. See above general info and attentions.
-----
Root:
Firstly, thanks to @ante0 for explaining different flags in the root methods: https://forum.xda-developers.com/showpost.php?p=72504501&postcount=210. Some more discussions between us are also around this post.
I also tried several other root tools on the market (mobilego, vroot, YoRoot, OneClickRoot, iRoot etc.), NONE of them works.
As mentioned, there are different root methods around for unlocking M9Pro, depending on if you want to format your data partition. For me, I didn’t format, and SuperSU works for me. And the mate_9_pro_root.zip from @raimondomartire thread didn’t work for me.
I followed the steps below:
1. Get TWRP 3.1.0-1 (https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617)
2. Disable fingerprint ID (I think it’s probably optional, but have read somewhere that fingerprint stops working after flashing root).
3. Flash stock boot image for B213D (in download section). I think it’s optional too, but if you have tried other methods before, you can do this step to make sure your boot is stock and clean
4. Flash TWRP 3.1.0-1
5. Flash SuperSU-v2.79-MATE9-init.d_support_no_decrypt-signed.zip (in download section) via USB-OTG (in TWRP the device is not recognized as an ADB device, hence no “ADB sideload”). Thanks to @ante0 for building this zip!
6. Reboot – phone will reboot itself twice and SuperSU.apk will be installed automatically
7. You could flash back to 3.0.3, if you want the ADB sideload function.
-----
Download:
- TWRP 3.0.3-1: https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976
- TWRP 3.1.0-1: https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617
- SuperSU modified for M9Pro (thanks to @ante0): https://mega.nz/#!bR8D2Bab!bIgMLVmoll9R0GFqoFgkLxULrXlQ2710INt3TNbuI0c
- Boot image from B213D: https://mega.nz/#!LFlGTTZY!AaFq-_quM44YlK_Qdh9PgOjBE3Wtepmyz5OAuo_mabw
-----
Useful links:
- Stock firmware: http://hwmt.ru/oth/HWFF/info/view.php?find_model=lon
- Huawei Update (ROM) Extractor: https://forum.xda-developers.com/showthread.php?t=2433454
Enjoy your Mate!
Just some clarification: (eventhough you wrote it's for AL00C00B213, which I missed xD)
Flashing stock boot is only needed if you're already rooted.
Boot image B213D is only for AL00C00. If you have a different model/build, use the boot image for that specific build:
Download your stock firmware from hwmt.ru and Huawei Update Extractor. Extract update.app from your firmware zip.
Open update.app in Huawei Update Extractor. Rightclick on BOOT and click on Extract selected.
Flash the extracted boot.img using fastboot in download mode (fastboot flash boot boot.img).
OEM Unlocking is required to be enabled. It's just not there in the chinese version (AL00). So check if it's there first and enable if it is.
Hi guys. Not sure if this is the right place to ask but how do I get rid of that annoying "your device is unlocked and can't be trusted....etc " msg?
I have a mate 9 pro and I want to flash twrp and to root it. I did it for some one plus, xiaomi, samsung so I have some experience. reading xda posts about the case of M9pro I understood that is not a simple path and I dont want to hard brick the phone. what precautions should I take?
attached phone config
thank you in advance
ante0 said:
Just some clarification: (eventhough you wrote it's for AL00C00B213, which I missed xD)
Flashing stock boot is only needed if you're already rooted.
Boot image B213D is only for AL00C00. If you have a different model/build, use the boot image for that specific build:
Download your stock firmware from hwmt.ru and Huawei Update Extractor. Extract update.app from your firmware zip.
Open update.app in Huawei Update Extractor. Rightclick on BOOT and click on Extract selected.
Flash the extracted boot.img using fastboot in download mode (fastboot flash boot boot.img).
OEM Unlocking is required to be enabled. It's just not there in the chinese version (AL00). So check if it's there first and enable if it is.
Click to expand...
Click to collapse
hwmt. ru is unavailable
mcn1970 said:
hwmt. ru is unavailable
Click to expand...
Click to collapse
http://hwmt.ru/hwmtsite/firmware-database/
working fine for me.
Edit: I should probably have posted the full link in my previous post. Sorry.
ante0 said:
http://hwmt.ru/hwmtsite/firmware-database/
working fine for me.
Edit: I should probably have posted the full link in my previous post. Sorry.
Click to expand...
Click to collapse
is it all procedures safe? no risk of hard brick?
ante0 said:
Just some clarification: (eventhough you wrote it's for AL00C00B213, which I missed xD)
Flashing stock boot is only needed if you're already rooted.
Boot image B213D is only for AL00C00. If you have a different model/build, use the boot image for that specific build:
Download your stock firmware from hwmt.ru and Huawei Update Extractor. Extract update.app from your firmware zip.
Open update.app in Huawei Update Extractor. Rightclick on BOOT and click on Extract selected.
Flash the extracted boot.img using fastboot in download mode (fastboot flash boot boot.img).
OEM Unlocking is required to be enabled. It's just not there in the chinese version (AL00). So check if it's there first and enable if it is.
Click to expand...
Click to collapse
i unlocked the bootloader and flashed recovery but my OTG stick is not recognized and cannot be mounted. also while in recovery the phone is not seen on PC.
i tried with both recoveries above.
ADB sideload doesnt work...keeps saying starting ADB sideloading features...in TWRP sdcard content is a bunch of files with weird names...
therefore how can I root the phone?
someone please help me!!
mcn1970 said:
i unlocked the bootloader and flashed recovery but my OTG stick is not recognized and cannot be mounted. also while in recovery the phone is not seen on PC.
i tried with both recoveries above.
ADB sideload doesnt work...keeps saying starting ADB sideloading features...in TWRP sdcard content is a bunch of files with weird names...
therefore how can I root the phone?
someone please help me!!
Click to expand...
Click to collapse
edit: solved it
any OTA after?
hi guys. You may or may not find this interesting. I certainly did. I'll post this in the mate 9 pro forum as well but i just thought i could get some ideas from as many of guys as possible seeying that theres a lot more posts here for mate 9 in general.
I have chinese version mate 9 pro that has been rebranded from AL00 to LON Spcseas and rooted. Build number b228. Anyway i recently saw in FF the new b229 so i downloaded all three files which had longer file names than usuall by the way. In twrp, the only file that was visable was the update.zip. So i renamed the hw and public zip files to what they would usually be named. Wiped data, and flashed all three files. Then reflashed supersu.
This is the interesting bit ( i think ). My imei numbers have changed, before flashing, the first imei number ended in 7 - now it ends with 4, the second imei number ended in 9 and now it ends with 7. Also, i now have a MEID number visable which was not there before and a section called android security patch level. Oddly enough im not getting any issues out of play store, im on play store right now and not a single problem regarding authentication. The build number is the same as well. As far as functionality goes, everything seems to be tip top, in fact everything seems to be working better, even unofficial exposed is working well. Only one thing isn't working properly. In phone manager there was a feature in the battery section that darkens the interface for everything to save power and prolong battery. That doesn't seem to be working anymore. In App - Permissions, the permissions is greyed out and it says no permissions requested.. Any thoughts or explenations guys??
Trying to flash another orginal stock rom
I bought a Mate 9 Pro, China Version (LON-AL00C00) want to install Mate 9 Pro, Asia Version (LON-L29C636) software on it. All explanations about Mate 9 Pro is for models which have SD Card. My Mate 9 Pro with dual sims and not containing a SD Card enrty.
I succesfully unlocked the bootloader, installed TWRP but couldn't flash LON-L29C636 stock software. Because TWRP don't see update.zip file. Not only update.zip, any files I downloaded or copied before. When I put a OGT TWRP suddenly exits and phone restarts.:crying:
As you see I can't flash a zip file and ofcourse superuser zip file to root as well. I'm stuck in this triangle. Please give me a hand guys.
I can't root my phone. Because I can't view and locate any file of my phone. When I plug a ogt cable twrp exits and phone restarts. 6GB-128GB Dual Sim version
---------- Post added at 11:48 AM ---------- Previous post was at 11:47 AM ----------
Seems I am the only one who is looking for something about Mate 9 Pro
CrisperNeO said:
This thread applies to Huawei Mate 9 Pro only (model LON*, as M9Pro below). For Mate 9 (model MAH*) please go to the corresponding forum.
-----
Disclaimer:
I won't be responsible for bricked phone. Proceed with your own risk, make sure you know what you are doing.
This thread can be seen as a guide if your phone has exactly the same model and build version as mine. Otherwise please consider it as a description of my experiences for unlocking, flashing and rooting the phone.
SUPPORTED DEVICES:
LON-L29
LON-AL00
-----
As a start, this phone is great and I feel that it doesn’t need to be unlocked and rooted for a stable and long lasting daily use. However, unlock and root is almost a religion if you use Android phones
As a piece of info, big thanks to @raimondomartire, there is a thread for unlock, flash TWRP and root in the Mate 9 forum https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976, which is however according to my experience not totally applicable for the M9Pro anymore. There are also several other threads on the Mate 9 forum. Many things can be shared between both phones, but not always. Be careful about what you are doing!
-----
General info and attentions:
-My phone is M9Pro LON-AL00 (All net version from Chinese Mainland); LON-L29 (International version) should also work.
-This thread applies for build LON-AL00C00B213. Can be also applicable for similar builds, but I couldn’t test. Please report.
-None of the current builds of TWRP (up to 3.1.0) can decrypt data partition by default, which means you could only format the data partition in TWRP in order to access it in recovery (for backup to and install from internal storage etc.). But after formatting, you have to flash Huawei’s special stock data back to data partition (/data/hw_init), otherwise several functions of Huawei ROM won’t work. Refer to this (https://forum.xda-developers.com/showpost.php?p=71302827&postcount=627) or this (https://forum.xda-developers.com/showpost.php?p=72497328&postcount=204). Thanks to @gm007 and @ante0
-There are several root methods which handles encrypted or decrypted data partition. I didn’t format the data partition, i.e. data is still encrypted. If you want to format the data partition, please refer to this thread: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986. Thanks to @eddmecha
-If you need stock ROM, refer to useful links below. Use Huawei Update Extractor to extract the individual partitions from the ROM: https://forum.xda-developers.com/showthread.php?t=2433454
-----
Unlock bootloader:
There is enough info in the internet about unlocking M9Pro’s bootloader. Just a few points to mention:
-Generally, you can follow the steps in @raimondomartire thread (https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976). But unlike he describes in his thread, there is no OEM Unlock options in the developer options anymore. Just use ADB to unlock.
-FRP unlock is not required!
-Huawei enables now a 14-day limitation, where you can officially get the bootloader unlock code 14 days after you first activate your Huawei ID on your phone and have logged in using your Huawei ID 14 CONSECUTIVE days.
-To go around this limitation, you can use dc-unlocker to get the bootloader code immediately. Google yourself
-----
Flash TWRP:
-Still, you can follow the steps in @raimondomartire thread (https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976).
-The image from this thread is 3.0.3, which has some bugs built in, especially when flashing SuperSU.
-You could use TWRP 3.1.0-1 from https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617, but this one seems to have problem to be recognized as ADB device in recovery.
-There is a version 3.0.2 for Mate 9, which seems to have problem mounting USB-OTG.
-If your data partition is encrypted, you can only use ADB sideload or USB-OTG to install anything.
-If you want to do data wipe in TWRP, you have to flash Huawei’s special stock data back to data partition. See above general info and attentions.
-----
Root:
Firstly, thanks to @ante0 for explaining different flags in the root methods: https://forum.xda-developers.com/showpost.php?p=72504501&postcount=210. Some more discussions between us are also around this post.
I also tried several other root tools on the market (mobilego, vroot, YoRoot, OneClickRoot, iRoot etc.), NONE of them works.
As mentioned, there are different root methods around for unlocking M9Pro, depending on if you want to format your data partition. For me, I didn’t format, and SuperSU works for me. And the mate_9_pro_root.zip from @raimondomartire thread didn’t work for me.
I followed the steps below:
1.Get TWRP 3.1.0-1 (https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617)
2.Disable fingerprint ID (I think it’s probably optional, but have read somewhere that fingerprint stops working after flashing root).
3.Flash stock boot image for B213D (in download section). I think it’s optional too, but if you have tried other methods before, you can do this step to make sure your boot is stock and clean
4.Flash TWRP 3.1.0-1
5.Flash SuperSU-v2.79-MATE9-init.d_support_no_decrypt-signed.zip (in download section) via USB-OTG (in TWRP the device is not recognized as an ADB device, hence no “ADB sideload”). Thanks to @ante0 for building this zip!
6.Reboot – phone will reboot itself twice and SuperSU.apk will be installed automatically
7.You could flash back to 3.0.3, if you want the ADB sideload function.
-----
Download:
-TWRP 3.0.3-1: https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976
-TWRP 3.1.0-1: https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617
-SuperSU modified for M9Pro (thanks to @ante0): https://mega.nz/#!bR8D2Bab!bIgMLVmoll9R0GFqoFgkLxULrXlQ2710INt3TNbuI0c
-Boot image from B213D: https://mega.nz/#!LFlGTTZY!AaFq-_quM44YlK_Qdh9PgOjBE3Wtepmyz5OAuo_mabw
-----
Useful links:
-Stock firmware: http://hwmt.ru/oth/HWFF/info/view.php?find_model=lon
-Huawei Update (ROM) Extractor: https://forum.xda-developers.com/showthread.php?t=2433454
Enjoy your Mate!
Click to expand...
Click to collapse
I unlocked bootloader but couldn't root. Anyway I wanted to rebrand my phone to Asia version. Now I'm done but not successful because there is no Google,frp locked, and version is test one.
I can't install twrp because frp lock don't allow it. Also twrp can't read 128 GB internal memory, so I needed to install from pc.
Is there anyway to resolve and install stock Oreo version to my Mate 9 Pro or do you suggest me to resolve it via paid services?
PRA-LX1 cihazımdan Tapatalk kullanılarak gönderildi
livevalue said:
I unlocked bootloader but couldn't root. Anyway I wanted to rebrand my phone to Asia version. Now I'm done but not successful because there is no Google,frp locked, and version is test one.
I can't install twrp because frp lock don't allow it. Also twrp can't read 128 GB internal memory, so I needed to install from pc.
Is there anyway to resolve and install stock Oreo version to my Mate 9 Pro or do you suggest me to resolve it via paid services?
PRA-LX1 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
I've installed Oreo to Mate 9 Pro. If you have 128GB edition don't try to install anything from internal storage. That's it.
PRA-LX1 cihazımdan Tapatalk kullanılarak gönderildi
Hi guys, for re-branding there are threads in general Mate 9 forum. I didnt do it and am not planning to do it either...
CrisperNeO said:
Hi guys, for re-branding there are threads in general Mate 9 forum. I didnt do it and am not planning to do it either...
Click to expand...
Click to collapse
Rebranding is easy with HWOTA system if you will keep your phone EMUI 5.0 Nougat. And there is no risk if you make everything clearly.
PRA-LX1 cihazımdan Tapatalk kullanılarak gönderildi
never used Huawei before have a couple of questions
1. Is there anyway to get back to full stock with relock bootaloder in case the device need to go to service center?
(assume unlock bootloader with dc-unlocker not huawei id one)
2. From question 1 what do i need to do or backup before root?
thnak you so much!
44alphabeT said:
never used Huawei before have a couple of questions
1. Is there anyway to get back to full stock with relock bootaloder in case the device need to go to service center?
(assume unlock bootloader with dc-unlocker not huawei id one)
2. From question 1 what do i need to do or backup before root?
thnak you so much!
Click to expand...
Click to collapse
Yes you can always flash stock ROM as factory out, if you are not in Oreo.
And you can root it. It's your own protection to have a backup. I suggest you have, anyway it's up to you. You can loose all your data after root.
Hi, yersterday I used TWRP trying to install a newer firmware and I wiped system partition and now it does not boot because it doesn't have an OS. I was on EMUI 8 (636) trying to update the firmware.
Is there any way to flash a firmware via TWRP or Fastboot on EMUI 8 (i know partition names change on Oreo).
Thanks!
I just bought a Huawei Mate SE which is a newer phone that looks like the Honor 7x. I've noticed whenever I search for Huawei Mate Se custom roms, recoveries, and even stock roms I only find Mate 9 stuff and find my self desperate with no support of root, and anything else. I found an article called "How to : Huawei Mate SE Root & TWRP Recovery" , and I successfully unlocked the bootloader, and I successfully installed twrp. The text on the bottom I didn't see which said to install the dm-verity thing. I ran into the problem where there were all these folders were displaying weird text in the main partitions, so instead of installing the version they told me, which was the no-verity-opt-encrypt-4.1.zip, I installed the latest which was the no-verity-opt-encrypt-6.0.zip version, which soft bricked. So I thought I could fix this by installing a custom ROM. But there were none, so I tried to install cm13 honor 7x rom and It didn't work. I tried installing the correct version after the rom. So even now if I tried to revert the old boot img it still wouldn't work because of the rom. However, since my bootloader is unlocked there is definitely a way I can fix all this. But the problem is their is not any Huawei Mate SE roms anywhere. I need a stock rom for my phone (possisbly a custom rom), or some fix. I can access my recovery, and the bootloader, but not anything else. My model is the BND-L34, pls help.
I did the same thing. Got it working
Put this in twrp back up folder on external SD card. Restored both files then factory reset in twrp. It worked for me every thing works. unzipped with Windows pc
Can't post links. Post [EMUI 5.1] OTA Firmwares and Unbrick Phone method. In Huawei 7x thread post#139 by AlexxC might be easter to search his posts. I have mate se in us on tmo/MetroPCS I flashed the correct 4.1 and still got soft brick. That article cost me couple hours. rooted with honor 7x method. Guess it really is the same phone with extra gig of ram. To AlexxC thanks, you the man
bradass402 said:
Put this in twrp back up folder on external SD card. Restored both files then factory reset in twrp. It worked for me every thing works. unzipped with Windows pc
Can't post links. Post [EMUI 5.1] OTA Firmwares and Unbrick Phone method. In Huawei 7x thread post#139 by AlexxC might be easter to search his posts. I have mate se in us on tmo/MetroPCS I flashed the correct 4.1 and still got soft brick. That article cost me couple hours. rooted with honor 7x method. Guess it really is the same phone with extra gig of ram. To AlexxC thanks, you the man
Click to expand...
Click to collapse
I tried the manual method of unbricking with multi touch and the phone booted, but it is a black screen, and I only see the home, back and tabs buttons. So after i figured out to use the backup that you sent me and it still wouldn't boot.
Are you getting errors in twrp restore you have to mount the partitions that your restoring boot system data etc
bradass402 said:
Are you getting errors in twrp restore you have to mount the partitions that your restoring boot system data etc
Click to expand...
Click to collapse
i did what you said in the pm, and got the cust.img flashed, but now it bootloops to the recovery
tomjfmu said:
i did what you said in the pm, and got the cust.img flashed, but now it bootloops to the recovery
Click to expand...
Click to collapse
Why dont you boot into huawei eRecovery? It downloads the firmware and recovery and recovers your phone.
Mate 10. So, I tried to install the latest EMUI version using HuRUpdater - bad idea. Now, my phone will not boot. I can enter EMUI Recovery Mode but when I try to receive download package, it says it can't be retrieved. I can also enter Fastboot Mode but the problem with that is that under Device Manager, it only gets recognized as, "Android Bootloader Interface."
Please, any help would be greatly appreciated.
edit: So, fastboot DOES work. What files from what version do I flash to return to stock recovery? I don't even know if Pie was actually written to the device or not before the device rebooted and wouldn't boot.
edit again: I have just successfully installed TWRP via fastboot but it hangs at startup screen - is this because it's not compatible with Pi?
So I've tried flashing ramdisk_recovery.img, kernel.img and system.img from the Pi version but I still can't factory reset the phone. It boots back to the white screen with the android dude and says, "Please update system again."
Any help would be appreciated...
Using Multi-Tool, it detects my device in Fastboot mode as still 8.0.0.143. So, I'm trying to flash System, Ramdisk, Cust, Recovery_Ramdisk and Userdata......all succeed, except one - Ramdisk.img. When I manually try to flash Ramdisk.img in command prompt, it also fails, "FAILED (remote: partition length get error)". In Multi-tool, the error is, "the size or path does not match the file system markup."
Please, does anyone have any other suggestions? I've been at this for nearly 12 hours straight.
I assume u have unlocked bootloader and frb unlocked too if both yes u can search in xda for zip file beta downy 0.4
It will help you to downgrade emui 9 to. Emui 8
If u have unlocked bootloader only I guess u need funky huawei to restore ur devise
I hope I did helped u
Thanks for the reply.
My bootloader is unlocked but how do I know if I have unlocked FRP?
And downy tool requires ADB but I can only access Fastboot.
edit: I just checked and my FRP is also unlocked. What now?
Tried Funky Huawei just now, no go. Still get package can't be received error in ERecovery after following all of the instructions. Have emailed them as that's what they suggest doing if it didn't work.
Not sure what else to try to be honest. How the hell does updating my phone from 8.0.0.143 to 9.0.0.159 with HuRUpdate brick my phone? Ffs.
essen212 said:
Tried Funky Huawei just now, no go. Still get package can't be received error in ERecovery after following all of the instructions. Have emailed them as that's what they suggest doing if it didn't work.
Not sure what else to try to be honest. How the hell does updating my phone from 8.0.0.143 to 9.0.0.159 with HuRUpdate brick my phone? Ffs.
Click to expand...
Click to collapse
Well, it happened because HuRUpdater it's not supported on EMUI 9.0.
Ramdisk fails to flash because even if in fastboot your device is showing as 8.0.0.143, it has EMUI 9's partition layout, so no more ramdisk partition.
Try flashing a firmware with the DLOAD method (search on androidhost.ru for a firmware designed for your device/cust).
Pretoriano80 said:
Well, it happened because HuRUpdater it's not supported on EMUI 9.0.
Ramdisk fails to flash because even if in fastboot your device is showing as 8.0.0.143, it has EMUI 9's partition layout, so no more ramdisk partition.
Try flashing a firmware with the DLOAD method (search on androidhost.ru for a firmware designed for your device/cust).
Click to expand...
Click to collapse
Damn. Well, that makes perfect sense. A question - do I flash the 9.0.0 version or 8.0.0.143 version?
essen212 said:
Damn. Well, that makes perfect sense. A question - do I flash the 9.0.0 version or 8.0.0.143 version?
Click to expand...
Click to collapse
Try with EMUI 9 first, then, if it fails, try Oreo. The most important part is finding a DLOAD firmware for your cust/region.
I've fixed it!
Funky emailed me back and I ended up using a different method on their site which worked like a charm. I couldn't recommend them enough.
Hi, good to hear you got it sorted! Would you mind sharing the details on what you had to do differently with FHC? I'm in the same boat here with a mate 10 pro that died on emui9 and I'm not sure if I should go the FHC way or not...
Thx - David
My phone just got the android 9 update, I already had installed root with twrp on my device with android 8.0
So when I tried to re-root my phone I needed to reinstall the TWRP but it couldn't decrypt the data
I tried all of the posible solutions to this but nothing
I think that is the TWRP version that can't decrypt data in android 9.0
But in the web isn't any version that support the Mi 8 LIte with Android 9.0
Do I need to wait until someone update the TWRP version or what can I do?
Thanks in advance
Sebaxe07 said:
My phone just got the android 9 update, I already had installed root with twrp on my device with android 8.0
So when I tried to re-root my phone I needed to reinstall the TWRP but it couldn't decrypt the data
I tried all of the posible solutions to this but nothing
I think that is the TWRP version that can't decrypt data in android 9.0
But in the web isn't any version that support the Mi 8 LIte with Android 9.0
Do I need to wait until someone update the TWRP version or what can I do?
Thanks in advance
Click to expand...
Click to collapse
Formatting data have to decrypt it, you have to be sure that TWRP is able to mount data partition.
SubwayChamp said:
Formatting data have to decrypt it, you have to be sure that TWRP is able to mount data partition.
Click to expand...
Click to collapse
So I need to erease all of my phone data to be able to use twrp? But why it didn't have this problem the first time?
Sebaxe07 said:
So I need to erease all of my phone data to be able to use twrp? But why it didn't have this problem the first time?
Click to expand...
Click to collapse
You are upgrading now; for this you need to decrypt it for first time and probably every time that you switch from a miui to an AOSP rom. Be sure that your data partition is mounted and I guess you can´t see the files under TWRP. Try first with this zip https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Stock Miui re-encrypt data on first boot after factory reset, so you need to flash Universal DM-Verity
I also need TWRP for pie.
Try this recovery, It has more features than TWRP https://sourceforge.net/projects/orangefox/files/test_builds/OrangeFox-R9.0-1-platina.zip/download
SubwayChamp said:
Try this recovery, It has more features than TWRP https://sourceforge.net/projects/orangefox/files/test_builds/OrangeFox-R9.0-1-platina.zip/download
Click to expand...
Click to collapse
Thanks
SubwayChamp said:
Try this recovery, It has more features than TWRP https://sourceforge.net/projects/orangefox/files/test_builds/OrangeFox-R9.0-1-platina.zip/download
Click to expand...
Click to collapse
Would you happen to know if opengapps aroma works with this recovery. I have tried 3 or 4 other revoveries and once options are selected and install starts recovery reboots. After that I have to hold power to force reboot because no matter what reboot option I choose it just goes back to recovery.
cidxtc said:
Would you happen to know if opengapps aroma works with this recovery. I have tried 3 or 4 other revoveries and once options are selected and install starts recovery reboots. After that I have to hold power to force reboot because no matter what reboot option I choose it just goes back to recovery.
Click to expand...
Click to collapse
Unfortunately I can't tell you for sure cause left 3 days to unlock my bootloader but I used this recovery in two Xiaomi devices (R5Plus and Mi Max) and was the best I ever tried, never had issue flashing Aroma zips.
Be sure that once finished the installation Reboot box in Aroma be unticked
SubwayChamp said:
Unfortunately I can't tell you for sure cause left 3 days to unlock my bootloader but I used this recovery in two Xiaomi devices (R5Plus and Mi Max) and was the best I ever tried, never had issue flashing Aroma zips.
Be sure that once finished the installation Reboot box in Aroma be unticked
Click to expand...
Click to collapse
Never had an issue with redmi note 4x and aroma either. The reboot box does not make a difference because the install never happens. I will download and try.
Sebaxe07 said:
I think that is the TWRP version that can't decrypt data in android 9.0
But in the web isn't any version that support the Mi 8 LIte with Android 9.0
Click to expand...
Click to collapse
If you are using the wzsx150 3.2.3 twrp found under the ROM/recovery section, versions 0121 and 0212 are both supposed to be for Android 9. I haven't tried myself though, as I am still on 8.
I can confirm version 0212 does indeed decrypt data partition, making it mountable it inside TWRP. Of course phone's now running on official Android 9 MIUI 10, updated on Wednesday.
So heads up for anyone trying to use open gapps aroma installer. No recovery will install it. Tried batik, orange fox, perp, and wzsx150 twrp and all do the same. After all the selections when the actual installation starts the device reboots (installs nothing but does save setting options) back to recovery. All reboot options (system, fastboot, etc) all reboot back to recovery only holding power button will allow device to boot into system.
MetallicGR said:
I can confirm version 0212 does indeed decrypt data partition, making it mountable it inside TWRP. Of course phone's now running on official Android 9 MIUI 10, updated on Wednesday.
Click to expand...
Click to collapse
I am using wzsx150 3.2.3-1003 and it does not decrypt data, even with proper password.. Where can I find 0212. I cannot find it in this forum. ..only the bad one I am using.
EDIT: Nevermind. Found it.
MetallicGR said:
I can confirm version 0212 does indeed decrypt data partition, making it mountable it inside TWRP. Of course phone's now running on official Android 9 MIUI 10, updated on Wednesday.
Click to expand...
Click to collapse
Any idea why is 0212 half the size of 0121, and the others for that matter (28MB vs 60MB).
I believe it's somehow compressed. If you open these files with something like 7zip you'll see the size is very close between the two.
MetallicGR said:
I believe it's somehow compressed. If you open these files with something like 7zip you'll see the size is very close between the two.
Click to expand...
Click to collapse
Oh okay. That would make sense.
lexridge said:
I am using wzsx150 3.2.3-1003 and it does not decrypt data, even with proper password.. Where can I find 0212. I cannot find it in this forum. ..only the bad one I am using.
EDIT: Nevermind. Found it.
Click to expand...
Click to collapse
Can yo share the 0212 img to Pie I'm stll in Oreo and the Pie update notification is a little annoying so I want to update but I haven't found the twpr 0212 for mi 8 lite.
Here you go. https://forum.xda-developers.com/showpost.php?p=78876979&postcount=46
Another member replied to your other thread as well.