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
Dear friends,
as i have been hanging out in this forum, i have learnt a lot. But still, i cannot understand the attitude why people treat, reply or explain everything in a way that assumes all of us are android experts.
TF700 is my first android device(have been using Apple before) so I really need to improve-or create- fundamental knowledge. Just for your information, replying messages like; "ok now Unlock the Root system instead OTA .21 and blablablabla?" (btw. i am well aware of the fact that this sentence is totally meaningless)
Whatever, my point is it would be wonderful to have a fundamental knowledge thread, also keeping your great posts too at the same time.
Cheers!!
archonur said:
Dear friends,
as i have been hanging out in this forum, i have learnt a lot. But still, i cannot understand the attitude why people treat, reply or explain everything in a way that assumes all of us are android experts.
TF700 is my first android device(have been using Apple before) so I really need to improve-or create- fundamental knowledge. Just for your information, replying messages like; "ok now Unlock the Root system instead OTA .21 and blablablabla?" (btw. i am well aware of the fact that this sentence is totally meaningless)
Whatever, my point is it would be wonderful to have a fundamental knowledge thread, also keeping your great posts too at the same time.
Cheers!!
Click to expand...
Click to collapse
I am a newbie too -- bought the tf101 a couple of months ago - loved it -- told my husband he could have it - I was buying the 700 ! and was lucky enough to be able to order one (we live in Canada..... Tiger Direct.ca had them)
I have learned a lot from this forum -- glad I found it --- but I won't be "unlocking" anything ! the only thing I know how to "root" are my house plants !!! lol !! we don't even own smart phones yet -- we still have dumb phones !!! but I have my TF700 !!!
You mean sth like this?
seems hard, but it's not.
It seems tough in the beginning for noob, but actually you're going to get it. You should read the "Index" pointing out by d14b0ll0s to gain some basic knowledge and familiar with the terminology then you should be fine. Couple key words I want to point out that you should know. Currently TF700 came with a locked boot loader, meaning you not able to flash (install) custom firmware from our developers. This is a biggest issue at the moment. Sure there're workaround but it's a pain in the as...and unstable(could brick your pad if you not doing it right). When you see numbers like 21,22,26, they are firmware version number. The latest should be 26. OTA stands for "over the air" and we referred to firmware push to our pad by Asus, not manually download and install ourselves. Rooted is a process that you gain access as a administrator on your pad (you have full access to your phone), with rooted privilege you can almost do anything with your pad, like uninstall Asus embed software, do a full backup of your entire OS (operating system), modified system files etc... CWM is a tool you installed on your pad in order to flash (install) custom firmware. So at the minimum you should have root, and in the future when new custom firmware arrived, you can install cwm and used this tool to flash them. Keep in mind that with locked boot loader, you can't flash custom firmware. Finally, once you're rooted or have custom firmware installed, your pad will no longer can accepted OTA firmware (firmware push to your pad by Asus). In this case you need to roll back to stock (re installed factory firmware and no root), before you can do OTA update. Currently, I suggest you should stay on the side line and waiting for the OTA 4.1.1 JB (new Operating System called Jelly Bean, version 4.1.1 will be push to your pad by Asus). After reading this post you should be ready to play... good luck!
Sorry, but I don't get it, what is it about Verizon? Is it because you bought yours from Verizon? Mine comes from ASUS and I believe the OTA updates are from ASUS servers. Is it the US-specific thing that you mentioned?
Yeah... Everything is pretty easy even for people that have no clue what they are doing. My suggestion right now is to root but not unlock. Rooting is as simple as running the .bat file and following on screen directions (assuming you are using Windows). The only thing you need to do after the program is finished is to open up the Superuser app (might be SuperSU) and restart after that for safe measure.
Unlocking does VOID YOUR MANUFACTURERS WARRANTY (and possibly all others you may have purchased). Make sure you know what you want to do with an unlocked device before you do it. Personally, I am waiting for a stable JB build before I unlock. But the choice is ultimately up to you.
d14b0ll0s said:
Sorry, but I don't get it, what is it about Verizon? Is it because you bought yours from Verizon? Mine comes from ASUS and I believe the OTA updates are from ASUS servers. Is it the US-specific thing that you mentioned?
Click to expand...
Click to collapse
Sorry you're right, must not awake yet. ASUS that is. Thanks bro.
Your going to be fine try learning how to build aosp from source in a time limit
Sent from my Galaxy Nexus using xda premium
Skullmonkey said:
Yeah... Everything is pretty easy even for people that have no clue what they are doing. My suggestion right now is to root but not unlock. Rooting is as simple as running the .bat file and following on screen directions (assuming you are using Windows). The only thing you need to do after the program is finished is to open up the Superuser app (might be SuperSU) and restart after that for safe measure.
Unlocking does VOID YOUR MANUFACTURERS WARRANTY (and possibly all others you may have purchased). Make sure you know what you want to do with an unlocked device before you do it. Personally, I am waiting for a stable JB build before I unlock. But the choice is ultimately up to you.
Click to expand...
Click to collapse
I agree with Skullmonkey on this. Until you are ready for really hacking the system, all you really need is to root the system (run the DebugFS) to get "administrator access to your device".
You might want to read what buhohitr wrote several times as there is much to be gleaned from it. If it helps, copy/paste the contents of buhohitr's repsonse to a notepad text document and go through it word-for-word, isolate those that you find questionable or troublesome, then research what those words are. Anything that is "super difficult" you can just post back here in the Q&A section and I'm sure someone will help you in no time.
another noob question: does rooting the device void manufacturing warranty?
It does not. Only unlocking the device does.
Sent from my Transformer Infinity!
So if I root my Infinity...
...which pre-included apps can I get rid of?
Also which preloaded apps are best to bump off if I dare a root?
I have never dabbled with android down in the file system much for fear of doing something irreparable.
Well, to the OP: we already have quite a few 'basic' threads going on here, and no one forces you to embark on the more advanced stuff, do we? Just read up on it, and when you feel like you can make the jump, pick it up little by little. We're not all experts in here, but most of us can follow directions of the gurus really good, and we have the advantage of knowing how to save our butts when the excrement impacts the ventilator. (And most of us learnt it the hard way, by bricking and breaking...)
You should be fine in the regular forums, and as the others have said, stay out of the development sections until you feel secure enough to dabble around with unlocking and so on.
Sent from my ASUS Transformer Pad TF700T
buhohitr said:
Currently, I suggest you should stay on the side line and waiting for the OTA 4.1.1 JB (new Operating System called Jelly Bean, version 4.1.1 will be push to your pad by Asus). After reading this post you should be ready to play... good luck!
Click to expand...
Click to collapse
What's the method for unrooting/reflashing to stock at the moment? I rooted because I wanted to use Titanium Backup right after I got back up to .26. If we haven't figured out how to custom flash roms by the time jellybean comes out, I'll need to go back to stock. I would *hate* to have to lose all my apps, and its possible that titanium backup from 4.0.3 to 4.1.1 might royally screw up the system in doing a restore. So, if that's the case, I guess I'll reflash someway and lose everything? Doh.
spinaldex said:
What's the method for unrooting/reflashing to stock at the moment? I rooted because I wanted to use Titanium Backup right after I got back up to .26. If we haven't figured out how to custom flash roms by the time jellybean comes out, I'll need to go back to stock. I would *hate* to have to lose all my apps, and its possible that titanium backup from 4.0.3 to 4.1.1 might royally screw up the system in doing a restore. So, if that's the case, I guess I'll reflash someway and lose everything? Doh.
Click to expand...
Click to collapse
Anyone figure out a way to go back from root back to stock yet so that when Jelly Bean comes out we can upgrade?
spinaldex said:
Anyone figure out a way to go back from root back to stock yet so that when Jelly Bean comes out we can upgrade?
Click to expand...
Click to collapse
One method to get rid of root would be factory reset (power on while holding both the power and volume down while booting and running a factory reset.) But you could probably temporarily unroot with voodoo ota root keeper and then reroot once you install the upgrade to jelly bean with its root keeper.
Sent from my DROIDX using xda app-developers app
ekalb10 said:
One method to get rid of root would be factory reset (power on while holding both the power and volume down while booting and running a factory reset.) But you could probably temporarily unroot with voodoo ota root keeper and then reroot once you install the upgrade to jelly bean with its root keeper.
Click to expand...
Click to collapse
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
d14b0ll0s said:
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
Click to expand...
Click to collapse
I guess I was just misinformed on the factory reset, sorry if I confused anyone.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
d14b0ll0s said:
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
Click to expand...
Click to collapse
+ 1 I have rooted several tablets/phone over the last two years and backed it up using voodoo rootkeeper with ZERO issues updating firmware/OTAS. The only thing that happens after updating is that I loose root, but that's where voodoo OTA rootkeeper comes to play. Only a handful of people have had problems. Some are legit while others have messed/modded their device prior to updates. (like removeing system apps or modding build. Props)
"60% of the time, it works everytime. "
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Unroot it again ??
If there are problems with the tablet and it must be repaired on warranty, then I need to unroot it again.
How do I unroot it again ??
Regards Peder
Heey
I have my TF300 since 16 august and i realy like the tablet . But i lost my root when i update to the new version because i did rootkeeper wrong. But i like the root ability to use my ps3 controller and other apps. And a custom build.prop for smoother gaming.
This is also my first ever android device and my first tablet. I'm also 15 years old.
Can you guys help me with the following:
Bootloader unlock? or wait for a new Root Method?
I realy don't wanna void the warrenty if there are to many risks for a noob to unlock etc.
And is installing a recovery and a custom rom difficult?
Are there tutorials for it? Or even easy ways?
Is the new root method during long?
Is it diffifult to find a new method or is the development slow or not there for the tf300 root with locked bootloader?
Thanks for your time!
xSvenHD said:
Heey
I have my TF300 since 16 august and i realy like the tablet . But i lost my root when i update to the new version because i did rootkeeper wrong. But i like the root ability to use my ps3 controller and other apps. And a custom build.prop for smoother gaming.
This is also my first ever android device and my first tablet. I'm also 15 years old.
Can you guys help me with the following:
Bootloader unlock? or wait for a new Root Method?
I realy don't wanna void the warrenty if there are to many risks for a noob to unlock etc.
And is installing a recovery and a custom rom difficult?
Are there tutorials for it? Or even easy ways?
Is the new root method during long?
Is it diffifult to find a new method or is the development slow or not there for the tf300 root with locked bootloader?
Thanks for your time!
Click to expand...
Click to collapse
if you really want root i think you will be waiting a while unless you go back to "stage 1" ICS. if that is even possible. From what i have seen, the TF300 dev support is not that great. however, you may want to look into the TF201 (transformer Prime) as their older root methods seem to work just fine for use tf300 folk. so maybe they have a root method for JB.
Ok thanks for your reply i will look in the tf201 forum.
EDIT: I looked on the tf201 forums and there are no root methods on jb with locked bl
Bumb
xSvenHD said:
Heey
I have my TF300 since 16 august and i realy like the tablet . But i lost my root when i update to the new version because i did rootkeeper wrong. But i like the root ability to use my ps3 controller and other apps. And a custom build.prop for smoother gaming.
This is also my first ever android device and my first tablet. I'm also 15 years old.
Can you guys help me with the following:
Bootloader unlock? or wait for a new Root Method?
I realy don't wanna void the warrenty if there are to many risks for a noob to unlock etc.
And is installing a recovery and a custom rom difficult?
Are there tutorials for it? Or even easy ways?
Is the new root method during long?
Is it diffifult to find a new method or is the development slow or not there for the tf300 root with locked bootloader?
Thanks for your time!
Click to expand...
Click to collapse
Actually, you cannot root your device if it's in JB.
You can unlock with Asus tool, but if you don't want void your warranty.
Your last solution, you must waiting a development which can root your TF300 on JB
Well i want unlock it if i'm sure it does not get bricked. I saw something about NVFlash. Can i use it on jellybean?
xSvenHD said:
Well i want unlock it if i'm sure it does not get bricked. I saw something about NVFlash. Can i use it on jellybean?
Click to expand...
Click to collapse
Nobody will say that you cannot brick your device, but a lot of users have unlocked their tf300 with this tools in ICS or JB
Have you read completly the post ?
Before you get too excited, there are a few details you need to know before starting:
It will only work on UNLOCKED devices
It requires access to Fastboot to prepare device first time
It won’t work on fully bricked devices (See 2.)
You need to keep files safe!
If you upgraded to Offiical JB it *won’t* work!
Click to expand...
Click to collapse
ok thanks for your reply's
and i have read the thread fast and i only saw this : THIS ONLY WORKS IF YOU HAVE A PRE-JB BOOTLOADER
and i dont know what pre-jb means.
so now i got my awnsers. And my decision is: i will wait for a new root method.
xSvenHD said:
ok thanks for your reply's
and i have read the thread fast and i only saw this : THIS ONLY WORKS IF YOU HAVE A PRE-JB BOOTLOADER
and i dont know what pre-jb means.
so now i got my awnsers. And my decision is: i will wait for a new root method.
Click to expand...
Click to collapse
It's cool if you Click "THANKS" If It Helps or Good
xSvenHD said:
ok thanks for your reply's
and i have read the thread fast and i only saw this : THIS ONLY WORKS IF YOU HAVE A PRE-JB BOOTLOADER
and i dont know what pre-jb means.
so now i got my awnsers. And my decision is: i will wait for a new root method.
Click to expand...
Click to collapse
Let us know how long you hold out. I made it about 3 weeks after upgrading to JB and losing root... Seemed like forever too!
so i see this problem in other threads for other devices but i just accepted an OTA update while rooted to go from 4.1.1 (what came with the s3) to 4.1.2
Now i have an unlocked phone without root access. how can i regain root access?
CWM wont boot, but otherwise everything i do on a regular basis on the phone works fine, can i just keep it in this state without issues?
i know i am an idiot for not using voodoo but if anyone has a solution i would greatly appreciate it
rdstrmfblynch79 said:
so i see this problem in other threads for other devices but i just accepted an OTA update while rooted to go from 4.1.1 (what came with the s3) to 4.1.2
Now i have an unlocked phone without root access. how can i regain root access?
CWM wont boot, but otherwise everything i do on a regular basis on the phone works fine, can i just keep it in this state without issues?
i know i am an idiot for not using voodoo but if anyone has a solution i would greatly appreciate it
Click to expand...
Click to collapse
There may be an easier method, but you can go through the whole unlock / custom recovery / root / restore 4.2.2 method per this thread: http://forum.xda-developers.com/showthread.php?t=2046439
I used this method to root from stock 4.1.1 without trouble.
So I just got my new Sony Xperia Z3 but unfortunately it's D6603 model so no 32GB goodness which means I probably need Link2SD as I'll end up with probably about 10GB user available storage after all the updated which means I need to root.
I haven't even turned the phone on yet, it's still sitting there charging, but let's assume for a moment that it's not yet on Lollipop and still running KitKat which should mean I have various easy rooting methods at my disposal, right?
So what I'm asking is what would be the easiest (and most universal/in other words covering the most versions) root I could use.
I don't care about custom this or whatever, I want to keep my phone as stock as possible, I just want to be able to use Link2SD and maybe Titanium Backup, so if possible I'd prefer not to add a custom recovery or mess with anything beyond getting root access for those 2 apps.
I know I will have to check the bootloader first (I assume it's already unlocked though given the phone it's an international version that isn't carrier locked but that's a different problem anyways). But after that is there a recommended one-click root to use that alters as little as possible and covers as many android versions as possible? Or something almost as easy?
I don't want easy because my technical knowledge is lacking by the way, I want easy because the fewer steps there are the less I can screw up and I'm terrified of bricking the phone....so terrified I've resisted rooting my previous two android phones even after getting replacement phones, but I really need Link2SD now.
Should I use Kingroot and then replace the king Super User app with normal SuperuserSU?
Can I still keep root by doing a PC update instead of an OTA one?
SCHUMI_4EVER said:
Should I use Kingroot and then replace the king Super User app with normal SuperuserSU?
Can I still keep root by doing a PC update instead of an OTA one?
Click to expand...
Click to collapse
Search forums. You can have Z3 rooted on both locked and unlocked bootloaders or or install custom fw.
Sent from my D6603 using Tapatalk
use kingroot with chainfire's supersu
ondrejvaroscak said:
Search forums. You can have Z3 rooted on both locked and unlocked bootloaders or or install custom fw.
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
I know there are many options, I was hoping to be pointed to what someone considers the ideal easy way. My very problem was that I was inundated by potential rooting options but many either modified more than I would have liked or some seemed suspect/too good to be true (no way there are 30 accepted one-click root programs for this phone) so I'd been hoping someone would help me find the right tree in the forest of options I was looking at.
Anyways today I finally turned the phone on and to my great dismay found that it was already fully up to date (well our local network OTA updates may be a revision or 2 behind international updates) and running Lollipop 5.02 and I gave up all hope then there but Kingroot looked so easy that I decided to try it anyways and to my great surprise and tremendous delight it worked perfectly. Downloaded rootchecker and I'm fully rooted. Tried Link2SD and I'm extremely pleased to say that I have all of Asphalt 8 - Airborne's massive bulk as well as Spiderman Unlimited taking up space on my SD card and most of my user available internal storage remains unused.
I think I'm going to stay with KingRoot's app though and not switch to SuperSU, I don't want there to be any chance of losing this root access (I know it shouldn't happen but I desperately need Link2SD to stay happy so I don't want to rock the boat in any way).
So I guess this thread can be closed now.
Black Plague said:
use kingroot with chainfire's supersu
Click to expand...
Click to collapse
Thanks. I ended up using Kingroot before this already because when I turned the phone on for the first time I saw that it was already on 5.02 which I thought made it unrootable (without a custom rom, but I may have missread something somewhere) so I decided give it a Hail Mary try and it worked!!
I think I'm going to stick with KingRoot's app though and not replace it with SuperSU, I just don't want to rock the boat and lose that root access (I know it can be done without losing it, but I'm super paranoid).
SCHUMI_4EVER said:
Thanks. I ended up using Kingroot before this already because when I turned the phone on for the first time I saw that it was already on 5.02 which I thought made it unrootable (without a custom rom, but I may have missread something somewhere) so I decided give it a Hail Mary try and it worked!!
I think I'm going to stick with KingRoot's app though and not replace it with SuperSU, I just don't want to rock the boat and lose that root access (I know it can be done without losing it, but I'm super paranoid).
Click to expand...
Click to collapse
I would be more paranoid about using quite unknown app instead of rock solid and proven SuperSU..
Sent from my D6603 using Tapatalk
ondrejvaroscak said:
I would be more paranoid about using quite unknown app instead of rock solid and proven SuperSU..
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
I don't have anything sensitive on my phone, I'd prefer they didn't spy on me of course but as far as I'm concerned they can have every shred of info they want. All I need is root access for Link2SD, I don't need the rock-solid and proven SuperSU for that and I don't want any more features incase that offers more.
Since KingRoot has given my phone a chance at a decent life I'm willing to trust them until being shown info to the contrary (and I mean more than just them knowing my IMEI number).
SCHUMI_4EVER said:
Thanks. I ended up using Kingroot before this already because when I turned the phone on for the first time I saw that it was already on 5.02 which I thought made it unrootable (without a custom rom, but I may have missread something somewhere) so I decided give it a Hail Mary try and it worked!!
I think I'm going to stick with KingRoot's app though and not replace it with SuperSU, I just don't want to rock the boat and lose that root access (I know it can be done without losing it, but I'm super paranoid).
Click to expand...
Click to collapse
Easy bro, relax la, do you want to stick with kingroot super user ? its ok but if u flash chainfire's super su, u can uninstall that kinguser
Black Plague said:
Easy bro, relax la, do you want to stick with kingroot super user ? its ok but if u flash chainfire's super su, u can uninstall that kinguser
Click to expand...
Click to collapse
Besides having the more trusted app what would I gain from SuperSU? Does it to do more? Besides the engrish the Super User app from Kingroot seems fine.
Can SuperSU also unroot my phone again (should I need to warranty claim) and also try to keep the root permanent even when updates happen (which Kingroot apparently tries to do even if it likely won't work)?
Oh by the way one more question with regards to rooting. Back when I had my Xperia neo apparently OTA updates would make you lose root but doing an update via the Sony PC companion program could maintain the root...is that still the case? Or do I lose root no matter what now?
Pc companion is a worthless pos. Believe me. Look for alts, anything that works with android to your liking. You'll be much happier. Kingroot is not needed AT ALL. Plus I don't like the fact it calls home. Reminds me of the latest lenovo fiasco where programs within the bios are calling home-wtf! Use the tested working giefroot, flashtool, xzdr stuff. My 2cents