MY QUESTIONS TO CHAINFIRE.... Im losing root - Samsung Galaxy S7 Edge Questions and Answers

Im using S7 Edge exynos version
Im using cf auto root method to root my device.. Root has been installed successfully... But after two weeks i am losing root.. I've almost reflashed my rom 7 times.. I thought Something is wrong in my side.... But its not... Just to check whether i'm losing root because of other app ..
I haven't installed any app on device.. I enabled and disabled su.. Nothing happens.. I disabled and left the app. When i enter ed the app a pop up message opened asking like su binary needs to be updated... If i click continue... Binary updated failed....
There is no su binary installed and su can't installed..
I also purchased pro version to support development
Why is this happening ?
Will you ever work on this fix ?

If u install the Security Patch from MM 6.01?
Gesendet von meinem SM-G935F mit Tapatalk

No i enabled and disabled su inside the app.. Functions were working... Just to check SU.. I disabled it and left the app... And i opened adaway it said root required.. So i went to su app to enable it.. When i opened the app message prompted to update su binaries.. I clicked continue...i lost root..
There is no su binaries installed and su cant install it........

http://forum.xda-developers.com/showthread.php?t=3378618
Gesendet von meinem SM-G935F mit Tapatalk

Related

Lollipop 🍭 Survival Mode alternative Solution!

We always used to update via OTA and maintain root access with SuperSU Survival Mode in previous Android versions.
But now in Lollipop, the Survival Mode option is missing and we can't update via OTA with SU installed because the OTA verification process scans the entire system partition rather than every single item in it, even the presence of an su app in system will cause it to fail. Which it didn't before, as long as you had stock kernel and recovery.
But today I found out a simple method to update via OTA even when SuperSU is installed and maintain root access
Instructions :
1- Remove Custome Recovery via XZRecovery app (IF EXISTED)
2- Enter SuperSU and uncheck the enable superuser option
3- Update via OTA
4- Enter SuperSU and check enable superuser
5- Enter XZRecovery app and install Recovery (OPTIONAL)
It should works flawless
XZRecovery 4.1 link :
https://xq55.box.com/s/k2l1y4goo4gfznilmlh4xs3bwhr4gxq6
#Thanks to my mentor Waleed Qsouda
If I helped, leave a thanks! ?
Doesn't work for me. Can't verify
Sent from my D6503 using Tapatalk
Maybe you have installed something else on system/app or system/bin-xbin.
I'm not try yet this method but I think that should work
Sent from my D6503 using XDA Free mobile app
diyabolic said:
Doesn't work for me. Can't verify
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
same for me. I installed a fresh version of 5.0.2 without anything else, but I also get the message unable to verify
Seems like this method does not work?
Hi, I'd like to install this mod, but I'm curious if this would affect the DRM of my Z2 which I've restored following androplus kernel's guide.
Thanks in advance
My phone was rooted by kingroot
Does this way work?
Sent from my D6503 using Tapatalk
Anyone Tried this method? And if it worked please let us know
Closed at OP's request

Lost root after install CM12.1 Temasek

Hi Guys
I just installed the CM12.1 Temasek, but when I check if my phone has root with the root checker leaves me no. Reviewing Internet tells me that in the options menu of programmer should I look for root access but that option dont appears to me, that you should do? or I can fix thi? i realize the update of SuperSU from TWRP and still does not work
Matthew6501 said:
Hi Guys
I just installed the CM12.1 Temasek, but when I check if my phone has root with the root checker leaves me no. Reviewing Internet tells me that in the options menu of programmer should I look for root access but that option dont appears to me, that you should do? or I can fix thi? i realize the update of SuperSU from TWRP and still does not work
Click to expand...
Click to collapse
Come on seriously. You flash a rom without checking the first post or at least read install instructions.
Warning: spoon feeding incoming:
To gain root access flash supersu file in recovery. Even linked to that file. Twrp doesn't magically root your device without having a file to flash. It's just a false reminder when it sees you have no root access.
Temasek removed the supersu from the rom as you have to do it yourself when you clean install. Get supersu survival after first install so you don't lose it on dirty flashes. Please don't ask how to do that. Just go to supersu settings and look.
Thank you
Hi Kenny
I do All The steps like says in The instructions but doesnt work, i flash the supersu in TWRP but stills doesnt work, that why asking
Enviado desde mi SM-N900W8 mediante Tapatalk
Matthew6501 said:
Hi Kenny
I do All The steps like says in The instructions but doesnt work, i flash the supersu in TWRP but stills doesnt work, that why asking
Enviado desde mi SM-N900W8 mediante Tapatalk
Click to expand...
Click to collapse
Err.... Which SuperSU?
emuandco said:
Err.... Which SuperSU?
Click to expand...
Click to collapse
Chainfire update 2.46
Enviado desde mi SM-N900W8 mediante Tapatalk
What did you update? In other words, what were you on before this?
I always use this one http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
Hey,
I too got my root access removed when installed CM ROM but the best way I did to recover my root is using ODIN and CF-AUTORoot files available on internet .
Just go and flash that .tar file and you'll get back your root access
IMO Odin should always be the last step. Flash SuperSU 2.52 from TWRP 2.8.7.0. It will fix whatever causes root to fail automatically
Matthew6501 said:
Hi Kenny
I do All The steps like says in The instructions but doesnt work, i flash the supersu in TWRP but stills doesnt work, that why asking
Enviado desde mi SM-N900W8 mediante Tapatalk
Click to expand...
Click to collapse
You are probably using older supersu and Twrp files, use the latest ones.
EDIT: Just follow what emuandco said in his last post, should solve the problem right away.

Cm14/LinOs & superSu

So I possibly did something stupid?
Flashed supersu over cm14-111417. How I've lost root. Can't seem to get it back. Super su crashes when I open it, and the root option under developer options gives me two options: disable and ADB only. I'd rather avoid a factory reset if I can help it. Thoughts?
Sent from my Nexus 6P using Tapatalk
Droid_JD said:
So I possibly did something stupid?
Flashed supersu over cm14-111417. How I've lost root. Can't seem to get it back. Super su crashes when I open it, and the root option under developer options gives me two options: disable and ADB only. I'd rather avoid a factory reset if I can help it. Thoughts?
Click to expand...
Click to collapse
Which version of SuperSU did you flash? Did you disable root in CM since you decided to use SuperSu?
Latest su, sr3.
Initially I did not disabled cm root. Things stated being word though, I tried to remove su, root stopped working, I lost root-app access. Though of I disabled cm root, and flashed su again it would fix itself... Nope!
Sent from my Nexus 7 using Tapatalk

Xposed and activated modules

This is the current situation:
Unlocked bootloader in B05 and updated to B08. Everyting fine so far. Playing with GravityBox and adjusted quicksettings settings. After reboot phone wasn't to handle anymore. Screen went on and off and other things. Wiped the device and installed xposed framework again - gravitybox as well and activated it - reboot - stuck on axon 7 boot screen. Tried it several times, but no module can be activated anymore. Installed B09 / B06 all the same. It is now only working in B03.
Hope anyone can help or offer some solutions. Thanks in advance ? ?
Marcus
Hey Marcus, I assume you have TWRP installed. So go to terminal in TWRP type
Reboot disemmcwp
Then hit enter after phone reboots install Xposed framework again and you should be good to go
nujackk said:
Hey Marcus, I assume you have TWRP installed. So go to terminal in TWRP type
Reboot disemmcwp
Then hit enter after phone reboots install Xposed framework again and you should be good to go
Click to expand...
Click to collapse
Okay, will try.
Unfortunately this was not the solution ? But thanks anyway ?
marcus.linkenbach said:
Unfortunately this was not the solution But thanks anyway
Click to expand...
Click to collapse
Have you installed the no-verity patch? otherwise you won't be able to boot a modified system partition.
It boots, but after activating any module with exposed installer it stucks.
What is the no-verity patch? Never heard so far.
Gesendet von meinem ZTE A2017G mit Tapatalk
marcus.linkenbach said:
It boots, but after activating any module with exposed installer it stucks.
What is the no-verity patch? Never heard so far.
Gesendet von meinem ZTE A2017G mit Tapatalk
Click to expand...
Click to collapse
By default the Axon 7 checks for modifications before booting. If anything's modified, you pretty much end up in a bootloop. The no-verity patch lets you work around this feature and prevents the bootloops.
OK. With B03 don't have issues.
Can someone please tell me where to find this patch?
Gesendet von meinem ZTE A2017G mit Tapatalk
I had the same situation.
what i do is go to twrp file manager and delete gravitybox folder in data/data.
take carefully what options you check in gravitybox, specially in lockscreen settings.
additionaly, it seems xposed causes some random reboots on my phone.
But it is not only gravitybox. It doesn't matter what kind of module I install. And don't forget that everything was working before I played with gravitybox. So I have to live without it. ??
Gesendet von meinem ZTE A2017G mit Tapatalk
That's right I forgot about that. Never could figure out what setting it was. Ended up doing a fresh install and only using couple status bar tweaks pretty much don't touch gravity box anymore.
But you are doing better then me as I could never fully boot since you are able to boot go to apps and delete the data for gravity box. Reboot see what happens
If anyone cares, here's my solution. On all my Phones I had xposed version 86 installed. Now just upgraded to 87 e voila it runs smoothly. ?
Gesendet von meinem ZTE A2017G mit Tapatalk

Lost root after iOS emojii install, SuperSU says 'Binary Occupied'. Please help!

I followed this guide https://forum.xda-developers.com/axon-7/how-to/guide-zte-axon-7-cm13-los14-1-eliminate-t3548598 to install Viper4Arise on LineageOS, had it working, then installed the iOS emojii pack. After reboot from installing emojii pack, I lost root, SuperSU says 'Binary Occupied'. When I follow SuperSU's guide on how to fix it it still says 'Binary Occupied'. I'm not quite sure what to do now. I also have Magisk installed so that may be contributing to the problem. I am very new to all of this. Can anyone help?
As apart of the Viper4Arise guide I installed root add on and SELinux Switcher if that helps.
Reflash su via TWRP this will fix the issue
Gesendet von iPad mit Tapatalk
klinggalaxy said:
Reflash su via TWRP this will fix the issue
Gesendet von iPad mit Tapatalk
Click to expand...
Click to collapse
I should have been more specific. I did that multiple times to no avail. This is what I meant when I said "When I follow SuperSU's guide on how to fix it it still says 'Binary Occupied'." That's exactly what they said to do.
I know SELinuxhide does some sneaky stuff behind the scenes so maybe that's the problem?
When i faced this issue i installed su via playstore to no avail. Second attempt twrp/zip did the job, thats all i can tell. If that doesn't work for you, consider reinstalling your system from scratch w/o magisk and then follow magisk installation routine.
Gesendet von iPad mit Tapatalk

Categories

Resources