FIX AVAILABLE!!
I bought my TF about 15 days ago, rooted it and installed CWM recovery, and it was running just great. Then, the ICS update came along and i just waited for the CWM package to update mine. No problems in the update process, but the random reboots started happening, so i thought the problem was that i updated without wiping, so i did this. No dice, still getting (not so) random reboots. So, i thought maybe it was the CWM package. I downgraded to HC via NVFlash, then let it update via FOTA. Even then, the random reboots persisted. Then, i noticed the tablet never rebooted while in use, but only while in deep sleep state. The "No Sleep" widget is the current workaround, but then, you risk getting a SOD.
So, from what i could gather until now, the following things are NOT the cause for the RRs:
1. Updating without wiping.
2. Updating via CWM.
3. Rooting.
Well, i got really sick of this problem, so it's time to do something about it. I am trying to gather as much info as possible to try and narrow down the possible cause for the random reboots, so i need everyone that is facing the same issue to give me the following info:
1. Serial number of your Transformer
2. Firmware region (TW, US or WW)
3. Logcat before the reboot
For number 3, you need to open Terminal Emulator, and do this:
# su -
# logcat > /sdcard/logcat.txt
Then you just turn off the screen and let your tablet go to deep sleep. After it reboots, post here the info above and attach logcat.txt.
Please, only use this thread to post the info i asked. Thanks!
Update: Some users contacted ASUS and it seems they are aware of the problem. A fix is supposed to released soon, in the form of another OTA update.
Update2: Very good knews for rooted users. The test13 version of guevor's kernel is able to let the TF deep sleep and not reboot. Link to his thread:
http://forum.xda-developers.com/showthread.php?t=1565519
THANK YOU, GUEVOR!
Good idea. Mine just randomly shuts down during sleep, as opposed to rebooting. Shall I contribute too?
Have you tried a factory reset?
Balor said:
Good idea. Mine just randomly shuts down during sleep, as opposed to rebooting. Shall I contribute too?
Click to expand...
Click to collapse
Yes, please.
Sent from my Transformer TF101 using XDA Premium HD app
Can´t give you a logcat yet but here's my TF101 info:
FOTA to ICS 2 days ago and started random reboot's... Not Rooted (never has), no service/app/etc.. killer, but i did disable all of ASUS crapware on the Apps manager.
I was able to caught one of the reboots (it's freeze on the ASUS logo) and when i hard reboot it, during boot sequence appear some message saying that was finalizing update (this was after the FOTA and after other 2 random reboots. I did reboot the device after the update at least twice before experiencing the 1st Random Reboot).
info:
S/N: B90KAS146231
WW (Build Number IML74K.WW_epad-9.2.1.11-20120221)
Kernel: 2.6.39.4-00002-g2977a0d » [email protected]#1
as soon i have the Log i will post.
Hope this help somehow
baseballfanz said:
Have you tried a factory reset?
Click to expand...
Click to collapse
Every kind of update method that you can think of was tried. In that case, yes, it was wiped. Several times, in fact.
Please, post just what i asked. I want this info to investigate the issue. Post on another thread if you want to share theories or something else.
Sent from my Transformer TF101 using XDA Premium HD app
Mine was never rooted, 100% stock, took the ICS OTA on Friday moring, ran great all day, I woke up Saturday morning (I had docked it and put the doc on the charger friday night when I went to bed) and it was stuck in a boot loop. Now I'm looking at how to NVFLASH it back to honey comb to recover it, might as well root it now.
Les
still waiting to freeze or reboot ... for now 493K of logcat
Sent from my Transformer TF101 using Tapatalk
This is going to be a problem in the kernel like it has been on previous releases. When kernel source is released then the kernel devs will fix it and then asus will fix it. My SODs are caused by a kernel panic so until we get an updated kernel we need to get asus to release source.
I am mostly a longtime lurker/user of XDA but I thought I should contribute to this thread.
Bone Stock 16g TF101-A1, Refurb purchased last week from online vendor. Still getting used to the tablet format but I also purchased a TF101 Dock.
I noticed yesterday that I had a couple of random re-boots. Didn't know if it was related to an update or why this particular tablet was "refurbished." About 7 hours ago, this morning, I got multiple re-boots. Splash screen then power off and on again. I saw at least 15 re-boots before I started looking around for solutions. I tried the stock rom (downloaded from Asus) and re-boot to recovery w/o any success. Re-booted and wiped (hard reset) multiple times as well.
Still no complete boot but I had two separate and distinct paths that displayed:
1. it would boot with an android bot asking for a password and the keyboard displayed
2. It would cold boot into the "Start" screen like a normal set up.
I did manage to get the recovery started only to reach the bot with the exclamation point and no further progress at recovery.
In either case, typing a password of any kind did nothing, and hitting start and beginning the set up process did nothing but continue the re-boots/splash screen/power up/power down.
Finally connected to my laptop and it succeed in a complete boot and I was able to set up and connect to my wireless. It did not re-boot for several moments and I was able to observe the "About" page from the settings. I was still running
HTK75.US_epad-8.6.5.21-20111216
I also noticed that it was actively downloading a "firmware update" I went through several more re-boots until it finished the download and then I installed the firmware w/o any further trouble. In watching the download, I noticed re-boots at 31%, 32%, 41% "download completion", and one or two more before it fully downloaded. Of course, it did re-boot upon completion of the upgrade.
I am now running Android version: 4.0.3 Build number: IML74K.US_epad-9.2.1.11-20110221
Everything has been stable for an hour or so of moderate use including installation of multiple apps.
FWIW, I think that the reason my problem started is that I had my WiFi set to turn off when screen is off. I believe my incomplete download started the re-boots and my settings "may" have contributed to the incomplete downloads that started the rest of my issues.
Thanks to all of the "regulars" around here that are busy helping us customize our devices. This may not be my first post, but I think I have less than 5 posts right now. Hope this helps in discovering the causes of the re-boots.
ICS OTA on Saturday, 2 reboots already, stock rom, 100% original, Italy. Should i contact Asus?
msaraiva said:
I bought my TF about 15 days ago, rooted it and installed CWM recovery, and it was running just great. Then, the ICS update came along and i just waited for the CWM package to update mine. No problems in the update process, but the random reboots started happening, so i thought the problem was that i update without wiping, so i did this. No dice, still getting (not so) random reboots. So, i thought maybe it was the CWM package. I downgraded to HC via NVFlash, then let it update via FOTA. Even then, the random reboots persisted. Then, i noticed the tablet never rebooted while in use, but only while in deep sleep state. The "No Sleep" widget is the current workaround, but then, you risk getting a SOD.
So, from what i could gather until now, the following things are NOT the cause for the RRs:
1. Updating without wiping.
2. Updating via CWM.
3. Rooting.
Well, i got really sick of this problem, so it's time to do something about it. I am trying to gather as much info as possible to try and narrow down the possible cause for the random reboots, so i need everyone that is facing the same issue to give me the following info:
1. Serial number of your Transformer
2. Firmware region (TW, US or WW)
3. Logcat before the reboot
For number 3, you need to open Terminal Emulator, and do this:
# su -
# logcat > /sdcard/logcat.txt
Then you just turn off the screen and let your tablet go to deep sleep. After it reboots, post here the info above and attach logcat.txt.
Please, only use this thread to post the info i asked. Thanks!
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
So... if you do the ful update via CWM there are no problems?
Sent from my Transformer TF101 using Tapatalk
Just Once
I have experienced a single random reboot since applying the OTA ICS upgrade to my US B70 TF101.
That was then...
Now the tablet is virtually unuseable. Not only are there random reboots, but lags and freezes ad nauseum. I am NOT a happy camper
I don't believe this has been mentioned before.
I just saw my device go into random reboot in sleep. However, this time the device completed the boot up sequence instead of getting stuck on the Asus loading screen...
All I did different was changing WIFI sleep policy from "never" to "on during sleep", which I don't think is the cause of the change.. I guess it all depends on luck weather the device gets stuck or complete the boot up sequence.
So perhaps the problem is caused by a combination of a bug in the deep sleep state and the CPU governor?... This is purely my speculation.
jparity said:
I don't believe this has been mentioned before.
I just saw my device go into random reboot in sleep. However, this time the device completed the boot up sequence instead of getting stuck on the Asus loading screen...
All I did different was changing WIFI sleep policy from "never" to "on during sleep", which I don't think is the cause of the change.. I guess it all depends on luck weather the device gets stuck or complete the boot up sequence.
So perhaps the problem is caused by a combination of a bug in the deep sleep state and the CPU governor?... This is purely my speculation.
Click to expand...
Click to collapse
My device never gets stuck in the ASUS logo, it always completes the boot process, and the wifi policy is the default one, so i don't think it's related to it. But it's probably something to do with the kernel and deep sleep state. Even with the wifi policy set to never turn off, the device enters DS.
Sent from my GT-I9100 using XDA App
reboot cant have anything to do with the apps (like google earth) as those will simply FC on fault and are not capable of taking system down. this must be a kernel or driver issue.
transformer prime got ota update recently that was supposed to fix reboots and it contained new wifi driver. so possibly this is something to do with wifi.
my wifi sleep policy setting is to be always on when on power and sleep when screen is off on battery.
never had a reboot when plugged in, had a few always on battery power - so it might be related to wifi beign powered on in sleep to do periodical email check. just a guess.
I am running stock unrooted atm. I reverted back from rooted to stock before the ota update.
I generally get one random reboot each day. They happen when my transformer is in sleep mode always. It'll be st next to me asleep and then I notice the screen turn on and it is rebooting. My "Keep Wi-Fi on during sleep" is set to "Always".
I removed root as I wanted to see what stock performance was like. Apart from these reboots I'm totally happy.
2.6.39.4 and WW_9.2.1.11
Not sure how much help that'll be to others, but there you go.
I had these random reboots aswell on my device but since yesterday morning it stopped.
- Removed SetCPU
- Forced 2D rendering to the GPU.
Still testing it but so far no reboots
Stock ICS + Root
Getting the same exact thing, froze during boot up one time.
Running S/N BBO
Tossed a ticket into Asus letting them know, hopefully I get a response back soon.
I had random reboots the first day after updating,
but have set
1. the wifi to be off when the screen is turned off (in wifi settings), and
2. have turned off the location service that uses your wifi to aid positioning (in location settings).
and this seems to have stopped the reboots.
Hope this helps someone.
Sometime last night, my AT&T G2 (D800) decided to go from being powered on and idling, to going into TWRP recovery mode. All by itself. I saw this, unplugged it from USB, and tried to reboot into system mode. But it simply won't do anything except boot into recovery. Powering off, trying to get to the bootloader, none of that works.
This is not a custom ROM, it's 4.2.2 stock from LG. I only rooted the phone, which was several weeks ago, and haven't had any problems, aside from TWRP not wanting to back up anything. I've been using Android since the original TMO G1 with JesusFreke's ROM, so I have a pretty good idea of what I'm doing, hopefully.
The only recent changes I've made are:
I updated busybox about 3 days ago (but have rebooted fine since)
I grabbed several legit apps from the market last night
Last night I also DL'ed, but did not apply, a ~50MB OTA update that has been pending. I don't think that would install without explicit permission anyway, which I didn't give it?
This phone was encrypted from the start. Maybe that;'s what prevents TWRP backups,, but right now I'm seeing TWRP errors/logs saying something like "Unable to mount \data". And yet I can browse to other folders, and see filenames in \etc for example. However, I don't see any files at all in \boot.
Since this phone has no external memory, and it's customized and has numerous configured apps, I really really don't want to have to wipe it. Although at this point, that may not even fix the problem? Even if it did, since I haven't been able to make backup images, it would be a Bad Thing™ either way. (Yes, I do have a secondary plan with Titanium, with backups going to cloud storage, but these are tedious and now a few weeks old. And wouldn't restore the ROM & system en masse.)
Please help.
Solved?
I'm not sure what caused this to occur, but I found somewhat of a solution after digging deep into my Google-fu.
I followed the instructions in this XDA thread and it actually worked. I didn't have adb access, but I was able to use dd successfully. It allowed me to boot into the device, unencrypt it, then arrive at the lock screen.
However, when I put in the lock code, it went apesh!t and played multiple notification sounds, with a blue circular wait symbol. It also flashed the LED from green to blue, as it normally only does during boot. Once I pressed the power button, I was back back into TWRP.
So then I followed Step 2 again, and once in the phone, I used terminal to run the dd command from inside the OS. This might be what it ultimately needs, because the prior attempt in TWRP had an error to the effect of "no space left on device".
I can't call it Solved yet, but it looks good to at least be able to get in and use the phone. I'm backing up with Titanium before I do anything else and will reboot and test its permanency later.
I'm gonna close this thread now that I think I have a handle on what is going on. The fix does survive a reboot, so I believe it's possible to repair the issue permanently per the instructions above. I also ran the phone for 3 hours with heavy app usage and no problems.
I believe what may have happened is my OTA decided to override my choice to NOT update the ROM, as some have reported in this Reddit thread. There's a lot of good info in that one, including how to stop getting nagged by turning the OTA notifications off, or to freeze it entirely with Titanium Backup if rooted.
Anyway, what apparently happens is that when the OTA/upgrade goes to reboot, and encounters a custom recovery, it gets confused... when you try to power cycle or reboot again, it sees the stock recovery still hasn't run whatever it wanted, so it starts recovery again Lather, rinse, repeat.
Fun times.
So as of today, the WiFi on my family's Nexus 7 tablet no longer wants to enable. Upon doing a factory reset, we found we could no longer get past the "Select a network" screen. It just got stuck on the message "Turning on wifi". There was no skip button as there would be usually and nothing else could be pressed. I suspect a hardware issue, because I've tried many solutions and the closest I've come is just making the device work again. It was unrooted at the time of the issue. When recovery was accessed we were met with a "No command" message.
So the first thing I did was get to work on re-flashing the device. I started back with the original OS from Google's stock ROMs. Fastboot worked great, but I was still facing the same problem on first run of the device. The wifi simply would not enable. After this, however, the recovery menu seemed to have fixed itself. Through this I did a reset process as well...with no results.
The last thing I tried, which restored basic functionality to the device, was installing the Paranoid Android custom ROM. At this point, you could access regular apps and other things. I reinstalled the Gapps and the device was back to normal, with the exception of the wifi. The wifi is a big reason we use the tablet. It would be preferable to find a fix, as we would rather not have to replace something that only has one problem.
As of now, the device is rooted, with superuser on Paranoid Android 4.4.2.
Anyways, I really hope there's a solution to this. It's a great tablet.
Guys,
I'm not even sure where to start with what I'm seeing, but maybe you can help me.
I have had Timur's ROM on my N7 2012 for a couple years. It's been crashing randomly, even though I have few things installed on it, and a good power supply. I took it out of my car and put it on an iPad 2 amp supply, and it still crashed a bunch so I knew I needed to wipe and reinstall. I also wanted to go from 4.2.2 to 5+, which I know takes away a lot of the good features I need (like power on/deep sleep).
I booted into TWRP and wiped my tablet, which appeared to softbrick it (I think I have the usage right from searching). I downloaded the Pure Nexus 6.0.1, CM13, and already had Autodroid ROMs to use. I tried to install Pure through ADB sideload, and got it installed. When I finished and tried to reboot, it said I had no OS. When I rebooted, I got the boot animation, and nothing else.
Long story short, I tried Autodroid and CM13, and using CM13 I got it back going. Unfortunately, every time I try to flash another ROM over it, it will no longer go past the boot screen. With CM13, it boots properly, but doesn't like the gapps pico I tried to install (error message when booted, keeps returning to the same pop up error).
I'm quite sure there's something I'm missing, but I don't know what it is.
Thanks!
Eric
Ok, before anyone goes nuclear on me, I think I better understand what happened. When I got ANYTHING to work, I stopped doing anything. As I understand, it wasn't functioning...it was just in a temporary mode of some sort.
After not being able to get it to work properly, I used this: http://forum.xda-developers.com/showthread.php?t=1781250 to try and restore the system. I followed all the directions, except for using the 5.1.1 version of the ROM, and used the corresponding file name for the zip file used.
After doing so, the bootloader won't go to TWRP, but goes to the pic as seen below. I did reboot the tablet, and after waiting quite a while, the tablet came on, but I don't understand what that picture means.
Thanks!
Eric
Ok...I realized that I lost root. I'm fixing it now. I had read before, but didn't understand what I saw.
Thanks,
Eric