[SuperSU][System-Mode][2.82 SR5]

[KreAch3R]

I moved v2.52 script with little modifications (aside from the ui_print).

Thank you!

 

[lzk123]

Doesn't work on Samsung Note 4 N910G android 5.1.1, stock rom with custom kernel. Stuck on Samsung logo. Tried 2.66

 

[slick97477]

Doesn't work on Samsung Note 4 N910G android 5.1.1, stock rom with custom kernel. Stuck on Samsung logo. Tried 2.66

Im running a Nexus 6p with screwd Rom and elementalx kernel. I flashed 2.64, however it kept failing and giving me a boot logo. I had reinstall stock kernel then su 2.64 then reflash the custom kernel to get su 2.64 to work properly.

Sent From My Nexus 6P.
Screwd Rom experimental 1/09/16,elementalx kernel

 

[lzk123]

Im running a Nexus 6p with screwd Rom and elementalx kernel. I flashed 2.64, however it kept failing and giving me a boot logo. I had reinstall stock kernel then su 2.64 then reflash the custom kernel to get su 2.64 to work properly.

Sent From My Nexus 6P.
Screwd Rom experimental 1/09/16,elementalx kernel

Official supersu2.66 works on custom kernel. But this system root supersu2.66 doesn't work on custom kernel that I tried.

Sent from my iNO 3 using Tapatalk

 

[aufarxda]

Doesn't work on Samsung Note 4 N910G android 5.1.1, stock rom with custom kernel. Stuck on Samsung logo. Tried 2.66

Looks like imei loss.There is a thread for that.Solutions maybe flashing v2.65 (what??) or restore efs backup (if you have one).

Im running a Nexus 6p with screwd Rom and elementalx kernel. I flashed 2.64, however it kept failing and giving me a boot logo. I had reinstall stock kernel then su 2.64 then reflash the custom kernel to get su 2.64 to work properly.

Sent From My Nexus 6P.
Screwd Rom experimental 1/09/16,elementalx kernel

Oh yeah, screwd rom already had root and custom kernel.Try updating by installing Superuser.apk inside common folder in the zip.Then update binary using normal or TWRP if normal failed.Easiest solution is asking the rom dev about it. Its still good that it still works after all.

Official supersu2.66 works on custom kernel. But this system root supersu2.66 doesn't work on custom kernel that I tried.

Sent from my iNO 3 using Tapatalk

Maybe SELinux or permission problems.Trying to fix the script.
######################
Trying to fix those problems buy modifying script. Recovery.log may be needed if the problem is caused by the phone or caused by a script error.Next week ill give the new zip for v2.64 and v2.66 only.

 

[ralfbergs]

How to install in "live" system, not recovery

Hi @Chainfire, all.

I have a problem installing SuperSU in a "live" Android 6.0 system, i. e. not via custom recovery (I don't have one and I can't install one either, but I have "root" via adb, and only in adb, not for apps).

Previously under Android 5.1 I could install SuperSU in the same scenario as described here (using "root" in adb): https://su.chainfire.eu/#embed-exploit

But this doesn't work anymore in Android 6.0.

Is there any way I could install SuperSU without a custom recovery?

Thanks for any help you can give.

Kind regards,

Ralf

 

[aufarxda]

Hi @Chainfire, all.

I have a problem installing SuperSU in a "live" Android 6.0 system, i. e. not via custom recovery (I don't have one and I can't install one either, but I have "root" via adb, and only in adb, not for apps).

Previously under Android 5.1 I could install SuperSU in the same scenario as described here (using "root" in adb): https://su.chainfire.eu/#embed-exploit

But this doesn't work anymore in Android 6.0.

Is there any way I could install SuperSU without a custom recovery?

Thanks for any help you can give.

Kind regards,

Ralf

Push files into system partition and set perms manually.
Hope that helps.

 

[deeplyyoung]

HI, can you pls get BETA-SuperSU-v2.67-20160121175247 as installs in System-Mode.

 

[coolparty]

Samsung s6 edge 128gb. Can't install 2.67. Android 5.1.1 unikernel.


-- Installing: /sdcard/Download/BETA-SuperSU-v2.67-20160121175247.zip
I:skiping set_bootloader_message: no /misc
Finding update package...
I:Update location: /sdcard/Download/BETA-SuperSU-v2.67-20160121175247.zip
Opening update package...
Installing update...
mount: mounting /dev/block/platform/15570000.ufs/by-name/USERDATA on /data failed: Device or resource busy
2+0 records in
2+0 records out
2 bytes (2B) copied, 0.000646 seconds, 3.0KB/s
3+0 records in
3+0 records out
3 bytes (3B) copied, 0.000060 seconds, 48.8KB/s
10+0 records in
10+0 records out
10 bytes (10B) copied, 0.000281 seconds, 34.8KB/s
0+0 records in
0+0 records out
0 bytes (0B) copied, 0.000853 seconds, 0B/s
/tmp/update_binary: line 765: /system/toolbox: not found

*****************
Archive: /sdcard/Download/BETA-SuperSU-v2.67-20160121175247.zip
inflating: META-INF/MANIFEST.MF

.......... Skipped ......

-permissive:domain=ok
-permissive:selinux_net_tmpfs=ok
- Success
skipping journal recoverybecause INCOMPAT_RECOVER was clear.
check whether gdt & bitmap free count is vaild
/data/su.img: clean, 24/2048 files, 1319/8192 blocks
ext2fs_close2 : fs->write_bitmaps is null
ext2fs_close2 : normal operation, return 0
mknod: /dev/block/loop0: File exists
ioctl LOOP_SET_FD failed: Device or resource busy
mkdir: can't create directory '/su/bin': File exists
- Mounting /system, /data and rootfsmkdir: can't create directory '/su/xbin': File exists
mkdir: can't create directory '/su/lib': File exists
mkdir: can't create directory '/su/etc': File exists
mkdir: can't create directory '/su/su.d': File exists

- Extracting filesrm: can't remove '/su/bin/su': No such file or directory
rm: can't remove '/su/bin/daemonsu': No such file or directory

rm: can't remove '/su/bin/supolicy_wrapped': No such file or directory
rm: can't remove '/su/lib/libsupol.so': No such file or directory
rm: can't remove '/su/bin/sukernel': No such file or directory
- System-less mode, boot image support required
mkdir: can't create directory '/su/xbin_bind': File exists
- Creating image
sukernel v2.67 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire

Loading from [/dev/block/sda5] ...

magic: [ANDROID!]
kernel: [21231232] (21231616) @ 0x10008000
ramdisk: [4497743] (4499456) @ 0x11000000
second: [0] (0) @ 0x10f00000
tags: @ 0x10000100
page size: 2048
unused: [0x0002d800] [0x00000000]
dtb(?): [186368] (186368)
name: []
command line: []
extra command line: []
id: [0x7381fefe90277f0f898ce8635b65acb4affbd615000000000000000000000000]

Saving to [/sutmp/ramdisk.packed] ...

sukernel v2.67 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire

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

Decompressing [4497743] --> ungzip: inflate: -3
failed
- Mounting image
- Creating paths
- Removing old files
- Remounting system r/w
- Placing files

******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/sda5
- Extracting ramdisk
- Decompressing ramdisk
--- Failure, aborting

*************************
IMPORTANT NOTICES
*************************
If TWRP offers to install
SuperSU, do *NOT* let it!
*************************
First reboot may take a
few minutes. It can also
loop a few times. Do not
interrupt the process!
*************************

- Unmounting /system
- Done !

 

[NickQuedateConmigo]

Samsung s6 edge 128gb. Can't install 2.67. Android 5.1.1 unikernel.

******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/sda5
- Extracting ramdisk
- Decompressing ramdisk
--- Failure, aborting

Hi. You're problem same with me, v2.67 systemless. I ask my developed ROM, because not used standard boot.img.
So, I used v2.66 system mode zip from this threat not from chainsu. It work. Look at the first page from OP, v2.67 will update next week.

 

[ralfbergs]

Push files into system partition and set perms manually.

Thanks, I tried that already, but it didn't work -- because I don't know what needs to get where, and which perms to set...

Of course I googled for it, but didn't find anything helpful.

Can you give me a clue?

KR,

Ralf

---------- Post added at 10:44 ---------- Previous post was at 10:39 ----------

HI, can you pls get BETA-SuperSU-v2.67-20160121175247 as installs in System-Mode.

Not sure what you're sayin'... Was that targeted at me? (I'm trying to install SuperSU in a "live" system from an adb root shell on a Marshmallow system...)

 

[deeplyyoung]

Not sure what you're sayin'... Was that targeted at me? (I'm trying to install SuperSU in a "live" system from an adb root shell on a Marshmallow system...)

I quoted you or mentioned your user name anywhere??

Sent from my Nexus 6 using Tapatalk

 

[aufarxda]

Thanks, I tried that already, but it didn't work -- because I don't know what needs to get where, and which perms to set...

Of course I googled for it, but didn't find anything helpful.

Can you give me a clue?

KR,

Ralf

---------- Post added at 10:44 ---------- Previous post was at 10:39 ----------


Not sure what you're sayin'... Was that targeted at me? (I'm trying to install SuperSU in a "live" system from an adb root shell on a Marshmallow system...)

First part,
use adb push for the files.
then install SuperSU manually on your phone.
At least youre rooted, maybe.(because normally files are in 0777 permissions)
Or just boot into twrp from fastboot.
And flash the zip while youre still stocked.
Hope that helps.
Second part,
He used reply from bottom section of your post.
He should've read OP before posting.
Third part,
Maybe you should make a new thread about it.Because this is new SuperSU in system mode only thread.Im sorry, don't mean to be rude at you but thats it.

 

[Droidphilev]

HI, can you pls get BETA-SuperSU-v2.67-20160121175247 as installs in System-Mode.

+1

 

[vjtigas]

Request: Please upload a modified zip of SuperSU v2.67 that installs in system mode, thank you!

 

[ralfbergs]

First part,
use adb push for the files.
then install SuperSU manually on your phone.

Sure, but how exactly? I looked into the SuperSU install script (update-binary) and tried to manually do what the script is supposed to do, but when I reboot my phone it cannot execute some binaries, so it's obviously that I goofed up...

Here's a bit of logging that might help people in the know to tell what's wrong: http://pastebin.com/jdzWiBBJ

Or just boot into twrp from fastboot.

As I said I don't have any custom recovery. The phone is a Huawei P8 with a developer firmware that automatically gives me root in adb. I don't think that TWRP for Android 6.0 exists yet, because it's too early (Android 6.0 is still in beta).

Maybe you should make a new thread about it.Because this is new SuperSU in system mode only thread.

Yes, but that's exactly what I want to accomplish. Manually install SuperSU in "/system" mode... This is why I posted here...

 

[aufarxda]

Sure, but how exactly? I looked into the SuperSU install script (update-binary) and tried to manually do what the script is supposed to do, but when I reboot my phone it cannot execute some binaries, so it's obviously that I goofed up...

Here's a bit of logging that might help people in the know to tell what's wrong: http://pastebin.com/jdzWiBBJ


As I said I don't have any custom recovery. The phone is a Huawei P8 with a developer firmware that automatically gives me root in adb. I don't think that TWRP for Android 6.0 exists yet, because it's too early (Android 6.0 is still in beta).

Yes, but that's exactly what I want to accomplish. Manually install SuperSU in "/system" mode... This is why I posted here...

1. Its caused by nothing to start root.In this case 99SuperSUDaemon or install recovery.sh.Probably.
2.OK then.But this thread is made for download.Thats why.And i dont force you too.

 

[Dr Faustus]

Is there an order to which I should flash these in?

Its been awhile since I have done oldschool root (NRT helped streamline things) but since everything is all about systemless root which I cannot use with Layers no matter how much I try to, I want to use the old root system again.

 

[aufarxda]

Is there an order to which I should flash these in?

Its been awhile since I have done oldschool root (NRT helped streamline things) but since everything is all about systemless root which I cannot use with Layers no matter how much I try to, I want to use the old root system again.

You should read OP, that you'll need custom kernel before flashing old school root.

 

[Dr Faustus]

You should read OP, that you'll need custom kernel before flashing old school root.

I have done this but unfortunately it results in a bootloop. Whether I flash the custom kernel first or not it seems to go into a bootloop.

Perhaps I need to look for another custom kernel? Currently (trying) to use the latest ElementalX.