Related
hey guys, so I want to encrypt my phone but I want to stay rooted with magisk and xposed. (Using SuperSU 2.78 SR3). Device: OnePlus One running SultanXDA's CM13.
Are there any special steps I need to take before I start the encryption process? do I need to completely unroot and remove all traces of all these before going back or will it just work?
I haven't seen this question addressed before and this would help others with the same questions.
Thanks for any advice!
Since there was no support from anyone, I decided to just remove everything (xposed, magisk and supersu) then encrypt, and finally re-add everything back. I did this just to avoid any complications and all works fine without issue.
@Nomelas what version of magisk did you use? and did you sideload them or just flash with the cache work around?
I've been at this all day with no luck
@GbizzleMcGrizzle what phone are you using? I had to completely remove everything before encrypting. Also reflashed stock system
@Nomelas Galaxy S7 (SM-G930F) it wont encrypt with magisk installed and magisk wont install after it has been encrypted.
@GbizzleMcGrizzle are you flashing through twrp? (are you decrypting when you boot into twrp)
i've tried flashing in twrp and sideloading. I don't think I can decrypt in twrp but magisk says it has a work around for not beiing able to boot /data and supposedly put in in cache and then moves it to data after boot so IDK
After installing the magisk as I was rooted, I installed 2-3 mods ie flashed in twrp but after I rebooted my root is gone. Magisk manager is showing not rooted and when I re flashed supersu in twrp, installation was successful but still no root. What happened I don't know. Also I didn't install any phh supersu or busybox. Please help me regain my root.
HELP
It was a known bug in Magisk that you would lose root.
Magisk
v10.2
- [Magic Mount] Remove apps/priv-app from whitelist, should fix all crashes
- [phh] Fix binary out-of-date issue
- [scripts] Fix root disappear issue when upgrading within Magisk Manager
Click to expand...
Click to collapse
So i'd make sure you flashed the latest version ? Pretty sure you have but if not might be worth flashing supersu then magisk over it again as it should recognise supersu and not modify it.
brichardson1991 said:
It was a known bug in Magisk that you would lose root.
So i'd make sure you flashed the latest version ? Pretty sure you have but if not might be worth flashing supersu then magisk over it again as it should recognise supersu and not modify it.
Click to expand...
Click to collapse
Yeah I just installed the latest version 10.2 via play Store. Help me regain my root
Vaibhunk786 said:
Yeah I just installed the latest version 10.2 via play Store. Help me regain my root
Click to expand...
Click to collapse
After installing from play store, did you "FLASH" magisk ?
brichardson1991 said:
After installing from play store, did you "FLASH" magisk ?
Click to expand...
Click to collapse
No I didn't flash anything. It was an automatic process which installed magisk and prompted me that installation success and reboot. Then I rebooted and root was gone
Now should I run magisk unstaller zip in twrp followed by supersu and then again flash magisk v10. 2 via twrp.. Should I follow these steps to gain my root again.. Anyone please help. I'm stuck @brichardson1991
Try installing PHH superuser from play store.
I had a similar experience. Having to reflash stock now to try a different tact. I'd rather use SuperSU to be honest, rather than PHH superuser.
Same problem here, have to investigate whats going on.
MattBooth said:
I had a similar experience. Having to reflash stock now to try a different tact. I'd rather use SuperSU to be honest, rather than PHH superuser.
Click to expand...
Click to collapse
yeah flashing the stock rom was the only viable option i think .
I have the same problem with latest magisk. After i installed mods root is gone and i can not root again. Only with supersu i have root. Magisk is very bugy.
Yeah it does appear the latest version now causes you to lose supersu
Same problem with me, on the OP3 running Open Beta 11. Reflashing SuperSU did not work. Rather than extract the boot.img to reflash that, I ended up reflashing the firmware (and ended up mistakenly using the 4.0.1 file instead of the OPB11 one!) ... Yet to try SuperSU and Magisk again on this, but figured better to investigate the issue before I attempt to reinstall.
From what I understand here, v10 won't have this problem, and its only on v11 that its cropped up again? Can anybody with v10 confirm this?
Hello, I am currently rooted on stock oos 4.0.3, with latest TWRP and super su free v2.79, can anyone help me out and tell me how to switch to magisk please, thank you!
Can I just use super su full unroot option then flash magisk?
Either reflash the original boot.img or download the unsu script from https://forum.xda-developers.com/showpost.php?p=63615067, then flash magisk again.
palesaint said:
Either reflash the original boot.img or download the unsu script from https://forum.xda-developers.com/showpost.php?p=63615067, then flash magisk again.
Click to expand...
Click to collapse
so flash unsu, then flash magisk. simple?
Dr Grato said:
so flash unsu, then flash magisk. simple?
Click to expand...
Click to collapse
If you use the unSU script the process is:
unSU
stock boot image
Magisk
This method did not work for me.
I am on KETAN n10 and initially, viper did not work. I installed magisk but that didn't fix it. nor the meefik busy box. So i decided to uninstall magisk and go back to superSU and it magically worked...
I unrooted from SuperSU itself like shown on the app's forum I believe. It rebooted my phone, I went into recovery first and then just flashed the latest magisk and made the switch :laugh:
SourPower said:
I unrooted from SuperSU itself like shown on the app's forum I believe. It rebooted my phone, I went into recovery first and then just flashed the latest magisk and made the switch :laugh:
Click to expand...
Click to collapse
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?
JG420 said:
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?
Click to expand...
Click to collapse
If there's a proper backup of the boot image for the SuperSU app's full unroot option to restore, then that process should work perfectly (I've done it on a few devices myself). It's when it can't properly restore the boot image you might have issues and you'll have to do it yourself.
Take a look in the Magisk Troubleshooting guide, under "Moving from another systemless root solution to MagiskSU".
The nuclear method might be, to just flash the full stock OOS zip (can flash in TWRP) which will unroot and restore the boot.img (and everything else!). Then immediately flash Magisk before rebooting (so have the Magisk zip on the phone before updating). This should fully remove SuperSU, install Magisk, and keep TWRP on the phone.
Seeing as the original poster is still on OOS 4.0.3, you may want to update, anyway!
JG420 said:
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?
Click to expand...
Click to collapse
I've done this on my 3t but I do have a G3 coincidentally lol, but yes I unrooted from su, it restarted my phone, before booting back into the system I went in twrp right away and then flashed magisk.
There are two options given in the SuperSU app, one is clean up to switch to a different SU app and the other is to permanently unroot. Which option is better?
hypothrax said:
There are two options given in the SuperSU app, one is clean up to switch to a different SU app and the other is to permanently unroot. Which option is better?
Click to expand...
Click to collapse
I chose the Full Unroot option. Then flashed magisk. Worked perfectly.
Use the full unroot option. Catch here is that you might get dm-verity warning. It won't affect the phone in anyway but Android Pay might not work and you will see the warning for 5 seconds, everytime you restart the phone.
Thanks so much for ths thread. I am on Resurrection Remix OS and inititally installed SuperSU over Magisk (which came with the ROM). I decided that I wanted to use Magisk instead and followed the instructions in this thread and it worked a treat.
Pretty much as in the title. I believe it was on the dualrecovery root for 5.1.1 and the latest supersu binary update just dropped it into a bootloop. What do I do now?
Same issue here... Don't know what to do!
Welp factory reset in both recoveries didn't do anything.
Seems that manually flashing the 2.81 supersu zip worked for me.
Yep I posted a workaround in the superSU thread a couple of days ago. Flashing the zip version from TWRP works and fixes the bootloop.
i have the same issue and i am not know with this flash stuff
what should i do can some one explain to me
same problem anyone plz post the step to fix this
s2nabil said:
same problem anyone plz post the step to fix this
Click to expand...
Click to collapse
Boot into TWRP recovery and install SuperSu 2.79 zip from ChainFire or his latest v2.82 linked below that supposedly fixes the issue with bootloop on Xperia devices.
https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip
Thread discussing the problems and solutions.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page1019
The last SuperSU 2.82 from 28.05.2017 working fine ... at last
Rebel2k said:
Same issue here... Don't know what to do!
Click to expand...
Click to collapse
Same problem but my computer wont recognise my phone & will only charge my phone I bought a new cable aswell still will only charge, Someone if any idea please help be appreciated.
Did you try to start in recovery with your phone, run the TWRP file manager and plug your phone? Don't you get access to the phone file system?
EQ2000 said:
Boot into TWRP recovery and install SuperSu 2.79 zip from ChainFire or his latest v2.82 linked below that supposedly fixes the issue with bootloop on Xperia devices.
https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip
Thread discussing the problems and solutions.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page1019
Click to expand...
Click to collapse
https://download.chainfire.eu/1113/S...0528234214.zip
v2.82 updated work fine for me, thank u
EQ2000 said:
Boot into TWRP recovery and install SuperSu 2.79 zip from ChainFire or his latest v2.82 linked below that supposedly fixes the issue with bootloop on Xperia devices.
https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip
Thread discussing the problems and solutions.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page1019
Click to expand...
Click to collapse
I was able to solve the boot loop problem with your advice but now the SuperSU icon is disappeared
Any idea how to bring it back?
so I had the exact same problem......supersu asked for an update and that caused a boot loop on my Z1c
I reflashed supersu using recovery,
First v2.82 << that did NOT fix the boot loop
Then v2.79 << this fixed the boot loop.
However, I left the phone to charge for a few minutes and supersu auto updated. Now it says it is v2.82 inside the supersu app. The app still keeps nagging about an update.......which I am not installing, fearing it will cause the boot loop again
Fix
Try to flash supersu.zip in twrp it's works on me
I also as many other users here have updated the library of super Su (got the
notification). And after the installation and rebooting got into the booting loop.
I have wiped cache and dalvick cashe with TWRP but it didn't help. I installed the
2.82 Update-SuperSu via TWRP. And after the long time of apps optimization I was
able to boot into the Android (Lollipop 5.1). However, I found the root was lost.
The RootChecker saying: "Root access is not properly installed on this device".
So, basically my question is how to restore the root and keep the bootloader locked
(important!)
Here I see several scenarios:
1. Restore using TWRP backup.
Should I wipe cache, dalvik cache and data before and after the restore?
2. install Update_SuperSU 2.79 or 2.76 (originally I have version 2.76)
Should I wipe cache, dalvik cache and data before and after the installation?
3. Flash with pre-rooted ROM.
Should I wipe cache, dalvik cache and data before and after the installation?
4. Start from zero, i.e to follow the procedure I have rooted the phone at time
I've purchased it. Namely:
4.1 Downgrade to KitKat
4.2 Root with FlashTool.
4.3 Flash prerooted Lollipop rom with TWRP
4.4 Flash with customized Lollipop rom
Xperia Z3c (compact)
Lollipop 5.1.1
I would appreciate for your suggestions.
Question for those you you way smarter than I'll ever hope to be. I randomly lost root and TWRP on my 3T and I have no idea how this happened.
Quick (or not so quick) background - I was stock rooted OOS 4.1.6. I disabled AdAway for a bit yesterday to gain access to something it was blocking (done it many times) and when I re-enabled it my phone was stuck in a boot loop afterwards. Weird, but not concerning. I booted into TWRP and restored a backup. OOS 4.1.3 was my latest backup, so after successfully loading that up, I flashed the full 4.1.6 OTA and SuperSu as I've done before to update. Worked fine. Was adding my preferred mods via Substratum and Magisk and I messed up. Couldn't get Substratum to work properly and couldn't get Magisk to update to 13.1. I verified I had root, which I did. Went back to TWRP and reflashed 4.1.6 and SuperSU. When my phone was up and running again I didn't have root. Weird, so I tried again, still couldn't get SuperSU to flash properly. Got frustrated and figured I haven't had a clean install since getting the device in January. Every update I've flashed via TWRP has been dirty. So, factory reset, blah, blah, blah. Done it plenty of times with many devices. Flashed the OTA and SuperSu again, but noticed SuperSu failed. Rebooted recovery to try again, but it went to the stock recovery. My phone is working fine now, but I'm without root and I no longer have TWRP.
What might have caused this to happen? And how can I avoid it in the future? I know how to get it back (I'll do it after work) but it's frustrating.
What version of TWRP are you using? A few of the past versions have been having problems.
If you're already using Magisk anyways, just flash the Magisk zip and use that as your rooting solution. IIRC, the more recent versions of Magisk are no longer compatible with SuperSU anyways.
Anova's Origin said:
What version of TWRP are you using? A few of the past versions have been having problems.
If you're already using Magisk anyways, just flash the Magisk zip and use that as your rooting solution. IIRC, the more recent versions of Magisk are no longer compatible with SuperSU anyways.
Click to expand...
Click to collapse
I was using 3.0.4-1. Never had an issue before. But after I factory reset my phone and clean flashed the 4.1.6 update I ended up with the stock recovery. Unless I'm mistaken, I can't flash Magisk until I have TWRP again. I know how to get it back, I was more curious as to how this may have happened in the first place. What would have caused my root and custom recovery to disappear?
Rodeojones said:
I was using 3.0.4-1. Never had an issue before. But after I factory reset my phone and clean flashed the 4.1.6 update I ended up with the stock recovery. Unless I'm mistaken, I can't flash Magisk until I have TWRP again. I know how to get it back, I was more curious as to how this may have happened in the first place. What would have caused my root and custom recovery to disappear?
Click to expand...
Click to collapse
My mistake, I meant to ask SuperSU version, not TWRP. If SuperSU failed to root your phone after dirty flashing OOS (even if there was not error message), OOS will replace your recovery with the stock one.
Anova's Origin said:
My mistake, I meant to ask SuperSU version, not TWRP. If SuperSU failed to root your phone after dirty flashing OOS (even if there was not error message), OOS will replace your recovery with the stock one.
Click to expand...
Click to collapse
I was using version 2.8.2. Regardless, you answered my question as to how it happened in the first place, so thanks.