Related
Hi.
So the latest Cyanogenmod (honestly every update out of the CM update that came out on 9th Oct) builds do not work for my device. Whenever I try to boot up the device, the device just gets stuck on the bootup screen, that is the screen where you see the OnePlus logo and there's text in the lower part that says "Powered by Android", except that there is no "powered by Android" text seen.
What should I do in order to get things working?
Sorry to post this in the general thread, I am not yet high enough that I can post in the Android Development Thread.
The latest 2 builds are only compatible with the new Marshmallow Bootloader, AFAIK.
In order to get them working, I would recommend you to flash the full OOS 3.1.3 zip file.
There is the alternative to flash a zip file to get the latest booloader and radio firmware. I haven't tested it, that's why I'm not telling you to do so.
Loureiro said:
The latest 2 builds are only compatible with the new Marshmallow Bootloader, AFAIK.
In order to get them working, I would recommend you to flash the full OOS 3.1.3 zip file.
There is the alternative to flash a zip file to get the latest booloader and radio firmware. I haven't tested it, that's why I'm not telling you to do so.
Click to expand...
Click to collapse
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
aamodjoshi23 said:
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
Click to expand...
Click to collapse
Yes. Just like that. But OOS 3.X.X has new Bootloader. So new TWRP should be flashed.
New TWRP : http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
And flash it as usual.
sundhar88 said:
Yes. Just like that. But OOS 3.X.X has new Bootloader. So new TWRP should be flashed.
New TWRP : http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
And flash it as usual.
Click to expand...
Click to collapse
Alright thanks! If I face any problems I'll post again!
aamodjoshi23 said:
Alright thanks! If I face any problems I'll post again!
Click to expand...
Click to collapse
Wait dude! If you're on OOS 2.X.X based ROM and TWRP, then you should flash official OxygenOS Recovery and then flash the Marshmallow ROM. And now you can flash TWRP root or flash CM13 or xposed and whatever...
Refer : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
sundhar88 said:
Wait dude! If you're on OOS 2.X.X based ROM and TWRP, then you should flash official OxygenOS Recovery and then flash the Marshmallow ROM. And now you can flash TWRP root or flash CM13 or xposed and whatever...
Refer : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
Yup. You need to first flash the OOS recovery and then you need to flash the OOS 3.1.3 and then again the TWRP and then you need to flash whichever ROM you want to... Been there, done that. Real pain...
aamodjoshi23 said:
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
Click to expand...
Click to collapse
That's right.
If you don't want to do a complete wipe, you can try this method: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Loureiro said:
That's right.
If you don't want to do a complete wipe, you can try this method: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
You're a lifesaver dude! Thanks for the link!!
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Cretandus said:
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
No need for you to do this.
Just follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917 and then flash latest CM13 nightly.
Adesh15 said:
No need for you to do this.
Just follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917 and then flash latest CM13 nightly.
Click to expand...
Click to collapse
Okay, thanks! I'll try this and let you know the outcome. I have to install CM13 before rebooting out of TWRP, right? "Older roms won't boot" meaning my OOS 2.2.2 won't boot. Just checking...
Cretandus said:
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
Install opx_recovery, flash 3.1.3 from recovery. After installed you can fastboot flash Blu sparks latest or Nichets twrp done.
Cretandus said:
Okay, thanks! I'll try this and let you know the outcome. I have to install CM13 before rebooting out of TWRP, right? "Older roms won't boot" meaning my OOS 2.2.2 won't boot. Just checking...
Click to expand...
Click to collapse
After flashing the new TWRP for new BL you should reboot to recovery from reboot tab in TWRP.
Then wipe System ,Data and Cache and then flash CM13
Cretandus said:
Hi all,
I�¢??m having the exact same problem. I�¢??ve searched several forums, and have seen different solutions, but I�¢??m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don�¢??t want to make any mistakes. I�¢??m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I�¢??m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
Hi there.
I tried the way these folks suggested, by updating the BL using the zip file and flashing the updated TWRP recovery, and it worked!
What I did was, first of all, I took the backup using Titanium Backup and took a nandroid backup. Then I already had downloaded the files required, that is the BL zip file, the TWRP recovery, and the latest CM 13.0 build. Then I went to recovery > install and then located the BL and flashed it. Then I tried to flash the TWRP recovery but it didn't. Gave an error saying, "Unsuccessful" or something on those lines.
So I took that TWRP img file and copied it on my laptop. Then I went into the bootloader, which at first I thought was a bad idea since I just flashed the BL zip, then I flashed the new TWRP img file and went to recovery mode. And it had worked. So I flashed the CM 13.0 build too and then booted up the device, and it worked!
I guess that should help
aamodjoshi23 said:
Hi there.
I tried the way these folks suggested, by updating the BL using the zip file and flashing the updated TWRP recovery, and it worked!
Click to expand...
Click to collapse
I'm glad it worked for(don't forget to drop a thanks and a vote would be good too)
Also for next time,please search the forums before creating a thread.:angel:
Adesh15 said:
After flashing the new TWRP for new BL you should reboot to recovery from reboot tab in TWRP.
Then wipe System ,Data and Cache and then flash CM13
Click to expand...
Click to collapse
Adesh15, it worked! Thank you very much!
Cretandus said:
Adesh15, it worked! Thank you very much!
Click to expand...
Click to collapse
Great !
LG G3 VS985
I flashed the kernel and modem to 24B then flashed crdroid 7.1 rom and gapps. Now i'm unable to get pixel launcher as a system app. Haven't attempted to get assitant yet. Any suggestions?
csongcuan said:
LG G3 VS985
I flashed the kernel and modem to 24B then flashed crdroid 7.1 rom and gapps. Now i'm unable to get pixel launcher as a system app. Haven't attempted to get assitant yet. Any suggestions?
Click to expand...
Click to collapse
why did you flash 24b? anyway enabling root access is in the developer options
cory733 said:
why did you flash 24b? anyway enabling root access is in the developer options
Click to expand...
Click to collapse
I got the error "E: Error executing updater binary in zip" when i tried to flash the rom. It was failing the baseband check.
cory733 said:
why did you flash 24b? anyway enabling root access is in the developer options
Click to expand...
Click to collapse
I got the error "E: Error executing updater binary in zip" when i tried to flash the rom. It was failing the baseband check. Anyways thanks!
csongcuan said:
I got the error "E: Error executing updater binary in zip" when i tried to flash the rom. It was failing the baseband check. Anyways thanks!
Click to expand...
Click to collapse
It failed the baseband check because you need the 35b bootstack. Do a search for xdabbeb's 35B bootstack. When yiou have that start over with a total wipe. Then flash in this order:
35b Bootstack
Cr Droid 7.1
Open Gaps ARM 7.1 (of your choice, I used pico)
35b Bootstack
Be sure to flash the 35b Bootstack first AND last. Also use TWRP, and keep using the "add zip" button until you have all 4 zips in queue THEN swipe to flash.
I've been running Cr Droid 7.1 since it was officially released several months ago, and it has worked perfectly. Been my dd since I ran across it, and I love it..
Every feature has worked for me. But I don't have BT ni my ride so I don't know about that. But Wifi, data, Hotspot, BT to other devices, Beam - they've all worked on my G3
Hey guys.
I'm using a 32/3GB kenzo with an unlocked bootloader running official rr mm.
I formatted the phone, flashed CM14 firmware, flashed the official RR nougat and GAPPS, then rebooted to system.
At this point, it started bootlooping, booting to the MI splashscreen, staying there for about half the time it usually does, before rebooting and repeating the process.
At this point, I was unable to access recovery, but was able to access fastboot and edl.
Flashing a recovery using the "fastboot flash recovery" command failed, so I assume that the partitions were corrupted.
I had to revert to MIUI by flashing through edl using MI flash, which fixed all the issues.
Can someone tell me what I did wrong?
Or should I follow the newbie guide 2.0 from the forums?
Thanks in advance to anyone who replies.
Ivanlai said:
Hey guys.
I'm using a 32/3GB kenzo with an unlocked bootloader running official rr mm.
I formatted the phone, flashed CM14 firmware, flashed the official RR nougat and GAPPS, then rebooted to system.
At this point, it started bootlooping, booting to the MI splashscreen, staying there for about half the time it usually does, before rebooting and repeating the process.
At this point, I was unable to access recovery, but was able to access fastboot and edl.
Flashing a recovery using the "fastboot flash recovery" command failed, so I assume that the partitions were corrupted.
I had to revert to MIUI by flashing through edl using MI flash, which fixed all the issues.
Can someone tell me what I did wrong?
Or should I follow the newbie guide 2.0 from the forums?
Thanks in advance to anyone who replies.
Click to expand...
Click to collapse
Which recovery you uaed for flashing rr n. Because you went bootloop and recovery was not able to access that means may be some problems in recovery or either in rom/gapps zip. Make sure you are flashing gapps for NOUGAT only. And use latest stable miui firmware (not cm14 zip one although may be both are same)
Try this
1. Flash zcx recovery (I recommend this, never disappointed)
2. Flash latest miui stable firmware
3. Flash rom zip
4. Flash gapps n
Boot to system
5. Then flash kernel or anything.
Apcoolboy said:
Which recovery you uaed for flashing rr n. Because you went bootloop and recovery was not able to access that means may be some problems in recovery or either in rom/gapps zip. Make sure you are flashing gapps for NOUGAT only. And use latest stable miui firmware (not cm14 zip one although may be both are same)
Try this
1. Flash zcx recovery (I recommend this, never disappointed)
2. Flash latest miui stable firmware
3. Flash rom zip
4. Flash gapps n
Boot to system
5. Then flash kernel or anything.
Click to expand...
Click to collapse
Thanks for the reply, I'll try it soon. Can you tell me how to get the miui stable firmware?
Should I fastboot flash latest MIUI stable before flashing the ROM or is there a MIUI firmware zip file to flash?
Ivanlai said:
Thanks for the reply, I'll try it soon. Can you tell me how to get the miui stable firmware?
Should I fastboot flash latest MIUI stable before flashing the ROM or is there a MIUI firmware zip file to flash?
Click to expand...
Click to collapse
There is flashable zip file which is extracted from miui rom only. So both way will be good as flash latest stable miui rom and then twrp > rom zip > gapps. Or twr0 > firmware zip (search in any custom rom thread you will get one) > custom rom zip > gapps.
Only benefit of flashing firmware zip is less time consuming and less file size (around 50mb) compare to full miui rom.
Ivanlai said:
Thanks for the reply, I'll try it soon. Can you tell me how to get the miui stable firmware?
Should I fastboot flash latest MIUI stable before flashing the ROM or is there a MIUI firmware zip file to flash?
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361
Ivanlai said:
Hey guys.
I'm using a 32/3GB kenzo with an unlocked bootloader running official rr mm.
I formatted the phone, flashed CM14 firmware, flashed the official RR nougat and GAPPS, then rebooted to system.
At this point, it started bootlooping, booting to the MI splashscreen, staying there for about half the time it usually does, before rebooting and repeating the process.
At this point, I was unable to access recovery, but was able to access fastboot and edl.
Flashing a recovery using the "fastboot flash recovery" command failed, so I assume that the partitions were corrupted.
I had to revert to MIUI by flashing through edl using MI flash, which fixed all the issues.
Can someone tell me what I did wrong?
Or should I follow the newbie guide 2.0 from the forums?
Thanks in advance to anyone who replies.
Click to expand...
Click to collapse
unlock your bootloader again it will run without problem..
FIRST OF ALL BACK UP FILES, PHOTOS, CONTACTS ETC
REMOVE ANY PASSWORD, LOCKSCREEN FINGERPRINT ETC, PHONE FREE TO USE WITHOUT ANYTHING SO YOU SHOULD BE FINE ON TWRP
battery more than 50%, ideal would be between 70 and 90%
UNLOCK BOOTLOADER
INSTALL TWRP for MI 9T/K20, download here: turn off the phone and go into fastboot, VOL- and power at the same time, decompress the folder and choose the file Flash_TWRP.bat
enter TWRP volume + and power at the same time, as soon as MI appears
do wipe data / factory reset, no need to format data with this TWRP-DO NOT LET THE ROM BOOT TO OFICIAL
choose rom file DOWNLOAD XIAOMI.EU 9.10.24 MI9 T and flash, reboot
for MI9T PRO/K20 PRO TWRP version NOW COMPATIBLE WITH ANDROID 9 AND ANDROID 10:twrp-3.3.1-25-raphael-mauronofrio
[*]ATTENTION:YOU SHOULD FORMAT DATA ON TWRP IF YOU STAY IN BOOTLOOP
DO NOT LET THE ROM BOOT TO OFICIAL
choose rom file DOWNLOAD XIAOMI.EU 9.10.24 MI9 T PRO and flash, restart, 5 minutes and enter
MI 9T/MI 9T PRO :HYPERCAM R4 android 10-https: //f.celsoazevedo.com/file/cfiles/gcm1/HyperCam_R4_Q_FINAL.apk
MI 9T PRO XML settings: https: //www.celsoazevedo.com/files/android/p/f/2019/10/hypercam_r3_mi9tpro.xml
MI 9T XML: http: //www.mediafire.com/file/ax5nl2bxwaym8i0/HiDynamic_V2.xml/file
reserved
after you install TWRP you can install any custom rom you want, XIAOMI.EU is only used as an example.:good::good::good:
UPDATE VIA OTA FOR MI 9T: click on 3 dots,choose install package and reboot
UPDATE VIA TWRP FOR MI 9T PRO:
Wipe - advanced Wipe - Dalvik cache - cache
Install the update rom
then again Wipe - advanced Wipe - Dalvik cache - cache
reboot
@Lippe35
Click to expand...
Click to collapse
GLOBAL DEVELOPER XIAOMI.EU 9.11.28
ANDROID 10---» update MI 9T:https://androidfilehost.com/?fid=4349826312261648891
ANDROID 10---»last update MI 9T PRO:https://androidfilehost.com/?fid=4349826312261648889
STABLE VERSIONS:
ANDROID 9---»MI 9T: https://androidfilehost.com/?fid=1899786940962604641
ANDROID 10---»MI 9T PRO:https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv11/xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.4.0.QFKCNXM_v11-10.zip/download
Hi so recently today I was able to successfully flash my stock ROM from Global 11.0.3 to Europe 11.2 (20.3.5).
All works, I have a new and version specific TWRP recovery which solves the decryption issue and such.
Only problem though is I can't seem to update my ROM from the latest Europe 11.2 (20.3.12). I am aware that we cannot install OTA updates like we normally would because we are on a custom recovery. I tried flashing it from the 'choose update package' where it brought me to the TWRP and executed OpenScript to flash, and also tried flashing from TWRP itself. No luck. Bootloop into Redmi Logo and TWRP recovery, so I end up restoring the working Eu version.
An updated tutorial on how to install OTA roms on custom recoveries would really be appreciated, thanks!
Hey OP, could you make a How to install GSI guide?... I'm really interested on doing that.
TheDarkLord098 said:
Hi so recently today I was able to successfully flash my stock ROM from Global 11.0.3 to Europe 11.2 (20.3.5).
All works, I have a new and version specific TWRP recovery which solves the decryption issue and such.
Only problem though is I can't seem to update my ROM from the latest Europe 11.2 (20.3.12). I am aware that we cannot install OTA updates like we normally would because we are on a custom recovery. I tried flashing it from the 'choose update package' where it brought me to the TWRP and executed OpenScript to flash, and also tried flashing from TWRP itself. No luck. Bootloop into Redmi Logo and TWRP recovery, so I end up restoring the working Eu version.
An updated tutorial on how to install OTA roms on custom recoveries would really be appreciated, thanks!
Click to expand...
Click to collapse
i think you can install OTA with orange FOX recovery
TheDarkLord098 said:
Hi so recently today I was able to successfully flash my stock ROM from Global 11.0.3 to Europe 11.2 (20.3.5).
All works, I have a new and version specific TWRP recovery which solves the decryption issue and such.
Only problem though is I can't seem to update my ROM from the latest Europe 11.2 (20.3.12). I am aware that we cannot install OTA updates like we normally would because we are on a custom recovery. I tried flashing it from the 'choose update package' where it brought me to the TWRP and executed OpenScript to flash, and also tried flashing from TWRP itself. No luck. Bootloop into Redmi Logo and TWRP recovery, so I end up restoring the working Eu version.
An updated tutorial on how to install OTA roms on custom recoveries would really be appreciated, thanks!
Click to expand...
Click to collapse
you have to flash https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.1.zip and then update the OTA..dont forget that we normally use a custom rom with TWRP, no point of having twrp with stock rom??? try xiaomi.eu , its way better and you dont have any problems with updates.
Fors4kenArg said:
Hey OP, could you make a How to install GSI guide?... I'm really interested on doing that.
Click to expand...
Click to collapse
install a GSI rom? its the same, i dont recommend it..you may have some problems afterwards..but if you want just follow the OP steps, normally its like that:
enter twrp
format data
reboot to recovery
flash recommended firmware
flash rom reboot..
:good:
TheDarkLord098 said:
Hi so recently today I was able to successfully flash my stock ROM from Global 11.0.3 to Europe 11.2 (20.3.5).
All works, I have a new and version specific TWRP recovery which solves the decryption issue and such.
Only problem though is I can't seem to update my ROM from the latest Europe 11.2 (20.3.12). I am aware that we cannot install OTA updates like we normally would because we are on a custom recovery. I tried flashing it from the 'choose update package' where it brought me to the TWRP and executed OpenScript to flash, and also tried flashing from TWRP itself. No luck. Bootloop into Redmi Logo and TWRP recovery, so I end up restoring the working Eu version.
An updated tutorial on how to install OTA roms on custom recoveries would really be appreciated, thanks!
Click to expand...
Click to collapse
Hello, you are lost mate...
You use Xiaomi.eu ROM, it's a custom MIUI ROM (Not Official ROM).
You can install updates given by Updater app (System app) without issue on this ROM.
If your phone bootloop just after a ROM update, and not after flashing Magisk, it can be because of a bad encryption from "bad" TWRP (so you need to "Format Data" in new TWRP <-- installed by xiaomi.eu ROM)
-OR-
Did you use my K20 to Mi 9T conversion patch (from xiaomi.eu forum)?
Check for update with Updater app, download and install it. That's simple on xiaomi.eu ROMs.
Trying to install evolution X on my Mi 9T but whenever I flash TWRP the phone won't boot to it, just keeps loading the fastboot screen. Anyone have any ideas where I'm going wrong? I've reflashed stock with miflash for now to get it working.
PearseCF said:
Trying to install evolution X on my Mi 9T but whenever I flash TWRP the phone won't boot to it, just keeps loading the fastboot screen. Anyone have any ideas where I'm going wrong? I've reflashed stock with miflash for now to get it working.
Click to expand...
Click to collapse
I have the same problem, but I can't find a solution. Did you find it ?
I found the solution with explication on how to install havoc_OS
after format data you have to reboot to recovery, flash firmware +rom+gapps...without firmware it wont boot on some roms..read well OP instructions, mine are only for xiaomi.eu, you dont need to flash firmware and it will boot fine.
Hi all.
I have Honor 9 (STF-L09), I successfully rooted it right when I got it (TWRP + Magisk), even manged to flash stock recovery a few times to get OTAs and re-root again (all updates were EMUI 8.x and Android 8).
Now after performing the latest update, I'm on EMUI 9.1.0, Android 9, Build 9.1.0.210(C432....).
I can't find Pie compatible TWRP. I tried patching the stock recovery (with Magisk) and flash it using fastboot (as always) but Magisk will not install.
I had, the first time I rooted the device) decrypted it. I have no idea if the update re-encrypted the phone.
1. How can I know if the phone is still decrypted? if it isn't how do I decrypt?
2. What is the easiest way to root the Android 9 version?
Thank you
Clonimus said:
Hi all.
I have Honor 9 (STF-L09), I successfully rooted it right when I got it (TWRP + Magisk), even manged to flash stock recovery a few times to get OTAs and re-root again (all updates were EMUI 8.x and Android 8).
Now after performing the latest update, I'm on EMUI 9.1.0, Android 9, Build 9.1.0.210(C432....).
I can't find Pie compatible TWRP.
Click to expand...
Click to collapse
Maybe there is still none... yet. Do an other emui9 device got a pie 's twrp ?
Clonimus said:
I tried patching the stock recovery (with Magisk) and flash it using fastboot (as always) but Magisk will not install.
Click to expand...
Click to collapse
On 9.x pie boot partitioning changed. There is no more ramdisk, and magisk boot is done by booting a patched recovery of your actual installed build (recovery_ramdisk).
Use splitupdate or Huawei Update Extractor to get it from UPDATE.APP inside base.zip of your actual installed build.
Clonimus said:
I had, the first time I rooted the device) decrypted it. I have no idea if the update re-encrypted the phone.
1. How can I know if the phone is still decrypted? if it isn't how do I decrypt?
Click to expand...
Click to collapse
Does 8.x twrp shows via adb random filenames in internal memory path : /sdcard/ ?
Clonimus said:
2. What is the easiest way to root the Android 9 version?
Thank you
Click to expand...
Click to collapse
Official one
https://topjohnwu.github.io/Magisk/install.html#emui-9-or-higher
oslo83 said:
Does 8.x twrp shows via adb random filenames in internal memory path : /sdcard/ ?
Click to expand...
Click to collapse
No, but I no longer have TWRP after the last OTA in order to check.
I think I saw some TWRP for EMUI9 but not for Honor 9.
oslo83 said:
Official one
https://topjohnwu.github.io/Magisk/install.html#emui-9-or-higher
Click to expand...
Click to collapse
Tried it, but Magisk Manager says it is not installed.
I got it to work.
My mistake was after flashing the patched recovery_ramdisk I pressed up+power to get to recovery (as the instruction stated), but I had to release the button the second the Honor logo appeared, and so the phone booted via Magisk.
I saw this in the instruction on the other site.
It works. Thanks