I am using the Sense 3.0 rom based 3.06 desire hd build by mikhei777 on my htc hd2. Once, the market told me to update the supersuser app.
I updated it. It told me about the outdated binary. I updated it. Eveything thing was working well until I rebooted my phone. Now everytime I launch an app that requires root access superuser force closes. The app itself wont even open. PLEASE Help!!!!!!
Related
Sup guys. This place seems a little dead without any new rom releases lol. Just went to the market to check for some new apps and updates and saw that superuser was available for update.
Kinda weird but I did it and opened the new app. It has a slightly different interface, something like the new market except without the lags. Then it told me that I had to do some updates and I just allowed it blah blah blah. It installed some new software and a custom busybox.
I find that the v6 supercharger works better with this busybox and the other new root stuff lol.
Go check it out!
Sent from my Milestone XT720 using XDA App
You must paying attention we have cm7 just wasting space in the forms.
Sent from my XT720 using XDA Premium App
I upgraded to 3.0 and saw all kinds of problems. Couldn't update the binaries for some reason and lost all permissions and could get su access back. Reverted in TB to okd su and ut was fine. Since then chains updated it again and everything works fine now. Just an fyi.
@Mchlbenner Like your new avatar. Funny.
Thanks
Sent from my XT720 using XDA Premium App
Hey, since we have these new ROMs going and there was some issues before with the Superuser.apk updating the binaries, Chains has created and update fix in the market also. You update the superuser app and then it either works or says the binary didn't update or the app itself couldn't update. Just go to the Update Fix app install and run it and then try to reinstall the Superuser.apk.
If you are flashing in between ROMs daily then I wouldn't worry about it until you settle on one, but if you do find one you like and want to run it for some time, then you'll probably have to eventually update it and this is how.
Woodrube said:
Hey, since we have these new ROMs going and there was some issues before with the Superuser.apk updating the binaries, Chains has created and update fix in the market also. You update the superuser app and then it either works or says the binary didn't update or the app itself couldn't update. Just go to the Update Fix app install and run it and then try to reinstall the Superuser.apk.
If you are flashing in between ROMs daily then I wouldn't worry about it until you settle on one, but if you do find one you like and want to run it for some time, then you'll probably have to eventually update it and this is how.
Click to expand...
Click to collapse
You can also get the latest as an update.zip at AndroidSU.com
Has anyone had an issue with the newest binaries with the latest superuser AP? When I updated the binaries, I lost root permissions even though it shows permission is granted.programs requiring root access will not work. If I use the old binaries aps work correctly. The only annoyance is the constant reminder that there is an update to the binaries available. Any fix?
I had that problem a few days ago.
Over the course of a few days, I received 2 update notifications of Superuser app from Android Market. The 2nd update fixes the problem.
I suggest you check "My Apps" in Android Market for an app update
goto the Market & uninstall the updates. 3.05 is the one causing the force closes. Revert back to 3.02. You can also search for the 3.02 version & goto cwm and flash 3.02. that will fix the problems saying you don't have root. I had that problem on my HTC Thunderbolt also. www.teambamf.net had this solution in one of their threads.
I had that problem a few days ago.
Over the course of a few days, I received 2 update notifications of Superuser app from Android Market. The 2nd update fixes the problem.
I suggest you check "My Apps" in Android Market for an app update
* * *
I tried the latest update and still have the same issue.
Thanks* * * *
ruddogg said:
goto the Market & uninstall the updates. 3.05 is the one causing the force closes. Revert back to 3.02. You can also search for the 3.02 version & goto cwm and flash 3.02. that will fix the problems saying you don't have root. I had that problem on my HTC Thunderbolt also. www.teambamf.net had this solution in one of their threads.
Click to expand...
Click to collapse
I'll try that and report back.
Thanks
I rolled back the update and I am no longer told the binary needs an update...although that does make me nervous about other stuff...
Just wondering if anyone has been able to successfully update Google Music? When I attempt to update from the Market, it errors out after downloading. It says installing for a bit then "Error: Package file was not signed correctly"
Currently, I'm on GS2.4.4
:edit:
Apparently you have to uninstall 4.0.1 first. Duh! Guess I tried everything but google... I'll go to my corner now.
https://www.androidpolice.com/2011/...sic-4-0-9-app-now-live-on-the-android-market/
Posted too soon. Couldn't just uninstall, so used Root Explorer to delete /system/app/music.apk
Reboot and install of 4.0.9 from Market was successful. However, it just FC.
More work to be done.
: edit:
Ignore me. Uninstall/reboot/re-install and now it works
Mine updated perfectly fine except oddly enough it does not look like the preview of the app I saw on theverge.com. Is it showing the tablet version? As it shows cover art in portrait mode, btw i'm still on streakdroid 2.3 though as it has been stable for me, so this may be the reason my update went fine.
Sent from my Dell Streak using XDA App
Problem was that tenorntex's ICS theme flashed a leak'd 4.0.1
I tried using Root Explorer and deleting /system/app/music.apk (when I had 4.01) but kept getting the error "App already exists" even after rebooting.
I still couldn't download the market version for some reason so I snagged the 4.09 from here
You cant install 4.09 if you have 4.01 installed as they apparently have different certs, this is true for all apps
I just upgraded to JB on my HTC Evo 4G lte. I am S-ON rooted and everything is working except SuperSU v0.99. I see several others are having the same issue. We are rooted and our apps can obtain root but when you open the SuperSU app, it wants to update the binary. If you allow it to update the phone crashes and reboots. If you select cancel SuperSU closes and you cannot get to any of the settings. There does not seem to be a solution that I have found. I would like to switch to another Superuser app but can't seem to find instructions on how to do so.Will changing to another Superuser app even solve the problem? Ideas?
Edit: Upon further investigation it appears that changing to ChainDD's superuser app may not solve the issue of not being able to update the binaries. So what is the solution?
Edit: I got my answer:
xHausx said:
The only solution is to get s-off. It looks like the new hboot locks the system partition so apps such as supersu and ad-free aren't going to work for you anymore.
Click to expand...
Click to collapse
I'm having the same issue. I switched to superuser and now I'm rooted as root checker states but I can't use adaway any more as Xhausx mentioned that the system directory in JB is locked now and the only way to make it work is to get s-off which is not available right now and i doubt it will be.
Sent from my EVO using xda app-developers app
I am losing root access and updating apps. This is the first time i have been having this problem. I think it has something to do the supersu update of app, but not sure. I backed up with root so not a big deal but dont know why this is happening. Do I need to unroot then root again or is there a know issue with this rom.
Try uninstalling the SU app completely and reinstalling it. Then, open the app and confirm the binaries are up to date. Next time, be sure to post questions in the Q&A category please.
Sent from my EVO using xda app-developers app
Last time I flashed sense 5 I think all I did reinstall updated binaries and reboot. If you have any market issues (force closing being most common) delete and reinstall Google play services