Database Info

Took the update to JB, but can't get my root back

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).

[Resolved] Understanding what Locked BL w/JB & root did

I just wanted to understand where I am and what happened.
I have a locked boot loader TF300T, it came with .30.
I rooted with the debugfs root process.
I downloaded and ran OTA root keeper,
and saved root.
Later JB was offered to me. I took the update
and lost root. I thought I had to rerun the
debugfs script again, but that doesn't work
in JB.
After a reboot, I re-downloaded and reinstalled
OTA root keeper, and it prompted me to restore
root. After another reboot, root is back.
I'm guessing whatever the debugfs script did
to get root is fixed in 4.1.1, but OTA root
keeper was successful in doing its job.
So I have root again in a locked otherwise
stock TF300T with JB 4.1.1.
Did I do it right?
Do I understand correctly?

If you have a root checker, run it to make sure. Just search for root check in the market. If you still have root, then you are lucky. Many others have lost half or all their root access.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Results of checker
funnel71 said:
If you have a root checker, run it to make sure. Just search for root check in the market. If you still have root, then you are lucky. Many others have lost half or all their root access.
Click to expand...
Click to collapse
Checker reports success

That's pretty cool that you kept it. Don't do a data wipe or you won't be able to get it back without unlocking the bootloader.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Followup Root on TF300T & 4.1.1 OTA
I'm hoping the nice folks here will figure out
a new way to root for jelly bean eventually.
I personally do not like ASUS's approach
of blacklisting unlocked serial numbers.
Realisticly, while some issues can be
caused by bad flashes. There are still
real hardware failures that should
be covered by warranty regardless
of content.
Loose ports or other obvious deflects,
for example. They would be there stock or
not.
For the time being, I'm staying locked
& rooted. At least I can use root apps
to backup apps and data.

That's pretty good thinking. I feel the same, hence waiting for a stock and lock root solution.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

fuzzynco said:
I'm hoping the nice folks here will figure out
a new way to root for jelly bean eventually.
I personally do not like ASUS's approach
of blacklisting unlocked serial numbers.
Realisticly, while some issues can be
caused by bad flashes. There are still
real hardware failures that should
be covered by warranty regardless
of content.
Loose ports or other obvious deflects,
for example. They would be there stock or
not.
For the time being, I'm staying locked
& rooted. At least I can use root apps
to backup apps and data.
Click to expand...
Click to collapse
funnel71 said:
That's pretty good thinking. I feel the same, hence waiting for a stock and lock root solution.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
+1... The desire to upgrade to JB has been eating me up but at only 3 weeks old I want to keep my tf300t locked a little while longer. And I also think the blacklist thing is a poor testament to ASUS's customer support. As a VAR I sold a lot of their product and had few issues, but their attitude toward open source is lame. If I wanted to be treated like an Ipad owner I would have bought an Ipad.
The upgrade bug had me so bad that I did put JB on my SGSII4G since I can restore that without issue. Really was not all that impressed. I agree with what others have said it is a resource hog. I know that is not as big a deal with android but it is getting kind of windoz like (every release is 33% fatter (IMHO). And Flash does have issues with the Bean.
For now I will stay with rooted ICS on the ASUS until I'm comfortable with the reliability or their is a truly safe way to run Bean. Anyone know how to get rid of this annoying upgrade nag screen, besides upgrading?

Preparing for Jelly Bean Update

Hey Everyone, I'm coming from a Asus Transformer tf300 , and my device was rooted, and didn't have bootloader unlocked....when receiving the OTA for Jelly Bean, I was under the impression that Using Voodoo OTA Rootkeeper would make everything smooth and dandy to take the OTA and still be rooted by restoring at after the update.... Well Voodoo OTA Rootkeeper worked but only half way, and what I mean by that is that the device was rooted but root permission was not given so it was pretty much no point in being rooted, and some say it was because an app called Supersu was not installed prior to the update and when the back up was made, so that app + Superuser had to be present and some people obtained their full root that way....But my point for this thread is to figure out before hand what methods we will take on the tf700 so that many wont be stuck without root when it happens.....I never was able to get full root or unroot or do anything, I ended up selling my tf300 and now have a tf700 so just taking precautions cuz I would love Jelly Bean on here but also would love root...... any suggestions?

I think the best way to prepare for Jellybean is to let some others do it first and see how it goes for them. Maybe we'll be fine, maybe we'll need the supersu trick, maybe we'll need something else entirely. At this point, we simply cant say. As such, better to be cautious.
I've been reading some of the 300 threads on the JB update, and it looks like some people are having issues with their custom recoveries as well. Until there's a full understanding of the consequences of updating, I think those who are on anything other than unrooted locked stock should hold off unless they want to play guinea pig.

The update will likely be posted as a cwm flashable ROM very shortly before or after it is available via ota dont worry you can find it here!
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

What do you think is more feasible? Stay stock and not root and wait for jelly bean and update to it, then see if a way to root is found for jelly bean? Or root now, and hope there is a way found to carry that root on to Jelly bean eventually? Cuz I know the jelly bean update was very sneaky on the tf300, I didnt even know it was updating until it was already downloaded and ready to be installed, and it only asks a few times before automatically installing it.....so risks are involved in both.....hhmmmmmmm

MrTonyToca said:
What do you think is more feasible? Stay stock and not root and wait for jelly bean and update to it, then see if a way to root is found for jelly bean? Or root now, and hope there is a way found to carry that root on to Jelly bean eventually? Cuz I know the jelly bean update was very sneaky on the tf300, I didnt even know it was updating until it was already downloaded and ready to be installed, and it only asks a few times before automatically installing it.....so risks are involved in both.....hhmmmmmmm
Click to expand...
Click to collapse
I would say root now, use OTA rootkeeper to protect root and that way when you get the JB OTA you can just use OTA rootkeeper to restore root.

swa2k4 said:
The update will likely be posted as a cwm flashable ROM very shortly before or after it is available via ota dont worry you can find it here!
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
That's well and good for people who are unlocked, but not for people who are locked and just rooted. I dont see a need to really unlock at this point. I will unlock it when I start deving for it in a few days though

I'm rooted but not unlocked. I'll be using the SuperSU trick to confirm that it works for us. I don't plan on any unlocking until I'm safely updated.

Alitheia said:
I'm rooted but not unlocked. I'll be using the SuperSU trick to confirm that it works for us. I don't plan on any unlocking until I'm safely updated.
Click to expand...
Click to collapse
Let us know if it works.....There was a way to fix the root permissions that they were sayin in the tf300 forum, but it involved alot of adb shell commands and pushing files, and me not being familiar with adb attempted it but wasn't able to execute all the commands, so even if it doesn't work there would be hope! (for people who are good with adb any way) :highfive:

So being rooted and unlocked, I will probably have to wait until someone creates a Rom from the jelly bean ota correct?
Sent from EVO LTE using the XDA app

Yes, you need SU and Voodoo working in conjunction after a root to maintain it. I rooted but didn't unlock because the rom scene isn't developed yet. I will be updating to JB as soon as possible and voodoo will hopefully preserve my root (It always did on my tf300 and on my htc amaze).
Any reason to believe it would not?

Diogenes5 said:
Yes, you need SU and Voodoo working in conjunction after a root to maintain it. I rooted but didn't unlock because the rom scene isn't developed yet. I will be updating to JB as soon as possible and voodoo will hopefully preserve my root (It always did on my tf300 and on my htc amaze).
Any reason to believe it would not?
Click to expand...
Click to collapse
Yes, because several people including myself, kept root but lost our root permissions when using voodoo......it was later found out to have both root and root permissions saved is to download an app called Supersu, and have that and Superuser and also in superuser make sure in the setting that OTA Restore is checked off in order for it to work.....that method worked for most people.....This only happened with the Jelly Bean OTA, every other time it worked like a charm.....

MrTonyToca said:
Yes, because several people including myself, kept root but lost our root permissions when using voodoo......it was later found out to have both root and root permissions saved is to download an app called Supersu, and have that and Superuser and also in superuser make sure in the setting that OTA Restore is checked off in order for it to work.....that method worked for most people.....This only happened with the Jelly Bean OTA, every other time it worked like a charm.....
Click to expand...
Click to collapse
Gotcha, thanks for the info. I got confused because I assumed you were using an acronym for "Superuser."

ooonimrodooo said:
So being rooted and unlocked, I will probably have to wait until someone creates a Rom from the jelly bean ota correct?
Sent from EVO LTE using the XDA app
Click to expand...
Click to collapse
Right as being unlocked prevents you from receiving the ota. I don't think you'd have to wait long though. Someone will surely post theirs right away.

Alitheia said:
Right as being unlocked prevents you from receiving the ota. I don't think you'd have to wait long though. Someone will surely post theirs right away.
Click to expand...
Click to collapse
Same situation .. I have my TF700 root, unlock and installed TWRP ... I must wait for a ROM upload here ..

just wanted to post this link from Asus' infinity facebook page: just wanted to post this link from Asus' infinity facebook page: http://www.gizmocanada.com/2012/08/a...ndroid-os-4-1/
No jelly bean yet.
Also at the end of the article it says if you're rooted you won't receive OTA updates? is this true?

Alitheia said:
I'm rooted but not unlocked. I'll be using the SuperSU trick to confirm that it works for us. I don't plan on any unlocking until I'm safely updated.
Click to expand...
Click to collapse
This is my plan, too, except I'm not planning to unlock the TF700 after JB unless it's the only way to stabilize it, like it was with the TF201 after ICS. The stock ROM with root is fine for me if it is stable.

chucky7910 said:
just wanted to post this link from Asus' infinity facebook page: just wanted to post this link from Asus' infinity facebook page: http://www.gizmocanada.com/2012/08/a...ndroid-os-4-1/
No jelly bean yet.
Also at the end of the article it says if you're rooted you won't receive OTA updates? is this true?
No jelly bean yet.
Also at the end of the article it says if you're rooted you won't receive OTA updates? is this true?
Click to expand...
Click to collapse
I would think they meant if you are unlocked, rather than rooted.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

PolishPoet said:
I would think they meant if you are unlocked, rather than rooted.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
You are right PolishPoet, I meant unlocked bootloader not rooted. Once the device is updated on a rooted device, it just unroots it, and you will have to root again.
NS
Gizmocanada

With all of this in mind...
I'm stock at the moment. Does it make more sense to stay stock until JB then root, or to root and try to keep it through the JB upgrade? My root needs aren't urgent.

So far there's no indication rooting under JB will be easy, so better root your tablet first and follow the SuperSU guidelines..

[Q] What to do with brand new TF700T with ICS 4.0.3

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

[Q] Tried multiple time multiple way can not ROOT TF700

I have tried Rooting I have even unlocked my tablet as it seems that this might have made rooting easier I have updated to JB. The easiest mething I found i keep getting a ADB server out of date message i tried doing the ADB Fix program and it says there was not issue please point me in the right direction to root a TF700 easily again my device is unlocked hopefully this helps the process more than hurts

silverrain21 said:
I have tried Rooting I have even unlocked my tablet as it seems that this might have made rooting easier I have updated to JB. The easiest mething I found i keep getting a ADB server out of date message i tried doing the ADB Fix program and it says there was not issue please point me in the right direction to root a TF700 easily again my device is unlocked hopefully this helps the process more than hurts
Click to expand...
Click to collapse
I recommend you use the forum's search feature. You'll find many, many, posts related to your situation.

Or now you are unlocked you can flash a custom stock ROM that is already rooted.
Visit the dev section. All you need is a custom recovery and you are set to go.

What he said^^^^^^
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

search a couple more times on the forum itself and was able to find a method that worked. it did take 3 days of active searching (like 3-5 hours a day) only reason i posted in the first place

silverrain21 said:
search a couple more times on the forum itself and was able to find a method that worked. it did take 3 days of active searching (like 3-5 hours a day) only reason i posted in the first place
Click to expand...
Click to collapse
Well if you are unlocked you just need to do two things ....
1. Install a custom recovery (head over to TWRP or CWM thread in dev section)
2. Either flash a custom rom or super user (SUPERSU) package from said custom recovery.
If you can't find one I will make you one but I am sure there is one in the dev section.

silverrain21 said:
search a couple more times on the forum itself and was able to find a method that worked. it did take 3 days of active searching (like 3-5 hours a day) only reason i posted in the first place
Click to expand...
Click to collapse
Can you post a specific method you have tried for rooting the Infinity?
It's really important to include details of your attempt so that those trying to help know where in the process you are exactly.
Typically one needs to return to an Ice Cream Sandwich version 4.03 copy a downloaded file to the external SDCard (preferably while inserted in a card reader on ones Windows PC) rename to "EP201_768_SDUPDATE.ZIP"
Reboot tab and look for the OTA message in the notification bar.
Once returned to ICS (Android 4.03) degugfs can be implemented to attain root.
After root is successful from ICS then OTA Rootkeeper can be used to save root when upgrading to Jellybean.

Thats OK said:
Can you post a specific method you have tried for rooting the Infinity?
It's really important to include details of your attempt so that those trying to help know where in the process you are exactly.
Typically one needs to return to an Ice Cream Sandwich version 4.03 copy a downloaded file to the external SDCard (preferably while inserted in a card reader on ones Windows PC) rename to "EP201_768_SDUPDATE.ZIP"
Reboot tab and look for the OTA message in the notification bar.
Once returned to ICS (Android 4.03) degugfs can be implemented to attain root.
After root is successful from ICS then OTA Rootkeeper can be used to save root when upgrading to Jellybean.
Click to expand...
Click to collapse
Do you still get ota updates on an unlocked device?

sbdags said:
Do you still get ota updates on an unlocked device?
Click to expand...
Click to collapse
Not sure there.
I believe the manual update notice may appear even after an unlock.

When I unlocked my bootloader and was running stock for a month I did not get any OTA updates when they released the update for 10.4.4.25. I had to go to their site and put it on my microsd card and update it that way.
Sent from my ASUS Transformer Pad TF700T Infinity using Tapatalk HD
Rom: CleanRom 3.4.4

The way i rooted and unlocked my asus tf700t
sbdags said:
Well if you are unlocked you just need to do two things ....
1. Install a custom recovery (head over to TWRP or CWM thread in dev section)
2. Either flash a custom rom or super user (SUPERSU) package from said custom recovery.
If you can't find one I will make you one but I am sure there is one in the dev section.
Click to expand...
Click to collapse
I used TWRP and then flashed super user
The way I unlocked was i used the unlock package on the ASUS website I am on 4.1.1 and had no issues what so ever.

sbdags said:
Do you still get ota updates on an unlocked device?
Click to expand...
Click to collapse
No, unlocking disables the OTA facility. But you knew that, too, didn't you?
I love these rhetorical questions.

MartyHulskemper said:
No, unlocking disables the OTA facility. But you knew that, too, didn't you?
I love these rhetorical questions.
Click to expand...
Click to collapse
I was being kind lol