Hello and just got a noon question for the pros. Have just flashed CM v10.2 android 4.3 everything running good only question is SuperUser says it need binary update but when I try to update it give me a fail message followed by reboot and try again I have several times even tried SuperSu with same outcome. Any input as to why I am guessing that Superuser is not comparable with 4.3 guess I just try to deal with the out dated Superuser for now and hope the pros got a good fix thanks in advance Galaxy S4 noob& Galaxy S2 Pro.
Sent from my SGH-I337 using XDA Premium 4 mobile app
I believe their 4.3 OP has instructions for what to do to allow superSU. Go check. You'll need to access your settings.
Update: To get root working go to Settings/Developer options/
Then change the option "root access" to "apps and adb"
Related
I have a Galaxy Tab 10.1 (PT-7500R from Rogers), trying to root on the new official ICS.
I have followed the directions at http://forum.xda-developers.com/showthread.php?t=1239185
CWM installed and works fine. After applying "Samsung_Galaxy_Tab_10.1_root.zip" in CWM, I boot into Android, I see SuperUser in my app menu and can bring up its interface.
However, when I try to launch a su-required function (such as Reboot Recovery in ROM Manager), I don't get a prompt for SU permissions.
I have tried this with both OTA and manual (Odin3) installs of the official ICS from Rogers, from unrooted stock Honeycomb, several times.
I don't encounter this problem with stock Honeycomb... rooting that version appears to work fine.
I have experimented with some community builds, perhaps I have installed an incompatible kernel that needs replacing? I don't know, but any advice would be greatly appreciated.
Regards,
diggerB
diggerb said:
I have a Galaxy Tab 10.1 (PT-7500R from Rogers), trying to root on the new official ICS.
I have followed the directions at http://forum.xda-developers.com/showthread.php?t=1239185
CWM installed and works fine. "After applying Samsung_Galaxy_Tab_10.1_root.zip" in CWM, I boot into Android, I see SuperUser in my app menu and can bring up its interface.
However, when I try to launch a su-required function (such as Reboot Recovery in ROM Manager), I don't get a prompt for SU permissions.
I have tried this with both OTA and manual (Odin3) installs of the official ICS from Rogers, from unrooted stock Honeycomb, several times.
I don't encounter this problem with stock Honeycomb... rooting that version appears to work fine.
I have experimented with some community builds, perhaps I have installed an incompatible kernel that needs replacing? I don't know, but any advice would be greatly appreciated.
Regards,
diggerB
Click to expand...
Click to collapse
Have you tried to see if superuser had an update in the market? I recommend to also make sure the binary is up to date in the superuser app.
Sent from my SAMSUNG-SGH-I747 using xda premium
nakedninja42 said:
Have you tried to see if superuser had an update in the market? I recommend to also make sure the binary is up to date in the superuser app.
Click to expand...
Click to collapse
Thank you for your reply.
I updated to the latest version in Play Store, it shows Binary v2.3.1-ef , update check shows latest version 3.1.1 but when I click Update, it fails on the step "Gaining root access..."
Cheers
diggerB
You're not rooted anymore. The superuser app is there but it can't do anything since the su is missing. You have to re-root.
Sent from my GT-I9300 using Tapatalk 2
Tyxerakias said:
You're not rooted anymore. The superuser app is there but it can't do anything since the su is missing. You have to re-root.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the feedback... but I just went back into CWM and applied the root again, still in exactly the same boat.
Thanks to all, I found a solution in another thread: http://forum.xda-developers.com/showthread.php?p=31179418#post31179418
Superuser just didn't want to work. The SuperSU root method referred by the OP in that thread worked great. All is well again. Until next time of course.
Hi, if you go to "www.galaxytabhacks.com" you will find the solution, there is an upgrade to superuser.
I hope someone can help me.
After my KF HD 7" running 7.2.3 updated itself to 7.3.0 i lost my root but I have now rooted it using v27 binary and qemu root as the guide on here shows. Everything worked perfect and i can use blackmart alpha again. But when I click on SuperSU I get the message The SU binary needs to be updated. Continue? I press continue and get the option to use normal or custom recovery so I press normal. Then after a minute or so i get the error installation failed!
I have searched for a solution but nothing is the same as my issue on this device.
I have SuperSU installed and superuser (when I try and open this I get superuser has stopped)
I have tried uninstalling SuperSU and re-installing it but still the same!
I can still install apps by downloading them on blackmart alpha then using ES explorer to install them. Where before blackmart used to do it itself.
Are you sure you aren't updated to 7.3.1 and have lost root
Sent from my GT-P3110 using xda app-developers app
No, definitely 7.3.0 in the about section of the device
In fact your are right! I've just had a look and its running 7.3.1, so I'll root it again. Thanks
Sent from my KFTT using Tapatalk 2
H17YD_L said:
In fact your are right! I've just had a look and its running 7.3.1, so I'll root it again. Thanks
Sent from my KFTT using Tapatalk 2
Click to expand...
Click to collapse
Problem for you over here
I just tried getting root access via this guide using Odin, but although I've already updated the firmware first, it just doesn't take. It installs the superSU app, but not the binary it seems. Any idea where I can get it from? I also tried superuser instead, which allows me to get an up to date binary, but when it then tries to install the binary it fails.
Here's the guide I followed:
http://m.ibtimes.co.uk/galaxys4-gti9505-official-android422-xxuadmn-jellybean-firmware-464478.html
Any ideas?
XXUAMDM Root not possible?
Hi,
have done the same, tried to root the I9505 XXUAMDM (European LTE model) - there was no SU installed.
Therefore I installed the SuperSU from the market and checked, but it says that the SU Binaries are missing...
So what went wrong with rooting? Any suggestions
BTW: After the start of Titanium Backup the window asking about root for the app appeared.
Now starting Super SU I can see Titanium in the list, but short after start the mentioned "SU-Binary missing" window appears...
jochenthomas said:
Hi,
have done the same, tried to root the I9505 XXUAMDM (European LTE model) - there was no SU installed.
Therefore I installed the SuperSU from the market and checked, but it says that the SU Binaries are missing...
So what went wrong with rooting? Any suggestions
Click to expand...
Click to collapse
Exactly the same as me, the update went fine, the rooting seemed to go fine too, but the binary is supposedly missing.
Just been pointed to this thread, which works a treat:
http://forum.xda-developers.com/showthread.php?t=2255190&nocache=1
It seems the method we used isn't compatible with the MDM and MDN firmware updates, so need to use a modified version of CF auto root instead. In that thread it also shows you how to reset the flash counter too! Result!
StuartTheFish said:
I just tried getting root access via this guide using Odin, but although I've already updated the firmware first, it just doesn't take. It installs the superSU app, but not the binary it seems. Any idea where I can get it from? I also tried superuser instead, which allows me to get an up to date binary, but when it then tries to install the binary it fails.
Here's the guide I followed:
http://m.ibtimes.co.uk/galaxys4-gti9505-official-android422-xxuadmn-jellybean-firmware-464478.html
Click to expand...
Click to collapse
I know your sorted ow but out of interest before were you using steps outlined here when it didn't work on mdm
http://androidjinn.com/root-xxuamdm-android-4-2-2-on-galaxy-s4-i9505-official-firmware.html/2
Sent from my GT-I9505 using xda app-developers app
topcat07 said:
I know your sorted ow but out of interest before were you using steps outlined here when it didn't work on mdm
http://androidjinn.com/root-xxuamdm-android-4-2-2-on-galaxy-s4-i9505-official-firmware.html/2
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Different guide, but same method. We simply needed a modified file t work on the newer firmware.
StuartTheFish said:
Different guide, but same method. We simply needed a modified file t work on the newer firmware.
Click to expand...
Click to collapse
Strange someone has got it working with normal file
Sent from my GT-I9505 using xda app-developers app
topcat07 said:
Strange someone has got it working with normal file
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Pass, don't know! All I do know is the regular cf auto root didn't work for me on this firmware, but the modified one did.
StuartTheFish said:
Just been pointed to this thread, which works a treat:
http://forum.xda-developers.com/showthread.php?t=2255190&nocache=1
It seems the method we used isn't compatible with the MDM and MDN firmware updates, so need to use a modified version of CF auto root instead. In that thread it also shows you how to reset the flash counter too! Result!
Click to expand...
Click to collapse
OMFG I have googled and torn my hair our for hours and hours as I just could not get root on my MDM S4 using the methods detailed on this site, this modified file rooted it straight away with no problems. It REALLY needs to be shouted a bit louder lol !
Thanks all.
this doesnt work for i9500
this kernel does not root i9500.
anyway i have a different problem and its about bluetooth. is this the proper place or should i search elsewhere?
No, there's a different method to rooting for a gt19500.
Thanks
My new Samsung Galaxy S4 GT-19505 is running build JDQ39.19505XXUBMEA (android 4.2.2).
I haven't found anything on this build number with regards to rooting, so I'm wanting to be a little cautious before I attempt anything.
Any pointers on what tools / options I might attempt to use to root this?
SirLoinOfBeef said:
My new Samsung Galaxy S4 GT-19505 is running build JDQ39.19505XXUBMEA (android 4.2.2).
I haven't found anything on this build number with regards to rooting, so I'm wanting to be a little cautious before I attempt anything.
Any pointers on what tools / options I might attempt to use to root this?
Click to expand...
Click to collapse
Flash CF-Root with Odin and you`re rooted. Link http://forum.xda-developers.com/showthread.php?t=2219803, read the OP well and it will be easy.
Thanks for your quick reply!
If I'm reading things properly, that will root my device & reset it to factory defaults (ie: wipe it). Correct?
Sent from my GT-I9505 using Tapatalk 4 Beta
SirLoinOfBeef said:
Thanks for your quick reply!
If I'm reading things properly, that will root my device & reset it to factory defaults (ie: wipe it). Correct?
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
No, it will only root it, you will not loose any data. After that flash a custom recovery if you need it and Busybox from Google Play,
SirLoinOfBeef said:
Thanks for your quick reply!
If I'm reading things properly, that will root my device & reset it to factory defaults (ie: wipe it). Correct?
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
There won't be any changes but root will be extra it won't wipe anything and u need not factory reset also
.
I tried it, and I'm not sure if it worked or not.
I have a a new SuperSU icon, but when I open it SuperSU tells me that the binary needs updating.
When I try to update it though it comes up with "Installation failed!"
Did the root fail? Is there something wrong with SuperSU? I'm not sure what's going on :s
SirLoinOfBeef said:
I tried it, and I'm not sure if it worked or not.
I have a a new SuperSU icon, but when I open it SuperSU tells me that the binary needs updating.
When I try to update it though it comes up with "Installation failed!"
Did the root fail? Is there something wrong with SuperSU? I'm not sure what's going on :s
Click to expand...
Click to collapse
Close all apps, reboot and try again to update the binaries. Have you checked for an update of the SU app in Google Play?
There was an update, which I have installed.
I also just installed Root Checker (https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en) which tells me I am not rooted
SirLoinOfBeef said:
There was an update, which I have installed.
I also just installed Root Checker (https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en) which tells me I am not rooted
Click to expand...
Click to collapse
Open the SU app and unroot and try rooting again by flashing CF-Root. Do you have usb debugging enabled on the phone in developer options?
I have debugging enabled.
I tried re-rooting, and now have no SU app at all
Very confused. This should be a simple process.
I was very keen to upgrade to OTA update of 1.8MB through CWM which I could by unrooting the device but what a fool I am that I didn't had any root keeper and now I have spent around 4 hours rebooting and testing my phone for like 50 times but CHAINFIRE SU don't appear at all and neither ROOT CHECKER shows any status about the root. I have tested almost everything posted on the internet but didn't helped I tried even the WUGSFRESH but it wasn't of any help. I have UNLOCKED BOOTLOADER and I am going mad without ROOT. Is there any way I can root my phone again.
Have you tried updating SuperSU from the market to see if it will prompt you to update the binaries?
Sent from my Nexus 4 using Tapatalk 4
you can just flash supersu from your recovery. google supersu, go to the supersu xda thread, download the flashable supersu, then flash it via your custom recovery.
fernandezhjr said:
Have you tried updating SuperSU from the market to see if it will prompt you to update the binaries?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
OMG, it was too easy just update the binary normally from the google play and I spent around 4 hours and 50 reboots. Damn, I cant believe I did that and didn't posted here on the forum of gurus. Next time will post here and then use my tiny little brain. Thanks to you two, You saved my day