Related
Header says it all... and if the answer is YES, then a link to HOW to accomplish that would be greatly appreciated...
Many thanks...
You would need to root, install cwm recovery, flash a rooted HC ROM.
@basballfanz: how to root the 9.2.2.3 Firmware?
From my experience, once you are on ICS, re-flashing Honeycomb via CWM does NOT solve the reboot issues (you'll have them in Honeycomb too). The ONLY way that I was able to return to a stable version of Honeycom was to NVFLash a stock honeycomb image and go from there. But, since you have a B90, you can't NVFlash, so basically, I think you're screwed at this point....
There is a whole thread about returning to honeycomb via CWM and still having the reboots, etc.. Search it out...
Sent from my Transformer TF101 using Tapatalk 2
meinmichi said:
@basballfanz: how to root the 9.2.2.3 Firmware?
Click to expand...
Click to collapse
Don't think there's a way right now.
Can't you modify/use an ASUS Ota update package and use the stock recovery to 'Update' to HC. Reboot issues will still be there though.
Edit: as in when downgrading for razorclaw root etc
Thing O Doom said:
Can't you modify/use an ASUS Ota update package and use the stock recovery to 'Update' to HC. Reboot issues will still be there though.
Edit: as in when downgrading for razorclaw root etc
Click to expand...
Click to collapse
You can't downgrade on a stock tf.
The trick going from 8.6.5.21 to 8.6.6.19 to use razorclaw is technically an upgrade not downgrade. It was going from 8.6..5.21 to 8.6.6.19
Sorry I wasn't clear, I mean modifying a downgrade ASUS package to trick the Tf into Thinking that it's being updated.
Thanks for the version # clearup though X.x"
a simple rename do not work. Have taste it....
The tf see the update, reboot and start Update. But stoppt...
So what to do? Edit buildprob? Or what read the tf in Thema Update file ?
Get a hc package, unzip the ics package, delete and replace as needed. Probably need to edit build.prop too, and make sure the kernel flashes.
Or is a replace of the blob file the onky we need?
How is the chance of bricked?
Considering the kernel/os differences, higher than you'd want it to be, so I'd only do it as a last resort. Make a nandroid backup before doing any tinkering.
Cant do Backup without root. Thats why i want to downgrade...
Seems like a new method to downgrade from ICS to HC even for the non rooted users.
http://forum.xda-developers.com/showthread.php?t=1622628
THX thats works!
Can someone lead me or explain to me exactly what the s/n number means in terms of rooting and nvflashing. I have C30.
Sent from my Transformer TF101 using XDA
I think the real question here is why would you want to downgrade to HC from ICS? It's pretty well known that a full system restore fixes most issues.
miketoasty said:
I think the real question here is why would you want to downgrade to HC from ICS? It's pretty well known that a full system restore fixes most issues.
Click to expand...
Click to collapse
Why? Because ICS is completely un-stable on ALOT of TF101's (if not all). Honeycomb was rock solid.
Sent from my Transformer TF101 using Tapatalk 2
McSurge45 said:
Can someone lead me or explain to me exactly what the s/n number means in terms of rooting and nvflashing. I have C30.
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
First letter:
B=2011 & C=2012 manufacture year.
Second letter/number:
1=Jan 2=Feb ect till Oct which is A(hex)
So your C3O was manufacture in March 2012.
Only different is the SBK
ASUS changed the sbk mid July 2011.
miketoasty said:
I think the real question here is why would you want to downgrade to HC from ICS? It's pretty well known that a full system restore fixes most issues.
Click to expand...
Click to collapse
Except, it doesn't.
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).
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..