yashsingh1/xdaforums huggingface dataset:
[SuperSU] thgxda:
Hi Captain_Throwback,

because the init.d is not the problem, the SuperSU is.

If I use SuperSU, then init.d is working, but "pm", "logcat" and others are not doing anymore!

If I do not use SuperSU, I still have root CyanogenMod, all programs are working, but the init.d is not started on boot :(

But I need root, init.d and all commands should work ...

Thanks a lot,

kind regards,

thgxda
[SuperSU] Captain_Throwback:
Well, if you're going to use SuperSU, I'd recommend you try su.d rather than adding init.d to the ROM and see if that works. Otherwise, maybe you're making a syntax error with your init.d setup.
[SuperSU] Chainfire:
Maybe the kitchen method doesn't implement the latest changes for SuperSU in the boot image ?

That error is not supposed to happen and I cannot replicate it on another CM13 device.

Perhaps /su/bin/app_process doesn't exist, or PATH isn't set correctly, or pm hardcodes app_process path? (cat /system/bin/pm)
[SuperSU] Chainfire:
v2.64 BETA posted to the WIP thread. Do read the notes!
[SuperSU] :
Hey man. I need your help. I have a samsung galaxy s3 with official cm13 and your supersu 2.62. if i wanna flash 2.62-x my phone doesn't boot. I comes to the end of optimizing apps and thats it. What do i have to do, to make it work? I tried to wipe cache, dalvik and /system. I know it's systemless. So what do i have to wipe? Data and / or internal storage? Please help me
[SuperSU] Ch3vr0n:
Wrong thread, this isn't the 'update failures' thread

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] corkiejp:
Successfully Installed over v2.62-3 on my Nexus 9. Had to also reflash ElementalX Kernel after flashing SuperSU.

Seems to be working fine, but you probably already know that as you have already tested on the N9.

Looking forward to going properly Systemless with the next factory image in January, as busybox already has systemless mode and intend to replace AdFree with AdAway then. Don't feel like reflashing the system at this time.
[SuperSU] FernBch:
Downloaded 2.64 beta release. Attempted yet again to install SU on SynergyCM13.0-20151213-jfltevzw. Near the end of the installation process I see:

- Decompressing ramdisk

sukernel v2.64 (ndk:armeabi-v7a) - Copyright (C) 2014-2015 - Chainfire

Loading from [/sutmp/ramdisk.packed] ...

--- Failure, aborting

Am I missing something cause I have been unsuccessful installing SuperSU.

Full recovery log:

https://www.dropbox.com/s/kmc3bafuvlfq20v/recovery.log?dl=0
[SuperSU] Anastacio_Guerrero:
Systemless root 2.64 is breaking WiFi Calling for some reason. I'm on 6.0.1 on my Nexus 6P. Anyone else have this issue?
[SuperSU] boxcar8028:
Are you on project Fi? I am and this is good to know.
[SuperSU] Anastacio_Guerrero:
No, I'm on T-Mobile. But I've tried without root and WiFi calling works both on stock and Franco kernel. As soon as I flash the root zip WiFi calling is gone.
[SuperSU] Neverendingxsin:
/su/xbin_bind folder

Do we delete that folder while still in recovery or boot up first and use root explorer to delete it?
[SuperSU] thgxda:
Hi Chainfire,

at least it says "BETA-SuperSU-v2.62-3" in the lates kitchen version.

But I have seen, that you just published the "BETA-SuperSU-v2.64-20151220185127.zip", so I will try to include this and try again.

I don't know yet, I have to make a new build and install it to check this.

Kind regards,

thgxda
[SuperSU] Alxoom33:
Either works. Just reebot after.
[SuperSU] Chainfire:
That kernel is probably not using gzip for ramdisk compression. The automated patcher only supports gzip at this time.
[SuperSU] H4X0R46:
So if I got this correctly, SuperSU 2.64 installs traditional if on lollipop and systemless if on Marshmallow? Unless it's a Marshmallow custom ROM?
[SuperSU] Adrianrff:
-Deleted-
[SuperSU] Adrianrff:
I have this exact same problem SuperSU 2.52,stock MM, EX kernel.

Once every few days SuperSU hangs and is unable to grant root access to apps. I'm also running Cygery's Toggle Data and Toggle Network Type 5.0 plugins in Tasker, but he says it's a problem with SuperSU. I'm not sure if that's the case because both apps (SuperSU and the plugins) hang when you try to open them. No app has root access, but only those hang.

As [MENTION=4808167]trawel[/MENTION] says, there's no easy way to determine what causes the problem, there doesn't seem to be any recognizable pattern. Doesn't the logcat posted by trawel provide any clues, [MENTION=631273]Chainfire[/MENTION]? If not, what can we do to help you figure this out?

Thanks in advance.

PS: I apologize for the 2 previous posts. I frequently have problems with this site when posting.
[SuperSU] Alxoom33:
Sorry, but that's a root folder, not a System App. I'm not doing that now. Use Root Explorer! Or ES File Explorer Pro.
[SuperSU] IronTechmonkey:
Considering how frequently and constantly Cyergy's data toggle requests SU permissions even when not actively invoked and with no widgets placed (unlike any other app/utility I've ever seen) it is not a surprise it has issues with SuperSU. In any event, you might be able to use tasker with "su -c svc data enable"/"su -c svc data disable" to toggle mobile data.
[SuperSU] boxcar8028:
Just flashed 2.64 over 2.62-3 on my n7 and 6p on stock mm 6.0.1 with no issues everything booted up very smooth and nicely just had to reinstall EX Kernel. Project Fi working perfectly. Thanks! Great job Chainfire:good::good::good:
[SuperSU] FernBch:
Thanks for the reply, I'll pass this along to the dev.
[SuperSU] AnGrY sCoTsMaN:
[MENTION=631273]Chainfire[/MENTION] just flashed 2.64su on sony z3c (aries) stock concept mm rom! identified systemless mode and boot image support required. so all seems to be working correctly. ideally full root access was the result i was hoping for but hey...happy i had the chance to try, thanks for all your work.
[SuperSU] thgxda:
it now says, that it has 2.64, I just updated the 2.62-3 in the kitchen.

I build a new ROM with SuperR's Kitchen 0.9.7.1 and cm-13.0-20151220-NIGHTLY-peregrine and installed it.

OK, with the new version "pm ..." seems to work now, that is great, but "logcat" still doesn't show any output if I make an "su -". It works if I make "adb shell" without any "su":

$ ./adb shell
shell@peregrine:/ $ logcat
--------- beginning of system
12-21 00:07:17.071 180 180 I vold : Vold 3.0 (the awakening) firing up
12-21 00:07:17.071 180 180 V vold : Detected support for: exfat ext4 f2fs ntfs vfat
12-21 00:07:18.257 180 192 D vold : Disk at 7:1 changed
--------- beginning of main
12-21 00:17:30.268 225 225 I ThermalEngine: action_info 1
12-21 00:17:30.268 225 225 I ThermalEngine: descending
12-21 00:17:30.268 225 225 I ThermalEngine: [VDD_RSTR_MONITOR-TSENS3]
12-21 00:17:30.268 225 225 I ThermalEngine: #algo_type monitor
12-21 00:17:30.268 225 225 I ThermalEngine: sampling 1000
12-21 00:17:30.268 225 225 I ThermalEngine: sensor tsens_tz_sensor3
12-21 00:17:30.268 225 225 I ThermalEngine: thresholds 5000
12-21 00:17:30.268 225 225 I ThermalEngine: thresholds_clr 10000
...
..
.
12-21 00:29:41.302 225 401 I ThermalEngine: Sensor:batt_therm:27800 mC
12-21 00:29:51.307 225 401 I ThermalEngine: Sensor:batt_therm:27800 mC
12-21 00:30:01.312 225 401 I ThermalEngine: Sensor:batt_therm:27700 mC
^C
shell@peregrine:/ $ su -
root@peregrine:/ # logcat
^C
root@peregrine:/ # su - shell
shell@peregrine:/ $ logcat
shell@peregrine:/ $ logcat
^C
shell@peregrine:/ $

Tried some more things:

root@peregrine:/ # su -V
264
root@peregrine:/ # logcat
^C
root@peregrine:/ # ls -l /su/bin/app_process
-rwxr-xr-x 1 root root 22144 2015-12-21 00:04 /su/bin/app_process
root@peregrine:/ # /su/bin/app_process
root@peregrine:/ # cat /system/bin/pm
#!/system/bin/sh
# Script to start "pm" on the device, which has a very rudimentary
# shell.
#
base=/system
export CLASSPATH=$base/framework/pm.jar
exec app_process $base/bin com.android.commands.pm.Pm "$@"
root@peregrine:/ # pm list users
Users:
UserInfo{0:eek:wner:13} running

Any ideas?

Kind regards,

thgxda
[SuperSU] Adrianrff:
Thanks for the suggestion. Would you elaborate a bit? How should go about doing that exactly, I'm not familiar with svc commands in Tasker. I did notice that that particular plugin requests SU permissions frequently, the other plugin though (Toggle network type) does not. Should I worry only about the toggling data plugin?

Thanks.

EDIT: Nevermind, got it to work. Thank you. Is there a way to control network type using a similar method?
[SuperSU] thgxda:
Just fixed a script, because several commands moved from "/system/xbin/..." to "/su/bin...":

$ ./adb shell
id: unknown ID 2000
COLUMNS=161;LINES=35;export COLUMNS LINES;
2000@peregrine:/ $ su -
COLUMNS=161;LINES=35;export COLUMNS LINES;
root@peregrine:/ # bash
peregrine / # ps -A | grep cron
root 883 1 9404 212 hrtimer_na d0100 S /su/bin/crond
peregrine / # pm list users
Error: Could not access the Package Manager. Is the system running?
peregrine / # su -V
264
peregrine / # ls -l /su/bin/app_process
-rwxr-xr-x 1 root 0 22144 Dec 20 23:04 /su/bin/app_process
peregrine / # /su/bin/app_process
peregrine / # pm list users
Error: Could not access the Package Manager. Is the system running?
peregrine / # cat /system/bin/pm
#!/system/bin/sh
# Script to start "pm" on the device, which has a very rudimentary
# shell.
#
base=/system
export CLASSPATH=$base/framework/pm.jar
exec app_process $base/bin com.android.commands.pm.Pm "$@"

No idea :(
[SuperSU] thgxda:
Hi darrendude1, hi all,

what is the correct way to install the latest BETA-SuperSU as ZIP on my mobile with cm13?

It can not be done via TWPR, because this results in a boot loop.

Thanks in advance,

thgxda
[SuperSU] chazall1:
Great Job, All working well here. Latest Cata and ELx 6.7

Thanks
[SuperSU] IronTechmonkey:
I dont think there is any cause for concern about the Cyergy apps but I prefer more control and less needless SU request chatter because when such requests occur so frequently it undermines the value of such warnings. Now straying a bit of topic for SuperSU but here is a tasker toggle using that command with variables that indicate whether mobile data is enabled or not. I dont know if there is a way to similarly control network type or background data.

A1: Variable Set [ Name:%wData To:0 Do Maths:eek:ff Append:eek:ff ] If [ %wData !Set ]

A2: Goto [ Type:Action Number Number:6 Label: ] If [ %wData ~ 1 ]

A3: Run Shell [ Command:su -c svc data enable Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: ]

A4: Variable Set [ Name:%wData To:1 Do Maths:eek:ff Append:eek:ff ]

A5: Stop [ With Error:eek:ff Task: ]

A6: Run Shell [ Command:su -c svc data disable Timeout (Seconds):0 Use Root:eek:n Store Output In: Store Errors In: Store Result In: ]

A7: Variable Set [ Name:%wData To:0 Do Maths:eek:ff Append:eek:ff ]

A8: Stop [ With Error:eek:ff Task: ]

Good grief! /\This/\ is why I hate eeemogeees for being the corruption of the written word that they are but you get the idea.
[SuperSU] gleggie:
If I am on super su 2.62 (12/10) can I just flash 2.64 or any other systemless root method over?
[SuperSU] shoey63:
The "systemless mode, boot image support required" message is just letting you know that the boot.img needs to be patched, and then that's exactly what the script does next:D

You are fully rooted, as am I on Leo (also on MM concept rom)
[SuperSU] vjtigas:
When does SuperSU v2.64 BETA root our phone in systemless mode and in system mode?

I don't want to root it in systemless mode. And based on my understanding, I can now use the latest version for that. Thanks you!
[SuperSU] Adrianrff:
Hahaha, yes. Thank you. I already have the Tasker profiles set up, I just never used an svc command before, but I got it to work. It's simple enough.

I'm reading in Cygery's thread that the plug-in updates itself upon any network change, that's why it asks so much for SU permissions. Although it has done it (the toggle network type plugin) when connected to a stable WIFI, so I don't know.

Anyway, I've uninstalled toggle data and kept toggle network type (which I need unless there's a way to change network type through a shell). Will report back here if the SU hang happens again.

Thanks again, bud.
[SuperSU] vjtigas:
When does SuperSU v2.64 BETA root our phone in systemless mode and in system mode?

I don't want to root it in systemless mode. And based on my understanding, I can now use the latest version for that. Thank you!
[SuperSU] BeingEEE:
Flashed supersu 2.64 in sultans cm13.0 for oneplus one. Working perfectly! :)
[SuperSU] Azhero:
Thank you so much [MENTION=631273]Chainfire[/MENTION], finally Seandroid warning has been removed after flashing 2.64 on my Galaxy J200GU via latest TWRP recovery. .I'm happy. .Thanks again. .
[SuperSU] GuardianUSMC:
6.0.1 (MMB29K) with Latest Root Results in Bizarre Battery Stat Behavior

I have been using the 6.0 images with the root since the beginning with no issues but once I crossed over to the newest image, it started giving bizarre problems with the battery stats and the consensus seems to be something in the boot (in this case the modified boot image) is not consistent with the kernel items in the system image. Can someone verify this is happening elsewhere and what (if anything) has been done so far to resolve it. Any assist would be appreciated.

I originally posted the issue here: http://android.stackexchange.com/questions/131830/
[SuperSU] r80ies:
I upgraded from SU 2.62-3 to 2.64 and upon rebooting all phone related systems gave me a fc error messages. I went back into recovery and tried to flash 2.62-3 and that made it worse. Reflashed stock 6.0.1 and then tried to clean install SU 2.64 and errors with the phone system started up again. I am on project fi and I am not sure if that has anything to do with it, but I am guessing it shouldn't. I finally had to factory reset and flash SU2.62-3 and I am back to a stable state with my phone.
[SuperSU] Er. Aditya:
i get a bootloop with stock kernel 910G note 4 5.1.1
[SuperSU] Ch3vr0n:
Yeah read the last dozen pages and the instructions, FLASH STOCK boot image then the zip. It's been a few versions now that you don't flash a modified boot image. The zip modifies the stock CORRECT boot image itself.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] GuardianUSMC:
OH good to know, thanks for the heads up. I guess reading through everything I must have missed that, will flash the stock boot and see if that fixes it, thanks.
[SuperSU] :
In update failure thread nobody answers. Here they do. So...

Hey man. I need your help. I have a samsung galaxy s3 with official cm13 and your supersu 2.62. if i wanna flash 2.62-x my phone doesn't boot. I comes to the end of optimizing apps and thats it. What do i have to do, to make it work? I tried to wipe cache, dalvik and /system. I know it's systemless. So what do i have to wipe? Data and / or internal storage? Please help me
[SuperSU] cavedano8:
Guys is possible to access temporarily to /system partition in r/w with systemless (2.64) with adb controsl?

Sorry for noob question
[SuperSU] kontini:
I like this, what I don't like is that I had SuperSU v2.52 installed in /system and after applying v2.64 the installer deleted SuperSU from /system and applied a system-less root and I think there is no reason to do that because if I previously patched my boot image and I had already chosen to have a system-based root the installer should have had detect my kind of root and only replace my old SuperSU without needing to "echo SYSTEMLESS=false>>/data/.supersu" that ovverrides this, in my opinion, bad behaviour and anyway I thank you it worked
[SuperSU] Chainfire:
How did you previously patch your boot image? Can you post the old patched image?

Depending on how you patched that boot image, the behavior you saw is probably normal and will not be changed. Note that if you have a system-based install and you update through the APK instead of the ZIP, it will always stay system-based.
[SuperSU] burduli:
I got into bootloop after flashing v2.64
[SuperSU] kontini:
I simply used previous systemless root installer and then I wiped data

Now, reading your words I believe that if I had had a fresh wiped stock boot and system and had set SYSTEMLESS=false and then I had flashed v2.64 the installer would have not patched my boot image. Shouldn't this give me the chance to do system-based root instead of a bootloop?
[SuperSU] Chainfire:
Without details like which firmware you are running, which SuperSU version you were running before, if it was system-based or system-less, etc, there's nothing we can do with that information.

If you used previous systemless root then how did you end up with 2.52 in /system? That doesn't make any sense.

Additionally, if you had done what you state above, you would have bootlooped, as the stock 6.0 image does not allow system-based root.
[SuperSU] buzzwyzr:
Don't think that's the problem. Layers worked fine on 2.62-3. I have 338mb free in the system partition.

So I reinstalled busybox and Layers are now working again.
[SuperSU] burduli:
Sorry, I'm running CM12.1 by [MENTION=3117667]pawitp[/MENTION], I was running v2.62-3 before, it's system-less I guess.
[SuperSU] kontini:
I told you that after systemless root I wiped data, what I didn't told you is that I have last stock MM v6.0.1 for hammerhead. I removed some apk from system/app freeing space (I free more than 40MB to be sure I don't have write error in /system) and then I flashed v2.52 and root perfectly worked. This is the reason I tell you that setting SYSTEMLESS= false the installer should patch my boot image and install system-based root but

MAYBE

SYSTEMLESS in your script is the variable that not only decides what kind of root but if patch or not the boot image too. I can always flash v2.64 to patch my boot image, set systemless to false and flash it again.

Anyway I know you are doing so much and you are dealing with code, installer, app, system or not system, different ways to root a firmware or patch a boot image and users like me. I'm only testing and just telling, not suggesting, I already have what we are talking about and I always trust your choices are the best. I know I'm not your boss, here you are ...and that's pretty clear to me!
[SuperSU] TigerSoul925:
How can I go from systemless root to traditional root? I ran into problems with an app not working with systemless and I'm adding xposed anyway, so how do I remove systemless root and go for traditional?
[SuperSU] Maxr1998:
It would also be very helpful to know why it's bootlooping, means a logcat while booting would be nice ;)
[SuperSU] burduli:
I have already restored backup :/
[SuperSU] shoey63:
That's your problem right there. Systemless root is (partially) stored in /data. By wiping it afterwards, you totally borked it.
[SuperSU] kontini:
I have no problem, my purpose was to remove system-less root and put SuperSU in /system because if in the future I want to do a factory reset my device would keep being rooted.

Anyway if this is considered to be a problem only mine, I'm sorry I've bothered enough people today. Thank you everybody.
[SuperSU] Poag:
Are you on a locked or unlocked BL?
[SuperSU] ArN0V:
Can we flash 2.64 system less over 2.63 system less?(nexus 6p 6.0.1 stock)

Envoyé de mon Nexus 6P en utilisant Tapatalk
[SuperSU] clothednblack:
Same here, had to do a restore to fix it. Didn't have that problem on previous version
[SuperSU] Chainfire:
Neither you nor the guy you quoted has included any information regarding phone or firmware...
[SuperSU] Antoine Vdb:
Sorry for my noobish question here but does systemless root means no changes can be done in the /system partition ? (Like editing the build.prop or removing system apps)
[SuperSU] Alxoom33:
There is no 2.63! However, you can flash 2.64 over 2.62-3. But why ask if you did not read [MENTION=4182290]cainfire[/MENTION]'s instructions when he posted 2.64. Are you going to just take my word?
[SuperSU] ArN0V:
I read the instructions but i see nothing about flash over...thx anyway for your answer

Envoyé de mon Nexus 6P en utilisant Tapatalk
[SuperSU] Alxoom33:
Sorry, I thought they did, and you are very welcome for your polite response. However, several users testing 2.64 have reported on this thread that they successfully flashed 2.64 over prior 2.6x versions. So flash away!
[SuperSU] azsl1326:
If I am on 2.64 systemless and want to go to traditional root - 2.52, can I just flash the 2.52 zip? On Nexus 6P.
[SuperSU] berndblb:
No. You have to factory reset, flash the modified boot image, then 2.5.2
[SuperSU] SamuriHL:
Apparently a factory reset wipes the cache. S4 lost the backup image for stock recovery in the process and failed the update to 2.6.4. To be clear, I'm only providing info here....the result was completely expected. I did not re-encrypt the data partition after the factory wipe on that phone as I'm not using it as a daily device. I'm using it for providing new ODIN images to the S4 GPE owners, so, system less root is a godsend to me. In any case, just wanted to report my experience upgrading the S4 after a factory reset, which again, was not unexpected. reflashed stock boot and all was fine. Haven't done the note 10.1 2014 yet, but, it's not had the cache wiped so I expect no issues. The NX6 had no issues upgrading.
[SuperSU] azsl1326:
Thanks. Or can I use this method found in your guide?

su
(you'll need to grant Supersu access at this point)
mount -o remount,rw /system
touch /system/bin/su /system/xbin/su
mount -o remount,ro /system
[SuperSU] clothednblack:
Sorry, was on a quick break at work.

Pure nexus rom 6.0.1

N6

Previously, I flashed unSU then systemless root, no issues. Rom updated last night, so this morning I flashed unsu (rom update gave me system root) then latest systemless root and fc galore.
[SuperSU] berndblb:
Uh? I don't have a guide in the Nexus forums... I'm a noob here :D

Oh - you are mixing me up with Heisenberg! Too much honor! No relations - just a similar avatar ;)

Try it - if he says it works, it probably does...
[SuperSU] goinflyn:
Does anyone know if the modified boot image knocks out WiFi calling on T-Mobile? I'm on 6.0.1 nexus 6 with systemless root and franco kernel and can't get WiFi calling to work.
[SuperSU] Ch3vr0n:
Read the last dozen pages and instructions. You need STOCK system/boot. The beta zip modifies the boot itself, you don't flash modified boot images.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] pkelly517:
I'll add that I saw the same thing Sunday morning on a 5X, also on Pure Nexus. Also using the unSu zip. I had to clean flash. After it was all said and done, I suspected maybe the installed busybox looking in /system/xbin. But I'm now running system root and 2.52. It works, and I had too many errands to run today to worry about what else I could screw up.

I'll have oodles more time come next Sunday.
[SuperSU] azsl1326:
Yea - my bad. Just looked at the avatar and not the name. Thanks for the assistance!
[SuperSU] vjtigas:
How can I root CM13 (6.0.1) using the traditional method? When I flash v2.64, it roots using the systemless mode.
[SuperSU] Blac Caesar:
[MENTION=631273]Chainfire[/MENTION] ..Flashed v2.64 over v2.62 (Systemless). No errors, or fcs. OnePlus One, latest CM-13 nightly
[SuperSU] lordmago:
Install SUperSU 2.64 on 2.52 on Lollipop ROM

Hi everybody, I read last few pages and it seems possible to update SuperSU from 2.52 to 2.64, using apk file, in a lollipop rom (I'm on LeeDrOiD's One M8 rom, stock kernel, http://xdaforums.com/htc-one-m8/development/rom-leedroid-one-m8-l-v1-0-5-t3019102+4.16.401.13 firmware). Did I understand correctly? :confused:

--------

I installed apk and then launched SUperSU. I selected to continue update not through TWRP.

It asked to reboot phone. I launched SUperSU and it's written 2.64 version: moreover, in Settings-System, it gives me the possibility to "Install SuperSU into /system", that means to convert it into a system app.

Will see next days what's going to happen (obviously made backup in twrp before :fingers-crossed:)...
[SuperSU] vjtigas:
Yes. I did that. Updated package to 2.64, updated binary, installed updated app to system.