XiAOMI MI MAX 2 Official ROM Root twrp - Xiaomi Mi Max 2 Questions & Answers

So Guys ROM twrp Root etc Now available for MI max 2. [oxygen 2]
You can Download official ROM from http://en.miui.com/a-234.html
and Flash it with MI flash.
or if you have dead Device follow deep Flashing Guide Here.https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-flash-hard-bricked-redmi-t3490055
twrp ported From mido Download Here
Flash with fastboot
Code:
fastboot flash recovery recovery.img
Flash magisk From here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
in trouble watch video-

Thank you! TWRP worked as intended, installed root manually. Donated as well.

TiMbl4 said:
Thank you! TWRP worked as intended, installed root manually. Donated as well.
Click to expand...
Click to collapse
ok thanks for Donation..

Lineage OS available https://forum.xda-developers.com/mi-max-2/development/linageos-14-1-mi-max-2-t3634864

Great toolkit but I have a couple questions. In the instructions on your site and youtube video it has a step to flash noverity. Is this really needed or is it just a precaution? Also, could I just flash the recovery via fastboot and then just pull noverity and magisk from their source and flash them? I always like to flash things myself the normal way so I understand what's going on.

noverity is just to protect from bootloop. i use noverity on all Nougat Devices. and also it can't cause any damage to device so don't worry.
correct meaning-
you can Root Your Phone without modified boot.img which is Must Require on Many Devices.

XN Logos said:
noverity is just to protect from bootloop. i use noverity on all Nougat Devices. and also it can't cause any damage to device so don't worry.
correct meaning-
you can Root Your Phone without modified boot.img which is Must Require on Many Devices.
Click to expand...
Click to collapse
Thanks for the quick response. I have one more question. Can I substitute SuperSU in place of magisk? After using the toolkit, I tried to update magisk to the latest version (13.2) using magisk manager but instead it gave an error. It didn't brick my phone or anything but when I rebooted and went into magisk manager it showed the phone was still properly rooted but reported that magisk wasn't installed. Not sure if it's a compatibility issue or not. I also tried flashing the latest version of magisk using twrp and got the same error in magisk manager upon reboot.
At any rate, do you see any problem with using SuperSU instead?

Flash SuperSu 2.79 make Sure you have a backup because Bricking Change me present.
or try with No verity.

XN Logos said:
Flash SuperSu 2.79 make Sure you have a backup because Bricking Change me present.
or try with No verity.
Click to expand...
Click to collapse
Thanks. I restored my phone from the nandroid backup I took after installing twrp and then flashed noverity and supersu and it all worked perfectly. Thanks again

Did you have to unlock the bootloader for installing twrp?
ikecomp said:
Thanks. I restored my phone from the nandroid backup I took after installing twrp and then flashed noverity and supersu and it all worked perfectly. Thanks again
Click to expand...
Click to collapse

unlock with developer rom

XN Logos said:
unlock with developer rom
Click to expand...
Click to collapse
Since 5 days i have been trying to unlock bootloader. Every time I get "Device not bound to account". I have tried everything. Can you help me?? I am already on developer rom..

yes that means You have not applied for unlock, First of all apply for unlock then when you receive Confirmation msg wait 72 hrs, then login mi unlock app with same account and then try to unlock

Magisk not detect root
{
"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 follow all instruction,i flash no verity and flash xnmagisk.zipafter reboot magisk appear like that? Have format but still not detect root, can root manually flash superusu but i want magisk to for hide root. So what next stepp for solve this problem? Let me know. Thanks

Hi guys, any idea why when I flash magisk 14.0 over a fresh 7.9.7 global developer rom I get CTS profile mismatch? It still shows safetynet as passing but android pay refuses to work. Also, is it safe to install OTA updates with magisk flashed?

How to root after flashing the official miui9 ? (my device is rooted miui 8.5)
please help (Device Mi Max 2 )

Related

Magisk Manager doesnt give the direct install option

All I get is the option to patch boot img and the option to install the zip.
{
"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"
}
You can only do direct install if the Manager has superuser access. In other words, if you already have Magisk installed and want to install an update. First install you need to patch the boot image and flash manually, or download the zip and flash in recovery.
Didgeridoohan said:
You can only do direct install if the Manager has superuser access. In other words, if you already have Magisk installed and want to install an update. First install you need to patch the boot image and flash manually, or download the zip and flash in recovery.
Click to expand...
Click to collapse
Thanks so much! boot image has been patched, i think. Now, how do i install magisk via stock recovery? how do i navigate to the
magisk manager folder?
fwng said:
Thanks so much! boot image has been patched, i think. Now, how do i install magisk via stock recovery? how do i navigate to the
magisk manager folder?
Click to expand...
Click to collapse
You can't install it with a stock recovery.
Depending on your device you need to use fastboot, ODIN or whatever is applicable.
If it's a non-Samsung device fastboot usually works. While booted to bootloader and with your device hooked up to your computer:
Code:
fastboot flash boot patched_boot.img
If you don't have adb and fastboot installed, get it here:
https://developer.android.com/studio/releases/platform-tools.html
If you can't get it to work, there's usually plenty of help and info in your device's forum.
Didgeridoohan said:
You can't install it with a stock recovery.
Depending on your device you need to use fastboot, ODIN or whatever is applicable.
If it's a non-Samsung device fastboot usually works. While booted to bootloader and with your device hooked up to your computer:
Code:
fastboot flash boot patched_boot.img
If you don't have adb and fastboot installed, get it here:
https://developer.android.com/studio/releases/platform-tools.html
If you can't get it to work, there's usually plenty of help and info in your device's forum.
Click to expand...
Click to collapse
That worked! thanks so much! sorry to trouble you!
fwng said:
That worked! thanks so much! sorry to trouble you!
Click to expand...
Click to collapse
Awesome! And it's no trouble... I'm here because I like to help. :good:
Hi,
I'm facing a strange issue. My note 8 exynos INS dual SIM has the Ironman rom installed and running. I had magisk root selected and installed. These days I get a notification about a magisk update (v16.0) when I tap the notification it takes me to magisk start screen where it shows magisk as not installed with the option to download the boot image or patch the boot file.
I then download the new zip, get into twrp recovery, flash the zip and reboot. After thd phone starts up and i click the magisc app icon magisk opens and shows me that the latest version is installed.
However in a random duration which can be 15 min or 1 hrs or 3 hrs, the update notification pops up again and tapping it shows magisk as not being installed with an older version in red below the latest version in green.
I have been using magisk on my devices for long and this is the fifth device SM-N950FD that I'm using it now and have seen this the first time on nougat 7.1.1.
Can I get some help regarding this. Apologies for this if it is a noob question or a duplicate but I couldn't find this anywhere so decided to post.
Thanks centaur31
centaur31 said:
Hi,
I'm facing a strange issue. My note 8 exynos INS dual SIM has the Ironman rom installed and running. I had magisk root selected and installed. These days I get a notification about a magisk update (v16.0) when I tap the notification it takes me to magisk start screen where it shows magisk as not installed with the option to download the boot image or patch the boot file.
I then download the new zip, get into twrp recovery, flash the zip and reboot. After thd phone starts up and i click the magisc app icon magisk opens and shows me that the latest version is installed.
However in a random duration which can be 15 min or 1 hrs or 3 hrs, the update notification pops up again and tapping it shows magisk as not being installed with an older version in red below the latest version in green.
I have been using magisk on my devices for long and this is the fifth device SM-N950FD that I'm using it now and have seen this the first time on nougat 7.1.1.
Can I get some help regarding this. Apologies for this if it is a noob question or a duplicate but I couldn't find this anywhere so decided to post.
Thanks centaur31
Click to expand...
Click to collapse
Does the ROM come with Magisk pre-installed? If so, I'd reflash the ROM without Magisk, if possible, make sure that there are no traces of Magisk on the device (Manager included) and install Magisk manually.
A better place for this post would have been the general support thread.
H
fwng said:
All I get is the option to patch boot img and the option to install the zip.
Click to expand...
Click to collapse
How do I install a zip?

[boot.img] Patched boot.img files & patching tool

Here you can find several patched boot.img files for various stock rom system versions of Redmi 7A.
https://www.mediafire.com/folder/zx0167qqaknc3/Redmi_7a_patched_boot
Note: The one for xiaomi.eu is custom rom, not stock EU.
If you can't find a patched boot.img for your version, you can also patch it yourself with this tool:
http://www.mediafire.com/file/c5e0idf6cy5ap25/patcher.7z/file
(follow instructions in readme file; credits to Russian 4pda forum)
Where i can find xiaomi.eu ROM for this device?
NV-Dev said:
Where i can find xiaomi.eu ROM for this device?
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=4349826312261652844
Can you please upload patched boot for 11.0.2 indian rom???
Can you make a patched boot for the Mokee rom because when I try to patch it with the patcher it has ramdisk error. Can you help me?
anonymousfun122 said:
Can you make a patched boot for the Mokee rom because when I try to patch it with the patcher it has ramdisk error. Can you help me?
Click to expand...
Click to collapse
Here for you
Mokee_boot.img
{
"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"
}
Not working for me
Auto Reboot to recovery
It worked
sjcbank said:
Here for you
Mokee_boot.img
Click to expand...
Click to collapse
Thank you so much !!! It worked instantly . I was trying weeks to make magisk working on the mokee rom.
Thank you !!
Hey,
I have MIUI v10.2.6.0.PCMINXM(Indian version), actually I downgraded to this version. Please help me install Mokee on my device. Enlist all the steps I need to take from scratch.
Your prompt response would be really appreciated.
Tenome7 said:
Hey,
I have MIUI v10.2.6.0.PCMINXM(Indian version), actually I downgraded to this version. Please help me install Mokee on my device. Enlist all the steps I need to take from scratch.
Your prompt response would be really appreciated.
Click to expand...
Click to collapse
Any rom version can install mokee. It's very easy, anyone can do it.
I am 60 years old, I am Vietnamese, I do not know English, all instructions are available online, I use Google, Google Chrome and Google translate.
sjcbank said:
Any rom version can install mokee. It's very easy, anyone can do it.
I am 60 years old, I am Vietnamese, I do not know English, all instructions are available online, I use Google, Google Chrome and Google translate.
Click to expand...
Click to collapse
I've been toying around with Android since it's Lollipop versions, rooting them, intalling custom ROMs etc. Probably 6 years. More than 7 devices.
As far as installing a custom ROM on this phone (Redmi 7A) is concerned, the different versions, like Indian, Global have different drivers or HAL's.
So, after successfully booting up into MOKEE OS on my variant 3-4 times, Torch, Audio, Video, Calls...... Nothing worked.
And to be very honest, there was nothing mentioned about this in MOKEE OS thread, as to which version of this device is not compatible with the ROM. The only reason I messed up was because the introduction of GSI ROMs has made the custom ROM creation process easier, but introduced a ****load of work in some devices, and ending up causing trouble.
This was the reason I requested all the steps in the thread so I could verify if I was missing some important step as far as the Indian variant is considered.
But thanks to everyone, I successfully booted Mokee ROM with everything working on my variant, including superuser privileges.
Also I messed up partitions in TWRP, and ended up with only 22gigs of Internal storage available, lol.
Thanks.
Tried @Tenome7 patched boot file for latest nightlly mokee OS 10, it bootloops, patched my own boot file, it still boot loops.
It seems impossible to get magisk working in mokee OS.
Ok I figured it out, AFTER you flash the patched boot.img you need to format the data partition, you'll loose all your data, however the ROM will boot.
I'm running Android 10 mokee os, more stable and no bugs compared to lineage os 17 rom
cg730620 said:
Here you can find several patched boot.img files for various stock rom system versions of Redmi 7A.
Click to expand...
Click to collapse
Hi
Do you have a patched boot.img for my 7A 11.0.18.0 (PCMEUXM) ?
Thanks
axy_david said:
Tried @Tenome7 patched boot file for latest nightlly mokee OS 10, it bootloops, patched my own boot file, it still boot loops.
It seems impossible to get magisk working in mokee OS.
Click to expand...
Click to collapse
Sorry for being so late to reply here. I would suggest using MIUI v10.2.10.0 as the base over which the Mokee OS needs to be installed.
As far as root is concerned, I tried Magisk but it gave me bootloops every time. As an alternative to getting root, I flashed the AddonSU installer which I downloaded from the Mokee Official site. You would just need to find it on the website.
I hope this helps. If you have further doubts, I'll stay a bit more active here. :fingers-crossed:
I want to unroot, but when i choose restore images in magisk manager it says stock backup doesnt exist. I downloaded the patched boot and stock boot.img prior to rooting, i didnt use magisk to patch the stock boot. What do i do now, i want to unroot and install ota on my xiaomi mi a3.
Can anybody help me?
I need the new version of patcher and the creator's website doesn't load me correctly.
Anyone have got pine 11.0.7 global patched boot image??? Cz yaalex patcher is down showing internal error
redmi7a
Hi
carried out
bootfromrecovery.bat - Reboot to recovery, connect to PC, install adb driver and run this file. this will extract boot.img from running phone, patch it on the fly and flash back patched boot.img
..but it didn't happen
* Requires internet connection. (it downloads latest Magisk release during process)
..I still don't have root
someone will help
Thank you
I asked the developer about a similar issue with the downloadable patcher, and he suggested me to try with the online one, which is more up to date.
https://patcher.yaalex.xyz/
romam suchanek said:
Hi
carried out
bootfromrecovery.bat - Reboot to recovery, connect to PC, install adb driver and run this file. this will extract boot.img from running phone, patch it on the fly and flash back patched boot.img
..but it didn't happen
* Requires internet connection. (it downloads latest Magisk release during process)
..I still don't have root
someone will help
Thank you
Click to expand...
Click to collapse

Problem to unroot with LineageOS 17.1

Hi guys,
I rooted and flashed my realme X2 Pro (Europe) to install LineageOS 17.1 and it's great.
But, some app detect my rooted was rooted and doesn't works properly (payment with NFC disabled, few apps aren't in PlayStore and can't install with apk.
I tried to unroot my phone, but Root checker app tell me my phone is not rooted properly.
I think, the root was corrumpt when I installed LineageOS 17.1.
I tryied to root again with Magisk and TWRP (after Lineage installed) but my phone loop on bootloader after that.
I tyried also to install magisk uninstaller but same problem at reboot.
I tryied to unroot manualy with ES File manager, but when I activate "Root" in settings, it's tell me that my phone is not rooted.
And, when I want to go in /system/bin, File manager can't displayed items. I'm unable to find this folder in TWRP.
Also, SuperSU app, say "Sorry ! Device did not rooted properly".
{
"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 also tryied to go back on RUI stock image with tutos, but twrp 3.4 (manuforio) failed after decrypting Ozip file.
Can I unroot my phone and keep LineageOS ? If yes, how can I unrooted my phone ?
Many thanks in advance.
Catskan
Catskan06 said:
Hi guys,
I rooted and flashed my realme X2 Pro (Europe) to install LineageOS 17.1 and it's great.
But, some app detect my rooted was rooted and doesn't works properly (payment with NFC disabled, few apps aren't in PlayStore and can't install with apk.
I tried to unroot my phone, but Root checker app tell me my phone is not rooted properly.
I think, the root was corrumpt when I installed LineageOS 17.1.
I tryied to root again with Magisk and TWRP (after Lineage installed) but my phone loop on bootloader after that.
I tyried also to install magisk uninstaller but same problem at reboot.
I tryied to unroot manualy with ES File manager, but when I activate "Root" in settings, it's tell me that my phone is not rooted.
And, when I want to go in /system/bin, File manager can't displayed items. I'm unable to find this folder in TWRP.
Also, SuperSU app, say "Sorry ! Device did not rooted properly".
I also tryied to go back on RUI stock image with tutos, but twrp 3.4 (manuforio) failed after decrypting Ozip file.
Can I unroot my phone and keep LineageOS ? If yes, how can I unrooted my phone ?
Many thanks in advance.
Catskan
Click to expand...
Click to collapse
Did you have any solution for (unrooted +LineageOS) or NFC payments enabled with rooted LineageOS
Catskan06 said:
Hi guys,
I rooted and flashed my realme X2 Pro (Europe) to install LineageOS 17.1 and it's great.
But, some app detect my rooted was rooted and doesn't works properly (payment with NFC disabled, few apps aren't in PlayStore and can't install with apk.
I tried to unroot my phone, but Root checker app tell me my phone is not rooted properly.
I think, the root was corrumpt when I installed LineageOS 17.1.
I tryied to root again with Magisk and TWRP (after Lineage installed) but my phone loop on bootloader after that.
I tyried also to install magisk uninstaller but same problem at reboot.
I tryied to unroot manualy with ES File manager, but when I activate "Root" in settings, it's tell me that my phone is not rooted.
And, when I want to go in /system/bin, File manager can't displayed items. I'm unable to find this folder in TWRP.
Also, SuperSU app, say "Sorry ! Device did not rooted properly".
I also tryied to go back on RUI stock image with tutos, but twrp 3.4 (manuforio) failed after decrypting Ozip file.
Can I unroot my phone and keep LineageOS ? If yes, how can I unrooted my phone ?
Many thanks in advance.
Catskan
Click to expand...
Click to collapse
Try reflashing lineageos 17.1 or if you want to go back to stock rom update your vendor and flash

How To Guide How I flashed official ROM updates...

DISCLAIMER: I am not responsible for any bricked phones or otherwise but this is how I updated to the latest version.
Flashing backwards has not been tried by myself, use at your own risk.
Only flashing the same version of ROM was tried, global for global.
I tried the local update method that is built into the MIUI ROM, my bootloader is still locked, and you can only use OFFICIAL MIUI ROM's.
{
"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"
}
Sorry guys , I'm don't find a right thread!
I don't know but plz help me .
I'm on stock ROM 12.0.16 global RKFEUXM , rooted an tw recovery !!not decrypted!!
I have on my ex SD card ,the newest Stock ROM flashabl.zip. ,Magisk and the twrp.img.
I don't know now the right steps to update to new with out losing data ,root ant tw recovery .
plz help me with the right steps .
what is needed to format ?
then the steps to flash an boot
thank you
Plz help me!!!
Thank you guys
Jakkomo77 said:
Sorry guys , I'm don't find a right thread!
I don't know but plz help me .
I'm on stock ROM 12.0.16 global RKFEUXM , rooted an tw recovery !!not decrypted!!
I have on my ex SD card ,the newest Stock ROM flashabl.zip. ,Magisk and the twrp.img.
I don't know now the right steps to update to new with out losing data ,root ant tw recovery .
plz help me with the right steps .
what is needed to format ?
then the steps to flash an boot
thank you
Click to expand...
Click to collapse
Flash full stock rom > flash magisk patched boot image (optional) > flash twrp > flash dm verity disabler > reboot
Spudsicles said:
DISCLAIMER: I am not responsible for any bricked phones or otherwise but this is how I updated to the latest version.
Flashing backwards has not been tried by myself, use at your own risk.
Only flashing the same version of ROM was tried, global for global.
I tried the local update method that is built into the MIUI ROM, my bootloader is still locked, and you can only use OFFICIAL MIUI ROM's.
View attachment 5344411
Click to expand...
Click to collapse
Hello,
I am on Miui 12.5.4 rooted with Magisk right now, no TWRP, and OTA update 12.5.6 is available.
With the above procedure, can I install the update without losing root and without losing my data ?
Thank you very much.
[email protected] said:
Flash full stock rom > flash magisk patched boot image (optional) > flash twrp > flash dm verity disabler > reboot
Click to expand...
Click to collapse
Sorry Bro information not with the right steps!
It is needed to wipe ?
After flashing ROM it is possible to flash Magisk? Or only patch boot IMG?
Flashing TWRP ?
Booting from Recovery to Recovery??
Plz right steps I'm in hospital I don't have a computer here.
Thanks a lot
Jakkomo77 said:
Sorry Bro information not with the right steps!
It is needed to wipe ?
After flashing ROM it is possible to flash Magisk? Or only patch boot IMG?
Flashing TWRP ?
Booting from Recovery to Recovery??
Plz right steps I'm in hospital I don't have a computer here.
Thanks a lot
Click to expand...
Click to collapse
You've older version of miui installed with twrp and device is rooted.
1) you don't need to wipe anything. Just flash the rom and If you want you can wipe caches after flashing the rom.
2) TWRP might get replaced with stock one so flash twrp immediately after flashing the ROM. Also flash DM Verity disabler zip otherwise miui will replace twrp with stock recovery.
3) According to topjohnwu, the method of getting magisk by flashing in recovery is old & deprecated and maintained with minimal efforts & no longer recommended.
I am on Miui 12.5.4 rooted with Magisk right now, no TWRP, and OTA update 12.5.6 is available.
With the above procedure, can I install the update without losing root and without losing my data ?
Click to expand...
Click to collapse
Ok so for those interested, here’s how I did it : 
- in Magisk I chose uninstall - restore image
- did the ota the normal way before any reboot
then had to reroot :
- downloaded the fastboot firmware here
- extracted boot.img from archive and transfered it to phone
- in magisk click install then select boot.img
- magisk writes a new file magisk_patched_[random_strings].img, copied it to pc
- booted the phone in fastboot mode
- used fastboot.exe with command fastboot flash boot magisk_patched_[random_strings].img
Done. No data or settings lost.

Should I update to Magisk 25.2 after flashing 24.3

According to this thread: https://forum.xda-developers.com/t/...1-legendarypixieos-4-1-for-galaxy-m21.4379385
Flashing 25.x with that certain rom bootloops, and I have that version of Magisk flashed and installed to my device, but the app is bothering me to download the latest version of it.
Should I continue? Since this is after the fact?
{
"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"
}
Magisk stopped patching avb and some other stuff since 25.0 so some roms and kernels that need it wont work anymore. But if you already had v24 installed everything should be already patched. I've noticed that if you're only flashing v25*, flashing dmverity disabler along with it fixes bootloops.
So in theory it should be okay if you already have magisk installed. However, dont forget to take a backup of your boot before doing anything.
Alright, I'll update the thread if everything goes well.
Thank you!
Whelp, it is bootlooping with no access to twrp and shutdown.
I'll try to turn it off by removing the battery and reflashing back the working 24.3.
Note to future-self:
You can uninstall the newer magisk version by renaming the APK of the version you updated to by renaming it to `uninstall.zip` and flashing it.
You can also get an infinitely bootlooping device to odin mode by holding the power up and down keys while being connected to a computer when the boot cycle starts.
I have successfully managed to update to v25.x. It seems patching the whole AP file causes issue related to vbmeta. Assuming you're on unmodified stock firmware, the solution is to only patch and flash the boot image. If you're installing/on a GSI, you'll also need to flash dmverity disabler.
Tne process that worked for me was:
1. Flash latest stock firmware.
2. Install Magisk Manager, patch boot image and flash it. Check Magisk Manager to ensure Magisk is installed.
3. Flash TWRP, perform factory reset from TWRP and flash GSI and dmverity disabler.
newt23 said:
I have successfully managed to update to v25.x. It seems patching the whole AP file causes issue related to vbmeta. Assuming you're on unmodified stock firmware, the solution is to only patch and flash the boot image. If you're installing/on a GSI, you'll also need to flash dmverity disabler.
Tne process that worked for me was:
1. Flash latest stock firmware.
2. Install Magisk Manager, patch boot image and flash it. Check Magisk Manager to ensure Magisk is installed.
3. Flash TWRP, perform factory reset from TWRP and flash GSI and dmverity disabler.
Click to expand...
Click to collapse
Greetings Friend,
Can you attach the Dmverity Disabler zip?
OldNoobOne said:
Greetings Friend,
Can you attach the Dmverity Disabler zip?
Click to expand...
Click to collapse
Greetings Friend newt23,
Can you also elaborate on the exact steps you did to get the GSI to boot.
I mean steps like which GSI booted? & did you put the GSI in sdcard then use terminal commands like- { mount partition system, cd documents, super flash system.img etc., did you use chodoe flasher, gapps }?
Thanks in advance.
Also, Magisk 26.1 seemed more stable on stock rom without the addon.d script ability on stock but some devs insisting on staying with 24.3 stable even though 26.1 has better SafetyNet but. What would be your advice?

Categories

Resources