Database Info

superuser 3.0.7 doesnt work

I tried upgrading from su 2.6.3.1 to superuser 3.0.7 over the weekend and after flashing 3.0.7 , none of my apps that required root work - is there a way around this [im using the latest update (1.63...)] Id like to update but seems stuck with older version for now - at least it works.
I did see a Superuser elite in the market... does the new version require you to pay for the license to get root (not that its about money but im just curious)?
Also yes there us an "update fixer" which requires root privileges which the new 3.0.7 version doesnt provide so i cant use that.

try flashing su in recovery http://androidsu.com/superuser/

yeah thats exactly what i did...
I rooted my phone long ago and just got the new update so had to reroot it after installation... which seemed to work fine (with the older su-2.6.3.1) but sadly now that i got this nonworking superuser 3.0.7 (elf).zip in my phone none of my apps that need root access work
At this point im trying to figure how to go back to the older version (unless i can get this one working). Was just hoping i dont have to start all over as i cant even seem to reflash the older version - as it now gives me errors. Might just have to wipe the phone and start all over with the update.
But yeah so I updated the latest htc update and had to reroot my phone, I was able to flash the su-2.6.3.1 via CMR and this worked fine. It seems as i should have stopped there as i saw that the 2.6.3.1 is an older version, so i tried flashing the latest 3.0.7 (elf) superuser -(which appeared to install just fine) but now I dont seem to have root anymore (although i see the superuser app - none of my apps that require superuser work). Ideas? Using adb .. I do see proper permissions on su at /system/bin but - for some reason SU is not working.

Did you make regular Nandroid backups?
You should have made a Nandroid backup through CWM after installation of Superuser 2.6.3.1. I take it this isn't the case, because that backup would mean you could perform a factory restore, reflash CWM, and restore the backup. Any time you are making changes to your phone, backup before and along the way, just in case something like this happens. Titanium has its uses, but if your phone environment gets borked and you can't use it, it kind of defeats the purpose. Nandroid backups are more reliable in my book, and aren't app-dependent.
Sounds like you will have to start from scratch, although I'm unsure as to why Superuser 3.0.7 didn't work as expected. Possibly there was a conflict in moving from 2.6.3.1 to the newer version. I don't know of any specific problems 3.0.7 has with the MT4GS, and I'm running it on my phone with the latest binary without any problems. I do get an error message for one app, Quick Boot, when I use it to boot into recovery, but that doesn't stop the app from functioning as expected. I think that difficulty is related to the app itself and not Superuser.
Hopefully someone with a little more Superuser experience will chime in here. I'm afraid I don't have any ideas beyond the above.
Good luck --
--
KingCheetah

steve_77 said:
It seems as i should have stopped there as i saw that the 2.6.3.1 is an older version, so i tried flashing the latest 3.0.7 (elf) superuser -(which appeared to install just fine) but now I dont seem to have root anymore (although i see the superuser app - none of my apps that require superuser work). Ideas? Using adb .. I do see proper permissions on su at /system/bin but - for some reason SU is not working.
Click to expand...
Click to collapse
I had a similar problem before with SU after switching ROMs. Don't know if it might help but with Titanium Backup it showed that I had no busybox so I dl'ed busybox then SU wouldn't allow the apps to gain root access. Couldn't figure out what the problem was at all. Then I went to the SU app then saw that under the apps that were allowed or disallowed root access, the SU app itself was there. Once I deleted it from the list all the other apps that needed access worked fine. Hope that helps...

KingCheetah said:
You should have made a Nandroid backup through CWM after installation of Superuser 2.6.3.1.
Click to expand...
Click to collapse
Yeah i know - as fate would have it this is the one time i did not make a backup yet as i was hoping to gut out all the crap apps before doing a backup. Guess ill need to get more religious with the backups.
manimmal
Yeah i had Titanium Backup running with busy box before i had the "bright" idea to upgrade to 3.0.7 - but i guess i could try that but likely i might have to start-over from scratch (and forget about the 3.0.7 version) - unless anyone has any other ideas.
The only thing I can think of is perhaps the first su was flashed using one version of CMR and the second another version of CMR (updated after i installed rom manager perhaps)?
Even more interesting is the "su-2.3.6.1-ef-signed" with su having a datestamp of 8/17/2010; while the "Superuser-3.0.7-efghi-signed2" su version has a datestamp of 2/29/2008 - which seems a bit weird....

steve_77 said:
I tried upgrading from su 2.6.3.1 to superuser 3.0.7 over the weekend and after flashing 3.0.7 , none of my apps that required root work - is there a way around this [im using the latest update (1.63...)] Id like to update but seems stuck with older version for now - at least it works.
I did see a Superuser elite in the market... does the new version require you to pay for the license to get root (not that its about money but im just curious)?
Also yes there us an "update fixer" which requires root privileges which the new 3.0.7 version doesnt provide so i cant use that.
Click to expand...
Click to collapse
I'm running Superuser v3.0.7 with no problem, I flashed it in recovery. It has the su binary 3.0.3.2.

Fuzi0719 said:
I'm running Superuser v3.0.7 with no problem, I flashed it in recovery. It has the su binary 3.0.3.2.
Click to expand...
Click to collapse
do you still have the exact same zip file you used to install 3.0.7 ? (perhaps you have a slightly different one then whats available on the website)
I have no doubt that it works on some peoples devices, but i just dont know why it doesn't work on my device. I am pretty much running stock rom with the latest htc update, CMR 5.0.2.7 , rom manager 5.0.0.6 , superuser 2.3.6.1, su binary 2.3.1-ef - this works ( i have root) but if i boot into recovery and install the latest su for froyo 3.0.7 I loose root. (made nandroid backup this time)
I was thinking of trying to use chainsdd "su update fixer" in the market - but dont know how to use this app.. if it helps in debug i am also having a hard time installing busybox. i use "partitions info lite" to check status of my partitions, root access, and that i have busybox installed... i tried installing it via "busybox" [Stephen (Stericson)], which didnt seem to be recognized so uninstalled and tried "busybox installer" [JRummy16] - they are probably separate issues but who knows...

steve_77 said:
... and install the latest su for froyo 3.0.7 I loose root. ...
Click to expand...
Click to collapse
You answered your own question.
Froyo was the version of Android that predates Gingerbread.
The only official release of software for this device is on Gingerbread.
We are moving forward into Ice Cream Sandwich, but not officially.
You are basically trying to install a Windows 7 Program on Windows 95, to craft an analogy.
Stick with the gingerbread release of superuser.
The reason why the version is higher is because for the Froyo version of Android it went through more iterations.
Shame I didn't see this thread sooner, someone else had this same issue a while ago and I gave the same answer, should be around here somewhere. Would have saved you some trouble.

Some confusion here, I think...
Here's what is at ChainsDD's official site, http://androidsu.com/superuser/
Eclair/Froyo/Gingerbread/Honeycomb/IceCreamSandwich (2.1 – 4.0.3)
md5: fc462fa0630379edbe10006b1d19d9b1
Superuser-3.0.7-efghi-signed.zip | mirror | RM Web Connect
binary only
md5: 26d08a253f1883c13561d173094d70b9
su-bin-3.0.3.2-efghi-signed.zip | mirror | RM Web Connect​
The lines after the md5 codes are links for the zip files. Superuser 3.0.7, according to the dev, is applicable to all flavors of Android as listed. This is also the exact file that I flashed and am using on my phone. There is a separate file for Donut 1.6, and it also is designated 3.0.7, but with a slightly different filename: Superuser-3.0.7-d-signed.zip.
I still think updating from 2.3.6.1 is part of the problem. If you go straight to 3.0.7 after your reformatting, it should work properly.
Also, Manimal's suggestion to check that Superuser isn't disallowed within the app itself is a great idea. It's weird, but an easy fix if this is the case.
I believe the update fixer Chains has available is to correct problems with the Superuser app updating new binaries. I don't think this would be of benefit to your situation.
Chains would be the best source for help, I think; an e-mail couldn't hurt --
--
KingCheetah

2.3.4 is froyo right?
Either way the one i installed (i.e. Superuser-3.0.7-efghi-signed.zip) was from the official site (http://androidsu.com/superuser)
which according to the notes shouldn't matter which version as long as its not 1.6 which it certainly isnt as its 2.3.4
will try it again... but thanks for the reply

So why not install the working version, and then just update the binary from within the app?
That would be one way.
Sent from a digital distance.

steve_77 said:
2.3.4 is froyo right?
Either way the one i installed (i.e. Superuser-3.0.7-efghi-signed.zip) was from the official site (http://androidsu.com/superuser)
which according to the notes shouldn't matter which version as long as its not 1.6 which it certainly isnt as its 2.3.4
will try it again... but thanks for the reply
Click to expand...
Click to collapse
Android 2.3.X is Gingerbread. Froyo is 2.2.X. Anyway, the SU you have SHOULD work, it is the same as I used. Have you tried flashing it via fastboot? I simply flashed the 3.0.7 version via recovery when I installed my ROM (stock 1.63.531.2).

Root on Samsung Galaxy 7.0 Plus (GT-P6210)

First, sorry if this is the wrong forum for this, but as a new user, this is the only place I seem to be allowed to post.
Anyway, I have been trying to follow the steps in this thread to gain root on my Samsung Galaxy Tab 7.0 Plus WiFi (P6210)
http://forum.xda-developers.com/showthread.php?t=1777003
I am running Stock ICS 4.0.4.
I managed to get through, booting into recovery, starting CWM (temp version) and installing the root package. Selected reboot and installed SuperUser apk from the market and then tried to update SU. All this went off without a hitch.
However, when I try to get the SuperUser apk to update SU, I get Gaining root access: Failed
I went to ChainsDD's site and grabbed the latest stable SU directly from there (version 3.1.1 for ARM)
http://androidsu.com/superuser/
I even tried some of the other archived versions and his latest 3.2RC3 release, but still the SU apk will not gain root.
It shows latest version = 3.1.1, installed version = 2.3.1-ef.
It succeeds in downloading sutools and new binary but fails in gaining root.
I saw some suggestions about clearing data for SuperUser.apk, so I tried that and another reboot, and still no luck
I am not sure what to try next. I saw some notes about fixing perm for SU, but I am not sure how to do that, I thought the SuperUser APK would do that for me. I did note that the listed perms for the SU seem odd to me (sell, odd compared to su on my Liniux box anyway) and are shown in red in the SuperUser app window
Can anyone help me?
Thanks

[Completed] Cant install v4a, possibly due to partial/incomplete root on vf685 smart kicka

Hi guys. I have a weird problem... I have a vf685 with android 4.4.2
Im trying to install viper audio(v4a) from this site but it fails and says its due to a problem with busy box or my device is not "completely rooted". I am rooted and used several root checker apps to confirm. I have twrp installed as well, xposed modules, root explorers, etc. Everything works fine... Except v4a and also when I open mtk droid tools the square is orange/yellow and it should be green, i have to first click to get root permission. I used king root(not kingo root) to root it, its the only one that seems to work on this phone, I didn't like the superuser app from kingroot so I searched google and found a zip file to replace kinguser with SuperSU and installed with terminal emulator. Is my device only partially rooted (if that's possible) or if not what else could it be?
P.S. its not a problem with busybox, although busybox is installed to /system/bin. Not to /system/xbin
Please help!
Timothy Behrmann

Hi,
Try asking in the official XDA thread: http://forum.xda-developers.com/showthread.php?t=2191223
Good luck

Stuck between Kingroot / SuperSu

Hello,
I successfully rooted my phone (Xperia Z1 Android 5.0.1) with KingRoot 5.0.6. Afterwards I tried to replace KingRoot with SuperSu (https://forum.xda-developers.com/a310/general/how-to-remove-replace-kingroot-kinguser-t3308989). When I ran the script, I got these errors: https://a.disquscdn.com/uploads/mediaembed/images/3096/6825/original.jpg
The script finished and KingRoot was removed but SuperSu wasn't installed. The manual installation of SuperSu (and its binaries) didn't work so I tried to reinstall KingRoot with the newest version. The problem is, that I can't open (nothing happens), uninstall (greyed out) or downgrade ("application was not installed") KingRoot.
Do you have any advice what I could try instead of flashing a new rom?
I have installed TWRP recovery

chicken2000 said:
Hello,
I successfully rooted my phone (Xperia Z1 Android 5.0.1) with KingRoot 5.0.6. Afterwards I tried to replace KingRoot with SuperSu (https://forum.xda-developers.com/a310/general/how-to-remove-replace-kingroot-kinguser-t3308989). When I ran the script, I got these errors: https://a.disquscdn.com/uploads/mediaembed/images/3096/6825/original.jpg
The script finished and KingRoot was removed but SuperSu wasn't installed. The manual installation of SuperSu (and its binaries) didn't work so I tried to reinstall KingRoot with the newest version. The problem is, that I can't open (nothing happens), uninstall (greyed out) or downgrade ("application was not installed") KingRoot.
Do you have any advice what I could try instead of flashing a new rom?
I have installed TWRP recovery
Click to expand...
Click to collapse
Maybe you need to open the TWRP and browse to the location where your phone stores the su binary file, which is most likely stored in the:
/system/xbin , or
/system/bin
Delete the existing binary if any alongwith the other su files like daemonsu,etc , and repeat your previous installation methods.

chicken2000 said:
Hello,
I successfully rooted my phone (Xperia Z1 Android 5.0.1) with KingRoot 5.0.6. Afterwards I tried to replace KingRoot with SuperSu (https://forum.xda-developers.com/a310/general/how-to-remove-replace-kingroot-kinguser-t3308989). When I ran the script, I got these errors: https://a.disquscdn.com/uploads/mediaembed/images/3096/6825/original.jpg
The script finished and KingRoot was removed but SuperSu wasn't installed. The manual installation of SuperSu (and its binaries) didn't work so I tried to reinstall KingRoot with the newest version. The problem is, that I can't open (nothing happens), uninstall (greyed out) or downgrade ("application was not installed") KingRoot.
Do you have any advice what I could try instead of flashing a new rom?
I have installed TWRP recovery
Click to expand...
Click to collapse
Try deleting the kingroot app manually. If its installed, it should be somewhere in data/app or system/app.
If that's successful, then reinstall Kingroot and try rooting again. Instead of running a script to replace Kingroot with SuperSu, try using "SuperSuMe" instead. Its available on the playstore.

Ya SuperSuMe is was worked for me a while back when I needed to do the same. I think it was 2$ bucks.
Sent from my Nexus 6P using Tapatalk

Root Kindle Fire HD 10

I was able to use Kingoroot for PC to root my Fire HD 10. Updated to the newest Firmware. It would say it was rooted. But, Trying to give permissions and checking with root checker was not successful and said there was no root. I installed SuperSU apk it says the binary is occupied. So I Uninstalled the superuser apk. that was installed by Kingoroot and tried to change the build prop with a root browser text editor and it was successful so apparently it roots but superuser is not working to grant or deny permissions. It automatically grants permissions does not even open up superuser so its kinda dangerous but it is rooted and working. My experience is that kingoroot superuser must be Uninstalled for root to work. I used twrp manager to backup my recovery img., and boot img. I am going to try to build a recovery for it but I'm not In a hurry plus I'm not sure if it will flash afterwards anyways but if you want root, Kingoroot for pc and Uninstalled the kingoroot superuser apk it installs and you will have it
Installed magisk manager installed zip direct (recommended) it bricked the fire. And then I adb sideloaded the update and now I'm back in business reasonably easy to do but I do not recommend magisk at this time .
Going to try xposed next
Couldn't get it to install says it's arm device tries to install and says it's an arm64 device. Plus has to be flashed in recovery and one hasn't been built yet

You can't manage Kingoroot su binary using SuperSU.
If you not install SuperSU su binary, SuperSU apk does not working.
Try this method to install SuperSU su binary.
https://forum.xda-developers.com/showpost.php?p=75242414&postcount=99

erono said:
You can't manage Kingoroot su binary using SuperSU.
If you not install SuperSU su binary, SuperSU apk does not working.
Try this method to install SuperSU su binary.
https://forum.xda-developers.com/showpost.php?p=75242414&postcount=99
Click to expand...
Click to collapse
I installed supersu to find out if it was rooted since the root checker said it was not. the binary error was a confirmation that it was in fact rooted and it doesn't matter what superuser is used it will not allow pop up or apps to draw over other apps so when it's rooted with kingoroot it automatically grants root without a confirmation,as long as the kingoroot super user app is not installed and if SuperSU is kept installed default permission has to be set to grant for root to work. I in fact installed the SuperSU binary through an older version of the apk and it installed but still has no control over denying or granting permissions. Thanks for the advice though. I appreciate your willingness to help me

Joker1716 said:
I was able to use Kingoroot for PC to root my Fire HD 10. Updated to the newest Firmware. It would say it was rooted. But, Trying to give permissions and checking with root checker was not successful and said there was no root. I installed SuperSU apk it says the binary is occupied. So I Uninstalled the superuser apk. that was installed by Kingoroot and tried to change the build prop with a root browser text editor and it was successful so apparently it roots but superuser is not working to grant or deny permissions. It automatically grants permissions does not even open up superuser so its kinda dangerous but it is rooted and working. My experience is that superuser must be Uninstalled for root to work. I used twrp manager to backup my recovery img., and boot img. I am going to try to build a recovery for it but I'm not In a hurry plus I'm not sure if it will flash afterwards anyways but if you want root, Kingoroot for pc and Uninstalled the superuser apk it installs and you will have it
Installed magisk manager installed zip direct (recommended) it bricked the fire. And then I adb sideloaded the update and now I'm back in business reasonably easy to do but I do not recommend magisk at this time .
Going to try xposed next
Click to expand...
Click to collapse
Not trying to insult your intelligence or anything here, but you said newest firmware? Newest Fire firmware? Newest firmware isn't rootable from my understanding.
What firmware were you on when you started the root process?
Also, are you making sure that the Kingoroot "install our extra junk" box isn't checked (not sure that would prevent root success)?
It wouldn't open superuser. superuser should be set to "grant" because of how the Fire works, which it sounds like you are aware of based on your last post. I wouldn't say it's dangerous, per se.
I've followed this guide nearly a dozen times now and I've not run into the issue(s) you're having.

smam1338 said:
Not trying to insult your intelligence or anything here, but you said newest firmware? Newest Fire firmware? Newest firmware isn't rootable from my understanding.
What firmware were you on when you started the root process?
Also, are you making sure that the Kingoroot "install our extra junk" box isn't checked (not sure that would prevent root success)?
It wouldn't open superuser. superuser should be set to "grant" because of how the Fire works, which it sounds like you are aware of based on your last post. I wouldn't say it's dangerous, per se.
I've followed this guide nearly a dozen times now and I've not run into the issue(s) you're having.
Click to expand...
Click to collapse

Prompt dialog not working in amazon fire devices.

erono said:
Prompt dialog not working in amazon fire devices.
Click to expand...
Click to collapse
Set prompt to grant and fixed.

yes. mind doesnt pop up supersu granting notification too
my fire hd 10 is on 5.6.1.0
someone told me it's amazon's own security measure

stevenchun said:
yes. mind doesnt pop up supersu granting notification too
my fire hd 10 is on 5.6.1.0
someone told me it's amazon's own security measure
Click to expand...
Click to collapse
One can try this improvement :
SuperSU access workaround for Fire devices
https://forum.xda-developers.com/hd8-hd10/general/supersu-access-workaround-fire-devices-t3738269