After a while of being on my phone loses root and i have to restart to get it back. its annoying and stupid and i lose everything in memory. How can i just magisk once and be done?
odd, haven't seen a temp root method for the OnePlus 7 pro
OcazPrime said:
After a while of being on my phone loses root and i have to restart to get it back. its annoying and stupid and i lose everything in memory. How can i just Magisk once and be done?
Click to expand...
Click to collapse
I assume that after your rooted and happy with it you'll still want to update Android. If that's the case then you need to go through the various methods to apply an OTA (OOS update) and retain root.
I don't think your taking into account that the full OOS OTA contains components such as stock recovery that clobbers the system modifications that allow you to be rooted.
It is what it is and there simply isn't a way around it unless you stay with stock OSS (no root) or go to a ROM replacement of OOS which has a built in way to update that ROM and retain root.
Happens to me too sometimes, I just lose root and magisk says that additional setup is needed and installing magisk from the manager app fails and I have to reboot to recovery to install magisk again for it to work. I do not lose any modules.
it happens to me also. Sometimes magisk gets uninstalled, or root is not being detected. Sometimes I have to restart and some magisk or Xposed modules get deleted. So root is kinda buggy on this phone
jamesfitzes said:
it happens to me also. Sometimes magisk gets uninstalled, or root is not being detected. Sometimes I have to restart and some magisk or Xposed modules get deleted. So root is kinda buggy on this phone
Click to expand...
Click to collapse
Something possibly wrong with how you rooted.
I never lose root. I also flash both slots with the exact same version of the OxygenOS, TWRP and Magisk in both slots.
I never have an issue and the only time I lose root is when I do an OTA.
Related
Hello, and I apologize if this is in the wrong place, and if there is already a thread to solve my issue please direct me there (I could not find one for my specific issue). I cannot install Magisk without my OP6 becoming stuck in Fastboot mode (I can still access TWRP recovery); Should I get this Blu_Spark? People tell me it's better, especially on OnePlus 6.
So I was installing modules for Magisk, but Magisk itself is fairly new to me; I am used to SuperSU which is now outdated. I enjoy Magisk and its interface and the lot. Earlier today I attempted to install Viper4Android via Magisk and was told I needed BusyBox. I installed it from the app store, but then realized Magisk had a module for it. So I uninstalled BusyBox and installed the module. Upon reboot I found myself stuck in Fastboot. Luckily I could still access TWRP and managed to fix the Bootloop without losing data. I've since made a full backup of my things.
However, now I am facing a new issue altogether. After getting back into the phone Magisk told me that it was not installed. So I uninstalled Magisk via their flashable uninstaller and attempted to reinstall. Now I think Magisk itself is causing these issues. I don't want to wipe and do a fresh reset because the phone has a large capacity and I have a lot on it. Backup would be 180GB+ and restoration would take forever. Unless I'm missing something...
Basically I had to uninstall Magisk completely for it to go back to my phone. I just want my root. Also, is LineageOS worth it, I hear OxygenOS is superior but I enjoy the features Lineage has. Thank you.
Why is Magisk causing these issues? The only thing I can think of was my mess-up with BusyBox. If anyone could help me find an alternative to a factory reset to fix Magisk so it doesn't cause bootloop or fastboot I'd appreciate it.
Thank you for your time
FURTHER INFORMATION UPON INQUIRY
If its better to provide solution if you include exact version name of your OS or magisk or twrp or other details instead of mentioning just names!
However below Solution might work if you are in Android 10. Read and follow the steps carefully
1. So if you access TWRP, flash Magisk Uninstaller so it will remove magisk and its existing modules. Dont teboot
2. Then flash the stock boot image or Full Rom ZIP in boot partition(current boot partition). Don't reboot since now you will lose TWRP as it will replace stock recovery. Remember dont reboot
3. Flash TWRP installer zip(not twrp image) and then now reboot to recovery. So now you have a fully working TWRP in OOS 10 with Magisk stuff removed. . Don't reboot .
4. Now Flash Magisk v20.1. Reboot to system.
Edit: you can get Twrp img and zip file from here https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
tvteja said:
If its better to provide solution if you include exact version name of your OS or magisk or twrp or other details instead of mentioning just names!
However below Solution might work if you are in Android 10. Read and follow the steps carefully
1. So if you access TWRP, flash Magisk Uninstaller so it will remove magisk and its existing modules. Dont teboot
2. Then flash the stock boot image or Full Rom ZIP in boot partition(current boot partition). Don't reboot since now you will lose TWRP as it will replace stock recovery. Remember dont reboot
3. Flash TWRP installer zip(not twrp image) and then now reboot to recovery. So now you have a fully working TWRP in OOS 10 with Magisk stuff removed. . Don't reboot .
4. Now Flash Magisk v20.1. Reboot to system.
Edit: you can get Twrp img and zip file from here https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Click to expand...
Click to collapse
Thank you so much for your suggestion, and reply. Magisk and TWRP were up to date (the latest releases); Magisk v20.1, and TWRP 3.3.1.2 ("Enchilada"). My device is a OnePlus 6 running Android 9, last updated August 1st of this year, "ONEPLUS A6003_22_190911"
I will try your suggestion and respond as soon as possible. If there is anything else you need to know, ask. I am new to the concept of forums so I've been kinda flopping around like a fish out of water. :laugh:
Marmalade_Shaws said:
Hello, and I apologize if this is in the wrong place, and if there is already a thread to solve my issue please direct me there (I could not find one for my specific issue). I cannot install Magisk without my OP6 becoming stuck in Fastboot mode (I can still access TWRP recovery); Should I get this Blu_Spark? People tell me it's better, especially on OnePlus 6.
So I was installing modules for Magisk, but Magisk itself is fairly new to me; I am used to SuperSU which is now outdated. I enjoy Magisk and its interface and the lot. Earlier today I attempted to install Viper4Android via Magisk and was told I needed BusyBox. I installed it from the app store, but then realized Magisk had a module for it. So I uninstalled BusyBox and installed the module. Upon reboot I found myself stuck in Fastboot. Luckily I could still access TWRP and managed to fix the Bootloop without losing data. I've since made a full backup of my things.
However, now I am facing a new issue altogether. After getting back into the phone Magisk told me that it was not installed. So I uninstalled Magisk via their flashable uninstaller and attempted to reinstall. Now I think Magisk itself is causing these issues. I don't want to wipe and do a fresh reset because the phone has a large capacity and I have a lot on it. Backup would be 180GB+ and restoration would take forever. Unless I'm missing something...
Basically I had to uninstall Magisk completely for it to go back to my phone. I just want my root. Also, is LineageOS worth it, I hear OxygenOS is superior but I enjoy the features Lineage has. Thank you.
Why is Magisk causing these issues? The only thing I can think of was my mess-up with BusyBox. If anyone could help me find an alternative to a factory reset to fix Magisk so it doesn't cause bootloop or fastboot I'd appreciate it.
Thank you for your time
FURTHER INFORMATION UPON INQUIRY
Click to expand...
Click to collapse
tvteja said:
If its better to provide solution if you include exact version name of your OS or magisk or twrp or other details instead of mentioning just names!
However below Solution might work if you are in Android 10. Read and follow the steps carefully
1. So if you access TWRP, flash Magisk Uninstaller so it will remove magisk and its existing modules. Dont teboot
2. Then flash the stock boot image or Full Rom ZIP in boot partition(current boot partition). Don't reboot since now you will lose TWRP as it will replace stock recovery. Remember dont reboot
3. Flash TWRP installer zip(not twrp image) and then now reboot to recovery. So now you have a fully working TWRP in OOS 10 with Magisk stuff removed. . Don't reboot .
4. Now Flash Magisk v20.1. Reboot to system.
Edit: you can get Twrp img and zip file from here https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Click to expand...
Click to collapse
Hello, just wanted to update you. I am happy to report your suggestion worked. Sadly I still lost my data, but that's alright; all the important bits were already backed up. Just lost the home screen layout and some application settings. All the same, I am now successfully running my rooted device and couldn't be happier! Thanks! :laugh::good:
Marmalade_Shaws said:
Hello, and I apologize if this is in the wrong place, and if there is already a thread to solve my issue please direct me there (I could not find one for my specific issue). I cannot install Magisk without my OP6 becoming stuck in Fastboot mode (I can still access TWRP recovery); Should I get this Blu_Spark? People tell me it's better, especially on OnePlus 6.
So I was installing modules for Magisk, but Magisk itself is fairly new to me; I am used to SuperSU which is now outdated. I enjoy Magisk and its interface and the lot. Earlier today I attempted to install Viper4Android via Magisk and was told I needed BusyBox. I installed it from the app store, but then realized Magisk had a module for it. So I uninstalled BusyBox and installed the module. Upon reboot I found myself stuck in Fastboot. Luckily I could still access TWRP and managed to fix the Bootloop without losing data. I've since made a full backup of my things.
However, now I am facing a new issue altogether. After getting back into the phone Magisk told me that it was not installed. So I uninstalled Magisk via their flashable uninstaller and attempted to reinstall. Now I think Magisk itself is causing these issues. I don't want to wipe and do a fresh reset because the phone has a large capacity and I have a lot on it. Backup would be 180GB+ and restoration would take forever. Unless I'm missing something...
Basically I had to uninstall Magisk completely for it to go back to my phone. I just want my root. Also, is LineageOS worth it, I hear OxygenOS is superior but I enjoy the features Lineage has. Thank you.
Why is Magisk causing these issues? The only thing I can think of was my mess-up with BusyBox. If anyone could help me find an alternative to a factory reset to fix Magisk so it doesn't cause bootloop or fastboot I'd appreciate it.
Thank you for your time
FURTHER INFORMATION UPON INQUIRY
Click to expand...
Click to collapse
Hey, I'm in a similar situation you were in and I'm stuck in a bootloop after I flashed/installed busybox from magisk repo, I wanted viper 4android as well and while installing viper it said that I'd need busybox. Soon after I install busy box from magisk I'm in this bootloop, i have access to twrp luckily and i tried deleting this busybox and viper 4android module from twrp file manager but still I'm in a boot loop, can you guide me on how you managed to get out of this bootloop?? Thanks
So back when I got my phone I had got it Sim unlocked and bootloader unlocked. Installed twrp and magisk to use some spoofing apps on my phone
Lately I've been promoted to update and just continually ignored it. It has since updated to 10.0.2.GM31CB.
My question is how can I return twrp and magisk to use my spoofs again? Once updated magisk wouldn't launch and got errors trying to use the spoof, so I'm pretty sure it deleted both magisk and twrp. I know things are different with the T-Mobile version so I'm scared to try an old version of a guide unless someone knows it still works
Just want directed to where to look to get those from the version I'm on, thanks!
Honestly not sure how you got the update with twrp installed it always failed for me. Had to restore original boot.img to install.
But the update relocks the bootloader ... At least it did for me so hopefully you still have your unlock bin. Just unlock the bootloader and root as usual.
Unfortunately unlocking wipes.
If your bootloader didn't relock just root per the guide
nujackk said:
If your bootloader didn't relock just root per the guide
Click to expand...
Click to collapse
Agreed. Would like to add, depending on which guide the top poster used to root originally, to make sure they use a version TWRP that is compatible with Android 10 (unofficial TWRP version -75 is the current); and current Magisk (20.3) is advisable, as well.
---------- Post added at 09:08 AM ---------- Previous post was at 08:51 AM ----------
StrawHatZakk said:
Lately I've been promoted to update and just continually ignored it. It has since updated to 10.0.2.GM31CB.
Click to expand...
Click to collapse
Did it reboot automatically after the forced update? If not, next time this happens, you should be able to do the following to easily keep root and TWRP:
1) After the update, do not reboot.
2) Open Magisk Manager
3) Flash TWRP installer zip as it were a Magisk module
4) Install Magisk, picking option "Install to Inactive Slot (After OTA)"
5) Reboot, and you should be on the updated OOS version, with root and TWRP.
Try this, if this ever happens again (forced update). But as mentioned, in your present situation you'll need to root using the method you used originally.
StrawHatZakk said:
Once updated magisk wouldn't launch and got errors trying to use the spoof, so I'm pretty sure it deleted both magisk and twrp.
Click to expand...
Click to collapse
That is correct, that updating removes root and TWRP. Both Magisk and TWRP patch the boot.img partition in order to install root and TWRP (respectively). Updating the phone overwrites the patched kernel with a new stock boot.img, so it needs to be patched again for TWRP/root to work. The Magisk Manager is an app that resides on the user dat partition, so the app itself remains (as will your other user apps, as is typical for updates). But nothing will really work right, since the necessary boot.img modifications are not present.
StrawHatZakk said:
So back when I got my phone I had got it Sim unlocked and bootloader unlocked. Installed twrp and magisk to use some spoofing apps on my phone
Lately I've been promoted to update and just continually ignored it. It has since updated to 10.0.2.GM31CB.
My question is how can I return twrp and magisk to use my spoofs again? Once updated magisk wouldn't launch and got errors trying to use the spoof, so I'm pretty sure it deleted both magisk and twrp. I know things are different with the T-Mobile version so I'm scared to try an old version of a guide unless someone knows it still works
Just want directed to where to look to get those from the version I'm on, thanks!
Click to expand...
Click to collapse
Just reflash twrp/magisk with powershell
Go to settings developer mode turn off auto install updates.
redpoint73 said:
Agreed. Would like to add, depending on which guide the top poster used to root originally, to make sure they use a version TWRP that is compatible with Android 10 (unofficial TWRP version -75 is the current); and current Magisk (20.3) is advisable, as well.
---------- Post added at 09:08 AM ---------- Previous post was at 08:51 AM ----------
Did it reboot automatically after the forced update? If not, next time this happens, you should be able to do the following to easily keep root and TWRP:
1) After the update, do not reboot.
2) Open Magisk Manager
3) Flash TWRP installer zip as it were a Magisk module
4) Install Magisk, picking option "Install to Inactive Slot (After OTA)"
5) Reboot, and you should be on the updated OOS version, with root and TWRP.
Try this, if this ever happens again (forced update). But as mentioned, in your present situation you'll need to root using the method you used originally.
That is correct, that updating removes root and TWRP. Both Magisk and TWRP patch the boot.img partition in order to install root and TWRP (respectively). Updating the phone overwrites the patched kernel with a new stock boot.img, so it needs to be patched again for TWRP/root to work. The Magisk Manager is an app that resides on the user dat partition, so the app itself remains (as will your other user apps, as is typical for updates). But nothing will really work right, since the necessary boot.img modifications are not present.
Click to expand...
Click to collapse
I took my sweet time trying it but wanted to get root back as I just moved and won't have internet for a while. Everything seemingly went fine, got TWRP going then after installing Magisk it would just hang at the t-mobile screen indefinitely. Attempted to do a restore with TWRP and must have hit a leftover restore from the previous android version now the only thing it does is boot to the fast boot section. Might make a new topic but I'm searching everywhere for a fix, can't seem to get this MSM tool thing to recognize it... thinking I might just be boned. If you know of any fixes let me know lol.
Hi guys. I know there has been a million topics about this and I've read most of them but does anyone know which route is currently the safest for an ota update? I have a 7pro rooted with Twrp and magisk. I'm on 10.0.5 and looking to update to 10.0.10.
Should I use trwp recovery and flash everything from there or can I flash locally and then use magisk along with the a/b retention script? I messed up rooting the phone originally and lost some data and now I have a mental block around which method is safest to do without losing my data or bootlooping. I want to make sure both slots update correctly and I'm unsure of the correct method.
Any help would be appreciated before I give it a go, thank you.
I'm also wondering if I've edited the build prop in any way with the build prop editor, will this cause a boot loop or will a full ota zip return it to normal anyway?
Thanks
Bxperiaz3 said:
Hi guys. I know there has been a million topics about this and I've read most of them but does anyone know which route is currently the safest for an ota update? I have a 7pro rooted with Twrp and magisk. I'm on 10.0.5 and looking to update to 10.0.10.
Should I use trwp recovery and flash everything from there or can I flash locally and then use magisk along with the a/b retention script? I messed up rooting the phone originally and lost some data and now I have a mental block around which method is safest to do without losing my data or bootlooping. I want to make sure both slots update correctly and I'm unsure of the correct method.
Any help would be appreciated before I give it a go, thank you.
Click to expand...
Click to collapse
the typical and safe route to take an OTA and keep your root is:
download OTA using oxygen downloader app
Use the sytem update app to install the file above using the local upgrade option. DO NOT REBOOT.
Use magisk to install the twrp a/b keeper script. DO NOT REBOOT.
Use magisk to install magisk to the inactive slot. Then reboot.
I have the gm1913 phone which is a different variant, but I'm sure that the concept is the same.
Good luck.
Thanks for the reply. Did something similar to this
What I ended up doing incase anyone else needs to know..
Disable all magisk modules and reboot
Flash full update from local storage
Don't reboot
Go to magisk and flash twrp zip
Don't reboot
Flash magisk zip to separate slot (ota option)
Now phone reboots its self
Re enable modules in Magisk
Reboot
Profit
Hi people. I have been rooted since day one on September 2020. I NEVER had a single issue with root and OTAs.
Since the last update, everytime I reboot, I loose root. The Magisk app (beta) stays but the root is gone.
What I have to do, since my bootloader is unlocked since day one is: I extract the boot.img file with payload dumper, patch it with magisk, reboot in fastboot and push it with ADB.
Any permanent solution?
I still have no issues although running 11.1.9.9 as well. I use Magisk 24.1 and whenever I got an OTA installed I flash magisk on the inactive partition and boot to it, I never lose root
Actually the only thing I can imagine is that your phone boots to the opposite partition. you could try to flash magisk to the inactive slot, but no warranty this will fix your issue
TheSSJ said:
I still have no issues although running 11.1.9.9 as well. I use Magisk 24.1 and whenever I got an OTA installed I flash magisk on the inactive partition and boot to it, I never lose root
Actually the only thing I can imagine is that your phone boots to the opposite partition. you could try to flash magisk to the inactive slot, but no warranty this will fix your issue
Click to expand...
Click to collapse
I don't know why but after switching to the beta Magisk channel the problem seems to be fixed. Weird.
exnokiafan said:
Hi people. I have been rooted since day one on September 2020. I NEVER had a single issue with root and OTAs.
Since the last update, everytime I reboot, I loose root. The Magisk app (beta) stays but the root is gone.
What I have to do, since my bootloader is unlocked since day one is: I extract the boot.img file with payload dumper, patch it with magisk, reboot in fastboot and push it with ADB.
Any permanent solution?
Click to expand...
Click to collapse
Can you share boot .img , I also want to root my phone.
I rooted my A7160 last year using Magisk only, no TWRP, since I couldn't find TWRP for the Exynos chipset. A couple days ago I dumbly let Magsik update to v22.1, which removed Magisk Hide, an essential for me. I want to downgrade Magisk, but haven't yet found a way to do so without TWRP.
First, does anyone know of a way to downgrade Magisk without TWRP? I've tried restoring my Titanium Backup of Manager, but that prompts me to download and install the full Magisk, which will leave me with the new Magisk. I also tried fresh install of the 7.5.1 Magisk Manager app, which only lets me install 22.1.
Second, is there any work on or anyone willing to work on TWRP or other custom recovery for the Exynos chipset (A7160)?
Third, is there any other way to hide root? A brief search did not yield anything promising yet.
Thanks in advance!
stgibson said:
I rooted my A7160 last year using Magisk only, no TWRP, since I couldn't find TWRP for the Exynos chipset. A couple days ago I dumbly let Magsik update to v22.1, which removed Magisk Hide, an essential for me. I want to downgrade Magisk, but haven't yet found a way to do so without TWRP.
First, does anyone know of a way to downgrade Magisk without TWRP? I've tried restoring my Titanium Backup of Manager, but that prompts me to download and install the full Magisk, which will leave me with the new Magisk. I also tried fresh install of the 7.5.1 Magisk Manager app, which only lets me install 22.1.
Second, is there any work on or anyone willing to work on TWRP or other custom recovery for the Exynos chipset (A7160)?
Third, is there any other way to hide root? A brief search did not yield anything promising yet.
Thanks in advance!
Click to expand...
Click to collapse
FYI Update for others' reference: I got what I needed with Zygisk and DenyList, so should be OK without downgrading. If I need to downgrade, I realized an option that may work: re-flashing the previously-used patched boot.img.