Hi. I have a rooted TF201 on the 9.4.2.11 firmware version. Whenever I try updating OTA, it successfully downloads the file, then reboots, but once in reboot, after a couple of seconds, I keep getting the picture of andy on his back with his front hing opened and a red triangle with a ! When I reboot, it says it was unable to update firmware. Does anyone know how to fix this? I have tried wiping all my data as well as doing the OTA on root and without root but so still no luck. I even tried downloading the update file from Asus online and extracting the zip on the root of my sdcard and still no luck. Any ideas? Any and all help is appreciated. Thanks.
****Also, I included a screen shot of the system settings so you can see exactly what I'm on.
Ronde90 said:
Hi. I have a rooted TF201 on the 9.4.2.11 firmware version. Whenever I try updating OTA, it successfully downloads the file, then reboots, but once in reboot, after a couple of seconds, I keep getting the picture of andy on his back with his front hing opened and a red triangle with a ! When I reboot, it says it was unable to update firmware. Does anyone know how to fix this? I have tried wiping all my data as well as doing the OTA on root and without root but so still no luck. I even tried downloading the update file from Asus online and extracting the zip on the root of my sdcard and still no luck. Any ideas? Any and all help is appreciated. Thanks.
****Also, I included a screen shot of the system settings so you can see exactly what I'm on.
Click to expand...
Click to collapse
Just figured it out. I restored the original launcher and system.ui apks; I had replaced them with the themed one. Once I restored the original files, the OTA worked perfectly!
Related
Hi all,
My first post and i've searched extensively for answers but nothing has helped!
I have a prime - for nearly 2 months now, as soon as I got it I updated to ICS then updated one more time to 9.4.2.11.
I've now not been able to update OTA to .14 and now not even the .15 update that's available. I've tried manually updating which always ends up with the android laying down with the explanation mark above him.
I did root my system - it's not unlocked (yet) which is another thing - tonight after not being able to update manually or OTA i tried unlocking to use the new ROM available - but again no luck as the unlock tool keeps telling me that it failed to unlock, please try again later... I've tried...
- Unrooting
- Factory resetting
- Updating manually
Would appreciate any light on the problems i'm having...
Have you modified any system files or deleted any stock apps that comes with the prime? If so that is your issue. You need to have all the stock system files and apps in place or OTA will not update.
Hi,
Yep i've now re-installed the present rom from Asus .11 to completly restore my system and i'm finally updated to .15.
In regards to unlocking my system - still getting the "failed to unlock" message...
thelast27 said:
Hi,
Yep i've now re-installed the present rom from Asus .11 to completly restore my system and i'm finally updated to .15.
In regards to unlocking my system - still getting the "failed to unlock" message...
Click to expand...
Click to collapse
Looks like it's an issue on asus side. Lots of people having this issue today.
ok im running stock ics my device was rooted for a short period of time and i got this ota update but it wont install i thought it might have been the root so i unrooted and it still wont install is there anyone who has or had the same issue that can shed some light
I had a similar issue. was on .15-rooted, then I unrooted, tried the OTA update, and it failed.
Seems like I had changed the wpa files to something different than stock.
I downloaded both 15 and 21....put the on the SD card (one at a time), then successfully applied each. Will edit shortly with a link from ASUS on how to appy updates manuallly (I have to go find it)
Asus Link: http://service.asus.com/TF201_fwupdate
Bob
thanx going to try it out asap
My situation:
.28 Rooted (not unlocked) with a few tweaks such as keyboard and browser2ram.
Tried to JB update via OTA and manual method and got red andy.
Said screw it, took the factory .28 image from asus and loaded it onto my tablet before and after doing a factory reset/data wipe.
So I'm now completely stock and when I check for updates it says not found.
Tried clearing DM and CM CLient as well as cold booting linux [Pow + Vol Dn] and still says "no update found"
So is the WW JB Update still avail or did asus pull it?
Thanks
I'm having the same problem. Can anyone confirm that they have successfully downloaded the JB update OTA in the last few hours?
Happened to me as well, i think after you got red andy once you dont get the ota anymore. I went ahead and used manual upgrade method.
clouds5 said:
Happened to me as well, i think after you got red andy once you dont get the ota anymore. I went ahead and used manual upgrade method.
Click to expand...
Click to collapse
Same problem here. Rooted, locked, stock.
Had the notification bar give me the JB update once, that install failed.
I then checked the f/w update manually, found it, redownloaded it, that install failed.
Now I can no longer get the update via the f/w update checker. (tried many times last night and this morning)
Clouds... is the JB update available to be installed manually? Can you point me in the right direction?
mothman0 said:
Same problem here. Rooted, locked, stock.
Had the notification bar give me the JB update once, that install failed.
I then checked the f/w update manually, found it, redownloaded it, that install failed.
Now I can no longer get the update via the f/w update checker. (tried many times last night and this morning)
Clouds... is the JB update available to be installed manually? Can you point me in the right direction?
Click to expand...
Click to collapse
I think the files you want are linked here, but they take an age to download:
forum.xda-developers.com/showthread.php?t=1909820
I had a completely stock ICS .28 and got a dead droid (DMClient error). I manually downloaded the .28 from asus put it on a micro sd and it found this on reboot and installed OK. Now I am watching the green bar slooooowwwwwlly download the WW rom. The file has no extension, so I can't tell yet whether it is a blob file or the required zip.
ClevaTreva said:
I think the files you want are linked here, but they take an age to download:
forum.xda-developers.com/showthread.php?t=1909820
I had a completely stock ICS .28 and got a dead droid (DMClient error). I manually downloaded the .28 from asus put it on a micro sd and it found this on reboot and installed OK. Now I am watching the green bar slooooowwwwwlly download the WW rom. The file has no extension, so I can't tell yet whether it is a blob file or the required zip.
Click to expand...
Click to collapse
Well, I just finished downloading that file, and whatever it is, and I renamed it as a zip (which it is) and my TFP ignored it. Maybe it needs a specific name to work.
The many of us for which the OTA failed will have to wait for Asus to list the files on their download site.
ClevaTreva said:
Well, I just finished downloading that file, and whatever it is, and I renamed it as a zip (which it is) and my TFP ignored it. Maybe it needs a specific name to work.
The many of us for which the OTA failed will have to wait for Asus to list the files on their download site.
Click to expand...
Click to collapse
Alrighty, thanks.
This is the first time I've had any issues with updates, so was/am hesitant to dive in with the suggested workarounds posted in various places... don't know enough about the whole 'adb shell' stuff, etc, and don't want to make things worse.
I'm assuming that manually updating is relatively simple once Asus provides the files.
mothman0 said:
Alrighty, thanks.
This is the first time I've had any issues with updates, so was/am hesitant to dive in with the suggested workarounds posted in various places... don't know enough about the whole 'adb shell' stuff, etc, and don't want to make things worse.
I'm assuming that manually updating is relatively simple once Asus provides the files.
Click to expand...
Click to collapse
Hi
I had the same problem with the move from Honeycomb to ICS. The OTA would not do it and I got the red/dead droid. I have tried EVERY method to get Jelly Bean. The first attempt was OTA, and this loaded the file and tried to update but failed. Before I did it I back up root and unrooted. I have made no changes to the core system files. I have tried each method posted and none work. It goes straight to a dead driod. I re-installed .28 from the Asus site and still it would not work.
I shall have to wait until Asus decide that those like me 'deserve' JB and post the manual update files on the download page:
http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_Prime_TF201/#download
Indeed.
Once the update is available there, is a pretty straight forward process? Or does it still require terminal commands, etc?
glad to see i'm not the only one.
Guess i'll have to wait for Asus to post the JB files.
after hearing about some of the bricks I'm patient enough to wait a few more days.
Help, my tablet does not boot.
Today, my tablet froze while I've seen a video, it stopped responding to input. I waited about half an hour, if something happened, because this was not, I pressed the reset button.
And now the tablet hangs on boot at the Sony logo.
In early May, before the ICS update in germany came out, I did the US update via Condis tool, rooted and installed initd support to mount the SD card on boot. Then I disabled the Automatic Updates and never run another update.
From time to time, i made an Titantium backup, but but otherwise the root access was unused.
I have now tried it with another reset, no success.
While I still have access to the recovery, a factory reset does not help either.
Ihave not tried to flasch yet because I no longer have acces to the needed file.
Who can help me, how do I get to run the tablet again?
If necessary I do without root.
Thanks for your help
Eismaus
eismaus said:
Help, my tablet does not boot.
Today, my tablet froze while I've seen a video, it stopped responding to input. I waited about half an hour, if something happened, because this was not, I pressed the reset button.
And now the tablet hangs on boot at the Sony logo.
In early May, before the ICS update in germany came out, I did the US update via Condis tool, rooted and installed initd support to mount the SD card on boot. Then I disabled the Automatic Updates and never run another update.
From time to time, i made an Titantium backup, but but otherwise the root access was unused.
I have now tried it with another reset, no success.
While I still have access to the recovery, a factory reset does not help either.
Ihave not tried to flasch yet because I no longer have acces to the needed file.
Who can help me, how do I get to run the tablet again?
If necessary I do without root.
Thanks for your help
Eismaus
Click to expand...
Click to collapse
I would try to flash an update. You can now root ICS anyway and then restore wth TB.
Look in my signature update link. There is ICS R1A and R5 for US, either of those will do. Be aware that R5 upgrades the recovery so we can no long make custom ROM's thoug (using AIO).
Good luck
Stifilz
Thanks for the links, i download the files at the moment and will try this.
Just to make sure i understand you correctly, the r1a is rootable the r5 is not?
Update: Ok, i tried both files, but i got an error:
Erohibit update as a result of checking version or base sku
eismaus said:
Thanks for the links, i download the files at the moment and will try this.
Just to make sure i understand you correctly, the r1a is rootable the r5 is not?
Update: Ok, i tried both files, but i got an error:
Erohibit update as a result of checking version or base sku
Click to expand...
Click to collapse
You need a decrypted ota , http://forum.xda-developers.com/showthread.php?t=1518028 (3.2.1)
eismaus said:
Thanks for the links, i download the files at the moment and will try this.
Just to make sure i understand you correctly, the r1a is rootable the r5 is not?
Update: Ok, i tried both files, but i got an error:
Erohibit update as a result of checking version or base sku
Click to expand...
Click to collapse
They are both decryptable. Well were for me anyway. But once you flash R5 the recovery changes and you can no longer pre-root future installs.
I have not found a way to restore original recovery.
As for the update failed, try the Germany files also as the region may be still on that.
If still not working, please use adb pull (while in recovery, after failed update) and post file here.
Stifilz
The german file doesn't work.
What exactly do i need to pull?
eismaus said:
The german file doesn't work.
What exactly do i need to pull?
Click to expand...
Click to collapse
Oops. Adb pull tmp. You want the recovery.log
So i recently just got my system update settings back after a minor mishap where the apk went missing. So the problem i am having is that when i try to download the 12B update since im still in 11C however the download fails. And im slightly confused as to why the update fails on the download seconds after clicking download now
ToF_Itachi said:
So i recently just got my system update settings back after a minor mishap where the apk went missing. So the problem i am having is that when i try to download the 12B update since im still in 11C however the download fails. And im slightly confused as to why the update fails on the download seconds after clicking download now
Click to expand...
Click to collapse
Have you done ANY modification of the system files (freezing) or did you bump (install TWRP)? If you installed TWRP, you cannot take OTAs and install them. You must be on the stock recovery.
iBolski said:
Have you done ANY modification of the system files (freezing) or did you bump (install TWRP)? If you installed TWRP, you cannot take OTAs and install them. You must be on the stock recovery.
Click to expand...
Click to collapse
Actually i managed to fix it myself had to go through a long 2 hour factory reset and reflashing using the flash tool just to get the update to work. But thanks for replying :good::fingers-crossed: