Related
Following the guides in the Development section, if you are to root the TF300T, would simply flashing a new blob file (whether its .17 or .26) remove your root? I am assuming the update formats the /system partition and restores all of the default files. Will this also be a way to restore anything that I remove from the /system partition manually (apks for example)?
I'm not new to Android, but haven't had to deal with blob files or the lack of a custom recovery before.
Well, I can confirm that if you need to unroot your TF300T for any reason, it is a very simple process:
1. Download your desired blob file from here: http://forum.xda-developers.com/showthread.php?t=1642614
2. Follow method 1 of Wolf's guide: http://forum.xda-developers.com/showthread.php?t=1622628
3. Factory reset/wipe data. All stock AFAIK!
Has anyone tried to hit the 'unroot' button in SparkyRoot's app?
Unroot in Sparkyroot is how I unrooted last night. It's quick, easy, and painless.
Unrooting with the sparky root works as well if your not into the ADB thing
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
I must have forgotten that Sparkyroot had that button, oh well. At least we know this method works to get back to .17
So just reviving this thread... if I need to take my rooted Pad back to the shop for a replacement (the fitting round the screen seems loose in one bit), I can
1) backup with the Asus Appbackup/Titanium Pro etc
2) click Sparklyroot's unroot button, and
3) do a Factory Reset/Wipe and voila!?
Anything else I should think about?
aliaird said:
So just reviving this thread... if I need to take my rooted Pad back to the shop for a replacement (the fitting round the screen seems loose in one bit), I can
1) backup with the Asus Appbackup/Titanium Pro etc
2) click Sparklyroot's unroot button, and
3) do a Factory Reset/Wipe and voila!?
Anything else I should think about?
Click to expand...
Click to collapse
Use voodoo ota root keeper to delete root backup
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
ok... everytime i unroot i keep getting superuser back... is that on by default?? I use the delete su backup awith ota rookeeper and then unroot with sparkyroot but it stays rooted...
I rooted my Infinity a few days ago, and I changed my mind. How the heck do I unroot? I cannot find the answer anywhere...
Before root the boot time was under a minute by far, now it is 3 minutes and 45 seconds...this can't be right.
Anyone know why this is happening or how I can fix it? If not can anyone tell me how to unroot please?
Thanks.
I rooted my tf700 and the boot is like unrooted, under 1 minute.
Have you tried to make a cold reboot?
If you want to unroot, i've used the method described in this post to unroot my previous tf300 before returning it.
http://forum.xda-developers.com/showthread.php?t=1622628
It had worked fine.
I've used 'Method 1 - Rooted' instructions.
You have to download the blob corresponding to your tf700 from asus and with adb write it to the tf700
Just remove /system/xbin/su (as root) and uninstall Superuser app, but this is user-based, so I doubt anything on the boot uses root privileges differently just because suddenly you have the binary there.
Are you sure you haven't installed any apps or new firmware lately?
Or just Factory Reset if your really desperate. Root gone.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
jjdevega said:
Or just Factory Reset if your really desperate. Root gone.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
I don't think that a factory reset removes root.
Don't ask me to prove it, i don't want to reinstall my Tf700
htcvidi said:
I don't think that a factory reset removes root.
Don't ask me to prove it, i don't want to reinstall my Tf700
Click to expand...
Click to collapse
Correct. Factory reset means wiping the /data partition, for which there is no reason in this case. Re-flashing firmware sometimes wipes /system, sometimes just overwrites the files on it (normally leaving /data intact), which will lead to removing "su" most of the time (Superuser.apk stays in /data, but can be easily uninstalled). If someone has used RootKeeper, it can leave a copy of "su" somewhere on the system partition, too, but can be removed from within the app.
OK, need someone to tell me what I'm missing please.
Yesterday I was on stock .30 and rooted. This morning I took the JB update. My first boot was OK and I still had root, but when I rebooted, I got stuck in a loop. It kept rebooting after getting to the desktop. I assumed at least one of my apps was causing it, so I used the wipe data function with the power + vol down thing. that wiped everything, including root.
I tried to re-do the debugfs method, but that seems to fail. Strange thing is, if I use adb shell from the computer, I can su - root and get root access. That's how I was able to give read/write access to the data folder where debugfs does its' work. It's just that root check says I'm not rooted. Voodoo OTA has all boxes checked on my root check, except the one that says granted root permissions. The SU file does exist inside /system/xbin
So it's as if the tablet's user just doesn't have permission to do root. I loaded a terminal emulator on the tablet, and tried to su - root that way, and got permission denied. I would normally get the "superuser" popup when doing something like that -
So there's definitely a piece I'm missing. Can someone point me in the right direction please?
reinstall ota rootkeeper and restore root. factory reset doesnt wipe root access you just need to restore it.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
jgaf said:
reinstall ota rootkeeper and restore root. factory reset doesnt wipe root access you just need to restore it.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Sorry, should have mentioned that I tried that. Attaching a screenshot as to what it looks like. Notice the center checkmark stating "root permission granted" is not checked, and there's no option to restore, only to remove or temp unroot, so it's like, everything is good, except for the actual root permission
Root checker shows red (no access) and root programs like root explorer do not prompt for superuser permission before running as I would expect them to the first time.
Did you run superuser? Did you reboot after running su for the first time?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Absolutely, more times than I can count. Here's another shot showing I can't execute such but it seems to have global execute...
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Install supersu and not superuser....update the binary ...then try again
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
pakure said:
Install supersu and not superuser....update the binary ...then try again
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
OK, uninstalled superuser, and installed superSU as you suggested and rebooted the tablet for good measure.
Ran it, and it prompted me, saying su needed updating, said yes do it, came back to me "installation failed", which I honestly expected because for whatever reason, current tablet user cannot get to su, even though it appears permissions said it should.
One other note, earlier I tried to refollow these directions: http://forum.xda-developers.com/showthread.php?t=1704209
That is how I rooted when under build .30, no issues at all. This time I hit a snag when trying to push files to /data/local - said I had no permission. now I got around it via ADB by simply typing su - root....root seems to work when I'm in ADB, but it doesn't work via tablet interface. I don't know what I'm missing here....
Just a thought.. I was considering flashing back to .30 using fastboot but I wasn't sure if that would even work. I tried loading the .30 zip into the root of storage and it detected it, as a downgrade even and asked to proceed. When done I was still on 4.1.1 not the older build.
BTW, thank you for taking the time. I really don't mean to be a pain here. I've not had this much trouble before...
Well sh++ This would explain why I couldn't redo the debugfs root process...
http://forum.xda-developers.com/showthread.php?p=27990303
I decided to go have a look at the nexus 7 area since that's native JB and saw that. So' for those just buying this, you might want to root before you update.
Still doesn't explain my problem but at least explains why I can't use the solution that WAS good.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
Well sh++ This would explain why I couldn't redo the debugfs root process...
http://forum.xda-developers.com/showthread.php?p=27990303
I decided to go have a look at the nexus 7 area since that's native JB and saw that. So' for those just buying this, you might want to root before you update.
Still doesn't explain my problem but at least explains why I can't use the solution that WAS good.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I was able to restore my root. See this post.
http://forum.xda-developers.com/showthread.php?p=30481502#post30481502
I've really messed up now. Set perms wrong for the such that was on the tablet so now can't get root using adb either so unless there is a way to downgrade without root I'm screwed.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I was so amped to grab JB, that I spaced that the OTA update would break root (i'm rooted but locked bootloader, b/c i was hoping 4.1.1 would come sooner than later!)
I had OTA rootkeeper installed, and while I was a little skeptical as to how easily it would work, it was 1-click simple and I just had to reinstall/update the binaries and reboot. I had the same check mark unchecked, but it worked, was straightforward, etc. It sounds like something got jacked in the JB flash, and I wonder if a full wipe/reset (&downgrade) to 4.04, re-root, then OTA update (using ota rootkeeper to hold root) might work for you?
thesuzukimethod said:
I was so amped to grab JB, that I spaced that the OTA update would break root (i'm rooted but locked bootloader, b/c i was hoping 4.1.1 would come sooner than later!)
I had OTA rootkeeper installed, and while I was a little skeptical as to how easily it would work, it was 1-click simple and I just had to reinstall/update the binaries and reboot. I had the same check mark unchecked, but it worked, was straightforward, etc. It sounds like something got jacked in the JB flash, and I wonder if a full wipe/reset (&downgrade) to 4.04, re-root, then OTA update (using ota rootkeeper to hold root) might work for you?
Click to expand...
Click to collapse
I would love to try the downgrade approach as that's the only one left I haven't tried, primarily because I have tried and haven't found a way to do it. If you know how with a locked boot loader then I'd love to hear.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
I would love to try the downgrade approach as that's the only one left I haven't tried, primarily because I have tried and haven't found a way to do it. If you know how with a locked boot loader then I'd love to hear.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
sorry, above my pay-grade at this point. I think i was overly optimistic about the "open-ness" of the device/bootloader (my other device is a galaxy nexus, so it's easy to do just about anything). I had a factory wipe or flash/img restore in my mind, but factory wipe wouldnt help (dont thinK), and If a stock 4.04 img exists, pretty sure there is a command set in fastboot that would let you restore using that image, but also pretty (99%) sure that requires an unlocked bootloader.
It sounds like there were a few changes in folder structure in JB that are limiting the root-ability, but my guess is the brainy folks around here will figure that out pretty quick, and JB will be root-able soon.
thesuzukimethod said:
sorry, above my pay-grade at this point. I think i was overly optimistic about the "open-ness" of the device/bootloader (my other device is a galaxy nexus, so it's easy to do just about anything). I had a factory wipe or flash/img restore in my mind, but factory wipe wouldnt help (dont thinK), and If a stock 4.04 img exists, pretty sure there is a command set in fastboot that would let you restore using that image, but also pretty (99%) sure that requires an unlocked bootloader.
It sounds like there were a few changes in folder structure in JB that are limiting the root-ability, but my guess is the brainy folks around here will figure that out pretty quick, and JB will be root-able soon.
Click to expand...
Click to collapse
Yes it's the /data folder where the exploit was and is causing the issue. I saw one of the commands was flash all, but I was too scared to try that. I tried the update.zip approach, but it came back with needed files weren't present in the archive.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
I would love to try the downgrade approach as that's the only one left I haven't tried, primarily because I have tried and haven't found a way to do it. If you know how with a locked boot loader then I'd love to hear.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
What did you do exactly? Details!
You can try this.... It may work... The worst case is that it just doesn't work. I have not seen a confirmation yet as to whether this method works or not yet.
https://www.dropbox.com/sh/jcpilpgoeta516e/QTl4TihVq0/Rooting-the-tf300.txt
---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------
calisro said:
What did you do exactly? Details!
You can try this.... It may work... The worst case is that it just doesn't work. I have not seen a confirmation yet as to whether this method works or not yet.
https://www.dropbox.com/sh/jcpilpgoeta516e/QTl4TihVq0/Rooting-the-tf300.txt
Click to expand...
Click to collapse
Oops. This is the whole link. Sorry about that. directions are in there.
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
---------- Post added at 03:11 PM ---------- Previous post was at 03:09 PM ----------
thesuzukimethod said:
I was so amped to grab JB, that I spaced that the OTA update would break root (i'm rooted but locked bootloader, b/c i was hoping 4.1.1 would come sooner than later!)
I had OTA rootkeeper installed, and while I was a little skeptical as to how easily it would work, it was 1-click simple and I just had to reinstall/update the binaries and reboot. I had the same check mark unchecked, but it worked, was straightforward, etc. It sounds like something got jacked in the JB flash, and I wonder if a full wipe/reset (&downgrade) to 4.04, re-root, then OTA update (using ota rootkeeper to hold root) might work for you?
Click to expand...
Click to collapse
If you have a check mark unchecked, you likely have root issues. Which check box?
calisro said:
If you have a check mark unchecked, you likely have root issues. Which check box?
Click to expand...
Click to collapse
Sorry - imprecise language on my part.
When I opened up OTA rootkeeper, it showed the same unchecked box (in rootkeeper) as others have mentioned, but I had "restore root" as an option. I did, and had no problems keeping root after updating to JB 4.1.1. OTA. I was using superuser but had checked "OTA survival" in Superuser's options, so I think that's how i kept root (seems like this "survival" option is baked in to Super Su, but a (non-default) option in Superuser).
Looking for input from anyone who has had experience with a Rooted TF300T with a "Locked" Bootloader Running "Official OTA Jellybean".My TF300T is Rooted with the Locked Bootloader and OTA Jellybean, Question is If a Factory Data Reset is Preformed will Root Remain or Be Lost ? I know from Past Experiences with my Acer A100 that after a Factory Data Reset Root is Retained. Any Input will be Greatly Appreciated.
Izzyb914 said:
Looking for input from anyone who has had experience with a Rooted TF300T with a "Locked" Bootloader Running "Official OTA Jellybean".My TF300T is Rooted with the Locked Bootloader and OTA Jellybean, Question is If a Factory Data Reset is Preformed will Root Remain or Be Lost ? I know from Past Experiences with my Acer A100 that after a Factory Data Reset Root is Retained. Any Input will be Greatly Appreciated.
Click to expand...
Click to collapse
You might get mixed answers, but I can tell you I did exactly that, same circumstances at the time, and I ended up being half-rooted. I could get root access via adb and ota root keeper said it was installed, but it also said I did not have root permissions, and apps could not gain root access no matter what I tried. I consider that a loss of root, so be careful doing that.
As such, I ended up unlocking the bootloader and fully rooting that way.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
You might get mixed answers, but I can tell you I did exactly that, same circumstances at the time, and I ended up being half-rooted. I could get root access via adb and ota root keeper said it was installed, but it also said I did not have root permissions, and apps could not gain root access no matter what I tried. I consider that a loss of root, so be careful doing that.
As such, I ended up unlocking the bootloader and fully rooting that way.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
funnel71 Thank's for the Reply to My Post.It was So Easy to Root My TF300T and Retain Root with the Upgrade to Jellybean that I am a Little Apprehensive about trying the Cold Reboot and Factory Rest in Fear of losing My Root in order to solve a couple of Small Concerns that I am having with certain Apps force closing to the Lock Screen. The UI is Perfect with Jellybean with No Concerns what so ever...Super Fast & Smooth....I think I will just Play it by Ear for Now and let things ride being that there are No other Concerns that this Tablet is experiencing .I was Lucky enough to be able to Purchase my TF300T 16 GB at Best Buy for $249.99 with the Clearance that they had with Overstock of the Blue Model.I have a 30 Day Return on this Bad Boy and sure Hope Not to have to use it.
cold booting won't make you lose root. I did factory reset once on ics and I was able to restore root not sure if it will work on jb. Also try clearing the app's data of the apps that are getting forced closed then cold boot.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
jgaf said:
cold booting won't make you lose root. I did factory reset once on ics and I was able to restore root not sure if it will work on jb. Also try clearing the app's data of the apps that are getting forced closed then cold boot.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
The thing is you were able to easily root because of exploits which were closed by jb - specifically the ability to link the data directory to the /system mount. Since a factory reset wipes the data area, it can break that link, and if on jb, you can't get it back, at least not that way. Only current way is to unlock the bootloader, flash in recovery, and use recovery to flash in the needed components for root. It's not a hard procedure at all, but some don't want to out of fear of bricking or the loss of warranty.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
jgaf said:
cold booting won't make you lose root. I did factory reset once on ics and I was able to restore root not sure if it will work on jb. Also try clearing the app's data of the apps that are getting forced closed then cold boot.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
jgaf Thanks for the reply to my Post.I have had problems with three Apps so far. (1) Astro File Manager: Solved with an Update. (2) OEM Camera while deleting a Photo Taken,Have Not had a Problem sense then.(Strange) (3) Riptide GP Cleared the Data as suggested and Fine So Far.
I Really Think that my Problems are with the Apps and Not Hardware of the TF300T or Software Related to Jellybean (I Hope). Again Thanks for the Input Greatly Appreciated . As Far as Root is Concerned I think the reason you were able to restore it is because you were on ICS and Not Jellybean with a Locked Bootloader.
After each fw update some apps always get wonky, which are almost always fixed by clearing data or cold booting. Sucks that we can't do factory reset on jb and keep root, it's always good to have that option when nothing else seems to work. Hopefully someone will find a way of rooting without having to unlock.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Hello,
Will a Factory Reset remove root? Also, how would you use Voodo to resotre root if it is removed?
jj4201998 said:
Hello,
Will a Factory Reset remove root? Also, how would you use Voodo to resotre root if it is removed?
Click to expand...
Click to collapse
Factory reset will not remove the su binary which is what's used to get root, but if you are on jb, it could break root permission, meaning you'd still have the binary but apps might lose the ability to call it. I like to call that state, half-rooted. In that case even a restore of root via ota root keeper doesn't seem to help. This was not true in all cases.
Bottom line, if you lose it, you can get it back, but to do so for certain, you'll need to unlock the bootloader and flash it in. Again, that's assuming you are on jb. If you are on ICS, a root keeper restore will fix you.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app