Related
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).
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..
Hi folks.
I've just bought an Infinity. When booting it for the time, I updated it to Jelly bean. Now I'd like to know how can I root it? Unfortunately the debugfs method does not work anymore. So am I stuck ?
Thanks.
I have the same issue!
Gesendet von meinem GT-I9100 mit Tapatalk 2
You will have to wait for a new method to come out which may be a while. At this time if you lose root or have not rooted prior to JB you cannot get it back.
slainer68 said:
Hi folks.
I've just bought an Infinity. When booting it for the time, I updated it to Jelly bean. Now I'd like to know how can I root it? Unfortunately the debugfs method does not work anymore. So am I stuck ?
Thanks.
Click to expand...
Click to collapse
Yes, you are stuck. You will either have to develop a root method yourself or wait for someone else to do it for you unless you are willing to unlock. If you unlock, you should be able to flash alternate ROMs, etc, the sky's the limit. Be aware though, if you unlock, you will void your warranty and will not be able get OTAs. Flashing ROMs also comes with a certain amount of risk (especially w/out nvflash which you can't get since you upgraded).
Return it if you can. With the new one, Root and save with Voodoo OTA First, then run the JB update. It may be a long time before someone develops a root method for JB. The TF300 has been on JB for a while now and still no Root solution.
micaman said:
Return it if you can. With the new one, Root and save with Voodoo OTA First, then run the JB update. It may be a long time before someone develops a root method for JB. The TF300 has been on JB for a while now and still no Root solution.
Click to expand...
Click to collapse
I think that's the best recommendation to the OP. Cause there's no telling when a native JB root solution will come. Especially since all the Devs are already rooted.
For anyone who has not applied JB yet, this is one thread you'd want to read before applying that update: Last chance to root.
micaman said:
Return it if you can. With the new one, Root and save with Voodoo OTA First, then run the JB update. It may be a long time before someone develops a root method for JB. The TF300 has been on JB for a while now and still no Root solution.
Click to expand...
Click to collapse
Its sad but it is the Best option imo. Its a damn shame that asus ( and others ) have to go so far out of there damn way to stop root.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
i did the voodoo ota rootkeeper. it says I have root but when I try and open titanium backup, it doesn't work. any solutions?
I had an issue with the device at first with es File explorer. Had to install newer beta version of superUser and that fixed it. I have SU 3.1 installed now and all is working fine.
I found a jellybean root exploit in another thread I'll see if I can adapt it to work on the infinity. No guarantees though. I'm sure we'll be able to get this wild beast to submit once more!... eventually.
http://forum.xda-developers.com/showthread.php?t=1915598
might as well try downgrading if your just going to return it anyway.
dopapifreak34 said:
i did the voodoo ota rootkeeper. it says I have root but when I try and open titanium backup, it doesn't work. any solutions?
Click to expand...
Click to collapse
Are you using Superuser or Supersu? SuperSu is better in JB in my experience. Anyway open it and have it forget Titanium. Then open TB again and grant access.
you dont have to wait. you can downgrade to .30 update root it. and upgrade and use vooodoo OTA root keeper to root JB
Downgrade, root, then upgrade to JB again.
[TIP] Downgrade from JB to 0.30 works!
So i just bought a TF700t came with a 1yr warranty from new-egg, and i was wondering, if i should root it or use a custom rom? PS is this think even rootable?
nixvaldez said:
So i just bought a TF700t came with a 1yr warranty from new-egg, and i was wondering, if i should root it or use a custom rom? PS is this think even rootable?
Click to expand...
Click to collapse
First, check your build number, if you have build .26 then you should make a bootloader backup with NVflash. (This is very important) before upgrade. I found the stock rooted JB with browse2ram is the best and trouble free. The only custom JB you should consider is Zeus JB, but it's not available right now. Dev is still sick.
buhohitr said:
First, check your build number, if you have build .26 then you should make a bootloader backup with NVflash. (This is very important) before upgrade. I found the stock rooted JB with browse2ram is the best and trouble free. The only custom JB you should consider is Zeus JB, but it's not available right now. Dev is still sick.
Click to expand...
Click to collapse
where exactly is the .26 located at?mine reads IML74K.US_epad-9.4.5.30-20120907 i take it mine is .30?
nixvaldez said:
where exactly is the .26 located at?mine reads IML74K.US_epad-9.4.5.30-20120907 i take it mine is .30?
Click to expand...
Click to collapse
Yes, yours is .30. NVflash bootloader backup is not working with .30 or JellyBean. Anyway you could root this without any issue, then use Voodoo OTA root keeper to backup root then ugrade to JellBean and use root keeper to restore root back on JB. If you unlock bootloader, there is no way back. Also voided your warranty. I would just root for now since I don't see any rom/kernel worth to unlock yet.
I agree with above the post. Rooting is good to have so you can use stuff like Titanium back up, Busybox, six asais controller and a few other apps. Plus rooting does not void warranty.
Until there is something you feel is a must have/need, I would wait to unlock the boot loader, such as a ROM or kernal. For me, I haven't seen that reason. I just freeze the bloat ware. I should back it up and delete it, but that's a whole different topic.
Rooting, from what I read is possible on .30. I believe the defugs method works. It's the method used on Prime (TF201). From what I read, just make sure you don't have ADB installed on your machine. It should be really easy. It was for me when I was on .26.
What did I get wrong?
Hey guys, I have the same exact TF700 as OP and I've tried miloj's rooting method to the exact letter. It says on the prompt after the whole process that I have root access, but in Root Checker it says that I do not have complete root access.
USB Debug mode: check
Unknown Sources: check
Updated ASUS driver in device manager: check
Not running ASUS sync on PC or tablet: check
What could I possibly missed? I've gone through all the relevant posts and followed every instruction but Root Checker still says I don't have root access..
Thanks for your time guys.
flamingsnot said:
Hey guys, I have the same exact TF700 as OP and I've tried miloj's rooting method to the exact letter. It says on the prompt after the whole process that I have root access, but in Root Checker it says that I do not have complete root access.
USB Debug mode: check
Unknown Sources: check
Updated ASUS driver in device manager: check
Not running ASUS sync on PC or tablet: check
What could I possibly missed? I've gone through all the relevant posts and followed every instruction but Root Checker still says I don't have root access..
Thanks for your time guys.
Click to expand...
Click to collapse
Did you try to open Superuser app after boot up?
buhohitr said:
First, check your build number, if you have build .26 then you should make a bootloader backup with NVflash. (This is very important) before upgrade. I found the stock rooted JB with browse2ram is the best and trouble free. The only custom JB you should consider is Zeus JB, but it's not available right now. Dev is still sick.
Click to expand...
Click to collapse
Not true anymore. CleanROM v1.3 absolutely flies. I was on Zeus ICS ROM v4.0, and this is really fast and functional.
okantomi said:
Not true anymore. CleanROM v1.3 absolutely flies. I was on Zeus ICS ROM v4.0, and this is really fast and functional.
Click to expand...
Click to collapse
Clean rom is nothing but stock rom and tons of bloatware removed, I wouldn't consider this as custom rom. I agreed with you on Zeus, since it cut down I/O by trading data integrity to achieve this, but Zeus is now "history" we are on JB now, until Zeus on JB released, I won't unlock the device.
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