[Q] Updated TF700T to OTA .30, no more root - Asus Transformer TF700

Hi there,
I've had root made by debugfs root tool from the the first day. A couple days ago, I updated my TF700T to official .30 version and after that my superuser have denied accesses of all programs, even itself.
Today I tried to reroot it with debugfs root tool. Before that I uninstalled Superuser and wiped all the data of it. The installation went fine without errors and at the end of it, it says you are now rooted. I managed to have superuser rights to superuser, but all other programs ie. TB are automatically denied by SU. Also Rootchecker says that there are no root on my device.
What should I do next? I use SwitchMe for two separate profiles, could it be something causing strange behaviour? I think it does something to partitions. I'm not an expert though I have a little experince from rooting my other devices.
Thank you very much in advance

There is already threads on this. Use the debugs root tool again it works, i played with uninstalling superuser reinstalling it and it worked for me
Sent from my ASUS Transformer Pad TF700T using xda premium

Related

trying to root asus transformer with nachoroot

Hi. I am trying to root an Asus Transformer using Nachoroot. My firmware version is 8.6.5.21.
I am new to both android and using the command line.
I followed a guide, and keyed in all of the commands (shell id was 0), then downloaded Superuser and OTA Rootkeeper.
I notice that in the Rootkeeper app there is no checkmark next to "device rooted" which makes me think my root was not successful.
Does this mean the root is not compatible with my device? Or are there some things I should double check, where I might have gone wrong?
Thanks in advance for your help.
Good news: I went through the same command-line process a second time, and the root took and is now acknowledged by Root Keeper.
But I've encountered a new problem. I would like to use an alternative ROM, but I am unable to enter recovery mode. I get stuck at a screen with a droid and an exclamation mark.
Anyone have any idea what might be causing this problem? Thanks.

[Q] Root/update question

I have done a lot of reading her about rooting and updating my TF300. After getting a headspinning amount of information, I'd like someone to verify what I think I know.
I have a TF300, stock ROM, no root, running US .17. I have not received any updates after going to Settings/about tab/update and pressing the update button (I get "no updates found') I have cleared DM and CM client and rebooted several times, but no updates are found. I have tried on several WiFI networks I have access to.
1. I should be able to root using one of several one click methods I have found here, correct?
2. Once rooted and root keeper is installed, I should be able to update to .29 and keep root, correct?
3. A manual update to US .29, once rooted, will cause me to lose root, correct?
4. Will I receive Over The Air update once rooted? If not, how can I update to US .29 without losing root?
5. Is this the best path to take, or is there another path that would be easier for a newb like me (I know just enough about Android to be dangerous)? What I mean by another path is, should I manually update to US .29 and wait for a one click solution to come out later, all the while enjoying the new update.
6. All this is to fix some lag issues I have with all browsers....Tried Stock, Dolphin, Firefox, Opera...all the same. Some FC and others just hang for up to 30 seconds, even in Performance mode (With only one tab open!) So this will "FIX" those lag issues, correct?
Thank you for your time
If you're still on .17, root with sparkyroot, save it with ota rootkeeper, update to .29 (if it isn't there, they've been posted in many places on the forums), and restore root. As for fixing lag issues, it depends on what you do, rooting alone won't change anything, but you can try out the different tweaks available.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Missed a couple of your questions, yes, you will still receive ota updates if you're rooted, as long as you don't unlock the bootloader. This is the easiest way to root too, all you need to do is follow sparkyroot's instructions and back up your root.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
One question always leads to another
Thank you! But of course, I now have just a few more questions.
I do understand rooting alone will not help me with my lag issues. I'm hoping the update to .29 will. I am not a power user, but I would like the option open to me later to install ROMs, hence why I want to root now.
1. I thought I had to unlock bootloader to root. With sparkyroot I do not?
2. Since I have not unlocked bootloader, will rooting alone void my warranty? I thinking not since I should be able to unroot with no trace, correct?
3. I thought, (or read somewhere here, I think) that if I do a MANUAL install, I would lose root and be unable to regain it. If I get an update PUSHED to me by ASUS, Ill be able to regain root with rootkeeper. Is that correct?
I'd like to thank everyone here, by the way, for all the information I have gotten in my 30 days of owning this tablet and lurking here.
Throb1231 said:
Thank you! But of course, I now have just a few more questions.
I do understand rooting alone will not help me with my lag issues. I'm hoping the update to .29 will. I am not a power user, but I would like the option open to me later to install ROMs, hence why I want to root now.
1. I thought I had to unlock bootloader to root. With sparkyroot I do not?
2. Since I have not unlocked bootloader, will rooting alone void my warranty? I thinking not since I should be able to unroot with no trace, correct?
3. I thought, (or read somewhere here, I think) that if I do a MANUAL install, I would lose root and be unable to regain it. If I get an update PUSHED to me by ASUS, Ill be able to regain root with rootkeeper. Is that correct?
I'd like to thank everyone here, by the way, for all the information I have gotten in my 30 days of owning this tablet and lurking here.
Click to expand...
Click to collapse
No need to unlock for root. They are completely unrelated. Just update manually and use THIS THREAD to root .29. There's even a one-click tool like you wanted. Don't forget to press Thanks for miloj.
Oh, and after you've updated to .29 and rooted; don't forget to use OTA rootkeeper to backup root.
If Asus releases a new update it may save your root.
EndlessDissent said:
No need to unlock for root. They are completely unrelated. Just update manually and use THIS THREAD to root .29. There's even a one-click tool like you wanted. Don't forget to press Thanks for miloj.
Click to expand...
Click to collapse
He's still on the .17 software, so no need to do that. Just use the sparkyroot method, backup with rootkeeper and then update.
Edit to add that no, rooting will not void the warranty, just unroot before you need to send it back.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Yeah, he's still on .17, but he's not getting the OTA prompt. He wants to manually upgrade, and you can't restore root after a manual upgrade, so my advice still stands.
Thank you both! Rooted with Sparky root and backed up with OTA rootsaver. Now I have downloaded the .29 update from ASUS webpage and installed. It says I have lost root.
I tried to restore root with OTA and it says SU restored, however it does not show that I have root access. Tring to use Titanium BU also shows I do not have root.
Tried then to go back to Sparkyroot and try again, but to no avail. Do I now have to downgrade back to .17 to gain root because I messed it up, or is there a solution? I was rooted for several hours before the upgrade to .29.
Throb1231 said:
Thank you both! Rooted with Sparky root and backed up with OTA rootsaver. Now I have downloaded the .29 update from ASUS webpage and installed. It says I have lost root.
I tried to restore root with OTA and it says SU restored, however it does not show that I have root access. Tring to use Titanium BU also shows I do not have root.
Tried then to go back to Sparkyroot and try again, but to no avail. Do I now have to downgrade back to .17 to gain root because I messed it up, or is there a solution? I was rooted for several hours before the upgrade to .29.
Click to expand...
Click to collapse
No, you need to go to:
h tt p://forum.xda-developers.c om/showthread.php?t=1704209 (sorry for the chopped up link. I can't post links yet)
and root again.
EndlessDissent said:
Yeah, he's still on .17, but he's not getting the OTA prompt. He wants to manually upgrade, and you can't restore root after a manual upgrade, so my advice still stands.
Click to expand...
Click to collapse
Ah, ok. Didn't realize you couldn't restore if you updated manually.
Yes, it is as I thought. Tried Sparkys and miloj's root program and I can not get root. I ran the program twice from my lap top. Driver's for TF300 show installed in Device manager (Windows 7). ASUS sync was installed in laptop and recognized TF300 but the program was not running during root attempt.
When I run Superuser and attempt to update SU binaries, I get "Failed" when it attempts pathway to write update.
Attempted to restore using OTA rootkeeper but all I get is "SU Restored". Check boxes indicate no root.
Any other ideas?
Confirmed I am on .29 from a MANUAL update.
Tried again from home computer. Ran Sparky and miloj program. I get error stating
"failed to copy 'Superuser.apk' to '/data/local/tmp/Superuser.apk' : not a directory"
Tablet reboots and says I should be rooted but obviously not. Superuser not written to tablet
Throb1231 said:
Tried again from home computer. Ran Sparky and miloj program. I get error stating
"failed to copy 'Superuser.apk' to '/data/local/tmp/Superuser.apk' : not a directory"
Tablet reboots and says I should be rooted but obviously not. Superuser not written to tablet
Click to expand...
Click to collapse
Can you just install Superuser from the market? The su binaries might be there and the app just isn't installing. I may be wrong, not sure how the automated program works, but it can't hurt.
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Throb1231 said:
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Click to expand...
Click to collapse
Try manually doing the code from miloj's thread?
While the instructions in his thread are clear, they are way past my level of expertise. I would not attempt it without someone standing next to me. I have not entered code since the 1980's Compute! magazine days.
Throb1231 said:
While the instructions in his thread are clear, they are way past my level of expertise. I would not attempt it without someone standing next to me. I have not entered code since the 1980's Compute! magazine days.
Click to expand...
Click to collapse
Well, I can't think of anything else, you could just use the downgrade method, that's easy enough. The code really is just copy/paste though.
Throb1231 said:
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Click to expand...
Click to collapse
Your problem is not with the superuser apk.
The actual root is when you write an "su" binary to system and makes it executable (there is some access control stuff in between, but it's what's happening in essence).
So - your trouble is not with the installation nor the messages from superuser.apk - it's with the actual rooting method.
Make absolutely sure your adb drivers are working and that you've got the files "debugfs", "su" and the other debugfs file on top of the .bat file, which is the installation script, in the same directory whilst running the .bat file.
Agreed. I posted this in development.
It was surprisingly more difficult to install the drivers correctly than anticipated.
For those noobs like me, here's a step-by-step for installing the drivers before running the root method.
http://transformerprimeroot.com/tra...all-transformer-prime-usb-drivers-on-windows/
Please note that before using the step-by-step guide above, I also had to put the tf300 in Camera Mount to even get the "“ASUS Android Composite ADB Interface" option to show up in Device Manager.
Once you get this far, you can manually update the driver (found in the sparkym3 "Drivers" folder from the download) via the step-by-step.
Sent from my ASUS Transformer Pad TF300T using XDA

[Q] Next steps on ICS TF300 - Just rooted and still locked

(FYI, this is my first android device so i'm a noob to this world, but I have some experience in the iphone jbreaking)
SITUATION: Ok, so I picked up a TF300 US model, with ICS 9.4.3.17 on it. Reading up all over the forums for help and did the following: used sparky's guide and used the Sparkyroot.apk tool, along with Superused.apk and VoodooOTArootkeeper, and it worked great! Thanks to the "Allaboutandroids dotcom" youtube user guide.
My plan is to stay on stock OS. I do NOT want to unlock. (keep warranty and such)
I'm into retro gaming mostly and I don't think I need custom ROMS to enjoy most apps. I would like to moderately overclock the CPU, if that's available without unlocking.
THREE QUESTIONS:
1. So i'm reading that to do the future updates and eventually JBean, that I need to let it do the OTA (that's the tablet requesting to update without me manually selecting it right?) and I will lose root, but SHOULD be able to restore it, without unlocking correct?
2. HOW/WHERE is my root backed up to and how can I extract it to my PC, in case I need to copy it back over after an update. (I have a microsd card in the tf300 as well)
3. Before I do an OTA update, should I do anything?
4. Can I somehow just jump to the latest JB update, or does the tablet need to do incremental updates starting with 9.4.3.18 (or whatever is after .17)
Thanks again for any advice forum people. Regarding question 3. I hear people saying I need to do stuff in Voodoo AND/OR install SuperSU. (Not just Superuser.apk
Great forum and helped my decision to get one of these. Just hoping now I can get my wife to stop nagging me for not getting a 2.5X as $$$ iPad! (under $250 for NEW TF300 16gb. Yay!)
So just as an update, I ran root checker and everything is good and in green. I have superuser installed but NOT SuperSU (I guess it's one or the other but not both, and i'm not sure what the difference is between them)
But when I go to update superuser binaries, it fails at the first step (downloading manifest) every time. I have shut down/restarted so that's not it.
I also ran superuser update fixer 1.2, and it says that everything is fine.
I read that binaries should be updated before allowing an OS update so any thoughts on next steps? The goal is to get jellybean up and running and NOT permanently lose my root. (while still keeping the bootloader unlocked, which it currently is)
I've hooked it up via usb to laptop and gone to the googleplay store and found superuser (in case I had a old version) but it always states "This application is not compatible with your TF300 device" and refuses to install it that way. Could try hunting on the net for a loose .apk version of it, if that's what I need.
Thanks!
Just get supersu (a lot more reliable than superuser) and run it right after installing, it will update the binaries. Then make sure your root is backed up with ota rootkeeper. Once you have done those things you can update through the notification on the pad. I'm not sure if the updates are incremental, but they might be, so just in case between each update restore root with ota rootkeeper run supersu and reboot before going to next update, also always make sure your root is backed up. Good luck, once you are on jb there's no way on getting rooted without unlocking as of yet, so I repeat myself make sure your root is backed up wit ota rootkeeper and you have supersu before updating.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
jgaf said:
Just get supersu (a lot more reliable than superuser) and run it right after installing, it will update the binaries. Then make sure your root is backed up with ota rootkeeper. Once you have done those things you can update through the notification on the pad. I'm not sure if the updates are incremental, but they might be, so just in case between each update restore root with ota rootkeeper run supersu and reboot before going to next update, also always make sure your root is backed up.
Click to expand...
Click to collapse
Thanks jgaf for the help!
So when I do the "backup" with rootkeeper, it's actually 'saving' the root but temporarily turning it off right? And doing an update doesn't wipe my device, so rootkeeper SHOULD be there correct? So to do a system update (when I click on the bottom right and see the brightness adjust and enable wifi, etc, there is a message saying a system update is available. That is the OTA update correct? Before I do that, I need to run rootkeeper and click the "temp save root", and it basically turns off root access but saves it from being wiped off with the new update right?
I've read that some people say to activate some optional "prevent root loss due to update" feature on Superuser. Does supersu have/need that?
And last, if I switch from Superuser to SuperSU, how do I safely switch over? Do I delete Superuser, and then download/install superSU, or install both on the device and then do some kinda remove or update?
I read that by doing the update methods you decscibed, I can basically keep my root on jellybean without being unlocked. (but it's tricky and some users lose the root regardless) Guess there's not one 100% "rooted and locked" foolproof method yet.
So far this method is working but i've only had one OTA update offered and that bumped it from .17 - .30. So that's not JellyBean yet. Hopefully the rootkeeper and supersu reapplying method will continue to work like this. Thanks!
You don't really need to temp unroot for updates, just make sure that everything is checked in rootkeeper. Sorry I took so long to answer, but those switching from superuser to supersu you need to install supersu and run it before removing superuser.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

[Q] Need help with rooting off brand tablet

I have a Linsay F-10xhd tab and have been searching everywhere on the net for a way to root this device. I have tried every 1 click method out there and they weren't able to root it. If anyone here has rooted a Linsay device can you point me in the right direction. I have a bunch of preloaded apps I would love to get rid of.
Didi some digging
And read that my drivers were not working properly with Vroot and Kingroot. So I uninstalled my drivers for this device and reinstalled then using PDA.net. Then I ran it through Vroot. After it did its thing it said it was successful rooted. Checked with root checker from playstore and it said it wasn't rooted
So I tried it again with kingroot but when it was finished connecting it said it was rooted and if I wanted to "unroot" or "root again"
That's as far as I've gotten. I didn't want to go further for fear of bricking my tablet.
I also downloaded Supersu, Busybox, and twrp and wasn't able to do anything cause they also said the device wasn't rooted. Anybody know why Vroot and Kingroot would say I'm rooted but these other apps are saying otherwise?
After days of trying to get this thing rooted, I figured out what went wrong. I deleted the kinguser app that comes with Kingroot when rooting. I downloaded the kinguser apk, installed it and got root permission!
So if you have a Linsay F-10XHD tablet, you have to use the kingroot method to root it. I'm still debating if I should replace kinguser with supersu. Don't see any real difference between the two. I might just keep kinguser
Sent from my F-10XHD using XDA Free mobile app
Hope this method works for me just got tablet for free today going to try later hope I don't run into issues now
Kingroot worked beautifully no problems here

Help! Lost Root??

Hi all,
I am having problems with my phone and its starting to drive me crazy. I have a ZTE N817 (Obama phone) which I rooted and flashed TWRP to about 8 months ago. The rom is stock because I've never been able to find any custom roms. I used the kingoroot PC application to root the device (the app I've found that was able to root it), and replaced kinguser with supersu. Everything worked great, or at least as good as one can expect from a device with such lown spec hardware.
About a week ago I opened my busybox installer (Busybox Pro (Stericson) and I noticed the app said either I didn't have root or I needed to update the supersu binary. I had the most recent supersu binary but I reinstalled it and updated the binary anyway. The binary updated fine. Busybox still said I didnt have root. I then down loaded a root checker app from the store, it said I had root and my busybox installation was fine. I opened a few more apps that require root (titanium backup, root explorer, etc) all said the device was not rooted. I installed a couple more root checkers, both said the device was not rooted but one said busybox was installed and the other said it wasnt. The first root checker app still said the phone was rooted and busybox installed.
Whenever I run an app that requires root, I get the popup from supersu asking me to grant root access. I grant it but then the apps just tell me that they are unable to get root access and my device is not rooted. I reinstalled kingoroot on my PC and ran it to root the phone again. It said it ran successfully, supersu installed fine and updated the binary. Still no change in anything. I tried to use kingoroot to unroot the device (just so I could root it again) but kingoroot was unsuccessful, but it says it has no problems rooting it.
At this point I have no idea what is going on or how I can get root access back. Any help or ideas anyone may have will be greatly appreciated.:highfive: Like I said, its seriously starting to drive me nuts. :crying::crying:
Happy Memorial Day to everyone!
jritt said:
Hi all,
I am having problems with my phone and its starting to drive me crazy. I have a ZTE N817 (Obama phone) which I rooted and flashed TWRP to about 8 months ago. The rom is stock because I've never been able to find any custom roms. I used the kingoroot PC application to root the device (the app I've found that was able to root it), and replaced kinguser with supersu. Everything worked great, or at least as good as one can expect from a device with such lown spec hardware.
About a week ago I opened my busybox installer (Busybox Pro (Stericson) and I noticed the app said either I didn't have root or I needed to update the supersu binary. I had the most recent supersu binary but I reinstalled it and updated the binary anyway. The binary updated fine. Busybox still said I didnt have root. I then down loaded a root checker app from the store, it said I had root and my busybox installation was fine. I opened a few more apps that require root (titanium backup, root explorer, etc) all said the device was not rooted. I installed a couple more root checkers, both said the device was not rooted but one said busybox was installed and the other said it wasnt. The first root checker app still said the phone was rooted and busybox installed.
Whenever I run an app that requires root, I get the popup from supersu asking me to grant root access. I grant it but then the apps just tell me that they are unable to get root access and my device is not rooted. I reinstalled kingoroot on my PC and ran it to root the phone again. It said it ran successfully, supersu installed fine and updated the binary. Still no change in anything. I tried to use kingoroot to unroot the device (just so I could root it again) but kingoroot was unsuccessful, but it says it has no problems rooting it.
At this point I have no idea what is going on or how I can get root access back. Any help or ideas anyone may have will be greatly appreciated.:highfive: Like I said, its seriously starting to drive me nuts. :crying::crying:
Happy Memorial Day to everyone!
Click to expand...
Click to collapse
you have twrp still?
install latest supersu.zip
Sent from my XT1096 using Tapatalk
sd_shadow said:
you have twrp still?
install latest supersu.zip
Sent from my XT1096 using Tapatalk
Click to expand...
Click to collapse
Yes, I still have TWRP. If I install supersu from the play store without the binary installed the app will tell me immediately after opening that my device is not rooted and it won't work. If I flash the binary through TWRP first, then supersu installs from the play store no different than if the device was still rooted, but I still don't have root. I get the toast notifications whenever an app requests access, but of course it is unable to grant it. I am still on the exact same version of Android as when I got the phone, nothing other than apps themselves have been updated. I have zero idea how I lost root, and even more confusing to me is why I cannot reacquire it. Again just last night, I tried Kingoroot (what I originally rooted the device with), Dr Fone, iRoot, eRoot and Framaroot. Every one failed.:crying: It's a real pain in the rear because the phone's hardware is so lacking that root access is needed just to make the device somewhat usable. I have not ever been able to find a custom rom despite searching all over many times. But last night I was thinking, since I stil have TWRP if I can find someone else with the same handset with root....could I flash a backup of their stock rom? Would that work?:fingers-crossed: I'm becoming extremely frustrated
jritt said:
Yes, I still have TWRP. If I install supersu from the play store without the binary installed the app will tell me immediately after opening that my device is not rooted and it won't work. If I flash the binary through TWRP first, then supersu installs from the play store no different than if the device was still rooted, but I still don't have root. I get the toast notifications whenever an app requests access, but of course it is unable to grant it. I am still on the exact same version of Android as when I got the phone, nothing other than apps themselves have been updated. I have zero idea how I lost root, and even more confusing to me is why I cannot reacquire it. Again just last night, I tried Kingoroot (what I originally rooted the device with), Dr Fone, iRoot, eRoot and Framaroot. Every one failed.:crying: It's a real pain in the rear because the phone's hardware is so lacking that root access is needed just to make the device somewhat usable. I have not ever been able to find a custom rom despite searching all over many times. But last night I was thinking, since I stil have TWRP if I can find someone else with the same handset with root....could I flash a backup of their stock rom? Would that work?:fingers-crossed: I'm becoming extremely frustrated
Click to expand...
Click to collapse
which Supersu.zip zip are you using?
Sent from my XT1254 using Tapatalk
sd_shadow said:
which Supersu.zip zip are you using?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
The one I used last night was SR3-SuperSU-v2.79-SR3-20170114223742.zip.
jritt said:
The one I used last night was SR3-SuperSU-v2.79-SR3-20170114223742.zip.
Click to expand...
Click to collapse
Here are some things to check.
Maybe you need to make sure you have root access in developer options set to "apps and adb".
Make sure you have a root explorer and that it is enabled.
Check SELinux to see if it's set to "enforcing" or "permissive", set it to permissive if you can.
You might need to use SuperSU in "systemless mode"
Yes, in theory, a rooted backup from someone else should work.
Sent from my SM-S903VL using Tapatalk

Categories

Resources