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).
Related
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.
This apparently has been like this for some time but, my daughter has just brought it to my attention.
I have not kept up with this like I should have recently so, Im sure I have forgotten/missed something
Transformer (US) is rooted and on 4.0.3 (9.2.1.11) There is an update available from ASUS but, each time we have tried it, it fails and goes to the exclamation
triangle.
My first thought it is a firmware update from ASUS and the tablet is rooted so it wont take it....am I right or ?
What do I need to do to get her tablet up to date with the latest and greatest? Going to try and read some more on
the forums and see if I can get it figured out.
Thanks ahead of time!
tarheelbuc said:
This apparently has been like this for some time but, my daughter has just brought it to my attention.
I have not kept up with this like I should have recently so, Im sure I have forgotten/missed something
Transformer (US) is rooted and on 4.0.3 (9.2.1.11) There is an update available from ASUS but, each time we have tried it, it fails and goes to the exclamation
triangle.
My first thought it is a firmware update from ASUS and the tablet is rooted so it wont take it....am I right or ?
What do I need to do to get her tablet up to date with the latest and greatest? Going to try and read some more on
the forums and see if I can get it figured out.
Thanks ahead of time!
Click to expand...
Click to collapse
I cant remeber if rooting disables the asus updates. alternativly you can use one of these:
If you have CWM installed you can use this: (http://forum.xda-developers.com/showthread.php?t=1627301)
If you don't have CWM you can use easyflasher: (http://forum.xda-developers.com/showthread.php?t=1688012)
If you want that lastest and greatest u'll need a custom rom :good:
If you have any other recovery or changed any /system/apps you will not be able to do the below. How did you Root your TF?
If you are completely stock with stock recovery, then all you need to do is download OTA Rootkeeper from the market. Open it up, grant SU permission and run it. Once complete, you can hit Temp Unroot and then take the OTA from Settings>About Device. Once your TF is rebooted, then just open OTA Rootkeeper again and hit Restore Root. There you go.
If you do have a custom recovery or changed some /system/apps, then you shoudl follow Jointherealms post. Otherwise there is no need to do all that.
One caveat to OTA Rootkeeper is the latest edition does save a back up of Root however it doesn't save it to /system/xbin anymore for some reason. This can cause some problems with apps looking for Root. So once you get your TF rebooted back up with Root, I suggest going into /system/bin and scroll down and copy SU and paste it in /system/xbin.
Thanks for the replies!
I do have CW recovery installed so, will give that a shot later this evening after work and see what happens.
Appreciate the help...I need to do a better job of keeping up with these things!
Thank you!
Woodrube said:
If you have any other recovery or changed any /system/apps you will not be able to do the below. How did you Root your TF?
If you are completely stock with stock recovery, then all you need to do is download OTA Rootkeeper from the market. Open it up, grant SU permission and run it. Once complete, you can hit Temp Unroot and then take the OTA from Settings>About Device. Once your TF is rebooted, then just open OTA Rootkeeper again and hit Restore Root. There you go.
If you do have a custom recovery or changed some /system/apps, then you shoudl follow Jointherealms post. Otherwise there is no need to do all that.
One caveat to OTA Rootkeeper is the latest edition does save a back up of Root however it doesn't save it to /system/xbin anymore for some reason. This can cause some problems with apps looking for Root. So once you get your TF rebooted back up with Root, I suggest going into /system/bin and scroll down and copy SU and paste it in /system/xbin.
Click to expand...
Click to collapse
JoinTheRealms said:
I cant remeber if rooting disables the asus updates. alternativly you can use one of these:
If you have CWM installed you can use this: (http://forum.xda-developers.com/showthread.php?t=1627301)
If you don't have CWM you can use easyflasher: (http://forum.xda-developers.com/showthread.php?t=1688012)
If you want that lastest and greatest u'll need a custom rom :good:
Click to expand...
Click to collapse
Ok, this failed with the following:
assert failed: apply_patch_check("/system/app/Applocker.odex". "f6e13482721276b130934ecff042404fbf3f5f45". "5197baa5a21df8a69c870f7ea658d6955f18f92e")
E: error in /sdcard/ww-9.2.1.17-to-9.2.1.21-CWM-rooted-v1.0.zip
(status 7 )
Installation aborted.
I read elsewhere in that thread (I think) that this is for .21...did it fail because Im on .11?
Woodrube said:
If you have any other recovery or changed any /system/apps you will not be able to do the below. How did you Root your TF?
If you are completely stock with stock recovery, then all you need to do is download OTA Rootkeeper from the market. Open it up, grant SU permission and run it. Once complete, you can hit Temp Unroot and then take the OTA from Settings>About Device. Once your TF is rebooted, then just open OTA Rootkeeper again and hit Restore Root. There you go.
If you do have a custom recovery or changed some /system/apps, then you shoudl follow Jointherealms post. Otherwise there is no need to do all that.
One caveat to OTA Rootkeeper is the latest edition does save a back up of Root however it doesn't save it to /system/xbin anymore for some reason. This can cause some problems with apps looking for Root. So once you get your TF rebooted back up with Root, I suggest going into /system/bin and scroll down and copy SU and paste it in /system/xbin.
Click to expand...
Click to collapse
Honestly, I dont recall how I rooted it! It has been that long.
I know I have CW 3.2.0.1 on it and as far as I know..it is simply stock rooted. No custom roms and no files changed or deleted (to my knowledge...keep in mind...my 14 yo daughter uses this daily and I havent touched it in several months)
I also dled OTA RK and tried to dl the update and it failed as well. (yellow triangle)
I tried to unroot with RK and check update in system settings but, check firmware tab is not highlighted. I tried to click on the asus system firmware popup and it goes to install...and then comes back to yellow triangle.
Possible she changed deleted something that is causing this to fail?
Try booting into recovery to see if you're still on cwm or not. The yellow triangle sounds like it's stock recovery.
Vol down plus power till you see prompt at left top corner, immediately push Vol up to get into recovery.
baseballfanz said:
Try booting into recovery to see if you're still on cwm or not. The yellow triangle sounds like it's stock recovery.
Vol down plus power till you see prompt at left top corner, immediately push Vol up to get into recovery.
Click to expand...
Click to collapse
Yep, boots into CW recovery just perfectly. Tried to install the files from the sd card in the first post and get the error I posted earlier
tarheelbuc said:
Yep, boots into CW recovery just perfectly. Tried to install the files from the sd card in the first post and get the error I posted earlier
Click to expand...
Click to collapse
Why don't you try installing a custom ROM.... either revolution HD or revolver ICS... both are rooted and tweaked stock ROMS... try them... just be sure to do factory reset/wipe, cache wipe and dalvik wipe before installing any ROM.. good luck
Link for revolution HD ROM
http://forum.xda-developers.com/showthread.php?p=17202357
Link for revolver ICS ROM
http://forum.xda-developers.com/showthread.php?p=23000467
Sent from my Transformer TF101 using xda app-developers app
---------- Post added at 05:17 AM ---------- Previous post was at 05:15 AM ----------
tarheelbuc said:
Yep, boots into CW recovery just perfectly. Tried to install the files from the sd card in the first post and get the error I posted earlier
Click to expand...
Click to collapse
Also one question... where did you download the ROM from ? The one you are trying to flash?
Sent from my Transformer TF101 using xda app-developers app
With CWM you will not be able to apply the OTA update.
You could just flash an update that's in cwm flashable zip
http://forum.xda-developers.com/showthread.php?p=25486812
udupa82 said:
Why don't you try installing a custom ROM.... either revolution HD or revolver ICS... both are rooted and tweaked stock ROMS... try them... just be sure to do factory reset/wipe, cache wipe and dalvik wipe before installing any ROM.. good luck
Link for revolution HD ROM
http://forum.xda-developers.com/showthread.php?p=17202357
Link for revolver ICS ROM
http://forum.xda-developers.com/showthread.php?p=23000467
Sent from my Transformer TF101 using xda app-developers app
---------- Post added at 05:17 AM ---------- Previous post was at 05:15 AM ----------
Also one question... where did you download the ROM from ? The one you are trying to flash?
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
I went head and flashed the revolution rom and it went thru perfectly fine..thank you.
I use "my backup" on my Galaxy Nexus to backup before updating and I did the same with the Transformer. Is there anything that is better to use on the TF rather than my backup when updating? Other than that and restoring the apps, everything looks fine at the moment.
In my first post, it wasnt a ROM I was trying to flash, it was an update from ASUS for the firmware. After reading the post for the member below your last post...you cannot do OTA updates after rooting...maybe I had brain freeze or something. She simply brought it to me, I tried to update it, it would not work so, I came here to figure out why!
Maybe it was a "pre-senior" moment I had but, after flashing Revolution...everything is great other than restoring apps!
I do greatly appreciate the help!
baseballfanz said:
With CWM you will not be able to apply the OTA update.
You could just flash an update that's in cwm flashable zip
http://forum.xda-developers.com/showthread.php?p=25486812
Click to expand...
Click to collapse
That right there may have been my issue all along..it is rooted and was running stock but would
not take the OTA...I upgraded to revolution and now everything seems perfectly fine
Thank you for the help!
tarheelbuc said:
I went head and flashed the revolution rom and it went thru perfectly fine..thank you.
I use "my backup" on my Galaxy Nexus to backup before updating and I did the same with the Transformer. Is there anything that is better to use on the TF rather than my backup when updating? Other than that and restoring the apps, everything looks fine at the moment.
In my first post, it wasnt a ROM I was trying to flash, it was an update from ASUS for the firmware. After reading the post for the member below your last post...you cannot do OTA updates after rooting...maybe I had brain freeze or something. She simply brought it to me, I tried to update it, it would not work so, I came here to figure out why!
Maybe it was a "pre-senior" moment I had but, after flashing Revolution...everything is great other than restoring apps!
I do greatly appreciate the help!
Click to expand...
Click to collapse
For restoring apps try titanium backup.. but remember don't backup app data just apps.. coz sometime app data messes ROM up.. if you like to do nand backup then go to recovery and do a backup of the installed ROM.. I always have one coz I have fallback option if I need it.. you can always flash rooted stock ROM but problem with them is, whenever Asus pushed an update you will see them and trying the latest update usually breaks or tablet... so stick with rooted OS.... also try jellybean ROMs when they become stable... much more smoother than ICS....
Sent from my Transformer TF101 using xda app-developers app
Wanted to thank everyone in this thread again. Sorry it has been a couple of days since Iast checked in...life happens! Now, the transformer is screaming along..everything is fine now and my daughter thanks you!
Now let me straggle on over to the Galaxy Nexus forum to see if I want to replace the screen in her Nexus that she just happened to break the day after I got the transformer up and running!
It never ends!
tarheelbuc said:
Wanted to thank everyone in this thread again. Sorry it has been a couple of days since Iast checked in...life happens! Now, the transformer is screaming along..everything is fine now and my daughter thanks you!
Now let me straggle on over to the Galaxy Nexus forum to see if I want to replace the screen in her Nexus that she just happened to break the day after I got the transformer up and running!
It never ends!
Click to expand...
Click to collapse
Hahahaha... sorry but that was just funny so good luck
Sent from my Transformer TF101 using xda app-developers app
I rooted my Infinity a few days ago, and I changed my mind. How the heck do I unroot? I cannot find the answer anywhere...
Before root the boot time was under a minute by far, now it is 3 minutes and 45 seconds...this can't be right.
Anyone know why this is happening or how I can fix it? If not can anyone tell me how to unroot please?
Thanks.
I rooted my tf700 and the boot is like unrooted, under 1 minute.
Have you tried to make a cold reboot?
If you want to unroot, i've used the method described in this post to unroot my previous tf300 before returning it.
http://forum.xda-developers.com/showthread.php?t=1622628
It had worked fine.
I've used 'Method 1 - Rooted' instructions.
You have to download the blob corresponding to your tf700 from asus and with adb write it to the tf700
Just remove /system/xbin/su (as root) and uninstall Superuser app, but this is user-based, so I doubt anything on the boot uses root privileges differently just because suddenly you have the binary there.
Are you sure you haven't installed any apps or new firmware lately?
Or just Factory Reset if your really desperate. Root gone.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
jjdevega said:
Or just Factory Reset if your really desperate. Root gone.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
I don't think that a factory reset removes root.
Don't ask me to prove it, i don't want to reinstall my Tf700
htcvidi said:
I don't think that a factory reset removes root.
Don't ask me to prove it, i don't want to reinstall my Tf700
Click to expand...
Click to collapse
Correct. Factory reset means wiping the /data partition, for which there is no reason in this case. Re-flashing firmware sometimes wipes /system, sometimes just overwrites the files on it (normally leaving /data intact), which will lead to removing "su" most of the time (Superuser.apk stays in /data, but can be easily uninstalled). If someone has used RootKeeper, it can leave a copy of "su" somewhere on the system partition, too, but can be removed from within the app.
I just wanted to understand where I am and what happened.
I have a locked boot loader TF300T, it came with .30.
I rooted with the debugfs root process.
I downloaded and ran OTA root keeper,
and saved root.
Later JB was offered to me. I took the update
and lost root. I thought I had to rerun the
debugfs script again, but that doesn't work
in JB.
After a reboot, I re-downloaded and reinstalled
OTA root keeper, and it prompted me to restore
root. After another reboot, root is back.
I'm guessing whatever the debugfs script did
to get root is fixed in 4.1.1, but OTA root
keeper was successful in doing its job.
So I have root again in a locked otherwise
stock TF300T with JB 4.1.1.
Did I do it right?
Do I understand correctly?
If you have a root checker, run it to make sure. Just search for root check in the market. If you still have root, then you are lucky. Many others have lost half or all their root access.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Results of checker
funnel71 said:
If you have a root checker, run it to make sure. Just search for root check in the market. If you still have root, then you are lucky. Many others have lost half or all their root access.
Click to expand...
Click to collapse
Checker reports success
That's pretty cool that you kept it. Don't do a data wipe or you won't be able to get it back without unlocking the bootloader.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Followup Root on TF300T & 4.1.1 OTA
I'm hoping the nice folks here will figure out
a new way to root for jelly bean eventually.
I personally do not like ASUS's approach
of blacklisting unlocked serial numbers.
Realisticly, while some issues can be
caused by bad flashes. There are still
real hardware failures that should
be covered by warranty regardless
of content.
Loose ports or other obvious deflects,
for example. They would be there stock or
not.
For the time being, I'm staying locked
& rooted. At least I can use root apps
to backup apps and data.
That's pretty good thinking. I feel the same, hence waiting for a stock and lock root solution.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
fuzzynco said:
I'm hoping the nice folks here will figure out
a new way to root for jelly bean eventually.
I personally do not like ASUS's approach
of blacklisting unlocked serial numbers.
Realisticly, while some issues can be
caused by bad flashes. There are still
real hardware failures that should
be covered by warranty regardless
of content.
Loose ports or other obvious deflects,
for example. They would be there stock or
not.
For the time being, I'm staying locked
& rooted. At least I can use root apps
to backup apps and data.
Click to expand...
Click to collapse
funnel71 said:
That's pretty good thinking. I feel the same, hence waiting for a stock and lock root solution.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
+1... The desire to upgrade to JB has been eating me up but at only 3 weeks old I want to keep my tf300t locked a little while longer. And I also think the blacklist thing is a poor testament to ASUS's customer support. As a VAR I sold a lot of their product and had few issues, but their attitude toward open source is lame. If I wanted to be treated like an Ipad owner I would have bought an Ipad.
The upgrade bug had me so bad that I did put JB on my SGSII4G since I can restore that without issue. Really was not all that impressed. I agree with what others have said it is a resource hog. I know that is not as big a deal with android but it is getting kind of windoz like (every release is 33% fatter (IMHO). And Flash does have issues with the Bean.
For now I will stay with rooted ICS on the ASUS until I'm comfortable with the reliability or their is a truly safe way to run Bean. Anyone know how to get rid of this annoying upgrade nag screen, besides upgrading?
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