Related
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
I am a complete noob with this stuff. So i wanted to root but i read that i had to downgrade my firmware to do it. So i do some sbf-ing with rsdlite 5.7 and it says that it PASSed but on my phone it had an error and wouldnt let me leave bootloader. so i did a ton of research to fix it and i end up getting it to work.. im not sure of it downgraded but im just happy that the phonee turned on. I rooted it with superoneclick and it was a success. after i rooted it i realized that my wifi wasnt working so i wiped all my data and everything and unrooted it and it still wouldnt work. I have verizon fios and it is secured with WEP. i tried other wifi networks and i wasnt able to connect to any of them. it would just say obtaining ip address and then it wud disconnect and scan for other wifi networks and that would keep repeating. I have no idea what is going on and did research for over 24 hours and still cant find the solution. My phone is not activated so i cant call or text or use 3g data. My system version is 4.5.608.A956.Verizon.en.US and my android version is 2.3.3. PLEASE HELP I CANT FIGURE THIS OUT! Thanks in advance
SOMEONE PLEASE REPLY I REALLY NEED TO FIX IT
:crying:
Your problem is that you are still on Android 2.3.3
You have to take the OTA update in order to get WIFI working again.
If you already have root, you can install Voodoo OTA rootkeeper (look for it in the play store, there is an alternate download link there). After installing rootkeeper, you can open it and protect root, then temp unroot.
After that, you need to get the OTA update, and put the zip file on your SD card, and install it from recovery.
Then, restore root with Rootkeeper.
All those files should be available at
http://forum.xda-developers.com/showthread.php?t=1660713
Or, an alternate option is to flash back to Android 2.3.4, and use the direct root method now available.
A combined SBF and Root CD is at
http://forum.xda-developers.com/showthread.php?t=1701862
Or there is a Root only CD there, for if you are on 2.3.4
Thanks SOOO much.. Im going to try it out right now with the first option you gave me and post the results later tonight
the ota rootkeeper app doesnt say temp unroot.. do i use the superoneclick to unroot it.. im not sure if temp unrooting is the same as unrooting? im sorry im just new to android
Rootkeeper doesn't root, just saves a copy of the files.
So, you need to root with super1click, then protect root with rootkeeper.
Then temp unroot, and update in recovery
Sent from my DROID3 using Tapatalk 2
nvm i figured it out. I just unrooted with superoneclick, rerooted again, and then temp unroot showed up.
SWEET after i rebooted (from installing 629 OTA) i restored root and checked if the wifi worked and it did! THANKS SO MUCH! i literally tried for a couple of days to do this. never going to miss with this phone again.. ahaha thanks a ton!
You are welcome, glad you got it back up and working.
Hi;
Had the same problem, with the same specs.
Did as you advised' and have WiFi working!
Thanks loads for your kind input!!
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
bhigham said:
Your problem is that you are still on Android 2.3.3
You have to take the OTA update in order to get WIFI working again.
If you already have root, you can install Voodoo OTA rootkeeper (look for it in the play store, there is an alternate download link there). After installing rootkeeper, you can open it and protect root, then temp unroot.
After that, you need to get the OTA update, and put the zip file on your SD card, and install it from recovery.
Then, restore root with Rootkeeper.
All those files should be available at
http://forum.xda-developers.com/showthread.php?t=1660713
Or, an alternate option is to flash back to Android 2.3.4, and use the direct root method now available.
A combined SBF and Root CD is at
http://forum.xda-developers.com/showthread.php?t=1701862
Or there is a Root only CD there, for if you are on 2.3.4
Click to expand...
Click to collapse
2.3.4/4.5.629 is directly rootable now
Magic MD5 Root 2.3.4 for D2, R2D2, D2G, DX and 2.3.5 for DX2
Hi,
I found out that asus made new update for our tf300t (i didnt get any info on device). Its. 17, I still had .9. Maybe its coz root but i didnt change anything in /system (only ad hosts via adblock).
So my device dont find any updates (network error or server busy, always, yes...). I know that there is manual update. But here comes a question: what with root? Ive never update it manually only ota, so will i lose root or is there possibility to brock device (coz root not failed update)?
My tf300t is locked and rooted. I dont want to brick it coz it is usefull on lessons.
Thx for answers
PS. Maybe there is no need to update?
Sent using tf300t - stock JellyBean (rooted)
i dont like waiting so i dl blop, make manually update and... its updated but no root, i wasnt ota so no rootkeeper...
But i think that if someone with jelly bean could give me his/her rootkeeper files i could copy it using adb with root rights and restore via rootkeeper? Is it really possible or im only dreaming?
So if someone could upload form his rootkeeper folder and write here the path to it (i dont remember where it should be) and the permission for files i will be really happy.
Sent using tf300t - stock JellyBean (nonrooted )
Apologize in advance if this is intuitively obvious to other but after searching and reading a better part of the day, I can't figure it out...
In any case...I rooted my 4.1.2 phone a while back with the casual root. Didn't unlock the bootloader or install a custom recovery, just rooted. So that puts busybox and supersu on my phone. Later on, I installed a custom sound thing to get some decent volume out of this thing.
Now I tried taking the OTA and it failed. I thought it would just wipe out the root stuff and be on it's merry way (like other devices I've had in the past). So, I used the one touch unroot in SuperSu and tried again. Still failed. And it still showed me busybox in the app drawer.
So, here's my question...
Do I need to remove my custom volume thing as well as do the unroot?
And do I need to uninstall busybox before doing the unroot via supersu? Or do i just go to the apps and install it there after the SuperSu unroot?
And, if none of those work right, do I fall back to flashing 4.1.2 directly - or maybe better to flash 4.3 directly? I plan on using saferoot once I'm up to 4.3.
If anyone can help me sort this out, I'd greatly appreciate it. I'm rerooted for the moment.
Thanks!
doncaruana said:
Apologize in advance if this is intuitively obvious to other but after searching and reading a better part of the day, I can't figure it out...
In any case...I rooted my 4.1.2 phone a while back with the casual root. Didn't unlock the bootloader or install a custom recovery, just rooted. So that puts busybox and supersu on my phone. Later on, I installed a custom sound thing to get some decent volume out of this thing.
Now I tried taking the OTA and it failed. I thought it would just wipe out the root stuff and be on it's merry way (like other devices I've had in the past). So, I used the one touch unroot in SuperSu and tried again. Still failed. And it still showed me busybox in the app drawer.
So, here's my question...
Do I need to remove my custom volume thing as well as do the unroot?
And do I need to uninstall busybox before doing the unroot via supersu? Or do i just go to the apps and install it there after the SuperSu unroot?
And, if none of those work right, do I fall back to flashing 4.1.2 directly - or maybe better to flash 4.3 directly? I plan on using saferoot once I'm up to 4.3.
If anyone can help me sort this out, I'd greatly appreciate it. I'm rerooted for the moment.
Thanks!
Click to expand...
Click to collapse
OTA will look for any rooted app and fail so you best bet is just Odin the full 4.3 then root with saferoot. This is you also have a nice clean install.
buhohitr said:
OTA will look for any rooted app and fail so you best bet is just Odin the full 4.3 then root with saferoot. This is you also have a nice clean install.
Click to expand...
Click to collapse
Thanks!
Been a looong time since I messed with Odin...this will just be firmware - no data or store apps will be touched, right?
doncaruana said:
Thanks!
Been a looong time since I messed with Odin...this will just be firmware - no data or store apps will be touched, right?
Click to expand...
Click to collapse
Sorry but flashing the full firmware will wipe everything bring it back to factory stock phone, so you need to backup all your stuff.
Well, just to share with everyone, I did not flash back to stock. For a number of reasons, that wasn't really an option.
My first step was removing viper4android. That actually got rid of the "custom" screen with the open lock on boot.
Then I uninstalled busybox from within itself. Unfortunately, as noted elsewhere, that leaves several hundred symlinks in xbin, so I removed all of those (I was only left with dexdump and su there). After that, I actually uninstalled busybox via the app manager.
Then I used the unroot option in supersu to clean up the rest and remove it.
At this point, I should be completely unrooted, but still got the 402 error when failing to upgrade with the OTA.
So...I plugged the phone in and ran the software upgrade assistant that shows up on the "CD" that presents itself from the phone when you plug it in to USB to the computer. And, actually, that successfully completed the upgrade to 4.3!
Haven't embarked on re-rooting yet (using saferoot) but that's the plan at least.
New to the droid maxx, not to rooting. Previous phone was a droid RAZR maxx xt912 that was rooted. I am currently on the 12.7.7 update and have rooted using pwnmymoto. Where do I go from there? I have done some searching and I currently have the camera update waiting for install. I understand I need to unroot before taking OTAs to prevent boot loops. Id like to update fully and retain root but I am not sure where to go from where I'm at. Also is the kit Kat an official update? Is there a voodoo ota rootkeeper type app I gotta install to retain root?
rboutin2 said:
New to the droid maxx, not to rooting. Previous phone was a droid RAZR maxx xt912 that was rooted. I am currently on the 12.7.7 update and have rooted using pwnmymoto. Where do I go from there? I have done some searching and I currently have the camera update waiting for install. I understand I need to unroot before taking OTAs to prevent boot loops. Id like to update fully and retain root but I am not sure where to go from where I'm at. Also is the kit Kat an official update? Is there a voodoo ota rootkeeper type app I gotta install to retain root?
Click to expand...
Click to collapse
see HERE and HERE
read them carefully and you shouldn't have issues. Basically:
1) Root
2)Unlock boot loader
3)reflash camera 4.2.2 camera update (losing root)
4) SlapMyMoto (prep root pre 4.4 update)
5)take or install 4.4 update
6)SlapMyMoto (finalize root).
be sure all steps 1-4 work properly because there is no going back after step 5.
jkhouw1 said:
see HERE and HERE
read them carefully and you shouldn't have issues. Basically:
1) Root
2)Unlock boot loader
3)reflash camera 4.2.2 camera update (losing root)
4) SlapMyMoto (prep root pre 4.4 update)
5)take or install 4.4 update
6)SlapMyMoto (finalize root).
be sure all steps 1-4 work properly because there is no going back after step 5.
Click to expand...
Click to collapse
Thank you for pointing me in the right direction! If in the future I ever need to wipe my phone while on kitkat, I'd there a root exploit in the works for kitkat yet? I don't want to have to wipe my phone in the future an lose my root. Also I keep reading about system/write access an only accessing it in recovery. I mostly root to run titanium backup to backup and restore my app data and I also use root for an ad blocker cud I hate ads in YouTube on mobile. Is the system/write access going to interfere with either of those? And one last question; what is the best way to get tethering to work. On my RAZR maxx I used to use the entitlement check hack.
if you do a factory reset you won't loose root. If you do a FXZ or full system restore on kitkat you WILL loose root with no way to get it back.
System/write doesn't interfere with anything.
tether entitlement hack doesn't work in KitKat - use this method
jkhouw1 said:
if you do a factory reset you won't loose root. If you do a FXZ or full system restore on kitkat you WILL loose root with no way to get it back.
System/write doesn't interfere with anything.
tether entitlement hack doesn't work in KitKat - use this method
Click to expand...
Click to collapse
Thanks a million again! Sorry for being such a pain. One more question: i d like to take advantage of features I didn't have before, like Google wallet. Is it possible for tap to pay to work on kitkat now? Everything I've read doesn't give a perfectly clear yes or no answer.
Okay, so I got all the downloads I need to start. Before I go any further, I just wanna be clear of the process:
1. Use rsd lite to flash my Maxx to the 12.15.15 OTA update.
2. Now that I am bone stock, no root, I then follow the directions in this link: http://forum.xda-developers.com/showpost.php?p=49477129&postcount=320[Linky
3. copy the 4.4 ota update.zip file onto the root of the storage, and then reboot the phone, and let it take the 4.4 update, and then i will be fully rooted on 4.4 no issues right?
EDIT:
When I try to flash 4.2.2 12.15.15 in rsdlite 6.1.4 and 6.1.5, it fails instantly, deleted the getvar line from the xml and now it fails at gpt.bin
edit 2: nevermind. figured it out. if anyone else has this problem, when you delete the getvar line, make sure the next line that takes it's place doesnt have any spaces before the < (it will line up with the rest of the < lines.)
I didn't see that you said you had removed write protection. Be SURE THAT YOU HAVE before going any further. Be sure to use slapmymoto BEFORE taking OTA and that it ran with no errors issues.
jkhouw1 said:
I didn't see that you said you had removed write protection. Be SURE THAT YOU HAVE before going any further. Be sure to use slapmymoto BEFORE taking OTA and that it ran with no errors issues.
Click to expand...
Click to collapse
I have had a lot of issues today. i am finally on the right track to getting updated. I had to run the rockmymoto with all the telnet stuff (ended up using puttytel cuz i had problems with impactor) and then had it fail the first time i tried to run MotoWpNoMo (i think i took too long to hit grant superuser access) ran MotowpnoMo again, and it worked, after running adb command, I am now showing 0. I just finished rebooting my phone after running rsd lite again with 12.15.15. About to run slapmymoto and update to 4.4
SUCCESS!! I am now rooted on 4.4! Thanks a ton for all the help you gave! I'll be sure to help others if they are encountering some of the same problems as I was,
jkhouw1 said:
see HERE and HERE
read them carefully and you shouldn't have issues. Basically:
1) Root
2)Unlock boot loader
3)reflash camera 4.2.2 camera update (losing root)
4) SlapMyMoto (prep root pre 4.4 update)
5)take or install 4.4 update
6)SlapMyMoto (finalize root).
be sure all steps 1-4 work properly because there is no going back after step 5.
Click to expand...
Click to collapse
so so far if I have not gain write protection bypass at 4.2.2 and updated to 4.4, there is no way to root my device yet right?
BlueEditionE6 said:
so so far if I have not gain write protection bypass at 4.2.2 and updated to 4.4, there is no way to root my device yet right?
Click to expand...
Click to collapse
I have just freshly rooted mine, and from what I have learned, no. You cannot. You have to bypass the write protection BEFORE updating to 4.4. You root 4.2.2, (12.15.15) bypass the write protection, then reflash 4.2.2 (12.15.15) the write protection stays bypassed, then you run some commands, update ota to kitkat, then run some adb shell commands, and you're rooted.
One last question: I am getting evrything reinstalled on my new Droid Maxx. I like a clean storage, so can i delete the following off the storage without affecting my root?:
.adobepassdb2
.adobepassdb_2-journal
classes.dex
install.sh
install-recovery.sh
SlapMyMoto.jar
su