Nowadays Magisk is integrated in to almost all Nougat ROM's. For some it works flawlessly, for some its getting conflicted with various apps. Those who are facing problems with Magisk can remove it from the ROM before flashing using the below method. Including flash files of Lineage OS rooting file & removal file.
1) Unzip the ROM flashfile
2) Delete magicsk folder
3) Go to META-INF>com>google>android>updater-script
4) Open with Notepad++ (https://notepad-plus-plus.org/download/v7.3.3.html)
5) After opening the script file, find these lines below, remove them and save the file
ui_print(" ");
ui_print("Flashing Magisk...");
ui_print(" ");
package_extract_dir("magisk", "/tmp/magisk");
run_program("/sbin/busybox", "unzip", "/tmp/magisk/magisk.zip", "META-INF/com/google/android/*", "-d", "/tmp/magisk");
run_program("/sbin/sh", "/tmp/magisk/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/magisk/magisk.zip");
ui_print(" ");
6) Zip back all the files using winrar or win zip
7) Copy this to phone and flash the ROM
8) Now flash SuperSU or Flash lineage OS rooting zip file (See the attachment) to root.
9) Uninstall Magisk using system app uninstaller
Congrats, you're good to go !!
Note : Also including Magisk Uninstaller below. It used to work in previous builds and now its giving boot loops or just gets stucked in moto logo with vibrations. So try this at your own risk. Safer method is to remove it from ROM (above method) and flash it.
You make it very complicated
Enviado desde mi XT1562 mediante Tapatalk
flopezm said:
You make it very complicated
Enviado desde mi XT1562 mediante Tapatalk
Click to expand...
Click to collapse
Simple way is to uninstall using Magisk Uninstaller. But its giving boot loops on new builds. Hence this method. You're always welcome if having simpler method
Shibin_1985 said:
Simple way is to uninstall using Magisk Uninstaller. But its giving boot loops on new builds. Hence this method. You're always welcome if having simpler method
Click to expand...
Click to collapse
uninstaller is giving bootloops? lol report that to the magisk dev. And use the latest uninstaller instead of the old one you posted. This work around is way too complicated
This workaround is exactly right if you want to remove Magisk from a ROM before installing, which is exactly what I've been trying to do for most of Friday night, to no avail. I want to encrypt my device which has caused boot loops every single time, even when I temporarily disable root. Tried the latest Magisk uninstaller, same result even though it says there's no more root or Magisk available when I open it under settings (Resurrection Remix Nougat). I am going full anti-spying mode right now, and I had no idea that it would be so difficult to get encryption on a Custom ROM (AICP gave me boot loops as well).
Unfortunately, the above method described by @Shibin_1985 doesn't do it for me. When trying to flash, it immediately stops, reporting an error due to invalid zip signature (TWRP 3.1.1.0, jfvelte).
PrivacyDefector said:
This workaround is exactly right if you want to remove Magisk from a ROM before installing, which is exactly what I've been trying to do for most of Friday night, to no avail. I want to encrypt my device which has caused boot loops every single time, even when I temporarily disable root. Tried the latest Magisk uninstaller, same result even though it says there's no more root or Magisk available when I open it under settings (Resurrection Remix Nougat). I am going full anti-spying mode right now, and I had no idea that it would be so difficult to get encryption on a Custom ROM (AICP gave me boot loops as well).
Unfortunately, the above method described by @Shibin_1985 doesn't do it for me. When trying to flash, it immediately stops, reporting an error due to invalid zip signature (TWRP 3.1.1.0, jfvelte).
Click to expand...
Click to collapse
Download the latest Magisk uninstaller.. Else unzip the rom zip file, remove the Magisk folder in it & zip it back...
Thanks a lot for this tutorial, I was getting bootloop when trying to uninstall using magisk manager. This helps me out. Thanks a lot!!!
Related
This is my installation process [last post is OK]
https://forum.xda-developers.com/galaxy-s5/help/wifi-problem-flashed-lineageos-t3576865
Below are screens from CATLOG [not full tho]
If I try to update binaries in TWRP it stops [nothing in TWRP logs about SU], restarts and stops during Lineage loading screen forever.
So I flash ROM again, and SuperSU from TWRP to fix it.
I was reading that after flashing SuperSU - during first restart it should ask me something like "DO you want to keep root" - it doesn't happen.
SuperSU has no apps listed with root access, but root is OK. TitaniumBackup works, but I'm afraid some of the apps doesn't work properly
Now I'm using
lineage-14.1-20170329-nightly-klte-signed.zip
addonsu-ARM-signed_14.1
SM-G900F
Is there a way to have it done?
I remember like trough a fod that once I was setting permissions in Terminal for some files before updating SU? AM I correct?
Thanks for reding
Hi,
With LineageOS, you must only use one root method otherwise problems will occur. The addonSU zip and SuperSU are not the same thing.
The provided root SU zip from Lineage should be enough to give root permissions for apps. If you want to use SuperSU instead of the SU provided by the Lineage team, you must not flash the addonSU zip.
Saber said:
Hi,
With LineageOS, you must only use one root method otherwise problems will occur. The addonSU zip and SuperSU are not the same thing.
The provided root SU zip from Lineage should be enough to give root permissions for apps. If you want to use SuperSU instead of the SU provided by the Lineage team, you must not flash the addonSU zip.
Click to expand...
Click to collapse
I have tried to flash everything and indeed only addonsu-ARM-signed_14.1 is working from TWRP level. Although SuperSU from APK is working OK [latest SR4].
So root seems to be fine for browsing into root or TB! is not complaining about root, but I can not update SU binary - I have also updated Lineage to today's nightly - same thing.
I've used an S4 with lineage and flashing supersu doesn't work. ONE app in particular will not work because the su part of lineage (and old cyanogenmod) doesn't cooperate; it needs supersu for some reason. I was originally on Cyanogenmod from about a year ago, and tried flashing supersu and had this very problem, which is why I tried lineage, but lineage doesn't work and I cannot flash supersu either. I can install from the play store, but it won't update the binary; flashing in recovery fails (in both older cyanogenmod and lineage os) at the boot image patcher step.
supersu 2.79 said:
Finding boot image
Boot image: /dev/block/mmcblk0p20
Extracting ramdisk
Decompressing ramdisk
Failure, aborting
Click to expand...
Click to collapse
The only reason I'm having to resort to this is because Samsung has a problem with their s7 screens failing and won't do a recall...so I'm having to use an older phone and trying to setup my rooted apps, all of which work with the standard Cyanogenmod root or lineage+su addon, except for one app.
EDIT:
Ah-ha, system mode may be the solution, but I'm still trying to get it to boot without getting stuck! I haven't tinkered with supersu in well over a year, and I didn't even know there were two methods for it now.
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
Since going back to stock from the RR ROM, I've been using SuperSU 2.79 and really missing Magisk. Is it possible to use Magisk on the stock ROM, or is that only an option on LOS-based ROMs?
Flapjack said:
Since going back to stock from the RR ROM, I've been using SuperSU 2.79 and really missing Magisk. Is it possible to use Magisk on the stock ROM, or is that only an option on LOS-based ROMs?
Click to expand...
Click to collapse
Yes, it is obviously an option. Simply download Magisk 14.0 zip, then go to SuperSU --> Full Unroot, then the phone will restart; after it does go to TWRP and flash Magisk
Choose an username... said:
Yes, it is obviously an option. Simply download Magisk 14.0 zip, then go to SuperSU --> Full Unroot, then the phone will restart; after it does go to TWRP and flash Magisk
Click to expand...
Click to collapse
I haven't been able to uninstall supersu. Even after updating it to 2.82, it still says "uninstallation failed". Attempting to flash Magisk 14.0 fails also, as it detects an existing root method.
So install just boot.img from twrp and flash magisk.
Flapjack said:
I haven't been able to uninstall supersu. Even after updating it to 2.82, it still says "uninstallation failed". Attempting to flash Magisk 14.0 fails also, as it detects an existing root method.
Click to expand...
Click to collapse
Either do what WesTD says or find a SuperSU uninstaller zip (i think there's one around), or wipe system and reflash the ROM
Flapjack said:
I haven't been able to uninstall supersu. Even after updating it to 2.82, it still says "uninstallation failed". Attempting to flash Magisk 14.0 fails also, as it detects an existing root method.
Click to expand...
Click to collapse
I once did a full unroot of SU from a secondary ROM on my G3 and it wound up unrooting the phone itself. Bricked and out of service for some months (flashed so many ROMs it lost its LG identity so drivers never worked. Had to bring it back the hard way). Anyway...
What WesTD said is the easy way. Also the first time SU is flashed it saves the original boot image in the /data directory I believe with a gz extension (compressed). Gunzip it and you'll have your image you can flash.
Check the web for osm0sis' unSU script. It safely removes all of SU. For systemless you'll have to restore your boot image or dirty flash the ROM.
Ah, here we go...
http://forum.xda-developers.com/showthread.php?t=2239421
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
marcdw said:
I once did a full unroot of SU from a secondary ROM on my G3 and it wound up unrooting the phone itself. Bricked and out of service for some months (flashed so many ROMs it lost its LG identity so drivers never worked. Had to bring it back the hard way). Anyway...
What WesTD said is the easy way. Also the first time SU is flashed it saves the original boot image in the /data directory I believe with a gz extension (compressed). Gunzip it and you'll have your image you can flash.
Check the web for osm0sis' unSU script. It safely removes all of SU. For systemless you'll have to restore your boot image or dirty flash the ROM.
Ah, here we go...
http://forum.xda-developers.com/showthread.php?t=2239421
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]
Click to expand...
Click to collapse
Good stuff. Thank you!
I used Magisk for awhile on B19, but I've had too many issues with it, so I prefer Phh's Superuser. It's not nearly as well known, but it's fast, reliable, and works on the latest versions of Android (Oreo too). Basically it's the little guy that most don't know about or consider, they think Magisk and SuperSU are the only legit rooting games in town. I won't even give KingRoot/KingoRoot more than a mention, because they have ads and install crap, not to mention I've bricked a handful of low end phones by using these 2.
As far as ditching SuperSU (like if it's built into a rom, or you just want to switch, I use this order:
1. Flash osm0sis's unSU zip.
2. Extract your boot.img from whatever ROM zip you use, flash in TWRP
3. Flash Phh or Magisk zip and reboot
Reflashing system partition shouldn't be necessary, it's just the nuclear option of last resort that noone wants to do.
AnonVendetta said:
I used Magisk for awhile on B19, but I've had too many issues with it, so I prefer Phh's Superuser. It's not nearly as well known, but it's fast, reliable, and works on the latest versions of Android (Oreo too). Basically it's the little guy that most don't know about or consider, they think Magisk and SuperSU are the only legit rooting games in town. I won't even give KingRoot/KingoRoot more than a mention, because they have ads and install crap, not to mention I've bricked a handful of low end phones by using these 2.
As far as ditching SuperSU (like if it's built into a rom, or you just want to switch, I use this order:
1. Flash osm0sis's unSU zip.
2. Extract your boot.img from whatever ROM zip you use, flash in TWRP
3. Flash Phh or Magisk zip and reboot
Reflashing system partition shouldn't be necessary, it's just the nuclear option of last resort that noone wants to do.
Click to expand...
Click to collapse
Could you say which problems you had with Magisk?
If you had f2fs then of course. But usually Magisk works as it should and has the module system which is very useful too.
I was waiting for a root enabler for oreo (41.3.A.2.24), and I could find https://forum.xda-developers.com/xperia-x-performance/how-to/guide-stock-kernel-root-twrp-drm-fix-41-t3711837.
But this link is for version 41.3.A.0.401 and it does not work for everybody including me.
Since androplus still didn't bring out a new version of his kernel I tried the method from the above link.
But I'm using newer versions than in the description, I use TWRP 3.2.0, Magisk manager 5.2.2 and Magisk 15.2.
I can install the new version, twrp, the new boor image and Magisk 15.2.
I can boot and Magisk runs but the Safetynet control failes and Magisk does not enable root.
On the installation of the boot image, twrp and magisk I got some messages (marked in red)
unable to mount storage
failed to mount
Before I tried with magisk manager 5.5.1 and magisk 15.1 but then I got stuck at boot time at the sony logo.
Does anybody have a way to root Oreo (the latest version), enable DRM and enable root?
Ok I started all over again and I noticed I didn't follow the procedure first time.
So I excluded the FOTA kernel but whatever else I check no full wipe is done, I can always see the previous installed apps, it does not matter if I check Cust-reset, master-reset or reset-wipe-reason, the system is not wiped.
So that's my first problem, how to wipe the previous install.
Flashing the rom seems to be OK, same thing for flashing boot_oreo.img and twrp-3.1.1-0-dora.img.
I'm not sure about twrp 3.2.0.0 because this version is off-line now, so I tried with TWRP 3.1.1.0 and 3.2.1.0 but they all gave me the same result.
Problems start when I have to flash drmfix.zip, safety-net cleaner or magisk 15.2. The procedure tells me the flash is ok but have a look at thet attached images, I get errors while flashing. One picture for drmfix, one for safety-net-cleaner and one for magisk 15.2
After flashing all of this I can boot successfully but when I try to get root in ES File Explorer pro, it does not work. When I go into Magisk and try the afety-net check I get ctsProfile false and basicIntegrity False.
So the rom does work but I do not get root.
I tried all of this with the Italian rom 41.3.A.2.24.R1E ? I can start all over again with the UK version 41.3.A.2.24.R2E but I do not know if this makes any sense.
So can anybody tell me what to do to get it all going?
deboopi2 said:
I was waiting for a root enabler for oreo (41.3.A.2.24), and...
Click to expand...
Click to collapse
1 - Do use always Adrian DC latest fully working TWRP build for dora.
2 - You don't need a 3rd party kernel to achieve that, instead, you can easily create your own one, based always on stock kernel!
Thats the SELinux's problem.
Flash this first then flash magisk
https://forum.xda-developers.com/xp...ment/mod-sony-stock-patcher-xperia-x-t3528148
I am trying to re-root my SM-T380 after updating to Pie and am following the latest process per [TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018 but am running into some issues with steps 3 & 4.:
Boot to TWRP
Format the Data partition (not wipe) using the FORMAT DATA button under Wipe options
Install the memory decryption patch
Assume this is the file found in Ashyx's siganture Samsung encryption disable patch but I can't find any mirrors when trying to download it. Is this the right file for the memory decryption patch?
Install the modified kernel
The file for the SM-T380 found in this post appears to be for the T380DXU3CSI5 but the current stock image is T380DXU3CSL2 for the latest firmware installation (Jan 2020 security patch). I assume a new kernel is needed for this latest version. Is that the case? Also, the file is in tar format but need in zip format to flash in TWRP. Is it as simple as repackaging the tar into a zip file instead?
Install Magisk
Thanks for the help!
I will write out what I just got to work with the latest update of Android Pie for the Samsung Galaxy Tab A T380 running T380DXU3CSL2, security patch January 2020. I have tried all of the methods on the main TWRP/Root thread (which is now closed) and only had success with one.
To clarify, yes - using the patched boot.img from ashyx that was made from T380DXU3CSI5 WILL work with T380DXU3CSL2 (latest as of time of writing) just fine. Make sure to flash Stock first and OEM Unlock.
Ashyx does give some files still needed in his/her first post on the main TWRP thread, but the boot image and the DM-verity are buried within a 66 page thread. Out of respect for ashyx's wishes I will not direct link to files. Get TWRP from the first post here. The patched boot image and DM verity no encrypt get from the guide here by user zfk110. Pg. 65 of the TWRP thread. The guide itself did not work for me though. Just grab the files.
So, files you will need:
>twrp_3.2.3-1_sm-t380_oo_4119.tar (TWRP)
>T380DXU3CSI5_patched_boot_111119.tar (boot.img inside the .tar)
>Latest Magisk version here
>Tab_A_2017_Pie_forced+encryption_disabler-1.zip (no-verity-no-encrypt)
Not only have I found RMM Bypass unnecessary, but in my many trials I think maybe it was causing an issue for me. Perhaps someone much smarter than I can explain, but there is no setting in build.prop to need it - I did check.
TWRP/Root:
>Flash TWRP with Odin with "Auto Reboot" setting turned off: (file: twrp_3.2.3-1_sm-t380_oo_4119.tar in AP slot)
>Boot straight to TWRP (home + vol down + power to get out of download mode then as soon as the screen flashes swap to home + vol up + power),
>In TWRP main menu press "Wipe" and the "Format Data", type "yes" to proceed.
>Reboot to TWRP by going back to main menu of TWRP, select "Reboot" then "Recovery"
>Install boot.img to your boot partition from your external SD card in TWRP (there is a YT video how to do this within TWRP if you need help, just Google it. The file you need is: T380DXU3CSI5_patched_boot_111119.tar then extract boot.img from that for TWRP (use ZArchiver or a program that will unzip .tar). It MUST be in .img to install it with the TWRP "Image" button. TWRP won't even read that the .tar is there, and I don't recommend Odin for this)
>Install Magisk from your external SD card (I used the latest, 20.4 just fine)
>Install the DM-Verity Forced Encryption Patch from your external SD card (file: Tab_A_2017_Pie_forced+encryption_disabler-1.zip)
>Wipe Cache and Dalvik
>Reboot to System
Notes:
Boot image must be first before flashing the others. I tried it after Magisk et.al as with a number of people's directions and several other configurations in addition both in TWRP and with Odin (and the other boot image as well on the thread: t380_boot_pp.img - no luck on XSA for me at least) and it caused a bootloop every time. I don't know why. The smart guys are on the TWRP thread but it's closed (and confusing). I just try things.
To the other OP question here - use the later version of the DM-verity patch - the original one (no-verity-no-encrypt_ashyx) you are referring to is a different size and structure (I have it archived) so it is probably necessary to use the Tab_A_2017_Pie_forced+encryption_disabler-1.zip. It's on pg.65 on zfk110's guide that I linked above (though again, the guide itself did not work for me).
Edit: I know someone could find this method out from the big thread but I know what it is like to feel newby and get confused and want to give up. And the number of different methods and files on that dang thread was a bit maddening honestly and frequently in direct conflict with each other.
Thank you for the guide Winston Churchill, I tried following it for my device Samsung Tab A T380 (build T380DXU3CTH4) but I am stuck at installing Magisk. The patched boot.img is installed successfully but when I go to the system and Magisk does not appear so I have to install it manually with Magisk.apk file. Then when I check the status it says "Installed N/A, Ramdisk Yes, A/B No, SAR No" and root is not active.
I really appreciate any help on this!!
Many thanks Winston Churchill, this worked for me after many failed efforts using other methods and procedures.
Just one or two cautions, as I had to go through the process twice -- because the first time I got locked out with an "unauthorized" firmware notice on the first reboot. I'm not sure if it was because I did not flash the RMM Bypass the first time, or I didn't make sure my OEM Unlock was showing after flashing TWRP, etc. At any rate, I ended up with the RMM Prenormal state.
So I started over . . .
- Odin-flashed my Pie version 3CSI5 one more time
- Setup, went through the time and software update thing to get OEM Unlock to show, and enabled USB Debugging
- Odin-flashed twrp_3.2.3-1_sm-t380_oo_4119.tar
- In TWRP, ran Format Data, rebooted recovery and Formatted again (this has been necessary or advised for other Samsung devices in the past, so I did it here too)
- Then flashed in TWRP:
--- (1) boot.img
--- (2) Magisk 20.4
--- (3) Tab_A_2017_Pie_forced+encryption_disabler-1.zip
--- (4) RMM-State_Bypass_Mesa_v2.zip.
- Wiped Dalvik and Cache
- Rebooted to system
- Made sure OEM Unlock showed and USB Debugging was enabled
- Installed Magisk Manager 7.5.1
- Opened Magisk Manager and made sure Magisk was installed (sometimes it takes a reboot to see Magisk, and sometimes I've actually had to go back into TWRP and reflash it).
All good. So I installed my usual root-needed apps, Speed Software Root explorer, Titanium Backup, Adaway and Power Toggles. All are now rooted and working (including Titanium Backup!!!) and my Android Pie appears to be very stable. Soooo . . . quickly back to TWRP to run a Backup in case something breaks!
I have never had so much trouble rooting any Android device before. The T380 is a nice size and very nice weight, but man oh man . . . I was beginning to wonder if I would ever get it rooted. I can't tell you how much I appreciate (finally) finding this thread and specifically your post.
Moondroid said:
Many thanks Winston Churchill, this worked for me after many failed efforts using other methods and procedures.
Just one or two cautions, as I had to go through the process twice -- because the first time I got locked out with an "unauthorized" firmware notice on the first reboot. I'm not sure if it was because I did not flash the RMM Bypass the first time, or I didn't make sure my OEM Unlock was showing after flashing TWRP, etc. At any rate, I ended up with the RMM Prenormal state.
So I started over . . .
- Odin-flashed my Pie version 3CSI5 one more time
- Setup, went through the time and software update thing to get OEM Unlock to show, and enabled USB Debugging
- Odin-flashed twrp_3.2.3-1_sm-t380_oo_4119.tar
- In TWRP, ran Format Data, rebooted recovery and Formatted again (this has been necessary or advised for other Samsung devices in the past, so I did it here too)
- Then flashed in TWRP:
--- (1) boot.img
--- (2) Magisk 20.4
--- (3) Tab_A_2017_Pie_forced+encryption_disabler-1.zip
--- (4) RMM-State_Bypass_Mesa_v2.zip.
- Wiped Dalvik and Cache
- Rebooted to system
- Made sure OEM Unlock showed and USB Debugging was enabled
- Installed Magisk Manager 7.5.1
- Opened Magisk Manager and made sure Magisk was installed (sometimes it takes a reboot to see Magisk, and sometimes I've actually had to go back into TWRP and reflash it).
All good. So I installed my usual root-needed apps, Speed Software Root explorer, Titanium Backup, Adaway and Power Toggles. All are now rooted and working (including Titanium Backup!!!) and my Android Pie appears to be very stable. Soooo . . . quickly back to TWRP to run a Backup in case something breaks!
I have never had so much trouble rooting any Android device before. The T380 is a nice size and very nice weight, but man oh man . . . I was beginning to wonder if I would ever get it rooted. I can't tell you how much I appreciate (finally) finding this thread and specifically your post.
Click to expand...
Click to collapse
So many conflicting instructions - Why exactly are people flashing this modified boot image and then magisk? Correct me if Im wrong, but isnt that what installing magisk DOES (patches the boot image) when you rename the magisk apk to a zip and install in TWRP? I only FINALLY got this working after I ignored the patched boot.img step completely and simply - flash twrp in odin, reboot rocovery, format data, reboot recovery, flash magisk, disable verity whatever, reboot system..
Dick_Stickitinski said:
So many conflicting instructions . . .
. . . isnt that what installing magisk DOES (patches the boot image) when you rename the magisk apk to a zip and install in TWRP? . . .
Click to expand...
Click to collapse
Magisk patches boot.img for Root access. Sometimes there are also other reasons for flashing a boot.img. I'm not an Android coder so I can't explain every reason why flashing boot.img might be necessary in this case.
. . . "rename the magisk apk to a zip" . . . you renamed a Magisk Manager apk to "zip" for flashing in TWRP? How did that work?
At any rate, my method worked for me and yours (however you actually did it) worked for you. I can say for sure that Android itself can be quirky, for example, my recent experiences with a Galaxy S9 on Pie where, after reflashing the exact same build 5-6 times -- because trying to set a security PIN for some screwy reason kept crashing the system (?!!) -- from one reflash to the next I got different app-disabling experiences. For example, a few built-in apps (like google movies etc) showed the option to Uninstall instead of the expected Disable. The same generic reason why an S8 G950U on Pie v8 can be rooted successfully using @jrkruse's Extreme Syndicate method, and other S8 G950s on Pie v8 will brick. Quirky? Weird, I don't know, can't explain, I just go with the flow as it flows and count my blessings when it works.
Moondroid said:
. . . "rename the magisk apk to a zip" . . . you renamed a Magisk Manager apk to "zip" for flashing in TWRP? How did that work?
Click to expand...
Click to collapse
Yeah, you can rename the APK to zip & flash it in TWRP
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
However, I spoke too soon... I got it to stop bootlooping and actually got it to boot into system, and magisk manager is installed, but still not rooted. When flashing magisk in recovery again (or even extracting the boot.img & patching it in magisk manager, it recognizes it as a magisk-patched boot.img, but it's still not rooted. This tablet is frustrating the hell out of me, I'm about to say the hell with it & toss it.
Dick_Stickitinski said:
Yeah, you can rename the APK to zip & flash it in TWRP
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
Click to expand...
Click to collapse
As of January last year, okay. On older phones/tabs I almost always go with older Magisk versions that were more current with the older device's firmware.
Dick_Stickitinski said:
However, I spoke too soon... I got it to stop bootlooping and actually got it to boot into system, and magisk manager is installed, but still not rooted. When flashing magisk in recovery again (or even extracting the boot.img & patching it in magisk manager, it recognizes it as a magisk-patched boot.img, but it's still not rooted. This tablet is frustrating the hell out of me, I'm about to say the hell with it & toss it.
Click to expand...
Click to collapse
Just a suggestion, maybe try using an older Magisk. I flashed Magisk v20.4 in TWRP and Magisk Manager v7.5.1 after booting to system. Older Magisk (zip and Manager) can be found on topjohnwu's GitHub.
Note, doing it this way, I always have to reboot one more time to see Magisk fully installed and working.
Now that 11.0.2.2 is available OTA, can anybody give me a quick guide on how to upgrade from my existing 11.0.1.1 without losing root?
Hi. you have to download the full rom package. disable all modules in magisk. update in local update system. especially do not restart. and in magisk manager click on install and install on inactive slot after OTA update. magisk will recreate a boot image on the inactive slot. which will become active on restart. once the restart is complete the root is kept. all that remains is to reactivate the magisk modules.
Envoyé de mon IN2023 en utilisant Tapatalk
Merci beaucoup - cela a parfaitement fonctionné!
Philip said:
Merci beaucoup - cela a parfaitement fonctionné!
Click to expand...
Click to collapse
I have a guide in the guides section for this very reason with img's
Hello.... Normally you have to install the twrp a/b script after install the local update and then the magisk in inactive slot.....
That was ok in a lot of older updates and works.
This time if can't install the twrp a/b script. Everytime I get a fault message that twrp is not present....?!
Very strange.....
jensemann1974 said:
Hello.... Normally you have to install the twrp a/b script after install the local update and then the magisk in inactive slot.....
That was ok in a lot of older updates and works.
This time if can't install the twrp a/b script. Everytime I get a fault message that twrp is not present....?!
Very strange.....
Click to expand...
Click to collapse
That script is for older devices that has recovery inside boot.
OnePlus devices launches with Android 10 has a separate recovery slot. This means in order to install TWRP again your need to flash it with fastboot again.
Twrp not working on Oos11
Envoyé de mon IN2023 en utilisant Tapatalk
So it isn't necessary to install, only magisk in inactive slot....?!
Have said this before, shouldn't be any confusion, like I said I have a guide for it.
Extract from the guide for retaining root.
Update from 11 stable to 11+ stable whilst retaining root
For these guides the version used, was canary, simply change the channel to canary then select install / update:
Magisk Manager - Magisk (Canary) version: 1469b82a (21101)
Magisk - Magisk (Canary) version: 1469b82a (21101)
1. Download the relevant firmware for your device via oxygen updater
2. Open Magisk and remove all the modules you have installed, then reboot
**NOTE- At this point I copied out the whole firmware to my computer and extracted payload then extracted the contents of payload using payload dumper, the full firmware for 11.0.1.1 EU IN2023BA ,the boot img and patched boot img are at the foot of this guide.
3. Open up settings / system / system updates, click the cog and select "Local Upgrade" the file should be listed on screen, if not then move the file to the root of your phones storage /sdcard
4. Click install and allow it to go through the process
**NOTE- DO NOT REBOOT AT THIS POINT YOU WILL LOSE THE ABILITY TO PATCH ON THE FLY, SIMPLY BACK OUT OF THE SCREEN WHICH SAYS INSTALLATION COMPLETED. RESTART TO EXPERIENCE NEW FEATURES
5. Open up magisk and click install (you may see two install buttons, top one is magisk and the bottom is magisk manager, we need the top one)
6. You'll be faced with a screen that has several options, you want to select Install to Inactive slot (After OTA) then select "LET'S GO" once complete click reboot
7. Once your phones booted up your system / files should all remain as they were and you should have root access.
Thread:. https://forum.xda-developers.com/oneplus-8-pro/how-to/root-uk-eu-patched-magisk-boot-img-t4175033
You have an easier method if the OTA update is there in the system. Follow below guide. Specifically, step 2,3 and 5. That's all you need. You don't need the whole update. Tested this twice. 11 to 11.0.1.1 and so on.
https://www.the***********.com/install-ota-update-rooted-android-device-guide/
dladz said:
Have said this before, shouldn't be any confusion, like I said I have a guide for it.
**NOTE- DO NOT REBOOT AT THIS POINT YOU WILL LOSE THE ABILITY TO PATCH ON THE FLY, SIMPLY BACK OUT OF THE SCREEN WHICH SAYS INSTALLATION COMPLETED. RESTART TO EXPERIENCE NEW FEATURES
5. Open up magisk and click install (you may see two install buttons, top one is magisk and the bottom is magisk manager, we need the top one)
6. You'll be faced with a screen that has several options, you want to select Install to Inactive slot (After OTA) then select "LET'S GO" once complete click reboot
7. Once your phones booted up your system / files should all remain as they were and you should have root access.
Thread:. https://forum.xda-developers.com/oneplus-8-pro/how-to/root-uk-eu-patched-magisk-boot-img-t4175033
Click to expand...
Click to collapse
Steps 5 and 6 did not preserve root comping from OOS10. Magisk Manager is still there though. Looks like I'll be looking for a way to apply root again.
Edit: used the boot image from this link to get root back. I wasn't able to patch the file myself using Magisk Manager and fastboot boot it and have root enabled. https://forum.xda-developers.com/showpost.php?p=83775505&postcount=471
I was able to use the oneplus-8-pro_15.O.30_boot_patched IMG from the link to adb boot oneplus-8-pro_15.O.30_boot_patched.img from fastboot screen and then direct install Magisk from the manager. I retained root after a reboot.
ProfEngr said:
Steps 5 and 6 did not preserve root comping from OOS10. Magisk Manager is still there though. Looks like I'll be looking for a way to apply root again.
Edit: used the boot image from this link to get root back. I wasn't able to patch the file myself using Magisk Manager and fastboot boot it and have root enabled. https://forum.xda-developers.com/showpost.php?p=83775505&postcount=471
I was able to use the oneplus-8-pro_15.O.30_boot_patched IMG from the link to adb boot oneplus-8-pro_15.O.30_boot_patched.img from fastboot screen and then direct install Magisk from the manager. I retained root after a reboot.
Click to expand...
Click to collapse
That must be you're magisk manager and or you left magisk modules enabled..
Otherwise your phone wouldn't be booted at all..
To confirm, the steps have been used 100's of times without problems, the few that have issues have specific problems, namely what I mentioned above but more often than not they have an issue they aren't aware of and don't declare to be so I can't help them.
I would hazard a guess that that is the problem
dladz said:
That must be you're magisk manager and or you left magisk modules enabled..
I would hazard a guess that that is the problem
Click to expand...
Click to collapse
It was a couple of modules I forgot about. Got it sorted now. Thanks.
Not sure if the question was answered really. I have the ota update alert but can't install the ota without flashing the original boot.img (not a problem just have to get in front of a computer)..I tried this method but the full image on oxygen updater and OnePlus support site is 11.0.1.1 and not the new 11.0.2.2.
What's the easiest way of doing an ota without having to flash back stock boot.img, taking the ota, and reinstalling magisk/patching image if there's one?
Wait for the 11.0.2.2 Full update to keep root; that's what a few of us are waiting on as well
galaxys said:
Wait for the 11.0.2.2 Full update to keep root; that's what a few of us are waiting on as well
Click to expand...
Click to collapse
Thanks. Anybody had problems flashing back stock boot partition and taking the ota/rooting again manually via patched magisk image?
I've read some threads about problems and success's. I would check them out if your interested. I just take the ota, have magisk install to the inactive slot, and then reboot.
galaxys said:
I've read some threads about problems and success's. I would check them out if your interested. I just take the ota, have magisk install to the inactive slot, and then reboot.
Click to expand...
Click to collapse
You were able to take the ota without reflashing stock boot.img? It's currently failing for me and I'm fairly sure it's because I have a patched boot partition (this happened already when I upgraded via ota from oxygen 10 that's why I'm fairly sure). Let me know.
Sounds like because of your patched boot.
No, I have not seen the full ota 11.0.2.2 to download, I was giving an example....