Related
Hi,
Is any app to block future OTA?
I'm leaving for two months, and take my tf as photos storage place.
We know ICS OTA is coming soon, I'd like to install update when back home in april.
As I remember previous OTA's it was possible to dismiss install of update, but only free times!
TF rooted.
Thank you for any ideas.
Sent from my Transformer TF101 using Tapatalk
_Pablo_ said:
Hi,
Is any app to block future OTA?
I'm leaving for two months, and take my tf as photos storage place.
We know ICS OTA is coming soon, I'd like to install update when back home in april.
As I remember previous OTA's it was possible to dismiss install of update, but only free times!
TF rooted.
Thank you for any ideas.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
How about installing CWM? Shouldn't that prevent official updates from installing?
With titanium backup there is a system app that you have to freeze to disable ota's but i cant remember the name of it off the top of my head
CWM installed right know, but it prevent OTA from installing?
Sent from my Transformer TF101 using Tapatalk
mrevankyle said:
With titanium backup there is a system app that you have to freeze to disable ota's but i cant remember the name of it off the top of my head
Click to expand...
Click to collapse
I checked sys apps in root uninstaller, and...
maybe "update launcher", I'll use google tomorrow, its 5 o clock mornig ;-) here, time to sleep.
Thanks for idea.
Sent from my Transformer TF101 using Tapatalk
Freeze DMClient app.
Sent from my Transformer TF101 using Tapatalk
_Pablo_ said:
CWM installed right know, but it prevent OTA from installing?
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Yep.
It has worked for me. You can try to install the update, but it will fail and no more OTA messages. I guess it will be the same with the ICS update.
Regards.
CalvinH said:
Yep.
It has worked for me. You can try to install the update, but it will fail and no more OTA messages. I guess it will be the same with the ICS update.
Regards.
Click to expand...
Click to collapse
So when I'll back, have to install oryginal recovery back before ICS OTA right ?
I hope it's possible to install oryginal recovery back
Sent from my Transformer TF101 using Tapatalk
OTA update uses stock recovery to flash the update. If you have cwm the update won't install. To install stock recovery, simply flash it via cwm. It takes a whole 10 seconds. Don't worry about it, its easy. Just enjoy your trip.
goodintentions said:
OTA update uses stock recovery to flash the update. If you have cwm the update won't install. To install stock recovery, simply flash it via cwm. It takes a whole 10 seconds. Don't worry about it, its easy. Just enjoy your trip.
Click to expand...
Click to collapse
Thank you very much!
It will be great test for transformer 20 days in Annapurna cirkuit trek and 20 days in India.
Sent from my Transformer TF101 using Tapatalk
As goodintentions said, it can be done in no time.
I have installed and removed CWM recovery a couple of times and it's pretty easy.
And the OTA updates always come back to me
CalvinH said:
As goodintentions said, it can be done in no time.
I have installed and removed CWM recovery a couple of times and it's pretty easy.
And the OTA updates always come back to me
Click to expand...
Click to collapse
thanks for update, from where you download orginall recovery image?
Sent from my Transformer TF101 using Tapatalk
Hi!
I have the following method used several times for unrooting + removing CWM recovery.
http://forum.xda-developers.com/showthread.php?t=1093403
There are two ways to get updated to the latest ROM. If you use the files on the first post of the thread, upon rebooting you will get an OTA update message (if yo don't you can check for updates manually ).
The other way is to navigate to asus support page, look for the TF101, select android as OS, and under firmware you will find the latest ROMs with the info needed about how to install them.
Once again I have used both methods. The first one is probably better because you need not to download anything, but both work.
Regards.
Purchased a used TF101 last night, and the update was waiting when I powered it on. Needless to say, I regret doing it now.
However, I believe I have it figured out how to get root. I'd just like someone that's had more experience with the TF101 to verify for me.
Opt. 1
- Download recoveryblob from Wolfman's thread.
- Downgrade to .11 or .17
- Root
- OTA Rootkeeper
- Update to newest firmware
Opt. 2
- Download recoveryblob from Wolfman's thread.
- Downgrade .11 or .17
- Root
- CWM
- Flash custom rom with OTA already included.
Am I looking at a bricked pad here? Not actually sure if .24 can be downgraded, but I figured since it worked for .21. I'd give it a shot and see what happens.
Not bricked in the slightest, bricked means can't turn on at all. Downgrade should work with .24 as well, or just wait for an official root for .24 to come out. I also recommend option 2, if you're going to go through the trouble of downgrading may as well put a ROM on there.
Thing O Doom said:
Not bricked in the slightest, bricked means can't turn on at all. Downgrade should work with .21 as well, or just wait for an official root for .24 to come out. I also recommend option 2, if you're going to go through the trouble of downgrading may as well put a ROM on there.
Click to expand...
Click to collapse
Thanks,
I've found the resident expert. I'll give it a shot tonight when I get home.
meant to type .24 not .21 Sorry, just give it a shot. If the exploit is still there it should work. Good luck.
Thing O Doom said:
meant to type .24 not .21 Sorry, just give it a shot. If the exploit is still there it should work. Good luck.
Click to expand...
Click to collapse
Thanks alot..
Worked perfectly! Downgraded to .17, rooted, installed CWM and Android Revolution.
What's the best way to get just root with .24
Sent from my Transformer TF101 using Tapatalk 2
Ellingsoc said:
What's the best way to get just root with .24
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
If you're currently on .17, you can root using Vipermod, install CWM, and flash just the .24 zip using CWM.
05GT said:
If you're currently on .17, you can root using Vipermod, install CWM, and flash just the .24 zip using CWM.
Click to expand...
Click to collapse
I think you would need to follow the sequence flashing from .17 to .21 update zip and lastly the .21 update zip using CWM. Use Voodoo OTA RootKeeper to retain your root previllage..
I am on .24
Sent from my Transformer TF101 using Tapatalk 2
I have the same problem.
I want to keep my .24 but i can't root this.
Is there a good guide to do this ?
I only want to root - nothing more.
Thanks in advance.
klopikxda said:
I have the same problem.
I want to keep my .24 but i can't root this.
Is there a good guide to do this ?
I only want to root - nothing more.
Thanks in advance.
Click to expand...
Click to collapse
Right now,
There's no way to root .24 without downgrading first. I'm pretty sure that you're going to need CWM as well. Only way I know to do it.
Downgrade without Unlock on .24 i have done 5 TF101's ussing this method all with serials b80 to c20 Go here: http //freek.ws/2012/05/07/howto-root-you-asus-transformer-tf101-or-asus-transformer-prime-tf201-running-ice-cream-sandwich-ics-9-4-2-21-without-unlocking-your-bootloader/
Hi!, i've just followed these instructions to downgrade my TF101 b70 and it was just perfect, easy and fast...
Now i'm with .24 rooted.
Thank you!
Yep, this method worked perfect with my .24 TF101 B50. Thanks!
If you don't aren't proficient with adb, or just don't feel like using it, this is a link that should be easy enough for anybody. It has illustrations and step by step directions. It works for. 24 also.
Good luck
http://freek.ws/2012/05/07/howto-ro...s-9-4-2-21-without-unlocking-your-bootloader/
Sent from my Team-B CM7 Nook Tablet using Tapatalk
No more downgrading crap required anymore! link in my signature for NvFlash for SBKv2!!!
Thing O Doom said:
No more downgrading crap required anymore! link in my signature for NvFlash for SBKv2!!!
Click to expand...
Click to collapse
While I'm not a dev by any stretch, I'm also not tech retarded lol... I have tried downgrading .24 using every method posted and can't seem to make it happen. Close as I get is the firmware update droid with the progress bar then he falls flat with a red triangle. Doom the whole APX mode and everything in your link throws me off and after doing all that I'd still have to root? or would I just have an easier time with the custom ROM stuff (which I don't really need).
Thanks in advance for any help that comes my way.
No, just vol-up+power to get into APX, then NvFlash a custom Recovery (rouge has a version specifically for NvFlash.) Then once you have recovery, either flash a ROM (which will be pre-rooted) or superuser.apk (if you want to stay stock) Easy as pie process.
Your need to downgrade to an ota that is able to be rooted first, then after rooting use ota rootkeeper to maintain your root. You can then update back to. 24 and keep your root. The link that i posted explains this or you could also try wolfs downgrade method, but it requires adb, which some people might not feel comfortable using.
Sent from my Team-B CM7 Nook Tablet using Tapatalk
balrog558 said:
Your need to downgrade to an ota that is able to be rooted first, then after rooting use ota rootkeeper to maintain your root. You can then update back to. 24 and keep your root. The link that i posted explains this or you could also try wolfs downgrade method, but it requires adb, which some people might not feel comfortable using.
Sent from my Team-B CM7 Nook Tablet using Tapatalk
Click to expand...
Click to collapse
It is no longer required with the release of nvflash for b70+ devices.
We are working on a windows binary, but no ETA quite yet.
The recommended way is to install a custom recovery then flash an update.zip to install Superuser.apk and the su binary.
Note that this should also enable "one-click" roots using nvflash for ANY rom version - eventually at least
I am version .29 (i think, how do i tell?) and i want to root.
I don't want to flash new ROMs yet, so I don't think i need an unlocked bootloader. If I only root the tablet, will I permanently void my warranty?
Thanks
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
No. As long as you get rid of all the root stuff, no one would be able to tell you were rooted.
sounds good.
Also, how do I tell what version tablet i have? where do i look for .29 vs .26?
Thanks
settings/about tablet and scroll down to build number...you will see a long number and .26 or .29 followed by a long number.
congrats...I'm still having some issues rooting. ota rootkeeper didn't keep my root when I upgraded from .17 to .29...still working on it
Throb1231 said:
settings/about tablet and scroll down to build number...you will see a long number and .26 or .29 followed by a long number.
congrats...I'm still having some issues rooting. ota rootkeeper didn't keep my root when I upgraded from .17 to .29...still working on it
Click to expand...
Click to collapse
Something is borked with your system my friend. I've been following your attempts to root. I rooted my system as of today with .17 using sparkys root. It didn't work the first time for whatever ryhme or reason, then after trying it a second time doing it a little differently, it worked. If there is a way for you to do a full wipe/reload and start fresh, I would do that.
Sent from my SGH-I777 using Tapatalk 2
cavsoldier19d said:
Something is borked with your system my friend. I've been following your attempts to root. I rooted my system as of today with .17 using sparkys root. It didn't work the first time for whatever ryhme or reason, then after trying it a second time doing it a little differently, it worked. If there is a way for you to do a full wipe/reload and start fresh, I would do that.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I thought he had manually updated to .29, in which case you wouldn't be able to restore with rootkeeper.
Rooted my stock .29 300 with sparky's root tool tonight; worked first time flawlessly.
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).
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