So my tf700 running ICS was encrypted. I updated using update prompt inside OS. After update and restart it got stuck on the ASUS screen with the circles for half an hour. Finally factory reset brings it back, noticed my version was now 4.1.1.
Got it all setup again, then chose encrypt tablet. Tablet was encrypting around 22%, left it alone for about an hour then came back.
It was sitting on the password prompt beeping periodically. Entered PIN, then tablet stuck in boot loop again.
How fix?
Same thing as shown here. My best conclusion is we wait for 4.1.2
Related
Hi, my UK transformer said it had an update to install so I started charging it and pressed 'install update'.
A few hours have passed and its still on the screen with the orange exclamation mark and a little green android figure.
My internet is really slow at weekends, download speed is around 60kb/s. Will this be the problem?
Any idea what is happening? I don't want to reset the tablet because it might cause a brick, thanks.
EDIT> I turned it off after 4 hours of it being stuck and it restarted fine, I checked the version and it didn't update.
I went to settings and checked for an update, it said I needed to update so I clicked install again and now I'm back to where I started - Stuck on the update screen.
Your internet speed shouldn't have anything to do with your problem. The update would have completely downloaded before starting to install it. Maybe somebody around here can point you in the right direction to restore your tablet.
Ive just found this
http://android.modaco.com/content/a...408/have-asus-pulled-the-ota-firmware-update/
People seem to have this problem with the first update, looks like i'll have to flash another firmware myself.
First, Lonnnng time reader/modder/hacker/technut, first time poster.
Secondly, my questions are: 1) Anyone else had such a positive experience as I did? And 2) Anyone else reproduce or trigger this ‘update’ in ICS?
Story below:
So I just purchased TF101 used, brought it home, and found out the long and hard way about the SOD/RR/DOCK/BATTERY/KERNEL issues that are plaguing a lot of users. So I researched for the past week (I'm a new owner), tried JB, ICS, etc, rom after rom. Still had same issues, and new ones (no wifi, sound, docking support gone, etc).
So, I went BACK to honeycomb 3.01 by flashing official update (WW version as I am in Canada) zip via CWM. I wiped cache, dalvik, data via CWM. Installed the zip. Tablet booted up perfectly. I did not sign into the google store. Turned tablet off completely WITHOUT being docked. Cold booted. Shut down. Used it for about 1.5 hrs, no reboots and could not repeat SOD/RR. However, HC is very slow compared to ICS. I then looked for the 3.2.1 update as it apparently makes the dock work correctly, and could never find it ANYWHERE (one rapidshare link and it was dead), all links were dead as the JP vers is the only one on Asus official site. 'check for updates' within the tablet did not work.
Next, I downloaded official xx.27 ICS off Asus website (around 253mB). Same procedure. wiped all cache/data/etc, flashed in CWM still (never put stock recovery as many recommended, didn't see the point). Booted tablet. Signed onto wifi, skipped signing in google account. Once in, turned off and cold booted back on. Used it for maybe 10 secs, and Asus updater pops up in task bar. The update had the same file-name of the update I just flashed however it had a July 27 date on it, and it was 302 mB (noticably larger than the 250~mB) update. NEVER saw this dialog before, even with my many attempts previously and all the different flashes/roms. Updater rebooted, installed itself (maybe 2 mins). I shut down completely once back in. Also, I still have not signed into my google account.
Following ICS update and shutdown, I then plugged my dock into wall outlet. I then finally docked (while off and for first time during entire process) the tablet, which then booted up. It immediately recognized the tablet, and made that ping sound confirming it was connected. Tablet booted up. I shut down, cold booted one last time. I then put it away on my shelf, lid closed. I opened this morning and 0 SOD or battery drain, which happened with EVERY SINGLE kernel/rom I tried for the past week. It would either SOD or RR. I left it open on 'about tablet' with uptime counter. It is still going. I checked various emails this morning, and ran some videos, etc, etc. Trying to reproduce RR/SOD. Usually it would occur within 10-15 mins of actually using it unit/being on wifi/etc/sleeping and waking.
I have a feeling that somehow Google is sending code (since you authorize OTA updates when you sign in) via being signed in that is somehow RR/SOD'ing (my theory), or there is some mysterious update I somehow triggered through this process. If anyone has reproduced this please let me know. But for now, this seems to fix battery drain at the very least, however I am running stock CPU clocks.
As i and many other are familiar with the RR/SOD troubles i have to say since i've updated with stock rooted .27 i haven't got the trouble anymore
Just checked and my transformer is still 86 % of battery capacity with an standby time of 1 day 18 hours
Before this update it almost always RR after using it when it was in standby mode again !
Ever since this update procedure my RR/SOD problems went down to near 0. I had one reboot in 3 long days of using my device, and that was from the stock browser. Which crashed before as well, anyways. I think this is a definite fix, which DOES NOT rely on external apps.
Not sure exactley how I triggered the update process. Please someone reproduce this 300~mB update that I triggered using CWM the entire update process!
Also, I have since extesively installed Google Play apps, and non-market sources. Not one crash, SOD, or RR. Dock work, charges excellent. Been using the unit for 2-3 days off and on with cbr viewer, movies n music playing, tonsof web browsing, etc. NO RR! NO SOD!
Hi all. 1st post here.
I've been having a lot of trouble with my Galaxy Tab 2 lately. I rooted it a long time ago. Never had trouble with it. A few days ago, after charging it, I tried to start it, but when it starter, after a minute or so, it restarted. Normally the tablet only did that when it was froze due to many apps or processes being used at the same time. The problem is that the tablet never started properly after that one time. It's on some type of infinite loop. It starts, stays on for 1 or 2 minutes and then freezes and restarts. Well, i thought what most people would think at the moment: "I need to reset the tablet". I went to Recovery mod, made the format, but when the tablet rebooted, everything was untouched. No format. Odd to me. I then tried to return to stock. If it after that the problem was still there, at least I could be able to call for warranty. Odin gave me a lot of failed errors when I was trying but there was once that it said "Pass". Rebooted, still the same. Updated the recovery, tried to format, still the same. I'm running out of options right now. I don't really know what can be the problem and how can I fix it. I thought that if there was a way to format it like in recovery but using my PC it would do something (or not)
I appreciate any type of help.
I bought my Xoom when they first came out and have never rooted or unlocked it. It's been a good tablet all these years, but for no apparent reason, now won't boot up. I haven't loaded any new apps on it in months. I picked it up off the charger one morning and it was frozen. I rebooted it, and it refuses to go past the "M" logo screen. Multiple soft resets had no effect. I tried a factory reset - it says "Wiping data...Performing BP Clear...BP clear failed. Formatting /data...formatting /cache...Data wipe complete." Another reboot takes me back to the "M" screen, and I'm stuck once again.
I loaded up the Motorola drivers into my computer, and plugged the Xoom in. The computer sees it on a hardware level (in Devices, it shows up as MZ602, but it never shows up as a drive letter where I could actually drag files to and from it. (As I recall, it has to be fully booted and on before it shows up as a drive letter, but I may be wrong on that. I haven't plugged it in to the computer very often)
So I'm out of ideas, other than spending $160 to send it back to Motorola repair, which I don't think I'll do for a four year old tablet. Any ideas, anyone? Thanks!
jfran2 said:
I bought my Xoom when they first came out and have never rooted or unlocked it. It's been a good tablet all these years, but for no apparent reason, now won't boot up. I haven't loaded any new apps on it in months. I picked it up off the charger one morning and it was frozen. I rebooted it, and it refuses to go past the "M" logo screen. Multiple soft resets had no effect. I tried a factory reset - it says "Wiping data...Performing BP Clear...BP clear failed. Formatting /data...formatting /cache...Data wipe complete." Another reboot takes me back to the "M" screen, and I'm stuck once again.
I loaded up the Motorola drivers into my computer, and plugged the Xoom in. The computer sees it on a hardware level (in Devices, it shows up as MZ602, but it never shows up as a drive letter where I could actually drag files to and from it. (As I recall, it has to be fully booted and on before it shows up as a drive letter, but I may be wrong on that. I haven't plugged it in to the computer very often)
So I'm out of ideas, other than spending $160 to send it back to Motorola repair, which I don't think I'll do for a four year old tablet. Any ideas, anyone? Thanks!
Click to expand...
Click to collapse
have u tried re-flashing the rom?
Since I have had this tablet remote it has behaved completely erratically. I thought maybe a software update would fix the issue but it is still the same POS as day one. Constant reboots. Always goes through an optimizing apps process. (for a different number of apps each time). It doesn't always complete the optimizing process before it reboots so now it usually just goes into a weird boot loop 95% of the time. I have done a factory reset on the device many times and it always goes back to the same behavior. Everything points to a corrupt install of whatever pos vizio android rom came installed. I was hoping someone out there had a good install and could create a rom image for me to flash on this pos before I just break the damn thing.
And what I have been using in the meantime is my phone with the vizio smartcast app.