I would appreciate if someone could help point me in the right direction with the issue I am having with my android. I upgraded to Jelly bean yesterday and watched the update run through successfully, after it had finished and it rebooted it crashed and I performed a cold boot on the device still with no luck. The device was encrypted, but I have run android updates on other encrypted devices in the past with no issues.
When I boot the device now it asks for the encryption password, accepts it and just displays the Asus scren with the spinning wheel thing
if any one can send me in the right direction would greatly be appreciated
Welcome to the forum to both of you!
My best advice is to download the firmware from the Asus website (ASUSTeK Computer Inc. -Support- Drivers and Download ASUS Transformer Pad Infinity TF700T)
Unzip it one time (it will still be a .zip)
Place on a microSD card.
Hold VOL DOWN and POWER. If you see small white text, release both buttons and tap VOL UP. If it goes to 4 icons, select the RCK icon to boot to recovery.
It should re-install the JB firmware.
Hard reset, see if she boots.
Just an update, after been tired of waiting I decided to just boot as in recovery Mode (Hold Vol-Down and Power Button) and move the cursor to Wipe Data, it did it, and it Factory reset it, now back to set eeeeeeverything back as it was before.
Last edited by erasat; 10-04-2012 at 09:18 AM.
I'm really getting frustrated and tired of this, after resetting and installed everything back as it was, and then some more consuming time encrypting it, it began again doing the same and it's stuck in the Asus welcome screen. Anybody from Asus seeing this? this is a work tablet and I must encrypt it, don't have any other option.
Thanks guys, appreciate the advice. I will let you know how I go
If you want ASUS to see it I would recommend calling them. They don't really watch the boards at all as we aren't a part of ASUS in any way, just volunteers. I can tell you that there is a rep around here somewhere (think its ASUS_USA or US_ASUS or something like that, but can't remember for sure). Gary Key is on XDA and may be able to help a bit as well.
TF101! - Running Domination built on my beautiful ArchLinux box!
Samsung Galaxy S4 - Stock Sadly...
Custom Built Desktop - Intel I7 w/ Windows7 & ArchLinux Dual boot - Go LINUX!
I firmly believe that any man's finest hour, the greatest fulfillment of all that he holds dear, is that moment when he has worked his heart out in a good cause and lies exhausted on the field of battle - victorious. - Vince Lombardi
Great Help Guide Here -> Frederucos Fantastical Forum Favorites
And Here -> Master Help Guide
Just registered to confirm that it's a relatively universal issue with this update. My encrypted tablet failed to boot after the update as well, and I did a full wipe from the bootloader menu, then tried encrypting it again, twice, without any custom apps or setting. It failed to boot after encryption both those times as well.
Seems as though this update breaks something critical with the encryption system.
BTW, mine is the US version.
Last edited by Forsaken; 10-07-2012 at 02:35 AM. Reason: add hardware SKU
The big issue is that I have sent Asus a couple of emails explaining in detail the problem, and for my surprise the following is just the almost generic reply that I received:
<<Dear valued customer
Thank you for contacting ASUS Technical Service
Hi,for the problem you mentioned after updating to JellyBean,I received the
TF700T JB V10.4.4.16 Release Note on October 5th,you may then receive the note soon,it will make some improvements.If the problem still remains,you may perform wipe data to have a try.
Welcome to refer Troubleshooting & FAQ for ASUS products in ASUS
ASUSTeK Computer Inc. -Support-
If you have any problems, please do not hesitate to contact us.
Wish you a nice day!>>
First of all, I barely understand what is saying, and second, a Wipe?, really?, have they even read the email I sent them explaining the issue? I even provided them a direct link to this thread, so they could see that it's not an isolated issue, but again, it seems that they didn't even read it. Unbelievable.
I wonder how much trouble it would be to downgrade back to 4.0.3 to resolve this...