yashsingh1/xdaforums huggingface dataset:
[SuperSU] fudgeboy:
Is there a simple way to unroot temporarily, if you've installed the systemless root?

I have a few annoying apps that detect root and complain, and it would be nice to be able to temp unroot to use them.

I tried reflashing the stock boot.img, and although that stopped root working, it didn't stop apps detecting that the device had been modified from stock.
[SuperSU] Segarra:
I'm interested too, just for be able to use Touch and Pay

Enviado desde mi U30GT 2 mediante Tapatalk
[SuperSU] ashyx:
[MENTION=631273]Chainfire[/MENTION] and anyone else who can answer, there's a few things about the systemless root method which puzzles me?

1. Will this method only work on android 6.0 and Nexus devices at the moment?

2. In the ramdisk modification instructions chainfire mentions an ext4 su.img that gets copied from cache to data and gets mounted to /su, but where does this su.img come from, it isn't supplied in the WIP thread.

EDIT: I think this is created in the zip flashing process.

3. chainfire also states that supersu v2.56 also still supports system root.

What is the mechanism it uses to decide whether to flash system or systemless?
[SuperSU] falanca:
thanx man...
[SuperSU] swa100:
So if I understand correctly.. For systemless root I need to install a custom recovery like twrp, then flash supers v2.56. That's it? When xposed for Android 6.0 will be released, I'll be able to install it? And when I wan't to install OTAs I just need to flash boot.img that I can extract out of the factory image? I just don't get what the "systemless boot" files mean in the download thread (http://xdaforums.com/showpost.php?p=63197935&postcount=2).

I'd like to hear if I'm correct! Sorry for my noobyness. I've been out of this "world" for a while
[SuperSU] spinosa:
I've got seamless root with MRA58V on a nexus 7 2013 LTE working using a boot image posted ways back in this thread. So far so good. I've not felt the need for xposed too badly yet. Entering the adb command 'settings put global policy_control immersive.navigation=*' enabled immersive mode for all apps and its working very well (no keyboard problems & apps all seem to cope). The suggestion to add a script with a bind mount for /system/etc/host to /su/etc/hosts in /su/su.d is working and enables adaway. The combination of seamless root, immersive mode and adaway is keeping me happy. Battery life is much improved too - no greeenify or amplify needed on my tablet with marshmallow.
[SuperSU] swa100:
So how did it work? You just flashed the systemless boot img and supersu was installed?

Edit: ah wait. So you flash the systemless boot img and then install supersu? You don't have to look for a custom recovery yourself, right?
[SuperSU] jazzruby:
The updater-script|binary is quite thorough / informative and I believe your interest is in these lines of code:

#testing
WANTSYSTEMLESS=true

API=$(cat /system/build.prop | grep "ro.build.version.sdk=" | dd bs=1 skip=21 count=2)

RWSYSTEM=true
if [ "$API" -eq "$API" ]; then
if [ "$API" -ge "23" ]; then
if ($WANTSYSTEMLESS); then
RWSYSTEM=false
fi
fi
fi

However I don't believe it will install a 'system' root to API 23; if that was part of your query

HTH,

-JR-
[SuperSU] ashyx:
Yep already found that code before you posted and changed it to API level 21, it works and installs systemless root on 5.02. Everything gets installed including everything in /su, and the superuser app, but not fully rooted. Superuser reports no binary installed.
[SuperSU] phpmyforum:
My Nexus 5x has version MDB08M, so do I need a new boot.img? Chainfire could you please update the images?

Thanks :)
[SuperSU] efler:
Hi

Which one from attached are for xperia z3 d6603?

Got already ZYXX V1.2

Thanks in advance
[SuperSU] koelspy:
Does anybody know if there will be a modified boot.img for mra58n on hammerhead (Nexus 5)?

I want to root stock mra58n, but can't find a modified boot.img.
[SuperSU] Ja_som:
http://xdaforums.com/showpost.php?p=63643850&postcount=2501
[SuperSU] amaruk27:
Has anybody that's using systemless root and SuperSU had any crazy battery numbers like 4200% instead of 100%?

Nexus 6 running:

Ubermallow

Benzo gapps

Systemless boot image

SuperSU 2.52
[SuperSU] ashyx:
Systemless boot uses v2.56 not v 2.52.

Supersu will be installed to system.
[SuperSU] androcraze:
I did with the 6.0.0_r26 compile on my N5. Changing to r2 fixed it. r26 was specifically for the 5X and 6P.

Although even with the r2 revision, using the MRA58N-based ROM with the MRA58K boot image (provided by CF in his "WIP" thread) gave erratic battery stats, with percentages jumping wildly by over 10% within minutes. This is for the 2.52 SuperSU and the non-systemless ("regular") image.
[SuperSU] Andro-Man:
I am not sure if I should ask my Q here, But I hope it is the right place for it:

I make some pre-rooted system files for some Samsung models, I follow the steps from (update-binary) script ( the one inside SuperSU-v2.52/META-INF/), I copy the needed files and make the needed changes, All is easy and understandable for me, But I could not get the exact meaning of the following:

# 21+ /system/bin/app_process32 *5 /system/bin/app_process32_original 0755 u:object_r:zygote_exec:s0 required
# 21+ /system/bin/app_process64 *5 /system/bin/app_process64_original 0755 u:object_r:zygote_exec:s0 required
# 21+ /system/bin/app_processXX *5 /system/bin/app_process_init 0755 u:object_r:system_file:s0 required
# 21+ /system/bin/app_process (symlink to /system/xbin/daemonsu) required
# 21+ *5 /system/bin/app_process32 (symlink to /system/xbin/daemonsu) required
# 21+ *5 /system/bin/app_process64 (symlink to /system/xbin/daemonsu) required
# *5: Only do this for the relevant bits. On a 64 bits system, leave the 32 bits files alone, or dynamic linker errors
# will prevent the system from fully working in subtle ways. The bits of the su binary must also match!

I understand these lines like:

- Rename /system/bin/app_process32 to /system/bin/app_process32_original ( If I found this one )

- Rename /system/bin/app_process64 to /system/bin/app_process64_original ( If I found this one )

- Change /system/bin/app_process file which is a symlink to /system/xbin/daemonsu

- Make /system/bin/app_process32 file which is a symlink to /system/xbin/daemonsu ( If I found this one )

- Make /system/bin/app_process64 file which is a symlink to /system/xbin/daemonsu ( If I found this one )

But I did not understand this order:

/system/bin/app_processXX *5 /system/bin/app_process_init So can anyone explain the what should I do for this?

Thanks in advance :)
[SuperSU] rpr69:
Considering that there is no LMY48X update for the N5, and that LMY48X is Lollipop, I'm not sure where you went wrong here, but something isn't right. Regardless, I would recommend not flashing LMY48X via OTA.
[SuperSU] !@ndre@!:
I've copied the wrong code..obviously it was MRA58N! ;)
[SuperSU] gorilla p:
When anyone gets the chance, be sure to flag the app "SU SuperUser" on the Play Store. Its pretty obvious theyre trying to ripoff SuperSU. Even stole the icon. Not to mention, theyre trying to charge $11.89?

https://play.google.com/store/apps/details?id=com.nxlab.superuser
[SuperSU] jimbomodder:
Done. In UK its £9.23 for super user?!!! Lol bad call on that one.
[SuperSU] Ch3vr0n:
There's so many options to choose to report I'm not sure what to use. Point me to the correct one and it will be done

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] slyguy2000:
Done as well! Apparently 5 idiots downloaded it!
[SuperSU] a g bell:
Send the dev a nice email too I did?
[SuperSU] Ch3vr0n:
Done with multiple different report options, and sent a nice little mail too. I hope that's his third strike and his dev account gets banned. Ffing imposters trying to make money off chainfire handing over control. Trying to charge nearly 12 eur for that crap.

Upd. Don't bother sending an email to the account listed in play store. While typing this I just got the mailer-daemon for address not found/message not delivered.

[MENTION=631273]Chainfire[/MENTION] adding you in this topic so you are notified of IP breach and are able to contact Google as well.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] gorilla p:
I used the IP violation (Intellectual Property) one
[SuperSU] Manuel15:
12,79€ ?!? They are crazy.
[SuperSU] shoey63:
Would just like to point out something on the "systemless root" method. Installing SuperSU 2.56 changes /system/etc/installrecovery.sh and backs it up. So therefore /system is compromised.

Edit: in MM it is in /system/bin

Edit2: Nope, it is untouched ;)
[SuperSU] Shepastian:
Excuse me , flasheable zip 2.52 work in shamu MRA58N Stock???
[SuperSU] betovanbuuren:
To flash the systemless root for android 6 in a nexus 6p, should i unlock bootloader? Of can i just boot in twrp and flash the modified boot and SU?
[SuperSU] shoey63:
I don't think you cam flash twrp on locked bootloader, even on nexus devices
[SuperSU] betovanbuuren:
That's why i mention "boot" in twrp using fastboot boot xxxx.img
[SuperSU] vt0r:
I would unlock the bootloader anyway, just because it's the only way to resolve some issues requiring fastboot intervention, but it's not required. Keep in mind: by leaving the bootloader locked, you're putting yourself at risk (unnecessarily) for a possible bad flash bricking your device, as without fastboot, there are a few conditions you can get into that would not be user-repairable, even if they are extremely unlikely.

With that being said, yes, you can simply boot into TWRP and flash the modified boot image + SuperSU 2.56 and be on your way. I'd recommend reflashing the factory system image if you've made any modifications to /system, or even if you think you might have but are unsure, as this gets you into a truly "clean" state.
[SuperSU] amaruk27:
Oops, actually I am using 2.56. My bad.

I'm also using the systemless root for MRA58N here:

http://xdaforums.com/showthread.php?p=63645513

With a ROM (ubermallow) that is supposed to be MRA58N based and I'm still getting crazy battery stats.
[SuperSU] betovanbuuren:
Thanks muich [MENTION=5451244]vt0r[/MENTION]
[SuperSU] efrant:
The "fastboot boot" command does not work if your bootloader is locked. (If you think about it, it makes sense: if you could boot TWRP with a locked bootloader, then you have root, and there wouldn't ever be a need to unlock the bootloader).
[SuperSU] betovanbuuren:
Yes you are right, better to unlock it, thanks all for your help
[SuperSU] ntegra:
Has anyone successfully taken an OTA while running with systemless root? I'm running a 6P on MDB08K.

It fails installing OTA complaining that "EMMC:/dev/block/platform/soc.0/f9824900.sdhci/by-name/boot:12350694:bab44710ce080ecef83475bbf637e24f86377aab:12350694:5a09986fd42a593f8075a78b29bf588394e0f120" has unexpected contents."

The only two apps that have SU is busybox & root explorer, neither of which were installed prior to OTA attempt.
[SuperSU] chrisonline:
Just did it, but if I open SuperSU I get a warning that I am not rooted.

I am on a Nexus 5X with build MDB08L.

Unlocked bootloader, flashed boot.img for MDB08L, flashed TWRP and installed SUPER SU 2.56!

TWRP has asked me after I hit "Reboot" if Super SU should be installed. Selected "Do not install" because I have done this before with 2.56!

Or should I select "install"?
[SuperSU] Ja_som:
v2.56 is only for systemless, did you flash systemless boot?

If not, flash v2.52
[SuperSU] vt0r:
As Chainfire mentioned in the WIP thread and also reiterated here at least once, taking the OTA will require reflashing the boot image, since it verifies the contents of any images before patching (to ensure the patch will be successful).

So just flash the factory boot.img before taking the OTA, and you should be all set, then reflash the modified one afterwards that corresponds with the current version.
[SuperSU] chrisonline:
I flashed the moified boot.img from this thread:

http://xdaforums.com/showpost.php?p=63781454&postcount=143

Where do I get a systemless boot.img for MDB08L?
[SuperSU] vt0r:
If I understood his post correctly, it sounded like he already unlocked the bootloader, flashed TWRP and relocked it afterwards.
[SuperSU] Ja_som:
I think, that is not systemless boot, is not mentioned there, so flash SuperSU v2.52
[SuperSU] chrisonline:
Do you know where I can get the systemless boot for Nexus5X - MDB08L?
[SuperSU] ntegra:
Thanks for the response. First time I tried systemless I did just that, but upon reflashing factory boot I got "you are corrupted" error and could not boot phone, so reflashed total stock. Saw a few pages back someone said "nothing needs to be flashed prior to taking OTA", so that's what I just tried. Of course I ASSUMED they were speaking from experience. MY BAD! (GRIN). I will retry the boot flashing process again....
[SuperSU] vt0r:
No worries. Just verify the factory image archive's signature matches that shown on the official download page before extracting, and then you shouldn't have to worry about corruption.

You may also need to flash a stock recovery for some OTAs as well, but that depends on whether or not it's touched by the update. You'll get the associated error message for recovery partition sig verification if so.
[SuperSU] Ja_som:
No, I don't. Try ask in your device forum on XDA.
[SuperSU] drewski_1:
this has one for mdb08i. you can try it and see if it works as the kernel may not have changed (much or at all) between the two releases.

http://xdaforums.com/showpost.php?p=63197935&postcount=2

i'm using an older build boot.img on my N7 2013 and it's working fine.
[SuperSU] efrant:
He asked if he could use "fastboot boot TWRP.img" with a locked bootloader, which doesn't work.

To be able to install any OTA update, you need to be completely stock, i.e., stock boot image, stock system image and stock recovery image.
[SuperSU] pkelly517:
I'll admit that I haven't been following the OTA requirements religiously, but hasn't Google just been checking the partition it's been updating? My somewhat flawed memory thinks this has been in effect for a while. I thought it was in effect even after the system block check update. If you root, then you are SOL. /system changes and all fails right up front.

But a minor update to /system wouldn't query /boot or /recovery.

Again, will all the monthly security updates only apply to those who are totally stock? And by totally, I mean a large majority of Nexus users. Only the rooting, TWRPing community can't hit the 'Update Now' button.

Thanks.

And really, when I hit Later, can I wait until I try to update myself?
[SuperSU] efrant:
You're right in that not every single update will verify the boot partition, but the vast majority do. As for the system, now that OTA updates are block-based, and change to system, minute or large, will cause the update to fail, even mounting the partition r/w. For recovery, the stock recovery is required to accept the OTA notification, or it will fail.
[SuperSU] silvertrain78:
I OTA updated my N7 2013 Wi-Fi with the November security patches, and didn't have a problem. Not rooted and stock recovery, but I did modify the hosts file for ad blocking. (Temporarily booted TWRP and flashed Moaab.
[SuperSU] nukeboyt:
Can anyone describe the process for a Nexus 6P of going FROM a working systemless root on MDB08K, TO working systemless root on MDB08M? Either by OTA or manual flash. I keep getting reminded to take the OTA, but from what I've read, I have to restore stock boot.img (and some people say recovery.img has to be restored too) I'm confused, and would love to hear from someone who's actually made the transition. Thanks
[SuperSU] efrant:
Block-based OTA updates are new - - starting on devices that were shipped with Android 5.0+. Older devices that were shipped with KK and earlier (such as your Nexus 7) are still file-based.
[SuperSU] Cares:
How would I move from systemless root to your traditional root? I didn't account for Adaway not working with systemless.
[SuperSU] lothos:
You are lucky, then, because a block based OTA could potentially overwrite blocks that you modified, corrupting the filesystem.
[SuperSU] mrRobinson:
It works fine. Go to the AdAway thread for details.
[SuperSU] Andro-Man:
------------------------------

Any Help Please? :)
[SuperSU] smitharro:
I saw that there is a 2.56 version. I'm using a Moto G 2014 with the unofficial CM13. But I'm reluctant to flash this, because I read that it might break the boot. Anyone knows if we can use SuperSU on anything else with Android 6.0 than nexus devices?

Written with my XT1068 using Tapatalk on CM13
[SuperSU] jimbomodder:
I've run it fine on S4 with cm13

Sent from my SM-A500FU
[SuperSU] Primokorn:
Deleted...
[SuperSU] ntegra:
Well it looks like something is also modifying my system partition cuz the OTA now fails due to unexpected content in system. I had installed busybox (installed to /su/bin), root explorer, and flashfire. All su enabled. Would just allowing them access in supersu change something in the (systemless rooted) system partition?
[SuperSU] osm0sis:
I've found the Stericson busybox installer to be pretty buggy; on one (but not the other :confused:) of my devices it reverts to /system/xbin even after I enter /su/bin, so perhaps you installed busybox by mistake.
[SuperSU] drewski_1:
AFAIK, 2.56 is just for systemless root and you need a modified kernel / boot.img

2.52 is for the "normal" root process, but may also need kernel mods for marshmallow.

Isn't cm13 prerooted?
[SuperSU] ntegra:
Yeah, you would think it would show correctly... It knows I got it in /su/bin... why is it saying it's going to install to /system/xbin?:p

Going to wipe for another try...
[SuperSU] Cares:
Which uninstaller? You mean just uninstall SuperSU like any other app?

And you mean flash the system root modified boot.img and SuperSU 2.52?
[SuperSU] jblazea50:
Can someone please post the boot.img for MRA58N Nexus Player (Fugu)?

I'm rooted and every day the NP is on the TWRP recovery because it's trying to install the OTA update.
[SuperSU] smitharro:
Yes, it is pre-rooted, but I prefer SuperSU. With SuperSU I can modify my /system partition without having to boot to recovery first. Besides, I'm annoyed by the # in the taskbar being constantly present...

Written with my XT1068 using Tapatalk on CM13
[SuperSU] PhrostB:
I have the latest CM12 nightly on my t-mobile Galaxy S5 and use cyandelta to update it daily.. anyway I would get errors before so I figured I would try installing SuperSU from the app store (even got SuperSU Pro) but I still get errors. Every time I open it it says "The SU binary needs to be updated, Continue?" and then I continue and it works. This happens on a daily basis. does anyone know why?
[SuperSU] Badgerkiller:
Hi guys,

I rebuild Hammerhead MRA58N kernel with systemless, if you can try ;)

Files replaced :

Personally I use 2.52 so I can't try before publish :(
[SuperSU] androcraze:
This is for the N5, or N7?
[SuperSU] Badgerkiller:
Hammerhead = N5 :D
[SuperSU] egingell:
It makes symlinks in /system/bin by default.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] ashyx:
The Supersu uninstaller in settings.

You will need a stock boot.img with the ramdisk mod to sepolicy if you are samsung 5.1.1 or Android 6.0. Then install v2.52
[SuperSU] Shepastian:
I flash this boot in cmd, and after i can flash supersu?? I dont understand :(
[SuperSU] Cares:
I'm talking about systemless root. There is no uninstall option for this.
[SuperSU] drewski_1:
Reflash stock boot.img
[SuperSU] ashyx:
All you need to do is remove the superuser apk.

Reflashing a stock boot.img basically removes root.
[SuperSU] vt0r:
These are true, as flashing any other boot.img that does not have the systemless root modifications to its ramdisk will effectively disable root. However, there will still be a file present at /data/su.img containing the SuperSU daemon, init scripts, etc. To remove all traces of SuperSU, you'll need to remove this file in addition to flashing a standard boot image. Of course this also assumes you already have a clean /system flash as well, meaning there are no previous installations of SuperSU (2.52 or older).
[SuperSU] Cares:
Thank you! Does "reverting host" files in Adaway also put it into full stock? Trying to figure out what I need to do before accepting OTAs.
[SuperSU] Dr0idgroove:
So I have a question: How do I check if I have systemless root?

I did a clean install of MRA58N factory image on my Nexus 5. Flashed the modified boot.img provided here. Then flashed TWRP 2.8.7.1. Booted up the device. Put the SuperSU v2.56 zip file on the phone. Booted into TWRP, installed the SuperSU Zip. Then TWRP said the phone wasn't rooted. It asked if I wanted to install SuperSU. I thought it was part of the process, so clicked Yes. Then phone rebooted, when Android was ready it showed an installation wizard for SuperSU. So clicked through. Then phone rebooted and I had SuperSU v2.46 all of a sudden. Not good. So I reflashed system.img and boot.img to undo any possible changes done by the wrong SuperSU version, then did the same steps in TWRP. Then rebooted, now I didn't get the installation wizard on restart and I checked the SuperSU app and now it was v2.56.

Root is working. The SuperSU app is the right version. So how do I check if I have systemless root and not 'normal' root?
[SuperSU] ashyx:
Look for /su in there you will see all the root files and in data will be su.img
[SuperSU] Dr0idgroove:
I reflashed system.img and the modified boot.img and then I lost root so I guess I wasn't systemless. Re-tried the steps I described above but I can't get root for the life of me. I decline TWRP's offer to install SuperSU after I flash the zip to prevent it from installing v2.46. How on earth do I get it to work?
[SuperSU] mmonaghan34:
If you are updating your CM12 daily then as CM has its own root method, every time you update it replaces SuperSU's su binary with its own, hence why SuperSU says it needs to update the binary, by which it means replace it with its own.
[SuperSU] Purerawenergy:
We're trying to get root on a custom Marshmallow rom but having difficulties. Any thoughts?

http://xdaforums.com/showthread.php?p=59193875

Tom 2.0

---------- Post added at 10:29 AM ---------- Previous post was at 09:57 AM ----------

I know how vague that was, sorry. We've just tried so many methods work 2.56 and no luck. Or rom developmer is awesome but just one man so I was reaching out. Can provide more details as well.

Tom 2.0
[SuperSU] Ch3vr0n:
There is no SU SUPERUSER, that's a copycat app asking $12 for chainfire's SU app.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] jimbomodder:
Report it. Almost everyone here already had
[SuperSU] Dr0idgroove:
OK, so after reading back a dozen of pages I came to the following conclusions:

- This MRA58N boot.img for hammerhead only works with v2.52. It does not enable systemless root in conjunction with SuperSU v2.56

- There is currently no modified MRA58N boot.img for systemless root for hammerhead (Nexus 5)

Are these conclusions correct?
[SuperSU] GROGG88:
There is a systemless image posted by someone as well.
[SuperSU] Alxoom33:
Please reread my post, I corrected my typo. I meant to say I used SuperSu, not SuSuperuser. As a trademark attorney I should know better[emoji2]

[MENTION=631273]Chainfire[/MENTION] can pm me about the knock- off app, if he would like to.
[SuperSU] Ch3vr0n:
As far as the imitation goes, just report it for IP violation. If enough go through maybe it will get removed. Perhaps we should even post review with 1 star to inform users about the imitation and the REAL free app.

[MENTION=6576153]jimbomodder[/MENTION] I have, did so the second after a user informed us about it here. :)

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] Alxoom33:
No, [MENTION=631273]Chainfire[/MENTION] needs to send a DMCA takedown notice. Flagging will not do much.

---------- Post added at 11:44 AM ---------- Previous post was at 11:13 AM ----------

Is there a Systemless boot.img for Nexus 6 MRA58R?

Edit: the MRA58K Systemlessboot.img file for Shamu worked great!

I confirm having Systemless Root working with my Cataclysm custom Shamu ROM on an encrypted phone.