yashsingh1/xdaforums huggingface dataset:
[SuperSU] gunit34328:
Did you figure out how to root your nexus 6?

I tried using this method found on this blog that soft bricked my phone (http://wccftech.com/flash-android-6-0-1-for-nexus-6-and-root-it/)

so I had to reflash stock and unroot to get my phone working again.

I was wondering if I flashed TWRP recovery and then flashed the BETA-SuperSU-v2.62-3-20151211162651 version of SuperSU, then I will be able to obtain root?

I am currently on a stock nexus 6 running 6.0.1 MMB29K.

Please let me know what worked for you! Thank you in advance!

---

edit update: So I flashed TWRP and the BETA-SuperSU-v2.62-3-20151211162651 version of SuperSU, which was able to root my device. I have restarted my phone 2 times and everything seems to work fine. For some weird reason though, when I go to edit the build.prop with "net.tethering.noprovisioning=true" it seems to soft brick my phone (stuck at the Google logo). It's very odd since it worked for me in the past when running android 5.1. Are there any new changes that I should be aware of?
[SuperSU] bobby janow:
It's kind of tricky but once you get it you're done. If you are now back on systemless 2.62 you can flash 2.65 (at least this is what I did) but before you do enter the command "echo SYSTEMLESS=true>>/data/.supersu" no quotes, in terminal. So the way I did it was to boot into recovery and on the computer go to adb shell and su. At the # copy and paste that line in then flash 2.65. That gave me systemless. I reflashed another kernel yesterday and reflashed superSU without the command and systemless remained. I'm not sure if this is the best way to do it but it worked for me.
[SuperSU] fdc77:
thank you, this work if i want to update supersu or if reinstall SU after I reflash another kernel, but is possible to force systemless on a fresh new install with ?
[SuperSU] bobby janow:
I believe so, yes.
[SuperSU] adampollack:
Can you point me to the link to supersu v2.62? I can only find v2.52

Thanks!
[SuperSU] shaggyskunk:
http://xdaforums.com/showthread.php?p=63168310

Google is your friend ;)

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] nathanchance:
All in this post.
[SuperSU] ceza1380:
I wonder if systemless root only works for Stock Android devices like Nexus devices? Because in Chainfire systemless root forum and here Supersu beta forum people only talks about stock Android devices. Chainfire systemless root forum has only Nexus devices boot images. I ask you because LG G3 which I'm using just got 6.0 and i wonder can I use systemless root with it?
[SuperSU] dahawthorne:
Anyone have any helpful comments...? Thanks.
[SuperSU] adampollack:
Thanks so I can go with 2.65 now as its the latest?
[SuperSU] Maxr1998:
Nope, it should work for every device now. The images were only needed at the beginning when the install zip didn't have automatic bootimage patching.

So you can use it. Be sure to make a nandroid in before, though.
[SuperSU] Maxr1998:
Sure.
[SuperSU] MrPib:
Hi. I've done a lot of reading, and I want to make sure that I have this right.

I have a stock N6 running 6.0.1, which I want to root. Since I have to wipe data to unlock the bootloader, I might as well decrypt.

So I think I need to:

. Enable OEM Unlocking

. Unlock the boot loader (wipes Data)

. Install TWRP

. Flash a non-forced-encryption MMB29K

. Reformat Data (should be unencrypted)

. Flash stock MMB29K

. Flash SuperSU 2.65

Please let me know if this looks right. Thanks!
[SuperSU] nathanchance:
I'd flash stock MMB29K, then the no force encryption boot image then format data but that is just me. If you flash stock MMB29K in that process, make sure to omit the boot.img.
[SuperSU] MrPib:
Thanks for the quick reply! The flash of stock MMB29K is so that SuperSU will install -- so don't I have to have boot.img included?
[SuperSU] nathanchance:
Well the no forced encryption kernel is a boot.img. As long as your system partition doesn't currently have SuperSU in it, you can flash the no forced encryption kernel, format then SuperSU.
[SuperSU] MrPib:
Ah, great! Thank you!
[SuperSU] BeingEEE:
i use sultans rom alone, no multirom, so i don't know
[SuperSU] berndblb:
No wait. If you want to flash systemless root you need the stock boot image, NOT the modified boot image.

Assuming that you are on the latest firmware just unlock the bootloader, flash TWRP, format data, flash SuperSU 2.6.5 and all should be well.
[SuperSU] berndblb:
There's been a detailed discussion on busybox with systemless within the last - idk - 20 pages or so. Do a search.

Another discussion was around the question if OTAs run a checksum on system or check a "lifetime write count" header or some such - not exactly my area of expertise.... I don't think that question was resolved.

But why don't you just flash the stock system image?
[SuperSU] jabbermacy:
^^ on this topic, if SU is built into the ROM (Pure Nexus) it's NOT SYSTEMLESS, right? Sorry for ROM question here :( I really don't want to go back to stock if I don't NEED to... also, I can't bloody find ANY SU folder using PN ????
[SuperSU] nathanchance:
Custom ROMs can have systemless root but most don't. You can check what it is in SuperSU > Settings > System > Install SuperSU into /system. In Pure Nexus' case, it is system root. You need to flash UnSU, then a custom kernel (if you have one), then systemless SuperSU.
[SuperSU] egingell:
Why should anybody update anything? You either want to or need to.

Sent from: SGS4 - JB 4.2.2 MF9
[SuperSU] jabbermacy:
^^ BUT only if I WANT to go system root > systemless, correct?

I didn't see anything detailed on Elemental installation procedure, but if you say PN system root is compatible, I'll do it.

One question, how can you go BACK to stock kernel? I assume ONLY way is to re-flash PN (since kernel is included), right? Sorry, just paranoid
[SuperSU] nathanchance:
Yes exactly. ElementalX is compatible with any kind of root. Systemless is only needed for stock because system root is not compatible with 6.0.1. Just flash EX over the Pure Nexus kernel and you will be fine. If you want to get back to the default kernel, just dirty flash the ROM.
[SuperSU] jabbermacy:
^^ NAT, thanks a ton... I have to admit, this encryption and all the new systemless stuff is confusing. I really appreciate the help a TON.

Happy new year!!!
[SuperSU] ssuds:
Has there been any new information about who Coding Code Mobile Technology, LLC is recently?
[SuperSU] Chainfire:
Please post the stock boot images. Not sure if that is enough for me to diagnose the issue, but the installer detects the current kernel *should* be able to boot with a system install, and thus uses that. For some reason that doesn't actually work, figuring out why may be tricky without a device in hand.

The boot image modifications made by SuperSU include removing forced encryption, there is no need to flash a no force encryption boot image before flashing SuperSU (systemless).
[SuperSU] nathanchance:
Oh right, thank you for the heads up. I keep it in mind!
[SuperSU] jediratte:
Edit: Beta 2.19 Working flawlessly on N4 with Frank reborn. Excellent Job no issues at all.
[SuperSU] Tinchoska:
Using latest beta since yesterday, no problems at all
[SuperSU] trungnghia:
2.19 BETA works on Nexus7 - 2013 - KK, thanks [MENTION=631273]Chainfire[/MENTION]! :good:

----------------------

chung cư linh đàm
[SuperSU] orcking:
SELinus

I have 2.19 SU on Nexus 4 and Android 5.0

after adb shell to device and su

I issue "pm install <package_name>"

I get this error

/system/bin/pm[6]: app_process: Permission denied

Any ideas on a fix??

Thanks
[SuperSU] nyuszika7h:
OTA survival/backup script not working

v2.19 couldn't restore superuser access after a CyanogenMod nightly update, I had to manually reflash from TWRP. It worked with v2.16.
[SuperSU] yOtAh:
Download failing - any mirror available?

Says domain blocked at http://click.xda-developers.com/api...v2.19 - XDA Forums&txt=BETA-SuperSU-v2.19.zip

Any mirror out there?

Thanks!
[SuperSU] Pkt_Lnt:
Something on your end is blocking, that link works for me just fine.
[SuperSU] yOtAh:
Thanks! Must be work proxy related :)
[SuperSU] Frank Westlake:
Set up Orbot:

https://www.torproject.org/docs/android.html.en

Frank
[SuperSU] Mr.Its:
On an older version of Android (4.1.x) if you add Superuser.apk as a system app and the su binary to xbin then it'll prompt you to update the su binary even though it's already correct. I found that in order to fix this I needed to create an .ext folder in /system/bin/ and copy .su to that folder. This happens with the current beta and the stable version of SuperSU, but it was fine for whatever the last stable version was (2.14?). I don't know if this is the new intended behaviour for older versions of Android or not.
[SuperSU] r00t4rd3d:
Hmm out of no where the DENY and GRANT buttons on the pop up are greyed out and I cant push either one. I re-flashed from recovery but still no go. Anyone else have this problem?

*EDIT*

I fixed it by turning off the "Tapjacking Protection" option.
[SuperSU] adipPL:
Does it work with lollipop?
[SuperSU] Megaflop666:
Latest Supersu? Yup
[SuperSU] adipPL:
Then I have problem on xpeira z with aosp link . I can use root in adb shell but when i flash superSU it "works" but su is not granting root for apps.
[SuperSU] Chainfire:
There will be new CF-Auto-Root's that do this when 5.0 images are released, with unofficial ports, ask the kernel devs.

Post in this thread http://xdaforums.com/apps/supersu/support-update-failures-t2907365 and provide the relevant logs.

http://su.chainfire.eu/#selinux-contexts-switching-when

Will check this out.

Some users on 4.1 have indeed reported this. I'm not sure why this path isn't automatically created on some devices, because it should. Unfortunately it is not reproducable on any of my 4.1 devices.

You probably need a patched kernel.
[SuperSU] XperianPro:
I have device with fully working Lollipop but not yet patched kernel,did you post how to instructions somewhere about patching?
[SuperSU] Mariner_1712:
2.19 Bug

The Clear All trash bin has been replaced with the refresh icon. Functionality is unchanged, but it's a bug nonetheless.
[SuperSU] ffejy462:
It looks fine in a 5.0 rom...(but I also have two refreshes on 4.4.x roms)

Nexus 7 5.0
[SuperSU] CHEF-KOCH:
Same bug here, installed via cwm but it's a low prio bug. But annoying if you press the wrong button and your logs getting wiped. ??
[SuperSU] USBhost:
Same bug here

Nexus 9
[SuperSU] dahawthorne:
Thanks. I did read the Busybox discussion, which is why I asked the question. Logically an amendment to system/xbin would count as an amendment to system.img, which would therefore prevent OTAs - just wondering if that's actually true. I guess I'll find out shortly when the January security update appears.

The reason that I don't want to flash the system image is that I can't be bothered with all the configuration resetting that follows it. The OTA is a straightforward simple process that leaves everything in place, so if systemless root allows that (even if I have to unroot, install OTA and then reroot) then it's a better process for me. The December 1st OTA was my first ever (all my devices have always been rooted) and the ease of update was a real pleasure.
[SuperSU] MrPib:
EDIT: please ignore the rest of this post. Berndbib hit the nail on the head in post#4330. I can reformat data in TWRP before flashing SuperSU, as long as I don't reboot in-between those two steps.

Original post:

Ok, this is where I'm confused. In this case, I'm starting with a stock N6 having encrypted Data. If I flash SuperSU, I'll have systemless root, and optional encryption -- but I'll still be encrypted until I do a Data reformat. But if reformat Data, I'll mess up root. I saw some posts where a Data wipe after installing systemless root messed things up pretty badly. So that's why I was planning on flashing the no-force-encrypt boot and then reformatting Data first, and then going back to stock boot (which won't reencrypt me unless I reformat Data again) so I can then flash SuperSU.

Thanks very much!
[SuperSU] TR2N:
No need for an OTA. Just flash the new system image over the previous one (in some cases with updated boot, modem or bootloader), if you are a Nexus user. Reflash TWRP, Kernel and SuperSU. Never waiting for an OTA, always dirty flashed the new images and never had any problems..
[SuperSU] shoey63:
So flash systemless superSU, wipe /data on newly baked kernel (which now does not force encryption) and flash it again :beer:

Edit: has anyone gone through the process of installing systemless superSU, doing a full unroot when an OTA is due, and updating OTA successfully?
[SuperSU] glauberlima:
XT1097 (Moto X 2014), Android 6 root achieved but...

Hi everyone!

I successfully got my Moto X 2014 (XT1097) running Android 6.0 rooted althought automatic boot image patcher didn't seem to work as I had to flash the modified boot image posted here along with SuperSU's:

http://xdaforums.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105

Coming from an untouched pure Android 6.0 with unlocked bootloader these are the steps I've followed:

First attempt:

- Booted through TWRP 2.8.7.1 without installing it (fastboot boot twrp-2.8.7.1-victara.img)
- Installed BETA-SuperSU-v2.65
- Wiped both Dalvik and Cache
- Rebooted
Result: Stuck at modified unlocked bootloader message. I've just waited 15 minutes just to make sure I really got stuck :)

Second attempt:

- The same steps from first attempt
- Flashed modified boot.img
Result: Worked!

So, since SuperSU failed (?) to automatic patch the boot image for my device, you can find attached my contribution: the untouched boot.img for further analysis. :)

Thanks
[MENTION=631273]Chainfire[/MENTION] for SuperSU
[MENTION=3813670]Junior Passos[/MENTION] for your modified boot.img
[MENTION=1722087]Dark9781[/MENTION] for your valuable tip on booting TWRP without installing it

All the XDA community members!
[SuperSU] dahawthorne:
Seriously? Did you even read my post before you replied?
[SuperSU] fdc77:
https://mega.nz/#F!WcUk1RAS!l27OTPY2rDHKGEeJdm3iYQ!6MMHkbgB

Here you can find originale MM boot image.

Thank you and happy new year
[SuperSU] shoey63:
Allow myself to quote, well, myself:p

As [MENTION=4544860]osm0sis[/MENTION] pointed out, the

toolbox_mount /system ro

command in the SuperSu zip update binary causes lifetime_write_kbytes to increase on devices without the appropriate kernel patch.

On Sony Concept rom for z3 (and maybe other MM roms for non-nexus devices) this is fatal, as it checks lifetime_write_kbytes as well as DM-VERITY, AND there is no kernel source to make the appropriate changes. (Omnirom zImage doesn't work when packed into the TWRP recovery.img)

By commenting out the "toolbox_mount /system ro" line, I can install systemless SuperSU without tripping a lifetime_write. Then I can receive OTA updates without issue, after a full unroot.

[MENTION=631273]Chainfire[/MENTION], can "toolbox_mount /system ro" be removed from the script in future releases without breaking universal support? Surely "mount -o ro /system" is enough.
[SuperSU] osm0sis:
Looked like he worked around that TWRP issue in 2.65 by adding a mount check to avoid the unnecessary remounts that trigger it. Is that still not the case?
[SuperSU] shoey63:
Didn't notice it. At any rate, latest twrp boots up with /system unmounted, so the toolbox_mount command still gets executed anyway. I'll try mounting manually in the twrp gui and see what happens..
[SuperSU] NZgeek:
If you only flash system.img, it'll reset the contents of the /system partition but should leave your /data partition alone. Given that all configuration info is stored in /data, you shouldn't need to reconfigure anything.
[SuperSU] evandena:
Fresh install of 6.0 on Moto X pure, 2.65 causes boot up to get stuck at Android/Moto splash screen. 2.64 is working via systemless method.

Man, this is a lot of work trying to get Capital One Wallet to work. Bugger can find root no matter what I try. Has anyone got it to work?
[SuperSU] Christendom...:
I have installed Chainfire's 2.65 SU System-less root and everything runs smoothly. Below are pictures of my Rom, the version of Android I'm using, and the proof of system-less root.
[SuperSU] RenatoXSR:
2.65 worked perfect on Nexus 6 (shamu) with stock 6.0.1 (MMB59K)

Hi all.

Just flashed stock 6.0.1 (build MMB59K) on my Nexus 6 (shamu), flashed TWRP 2.8.7.1 and then installed SuperSU v. 2.65 via recovery.

Everything is working great!

Thank you bery much,

r.
[SuperSU] TacoKing0218:
Did you flash the system or systemless build?
[SuperSU] berndblb:
2.6.5 is systemless. Period
[SuperSU] drewski_1:
Starting with 2.64, it could be either and is auto detected by the installer. Systemless can be forced though.

Sent from my 6.0 OG Shield Tablet
[SuperSU] DjDiabolik:
Simply question.. All version upper 2.52 posted in first page (and also on chainfire site) it's can be considered as alpha?
[SuperSU] RGSPro:
What would the command be to flash 2.65 with systemless forced in TWRP? I can't figure it out :(
[SuperSU] nathanchance:
Go into TWRP > Advanced > Terminal Command > Select in right corner and type echo SYSTEMLESS=true>>/data/.supersu then flash SuperSU 2.65. You can do that in any terminal emulator or from the adb shell but I think it is easier from TWRP.
[SuperSU] RGSPro:
Followed this to the t and the installer still says it is still installing via system. Do you have to install the zip from the terminal too?
[SuperSU] nathanchance:
You will need to flash UnSU to remove SuperSU from the /system partition then you should be able to type the command and flash it again to get systemless root.
[SuperSU] RGSPro:
Yeah that was the order. Run Unsu.zip, echo command in terminal, flash through install zip. The log says its installing in system and no warning on reboot. Running Chroma on angler.
[SuperSU] osm0sis:
Should only mount read-only unless needed.
[SuperSU] Mao04:
I think there needs to be a space between >> & /. Like so:

>> /
[SuperSU] nathanchance:
It shouldn't matter, I typed >>/ and it worked fine.
[SuperSU] RGSPro:
Tried both ways, still can't get it to force systemless. Any other method I should try?
[SuperSU] mielletseed:
As I understood this the installer script in the zip analyses wether systemless is possible or not (and then it uses systemless mode) but you can force it to system mode but not the other way...
[SuperSU] RGSPro:
What about editing the install script to always install systemless?
[SuperSU] mielletseed:
Maybe there is a restriction so the script uses system mode? I think you would mess it up when you try to force it anyway... but yeah, maybe you could edit that script.
[SuperSU] shoey63:
What about just reflashing /system and /vendor images and try again as per Chainfire's instructions? (seeing as you have inadvertently done a /system install)
[SuperSU] k2828:
cm13 nightly 01.02.2015/jfltexx: leads to bootloop

http://xdaforums.com/showpost.php?p=64602047&postcount=83
[SuperSU] RGSPro:
Isn't it doing that if I dirty flash my ROM and then run unSU? Also flashed the stock vendor img.
[SuperSU] shoey63:
unSu might not be catching everything on 2.65. It might need to be updated. Anyway, the time you have spent trying to resolve the issue could have been solved by now by reflashing images (unless you don't have access to a pc, or your internet is too slow to update the system apps)

Edit: This getting to the point of spamming the thread. You should of sought support from your rom thread in the first place. Please go there for further help from users who have had success.

Thank you.

---------- Post added at 10:50 PM ---------- Previous post was at 10:03 PM ----------

My bad - it's fixed.

Before installing SuperSU 2.65

~ # cat /sys/fs/ext4/mmcblk0p24/lifetime_write_kbytes
0

And after installing, and booting into /system

root@leo:/ # cat /sys/fs/ext4/mmcblk0p24/lifetime_write_kbytes
0

:)

Edit: It turns out that I had to format /system and reboot to recovery to set the counter to "0", then dd the system image and flash SuperSu 2.65 :good:
[SuperSU] RGSPro:
Didn't have access to my PC. Thanks anyways.
[SuperSU] osm0sis:
Chainfire said in order to get support here people need to have done the install over a clean ROM/system.img flash.

unSU is designed to remove up to 2.52. It shouldn't be necessary for 2.65, because there's no point in switching to systemless on a custom ROM that would include root and because Chainfire fixed the uninstall routines in the app so stock should be fine now too, but as far as I know, but the only thing it would be missing looks like /system/lib(64)/libsupol.so
[SuperSU] bobby janow:
Are you sure it is being installed as system root? Have you checked the SuperSU app? Under settings -> system what does it say?
[SuperSU] RGSPro:
It was being installed as system root, and verified in supersu settings. Not getting the this is not a rooted device notification in TWRP on reboot either.
[SuperSU] bobby janow:
I never get that notification. Well maybe once or twice some time ago after I flashed the Google image. Under system is it grayed out saying "Not currently available in system-less root mode"?
[SuperSU] RGSPro:
It is grayed out and says "SuperSU is already a system app"

Edit: Flashed the stock vendor and system images, still installing in system.
[SuperSU] PhrostB:
is this running well on cm13 nightly for galaxy s5 (kte - tmo)? for some reason even though i gave cyandelta root access in developer settings it still doesn't install through the app... so basically i have to boot into recovery to do nightly updates :[
[SuperSU] drewski_1:
The opposite. Checks if System is possible

http://xdaforums.com/showthread.php?p=64574093
[SuperSU] RGSPro:
Finally got everything sorted out. Here is the order I had to complete to get it all working.

Returned to full stock MMB29M minus the boot.img (used the mdb08k-systemless boot.img)

Removed SuperSU zip from Chroma's flashable zip (Don't know if this was necessary)

Flashed this Chroma Zip

Installed ElementalX

Install Gapps

"echo SYSTEMLESS=true>>/data/.supersu" in terminal

Flash BETA-SuperSU-v2.65-20151226141550.zip... Systemless finally worked this time

I wonder what part was tripping up the installer. Glad it's working now. Thanks for all who tried to help!
[SuperSU] ddrum2000:
How do you set the counter to 0 in the recovery? Also is this stock recovery or TWRP? Also you mentioned "dd the system image", is that any different from simply flashing the system image with fastboot?
[SuperSU] holydevil27:
I'm running Cataclysm on nexus 6p with super su 2.64. Is it safe to simply download 2.65 and flash it directly with TWRP or is it much more complicated than that?
[SuperSU] NZgeek:
That's odd. I installed SuperSU on the last of the CM12.1 nighties for jfltexx and it not only works fine, it also installed in systemless mode.

Note that it is normal to get one reboot during boot after installing SuperSU. For me, it happened shortly after entering my data encryption PIN. After that it all worked as normal.
[SuperSU] k2828:
2.65 beta works
[SuperSU] shoey63:
I formatted /system in TWRP recovery and rebooted to TWRP, and yes, using dd command to flash the system.img is the same as flashing with fastboot.

The only difference is you don't need a pc. You can store it on your sdcard and use the terminal in TWRP.

dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system

System path can vary between devices though.
[SuperSU] ddrum2000:
So how do you reset the counter then since mine is not 0? It's in the 4000's

So my understanding is...

1. Format system in TWRP

2. Reset counter in TWRP - not sure how to do this (see previous comment)

3. Use the dd command in TWRP to flash the ROM

I understand the concept but how do I find out which mmc block is the correct one? I have a Nexus 5X and I have a understanding of using the command line but I do not "know" all of the linux commends. Thanks a ton.
[SuperSU] Alxoom33:
Yes, if 2.64 is installed correctly just flash 2.65. No need to repeat the adb terminal commands. TWRP, like Peparidge Farms, remembers-sh.[emoji2]
[SuperSU] GieltjE:
Just found out the hard way that it is a bad idea to install 2.65 on a LG G3, this will cause a boot certificate exception and requires a full stock restore to fix.