Database Info

[Q] System update file detected?

I got this message!!!Anyone else? Rooted ICS btw.

Save the file, it is in your cache.. then if it is the kernel update we can get it to thedevs to put into their custom ROM s

peshta said:
I got this message!!!Anyone else? Rooted ICS btw.
Click to expand...
Click to collapse
US?
Sent from my Transformer TF101 using Tapatalk

No system update message here on the East Coast as of this moment and I just checked..

vicw said:
US?
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
WW
@luna_c666 I'm kind of noob with this stuff and saw your post too late so instead of downloading the file i rebooted into recovery to make a backup, and then after reboot it just disappeared then i've checked manually for update trough settings-> about tablet -> system firmware update , but no luck.
My TF is B60 if it's matters.

If it's an OTA update, it will probably still be in /cache. You can copy it from there, although I don't know if all file managers will see it.
However, you might have the stock firmware on your external sd card- I think that is what generates that message.

gee one said:
If it's an OTA update, it will probably still be in /cache. You can copy it from there, although I don't know if all file managers will see it.
However, you might have the stock firmware on your external sd card- I think that is what generates that message.
Click to expand...
Click to collapse
Yeah, but i didn't download it. I thought that after nandroid backup, the update will still be there, but as I mentioned already the message disappeared.
Is there a log or something for this kind of messages?
Sent from my Transformer TF101 using XDA

Yep got the same notification today here in UK WW. I'm using the rooted stock ROM from our DEV section.( http://forum.xda-developers.com/showthread.php?t=1514658 )
Not going to run it tho as I'm @ a conference so don't want to rock the boat.
L
Sent from my Transformer TF101 using XDA Premium HD app

Win$t said:
Yep got the same notification today here in UK WW. I'm using the rooted stock ROM from our DEV section.( http://forum.xda-developers.com/showthread.php?t=1514658 )
Not going to run it tho as I'm @ a conference so don't want to rock the boat.
L
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
then post the file here ?? other wise it's a really useless post...

gkillerx said:
then post the file here ?? other wise it's a really useless post...
Click to expand...
Click to collapse
Like I said I am @ a conference, just answering the OP. Because it was obviously not just me who had this...
... And now like others the notification has gone now. No file I'm afraid.
Sent from my Transformer TF101 using XDA Premium HD app

I also got this message on my revolver 1.3.1, i clicked yes to let it download, but then nothing happened, no files in /cache, nothing....

gee one said:
If it's an OTA update, it will probably still be in /cache. You can copy it from there, although I don't know if all file managers will see it.
However, you might have the stock firmware on your external sd card- I think that is what generates that message.
Click to expand...
Click to collapse
That is exactly what it is. I had stock firmware on my external sd card. I received this notification after booting up for the first time after performing a return to stock via the official full download from asus' website. I deleted the file off of my sd card and rebooted. The message didn't come back.

[Q] How can I get root for .24?

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

Rooted Transformer Will Not Update From 4.0.3

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

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

OK, need someone to tell me what I'm missing please.
Yesterday I was on stock .30 and rooted. This morning I took the JB update. My first boot was OK and I still had root, but when I rebooted, I got stuck in a loop. It kept rebooting after getting to the desktop. I assumed at least one of my apps was causing it, so I used the wipe data function with the power + vol down thing. that wiped everything, including root.
I tried to re-do the debugfs method, but that seems to fail. Strange thing is, if I use adb shell from the computer, I can su - root and get root access. That's how I was able to give read/write access to the data folder where debugfs does its' work. It's just that root check says I'm not rooted. Voodoo OTA has all boxes checked on my root check, except the one that says granted root permissions. The SU file does exist inside /system/xbin
So it's as if the tablet's user just doesn't have permission to do root. I loaded a terminal emulator on the tablet, and tried to su - root that way, and got permission denied. I would normally get the "superuser" popup when doing something like that -
So there's definitely a piece I'm missing. Can someone point me in the right direction please?

reinstall ota rootkeeper and restore root. factory reset doesnt wipe root access you just need to restore it.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

jgaf said:
reinstall ota rootkeeper and restore root. factory reset doesnt wipe root access you just need to restore it.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Sorry, should have mentioned that I tried that. Attaching a screenshot as to what it looks like. Notice the center checkmark stating "root permission granted" is not checked, and there's no option to restore, only to remove or temp unroot, so it's like, everything is good, except for the actual root permission
Root checker shows red (no access) and root programs like root explorer do not prompt for superuser permission before running as I would expect them to the first time.

Did you run superuser? Did you reboot after running su for the first time?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

Absolutely, more times than I can count. Here's another shot showing I can't execute such but it seems to have global execute...
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Install supersu and not superuser....update the binary ...then try again
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

pakure said:
Install supersu and not superuser....update the binary ...then try again
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
OK, uninstalled superuser, and installed superSU as you suggested and rebooted the tablet for good measure.
Ran it, and it prompted me, saying su needed updating, said yes do it, came back to me "installation failed", which I honestly expected because for whatever reason, current tablet user cannot get to su, even though it appears permissions said it should.
One other note, earlier I tried to refollow these directions: http://forum.xda-developers.com/showthread.php?t=1704209
That is how I rooted when under build .30, no issues at all. This time I hit a snag when trying to push files to /data/local - said I had no permission. now I got around it via ADB by simply typing su - root....root seems to work when I'm in ADB, but it doesn't work via tablet interface. I don't know what I'm missing here....
Just a thought.. I was considering flashing back to .30 using fastboot but I wasn't sure if that would even work. I tried loading the .30 zip into the root of storage and it detected it, as a downgrade even and asked to proceed. When done I was still on 4.1.1 not the older build.
BTW, thank you for taking the time. I really don't mean to be a pain here. I've not had this much trouble before...

Well sh++ This would explain why I couldn't redo the debugfs root process...
http://forum.xda-developers.com/showthread.php?p=27990303
I decided to go have a look at the nexus 7 area since that's native JB and saw that. So' for those just buying this, you might want to root before you update.
Still doesn't explain my problem but at least explains why I can't use the solution that WAS good.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

funnel71 said:
Well sh++ This would explain why I couldn't redo the debugfs root process...
http://forum.xda-developers.com/showthread.php?p=27990303
I decided to go have a look at the nexus 7 area since that's native JB and saw that. So' for those just buying this, you might want to root before you update.
Still doesn't explain my problem but at least explains why I can't use the solution that WAS good.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I was able to restore my root. See this post.
http://forum.xda-developers.com/showthread.php?p=30481502#post30481502

I've really messed up now. Set perms wrong for the such that was on the tablet so now can't get root using adb either so unless there is a way to downgrade without root I'm screwed.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

I was so amped to grab JB, that I spaced that the OTA update would break root (i'm rooted but locked bootloader, b/c i was hoping 4.1.1 would come sooner than later!)
I had OTA rootkeeper installed, and while I was a little skeptical as to how easily it would work, it was 1-click simple and I just had to reinstall/update the binaries and reboot. I had the same check mark unchecked, but it worked, was straightforward, etc. It sounds like something got jacked in the JB flash, and I wonder if a full wipe/reset (&downgrade) to 4.04, re-root, then OTA update (using ota rootkeeper to hold root) might work for you?

thesuzukimethod said:
I was so amped to grab JB, that I spaced that the OTA update would break root (i'm rooted but locked bootloader, b/c i was hoping 4.1.1 would come sooner than later!)
I had OTA rootkeeper installed, and while I was a little skeptical as to how easily it would work, it was 1-click simple and I just had to reinstall/update the binaries and reboot. I had the same check mark unchecked, but it worked, was straightforward, etc. It sounds like something got jacked in the JB flash, and I wonder if a full wipe/reset (&downgrade) to 4.04, re-root, then OTA update (using ota rootkeeper to hold root) might work for you?
Click to expand...
Click to collapse
I would love to try the downgrade approach as that's the only one left I haven't tried, primarily because I have tried and haven't found a way to do it. If you know how with a locked boot loader then I'd love to hear.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

funnel71 said:
I would love to try the downgrade approach as that's the only one left I haven't tried, primarily because I have tried and haven't found a way to do it. If you know how with a locked boot loader then I'd love to hear.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
sorry, above my pay-grade at this point. I think i was overly optimistic about the "open-ness" of the device/bootloader (my other device is a galaxy nexus, so it's easy to do just about anything). I had a factory wipe or flash/img restore in my mind, but factory wipe wouldnt help (dont thinK), and If a stock 4.04 img exists, pretty sure there is a command set in fastboot that would let you restore using that image, but also pretty (99%) sure that requires an unlocked bootloader.
It sounds like there were a few changes in folder structure in JB that are limiting the root-ability, but my guess is the brainy folks around here will figure that out pretty quick, and JB will be root-able soon.

thesuzukimethod said:
sorry, above my pay-grade at this point. I think i was overly optimistic about the "open-ness" of the device/bootloader (my other device is a galaxy nexus, so it's easy to do just about anything). I had a factory wipe or flash/img restore in my mind, but factory wipe wouldnt help (dont thinK), and If a stock 4.04 img exists, pretty sure there is a command set in fastboot that would let you restore using that image, but also pretty (99%) sure that requires an unlocked bootloader.
It sounds like there were a few changes in folder structure in JB that are limiting the root-ability, but my guess is the brainy folks around here will figure that out pretty quick, and JB will be root-able soon.
Click to expand...
Click to collapse
Yes it's the /data folder where the exploit was and is causing the issue. I saw one of the commands was flash all, but I was too scared to try that. I tried the update.zip approach, but it came back with needed files weren't present in the archive.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

funnel71 said:
I would love to try the downgrade approach as that's the only one left I haven't tried, primarily because I have tried and haven't found a way to do it. If you know how with a locked boot loader then I'd love to hear.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
What did you do exactly? Details!
You can try this.... It may work... The worst case is that it just doesn't work. I have not seen a confirmation yet as to whether this method works or not yet.
https://www.dropbox.com/sh/jcpilpgoeta516e/QTl4TihVq0/Rooting-the-tf300.txt
---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------
calisro said:
What did you do exactly? Details!
You can try this.... It may work... The worst case is that it just doesn't work. I have not seen a confirmation yet as to whether this method works or not yet.
https://www.dropbox.com/sh/jcpilpgoeta516e/QTl4TihVq0/Rooting-the-tf300.txt
Click to expand...
Click to collapse
Oops. This is the whole link. Sorry about that. directions are in there.
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
---------- Post added at 03:11 PM ---------- Previous post was at 03:09 PM ----------
thesuzukimethod said:
I was so amped to grab JB, that I spaced that the OTA update would break root (i'm rooted but locked bootloader, b/c i was hoping 4.1.1 would come sooner than later!)
I had OTA rootkeeper installed, and while I was a little skeptical as to how easily it would work, it was 1-click simple and I just had to reinstall/update the binaries and reboot. I had the same check mark unchecked, but it worked, was straightforward, etc. It sounds like something got jacked in the JB flash, and I wonder if a full wipe/reset (&downgrade) to 4.04, re-root, then OTA update (using ota rootkeeper to hold root) might work for you?
Click to expand...
Click to collapse
If you have a check mark unchecked, you likely have root issues. Which check box?

calisro said:
If you have a check mark unchecked, you likely have root issues. Which check box?
Click to expand...
Click to collapse
Sorry - imprecise language on my part.
When I opened up OTA rootkeeper, it showed the same unchecked box (in rootkeeper) as others have mentioned, but I had "restore root" as an option. I did, and had no problems keeping root after updating to JB 4.1.1. OTA. I was using superuser but had checked "OTA survival" in Superuser's options, so I think that's how i kept root (seems like this "survival" option is baked in to Super Su, but a (non-default) option in Superuser).

[Q] How to reset update check to re get update notification after failure

so ya.. topic says it pretty much..
bunch of us i see on the other threads are rooted had a failure and would like to attempt again, but nobody saved the ww update patch so we need to re download it..
dmclient and cmclient have been force stopped and wiped clean
/data/ files associated with updating have been removed..
rebooted and nope no new update available..
what are we missing here?

I am afraid we may have to try a factory reset although I am holding out for a better alternative.
EDIT: Do not factory reset if you are rooted! On JB factory reset will delete root.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

How to restart failed 4.2.1 OTA(root required)
OTA file is here: http://www.mediafire.com/?3f13caikjfxoxpv
Copy dlpkgfile_4.2.1_Init to /cache, renaming it to dlpkgfile. Make a file in /cache/recovery named "command" with this in it:
Code:
--update_package=/cache/dlpkgfile
Boot into recovery by holding volume down and power button....then when you see text....hit the volume up button....and the update will go.
If the update fails, look at the logs in /cache/recovery to see what caused the failure.

bads3ctor said:
OTA file is here: http://www.mediafire.com/?3f13caikjfxoxpv
Copy dlpkgfile_4.2.1_Init to /cache, renaming it to dlpkgfile. Make a file in /cache/recovery named "command" with this in it:
Code:
--update_package=/cache/dlpkgfile
Boot into recovery by holding volume down and power button....then when you see text....hit the volume up button....and the update will go.
If the update fails, look at the logs in /cache/recovery to see what caused the failure.
Click to expand...
Click to collapse
that looks to be the same URL you posted for the US update or is it different?

Ashcunak said:
that looks to be the same URL you posted for the US update or is it different?
Click to expand...
Click to collapse
I didn't post it but it worked on my US TF300T. I had a failed update because I had deleted CMClient.apk and CMClient.odex and after fixing this problem, the above method got me to 4.2.1.

bads3ctor said:
I didn't post it but it worked on my US TF300T. I had a failed update because I had deleted CMClient.apk and CMClient.odex and after fixing this problem, the above method got me to 4.2.1.
Click to expand...
Click to collapse
Oh sorry, i shoulda capitalized it up in the first post of the thread or something.. were looking for WW not US :\

bads3ctor said:
I didn't post it but it worked on my US TF300T. I had a failed update because I had deleted CMClient.apk and CMClient.odex and after fixing this problem, the above method got me to 4.2.1.
Click to expand...
Click to collapse
Thank you for trying to help.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

As far as I can tell the new 4.2.1 ota update has not been released for WW yet only US.
Should hopefully be out by end of the month but have no confirmation on that.

pjc21 said:
As far as I can tell the new 4.2.1 ota update has not been released for WW yet only US.
Should hopefully be out by end of the month but have no confirmation on that.
Click to expand...
Click to collapse
It has been rolling out for the last two days, check this thread: http://forum.xda-developers.com/showthread.php?t=2181235
We got the OTA for WW, but it failed and therefore are trying to get the OTA to reset.

So far there have been alot of issues trying to root after the 4.2.1 ota which I'm on now. Was thinking of rooting as I've done all my other devices in the passed and just recently got this one but as of now there's an issues with the new bootloader encrypting the file system so recoveries can't mount the system. I was about to root before read that and unlocked my bootloader but i guess my question is is there any way to reflash the stock bootloader to lock it again as i also read that you can lose future otas after unlocking it. Any help appreciated thanks.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

The answer is still no. There is no going back once unlocked.
Sent from my SCH-I510 using xda app-developers app

Reilly1812 said:
The answer is still no. There is no going back once unlocked.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
Yea you can ignore the post was just hoping for a fix for the unlocked bootloader if were to effect future ota. Ill just monitor the threads for possible fix in future thanks anyway. Delete posts if need be.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

The topic of this thread is related to those on WW firmware with locked bootloaders that had a failed update, and are seeking a method to get the ota notification again.
Sent from my SGH-I747M using XDA Premium HD app

Still cannot reset ota check. Also, do not try a factory reset to get the ota if you are rooted, you will lose root. This sucks!
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

David Dee said:
Still cannot reset ota check. Also, do not try a factory reset to get the ota if you are rooted, you will lose root. This sucks!
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
ya its odd this time, i swore before we were able to reset this to try again...

Ashcunak said:
ya its odd this time, i swore before we were able to reset this to try again...
Click to expand...
Click to collapse
I had problems with the JB update back in August, but I was able to reset constantly by the CM / DM cache delete. This time something is definitely different. We need to the find the ota file. Alternative is to unlock.

no luck yet anyone?

Nothing on my end.
Sent from my SGH-I747M using XDA Premium HD app