Related
Good morning...
I've had my S6 with 6.0.1 "CDP2" "rooted and with twrp 3 for about one week.
However late last nite I noticed I lost root. "There is no SU binary installed and Supersu cannot install it".
Recovery was updated and default was installed..
I tried to root again, successfully "stated by ODIN" re-boots and goes through the phase as establishing TWRP, then default recovery is re-installed...
Any ideas ?
Thanks..
I have run into the exact same issue. Lost root with latest security update yesterday and can't seem to get it back
I was able to regain root. My mistake was trying to flash an older SuperSU. When I flashed the 2.71 version everything went fine. I did loose root after the OTA just needed to flash the right SuperSU to regain it.
Sent from my SM-G920P using XDA-Developers mobile app
I also need to flash new Super SU. But my recovery is not TWRP. It's Android recovery and has 3 options for Install update : Through ADB, External storage or Cashe. Which option to choose?
IronMaidenBG said:
I also need to flash new Super SU. But my recovery is not TWRP. It's Android recovery and has 3 options for Install update : Through ADB, External storage or Cashe. Which option to choose?
Click to expand...
Click to collapse
Flash the latest CF-Auto root, then flash TWRP. CF-AUTO root will knock out the kernels protections and allow you to flash TWRP.
kbless60 said:
I was able to regain root. My mistake was trying to flash an older SuperSU. When I flashed the 2.71 version everything went fine. I did loose root after the OTA just needed to flash the right SuperSU to regain it.
Sent from my SM-G920P using XDA-Developers mobile app
Click to expand...
Click to collapse
Same thing happened to me. I had an OTA security update, lost root, but reflashed 2.71 SuperSu using TWRP to regain root.
Tutorial Available
There is a tutorial, including links, available here: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Specific instructions for rooting after PD3 are here: http://forum.xda-developers.com/showpost.php?p=66978384&postcount=41
Hello all,
Yesterday I did what many did and upgraded to Nougat as soon as it dropped, using the "sign up for Android beta" method. I came from a bootloader unlocked, rooted Nexus 5x running the latest version of 6.0.1 with a few basic mods - AdAway, Viper4Android, ElementalX Kernel w/ profile manager, Cf.Lumen and Greenify.
In upgrading to Android 7.0, I first flashed the system, vendor, boot and recovery image from the most recent version of 6.0.1 to revert completely to unrooted stock before taking the OTA.
After reading about this new method of systemless root that also seems to allow Android Pay to work, I'm trying to wrap my head around it before trying, and wanted some of the wise minds of XDA to confirm my procedure.
Current Status-
Device: Nexus 5x
Build: Android 7.0 NRD90M
Unlock Status: Bootloader Unlocked
Root Status: Unrooted
Boot.img and Recovery.img: Stock
Procedure:
1. Download latest TWRP, boot device into fastboot mode, and "fastboot flash recovery [TWRP file]"
2. Navigate to TWRP Recovery, locate phh root .zip (already downloaded to device), Magisk mod and ElementalX kernel, flash these.
3. Once booted, follow directions in the Magisk thread to mount the desired mods (AdAway, Viper4Android, etc.) while still passing SafetyNet check, and Android Pay will continue to work.
Also, if I understand correctly, future system updates will be possible using FlashFire and the OTA .zip while maintaining root status and the modifications, since \system is not modified using this method.
Any confirmation/feedback is welcome!
Thanks,
Moonboots
Moonboots said:
Hello all,
Yesterday I did what many did and upgraded to Nougat as soon as it dropped, using the "sign up for Android beta" method. I came from a bootloader unlocked, rooted Nexus 5x running the latest version of 6.0.1 with a few basic mods - AdAway, Viper4Android, ElementalX Kernel w/ profile manager, Cf.Lumen and Greenify.
In upgrading to Android 7.0, I first flashed the system, vendor, boot and recovery image from the most recent version of 6.0.1 to revert completely to unrooted stock before taking the OTA.
After reading about this new method of systemless root that also seems to allow Android Pay to work, I'm trying to wrap my head around it before trying, and wanted some of the wise minds of XDA to confirm my procedure.
Current Status-
Device: Nexus 5x
Build: Android 7.0 NRD90M
Unlock Status: Bootloader Unlocked
Root Status: Unrooted
Boot.img and Recovery.img: Stock
Procedure:
1. Download latest TWRP, boot device into fastboot mode, and "fastboot flash recovery [TWRP file]"
2. Navigate to TWRP Recovery, locate phh root .zip (already downloaded to device), Magisk mod and ElementalX kernel, flash these.
3. Once booted, follow directions in the Magisk thread to mount the desired mods (AdAway, Viper4Android, etc.) while still passing SafetyNet check, and Android Pay will continue to work.
Also, if I understand correctly, future system updates will be possible using FlashFire and the OTA .zip while maintaining root status and the modifications, since \system is not modified using this method.
Any confirmation/feedback is welcome!
Thanks,
Moonboots
Click to expand...
Click to collapse
Howdy sir! I'm still learning myself so I can't give you a great answer, but it's been a few weeks so I thought maybe you already gave this a shot? I'm looking to follow about the same process soon. I'm currently bootloader unlocked with TWRP loaded on Nougat (NRD90S on 5X).
How'd this go for ya?
Thanks!
VZW Pixel on the way. I have ADB & fastboot ready through Android Studio SDK. dePixel8 downloaded. Just want to check the best order of operations here (spans multiple things):
1. Run dePixel8 to unlock bootloader
2. OTA update to 7.1.1
3. Boot to TWRP, install recovery
4. Boot-to-root
5. Flash ElementalX kernel, install kernel manager (root ver.)
5.5. Full unroot SuperSU?
6. Delete fstab.marlin in TWRP
7. Flash SuperSU 2.79 stable, systemless
8. Patch libandroid files, flash suhide, add apps to blacklist
Upon this, I should have my Pixel XL running Android 7.1.1, TWRP recovery, ElementalX kernel, Root, with SafetyNet fooled and Android Pay working... right? Should I do anything in a different order/way?
If I stop after step 5.5 I won't have root, but will have AP working I assume? Is 5.5 necessary if I do the remaining steps?
JU57US said:
VZW Pixel on the way. I have ADB & fastboot ready through Android Studio SDK. dePixel8 downloaded. Just want to check the best order of operations here (spans multiple things):
1. Run dePixel8 to unlock bootloader
2. OTA update to 7.1.1
3. Boot to TWRP, install recovery
4. Boot-to-root
5. Flash ElementalX kernel, install kernel manager (root ver.)
5.5. Full unroot SuperSU?
6. Delete fstab.marlin in TWRP
7. Flash SuperSU 2.79 stable, systemless
8. Patch libandroid files, flash suhide, add apps to blacklist
Upon this, I should have my Pixel XL running Android 7.1.1, TWRP recovery, ElementalX kernel, Root, with SafetyNet fooled and Android Pay working... right? Should I do anything in a different order/way?
Click to expand...
Click to collapse
3 Make sure it is TWRP RC1
4 No, boot to root is dead after 7.1. Use 2.79 SR3 for all of this. And skip 4 anyway, in unneeded.
5.5 Here is where you flash 2.79 SR3. To be clear, you install it via TWRP.
6 Unneeded with the 2.79 SR3
And I doubt suhide will hide root, my understanding is that it currently does not. But I don follow it very closely.1
My understanding was that suhide works with the libandroid patches, but only with 2.79 stable, and not RC1+
Also, question... if flashing ElementalX isn't it recommended to have root before flashing, or does it not really matter?
JU57US said:
VZW Pixel on the way. I have ADB & fastboot ready through Android Studio SDK. dePixel8 downloaded. Just want to check the best order of operations here (spans multiple things):
1. Run dePixel8 to unlock bootloader
2. OTA update to 7.1.1
3. Boot to TWRP, install recovery
4. Boot-to-root
5. Flash ElementalX kernel, install kernel manager (root ver.)
5.5. Full unroot SuperSU?
6. Delete fstab.marlin in TWRP
7. Flash SuperSU 2.79 stable, systemless
8. Patch libandroid files, flash suhide, add apps to blacklist
Upon this, I should have my Pixel XL running Android 7.1.1, TWRP recovery, ElementalX kernel, Root, with SafetyNet fooled and Android Pay working... right? Should I do anything in a different order/way?
Click to expand...
Click to collapse
Make sure before you power on you take the SIM card out. Then during the setup SKIP connecting to Wi-Fi. Then once you're through the setup unlock with dePixel8.
Take OTA update
Fastboot boot twrp RC 1 IMG
Install Twrp RC 1 zip from within twrp
Boot phone up then reboot to recovery
Flash SU 2.79 SR 3
Flash kernel if you want
Reboot
Don't use any other versions of twrp or SU. Also make sure your platform tools are completely up to date. Google also just released a separate download of them so grab those and you know for sure you're up to date
JU57US said:
My understanding was that suhide works with the libandroid patches, but only with 2.79 stable, and not RC1+
Also, question... if flashing ElementalX isn't it recommended to have root before flashing, or does it not really matter?
Click to expand...
Click to collapse
I don't believe SUHide works even with the 2 libandroid replacements. That's what I have. I think I'll have better luck with RootSwitch. I'm working to come up with something similar to RootSwitch.
quangtran1 said:
I don't believe SUHide works even with the 2 libandroid replacements. That's what I have. I think I'll have better luck with RootSwitch. I'm working to come up with something similar to RootSwitch.
Click to expand...
Click to collapse
There's a report in @Fenny's thread, here, about the files working on NMF26V stock for suhide.
JU57US said:
There's a report in @Fenny's thread, here, about the files working on NMF26V stock for suhide.
Click to expand...
Click to collapse
I know, I've been following that and one off of that. I use fenny's instructions. However, those conversations gave me some ideas to attack this.
@rbox Hey I keep getting notices that Su binary needs updating. Should I flash latest update via recovery?
I thought i saw mention of a fix for this but I can't seem to locate it again.
nujackk said:
@rbox Hey I keep getting notices that Su binary needs updating. Should I flash latest update via recovery?
I thought i saw mention of a fix for this but I can't seem to locate it again.
Click to expand...
Click to collapse
Just dismiss the notification.
rbox said:
Just dismiss the notification.
Click to expand...
Click to collapse
I've been doing that, just wondering if i can/should update ? Will It cause problems if i flash latest version?
got the same idea: just flash super su 2.79 sr3 should work?
That's what I'm thinking, just wanting rbox to confirm it shouldn't hose anything. I know some roms on phones don't work with latest versions. And since he is using such an old version, I'm think that might be the case here
Hmm i think i will try it next time. Create a backup and flash supersu.
Spillunke said:
Hmm i think i will try it next time. Create a backup and flash supersu.
Click to expand...
Click to collapse
flashing/updating SuperSU is not working and you will lose root
Since SuperSU is now a system program. I think doing fresh installs are the most secure way to test newer versions.
What I was planning to test before the XPosed APK fix came out was to have the latest PreRooted ROM & manually change the inners of the SuperSU folder to the latest. Not just the APK but the binaries or what ever is included. And then flash that modded PreRooted Rom.
XPosed APK fix: http://forum.xda-developers.com/fire-tv/themes-apps/protip-how-to-supersu-xposed-app-t3552590/page1
I asked @rbox about it & he said it should be fine. At worst I think you will end up with a non-rooted FireOS 5 install but as long as it doesn't update (make sure you are only messing with the latest FW version) & you can still get into TWRP. Then you can flash the latest original PreRooted ROM to get back your root.
I might still do some testing regarding this in the next few days. Might try the latest beta, final & a few other versions since v2.46.
Y314K said:
Since SuperSU is now a system program. I think doing fresh installs are the most secure way to test newer versions.
What I was planning to test before the XPosed APK fix came out was to have the latest PreRooted ROM & manually change the inners of the SuperSU folder to the latest. Not just the APK but the binaries or what ever is included. And then flash that modded PreRooted Rom.
XPosed APK fix: http://forum.xda-developers.com/fire-tv/themes-apps/protip-how-to-supersu-xposed-app-t3552590/page1
I asked @rbox about it & he said it should be fine. At worst I think you will end up with a non-rooted FireOS 5 install but as long as it doesn't update (make sure you are only messing with the latest FW version) & you can still get into TWRP. Then you can flash the latest original PreRooted ROM to get back your root.
I might still do some testing regarding this in the next few days. Might try the latest beta, final & a few other versions since v2.46.
Click to expand...
Click to collapse
Good luck! I always ended up with non-root after trying to replace/update SuperSU on my FireTVs
rainman74 said:
Good luck! I always ended up with non-root after trying to replace/update SuperSU on my FireTVs
Click to expand...
Click to collapse
What FW where you on & what method did u try using ?
- manual clean up of apk installation first (system/apps & /data/app, but left /system/xbin/su)
- adb install eu.chainfire.supersu.vX.xx.apk (1.94, 1.97, 2.00, 2.4x,...)
- TWRP flash of UPDATE-SuperSU-vX.xx.zip (1.94, 1.97, 2.00, 2.4x,...)
- ...
rainman74 said:
- manual clean up of apk installation first (system/apps & /data/app, but left /system/xbin/su)
- adb install eu.chainfire.supersu.vX.xx.apk (1.94, 1.97, 2.00, 2.4x,...)
- TWRP flash of UPDATE-SuperSU-vX.xx.zip (1.94, 1.97, 2.00, 2.4x,...)
- ...
Click to expand...
Click to collapse
Although it is much more of a pain to do fresh installs. I think when dealing with root it should be more stable to mess with it that way.
One can also do the build.prop mod to stop updates if one wants to test older FW versions.
Y314K said:
Since SuperSU is now a system program. I think doing fresh installs are the most secure way to test newer versions.
What I was planning to test before the XPosed APK fix came out was to have the latest PreRooted ROM & manually change the inners of the SuperSU folder to the latest. Not just the APK but the binaries or what ever is included. And then flash that modded PreRooted Rom.
XPosed APK fix: http://forum.xda-developers.com/fire-tv/themes-apps/protip-how-to-supersu-xposed-app-t3552590/page1
I asked @rbox about it & he said it should be fine. At worst I think you will end up with a non-rooted FireOS 5 install but as long as it doesn't update (make sure you are only messing with the latest FW version) & you can still get into TWRP. Then you can flash the latest original PreRooted ROM to get back your root.
I might still do some testing regarding this in the next few days. Might try the latest beta, final & a few other versions since v2.46.
Click to expand...
Click to collapse
First thanks for the link to the xposed fix:good: And now that you mention it I don't know why i didn't think of that sooner, should be relatively easy to just replace the files in the zip with 7zip DUH. Only problem is I have everything all setup perfect.
I'm a little lost on Root for the Pixel XL. I am currently running unlocked with Screw'd ROM - 3.1.2-****ery-20170712-1454. This is a BETA, but has been running really smooth for the last 2 days.
Security Patch Level - July 5, 2017
Vendor - NJH47D
Last time I tried to apply root while running PureNexus the phone continued to boot loop and I had to eventually flashall.bat and start over.
1. What version of SuperSU should I be flashing? The latest and newest or is there other versions that work better?
2. What are the correct steps? Is wipe cache/dalvik necessary before? Do I need to install anything on the phone beforehand?
Boot to TWRP, Flash SuperSU, Reboot? Easy as that?
I see this version being talked about a lot - SR3-SuperSU-v2.79-SR320170114223742.zip, but it isn't the latest available that I can see. The SuperSU thread states to install the latest version and using google brings me to many versions of SuperSU.
Lastly, after rooting will apps like SnapChat work? If not how to you bypass this?
So I just found some information after searching more. Some of it is dated. I currently have twrp-pixel-installer-marlin-3.1.0-0RC2.zip version for TWRP installed.
Is RC1 needed for root, and with what SuperSU version. Or which combination of RC2 and SuperSU work together?
jws86 said:
So I just found some information after searching more. Some of it is dated. I currently have twrp-pixel-installer-marlin-3.1.0-0RC2.zip version for TWRP installed.
Is RC1 needed for root, and with what SuperSU version. Or which combination of RC2 and SuperSU work together?
Click to expand...
Click to collapse
When I was rooted I initially was using RC1, I think my supersu was V2.8? And no Snapchat, Pokemon go, and Android pay, etc, will not work. So a little work around for Snapchat, you need to log in first then flash supersu, or just go with magisk and enable magisk hide to make life easier.
sakumaxp said:
When I was rooted I initially was using RC1, I think my supersu was V2.8? And no Snapchat, Pokemon go, and Android pay, etc, will not work. So a little work around for Snapchat, you need to log in first then flash supersu, or just go with magisk and enable magisk hide to make life easier.
Click to expand...
Click to collapse
Is there a guide to Root with Magisk somewhere floating around?
jws86 said:
Is there a guide to Root with Magisk somewhere floating around?
Click to expand...
Click to collapse
I believe it's the same as when you flash supersu, don't quote me on that
sakumaxp said:
I believe it's the same as when you flash supersu, don't quote me on that
Click to expand...
Click to collapse
Yeah I found the guide. It seems I need to flash stock image first before. So Magisk gives you the ability to root first, then download apps such as snapchat and still login if you use magisk hide?
jws86 said:
Yeah I found the guide. It seems I need to flash stock image first before. So Magisk gives you the ability to root first, then download apps such as snapchat and still login if you use magisk hide?
Click to expand...
Click to collapse
Correct, downloading isn't a problem, but it'll just prevent you from logging in since supersu, trips safetynet
sakumaxp said:
Correct, downloading isn't a problem, but it'll just prevent you from logging in since supersu, trips safetynet
Click to expand...
Click to collapse
I read through this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
Seems pretty straightforward, however currently I have a ROM installed I'm really liking. To do this I would have to flash back to stock image, then go through the root process. My question would be after rooting, if I went to flash Screw'd again, doesn't it wipe everything and I would lose root again, then just have to flash it after the ROM?
jws86 said:
I read through this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
Seems pretty straightforward, however currently I have a ROM installed I'm really liking. To do this I would have to flash back to stock image, then go through the root process. My question would be after rooting, if I went to flash Screw'd again, doesn't it wipe everything and I would lose root again, then just have to flash it after the ROM?
Click to expand...
Click to collapse
Myself I've never been on screwd before, I would assume so, but in my experience the pixel XL is more complicated than my previous phones
If you just want root you shouldn't need to flash the stock image again. You would need to do that if you wanted to flash a custom kernel but not for root. You need to download the modified version of Magisk for the Pixel XL. The official version doesn't work on the Pixels. I'm not currently rooted as I went back to stock but I was using Magisk. At that time the latest version wasn't stable but it might be fixed now. You need to boot into fastboot TWRP, flash the Magisk zip, flash the TWRP zip and then boot up. After you are booted up you install the Magisk Manager app. The tricky thing is installing the right version of Magisk Manager that works properly with the unofficial build of Magisk that you are using. You can get more information in the Resurrection Remix rom thread which for some reason is the official place where the modified version of Magisk is hosted if you can't find good info about which combination of unofficial Magisk and Magisk Manager you should be using. Also when I used Magisk you needed to enable core only mode for it to pass Safety Net but that may no longer be the case. You should be able to find the most up to date info either in the thread you cited or the RR rom thread. Just remember that official builds of Magisk do not work on the Pixel. You need to stick with one of the unofficial builds.
jhs39 said:
If you just want root you shouldn't need to flash the stock image again. You would need to do that if you wanted to flash a custom kernel but not for root. You need to download the modified version of Magisk for the Pixel XL. The official version doesn't work on the Pixels. I'm not currently rooted as I went back to stock but I was using Magisk. At that time the latest version wasn't stable but it might be fixed now. You need to boot into fastboot TWRP, flash the Magisk zip, flash the TWRP zip and then boot up. After you are booted up you install the Magisk Manager app. The tricky thing is installing the right version of Magisk Manager that works properly with the unofficial build of Magisk that you are using. You can get more information in the Resurrection Remix rom thread which for some reason is the official place where the modified version of Magisk is hosted if you can't find good info about which combination of unofficial Magisk and Magisk Manager you should be using. Also when I used Magisk you needed to enable core only mode for it to pass Safety Net but that may no longer be the case. You should be able to find the most up to date info either in the thread you cited or the RR rom thread. Just remember that official builds of Magisk do not work on the Pixel. You need to stick with one of the unofficial builds.
Click to expand...
Click to collapse
I think I got which versions of magisk and magisk manager I need to use from the other thread I had posted earlier. This helps to clear some things up for me though. I have both the .apk and the zip on my phone now. Getting a bit of a charge and I guess I'll go ahead and try it.
It worked, I'm officially rooted .Thanks for the help!
jws86 said:
It worked, I'm officially rooted .Thanks for the help!
Click to expand...
Click to collapse
Cool.