[Q] Root/update question

[Throb1231]

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

 

[prototype7]

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

 

[prototype7]

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

 

[Throb1231]

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.

 

[EndlessDissent]

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.

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.

 

[gasingvar]

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.

 

[prototype7]

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.

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

 

[EndlessDissent]

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.

 

[Throb1231]

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.

 

[/dev/void]

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.

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.

 

[prototype7]

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.

Ah, ok. Didn't realize you couldn't restore if you updated manually.

 

[Throb1231]

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.

 

[Throb1231]

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

 

[prototype7]

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

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.

 

[Throb1231]

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

 

[prototype7]

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

Try manually doing the code from miloj's thread?

 

[Throb1231]

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.

 

[prototype7]

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.

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.

 

[/dev/void]

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

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.

 

[Science Ninja]

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