FORUMS
Remove All Ads from XDA

[STABLE][2016.07.05] SuperSU v2.76 [CLOSED]

11,416 posts
Thanks Meter: 88,011
 
By Chainfire, Moderator Emeritus / Senior Recognized Developer - Where is my shirt? on 9th March 2012, 09:20 AM
Thread Closed Email Thread
3rd September 2016, 07:10 PM |#11491  
Senior Member
Thanks Meter: 132
 
More
Quote:
Originally Posted by Didgeridoohan

When flashing through TWRP the script examines the boot image for previous modifications. If found, it restores an unmodified backup, saved from the first time flashing SuperSU. Read the script output in TWRP and you'll see it happening.

That's probably why your kernel suddenly reverted to an old version.

i thinks this is a possibly solution... infact the first time i have flash supersu zip it's immediately after recently installation of latest cos 13.x zip file and immediately before i have flashed the beta5 of boeffla kernel (and in next days the upgrade) and now every time i reflash the supersu zip this beta5 it's been restored over the latest.....

At this point... how i can avoid this restored? or how i can check the files restored by supersu zip?
 
 
3rd September 2016, 11:08 PM |#11492  
ktmom's Avatar
Senior Member
Thanks Meter: 1,960
 
More
Quote:
Originally Posted by DjDiabolik

i thinks this is a possibly solution... infact the first time i have flash supersu zip it's immediately after recently installation of latest cos 13.x zip file and immediately before i have flashed the beta5 of boeffla kernel (and in next days the upgrade) and now every time i reflash the supersu zip this beta5 it's been restored over the latest.....

Dating back to V2.74:

Quote:

Ramdisk backups

To reduce the impact of lost boot image backups for the future, starting v2.74, the SuperSU ZIP installer (and thus also CF-Auto-Root) will backup changed files in the boot image ramdisk to the ramdisk itself.

While this backup is not good enough to restore your original boot image to the exact state required to perform an incremental OTA, it should be good enough to be able to re-flash SuperSU even if the full boot image backup got lost - though I make no claims as to what happens if you mix it with custom kernels.


Quote:
Originally Posted by DjDiabolik

At this point... how i can avoid this restored?

It was well said in post 6354.

Quote:
Originally Posted by DjDiabolik

or how i can check the files restored by supersu zip?

After flashing in TWRP, you can run:
Code:
"adb shell cat /tmp/recovery.log”
4th September 2016, 11:47 AM |#11493  
Junior Member
Thanks Meter: 0
 
More
Doesn't work for me, here's the description. Please help.
0) Samsung Galaxy Alpha (probably most similar to S5)
1) Rooted via Kingroot
2) Ran some root checker app and it said it was ok
3) Installed SuperSU from Google Play Store Market App Repository whatever
4) Clicked through the initialization process
5) It said something like "Disabling Knox Failed"

What do I do now?
4th September 2016, 12:57 PM |#11494  
ktmom's Avatar
Senior Member
Thanks Meter: 1,960
 
More
Quote:
Originally Posted by JerBearrr

Doesn't work for me, here's the description. Please help.
0) Samsung Galaxy Alpha (probably most similar to S5)
1) Rooted via Kingroot
2) Ran some root checker app and it said it was ok
3) Installed SuperSU from Google Play Store Market App Repository whatever
4) Clicked through the initialization process
5) It said something like "Disabling Knox Failed"

What do I do now?

Try rebooting the giving it another shot. This is pretty specific to your device, you'll find more answered in your device forum.
4th September 2016, 04:31 PM |#11495  
Junior Member
Flag Saint-Petersburf
Thanks Meter: 3
 
More
Flashed v4. Everything works fine, video saving OK. One question, is there function in AOSP to hide navi bar in apps?
UPD. Video saves in camera 4.1 720p. 1080p makes it crash.
4th September 2016, 04:37 PM |#11496  
Pkt_Lnt's Avatar
Recognized Contributor
Flag SLO
Thanks Meter: 5,796
 
More
Quote:
Originally Posted by SqoLi

Flashed v4. Everything works fine, video saving OK. One question, is there function in AOSP to hide navi bar in apps?
UPD. Video saves in camera 4.1 720p. 1080p makes it crash.

Wrong thread. This is the SuperSU root manager.
4th September 2016, 04:38 PM |#11497  
egingell's Avatar
Senior Member
Thanks Meter: 2,072
 
Donate to Me
More
Quote:
Originally Posted by SqoLi

Flashed v4. Everything works fine, video saving OK. One question, is there function in AOSP to hide navi bar in apps?
UPD. Video saves in camera 4.1 720p. 1080p makes it crash.

Um?

...this is a SuperSU thread.

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
4th September 2016, 04:57 PM |#11498  
Junior Member
Thanks Meter: 1
 
More
Can't get SuperSU zip to install
On the TWRP screen when I try to install the SuperSU zip I do see:

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

Not sure what that means, but it doesn't sound good...


Quote:
Originally Posted by grep_i

No can't make sense of it the log does not even contain your attempt to flash SuperSU zip binaries.
It looks more like the booting of the TWRP custom recovery.

Sent from my Nexus 5 using XDA-Developers mobile app

4th September 2016, 05:03 PM |#11499  
Mesmurized's Avatar
Senior Member
Thanks Meter: 295
 
More
Quote:
Originally Posted by rdmd

On the TWRP screen when I try to install the SuperSU zip I do see:

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

Not sure what that means, but it doesn't sound good...

What TWRP version? -1 and -2 have known issues.
4th September 2016, 05:07 PM |#11500  
Pkt_Lnt's Avatar
Recognized Contributor
Flag SLO
Thanks Meter: 5,796
 
More
Quote:
Originally Posted by rdmd

On the TWRP screen when I try to install the SuperSU zip I do see:

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

Not sure what that means, but it doesn't sound good...

What phone and ROM? One of those is unsupported by SuperSU. That is usually a non standard method of compression that causes the ramdisk patch to fail.
4th September 2016, 05:11 PM |#11501  
Junior Member
Thanks Meter: 1
 
More
TWRP version
Quote:
Originally Posted by Mesmurized

What TWRP version? -1 and -2 have known issues.

3.0.2-0

---------- Post added at 04:11 PM ---------- Previous post was at 04:09 PM ----------

Quote:
Originally Posted by Pkt_Lnt

What phone and ROM? One of those is unsupported by SuperSU. That is usually a non standard method of compression that causes the ramdisk patch to fail.

Stock Tmobile LG G3 with Marshmallow 6.0 (30d)
Thread Closed Subscribe to Thread

Tags
root, super user functions
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes