Update 2: Root was still acting wonky. I was getting multiple requests per app and it wasn't remembering my preference even with the box checked. I tried to allow all but it just wouldn't work at all that way. So I went to update the binaries just to be sure and I had version 3.2 while the latest (and I'm assuming stable) version is only 3.1.1. So if anyone has the problems I did, UPDATE YOUR BINARIES! That fixed everything for me.
Update: I uninstalled the Superuser apk via ES File Explorer, reinstalled it from the Play Store, and just let the phone sit while I was browsing and looking for an answer and when I went back to it Superuser opened and my root was back. I'm not sure if what I did helped but if anyone else has this problem then I can only recommend what I did. If someone can explain what I did wrong or why I lost root, that would still be helpful. If this post needs to be deleted then the mods can do so, I left it in case anyone else runs into this and searches the forums for it.
I have the At&t ion and I managed to get root on ICS on my second try. I was happy about it and decided to start flashing some zips after installing CWM so I deodexed, rebooted, and then flashed one of the status bar tweaks. When I rebooted again Superuser would force close as soon as it opened with the message "Unfortunately Superuser has stopped working". I still have root access in ES File Explorer since I granted it before Superuser stopped working. I cannot however grant any new root permissions since Superuser won't open.
I'm willing to reflash GB and start from scratch again, I'd just like to know what the reason is (was it deodexing? Flashing the zip for the status bar? Or is this just something that can happen?) so I can avoid it the next time. I'm not too excited about having to redownload all my apps for the 3rd time (I was living without root on ICS but decided to go ahead and get it) so if there's a way around it I'd like to find it. Any help is appreciated. I'll try to reply as quickly as possible, thanks guys.
Related
Hi guys I rooted my desire using the live cd method, powered up my phone before installing a2sd and I could see all of my download history on the market with access to all apps. After this I booted into recovery using step2 on the live cd and installed A2SD. When I turned the phone on again all of the download history was gone and I can't see apps like Google Earth, National Rail etc.
I thought I did something wrong so I wiped the device and installed the rooted rom update again with a2sd at the same time. The problem still exists and nothing has changed.
Could you please help me because this is very annoying and I cant set up my phone the I want until this is resolved.
Very strange... Use Market enabler > http://market-enabler.googlecode.com/files/MarketEnabler_latest.html
install, apply new settings and reboot, problem solved
Thanks for the suggestion but the market enabler doesn't solve it, I tried it.
Another strange thing that I found is I have an .apk of CoPilot which I was using before rooting and when I tried installing it now it gives me an error "Application not installed".
I still haven't solved this problem and its really bugging me.
I un-rooted my phone and used a different google account with no luck. I still don't see some applications in the market.
Just to let you know I am in the UK using a generic sim free desire on 3 network. Could you please, please, please help me out. I am running out of options and I thought unrooting would fix it.
Weird issue you are describing. As far as I know it depends on the fingerprint of the build.prop in the ROM (and if Google added it to the white list(?)) or not.
Many people are using the rooted ROM (all the same build.prop) and they can access protected apps just fine. So probably the problem lies elsewhere.
I have a similar problem, before I rooted my device I could see all apps I bought in my g1 days. After I rooted first of all none showed up, after a day or so only a few showed up... rebooted a few more times (only ever flashed once using Windows with apps2sd) now I have a few I had before show up not all just a few and thats how its been since. weird. I had half results :/
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Same problem here with one single application.
Had SlideIT paid version installed on stock firmware.
Once i rooted it gave me the message "application not installed" once i tried to install it.
Funny enough the SlideIT lite version is still able to install fine.
Definitely want it to work again, so i hope someone knows how to fix it
I tried a couple of different ROMs today and had this same problem, clicking My Downloads would just show a blank screen, and there was no "Top Paid Apps" tab. I tried unrooting, rerooting, nothing fixed it, until I found this;
http://www.google.com/support/forum/p/Android+Market/thread?tid=1ea082d443f3d16c&hl=en
Pushing that xml file (note the spelling mistake before you do it) fixed it all back up, no idea what caused it to get all messed up and why it wasn't fixed by wiping and reflashing.
bam0 said:
I tried a couple of different ROMs today and had this same problem, clicking My Downloads would just show a blank screen, and there was no "Top Paid Apps" tab. I tried unrooting, rerooting, nothing fixed it, until I found this;
....
Pushing that xml file (note the spelling mistake before you do it) fixed it all back up, no idea what caused it to get all messed up and why it wasn't fixed by wiping and reflashing.
Click to expand...
Click to collapse
I tried to push the file via adb shell in windows and got permission denied. Am I doing it right or do I need to root the phone again to be able to push that file because I have reverted back to the generic stock rom?
Mine was rooted when I pushed it, try re-rooting it and pushing it again I guess.
I finally got around to re-rooting it and tried your solution with pushing that file but no change to my market
Just to be clear I can see the Top Paid apps tab, but I cant access copy protected apps like Google Earth.
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.
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] Root "disabled" itself!? (Rooted phone that is no longer allowing root access)
Anyone here with this phone (or any) - that is rooted - have it just seemingly act as if it is no longer rooted? or unjustly denying root access for no apparent reason....
Have been rooted since purchase and have never seen or had any issue with this..have flashed custom recovery and rom's hundreds of times...no problems...currently using Task's latest KK 4.4.4 rom and had no issues from beginning...
It comes with SuperUser...i do usually install SuperSU instead but hadn't tried yet...it was fine and apps that needed root appeared ok..even SuperUser has three or four listed apps in the "allow" section...but all of a sudden I can't seem to give root access to anything else now..
First noticed the other day when trying to sideload an apk..couldn't...tried to do it manually by just copying it to system/apps folder and that's when the first message came up saying "it appears your device may not be rooted"...quite odd I thought.. i then tried to install SuperSU and it when SuperUser popped up to give it allowable root access it would only timeout and say denied...i then tried a bunch of other apps that require root and they would all just get denied by SuperUser...
Anyone seen this before or know what causes this and/or how to fix?
THanks for any help or suggestions
ps.. i'm no noob and have been doing this a long time and have rooted/modded dozens of phones, hundreds of times...but this issue is a new one for me.. IF i have to completely wipe and even go back to stock image and then start over to re-root and re-mod... I will and can do so easily..but that would be last resort if necessary...thanks!
In SuperSU, try the clean-up for reinstallation option.
DocHoliday77 said:
In SuperSU, try the clean-up for reinstallation option.
Click to expand...
Click to collapse
when launching SuperSU it needs root access to begin with and SuperUser wont allow..this clean up for reinstall is still doable?
Get the recovery flashable SuperSU then. It'll get rid of the other one in the process. You can get it from my sig, but it'll need to be updated after.
I am not very knowledgeable with the android operating system as a whole, I tried to learn as much as I can but mostly just wanted functionality so I installed cm12.1 for simplicity and root capabilities. Everything was going fine until one day the superuser built into cm12 stopped working after a nightly update(about 3 weeks ago i think), I didn't know what to do, so I tried downloading the app superuser from the play store. When I launched the app there was a notification saying the binaries needed updating and it wasn't working so I found the xda tread for SU 2.46 and downloaded it from chainfire's website. Then everything was back to normal, root checker was showing proper root and all apps were working fine.
When I updated to the current nightly (20151229) and booted back up I had the same problem where root checker shows no root and none of my apps work. So I thought all I need to do is reflash the binaries for SU. After I selected to reboot but right after the s4 mini screen it goes to a black screen and stays there.
Just reading about superuser now, I read that there can only be one super user method so I am thinking that when I downloaded SU from the play store I broke the cm12 internal rooting method, which caused real problems when I flashed the nightly as it overwrote that new method.
What I don't get is why cm12's superuser stopped working in the first place? If somebody knows what I am doing wrong I would really appreciate the help!
My plan as of now is to try and remove the app cleanly remove the app superuser and hopefully restore function to the in built cm12 superuser.
PLEASE HELP :cyclops: