Related
Hey guys my gf has a rooted transformer through the razorclaw method on honeycomb. I want to update her tablet to ics but also keep root. However her tablet is one of the older models with the broken power button issue. Does anyone have any ideas on how to update and keep root that does not involve using the power button/ volume up and down keys? Any help would be greatly appreciated.
[ EDIT: SORRY DIDNT REALIZE I POSTED IN THE WRONG SECTION, MODERATERS COULD YOU PLEASE MOVE THIS TO THE GENERAL SECTION]
Sent from my Transformer TF101 using xda premium
There is a NVflash version but you still need power button to get into apx mode. Just a suggestion, you should look into fixing power button, it is pretty easy. I'm not good with tools at all and i was able to fix it after one RMA.
Perhaps you should look here...
http://forum.xda-developers.com/showthread.php?t=1391254
OTA rootkeeper worked perfectly for me.
I have already tried fixing the power button. Took the bezel off and realigned everything yet still no response. I even tried remapping the button but that didn't work either,
Sent from my Transformer TF101 using xda premium
st0nedpenguin said:
OTA rootkeeper worked perfectly for me.
Click to expand...
Click to collapse
Will i have to boot into any recovery for root keeper? Or do i just apply root keeper once root is lost during the ICS update?
Sent from my Transformer TF101 using xda premium
Actually OTA rootkeeper might be a good call, if you are able to receieve OTA update. It is a free app in the market. Here is the link..
https://market.android.com/details?id=org.projectvoodoo.otarootkeeper
I just got the tablet, it was preinstalled with honeycomb. I upgraded it with firmware V9.2.1.11 (android 4.0.3), then applied the following method with success :
http://forum.xda-developers.com/showthread.php?t=1515470
It only required activating USB debugging and playing with integrated backup software.
pierrekid said:
Will i have to boot into any recovery for root keeper? Or do i just apply root keeper once root is lost during the ICS update?
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Just install OTA rootkeeper, run it so it'll back up your root, then let the OTA ICS update install.
Once it's updated you can run OTA rootkeeper again and restore root.
No need for recovery or any fiddling.
OK, need someone to tell me what I'm missing please.
Yesterday I was on stock .30 and rooted. This morning I took the JB update. My first boot was OK and I still had root, but when I rebooted, I got stuck in a loop. It kept rebooting after getting to the desktop. I assumed at least one of my apps was causing it, so I used the wipe data function with the power + vol down thing. that wiped everything, including root.
I tried to re-do the debugfs method, but that seems to fail. Strange thing is, if I use adb shell from the computer, I can su - root and get root access. That's how I was able to give read/write access to the data folder where debugfs does its' work. It's just that root check says I'm not rooted. Voodoo OTA has all boxes checked on my root check, except the one that says granted root permissions. The SU file does exist inside /system/xbin
So it's as if the tablet's user just doesn't have permission to do root. I loaded a terminal emulator on the tablet, and tried to su - root that way, and got permission denied. I would normally get the "superuser" popup when doing something like that -
So there's definitely a piece I'm missing. Can someone point me in the right direction please?
reinstall ota rootkeeper and restore root. factory reset doesnt wipe root access you just need to restore it.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
jgaf said:
reinstall ota rootkeeper and restore root. factory reset doesnt wipe root access you just need to restore it.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Sorry, should have mentioned that I tried that. Attaching a screenshot as to what it looks like. Notice the center checkmark stating "root permission granted" is not checked, and there's no option to restore, only to remove or temp unroot, so it's like, everything is good, except for the actual root permission
Root checker shows red (no access) and root programs like root explorer do not prompt for superuser permission before running as I would expect them to the first time.
Did you run superuser? Did you reboot after running su for the first time?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Absolutely, more times than I can count. Here's another shot showing I can't execute such but it seems to have global execute...
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Install supersu and not superuser....update the binary ...then try again
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
pakure said:
Install supersu and not superuser....update the binary ...then try again
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
OK, uninstalled superuser, and installed superSU as you suggested and rebooted the tablet for good measure.
Ran it, and it prompted me, saying su needed updating, said yes do it, came back to me "installation failed", which I honestly expected because for whatever reason, current tablet user cannot get to su, even though it appears permissions said it should.
One other note, earlier I tried to refollow these directions: http://forum.xda-developers.com/showthread.php?t=1704209
That is how I rooted when under build .30, no issues at all. This time I hit a snag when trying to push files to /data/local - said I had no permission. now I got around it via ADB by simply typing su - root....root seems to work when I'm in ADB, but it doesn't work via tablet interface. I don't know what I'm missing here....
Just a thought.. I was considering flashing back to .30 using fastboot but I wasn't sure if that would even work. I tried loading the .30 zip into the root of storage and it detected it, as a downgrade even and asked to proceed. When done I was still on 4.1.1 not the older build.
BTW, thank you for taking the time. I really don't mean to be a pain here. I've not had this much trouble before...
Well sh++ This would explain why I couldn't redo the debugfs root process...
http://forum.xda-developers.com/showthread.php?p=27990303
I decided to go have a look at the nexus 7 area since that's native JB and saw that. So' for those just buying this, you might want to root before you update.
Still doesn't explain my problem but at least explains why I can't use the solution that WAS good.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
Well sh++ This would explain why I couldn't redo the debugfs root process...
http://forum.xda-developers.com/showthread.php?p=27990303
I decided to go have a look at the nexus 7 area since that's native JB and saw that. So' for those just buying this, you might want to root before you update.
Still doesn't explain my problem but at least explains why I can't use the solution that WAS good.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I was able to restore my root. See this post.
http://forum.xda-developers.com/showthread.php?p=30481502#post30481502
I've really messed up now. Set perms wrong for the such that was on the tablet so now can't get root using adb either so unless there is a way to downgrade without root I'm screwed.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I was so amped to grab JB, that I spaced that the OTA update would break root (i'm rooted but locked bootloader, b/c i was hoping 4.1.1 would come sooner than later!)
I had OTA rootkeeper installed, and while I was a little skeptical as to how easily it would work, it was 1-click simple and I just had to reinstall/update the binaries and reboot. I had the same check mark unchecked, but it worked, was straightforward, etc. It sounds like something got jacked in the JB flash, and I wonder if a full wipe/reset (&downgrade) to 4.04, re-root, then OTA update (using ota rootkeeper to hold root) might work for you?
thesuzukimethod said:
I was so amped to grab JB, that I spaced that the OTA update would break root (i'm rooted but locked bootloader, b/c i was hoping 4.1.1 would come sooner than later!)
I had OTA rootkeeper installed, and while I was a little skeptical as to how easily it would work, it was 1-click simple and I just had to reinstall/update the binaries and reboot. I had the same check mark unchecked, but it worked, was straightforward, etc. It sounds like something got jacked in the JB flash, and I wonder if a full wipe/reset (&downgrade) to 4.04, re-root, then OTA update (using ota rootkeeper to hold root) might work for you?
Click to expand...
Click to collapse
I would love to try the downgrade approach as that's the only one left I haven't tried, primarily because I have tried and haven't found a way to do it. If you know how with a locked boot loader then I'd love to hear.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
I would love to try the downgrade approach as that's the only one left I haven't tried, primarily because I have tried and haven't found a way to do it. If you know how with a locked boot loader then I'd love to hear.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
sorry, above my pay-grade at this point. I think i was overly optimistic about the "open-ness" of the device/bootloader (my other device is a galaxy nexus, so it's easy to do just about anything). I had a factory wipe or flash/img restore in my mind, but factory wipe wouldnt help (dont thinK), and If a stock 4.04 img exists, pretty sure there is a command set in fastboot that would let you restore using that image, but also pretty (99%) sure that requires an unlocked bootloader.
It sounds like there were a few changes in folder structure in JB that are limiting the root-ability, but my guess is the brainy folks around here will figure that out pretty quick, and JB will be root-able soon.
thesuzukimethod said:
sorry, above my pay-grade at this point. I think i was overly optimistic about the "open-ness" of the device/bootloader (my other device is a galaxy nexus, so it's easy to do just about anything). I had a factory wipe or flash/img restore in my mind, but factory wipe wouldnt help (dont thinK), and If a stock 4.04 img exists, pretty sure there is a command set in fastboot that would let you restore using that image, but also pretty (99%) sure that requires an unlocked bootloader.
It sounds like there were a few changes in folder structure in JB that are limiting the root-ability, but my guess is the brainy folks around here will figure that out pretty quick, and JB will be root-able soon.
Click to expand...
Click to collapse
Yes it's the /data folder where the exploit was and is causing the issue. I saw one of the commands was flash all, but I was too scared to try that. I tried the update.zip approach, but it came back with needed files weren't present in the archive.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
I would love to try the downgrade approach as that's the only one left I haven't tried, primarily because I have tried and haven't found a way to do it. If you know how with a locked boot loader then I'd love to hear.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
What did you do exactly? Details!
You can try this.... It may work... The worst case is that it just doesn't work. I have not seen a confirmation yet as to whether this method works or not yet.
https://www.dropbox.com/sh/jcpilpgoeta516e/QTl4TihVq0/Rooting-the-tf300.txt
---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------
calisro said:
What did you do exactly? Details!
You can try this.... It may work... The worst case is that it just doesn't work. I have not seen a confirmation yet as to whether this method works or not yet.
https://www.dropbox.com/sh/jcpilpgoeta516e/QTl4TihVq0/Rooting-the-tf300.txt
Click to expand...
Click to collapse
Oops. This is the whole link. Sorry about that. directions are in there.
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
---------- Post added at 03:11 PM ---------- Previous post was at 03:09 PM ----------
thesuzukimethod said:
I was so amped to grab JB, that I spaced that the OTA update would break root (i'm rooted but locked bootloader, b/c i was hoping 4.1.1 would come sooner than later!)
I had OTA rootkeeper installed, and while I was a little skeptical as to how easily it would work, it was 1-click simple and I just had to reinstall/update the binaries and reboot. I had the same check mark unchecked, but it worked, was straightforward, etc. It sounds like something got jacked in the JB flash, and I wonder if a full wipe/reset (&downgrade) to 4.04, re-root, then OTA update (using ota rootkeeper to hold root) might work for you?
Click to expand...
Click to collapse
If you have a check mark unchecked, you likely have root issues. Which check box?
calisro said:
If you have a check mark unchecked, you likely have root issues. Which check box?
Click to expand...
Click to collapse
Sorry - imprecise language on my part.
When I opened up OTA rootkeeper, it showed the same unchecked box (in rootkeeper) as others have mentioned, but I had "restore root" as an option. I did, and had no problems keeping root after updating to JB 4.1.1. OTA. I was using superuser but had checked "OTA survival" in Superuser's options, so I think that's how i kept root (seems like this "survival" option is baked in to Super Su, but a (non-default) option in Superuser).
I did an OTA update to JB and successfully saved my root with OTA Root Keeper. I then had to do a factory reset and my device went back to ICS which I was surprised by...
I ran the OTA update again and it failed. I couldn't re-download from the ASUS site OTA so I downloaded manually. Ran SuperSU, updated my binaries, backed up root with OTA Rootkeeper then ran the manual update to JB.
On reboot I tried to restore root but OTA Rootkeeper reports that there is no backup of root saved so I am stuffed.
Where should it be saved? Why would it have been lost during the update? Is there any chance than I can recover it from somewhere? I'm wishing I hadn't bothered with the upgrade now.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Reroot it using post jb update method?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
I would if there was one. I've not unlocked my bootloader and was not planning on doing so at this time.
Sent from my Galaxy Nexus using Tapatalk 2
Tried rebooting it?
Sent from my SAMSUNG-SGH-T989 using xda premium
Yup. No dice. I wondered where the root was actually saved and if it will still be there somewhere, hidden from view or if it has just been wiped by the update.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Its evident your root is gone, you won't be getting it back until root is available with out unlocking bl
Or u unlock it.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Hi, I got the device with root. But every thing which need su permission, su directly denies them, even it self while updating ! I changed option in su to auto accept root permissions. It didnt worked. I tried re rooting according to guide in thedroiddemos and after it batchfile said my device is succesfully rooted. Aaaand it was same result su denies everything. Help please cant do without root
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
muhsino said:
Hi, I got the device with root. But every thing which need su permission, su directly denies them, even it self while updating ! I changed option in su to auto accept root permissions. It didnt worked. I tried re rooting according to guide in thedroiddemos and after it batchfile said my device is succesfully rooted. Aaaand it was same result su denies everything. Help please cant do without root
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
What worked for me was installing SuperSU (updated binaries), installing Superuser Update Fixer (forcing fix if need be) and installing BusyBox and running it. I don't know which of these was the most essential to do, but it made the difference.
I was trying to fix it about 2 hours after 5min I post this thread I got it working lol. Sorry for spam ignore please
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Hello,
Bit confused what to do. I have brand new TF700T ICS 4.0.3 and I think I would benefit with rooted device. But what to do first? Update to JB and then root or root and update? I read this http://forum.xda-developers.com/showthread.php?t=1833212 so I would like to use the NvFlash before I start flashing... Is there any catch?
Please help...
Otas
otas78 said:
Hello,
Bit confused what to do. I have brand new TF700T ICS 4.0.3 and I think I would benefit with rooted device. But what to do first? Update to JB and then root or root and update? I read this http://forum.xda-developers.com/showthread.php?t=1833212 so I would like to use the NvFlash before I start flashing... Is there any catch?
Click to expand...
Click to collapse
You first have to decide if you want to void your manufacturer warranty by unlocking the boot loader (so that you can install custom ROMs). You do not need to unlock the boot loader if you only want to root it.
However, once you upgrade to JellyBean, you won't be able to install NVFlash any more, so if you are planning to unlock it in the near future, you should seriously consider doing it now, and then install NVFlash.
If you decide to unlock, there's no problem in rooting it afterwards. If you decide NOT to unlock, but still want to root, you should do so BEFORE you upgrade to JellyBean, as there's currently no way to root a JellyBean installation on the TF700 (if you install JellyBean without root, you'll have to downgrade to ICS to root, and then upgrade to JellyBean again).
As you can see, it all depends on what you want to do with your device - now and in the future. There's no way to know if it'll be possible in the future to install NVFlash on a JB installation, but once you have installed JB, you CANNOT install NVFlash - not even if you roll back to ICS. So you have to decide if you want NVFlash or not, and if so, you need to unlock it while on ICS and proceed from there.
If you want to keep the locked bootloader and warranty: First, root it. Look for the tutorial here in the Forum, it's very easy, should be something like "Root with debugfs".
Then, download OTA Rootkeeper from the Market (Google Play). Use it to protect your root.
Afterwards, you can either try the normal OTA Update (Didn't work for me, too big of a jump), or follow the following tutorial to update from one revision to the next. (So you've gotta update around 4-5 times in total to get to the newest JB revision).
http://forum.xda-developers.com/showthread.php?t=1926147
How to update to JB and keep root (Locked Bootloader)
Sent from my ASUS Transformer Pad TF700T using xda premium
ZeDroid said:
If you want to keep the locked bootloader and warranty: First, root it. Look for the tutorial here in the Forum, it's very easy, should be something like "Root with debugfs".
Then, download OTA Rootkeeper from the Market (Google Play). Use it to protect your root.
Afterwards, you can either try the normal OTA Update (Didn't work for me, too big of a jump), or follow the following tutorial to update from one revision to the next. (So you've gotta update around 4-5 times in total to get to the newest JB revision).
http://forum.xda-developers.com/showthread.php?t=1926147
How to update to JB and keep root (Locked Bootloader)
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
So I see.
Option 1) Rooted only and keep warranty - can't flash it.
Option 2) Root and unlock, lost warranty but be able to flash it. For this I need unlock the bootloader. And I would need to unlock to bootloader to install NvFlash, is it right?
What will be your recommendation? Do I need to flash it? The use would be recreational (internet/video/games) and travel laptop.
Otas
I personally didn't flash mine, at the moment I just don't need it. Should be fine for you to, why don't you try root & locked bootloader first?
You can always unlock the bootloader later on, but you can't "relock" it
Sent from my ASUS Transformer Pad TF700T using xda premium
ZeDroid said:
I personally didn't flash mine, at the moment I just don't need it. Should be fine for you to, why don't you try root & locked bootloader first?
You can always unlock the bootloader later on, but you can't "relock" it
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
The only reason why I would be considering to unlock it NOW is the NvFlash. Because I definitely want to update to JB.
otas78 said:
Hello,
Bit confused what to do.
Otas
Click to expand...
Click to collapse
Well you could always just use it for a day or two before you risk blowing it up.
Any manufacturing problems with it?
How familiar with the ins-outs of rooting\flashing are you?
If relatively new read then read some more.
The chances of a brick are low...then again you never know for sure.
Good luck...
So I did rooted using this http://forum.xda-developers.com/showthread.php?t=1706588 and all went well and I was told that the device is rooted.
Then I installed JB OTA no issues.
But now OTA Rootkeeper is telling me that I'm not rooted??!! What is going on?
otas78 said:
So I did rooted using this http://forum.xda-developers.com/showthread.php?t=1706588 and all went well and I was told that the device is rooted.
Then I installed JB OTA no issues.
But now OTA Rootkeeper is telling me that I'm not rooted??!! What is going on?
Click to expand...
Click to collapse
Did you actually backup your root using OTA Rootkeeper?
Did you protect the root with OTA Rootkeeper? Otherwise you just lost it....
You should be able to downgrade to ICS and root again following this:
http://forum.xda-developers.com/showthread.php?t=1925230
7786 said:
Did you actually backup your root using OTA Rootkeeper?
Click to expand...
Click to collapse
I see, f*** I updated before the I downloaded the OTE Rootkeeper. Any way out of it?
See my post on the first page. And guys, please don't do Full Quotes, we all know what you're replying to
Thank's I saw it later, looking to downgrade now.
So I downgraded already twice, run the OTA Rootkeeper, got the message that SU protected, run the JB update, run the OTA Rootkeeper again and no protected SU available... Where am I doing it wrong?
How exactly are you updating to JB? Per OTA?
Sent from my ASUS Transformer Pad TF700T using xda premium
Yes, per OTA
Strange. Did you try the update files from the thread I linked previously? (in my first post) The OTA never worked for me, so I used those.
Sent from my ASUS Transformer Pad TF700T using xda premium
Didn't need to because the OTA came on always automatically as soon as I rebooted. So I let it run.
I think I'm doing something wrong with the OTA Rootkeeper because it will not give me option to temp un-root...
Do you have Superuser installed? If not, try to install it from the Market, it will show you if you really got root.
From my perspective it sounds like you don't actually have root or just no application to control root.
Sent from my ASUS Transformer Pad TF700T using xda premium