[Q] SU Binary Updater to 3.1 fails when getting root - Samsung Galaxy Nexus

Hey there,
when I open superuser and swipe to the Info page I see that my su binary is outdate. So I select update, tells me
new version = 3.1
installed version = 3.0.3.2
So i press the update button
[..]
new binary will be downloaded ... okay!
getting root-access... failed! (pop up comes and tells that superuser root access has been granted)
strange thing is all root access is working as expected (adfree, es file explorer, etc), uninstalled superuser, reinstalled it, tried again, no luck, booted a couple of times, no luck
Sure this update isnt really necessary but still I would like to update. On my GTab 10.1 it worked without a problem.
Searched xda forums for this bug and asked google, no luck.
Any hint for me?
Thanks

I read in one of the other forums that this is a problem with the 4.0.4 and above (jelly bean) versions. There is actually an updated version of the SU.zip in the androidcentral forum:
http://forums.androidcentral.com/ge...ry-update-gaining-root-access-fail-error.html
it is the fourth post, and the link it gives you is actually here in xda, but I´m at work and cannot log in android central. If you dont already have android central account, register and download it.
Reflash the SU.zip though ADB (as you did the first time you rooted) and the problem should be fixed.

I think you mean this posting:
There is currently a problem with the su.zip used in GSM GNex with 4.0.4, in order to make Superuser work properly, just instal [Only registered users can view links. ] (ClockworkMod flashable) and Viola! Problem fixed.
Click to expand...
Click to collapse
I found this su.zip on an other android forum but all are talking about flashing via CWM. Well I am on stock rom without CWM and I am not planing to install it just now before jelly bean comes out. Then I wont receive the OTA update etc.
Guess I will stay then with my current version (root access is indeed working) and wait for jelly bean and then will have a look again how to root when it has been discovered.
I thank you very much for your information, I am also sitting at work

Related

I'm rooted, but not...?

So, a few weeks ago I flashed freeza's Sprint Touchwiz Jelly Bean 4.1.1 (L710VPBLJ7) Odex from ICS. It's been running beautifully without issue. I was able to install this ROM after installing ClockworkMod without issue since I was running a stock, but rooted version of ICS.
It wasn't until today I noticed that I can't perform a lot of tasks that require root
Apps that run:
- WiFi Tether: Launches without error, but I no longer see the SSID that was visible when I was still on ICS. Can't see it on laptops, tablets, etc.
- Root Explorer launches: I tap Mount R/W and nothing happens. No errors about not being rooted.
- File Explorer: I tap Root Explorer and get a message saying "Root explorer cannot be enabled. Make sure your device is rooted." (see screen shot)
- Super User: It shows lots of logs giving root access to various apps. I tried updating the binaries, but it fails (see screen shot).
I've attached a bunch of screen shots to see if it helps you guys figure anything out.
I'd appreciate your feedback.
Thanks!
Try installing SuperSU from the Playstore and uninstalling the regular SU app.
Sent from my SPH-L710 using xda app-developers app
INHUMANITY said:
So, a few weeks ago I flashed freeza's Sprint Touchwiz Jelly Bean 4.1.1 (L710VPBLJ7) Odex from ICS. It's been running beautifully without issue. I was able to install this ROM after installing ClockworkMod without issue since I was running a stock, but rooted version of ICS.
It wasn't until today I noticed that I can't perform a lot of tasks that require root
Apps that run:
- WiFi Tether: Launches without error, but I no longer see the SSID that was visible when I was still on ICS. Can't see it on laptops, tablets, etc.
Click to expand...
Click to collapse
Are you using the TrevE modified version of WiFi Tether? The other one will not work on this rom (while it did on ICS).
mikeregister said:
Try installing SuperSU from the Playstore and uninstalling the regular SU app.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
No bueno. I tried updating the binaries in SuperSU and it failed.
I can't uninstall the regular super user app. I originally rooted my phone using TeamEpic's method, so I believe it it came with that.
If all else fails do a clean install
Sent from my SPH-L710 using xda app-developers app
m20120 said:
Are you using the TrevE modified version of WiFi Tether? The other one will not work on this rom (while it did on ICS).
Click to expand...
Click to collapse
I installed the version directly from the dev's website: http://code.google.com/p/android-wifi-tether/. I'll try one of the experimental versions.
Still, root access from a lot of other programs are not possible.
Is there a way to re-root this rom?
Thanks!
EDIT: I installed the latest beta listed on the link and installed the latest experimental version. That one turned out to be the TrevE modified version that you mentioned. This time, the beacon was visible to my laptop and tablet, but they could not connect to the phone.
I uninstalled and went back to 3.1 beta 14. I set the profile to the SIII and launched it. It failed the first time. Close the app, re-launched, and the tethering started without error. Again, back to not seeing the beacon.
This one is a definite head scratcher.
mikeregister: Obviously wiping and starting over would probably work, but that's not how troubleshooting works.
Thought I'd share an update...
I came across the below thread. I installed the version mentioned and WiFi tethering once again works.
http://forum.xda-developers.com/showthread.php?p=34038908
Now, onto the matter of re-rooting to see if that fixes things.
Let me know if you guys have any ideas.
I ran across the SU failed to update a couple times on my photon, there is an SU update fixer in the playstore that you can run and it fixes that issue, if you're still running into it after you attempt to re-root.
xTMFxOffshore said:
I ran across the SU failed to update a couple times on my photon, there is an SU update fixer in the playstore that you can run and it fixes that issue, if you're still running into it after you attempt to re-root.
Click to expand...
Click to collapse
I tried the SU fixer.
It said no problems were found. I checked the "force" button and when I attempt the fix, the app crashes. I can't get a screenshot while it's attempting to fix to post the results.
Find the CMteam root package, and flash that in cwm/twrp. This gives you superuser, but fixes root, then you can install supersu if you want.
Follow me on...
Youtube http://bit.ly/To93d6
Google+ http://bit.ly/RqyYPa
Facebook http://on.fb.me/RFIADb
Twitter @Jason_Feriani http://bit.ly/Qa3Yyu
ecooce said:
Find the CMteam root package, and flash that in cwm/twrp. This gives you superuser, but fixes root, then you can install supersu if you want.
Follow me on...
Youtube http://bit.ly/To93d6
Google+ http://bit.ly/RqyYPa
Facebook http://on.fb.me/RFIADb
Twitter @Jason_Feriani http://bit.ly/Qa3Yyu
Click to expand...
Click to collapse
I'm searching the interwebs, but Google is filled with tons of links that are irrelevant. I can't find the specific root package.
Would you happen to have a link handy?
Much appreciated!
INHUMANITY said:
I'm searching the interwebs, but Google is filled with tons of links that are irrelevant. I can't find the specific root package.
Would you happen to have a link handy?
Much appreciated!
Click to expand...
Click to collapse
I would start here, this zip will clean out any binary remnants and all that, you will then need to flash TWRP if you want that for recovery.
epiccm.org/2012/06/team-epics-root-from-recovery.html
TeamBringIt said:
epiccm.org/2012/06/team-epics-root-from-recovery.html
Click to expand...
Click to collapse
That's the zip I used to originally root my phone when it was still running ICS.
I re-ran it yesterday to see if it would fix anything, but it didn't. After the phone re-booted, the OS began the Optimizing app xx of xx process, but it didn't fix anything. WiFi tether runs without errors, but Root Explorer and File Manager with root say my phone is not rooted. I confirmed it's rooted via Root Checker again.
Just to make sure, are you referring to TeamEpic-Root-from-Recovery-v5.zip? That's what I ran on ICS and re-ran yesterday.
What's your take on flashing TeamEpic-RemoveRoot-from-Recovery-signed.zip and then re-rooting with the link you referenced?
Im about to search for the file im talking about, if you have twrp, you will still have twrp after...
Well ths file link posted for epicteam root v5 was the file, should work 100%.
Follow me on...
Youtube http://bit.ly/To93d6
Google+ http://bit.ly/RqyYPa
Facebook http://on.fb.me/RFIADb
Twitter @Jason_Feriani http://bit.ly/Qa3Yyu

[Q] SuperSU not updating, etc

OK, I know this has been asked and asked again, but I have been reading and digging and googling for several days now, and cannot find a solution.
I've got a JB S3 At&t, and wanted to root it, so after reading for a few weeks, I got the "Samsung_Galaxy_S3_ToolKit_v7.0", donated, and got 7.2 (newest version). I flashed with the toolkit to get an unsecured boot image, with SuperSU 1.04, busybox, and TWRP .
Root happened fine. The phone booted, and when I went to open SuperSU (the icon was in my apps), it asked to update the binaries. I said yes, it failed, and the app opened anyway to allow me to access the options. Triangle away worked fine.
The update binaries thing was bugging me, so I updated to SuperSU 1.10 via google store, and the same thing happened, but now I could not access the program after the binary update failed. It still works (triangle away asks and gets permission) but I could not access the program any longer. It just closes after it informs me that updating the binaries failed.
I have tried installing the program as an app, pushing an APK, and installing a zip from recovery. No matter what I do, it ends up the same.
I have also re-flashed the boot several times, and tried a different method using Odin directly and CF-Root. (seems to be the only way to uninstall it) I have tried numerous combinations, but to no avail. I feel like I have done everything I know how to do short of an unroot to stock and try again.
Any helpful suggestions are welcome.
I'd like to be able to use the program, but this is turning into an OCD nightmare. I'd post this in a development forum, but do not have enough posts yet.
Install "SuperUser" from the market. Manually delete SuperSU from /system/app. Reboot. Reinstall SuperSU from play store and binaries should install fine...
illmatic24 said:
Install "SuperUser" from the market. Manually delete SuperSU from /system/app. Reboot. Reinstall SuperSU from play store and binaries should install fine...
Click to expand...
Click to collapse
Thanks. I ended up doing it the hard way. (I swear I had auto email notification enabled here, or I would have seen your post and tried it)
Anyway, I cleared caches/userdata/wipe cache partition first, then flashed a stock unrooted 4.1.1 rom from here,
Then I used CF-autoroot, and low and behold, SU was showing up as an app. (it was not previously when I used CF-AR)
I let it update itself and bam, it works! Installed adbd insecure, and it works too. (it was not showing up as an app when I did it before either)
Next I added TWRP 2.4.3.0. and everything still works!
Either the stock AT&T rom on this unit had something interfereing with root, or the root image I used in the toolkit has an issue. I'm leaning towards a toolkit issue since when I used it and it installed TWRP 2.4.1.0, I could not get into recovery, just a black screen.
I lieu of this, I'm limiting my use of the toolkit.
Curiously, the toolkit also allows a sideload via TWRP/CWM, but does not provide a driver. Windows 7 cannot recognize the phone in recovery mode with a custom recovery installed, although it does when a stock recovery is. I have yet to find a driver.

Trouble Re Rooting Device

Hello,
So as the forum discussion I have the AT&T S3 I747 - Initially I rooted the phone to be able to use it at as a wireless hotspot and everything worked great the method i used was galaxys3root .com (I cant post the actual link <10 posts)
What I thought was a notification OTA triggered me to opening superuser and doing an uninstall/permanent unroot to ensure i didn't brick my phone, well I was wrong about the notification feeling like an idiot i decided to go ahead a reroot the phone again.
I followed the same procedure as linked above this time with problems, I have no Superuser Icon in apps tray, under applications manager it appears but only gives me the option to "Uninstall Updates" and that all
Things I have tried
- installing both versions onto the phone Clockwork mod simply just sits there under "Installing Superuser" Chain version installs but appears to do nothing.
- Used odin to reflash the stock rom then tried the re root process again
- reinstalled the wifi app to see if working but no longer is
I am not looking for a custom rom I like the default one I have I just want the Superuser app to show up again, anyone know what I could do to fix this?
Thanks for all your help
Flash the rooted stock version with Odin
mrhaley30705 said:
Flash the rooted stock version with Odin
Click to expand...
Click to collapse
Thanks for your reply I seem to have got it solved. I downloaded a File Explorer Went into system/Apps found the SuperUser APK opened it, let it install updates and what not after done the app showed back in my apps drawer, installed my wifi mod and superuser granted permissions so everything is good
Questions and help issues go in Q&A and Help section
Thread moved
FNM

[Q] Tried rooting using Towelroot and chainfire but no joy

Hi Guys,
I am having some issues trying to root my Samsung Galaxy S3. I am currently running the stock Kitkat version of AT&T on my S3(SGH-I747) and trying to root it to be able to install CWM and a custom rom.
I have tried chainfire and towelroot methods.
I used the following tutorial of using ODIN and chainfire image for samsung SGH-I747:youtube.com/watch?v=LwsvPO8jVGE
I was able to get all steps to work and get everything same as the video above except when I install "Root Checker" from android play store it gave me message that "Root method is not properly configured" even after odin showed "Success" after rebooting and applying the patch
I then used the towelroot method by going to the towelroot.eu website on my phone and installing the apk. the towelroot app gave me the message that "I have root and do not need to reboot my device" but Root checker still says that my root is not configured.
I then reset my phone by pressing volume up+power and home button and clearing "Cache" and wiping data" and trying the above methods again but still unable to get the phone to root.
I am completely stumped as to what I am doing wrong. And would really appreciate some help from the pros.I have attached a snapshot of my device info and thanks for the great work and guidance.
Matt
PS. I already made sure that my phone is in the "Developer Mode" and "USB debugging" is enabled
tried another method
Also tried using the casual method but that also failed with the error "Unsupported device" here is the url for the log file:http://pastebin.com/vZRvYH3g
I followed the follwowing thread:
http://forum.xda-developers.com/showthread.php?t=2189536
amti366 said:
Hi Guys,
I am having some issues trying to root my Samsung Galaxy S3. I am currently running the stock Kitkat version of AT&T on my S3(SGH-I747) and trying to root it to be able to install CWM and a custom rom.
I have tried chainfire and towelroot methods.
I used the following tutorial of using ODIN and chainfire image for samsung SGH-I747:youtube.com/watch?v=LwsvPO8jVGE
I was able to get all steps to work and get everything same as the video above except when I install "Root Checker" from android play store it gave me message that "Root method is not properly configured" even after odin showed "Success" after rebooting and applying the patch
I then used the towelroot method by going to the towelroot.eu website on my phone and installing the apk. the towelroot app gave me the message that "I have root and do not need to reboot my device" but Root checker still says that my root is not configured.
I then reset my phone by pressing volume up+power and home button and clearing "Cache" and wiping data" and trying the above methods again but still unable to get the phone to root.
I am completely stumped as to what I am doing wrong. And would really appreciate some help from the pros.I have attached a snapshot of my device info and thanks for the great work and guidance.
Matt
PS. I already made sure that my phone is in the "Developer Mode" and "USB debugging" is enabled
Click to expand...
Click to collapse
After rooting with Towelroot you have to install SuperSU from the store. Then open and let it update its binary.
You dont need root to get cwm.
DocHoliday77 said:
After rooting with Towelroot you have to install SuperSU from the store. Then open and let it update its binary.
You dont need root to get cwm.
Click to expand...
Click to collapse
Hi Doc, I was able to follow one of your other treads at "http://forum.xda-developers.com/galaxy-s3-att/help/att-bricked-s3-help-please-t2817566/page2" and install TWRP. I think my issue was that the firmware had got upgraded to the NE4 and I was not flashing the correct bootloaders.
I do have one more question and I am not sure if it is a ROM related issue or a phone setting. I will understand if you think I should ask in the ROM thread. I flashed CM11 on the phone after installing TWRP and rooting with superSu. I noticed that the led buttons on the bottom of the phone are disabled(the back and the setting buttons) do you know if this is a changeable setting(pic attached)? I would hate to loose the screen-space at the bottom to the buttons and even though that's standard Kitkat layout I wont mind being able to use the phone led buttons to go back and change settings.
I installled the follwoing version of cm11: cm-11-20140805-SNAPSHOT-M9-d2lte.zip from (http://download.cyanogenmod.org/?device=d2lte)
Thanks for your help and guidance.
Matt
Im not sure about that one. I don't use CM so im not very familiar with all of its different settings. Someone else may have the answer for you though. If not, then ask in the rom thread like you mentioned.

Disabling Knox on Tab S 8.4 4G

I'm brand new to this website, and have only signed up because I cannot find a solution for this problem. I have always used the forum to get answers, but never though to join! My Galaxy Tab S 8.4 4G T705Y was put through the CF-Auto-Root method, and no a glitch at all. Very smooth. By the way I checked the ChainFire website to make sure I was using the latest. When my device started up I noticed, as I have done before with my Nexus phones, that SuperSU has been added. Good Sign!
But when I open SuperSU I was prompted to update the Binary. Then I pressed 'continue', used the 'normal' method, and waited. It then asked me if I would like to Disable Knox. Yes I would! FAILED TO DISABLE KNOX. Shut down SuperSU. Unhappy Face. As you can see at this point, I am not very up to speed with my rooting knowledge.
So then I decided to select the 'never' option to updating SuperSU, and still it failed to update the binary, I'd say due to Knox stopping it from gaining access.
So my pickle is this: I can't update SuperSU because Knox will not allow me to use SuperSU. I cannot simply hit yes to disabling Knox in SuperSU, as that didn't work for me. I also tried finding something called Knox on my tablet and it seems to be very elusive. I tried updating SuperSU on Play Store also, but to no avail!
I am also unable to use any third party app to do so as I need to grant them access in SuperSU before they can begin! And around I go...
There is a guide here http://forum.xda-developers.com/showthread.php?t=2540761 but it's not for my device so I'm a bit hesitant to start trying random things, as my device is working great atm!
Any info or help would be greatly appreciated!
Look in the android development section for my updated builds of cf_autoroot and flash that.
If you still get issues flash supersu v2.49 with twrp.
ashyx said:
Look in the android development section for my updated builds of cf_autoroot and flash that.
If you still get issues flash supersu v2.49 with twrp.
Click to expand...
Click to collapse
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
clint.fish said:
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
Click to expand...
Click to collapse
UPDATE: So now I have managed to try and install the version of superSU that you have released in the dev thread, using TWRP. seemed to work fine, but i still got the same binary missing error.
clint.fish said:
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
Click to expand...
Click to collapse
Whoah way way way over complicating things. You just install twrp with odin and that's it.
Then you flash this with twrp http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
ashyx said:
Whoah way way way over complicating things. You just install twrp with odin and that's it.
Then you flash this with twrp
Click to expand...
Click to collapse
So this is what I do.
Power off device.
Restart in Download Mode.
Use Odin to install the cf-autoroot-twrp-t705.tar from the development section.
When device restarts I put supersu version 2.52 (beta) on the devices memory, then turn off device.
Restart in TWRP Recovery mode, hit install, choose the zip file, install, reboot device.
When device reboots, open superuser and get this message: "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device".
I swear i'm not blonde. :good:
Something is blocking supersu from installing. Which firmware build is this device running and is reactivation lock disabled?
ashyx said:
Something is blocking supersu from installing. Which firmware build is this device running and is reactivation lock disabled?
Click to expand...
Click to collapse
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
clint.fish said:
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
Click to expand...
Click to collapse
UPDATE: So I went into my Samsung account and Performed a factory reset. Only had the device a few days so no biggy. Then as it reset i chose not to put in and Samsung details and skip all the options i could, assuming this would help. Flashed cf autoroot with odin, then updated supersu through twrp... still nothing
clint.fish said:
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
Click to expand...
Click to collapse
UPDATE: SUCCESS! I used the latest version of Kingroot available on this forum. From looking around, you are a very patient person ashyx. Thanks for all your help!
clint.fish said:
UPDATE: SUCCESS! I used the latest version of Kingroot available on this forum. From looking around, you are a very patient person ashyx. Thanks for all your help!
Click to expand...
Click to collapse
This doesn't make sense. Something is amiss if you can't root with cf_autoroot or twrp. You are the only one as far as I'm aware that has experienced this.
Reactivation lock is under 'Find my phone' in security settings.
clint.fish said:
I'm brand new to this website, and have only signed up because I cannot find a solution for this problem. I have always used the forum to get answers, but never though to join! My Galaxy Tab S 8.4 4G T705Y was put through the CF-Auto-Root method, and no a glitch at all. Very smooth. By the way I checked the ChainFire website to make sure I was using the latest. When my device started up I noticed, as I have done before with my Nexus phones, that SuperSU has been added. Good Sign!
But when I open SuperSU I was prompted to update the Binary. Then I pressed 'continue', used the 'normal' method, and waited. It then asked me if I would like to Disable Knox. Yes I would! FAILED TO DISABLE KNOX. Shut down SuperSU. Unhappy Face. As you can see at this point, I am not very up to speed with my rooting knowledge.
So then I decided to select the 'never' option to updating SuperSU, and still it failed to update the binary, I'd say due to Knox stopping it from gaining access.
So my pickle is this: I can't update SuperSU because Knox will not allow me to use SuperSU. I cannot simply hit yes to disabling Knox in SuperSU, as that didn't work for me. I also tried finding something called Knox on my tablet and it seems to be very elusive. I tried updating SuperSU on Play Store also, but to no avail!
I am also unable to use any third party app to do so as I need to grant them access in SuperSU before they can begin! And around I go...
There is a guide here http://forum.xda-developers.com/showthread.php?t=2540761 but it's not for my device so I'm a bit hesitant to start trying random things, as my device is working great atm!
Any info or help would be greatly appreciated!
Click to expand...
Click to collapse
Chimed in with some feedback but noticed your problem solved after I replied. Unable to delete. Glad to see you're good to go though.

Categories

Resources