Tutorial for Installing Android 10 GSI - Asus Zenfone Max M2 Guides, News, & Discussion

1 .Make sure your device has unlocked bootloader
2. Download Stock A10(in ASUS website) & modify updater script ( Remove everything before uiprint)
3. Reboot to Recovery and wipe data cache dalvik
4. Install Stock A10 zip
5. Flash Magisk 20.4 then dm verity 08-18 zip
6. Reboot to system after doing those
7. After rebooting go to recovery again
8. Take boot img backup(this step is for precaution otherwise if any problem of boot loop u will need to do again)
9. After backing up Flash gsi img (must be arm64 AB and don't forget to extract it)
10. Flash Magisk 20.4 then dm verity 08-18 zip again
11. Reboot to system after doing those
Note: if doesn’t boot or u have bootloop reflash boot img
BY AP XD
Hit Thanks if I had helped You.
FEEL free to PM me.
GSI: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Magisk 20.4 : https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
DM verity forceencrypt disabler : https://drive.google.com/file/d/1b2DUcWpDLM5lW1oPwdHshH6CEdvL9ZxM/view?usp=sharing

AP#xda said:
1 .Make sure your device has unlocked bootloader
2. Download Stock A10(in ASUS website) & modify updater script ( Remove everything before uiprint)
3. Reboot to Recovery and wipe data cache dalvik
4. Install Stock A10 zip
5. Flash Magisk 20.4 then dm verity 08-18 zip
6. Reboot to system after doing those
7. After rebooting go to recovery again
8. Take boot img backup(this step is for precaution otherwise if any problem of boot loop u will need to do again)
9. After backing up Flash gsi img (must be arm64 AB and don't forget to extract it)
10. Flash Magisk 20.4 then dm verity 08-18 zip again
11. Reboot to system after doing those
Note: if doesn’t boot or u have bootloop reflash boot img
BY AP XD
Hit Thanks if I had helped You.
FEEL free to PM me.
GSI: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Magisk 20.4 : https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
DM verity forceencrypt disabler : https://drive.google.com/file/d/1b2DUcWpDLM5lW1oPwdHshH6CEdvL9ZxM/view?usp=sharing
Click to expand...
Click to collapse
is it stable enough for daily usage

ankushlohiya said:
is it stable enough for daily usage
Click to expand...
Click to collapse
GSI is expected to have bugs.
Like phh based gsi has the Bluetooth audio bug.
But yes oneplus gsi doesn't have that bug.
It depends on your choice of GSI.

How to edit stock zip
And remove everything before ui print

Related

no_verity_op5(t) _v3.zip for OOS OB13 with Project Treble

I made small changes based v2
Suitable with OOS OB13 with Project Treble.
No need to mount any specific partitions (in recovery) manuly such as /vendor
Click to expand...
Click to collapse
How to use
If you see this thread, you should know how to use this file.
Just all the same as v2. More info here https://forum.xda-developers.com/oneplus-5/how-to/guide-how-to-decrypt-data-partition-t3642144
Can be used for HOS/OOS 7.1 8.0 8.1 and 8.1 with Project Treble and mokee rom
Download Link https://drive.google.com/open?id=1dMeYaIC4eFNBc3sfNQpGUqFzcqttlMZ0
daxiaamu said:
How to use
If you see this thread, you should know how to use this file.
Just all the same as v2. More info here https://forum.xda-developers.com/oneplus-5/how-to/guide-how-to-decrypt-data-partition-t3642144
Can be used for HOS/OOS 7.1 8.0 8.1 and 8.1 with Project Treble and mokee rom
Click to expand...
Click to collapse
File is damanged. also, has a zip.zip extension, but still, after renaming it, doesn't open (at least on the PC)
Awesome. Thank you very much @daxiaamu!
fjsferreira said:
File is damanged. also, has a zip.zip extension, but still, after renaming it, doesn't open (at least on the PC)
Click to expand...
Click to collapse
Same thing here. Thanks for the heads up.
fjsferreira said:
File is damanged. also, has a zip.zip extension, but still, after renaming it, doesn't open (at least on the PC)
Click to expand...
Click to collapse
link https://drive.google.com/open?id=1dMeYaIC4eFNBc3sfNQpGUqFzcqttlMZ0
a63548 said:
Awesome. Thank you very much @daxiaamu!
Same thing here. Thanks for the heads up.
Click to expand...
Click to collapse
link https://drive.google.com/open?id=1dMeYaIC4eFNBc3sfNQpGUqFzcqttlMZ0
Need new link please
Aballamis said:
Need new link please
Click to expand...
Click to collapse
You can also use the one from xXx https://forum.xda-developers.com/on...1-1-speed-ram-optimized-t3627121/post72802213
Aballamis said:
Need new link please
Click to expand...
Click to collapse
Here's a mirror: http://www.mediafire.com/file/1psz6...ForceEncrypt_2.0_%28OP5-5T-Treble%29.zip/file
Recommendation
I recommend this-
Its unversaly. I use this on every rom.
Regularly updated.
http://zackptg5.com/android.php#disverfe
XDA Thread for this-
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
P.S. I never format data while updating before flashing this (never needed, it works fine without that). I onlyformat data whenever i want pure clean install of any rom.
Just make sure to flash this after rom and after custom kernel or anything that edits boot. But flash this before Magisk. So. In short-
1. Flash- rom
2. Flash custom kernel or any thing that edits boot
3. Flash this to decrypt and to boot ur device successfully
4. Then flash Magisk
Note1: When you need clean install then follow these steps-
1. Factory reset (as normal when u do but if u r flash pure stock than wipe everything- i recommend this everytime for every stock(based) rom)
2. Reboot to recovery again
3. Click on Format data, type yes and format it.
4. Reboot to recovery again
5. And now go on flashing as mentioned above before these steps.
Note2: When u just need to update and not clean install. Then follow these steps-
1. First make sure to remove all magisk modules (when enabled it makes issues - after Magisk 18 and Pie update - before these updates i never got issues)
2. Now in twrp flash update zip
3. Flash anything that edits boot (ex. - custom kernel) if you want.
4. Now flash Magisk
5. Don'y flash any tweaks etc yet. (xXx NoLimits also)
6. Reboot.
7. Now if you want flash tweaks, modules etc.
8. And now only you are ready to flash xXx NoLimits again if you want.
**
*I guess this may help many of you in many cases.*
**
Mohitash said:
I recommend this-
Its unversaly. I use this on every rom.
Regularly updated.
http://zackptg5.com/android.php#disverfe
XDA Thread for this-
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
P.S. I never format data while updating before flashing this (never needed, it works fine without that). I onlyformat data whenever i want pure clean install of any rom.
Just make sure to flash this after rom and after custom kernel or anything that edits boot. But flash this before Magisk. So. In short-
1. Flash- rom
2. Flash custom kernel or any thing that edits boot
3. Flash this to decrypt and to boot ur device successfully
4. Then flash Magisk
Note1: When you need clean install then follow these steps-
1. Factory reset (as normal when u do but if u r flash pure stock than wipe everything- i recommend this everytime for every stock(based) rom)
2. Reboot to recovery again
3. Click on Format data, type yes and format it.
4. Reboot to recovery again
5. And now go on flashing as mentioned above before these steps.
Note2: When u just need to update and not clean install. Then follow these steps-
1. First make sure to remove all magisk modules (when enabled it makes issues - after Magisk 18 and Pie update - before these updates i never got issues)
2. Now in twrp flash update zip
3. Flash anything that edits boot (ex. - custom kernel) if you want.
4. Now flash Magisk
5. Don'y flash any tweaks etc yet. (xXx NoLimits also)
6. Reboot.
7. Now if you want flash tweaks, modules etc.
8. And now only you are ready to flash xXx NoLimits again if you want.
**
*I guess this may help many of you in many cases.*
**
Click to expand...
Click to collapse
Can the DM Verity n force encrypt disbler installed after magisk and without formatting data
And which one is best for Android pie
amitporedi007 said:
Can the DM Verity n force encrypt disbler installed after magisk and without formatting data
And which one is best for Android pie
Click to expand...
Click to collapse
Magisk must be flashed after dm...zip. But if you have already installed magisk then no worries. Flash DM Verity n force encrypr disabler and then again flash magisk. No need to format data in this case. Format data only needed when you are doing pure clean install of stock (based) rom. Check my signature, i am on OOS 9.0.2 that is android pie 9.0 and magisk v18. Decrypted (using that dm verity and force encrypr disabler).

[GUIDE] [HOW TO]Flash GSIs on Pie Vendor [X01AD]

Since the Pie update GSIs are not working because of System-as-root partiton But ASUS launched a new update in which GSIs are working.
READ WHOLE THREAD CAREFULLY.
REQUIREMENTS:
Unlocked bootloader (After Unlocking bootloader you will get a Red END OF STATE Warning. Don't Worry Press Power Button on that screen
Decrypted Data
Should be on latest firmware
If You're Using PitchBlack Recovery:
1. Boot into Recovery
2. Click On Advanced > Additional > Special > Setting OTA
3. Uncheck "Disable DM-Verity" Option Here
4. Done, Now You Can Use PitchBlack To Flash GSI on Pie Vendor.
INSTALLATION METHOD:
1. Download Any GSI of A/B type.
2. Download latest magisk manager zip
3. Patch your boot.img with Magisk (Tick on Preserve dm-verity by clicking on Advanced settins in magisk) or Download from Here
4. Boot into Recovery and Wipe Data, Dalvik Cache. Do not wipe system
5. Flash patched boot.img
Note: If your data is Encrypted then This step should be done with pitchblack otherwise your data may remain encrypted
6. Flash GSI image
7. Flash latest Magisk.
8. Go to Wipe option > Select Advanced Wipe > Tick on system > Click on Repair or Resize > Click on Resize.
9. Optional : Flash Gapps According to your choice If Gapps are not included in GSI.
10. Reboot System.
There is a possibility That your device will reboot again after asus logo. Don't worry
HIT THANKS IF I HELPED YOU:good:
do you see the red state warning after booting into gsi
sir iam unable to flash gapps after flashing the gsi. TWRP says the gapps variant is incompatible. I tried to flash arm 64 pico for pie. The gsi though boots. I flashed RR pie gsi (A/B) with pie vendor.. Please help Thanks in advance
jeno33 said:
sir iam unable to flash gapps after flashing the gsi. TWRP says the gapps variant is incompatible. I tried to flash arm 64 pico for pie. The gsi though boots. I flashed RR pie gsi (A/B) with pie vendor.. Please help Thanks in advance
Click to expand...
Click to collapse
Sorry I didn't mentioned in guide, that you've to modify script of gapps to get it working. I'll upload modified gapps tomorrow. Again I apologize
jeno33 said:
do you see the red state warning after booting into gsi
Click to expand...
Click to collapse
Red state warning is due to unlocked bootloader. It'll remain as long as bootloader is unlocked. But that doesn't create any problem except for increasing boot time by 5-6 seconds.
use A/B type cannot flash gapps,error 64. A type can flash gapps. Why?
gxfuzion92 said:
use A/B type cannot flash gapps,error 64. A type can flash gapps. Why?
Click to expand...
Click to collapse
Updater-script needs to be modified inside gapps, because gapps wrongly detects architecture as arm.
Install this gappshttps://drive.google.com/file/d/1nS2z4emxHovZ0x3CqXl59r8oBqx9DiPU/view?usp=drivesdk
I have modified the script
what rums for example are loaded and working?
currently the Havoc-OS-v2.0-20181027-GSI-ARM64-Aonly-Official is being loaded and running.
tried miui, flyme, Havoc-OS other versions
Is there any video tutorial?
Any tutorial videos?
gxfuzion92 said:
use A/B type cannot flash gapps,error 64. A type can flash gapps. Why?
Click to expand...
Click to collapse
Hey you able to flash any GSI except havoc 2.0 ??
I'm not able to access your document

Magisk Bootloop on MIUI 11 11.0.1.0 Global Version

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!

General [TWRP] [ORANGEFOX] [UNOFFICIAL] [ROSEMARY] [BETA] TWRP 3.5.2 and TWRP 3.6+ for Xiaomi Redmi Note 10s

WARNING: THIS IS EXPERIMENTAL BETA MEANT FOR DEVELOPERS AND TESTERS NOT AS DAILY DRIVER
Caution: Android 11 builds are incompatible with Android 12. Beware!
Credits:
@Woomymy
@J6idot
@mastersenpai05
@myst33d
https://github.com/notmyst33d
Developers WoomyMy, J6idot , mastersenpai05 and Myst33d have helped develop an unofficial TWRP for rosemary - xiaomi redmi note 10s
Installation Video:
Code:
https://www.mediafire.com/file/f4zcls9sgi3nkoj/352+redmi+note+10s.rar/file
http://www.mediafire.com/file/p3zhivru97bdlke/no-verity-opt-encrypt-6.1.zip/file
https://github.com/RedmiNote10S/recovery_device_xiaomi_rosemary
Since this is not yet official, only proceed if you are competent enough and brave.
(If you need instructions on how to flash, please do not flash this with fastboot method)
Feel free to discuss any bugs or issues and fixes so that everybody can benefit from our findings.
TWRP 3.6+ Development Build status, fixes, bugs and downloads: [here]​
TWRP -3.6.2_11-2
NameModifiedTWRP-3.6.2_11-208/03/2022
Changelog
Fix brightness when max brightness is 255
Render GUI at 60FPS
Reposition statusbar icons and remove top offset
A lot of code cleanup
Update TWRP sources
DONT INSTALL THIS ON MIUI 13
Install instructions
Without TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download TWRP .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Install -> Install Image -> Select stock boot.img -> “Flash to: Boot”)
Next, go in Advanced -> Flash current TWRP and swipe to flash TWRP.
Reboot and enjoy!
With custom recovery
Download TWRP .ZIP installer and flash it in recovery (you can also use adb sideload for recoveries like LineageOS recovery)
Compatibility
Android 11 Roms: YES
Android 12 Roms: NO
TWRP-3.6.2_12-rc1
NameModifiedTWRP-3.6.2_12-rc108/04/2022
Changelog
Sync TWRP sources
Add support for Android 12 decryption
Fix booting on MIUI13
DONT INSTALL THIS ON MIUI 12.5
Install instructions
Without TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download TWRP .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Install -> Install Image -> Select stock boot.img -> “Flash to: Boot”)
Next, go in Advanced -> Flash current TWRP and swipe to flash TWRP.
Reboot and enjoy!
With custom recovery
Download TWRP .ZIP installer and flash it in recovery (you can also use adb sideload for recoveries like LineageOS recovery)
Compatibility
MIUI 13 vendors: COMPATIBLE
MIUI 12 vendors:
A11 GSI / MIUI 12 system: FULLY INCOMPATIBLE
A12 GSI: COMPATIBLE, but you CAN NOT flash the boot.img, you need to flash the UPDATE ZIP using a custom recovery / Magisk
OrangeFox-R11.1_1-Unofficial
NameModifiedOrangeFox-R11.1_1-Unofficial07/01/2022
Changelog
Fix brightness when max brightness is 255
Render GUI at 60FPS
Reposition statusbar icons and remove top offset
A lot of code cleanup
Update OrangeFox sources
DONT INSTALL THIS ON MIUI 13
Update Magisk OrangeFox addon to v25.2
Install instructions
Without TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download OrangeFox .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Select stock boot.img -> “Flash to: Boot”)
Next, go in Menu -> Flash current OrangeFox and swipe to flash OrangeFox.
Reboot and enjoy!
To get Fox addons working, you need to reflash OrangeFox .zip file
With custom recovery
Download OrangeFox .ZIP installer and flash it in recovery (you can also use adb sideload for recoveries like LineageOS recovery)
Compatibility
Android 11 Roms: YES
Android 12 Roms: NO
Older versions:
NameModifiedBeta-07-11-30-202112/17/2021
🗞 Changelog
Sync TWRP sources (Version number updated to 3.6.0)
Symlink /dev/block/bootdevice -> /dev/block/platform/bootdevice (required by some scripts like OrangeFox installer)
Allow flashing VBMeta
Disable "Reflash TWRP after flashing ROM". (Causes AVB problem when installing MIUI, can still be done manually)
Build ZIP TWRP installer
Publish build logs for more transparency
Known bugs
Mounting Adopted storage
Vibrator
NameModifiedRC-01-01-09-20221/9/2022
🗞 Changelog
Fix Bootctrl
Fix vibrator
Known bugs
Mounting Adopted storage
TWRP Version 3.6.1_11-1​
NameModifiedTWRP-3.6.1_11-13/13/2022
🗞 Changelog
Fix BootCTRL
Update TWRP sources
Fix vibrator
Enable DT2W in recovery
Install instructions​Without TWRP/OrangeFox​
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download TWRP .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Install -> Install Image -> Select stock boot.img -> “Flash to: Boot”)
Next, go in Advanced -> Flash current TWRP and swipe to flash TWRP.
Reboot and enjoy!
With TWRP/OrangeFox​
Download TWRP .ZIP installer and flash in recovery
TWRP Version 3.6.2_11-1​
NameModifiedTWRP-3.6.2_11-16/14/2022
🗞 Changelog
Sync TWRP sources
Orangefox Recovery Version R11.1_1-Beta​
NameModifiedOrangeFox-R11.1_1-Beta3/13/2022
🗞 Changelog
Fix BootCTRL
Update OrangeFox sources
Fix vibrator
Enable DT2W in recovery
Update Magisk OrangeFox addon to 24.2
Install instructions​Without TWRP/OrangeFox​
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download OrangeFox .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Select stock boot.img -> “Flash to: Boot”)
Next, go in Menu -> Flash current OrangeFox and swipe to flash OrangeFox.
Reboot and enjoy!
To get Fox addons working, you need to reflash OrangeFox .zip file
With TWRP/OrangeFox​
Download OrangeFox .ZIP installer and flash in recovery
Nice, it's beta 2
to apply encrypt patch, you must decrypt first.
So
- you have to disable security password/fingerprint in your parameter first.
- then reboot in recovery
- format data
- reboot again to recovery and apply patch.
How to use redmi note 10s unofficial twrp recovery
test (beta 2) after disabling security (fingerprint and pin)
- flashing magisk.zip -> ok
- backup -> ok
- restore -> ok
- MTP internal SD -> ok
- MTP external SD -> nok, file manager stuck on it (win10 or linux mint)
Please full prosses explain and 1 question flash fastboot method
This the link of the Official Tutorial from the Unofficial TWRP Website:
unofficial twrp 3.6.1 Root Redmi Note 10s (rosemary) - unofficial twrp
Download unofficial twrp 3.6.1 root Redmi Note 10s, user who own Redmi Note 10s can root it by following the below instructions
unofficialtwrp.com
Great
miravision said:
Developer WoomyMy has released an unofficial TWRP for rosemary - xiaomi redmi note 10s
Installation Video:
Code:
https://www.mediafire.com/file/f4zcls9sgi3nkoj/352+redmi+note+10s.rar/file
http://www.mediafire.com/file/p3zhivru97bdlke/no-verity-opt-encrypt-6.1.zip/file
Since this is not yet official, only proceed if you are competent enough and brave.
(If you need instructions on how to flash, please do not flash this with fastboot method)
Feel free to discuss any bugs or issues and fixes so that everybody can benefit from our findings.
Click to expand...
Click to collapse
I'm sorry but, do you atleast have the permission to share this?
Also, WommyMy should be the guy to upload it, not you.
Edit: thanks for fixing the thread
Also you're missing the device tree.
Hello. As one of the developpers of this TWRP DT, I am not really OK with that.
Firstly, you linked the wrong device tree Real link here
Also, I didn't published this on XDA because this TWRP is still in BETA. And it contains major bugs, like flashing dynamic partitions in fastbootd. Even if bugs will me fixed, I was planning to wait a release candidate before publishing the release here (this will require even more testing, if people want to help us testing, this will be even better).
So please, can you delete this or add clear warnings about the beta state?
Regards, Woomy
@miravision I think we should also add credits to people like @J6idot , @mastersenpai05 and Myst33d who did a great job helping building twrp.
Woomymy said:
@miravision I think we should also add credits to people like @J6idot , @mastersenpai05 and Myst33d who did a great job helping building twrp.
Click to expand...
Click to collapse
Yes, I believe they should get their work credit.
Will be fix soon.. don't too hurry.
mastersenpai05 said:
Will be fix soon.. don't too hurry.
Click to expand...
Click to collapse
Thanks bro
Keeps restarting when i try to flash a custom ROM from xiaomi eu, any Fix please ?
Wow., Hoping for releasing custom roms for our handsets.,keep up the good work devs
Katho536 said:
Keeps restarting when i try to flash a custom ROM from xiaomi eu, any Fix please ?
Click to expand...
Click to collapse
Xiaomi eu has no support for 10s iirc
No support for Mediatek devices on Xiaomi.eu, Global.rom and other
@miravision can u provide the vbmeta.img file?
Original post updated with attached vbmeta.img
langithitam said:
@miravision can u provide the vbmeta.img file?
Click to expand...
Click to collapse
Hi and thanks for sharing
Is it possible just to boot from TWRP recovery via Fastboot without flashing it on the phone?
I have also a Poco X3 NFC with stock MIUI 12.5 with Magisk root, but with stock recovery (so I can do all OTA updates) where I'm doing the same.
When I need it, I just do
fastboot boot TWRP-file.img
Thanks

How install magisk on raphael/in with v13 android?

Hi.
How install magisk on raphael/in with v13 android?
mablue said:
hi
How install magisk on raphael/in with v13 android?
Click to expand...
Click to collapse
Why don't you try standard way:
- Extract boot img from your ROM zip
- Install Magisk app
- From Magisk app, use Magisk Install option to patch the boot.img (do not enable Recovery option)
- Flash from Fastboot the patched boot.img
Actually, instead of permanently flashing (you could also reflash the original boot.img if something goes wrong), first test just to boot with:
fastboot boot <patched boot. img>
That is actually the recommended method by Magisk GitHub documentation (not the old way through TWRP - and bcs of the lack of available custom recoveries for A12, A13)

Categories

Resources