Welcome to the Mate 20 X GlobAL00ized project. This ROM's goal is to transform your Chinese AL00 into a global device. This ROM is based on EMUI 9.1 version 9.1.0.120
[size=+2]NOTE: YOU CANNOT DOWNGRADE AFTER UPDATING TO EMUI 9.1. Also, a factory reset is not needed if you are coming from EMUI 9, but if you want to, that's fine.[/size]
Join our Telegram group:
Everest Dev
Requirements:
TWRP
Know how to boot into TWRP
EMUI Flasher by @olddroid
EMUI 9.1 (9.1.0.120)
Transformation ROM 2.2
Root with magisk
TWRP image on your PC
Recommendations:
Be decrypted
A factory reset for first time users
Magisk installed to recovery_ramdisk
A backup of your system, preload, product, version, and vendor partitions. Not necessary as erecovery can restore your device, but I thought I'd mention it anyway.
Changelog in the second post
Known Issues:
Google Play store is missing
SetupWizard doesn't work for clean flashes
These will be fixed when L29 EMUI 9.1 is released.
Sometimes the device will refuse to boot with magisk root and get stuck at "your device is booting." Hopefully later magisk versions will fix this. For now simply hold the power button down to reboot and try again. You may need to do this several times. but wait a least a minute before you do.
Installation steps:
First and foremost, backup your device. If you use TWRP or hisuite, go ahead and create a backup with either and backup your internal storage.
Step 1:
Start off by downloading and installing EMUI Flasher below:
Download EMUI Flasher
Step 2:
Download EMUI 9.1 9.1.0.120 AND Transformation ROM 2.2 with either your phone or PC below:
Download EMUI 9.1 version 9.1.0.120
Download Transformation ROM 2.2
Step 3: If you have downloaded EMUI 9.1 and Transformation ROM 2.2 with your phone, skip to step 3.5
Copy EMUI 9.1 (update_full_base.zip) and Transformation ROM 2.2 to your device.
Step 3.5: Now's a good time to disable any magisk modules that may modify or write over system files designed for EMUI 9, they more than likely will not be compatible with EMUI 9.1 and could cause bootloops.
Step 4:
Open EMUI Flasher and select the update_full_base.zip and start the flash.
If you want to remain on EMUI 9.1 official without the Transformation ROM, simply let EMUI Flasher do its thing and you're done. Otherwise, continue on below.
At this point, EMUI Flasher will copy the update_full_base.zip to /data and automatically reboot the phone to nocheck recovery. You will need to pay attention. The flashing process will take less than 3 minutes and when it is done, you will need to boot into fastboot with the phone connected to a PC and the volume DOWN button held.
Step 5:
Once you are in fastboot, open a command prompt/terminal where the TWRP image is located and issue the command "fastboot flash recovery_ramdisk twrp.img"
Step 6:
Issue the command "fastboot reboot" and immediately unplug your device from the computer and begin holding volume UP AND power (release POWER after the display turns on but continue holding volume UP) to get into TWRP.
Note: If for some reason you don't get into TWRP and instead get the boot screen telling you to press volume up for 3 seconds, do that to get to eRecovery, then SHUT DOWN from eRecovery. Once fully shut down, hold volume UP and power until the device vibrates and the display powers on--at this point you may release the power button but CONTINUE HOLDING VOLUME UP until the phone comes on and says it is booting.
Step 7:
Once you are in TWRP, flash Transformation ROM 2.2. The ROM will flash magisk as well but you will still need to have magisk manager if it isn't already installed.
Step 8:
Reboot Recovery from TWRP if you want root, or Reboot System from TWRP if you don't.
Step 9:
Rejoice!
XDA:DevDB Information
GlobAL00ized ROM, ROM for the Huawei Mate 20 X
Contributors
freeza
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: TWRP
Version Information
Status: Stable
Current Stable Version: 2.2
Stable Release Date: 2019-05-09
Created 2019-04-13
Last Updated 2019-05-09
Changelog
5/9/19: updated for fw 120 with May 2019 Security Patch.
4/22/19: updated for fw 119
4/12/19: Initial release
Patches and fixes
Restore Huawei Dialer and Contacts:
Huawei Dialer and Contacts for EMUI9.1
Great work !
Gửi từ EVR-AL00 của tôi bằng cách sử dụng Tapatalk
Can i flash the 9.1 beta without unlocked bootloader?
You are a superstar! ???
I messed up. When the EMUI flasher exited EMUI to install the base, I thought it had already installed the base, and I had missed the part where I needed to hold the volume down button, and I thought the phone was being encrypted. So I force closed the phone, and booted into TWRP and installed the 2.0 ROM. So I mistakingly installed the 2.0ROM without installing the upto date base. When I realised what I had done, I installed the new base and then the 2.0 ROM again. But ever since the phone has been buggy, e.g. if I do 2 finger touch, it exits the app I'm in. Also, now when I try to get into TWRP, it takes me to Stock eRecovery, even after I flash TWRP with ADB. And also now I am stuck in a bootloop.
I am currently using stock eRecovery to reinstall upto date package and recovery. What should I do from here to get back to 2.0 ROM. Thanks in advance.
Stock eRecovery downgraded to EMUI 9.0.0.200!!! Not sure what to do from here. Will keep tinkering.
Abdul Oxford said:
Stock eRecovery downgraded to EMUI 9.0.0.200!!! Not sure what to do from here. Will keep tinkering.
Click to expand...
Click to collapse
Nice. Was unaware that it would work.
Sent from my EVR-AL00 using Tapatalk
freeza said:
Welcome to the Mate 20 X GlobAL00ized project. This ROM's goal is to transform your Chinese AL00 into a global device. This ROM is based on EMUI 9.1 Beta version 9.1.0.115
[size=+2]NOTE: YOU CANNOT DOWNGRADE AFTER UPDATING TO EMUI 9.1 BETA. Also, a factory reset is not needed if you are coming from EMUI 9, but if you want to, that's fine.[/size]
Join our Telegram group:
Everest Dev
Requirements:
TWRP
Know how to boot into TWRP
EMUI Flasher by @olddroid
EMUI 9.1 BETA 9.1.0.115
Transformation ROM 2.0 beta
Root with magisk
TWRP image on your PC
Recommendations:
Be decrypted
A factory reset for first time users
Magisk installed to recovery_ramdisk
A backup of your system, preload, product, version, and vendor partitions. Not necessary as erecovery can restore your device, but I thought I'd mention it anyway.
Changelog in the second post
Installation steps:
First and foremost, backup your device. If you use TWRP or hisuite, go ahead and create a backup with either and backup your internal storage.
Step 1:
Start off by downloading and installing EMUI Flasher below:
Download EMUI Flasher
Step 2:
Download EMUI 9.1 Beta 9.1.0.115 AND Transformation ROM 2.0 beta with either your phone or PC below:
Download EMUI 9.1 Beta version 9.1.0.115
Download Transformation ROM 2.0 Beta
Step 3: If you have downloaded EMUI 9.1 beta and Transformation ROM 2.0 beta with your phone, skip to step 3.5
Copy EMUI 9.1 Beta (update_full_base.zip) and Transformation ROM 2.0 beta to your device.
Step 3.5: Now's a good time to disable any magisk modules that may modify or write over system files designed for EMUI 9, they more than likely will not be compatible with EMUI 9.1 and could cause bootloops.
Step 4:
Open EMUI Flasher and select the update_full_base.zip and start the flash.
If you want to remain on EMUI 9.1 Beta official without the Transformation ROM, simply let EMUI Flasher do its thing and you're done. Otherwise, continue on below.
At this point, EMUI Flasher will copy the update_full_base.zip to /data and automatically reboot the phone to nocheck recovery. You will need to pay attention. The flashing process will take less than 3 minutes and when it is done, you will need to boot into fastboot with the phone connected to a PC and the volume DOWN button held.
Step 5:
Once you are in fastboot, open a command prompt/terminal where the TWRP image is located and issue the command "fastboot flash recovery_ramdisk twrp.img"
Step 6:
Issue the command "fastboot reboot" and immediately unplug your device from the computer and begin holding volume UP to get into TWRP.
Note: If for some reason you don't get into TWRP and instead get the boot screen telling you to press volume up for 3 seconds, do that to get to eRecovery, then SHUT DOWN from eRecovery. Once fully shut down, hold volume UP and power until the device vibrates, at this point you may release the power button but CONTINUE HOLDING VOLUME UP until the phone comes on and says it is booting.
Step 7:
Once you are in TWRP, flash Transformation ROM 2.0 beta. The ROM will flash magisk as well but you will still need to have magisk manager if it isn't already installed.
Step 8:
Reboot Recovery from TWRP if you want root, or Reboot System from TWRP if you don't.
Step 9:
Rejoice!
XDA:DevDB Information
GlobAL00ized ROM, ROM for the Huawei Mate 20 X
Contributors
freeza
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: TWRP
Version Information
Status: Beta
Current Beta Version: 2.0
Beta Release Date: 2019-04-12
Created 2019-04-13
Last Updated 2019-04-13
Click to expand...
Click to collapse
Huawei's dialer is not functioning right with new update. Is there a newer one with the 9.1. beta?
Is it really not possible to make a TWRP flashable stock full ROM? Then, flash the ROM after... I don't want to take the risk of doing it the EMUI flasher way again as I did before and messed up.
Or can you make a version using the method described here? Only If it's not too much to ask. Thank you.
https://forum.xda-developers.com/hu...awei-p20-pro-charlotte-l29c432b131-8-t3809964
Sent from my HUAWEI EVR-AL00 using XDA Labs
Steamer2499 said:
Huawei's dialer is not functioning right with new update. Is there a newer one with the 9.1. beta?
Click to expand...
Click to collapse
I'll create one
Sent from my EVR-AL00 using Tapatalk
freeza said:
I'll create one
Sent from my EVR-AL00 using Tapatalk
Click to expand...
Click to collapse
Thanks! The new updates and rom working great!
freeza said:
Nice. Was unaware that it would work.
Sent from my EVR-AL00 using Tapatalk
Click to expand...
Click to collapse
I guess I screwed it up too. I ended up with kinda hybrid (see attached pictures).
So what really happened? I flashed update without any problem. Flashed twrp after, but there was no way to reboot to twrp. I was aware that it might not happen the first time but after about ten times, when I was confident that I was doing the procedure as it was described, I panicked. I always got into erocovery and I believed that I was in some kind of bootloop. So I studied my options and I decided to recover the stock. I had done it once before on my tablet and I'd managed to recover the corrupted system for the price of the lost root, factory reset, and locked bootloader.
I was expected the same but surprisingly I got the 200 rom back with the fully recovered phone. I started the procedure of flashing 9.1 again and this time I was able to get twrp immediately. Only what I noticed that during update flashing procedure about two lines appeared red. Otherwise flashing ended up flawlessly.
The result is a monster which at first sight appears fully operative. I noticed improved gesture navigation. Otherwise, the system lacks any of the improvements promised for the new EMUI (https://www.******************/emui-9-1-is-here-check-its-impressive-features/). And both magisk and twrp are tied to recovery (you can have only one mounted), erecory is original). I assume that transformation rom should sort this out but it didn't in my case.
After factory reset when up to 9.1. My phone can't conect to hisuite. Please help... thanks
I no longer have to hold the up button when booting to have root access. But CTS profile false in magisk.
...NICE ROM...
Hello do you have same problem with this theme: "Black EMUI 9 Theme for Huawei [ Dark EMUI ]" or "Mountain Dark Theme for EMUI ".
Police on background... Can't read... (like in phone settings)??? (For now only use original theme...)
AND i'm always build 9.0.0.1.198 and not in 9.1.0.115, but emui is 9.1.0???
Why... (i follow the right procedure...)
freeza said:
Nice. Was unaware that it would work.
Sent from my EVR-AL00 using Tapatalk
Click to expand...
Click to collapse
Abdul Oxford said:
Stock eRecovery downgraded to EMUI 9.0.0.200!!! Not sure what to do from here. Will keep tinkering.
Click to expand...
Click to collapse
I'm in rom 9.1.0.115 Beta... Please help me how to downgraded to EMUI 9.0.0.200. eRecovery say error while checking rom version from sever. Thanks
I can not get root
Thanks for this. However, I'm unable to get root with magisk. I install the magisk ramdisk severally without any effect. Please help. Thanks.
I don't have my phone rooted yet, but I want to thank you for the great job!
Related
So i got my Honor 5x yesterday and thought i would install a custom rom on it since people are recommending it.
Its my first time so i followed guids. I installed adb and fastboot and managed to get TWRP 3.1.1-0- on it.
Btw, i have a Honor 5x
Model KIW-L21
I am able to get into the recovery TWRP. I made a backup and saved the folder "BACKUPS" on my PC.
I then downloaded LineageOS from their Homepage: download (DOT) lineageos (DOT) org/kiwi
I downloaded the latest version. I also downloaded Gapps from Opengapps.org. I downloaded ARM64 version 7.1
I wiped my phone completely and copied the two zip files on the phone. I went to "install", selected LineageOS zip and added Gapps. i swiped right to install and the installation stopped with ERROR 7
I tried to download older versions of LineageOS but the same thing happens. ERROR 7
I then downloaded an olderversion of CM13 with GAPPS 6.0. Again, Error 7
I downloaded XENON HD ZIP from here: mirrors (DOT) c0urier (DOT) net/android/teamhorizon/N/Official/kiwi/
Error 7
I downloaded ASOP from here: downloads (DOT) aospextended (DOT) com/kiwi/
Error 7
I looked up Error 7 and its says it is a security check that figures out, that the ROM is not compatible with the Phone. Some guy told me that this happens a lot and that i should use another rom.
I looked for a solution on youtube and found a guy who said that i can do the following:
Unzip the ROM on your pc, go into \META-INF\com\google\android and open the updater script with Notepad++. Delete the first two lines that says asserts, save, close it again and zip the whole package again.
I copied the new, modifiled rom on the phone with the GAPPS and installed it. This time ERROR 7 didnt appear. GAPPS were also installed. When i boot my device i get in the loading screen from Lineage for about 5-10 minutes. After that, it just restarts and restarts and restarts. I can't get out of the boot loop since I can't remove my battery. when I press VOL UP I come back the TWRP and can wipe the phone again.
I tried that with 3 different LineageOS ROMS and one XENON HD ROM.
I also get into a boot loop where my phone just restarts and restarts and restarts.
I tried to get my backup working so I copied the folder "BACKUPS" on my phone and went to restore in TWRP. but... i found nothing there?
I am super frustrated since my phone is basically dead and I have no idea what I can do.
BTW, every site calls my phone "KIWI" but my model number is "KIW-L21"
As mentioned in Los 14.1 thread (& should be mentioned in all threads), "ROM Firmware Required: No VoLTE firmware! (B360, B370, ...)". You must downgrade your stock rom to B350 at least, before try playing with custom roms (only for kiwi, of course).
Non VoLTE Marshmallow firmware is required. As said by @mauam get in there and have the same process repeated
Thank you for your replies.
The only thing i could find was this thread: https://forum.xda-developers.com/ho...-lineageos-14-1-pre-official-kiw-l24-t3528488
It said there:
Important note:
Stock Firmware B360 and B370 are known to cause bootloops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
All others might work, please do not ask in here how to up- or downgrade!
It doesnt mentioned what that mean and even said "dont ask in here how to downgrade"
I have no idea what all that means. I dont know what stock firmware is, what version i have or how i could downgrade it. I can access TWRP, but still have no OS on it.
edit: this is the full log:
Updateing partition details...
... done
Full SElinux support is present.
MTP Enabled
Installing zip file '/sdcard/lineage-14.1-20170816-nightly-kiwi-signed.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Comparing TZ version TZ.BF.3.0.C3-00025 to TZ.BF.3.0.C3-00022") =="1"
assert failed: kiwi.verify_trustzone("TZ.BF.3.0.C3-00025") == "1"
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/lineage-14.1-20170816-nightly-kiwi-signed.zip'
Updating parition details...
...done
Click to expand...
Click to collapse
When i edit the zip file and delete the first two line of the updater scripter with notepad++ as i mentioned above, i can install these ROMS, but they wont boot / are in an infinite Bootloop
So on which firmware you were before flashing Los
PalakMi said:
So on which firmware you were before flashing Los
Click to expand...
Click to collapse
how do i check that?
I was able to get the backup running. So I am back to EMUI 3.1 / Android 5.1.1. Here is a screenshot from my phones status: i.imgur (DOT) com/rCnuOpX.png
Activehannes said:
how do i check that?
I was able to get the backup running. So I am back to EMUI 3.1 / Android 5.1.1. Here is a screenshot from my phones status: i.imgur (DOT) com/rCnuOpX.png
Click to expand...
Click to collapse
Just go to about phone
PalakMi said:
Just go to about phone
Click to expand...
Click to collapse
I did and posted a screenshot above
is it Build number "KIW-L21C432B160"
so... B160?
update:
I just downloaded this:
NEW KIW-L21 C432B350 - D003
from this thread: https://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
I was going to unzip it, copy the "dload" folder on my device, go the the updater and run the "local update package".
And then my phone will be on android 6.0 with b350, right?
The next step would be to start the phone in the recovery TWRP, go to wipe --> advance wipe and select everything (system, data, cache etc). after that i copy the latest Kiwi lineage OS zip rom on my device with the GAPPS 7.1 and try to install them again via TWRP 3.1.1?
Is this right?
I just wanna ask because my phone doesnt work for 2 days now and i dont want to brick it completely. cant afford a new one
Update to marshmallow first (any update before b360, like b320)
Update to marshmallow first (any update before b360, like b320)
Click to expand...
Click to collapse
when i go to the "updater" and and search for a new update it says that there is none. My phone is still on EMUI 3.1/android 5.1.1/b160. Do i need to manually download another firmware? so a B320 patch first (with the dload folder and local upgrade package) and after that the B350 upgrade?
Try manual ota here or search here. If no luck use XDA search bar &/or Google. Good luck.
Activehannes said:
when i go to the "updater" and and search for a new update it says that there is none. My phone is still on EMUI 3.1/android 5.1.1/b160. Do i need to manually download another firmware? so a B320 patch first (with the dload folder and local upgrade package) and after that the B350 upgrade?
Click to expand...
Click to collapse
Try any marshmallow update before b360.
If it didn't work, try the above post.
so i followed this guide: https://forum.xda-developers.com/honor-5x/how-to/manual-ota-update-guide-update-app-t3445976
he describes 2 methods.
I wasnt able to find a B320 update for KIW L21, only for KIW L22 which is the Indian device I think. so I downloaded KIW L21 B330 Denmark. I unzipped the file and copied the dload folder on my device,
i went to update --> menu --> local update --> UPDATE.APP
my phone restarts into TWRP and does nothing. I know that I need the EMUI stock recovery, not TWRP, but no matter how many times I do this, it always restarts into TWRP.
i also tried the other method.
I shut down my phone, press VOLUP and VOLDOWN and Power. The phone goes into the the "honor" loading screen and restats after a few seconds. and restart again and again. If i release the power button before it restarts, it just boots into the system. If I shut it down and hold VOLUP and Power it boots into TWRP. I tried so many different compinations, but i cant get my phone into the EMUI Stock recovery. I read in the other XDA thread, that i need to unlock my phone. So i tried that. i went adb reboot bootloader --> fastboot oem relock CODE. the console did its magic but my phone is still unlocked. And now i cant repeat that command. when i go again into the bootloader and type fastboot oem relock it says:
PS C:\adb> adb devices
List of devices attached
W6HDU17610003396 device
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot oem relock 1524319619165116
...
FAILED (remote: Image verify failed,relock fail)
finished. total time: 1.810s
PS C:\adb> adb devices
List of devices attached
PS C:\adb>
Click to expand...
Click to collapse
So, i still have b160 / android 5.1 on my phone :/ can anyone figure out what went wrong?
Activehannes said:
so i followed this guide: https://forum.xda-developers.com/honor-5x/how-to/manual-ota-update-guide-update-app-t3445976
he describes 2 methods.
I wasnt able to find a B320 update for KIW L21, only for KIW L22 which is the Indian device I think. so I downloaded KIW L21 B330 Denmark. I unzipped the file and copied the dload folder on my device,
i went to update --> menu --> local update --> UPDATE.APP
my phone restarts into TWRP and does nothing. I know that I need the EMUI stock recovery, not TWRP, but no matter how many times I do this, it always restarts into TWRP.
i also tried the other method.
I shut down my phone, press VOLUP and VOLDOWN and Power. The phone goes into the the "honor" loading screen and restats after a few seconds. and restart again and again. If i release the power button before it restarts, it just boots into the system. If I shut it down and hold VOLUP and Power it boots into TWRP. I tried so many different compinations, but i cant get my phone into the EMUI Stock recovery. I read in the other XDA thread, that i need to unlock my phone. So i tried that. i went adb reboot bootloader --> fastboot oem relock CODE. the console did its magic but my phone is still unlocked. And now i cant repeat that command. when i go again into the bootloader and type fastboot oem relock it says:
So, i still have b160 / android 5.1 on my phone :/ can anyone figure out what went wrong?
Click to expand...
Click to collapse
May be i can help u with this .
Redmi K20 Pro
[Raphael]
WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are NOT risking voiding your warranty! I am NOT responsible for what you do to your device either, so follow these instructions at your own risk. Make sure you know what you're doing, it's best to understand the process rather than just copy and paste commands and such.
Drivers
Mi Flash
Minimal ADB and Fastboot
Unlock Bootloader
Unlock Bootloader
Unlock here
*AMD Ryzen System has a issues in Unlocking Bootloader try another PC (Intel System)
TWRP Recovery
TWRP
TWRP auto install
Unofficial TWRP 3.3.1 Recovery - RU and Eng
Unofficial TWRP 3.3.1 Recovery @nikk3d - Multilingual
Unofficial Pitch Black Recovery @nikk3d
OrangeFox Recovery Official R10
TWRP Recovery for Android Q
/ Installation
Root
Magisk Stable
Magisk Manager
Firmwares
China MIUI 11
9.9.9
9.9.6-9.9.9
9.10.8
11.0.2.0
11.0.3.0
11.0.1.0.
11.0.4.0
11.0.5.0
9.12.27
Global Stable
10.3.3.0 Fastboot
10.3.3.0 Recovery
Global Beta
China
V10.3.6.0.PFKCNXM Fastboot
V10.3.7.0.PFKCNXM Recovery
V10.3.7.0PFKCNXM Fastboot
V10.3.8.0.PFKCNXM Recovery
V10.3.8.0PFKCNXM Fastboot
V10.3.9.0PFKCNXM Recovery
V10.3.10.0PFKCNXM Recovery
V10.3.110.PFKCNXM Recovery
V10.3.12.0PFKCNXM Recovery
V10.3.14.0PFKCNXM Recovery
V10.3.16.0PFKCNXM Recovery
V10.4.4.0 RecoveryQFKCNXM
V10.4.4.6 RecoveryQFKCNXM
OTA
10.3.10.0 to 10.3.11.0
10.3.8.0 to 10.3.10.0
10.3.7.0 to 10.3.8.0
10.3.9.0 to 10.3.10.0
Beta
9.6.11
9.6.20
9.7.4
9.8.12
9.8.21
9.9.3
India
Stable Firmwares
10.3.3.0 Fastboot
10.3.5.0
10.4.7.0 Android Q
10.4.8.0 Android Q
Beta
Global
EU
9.6.13
9.6.20
10.3.9.0
10.3.10.0
10.3.11.0
9.6.27
[URL="https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv10/xiaomi.eu_multi_HMK20ProMI9TPro_V10.3.12.0.PFKCNXM_v10-9.zip/download"]10.3.12.0[/URL]
9.7.4
10.3.14.0
10.3.15.0
9.7.11
9.7.18
9.7.19
10.3.16
9.7.27
9.8.1
EU Android Q 9.8.8
9.8.12
9.8.15
9.8.22
10.3.17
EU Android Q 9.8.29
EU Android Q 10.4.4.0
9.9.3
9.9.6
10.3.30
EU Android Q 10.4.6.0
MIUI 11 9.9.26
MIUI 11 9.10.10
MIUI 11 11.0.2.0
MIUI 11 9.10.24
MIUI 11 9.11.7
MIUI 11 9.11.14
MIUI 11 9.11.21
MIUI 11 9.11.22
MIUI 11 9.11.28
MIUI 11 9.12.5
MIUI 11 9.12.12
MIUI 11 9.12.27
MIUI 11 20.1.16
Global EEA
10.3.1.0 PFKEUXM Fastboot
10.3.1.0 PFKEUXM Recovery
10.3.3.0 Recovery
Mi-Room
9.6.20
9.6.27
9.7.4
9.8.1
9.8.22 Android Q
9.8.29 Android Q
9.9.6 Android Q
MiuiMix
10.3.17.0
Mi-Italia
10.3.16.0
MIUI MS
9.7.18.9
9.7.25.9
9.8.1
Android Q 9.8.8
*Back up everything and Flash via TWRP Recovery
*For Raphael only (China ROM)
9.8.8 Q
9.8.8-9.8.29 Q
9.8.29 Q
MIUI 11 9.9.24
MIUI 11 9.9.25
[URL="https://hugeota.d.miui.com/9.9.26/miui_RAPHAEL_9.9.26_c74ffeeec0_10.0.zip"]MIUI 11 9.9.26[/URL]
Revolution OS
9.9.7
Google service error flash this
9.9.21 Q
9.9.21 Pie
Android Q [Unlocked Bootloader]
Beta 1
TWRP RESET Password
If you forget the password go to TWRP Recovery and Flash.
Removing Bloatwares in Locked/Unlocked Bootloader
-Enable Developer Options and click USB debugging
1.Open and click run as administrator XiaomiADBfastboottools.exe
2.Click Debloater
3.Check your phone (Allow)
4.Select the system apps that want you to delete
5. Wait for the process....
6.After finished.. click the Reboot into System
The Ultimate Guide for Redmi K20 Pro [Raphael]
Fake Global ROM to Chinese ROM to Global ROM/EU/Mi-Room
ATTENTION!*All that you will do with the phone is guided by this guide - it lies in the area of your personal responsibility only.*Neither I nor other members of the forum, not the administration of the forum are responsible.*
If you do not understand something and the written guide below - contact the LS to knowledgeable colleagues, as I did!*Hide created for the Chinese version of the phone K20 Pro - Global ROM.*(for India it will not work!)*
I will explain in stages what to do, giving my comments in my simple language: what?*What for?*Why?*Don't be scared that there are a lot of points - I tried to chew everything up.
So what do we have?*
• K20 Pro - Global ROM (Installed by the Chinese firmware, with no updates, poor translation, with not working Gpay)*
• You must create an official mi account and link the device to it.*
What do we need?:*
• Installation Recovery - Orange fox (Advanced replacement of standard Recovery, and installation of any firmware) - Wildly necessary thing!*
• Installing the firmware MI Room 9.7.4*
• Proper operation of the GPAY through the patch*
Introduction)*
So, you got a phone from China.*What do you have in your hands?*This is the device on which the Chinese put the left firmware and at the same time did not unlock the bootloader officially - which is not compatible with the transition to any, really good firmware.*
Before we begin - the most important thing!*(further quote from the forum):
ATTENTION!*CHINESE VERSION REDMI K20 PRO CAN BE BLOCKED ONLY ON THE CHINESE FIRMWARE!*Before carrying out any operation, read the materials that are referenced in the header themes, check Search by topic, and if not found the answer to your question, or do not understand something, ask more experienced users.*
Do you understand?*Now read again 20 and memorize this phrase!*
INSTALLATION OF THE CHINESE OFFICIAL FIRMWARE AND LOCKER DOWNLOAD AND UNLOCK!*
What for?*Your phone needs to be unlocked officially.*To do this, you must put the official firmware and file for unlocking officially.*
What is needed (all in the header):*
•Firmware file - *10.3.6.0 China Fastboot
• Program MiFlash 2018.11.15.0 (we need administrator rights) - a program to install Fastboot-type firmware and lock the phone loader.*
• Driver for computer - ADB Driver Lite
• Program - miflash_unlock*
• Phone*
• Type C Cable*
1) Download all of the above and check that everything downloaded*in the right “size”.*
2) Install MiFlash 2018.11.15.0*on the C drive:
3) Go to MiFlash 2018.11.15.0 - it will offer to install the drivers.*Do not hesitate to install everything - exit the program!*
4) Install ADB Driver Lite (by default it is set by MiFlash but will not be worse if you additionally install the latest driver from the header)
5) - CORRECTLY unpacking the firmware 10.3.6.0 China Fastboot!*By default, you download it with the extension .tgz!*The file you downloaded will be called raphael_images_V10.3.6.0.PFKCNXM_20190516.0000.00_9.0_cn_ed862b8182.tgz*
- Unzip this .tgz file and get a file with the .tar extension.*The full name will be - raphael_images_V10.3.6.0.PFKCNXM_20190516.0000.00_9.0_cn_ed862b8182.tar.*
- Unzip this .tar file and get a folder named raphael_images_V10.3.6.0.PFKCNXM_20190516.0000.00_9.0_cn.*Here we will work with this folder in the future!*You need to move it to drive C:!*It is important!*
6) Switch the phone to debug mode via USB.*(I think there will be no problems here)
7) Transfer the phone to FASTBOOT mode.*Turn off the device.*Clamp the power button + volume rocker down.*If there is a hare and the inscription Fastboot then everything is OK!*
8) In MiFlash, press the Select button, specify the path to the folder with the firmware raphael_images_V10.3.6.0.PFKCNXM_20190516.0000.00_9.0_cn and click ok.*
9) Something like this should appear in the line:*С: \ raphael_images_V10.3.6.0.PFKCNXM_20190516.0000.00_9.0_cn
10) Put a clean all and lock checkbox at the bottom.*This parameter means that the*
phone will be erased while all data is erased, and the bootloader is locked.*(only for the Chinese version of the phone)*
11) We connect the phone (in fastboot mode) to the computer through the official drawstring.*And without any USB hubs and adapters!*
12) Press the Refresh button.
13) If everything is correct then a line should appear with the id of the phone and the status ready.*
14) So, the phone is recognized.*The path to the folder with the firmware is specified.*Galka clean all and lock costs.*Press the flash button.*
15) The phone starts to sew!*Do not unplug the power cord!*don't touch anything at all.*Do not breathe!*The firmware time is about 10 minutes.*
16) At the end of the firmware, complete will appear in the line with the execution status and the phone will restart (up to 10 minutes) to the initial welcome screen.*Disconnect the phone.*
17) Hooray you flashed to the Chinese firmware and officially blocked the phone.*Let's start the activation and application for unlocking.
18) The first thing that will meet you is the screen in Chinese.*With two button in Chinese.*Push first you are asked to enter something ... This is the password from your mi account.*We enter.*
19) Tap on the second button connect to the Wi-Fi or skip.*
20) Choose the English language.*Customize your phone.*
21) Transfer the phone to the developer mode.*In the settings of the developer, we go into the unlock status (I don’t remember exactly how to speak English).*We see the closed lock, below we see the button.*Click on it!*And we will register the phone for the official unlock (Wi-Fi should be turned off and mobile networks on).*
22) Next, go to the mi account and check that your mobile phone is tied.*Are you convinced?*I recommend to look at the corresponding topic on the forum with the video.
23) On the PC, run miflash_unlock.*Log in to your mi account.*The phone is transferred to the Fastboot mode (point 7) and connected to the computer.*Press the unlock button.*At the same time, we confirm a bunch of times that we are sure that we want to do this.*All your data will be destroyed.*
24) The PC starts to unlock and at some point gives a message that the unlock failed and should be tried again after 168 hours.
25) Congratulations, you activated the counter before unlocking.*You walk with the phone 7 days on the Chinese firmware.*Is it hard?*Well no.*You can take the apk with Google services from the page on this forum and install what you need.*
26) It's been 168 hours, and you're ready to unlock.*
27) But before you do ... Update your phone over the air to the latest version - nowhere on the forum it is not written (I have not seen) but this is important.*I will explain later why!*Remember this item.*
28) Start and repeat paragraph 23. And lo and behold!*The unlock process has begun.*And at the end there is an inscription that the phone is unlocked.
29) Now, when you boot your phone, you should see Unlocked.*Check out what it is!*
30) Configure the phone again.*Turn on USB debugging mode.*
31) Further, in my opinion the most dreary, because the forum has a lot of conflicting information.*I will tell you how I did.*But before continuing, I can say that since you have already received unlock, it is almost impossible to turn the phone around (but everything is possible)*
32) So, download three things:*
- TWRP-3.3.1*
- OrangeFox R10.0 Recovery*
- MI Room 9.7.4 firmware
33) Everything that you downloaded in the zip archives.
34) Unzip -TWRP-3.3.1 to drive C. Transfer the phone to Fastboot (item 7) and connect it to the computer.*We find in the unpacked folder TWRP file with the extension .bat.*in different versions of TWRP called differently.*I called Flash_twrp.bat*
35) And before*proceeding, I’ll*remind you about clause 27).*The fact is that I could not install TWRP without updating over the air.*Therefore, you must first install the update.*And on the firmware 10.3.6.0 China Fastboot.*- It will not work to put TWRP and you will have to do a lot again*
36) Start and get the menu in my Russian language, where we select the auto installation (1).*After a couple of seconds, your phone should reboot into TWRP recovery.*There we choose the language if asked.*
37) And
so, we are in the main menu of TWRP.*We need to take a series of actions*(in a strict order)
38) Go to the Wipe point and select FORMAT DATA -> svayp -> type yes.*The formatting process takes a couple of seconds.*What does this item do in my understanding?*He decrypts the data on the phone, which is necessary to throw on the phone firmware and Orange fox.*
39) Exit the main menu by clicking REBOOT Recovery.*The phone should reboot into the main menu again.*And on the PC, it should be defined as a phone with Internal storage.*Go to the Internal storage on the PC.*See the TWRP folder?*If yes, then everything is OK!*
40) On the phone, go to the Wipe point and select Advanced wipe -> svayp -> select all the items*except System and OTG* svayp
41) Exit the main menu, press REBOOT -> Recovery.*The phone should reboot into the main menu again.*
42) On the PC, go to the phone -> Internal storage and next to the TWRP folder, throw the downloaded OrangeFox R10.0 recovery directly into the zip archive.*
43) On the phone, go to the Install item and see our Orange Fox.*Choose it.*AND THERE IS THE MOST IMPORTANT!*He will ask you to install two checkboxes before installation: one of them Verification of the ZIP signature (in English) and so this checkbox must be removed, otherwise the error will be.*We start the installation.*Your phone must reboot into Orange FOX.*
44) So what is Orange Fox?*This same TWRP is simply much more convenient and stable.*
45) On the PC, go to the phone -> Internal storage and next to the TWRP folder, throw the downloaded firmware to the worlds.
46) In Orange Fox, select this firmware, also remove the checkmark ZIP signature check (in English).*And start the process of installing the firmware.*
47) Hooray you got the best, in my opinion, firmware)*
48) Disconnect from the computer.*Customize your phone.*
49) Installing a patch for Gpay is easy.*Straight from the phone, download the patch file.*
50) Put the phone in orange fox recovery mode.*Turn off the device.*We press the power button + volume rocker UP (not to be confused with the power button + volume rocker DOWN for Fastboot boot mode)*
51) In the Downloads folder we see our patch and install (also remove the Check Signature ZIP checkbox).*
52) Congratulations!
Thanks to
helpbabay911
Mysttorent
Viper4Android + DDPlus and Google Pay Fix for Redmi K20 Pro
Google Pay Fix
•TWRP Recovery from our site
•Do not install the patch simultaneously with other patches or firmware.
•Install the patch only on top of the installed firmware. If you have made a date wipe, first launch the firmware, perform the initial setup, and then install the patch itself.
•Before installing the patch, make sure that the Data section is mounted (usually it is mounted by default on all TWRPs).
Download
*Credits to Mi-Room RU
Viper4android + DDPlus =
1.Install Audio Modification Library (AML) and Audio Compatible Patch (ACP) via Magisk Repo and reboot.
2.Install DDPlus via Magisk and reboot.
3.Install Viper4Android via Magisk and reboot. (materialized).
4.selinux changer (choose permissive if not working in enforcing).
5.Profiles
Profiles with IRS 1
Profiles with IRS 2
Profiles
DDPlus
AML (You can download from Magisk Repo)
ACP (You can download from Magisk Repo)
Viper4android (You can download from Magisk Repo)
Reserved 3
Reserved 4
So EU 9.5.13 is the global ROM for K20 Pro?
I'm using China ROM, I wanna switch to Global, can I just flash it?
Thank you
Thank you for your amazing work!
khoaitaychienvn said:
So EU 9.5.13 is the global ROM for K20 Pro?
I'm using China ROM, I wanna switch to Global, can I just flash it?
Thank you
Click to expand...
Click to collapse
Yes, you can flash it with TWRP. That's the multilanguage rom with Google Play preinstalled and without the bloatware of the Chinese version.
madsponge26 said:
Reserved 1
Click to expand...
Click to collapse
Hi. I really appreciate the post.. just one question though? What are the firmwares for? Coz if I am not mistaken, to be able to install twrp and root, all I need is to unlock the bootloader then flash the twrp.img. Please enlighten me.. thank you..
---------- Post added at 07:35 PM ---------- Previous post was at 07:33 PM ----------
Also, will bootloader unlocking and installing twrp wipe everything I have in my internal storage?
melmarPH said:
Hi. I really appreciate the post.. just one question though? What are the firmwares for? Coz if I am not mistaken, to be able to install twrp and root, all I need is to unlock the bootloader then flash the twrp.img. Please enlighten me.. thank you..
---------- Post added at 07:35 PM ---------- Previous post was at 07:33 PM ----------
Also, will bootloader unlocking and installing twrp wipe everything I have in my internal storage?
Click to expand...
Click to collapse
The firmwares are the stock roms, should you need to recover the phone. The fastboot ROM is the absolute failsafe and flashes almost all partitions. This can be updated using scripts within the package or using the Mi flash tool. The recovery roms will just update the system partition and flashed using recovery, either stock or TWRP or any other recovery.
Installing TWRP won't touch anything on the phone except the recovery partition. However bootloader unlocking will perform a factory reset. In theory the internal storage should remain untouched, but best to back it up.
madsponge26 said:
Reserved 4
Click to expand...
Click to collapse
Hi, Please update the thread, here's a fastboot link for Firmware 10.3.7.0
https://bigota.d.miui.com/V10.3.7.0...FKCNXM_20190528.0000.00_9.0_cn_8b5bfd6d56.tgz
and 10.3.8.0
http://bigota.d.miui.com/V10.3.8.0....FKCNXM_20190601.0000.00_9.0_cn_beb2b2a432.tgz
Robbo.5000 said:
The firmwares are the stock roms, should you need to recover the phone. The fastboot ROM is the absolute failsafe and flashes almost all partitions. This can be updated using scripts within the package or using the Mi flash tool. The recovery roms will just update the system partition and flashed using recovery, either stock or TWRP or any other recovery.
Installing TWRP won't touch anything on the phone except the recovery partition. However bootloader unlocking will perform a factory reset. In theory the internal storage should remain untouched, but best to back it up.
Click to expand...
Click to collapse
That's crystal clear. Thank you so much..
khoaitaychienvn said:
So EU 9.5.13 is the global ROM for K20 Pro?
I'm using China ROM, I wanna switch to Global, can I just flash it?
Thank you
Click to expand...
Click to collapse
I would not suggest to flash it right now as a daily driver, here is a review for xiaomi eu rom.
https://www.youtube.com/watch?v=mTi8nYMJRx4
sorry can i ask 9.6.11 is global beta rom or china rom?
What is the wait time to unlock the bootloader?
bretzelpopo said:
What is the wait time to unlock the bootloader?
Click to expand...
Click to collapse
7 days
knight06 said:
sorry can i ask 9.6.11 is global beta rom or china rom?
Click to expand...
Click to collapse
I was with the same doubt. is that rom really a Beta version of the global rom?
knight06 said:
sorry can i ask 9.6.11 is global beta rom or china rom?
Click to expand...
Click to collapse
rafa_martineiz said:
I was with the same doubt. is that rom really a Beta version of the global rom?
Click to expand...
Click to collapse
9.6.11 is China Beta
9.6.13 is EU version which is from Xiaomi.EU . Unofficial global version based on China ROM that removes all chinese bloat and adds more languages.
New Links!
10.3.6.0 for Recovery
http://bigota.d.miui.com/V10.3.6.0.PFKCNXM/miui_RAPHAEL_V10.3.6.0.PFKCNXM_e679907a50_9.0.zip
10.3.9.0 for Recovery
http://bigota.d.miui.com/V10.3.9.0.PFKCNXM/miui_RAPHAEL_V10.3.9.0.PFKCNXM_bd915c4259_9.0.zip
MIUI 10 10.3.9.0 Android Pie 9.0 is up!
Changelog
MIUI 10 EU 10.3.9.0 Android Pie 9.0 is up!
Changelog
Hi all,
I'm trying to install Havoc OS on my P20 lite (2018 model - ANE-LX1 8.0.0.0.135(C432)). My current version of EMUI is 8.0. So I need to install a A version of ARM and NOT AB.
The system image is
Havoc-OS-v3.1-20200202-ARM64A-GSI.img
I have TWRP 3.4.0 installed and working. PS, I have also tried this via fastboot (fastboot flash system Havoc-OS-v3.1-20200202-ARM64A-GSI.img.xz) with the same results
Before flashing the ROM and my GAPPS file (open_gapps-arm64-10.0-nano-20200808.zip). Via TWRP I wipe Dalvik/Cache/System/Data
Then I installed the ROM via TWRP install and selected .img install, there are no errors and the screen output says it is installed correctly.
Then I flashed the GAPPS mentioned above. After that I wipe Dalvik/Cache again.
And reboot....nothing happens. The phone boots back up and goes straight to TWRP again. It's like the ROM is not being initialized at all.
Any help would be appreciated.
MayhemIam said:
Hi all,
I'm trying to install Havoc OS on my P20 lite (2018 model - ANE-LX1 8.0.0.0.135(C432)). My current version of EMUI is 8.0. So I need to install a A version of ARM and NOT AB.
The system image is
Havoc-OS-v3.1-20200202-ARM64A-GSI.img
I have TWRP 3.4.0 installed and working. PS, I have also tried this via fastboot (fastboot flash system Havoc-OS-v3.1-20200202-ARM64A-GSI.img.xz) with the same results
Before flashing the ROM and my GAPPS file (open_gapps-arm64-10.0-nano-20200808.zip). Via TWRP I wipe Dalvik/Cache/System/Data
Then I installed the ROM via TWRP install and selected .img install, there are no errors and the screen output says it is installed correctly.
Then I flashed the GAPPS mentioned above. After that I wipe Dalvik/Cache again.
And reboot....nothing happens. The phone boots back up and goes straight to TWRP again. It's like the ROM is not being initialized at all.
Any help would be appreciated.
Click to expand...
Click to collapse
Hi,
1. On Oreo use this TWRP
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
2. You have to extract system.img (cca 1,2GB) from .xz package (unpack it on PC), then transfer it to SD .
Reboot to the TWRP > Wipe > Format Data > go back > Wipe > Advanced > Dalvik/Cache/System/Data > go back > flash system.img
Go back > Reboot> Recovery and do factory reset from Stock recovery (se the note bellow!)
P.S.: it's recommended install TWRP over eRecovery:
Copy downloaded TWRP file to the SD card, and also copy to card Stock ramdisk_recovery , download here: (for EMUI 8 only! )
https://mega.nz/#!04dG0JBb!hEgTk6DMKVDffttHiXGqa_YR_zG5UYwTMEi41KTkZi8
Since A8 and above you can not install TWRP over eRecovery from fastboot, follow instructions:
- install TWRP from fastboot , reboot to TWRP, select install image, and flash TWRP over eRecovery, go back, find recovery_ramdisk330 and flash it over recovery. Reboot system. After the boot screen appears in the recovery with the inscription "Your device is booting now ..." press and hold Volume Up
for 3 sec, device will boot to TWRP.
-Alf- said:
Hi,
1. On Oreo use this TWRP
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
2. You have to extract system.img (cca 1,2GB) from .xz package (unpack it on PC), then transfer it to SD .
Reboot to the TWRP > Wipe > Format Data > go back > Wipe > Advanced > Dalvik/Cache/System/Data > go back > flash system.img
Go back > Reboot> Recovery and do factory reset from Stock recovery (se the note bellow!)
P.S.: it's recommended install TWRP over eRecovery:
Copy downloaded TWRP file to the SD card, and also copy to card Stock ramdisk_recovery , download here: (for EMUI 8 only! )
https://mega.nz/#!04dG0JBb!hEgTk6DMKVDffttHiXGqa_YR_zG5UYwTMEi41KTkZi8
Since A8 and above you can not install TWRP over eRecovery from fastboot, follow instructions:
- install TWRP from fastboot , reboot to TWRP, select install image, and flash TWRP over eRecovery, go back, find recovery_ramdisk330 and flash it over recovery. Reboot system. After the boot screen appears in the recovery with the inscription "Your device is booting now ..." press and hold Volume Up
for 3 sec, device will boot to TWRP.
Click to expand...
Click to collapse
Hi Alf my man
So I am having a bit of trouble with your instructions. I am very sure it is my own fault! I just want to clarify the steps please. I have downloaded the 2 provided files you gave in the link.
1
Install TWRP via
"fastboot flash recovery_ramdisk TWRP-oreo-smart.img"
2
Boot into newly flashed TWRP and flash the 2 files again as specified
"....flash TWRP over eRecovery, go back, find recovery_ramdisk330 and flash it over recovery...."
3
Reboot after step 2 and go into TWRP again and perform the system.img install as per instructions via TWRP
"Reboot to the TWRP > Wipe > Format Data > go back > Wipe > Advanced > Dalvik/Cache/System/Data > go back > flash system.img
Go back > Reboot> Recovery and do factory reset from Stock recovery"
I take it that I need to install my GAPPS package as well in this stage?
4
After factory reset from stock recovery the OS should boot and initiate...
Thanks again man for your help!
MayhemIam said:
Hi Alf my man
So I am having a bit of trouble with your instructions. I am very sure it is my own fault! I just want to clarify the steps please. I have downloaded the 2 provided files you gave in the link.
1
Install TWRP via
"fastboot flash recovery_ramdisk TWRP-oreo-smart.img"
2
Boot into newly flashed TWRP and flash the 2 files again as specified
"....flash TWRP over eRecovery, go back, find recovery_ramdisk330 and flash it over recovery...."
3
Reboot after step 2 and go into TWRP again and perform the system.img install as per instructions via TWRP
"Reboot to the TWRP > Wipe > Format Data > go back > Wipe > Advanced > Dalvik/Cache/System/Data > go back > flash system.img
Go back > Reboot> Recovery and do factory reset from Stock recovery"
I take it that I need to install my GAPPS package as well in this stage?
4
After factory reset from stock recovery the OS should boot and initiate...
Thanks again man for your help!
Click to expand...
Click to collapse
I have done as instructed yet there is am issue at the last step. I can boot into stock recovery but when I try and do a Factory Reset via the menu the reset only goes to 9% and gives a large orange/red exclamation mark.....so it did not finish. When I try and reboot and load the OS it goes into a boot loop and that is it.
MayhemIam said:
I have done as instructed yet there is am issue at the last step. I can boot into stock recovery but when I try and do a Factory Reset via the menu the reset only goes to 9% and gives a large orange/red exclamation mark.....so it did not finish. When I try and reboot and load the OS it goes into a boot loop and that is it.
Click to expand...
Click to collapse
Okay, reboot system. You can perform factory reset later (if needed).
---------- Post added at 19:17 ---------- Previous post was at 18:56 ----------
Please provide me the link where you downloaded Havoc OS
-Alf- said:
Okay, reboot system. You can perform factory reset later (if needed).
---------- Post added at 19:17 ---------- Previous post was at 18:56 ----------
Please provide me the link where you downloaded Havoc OS
Click to expand...
Click to collapse
No it's stuck on a bootloop Alf :crying:
MayhemIam said:
No it's stuck on a bootloop Alf :crying:
Click to expand...
Click to collapse
Don't panic! IMO it's time to clean your phone , download Service ROM
https://androidhost.ru/5NX
Unpack .zip package, find dload file and copy it to the SD card (without unpacking it!). Then turn off the phone and flash ROM using three button combo.
(instruction can be found in file ReleaseDoc).
Important: the process will erase all your data and will lock again the bootloader!
I will now try to install Havoc 3.1A and I will let you know, okay?
-Alf- said:
Don't panic! IMO it's time to clean your phone , download Service ROM
https://androidhost.ru/5NX
Unpack .zip package, find dload file and copy it to the SD card (without unpacking it!). Then turn off the phone and flash ROM using three button combo.
(instruction can be found in file ReleaseDoc).
Important: the process will erase all your data and will lock again the bootloader!
I will now try to install Havoc 3.1A and I will let you know, okay?
Click to expand...
Click to collapse
Well I can still dload back to my old EMUI 8.0 OS! I just did it again and it works. I can get back into my OS no probs. I have done this about 6 times today, lol. I really do not want to lock my bootloader again as it took me a long time to get it unlocked!
Thnx for the reply!
MayhemIam said:
Well I can still dload back to my old EMUI 8.0 OS! I just did it again and it works. I can get back into my OS no probs. I have done this about 6 times today, lol. I really do not want to lock my bootloader again as it took me a long time to get it unlocked!
Thnx for the reply!
Click to expand...
Click to collapse
Also just for me to understand. I have EMUI 8.0 running then I can't upgrade to a Android 9 Custom ROM?
MayhemIam said:
Also just for me to understand. I have EMUI 8.0 running then I can't upgrade to a Android 9 Custom ROM?
Click to expand...
Click to collapse
I'm not sure I fully understand your question, you cannot upgrade to A9 , you can flash Custom ROM based on A9 (which requires A8 OS).
Btw, I tried flash Havoc 3.1, 3.0, tried several TWRP, no luck. Flashed system.img from fastboot, nothing. It seems A-only version doesn't work on ANE. I have no idea what the problem is...
(hehe, R.I.P. English )
-Alf- said:
I'm not sure I fully understand your question, you cannot upgrade to A9 , you can flash Custom ROM based on A9 (which requires A8 OS).
Btw, I tried flash Havoc 3.1, 3.0, tried several TWRP, no luck. Flashed system.img from fastboot, nothing. It seems A-only version doesn't work on ANE. I have no idea what the problem is...
(hehe, R.I.P. English )
Click to expand...
Click to collapse
OK I can't upgrade to EMUI 9 but I can upgrade to a custom ROM which has Android 9 (through AB partition)?
"...you can flash Custom ROM based on A9 (which requires A8 OS)." Which means I can upgrade to any custom ROM which has Android 9 / 10?
What is the difference then between the following?
ARM64A
ARM64AB
-Alf- said:
Okay, reboot system. You can perform factory reset later (if needed).
---------- Post added at 19:17 ---------- Previous post was at 18:56 ----------
Please provide me the link where you downloaded Havoc OS
Click to expand...
Click to collapse
Oh snap man, I only saw the last part of your post now.
I tried the following ROMS.
Most of them was downloaded from SourceForge man.
Havoc-OS-v3.0-20191225-ARM64A-Unofficial.img.xz
Havoc-OS-v3.1-20200202-ARM64A-GSI.img
I have tried others as well but they were ARM64AB....
MayhemIam said:
OK I can't upgrade to EMUI 9 but I can upgrade to a custom ROM which has Android 9 (through AB partition)?
"...you can flash Custom ROM based on A9 (which requires A8 OS)." Which means I can upgrade to any custom ROM which has Android 9 / 10?
Click to expand...
Click to collapse
For example:
Pixel Experience, ROM for the Huawei P20 Lite
Contributors
DarkJoker360
Source Code: https://github.com/DarkJoker360
ROM OS Version: 9.0 Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8 unlocked bootloader & twrp
MayhemIam said:
OK I can't upgrade to EMUI 9 but I can upgrade to a custom ROM which has Android 9 (through AB partition)?
"...you can flash Custom ROM based on A9 (which requires A8 OS)." Which means I can upgrade to any custom ROM which has Android 9 / 10?
What is the difference then between the following?
ARM64A
ARM64AB
Click to expand...
Click to collapse
What is the difference then between the following?
ARM64A
ARM64AB
OK so the answer is
Use ARM64xA - when your phone is using Android 8.0 (EMUI 8.0)
Use ARM64xAB - when your phone is using Android 9 (EMUI 9.1)
-Alf- said:
For example:
Pixel Experience, ROM for the Huawei P20 Lite
Contributors
DarkJoker360
Source Code: https://github.com/DarkJoker360
ROM OS Version: 9.0 Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8 unlocked bootloader & twrp
Click to expand...
Click to collapse
Hi Alf,
I have abandoned ship to get HavocOS on my device
But I'm trying now the following AOSP Android 10 Q
https://www.getdroidtips.com/android-10-huawei-p20-lite/
I'm going to try and use this TWRP (twrp-3.4.0-0-anne.img)
Will let you know how it goes!
MayhemIam said:
Hi Alf,
I have abandoned ship to get HavocOS on my device
But I'm trying now the following AOSP Android 10 Q
https://www.getdroidtips.com/android-10-huawei-p20-lite/
I'm going to try and use this TWRP (twrp-3.4.0-0-anne.img)
Will let you know how it goes!
Click to expand...
Click to collapse
Getdroidtips? Really reliable source
I finally installed Havoc 3.8ab (latest version), I'm disappointed . No Music player, no Sound recorder (=no call recording) , no email client, Calendar etc. etc....
I think you should upgrade to EMUI 9.1 and try AB versions , hm?
-Alf- said:
Getdroidtips? Really reliable source
I finally installed Havoc 3.8ab (latest version), I'm disappointed . No Music player, no Sound recorder (=no call recording) , no email client, Calendar etc. etc....
I think you should upgrade to EMUI 9.1 and try AB versions , hm?
Click to expand...
Click to collapse
I would have really like to test an earlier version then which did not have all those missing features! It seemed to me that customization was very good on the ROM....
facepalm on Get Droid Tips....because the only tip I got from them is more than 12 hrs of trying to implement their crappy advice!
Ok I will upgrade to EMUI 9 then Alf.
Thanks for all the advice man and flashing along side me
Try Havoc 2.9 for Oreo , the Rom is just perfect . (own experience, tested on 8.0.0.126 )
INSTALL ON CLEAN OS (if your current OS is Custom ROM, flash stock ROM).
Download and unpack on your PC Havoc 2.9 arm64a:
https://sourceforge.net/projects/ha...90914-phhgsi_arm64_a-Official.img.xz/download
Flash extracted Havoc.img from fastboot using command
fastboot flash system (file name).img
Before booting up the ROM, you will need to perform a factory reset in stock recovery!!!
Reboot system.
In the Phh-Treble Settings-Huawei features, select fast charge 4000mA and Enable blurry UI workaround
If you want to install GAPPs or Magic (Magic v20.3 works without problems) , use TWRP by "ascuccio" (own experience), download link:
https://mega.nz/#!EsdTgYqZ!2QX9wgAhA653Dp2MkDTLPHa3tmFdNqmC5CDDHB-7f5Y
Screenshots:
https://mega.nz/#!1tlnlSyS!3SdAkZwf9miFVMkEXiq5Ypy3PcTOhuuohywk1ta-eXI
MayhemIam said:
Hi all,
I'm trying to install Havoc OS on my P20 lite (2018 model - ANE-LX1 8.0.0.0.135(C432)). My current version of EMUI is 8.0. So I need to install a A version of ARM and NOT AB.
The system image is
Havoc-OS-v3.1-20200202-ARM64A-GSI.img
I have TWRP 3.4.0 installed and working. PS, I have also tried this via fastboot (fastboot flash system Havoc-OS-v3.1-20200202-ARM64A-GSI.img.xz) with the same results
Before flashing the ROM and my GAPPS file (open_gapps-arm64-10.0-nano-20200808.zip). Via TWRP I wipe Dalvik/Cache/System/Data
Then I installed the ROM via TWRP install and selected .img install, there are no errors and the screen output says it is installed correctly.
Then I flashed the GAPPS mentioned above. After that I wipe Dalvik/Cache again.
And reboot....nothing happens. The phone boots back up and goes straight to TWRP again. It's like the ROM is not being initialized at all.
Any help would be appreciated.
Click to expand...
Click to collapse
You have tried to decrypt the data?
https://forum.xda-developers.com/honor-7x/development/mod-decrypt-data-emui-8-t3765403
Dego02 said:
You have tried to decrypt the data
Click to expand...
Click to collapse
No comment...
Disclaimer:
The use and installation of this software product is at the exclusive responsibility of the user.I am not responsible for any damage that may occur to your device resulting from the use of this software.This software product is "as is". Its first goal is to allow the xiaomi.eu Rom be installed via recovery.If you have any doubts regarding the above lines, you should not use or install it.
Recovery:
Unofficial release 3.7.0 for Xiaomi Mi 10T Lite and Redmi Note 9 Pro 5G devices. Status : StableVersion : 3.7.0.4GRelease Date : 2022.12.26Features:
Android 12 decryptionAndroid 13 decryption (Not tested by myself)FlashingAdbOtg (Not tested by myself)MtpBackup / Restore to / from microSDBackup / Restore through adbSideloadDevice boot Logo changerMagisk tools and theme from @ Brigudav (Not tested by myself)
Notes:
I concluded that custom roms (without Miui) are unable to decrypt /data with this recovery.Checking LineageOS and ArrowOS, it seems that they use a different encryption mode than Miui.I haven't found how to check on Twrp booting what encryption mode /data uses and adjust to it.Therefore, I have uploaded another release for non Miui devices.Can't tested by myself, I don't know if it decrypts fine.However, it is likely the Miui variant will work correctly on the rest.
About official TWRP: The current official release https://twrp.me/xiaomi/xiaomimi10i.html does not work anymore since Miui 13. Use instead this TWRP.
Twrp not decryping on miui 14: Please, read this post
Downloads:
Last release from Xda (Post #2)
Older releases from androidfilehost
Release 3.7.0.3F for CUSTOM NOT Miui rom from Xda (Post #2)
Installation:
Updating this Twrp release:Downloaded to phone:Click on Install and locate the .zip file.Downloaded to PC (no need to copy it to the phone): On phone: start install via ADB (sideload). On PC execute: adb sideload file_name.zip
Try without installing: (does not alter the phone unless you want to do)Extract recovery.img from .zip file downloadedEnter fastboot mode.Execute: fastboot boot recovery.img
Installing this for the first time:
Your bootloader must be open. Extract recovery.img from downloaded .zip file. Enter fastboot mode Execute: fastboot flash recovery recovery.imgCredits:
Team Win RecoveryMinimal Manifest PlatformAlexander Brigudav
Latest release 3.7.0.4G for MIUI rom
Release 3.7.0.3F for CUSTOM Non Miui rom
Nice work
Flashed R2 release, but it doesn't decrypt my data (it doesn't ask about my PIN). I am Polish xiaomi.eu translator and tester, and will ask Xiaomi.eu team about recovery ROM if the storage is decrypted... but can't for now...
Also, I was unable to boot to system after flash that TWRP, I had to use OrangeFox to be able to boot.
kacskrz said:
Flashed R2 release, but it doesn't decrypt my data (it doesn't ask about my PIN). I am Polish xiaomi.eu translator and tester, and will ask Xiaomi.eu team about recovery ROM if the storage is decrypted... but can't for now...
Also, I was unable to boot to system after flash that TWRP, I had to use OrangeFox to be able to boot.
Click to expand...
Click to collapse
Hello. I'm Spanish xiaomi.eu translator and user.
I don't understand how is possible your issue...
When I boot TWRP it asks me for the PIN to decrypt.
I would not have uploaded the image without testing it first.
Also the reboot buttons do what they say..
I have so far tested it without installing, because I have not yet dumped the Stock Recovery partition.
In theory, it is supposed to work exactly the same in boot mode as in flash mode.
Can you try it without installing?
As stated in the third disclaimer lines:
"Its intention is to allow the Rom xiaomi.eu be installed via recovery."
I retired here due to lack of free time and have only become involved now for this reason.
Best regards
tuxafgmur said:
Can you try it without installing?
Click to expand...
Click to collapse
Same situation, unfortunately... (except the reboot button which boots system, as i've just booted recovery, not flashed).
Edit: removed all screen lock methods I've set, still same. Looks like it isn't able to decrypt my data even without screen lock... Maybe something works differently between beta (which I use) and stable (which you use) release?
Edit2: logs there with set PIN as screen lock method https://miuipolska.pl/d/Orjon/gauguin_twrp.zip
Edit 3 24.07. 9:00am CEST: reboot to system works fine now after flashing your recovery, maybe the fact i've used "fastboot reboot-recovery" command was the reason to fail before...
kacskrz said:
Same situation, unfortunately... (except the reboot button which boots system, as i've just booted recovery, not flashed).
Edit: removed all screen lock methods I've set, still same. Looks like it isn't able to decrypt my data even without screen lock... Maybe something works differently between beta (which I use) and stable (which you use) release?
Edit2: logs there with set PIN as screen lock method https://miuipolska.pl/d/Orjon/gauguin_twrp.zip
Click to expand...
Click to collapse
Your logs do not seem to give relevant information about the issue.
It is clear that booting are completely ignoring the security lockout..
During the night I dumped and unpacked the stock recovery.
After studying it, I found nothing significant except that the kernel is not exactly the same as in boot.img.
I'm now downloading the latest weekly release to unpack it and compare vs stable release.
kacskrz said:
Edit 3 24.07. 9:00am CEST: reboot to system works fine now after flashing your recovery, maybe the fact i've used "fastboot reboot-recovery" command was the reason to fail before...
Click to expand...
Click to collapse
I'm not sure I understand what this paragraph means..
Regards.
Pixel Experience 12 data decrypted successfully.
Thanks
Lineage os data decrypted successfully.
Unfortunately, the weekly xiaomi.eu does not decipher the date.
For @kacskrz , @nolan2112 and anyone else using weekly xiaomi.eu:
I would appreciate the test of the new Release 3 I just uploaded.
Thanks in advance.
@tuxafgmur Unfortunately, nothing changed. I've posted logs on the xiaomi.eu thread.
The latest version also cannot decode the date. firmware weekly 22.7.21
New release 3.6.2.1B uploaded
In addition to some other minor changes,
fixed decryption on xiaomi.eu weekly.
New release 3.6.2.1B-R2 uploaded
No relevant changes.
Tested to flash xiaomi.eu from storage and sideload.
tuxafgmur said:
New release 3.6.2.1B-R2 uploaded
No relevant changes.
Click to expand...
Click to collapse
Everything is fine, the recovery is fully working. Thanks Amigo!
New release 3.6.2.1B-R3 uploaded
Revision
New release 3.6.2.1C uploaded
Format: Zip file to install from TWRP.
Some reviews.
Since xiaomi.eu rom replaces boot Logo on global devices, showing "Redmi"
this release includes options to switch logo between "MI" and "Redmi".
Each has two versions to choose from:
1 - Factory stock.2 - Like stock but hiding the padlock shown when bootloader is open.
The only recovery that works (and decrypts) on the newest MIUI 13 Android 12. Thank you!
Fantastic work, congratulations!
Loaded twrp with odin, then loaded aicp custom rom.
A year later loaded pixel pie custom rom
On power off the fone wouldn't restart in pixel, or twrp
I tried taking the Battery out and waiting 5 mis, 1hr, 3 hrs the fone still wont start.
BUT if the fone is left with the battery out for 3days it starts in both pixel and twrp no problem !!!
I also tried cleaning all partitions on twrp except sd card and loading my image of aicp which used to work, .. no change.
Anyone have an idea what this might be?
The phone is a samsung note 4 snapdragon originally on marshmallow android.
Im thinking of asking samsung to put marshmallow on again then reloading twrp and aicp
What happens when, instead of ACPI power off, you go to TWRP, reload TWRP, and then turn off the phone with TWRP?
If enabling works fine, the ACPI kernel may be to blame.
Be specific about which version of TWRP and ACPI you are using.
ze7zez said:
What happens when, instead of ACPI power off, you go to TWRP, reload TWRP, and then turn off the phone with TWRP?
If enabling works fine, the ACPI kernel may be to blame.
Be specific about which version of TWRP and ACPI you are using.
Click to expand...
Click to collapse
Sorry for delay, each restart takes 3 days!
Thankyou very much for your reply, appreciated,
Yes if close with twrp it opens without problem. If then close with power button have to wait 3 days before it restarts.
Note 4 snapdragon trite official Samsung phone bought uk originally marshmallow
Aicp _trite_q_15_unofficial 202 00 409 april 2020
previously used pexelrom, i dont know vesrion,it was pie though for note4 trite
Twrp 3 6 1 9.0 trite tar From https://eu.dl.twrp.me/trlte/
(the files were .img.tar I assumed this is ok for odin, battery removed and boot first into recovery)
Pleeas can you give me overview of kernal problem,
.........................
The aicp rom worked except battery ran down on pwer off (known fault) Image taken.
Tried pixel rom with incuded gapps pie version and couldnt get twrp (to make image)
Used odin to rload twrp 3 6 1 9.0 trite tar .img.tar file
reloaded my image of aicp
......................
limit of my knowledge here!
Could piexel rom have locked something for future custom roms using twrp
Could the later version of twrp be worse
I assume version of odin twrp are for the original phone (samy note4 snapdragon) not the last custom rom
.... Is twrp in a separate partition that isnt wiped by loading custom rom with twrp? Isit this that is the problem, or someting in the custom rom,. Ive got this far without rooting the phone,has pixel altered this.
......................
If you are installing a new/different custom rom, it's best to do a full wipe with internal memory included.
For many phone models, twrp 3.6.x performs worse than 3.5.2.x.
Since the twrp kernel is good for shutting down the phone, change the ROM to one that also shuts down the phone well.
Read the first post of the thread very carefully and understandingly:
[ROM][UNOFFICIAL][11] LineageOS 18.1 [tblte][trlte][trlteduos]
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS...
forum.xda-developers.com
and install LineageOS 18.1 by @ripee.
gwm121 said:
Sorry for delay, each restart takes 3 days!
Thankyou very much for your reply, appreciated,
Yes if close with twrp it opens without problem. If then close with power button have to wait 3 days before it restarts.
Note 4 snapdragon trite official Samsung phone bought uk originally marshmallow
Aicp _trite_q_15_unofficial 202 00 409 april 2020
previously used pexelrom, i dont know vesrion,it was pie though for note4 trite
Twrp 3 6 1 9.0 trite tar From https://eu.dl.twrp.me/trlte/
(the files were .img.tar I assumed this is ok for odin, battery removed and boot first into recovery)
Pleeas can you give me overview of kernal problem,
.........................
The aicp rom worked except battery ran down on pwer off (known fault) Image taken.
Tried pixel rom with incuded gapps pie version and couldnt get twrp (to make image)
Used odin to rload twrp 3 6 1 9.0 trite tar .img.tar file
reloaded my image of aicp
......................
limit of my knowledge here!
Could piexel rom have locked something for future custom roms using twrp
Could the later version of twrp be worse
I assume version of odin twrp are for the original phone (samy note4 snapdragon) not the last custom rom
.... Is twrp in a separate partition that isnt wiped by loading custom rom with twrp? Isit this that is the problem, or someting in the custom rom,. Ive got this far without rooting the phone,has pixel altered this.
......................
Click to expand...
Click to collapse
Thankyou ze for succinct helpful info.
I am reading very carefully as you suggest
In this section im unsure about ..........."type fastboot reboot" ...
Recovery is to get to twrp right? vol up pwr home with note 4, that would bring up menus on twrp, .there is a menu box for reboot.. Have I undersood this please?
I can follow ypour suggestion tomload an earlier version of twrp
is it possible a later twrp has anything to do with the loading kernal of the rom
"""Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."""