After updating to this firmware I lost root. So I tried as usual to flash via fastboot twrp-3.6.0_11-0-I001D.img and then in recovery magisk 23.0 (24.1 makes twrp crash). When I reeboot into system (after clearing dalvik/cache) magisk is not installed, although the flashing of the zip in recovery was flawless. i even reflashed the stock rom+magisk (losing the twrp recovery) but no way magisk was there.
With the previous rom versions nevere had this problem. Is it a trick og the new rom to prevent from rooting? Any idea? Suggestions?
fux1976 said:
After updating to this firmware I lost root. So I tried as usual to flash via fastboot twrp-3.6.0_11-0-I001D.img and then in recovery magisk 23.0 (24.1 makes twrp crash). When I reeboot into system (after clearing dalvik/cache) magisk is not installed, although the flashing of the zip in recovery was flawless. i even reflashed the stock rom+magisk (losing the twrp recovery) but no way magisk was there.
With the previous rom versions nevere had this problem. Is it a trick og the new rom to prevent from rooting? Any idea? Suggestions?
Click to expand...
Click to collapse
so...basically, you are unable to root using either the TWRP or simply Magisk?
What version of Magisk were you using?
I am thinking of updating but I need root access so the situation you are facing is worrisome to me.
ausaras said:
so...basically, you are unable to root using either the TWRP or simply Magisk?
What version of Magisk were you using?
I am thinking of updating but I need root access so the situation you are facing is worrisome to me.
Click to expand...
Click to collapse
I updated to the latest version and as always installed magisk to the inactive slot before reboot. Update was fine and root intact.
I was on magisk 24.1
gilsol said:
I updated to the latest version and as always installed magisk to the inactive slot before reboot. Update was fine and root intact.
I was on magisk 24.1
Click to expand...
Click to collapse
Thank you very much for sharing. This puts my mind at ease.
I will update when I find the time.
Thanks, again!
jb
*issue resolved*
Related
Hello everyone, I am using OOS 4.1.6 on my new 3T, however I am unable to get root even though I have already tried with latest TWRP, magisk 12, and SuperSU 2.82. Nothing worked everytime I've got not rooted on root checker.
Please describe in steps what you did.
AcidNoteZ said:
Please describe in steps what you did.
Click to expand...
Click to collapse
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.
mittal.bti said:
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.
Click to expand...
Click to collapse
Well first of all, format your whole phone over TWRP. (System too, but make sure you have the full Oxygen OS zip on a computer.)
After formating all partitions, move the full OOS zip and Magisk 12.0 on your phone. Flash the OOS zip, restart your recovery and flash Magisk after it.
That worked 100% for me all the time.
If you still need assistance with that, we can setup Teamviewer so I can guide you through this.
mittal.bti said:
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.
Click to expand...
Click to collapse
Same here! The phone freezes in boot animation screen. Even the animation stopped!
Guessing it's about the f2fs file system. I used to have a situation like this with Oneplus 2. My step was to format data and cache partitions back to ext4, and that worked.
Using 3t now, still not rooted. Don't want to start over after bootloader unlocking
Sent from my ONEPLUS A3003 using Tapatalk
I had the same problem and was solved with twrp 3.0.4-1 and SuperSU-v2.82.
AcidNoteZ said:
Well first of all, format your whole phone over TWRP. (System too, but make sure you have the full Oxygen OS zip on a computer.)
After formating all partitions, move the full OOS zip and Magisk 12.0 on your phone. Flash the OOS zip, restart your recovery and flash Magisk after it.
That worked 100% for me all the time.
If you still need assistance with that, we can setup Teamviewer so I can guide you through this.
Click to expand...
Click to collapse
Should I flash whole os using twrp. Or should I flash Via adb sideload?
ajsonofgod said:
Should I flash whole os using twrp. Or should I flash Via adb sideload?
Click to expand...
Click to collapse
If you still want root, twrp, if dont flash it over adb
AcidNoteZ said:
If you still want root, twrp, if dont flash it over adb
Click to expand...
Click to collapse
Ok, I will try and update here then.
I'd say wipe everything possible in TWRP except for system partition, then boot the system and then eventually flash some kind of a root package - either Magisk or SuperSU. I always do it that way and it works. I am not really sure but otherwise it might have something to do with the data encryption.
Use following and you should be all set (just did it 2 days ago):
1st Flash Stock Recovery (go back to stock - https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Flash TWRP after you achieve STOCK OS 4.1.6.
Use this TWRP version for now (there is some issue with 3.1.1-2 i saw on forums):
twrp-3.1.1-0-oneplus3t.img
To Root just use Magisk-v13.3.zip (IMO way better than SuperSu + has MagiskHide for AndroidPay/Snapchat/SafetyNet checks):
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
That is it, done!
Showbiz81 said:
I had the same problem and was solved with twrp 3.0.4-1 and SuperSU-v2.82.
Click to expand...
Click to collapse
Thanks you are a life saver
I had the same problem and was solved with twrp 3.0.4-1 and Magisk-v13.3
Hey all, I have always updated each month using the simple methods posted here, just doing a fresh install of each factory image.
I have got the november update installed, TWRP installed. However, I cannot for the life of me get the magisk install to "take".
I have installed various versions, 16.7 17.1 and 17.3 in TWRP, have rebooted to system each time, and yet no magisk zip. Have even tried doing fresh install wiping system, magisk uninstall, etc. Anything you can think I am doing wrong?
I just checked and its nothing wrong with the TWRP method... I was just able to install sultan zip from it. Any other way I can get magisk manager/Magisk zips? I have always just flashed the zip from TWRP. please help, thanks
Cowbell_Guy said:
Hey all, I have always updated each month using the simple methods posted here, just doing a fresh install of each factory image.
I have got the november update installed, TWRP installed. However, I cannot for the life of me get the magisk install to "take".
I have installed various versions, 16.7 17.1 and 17.3 in TWRP, have rebooted to system each time, and yet no magisk zip. Have even tried doing fresh install wiping system, magisk uninstall, etc. Anything you can think I am doing wrong?
I just checked and its nothing wrong with the TWRP method... I was just able to install sultan zip from it. Any other way I can get magisk manager/Magisk zips? I have always just flashed the zip from TWRP. please help, thanks
Click to expand...
Click to collapse
Very strange, but it just worked, after the 20th time of doing the same thing. Who knows why
Hey, my issue with Magisk is a bit different. I've upgraded my Pixel 2 XL every month and flashed Magisk afterwords. What I keep running into for the past couple of months is that after I'm all done, I will get a notification that there's an update to Magisk, but it's the same version I already have. I've tried different versions from 16.7 to the beta 17.3 and I would always seem to lose root after a while and be prompted to download the update to Magisk. Any help is greatly appreciated! Thanks in advance.
I am having the same issue with magisk after updating to nov update. Did the flashall then booted twrp and flash magisk Not sure why
Cowbell_Guy said:
Hey all, I have always updated each month using the simple methods posted here, just doing a fresh install of each factory image.
I have got the november update installed, TWRP installed. However, I cannot for the life of me get the magisk install to "take".
I have installed various versions, 16.7 17.1 and 17.3 in TWRP, have rebooted to system each time, and yet no magisk zip. Have even tried doing fresh install wiping system, magisk uninstall, etc. Anything you can think I am doing wrong?
I just checked and its nothing wrong with the TWRP method... I was just able to install sultan zip from it. Any other way I can get magisk manager/Magisk zips? I have always just flashed the zip from TWRP. please help, thanks
Click to expand...
Click to collapse
Run the Magisk uninstaller first
run 17.1 or the uninstaller. i've had better luck with 17.1
I guess the issue is linked to the Active Edge Module!
Download "uninmod_magisk", install it via TWRP, execute it via Terminal in TWRP, delete the Active Edge Module.
Now you can boot and reinstall that module.
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!
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
hello
I have rooted my device with magisk patch boot image and it work .my device is rooted.
but when I restart my device root has lost.
I have try 3-4 time this process but each time after device restart root has lost.
pls help...
miui version- miui global 14.0.3
magisk version - 26.1
wakram001 said:
hello
I have rooted my device with magisk patch boot image and it work .my device is rooted.
but when I restart my device root has lost.
I have try 3-4 time this process but each time after device restart root has lost.
pls help...
miui version- miui global 14.0.3
magisk version - 26.1
Click to expand...
Click to collapse
I suggest you install the latest Orang fox recovery if you don't have it or if you don't have custom recovery. Ive had issues with magisk "sticking" bc of the installed recovery. Flash Magisk zip via recovery then reboot to system and make sure it's still there. Make a copy of magisk zip and rename it "uninstall.zip" Then reboot to recovery and flash uninstall.zip. Then reboot to system then again to recovery and reflash Magisk zip. You can also try installing magisk alpha
Aserar said:
I suggest you install the latest Orang fox recovery if you don't have it or if you don't have custom recovery. Ive had issues with magisk "sticking" bc of the installed recovery. Flash Magisk zip via recovery then reboot to system and make sure it's still there. Make a copy of magisk zip and rename it "uninstall.zip" Then reboot to recovery and flash uninstall.zip. Then reboot to system then again to recovery and reflash Magisk zip. You can also try installing magisk alpha
Click to expand...
Click to collapse
i don't want to install custom recovery.[ bcz of ota update].
is there any way to fix this issue?
Flash Magisk zip
wakram001 said:
i don't want to install custom recovery.[ bcz of ota update].
is there any way to fix this issue?
Click to expand...
Click to collapse
Most people will have minimum to no experience regarding your situation honestly since its rare to root without the safty of a custom recovery. I think you should ask in the main magisk XDA thread or consider a custom recovery. Its hard to pinpoint the reason in this situation
Aserar said:
Most people will have minimum to no experience regarding your situation honestly since its rare to root without the safty of a custom recovery. I think you should ask in the main magisk XDA thread or consider a custom recovery. Its hard to pinpoint the reason in this situation
Click to expand...
Click to collapse
ok now I will consider custom recovery.( twrp ).