Related
I rooted my transformer using the pure root method in the development transformer forums for devices that already received 3.1. People have said that they receive their update and unroots their device, but I haven't even received the FOTA. I only rooted my device; without clockwork or a custom rom. I did delete some pre installed programs (bloatware) with titanium backup but I re installed them. Not sure if the damage has been done but I want someone to confirm if that can be the issue and how do I go about to properly reinstall the bloatware.
I know .11 will not install on a rooted device. I even unrooted several different ways installing the normal software from the asus site and never could get ota working... I am wondering if any others have got updates working after unrooting... (ended up exchanging at Best Buy for a new one....
Danny80y said:
I know .11 will not install on a rooted device. I even unrooted several different ways installing the normal software from the asus site and never could get ota working... I am wondering if any others have got updates working after unrooting... (ended up exchanging at Best Buy for a new one....
Click to expand...
Click to collapse
I am having the exact same problem and a lot of people will. Once you root and try to unroot it appears you cannot receive anymore OTA or make them work for that matter. I have found how to get the notification telling me that the .11 update is available for me. (Place the update file in sdcard/asus/update/) and then rename it US_epad-user-8.4.4.11.zip and rebooting. After this you can choose to make the update but it will not work. It will just go to the stock recovery with the android and the exclamation after a one second loading appearing that it will work. After you turn it off and back on it will tell you (System Update Failed Error (12) )Still trying to figure out why it is not accepting the update.
You can get the update in the "Just got an OTA update" thread.
Thank you for that valuable information. It worked like a charm. Now I just need the original update for the dock.
Sent from my Nexus S 4G using Tapatalk
...................
martijua said:
You can get the update in the "Just got an OTA update" thread.
Click to expand...
Click to collapse
I guess I'll have to manually install. Let's see how it turns out...
for just patiently wait for FOTA or rooted repack... The improvements are not HUGE.
TheIneffable said:
I guess I'll have to manually install. Let's see how it turns out...
Click to expand...
Click to collapse
Didn't even work. I guess my device is not recognizing the file or something. I guess I'll have to wait or probably get use to installing roms
TheIneffable said:
Didn't even work. I guess my device is not recognizing the file or something. I guess I'll have to wait or probably get use to installing roms
Click to expand...
Click to collapse
Did you tried the explanation give in the thread that the guy on top of my post suggested? It helped me out.
Sent from my Transformer TF101 using Tapatalk
Meh I am givin up for today. Flashed back to stock recovery, plopped the update package on a card in the format of EP101_SDUPDATE.zip, reboot to stock recovery, just kept getting the exlamation point. Can't flash the thing any other way either.
Guess I'll wait for a rooted 3.2 to come out.
You are not suppose to rename the file. Extract the contents of the ZIP file to the ROOT DIRECTORY of the MicroSD card.
Works everytime for me....while the renaming of the file never worked for me.
It's weird because, I downloaded the txt, and rename it, placed it on the root of the so card and the update passed flawlessly.
Sent from my Transformer TF101 using Tapatalk
Fixter said:
Did you tried the explanation give in the thread that the guy on top of my post suggested? It helped me out.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
"Then press volume up when you see the text on the top left of the screen"
I did it just how the instructions stated but I never saw the text on the top left of my screen. It just boots up normally with stock boot animations. The update notification is not present either. I guess I'll try and see if not renaming it might help. Even though I don't think leaving the file extension to just "file" will help. I'll try...
Digiguest said:
You are not suppose to rename the file. Extract the contents of the ZIP file to the ROOT DIRECTORY of the MicroSD card.
Works everytime for me....while the renaming of the file never worked for me.
Click to expand...
Click to collapse
hmm...Probably because you extracted the .zip to the SD card. It just stated to move the .zip to the sd card. Maybe extracting might work.
None of the methods worked. Guess I'll be installing roms. I guess when I deleted some of the preinstalled apps, my device became disqualified for any sort of updates.
I don't understand most of you. You buy this stuff as early adopters, complain about the price, then ***** about how it "doesn't work", then hack/break it and then complain i doesn't update properly or whatever. Then come on here and piss all over the vendor.
Really?
superevilllama said:
Meh I am givin up for today. Flashed back to stock recovery, plopped the update package on a card in the format of EP101_SDUPDATE.zip, reboot to stock recovery, just kept getting the exlamation point. Can't flash the thing any other way either.
Click to expand...
Click to collapse
Read the first post of this thread to properly flash the update when renamed to ep101_sdupdate.zip:
http://forum.xda-developers.com/showthread.php?t=1171116
Carl LaFong said:
I don't understand most of you. You buy this stuff as early adopters, complain about the price, then ***** about how it "doesn't work", then hack/break it and then complain i doesn't update properly or whatever. Then come on here and piss all over the vendor.
Really?
Click to expand...
Click to collapse
haha. Who's *****ing? My transformer still works great. Just wanted to diagnose why I wasn't getting an update so I can be more informed about it and see if I should just stick to installing roms or unroot.
Right. That says exactly what I just said, and did. Anyway.. I eventually got it to work. I had to go compeletly back to stock as apparently deleting stuff from the stock rom altered it enough that the update didn't see it as the same rom.
Tried to root after and got froze up at the boot screen like everyone else. Been playing with this too long. Understanding that we risk messing up our devices by rooting and such.. other issues that are in complete control of Asus such as build quality... IE light bleed, bezel issues, freezing, touch screen not sensing touch are making me rethink this product. Sigh. Sucks too because the idea is awesome. Just wish the build quality was there.
i have stock 4.0.3. I try to download the OTA 4.0.4 but I get the red triangle with the green android as it is trying to install. did these steps and it still won't update:
1. go to setting / apps then hit the all button at the top
2. scroll down to google services framework and then press it to open
3. hit the clear data button
4. go to settings / about phone / system updates (you will notice the date will be 1969 or 1970 this is ok )
5. hit the check now button
6. xoom should show you the 4.0.4 update avalaible
7. hit install and enjoy
any suggestions?? seems like I have to send it in to Motorola for them to manually flash this update
a bunch of users in the Official Motorola forum also have this issue: https://forums.motorola.com/posts/0212457c59
vinnyt225 said:
i have stock 4.0.3. I try to download the OTA 4.0.4 but I get the red triangle with the green android as it is trying to install. did these steps and it still won't update:
1. go to setting / apps then hit the all button at the top
2. scroll down to google services framework and then press it to open
3. hit the clear data button
4. go to settings / about phone / system updates (you will notice the date will be 1969 or 1970 this is ok )
5. hit the check now button
6. xoom should show you the 4.0.4 update avalaible
7. hit install and enjoy
any suggestions?? seems like I have to send it in to Motorola for them to manually flash this update
a bunch of users in the Official Motorola forum also have this issue: https://forums.motorola.com/posts/0212457c59
Click to expand...
Click to collapse
It's because you're not using a stock recovery. Go into your /cache folder, pull the file out of there and put it on your internal storage somewhere, then go into whatever recovery you use and flash the zip file.
You can only do the auto OTA installs if you're using stock recovery. Otherwise, you have to flash manually. Just the way it is.
thanks for the reply oldblue910. I don't have any zip files anywhere. Everything i am trying to do is over the internet. But if you could guide me your process maybe i'll try your way.
vinnyt225 said:
thanks for the reply oldblue910. I don't have any zip files anywhere. Everything i am trying to do is over the internet. But if you could guide me your process maybe i'll try your way.
Click to expand...
Click to collapse
OK first off, I assume you're rooted, yes?
i am not rooted...forgot to say that. completely stock. tablet came with 4.0.3 and was new out of the box.
vinnyt225 said:
i am not rooted...forgot to say that. completely stock. tablet came with 4.0.3 and was new out of the box.
Click to expand...
Click to collapse
Interesting...the OTA should apply fine then. OK here's the next thing. Go and flash the OTA as normal. Once it gets to the Android with the red triangle, press and hold the power button, then press volume up (while holding down the power button). Some text will appear on screen. Please post that text here.
oldblue910 said:
Once it gets to the Android with the red triangle, press and hold the power button, then press volume up (while holding down the power button). Some text will appear on screen. Please post that text here.
Click to expand...
Click to collapse
Same exact issue here!!!!
I did that, and it reads in yellow text:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
That means for some reason the downloaded file is corrupt...hmmm....not quite sure on that one...
Sent from my Xoom using Tapatalk 2
From what I can read, the only way to get 4.0.4 is to either root of send it in to Moto. Here is a link that I read that is about the same issue.
*** I tried to post the link but since I am a new member I can't post outside links. It is on the motorola xoom owner's forum
False. If you haven't dicked around with your tablet and wait for the OTA notification like a good boy, it installs fine.
Sent from my Xoom using Tapatalk 2
I'm having the exact same issue, and I'm two for two on brand new Xoom's that will not install the update right out of the box.
---------- Post added at 07:11 PM ---------- Previous post was at 06:21 PM ----------
MikeMBau said:
Same exact issue here!!!!
I did that, and it reads in yellow text:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
I'm getting the same text(obviously), but at the top of the screen, are you guys seeing these 4 options:
reboot system now
apply update from USB drive
wipe data/factory reset
wipe cache partition
?
I'm sure you are. The one I'm interested in is the "apply update from USB drive", because someone at Xoom Forums suggested doing the update from a USB drive, but with a USB host cable, and it was a different method than what I think this option is suggesting, but mu understanding is that using a USB host cable doesn't work with an unrooted Xoom.
This option makes me curious.......and I'm wondering if it would see the update on a USB drive attached to the Xoom, should you have it attached with the stock 4.0.4 zip file on the USB drive, and selected this option.
I'd never do it unless someone said it would work.
All that being said, it also seems that if you installed a recovery, and rooted it, that you could flash the stock 4.0.4, but I'm just assuming that's right.
You know guys, I totally forgot about this...
If you are on 4.0.3 and trying to update manually to 4.0.4 in stock recovery via OTG cable, you will not be able to. There is a bug in the stock recovery that only allows flashing OTAs when using the OTA notification software, and will fail if attempted manually.
This topic was beat to death when the 4.0.4 OTA for the WiFi Xoom came out back in April. The Nexus S had the same problem as well because of the same stock recovery bug. If you want to read up on it, just do some searching here on XDA. There was a ton of chatter about it.
Sent from my Xoom using Tapatalk 2
oldblue910 said:
If you are on 4.0.3 and trying to update manually to 4.0.4 in stock recovery via OTG cable, you will not be able to.
Click to expand...
Click to collapse
Nope, this is all in reference to OTA updates. None of us are attempting to install it manually. It is a known issue with this device.
I don't get why you think I "dicked around" with my tablet... I got it in the mail, saw it was on 4.0.3 and just went to settings>about tablet>system updates. I haven't "dicked around" at all.
Do you have any other ideas in order to get 4.0.4 on my Xoom? Is the USB host cable worth a shot?
This is what someone on the Motorola support forums had to say about this:
I agree with the possibility that the OTA package could be corrupt and there are theories out there that Google's process is causing the issue, but no confirmation. The problem with the storage of Android OTA images is that they reside in a system partition without user accessibility, so if they are corrupt, the system just keeps trying to install it.
Let me share your details with the Motorola Tech I have been working with and see what your upgrade status shows.
I submitted a ticket online to send my Xoom in, but I am uncomfortable doing that. If someone told me that the USB works, then I would rather do that instead.
MikeMBau said:
I submitted a ticket online to send my Xoom in, but I am uncomfortable doing that. If someone told me that the USB works, then I would rather do that instead.
Click to expand...
Click to collapse
Yeah, I haven't pulled the trigger on that decision yet. I have to sleep on it. I told the one guy I talked to, who was "level 2"......Motorola is doing nothing about this. He said "we are doing something........we'll send you a box". Great answer.
On the USB thing.....I feel the same way, but sounds like you have to root it to do that. If I root it, it will be because I want to, and right now I don't. I just bought it. I'm on my second one in 3 days that has the same issue. If I root it, I'm going to cut to the chase and just flash a custom ROM, and I won't have to worry about updates. Right now I just don't want to do that.
On a side note, make sure they're real clear on what the issue is with your Xoom. The reason I say that is that I saw one lady post on the Motorola support forums that she has two Xooms that she bought at the same time, with the same issue you and I have, and they simply put "repair" in the notes. She got them both back, and they still had 4.0.3 on them, and wouldn't update. Read the second post on this page, from "Sharon"
https://forums.motorola.com/posts/0bc09ed02d?commentId=613182#613182
Totally ridiculous.
I was just about to say "screw it" and send it in, and then read that. I'd go through the roof if that happened to me. I still might send it in, but I'm just really uncomfortable doing that with something that has an issue right out of the box, but I don't want to keep sending them back to Amazon, with the hope that the "next one" will update correctly.
Trust me.......any method that would work to resolve this, that didn't involve rooting the damn thing, I'd be all over, just like you.
Just read this post from a guy on the Motorola support forums that has been talking to a Motorola tech he knows:
"The Android OS always downloads an update first (to a system-only partition), does a basic validation (like total size) and then applies the update to your system. What I have heard from other developers is that if the update fails (for any reason), the OS does not download a new copy nor delete the current image, it just keeps trying to reinstall the same image. If that is true, then someone (like the service center) may have to unlock the Xoom and apply a new image to resolve the issue."
MikeMBau said:
I submitted a ticket online to send my Xoom in.
Click to expand...
Click to collapse
So did I.......not crazy about it either.
MikeMBau said:
I submitted a ticket online to send my Xoom in, but I am uncomfortable doing that.
Click to expand...
Click to collapse
Did you end up sending it in after all? I sent mine, they got it the next day, the repair status says closed, and hopefully it will ship back today, and be here tomorrow.
I'm at wit's end here...
I had to get a replacement TF300, and it came with .26. I downgraded to .17, rooted, OTA Rootkeeper'ed SU, then accepted the OTA update.
The update FAILED (green robot with red ! above). I powered down, rebooted.
Since then, I cannot get my device to find any OTA updates. I tried manually installing .29 - then no update. I installed .30 manually .. no update to JB.
I've force stopped DMClient and CMClient - cleared data/cache and cold booted as directed from some other posts.
Still no OTA.
While I realize I can do manual updates from this point forward, I'd like JB back - and so far, no manual installer of that.
I appreciate any help - this is making me nuts.
darkuni said:
I'm at wit's end here...
I had to get a replacement TF300, and it came with .26. I downgraded to .17, rooted, OTA Rootkeeper'ed SU, then accepted the OTA update.
The update FAILED (green robot with red ! above). I powered down, rebooted.
Since then, I cannot get my device to find any OTA updates. I tried manually installing .29 - then no update. I installed .30 manually .. no update to JB.
I've force stopped DMClient and CMClient - cleared data/cache and cold booted as directed from some other posts.
Still no OTA.
While I realize I can do manual updates from this point forward, I'd like JB back - and so far, no manual installer of that.
I appreciate any help - this is making me nuts.
Click to expand...
Click to collapse
im in the same boat as you i would also like help
joeyman08 said:
im in the same boat as you i would also like help
Click to expand...
Click to collapse
I am also in the same boat as I have an unlocked bootloader and will no longer receive OTA's from ASUS. We just have to be patient for another day or 2 and ASUS will post the JB Firmware on their site here:
http://support.asus.com/download.as...er Pad TF300T&os=32&hashedid=8BmzkQ4yoz5WzBrW
---------- Post added at 10:17 AM ---------- Previous post was at 10:11 AM ----------
But who wants to be patient. THere is always the option of updating manually. Thank krabappel2548 for this one!
http://forum.xda-developers.com/showthread.php?t=1845377
I will give the manual update a go. Thanks!
The manual process requires unlocking the bootloader. Not sure I'm ready to do that.
I'm open to other options.
darkuni said:
The manual process requires unlocking the bootloader. Not sure I'm ready to do that.
I'm open to other options.
Click to expand...
Click to collapse
Don't do all that crap. Do this. I did. Others as well.
Reference: http://forum.xda-developers.com/showthread.php?t=1840540
1) Found the correct OTA file. Someone posted it here for my US MODEL. If your WW or JP or something else, you'll need a different file.
http://forum.xda-developers.com/show...840397&page=11
2) I downloaded that file, named it dlpkgfile and put it in /cache/ (I also kept a copy in /sdcard so I can simply recopy it if/when it failed to update because of some missing app or something again)
3) I created a file called 'command' and put it in /cache/recovery with the contents of that file being as follows(without quotes): "--update_package=/cache/dlpkgfile". (I also kept a copy in /sdcard so I can simply recopy it if/when it failed to update because of some missing app or something again)
4) Now just run the update. To do this, make sure you do all your prep work (Voodoo OTA root keeper, supersu binary installed and run at least once, all original system apps in place. yada yada yada. To run the update shut down your tf300. and then start it holding the POWER and VOLUME DOWN. Keep holding it until you see writing appear. when the writing appears release and press VOLUME UP within 5 seconds of those words appearing.
5) you'll see the normal asus upgrade spin up.... and either complete or fail. If it fails, check your log file in /cache/recovery and see WHY it failed. Fix why it failed, and restart from step 1.
We have a winner! I had the command and dlpkg file ... what I didn't have was the boot process to enact it.
WONDERFUL! I'm safe for one more update
We are running HYDRO 4.4-(8/10) and got a message System update file detected. I downloaded the US JellyBean drivers, but fear if I simply click on the install, something will go wrong.
Am I right?
soccerdude123 said:
We are running HYDRO 4.4-(8/10) and got a message System update file detected. I downloaded the US JellyBean drivers, but fear if I simply click on the install, something will go wrong.
Am I right?
Click to expand...
Click to collapse
Most likely the update is going to fail, anyways since you are unlock just upgrade to seanzscream's new JB rom.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Bumping an old thread here, but is there a way to remove the update notification?
About the time JB was released I checked for an update not realising that it would go ahead without confirmation. As I didn't want to update just then I cancelled the download by clearing data in CM & DMclient (seemed to be the only way after turning wifi off).
Recently I just rooted (locked) using the debugfs method, after which checking for updates comes back with a zilch.
I tried clearing DM/CMclient data again and removing the update files :
fw_update_progress & isp_fw_progress
These had java errors in them presumably because I had aborted. After trying again they hold "0" and "100" in text format.
Finally on someone's recommendation I did a full factory reset (which worked for him) but I'm still without OTAs.
I'm hoping someone can shed some light on what may be the problem. AFAIK just rooting doesn't kill OTAs yet something has. Does Asus perhaps keep a database record as to what has been downloaded? I somehow doubt it but with a full factory reset I fail to see what's stopping these updates.
Any help , suggestions appreciated.
I dont know if the OTA is operational again, but a lot of people like myself never received any automatic updates for a brand new stock infinity on the 11th. You might might want to try a manual update. Here is my post on the other threads on what I did to manual update to 4.1.1.
"I just returned a prime today that I bought for a friend in exchange for a C8 infinity. Tablet didnt want to update to JB and was stuck on 4.0.3. So I used my laptop and went to the Asus support download site, download 4.1.1 US version, unzipped it and another zipped file came up, Plugged the infinity to the laptop via Asus cable, copied the second zipped file into the main directory I think it was /mnt/sdcard, Rebooted and the exclamation sign came up and installed the new 4.1.1. Then went back and deleted the file that I copied on to the main directory. Dont need an sdcard to manually update. "
junrider said:
I dont know if the OTA is operational again, but a lot of people like myself never received any automatic updates for a brand new stock infinity on the 11th. You might might want to try a manual update. Here is my post on the other threads on what I did to manual update to 4.1.1.
"I just returned a prime today that I bought for a friend in exchange for a C8 infinity. Tablet didnt want to update to JB and was stuck on 4.0.3. So I used my laptop and went to the Asus support download site, download 4.1.1 US version, unzipped it and another zipped file came up, Plugged the infinity to the laptop via Asus cable, copied the second zipped file into the main directory I think it was /mnt/sdcard, Rebooted and the exclamation sign came up and installed the new 4.1.1. Then went back and deleted the file that I copied on to the main directory. Dont need an sdcard to manually update. "
Click to expand...
Click to collapse
Yes I was aware of cases where OTAs never happened from the beginning but they did work for me . I had a pre-JB update and then the JB update itself which I aborted. So I think this is a slightly different case.
louiscar said:
Yes I was aware of cases where OTAs never happened from the beginning but they did work for me . I had a pre-JB update and then the JB update itself which I aborted. So I think this is a slightly different case.
Click to expand...
Click to collapse
I believe after a sucessful download OTA, Asus marked your ID, so you will not able to receive OTA again, the only way now is you have to do it manually.
buhohitr said:
I believe after a sucessful download OTA, Asus marked your ID, so you will not able to receive OTA again, the only way now is you have to do it manually.
Click to expand...
Click to collapse
Right, I've been trying to confirm if this is the case and how Asus do their OTAs. Thing is though, I aborted the download so it should have detected that the OTA was unsuccessful.
louiscar said:
Right, I've been trying to confirm if this is the case and how Asus do their OTAs. Thing is though, I aborted the download so it should have detected that the OTA was unsuccessful.
Click to expand...
Click to collapse
Here is how to update manually when OTA failed to update:
1. Download dlpkgfile.bin (US version)
http://www.mediafire.com/?2ctnjai5b68c7im
2. Rename dlpkgfile.bin to dlpkgfile then copy the dlpkgfile to /cache then set permissions to rw-r-r.
3. Download command file:
http://www.mediafire.com/?yq1bt16mnm7tc8d
4. Unzip and copy the "command" file to /cache/recovery, then set the file's permissions to rw-r-r.
5. Temp-unroot if you want to keep your root with OTA Root Keeper.(skip this if you already done this)
6. Power off.
7. Reboot holding power on and volume down, when you see white text message on the screen release both buttons
8. Press power up to confirm recovery mode.
9. Update will install and upgrade your device.
10. Once done, use OTA root keeper to restore root.
11. If you want to switch to superSU, you can download superSU, launch the app, verify it's working, then you can un install superuser.
buhohitr said:
Here is how to update manually when OTA failed to update:
1. Download dlpkgfile.bin (US version)
http://www.mediafire.com/?2ctnjai5b68c7im
2. Rename dlpkgfile.bin to dlpkgfile then copy the dlpkgfile to /cache then set permissions to rw-r-r.
3. Download command file:
http://www.mediafire.com/?yq1bt16mnm7tc8d
4. Unzip and copy the "command" file to /cache/recovery, then set the file's permissions to rw-r-r.
5. Temp-unroot if you want to keep your root with OTA Root Keeper.(skip this if you already done this)
6. Power off.
7. Reboot holding power on and volume down, when you see white text message on the screen release both buttons
8. Press power up to confirm recovery mode.
9. Update will install and upgrade your device.
10. Once done, use OTA root keeper to restore root.
11. If you want to switch to superSU, you can download superSU, launch the app, verify it's working, then you can un install superuser.
Click to expand...
Click to collapse
Thanks, yes I have already done that. I've also emailed Asus to try to get something sorted for future updates. I'm not sure if updating JB in this way will restore the OTAs. Asus' reply so far has been to tell me to clear DMclient data and I've just replied to tell them I've done that many times already. I'll see what transpires.
louiscar said:
Thanks, yes I have already done that. I've also emailed Asus to try to get something sorted for future updates. I'm not sure if updating JB in this way will restore the OTAs. Asus' reply so far has been to tell me to clear DMclient data and I've just replied to tell them I've done that many times already. I'll see what transpires.
Click to expand...
Click to collapse
Thank you for the update. I believe the issue is with their update servers. I had help people with brand new tf700 without receiving update, so it's not the tablet and it's not software or configuration related.
buhohitr said:
Thank you for the update. I believe the issue is with their update servers. I had help people with brand new tf700 without receiving update, so it's not the tablet and it's not software or configuration related.
Click to expand...
Click to collapse
Ok I will report here if I get anywhere with them. I somehow suspect that their support may not even realise or understand the issue but I will persist and see if I can get some kind of acknowledgment about their servers.
Well my OTA resumed after updating to JB so I think that it's as you state, the datebase on their servers. I don't know what the update was but your post in another thread would probably confirm this was JB .18. I guess once they have pushed an OTA, regardless of whether it was successful or not they don't seem to do it again. Which means I need to collect the dlpkgfile for each JB update given that I need to go back to ICS to do a proper factory reset and retain root.