yashsingh1/xdaforums huggingface dataset:
[SuperSU] cossak2007:
Custom CM 14 - 7.1 Rom by Santhosh - Cannot Root

Already flashed the supersu 2.78 & also SR1 versions sucessfully from TWRP 3x already but still cannot get root.

First time ever over the past 5 years and many phones that I am not able to get root.

Have never been able update Supersu with the Play Store Supersu app as error from TWRP installation , so I have manually flashed the newest Supersu .

Maybe an issue with TWRP?

Used ALKA version and now have tried the 3.0.2.0 Dad11 custom version with same results.

No problems with rooting on 7.0 but now have with 7.1

Wiped clean all the partitions including SD storage

Installed SR2-SuperSU-v2.78-SR2-20161029143931.zip

As usual, no errors during installation from TWRP

Boot phone and still no root.

Ran Supersu app and it tells me to update and I choose to update using TWRP

Phone reboots and installation of update.zip begins

Error ZIP file is corrupt

Error installing zipfile " /cache/recovery/update.zip"

Flash Supersu manually again. Reboot and still no root.

Attaching Root Checker Pro snapshots to see if it helps someone come up with a solution.

I am perplexed by this issue and need help.

No solutions on XDA rom thread

Thanks
[SuperSU] Paschfire:
I am Running DUv11 7.0 N Rom on my Nexus 5 using FK r98 without encryption, the SuperSU menu in natively built into system settings, I also have "no logs available" displayed when using SuperSU2.78SR2.
[SuperSU] grep_i:
Please be more specific and come up with at least an error message, what you shared is just a screenshot of flashing, no error at all except for not patching sepolicy further than that everything went well.

Maybe you can try and look in recovery.log to see if it logged something more specific than this.

One last question is root working or not I guess it's working is it possible you have your sepolicy set to permissive ?
[SuperSU] Ch3vr0n:
New random reboot after reflashing SR1, "com.google.phone" or something has stopped. Had to manually force a reboot. Seems too be fixed for now.
[SuperSU] grep_i:
And did you find out why or how this happens so you can make a nice error report so the dev can fix this ?
[SuperSU] chyri1:
Not root CM14.1 7.1 in Hammerhead, after install zip, root not work, only work root of ROM
[SuperSU] Pkt_Lnt:
Yes he does, just like you. (Always happy to see devs get donations!)
[SuperSU] Alxoom33:
I have not had a charging problem with either of my devices rooted with 278 SR2. Google Pixel C running 7.1.1 and Nexus 6 running 7.0
[SuperSU] egingell:
Successfully updated my SGS5 via the apk in the zip. I will post if I have any of the problems I've seen posted. I barely use the phone, so the battery drain issue should present itself if at all.

The logs work fine on my SGS5.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] SecUpwN:
Thanks, but I meant to send CASH. Possible?
[SuperSU] Ch3vr0n:
no i havent found it why. I was sleeping at the time. But there's no way a 6P that was at 100% 2hrs earlier would be "dead" 15h later doing nothing.

I didn't say i had a problem charging, i said the battery was drained. Everything else i've said in an earlier reply. SR2 Slows 6P down to a full lockup where the device shuts down, root doesnt respond to a simple check with "root checker basic". SR1: no such issues. Also I'm not using a pixel C running 7.1.1 or a Nexus 6. I'm using a 6P

Of course you can't. Different device, different rom... I'm using 6P on Android 7, not a note 4 on costume rom.
[SuperSU] j1gga84:
I think it was already asked before but does it run on Android 6.0.1 or does it make sense to flash over 2.78 SR1?

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[SuperSU] runtime_Err0r:
I'm unable to make Xposed to work with my HTC 10 using LeeDroid and Ex kernel on MM.

Xposed installer says that xposed is installed but not enabled. Logs are empty. I've tried with 86.1 and 86.2.

View attachment 3920751

View attachment 3920752
[SuperSU] Ja_som:
Wrong thread, this thread is for SuperSU....
[SuperSU] Ch3vr0n:
There's definitely something wrong. Charged to 100% again, had like 7hrs left and only thing under battery usage was android system. Reflashing factory image (-w) and flashing SR2.

edit: no dice. Root doesnt respond as expected. Reflashed SR1, hoping it'll work this time. I'm running out of idea's other than a full factory reset (incl data). All possible logs i could thing of added
[SuperSU] vt0r:
Still no logs or useful debug info. Why not get the list of wakelocks at least? BetterBatteryStats can do that for you if you prefer a GUI method. Also, a logcat and last_kmsg could be helpful, depending on what the cause is.
[SuperSU] Ch3vr0n:
As i said, the only thing at that point was "Android System" using battery. But all logs i could think of were now added to previous post. Anyway. Something's off. Doing full wipe reset. Full factory wipe. Just SR2 and root checker: The access toasts come up. But it ends there. Root checker basic sais "incorrectly installed"
[SuperSU] kylemd:
[MENTION=631273]Chainfire[/MENTION] having problems installing SuperSU on a F2FS formatted partition. Logs below. Is this a SuperSU or TWRP problem?
[SuperSU] egingell:
I have no excessive battery use and root still seems to work.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] humdogm:
S5 no longer boots after installing SR2

Hi, I have a Samsung Galaxy S5 on Marshmallow.

I had installed SuperSU v2.78 SR1 systemless a few weeks ago, and it was working fine, I was using suhide and xposed as well just fine.

Yesterday I installed v.2.78 SR2 systemless; when it first booted it was really slow and took a while for the "Grant root" prompt to show up for any root apps I had installed. However, it slowed to a crawl and eventually rebooted. From then on, it did the same thing except on first boot it showed the "optimizing apps" thing. It didn't finish optimizing all apps before it booted up, and then it did the thing where it was slow again. Then I rebooted one more time, after which my phone would no longer boot past my carrier screen. I booted into recovery to save my data partition before reflashing stock firmware using odin and then installing TWRP and restoring my data partition. Now, on stock bootloader my phone can boot fine, but now when I install v2.78, v2.78 SR1, or v2.78 SR2 systemless my phone gets past the samsung animation but it does not boot past the carrier screen.

After restoring stock bootloader I tried using phh's 259 superuser systemless, and it worked, so now I have root back. What sort of logs would I need to go through or what would I need to do to troubleshoot? Also, what would I need to provide to get some sort of support?

PS: Also when I restore stock bootloader from TWRP or through odin, I lose TWRP after reboot. Is this normal?
[SuperSU] Ch3vr0n:
See, I knew I couldn't be the only one when 'slow' and 'reboot' issues.
[SuperSU] 89titanium:
Hey everybody. Would I need to uninstall my phh superuser before installing this SuperSU? Do I just uninstall from my app drawer?
[SuperSU] Alxoom33:
Dahh... no battery drain either. You know, you could be a little bit more polite to people who are trying to help you. Replace that 6p with a real Pixel! ;) LOL!

Edit: Sorry, your last post kinda got me going. How about some logcats so we can figure out your battery drain.
[SuperSU] luigidk:
I recently did a full unroot following a cleanflash/root of a new rom. I started out in root so I could restore my apps using Titanium Backup. However, once I completed that I did a full unroot so I could pass SafetyNet.

The full unroot didn't work - I had to do a dirty flash/re-flash kernel.

Is there an add'l step/file/directory removal I can do to avoid the need to dirty flash?
[SuperSU] ulxerker:
no, because it mainly effects the new Pixel phone and it introduces some issues on other phones.
[SuperSU] grep_i:
It runs on Android 6.0.1 I have it running myself on a Nexus 5 with Android 6.0.1 and you can flash it over 2.78 SR1.

It's up to you to make out if it makes sense to flash it.

---------- Post added at 11:35 AM ---------- Previous post was at 11:30 AM ----------

When restoring stock boot.img you revert back to stock kernel and stock recovery also and that's why you loose your custom recovery so yes that's normal behaviour.
[SuperSU] RandomPooka:
Recovery on the s5 is in the boot image?
[SuperSU] Ch3vr0n:
[MENTION=4100646]Alxoom33[/MENTION] logs? I provided everything I could log wise in post 7701

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[SuperSU] zigonneux:
noob question, on a stock MM6 rom on samsung Tabs 10.5 , rooted with supersu pro and SuperSU v2.78. Why does some applications say that I'm not rooted. Like ES file explorer, I can't activate the root explorer. Something seem to be locked somewhere , no ways to make system writable to change the boot animation. I was able to debloat that Rom though.
[SuperSU] OsniNO:
RIL fixed in Moto G 2014 CM 14?

Edit: I'll test
[SuperSU] corkiejp:
ES File Explorer has been discussed many times in the SuperSU Thread, either enable compatibility mode of supersu or get a better app!

ES File Explorer is loaded with garbage, here is 4 better alternatives.
[SuperSU] ruchern:
Which variant of SGS5? SM-G901F?

---------- Post added at 01:39 AM ---------- Previous post was at 01:38 AM ----------

Could it be the 06suhide problem? Chainfire did mention to delete that before updating to the next release.
[SuperSU] egingell:
SM-G900T

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] zigonneux:
only $2.00 canadian for solid explorer pro, thanks for the tip. :good:
[SuperSU] LinoX:
Is there a way to avoid losing the settings of supersu every time I flash the zip from recovery?

I am on CM nightlies and every time I flash a nightly I have to reflash supersu (zip) as well..but doing so makes the app lose all the authorizations I already gave to apps....
[SuperSU] ashyx:
Why not just back it up with TB?
[SuperSU] LinoX:
That could be an option but modifying the installation script like "if .apk is installed don't delete apk's data folder" could be more user friendly, no? Maybe in the SR3...:p
[SuperSU] ruchern:
Root Explorer is fine too, if you are looking for paid options.
[SuperSU] Ch3vr0n:
Not in my case (same slowness and reboots...). I never did the 06 "fix" as i knew it wouldn't last very long anyway.
[SuperSU] ashyx:
I think the script does that so it starts with a clean slate to prevent issues.
[SuperSU] grep_i:
But your not loosing the apps, is it possible you have root flashed as systemmode or comes your CM nightly prerooted ?
[SuperSU] egingell:
SuperSU is actively ignored by Titanium Backup as are other apps which enable the "no backup" flag.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] ashyx:
I can backup and restore supersu app settings and authorizations just fine with TB.
[SuperSU] egingell:
The only one that shows up on my app list is SuperSU Pro, which is not the same app.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] ashyx:
Not sure what you're getting at here?

Supersu is listed in the app list. It can be backed up and restored.

Supersu free v2.78 SR1.
[SuperSU] Vadzhik:
Hi, how to install systmless SuperSU 2.78 SR2 on android 5.0, where to get this patches?

Tell me please, where can read the manual?
[SuperSU] dtriguero:
had some issues after flashing supersu 2.78 Sr2 over Sr1. My phone is a Tmobile S4 sgh-m919 and i have it unlocked to run on at&t. i unlocked it back when on MDL firmware/modems using the golden backup method and region lock away [MENTION=631273]Chainfire[/MENTION]. all has worked fine and remained unlocked over numerous flashs until now. i flashed the supersu 2.78 Sr2 over the Sr1. Sr2 flased fine phone rebooted and all seemed good. After a few hours my phone suddenly rebooted. i no longer had root phone was saying my sdcard was corrupted and was asking for the sim network unlock code. i opend es file explorer and found /su was there but noting in it as if su.img was blank or gone. Booted to twrp looked in data the su.img was there but /data must of got corrupted so resoted my backup i made prior to flashing Sr2. apon reboot root was back(Sr1) and my sdcard was working again but it still said i need the sim network unlock code. i was able to unlock again thankfully i still had the old stock tars for mdb and tars for mdl modems. i downgraded to thoses redid the unlock steps and it worked restored my backup and flashed the nk2 modem tars and all is back up and running unlocked. not sure what Sr2 did when flashed only thing i noticed was it imported the new root method. I not sure why it would cause phone to sim lock again maybe [MENTION=631273]Chainfire[/MENTION] could fingure out what happend. well long story short i was able to get it all fixed but will be staying with Sr1 till i or someone with more knowlage can figure out why this happend. for all i know it could of just been a one time fluke. The rom I was on when happened is aokp mm by [MENTION=7026648]AlaskaLinuxUser[/MENTION] and his dev kernel. the backup I restored after reunlocking is the same rom/kernel setup

sent from my SGH-M919 BadAss TinkerToy
[SuperSU] egingell:
Well, there's this as it has always been for me:

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] humdogm:
I never used 06suhide, so that shouldn't be the issue.
[SuperSU] daywalk3r666:
supersu still breaks the ril on moto g 2014 with cm14/14.1

hope the logs helps to find a solution
[SuperSU] simmusss:
Same problem with xperia m dual also, hope this log will help to developers, ThanQ. By the way super su works with AOSP 7.0 in ur device??
[SuperSU] daywalk3r666:
with tesla N supersu works great.
[SuperSU] Ja_som:
[MENTION=246207]LinoX[/MENTION]

Make a backup of eu.chainfire.supersu_preferences.xml file from /data/data/eu.chainfire.supersu/shared_prefs/

After you reflash SuperSU zip file, copy it back and reboot...

[MENTION=4899305]ashyx[/MENTION]

SuperSU app is not visible in TB, I saw once a modified TB which has this enabled, so, are you sure that you use original TB app? ;)
[SuperSU] CrazyCypher:
I have HTC 10 with stock rom and magisk+xposed+ SuperSU SR1..all systemless...how can I update SuperSU?
[SuperSU] grep_i:
You can start with the updated SuperSU.

I think Magisk is standalone so this would be sufficient.
[SuperSU] trevorcobb:
has anyone tried to install suhide on their rooted pixel or xl?
[SuperSU] Captain_Throwback:
Why would anyone do that? The release notes clearly state that it won't work...:rolleyes:
[SuperSU] Chainfire:
Don't see anything useful in here, sorry.
[SuperSU] Chainfire:
Whats the output of 'mount' in adb shell when in TWRP (before trying SuperSU ZIP) ?
[SuperSU] daywalk3r666:
thx for the answer.maybe cm fix it later.
[SuperSU] fmc000:
SR2 on OPO running Slim7 (Android 7.0) - root works fine but toast notifications had to be disabled to be able to actually use the phone, otherwise they were showing up continuously, like they were looping (sorry if I don't make myself clear, I'm not an English native speaker). The log content is correct and shows only the right entries (i.e. no multiple lines).
[SuperSU] egingell:
The problem with the notification is that it pops up for every single call to su and they queue up. So if an app makes a lot of calls to su, it's going to generate a lot of toasts. It's not necessarily an issue, it's a symptom of an app doing a lot of root stuff.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] fmc000:
The behavior I describe is new with SR2 - never had problems with any of the previous versions.
[SuperSU] Strephon Alkhalikoi:
I found the app backup feature of ES indispensable, and nothing else worked. If you still want the functions of ES, hit the link in my signature. Otherwise, enjoy Solid. :)
[SuperSU] SquallyDoc:
Has anyone tried rooting a Nexus Player with 2.78? I've tried with all 2.78 versions but keep getting a segmentation fault while installing via TWRP.

This is stock Android N: NRD90R (also tried NRD91D with same error). I've attached my recovery.log which I hope helps. I've tried searching and couldn't find anything to resolve the issue. I did however find this:

http://xdaforums.com/showpost.php?p=68456910&postcount=11401

Is this by chance a known issue which hasn't been addressed or a new issue?

Thanks!
[SuperSU] USBhost:
http://xdaforums.com/showpost.php?p=69343083&postcount=441

With a workaround....

I had the same problem but SR2 seemed to have fixed it...
[SuperSU] SquallyDoc:
Weird SR2 didn't fix it for me. Maybe a slightly different issue then? Thanks for the link. I'll give it a try. Didn't see that one with my searches.
[SuperSU] Lord Meshadieme:
- Calling user ramdisk patch script

--- Failure, aborting

my log when trying to install after a clean system + boot reflash.

Is something wrong? HtC 10 stock rom
[SuperSU] phyl0x:
same message here galaxy s6... not sure what's up.

UPDATE: fixed it using a rootpatch file found in this thread, that post is about galaxy s6...not sure if its safe for other phones.
[SuperSU] rhyzan:
Try to flash the stock image again in a clean system (clear it all out. Format data too. Everything.) and don't reflash your boot image since the stock image has boot included.

Had the same problem whenever I try to flash SuperSU after uninstalling Magisk since it basically flashes back the stored stock image after removing some magisk files.

---------- Post added at 02:43 AM ---------- Previous post was at 02:42 AM ----------

Same thing.
[SuperSU] ZabiGarma:
Do you need to uninstall suhide or Xposed prior to flashing SR2?

Do I need to reflash suhide and Xposed after installing SR2?
[SuperSU] bernick:
I have exactly the same problem on my rooted Pixel.
[SuperSU] Chiyo-chan:
Hi,

I had the same issue.

Looking at the code in the SR2 zip file, I pinpointed it to the file /data/custom_ramdisk_patch.sh. Looking inside the file, it's some remains of Magisk. I removed that file via the TWRP Terminal (rm /data/custom_ramdisk_patch.sh) and it solved the problem.

Hope this helps!
[SuperSU] Barzoul:
Backing up Ramdisk Error

Hello !

My device is a Huawei P9 Lite VNS-L31, with Emui 4.1.1 (tried on 4.1 too) a (****) system based on Android 6.0.

I use TWRP 3.0.2-0 and when I flash 2.78 SR2 in systemless mode all the installation is good but at the last line => "Creating ramdisk backup => Error, aborting" => The SuperSU isn't installed and doesn't work at all :/

Could you help me please ?

Thanks in advance !
[SuperSU] grep_i:
Check recovery log for errors if you can't read it yourself post it here.

You can find it at /cache/recovery
[SuperSU] afr33sl4ve:
So, I'm having an interesting issue. The flash is successful, however, the app doesn't initialize.

It has the first splash screen, with the 2 options (new user/expert), then it goes nowhere.

Using CM13 nightly with Galaxy S5.

EDIT: Please disregard. Turns out there's some issue with the root in anything higher than 1028. Rolled back to 1028 and it works.

Ok... suhide now is failing with SR2 isn't installed in systemless mode. :confused:
[SuperSU] Chainfire:
Post your boot.img so I can reproduce it on my end and possibly fix it.
[SuperSU] Assenssins:
SuperSU icon is visible outside of Setting. It would be great if we Supersu icon only visible inside of setting.
[SuperSU] asert:
Not the same poster but I have the exact same problem, I use the same procedure as SR1 but I get the ramdisk backup error.

After rebooting the phone is unrooted and still pass safetynet

Huawei P8 GRA-UL00 B370 Android 6.0 EMUI 4.0.1

Here's the boot.img

Thanks!
[SuperSU] Äptiva:
[MENTION=4544860]osm0sis[/MENTION] if you added "/system/bin/su" to the list for rm in your unSU script it would also help to remove all traces of root from CM so systemless root could be a bit cleaner. Just my .02

Great script and SuperSU is still my fave root management tool to date
[SuperSU] osm0sis:
Well, and I've said it a few times before, that was never what unSU was intended for...

But, that said, there do appear to be thousands of people using it "off-label" this way (current download count is just shy of 58,000 :eek::cool:), so I'll consider an updated version that removes CM's, phh's and SuperSU Systemless.

Not sure when I'll get to it but it's on my to-do and it will be released in my Odds and Ends thread. :good:
[SuperSU] ZabiGarma:
Before I update, do I need to uninstall suhide?

Do I also need to input the "SYSTEMLESS=true" > /data/.supersu. line in TWRP's terminal?

I've never used before, and I've never had problems getting systemless root.
[SuperSU] EatBeans:
Does anyone know how to disbale dm-verity without flashing SuperSU and a custom kernel?
[SuperSU] Captain_Throwback:
Seems like you should have a few more "Thanks" than you do, then, but isn't that always the way...:rolleyes:

Don't worry, I still appreciate you :).
[SuperSU] henderjr:
Newer Samsung device? http://xdaforums.com/android/apps-games/play-pokemon-root-switch-method-patched-t3483179

The no-verity-opt-encrypt-2.1.zip allows me to start stock, flash twrp, and then this zip and boot. Without that zip I have to flash SuperSU in order to boot after flashing TWRP.
[SuperSU] Chaud227:
Can this still happen please? And if not, is there another easy solution, for example, changing the compression on Arter Kernal for the Note 3 to gzip or the other compression format that systemless SuperSU works with? Not sure if its possible or how one would do that, information is scarce on the issue besides a tutorial that temporarily changes the compression while in adb and changes back with a risk of brick if you reboot before finishing. I'm uncomfortable with that particular tutorial.
[SuperSU] EatBeans:
The Problem is that i need the disabled dm-verity for a oneplus3 so I can't just use the ZIP :/
[SuperSU] Strephon Alkhalikoi:
Not a SuperSU issue. Developers need to add support for SuperSU in Settings to achieve what you want.
[SuperSU] Alxoom33:
I believe your issue may be a remenent of magisk in your root/ data folder. Look for a -sh extension labeled file in /data and delete it. It should fix your Su random error.

See above.
[SuperSU] Chainfire:
SuperSU v2.78 SR3 released. Download in the first post, release notes here: https://plus.google.com/+Chainfire/posts/24xhJN724HG
[SuperSU] grep_i:
SuperSU + systemless and CM root cleanup script

Changed the script to clean up Supersu systemless and systemmode not phh as I never used that.

Used this for some time already and it worked.

Today I walked through the script again to see if I missed something because I saw that someone asked you to add /system/bin/su to the removal list and than I remembered I already changed this for my own copy I use to remove all root on my friends devices.

I let the credits to you intact and only added my name and what I changed to it.

As you do not respond to private messages for technical messages I thought I do it like this.
[SuperSU] Barzoul:
Huawei RAMDISK Backup Error

Hello,

Thanks for your answer, I deleted an sh files (like your said to the other user) in /data but doesn't work and there was one week I've fully recovered my phone with stock rom => same error. "Ramdisk backing up => Aborting"

I join to this post the recovery logs + my boot img (in .win extension because I didn't found a .img in TWRP) and the stock_boot.img.

Here the download link : https://mab.to/UzkaKeaXe

Thanks in advance for your help,

---------- Post added at 05:33 PM ---------- Previous post was at 05:28 PM ----------

Hello,

Thanks for your answer, I deleted an sh files (like your said to the other user) in /data but doesn't work and there was one week I've fully recovered my phone with stock rom => same error. "Ramdisk backing up => Aborting"

I join to this post the recovery logs + my boot img (in .win extension because I didn't found a .img in TWRP) and the stock_boot.img.

Here the download link : https://mab.to/UzkaKeaXe

Thanks in advance for your help,

=====================================

WORK PERFECTLY WITH SR3 !!!! THANK ALL THE CHAINFIRE TEAM !!!! :D
[SuperSU] osm0sis:
Thanks, I'll take a look, but I might end up doing things differently since I'll be supporting all the roots. :)