Hey folks
Updated my N700 rom to the version listed in the title (which I got here) and it comes with CWM's SuperUser installed as sys app.
I have the following problem: it says outdated binary and I can't install them or update them. Of course since it's a sys app I can't delete and try to use Chainfire's SuperSU which is the one I prefer. And I don't have root access now, can't restore my Titaium Backups and such.
Downloaded the "fix" from CWM's Market links and reinstalled the app manually but I keep getting the same problem: no SuperUser binary installed and no root access.
Thanks in advance!
Try flashing the supersu zip file that's used for rooting. Or better, try flashing xxlsz Philz kernel zip from recovery.
flashed the supersu.zip and still no luck, will dig for PhilZ kernel now.
http://forum.xda-developers.com/showthread.php?t=1538053
Related
GT-P3110 by RomsWell
Base.P3110OXXBLH1 For the GT-P3110
This is a mostly stock version of the OTA. With a some of the more basic features added.
De-Odex
Zip Align
Rooted
init.d Support
I do not own this device.
Install Instructions
Flash thru Custom Recovery
DO NOT UPDATE SUPERUSER BINARYS YOU WILL LOSE ROOT!
If coming from CM you will need to do a full wipe including System before flashing.
Download Here
Thanks for the ROM. I just wanted to mention that the "su" binary included in this ROM does not match the "su" binary for Superuser 3.1.3. You have the "su" binary for Superuser 3.0.7 and the Superuser.apk 3.1.3. Just need to update the "su" binary to match the 3.1.3 version.
Regards.
Tsjoklat said:
Thanks for the ROM. I just wanted to mention that the "su" binary included in this ROM does not match the "su" binary for Superuser 3.1.3. You have the "su" binary for Superuser 3.0.7 and the Superuser.apk 3.1.3. Just need to update the "su" binary to match the 3.1.3 version.
Regards.
Click to expand...
Click to collapse
Yeah because using the latest version of superuser binarys wasent working when injecting it into the Rom.
deleted
? This is for the 3110. The 3113 has a New update or so samfirm says. But I just got home from work. I prolly won't post it till morning.
RomsWell said:
Yeah because using the latest version of superuser binarys wasent working when injecting it into the Rom.
Click to expand...
Click to collapse
It should work. I have fixed it for my rom and its fine.
Any chances of this working on 5113 or where I can find a similar stock "tweaked" ROM?
Thanks!
RomsWell said:
Yeah because using the latest version of superuser binarys wasent working when injecting it into the Rom.
Click to expand...
Click to collapse
Sorry for doubting you. I tried it with the new binary and it indeed does not work. But the 3.0.7 version works. I wonder why? When I rooted the stock rom (odexed), then the new binary (3.1.3) worked.
I'm not sure but its driving me nuts. I spent a week thinking I was doing something wrong. I have the latest superSU working and updatable. I'm working on the newest p3113 ota if it works on that. I'll fix it on the current uploads.
I have switched over to SuperSU 0.95 and it is working fine. Although, I am noticing some strange behaviour with TiBackup. When I try to "clean dalvik cache", TiBackup just freezes up every time. I'm starting to think that these problems have to do with the "De-Odex" procedure. Would it be possible to create an untouched stock rom (odexed) that is CWM flashable?
Best Regards.
Note:
When I extracted the samsung package (P3110OXXBLH1) to create a custom ROM for testing, I noticed that "boot.img" is not the same as the one in your ROM.
When I extract boot.img from P3110OXXBLH1, this is what I get:
4540672 2012-08-07 02:31 boot.img
MD5SUM:
a08c7f58d6aa99a648e55859281375fe boot.img
Is there something you do to the boot.img to change the size?
Edit: I got it working now The problem was that I was still missing a few files from /system/bin. But, the kernel in your ROM is not the stock kernel for this ROM.
Edit2: The latest su binary for Superuser (3.1.3) is still not working. This leads me to believe that the problem is NOT with the de-odex process. The last stock ROM that I tested with su (3.1.3) was Android 4.0.3. So, maybe the latest Superuser su binary just doesnt work with this version.
Edit3: I found some problems with the updater-script. /system/bin/sh is being linked twice, to two different apps. Also, there is a recursive chmod in the wrong location that is overwriting the chmod permissions in /system/xbin.
symlink("mksh", "/system/bin/sh");
symlink("/system/bin/bash", "/system/bin/sh");
I think the "bash" one needs to be removed.
Edit4: Changing the shell did not fix anything with Superuser.
Hi I'm trying to install above since viper4android wont work with the stock su, but no luck.
I've tried installing from the market per this:
1. Install SuperSU from Play Store.
2. Open SuperSU and grant it SuperUser permissions (important; if you delete SuperUser before you grant rights to SuperSU you lose your root and need to either reflash the ROM or flash the zip I linked above).
3. gone into supersu settings and told it to grant su on boot, and grant to anything in the system folder as well
and I've also tried installing the zip version in recovery. I've also tried using the file manager in recovery to rename the current su binary in system//xbin and put the new one from the zip file in the directory.
Any way I try installing it freezes on boot up and I have to restore a nand to get my TP working again.
Overall loving flintmans new evervolv, it's really smooth, but the sound on the TP is pretty low and crappy sounding without viper4android so it's a pretty big issue for me.
Can anyone help please?
PS I cant find the apk for the current su, maybe thats part of my issue as well. Also Supersu works with 3.4 kernel version of cyanogenmod so its not a kernel issue.
I am a proud owner of OP One and SuperSu Pro. Currently i am using http://forum.xda-developers.com/oneplus-one/development/daily-stock-unofficial-cm12-builds-t2948099 ROM (as of today 15-12 build).
I installed SuperSU through TWRP 2.8 and used to work fine, untill i updated to a new CM12 build. Then i was promted to grand permissions to an app, but i could not press "grant", later opened the SuperSU app and got a message that there is no binary installed, so i tried to reflash the zip noumerous times, but it seems that TWRP is unable to flash the zip.I can flash other zips like new versions of the ROM, GAPPS etc.
It seems like TWRP is not able to flash the SuperSu zip, even though i get a "succesful" message while flashing. I tried cleaning Cache and Dalvik. Also i can't find the log created by TWRP which is suposedly created in data/media/0 so i can't post detailed info about it.
Super Su
There is no Su binary installed and SuperSu cannot install it. This is a problem.
...
Click to expand...
Click to collapse
**** The posted systemless kernel is only compatible with SuperSU 2.56!!! ****
*** Starting with SuperSU 2.60+ kernel can now be auto-patched for systemless root. ***
**As of 06 December 2015 flar2 has released ElementalX 6.02 for Sense Marshmallow **
* If you still desire a stock kernel with systemless root but want to use newer SuperSU see below *
Messed around with the boot.img from today's Marshmallow update and have made it compatible with systemless root.
Systemless root in general is experimental and so is the kernel. I've literally just made it and tested it enough to that it boots and apps are able to be granted root access, so flash at your own risk.
Kernel has been running without issue.
Other than systemless root compatibility, this kernel is completely stock and no other modifications made.
Intructions - Systemless:
Download kernel from here.
Download SuperSU 2.56 beta from this post (only one that works with this method of root).
Copy both to phone
Flash the image directly using TWRP (toggle from ZIP to IMG under install)
Immediately flash SuperSU-v2.56-20151030013730.zip afterwards.
Reboot
TWRP will notify of no SU when you reboot, click DO NOT INSTALL as TWRP needs to be updated to detect this root method (it only looks in /system)
Instructions - Traditional:
Download kernel from here.
Download SuperSU 2.52 beta from this thread (it's the M compatible version)
Copy both to phone
Flash the image directly using TWRP (toggle from ZIP to IMG under install)
Immediately flash BETA-SuperSU-v2.52.zip afterwards.
Reboot
Keeping stock kernel with updated SuperSU:
If you prefer running the stock kernel with systemless root and want to stay current on SuperSU versions you need a stock kernel when you update SuperSU. When SuperSU installs it tries to restore a backup it made of your boot.img from the last time SuperSU was installed. Since this was made before auto patching there won't be a backup. Also, in newer versions it detects if your device needs systemless or if it can modify /system. If TWRP hasn't been told to keep system read-only it will likely default to a /system install. So, if you want to keep stock kernel and systemless root there are two things you are going to need:
Stock Kernel: You can actually use the kernel provided for traditional root as a stock kernel for the purpose of these instructions.
Systemless Override: To guarantee that SuperSU gives you the systemless install over /system you need to create a file called ".supersu" with the line "SYSTEMLESS=true" and place it in /data in TWRP before you install (eg. /data/.supersu). Alternatively, you can download this one (extract from the ZIP and place in /data).
When the file is placed in /data flash the boot.img in TWRP and then flash SuperSU. It will make a backup when it installs so don't remove it as it will look for this backup again when you install an updated version.
Note: These are only to tide us over until HTC releases source allowing awesome devs like flar2 to work their kernel magic.
Not checked yet, but is systemless the only way to do it on 6.0 ?
Electronic Punk said:
Not checked yet, but is systemless the only way to do it on 6.0 ?
Click to expand...
Click to collapse
No, you can still do it by modifying /system, but Marshmallow made it so kernels had to be modified as well to allow root. @Chainfire took it a step further, since we already have to modify the boot.img we can modify it a little more and remove the need to alter /system and make it easier to accept OTA updates. The link I put in the OP explains it a little more, but here it is again.
Added root modified kernel for using "traditional" (modifies /system) root to the OP along with link to current Marshmallow compatible SuperSU.
I'm trying to do a systemless root. Just to confirm, I should flash the latest TWRP. Then from there flash the kernel then SuperSU both through TWRP?
mcta said:
I'm trying to do a systemless root. Just to confirm, I should flash the latest TWRP. Then from there flash the kernel then SuperSU both through TWRP?
Click to expand...
Click to collapse
If you still have stock kernel and no root you can just flash the latest SuperSU (v2.65).
If you're systemless already but don't have a backup you need to flash a boot.img that isn't already systemless modified as SuperSU will abort the install.
You can't flash the one in the OP for traditional (modifies /system) root and it will patch that one, but unless your set your /system partition to read-only, it will install using traditional root (this is the case with any unmodified boot.img not just this one because it's modified for traditional root). To make sure SuperSU installs using systemlesss you need to place the mentioned .supersu file in /data/ o make sure system is read-only in twrp. You also want to use latest SuperSU.
Just make sure you don't let TWRP install it's own SuperSU package that it includes. TWRP by default can't detect systemless root installs, so each time you reboot from TWRP it will warn that there is no root access on the device. It is important you make sure to click DO NOT INSTALL.
If you don't want to be bugged with the no root message in TWRP you can download this version which has the incompatible SuperSU package removed disabling the root check.
HAHAHAHAHA!!!!! Silly me...... it was written up there......
mcta said:
I'm trying to do a systemless root. Just to confirm, I should flash the latest TWRP. Then from there flash the kernel then SuperSU both through TWRP?
Click to expand...
Click to collapse
Okay, hopefully this is a stupid question, but I want to be sure before I flash something to boot.
I followed the instructions before the later versions of SuperSU betas came out, so I have the above linked custom boot image, but would like to be able to update to later versions. Can I safely assume that the boot_signed.img file I pulled out of ROM.ZIP in the Developer Edition Marshmallow RUU is the correct "stock" bootloader? Note that I ran the RUU, let it pause on accepting the license, then pulled the ROM.ZIP out of the temp folder to extract the binary.
Hi! Im pretty much new to rooting and I was wondering does the phone have to be S-OFF or S-ON. If it has to be S-OFF, how do you do it?
Thank you for help!
Hello everyone,
So I wanted to root my Honor 5c (NEM-L51) under android 7.0, so I have unlocked the bootloader, I have installed a custom recovery compatible with android 7.0 which is twrp-3.1.0-2-hi6250 I think ...
Then I tried to flash the supersu.zip, I had to try several versions because many did not work and indicate "image boot patcher" failure aborting "then I flash a supersu that works but I have the impression that the root has badly installed ...
I explain, first I test with root checker which tells me that everything is fine, but I can not update the binaries su as the supersu app asks me ... I reboot remove , Reinstall the app supersu NOTHING does !! So I wanted to remove the root to reinstall it properly but it does not want to be deleted (root checker still shows the presence of the root) more so I wanted to delete it manually but the file "system / bin / su " and "xbin / su "are not found there is only one su "su" file at the root directory...
Maybe the best method would be to flash the emui stock rom 5.0 but it is not found, and it seems to me that you must also remove the root to avoid any "brick"..
if you have solutions to my questions it would be fine !!!!!
Thank you in advance !!!
Curiosity2000 said:
I explain, first I test with root checker which tells me that everything is fine, but I can not update the binaries su as the supersu app asks me ... I reboot remove , Reinstall the app supersu NOTHING does !! So I wanted to remove the root to reinstall it properly but it does not want to be deleted (root checker still shows the presence of the root) more so I wanted to delete it manually but the file "system / bin / su " and "xbin / su "are not found there is only one su "su" file at the root directory...
Click to expand...
Click to collapse
I have the same problem with the latest stable SuperSU (2.82) that asks me to update the su binary and fails.
As for the su binary not found in /system/bin and /system/xbin it's probably because SuperSU made a systemless root (check this).
And be advised there might be some problem with restoring in the TWRP version you found (see here).
[EDIT]: I was able to update my SuperSU installation by flashing the latest stable version from the official thread with TWRP.
sclarckone said:
I have the same problem with the latest stable SuperSU (2.82) that asks me to update the su binary and fails.
As for the su binary not found in /system/bin and /system/xbin it's probably because SuperSU made a systemless root (check this).
And be advised there might be some problem with restoring in the TWRP version you found (see here).
[EDIT]: I was able to update my SuperSU installation by flashing the latest stable version from the official thread with TWRP.
Click to expand...
Click to collapse
Okay , thanks you for yours answers, I have effectively a supersu systemless I will test yo flash the latest supersu, if it don't work I will remove the su and flash an other twrp or flash the rom stock I think ...
[EDIT] I success to remove the Root systemless with flash the boot.img , but the latest supersu doesnt work for me . I try to install Magisk
[REEDIT] Okay, I success to flash Magisk 13.3 I am root
Stay with magisk, it is better than SuperSU
PalakMi said:
Stay with magisk, it is better than SuperSU
Click to expand...
Click to collapse
Okay thanks you !
Curiosity2000 said:
Okay thanks you !
Click to expand...
Click to collapse
No prob