I just unlocked my bootloader, and rooted my Nexus 6, and installed TWRP 3.0.0 using the Nexus Root Toolkit.
I just installed Adaway, and unrooted it, cus I use a lot of banking apps.
But the question is, when I want to re-root it, could I just flash supersu zip with the custom recovery and that's it?
or do I have to do the root process all over again?
I remember using TWRP 2.8.6.0 on the oneplus one, and when I rebooted it from the custom recovery, it said something like
'It seems like supersu is not installed would you like to install it?' or something like that.
and 'yes' would re-root it, that simple.
it seems like TWRP 3.0.0 doesn't have that.
Thanks
You don't really want to try to root using the built-in option in TWRP - with the newer Android builds (6.x), that won't work - you need to use the current version of supersu that modifies the boot img - I prefer the systemless version.
Glad to hear that TWRP 3.x has removed the prompt for installing supersu.
You should be able to reroot.
I agree with the above, keep systemless root in twrp's readytoflash folder and boot into twrp and flash that zip as you need it.
Sent from my Nexus 6 using XDA Labs
I think I remember (but not sure) that I read that TWRP 3 is smart enough not to suggest the root option when SuperSU systemless is installed, whereas the older versions tempted unwary users to root their already-rooted device and screwed it up in the process. Smart piece of programming to remove the misleading option.
root > flash kernel (boot.img) and then supersu 2.68 (latest)
un-root > flash kernel
thats it
Related
Hey y'all - I saw this and am wondering if this is still applicable?
I'm on v7 with phh's SuperUser r259; so if, say, the November security patch drops, I can accept, download, and install directly from the notification panel? Or am I reading this wrong?
TIA!
alamo76 said:
Hey y'all - I saw this and am wondering if this is still applicable?
I'm on v7 with phh's SuperUser r259; so if, say, the November security patch drops, I can accept, download, and install directly from the notification panel? Or am I reading this wrong?
TIA!
Click to expand...
Click to collapse
You should be able to, but you will have to reflash the magisk zip so that the boot image is re-patched. I accepted an OTA on my Nexus 6P without any issues although I did use Flashfire.
ryaniskira said:
You should be able to, but you will have to reflash the magisk zip so that the boot image is re-patched. I accepted an OTA on my Nexus 6P without any issues although I did use Flashfire.
Click to expand...
Click to collapse
I want to try to start from stock and be able to get OTA updates.
First post in phh's SuperUser states that phh's SuperUser r259 "Magisk compatible, no boot image modifications are required"
So then I am guessing we don't need to reflash Magisk again since boot image is untouched.
Also what about the recovery? Will OTA update replace the twrp and therefore, TWRP needs to be reflshed after each OTA update.
Maybe someone who experienced this can write what needs to be done in order to successfully flash OTA update.
Thanks.
Orochi77 said:
I want to try to start from stock and be able to get OTA updates.
First post in phh's SuperUser states that phh's SuperUser r259 "Magisk compatible, no boot image modifications are required"
So then I am guessing we don't need to reflash Magisk again since boot image is untouched.
Also what about the recovery? Will OTA update replace the twrp and therefore, TWRP needs to be reflshed after each OTA update.
Maybe someone who experienced this can write what needs to be done in order to successfully flash OTA update.
Thanks.
Click to expand...
Click to collapse
Yes because Magisk itself modifies the boot image. So that's why the Magisk version of PHH Superuser doesn't modify the boot image.
Also, you can use FlashFire to install OTAs and preserve the custom recovery, also you can set it to reflash Magisk after the OTA. (With PHH Superuser, SELinux needs to be in permissive mode to use FlashFire)
ryaniskira said:
Yes because Magisk itself modifies the boot image. So that's why the Magisk version of PHH Superuser doesn't modify the boot image.
Also, you can use FlashFire to install OTAs and preserve the custom recovery, also you can set it to reflash Magisk after the OTA. (With PHH Superuser, SELinux needs to be in permissive mode to use FlashFire)
Click to expand...
Click to collapse
But FlashFire says it needs SuperSU or cm's SU
KaMonsieur said:
But FlashFire says it needs SuperSU or cm's SU
Click to expand...
Click to collapse
PHH's Superuser technically is CM's SU, it's a fork of Koishik's Superuser that was used in CM up until MM.
ryaniskira
With PHH Superuser, SELinux needs to be in permissive mode to use FlashFire
Click to expand...
Click to collapse
I am on stock samsung kernel which is set to SELinux enforcing.
What are my options in terms of getting OTA and what needs to be done?
Do I accept OTA, then flash recovery and flash Magisk + PHH Supersuser?
Can I use Flashfire with supersu instead of PHH superuser, will it work with SELinux enforcing?
Thanks for your time.
ryaniskira said:
PHH's Superuser technically is CM's SU, it's a fork of Koishik's Superuser that was used in CM up until MM.
Click to expand...
Click to collapse
I once used SuperSU and FlashFire. But I did not set SElinux to permissive myself. Does SuperSU automatically do it?
KaMonsieur said:
I once used SuperSU and FlashFire. But I did not set SElinux to permissive myself. Does SuperSU automatically do it?
Click to expand...
Click to collapse
SELinux does not need to be set to permissive when you use SuperSU because SuperSU modifies SEPolicy to allow his apps to work with SELinux set to enforcing.
ryaniskira
So to get OTA update in a reliable way. One has to do the following steps.
1. TWRP
2. SuperSu
3. Magisk 7
4. Flashify
Let me know if this is correct?
ryaniskira said:
SELinux does not need to be set to permissive when you use SuperSU because SuperSU modifies SEPolicy to allow his apps to work with SELinux set to enforcing.
Click to expand...
Click to collapse
Thanks for your help!
Answering to my previous post.
In my case flashfire was useless as it could not detect ota zip update at all on my S5, even when I pointed flashfire to the exact location.
It is possible that the OTA zip is encrypted. I could not even open it as archive.
Even if system is untouched, updater detects custom boot image (patched by supersu) and custom recovery. I was able to fool the system by turning the device status to official. Then flashing original recovery and flashing the OTA. Of course after this, you would have to flash custom recover, root and magisk. Unless the process with stock recovery and stock boot is automated, it seems like too much work.
For now, the easiest solution is just to flash an updated firmware when it comes out. This way it will update everything while preserving your data partition.
This begs me to ask this question. Why even bother with systemless this or systemless that. At the end after flashing an updated firmware, the system partition will be overwritten whether it was systemless or not.
Orochi77 said:
Answering to my previous post.
In my case flashfire was useless as it could not detect ota zip update at all on my S5, even when I pointed flashfire to the exact location.
It is possible that the OTA zip is encrypted. I could not even open it as archive.
Even if system is untouched, updater detects custom boot image (patched by supersu) and custom recovery. I was able to fool the system by turning the device status to official. Then flashing original recovery and flashing the OTA. Of course after this, you would have to flash custom recover, root and magisk. Unless the process with stock recovery and stock boot is automated, it seems like too much work.
For now, the easiest solution is just to flash an updated firmware when it comes out. This way it will update everything while preserving your data partition.
This begs me to ask this question. Why even bother with systemless this or systemless that. At the end after flashing an updated firmware, the system partition will be overwritten whether it was systemless or not.
Click to expand...
Click to collapse
For me, the greatest benefit with Magisk is that after an update (by flashing relevant parts of the factory image) all that is needed for my different system modifications is to flash Magisk. It has cut the time it takes for me to update by a huge factor.
Didgeridoohan said:
For me, the greatest benefit with Magisk is that after an update (by flashing relevant parts of the factory image) all that is needed for my different system modifications is to flash Magisk. It has cut the time it takes for me to update by a huge factor.
Click to expand...
Click to collapse
What tool are you using to flash your firmware?
Orochi77 said:
What tool are you using to flash your firmware?
Click to expand...
Click to collapse
Big update, fastboot from my PC. Small update (monthly security update), flash boot and system image in TWRP.
Didgeridoohan said:
Big update, fastboot from my PC. Small update (monthly security update), flash boot and system image in TWRP.
Click to expand...
Click to collapse
Ok thanks. I have to use odin as I have Samsung phone.
When you flash system and boot, don't you lose root?
Orochi77 said:
Ok thanks. I have to use odin as I have Samsung phone.
When you flash system and boot, don't you lose root?
Click to expand...
Click to collapse
Flashing boot image means I need to reflash Magisk (and my custom kernel), but that's it. I use Magisk compatible phh's superuser, which means that's all I need to do. That's why I use (and love) Magisk.
I'm sorta n00b these days been years since ive been much into modding, but got a couple simple questions, i think i know the answer from what i've seen and read, but just want to verify. Save myself a bit of time if i screw it up.
My Device:
LG Nexus 5x Stock ROM 7.1.1 (Recently Flashed clean image that included Feb 2017 security patch) w/ElementalX Kernel
Magisk v11.x (whatever the most recent is, it's up to date) w/phh superuser
I want to flash the new March 2017 Security patch, ideally without losing any data or having to restore all my apps and data from backup ect.. This is what it seems i should do, i think i can use Flashfire (yes it detects my OTA packages and asks to prepare to flash):
I do backups regularly via otg to an external drive. Just completed one before this post
1. Flash OTA, allow flashfire to handle
2. (RE)flash magisk zip
3. (RE)flash phh superuser
4. (RE)flash elementalX kernel
This should leave everything as it was when i started relatively unmodified besides having the new security patch added yes?
g0d0fmischief said:
I'm sorta n00b these days been years since ive been much into modding, but got a couple simple questions, i think i know the answer from what i've seen and read, but just want to verify. Save myself a bit of time if i screw it up.
My Device:
LG Nexus 5x Stock ROM 7.1.1 (Recently Flashed clean image that included Feb 2017 security patch) w/ElementalX Kernel
Magisk v11.x (whatever the most recent is, it's up to date) w/phh superuser
I want to flash the new March 2017 Security patch, ideally without losing any data or having to restore all my apps and data from backup ect.. This is what it seems i should do, i think i can use Flashfire (yes it detects my OTA packages and asks to prepare to flash):
I do backups regularly via otg to an external drive. Just completed one before this post
1. Flash OTA, allow flashfire to handle
2. (RE)flash magisk zip
3. (RE)flash phh superuser
4. (RE)flash elementalX kernel
This should leave everything as it was when i started relatively unmodified besides having the new security patch added yes?
Click to expand...
Click to collapse
PHH Superuser is not compatible with v11
1. It is either Systemless SuperSU (installed before Magisk, or the included MagiskSU (if systemless SU is not installed before Magisk).
jhedfors said:
PHH Superuser is not compatible with v11
1. It is either Systemless SuperSU (installed before Magisk, or the included MagiskSU (if systemless SU is not installed before Magisk).
Click to expand...
Click to collapse
I did it with a previous version, and upgrade to version 11. As long as i follow those steps to get back to 11 it shouldn't matter does it? Meaning flash the other version of magisk i did to start with along with the corresponding phh su, then allow it to update to v11. This is how i got to v11. I planned on using the very same files to flash and root that i did before and allowing it to update. I read the magisk thread about the updates and changes to it. If this isn't a good idea, or just flat out won't work on that basis of trying to flash the older version and allowing the upgrade as i did initially, should i just flash magisk v11? Didn't want to stray from what worked in this regard. But yea ive read this from the magisk thread
If you're already rooted with MagiskSU, Magisk phh's superuser (not original), or Official Systemless SuperSU
Install/upgrade Magisk Manager from Play Store
Install/upgrade Magisk as prompted in the application
Reboot and you're done!!
I will have lost root by flashing the OTA, right? So say i flash just magisk v11 afterwards, what would i need to flash for root and the app to use once started?
This is the method for rooting and magisk install that i used.. Just allowed it to update to 11 after it starts. Do you mean to say this won't work again?
http://www.theandroidsoul.com/systemless-root-magisk-android/
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.
Hey everyone. I just got my new OnePlus 3T a week back. I was loving it till today but I wanted to mess with my phone and I guess I did just that. Long story short, I was on 7.1.1 and unlocked OEM and installed TWRP. Phone booted up and i went into recovery and installed Super SU and the dm verity. After this step, my phone is stuck on the boot animation. I'm able to access TWRP as well as Fastoot ADB. I want to sideload the stock OxygenOS ROM into my phone through ADB, but i'm unsure which file to flash and the exact process. Could someone please help me out? :crying:
That's why you always make a nandroid back up
I figured out why the adb sideload wasn't working. I tried to do the sideload directly from the ADB cmd while my phone was in fastboot mode. So, I tried an alternate method by going into TWRP and doing the sideloading from the advanced menu. It worked and I'm setting up my OP 3T now Guess I jumped the gun by posting here without thinking.
On a side note, my device doesn't have root access now. Maybe it never got installed properly before getting bricked. I think it had to with the fact that I had updated to 7.1.1 by using a VPN. I'm pretty good at following instructions so i couldn't have gone wrong. Can anyone tell me if i can go ahead and root my device now that I'm back on stock OS?
You dont flash supersu and dm verity files at the same time
No wonder you end up in bootloop
Multiple threads are already there about the same issue.
For root just flash supersu
kunal1540 said:
You dont flash supersu and dm verity files at the same time
No wonder you end up in bootloop
Multiple threads are already there about the same issue.
For root just flash supersu
Click to expand...
Click to collapse
Damn, I didn't know that. I only searched for the bootloop issue and didn't really find something that seemed simple enough for me. Almost all the guides I read had similar instructions so I flashed the Dm-verity first and then the Super SU immediately after that. What does dm verity do if it doesnt need to be flashed? And just so that I'm clear - flashing Super SU is enough and no need to bother with the dm verity?
Rahulsingh9367 said:
Damn, I didn't know that. I only searched for the bootloop issue and didn't really find something that seemed simple enough for me. Almost all the guides I read had similar instructions so I flashed the Dm-verity first and then the Super SU immediately after that. What does dm verity do if it doesnt need to be flashed? And just so that I'm clear - flashing Super SU is enough and no need to bother with the dm verity?
Click to expand...
Click to collapse
There's a much much simpler solution, you just use magisk. There's no need to flash supersu or dm-verity fix, just flash the latest magisk zip file in TWRP -> reboot -> install Magisk manager from playstore and you have perfectly working rooted phone.
fluster84 said:
There's a much much simpler solution, you just use magisk. There's no need to flash supersu or dm-verity fix, just flash the latest magisk zip file in TWRP -> reboot -> install Magisk manager from playstore and you have perfectly working rooted phone.
Click to expand...
Click to collapse
Tried flashing the Magisk v9 zip and checked the option that goes something like "verify after flashing" and it failed. Should I uncheck both those options before flashing or flash the phh super user zip too?
Azar_98 said:
Try the latest version of magisk, v11.6.
http://tiny.cc/latestmagisk
Click to expand...
Click to collapse
Worked perfectly and no hassle at all. Thank you so much!
Rahulsingh9367 said:
Tried flashing the Magisk v9 zip and checked the option that goes something like "verify after flashing" and it failed. Should I uncheck both those options before flashing or flash the phh super user zip too?
Click to expand...
Click to collapse
Always flash the latest magisk, and you don't need to flash phh or anything else. Magisk now comes with magisksu that works great with OOS 4.1.1.
Check the link below for latest magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless
If you don't mind losing your data, you can try this 100% clean but slightly painful install. It might be overkill for most but you can start from a clean slate. Backup your stuff to the PC before you do this.
1. Flash compatible stock recovery (stock recovery for android N) in fastboot
2. Now choose to wipe everything (even music, photos) from stock recovery. You will lose everything on your phone.
3. Sideload OOS 4.1.1 rom
4. Reboot and complete phone setup
You are now completely stock except with a unlocked bootloader. In order to gain root, continue further -
5. Enable developer options in Settings and then enable Advanced Reboot and USB debugging
6. Reboot to fastboot and flash twrp 3.0.4.-1
7. Reboot to twrp and flash Magisk v11. 1 zip
8. Reboot and install Magisk Manager from playstore.
Congratulations, you have a stock 4.1.1 with working root and it will even pass safety net check (enable magisk hide in magisk manager)
My device is BLU Dash X2 ( D110L ) running android 6.0 with Kernel Version 3.18.19.
It's an MTK phone ( MT6580 ).
I managed to port and flash TWRP custom recovery by myself and it's working find. So I decided to flash SuperSU.zip with it. Everything seem to be working perfectly but after the flashing finished and I tried to open SuperSU app a message pop up with text "There is no SU binary Installed, and SuperSU cannot install it. This is a problem. If you just upgraded to android 5.0 you need to manually re-root - consult the relevant forums for your device!".
Please help me find a solution. I tried many version of SuperSU.zip already but the same message still appear. I also tried remove SuperSU app first before re-flash SuperSU.zip. I even tried to perform a clean stock rom flash before flashing latest SuperSU.zip and it's still the same.
I have the same phone, also managed to port TWRP, working fine after edit fstab, but no way I can root this device.
Tried with phh s SuperUser instead supersu, but no avail.
My biggest regret was buy this fone, it works fine but seems impossible to root.
Sorry for late update, you can root this device with magisk, successfully done with magisk v18.00
Super su
Sent from my Samsung Galaxy Note 8 using XDA Labs
Hi,
Till this morning i had rooted Android 6.0.1 (MOB30O) in my Nexus 6. I hadn't updated before because i was lazy, i didn't want to un-root and re-root. But since I've been having battery issues, I decided to give 7.1.1 a try.
I always rooted my device using Wugfresh Nexus Root toolkit... and it always worked great. So, I basically un-rooted my device, using said tookit, and updated it thru OTA. Problem is... I ended up in Android 7.1.1 NGI55D. When I was about to root using NRT, i noticed that last supported version was N6F26U. Also noticed that NRT last version is from September 2016, so i don't know if it is deprecated or what...
So basically, i have a question here: Is it possible to root 7.1.1 NGI55D? If so, can anyone point me to the right direction? I have always used NRT, but i can follow a tutorial and do it manually. Just don't wanna mess things up.
Thanks in advance.
Yes, the N6 is easy to root. Just flash the chosen root method in TWRP recovery. Typically SuperSu, Magisk or phh's - which is used in Magisk.
You don't have to have TWRP installed either if you are set-up with adb drivers and use fastboot. The command is:
fastboot boot <recovery.img>
On a rooted device, you can just use Chainfire's FlashFire app to update then re-root with SuperSu by using the EverRoot option. Or add Magisk zip to the flash queue and re-root that way.
ktmom said:
Yes, the N6 is easy to root. Just flash the chosen root method in TWRP recovery. Typically SuperSu, Magisk or phh's - which is used in Magisk.
You don't have to have TWRP installed either if you are set-up with adb drivers and use fastboot. The command is:
fastboot boot <recovery.img>
On a rooted device, you can just use Chainfire's FlashFire app to update then re-root with SuperSu by using the EverRoot option. Or add Magisk zip to the flash queue and re-root that way.
Click to expand...
Click to collapse
i need unlock bootloader before to root?
Yep.