yashsingh1/xdaforums huggingface dataset:
[SuperSU] VE2HRJ:
Hi and Tank You for your response, actually I just re-flashed the Os from the carrier and the SD card work fine including all the content still intact!

I’ll go to the carrier’s forum to see if they have an update on this.

If not, I’ll search for a ROM that is cleaner like the XtreStoLite that I use before: Great, Clean and worked great!

Just find a Marshmallow one…

Thank you again!

VE2HRJ :cool:
[SuperSU] ratson:
[MENTION=631273]Chainfire[/MENTION] are you aware of the memory related issues which did not get resolved with 2.76 and is usually quick fixed with tweaking minfree settings? Here is the relevant android bugreport and logs.
[SuperSU] agentfazexx:
I'm running PureNexus build 7/8. I just flashed this so I could use apps like Wakelock Detector... After flashing this, my phone seems to be kind of sluggish. Even after a subsequent reboot. Any suggestions?
[SuperSU] Chainfire:
That bugreport has been quoted here a number of times. While some real leaks were fixed in v2.76, the linked issue apparently isn't.

So far I have not been able to reproduce it on my own 6P, which means I can't fix it. I have some doubts that the bug is actually in SuperSU, I rather suspect it's a combination of factors, as this does not seem to be happening on any other devices.
[SuperSU] ratson:
Could I do anything which helps you get closer to the solution?
[SuperSU] DxMo:
Can i Flash the latest version 2.76 over 2.64 version with TWRP 3.0.x withoy any problems, right?
[SuperSU] purian23:
Yes
[SuperSU] DxMo:
I flashed the 2.76v over 2.64 with TWRP 3.0.2 and my phone now is in bootloop. Just reeboting all time with the whithe screen with htc logo and red words... what can i do now? flash the 2.64 supersu?

I press power button but the phone doesnt turn off
[SuperSU] Alxoom33:
Go back to TWRP recovery by pressing the power and vol down buttons simultaneously and flash a custom kernel, for your device.
[SuperSU] DxMo:
I just re-flashed 2.64 and it worked and everythings fine(the phones was almost burning), i dont know why the 2.76 doesnt work.. what is that about kernel if you dont mind on explain me a little? :confused::confused:

And the SuperSU 2.76 cant be updated through playstore to latest version? or downloading the APK file?

Thank you.
[SuperSU] Kamal363:
Just a suggestion... try install v2.74... then update thru playstore...

SM G900F 6.0.1 xXx 4.9 Deodexed Boeffla 2.1 beta1 Twrp 3.0.2-2
[SuperSU] DxMo:
Ok i will try tomorrow.

One more thing: Once the backup with TWRP is done, can i just save the whole folder on my pc and just delete the save on my phone? I guess in case i need the backup i just have to copy the folder again on my phone, right?
[SuperSU] Kamal363:
Yes... as long as i know... make sure it was original/dont change any letter or number that was ganerate by default.. just to be careful...

SM G900F 6.0.1 xXx 4.9 Deodexed Boeffla 2.1 beta1 Twrp 3.0.2-2
[SuperSU] NLBeev:
Why don't you leave it that way.

When 2.64 works and gives you root acces; why do you want another version?
[SuperSU] RandomPooka:
You could name the folder "Fruity Pebbles" and it wouldn't matter, so long as you copy it back to the directory that TWRP saved it to in the first place:

TWRP/BACKUPS/DEVICE_ID/FruityPebbles

I'm not sure what the device ID folder is on yours, but it's been different for every device I've used TWRP on, so just be sure to put your Fruity Pebbles folder inside that one, and it will be a healthy and nutritious start to restoring your backup.
[SuperSU] DxMo:
I just copied the folder exactly like the pone and i saved it on another folder so its ok i guess xD

Im looking to install a custom rom, i did a System+Boot+Data(wich includes ROM files no?) backup, After flash the custom rom i just could restore only the part of App+Boot to get back all to the new ROM? If i flash Restore System+App*data will i back to the stock rom that i have now?
[SuperSU] Kamal363:
What backup did u used....?? If u want to restore user/system apps and data u can try 'backup your mobile' apps... in playstore

SM G900F 6.0.1 xXx 4.9 Deodexed Boeffla 2.1 beta1 Twrp 3.0.2-2
[SuperSU] frankbald:
Hi, I have a lg g2 with Cyanogenmod, installed super su from the play store and then updating the binary files, now it is stuck on boot loop, I can only go on download mode and cyanogen recovery, how can i flash your zip?
[SuperSU] ulxerker:
:good:

exactly, never touch a running system ... just stay happy with 2.64
[SuperSU] RandomPooka:
You typically do NOT want to restore Data or Boot from one ROM to another.

System = Your operating system, or ROM. This is also where Gapps go when you flash them from a recovery

Data = Where all your user data is, like downloaded apps (This is not where Camera pics and app data necessarily are) This is also where updates to system apps (like Gapps, phone, etc) go when you update them in the Play Store

Boot = Your kernel, for all practical purposes. Some phones and tablets have custom kernels available.

Cache = Your system's temp directory, again for practical purposes. Dalvik-Cache is similar.

EFS/Radio = These are the files pertaining to your cellular's radio. They're what you use to connect to your network. Good to have a backup of these from stock, because they also contain hardware ID information that is a real pain to restore if you somehow manage to screw it up

Before installing a custom ROM, make your backup, and then go into advanced wipe and wipe system, data, cache, and dalvik-cache. Then flash your ROM and the gapps package you downloaded. gapps are not allowed to be included in custom ROMs for legal reasons. It stands for Google Apps, which are owned by Google.

To revert to your current ROM if you don't like the custom ROM you installed, you would go into your recovery and wipe System, Data, and Boot. Then restore your entire backup.

I would recommend not bothering to back up Cache and Dalvik-Cache, but to just wipe them with TWRP advanced wipe after restoring and/or flashing before you reboot to the phone's operating system.

If the Dalvik-Cache is empty, it gets rebuilt on the fly by Android anyway when you boot. That's what the "Optimizing App 1 of 50" is (or whatever number you have installed).

If your regular cache is empty .. so what? It gets constantly changed by using the phone. It's essentially a swap file for Android to store frequently used bits of information, so it can be readily available when you next need it. After a few hours of regular use, it will be full of all sorts of things.

-- Edit --

One final thing. This is unrelated to SuperSU, and should honestly go in a general discussion thread. Off topic conversations are generally not well received by Chainfire, as they create needless clutter that prevents people from finding actual SuperSU related information that he's put out there
[SuperSU] osm0sis:
CyanogenMod Recovery is terrible, as soon as you get the chance switch to TWRP. Anyway, for CMR just first sign my unSU zip with ZipScriptSign from my Complete Shell Zip Documentation thread. I'm not sure it will help in your situation but you should then be able to sideload it. :good:
[SuperSU] Alxoom33:
No! It can't. Download 2.76 zip file from chain fire's website. Usually a custom kernel will cure reboot problem after flashing SuperSu.
[SuperSU] Ch3vr0n:
Wrong, yes it can. V2.76 has been in the play store since July 5th.
[SuperSU] Alxoom33:
But I don't think it can just be dl'd from the play store and work. You need to flash the zip to get Systemless root access. I believe@chainfire commented on this a few days ago.
[SuperSU] egingell:
He said "update". You can't root your phone with the download from the Play Store, but you can surely update it just fine.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] Alxoom33:
I don't think you can update from system root to Systemless, without flashing the 2.76 zip file.
[SuperSU] egingell:
Sure, you can. As long as su is already present. The only thing it does to update it is replace the binary files wherever they may be.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] mielletseed:
you missed the part from system mode to systemless mode...
[SuperSU] egingell:
I did, indeed. But why would anybody want to do that? Seems unnecessary. But that's just my opinion.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] RandomPooka:
True. It isn't like AP or other SafetyNet based apps will work if you do that. The system image has already been altered.
[SuperSU] Alxoom33:
No, Ap is working fine for me rooted 2.76 Nexus 6 on N DP4. Check out the AP thread.
[SuperSU] giorgis91:
How can I know if i'm using systemless root or normal?
[SuperSU] Pkt_Lnt:
supersu settings > scroll down to "install as system app" and read what it says
[SuperSU] giorgis91:
It gives me the possibility to install supersu app in system
[SuperSU] Pkt_Lnt:
you are not systemless then. You can use that choice to do system install or use the zip in twrp with the terminal command to force systemless
[SuperSU] giorgis91:
so if i install supersu in system, i have systemless root?
[SuperSU] Pkt_Lnt:
no, you have system root if installed in system
[SuperSU] giorgis91:
sry i misunderstood. Can u give me a guide/link to force systemless?
[SuperSU] stang5litre:
Hey [MENTION=631273]Chainfire[/MENTION] and everyone else that might have the right answer. I have built a rom for the Verizon s7e and I can't get it to keep SuperSU after that flash if you will. Still have to hook it up to the computer and run the bat file. By the way THANKS A MILLION FOR MAKING IT POSSIBLE AT ALL!!! That being said since our method has a img in it as well is there a way to get it to flash with a Rom zip so I can cut out the Needing the computer to run the root bat file? Thanks so much for all your hard work and for everyones input(we can only use Flash Fire)
[SuperSU] Alxoom33:
You can look at the installation log. Or you can check with root explorer.

---------- Post added at 01:21 PM ---------- Previous post was at 01:19 PM ----------

You can read this thread. Start with the OP.
[SuperSU] alex00006:
Hi

why not work root explore Es file manager with SU 2.76 or 2.74 ?????

i use last version Es file and soild manager....
[SuperSU] anagramgenius:
Time to change file manager.

Jokes apart, you should really ask the above mentioned apps developers.
[SuperSU] osm0sis:
Why not search for your answer? It's been discussed to death.
[SuperSU] gdecker:
Not only discussed to death, the es file explorer app devs are ignoring all requests to even acknowledge the issue.
[SuperSU] sonwon:
Yes, the es file explorer app can go now. Please everyone return to the OP thread now.
[SuperSU] NLBeev:
The version. What I remember is version > 2.5x
[SuperSU] Pkt_Lnt:
Look at Setting in SuperSU app to see if system or systemless install.
[SuperSU] kirito9:
[MENTION=631273]Chainfire[/MENTION]

I have an mt6580 device running android 6.0 and I would like to know if your systemless root is compatible with it. I flashed the lastest beta zip with TWRP but root wasn't achieved. I got a supposedly systemless root zip from SuperSU Root and flashed it but the device didn't boot and I had to restore boot.img.

Do I need a boot.img that's systemless or would this guide work?

Don't think it systemless works with MTK sadly.
[SuperSU] NLBeev:
I found under 'system' a disabled setting / notification telling me it is not available in system less mode
[SuperSU] Pkt_Lnt:
That means you have a systemless install and SuperSU can not move it from a user app to a system app. TL;DR you are systemless.
[SuperSU] NLBeev:
[MENTION=1910244]Giorgis[/MENTION] did you read the above post #6768
[SuperSU] Pkt_Lnt:
Start at post #6751 for the discussion we had.
[SuperSU] alex00006:
This thread for fix problem Enable root explore Es file manager

http://xdaforums.com/galaxy-s5/general/fix-es-file-explorer-root-error-t3382537
[SuperSU] osm0sis:
No. Don't spam, and this is not even good advice. That ruins the point of systemless root.

The correct things to recommend are to use SuperSU's compatibility mode (which accomplishes the same thing as your link), use the patched APKs someone linked that fix the issue, or switch file explorers to one that cares about their users.
[SuperSU] nathanchance:
I am in favor of this one. When an app can't fix something that is broken to get with the times, it is time to find a different app.
[SuperSU] alex00006:
i fixed problem myself with [emoji115] Education

Now everything ok and

My goal was to help people not spam or

Or any interference.....

[emoji116] [emoji116] [emoji116] [emoji116] [emoji116] [emoji116] [emoji116] [emoji116]
[SuperSU] GrndSers-Rcng:
Somehow when I flash latest supersu on twrp and boot to the system, supersu is nowhere to be found... Can't seem to find a fix for it... Anybody have any ideas? Thanks in advance...

Im running latest Pure Nexus on my 6P, with its gapps and thats pretty much it...
[SuperSU] mondohow:
Does it give an error post install or does it say successful? Upload your logs and I'm sure someone will take a look.
[SuperSU] ktmom:
Have you looked at the twrp log after flashing supersu? After flashing supersu in twrp, Advanced > save log
[SuperSU] GrndSers-Rcng:
It didn't when first installed, but tried ot again and it gave me an error log pic on the bottom...
[SuperSU] ktmom:
It's showing that the image was already patched. Probably from the first flash. Have you tried installing the apk from the play store?
[SuperSU] GrndSers-Rcng:
Yes... But everytime i reboot every app has to be granted root again...
[SuperSU] egingell:
That sounds like a completely independent issue. Try deleting SuperSU's data folder (/data/data/eu.chainfire.supersu).

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] GrndSers-Rcng:
Ok, will report back...
[SuperSU] linkhunter:
is it safe enough to use this http://xdaforums.com/showpost.php?p=64161125 on samsung galaxy view we try all different kinds of root kingo root, kingroot, one click root, framaroot, etc.
[SuperSU] ldeveraux:
Is supersu installed as a system service? It might not show up as an app if so.
[SuperSU] GrndSers-Rcng:
Dont get what you are saying, you mean as a system app?
[SuperSU] ktmom:
Have you looked in the settings menu for supersu? If it's there, it won't might not show up as an app in the app drawer. If it's in neither place, try looking in the apps list within the settings menu - also enable all/system apps using the 3 dot menu.

-----edit-----

This is not describing all use cases. This situation is an unusual one but can happen with certain ROMs if su is built in
[SuperSU] egingell:
That's not true at all.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] grep_i:
What are you talking about SuperSU when installed properly will always show up in app drawer.
[SuperSU] Tecalote:
Maybe it does in some other Roms, but in Huawei p8 it is necessary to use in Recovery the Terminal before flashing the zip and execute the Force systemless Command.
[SuperSU] ldeveraux:
When supersu is baked into some roms as a system app, it's hidden from the app drawer. You have to root uninstall, then install from apk. It's a monstrous pain, and I hate when developers do it that way.
[SuperSU] egingell:
That may be true of those ROMs, but ktmom was saying it as if it were always the case.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] ktmom:
Not my intent. It was meant to move that poster's conversation forward.
[SuperSU] Moiremoi:
Firstly, i would like to thank you for all the work you've done for the XDA community =D

Secondly, i want to report a bug that touch only one phone, let me explain.

As you may know Xperia Z3 has got the Android N Developer Preview, and thanks to you, Gustavo RD78 and shoey63, the root access has been reached.

But, when we flash the SuperSu zip and the phone reboot, there is two issue :

The phone governor turn change itself to performance (with kernel audiutor, it's easily fixable) and

The phone can't enter deep sleep mode.

The probleme is that I can't provide logcat because of patched logd used for permissice SeLinux on android N

I don't know if that have been reported, or of you want to work on it (because it only touch one device) but I hope you can do something fot it ! ^^

Ps: sorry for my english mystakes ^^'
[SuperSU] GrndSers-Rcng:
No, it doesn't show up anywhere... And I just figured out that this happens only if its a systemless install... Otherwise it installs normally...
[SuperSU] defconoi:
Any news on root for DP6? Anxious to pwn my phone on N6P, just want to keep encryption if possible.
[SuperSU] egingell:
Where it's installed to is also meaningless. If it doesn't show in the app drawer, it's probably a ROM issue. Look in Settings. You can also make one using Quick Shortcut Maker. You can also access it from the dialer by dialing *#*#SUPERSU#*#* (I think that's right).

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] ldeveraux:
You won't find root status for devices here. Try the forum for your specific device
[SuperSU] Ja_som:
1. DP6 does not exists

2. I posted my root procedure here: http://xdaforums.com/showpost.php?p=67802515&postcount=11044

or if you use FlashFire, then use it to update...
[SuperSU] JulianJenner:
Which link what you want?

LGE-P760 Lollipop Android 5.0 by Artas182x
[SuperSU] Foulwx:
Nexus 7, Twrp, ElementalX 3.2. So far, so good.

Beta 2.25
[SuperSU] Gu$houn*:
http://xdaforums.com/nexus-4/development/lpv-79-mako-port-beta-t2807446

P.
[SuperSU] laverdure#1:
You need Secure Settings beta for Lollipop compatibility for now. Join the G+ community and beta program. Secure Settings now works fine for me. SU2.20

Instructions and links are here.

Cheers
[SuperSU] DaBigFreak:
Oh dudes, quiet everything beside "untouched stock" is a port, or at least an AOSP built, has quiet nothing to do with stock google ROM.

You guys are on heavy tweaked ROMs.

Now WugFresh downloaded an modified kernel, then did all the other flashing stuff. Will do everything with WugFresh for the nexus 10.
[SuperSU] buffal0b1ll:
Regular old secure settings is working for me since 2.23 on nexus 9 lollipopolooza rom

---------- Post added at 02:59 PM ---------- Previous post was at 02:58 PM ----------

2.25 doesn't seem to be giving toast notifications when root apps are opened. I'm on nexus 9 lollipopolooza rom
[SuperSU] Nicknoxx:
I was on the Secure Settings beta so uninstalled it, reinstalled, now all seems OK. Thanks

N4 Twrp Hells-core LRX21T
[SuperSU] SamuriHL:
Now we need some Nexus 6 love. sniff sniff. :D Just got mine a little bit ago. Unlocked and ready to go. :D
[SuperSU] Blac Caesar:
Nexus 5, stock Lollipop.. SuperSU v2.25 running perfectly it seems so far
[SuperSU] Scottchy014:
(Nexus 7 2013) ES File Explorer "Root Explorer" works now on 2.25 running on stock LRX21P. Good job!
[SuperSU] scrin378:
I notice that with 2.22 - 2.25. my battery Is draining much faster...so i went back to 2.19. Dont know if its just me or someone else have this issue...but all versions works fine though...
[SuperSU] Frank Westlake:
Take a look at 'top' or 'htop'.

Frank
[SuperSU] Paschfire:
nexus 5 running 5.0 factory images LRX21O / TWRP Recovery + Franco Kernel r68. version 2.25 working great so far,will report back with any issue's if they arise.

current root apk;

Titanium Backup

Root Explorer(speedsoft)

flashify

terminal emulator

FKU (kernel control)

adbd insecure

stickmount

BusyBox pro(stericson)
[SuperSU] HorstiG:
No Problems Galaxy S3 - Philz Touch 6.58.9 - Liquid Smooth KK 4.4.4 - Boeffla Kernel Omni NG Beta 7

Thanks for Update
[SuperSU] landstander:
My N5 wouldn't boot up (got stuck on the initial animation screen) after flashing SuperSU 2.25, on a rooted but otherwise 100% stock Lollipop release... tried twice just to verify. Versions 2.20 and 2.23 were both fine.

I also tried updating via APK, with the same results.
[SuperSU] Empty Hand:
No problem on N5 here.
[SuperSU] olwen669:
.noobie alert needs advice gtn7100

Sorry noob here ... unsure what to do next

SuperSU v2.23 & SuperSUPro v2.01

rooted Samsung Galaxy Note 2 GTN7100

ROM KK 4.4.4 liquidsmooth stable v3.1

ZIP FILE Using CWM RECOVERY 6.0.4.3 with gapps and camera fix

getting message saying su binary needs updating plus asking I want root fixed said no.

Phone was ok but started phone acting erratic always updating apps even if I had uninstalled them.

Was going to use beta 2.25 but couldn't find my version TWRP & noticed comments about not working on GS3 so thought maybe same to me as similar phones.

Advice would be great

:confused:
[SuperSU] MikeRL100:
Maybe with all the abnormal behavior cropping up, Chainfire should pull the current beta and work on another one. Only if these issues are actual bugs.

I myself can't seem to get SuperSu to respond, but I wonder if I can upload anything that would be of use for Chainfire considering that I may have run into a bug. I'll wait to wipe until he answers me. I will need to figure out how I can get any useful log info without having root. Can't easily log stuff without root.

I seem to be also getting some errors even with grant as the default option. Anyway to export these logs from SuperSu? I want to help, not complain. But if this is a bug, I'm sure Chainfire would like to see information on this.

As for the logs, I'm talking about the app logs under the logs tab I. SuperSu, to be more clear.
[SuperSU] suchevent:
That's the whole point of a beta and I'm sure that he is working hard on this (he's already updated this a few times in the last day or two). Perhaps, you should just say thank you and give the man some time while he works his magic. I have no doubt that all the bugs will be remedied in due time.

Sent from my Nexus 5
[SuperSU] MikeRL100:
I'll assume I came off on the wrong note. I will clarify things.
[SuperSU] Abraheem:
This Root Toolkit identified my systemless root on Note 5

https://play.google.com/store/apps/details?id=sa.root.toolkit
[SuperSU] Wolfcity:
Where do you see the systemless/non systemless state in this app?
[SuperSU] g2uzer:
im trying to find out to see if i still need both terminal commands to install systemless with 2.76 superSU..
[SuperSU] egingell:
Did you look? Click the top item, "display root and device status". At the top it either says, "device does have root" or "device does have (system-less) root".

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] Wolfcity:
Ah ok, in my case it's "device does have root", I didn't know about another option there.
[SuperSU] Abraheem:
Select the 1st option (Display Root and device status). Check 2nd screenshot in the playstore
[SuperSU] Ch3vr0n:
Why on earth would you use a third party app to see if you're running systemless. Just open superSU and scroll down to the 'system' section. If the setting to 'install superSU to system' is greyed out you're running systemless. As that settings sub line would tell you.
[SuperSU] mrjoy:
Im on galaxy s5. I want to unroot supersu for ota update but when i try from app itself it shows "supersu unistallation failded". Please help
[SuperSU] Tecalote:
Unroot in Custom Recovery with unsu.zip

Just go to your custom recovery and flash the unsu.zip located from following site: http://xdaforums.com/showpost.php?p=63615067
[SuperSU] mrjoy:
After flash this, does it need boot.img file to flash later manual? If it must then how to get original boot.img files for galaxy s5?
[SuperSU] Tecalote:
I dont know, if you have to flash this on galaxy s5 (I am already Huawei User) - but if, you can try this: https://www.androidfilehost.com/?fid=95916177934533844

But I would try it first without reflashing the boot.img - if the phone dont start you can go with the hardware-buttons to your recovery again und do this.

Before doing all - make a full nandroid backup
[SuperSU] mrjoy:
Thanx for providing boot.img file. Im on marshmalloe but i dont know this file is compatible for marshmalloe 6.0.1...& how to undo in case?