I moved v2.52 script with little modifications (aside from the ui_print).
Thank you!
I moved v2.52 script with little modifications (aside from the ui_print).
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.Doesn't work on Samsung Note 4 N910G android 5.1.1, stock rom with custom kernel. Stuck on Samsung logo. Tried 2.66
Official supersu2.66 works on custom kernel. But this system root supersu2.66 doesn't work on custom kernel that I tried.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
Looks like imei loss.There is a thread for that.Solutions maybe flashing v2.65 (what??) or restore efs backup (if you have one).Doesn't work on Samsung Note 4 N910G android 5.1.1, stock rom with custom kernel. Stuck on Samsung logo. Tried 2.66
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.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
Maybe SELinux or permission problems.Trying to fix the script.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
Push files into system partition and set perms manually.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
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.
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...
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...)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...)
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...)
HI, can you pls get BETA-SuperSU-v2.67-20160121175247 as installs in System-Mode.
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...First part,
use adb push for the files.
then install SuperSU manually on your phone.
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...Maybe you should make a new thread about it.Because this is new SuperSU in system mode only thread.
1. Its caused by nothing to start root.In this case 99SuperSUDaemon or install recovery.sh.Probably.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...
You should read OP, that you'll need custom kernel before flashing old school root.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.
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.You should read OP, that you'll need custom kernel before flashing old school root.