Related
Twice I have updated from ICD to JB after getting root on ICS then saving my root with OTA.. however after I get into JB and launch OTA, there is no option to restore root.
Superuser is checked and so is /system supports root protection..
can i get some help? do i have to use SU Elite? :/
Beret67 said:
Twice I have updated from ICD to JB after getting root on ICS then saving my root with OTA.. however after I get into JB and launch OTA, there is no option to restore root.
Superuser is checked and so is /system supports root protection..
can i get some help? do i have to use SU Elite? :/
Click to expand...
Click to collapse
bump
Did you temp unroot before accepting the OTA? I don't think it works unless you do this step.
sbdags said:
Did you temp unroot before accepting the OTA? I don't think it works unless you do this step.
Click to expand...
Click to collapse
I have reverted and upgraded 3 times and never "temp unrooted"
If you have a file explorer look for: /system/usr/we-need-root/su-backup
If that exists and if the perms are correct you can regain root. There are guides (I don't know where) but they walk you through regaining root.
Try the instruction here
http://forum.xda-developers.com/showthread.php?t=1926147
I had OTA RK and it didn't work for me either, for some strange reason I never found out. I installed SuperSU from the Play Store and that worked. It's been a loooooooooooong time since I had stock ROM though, so YMMV.
MartyHulskemper said:
I had OTA RK and it didn't work for me either, for some strange reason I never found out. I installed SuperSU from the Play Store and that worked. It's been a loooooooooooong time since I had stock ROM though, so YMMV.
Click to expand...
Click to collapse
Yeah, several guides suggest that you might have "partial root" and that rmoving/reinstalling supersu restores full root access.
Okay so this is getting a little frustrating now..
I never did untemp before with OTA and so i tried that. I rooted at ICS, saved the root with OTA and then untemp rooted and then upgraded to JB.. however I think i got a partial root because when I look at the OTA app again in JB there was no option to restore root..
so i tried SU E and it saus SU binary not found, i had only checked OTA survival though but there was two apps under the allow list: Root Checker Basic and Superuser. After unckecking ota survival i couldnt recheck them though. So here i am stuck on JB without root again. I have not tried bluewr post yet which i am about to. Also i hope flash still works in jb
Beret67 said:
Okay so this is getting a little frustrating now..
I never did untemp before with OTA and so i tried that. I rooted at ICS, saved the root with OTA and then untemp rooted and then upgraded to JB.. however I think i got a partial root because when I look at the OTA app again in JB there was no option to restore root..
so i tried SU E and it saus SU binary not found, i had only checked OTA survival though but there was two apps under the allow list: Root Checker Basic and Superuser. After unckecking ota survival i couldnt recheck them though. So here i am stuck on JB without root again. I have not tried bluewr post yet which i am about to. Also i hope flash still works in jb
Click to expand...
Click to collapse
Flash will work, you just need to install it either in ICS, or after as a third party app, as Google play doesn't allow download, only update now.
And try either SuperSU or Super User only, not both, and before temp unroot, be sure to update the binary on which ever one you use.
bluewr said:
Flash will work, you just need to install it either in ICS, or after as a third party app, as Google play doesn't allow download, only update now.
And try either SuperSU or Super User only, not both, and before temp unroot, be sure to update the binary on which ever one you use.
Click to expand...
Click to collapse
Update binary? How exactly do i do that? thanks for advice
Beret67 said:
Update binary? How exactly do i do that? thanks for advice
Click to expand...
Click to collapse
The trick is once you rooted, you need to launch superuser, and it will auto update your binary, then install OTA root keeper., then save root, then temp unroot, then upgrade, then use ota to restore root.
http://forum.xda-developers.com/showthread.php?t=1241517&nocache=1
Original devs op instructs to temp unroot.
Oops... double post.
Where'd the delete option go?
I installed the OTA for 4.1.2 and have not rooted my T-mobile T999 at all. I've watched videos that said it was for this firmware and model, but when I go into recovery mode and try to install the zip file, I get a message saying "E: Signature Verification Failed." SuperSU is on my phone, but when I try to launch it, it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!"
I've never rooted a phone before, but the videos I watched seemed really easy, but it's not working for me.
Can somebody post how to do it with the most updated G3rootsprint.zip file. Maybe I'm using one that's too old, or maybe since the update is only days old, it's not possible with the processes that are online already.
gstoliby said:
I installed the OTA for 4.1.2 and have not rooted my T-mobile T999 at all. I've watched videos that said it was for this firmware and model, but when I go into recovery mode and try to install the zip file, I get a message saying "E: Signature Verification Failed." SuperSU is on my phone, but when I try to launch it, it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!"
I've never rooted a phone before, but the videos I watched seemed really easy, but it's not working for me.
Can somebody post how to do it with the most updated G3rootsprint.zip file. Maybe I'm using one that's too old, or maybe since the update is only days old, it's not possible with the processes that are online already.
Click to expand...
Click to collapse
try disabling signature verification in your recovery
chromium96 said:
try disabling signature verification in your recovery
Click to expand...
Click to collapse
I can't even figure out how to do that!
gstoliby said:
I can't even figure out how to do that!
Click to expand...
Click to collapse
Which recovery are you using? In clockwordmod the option is located in the advacned menu
chromium96 said:
Which recovery are you using? In clockwordmod the option is located in the advacned menu
Click to expand...
Click to collapse
I'm attempting to root with clockworkmod, but since I can't get that far, it's the android recovery.
gstoliby said:
I'm attempting to root with clockworkmod, but since I can't get that far, it's the android recovery.
Click to expand...
Click to collapse
Use this guide to root the t999v. I used it a couple months ago and it works fine, and as a bonus it wont trip your flash counter.
chromium96 said:
Use this guide to root the t999v. I used it a couple months ago and it works fine, and as a bonus it wont trip your flash counter.
Click to expand...
Click to collapse
I'll have to give it a try when I get to my personal computer.
I tried to root my sch-i535 4.3 I had MTP click and usb debugging click...and it failed in odin...I have an image and link of what I was using to root the phone below and this is what the phone gave me in download mode...how can I fix this problem?
product name: sch-i535
custom binary download: no
current binary Samsung: official
QUALCOMM secureboot: enable
warranty bit:0
bootloader rp swrev: 1
secure check fail: recovery
eddieleed said:
I tried to root my sch-i535 4.3 I had MTP click and usb debugging click...and it failed in odin...I have an image and link of what I was using to root the phone below and this is what the phone gave me in download mode...how can I fix this problem?
product name: sch-i535
custom binary download: no
current binary Samsung: official
QUALCOMM secureboot: enable
warranty bit:0
bootloader rp swrev: 1
secure check fail: recovery
Click to expand...
Click to collapse
If you spend the time looking through the countless 4.3 ota threads, you would see that you can't root from 4.3 that way... safestrap is it and trying to Odin root will probably brick your device...
Check twice, flash once...
Sent from my SCH-I535 using xda premium
Do you have info on it???
Do you have info on how to do it with Safestrap?
Macrodroid said:
If you spend the time looking through the countless 4.3 ota threads, you would see that you can't root from 4.3 that way... safestrap is it and trying to Odin root will probably brick your device...
Check twice, flash once...
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Dadiekane said:
Do you have info on how to do it with Safestrap?
Click to expand...
Click to collapse
It's actually saferoot not safestrap and you can find info about it and a link for it in the OP of this thread:
http://forum.xda-developers.com/showthread.php?t=2575661
landshark68 said:
It's actually saferoot not safestrap and you can find info about it and a link for it in the OP of this thread:
http://forum.xda-developers.com/showthread.php?t=2575661
Click to expand...
Click to collapse
I'll look into this as well...I'll keep faith that thier is a root out there or will b out there.
works
landshark68 said:
It's actually saferoot not safestrap and you can find info about it and a link for it in the OP of this thread:
http://forum.xda-developers.com/showthread.php?t=2575661
Click to expand...
Click to collapse
thanks for the link..it worked...I am rooted on my Verizon 4.3 galaxy s3...can I install recovery (cwm or twrp)?
eddieleed said:
thanks for the link..it worked...I am rooted on my Verizon 4.3 galaxy s3...can I install recovery (cwm or twrp)?
Click to expand...
Click to collapse
No, you can only root.
landshark68 said:
No, you can only root.
Click to expand...
Click to collapse
That's what I have been reading. Ill be waiting for a custom recovery...thank you for your and comments. :good:
can any one help I safe rooted my sch-i535 verizon jellybean 4.3 ..added titanium back and pressed something wrong in titanium back up that soft brick my phone so now all it says is "unauthorized software take to you local verizon dealer" i've tried everything Ive read on this site and then some,still boots to yellow screen of death.this is not the first phone i've rooted been playing with modifying phones since the V3M came out.yes it was updated by OTA 4.3..everything in Odin fails, the knot counter is tripped but i don't buy my phones from Verizon anyway, tried hard reset still nothing.I can get into down load mode (power,vol down/home)and reset mode(power, vol up/home)Kies says unauthorized software .anything would be helpful.......deadcat
Saferoot working in s3 verizon
Sent from my SCH-I535 using xda app-developers app
deadcatsrule said:
can any one help I safe rooted my sch-i535 verizon jellybean 4.3 ..added titanium back and pressed something wrong in titanium back up that soft brick my phone so now all it says is "unauthorized software take to you local verizon dealer" i've tried everything Ive read on this site and then some,still boots to yellow screen of death.this is not the first phone i've rooted been playing with modifying phones since the V3M came out.yes it was updated by OTA 4.3..everything in Odin fails, the knot counter is tripped but i don't buy my phones from Verizon anyway, tried hard reset still nothing.I can get into down load mode (power,vol down/home)and reset mode(power, vol up/home)Kies says unauthorized software .anything would be helpful.......deadcat
Click to expand...
Click to collapse
As long as you can get to download mode, you can flash the stock 4.3 image back. When you start TB, pay attention. Do not restore ANY system apps and do not allow it to change the phone ID.
Sent from my SCH-I535 using xda app-developers app
5ft24 said:
As long as you can get to download mode, you can flash the stock 4.3 image back. When you start TB, pay attention. Do not restore ANY system apps and do not allow it to change the phone ID.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I backd up my phone with TB and have it saved on my laptop but dont know what file to try to flash and I can not find a good stock 4.3 image that i can get to flash back to the phone.from what im reading the boot loader is locked keeping me from flashing anything .I've picked up another S3 to use for now so I can try to undo what ever i did wrong
deadcatsrule said:
I backd up my phone with TB and have it saved on my laptop but dont know what file to try to flash and I can not find a good stock 4.3 image that i can get to flash back to the phone.from what im reading the boot loader is locked keeping me from flashing anything .I've picked up another S3 to use for now so I can try to undo what ever i did wrong
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=2589314
post one is to download the official firmware 4.3
post 2 is how to fix and if you follow the link after you redirected there're more info how to recover your phone depended on how bad it is, but if you still get into download mode you should be ok.
buhohitr said:
Try this http://forum.xda-developers.com/showthread.php?t=2589314
post one is to download the official firmware 4.3
post 2 is how to fix and if you follow the link after you redirected there're more info how to recover your phone depended on how bad it is, but if you still get into download mode you should be ok.
Click to expand...
Click to collapse
UPDATE!! the link and info you posted for me fixed my phone first try..THANKS
Help, using Saferoot to root OTA 4.3, but Supersu binary update failed
Followed all the steps of Saferoot, everything else seems ok except SuperSU failed to update su binary.
The weird thing is that steps after SuperSU update (disabling KNOX and installing busybox) seem ok, and while SuperSU's popup window asking for SU binary needs to be updated, I can see in the grayed out back showing ADB Shell as the only apps gained root access.
More detail on SuperSU binary update, I chose update su normal way (instead CWM/TWRP) and next popup will report "Installation failed. Please reboot and try again." I tried many reboots and results were all the same.
From Terminal emulator, su -v command shows su is at version 3.1.1 (that's the latest already). If I cancel binary update, SuperSU app will exit too. I tried to install superuser app and use it to update su binary as someone suggested, it will fail in gaining root access.
Any way to overcome this issue and gain root on this OTA 4.3? Please help.
Phone Info:
Device Name: SCH-I535
Baseband Version: I535VRUCML1
Build Number: JSS15J.I535VRUCML1
Hardware Version: I535.10
nook2hd said:
Followed all the steps of Saferoot, everything else seems ok except SuperSU failed to update su binary.
The weird thing is that steps after SuperSU update (disabling KNOX and installing busybox) seem ok, and while SuperSU's popup window asking for SU binary needs to be updated, I can see in the grayed out back showing ADB Shell as the only apps gained root access.
More detail on SuperSU binary update, I chose update su normal way (instead CWM/TWRP) and next popup will report "Installation failed. Please reboot and try again." I tried many reboots and results were all the same.
From Terminal emulator, su -v command shows su is at version 3.1.1 (that's the latest already). If I cancel binary update, SuperSU app will exit too. I tried to install superuser app and use it to update su binary as someone suggested, it will fail in gaining root access.
Any way to overcome this issue and gain root on this OTA 4.3? Please help.
Phone Info:
Device Name: SCH-I535
Baseband Version: I535VRUCML1
Build Number: JSS15J.I535VRUCML1
Hardware Version: I535.10
Click to expand...
Click to collapse
In super su options do the clean up for market reinstall. Then download supersu from the market. It may not be worded like that but you will see what I mean. And make sure you uninstall superuser if you haven't already.
Still the same
ThePagel said:
In super su options do the clean up for market reinstall. Then download supersu from the market. It may not be worded like that but you will see what I mean. And make sure you uninstall superuser if you haven't already.
Click to expand...
Click to collapse
I cannot get into SuperSU options (or settings as in the snapshots). Neither Cancel nor Continue to the binary update popup will not stop me into SuperSU app.
Unistalled superuser, force stopped SuperSU and cleared data, then reinstalled SuperSU from play store. However, when open SuperSU, still asks for su binary update and fail.
Any other ways to get this to work?
nook2hd said:
Unistalled superuser, force stopped SuperSU and cleared data, then reinstalled SuperSU from play store. However, when open SuperSU, still asks for su binary update and fail.
Any other ways to get this to work?
Click to expand...
Click to collapse
Did you do the cleanup option in supersu?
---------- Post added at 11:16 AM ---------- Previous post was at 11:12 AM ----------
Labeled reinstall under supersu settings.
ThePagel said:
Did you do the cleanup option in supersu?
---------- Post added at 11:16 AM ---------- Previous post was at 11:12 AM ----------
Labeled reinstall under supersu settings.
Click to expand...
Click to collapse
I cannot get into SuperSu settings when there are popup windows, and when popup is gone, SuperSU app exits with it somehow. Is there a way to bypass those popups and allow me to click on the settings?
nook2hd said:
I cannot get into SuperSu settings when there are popup windows, and when popup is gone, SuperSU app exits with it somehow. Is there a way to bypass those popups and allow me to click on the settings?
Click to expand...
Click to collapse
I have no clue. If you can't find a solution you could always factory reset and start over.
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
voigts said:
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
Click to expand...
Click to collapse
I'm not sure if this works at this point but Chainfire had a super SU zip especially for 4.3 roms on his website. This may fix your issue
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
voigts said:
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
Click to expand...
Click to collapse
If you have root before 4.3, my experience may be helpful to you: http://forum.xda-developers.com/showpost.php?p=49334077&postcount=21
Though, I didn't have problem with KNOX, my problem was SuperSU fail to update su binary.
voigts said:
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
Click to expand...
Click to collapse
Have you verify that your phone successfully rooted? Check it with root checker from the market.
ShapesBlue said:
I'm not sure if this works at this point but Chainfire had a super SU zip especially for 4.3 roms on his website. This may fix your issue
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Have you got a link? I'm looking but not finding.
nook2hd said:
If you have root before 4.3, my experience may be helpful to you: http://forum.xda-developers.com/showpost.php?p=49334077&postcount=21
Though, I didn't have problem with KNOX, my problem was SuperSU fail to update su binary.
Click to expand...
Click to collapse
I did have my phone rooted prior to the OTA. I've been rooting my phones for years, but have never messed with adb shell. I read your post before posting this question but it is kind of greek to me. I've always used the usual run this, run that, Odin this, CWM that type approaches. My SuperSU binary won't update because it can't disable KNOX.
buhohitr said:
Have you verify that your phone successfully rooted? Check it with root checker from the market.
Click to expand...
Click to collapse
I already used root checker to verify the phone did not root successfully.
voigts said:
Have you got a link? I'm looking but not finding.
Click to expand...
Click to collapse
I have the zip file. I downloaded it awhile ago. It's dated from October.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
---------- Post added at 01:44 PM ---------- Previous post was at 01:32 PM ----------
voigts said:
Have you got a link? I'm looking but not finding.
Click to expand...
Click to collapse
Best bet is his thread here on xda. He has a flashable zip
http://forum.xda-developers.com/showthread.php?t=1538053
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
I've been trying to get this OTA 4.3 rooted with no success. I ran the saferoot install.bat, and after multiple tries, it finally managed to disable KNOX. I cannot however get SuperSU to update the binaries. I've run it a bunch of times. SuperSU managed to turn off Superuser citing a conflict, but simply fails at installation. I downloaded the 1.91 SuperSU update, and have tried multiple times to flash via stock recovery. After verifying update package comes up, it fails to verify update signature, ends, reboots, and doesn't install. I uninstalled SuperSU and tried to flash and it doesn't install.
I have Googled and Googled with no solutions.
I am also finding that this OTA isn't very stable. I am having intermittent weird issues like today my camera just wouldn't work for a while until reboot, and the phone has turned itself off a couple of times.
voigts said:
I've been trying to get this OTA 4.3 rooted with no success. I ran the saferoot install.bat, and after multiple tries, it finally managed to disable KNOX. I cannot however get SuperSU to update the binaries. I've run it a bunch of times. SuperSU managed to turn off Superuser citing a conflict, but simply fails at installation. I downloaded the 1.91 SuperSU update, and have tried multiple times to flash via stock recovery. After verifying update package comes up, it fails to verify update signature, ends, reboots, and doesn't install. I uninstalled SuperSU and tried to flash and it doesn't install.
I have Googled and Googled with no solutions.
I am also finding that this OTA isn't very stable. I am having intermittent weird issues like today my camera just wouldn't work for a while until reboot, and the phone has turned itself off a couple of times.
Click to expand...
Click to collapse
Use saferoot to install SuperSu, then run adb command as:
adb shell
You should see "$" prompt
Then type
/system/xbin/su
You should see "#"
Please verify.
buhohitr said:
Use saferoot to install SuperSu, then run adb command as:
adb shell
You should see "$" prompt
Then type
/system/xbin/su
You should see "#"
Please verify.
Click to expand...
Click to collapse
I uninstalled SuperSU that I installed via Google play. I ran saferoot and let it do its thing and install SuperSU. When I get to the part of updating SuperSU, it fails to install. I ran your commands in adb, and I got the #.
voigts said:
I uninstalled SuperSU that I installed via Google play. I ran saferoot and let it do its thing and install SuperSU. When I get to the part of updating SuperSU, it fails to install. I ran your commands in adb, and I got the #.
Click to expand...
Click to collapse
Once you got the # , then run the following:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
After this open SuperSu app and see if you can update. If updated successfully then reboot your phone.
buhohitr said:
Once you got the # , then run the following:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
After this open SuperSu app and see if you can update. If updated successfully then reboot your phone.
Click to expand...
Click to collapse
Many thanks. It worked! :good: SuperSU updated just fine, and root checker shows root access. What did these commands actually do and what was the problem?
voigts said:
Many thanks. It worked! :good: SuperSU updated just fine, and root checker shows root access. What did these commands actually do and what was the problem?
Click to expand...
Click to collapse
You have Superuser and SuperSu in your phone and the Superuser is the default one which root no longer working. So these commands basically remove the Superuser "su" executable file, which allowed your SuperSu to be updated and became a default root.
buhohitr said:
You have Superuser and SuperSu in your phone and the Superuser is the default one which root no longer working. So these commands basically remove the Superuser "su" executable file, which allowed your SuperSu to be updated and became a default root.
Click to expand...
Click to collapse
Makes sense. I get the concept. Thank you very much for your help. I Googled over and over and couldn't come up with an answer.
Using Saferoot with Knox disable
voigts said:
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
Click to expand...
Click to collapse
I had tried the saferoot and it failed several times, until i installed kies 3 here's how finally was able to root my SCH-R530u Us cellular phone with JB 4.3:
downloaded saferoot & unzipped, then installed kies 3 & run it (make sure your phone is detected ok in kies) after kies opens & your phone is recognized open saferoot and run it. wait for the phone to restart, then go to play store and download supesu and install it or update it, then open supersu & it should ask to install binary. that should do it! Hope this helps:victory:
voigts said:
I've been trying to get this OTA 4.3 rooted with no success. I ran the saferoot install.bat, and after multiple tries, it finally managed to disable KNOX. I cannot however get SuperSU to update the binaries. I've run it a bunch of times. SuperSU managed to turn off Superuser citing a conflict, but simply fails at installation. I downloaded the 1.91 SuperSU update, and have tried multiple times to flash via stock recovery. After verifying update package comes up, it fails to verify update signature, ends, reboots, and doesn't install. I uninstalled SuperSU and tried to flash and it doesn't install.
I have Googled and Googled with no solutions.
I am also finding that this OTA isn't very stable. I am having intermittent weird issues like today my camera just wouldn't work for a while until reboot, and the phone has turned itself off a couple of times.
Click to expand...
Click to collapse
can you please tell me how did you manage to disable knox because i have the same exact problem tnx
LYwaa said:
can you please tell me how did you manage to disable knox because i have the same exact problem tnx
Click to expand...
Click to collapse
I'd try to help but I know hardly anything about Knox. Try sending a PM to the person
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Just updated my Nexus 5 using the OTA thread that went through fine,
I then proceeded to update SuperSU using the following link: http://download.chainfire.eu/supersu which was the update v1.99r3.
Using TWRP I flashed this and root is working for most apps i have tested: titanium, adblock, root explorer. So root is back.
However whenever I load up SuperSU I keep getting the following message: "The SU binary needs to be updated. Continue?"
So of course I have done this and let it use TWRP to flash. Let the phone boot up and upgrade the app as it needed. However on next load up of the app it asks to do the same yet again.
I feel as though I'm forgetting something as it's been a while since I've done this. ( use to live on flashing when i had my SII)
My Nexus is Stock ROM. CF-Auto Rooted. TWRP Recovery. Nothing else is modified.
Help would be appreciated, even though I don't go into supersu all that often anyways.
Cheers all.
What if you upgrade it using the "normal" method?
If I do a normal install i get the following:
Installation failed!
Please reboot and try again.
brichardson1991 said:
If I do a normal install i get the following:
Installation failed!
Please reboot and try again.
Click to expand...
Click to collapse
That message is usually indicative of not having root in the first place. What if you flash it via TWRP then do it normally? Could TWRP be removing it with its "Fix root" option?
What about other recoveries? Do they allow root to stay?
rootSU said:
That message is usually indicative of not having root in the first place. What if you flash it via TWRP then do it normally? Could TWRP be removing it with its "Fix root" option?
What about other recoveries? Do they allow root to stay?
Click to expand...
Click to collapse
How odd like I said my apps are all receiving their root permissions...
What file would we be talking about flashing? The Temp one SuperSU makes to flash when you click install via TWPR?
I don't have any other recoveries on my phone, so I wouldn't know about that last option.
brichardson1991 said:
How odd like I said my apps are all receiving their root permissions...
Click to expand...
Click to collapse
Are they though? SuperSU grants permissions but if the binary is not present, its irrelevant. Can you actually do root things with the root apps that have the permissions?
Have you tried other binary download?
brichardson1991 said:
What file would we be talking about flashing? The Temp one SuperSU makes to flash when you click install via TWPR?
Click to expand...
Click to collapse
In SuperSU, do the TWRP flash install of the binary and reboot, then try the "normal" install immediately after
brichardson1991 said:
I don't have any other recoveries on my phone, so I wouldn't know about that last option.
Click to expand...
Click to collapse
Theres a link in my signature to Philz recovery. In the settings is a root option, so the recovery itself can root without flashing any zips. Maybe try that if downloading an older flashable zip or the above hasnt worked.
rootSU said:
Are they though? SuperSU grants permissions but if the binary is not present, its irrelevant. Can you actually do root things with the root apps that have the permissions?
Click to expand...
Click to collapse
It does seem that way Titanium has backed up an app just now, adblock has updated and Nova is hiding the time on the first screen.
rootSU said:
Have you tried other binary download?
Click to expand...
Click to collapse
No, I shall give a older one a try.. Tried 1.97 as well and to no luck.....
rootSU said:
In SuperSU, do the TWRP flash install of the binary and reboot, then try the "normal" install immediately after
Click to expand...
Click to collapse
This failed to do anything just got the install failed again.
rootSU said:
Theres a link in my signature to Philz recovery. In the settings is a root option, so the recovery itself can root without flashing any zips. Maybe try that if downloading an older flashable zip or the above hasnt worked.
Click to expand...
Click to collapse
I assume this would override TWRP recovery?
brichardson1991 said:
I assume this would override TWRP recovery?
Click to expand...
Click to collapse
Yes it would. You can always flash back to twrp afterwards
rootSU said:
Yes it would. You can always flash back to twrp afterwards
Click to expand...
Click to collapse
Well considering that worked and I now can get into SuperSU I think I will stick with Philz. Even if I paid for the TWRP app
brichardson1991 said:
Well considering that worked and I now can get into SuperSU I think I will stick with Philz. Even if I paid for the TWRP app
Click to expand...
Click to collapse
Good news. The latest version of Philz, s it is CWM based - uses the latest Cyanogen sources to build. I update the CM sources everytime I build Philz so hopefully there should be fewer issues when new stuff comes out.