Related
Hi friends, every time I try to root the 11.0.1.0 Global, my phone end up in Bootloop (goes to TWRP every time). I tried to flash disable dm verity, but same results.
I'm using TWRP unnoficial (twrp-3.3.1-25-raphael-mauronofrio.img) but tried with the official too, same results.
This time I will try to flash Magisk v18, or older.
I'm using Mi 9T Pro Global Rom.
Clear Cache and Dalvik cache in TWRP
XblackdemonX said:
Clear Cache and Dalvik cache in TWRP
Click to expand...
Click to collapse
Okay, now I'm unrooted, what steps I need to do? TWRP >> Flash Magisk >> Flash DM Verity >> Wipe Cache/Dalvik? Or only Flash Magisk via TWRP and Wipe Caches?
Edit: same results, tried to flash magisk and clear cache and dalvik, bootloop again.
Edit²: tried to do a Factory Reset on TWRP and system booted up normally, Magisk Manager says that I'm rooted, but I can't install any module. Tested AdAway do get root, and all ok.
Edit³: Magisk Manager requested for some "additional files", I pressed to install and he rebooted the phone, now I'm stuck again in TWRP. Tried to clear Cache and Dalvik cache, same results.
RobertPirainoBR said:
Hi friends, every time I try to root the 11.0.1.0 Global, my phone end up in Bootloop (goes to TWRP every time). I tried to flash disable dm verity, but same results.
I'm using TWRP unnoficial (twrp-3.3.1-25-raphael-mauronofrio.img) but tried with the official too, same results.
This time I will try to flash Magisk v18, or older.
I'm using Mi 9T Pro Global Rom.
Click to expand...
Click to collapse
install magisk 19.3
Video install
https://drive.google.com/file/d/16vDfZDWBgtY8_ECB8aRWNed_6mqctY5T/view
@redmiK20ProIndonesia
RobertPirainoBR said:
Hi friends, every time I try to root the 11.0.1.0 Global, my phone end up in Bootloop (goes to TWRP every time). I tried to flash disable dm verity, but same results.
I'm using TWRP unnoficial (twrp-3.3.1-25-raphael-mauronofrio.img) but tried with the official too, same results.
This time I will try to flash Magisk v18, or older.
I'm using Mi 9T Pro Global Rom.
Click to expand...
Click to collapse
To install magisk on the global version, you must first remove the encryption.
1. return the system to its original state so that it boots, most likely it is flash via MiFlash (or via twrp ROM version for twrp)
2. flash DFE-script, reboot from twrp in twrp ( https://drive.google.com/open?id=1mFVdDlnp32g2AjdKlMq6tZcqK0krP-js )
3. format data-yes, reboot in system
4. check in the settings that encryption is disabled
5. flashing magisk in twrp
kancutluh said:
install magisk 19.3
Video install
https://drive.google.com/file/d/16vDfZDWBgtY8_ECB8aRWNed_6mqctY5T/view
@redmiK20ProIndonesia
Click to expand...
Click to collapse
alex9yust said:
To install magisk on the global version, you must first remove the encryption.
1. return the system to its original state so that it boots, most likely it is flash via MiFlash (or via twrp ROM version for twrp)
2. flash DFE-script, reboot from twrp in twrp ( https://drive.google.com/open?id=1mFVdDlnp32g2AjdKlMq6tZcqK0krP-js )
3. format data-yes, reboot in system
4. check in the settings that encryption is disabled
5. flashing magisk in twrp
Click to expand...
Click to collapse
I will try this now. I can do this with dirty flash? I'm able to boot system, with Magisk v20.1 installed and partially working (if I install the additional content in Magisk Manager will Bootloop again, and I can't install modules).
RobertPirainoBR said:
I will try this now. I can do this with dirty flash? I'm able to boot system, with Magisk v20.1 installed and partially working (if I install the additional content in Magisk Manager will Bootloop again, and I can't install modules).
Click to expand...
Click to collapse
You can flash the magisk-uninstaller 20.1.
and after format data-yes all your data will be gone.
Go to /data/adb/magisk/chromeos find "futility" file. Permission 644 for it.
Go to /data/adb/magisk find "BusyBox" file and permission 664 for it.
Reboot and done.
In future, when you flash any rom on k20 pro. Remember that do it if you flash magisk.
Good luck!
(Solution from 4pda)
shinigami_tsin said:
Go to /data/adb/magisk/chromeos find "futility" file. Permission 644 for it.
Go to /data/adb/magisk find "BusyBox" file and permission 664 for it.
Reboot and done.
In future, when you flash any rom on k20 pro. Remember that do it if you flash magisk.
Good luck!
(Solution from 4pda)
Click to expand...
Click to collapse
Wow this seems to have worked!
shinigami_tsin said:
Go to /data/adb/magisk/chromeos find "futility" file. Permission 644 for it.
Go to /data/adb/magisk find "BusyBox" file and permission 664 for it.
Reboot and done.
In future, when you flash any rom on k20 pro. Remember that do it if you flash magisk.
Good luck!
(Solution from 4pda)
Click to expand...
Click to collapse
This is great. I downloaded magiskhide and had to enable it through terminal then it showed up in the drop down browser for magisk but wasnt in modules list of magisk. None of the modules seem to download and go there. Is it supposed to be like that?
Vanmanman said:
This is great. I downloaded magiskhide and had to enable it through terminal then it showed up in the drop down browser for magisk but wasnt in modules list of magisk. None of the modules seem to download and go there. Is it supposed to be like that?
Click to expand...
Click to collapse
Same here, trying to install modules but don't show up on modules tab.
RobertPirainoBR said:
Same here, trying to install modules but don't show up on modules tab.
Click to expand...
Click to collapse
Yeap!
1. Flash magisk via twrp (suggest pitchblack)
2. Delete 2 files
3. Reboot (→solved bootloop)
4. Open magisk manager and update (if failed, close app and try again and agian) → after auto reboot (after 5 seconds), can solved issue "can not flash modules - of course with all modules flashed, it's showed in list).
RobertPirainoBR said:
Same here, trying to install modules but don't show up on modules tab.
Click to expand...
Click to collapse
Solution is here https://forum.xda-developers.com/mi-9t/help/phone-stuck-bootloop-try-to-install-t4007259
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/and...crypt-t3817389
Vanmanman said:
Solution is here https://forum.xda-developers.com/mi-9t/help/phone-stuck-bootloop-try-to-install-t4007259
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/and...crypt-t3817389
Click to expand...
Click to collapse
doesn't work, tried and stuck on boot loop
Vanmanman said:
Solution is here https://forum.xda-developers.com/mi-9t/help/phone-stuck-bootloop-try-to-install-t4007259
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/and...crypt-t3817389
Click to expand...
Click to collapse
I tried in many ways but did not succeed
Khaledms said:
I tried in many ways but did not succeed
Click to expand...
Click to collapse
Not sure sorry. I ended up waiting for a better version of Magisk to come out. Have you tried Magisk 20.3 on K20/mi96t android 10 miui 11?
Hi guys,
Try to format data in TWRP before the first reboot. Remember, this will clear your data.
It is very easy to get bootloop because of cryptography.
Good luck!
UNLOCK BOOTLOADER & ROOT DEVICE
1. Unlock Bootloader (Xiaomi procedure, 7 days via MI Unlock tool)
https://fossbytes.com/how-to-unlock-bootloader-on-xiaomi-devices-using-mi-unlock-tool/
2. Fastboot flash recovery TWRP and root the android 9 rom
(based on https://www.cyanogenmods.org/forums/topic/twrp-download-for-mi-mix-3-5g-and-rooting-guide/)
2.1 Install ADB for Windows and Xiaomi Drivers
2.2 Download TWRP for MI MIX3 5G Android 9 PIE - twrp-3.3.1-0-andromeda.img
https://androidfilehost.com/?fid=6006931924117900528
(based on https://forum.xda-developers.com/showthread.php?t=3941867)
2.3 Rename file to recovery.img and put it into ADB folder on Windows
2.4 Turn off the phone, Reboot to Fastboot (Volume Down + Power)
2.5 Plug the phone into computer
2.6 Open Windows CMD
2.7 Go to your ADB directory
2.8 Type the commands in cmd
cd C:/adb
fastboot devices
fastboot flash recovery recovery.img
2.9 Download Disable Force Encryption and Magisk Zip
https://www.cyanogenmods.org/downloads/disable-force-encryption-twrp-flashable-zip-treble/
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2.10 Copy the files to USB memory stick formatted to FAT32, you should have two files:
Magisk-v20.3.zip
DisableForceEncryption_Treble.zip
2.10 Turn on phone to recovery (Volume Up + Power)
2.11 Go to Menu > Wipe > Format Data > "yes" (this will format the data)
2.12 Go to Menu > Advanced > Fix Contents
2.13 Plug in your USB stick with files via OTG USB C connector
2.14 Go to Menu > Install > Select Storage > OTG
2.15 Select Magisk-v20.3.zip
2.16 Add more zips and select DisableForceEncryption_Treble.zip
2.17 Flash the zips and reboot device
UPDATE FOR TWRP
To gain root you may now only boot the recovery instead of flashing and proceed with flashing Magisk and Disable Force Encryption.
# fastboot boot recovery.img
TWRP 3.3.1-1 Xiaomi Mi Mix 3 5G (andromeda) by mauronofrio:
- Added Android 10 Support;
- Fixed compatibility.zip errors;
- Make the TWRP able to boot directly from fastboot;
- Removed TWRP app;
- Added dtbo and persist target to flash image menu;
- Fixed some problems with Stock ROMs flashing.
Download TWRP: https://androidfilehost.com/?fid=4349826312261701065
Thanks to @mauronofrio
## QUALCOMM DIAGNOSTIC PORT AND TOOLS
(based on https://forum.xda-developers.com/oneplus-7-pro/help/force-enable-volte-vowifi-t3934227)
1.1 Download
https://androidfilehost.com/?fid=11410963190603864074
https://androidfilehost.com/?fid=11410963190603912872
QPST_2.7.474.zip
QUD.WIN.1.1 Installer-10037.3 Setup.zip
Just use the standard settings and click on OK, next,
1.2 OPEN DIAGNOSTIC PORT FOR THE SESSION FOR QPST (WINDOWS CMD ADB)
cd C:/adb
adb devices
adb shell
su (you need to add root permisions on android screen)
setprop sys.usb.config diag,serial_cdev,rmnet,adb
1.3 Once The Port is up you can use your Qualcomm Tools.
1.4 For example you can change the VOLTE/VOWIFI settings with PDC Tool
Select your device, right click on "Commercial" and deactivate Sub0 and Sub1
Click on Oversea-Commercial_DS again and click on remove -- DO NOT CLICK REMOVE, JUST DE-ACTIVATE IT - your settings stick after a reboot, so no longer need to remove the profile (at least on my device my profiles stick, also makes it easier to go back to default)
## FORCE ENABLE VOLTE AND VOWIFI BUTTONS IN ANDROID
cd C:/adb
adb devices
adb shell
su (you need to add root permisions on android screen)
setprop persist.dbg.ims_volte_enable 1; setprop persist.dbg.volte_avail_ovr 1; setprop persist.dbg.vt_avail_ovr 1; setprop persist.dbg.wfc_avail_ovr 1
######################## CODES FOR THE DIALER #####################
1. Diagnostic codes:
*#*#6484#*#*
2. Testing
*#*#4636#*#*
3. Calendar
*#*#225#*#*
4. Google Play services
*#*#426#*#*
5. Rlz Debug Ul.
*#*#759#*#*
6. Imei Information
*#06#
Enter these codes into the Dialer to enable the options in Settings. (Settings < SIM Cards & mobile networks < Sim Card Settings < VoLTE Enabled/Make Calls using WLAN) . THEY ARE ENABLED BY DEFAULT
VoLTE *#*#86583#*#*
VoWIFI *#*#869434#*#*
##### FLASH ROM AGAIN IF ANYTHING FAILS VIA FASTBOOT ###
01. You need to have unlocked bootloader
02. Download latest ROM based on your model (mine is 5G EEA n78)
Mi MIX 3 5G EEA Stable Fastboot V10.3.21.0.PEMEUXM 9.0 Download 2.5 GB
https://xiaomifirmwareupdater.com/miui/andromeda/
03. Download Mi Flash Tool
https://www.xiaomiflash.com/
04. Open the Mi Flash Tool, install drivers (if the install fails go to Mi Flash directory and create folder logs and log; open app again and install drivers)
05. Unpack the rom fastboot tgz
06. Select the Folder where the rom is unpacked (it should containg numerous of flash files)
07. Tick the Clear Data at the bottom (don't choose the clear data and lock cause it will lock your bootloader again)
08. Turn off the phone, Reboot to Fastboot (Volume Down + Power)
09. Plug the phone into computer
10. Click refresh, phone should be visible
11. Click flash
12. After successfull flash there could be an error fastboot lock (don't bother since you want to be unlocked)
13. If you want root flash twrp and magisk again
Thank you so much for this guide! Can I flash gsi rom with this? Sorry for the noob question
Jktfong said:
Thank you so much for this guide! Can I flash gsi rom with this? Sorry for the noob question
Click to expand...
Click to collapse
I have not tried to load the GSI ROM on that model. I guess there was some other topic under ROM development opened for that
https://t.me/mimix3_5G feel free to join this telegram group chat if you need any help we are all running a custom gsi with aosp 9 and 10 (pixel experience) @mxtuu222
Since last 20.1.9 update lost ecryption in twrp. Installed the latest 3.3.1.1.perseus. since then got loops to twrp. But if i try to launch
fastboot boot C:\mimix\twrp-3.3.1-1-perseus.img it boots to the system.
How to fix it?
dont want to use my PC to start the system every time.
Regards
Most probably you get bootloop, because after the update the partition was encrypted, you need to either flash DisableForceEncryption_Treble.zip or make a backup and install fresh OS with the guide from scratch,
Hey. help me with my problem inversion of the axes of the accelerometer https://forum.xda-developers.com/android/help/inversion-rotated-x-y-axes-accelerometer-t4059277
flash persist did not help me
Root Mix 3 5G
Hello,
i have some problems at point of rooting. my phone accept twrp recovery it's fully working and stays as recovery but when i try to istall magisk 20.4, 19.3 or whatever it will stuck at Mi screen and won't boot. when i reflash original boot img it will boot again but no root. can someone help me?
thank you
Thank you so much for this guide Without it I would have gone a little crazy trying to do a simple reset and update of my phone Saved for reference and I always come back.
This is a bit late but why not. THIS IS A COMPILATION OF ALL THE OS METHODS YOU NEED FOR THE OP6/6T.
ENJOY my guide
DISCLAIMER:
*I am not responsible for bricked devices, damage to your device*
Sorry for a long list of methods, some work for others and some don't. But I recommend to pick a method and stick to it. Maybe read the part at the top as some have notes about mine or someone else's experience/recommendation. Don't skip steps and follow each step.
If stuck, just ask and I or anyone else will try and help
I am here to post methods for anyone who is interested/need help. I have tested these myself and helped others who may be struggling
Download
The guide has loads of files/ zips/ tools to use/flash/install. But no worries as everything can be downloaded and there are links AT THE BOTTOM OF THIS THREAD (NOT COMMENTS) to where to download:
SDK Platform Tools (Fastboot tools) from Developer Android
TWRP from mauronofrio
Magisk from topjohnwu
Gapps (Google Apps) from NikGapps. I recommend omni for ROMs that don't include Gapps.
Fastboot ROM for OP6 + OP6T from mauronofrio
MSMDownload tools for OP6 + OP6T from Some_Random_Username
IMPORTANT NOTES!
YOU REQUIRE Platform Tools (Fastboot Tools) IN ORDER TO USE THE METHODS IN THIS GUIDE AS TWRP NEEDS TO BE INSTALLED!
YOU NEED TO HAVE A UNLOCKED BOOTLOADER AS WELL!
For GAPPS, u can use the same or a updated version of the package. But has to be the same type u used to install it like (stock, full, Omni, basic, etc). ONLY FLASH/INSTALL IF the RESTORE SCRIPT DIDN'T SHOW UP during a DIRTY FLASH/UPDATE AND ONLY FLASH AFTER REBOOTING TO RECOVERY AFTER FLASHING/INSTALLING A OS/BUILD ZIP FILE!
How to get Platform Tools
These tools are used to install TWRP, to unlock the bootloader of your device and is needed to use the METHODS in this guide.
Download the platform tools.zip of your software platform (Mac, Windows, Linux)
Extract the platform-tools.zip
To use it go into your platform-tools folder
Press shift + right-click and choose command prompt or PowerShell
Connect your device when it's in fastboot mode and done
How to install TWRP
Sadly this Guide is for Windows, but other platforms like Mac or Linux can be found online.
YOU CAN USE THIS METHOD TO INSTALL A NEWER VERSION OF TWRP TOO
You need to have downloaded Platform Tools which the link is attached below.
Transfer the TWRP.img file into the platform-tools folder
Now transfer TWRP.zip into your device's internal storage. (connect -> allow file transfer -> drag and drop files)
If you want root download and transfer magisk.apk and the link is supplied below. Also, RENAME from .apk to .zip
Now we must boot into fastboot mode. (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Now connect your device to a Windows device
Press shift + right-click. Choose command prompt or PowerShell
Enter "fastboot devices" and your device should be displayed if it's connected
Type "fastboot boot twrp" file name (do twrp + press tab) and press enter
Then you should be booted into TWRP
Enter the password and swipe to allow modifications
Press install and find your TWRP.zip file
Swipe to confirm Flash
If you want root do this
Press the back arrow and find your magisk.zip
Swipe to confirm Flash
Reboot to the system and done
Otherwise, just reboot to system. Up to u
Installing a Custom ROM
Install Custom ROM on OP6T from OOS
Make sure u have BACKED UP your device and have the latest OOS installed in both slots. If u do, go to Method 3.
If u have finalize.zip, go to Method 2.
Method 1
If u don't have OOS installed in both slots or finalize.zip, use this method.
Transfer OOS.zip file, TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to Bootloader
Boot TWRP
Flash OOS + TWRP
reboot recovery
Flash OOS + TWRP
Reboot recovery
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Reboot to system
Otherwise, just Format data -> reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Method 2
If u have finalize.zip, do this method. Using finalize is way quicker as there's less flashing and rebooting.
Transfer OOS.zip file, finalize.zip, TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to Bootloader
Boot to TWRP
Flash OOS + finalize
Boot to Bootloader
Boot to TWRP
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Reboot to system
Otherwise, just Format data -> reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Method 3
Once you have installed OOS in both slots do this part.
Transfer TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to Bootloader
Boot to TWRP
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Reboot to system
Otherwise, just Format data -> reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Installing Custom Rom not from OOS
You can use finalize method or just flash OOS + TWRP way. The finalize way is there for some who like less flashing and rebooting.
Using the methods in Install Custom ROM on OP6T from OOS
Using the old way, use Method 1
Using finalize.zip, use Method 2
Remember to factory reset (wipe, but no need to wipe internal storage)
Backing Up OOS and Custom ROM
Make sure u have installed the latest TWRP version from mauronofrio
You should use TitaniumBackup or Migrate to back up your apps and contacts.
Also, have a copy of your Internal Storage folders if u have important files.
TWRP Backup backs up your OS like Apps, settings and set up, but not internal storage.
NEVER BACKUP SYSTEM AND VENDOR! ONLY SYSTEM.IMG or VENDOR.IMG IF YOU HAVE TO!
Restoring it makes going back way easier like you have never left
Or you can go manually and try and restore everything, but why do that when you got TWRP?
I do both ways of backing up
Backing up OOS
Boot TWRP recovery
Choose Backup
Choose boot, data. YOU DO NOT NEED TO BACKUP System.img and Vendor.img!
Swipe to backup
Once done, either boot to system or mount
Transfer the whole TWRP folder onto a storage device
Done
Backing up a Custom ROM
Boot TWRP recovery
Choose Backup
Choose boot, data, system.img, vendor.img
Swipe to backup
Once done, either boot to system or mount
Transfer the whole TWRP folder onto a storage device
Done
Restoring OOS and Custom ROM
Restoring OOS TWRP Backup
To restore OOS use either fastboot ROM or MSM. Fastboot is the fastest and easiest way if u have a TWRP backup which there's a method to how to make one in this guide. BUT if you are restoring to go back to stock OOS then use MSM
I use Fastboot ROM restore for that too as we are restoring our data anyways and also for switching/installing a custom ROM. Much easier in my experience.
DOWNLOAD FULL ZIP OF OOS version of your TWRP backup otherwise you could risk doing the whole restore method again OR setup from SCRATCH! IF you aren't restoring a TWRP backup, I recommend either TRANSFER or DOWNLOAD via WiFi or oxygen updater, a UPDATED version of OOS AFTER doing either fastboot ROM or MSM restore methods. As they restore a old version of OOS!
Restoring using Fastboot ROM
Download fastboot ROM of your choice using the link in the Download Link section.
Extract/ un-zip
Boot your device into fastboot mode (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Click flash-all.bat
Restoring using MSM Download Tool
Download latest MSM version of your choice using the link in the Download Link section.
Extract/ un-zip
Click on MSM tool .exe file
Turn off device
HOLD BOTH volume buttons
Connect your phone
Wait for your device to be connected and it should show as green
Click verify to check and press start
Wait till phone reboots
The setup device and u can carrying on restoring your device if u don't want a unlock bootloader or return to what your device was like before.
Go into developer options
Allow OEM unlocking
Reboot to bootloader
Enter "fastboot devices" to check your device is connected
Enter "fastboot oem unlock"
Swipe for yes
Then it will reboot again
continue to the next method
For both fastboot and MSM
Once booted into system, set it up and update to OOS version of your TWRP backup.
Download the full zip using the link in the Download Link section.
Transfer the OOS .zip to internal storage.
Go into settings -> system update -> Update via local upgrade -> find zip file and press install
Do this twice to make sure you have installed that version of OOS in both slots
Boot to bootloader
Boot TWRP
Install TWRP
Reboot recovery
Transfer whole TWRP Folder into internal storage
Restore only boot and data
Swipe to restore
If you have backed up your internal storage folders do this
Reboot to recovery
Transfer all your internal storage folders
Reboot to system and done
Otherwise, just reboot to system. U can update OOS as well if it's outdated. The method is below to update OOS with ROOT. Up to u
RESTORING TWRP BACKUP HAS ISSUES ON THESE ROMs
CrDroid (Method 1 + 2 don't work). Method 3 works (install Gapps if the ROM doesn't have it!)
Restoring a Custom ROM TWRP backup 1
I tried using this method, but it didn't work for me.
You can use this method to switch ROMs too
Boot TWRP Recovery
Flash OOS + Finalize
Boot to bootloader, boot TWRP
Flash TWRP
Reboot Recovery
Transfer twrp backup
Restore System.img, Vendor.img and boot
Boot to system and setup system
Reboot to recovery
Restore data
Reboot system. Done
I had an issue with this method where rebooting system it was from fresh and my data didn't restore. If this happened to you, then do method 2 (Restoring a Custom ROM TWRP Backup 2)
Restoring a Custom ROM TWRP Backup 2
The first method didn't work for me. But this method did
Restore fresh like you're going back to OOS.
Choose one method. Fastboot or MSM method.
I prefer the fastboot method.
Download fastboot ROM using the link in the Download Link section.
Extract/ un-zip
Boot your device into fastboot mode (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Click flash-all.bat
Once booted into system, set it up briefly and DO NOT RESTORE ANYTHING.
Boot to bootloader
Boot TWRP
Install TWRP
Reboot recovery
Transfer whole TWRP Folder into internal storage
Restore everything (System.img, vendor.img, boot.img and data)
Swipe to restore. If data couldn't restore then boot system, setup system, boot TWRP and restore data.
Reboot system. The first reboot might go dodgy and it did for me.
Reboot system and transfer all your internal storage stuff
done
If this did not work still. Then do the 3rd method...
Restoring a Custom ROM TWRP backup 3
If the previous 2 methods has failed for you. Then try this.
Restore fresh like you're going back to OOS.
Choose one method. Fastboot or MSM method.
I prefer the fastboot method.
Download fastboot ROM using the link in the Download Link section.
Extract/ un-zip
Boot your device into fastboot mode (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Click flash-all.bat
Once booted into system, set it up and update to OOS version of your TWRP backup.
Download the full zip using the link in the Download Link section.
Transfer the OOS .zip to internal storage.
Go into settings -> system update -> Update via local upgrade -> find zip file and press install
Do this twice to make sure you have installed that version of OOS in both slots
Transfer TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to bootloader
Boot TWRP
Install TWRP
Reboot to Recovery
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Otherwise, just Format data -> reboot to recovery. Up to u
Reboot Recovery
Transfer twrp backup
Restore data
Reboot system. Done
If it still fails, repeat steps 1 to 15. But restore everything and you should be back on your custom ROM like you never left.
Updating OOS and Custom ROM
Update OOS with Root (Magisk)
Always do a TWRP backup before updating your OS in case
Download the full zip file of the latest OOS, transfer the zip file to internal storage NOT IN ANY FOLDER
Download and transfer twrp.zip file to internal storage
Go into settings, system update, update via local upgrade and choose the file
Wait till the installation has finished. If failed TRY AGAIN!
DO NOT REBOOT!
Go into Magisk Manager, modules
Find the twrp zip file and install TWRP
DO NOT REBOOT!
Go into Magisk Home
Press install
Press install via inactive slot
Reboot system and done
You will reboot into the next slot
You don’t have to repeat the installation to install the latest OOS in the other slot. But you should and I use this method many times and has never let me down.
Updating OOS without root
Go to System Update -> find the update install and reboot.
Or download the zip -> transfer to internal storage -> update via local upgrade -> reboot and done
Update a Custom ROM
Method 1
Always do a TWRP backup before updating your OS in case
Use this method just to update the ROM.
Boot recovery
Flash new version + twrp
Reboot recovery
Flash new version + twrp
If the ROM doesn't have GApps included,
The restore script should show up during the installation of the new ROM.zip
BUT if the restore script DIDN'T pop up do this
Reboot to recovery
Flash Gapps if not included
Reboot to system
Otherwise, reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Method 2
This method uses finalize.zip
Boot recovery
Flash new version + finalize + twrp
If the ROM doesn't have GApps included,
The restore script should show up during the installation of the new ROM.zip
BUT if the restore script DIDN'T pop up do this
Reboot to recovery
Flash Gapps if not included
Reboot to system
Otherwise, reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Updating vendor
Use Method 1 and 2 for ROMs with Gapps. Use Method 3 for ROMs with no Gapps included.
Method 1
If u haven’t updated your Custom ROM and your Vendor… You can use this method to update both or just the vendor.
Boot recovery
Flash OOS + twrp
Reboot recovery
Flash OOS + twrp
Reboot recovery
Flash Custom ROM + twrp
Reboot recovery
Flash Custom ROM + twrp
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system
Method 2
This method uses finalize.zip
Boot recovery
Flash OOS + finalize + twrp
Reboot recovery
Flash Custom ROM + finalize + twrp
Otherwise, reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system
Method 3
This method is for ROMs with no Gapps included
You can use this method as well for updating to a vendor that has a NEWER ANDROID version like from OOS 10 to OOS 11 vendor.
Boot recovery
Flash OOS + Custom ROM + twrp
Reboot recovery
Flash OOS + Custom ROM + twrp
If u flashed GApps, the restore script should show up during the installation of the ROM.zip
If the GApps script didn't show up do this
Otherwise, skip step 3
Flash Magisk if u want root, otherwise skip step 2
Reboot to recovery
Flash Magisk
Flash Gapps
Reboot to system and done
Download Links:
SDK Platform Tools (Fastboot Tools) Here
OOS versions for OP6 (under Signed Flashable zips) Here
OOS versions for OP6T (under Signed Flashable zips) Here
TWRP for OP6 Here
TWRP for OP6T Here
Magisk Here
NikGapps Here
Stock Fastboot ROM for OP6 Here
Stock Fastboot ROM for OP6T Here
MSMDownloadTool for OP6 Here
MSMDownloadTool for OP6T Here
TitanumBackup App Here
Migrate App Here
Credits:
@mauronofrio For his amazing work on the TWRP recovery and Stock Fastboot ROMs for OP6/6T
@topjohnwu For his work on Magisk
@Nikgapps For their work on creating Gapps
@Some_Random_Username For his Collection of MSMDownloadTool for OP6/6T
@OPTeam For the collection of OOS zips for OP6/6T
@dreamwhite For the method (Method 3) of updating the vendor which works wonders for ROMs with no GApps included
First
Hey Guys,
Need a some expert advice please.
Long story short. I need to replace my OP 6T McLaren's battery as I have serious degradation in battery capacity (73% Serious Loss), meaning the battery is no longer charging to 3700mAh, max charging atm is around 2600mAh, which it drains very quickly. FYI Anything above 80% is the limit for average performance, >90% is best. You can use the OP Diagnostic App 1.0.0.9 to determine your own status. Does not work on all OP devices above 6 btw. Maybe other versions work. Anyway, will be getting OP to change the battery (no real local guys I can trust tbh, all Sammy & Apple guys...) and they want me to Factory Reset the device (complete wipe including internal storage (backed up already to PC)) before sending the device to the OP Repair Center for the obvious reasons of Privacy & Security.
On my device, I have a suite of apps that are no longer available to install with APK specially Signed, but won't be able to re-install (long story & can discuss in a PM more if there is an interest to help on this). These APK will not work any other way, I've tried! This being said, I know that TWRP Nandroids work well & have been doing these backups for yrs and have restored backups with these apps installed and it works! But I have not had to restore any as of late and TWRP Backup has somewhat changed in regards to the partition selections available. See TWRP Options pic below.
When OP returns the device to me, it will mostly likely be on the latest release of 10.3.11 (Hopefully).
Here is the current setup and runs perfectly!
OOS 10.3.11
TWRP: twrp-3.5.2_9-0-fajita
Magisk 23
The last Nandroid done today (No PW for good measure, but secured locally offline), I selected all partitions. Is this the best way to insure I get my full device backup restored?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm guessing that I will have to, Unlock the Bootloader, reinstall TWRP same version the Nandroid was created with in order to restore that backup.
Looking forward to hearing from you guys to make the best decision before proceed with the factory reset.
Thanking you all in advance for your time & assistance!
Cheers!
plepew said:
Hey Guys,
Need a some expert advice please.
Long story short. I need to replace my OP 6T McLaren's battery as I have serious degradation in battery capacity (73% Serious Loss), meaning the battery is no longer charging to 3700mAh, max charging atm is around 2600mAh, which it drains very quickly. FYI Anything above 80% is the limit for average performance, >90% is best. You can use the OP Diagnostic App 1.0.0.9 to determine your own status. Does not work on all OP devices above 6 btw. Maybe other versions work. Anyway, will be getting OP to change the battery (no real local guys I can trust tbh, all Sammy & Apple guys...) and they want me to Factory Reset the device (complete wipe including internal storage (backed up already to PC)) before sending the device to the OP Repair Center for the obvious reasons of Privacy & Security.
On my device, I have a suite of apps that are no longer available to install with APK specially Signed, but won't be able to re-install (long story & can discuss in a PM more if there is an interest to help on this). These APK will not work any other way, I've tried! This being said, I know that TWRP Nandroids work well & have been doing these backups for yrs and have restored backups with these apps installed and it works! But I have not had to restore any as of late and TWRP Backup has somewhat changed in regards to the partition selections available. See TWRP Options pic below.
When OP returns the device to me, it will mostly likely be on the latest release of 10.3.11 (Hopefully).
Here is the current setup and runs perfectly!
OOS 10.3.11
TWRP: twrp-3.5.2_9-0-fajita
Magisk 23
The last Nandroid done today (No PW for good measure, but secured locally offline), I selected all partitions. Is this the best way to insure I get my full device backup restored?
View attachment 5319753
I'm guessing that I will have to, Unlock the Bootloader, reinstall TWRP same version the Nandroid was created with in order to restore that backup.
Looking forward to hearing from you guys to make the best decision before proceed with the factory reset.
Thanking you all in advance for your time & assistance!
Cheers!
Click to expand...
Click to collapse
Idk if u have read Mauronofrio's XDA thread on TWRP backups. BUT NEVER BACKUP OR RESTORE SYSTEM OR VENDOR! From my guide, you don't need to backup vendor.img or system.img or anything else that's not Boot or Data FOR OOS. Make sure you have everything like a copy of everything folder/file in your internal storage before u wipe it.
BUT because you're going to wipe your device. U should have a copy of everything in case but don't backup system or vendor as they're useless and will crash your system if u restore those!
After you've got your device from repair, follow my method to restore OOS TWRP backup on your device and YOU'LL only NEED TO RESTORE BOOT + DATA. Once you have booted back to your system, everything should be there like you never left, but transfer your internal storage stuff as some apps store files in your internal storage. Once that is done, that should be it and it would be like you've never left
If the TWRP backup restore doesn't work let me know, but from my experience with going back to OOS via my TWRP backup I only backed up and restored boot + data for OOS. Custom ROMs are different but isn't the case for you
Extreme_Ninja2099 said:
Idk if u have read Mauronofrio's XDA thread on TWRP backups. BUT NEVER BACKUP OR RESTORE SYSTEM OR VENDOR! From my guide, you don't need to backup vendor.img or system.img or anything else that's not Boot or Data FOR OOS. Make sure you have everything like a copy of everything folder/file in your internal storage before u wipe it.
BUT because you're going to wipe your device. U should have a copy of everything in case but don't backup system or vendor as they're useless and will crash your system if u restore those!
After you've got your device from repair, follow my method to restore OOS TWRP backup on your device and YOU'LL only NEED TO RESTORE BOOT + DATA. Once you have booted back to your system, everything should be there like you never left, but transfer your internal storage stuff as some apps store files in your internal storage. Once that is done, that should be it and it would be like you've never left
If the TWRP backup restore doesn't work let me know, but from my experience with going back to OOS via my TWRP backup I only backed up and restored boot + data for OOS. Custom ROMs are different but isn't the case for you
Click to expand...
Click to collapse
Wow, thanks for the quick reply!
I have not read Mauronofrio thread and will do!
I completely missed the system & vendor piece in your instructions....my bad!
So just to confirm, my backup that I have done with all checked off is good, but only restore Boot & Data with an exact duplicate of the current Internal Storage...right?
Going forward, when creating the Backup, just select Boot & Data and I'm good to go? Or select all Except: System Image(only) & Vendor options (both)?
Also, just so I can understand a bit better, "System" is the actual OOS? Meaning, if I restore Boot & Data on any OOS, all my apps and data will be as I never left, or we should always restore on the OOS that was current at the moment of the Backup (which I have always done in the past).
PS. I may just do the backup again, just to make sure SYSTEM & VENDOR are not there for good measure!
plepew said:
Wow, thanks for the quick reply!
I have not read Mauronofrio thread and will do!
I completely missed the system & vendor piece in your instructions....my bad!
So just to confirm, my backup that I have done with all checked off is good, but only restore Boot & Data with an exact duplicate of the current Internal Storage...right?
Going forward, when creating the Backup, just select Boot & Data and I'm good to go? Or select all Except: System Image(only) & Vendor options (both)?
Also, just so I can understand a bit better, "System" is the actual OOS? Meaning, if I restore Boot & Data on any OOS, all my apps and data will be as I never left, or we should always restore on the OOS that was current at the moment of the Backup (which I have always done in the past).
PS. I may just do the backup again, just to make sure SYSTEM & VENDOR are not there for good measure!
Click to expand...
Click to collapse
First off, I already posted everything you need in my last comment and that's what I usually do. Everything should be there and not like you need to pay or reply to get the extra stuff that you may need. No point in replying asking for more as I'll just be repeating myself over and over.
Just choose boot & data for TWRP backups for OOS specifically going forward and after you got your device from repair. System, vendor doesn't work in my experience and will crash your system. Only backup the .img variant which was stated by the dev (Mauronofrio) for TWRP for OP6/6T devices. Only backup system.img and vendor.img if u need to backup system+vendor, but YOU don't have to for OOS and I said this previously.
JUST DO A BACKUP OF EVERYTHING OTHER THAN SYSTEM AND VENDOR. YOU SHOULD ONLY BACKUP SYSTEM.IMG AND VENDOR.IMG NEVER SYSTEM OR VENDOR.
They never work and will increase the size of your backup and will take even longer to transfer to your storage device from your phone.
YES, to your new question. You should update/ be on the same OOS version as your TWRP backup before u restore data + boot. Restore OOS via fastboot or msm and update to get to the same version of OOS as your TWRP backup. YOU should only do this if your phone is in the wrong version of OOS as your backup after you've got it back from REPAIR.
ALWAYS BE ON THE SAME VERSION OF OOS AS YOUR TWRP BACKUP BEFORE YOU RESTORE YOUR TWRP BACKUP OF OOS!
Maybe take a copy of your wifi passwords, take a google backup in settings, take a copy of sms/call logs and contacts. Other stuff that you may not have stored just in case the TWRP backup fails, but it shouldn't. Good luck
This should be it and there isn't anything else that you'll need
Extreme_Ninja2099 said:
First off, I already posted everything you need in my last comment and that's what I usually do. Everything should be there and not like you need to pay or reply to get the extra stuff that you may need. No point in replying asking for more as I'll just be repeating myself over and over.
Just choose boot & data for TWRP backups for OOS specifically going forward and after you got your device from repair. System, vendor doesn't work in my experience and will crash your system. Only backup the .img variant which was stated by the dev (Mauronofrio) for TWRP for OP6/6T devices. Only backup system.img and vendor.img if u need to backup system+vendor, but YOU don't have to for OOS and I said this previously.
JUST DO A BACKUP OF EVERYTHING OTHER THAN SYSTEM AND VENDOR. YOU SHOULD ONLY BACKUP SYSTEM.IMG AND VENDOR.IMG NEVER SYSTEM OR VENDOR.
They never work and will increase the size of your backup and will take even longer to transfer to your storage device from your phone.
YES, to your new question. You should update/ be on the same OOS version as your TWRP backup before u restore data + boot. Restore OOS via fastboot or msm and update to get to the same version of OOS as your TWRP backup. YOU should only do this if your phone is in the wrong version of OOS as your backup after you've got it back from REPAIR.
ALWAYS BE ON THE SAME VERSION OF OOS AS YOUR TWRP BACKUP BEFORE YOU RESTORE YOUR TWRP BACKUP OF OOS!
Maybe take a copy of your wifi passwords, take a google backup in settings, take a copy of sms/call logs and contacts. Other stuff that you may not have stored just in case the TWRP backup fails, but it shouldn't. Good luck
This should be it and there isn't anything else that you'll need
Click to expand...
Click to collapse
Thank you!!
Hey guys, for some reason I ended up on "Unmodified System Partitions", must have tapped the screen a few times in error while handling the phone I guess.
What should I do?
Unable to go back to TWRP main menu without selecting an option.
I am rooted, on stock OOS and not doing customs ROM at this time...
What should I do?
Select "Keep Read Only"? or Swipe to "Allow Modifications"?
thanking you guys in advance for you help & guidance!
plepew said:
Hey guys, for some reason I ended up on "Unmodified System Partitions", must have tapped the screen a few times in error while handling the phone I guess.
What should I do?
Unable to go back to TWRP main menu without selecting an option.
I am rooted, on stock OOS and not doing customs ROM at this time...
What should I do?
Select "Keep Read Only"? or Swipe to "Allow Modifications"?
View attachment 5320971
thanking you guys in advance for you help & guidance!
Click to expand...
Click to collapse
Swipe to allow modifications. But it seems that your internal storage corrupted. Not sure what you did and how you got into this situation.
After you swiped to allow modifications... If the internal storage files are a messed up, try to switch slots and reboot recovery
Extreme_Ninja2099 said:
Swipe to allow modifications. But it seems that your internal storage corrupted. Not sure what you did and how you got into this situation.
After you swiped to allow modifications... If the internal storage files are a messed up, try to switch slots and reboot recovery
Click to expand...
Click to collapse
I swiped and yeah, the IS was messed up in File Managfer(TWRP).
Selected Reboot then Selected the Slot I remembered I was on : "A"
Rebooted & Boom all good!
Thank you for the help once again! You rock!!
plepew said:
I swiped and yeah, the IS was messed up in File Managfer(TWRP).
Selected Reboot then Selected the Slot I remembered I was on : "A"
Rebooted & Boom all good!
Thank you for the help once again! You rock!!
Click to expand...
Click to collapse
Cool and at least that was a easy fix
Sorry, I'm a total noob, hopefully this is an easy question to answer. Is there any way that I can tell what version of OOS my TWRP Backup contains? I can't remember what version my phone was running when I did the TWRP backup and don't want to mess it up after I restore the phone from MSM. Thanks in advance for your help!
Sorry, I'm a total noob, hopefully this is an easy question to answer. Is there any way that I can tell what version of OOS my TWRP Backup contains? I can't remember what version my phone was running when I did the TWRP backup and don't want to mess it up after I restore the phone from MSM. Thanks in advance for your help!
jas84701 said:
Sorry, I'm a total noob, hopefully this is an easy question to answer. Is there any way that I can tell what version of OOS my TWRP Backup contains? I can't remember what version my phone was running when I did the TWRP backup and don't want to mess it up after I restore the phone from MSM. Thanks in advance for your help!
Click to expand...
Click to collapse
Well u posted this twice which isn't necessary and people will try and reply. But I'm not sure if there is a way to know and as long as u copied the whole TWRP folder for that backup, u should be fine restoring it with a newer version of TWRP. If it really matters to you, then maybe try and find the latest TWRP on the date you did the backup? I think just using a newer TWRP version should be fine
Should I use the same Gapps package I flashed during clean installing when updating custom rom?
Waynenolan92 said:
Should I use the same Gapps package I flashed during clean installing when updating custom rom?
Click to expand...
Click to collapse
U don't have to use the same gapps package. Using a updated one would be better. But, u only have to for ROMs that don't include gapps (vanilla builds) AND the Restore script doesn't show up during installation. Opengapps doesn't have that script but nikgapps does. Using dirty flash/updating a ROM should show the restore script and if it doesn't then just reboot to recovery and flash the updated or same gapps package. This can also be the same for updating the base/vendor (use method 3 in that section of the guide). I hope this helps
Extreme_Ninja2099 said:
U don't have to use the same gapps package. Using a updated one would be better. But, u only have to for ROMs that don't include gapps (vanilla builds) AND the Restore script doesn't show up during installation. Opengapps doesn't have that script but nikgapps does. Using dirty flash/updating a ROM should show the restore script and if it doesn't then just reboot to recovery and flash the updated or same gapps package. This can also be the same for updating the base/vendor (use method 3 in that section of the guide). I hope this help
Click to expand...
Click to collapse
Thanks for your replay)))it's my first using vanilla rom(without Gapps), so I flashed nikigapps Omni package, and my question is: should I always use the same package, or I can go with core package for example?
Waynenolan92 said:
Thanks for your replay)))it's my first using vanilla rom(without Gapps), so I flashed nikigapps Omni package, and my question is: should I always use the same package, or I can go with core package for example?
Click to expand...
Click to collapse
U can... But it doesn't really matter as a updated package works fine and u only need to use it if the nikgapps restore script doesn't show up when updating the ROM or vendor/base (OOS underneath)
I want to CHANGE custom ROMs (havoc to Lineage OS a11 to a12) I have taken TWRP back up of boot+data+system.img+ vendor.img. once I flash the new a12 Lineage plus Nikapps core plus magisk. What steps to restore data? any response is appreciated in advance. Thank you.
Hey, my 9 power has an NVT-TS touch panel. All android 11 based ROMs seem to work such as Pixel Blaster and Lineage. However, when we talk about Android 12, my touch seems to only work on Evolution X.
I tried installing PixelPlusUI and PixelOS, however my touch does not work in them. If I try installing a custom kernel with those two, the OS does not boot and the phone gets stuck on the Redmi boot logo.
I have tried many fixes from various threads but nothing seems to work.
Anybody with a workaround or suggestion?
Update: Only a previous version of EvoX works. The latest version does not boot.
Hi. What kernel and recovery did you used for a12 rom ? Can you put here links to twrp/kernel and roms used in process ? Thanks. I have the same model with nvt touch and nothing worked for me and now i'm back to stock miui 12.5.11 global.
I used PitchBlack Recovery but also tried 2 different TWRP and Orange Fox Recoveries. I tried flashing various kernels but none worked. In the end, the kernel within the evox rom itself had to be used.
Hello,
I'm actually running fine a CrDroid on android 12 without issue.
Here's how i flashed it :
FOR JUICE!
1. Reflash the Firmware using MiFlash (From clean all and lock, change it to clean all Only)
2. Boot your device to Fastboot mode and Connect your device again to the PC
3. Download Minimal ADB and Fastboot and Install it, as follow the Instructions.
4. Download the OrangeFOX Recovery, download the Xiaomi.eu Rom, and download your Favourite Custom Rom.
5.Go to the Directory of Minimal ADB and Fastboot ----> C:\Program Files (x86)\Minimal ADB and Fastboot
and paste the recovery.img from the Archive in the Directory of Minimal ADB and Fastboot
6. Launch the Minimal ADB and Fastboot.exe Shotcut from the Desktop and type these commands:
1. Fastboot flash recovery recovery.img
2. If you want to reboot the device Fast type Fastboot reboot
7. Boot the device to the OrangeFOX Recovery, go to the Menu and open the Settings
8. From the Settings select General and uncheck Mount system and vendor read-only
9. Important! To install Successfully the Rom u need first to format the Data, go to Wipe section, select Format Data, type yes and Confirm.
10. Disconnect the Phone, connect it again to the USB and drag the Xiaomi.eu rom zip and the Custom Rom zip to the Phone
11. First u need to Install the Xiaomi.eu Rom zip this is Important!
12. When the flashing of the Xiaomi.eu Rom zip is Complete, u can flash your Favourite Custom Rom
13 Final Step: Format the Data with typing Yes again and Reboot the device, Enjoy!
From another XDA Post : https://forum.xda-developers.com/t/...onsive-with-custom-roms.4342665/post-86009079
Except i didn't fhashed an old CrDroid release, but the latest. Android 12 work just fine on my Juice with the same screen as yours
uzurka said:
Hello,
I'm actually running fine a CrDroid on android 12 without issue.
Here's how i flashed it :
FOR JUICE!
1. Reflash the Firmware using MiFlash (From clean all and lock, change it to clean all Only)
2. Boot your device to Fastboot mode and Connect your device again to the PC
3. Download Minimal ADB and Fastboot and Install it, as follow the Instructions.
4. Download the OrangeFOX Recovery, download the Xiaomi.eu Rom, and download your Favourite Custom Rom.
5.Go to the Directory of Minimal ADB and Fastboot ----> C:\Program Files (x86)\Minimal ADB and Fastboot
and paste the recovery.img from the Archive in the Directory of Minimal ADB and Fastboot
6. Launch the Minimal ADB and Fastboot.exe Shotcut from the Desktop and type these commands:
1. Fastboot flash recovery recovery.img
2. If you want to reboot the device Fast type Fastboot reboot
7. Boot the device to the OrangeFOX Recovery, go to the Menu and open the Settings
8. From the Settings select General and uncheck Mount system and vendor read-only
9. Important! To install Successfully the Rom u need first to format the Data, go to Wipe section, select Format Data, type yes and Confirm.
10. Disconnect the Phone, connect it again to the USB and drag the Xiaomi.eu rom zip and the Custom Rom zip to the Phone
11. First u need to Install the Xiaomi.eu Rom zip this is Important!
12. When the flashing of the Xiaomi.eu Rom zip is Complete, u can flash your Favourite Custom Rom
13 Final Step: Format the Data with typing Yes again and Reboot the device, Enjoy!
From another XDA Post : https://forum.xda-developers.com/t/...onsive-with-custom-roms.4342665/post-86009079
Except i didn't fhashed an old CrDroid release, but the latest. Android 12 work just fine on my Juice with the same screen as yours
Click to expand...
Click to collapse
Hi. What type of screen do you have ? Can you put the link here to download what rom you installed ? Thx.
I have the exact same type of screen than you, NVT-TS
I downloaded the rom from the official website of CrDroid : https://crdroid.net/juice/8
For the stock zip (step 11), i used this one : https://sourceforge.net/projects/xi...i_HMNote94G_HM9T_21.11.24_v12-11.zip/download
Btw, use crdroid 8.6 for juice. ATM 8.7 don’t work with touchscreen afaik. I did have to reinstall 8.6 after update
uzurka said:
Btw, use crdroid 8.6 for juice. ATM 8.7 don’t work with touchscreen afaik. I did have to reinstall 8.6 after update
Click to expand...
Click to collapse
Thank you, crdroid 8.6 worked. However, I wanted to use ROMs like Pixel Experience and PixelPlus but they touch does not work on them.
Atm, PixelPlusUI or PixelExperience are A12 AOSP with integrated Gapps (probably others differences but no matter), use flamegapps to get full gapps package and there you go!
Atm, i tried a lot of roms, and with A12, only CrDroid8.6 works...
I'm going to explain the complete process for getting up and running on a custom GSI ROM as the guides so far seem to either have only parts of information or incorrect information.
Following this process will wipe your data and alter your phone. I am not responsible for any bricked or damaged devices.
For the purpose of this thread I'm going to assume the installation of an Android 13 GSI image which you can get from the GSI images site. I like to use crDroid.
Make sure you read and understand all instructions before beginning!
1 - Unlock the bootloader
Important things to note:
One Xiaomi account can unlock one device per month. If you need to unlock multiple devices create an account for each one.
Unlocking the bootloader requires a wait time of 1 week after adding your Xiaomi account to the device before it can be unlocked
Create a Xiaomi account to use during this process here: https://account.xiaomi.com
Download the MI Unlock tool from here: https://en.miui.com/unlock/download_en.html
Procedure:
Ensure a SIM card is in with mobile data working and disable Wifi (required when associating your device with your Xiaomi account)
Enable developer mode by going into "About Phone" and tapping on the MIUI Version until it unlocks the setting
In Settings go to Additional Settings > Developer Options
Enable "OEM Unlocking" option
Select the "Add Account" option and enter your Xiaomi account details to link your device to your account
Open the Mi Unlock tool on your PC and log in with your Xiaomi account
If you get asked for a phone number when you log in the tool may get stuck as it doesn't allow you to click on the country code drop down correctly.
To avoid this, use the QR code icon on the first sign in page and from your phone go into the Xiaomi Account settings and click the scan icon on the top right
Log your account in with your phone to set the phone number there and you should be able to log in through the Mi Unlock tool next time without a problem.
Boot your phone into fastboot mode by holding Volume Down & Power buttons
Connect your phone to your PC with a USB cable
Click Unlock on the Mi Unlock tool and it should check your device and then give you a wait timer (generally 168 hours)
After that time is up (you can use your phone normally while waiting but don't mess with the Xiaomi Account settings) connect your phone in fastboot mode again and click Unlock in the Mi Unlock tool to unlock the bootloader.
2 - Install TWRP Recovery (or alternative)
Important things to note:
This phone does not have a dedicated recovery partition, the recovery is a ramdisk that resides within the boot partition
You cannot flash a recovery partition directly to the boot partition as it will then fail to boot
Make sure you use a current version of fastboot: https://provider.xiaomi.eu/tools/fastboot.zip
All commands written below are to be used without the apostrophes within a command prompt (powershell will require .\ placed in front of the command)
Download a TWRP image from here: https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/vili/ Use the A13 image for Android 13 ROMs.
Procedure:
Boot your phone into fastboot mode by holding Volume Down & Power buttons
Connect your phone to your PC with a USB cable
Run command "fastboot boot twrp.img" to reboot phone into TWRP recovery
If this is the first time using TWRP it will likely be in Chinese language. Click the 2nd to last button on the right side of the menu, then the globe icon on the top right to change language.
Go to Advanced and choose Flash Current TWRP to install TWRP into the boot image
Choose Reboot to Recovery to test the image is installed
3 - Install Latest Xiaomi.eu ROM (optional)
Important things to note:
I like to use the xiaomi.eu ROM as a base before installing a GSI image as it seems to be more stable and functional afterwards
This step is optional as you can continue with the global ROM base instead
Additionally, you can stop after this step if you would prefer to use a MIUI based ROM instead of a custom GSI image
The Xiaomi.eu ROM can be downloaded from here: https://xiaomi.eu/community/threads/miui-14-stable-release.67685/
The bootloader must be unlocked and TWRP recovery installed
Procedure:
Boot your phone into TWRP recovery by holding Volume Up & Power buttons
Click the Wipe button and then Format Data. Enter yes to wipe the data partition. (This will erase all data as well as the internal storage)
Connect your phone to PC and copy the xiaomi.eu ROM onto the phone
Click the Install button on the main menu in TWRP and select the ROM zip file to install
Go to Advanced and choose Flash Current TWRP to install TWRP back into the boot image
4 - Install Custom GSI Image
Important things to note:
This phone has a Super partition which dynamically contains system, system_ext and vendor partitions
This means that you cannot flash a GSI image directly to the system partition from TWRP so it must be installed via fastbootd
fastbootd is an enhanced version of fastboot that works with the dynamic Super partition
fastbootd mode looks like TWRP but it will say "Entered fastboot mode..." on the screen
Make sure you use a current version of fastboot: https://provider.xiaomi.eu/tools/fastboot.zip
All commands written below are to be used without the apostrophes within a command prompt (powershell will require .\ placed in front of the command)
Extract vbmeta.img file from the Xiaomi.eu ROM (or global ROM if using that) and place it in same folder as fastboot
Download your custom GSI image of choice from here or other source: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Extract the GSI image, rename it system.img and place it in the same folder as fastboot
Procedure:
Enter fastbootd mode on your phone using one of the following methods:
boot phone into fastboot mode and from your PC run command "fastboot reboot fastboot"
boot phone into TWRP and choose Reboot and then Fastboot
From your PC run the command "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" to disable the boot image hash checks to avoid boot loops
Run the command "fastboot erase system" to wipe the existing system image
Run the command "fastboot flash system system.img" to install your custom GSI image
NOTE: If you get an error saying "Not enough space to resize partition" run the command "fastboot delete-logical-partition product_a" and repeat the install again
5 - Install Magisk and Root
Important things to note:
Using the TWRP installation method by renaming the magisk apk to zip is not very reliable and the lastest versions require installation to be performed from within the OS
Download the lastest magisk from here: https://github.com/topjohnwu/Magisk/releases
We use a backup of the installed boot image rather than one from the xiaomi ROM as it has TWRP recovery installed in the ramdisk
Procedure:
Boot your phone into TWRP recovery
Enter the Backup menu, select the boot partition and run the backup
Copy the boot.emmc.win file out of the TWRP backup folder into the Download folder on your phone and rename it boot.img
Reboot your phone into System
Install the magisk apk file
Open magisk and click Install on the top right (in the Magisk section, not the App section)
For the Method choose Select and Patch a File then click Lets Go
Find the boot.img backup file copied to the Download folder and select it (after patching it will tell you the filename of the patched image)
Reboot your phone into TWRP recovery
Choose Install, then Install Image, select the file Magisk created above, select the Boot partition and then swipe to flash
Reboot to system and check in Magisk that it shows as installed (you may also want to reboot to recovery to ensure TWRP is still installed)
6 - Fixing Safetynet
Important things to Note:
The Shamiko magisk module is used to hide root status from apps that detect root/magisk. This can be used to make any app work that fails due to root status.
Shamiko uses the Denylist in Magisk settings to block root settings for those apps enabled but you should NOT have the denylist enforced in Magisk settings
You can find the Shamiko module here: https://github.com/LSPosed/LSPosed.github.io/releases
The default Universal Safetynet Fix can be found here however due to problems in a previous phone, I used the modded version from here (I'm not sure if that's still required for A13)
Procedure:
In Magisk settings choose to hide the magisk app to reinstall it with a different name and app id
In Magisk settings enable Zygisk and reboot phone
In Magisk settings choose Configure Denylist, show system apps from the top menu and enable Google Play Services, Google Play Store & Google Service Framework
In Magisk install the following modules: Shamiko, Universal Safetynet Fix
Install a Safetynet Checker from Google Play (SafetyNet Device Check) and verify safetynet tests pass successfully
7 - Post installation Fixes
Below are some fixes to common problems after installing a custom ROM.
Phh Settings Tweaks:
Qualcomm features - Use alternate audio policy -> fix audio in whatsapp
Qualcomm features - Disable soundvolume -> fix broken audio
Xiaomi features - Enable DT2W -> to enable double tap to wake
Misc features - Force alternative backlight scale -> fix auto brightness
IMS Features - Install IMS APK for Qualcomm -> allows SMS to work