To root even tmp root you need Kingroot, from:
http://forum.xda-developers.com/devdb/project/dl/?id=12450
Download SuperSU.zip:
http://download.chainfire.eu/supersu
Install and run kingroot, may take several attempts to tmp root device, once tmp root has been achieved download and flash TWRP.apk from thread below
http://androidforums.com/index.php?threads/918537/
Install twrp recovery and flash twrp recovery,BUT DON'T REBOOT.....FIRST UNINSTALL KINGROOT:
Uninstall all kingroot, kinguser, Chinese char apks
Reboot to twrp with twrp.apk
Make full backup
Flash SuperSU.Zip
1. Get full read/write to system per @jcase tutorial
Can be found here:
https://plus.google.com/+JustinCaseAndroid/posts/KzgyHLgVhwo
If you get a black screen with your led light blinking red, and green hold power button until it powers off, if it keeps rebooting hold volume up while you do this. To get out of booting into black screen with green and red flashing led you have to boot into twrp, and wipe cache, once you wipe cache you can reboot system and should have everything setup, rooted with updated su binaries
Once rooted if you would like to have full read write while keeping your twrp recovery there has been a solution made by Masterchief87 he created two zips one that flashes twrp to boot partition and your boot to recovery, with boot on your recovery partition booting into recovery boots up normal, but with read and write to system, while keeping twrp on boot if you boot normo you boot straight into your twrp recovery
http://androidforums.com/index.php?threads/919330/
Is were you can check md5 and see Masterchief87 original post
Flash for read write to system to boot into android you must choose reboot recovery, or hold volume up + power or you will boot into twrp again.
The second zip allows you to boot into android with only read as it has twrp on your recovery partition and only boot on your boot partition.
Flash for twrp on recovery, this will allow you to flash ROMs, zips, but will only mount system ad read only if you boot into android
To boot into twrp with this one flashed you must use reboot recovery or power + volume up
As always be careful when flashing any zip from recovery, and ones that write new boot.img I myself and or anyone else are not responsible if you brick your device
OK if you permrooted with kingroot, and are having issues getting SuperSU to read binary here is what you have to do
(this means you didn't uninstall kingroot, kinguser,Chinese char apks before a reboot)
Method 1 backup restore
1. Get su binary on sdcard
2. Make a backup of your system and boot
3. Run Restore from twrp(this restores your backup you just made)
4. Don't reboot yet
5. Mount system in twrp
6. Copy su binary from sdcard to /system/xbin/su
7. chmod 755 with twrp file browser
8. Copy install-recovery.sh to /system/etc/install-recovery.sh
9. Chmod 755 install-recovery. sh
10. Copy daemonsu /system/xbin/daemonsu
11. Chmod daemonsu 755
12. Cleanup delete old ku.sud from /system/xbin
Delete /system/use/iku
Delete kingroot.txt in system folder
Reboot
Enjoy SuperSU
Special thanks to jcase for getting the ball rolling
Special thanks to @hroark13 for his twrp.apk and twrp.recovery
Head over to hroark13 thread for more info
http://androidforums.com/index.php?threads/918537/
Special thanks to @Masterchief87 for his boot on recovery and twrp on boot zip
Thanks @tech_yeet for showing us kingroot
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
OBSOLETE
Method 2 terminal/adb copy
2. Get su binary on sdcard
3. use either adb or terminal emulator and grant su
4. Keep the adb or terminal emulator as su and uninstall kingroot, make sure you unchecked all three of the root options in kingroot, keep updated, backup, and the other one I already forgot lol.
5. In adb or terminal emulator use
cat /sdcard/su > /system/xbin/su
chmod 755 /system/xbin/su
cat /sdcard/su > /system/xbin/daemonsu
chmod 755 /system/xbin/daemonsu
cat /sdcard/su > /system/xbin/ku.sud
chmod 755 /system/xbin/ku.sud
cat /sdcard/su > /system/usr/iku/isu
chmod 755 /system/usr/iku/isu
Method 3 twrp copy
If you would like to keep twrp the whole time, and copy files over using twrp this is also possible.
1. boot into twrp recovery
2. mount system: check under mount system to mount
3. copy over files make a backup of su by placing in another folder or using adb and cp
cp sdcard/su /sdcard/ku.sud
copy su to /system/xbin/su
copy ku.sud to /system/xbin/ku.sud
copy su to /system/usr/iku/isu
copy deamonsu(which is also another su so you can make another copy of su as deamonsu)
copy deamonsu to /system/xbin/deamonsu
This should allow SuperSU to see su binary, the problem we are having is that install-recovery.sh instead of running daemonsu as a service with /system/xbin/daemonsu --auto-daemon &
is its just linking to another su in system/xbin and system/usr/iku,
so were just going to replace those extra su with SuperSU binary instead, when we permrooted with kingroot it added a /dev/null for its recovery-install.sh to survive ota update and Its beyond my knowledge to change that, but I can tell you how to change kingroot su to SuperSU, and thus we have SuperSU instead of kingroot.
After binary is pushed in all spots install SuperSU and enjoy!
After this please reinstall twrp recovery so you don't brick your device.
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
Okay before I try this I wanted to know, do I have to uninstall twrp and install stock recovery? Is there anyway to do this within the os? Also I have already uninstalled kingroot and have kept my root.
You can from twrp just mount system, then use advanced file manager, and copy all files over to their correct places, copy su, and make a nother su named isu, and ku.sud and replace all those files like I showed using twrp it will work.
The following i copied form masterchief in the other zmax post it is IMO a good safe way of having the ability to run the phone in "recovery boot mode" and still having a twarp in the boot partion that will allow a user to reinstall a backup to the "recovery boot" at least that is how I understand it . As I haven't done any of this yet I'm just going on what I have siffed out of the sea of posts.
"Masterchief"
Here is what I've been doing.
I used kingroot to get temp root.
I then used terminal emulator to make backup copies of the stock recovery and boot.img.
I then downloaded and installed twrp, and then rebooted to recovery and flashed the UPDATE-SuperSU-v2.46.zip for permanent root.
After doing this I made two flashable zips.
The first one
(ZMAX_TWRP_&_BOOT_SWITCHER.zip) flashes the boot.img to the recovery partition in order to allow the system to be mounted rw while booted in android, and flashes twrp to the boot partition just in case the s### hits the fan.
The second zip
(ZMAX_TWRP_&_BOOT_RESTORE.zip) flashes twrp back to the recovery partition and puts the boot.img back on the boot partition for whenever I need to restore a backup to fix a soft brick or if I need to flash a zip.
These two flashable zips allow me to have full root capabilities without ever having to uninstall twrp.
Twrp cannot write to the system partition when it is on the boot partition, BUT IT CAN flash
ZMAX_TWRP_&_BOOT_RESTORE.zip. Once you flash twrp back on the recovery partition and reboot recovery, you can restore a backup or flash zips. Once that is done you can flash
ZMAX_TWRP_&_BOOT_SWITCHER.zip again and have full root capabilities. Because of this I can modify the system however I see fit without fear of bricking my phone. It is not the most sophisticated way of doing things BUT IT WORKS.
How can I flash xposed installer with twrp to make it work?
Sent from my (ROOTED) Z970 ZTE Zmax
rkey1000 said:
How can I flash xposed installer with twrp to make it work?
Sent from my (ROOTED) Z970 ZTE Zmax
Click to expand...
Click to collapse
Make a backup first!!
Then open xposed inside framework chose install settings and choose install settings again, and check install from twrp, either auto flash or sdcard flash, then it should reboot to install xposed framework
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
simple root guide
http://forum.xda-developers.com/showthread.php?t=3110178
Shlickwilly said:
The following i copied form masterchief in the other zmax post it is IMO a good safe way of having the ability to run the phone in "recovery boot mode" and still having a twarp in the boot partion that will allow a user to reinstall a backup to the "recovery boot" at least that is how I understand it . As I haven't done any of this yet I'm just going on what I have siffed out of the sea of posts.
"Masterchief"
Here is what I've been doing.
I used kingroot to get temp root.
I then used terminal emulator to make backup copies of the stock recovery and boot.img.
I then downloaded and installed twrp, and then rebooted to recovery and flashed the UPDATE-SuperSU-v2.46.zip for permanent root.
After doing this I made two flashable zips.
The first one
(ZMAX_TWRP_&_BOOT_SWITCHER.zip) flashes the boot.img to the recovery partition in order to allow the system to be mounted rw while booted in android, and flashes twrp to the boot partition just in case the s### hits the fan.
The second zip
(ZMAX_TWRP_&_BOOT_RESTORE.zip) flashes twrp back to the recovery partition and puts the boot.img back on the boot partition for whenever I need to restore a backup to fix a soft brick or if I need to flash a zip.
These two flashable zips allow me to have full root capabilities without ever having to uninstall twrp.
Twrp cannot write to the system partition when it is on the boot partition, BUT IT CAN flash
ZMAX_TWRP_&_BOOT_RESTORE.zip. Once you flash twrp back on the recovery partition and reboot recovery, you can restore a backup or flash zips. Once that is done you can flash
ZMAX_TWRP_&_BOOT_SWITCHER.zip again and have full root capabilities. Because of this I can modify the system however I see fit without fear of bricking my phone. It is not the most sophisticated way of doing things BUT IT WORKS.
Click to expand...
Click to collapse
Where can I get my hands on those zips?
I updated post it has the twrp zips that Masterchief87 made to allow booting into read/write
Thanks hroak13 for the twrp recovery
Worked, uninstalled kingroot and kinguser. Can't find Chinese character apps.
Looked in app manager and app drawer.
Safe to reboot to twrp?
"a clock is ticking, but it's hidden far away, safe and sound, safe and sound....."
Did you choose uninstall su or unroot, in kinguser APK, there is 3 options, like backup ota survival, and one more the top three choices under kinguser settings need to be done I believe, but I might be wrong, Chinese characters APK will be the last APK in your app drawer doesn't need to be uninstalled, but its just a task manager that will watch your activities I would just delete it, if you can't find it !maybe you didn't install it it normally installs itself right after root, maybe the English very doesn't install it
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
simple root guide
http://forum.xda-developers.com/showthread.php?t=3110178
Deleted
Changed to thread Hadn't read that till now
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
simple root guide
http://forum.xda-developers.com/showthread.php?t=3110178
DroidisLINUX said:
Changed to thread Hadn't read that till now
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
simple root guide
http://forum.xda-developers.com/showthread.php?t=3110178
Click to expand...
Click to collapse
Thank you sir
Kingroot sure fire root
DroidisLINUX said:
To root even tmp root you need Kingroot, from:
http://forum.xda-developers.com/devdb/project/dl/?id=12450
Download SuperSU.zip:
http://download.chainfire.eu/supersu
Install and run kingroot, may take several attempts to tmp root device, once tmp root has been achieved download and flash TWRP.apk from thread below
http://androidforums.com/index.php?threads/918537/
Install twrp recovery and flash twrp recovery,BUT DON'T REBOOT.....FIRST UNINSTALL KINGROOT:
Uninstall all kingroot, kinguser, Chinese char apks
Reboot to twrp with twrp.apk
Make full backup
Flash SuperSU.Zip
1. Get full read/write to system per @jcase tutorial
Can be found here:
https://plus.google.com/+JustinCaseAndroid/posts/KzgyHLgVhwo
If you get a black screen with your led light blinking red, and green hold power button until it powers off, if it keeps rebooting hold volume up while you do this. To get out of booting into black screen with green and red flashing led you have to boot into twrp, and wipe cache, once you wipe cache you can reboot system and should have everything setup, rooted with updated su binaries
Once rooted if you would like to have full read write while keeping your twrp recovery there has been a solution made by Masterchief87 he created two zips one that flashes twrp to boot partition and your boot to recovery, with boot on your recovery partition booting into recovery boots up normal, but with read and write to system, while keeping twrp on boot if you boot normo you boot straight into your twrp recovery
http://androidforums.com/index.php?threads/919330/
Is were you can check md5 and see Masterchief87 original post
Flash for read write to system to boot into android you must choose reboot recovery, or hold volume up + power or you will boot into twrp again.
The second zip allows you to boot into android with only read as it has twrp on your recovery partition and only boot on your boot partition.
Flash for twrp on recovery, this will allow you to flash ROMs, zips, but will only mount system ad read only if you boot into android
To boot into twrp with this one flashed you must use reboot recovery or power + volume up
I HAVE T-mobile AND MASTERCHIEF87 Flashable boot switcher could have bricked my device, I was lucky and know what I am doing, I urge caution when using these files some devices, and or carrier phones it might not work with. If you brick your phone I am not responsible
OK if you permrooted with kingroot, and are having issues getting SuperSU to read binary here is what you have to do
(this means you didn't uninstall kingroot, kinguser,Chinese char apks before a reboot)
Method 1 backup restore
1. Get su binary on sdcard
2. Make a backup of your system and boot
3. Run Restore from twrp(this restores your backup you just made)
4. Don't reboot yet
5. Mount system in twrp
6. Copy su binary from sdcard to /system/xbin/su
7. chmod 755 with twrp file browser
8. Copy install-recovery.sh to /system/etc/install-recovery.sh
9. Chmod 755 install-recovery. sh
10. Copy daemonsu /system/xbin/daemonsu
11. Chmod daemonsu 755
12. Cleanup delete old ku.sud from /system/xbin
Delete /system/use/iku
Delete kingroot.txt in system folder
Reboot
Enjoy SuperSU
Special thanks to jcase for getting the ball rolling
Special thanks to @hroark13 for his twrp.apk and twrp.recovery
Head over to hroark13 thread for more info
http://androidforums.com/index.php?threads/918537/
Special thanks to @Masterchief87 for his boot on recovery and twrp on boot zip
Thanks @tech_yeet for showing us kingroot
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
Click to expand...
Click to collapse
Use MASTERCHIEF87 boot swither zip to get system r/w and kingroot will work first time every time. Then boot into recovery flash the boot restore and flash a system backup only need system. ...Then move the su files into the proper places in system.. It would seem that the problem with kingroot is getting system to be r/w, I tried this five different times today and all five times were on a clean system backup..every one of them worked without kingroot failing or rebooting.
I'm a little confused on what to do here., Im not exactly a noob, but Im still a little confused and would appreciate some help.
I got temp rooted using Kingroot
While temp rooted I installed ZMAX TWRP the lasted VERSION 2.8.6.0 from
( FROM ANDROID FORUM CANT POST LINKS, BUT I THINK IT WAS UPDATED YESTERDAY )
From there I deleted all the Chinese apps
booted into recovery with the TWRP app
Made a backup like I always do,
Installed S.U with no problems.
So I'm wondering if my device is ready to install custom roms yet, I still have TWRP 2.8.60 because I am able to boot into it from just holding the Up Volume button and Power button. Im able to boot into it anytime I want and I still have root. because in a normal android case it looks like it would be ready to go, but then I see these two links below and I get confused ( JUSTIN CASE TUTORIAL FROM GOOGPLE PLUS , AGAIN CANT POST LINKS ) and ( THE LINK RIGHT AFTER THE JUSTIN CASE LINK IN THIS THREAD THAT GOES TO ANDROID FORUM )
CarlJung said:
I'm a little confused on what to do here., Im not exactly a noob, but Im still a little confused and would appreciate some help.
I got temp rooted using Kingroot
While temp rooted I installed ZMAX TWRP the lasted VERSION 2.8.6.0 from
( FROM ANDROID FORUM CANT POST LINKS, BUT I THINK IT WAS UPDATED YESTERDAY )
From there I deleted all the Chinese apps
booted into recovery with the TWRP app
Made a backup like I always do,
Installed S.U with no problems.
So I'm wondering if my device is ready to install custom roms yet, I still have TWRP 2.8.60 because I am able to boot into it from just holding the Up Volume button and Power button. Im able to boot into it anytime I want and I still have root. because in a normal android case it looks like it would be ready to go, but then I see these two links below and I get confused ( JUSTIN CASE TUTORIAL FROM GOOGPLE PLUS , AGAIN CANT POST LINKS ) and ( THE LINK RIGHT AFTER THE JUSTIN CASE LINK IN THIS THREAD THAT GOES TO ANDROID FORUM )
Click to expand...
Click to collapse
Yes your ready for custom roms
Sent from my Z970 using XDA Free mobile app
DroidisLINUX said:
Changed to thread Hadn't read that till now
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
simple root guide
http://forum.xda-developers.com/showthread.php?t=3110178
Click to expand...
Click to collapse
I'm a little confused man how did my zips almost brick your phone? If you follow all the instructions there shouldn't be any risk at all. I been using them since before I posted em.
Not sure how to proceed
Got temp root with Kingroot
Installed TWRP APK
Successfully installed recovery
Removed all Kingroot related APK's
Now when I hit "Reboot Recovery" in the TWRP APK it does nothing....
What should I do now??
Haggis Warrior said:
Got temp root with Kingroot
Installed TWRP APK
Successfully installed recovery
Removed all Kingroot related APK's
Now when I hit "Reboot Recovery" in the TWRP APK it does nothing....
What should I do now??
Click to expand...
Click to collapse
Download the SuperSU zip from HERE then power off your zmax and boot into twrp recovery by holding power+volume up for approximately 4 seconds and then flash the SuperSU zip and reboot system.
So I'm following the guide on rooting, unlocking, etc and confused about systemless root and traditional. I was going to do systemless to keep android pay alive and it seems that is the future. However, I'm at the point of installing TWRP. But the guide mentioned "TWRP isn't able t persist without modifying system, so you'll lose it after booting into Android, you'll need to flash/boot it to access it again". What does this exactly mean? I read it as that after I reboot my phone after doing something in TWRP, than TWRP becomes non existent. And I'd have to flash it every time I wanted to get into TWRP. Is this correct? Seems not very smart because if something happens on my phone, I'd like to be able to boot right into my TWRP recovery to restore a stable version.
I don't know why it says that but I allow TWRP to make system modifications and I have systemless root with AP working.
You definitely don't want to let TWRP install it's version of SuperSU though. When it gives you the option select "Do not install".
I would like to share my experience on flashing systemless root with TWRP on my Nexus 9:
1. Reboot to bootloader and perform fastboot boot TWRP.img (TWRP.img is the filename of TWRP IMG file). Yes, TWRP is temporary and won't keep after reboot)
2. If TWRP prompts you to decrypt /data partition, simply skip that
3. Don't allow /system modifications
4. Use adb sideload to install systemless SuperSU
5. Directly reboot to system after installation. The device may reboot multiple times, just let it finish.
SuperSU should now appear in the app tray. This method works well for me.
Much info on systemless root here
http://forum.xda-developers.com/nexus-6p/themes-apps/systemless-root-themed-apps-t3292105
Hello all,
This may seem like a stupid question, but I want to make sure that I know what i'm doing before I mess something up and become
So I'm running a Samsung Galaxy S5 (G900V ovbiously), and it has the tobisha emmc chip
Is the only way to gain root on Marshmallow/Nougat or whatever is by reverting to Lollipop, gaining root access, installing TWRP, and then flashing LineageOS/some ROM?
Directions For Users With CID 11 Toshiba eMMC
1. Download EMMC_11_ Root S5_QB2_PB1.zip
2. Unzip
Copy the following to your External SD card:
Root S5 Folder,
EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip, EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip,
and the TouchWiz ROM you want to install.
3. Reboot Phone to Download Mode (Pwr +Vol Dwn+Home)
4. Use Odin 3.12 and load the COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_257265 6_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot
5. Flash and let the phone reboot. It will reboot to recovery and finish install then it will reboot and take about 20 seconds to boot.
6. If you do not have an External SD Card, copy the following NOW to your Internal Storage:
Root S5 Folder,
EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip, EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip,
and whatever TouchWiz ROM you want to install.
7. Use the File Manager in the app drawer of the phone and install Apex_Lancher.apk press home button and set Apex as the default launcher.
Install Superuser.apk, Busybox.apk and SafeStrapKK.apk do not open anything yet.
8. Now Install tr_v2.apk.
Open TowelRoot and CLICK MAKE IT RAIN . It should tell you you have succeeded.
9. Now Open Superuser app and click "New User" to install it.
Once done, open SuperSU and update the SU binaries using the "NORMAL" method. It will tell you you need to reboot. You can skip doing this. (If the Superuser install hangs for more than 5 minutes reboot phone and try to install it again.)
10. Now open the BusyBox app, grant SuperSU access and install BusyBox.
11. Now open SafeStrap, grant SuperSu access and click "install recovery". If the SafeStrap recovery fails to install, make sure BusyBox is installed by rerunning the BusyBox app (it will tell you if BusyBox is installed) if not click "install" again, reboot phone and open SafeStrap and try to install recovery again
12. Once SafeStrap Recovery is installed click "reboot to SafeStrap Recovery".
13. Once in SafeStrap Recovery, choose what firmware you want to be on:
Lollipop 5.0 Firmware=EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip
Marsmhallow 6.0 Firmware=EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip
14. Install the firmware zip, and then flash a TouchWiz Lollipop ROM. (Here is the latest stock rooted Lollipop Rom: VZW_BPB1_ODEX_DEODEX_V9.zip). You may want to download a copy of the latest SuperSu zip, and flash if installing a Lollipop ROM that is not rooted. Remember, you cannot root Marshmallow ROMs, so do not try and flash the SuperSu zip on a Marshmallow Rom (you will softbrick if you do).
15. After you install any Lollipop ROM, you may need to reinstall SafeStrap Recovery. Most of the time you don't have to and SafeStrap can be reached by flashing the KitKat Kernel in Download Mode with ODIN. But, in some cases, when flashing a ROM that flashes a system.img instead of a system folder, you may lose SafeStrap during install. This will be the case if you install the above ROM. You can reinstall it after the ROM is booted up. A Safestrap-G900V-4.04_LL_MM.apk is included that will flash a version of SafeStrap that will allow you to reboot to SafeStrap Recovery without flashing a KitKat kernel in Odin. Install BusyBox again from the BusyBox App in the RootS5 Folder. Install Safestrap-G900V-4.04_LL_MM.apk and make sure to grant SuperSU access. It may take a few seconds to prompt. If SafeStrap is not installed, click "Install Recovery". If Safestrap is still installed click on "Uninstall Recovery", close the app, and reopen it. It should say recovery is not installed. Now click on "Install Recovery". If this doesn't work, reboot the phone and try again. Once installed, you can just click reboot to SafeStrap from the SafeStrap app and you will reboot straight to SafeStrap. Remember to flash the appropriate Kernel when leaving SafeStrap!
Download and place these on your device:
LL_KERNEL_SS-FF_Flashable.zip, and
MM_KERNEL_SS-FF_Flashable.zip
If something bad goes wrong you can usually get back to SafeStrap by simply rebooting the phone to Download Mode and flashing NI2_stock_kernel.tar.md5. When the phone reboots, watch for the SafeStrap splash screen and enter SafeStrap.
16. Do NOT change ANY boot options in SafeStrap. ROM slots cannot be used, so you must flash to the Stock ROM slot EVERY TIME OR YOU WILL SOFTBRICK. Some functions don't work in SafeStrap, like choosing an image file to flash directly. All image files must be flashed via zip file.
---------- Post added at 12:50 AM ---------- Previous post was at 12:49 AM ----------
Get the needed files at https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Is there a way to update system to .14 and preserve TWRP?
I know that I can preserve Magisk, but I don't want to lose TWRP because I need to flash few more things.
Two more constraints:
I don't want to lose data
I don't have access to pc
In what steps I can achieve it, if any?
Yes, just go to TWRP with your OTA file, install the OTA file (in TWRP!), don't restart and install the ZIP file of the TWRP, reboot to recovery, flash magisk and reboot. Done. You'll still with your TWRP, rooted and updated.
MatheusPimentel said:
Yes, just go to TWRP with your OTA file, install the OTA file (in TWRP!), don't restart and install the ZIP file of the TWRP, reboot to recovery, flash magisk and reboot. Done. You'll still with your TWRP, rooted and updated.
Click to expand...
Click to collapse
Exactly. But make sure to only use the full OTA and not the incremental one.
Full guide
1. Go to TWRP
2. Flash FULL ROM
3. Flash TWRP INSTALLER (if u fail to u will lose TWRP)
4. Reboot your device. (yes boot it...and access your phone)
5. Reboot back to TWRP
6. Flash Magisk
Working method...tried nd tested 50+ times
The following also works. Follow it precisely.
> Install the update through the OS Update UI.
> Open Magisk Manager and find the module that preserves TWRP. Flash it. It won't appear in the module list. Don't restart yet, you'll lose Magisk if you do.
> Open Magist Manager and click "install". Install to inactive slot (OTA)
> Reboot!
Done this a few times now, it's actually more convenient than booting to TWRP.
I use always that way. The module is called TWRP_A_B_Retention_Script-Magisk.zip.
Open Magisk Manager > Downloads and it's called : TWRP A/B Retention Script.
To find it easy order by name. Default it's by last update.
https://forum.xda-developers.com/showpost.php?p=79358976&postcount=2012
Done.
Thank you all.