Stuck in partially rooted vicious circle on TF201 - Asus Eee Pad Transformer Prime

I had root on my TF201. Had to send the POS back to Asus, they flashed new OS, killed my root, but it appears to have left behind files or an SU Binary & Superuser.apk. So, when I try to use new root methods - Motochopper or Kingo - it fails despite both showing I am rooted. So, since I am not rooted, and thus do not have proper permissions to remove files, I cannot remove the old Superuser.apk or SU. So it is kind of an ugly circle. No root means no ability to get rid of old root files to try to do a clean root, but yet the newer root exploits see me as rooted and so.. don't actually root (or correct my root). And the system shows Superuser.apk installed but there is no way to uninstall the app - it gives no ability to do so.
Any thoughts on how to get out of this ouroboros? A way to get this old Susperuser.apk and SU off my tablet so I can do a fresh root.

Bump... any help on this?

I am in the same boat....mine was due to an OTA though

Related

[Q] superuser.apk force close

Superuser.apk is force closing on me. I can run TiBu and Wireless Tether (both of which require root access), so I know I have root access, but when I try to open the superuser.apk, or when I install / upgrade an app I get a FC from the superuser.apk.
Where I am:
-ATT Atrix, stock / bootloader locked with 4.5.91 applied through USB over stock / bootloader locked / rooted 4.1.83
-Did the preinstall root method from briefmobile after the 4.5.91 update
-Updated the superuser.apk from the market
-Rebooted a number of times
At this point the phone is running fine, and I need it for work so I want to stay away from a potential brick, but I have gone through custom ROM's on previous phone (ATT Captivate). The FC is really more of an annoyance, and I'd like to make sure that if / when I decide to go the custom ROM route my su is working as it should.
Any thoughts / suggestions?
OK, I read a bit more and tried to clear the data on the superuser app. Now, after a reboot, TiBu can't even get root access because the app FC's when I open TiBu.
Help?!
sjroberts98 said:
OK, I read a bit more and tried to clear the data on the superuser app. Now, after a reboot, TiBu can't even get root access because the app FC's when I open TiBu.
Help?!
Click to expand...
Click to collapse
Have you tried unrooting, factory reset, and then rooting yet?...
No, haven't tried that. To unroot, should I just uninstall the superuser.apk? I don't think I've seen an unroot script for 4.5.91 yet.
Thanks for the tip, I'll try that once I figure out the best way to unroot.
OK, it appears to be resolved.
What I did:
-uninstall the superuser.apk through Manage Applications
-download the preinstall file from the XDA forum post (versus the file from briefmobile.com)
-re-ran the same steps
-rebooted
All appears to be working now. My guess is that it was user error (read: I did something wrong the first time).
Nevermind...

[Q] Busybox install location

Hi
I used busybox installer from the market, the default was to install it in system/xbin I subsequently installed again, this time in system/bin (don't ask) Will having multiple instances of busybox be harmful in any way? I ask this, as I lost root when I did the second install, and couldn't root the phone again after this via superoneclick. Since then however, I have managed to root the phone through other means. But as this did happen, I wondered if I might run into future problems? Everything seems stable at the moment though.
Thanks.

[Q] At&t logo in status bar?

In the stock firmware, was it always there? I just rooted my phone and I just noticed it. I don't remember if it was there before I rooted.
Lol
Rooting does nothing to the firmware it just places the su and busybox binaries into the correct directories so that when an app requests root access, another app like superuser or supersu is launched to grant that access with said binaries.
therefore, yes it was there before.

[Q] Can Malware install silently if I have SU installed?

One thing that I keep reading about android malware, is that it needs to gain root access to do its dirty work.
My android phone is already rooted and I have SuperUser (SU) installed. And whenever an app runs that needs root access (such as titanium backup), SU asks me if I want to grant root to that app.
So, my question is this - can I rest assured that I won't get infected because if for some reason malware makes it into my phone (through one of the many exploits like the MMS/Stagefright thing), I will see it try to run because SU will ask me for permission, and I can simple deny it?
Yes, Lookout security recently discovered a malware that does the exact thing you mentioned.
http://www.xda-developers.com/looko...ed-adware-that-secretly-acquires-root-access/

How to Unroot Android Device (Samsung Galaxy Avant)

This question has probably been asked a million times before, but my circumstances are a little different. On my first attempt, I used the "unroot" option on Superuser, and it claimed my device had been cleared of root access after booting back up. However, after realizing my root apps still worked, I downloaded a root checker and confirmed my suspicion that my phone hadn't changed. Afterwards, I followed a Youtube tutorial and deleted various SU files in my system's directory, but partial root access remains. No unroot app works because Superuser can't grant full root access, and SU itself crashes upon booting when I re-download it. I've attempted re-rooting my phone so I had full root access, but that won't work either. Any suggestions?

Categories

Resources