yashsingh1/xdaforums huggingface dataset:
[SuperSU] magnamentis:
yes, i was not apple to acquire root yet this part has been deleted now that i know it was not welcom to mention an alternative, sorry, but it was not visible since all posts referring to that were deleted before i was able to read them

---------- Post added at 01:17 AM ---------- Previous post was at 01:16 AM ----------

TWRP 3.0.x.x working on my nexus 6

EDIT: just see a lot of stuff deleted and not sure if the above mentioned would cause such a thing, i mean it simply answers the question in useful manner.

sometimes it's not the best way to just remove posts without mention of reason, some hint or keyword. so i thinkg for those seeking root on N

it's useful info and an extra thread for that would be overkill, especially considering that i don't use that, just been reading and seen it working

for others.
[SuperSU] bouchigo:
Look at the last answer in this post for the "mention" you are inquiring about: http://xdaforums.com/showpost.php?p=65766230&postcount=5300
[SuperSU] drewski_1:
On Shield Tablet, MM broke custom recovery because of bootloader changes. Still no Official TWRP, but are a couple of unofficial versions, though both are a little buggy / laggy

Sent from my Moto X
[SuperSU] mikereidis:
OK, :)

I hope Google has left some openings for a system-less, enforcing SuperSU for N.
[SuperSU] Nino1238:
Thks for yr reply
[SuperSU] ManikandanGuru:
What is this?

https://www.androidfilehost.com/?fid=24438995911976313

I don't know if I can post this link. Please forgive me.
[SuperSU] LoverBoy2415:
Dont know ... [MENTION=5385900]manikandanguru[/MENTION] ..but It looks like by the Name , Supersu 2.68 for N developer preview.. But [MENTION=631273]Chainfire[/MENTION] haven't released anything officially for N so far ..
[SuperSU] Chainfire:
http://xdaforums.com/apps/supersu/unofficial-supersu-v2-68-android-n-t3333423
[SuperSU] ohad129:
What ever i try its not works for me i dont know why i lost my twrp even i revert to 6.0.1 and did the root and did root +custom recovery flash and after that through the beta push did the update and its gone

What id weird that if i try to flash through NRT the twrp v 3.0.0.0 is there but if i do it manualy i get the android with the red triangle any help please
[SuperSU] ManikandanGuru:
Thank you so much for clearing it.

I am gonna try it now and lets see. Hurray.
[SuperSU] LoverBoy2415:
:) ..Good Luck [MENTION=5385900]manikandanguru[/MENTION] ;) [emoji106] [emoji111] ...
[SuperSU] CptanPanic:
So if it determines you have a modified boot image then it will be systemless? Of do you just have to flash SuperSU in twrp, and it will automatically install this boot image now?
[SuperSU] alwaysbelieve1:
I can't seem to figure out how to flash 2.68. It keeps giving me file corrupt error. I don't have the box check to verify the file either. So I'm not sure why this keeps happening. I downloaded the file twice and the same thing occurs in TWRP. Anyone have any advice?
[SuperSU] Chainfire:
Regarding N Preview: I've made a lot of progress, but it's not working yet. I will be away for the next 24 hours. I'm quite confident it will be working within a few days.
[SuperSU] ohad129:
I wonder how we going to flash it if the prob its that twrp is also a prob
[SuperSU] rgavioli:
You saved me lots of lots of hours...

It worked. After 20 loops with 2.68, installing the 2.65 again fixed the issue.

Thanks!
[SuperSU] magnamentis:
that's the post which made me make the EDIT but it does not mention what it refers to because all reffered posts were deleted which is what i

mentioned. since we're all here to get the best out of our device i can't see any helpful reason why one should not be allowed to mentione something that works if it's not available in the thread one posts, this is what we do every day, hinting and posting helpful links if it's not

in competition with the dev's work. unavailable features and pieces of software cannot compete, hence if this is an exception it would be

the "bonus for the famous"
[SuperSU] Chainfire:
You are in the SuperSU BETA thread in the SuperSU subforum.

You can talk about whatever you want in the appropriate place. Anything not about SuperSU is quite obviously off-topic for this section.

Your understanding is not required. Your agreement is not required. Your cooperation is requested.

This part of the forum is my house, where you will abide by my rules. This is not a debate, if you do not agree, you can post about it elsewhere.

If you cannot respect the simple request to keep this (and all other things off-topic) out of here, then please simply do not post here.
[SuperSU] ManikandanGuru:
I didn't worked. Stuck on Bootloader Google Logo. LOL

Not a surprise though
[SuperSU] LoverBoy2415:
Hmmm...So You should Wait Till [MENTION=631273]Chainfire[/MENTION] Release it officially then..:) ..Just some more days I think.. See the Previous post by #Chainfire for details :) ..
[SuperSU] magnamentis:
absolutely, my original post was basically ASKING if that refers to this topic and this is the answer i was looking for.

and yes my agreement is not needed, of course not, but still i feel free to provide a point of view to "consider" not to agree

your answer is clear and since all the previous posts were deleted, only now is the moment i KNOW for sure that indeed my suspicion

that mentioning that was not welcome, not problem, this is your good right, exactly like my good right is to ask (make sure)

what is meant and how it is. only think i can't see ( not needed that i see it LOL i know) is why this happens in such a manner.

a friendly reply like, yes that referred to that" would have made me delete my post which i do now if has not already been done

hence full cooperation, just whenever possible not taking things personal.

EDIT: [MENTION=631273]Chainfire[/MENTION] i have altered my original post as per your request according to you clarification.
[SuperSU] ManikandanGuru:
Yeah sure. Thanks for the update. Hopefully this weekend...! :good::good:
[SuperSU] LoverBoy2415:
Yeah.. many Users Are Waiting for the N Release only...
[SuperSU] AnSnarkista:
I was about to ask a long question, but while I was writing, I solved my problem (2 days reading this thread and trying things).

I have a MotoG 2015 2Gb, and I couldn't get supersu in systemless mode installed, and was because I reboot into system after flashing official firmware, and I think that was the problem.

Another question, and just for knowing, is that I can create a .supersu file, write in it SYSTEMLESS=True (or False), move to my sd card, and then with TWRP move to /data instead of using adb shell "echo SYSTEMLESS=True>>/data/.supersu if I don't have any notions about adb.

Thanks a lot!
[SuperSU] avs333:
forcing rarely hits, sorry, I beg you cool down and it'd be decided for sure
[SuperSU] Administr4tor:
I am having troubles,

I installed all files as instructed from CUSTOM recovery but there is no root,

I installed twrp and then installed all files through recovery but noW PHONE IS IN BOOT LOOP with error " custom warranty bit - kernel"

i reinstalled STOCK FIRMWARE, 5.1.1 , now phone is good,

how to root??

g900w8 5.1.1 G900W8VLU1COI4_G900W8OYA1COI4_FMC
[SuperSU] H4X0R46:
You on Marshmallow? Try a custom kernel, just a guess! I know Nexus phones have a verity check in the kernel that gives errors when the system is at all modified, try a custon kernel that has dm verity disabled. Someone correct me if I'm wrong, I prefer Nexus stuff! I use systemless root on a Nexus 6!
[SuperSU] vladashram:
I apologize for this. I won't do so again. I did it primarily because I wanted to keep the list of people spamming the thread asking for Root in Android N down.

I was also unaware of any issues you had previously with the developers of the project I linked to. I sincerely apologize for any grievances I might have caused.

I am glad there in an unofficial SuperSu available with Sepolicy set to Permissive to provide root for those who really need it on N until you are able to get it working. I have been a fan of you project from the moment I found it.

On top of purchasing SuperSu Pro(which I did years ago) and not mentioning projects-that-should-not-be-named ever again, is there anything I could do to help support you and make up for the mistake I made?
[SuperSU] bournaze:
Hello

I've generated the logs you want. Notice that I have the same problem with Syslog than Titanium : when Root namespace separation is enabled the app cannot obtain root... So i've generated logs with and without this option...

Thank you for help

David
[SuperSU] Chainfire:
Good news everyone!

Everything appears to be working now on N preview. Just need to do a little bit more testing, cleaning up, tweaking, etc.
[SuperSU] Phrodini:
Good news indeed. Thank you
[SuperSU] milojoseph:
One thing that is always on my mind is if the people who will soon have control of this app will have the same dedication as you to continue to develop SuperSU till it's no longer needed (which is never).. I appreciate your work chainfire!!!
[SuperSU] zarocks:
you're ****ing awesome

Soda!!!! :)

4G4799878F638772F

Enviado desde mi Nexus 6P mediante Tapatalk
[SuperSU] qtipbailey:
Who else read this in Professor Farnsworth's voice?
[SuperSU] GROGG88:
I prefer to change the header to 'Hi Everybody' and read it as Dr. Nick. :silly:
[SuperSU] :
Awesome news!!! You're a gentleman and a scholar. ?
[SuperSU] force70:
Sorry i thought that would have been sort of obvious.

Nexus 6P TWRP thread here on xda

Sent from my Nexus 6P, Note 5, Note 4 or Nexus 6
[SuperSU] Chainfire:
N Preview builds of SuperSU: http://xdaforums.com/apps/supersu/wip-android-n-preview-t3335726

Let me know how it works out!
[SuperSU] hlxanthus:
Working well so far on shamu.
[SuperSU] eradicator006:
2.68 fails on my G3. 2.67 works great. Any ideas on this error? I am using TWRP 3.0.0

magic: [ANDROID!]
kernel: [7958488] (7958528) @ 0x00008000
ramdisk: [1079083] (1079296) @ 0x02000000
second: [0] (0) @ 0x00f00000
tags: @ 0x00000100
page size: 2048
unused: [0x00077000] [0x00000000]
dtb(?): [487424] (487424)
name: []
command line: [console=none androidboot.hardware=g3 user_debug=31 msm_rtb.filter=0x0]
extra command line: []
id: [0xc43af941f3c6c309df5c664777b2416dad9d6a89000000000000000000000000]

- Calling user boot image patch script
CANNOT LINK EXECUTABLE: could not load library "libcutils.so" needed by "sh"; caused by empty/missing DT_HASH in "libcutils.so" (built with --hash-style=gnu?)
--- Failure, aborting
[SuperSU] hamada samir:
Where the update v69?
[SuperSU] Ch3vr0n:
If you bother to read the post above you, you'd know. 3 posts above yours.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] Linux23:
Thanks for all of your hard work and effort my good sir.
[SuperSU] spevil07:
[MENTION=631273]Chainfire[/MENTION]

I have no root access to change files like build.prop or mixer_paths.xml.

I can access and edit them but when I will exit the files I have the message: Error pipe

Gesendet von meinem Nexus 6
[SuperSU] Chainfire:
I think the wrong "sh" command may be called here.

Can you make sure /system is mounted, then "adb shell" into TWRP, and test which of one of these commands works and which doesn't ?

sh -c id
/sbin/sh -c id
/sbin/busybox sh -c id

also, what is the output of...

echo $PATH

You forgot to include information like which phone, which firmware, which app this is, system logs (dmesg, locat), etc
[SuperSU] eradicator006:
Looks like they all work?

~ # sh -c id
uid=0(root) gid=0(root)
~ # /sbin/sh -c id
uid=0(root) gid=0(root)
~ # /sbin/busybox sh -c id
uid=0(root) gid=0(root)
~ #
[SuperSU] Chainfire:
Well, that is certainly weird. And if you try them without the "-c id" part? Just opening a new shell?

Also, what does "echo $PATH" output ?
[SuperSU] eradicator006:
They all open a shell. No errors

~ # echo $PATH
/sbin:/system/bin
[SuperSU] eradicator006:
Figured out the problem.

Remove LD_LIBRARY_PATH=$SYSTEMLIB from before 'sh /data/custom_boot_image_patch.sh /sutmp/boot.img' in update-binary

This works for me:

if [ -f "/data/custom_boot_image_patch.sh" ]; then
check_zero_def "- Calling user boot image patch script" "sh /data/custom_boot_image_patch.sh /sutmp/boot.img"
fi
[SuperSU] dhruvdave:
Will this work on samsung j7
[SuperSU] spevil07:
Its N6 with N, i don´t make logs, its my mistake! I´ve forget them.

i´ve tried to change settings in mixer_paths.xml in System/etc with ES File Explorer :(
[SuperSU] droidfta:
I tried flashing this over 2.67 on my lg g3 running rooted stock marshmallow 6.0, but it gives me error 620 boot certification error and I have to restore the previous boot partition. is this because the bumped portion is getting altered on the patching side, is there a way i can go from 2.67 to 2.68 on the verizon LG G3
[SuperSU] lsemprini:
minor fix for update-binary script

Hi Chainfire,

Here's a fix for a small typo in BETA-SuperSU-v2.68/META-INF/com/google/android/update-binary that will help people figure out how things are working:

Under "SYSTEM-LESS" INSTALL correct

# 22+ /su/bin/su (symlink) *2 /su/[COLOR="Red"]lib[/COLOR]/supolicy 0755 u:object_r:system_file:s0 required

to

# 22+ /su/bin/su (symlink) *2 /su/[COLOR="Lime"]bin[/COLOR]/supolicy 0755 u:object_r:system_file:s0 required

Thanks for all your amazing work over the years. It's truly awe inspiring looking through update-binary and seeing how many zillions of cases of device bugs and inconsistencies you had to handle.
[SuperSU] :
Deleted wrong thread srry
[SuperSU] Chainfire:
Your kernel needs to be bumped after patching. Ask in the G3 forums.
[SuperSU] DingoBat:
Bump Script here - http://xdaforums.com/lg-g2/general/bump-supersu-t3273251

[MENTION=631273]Chainfire[/MENTION] - thanks for the work you do.
[SuperSU] rolo143:
Do I really need a recovery to flash SuperSu? Or could I just install it via adb commands from the computer?
[SuperSU] Ch3vr0n:
You can download the zip, and fastboot boot into recovery but to install properly you MUST do it through a recovery. If you'd read changelog you'd know. It clearly states you MUST install through recovery to get an the fixes correctly.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] alex00006:
the version 2.70 can be for routed to Android 6 to use or version of special android N is ?????
[SuperSU] j1gga84:
I use it without any problems on 6.0.1 Resurrection Remix :good:

Not all fixes in this RC build are for Android N.

regards
[SuperSU] carlese:
Is 2.70 systemless or like 2.65 can be used normally?
[SuperSU] manbat:
I flashed it on my Note 4.... "normal" root...works fine.

Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / Custom Kernel-ed/ TWRP 3.0.0-0.trltevzw
[SuperSU] Fif_:
However that does not mean that you HAVE to flash the recovery image into the phone.

You can boot the recovery partition and fastboot into it without ever flashing the recovery.
[SuperSU] Ch3vr0n:
You may want to read my post again, I said they could fastboot boot into the recovery. It's the very first line. I said the zip file MUST be flashed through recovery. How they launch the recovery is up to them.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] praveen Glaxi:
Can someone help me to unlock bootloader and flash cwm or twrp recovery and root intex aqua trend phone ? :(
[SuperSU] Tzfardaya:
Here, try this
[SuperSU] rolo143:
Too boot into recovery do I have to flash one? Or can I boot into fastboot or use adb commands to boot into it and flash a file? I think you can also flash zip files as long they're located in the platform-tools folder.. Am I right?
[SuperSU] Tzfardaya:
The command to boot into a recovery without flashing it to the phone was given in an earlier post to you...

fastboot boot recovery_file.img

This boots the phone using that recovery, but does not install it to the phone.
[SuperSU] iaacp:
Hey all,

Trying to install BETA-SuperSU-v2.67 on my G4 H811, via TWRP zip. Towards the end of the install, I saw this:

followed by some finish-up text.

Does that mean the installation failed, or did it go fine?
[SuperSU] Ch3vr0n:
Post the required logs that are asked, do chainfire has something to look at besides 2 lines of text that lack any and all surrounding meaning.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] iaacp:
Will do. Where can I find the logs?
[SuperSU] Ch3vr0n:
The first post

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] j1gga84:
is 2.70 RC only for N or also for MM?

I installed it on a CM13.0 based ROM and it runs without any problems (apkmirror does not say, that 2.70 RC is exclusive for Android N).

regards
[SuperSU] chubby65:
Works just fine on MM mate
[SuperSU] milojoseph:
I'm using it for lollipop on my note for. Chainfire made some changes and bug fixes which MAY be compatible for all devices........ Change log has N for n devices.
[SuperSU] praveen Glaxi:
Can I install any cwm recovery.IMG to any phone ?
[SuperSU] Tzfardaya:
No, the recovery image is specific to each device, you can check their website to see if they have a recovery image for you phone.
[SuperSU] nathanchance:
This isn't the place for your question as this is the SuperSU thread. However, no, you cannot install any recovery image onto any phone, it doesn't work that way. I highly recommend visiting your device's forum if you are in need of a custom recovery.
[SuperSU] praveen Glaxi:
There is no proper forum for my device :'( intex aqua trend !! So why I am jumping from thread to thread sorry if this is wrong place
[SuperSU] Vel-San:
Hey,

can i know if there is a procedure to get back on System Mode root and get rid of systemless root ? i cant use adaway and other applications on S6 Tyrannus Rom bcuz of that.. so if someone can help me to get back without any errors ( i already tried a method but it gave me a bootloop and i had to reflash the rom )
[SuperSU] fmc000:
adaway is systemless compatible, check the app thread for a solution that has been known to work for months.
[SuperSU] d3m0n1:
This post on this thread has the info you need.

Basically, what you need to do, is to boot to custom recovery, open an adb shell and issue this command:

echo SYSTEMLESS=false>>/data/.supersu

after that you can install supersu, and it will install into system. (This works only for SuperSU 2.64 and higher).

br

d3m0n
[SuperSU] RandomPooka:
Once you HAVE that .supersu file created, back it up to your sdcard. Then you can just copy it into /data with TWRP's built in file manager the next time you clean flash and avoid typing it repeatedly or making a mistake when entering it.
[SuperSU] ithehappy:
Can I do this somehow without the help of ADB commands? I never understood them!
[SuperSU] egingell:
It's just a text file. Use a text editor to paste SYSTEMLESS=false and save it to "/data/.supersu".

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] alex00006:
Who knows exactly what the difference is between version 2.68 and 2.70?

change log ?

Now

For root Note5 (MM)

Which version should I use?
[SuperSU] egingell:
The OP says exactly where the changelog is.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Ja_som:
In first post there is a link to changelog post

http://xdaforums.com/showpost.php?p=64916199&postcount=3
[SuperSU] ithehappy:
Sorry for asking this, but I don't see that folder under Data! Do I have to create it or what?
[SuperSU] egingell:
It's not a folder. It's a text file.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] ithehappy:
Okay creating one then.
[SuperSU] Drifus Dreskeke:
Nexus 9 LRX21Q - v2.22 installed through apk, binaries updated, PRO license recognized. Running fine.

Nexus 5 LRX21O - v2.22 installed through TWRP. All good.
[SuperSU] Bill Gamble:
http://download.chainfire.eu/606/SuperSU/BETA-SuperSU-v2.22.zip?retrieve_file=1
[SuperSU] JulianJenner:
This works for me without problem on LGE-P760 Lollipop. Thanks [MENTION=631273]Chainfire[/MENTION]!

Redmi Note 1W Enhanched / MIUI 37.0.0 Stable Multilanguage / Tapatalk Pro 4.6.2
[SuperSU] tobitege:
2.22 Pro version now runs fine on LG G3 Lollipop. Deamonsu process problems fixed.
[SuperSU] Petertyuh:
Installed version 22 on my OnePlus ONE and it works like a charm.

Currently running Carbon rom, kk 4.4.4 (without any further tweaks).
[SuperSU] scrin378:
2.22. works great on N7100 with TW based 4.4.2....no problem
[SuperSU] Gips3yD4ng3r:
Nexus 5 running frank hammerhead 9.1 works great
[SuperSU] c3k:
very big thanks

anyway no other kind of problem with 2.22 (neither with 2.20) on hammerhead and flo
[SuperSU] Long Island NOOBIE:
Functioning flawlessly on my older devices: SGS3-i747 and SG Tab2 10.1-P5113. As always, thank you sir!
[SuperSU] quang61:
2.22 works great like never before with lg G2 and Cloudystock 2.6

from F320L
[SuperSU] D@nge1:
OPO, work fine!
[SuperSU] DJxSpeedy:
nexus 5 with Stock Android 5.0 and autoroot used...works fine

Send from my Nexus 5 with Tapatalk
[SuperSU] jakal46:
Hi!

Work fine on LG G2 with Optimus G3 and latest TWRP.

thanks
[SuperSU] brsclkr:
can i flash v2.22 to stock nexus 4 lollipop without untouched kernel??
[SuperSU] gogetrd:
Problem with PM

Im running SuperSU 2.22 on a Nexus 7 (2012 and 2013) with Android 5.0 stock room. I have rooted with CF-auto-root and then upgraded SU binary with this one. Running shell with su I cant run the application PM.

root@grouper:/ # pm list packages
Error: Could not access the Package Manager. Is the system running?

if Im not using root then I get this:

shell@grouper:/ $ pm list packages
package:com.android.backupconfirm
package:com.android.packageinstaller
package:com.android.providers.userdictionary
package:com.android.providers.downloads.ui
package:com.android.externalstorage
....

So there is something fishy
[SuperSU] Mariner_1712:
Beta 2.22 working fine on xdabbeb's 2.2.0 LG G2 ROM.

BTW the log clear icon bug is gone now. :)
[SuperSU] c3k:
su --context u:r:system_app:s0 -c "pm list packages"

Will work
[SuperSU] HorstiG:
SuperSU 2.23

Works just as well as ever with my old Galaxy S3.

Thank you. :)

P.S No, not as always, something much faster in detecting root Apps. :)
[SuperSU] FoulDroid:
Helium was not working on Lollipop Nexus 7 2013.. Working now ! Thx :) ﻿
[SuperSU] mondohow:
Just tried this on my Nexus 5 and now it's just stuck at the Marshmallow loading animation for the last 30 mins.

Did the command, flashed the 2.68 zip and the script successfully installed to 'system'. Went back to main menu in TWRP and did Reboot > System and now it's stuck on the animation bit.

Is there anything else that has to be done besides running that command?
[SuperSU] Captain_Throwback:
You have to have a patched sepolicy for the system root method to work on Marshmallow. In a systemless install, the installer patches it for you. If you force a system install, however, you have to do it manually prior to flashing.
[SuperSU] mondohow:
Thanks for the reply. I have no idea how to do that unfortunately so I think I'm gonna have a look at Pure Nexus since I only broke this out of the drawer to test going old school system root.
[SuperSU] Captain_Throwback:
There are instructions in the OP of the WIP Marshmallow root thread.
[SuperSU] iaacp:
The first post is --- reserved ---.
[SuperSU] Ch3vr0n:
No it ain't, that's the second

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] iaacp:
The first post does not contain information on where to find installation logs, only changelogs.
[SuperSU] Ch3vr0n:
Then you haven't been paying much attention to the links.

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] iaacp:
I figured it out on my own, but thanks for pretending to be helpful! :good:
[SuperSU] PresidentMcCain:
Stuck at Boot Logo on Moto E (2015) with either SuperSU 2.65 or 2.68 BETA, on Stock Marshmallow.
[SuperSU] CyDroid43:
In lollypop not installed to system but intalled as user apps, please fix this problem. Thanks :)
[SuperSU] egingell:
It's not broken. It's by design.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Androidwarrior:
Is this the latest beta release?
[SuperSU] haseoxth:
Yes, thread here:

http://xdaforums.com/apps/supersu/wip-android-n-preview-t3335726/
[SuperSU] DutchDogg54:
Might I ask, what app is that in your screenshot?
[SuperSU] LoverBoy2415:
What's the app u r using(screenshot) [MENTION=5811514]Androidwarrior[/MENTION] ..?
[SuperSU] Androidwarrior:
It's another app market. It's called Aptoide