Nexus 6 + SuperSU + ElementalX = no (full) root? - Nexus 6 Q&A, Help & Troubleshooting

Root checker and AdAway are telling me that I don’t have root. I’ve rooted my phone using super su and other root apps are working ( FireFlash and Clocksync for example). But AdAway and BusyBox are not.
Flash stock system.img (june security update)
Flash stock boot.img (june security update)
Flash supersu
Flash elementalX
No profit ☹
I’m using:
twrp-2.8.6.0-shamu
ElementalX-N6-3.16
Systemless supersu 2.74 ( on I have 2.65 same issue)
Everything was working for me since last year after update to june security update I can't root fully my phone . Any ideas? Please help.

You didn't give much information about the state or history of your device before hand. Stock/Custom ROM? Wiped? Factory reset from stock recovery? For starters, you're using a way outdated version of TWRP. Should be 3.0.2-0. Install the latest recovery and try flashing SU again from recovery. Any errors? Record them. If that doesn't work, flash the stock recovery and do a hard factory reset and try again using fastboot (not FF).

radziop said:
Root checker and AdAway are telling me that I don’t have root. I’ve rooted my phone using super su and other root apps are working ( FireFlash and Clocksync for example). But AdAway and BusyBox are not.
Flash stock system.img (june security update)
Flash stock boot.img (june security update)
Flash supersu
Flash elementalX
No profit ☹
I’m using:
twrp-2.8.6.0-shamu
ElementalX-N6-3.16
Systemless supersu 2.74 ( on I have 2.65 same issue)
Everything was working for me since last year after update to june security update I can't root fully my phone . Any ideas? Please help.
Click to expand...
Click to collapse
flash your kernel first. EDIT: first meaning before supersu. And also try updating to TWRP 3.0 always want to stay up to date on recovery releases.

I have the same set up with root...

radziop said:
Root checker and AdAway are telling me that I don’t have root. I’ve rooted my phone using super su and other root apps are working ( FireFlash and Clocksync for example). But AdAway and BusyBox are not.
Flash stock system.img (june security update)
Flash stock boot.img (june security update)
Flash supersu
Flash elementalX
No profit ☹
I’m using:
twrp-2.8.6.0-shamu
ElementalX-N6-3.16
Systemless supersu 2.74 ( on I have 2.65 same issue)
Everything was working for me since last year after update to june security update I can't root fully my phone . Any ideas? Please help.
Click to expand...
Click to collapse
I have the exact same issue. The issue is we can't seem to remount the system partition as read/write anymore.
The problem is that for the life of me I can't get it to remount using any method. Someone else has the same issue also https://www.reddit.com/r/nexus6/comments/4nvgfv/can_no_longer_modify_system_after_june_ota_even/
Any help would be appreciated.

Related

Can't attain Root on Moto X 2014 (decompressing ramdisk failure aborting)

I'm running CM 13 nightly with TWRP recovery, trying to get root access.
When I enable root through developer options in the rom, it doesn't work, according to root check.
When I flash Super SU Beta 2.68 through recovery is says partway through installation it says "decompressing ramdisk; failure, aborting"
Flashing v. 2.46 causes a bootloop.
Anyone have any ideas why I can't get root?
Thanks!
Deivore said:
I'm running CM 13 nightly with TWRP recovery, trying to get root access.
When I enable root through developer options in the rom, it doesn't work, according to root check.
When I flash Super SU Beta 2.68 through recovery is says partway through installation it says "decompressing ramdisk; failure, aborting"
Flashing v. 2.46 causes a bootloop.
Anyone have any ideas why I can't get root?
Thanks!
Click to expand...
Click to collapse
Never flash supersu on CM! You should reinstall CM just incase flashing supersu messed something up.
You should never flash supersu on a custom rom, they usually come pre-rooted.
Sent from my XT1095 using Tapatalk

OTA Updates and Magisk

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/

Super su Root Undetected

I have just updated supersu through the play store and am now getting "Root Undetected " when I open the app. My phone is a Galaxy gt i9305 running a stock based TouchWiz 4.4.4 rom any suggestions please?
So I had to restore a backup which uses the previous SuperSu 2.79 and all is well again. Looking at the reviews on Google play store I'm not the only one having problems with version 2.80. Will this problem be getting sorted anytime soon because this is an important app for me and my confidence in using it is draining fast.
There is a version 2.81 on Google playstore right now (although it's still saying v2.80) which works fine again for me.
Same deal here. Pretty upsetting, I don't have a backup handy. Does anyone have a link to the 2.79 version that can be flashed in TWRP? If I find it first I'll post it here for others' convenience.
Yes I had same problem just 10 min ago
But I downloaded the zip of new version reflashed it ,works perfect
Old (working) version SuperSU Download:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
Just flashed in TWRP and all is well
devytrip said:
Old (working) version SuperSU Download:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
Just flashed in TWRP and all is well
Click to expand...
Click to collapse
This one is not working for me! Just like the latest 2.8! I flash it on four devices! one fails the other three claim it was successful but there is NO SuperSu on any of the devices that I tried flashing it on with TWRP! I cannot give apps root access and it is like a device that is not rooted that was rooted before!
Anything else to try??
devytrip said:
Old (working) version SuperSU Download:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
Just flashed in TWRP and all is well
Click to expand...
Click to collapse
I installed this version. It's not working.
Thing is you install 2.79 with TWRp, after reboot. I used Root Checker Basic and Root Checker, they say no root. If you try to open SuperSu app, it will update to version 2.8. Same problem no root.
I am using Asus Zenfone ze552kl
Having the same problem on my cm14.1.....is there a solution?
Same here bro. I tried all supersu zip version 2.67 to 2.82 sr5. Version 2.82 says root undetected and below this version says supersu can't install su binary. I tried to install su binary but it says no su binary.
jisanhoque said:
Same here bro. I tried all supersu zip version 2.67 to 2.82 sr5. Version 2.82 says root undetected and below this version says supersu can't install su binary. I tried to install su binary but it says no su binary.
Click to expand...
Click to collapse
Same with me I try every version but sill not working

[SOLVED] Samsung A5 2017 (A520F) Dual Sim - How to Root Nougat?

I flashed the Russian Firmware for my A5 (2017), but the Magisk 13.3 root method didnt work.
So far, I have failed in rooting Nougat with the following methods:
1. Magisk 13.3
2. CF Root although this is for Nougat. The phone goes into bootloop.
Currently, out of options as not too many options/info available for this phone.
Any definite way of rooting on this device?
[EDIT:]
SOLVED:
Flashed this version of SuperSU through TWRP and it worked!
Once installed SuperSU will ask KNOX detected, try to disable: Press OK.
Going to test it out & see if anything is off about it.
EDIT 2:
False Alarm. SuperSU flashed but does not have Root access as apss dont have SU Binary access. This is getting frustrating.
Any other way to root?
Keith0222 said:
I flashed the Russian Firmware for my A5 (2017), but the Magisk 13.3 root method didnt work.
So far, I have failed in rooting Nougat with the following methods:
1. Magisk 13.3
2. CF Root although this is for Nougat. The phone goes into bootloop.
Currently, out of options as not too many options/info available for this phone.
Any definite way of rooting on this device?
[EDIT:]
SOLVED:
Flashed this version of SuperSU through TWRP and it worked!
Once installed SuperSU will ask KNOX detected, try to disable: Press OK.
Going to test it out & see if anything is off about it.
EDIT 2:
False Alarm. SuperSU flashed but does not have Root access as apss dont have SU Binary access. This is getting frustrating.
Any other way to root?
Click to expand...
Click to collapse
For android 7. Extract boot.img archive. Install it from Twrp reboot then install magisk
say55 said:
For android 7. Extract boot.img archive. Install it from Twrp reboot then install magisk
Click to expand...
Click to collapse
Hey! Thanks for the reply. So, I just Flash this in TWRP like all Zip's and then Flash Magisk?
EDIT: It seems the boot image is something I have already tried, except I flashed SuperSU after, instead of Magisk. If you don't mind, could you go through this post, as this is the only problem remaining.
Samsung A5 2017 [A520F} Root issue resolved.
Gonna leave the steps for future reference if anyone needs it:
Firmware, Magisk & dm_verity all linked in my original post.
1. Install Samsung Nougat 7.0 (Russian Version in this case)
2. Flash TWRP
3. Try to flash dm-verity through TWRP
3. If it doesn't work go to Wipe > data > Change System Files > FAT & F4 wipe to change
3. Flash dm-verity again. The .zip should flash successfully this time.
4. Flsh Magisk 13.3. It will flash.
and you are rooted!
Keith0222 said:
Samsung A5 2017 [A520F} Root issue resolved.
Gonna leave the steps for future reference if anyone needs it:
Firmware, Magisk & dm_verity all linked in my original post.
1. Install Samsung Nougat 7.0 (Russian Version in this case)
2. Flash TWRP
3. Try to flash dm-verity through TWRP
3. If it doesn't work go to Wipe > data > Change System Files > FAT & F4 wipe to change
3. Flash dm-verity again. The .zip should flash successfully this time.
4. Flsh Magisk 13.3. It will flash.
and you are rooted!
Click to expand...
Click to collapse
Hi, will smart switch still work after rooting?

Nexus 6 Root - Android 7.1.1 (NGI55D, Sep 2017)

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.

Categories

Resources