yashsingh1/xdaforums huggingface dataset:
[SuperSU] jackdubl:
Hmm. Editing the dpi seems to break it. But everyone is posting that they can change dpi and AP still works?
[SuperSU] fprhqkrtk303:
It seems boot image patcher can't decompress lz4-compressed ramdisk. Boot image of G3 stock MM uses lz4, so

check_zero_def "- Decompressing ramdisk" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel [B][COLOR="Red"]--ungzip[/COLOR][/B] /sutmp/ramdisk.packed /sutmp/ramdisk"

this command gives me an error: "--- Failure, aborting"
[SuperSU] Ch3vr0n:
Nothing new, chainfire has set stated in one of his earlier posts that currently only gzip is supported.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Ingenium13:
I think you can change that with an adb command without root, but I could be wrong. I would go that route if I were you.

For tethering, because I didn't want to have to edit build.prop after every system update, I just put a setprop command in a su.d script. Seems to work just fine. Might work for the dpi as well if you want to make the change there instead of with the adb command.

Sent from my Nexus 6P
[SuperSU] ShrekOpher:
Trouble with v2.66 beta.

I flashed the 2.66 beta with TWRP on my Note 4 (910T). after reboot I lost signal and IMEI. I am not sure what changed, but it looks like something from 2.65 to 2.66 broke the cell signal on the Note 4.

I am running stock firmware 5.1.1 DOK2

Just wanted to let you know.
[SuperSU] milojoseph:
I think 2.66 cause many problems with Samsung deviced

Sent from my SM-G900T powered by AllianceROM

and boosted by speedy kernel

Lollipop ?
[SuperSU] shaggyskunk:
Did you restore a Nandroid & Flash 2.65 before reboot?

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] ShrekOpher:
I restored a previous backup that was working on 2.65. It recovered fine. I didn't permanently loose my IMEI, but for some reason 2.66 is not working on stock firmware on the Note 4.
[SuperSU] shaggyskunk:
Did you flash 2.65 for systemless root?

Sorry if it's a dumb question - I'm just trying to catch up with the latest from Chainfire - I'm running an AOSP custom rooted 6.01 Rom - I'm not so much interested in systemless root as in the patches for SELinux Enforcing...

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] ShrekOpher:
Yeah I flashed the 2.65 systemless root. It is the only one that will work on Stock 5.1.1 DOK2 firmware. to my knowledge. ..
[SuperSU] NZgeek:
It'll help Chainfire a lot if you can grab logs. They should contain what's going on and help to narrow down the problem.

You can use an app like SysLog to capture the relevant log files.
[SuperSU] chazall1:
All working great here. Great work.
[SuperSU] ddominator:
2.66 working on stock Nexus 5x 6.01 MMB29P (January 2016 update). Thanks.
[SuperSU] droppe:
Not a pro at this, but I used the Nexus Root Toolkit, and was able to get my 64gb nexus 6 running with the MMB29K rooted, and able to update /system/build.prop. I then tried the same on my other phone 32gb Nexus 6 with the MMB29K rooted, but I am unable to edit the /system/build.prop file. The /system will not allow me to save the the build.prop file. it says not enough memory. Is there any way that my 32gb phone has s=on? I am now on my 4th trip through flash stock + unroot to get the phone working again. because messing with the build.prop in /system when it won't allow you to save is not working well.

The main difference between the two is that the sim card is in the 64gb phone and not in the 32gb phone. but I would guess that should not make a difference on access to /system under root.

Any help would be appreciated.
[SuperSU] Pkt_Lnt:
This should help.

http://xdaforums.com/showpost.php?p=64208563&postcount=3393
[SuperSU] droppe:
So are there any suggestions of files to delete to allow for this update? I just tried to root the MRA58R on the 32gb Nexus 6 through NRT V2.1.0 and it worked, and I was able to edit the /system/build.prop file just fine. So if it is just space preventing update of the MMB29K build, I would just like to know what none needed files to delete so I can update the file /system/build.prop. Thanks
[SuperSU] purejoy:
My device sometimes loses root after reboot.Supersu says no binary installed, however reboot again can bring ROOT back.

Moto X 2014 XT1095 stock 6.0 ROM System version: 24.11.18

ROOT: 2.65 systemless mode
[SuperSU] Apocalypse~:
I have read through the thread but I'm still a bit confused. I, currently have a rooted Nexus 6P on SuperSu 2.52 running Cataclysm ROM. I don't want systemless root as it is useless to me. If I flash 2.66 over my existing setup, will I retain non-systemless root? Also, is there an issue I should be aware of (like issues on Samsung devices)?

Sent from my Nexus 6P
[SuperSU] snovvman:
Interesting.. I saw this when SuperSU was on 2.62. I couldn't find a solution so decided to go traditional root. I guess the problem still persists for some. It would be nice to know the cause.

Have you tried 2.66?
[SuperSU] shaggyskunk:
Dup

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] NYLimited:
Yes, it will update what you have. I'm not personally aware of issues with different devices - I simply installed the update through recovery. If you want to be totally safe, make a backup with TWRP before upgrading. :)
[SuperSU] shaggyskunk:
Could you clarify "update what you have" - Are you saying that you will still retain system root but with the updated version of SU - Or flashing 2.66 will update your device to systemless root?

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] NYLimited:
I have not played with systemless root. My device was running SU 2.52 (beta) installed in system. The current beta will install the same way your previous one was, in other words, if you had SU installed in system the new one would install the same way by default. The only way to go from system to systemless (as I understand it) is to do a complete unroot before trying to go systemless. I don't believe you can switch accidentally. Keep in mind that my device and Android version is different from yours but the above is the intended behavior.
[SuperSU] shaggyskunk:
Thank you for the clear response - It's a bit of a rat's nest looking at these changes for the various devices - Those that require systemless to get Root Access and those who are looking for the patches for Samsung devices and are already rooted in the previously conventional method - Thanks again :)

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] Tigana:
I have 2.62-3 systemless root installed. I thought OTAs were supposed to work with it. For the January Security update when it asks me to restart to install the update, it goes right into TWRP. Anybody know what that's about?
[SuperSU] corkiejp:
You would need stock recovery (not TWRP) installed, also probably stock boot image as well!
[SuperSU] hardcore_sac:
Hi guys!

I have a Nexus 6 with latest factory image, i have boot.img from Chainfire and Super SU v2.66, and everything is ok, but i have a crazy battery percentage, like 3452%.....

Anyone know how to fix this?

Thks in advance!

https://www.dropbox.com/s/pl4uhwz5l9jaeow/2016-01-06%2018.33.11.png?dl=0
[SuperSU] nathanchance:
Flash the boot.img from your latest factory image then flash SuperSU 2.66. A separate boot.img is not needed for root anymore, it can be done with the stock one.
[SuperSU] RandomPooka:
Don't use the boot.img from Chainfire. It's way outdated. From what I understand, 2.66 auto-patches the boot.img now, so you should be able to just fastboot the original boot.img and then flash SuperSu 2.66

-- [MENTION=6842057]nathanchance[/MENTION] is a ninja --
[SuperSU] hardcore_sac:
Thanks, i will do that!

---------- Post added at 12:22 AM ---------- Previous post was at 12:03 AM ----------

Done!!! Problem solved.

Thank you all for the time to help me.
[SuperSU] xd4d3v:
Hi Chainfire

a couple of feature requests

1) would it be possible to add some sort of popup generated by the supersu app when you try to modify the /system ?

I think this would help people without an understanding of how the systemless root works avoid unnecessary modification of /system

2) a built in unroot

not sure whether this is possible without the use of a computer, but ideally re-flash the stock recovery and stock boot.img when selected for preparation when an OTA is available.

even better would be to hook with the OTA system and popup automatically when there's an OTA.

thanks
[SuperSU] H4X0R46:
How exactly do you do the terminal command? Do you just navigate to the folder with the SuperSU zip in TWRP and type that terminal command and it installs? I'm already using 2.66 systemless, but I'm not sure how terminal commands like that work exactly. Thanks to whoever can answer this real quick! And chainfire, awesome work man! It works FLAWLESSLY! :D
[SuperSU] nathanchance:
You go into TWRP > Advanced > Terminal Command, then select the current folder (it could be the root folder, it doesn't matter). Then type the command(s) in the text box one by one. You don't need to worry about it since you are already on systemless root.
[SuperSU] bijixda:
Flashed 2.66 version with systemless root

/dev/block/loop0 /system/xbin ext4 rw,seclabel,noatime,data=ordered 0 0

work nicely on stock Android 6 on Nexus 5

and it seem my battery saving app run well
[SuperSU] Zer3s:
just want to report in:

Nexus5(hammerhead) with 6.0.1(mmb29k) and SuperSU2.62-3.

Flashed 6.0.1(mmb29k) boot.img/recovery.img.

Completed January security-patch OTA (mmb29s).

Reflashed TWRP2.8.7.1 and SuperSU2.66.

Works.
[SuperSU] shaggyskunk:
It looks like SuperSU 2.66 does install as Systemless on my device running Android 6.01 (Nexus 7) Even though the N7 was rooted and running a Custom Rom with SuperSU 2.52

But I think as expected on my Note 3 running SlimLP 5.1.1 with SuperSU - I Flashed SuperSU 2.66 and on this Device SuperSU is running as a System App.

I'm trying to figure out how to get SuperSU to install as a System app on devices running Android AOSP 6.01 instead of Systemless - if that makes any sense?

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] b4nd0ler0:
Cannot sideload SuperSU 2.66 on Nexus 9

Hi,

I'm stuck on the last step rooting my Nexus 9 Wifi (Android 6.0.0) following the instructions from [WIP][2016.01.03] Android 6.0 Marshmallow [v2.66]

Updated Android Platform tools on Windows 7. adb version is 1.0.32

Flashed Marshmallow 6.0.0 factory image MRA58K flashing all images BUT USER DATA. (New OS version boots ok)

Flashed ChainFire's boot image volantis-mra58k-boot.zip from here

Booted TWRP 2.8.7.1 with "fastboot boot twrp-2.8.7.1-flounder.img", went to Advanced > ADB Sideload

Tried to sideload SU 2.66 from here with command "adb sideload BETA-SuperSU-v2.66-20160103015024.zip"

I get "ERROR: device '(null)' not found"

"adb devices" and "fastboot devices" return no device at this point.

Rebooted and repeated but same outcome.

Any ideas?

Thanks
[SuperSU] thaidroid:
Adaway systemless Root

I was running a really old version, Anyhow the latest version supports both MM and SU2.66 Make sure you install the Zip before the app to get systemless adblock.

http://xdaforums.com/show....php?t=2190753
[SuperSU] corkiejp:
A. Why didn't you flash the latest 6.0.1 Factory Image.

B. You don't sideload supersu zip, you install it from TWRP.

No need for modified boot under 6.0.1 the SuperSU V2.66 will modify it on install.

Get the latest SuperSU v2.66 and instructions from here
[SuperSU] b4nd0ler0:
Thanks a lot. I'll try again.
[SuperSU] jackdubl:
Why is systemless useless to you? It's just root.
[SuperSU] jackdubl:
Didn't you just make extra steps for yourself? If your flashing stuff via computer, why not just flash the system/boot for the update? Instead of flashing boot/recovery, then OTA, then flash recovery again, just flash system and boot, keep your recovery, and skip needing the OTA.
[SuperSU] jackdubl:
Never saw this before. Also never had an issue with Adaway and systemless root. Also never heard of anyone else having an issue, though I stay mostly in the Nexus forums. Do you HAVE to flash this before installing Adaway?
[SuperSU] corkiejp:
If you want to keep your system partition untouched, yes flash that zip. Otherwise your hosts file will be written to the system partition.

The link above does not work for me and you can get the zip here.
[SuperSU] sabret00the:
I tried to install SuperSu 2.66 but upon booting and loading the SuperSu app, it says I don't have root. I'm guessing 2.66 isn't compatible with the stock LG ROM on the D855. Has anyone else found this and will I need to reflash the ROM before I try 2.55?
[SuperSU] bobby janow:
Can't you manually uninstall the layers for now? It's a little pain but not awful.
[SuperSU] Tigana:
Thanks! But I flashed the stock recovery and the update seemed to be working but it failed with a red triangle inside an android while it was installing. I'm not getting notified to install the update anymore either. I don't think I care though.
[SuperSU] Erik Rye:
Twrp error with SU 2.66 'zip corrupt' when flashing over SU 2.65... I reflashed SU 2.65 zip with no errors. what to do if/when SU zip is corrupted?
[SuperSU] BenPope:
Perhaps the zip is corrupt, did you check the md5sum?
[SuperSU] 1BadWolf:
Read post #'s 385 & 386 :thumbup:
[SuperSU] jetsaredim:
Any update on compatibility with L (5.0)? I noticed that previous posts in this thread say that the BETA 2.19 works with L, but I'm not able to make it work... I'm sure I'm missing a step somewhere. I just flashed the Google factory image for L onto my 2012 Nexus 7, installed CWM and attempted to flash both the stable (2.16) and BETA versions of SuperSU with no success. I say no success, but it installed just fine, just doesn't seem to allow root access to any apps (TiBu, etc.) and running SuperSU reports the following:

Similarly, TiBu reports that it can't work properly.

I have installed the BETA zip file a couple times and not gotten any different....

Any suggestions would be appreciated.

Thanks...

- Exact device model

nagasaki

- Exact firmware version

stock 5.0

- Exact Android version

5.0

- Exact SuperSU version

2.19

- Interfering apps

??

- Update methods tried

Sideload or install zip from /sdcard within CWM

- What kind of root are you left with?

Root is lost. Apps cannot get root anymore, you cannot get root using "su" from an adb shell, etc

- Logs

sulog.txt & logcat.txt attached
[SuperSU] JulGer01:
I'm pretty sure that it takes more to root your phone then just install SuperSU...

Gesendet von meinem GT-N7000 mit Tapatalk
[SuperSU] Pkt_Lnt:
You need one of the patched kernels posted earlier in the thread.
[SuperSU] claytonjn:
Just installing the SuperSU apk does not root your phone, however flashing the SuperSU zip is typically all that is required. Sometimes a modified kernel is needed in addition.
[SuperSU] jetsaredim:
There's 40+ pages of posts here. Can you give me a little bit of a hint? I saw the Google+ post from CF listing the kernels for various devices, but that was only Nexus 5, 2013 Nexus 7 (razor) and ADT-1 for LPX13D. The device I have is the 2012 Nexus 7 (nagasaki) and I just noticed that the build is marked LRX21P. So, I'm guessing that none of those kernels will apply to this situation...?
[SuperSU] scoobyjenkins:
Agreed. I've rooted several Samsung devices just by flashing TWRP via odin with auto reboot unticked, booting straight to TWRP and flashing a SuperSU zip. Then installing Busybox (and binaries) for good measure!

Tapatalked that shiznit.
[SuperSU] Pkt_Lnt:
That was the post I saw. Check your device forum to see if someone has a patched kernel, otherwise you will need to wait for Lollipop.
[SuperSU] XperianPro:
Whats the deal with root in Android 5.0?

I patched kernel,set Selinux to run in permissive mode and supersu still does not work... :crying:
[SuperSU] JulGer01:
Are there even ways to root lollipop already?

Gesendet von meinem GT-N7000 mit Tapatalk
[SuperSU] ffejy462:
Nearly ready to go...

http://xdaforums.com/showthread.php?t=2931064

Running this rom since last Thursday on my grouper. Runs great. Actually, surprisingly, a few KitKat kernels are working. Using faux123's v26u with great results.

lg g2 xdabbeb's vs980 v2.2.0

---------- Post added at 02:31 PM ---------- Previous post was at 02:29 PM ----------

Yes. I believe chainfire had it done within hours of the launch of Nexus 9.

lg g2 xdabbeb's vs980 v2.2.0
[SuperSU] jetsaredim:
FWIW, using CF-Auto-Root fixed my kernel issue and I'm able to use root now. Just download from the cf-auto-root website.
[SuperSU] mbirth:
Does CF-Auto-Root for Nexus 9 LRX21L also work for LRX21Q? Or does it install an older kernel?

EDIT: To answer my own question: Yes, it works.
[SuperSU] a g bell:
Anyway to root stock L on nexus 5 ?2.19 not installing bins
[SuperSU] mbirth:
Boot the hammerhead image from here. It will install SuperSU 2.20.
[SuperSU] Craiq:
is this the solution to set selinux to permissiv?

because i saw it flashed a new kernel

btw it works with the n5 factory images
[SuperSU] kenpen:
Nice
[SuperSU] gannjunior:
Hi

ho to install the latest autoroot zip with 2.20 using TWRP 2.8.1.0 ?

If I run it in "install" I get an error.

thanks

ciao!
[SuperSU] mbirth:
As far as I understand it's patching the installed kernel and flashing the patched version.

Boot the CFAR image, like in "fastboot boot CF-Auto-Root-hammerhead-hammerhead-nexus5.img".
[SuperSU] spiral777:
kexec

would there be a way to get kexec/ multirom working with systemless root?

and would flashing a modified boot image to a rom also effect the kexec hardboot partch of the kernel?
[SuperSU] jcadduono:
Hi [MENTION=631273]Chainfire[/MENTION], would you please add a command to sukernel binary that patches a pre-extracted ramdisk with everything necessary for systemless root?

ex. (after doing supolicy on /tmp/someramdisk/sepolicy)

sukernel patchrd --systemless /tmp/someramdisk

Also support for extra ramdisk compression formats would be nice. Something like this:

http://pastebin.ca/3321613

It's pretty much impossible at the moment to install SuperSU on some Marshmallow ROMs using lzma or xz compressed ramdisks in their boot images.

I suppose if ramdisk is unsupported fallback to system mode install would be the best option.
[SuperSU] Rix70:
Guys please, witch is the better version of SU for M9/MM ?

Thanks
[SuperSU] BestWorker:
Tried from 2.62 to 2.66 on shamu stock mmb29k and mmb29s. Apps got root, but in File manager HD, when I try to modify files in /system, they become empty. Other file managers also got errors, when modifying /system. Is there any suggestions?
[SuperSU] sabret00the:
SuperSu 2.52 caused the D855 not to boot at all. Is it possible it tried to do a systemless root and didn't pick up the custom kernel patch file?
[SuperSU] Erik Rye:
Issue was ES file downloader. the zip installs fine when I used chrome to download the file.
[SuperSU] nkk71:
1- the current versions of systemless root make changes/additions to the kernel, but you're not "flashing a modified boot img", so kexec is not broken, since the kernel is in essence the same as before

2- yes it is possible for systemless root (tested with 2.65) to get it working on multirom, however some changes were needed; we're still debugging the problem to try to narrow down the issue, to get it to work with as little changes as possible

EDIT: I'll just mention the problems encountered in case [MENTION=631273]Chainfire[/MENTION] wants to be aware of them

a) line 1170: dd if=/dev/zero of=$BOOTIMAGE bs=4096

since MultiROM creates a symlink, the above command actually starts nulling out a "dummy boot.img" file, which basically continues on, untill all free space in internal storage (or external sdcard where applicable) is filled out

b) when MultiROM-TWRP finishes installing SuperSU, the fake /data is still "busy" (some open file or something else keeping it busy), since it's busy, it can't be unmounted properly, and the real mount points don't get restored

at that point mrom injection will fail

using a lazy unmount helped alleviate that (as a workaround), but obviously not the best solution

c) the setprop sukernel.mount 1 (in launch_daemonsu.sh) doesn't trigger the mount properly, workaround was to mount it in the launch_daemonsu.sh using "mount -t ext4 -o loop /data/su.img /su" instead of the setprop

EDIT2: thanks [MENTION=1162986]Captain_Throwback[/MENTION] for the reminder

d) the attempted remount read-only, will cause a bootloop; workaround: had to comment that out

just FYI, but I'll check more thoroughly when I get a chance
[SuperSU] spiral777:
multirom

wow thnx for the writeup, i havent gotten an answer back yet but do you think xtrafactory for nexus 6 would work if flashed as a primary?

http://xdaforums.com/nexus-6/development/rom-xtrasmooth-1-0-xtreme-battery-nexus-t2998811

im running daniels last xtrasmooth now
[SuperSU] Idan73:
When you say you'd be hard pressed to call it a samsung issue, you're probably looking from a standpoint of how it behaves on s6 and s6 edge, that you can reflash full stock firmware and no worries, but maybe you're unaware that on note5 and edge+ the issue is much worse.

Now we can never go back to full stock once we mess with the phone, even once. Reflash in full stock still leaves u with deep sleep issue, so once we root first time, we are forced to root forever, or at least flash modified or custom kernel, if we want our phone sleeping.

This seems less and less a bug, and more and more intentional...

And what [MENTION=336863]garyd9[/MENTION] said http://xdaforums.com/showthread.php?p=64648054 about adapting next version for note 5 as well, by adding aditional line to the script if feasible.

Note 5 ?
[SuperSU] sabret00the:
So I've been doing a ton of research and it appears that people are only able to get root on their stock G3 (D855) by changing their SELinux status to permissive.
[SuperSU] Manh_IT:
[MENTION=631273]Chainfire[/MENTION]

Add fix deepsleep for System mode :p

...
ui_print "- Post-installation script"
rm /system/toybox
rm /system/toolbox
LD_LIBRARY_PATH=$SYSTEMLIB /system/xbin/su --install
[COLOR="DeepSkyBlue"] if ($SAMSUNG); then
ui_print "- Fix Samsung deep sleep issue"
mkdir /system/su.d
chmod 0755 /system/su.d
cp_perm 0 0 0700 $COM/000000deepsleep /system/su.d/000000deepsleep
fi[/COLOR]
else
ui_print "- System-less mode, boot image support required"
...
[SuperSU] AtrumDelorox:
Did you happen to get an answer? I've also been curious about this. It'd be really convenient if it was possible.
[SuperSU] Rix70:
Guys sorry, i'm italian and do not understand good sometime..

I've Viper rom 4.1.1...after update SU (2.64) twrp get a message that the phone is not rooted....exist a solution for this issue?

Thanks
[SuperSU] Ja_som:
No, there is no solution, TWRP does not know, that your device is rooted with systemless method, just ignore that message and do not let TWRP to root your device.
[SuperSU] xTPTBx:
Alright I have a simple question which I literally cannot wrap my head around. Why can we not use ADB Sideload on a Stock N920C to install the Systemless-Root Supersu-Update package?

I would presume, the Custom Recovery could do the same.

Hence if this was achievable we would end up getting a Stock Rooted Note 5 without tripping knox.

Go easy on me and there is no need to burst into flames. I'm still understanding certain concepts. A bit of help would be nice.
[SuperSU] shaggyskunk:
Just curious - if you let TWRP root the device - What gets installed - SuperSU 2.66 as a System App - or does the sky fall?

Sent From My SM-N910W8 Running CMRemix 6.01
[SuperSU] Ja_som:
AFAIK v2.46 with binaries will be installed in system
[SuperSU] Sugarkryptonite:
I'm running 2.61 beta.

I was wondering if updating to the latest January security update will remove root, or the system less method has now bypassed that? I have the update available on my phone, but just wanted to know that before I do the actual update.

Thanks
[SuperSU] robertogl:
I've flashed v2.66 on Cm13. I've root access but no SuperSU app. Every app can use root without asking for it. I've the folder '/data/app/eu.chainfire.supersu-1 with 'base.apk' in it, but no supersu in the app drawer...

If i try to install from Play Store, it gives me error (-505, other apps are ok), if i try from apk it says that it can't install.