Database Users

Root Issues after installing Cataclysm

Hey guys,
I unlocked the bootloader and rooted my phone using the toolkit and all was well. I installed the Cataclysm ROM and everything was too. However, one day randomly I checked and Super SU and BusyBox was missing and Root checker said my device isn't rooted. However, my phone does boot into recovery (TWRP) and it IS running Cataclysm ROM. I downloaded Super SU from Playstore and it says "There is no SU binary installed and Super SU cannot install it". Some forums for other devices say just flash the latest version of Super SU but the marshmallow pages say go back to stock or something, I don't get it since I'm a Noob. If someone could tell me what I need to do to fix this the right way I would be really grateful. Thanks in advance. :angel:

holydevil27 said:
Hey guys,
I unlocked the bootloader and rooted my phone using the toolkit and all was well. I installed the Cataclysm ROM and everything was too. However, one day randomly I checked and Super SU and BusyBox was missing and Root checker said my device isn't rooted. However, my phone does boot into recovery (TWRP) and it IS running Cataclysm ROM. I downloaded Super SU from Playstore and it says "There is no SU binary installed and Super SU cannot install it". Some forums for other devices say just flash the latest version of Super SU but the marshmallow pages say go back to stock or something, I don't get it since I'm a Noob. If someone could tell me what I need to do to fix this the right way I would be really grateful. Thanks in advance. :angel:
Click to expand...
Click to collapse
It really depends on what you're trying to do. If you flash the older beta 2.52 super su, for the 'old style' system root, you should be able to flash the zip and be well on your way. You need to go back to the stock and follow the flash instructions if you're going to use the newer / experimental systemless root. If you don't know what you're doing exactly, I'd recommend the old system root, but flashing super su 2.52.

It sounds pretty messed up for Super SU just to disappear and root access to just be gone. Although like teh roxxorz said it depends on what type of root you are doing. I think system root is much easier and cleaner personally. If I was you I would probably flash back to stock, flash TWRP, install SuperSU 2.65. Then flash back which ever ROM you want. Since you are having issues with root I would not restore your ROM from a back up either, just start fresh.

teh roxxorz said:
It really depends on what you're trying to do. If you flash the older beta 2.52 super su, for the 'old style' system root, you should be able to flash the zip and be well on your way. You need to go back to the stock and follow the flash instructions if you're going to use the newer / experimental systemless root. If you don't know what you're doing exactly, I'd recommend the old system root, but flashing super su 2.52.
Click to expand...
Click to collapse
If I want to do the old system root, do I just download Super SU and flash it with TWRP? Or do I format my phone and do it? Or do I have to flash stock firmware first?

AndroidPurity said:
It sounds pretty messed up for Super SU just to disappear and root access to just be gone. Although like teh roxxorz said it depends on what type of root you are doing. I think system root is much easier and cleaner personally. If I was you I would probably flash back to stock, flash TWRP, install SuperSU 2.65. Then flash back which ever ROM you want. Since you are having issues with root I would not restore your ROM from a back up either, just start fresh.
Click to expand...
Click to collapse
Can you guide me as to how to flash back to stock? A link would be great, and I apologize for the lack of knowledge, the last rooted Android phone I had was Samsung s3! Things have really changed since then xD

holydevil27 said:
Can you guide me as to how to flash back to stock? A link would be great, and I apologize for the lack of knowledge, the last rooted Android phone I had was Samsung s3! Things have really changed since then xD
Click to expand...
Click to collapse
No worries man. Even tough I been rooting phones and playing around for over a year I still have lots to learn myself. What helped me the most when I wanted to know how to do something was watching a you tube tutorial on it. Here is a good detailed tutorial how to flash back to stock right here.
Once you do that, to do a systemless root, you can watch this short little video tutorial right here. The newest SuperSU 2.65 you can find on Chainfire's thread at the bottom of this page right here.
If you have any questions going through either of those 2 video tutorials feel free to ask.

holydevil27 said:
Can you guide me as to how to flash back to stock? A link would be great, and I apologize for the lack of knowledge, the last rooted Android phone I had was Samsung s3! Things have really changed since then xD
Click to expand...
Click to collapse
No need to be sorry; we all have to start somewhere..
AndroidPurity said:
No worries man. Even tough I been rooting phones and playing around for over a year I still have lots to learn myself. What helped me the most when I wanted to know how to do something was watching a you tube tutorial on it. Here is a good detailed tutorial how to flash back to stock right here.
Once you do that, to do a systemless root, you can watch this short little video tutorial right here. The newest SuperSU 2.65 you can find on Chainfire's thread at the bottom of this page right here.
If you have any questions going through either of those 2 video tutorials feel free to ask.
Click to expand...
Click to collapse
Good look. Though I still think the system root might be a good pace, and it's 100% working; still some quirks with certain root apps on systemless root. SuperSu 2.52
---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------
holydevil27 said:
If I want to do the old system root, do I just download Super SU and flash it with TWRP? Or do I format my phone and do it? Or do I have to flash stock firmware first?
Click to expand...
Click to collapse
Correct, you would just download the zip and flash in TWRP; I linked it in an above post.

teh roxxorz said:
Good look. Though I still think the system root might be a good pace, and it's 100% working; still some quirks with certain root apps on systemless root. SuperSu 2.52
Click to expand...
Click to collapse
Thanks! Just curious, what are a couple of the most known/popular root apps that don't work with system less root? I haven't found a thread yet on that. Also on the other hand Android pay don't work with the 'old' system root method right? And I think wallet no longer works with it too, correct?

AndroidPurity said:
Thanks! Just curious, what are a couple of the most known/popular root apps that don't work with system less root? I haven't found a thread yet on that. Also on the other hand Android pay don't work with the 'old' system root method right? And I think wallet no longer works with it too, correct?
Click to expand...
Click to collapse
No problem. And the one I know that comes to mind that doesn't work with systemless root is Es File Explorer - though any root app where it is hardcoded tot he path for supersu won't work, additionally, apparently some kernels won't work with systemless root, though I haven't seen it on our end.
Wallet still works with the system root, but as you said, Android Pay does not - though the Chroma ROM apparently has it working, but I've yet to use the ROM, as it isn't a deal breaker for me.

teh roxxorz said:
No need to be sorry; we all have to start somewhere..
Good look. Though I still think the system root might be a good pace, and it's 100% working; still some quirks with certain root apps on systemless root. SuperSu 2.52
---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------
Correct, you would just download the zip and flash in TWRP; I linked it in an above post.
Click to expand...
Click to collapse
Thanks guys,
I just went into TWRP and flashed 2.64 Super SU (since that's the one I got with the tool kit and what I had installed before) and Root came back! I hope it stays! Thanks again folks!

My 6P is still on 6.0.0 (Oct. build) because instructions not clear. Question about i

It's about time I finally do this. I have 1 question though.
I'm currently on SU2.52, 6.0.0 and I'm updating to SU 2.66 6.0.1. Chainfire mentions that with the newer systemless root we can install it as traditional root instead. I'm just not clear on how and what to do with what he says below...
His full instructions are:
"Notes on 2.62+
A poor man's overlay is used on /system/xbin. We are creating a copy of /system/xbin in /su/xbin_bind, adding a symlink to /su/bin/su there, then mounting the entire thing on top of the original /system/xbin. This is likely to fix some compatibility issues with some apps, without actually modifying /system. Removing /su/xbin_bind and rebooting will disable this feature, or "echo BINDSYSTEMXBIN=false>>/data/.supersu" in recovery root shell before a SuperSU ZIP flash.
If you have one of those devices that refuse to remount system r/w in Android such as the Nexus 6P, but you do want to do this, "echo FSTABSYSTEMRW=true>>/data/.supersu" in recovery root shell before a SuperSU ZIP flash will patch the boot image in such a way that remounting will work. This feature itself breaks OTA compatibility, regardless of if you end up writing to /system or not.
Both of these features are likely temporary.
Notes on 2.64+
There have been a lot of changes to the ZIP installer. Hopefully they won't break a lot of installs. If 2.64 works well, it is likely to be promoted to the "main beta" in place of 2.52, and the How-To SU document will be updated with the relevant information.
A major change in setup is that the ZIP installer will try to detect 6.0 firmwares that can be rooted without doing a systemless install. In other words, a root that modifies only /system, but not the boot image. If this is possible, the installer will install into /system (unless you override via "echo SYSTEMLESS=true>>/data/.supersu").
This may catch (a) firmwares that allow sepolicy reloading from /data but have a locked bootloader and (b) custom firmwares setup to handle this. Regarding the latter, while it is not as clean as systemless, those running custom firmwares are more likely to want to modify /system anyway, it is less likely to mess with updates to those firmwares, and it prevents the necessity of reflashing the ZIP after each kernel switch. Of course, the kernel's SELinux policies must support this! See this thread for details for devs.
Click to expand...
Click to collapse
1.) Can someone rephrase what he said and make it sound a little simpler?
2.) Do I do both of these or one? (I'm flashing 2.66).
echo FSTABSYSTEMRW=true>>/data/.supersu or echo BINDSYSTEMXBIN=false>>/data/.supersu do both or 1?
3.) Should I override this with 6P? "The (2.64+) zip installer will try to detect a root that modifies only /system, but not the boot image. If this is possible, the installer will install into /system (unless you override via "echo SYSTEMLESS=true>>/data/.supersu")."
I have a ton of apps that rely on root so I want to go with the best method that will give me the least compatibility problems. I don't care for android Pay.

Bump please

are you basically saying you want traditional root using 2.66?
Sent from my Nexus 6P using Tapatalk
---------- Post added at 06:02 PM ---------- Previous post was at 06:01 PM ----------
toknitup420 said:
are you basically saying you want traditional root using 2.66?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you want traditional root flash a modified boot.img that will allow traditional root to work. Then flash SuperSU 2.66 and it will automatically install as traditional root.
Sent from my Nexus 6P using Tapatalk

toknitup420 said:
are you basically saying you want traditional root using 2.66?
Sent from my Nexus 6P using Tapatalk
---------- Post added at 06:02 PM ---------- Previous post was at 06:01 PM ----------
If you want traditional root flash a modified boot.img that will allow traditional root to work. Then flash SuperSU 2.66 and it will automatically install as traditional root.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Basically I'm trying to decipher what he is saying in his notes I've quoted. There are 3 things he mentions that I could do if I wanted to and I'm asking what those 3 things are (question 2&3 in my op).
I shouldn't need a modified boot for 2.66 and would prefer not to.

JustRootDontCustomRomIt said:
Basically I'm trying to decipher what he is saying in his notes I've quoted. There are 3 things he mentions that I could do if I wanted to and I'm asking what those 3 things are (question 2&3 in my op).
I shouldn't need a modified boot for 2.66 and would prefer not to.
Click to expand...
Click to collapse
You don't need one if you're using systemless root. If you want traditional root then you need modified boot.img or custom kernel.
Sent from my Nexus 6P using Tapatalk

toknitup420 said:
You don't need one if you're using systemless root. If you want traditional root then you need modified boot.img or custom kernel.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I'm not sure if that's right. I think systemless can be installed into system permanently without boot. The systemless versions patch the boot automatically...

JustRootDontCustomRomIt said:
I'm not sure if that's right. I think systemless can be installed into system permanently without boot. The systemless versions patch the boot automatically...
Click to expand...
Click to collapse
See the part where he mentions the kernel(boot) se policy, this is what you have to modify for root. So yes. It does require a modified boot to install to system. Which is exactly what is explained in the last 2 paragraphs of that quote. However you can override that and force a systemless install if you desire. See the echo command at the end of the 2nd to last paragraph in quote.
JustRootDontCustomRomIt said:
I'm not sure if that's right. I think systemless can be installed into system permanently without boot. The systemless versions patch the boot automatically...
Click to expand...
Click to collapse
Sent from my Nexus 6P using Tapatalk

toknitup420 said:
See the part where he mentions the kernel(boot) se policy, this is what you have to modify for root. So yes. It does require a modified boot to install to system. Which is exactly what is explained in the last 2 paragraphs of that quote. However you can override that and force a systemless install if you desire. See the echo command at the end of the 2nd to last paragraph in quote.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Not saying you're wrong here because I actually don't know but it isn't what I've been reading throughout the forum. Hoping to get a second opinion on this.

JustRootDontCustomRomIt said:
I'm not sure if that's right. I think systemless can be installed into system permanently without boot. The systemless versions patch the boot automatically...
Click to expand...
Click to collapse
You definitely need a modified boot.img for none systemless root that includes a few system checks removed and a sepolicy. I do this myself on every factry imgs because I will never use systemless root is stupid and pointless...So he was dead right for root on 2.66 you need modified boot.img

Tigerstown said:
You definitely need a modified boot.img for none systemless root that includes a few system checks removed and a sepolicy. I do this myself on every factry imgs because I will never use systemless root is stupid and pointless...So he was dead right for root on 2.66 you need modified boot.img
Click to expand...
Click to collapse
Ok. That's a bummer I guess.
Still confusing though because it's the first I hear about this. I could of swore I read that chainfire said the systemless versions will automatically patch boot.. I think I probably misread.
I'm going to sleep right now but could you help me get started? Anything to get me on the right start is appreciated. I know I'll need a modified boot img that works for 6.0.1. you're on 6p right? Because systemless sounds pretty good for me atm. Sounds simpler. It supposedly the same thing as traditional except a very few apps that I hear have compatibility issues. Nothing that can't be fixed with a symlink I believe.
I'm still weighing everything in.

JustRootDontCustomRomIt said:
Ok. That's a bummer I guess.
Still confusing though because it's the first I hear about this. I could of swore I read that chainfire said the systemless versions will automatically patch boot.. I think I probably misread.
I'm going to sleep right now but could you help me get started? Anything to get me on the right start is appreciated. I know I'll need a modified boot img that works for 6.0.1. you're on 6p right? Because systemless sounds pretty good for me atm. Sounds simpler. It supposedly the same thing as traditional except a very few apps that I hear have compatibility issues. Nothing that can't be fixed with a symlink I believe.
I'm still weighing everything in.
Click to expand...
Click to collapse
if you like I can share my modified boot.img I did myself and yes I can help you just PM me. It will only take a few mins. You have working fastboot setup already? It's not the same I don't have time to explain right now tho. If you want help PM me when your ready

Tigerstown said:
if you like I can share my modified boot.img I did myself and yes I can help you just PM me. It will only take a few mins. You have working fastboot setup already? It's not the same I don't have time to explain right now tho. If you want help PM me when your ready
Click to expand...
Click to collapse
Pm you. I have fastboot ready.

JustRootDontCustomRomIt said:
Pm you. I have fastboot ready.
Click to expand...
Click to collapse
I didn't get a Pm. But I'm eating right this minute first you need to flash factory imgs for 6.0.1 via fastboot. Have you don't that before?

Adaway Error

I was running Adaway on my rooted/soff M7 and would like to run it on my now rooted/soff 10. I tried downloading v3.3.1 from @mrRobinson thread here but each time I tried to open the program it said something about a SuperSU error. I'm guessing that it didn't like the modified SuperSU we used rooting the 10 to keep forceencrypt? Any one have an idea or see something I did wrong?
Edit:
Looking through my apps list I can't find SuperSU, but I know it's on here cause it ran when sunshine requested root access and I had to side load it through TWRP for root. Why wouldn't it show up in my app list?

use this, then adaway works fine: http://forum.xda-developers.com/htc-10/development/root-supersu-2-71-forceencrypt-verity-t3373258

Load this app: jRummy Root Check
It should work if the SuperSU process was successful. I used jcase's guide Root-optionally-s-off-radio
After that, I loaded the XDA Labs App, then loaded AdAway. Everything working as it should.
You may want to retrace your steps to jcase's quide, and see what might have been missed.
HTH.

I followed jcases method for root and soff and had to side load the modified SuperSU that @starbase64 linked to in that process. That jRummy app says I do not have root. Can I just flash the modified SuperSU in TWRP? I'm definitely soff, so how would I be able to get soff without root? So weird

yes, but restore stock boot.img first

Yes that should work.
Root these days is in the boot.img so if you reflashed that at any point you are back at stock.
Adaway is working fine here!

The only thing I did after jcases root/soff procedure was flash the Verizon radio from @dottat. Not sure how I would have messed with the boot.img

Light1984 said:
The only thing I did after jcases root/soff procedure was flash the Verizon radio from @dottat. Not sure how I would have messed with the boot.img
Click to expand...
Click to collapse
starbase64 said:
use this, then adaway works fine: http://forum.xda-developers.com/htc-10/development/root-supersu-2-71-forceencrypt-verity-t3373258
Click to expand...
Click to collapse
Did you flash this file in twrp yet? That should be all you need to do.

Light1984 said:
The only thing I did after jcases root/soff procedure was flash the Verizon radio from @dottat. Not sure how I would have messed with the boot.img
Click to expand...
Click to collapse
Oh well
If SuperSU isn't in the app tray and you haven't hidden it manually, flashing back SuperSU (preferably topjohnwu version) should bring it back.

10-4 brb. Thanks
Edit: yes, I checked with jcase too. Just reflashed the zip in TWRP. Although when it was going through its process it said it already found the files and over wrote them anyways, maybe something got corrupted at some point. All is well now, thanks for the help all.

May also be something in /data/ somewhere which will be lost as S-Off forces data to be reset -- but again a TWRP install of SuperSU should cover it.

Supersu abort on 7.1.1

Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash

Guitarboarder28 said:
Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash
Click to expand...
Click to collapse
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).

ohlin5 said:
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).
Click to expand...
Click to collapse
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess

I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)

Mgrev said:
I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)
Click to expand...
Click to collapse
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.

Guitarboarder28 said:
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.
Click to expand...
Click to collapse
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?

Mgrev said:
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?
Click to expand...
Click to collapse
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!

Guitarboarder28 said:
you sound like you need a hug!
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess
Click to expand...
Click to collapse
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck

I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.

ohlin5 said:
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck
Click to expand...
Click to collapse
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
dratsablive said:
I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.
Click to expand...
Click to collapse
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore

Guitarboarder28 said:
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore
Click to expand...
Click to collapse
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.

dratsablive said:
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.
Click to expand...
Click to collapse
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work

Guitarboarder28 said:
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work
Click to expand...
Click to collapse
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.

Guitarboarder28 said:
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!
Click to expand...
Click to collapse
I didn't think you meant to express hate either!
I seemed to forget to mention that i backed up my data with titanium backup, flashed, then wiped, and then restored it. So in the end, you probably need to wipe (just like you did)

dratsablive said:
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.
Click to expand...
Click to collapse
Magisk hide just hides Magisk itself... it doesn't do anything for root. As for PoGo, right now the only way to do that on 7.1.1 is to NOT be rooted.
Once the kernel sources for the 7.1.1 are released, this patch will make its way onto custom kernels, which means you'll still be able to edit /system while rooted, unroot, and keep the changes via the patched kernel, as well as bypassing the SafetyNet bootloader check.
A kernel does exist now with that patch (francokernel), but it is based on the 7.0 kernel sources, so some things are broken if used on 7.1.1.
In re: to the superSU ramdisk install failure, this will happen if there are old files left over in /data from a previous magisk install and/or patched boot images. The SuperSU installer script will detect those and step into code branches that it doesn't need to be in, and thus fail. The solution is deleting the offending files from TWRP w/ adb, and installing SuperSU zip again.
/thread

Thread cleaned a bit, please stay on topic.
Have a good day!
Forum moderator,
Matt

Works fine for me flashed 7.1.1 OTA then flashed SuperSU zip

Is developer OS Image mandatory for root/magisk?

I'm a little lost on the differences between the shield and every other android phone I've owned. What difference does the developer image offer compared to simply unlocking the bootloader and installing magisk through TWRP on the shipped firmware?
Ultimately I want to root for all the obvious reasons, but also use magisk hide to keep PSVue and the like still working with root undetected. It seems that the developer image is pre-rooted, can that be hidden?
Thanks for any clarification

tstack77 said:
I'm a little lost on the differences between the shield and every other android phone I've owned. What difference does the developer image offer compared to simply unlocking the bootloader and installing magisk through TWRP on the shipped firmware?
Ultimately I want to root for all the obvious reasons, but also use magisk hide to keep PSVue and the like still working with root undetected. It seems that the developer image is pre-rooted, can that be hidden?
Thanks for any clarification
Click to expand...
Click to collapse
No it is not, as long as your bootloader is unlocked and you follow the directions on the thread how to install Magisk you will achieve root

jionny said:
No it is not, as long as your bootloader is unlocked and you follow the directions on the thread how to install Magisk you will achieve root
Click to expand...
Click to collapse
You don't get true root with the ota firmware though.
You won't have write access to the root dir.
Which you will if you use the developer image through adb, or by disabling dm-verity.
You won't be able to do that on the ota.

mLgz0rn said:
You don't get true root with the ota firmware though.
You won't have write access to the root dir.
Which you will if you use the developer image through adb, or by disabling dm-verity.
You won't be able to do that on the ota.
Click to expand...
Click to collapse
So on non dev if I disable dm verity with magisk, I can write to system.
Or is it not that simple.
Sent from my SM-G965F using XDA-Developers Legacy app

Largewoodenspoon said:
So on non dev if I disable dm verity with magisk, I can write to system.
Or is it not that simple.
Sent from my SM-G965F using XDA-Developers Legacy app
Click to expand...
Click to collapse
No you won't be able to get write access on the non dev.

mLgz0rn said:
No you won't be able to get write access on the non dev.
Click to expand...
Click to collapse
I was referring to the Pro version

jionny said:
I was referring to the Pro version
Click to expand...
Click to collapse
Does not matter if it's the pro version or not.
You can only get write access to the root dir using the developer image.

mLgz0rn said:
Does not matter if it's the pro version or not.
You can only get write access to the root dir using the developer image.
Click to expand...
Click to collapse
Definitely not true I unlocked bootloader and did not use developer image installed magisk, patched and gained full write privileges

jionny said:
Definitely not true I unlocked bootloader and did not use developer image installed magisk, patched and gained full write privileges
Click to expand...
Click to collapse
This ^^
I don't understand why so many people say they don't have write privileges. I've not installed TWRP or any other custom recovery, I've simply used ADB to fastboot (boot only , not flashed) with an image that was posted in the magisk thread. Once loaded , I installed Magisk , let it root my shield, used x-plore and verified that I can change permission on any file in the system folder. All my root related functions work without any issue. Shield 2017 with 7.2.2

jionny said:
Definitely not true I unlocked bootloader and did not use developer image installed magisk, patched and gained full write privileges
Click to expand...
Click to collapse
On what firmware version?
I doubt you can write to the /system and /data dir if you are on 7.2+.
---------- Post added at 14:37 ---------- Previous post was at 14:31 ----------
Roamin64 said:
This ^^
I don't understand why so many people say they don't have write privileges. I've not installed TWRP or any other custom recovery, I've simply used ADB to fastboot (boot only , not flashed) with an image that was posted in the magisk thread. Once loaded , I installed Magisk , let it root my shield, used x-plore and verified that I can change permission on any file in the system folder. All my root related functions work without any issue. Shield 2017 with 7.2.2
Click to expand...
Click to collapse
Which image was that?
You can't get write access on the ota that comes with the updater on the shield without modifying the kernel and build.prop.
Hence why they are making a developer image that is prerooted.

jionny said:
Definitely not true I unlocked bootloader and did not use developer image installed magisk, patched and gained full write privileges
Click to expand...
Click to collapse
mLgz0rn said:
On what firmware version?
I doubt you can write to the /system and /data dir if you are on 7.2+.
---------- Post added at 14:37 ---------- Previous post was at 14:31 ----------
Which image was that?
You can't get write access on the ota that comes with the updater on the shield without modifying the kernel and build.prop.
Hence why they are making a developer image that is prerooted.
Click to expand...
Click to collapse
It was the boot.img posted by ACiDxCHRiST in that post : https://forum.xda-developers.com/showpost.php?p=78496132&postcount=163
He has since taken down the boot.img file, but I had saved it in my pc when he posted it. I never flashed it , because I didn't want to brick anything. That is why I had only "fastboot boot boot.img" . Worked fine on 7.2.1 , and then again worked fine on 7.2.2. I haven't tried to root 7.2.3 yet. If you need that exact file to test , I can provide it to you in a few hours when I get back home.

Roamin64 said:
This ^^
I don't understand why so many people say they don't have write privileges. I've not installed TWRP or any other custom recovery, I've simply used ADB to fastboot (boot only , not flashed) with an image that was posted in the magisk thread. Once loaded , I installed Magisk , let it root my shield, used x-plore and verified that I can change permission on any file in the system folder. All my root related functions work without any issue. Shield 2017 with 7.2.2
Click to expand...
Click to collapse
Exactly and I also use x-plore

Roamin64 said:
It was the boot.img posted by ACiDxCHRiST in that post : https://forum.xda-developers.com/showpost.php?p=78496132&postcount=163
He has since taken down the boot.img file, but I had saved it in my pc when he posted it. I never flashed it , because I didn't want to brick anything. That is why I had only "fastboot boot boot.img" . Worked fine on 7.2.1 , and then again worked fine on 7.2.2. I haven't tried to root 7.2.3 yet. If you need that exact file to test , I can provide it to you in a few hours when I get back home.
Click to expand...
Click to collapse
I'm pretty sure that would be the boot.img from the developer build, hence why you can get write access, since it has the modifications needed.
But if you do find it, please share it so I can check .

mLgz0rn said:
I'm pretty sure that would be the boot.img from the developer build, hence why you can get write access, since it has the modifications needed.
But if you do find it, please share it so I can check .
Click to expand...
Click to collapse
That boot.img was patched , most probably by magisk itself. Anyways, sent you the link via PM.

mLgz0rn said:
I'm pretty sure that would be the boot.img from the developer build, hence why you can get write access, since it has the modifications needed.
But if you do find it, please share it so I can check .
Click to expand...
Click to collapse
magisk makes the modifications,, you patch the boot img with magisk then transfer it to your pc then abd fastboot flash boot patched_boot.img... really is that simple.. Has nothing to do with the developers image