HI there, so after patching the Boot.img with Magiskv23, it seems as if flashing it with ABD/Fastboot causes the bootloop. I had to flash to flash the stock boot.img back. Any advices? As I research this seems to be an issue with the fix being "I made some investigation and checked that replacing the file in the Magisk-v21.4.zip/arm/magiskboot with the magiskboot from v21.0 and flashing that one fixes the problem." But I have no idea how it'd work.
My device used to work with Magiskv21 until I updated my device and it has to be rooted again. So I got the stock boot.img file, patched it adb/fastboot flash it into the device (same method as before) and it causes bootloop.
If you experience a bootloop, attach a dmesg (kernel logs) when the device refuse to boot. This may very likely require a custom kernel on some devices as last_kmsg or pstore ramoops are usually not enabled by default.
HOW do I do this?
In addition, please also upload the result of cat /proc/mounts when your device is working correctly WITHOUT ROOT.
I can't go back to unrooting it, as I still want to keep my data on the device. Is there any way I could attach this without unrooting it?
If you experience issues during installation,
boot.zip
in recovery, upload the recovery logs, or in Magisk, upload the install logs. Please also upload the boot.img or recovery.img that you are using for patching.
Will include both stock boot.img, and stable and v23001 patched files.
I'll upload the boot.img file I use and the patched_boot.img file.
I can't upload with github so here https://drive.google.com/drive/folders/1YkekFaXmtOg6d5sMiecf3OnT7oqCEf4S?usp=sharing
Uploading boot.zip…
Device: Xiaomi 10T Pro (apollo) with MIUI Global Stable 12.5.1.0 (RJDMIXM)
Android version: 11 RKQ1.200826.002
Magisk version name: 23001
Magisk v23001 (I chose canary because that's what's needed to submit this report but I tried stable and the issue is the same as well)
Magisk version code: f822ca5(23001)
chinjangs said:
HI there, so after patching the Boot.img with Magiskv23, it seems as if flashing it with ABD/Fastboot causes the bootloop. I had to flash to flash the stock boot.img back. Any advices? As I research this seems to be an issue with the fix being "I made some investigation and checked that replacing the file in the Magisk-v21.4.zip/arm/magiskboot with the magiskboot from v21.0 and flashing that one fixes the problem." But I have no idea how it'd work.
My device used to work with Magiskv21 until I updated my device and it has to be rooted again. So I got the stock boot.img file, patched it adb/fastboot flash it into the device (same method as before) and it causes bootloop.
If you experience a bootloop, attach a dmesg (kernel logs) when the device refuse to boot. This may very likely require a custom kernel on some devices as last_kmsg or pstore ramoops are usually not enabled by default.
HOW do I do this?
In addition, please also upload the result of cat /proc/mounts when your device is working correctly WITHOUT ROOT.
I can't go back to unrooting it, as I still want to keep my data on the device. Is there any way I could attach this without unrooting it?
If you experience issues during installation,
boot.zip
in recovery, upload the recovery logs, or in Magisk, upload the install logs. Please also upload the boot.img or recovery.img that you are using for patching.
Will include both stock boot.img, and stable and v23001 patched files.
I'll upload the boot.img file I use and the patched_boot.img file.
I can't upload with github so here https://drive.google.com/drive/folders/1YkekFaXmtOg6d5sMiecf3OnT7oqCEf4S?usp=sharing
Uploading boot.zip…
Device: Xiaomi 10T Pro (apollo) with MIUI Global Stable 12.5.1.0 (RJDMIXM)
Android version: 11 RKQ1.200826.002
Magisk version name: 23001
Magisk v23001 (I chose canary because that's what's needed to submit this report but I tried stable and the issue is the same as well)
Magisk version code: f822ca5(23001)
Click to expand...
Click to collapse
when you were setting up the patched file you made sure you didnt choose rrecovery method in the magisk app
also rather flash it through twrp there are probably scripts that twrp has to run during the installation
if you dont have twrp you can flash it to recovery if you can access your fastboot/bootloader
reboot to recovery after then flash the patched boot.img to boot in twrp
(i dont know if you should clear cache or data or not just look for the guide )
reboot
flairepathos.info said:
when you were setting up the patched file you made sure you didnt choose rrecovery method in the magisk app
also rather flash it through twrp there are probably scripts that twrp has to run during the installation
if you dont have twrp you can flash it to recovery if you can access your fastboot/bootloader
reboot to recovery after then flash the patched boot.img to boot in twrp
(i dont know if you should clear cache or data or not just look for the guide )
reboot
Click to expand...
Click to collapse
I'm not sure how to use twrp, but I've rooted this device already just have issues with installing magisk patching boot.img after updating from magisk v20=>v23.
After that using boot.img that has been patched by magisk just causes bootloops.
Thanks for you comment though <3
chinjangs said:
I'm not sure how to use twrp, but I've rooted this device already just have issues with installing magisk patching boot.img after updating from magisk v20=>v23.
After that using boot.img that has been patched by magisk just causes bootloops.
Thanks for you comment though <3
Click to expand...
Click to collapse
Yes the stock boot image is locked bootloader so you will boot loop, flash magiskpatched boot image again to stop bootloop , even if its the old patched one
flairepathos.info said:
Yes the stock boot image is locked bootloader so you will boot loop, flash magiskpatched boot image again to stop bootloop , even if its the old patched one
Click to expand...
Click to collapse
Are you suggesting I use the old stock image where it works before I updated the magisk to version 23?
(I did that and it still bootloops)
Thank you for everyone's help. I've solved this by Uninstalling magisk v23001 and reinstalling magisk v23 thru TWRP in this method https://forum.xda-developers.com/t/...tom-rom-working-on-xiaomi-mi-10t-pro.4246339/
Related
I tried it many times. After flashing Magisk from orange fox I tap on reboot and it always shows me this boot/recovery corrupt message and didn't start. Can anyone help me?
Sumit Sikder said:
I tried it many times. After flashing Magisk from orange fox I tap on reboot and it always shows me this boot/recovery corrupt message and didn't start. Can anyone help me?
Click to expand...
Click to collapse
My boot partition was corrupted when I installed Magisk also. I installed from ADB after extracting stock boot.img and patching it with Magisk, then flashed patched.img with ADB,. There were no warnings and flashing had no errors.
I had to flash stock ROM to boot again.
My only guess would be to try flashing newer versions of Magisk. Hope we can get help
I tried the latest v22.1. It worked in Android 11 evolution X ROM but not in realme UI 1! The only reason I installed my Android 10 was because Magisk modules weren't working in Android 11!
oxbowlarry said:
My boot partition was corrupted when I installed Magisk also. I installed from ADB after extracting stock boot.img and patching it with Magisk, then flashed patched.img with ADB,. There were no warnings and flashing had no errors.
I had to flash stock ROM to boot again.
My only guess would be to try flashing newer versions of Magisk. Hope we can get help
Click to expand...
Click to collapse
I have seen another rooting method with ADB and the patched boot image BUT that method first flashes vbmeta.img before flashing the patched boot.img.
Perhaps that is why my boot partition was corrupted because I just flashed the patched boot.img.
Has anyone had success with this rooting method on a Realme 6 pro ?
Hello, this morning I found my poco f3 updated to Miui 12.5.3.0 (I was on 12.5.0.0) even though I had automatic updates disabled. After the automatic update I lost my root via magisk and twrp in recovery. No problem, I got twrp installed again, then I proceeded to install magisk v23.0 from TWRP, as I had done after 12.5.0.0. update.
Afterwars phone is stuck in a bootloop. I reflashed stock boot image, recovering the phone, but I ave been unable to install magisk in 12.5.3.0, I tried copying boot.img to the phone, then using magisk manager to patch the boot image, then flash the patched image trough fastboot, with the same result.
Anyone knows how to make magisk work in this new update?
Thank you
suloku said:
Hello, this morning I found my poco f3 updated to Miui 12.5.3.0 (I was on 12.5.0.0) even though I had automatic updates disabled. After the automatic update I lost my root via magisk and twrp in recovery. No problem, I got twrp installed again, then I proceeded to install magisk v23.0 from TWRP, as I had done after 12.5.0.0. update.
Afterwars phone is stuck in a bootloop. I reflashed stock boot image, recovering the phone, but I ave been unable to install magisk in 12.5.3.0, I tried copying boot.img to the phone, then using magisk manager to patch the boot image, then flash the patched image trough fastboot, with the same result.
Anyone knows how to make magisk work in this new update?
Thank you
Click to expand...
Click to collapse
Try flashing the older patched boot.img on the new stock firmware.
On the 12.5.3.0 ill patched boot.img from 12.5.1.0 and all right.
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
i have the same issue of auto updated and lost my root access.
Which boot.img I should Magish'd to get the root access again?
Currently installing my twrp
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
if Flash Current TWRP fails, go to Backup > Refresh Sizes and try Flash Current TWRP again
Click to expand...
Click to collapse
Currently at the Resizing stage
Edit 1: failed, I have the error bootctrl error that prevent me from installing after resizing.
I have flashed the twrp3.5.2 directly to boot resulting in bootloop and needed to install the Boot.img from the 12.5.1 from the previous bulit
Edit: actually I can ignore that error.
Magisk installed but safety checked failed even I have the "universal safety check module installed "
Also the app thoax isn't working
I'd try removing all magisk modules, installing stock 12.5.3, then using magisk apk to create patched boot.img and flash it with fastboot (fastboot flash boot magisk_boot_patched.img)
Also, maybe try flashing bot boot_a and boot_b? I had a problem were my active boot partition changed and phone became even more broken.
suloku said:
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
Might wanna also uncheck Automatic system updates in the Developer settings to be safe.
suloku said:
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
There is a setting in the Xiaomi system updater that had by default checked auto-update. That setting need to be disabled/unchecked as well.
Since you have root with Magisk, can also Force stop or debloat the updater app, so the system will not update itself.
suloku said:
Thanks for your replies. It seems the problem was a module I had installed being incompatible with the update (smali patcher). I tried removing the module from /data/odb/modules/ via twrp after installing magisk (also via twrp) and everything finally booted just fine!
But I hope this time disabling automatic updates works as intended
Click to expand...
Click to collapse
I had the same issue on Redmi Note 9 Pro (joyuse). Based on your tip I've removed some modules from `data/adb/modules` and my device is finally booting normally. Thanks!
The magisk apk, when flashed in TWRP flashes as normal but the app does not show up in the ROM, and the phone doesn't get rooted.
I had this problem on both ArrowOS and Syberia OS now, and I clean flashed both times directly from MIUI.
Can anyone help me out with this?
Install the magisk app
Rename magisk.apk to magisk.zip (only change the last 3 letters) and install it from TWRP-recovery.
zhyylz0201 said:
Install the magisk app
Click to expand...
Click to collapse
I already tried, this happened -
Iceman66 said:
Rename magisk.apk to magisk.zip (only change the last 3 letters) and install it from TWRP-recovery.
Click to expand...
Click to collapse
It didn't work either, when I open magisk app it shows this -
Download Canary version of Magisk (23001) from Github: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Rename app-debug.apk to app-debug.zip and flash it with TWRP
Iceman66 said:
Download Canary version of Magisk (23001) from Github: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Rename app-debug.apk to app-debug.zip and flash it with TWRP
Click to expand...
Click to collapse
No change
Other method is patching boot.img with magisk manager. You can find some tutorials with google. Extract the boot.img from ROM.zip, put in on internal memory of your phone and patch it with magisk manager app on your phone.
Than flash the patched boot.img with adb or TWRP. You need an extractor tool to get the boot.img from the rom.zip.
Iceman66 said:
Other method is patching boot.img with magisk manager. You can find some tutorials with google. Extract the boot.img from ROM.zip, put in on internal memory of your phone and patch it with magisk manager app on your phone.
Than flash the patched boot.img with adb or TWRP. You need an extractor tool to get the boot.img from the rom.zip.
Click to expand...
Click to collapse
I am using a custom kernel, will that change the process?
You need to reflash the custom kernel again after flashing the patched boot.img, but first check if your phone is rooted. (check in magisk app or install a root check app.)
The boot backup that I took before I flashed my custom kernel is the one that needs to be patched right?
If this isn't the case, can you guide me on how to get the boot.img? I only see payload.bin in my ROM.zip .
Okay, thank you for your help everyone
I ran into a different problem - when I install the patched boot.img, I get magisk but then I boot into TWRP and flash TWRP and my custom kernel, and I lose my root.
Dhruv.m said:
Okay, thank you for your help everyone
I ran into a different problem - when I install the patched boot.img, I get magisk but then I boot into TWRP and flash TWRP and my custom kernel, and I lose my root.
Click to expand...
Click to collapse
You have to patch the boot IMG with the TWRP already flashed, our phone doesn't have a recovery partition, so it's saved in the boot partition and installing Magisk from TWRP deletes the recovery, here is a good tutorial:
TWRP + Root
Hi all. Hope you are good and safe from Covid-19. If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP...
forum.xda-developers.com
Hello
I have big problem.
After patching img over Magisk and flash this new patched img, can not start system / boot loop to POCO logo, or boot loop to MIUI logo - here system starting, but every restart and boot loop
Help please
Thanks
Hi!
Which boot-img did you patch and where did it come from?
How did you flash it?
So:
I received an update 12.5.8.0.RKHEUXM
After the update, I always have to root the phone again.
So I took boot.img from the original 12.5.8.0.RKHEUXM and patched it via Magisk.
I flashed the patched boot.img via ADB.
Well, after the restart, my phone will boot only after the MIUI logo and a bit of a melody, and the phone will restart again. This restart is performed about 4 times and remains/stops in fastboot mode,or it will return to TWRP after clearing dalvik and cache and restarting.
He does what he wants
I've had a problem with that before, but it was enough to delete Dalvik and the cache via temporary TWRP.
Then the system booted up normally, but now it doesn't work even after deleting Dalvik and the cache.
Here is a link to the thread where I solved it. Nobody actually advised me there, I just tried to clear dalvik and cache via TWRP and it was after the problem. Unfortunately, now the problem persists.
Poco F3 - Boot Loop to POCO logo / Please help
Hello. I have a big problem after updating the firmware. Poco F3 root over magisk. After updating from 12.5.6.0 RKHEUXM, I updated to 12.5.7.0 RKHEUXM. After the restart, both the phone and the system booted up. I patched the original boot.img...
forum.xda-developers.com
Thats what I did also with 12.5.8.0.RKHEUXM and everything is working fine.
Updated to 12.5.8.0 via the MIUI updater, but downloading the full rom, as the updater told me that the incremental update (~58MB) wouldn't work.
Then downloaded the the recovery file here: https://xiaomifirmwareupdater.com/miui/alioth/stable/V12.5.8.0.RKHEUXM/
Unzipped it and extracted the boot.img with payload-dumper-go on my Mac: https://github.com/ssut/payload-dumper-go
Patched the boot.img with Magisk on the phone.
Copied the patched_boot.img file back to the Mac.
Flashed the patched_boot.img from the mac with fastboot to both partitions:
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Friend, I did exactly what you were writing, and unfortunately my system won't start
The only thing I did differently was to download the big rom 6gb update so I didn't have to extract boot.img. I didn't have to use a payload dumper.
Any other solution?
But I don't want to lose data and applications!
Did you try wiping data partition?
takichiman said:
Did you try wiping data partition?
Click to expand...
Click to collapse
Where should I do it?
But I don't want to lose data and applications!!!!!
I have bootloop to MIUI logo 4times - 5times and then stop in fastboot mode , It stops in fastboot mode and after pressing and holding the power button, the mobile starts only in fastboot mode, it no longer starts booting to the MIUI log
You can do it from recovery.
If you have twrp recovery you can backup your data before wiping.
But I'd only recommend backuping pictures(files) not the apps which you can reinstall.
takichiman said:
You can do it from recovery.
If you have twrp recovery you can backup your data before wiping.
But I'd only recommend backuping pictures(files) not the apps which you can reinstall.
Click to expand...
Click to collapse
You didn't give me much advice, my friend
I don't want to lose any data, or applications, pictures, just anything.
If it went after deleting the dalvik / cache last time, then why shouldn't it go now?
The system boots only to the miui logo, then the boot loop.
I don't understand why this is so.
And can't you somehow refresh the whole rom without losing data, applications and files?
Boot temp recovery, backup boot, patch backed boot and flash patched boot ... Just rename the boot backed image of twrp in boot.img, patch and flash ...
Try reflashing the official boot.img, you won't have root but at least you will be able to boot your phone. Also if you have TWRP why aren't just rooting your phone with the Magisk.zip instead of patching the boot.img yourself ?
Dark-Yox said:
Try reflashing the official boot.img, you won't have root but at least you will be able to boot your phone. Also if you have TWRP why aren't just rooting your phone with the Magisk.zip instead of patching the boot.img yourself ?
Click to expand...
Click to collapse
I tryed flashing official boot image, but still dont work.
Reboot back to recovery or booting only to miui logo and bootloop
Do you have module in magisk? Remove them ...
Frequently Asked Questions
The Magic Mask for Android
topjohnwu.github.io
snx413 said:
Do you have module in magisk? Remove them ...
Frequently Asked Questions
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
Yes, I have modules in Magisk.
How do I remove modules in Magisk if I don't get into the system — I don't boot
jkmaxfli said:
Yes, I have modules in Magisk.
How do I remove modules in Magisk if I don't get into the system — I don't boot
Click to expand...
Click to collapse
When you boot, you have access normally
snx413 said:
When you boot, you have access normally
Click to expand...
Click to collapse
And how do I remove them? instructions please
jkmaxfli said:
Yes, I have modules in Magisk.
How do I remove modules in Magisk if I don't get into the system — I don't boot
Click to expand...
Click to collapse
You can remove them in TWRP
jkmaxfli said:
I tryed flashing official boot image, but still dont work.
Reboot back to recovery or booting only to miui logo and bootloop
Click to expand...
Click to collapse
Dirty flash the whole ROM then
Adb shell
then
magisk --remove-modules
Dark-Yox said:
You can remove them in TWRP
Dirty flash the whole ROM then
Click to expand...
Click to collapse
How it dirty flash ?
I used it over TWRP recovery ROM zip file, and not work flashing
I have OnePlus7T Indian version. I was on 11.0.9.1 and rooted with Magisk Canary version. There was an Update to Magisk which I accidentally installed with OTA option instead of full. Now my phone is not booting. It goes into original recovery mode or fastboot only. How can I recover from this? I tried to flash the magisk patched image file and it shows as flashed but when I reboot I again reach original recovery / fastboot menu only. Please help!!
Problem solved but don't know how. I was trying many things and when I used Tool All in One to flash TWRP the phone rebooted into the system. Not even sure if TWRP is installed or not but everything is working now and phone is rooted. Not sure how it got resolved. Magisk is updated to latest version.
jesrani said:
Problem solved but don't know how. I was trying many things and when I used Tool All in One to flash TWRP the phone rebooted into the system. Not even sure if TWRP is installed or not but everything is working now and phone is rooted. Not sure how it got resolved. Magisk is updated to latest version.
Click to expand...
Click to collapse
Most likely changed slot accidentally when it crashed and then corrected on multiple interventions
HueyT said:
Most likely changed slot accidentally when it crashed and then corrected on multiple interventions
Click to expand...
Click to collapse
Hi. I am again having same problem. I updated Magisk Manager and Magisk and some other apps and phone was not booting. After many tries it again booted but all the modules in Magisk were off. So I switched them on and rebooted the phone and now it is just not booting. I tried to use Tool All In One to flash a TWRP but now there is no recovery. The phone is either not booting (stuck on Circle dot rotating) or just going into fastboot, does not go into recovery. I was on OOS11. I tried flashing original recovery through the tool but it fails. Any way out of this mess??
jesrani said:
Hi. I am again having same problem. I updated Magisk Manager and Magisk and some other apps and phone was not booting. After many tries it again booted but all the modules in Magisk were off. So I switched them on and rebooted the phone and now it is just not booting. I tried to use Tool All In One to flash a TWRP but now there is no recovery. The phone is either not booting (stuck on Circle dot rotating) or just going into fastboot, does not go into recovery. I was on OOS11. I tried flashing original recovery through the tool but it fails. Any way out of this mess??
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
This will wipe your data. Otherwise, you can try manually fastboot flash each individual files of oos11 rom:
⭐[ROM][STOCK] 11.0.9.1-GLOBAL-OnePlus7TOxygen_14.O.35_GLO_0350_2206171459-FASTBOOT
Created my own FASTBOOT Rom can anybody test this out, to see if it works please? Used to "Restore the Firmware" on your phone or when bricked you cannot downgrade or upgrade with FASTBOOT Roms, you must be on the same (Firmware Update Global...
forum.xda-developers.com
HueyT said:
This will wipe your data. Otherwise, you can try manually fastboot flash each individual files of oos11 rom:
Click to expand...
Click to collapse
Thanks. I managed to boot the phone but having root problems. After spending a number of hours doing various trials and checking Xda threads I managed to get it to boot again but root was lost.
I again read more articles and learnt that I have to flash recovery to both partitions so I used Tool All in one, changed active slots and flashed the magisk patched image from this thread i think on both slots. But i am not sure. I managed to get root but the Magisk manager was not getting installed.
I tried few other things and finally i am now not able to root again. Phone is booting after I flash a recovery but I am not sure if it will boot if restarted or go into loop.
Can anyone explain the proper procedure and sequence to follow for rooting and which files to use.
I am on OOS11.09.1
jesrani said:
Thanks. I managed to boot the phone but having root problems. After spending a number of hours doing various trials and checking Xda threads I managed to get it to boot again but root was lost.
I again read more articles and learnt that I have to flash recovery to both partitions so I used Tool All in one, changed active slots and flashed the magisk patched image from this thread i think on both slots. But i am not sure. I managed to get root but the Magisk manager was not getting installed.
I tried few other things and finally i am now not able to root again. Phone is booting after I flash a recovery but I am not sure if it will boot if restarted or go into loop.
Can anyone explain the proper procedure and sequence to follow for rooting and which files to use.
I am on OOS11.09.1
Click to expand...
Click to collapse
[OP7T][Stock/Magisk v23.0] OxygenOS 11.0.9.1.HD65AA boot.img
OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img Stock: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g Magisk v23.0 Patched: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc Note: DISABLE...
forum.xda-developers.com
HueyT said:
[OP7T][Stock/Magisk v23.0] OxygenOS 11.0.9.1.HD65AA boot.img
OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img Stock: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g Magisk v23.0 Patched: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc Note: DISABLE...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi. I already used these boot images but I was still having a problem. I had flashed the stock image to both partitions and then the Magisk patched image also but either I was not rooted or Magisk App not working. Finally got things to work by installing TWRP to partition a I believe. I changed active partition to a and then flashed the twrp recovery. Again changed active to b and booted and had root. I had to install Magisk Canary 25210 version only as other versions did not install. After checking on net it seems this version is faulty. So I installed Magisk Delta, then installed Magisk using Direct Install option, rebooted, checked regular Magisk Manager and showed the same Magisk version. Removed all modules from old Magisk Manager and unstalled the app. Setup Magisk Delta modules, hide, SuList as well as apps like LSPosed, HMA etc and now everything is working again.
I still am not very sure where the recovery is installed, on partition a or b? And if a difference recovery is installed on each partition what happens? I am pretty sure I had not installed TWRP on partition b. I am also assuming that once I set a partition as active and flash a recovery in fastboot that recovery is flashed to that partition, is this correct? Things are working but I don't know if the phone will go to recovery mode from system, I have not tried that. So I am not very clear yet but still got things to work.
jesrani said:
Hi. I already used these boot images but I was still having a problem. I had flashed the stock image to both partitions and then the Magisk patched image also but either I was not rooted or Magisk App not working. Finally got things to work by installing TWRP to partition a I believe. I changed active partition to a and then flashed the twrp recovery. Again changed active to b and booted and had root. I had to install Magisk Canary 25210 version only as other versions did not install. After checking on net it seems this version is faulty. So I installed Magisk Delta, then installed Magisk using Direct Install option, rebooted, checked regular Magisk Manager and showed the same Magisk version. Removed all modules from old Magisk Manager and unstalled the app. Setup Magisk Delta modules, hide, SuList as well as apps like LSPosed, HMA etc and now everything is working again.
I still am not very sure where the recovery is installed, on partition a or b? And if a difference recovery is installed on each partition what happens? I am pretty sure I had not installed TWRP on partition b. I am also assuming that once I set a partition as active and flash a recovery in fastboot that recovery is flashed to that partition, is this correct? Things are working but I don't know if the phone will go to recovery mode from system, I have not tried that. So I am not very clear yet but still got things to work
Click to expand...
Click to collapse
Only data partition is shared. All else have both A and B parts