I have had my TF for a week or so, and have had no issues whatsover. I have am rooted, running a custom kernel.
All of the sudden I am having the TF reboot at random places, and now it is freezing even in CWM recovery. I wiped everything and went back to stock and still having the problem (on 3.1). Anyone else with this issue, and does it sound like hardware at this point? I think I may return it today, but I am nervous since the screen on this one is perfect.. don't want to get one with light bleed like my last.
Thanks guys.
yes. A quick search will show you the multitudes of threads regarding this issue.
skydirt said:
yes. A quick search will show you the multitudes of threads regarding this issue.
Click to expand...
Click to collapse
Yeah.. I get that.. I have been on XDA for 4 years.
I understand the freezes and reboots happen and are happening and other people are having them happen, however per my subject line I was looking for people who are having it happen while they are in their recovery mode. I have had the tab freeze after booting into recovery, as well as during a restore and backup. I wasn't having any issues for an entire week and without any kernal or rom mods this just started. (SPECIFICALLY IN RECOVERY MODE AS WELL AS NORMAL MODE)
If it freezes + reboots in recovery, see if a Ramdump file is placed in the root of your /sdcard/ folder. If so, paste it up here so we can look at it.
sassafras
sassafras_ said:
If it freezes + reboots in recovery, see if a Ramdump file is placed in the root of your /sdcard/ folder. If so, paste it up here so we can look at it.
sassafras
Click to expand...
Click to collapse
I actually have a bunch of those files. I attached them here. Oddly, today I am trying to dup the issue after the tablet has sat on but unused, it is working fine. I went into CWM, moved around the menus and waited for it to freeze but it didn't. I restored my backup and am currently testing different things to repeat the freezes. I know there was an issue so if possible I would love to be able to find out what it was/is, and make sure it will or won't happen again so I can get a replacement if needed while I can.
I post if I have the issue again..
EDIT: yup rebooted 3 times again after barely using the tablet. Also completely locked up on one boot before I even put in my pass pattern.
I then went into recovery mode, moved around the menu system and it froze again in CWM.
superevilllama said:
I actually have a bunch of those files. I attached them here. Oddly, today I am trying to dup the issue after the tablet has sat on but unused, it is working fine. I went into CWM, moved around the menus and waited for it to freeze but it didn't. I restored my backup and am currently testing different things to repeat the freezes. I know there was an issue so if possible I would love to be able to find out what it was/is, and make sure it will or won't happen again so I can get a replacement if needed while I can.
I post if I have the issue again..
EDIT: yup rebooted 3 times again after barely using the tablet. Also completely locked up on one boot before I even put in my pass pattern.
I then went into recovery mode, moved around the menu system and it froze again in CWM.
Click to expand...
Click to collapse
Hey there superevilllama, glad to see you back on XDA. Question, are you running custom firmware, ie. custom kernel, ROM, etc? If so, I would suggest downloading the stock firmware from ASUS and flashing back completely to stock and see if that alleviates any issues. If this continues to happen on a completely stock system, you might have faulty hardware.
It was the kernel...
Alright guys.. It was the kernel. I wiped and reset to stock, thinking I had already went back to stock kernel but apparently flashed the same kernel instead of stock.
I checked Clemsyn's kernel thread and # 17 of his had other people getting lockups and reboots too, OC or not. Gave me a scare because I did a bunch of things at one time.. updated kernel, got a new keyboard dock, updated setcpu.
I kept freezing all over the place and rebooting, OC or not. Thought I restored back to stock kernel but I didn't. Thought it was wierd as I had no issues before. Back to 16 of Clemsyn's kernel and all is well, both when not overclocked and OC to 1.5ghz.
I appreciate your help guys. Glad to know my TF is still in good shape. Good thing because the replacement I got had bbaaadd light leakage. Now I can just take it back.
Yes, it was the kernel.
More importantly, it looks like it was the clock speed.
sassafras
It is wierd that it froze in recovery mode tho. I thought recovery had its own kernel, I didn't think it used whatever kernel I had flashed. Eh either way I am glad it is working.
Related
I only installed the software cwm recovery (not nvflash), so I have no way out now. I haven't done anything serious except flash paul's patch and use titanium to uninstall some crapware like qik, that reader software, polaris office, etc.. nothing OS related, just apps. I also removed the GPS software, so I don't know what killed it exactly.
After removing those apps with TB, everything ran fine except I kept getting a force close from Qik... so I rebooted. Now it doesn't load and freezes on the LG screen with the loading bar not moving.
I don't know of any other options at this point...
Load up nvflash and get CWM on there so you can vol down + power into it. Then wipe data/cache and reboot.
You're not bricked even tho you think you are
GideonX said:
Load up nvflash and get CWM on there so you can vol down + power into it. Then wipe data/cache and reboot.
You're not bricked even tho you think you are
Click to expand...
Click to collapse
brick means HARDWARE LOCK or SOFTWARE LOCK
if your screen turns on at all... there is hope
fallow gideonx instructions... they have a nice tut set up for Nvflash
plus a one click type thing in the development section
I'm bricked for the time being until I can get home. I'm locked out of the device manager here at work, so I can't install the nvflash driver. Ignorant sons o'....
Sometimes I really hate the IT department.
Hopefully this is a warning to everyone else that if they want a custom recovery, they should bypass the rom manager option as it's too dangerious and just do the nvflash option.
For now nvflash is a better option instead of RM.
So I got home and used nvflash to put the latest cwm recovery on it. I wiped cache and rebooted... it shutdown the phone instead. So I manually turned it back on and it did the same thing.
So I did a full wipe and flashed a rom... and now it bootloops. I may very well have a bricked device after all.
Flashed which rom?
Here's a nandroid restore you can use:
http://forum.xda-developers.com/showthread.php?t=1048274
Eagles Blood since it was the fastest available.
The stock backup image is taking a long time thanks to the slow download. It's really irritating when all I can get on my 20mbps connection is 64KB/s.
antoniouslj said:
Eagles Blood since it was the fastest available.
The stock backup image is taking a long time thanks to the slow download. It's really irritating when all I can get on my 20mbps connection is 64KB/s.
Click to expand...
Click to collapse
I'd do the nandroid restore if I were you...
antoniouslj said:
Hopefully this is a warning to everyone else that if they want a custom recovery, they should bypass the rom manager option as it's too dangerious and just do the nvflash option.
Click to expand...
Click to collapse
noone will heed that warning lol.
Not a brick bro...just a minor bump in the road..you will get wiser from this..
G2X
fcisco13 said:
Not a brick bro...just a minor bump in the road..you will get wiser from this..
G2X
Click to expand...
Click to collapse
Actually it is completely gone now... seems like I have a defective device.
It won't boot into recovery or anything for that matter now, it just freezes at the first LG screen (the one without the progress bar). What's even weirder is I haven't really done anything to it... just installed and ran apps/games. I shut it down so I could install CM, but it won't boot into recovery or anything.
I tried redoing nvflash and it went fine, but it still won't boot into recovery.
This really sucks too... right on the eve of CM for this thing.
so, last night my phone was acting wierd... slow, battery was getting destroyed literally in an hour or two so i cleaned it up..
somehow i lost clockwork recovery... no flippin idea what happened, i never flashed or installed anything, but i went to do a backup and all i got was samsung recovery.
i did not lose root...
tried to install via rom manager and it said it worked... yeah whatever, that program is rubbish and ALWAYS says it worked...
anyways rebooted to a black screen but the capacitive buttons would light up if i touched them.
finally it installed but nothing worked and the phone locked up.
by the way rom manager installed CWM 3.0.0.8 (orange)
so now i had to completely blow out the phone, reroot, reinstall CWM (which worked the first time) but nothing is working in clockwork again.
back up.. nope says error backing up.. thats it
restore... nope, something about only having 8gb of space on my SDcard
i can wipe cache,, or so it seems.
but
if i wipe dalvik it locks the phone and i completely lose CWM again.
its acting like CWM is only temporary or something.
so what the heck.. i have never seen this before... ever.
I cant do anything with regards to bqcking up or restoring.
I cant.flash anything either even though rom manager boots to a portion of cwm which tries to flash a eom. But the phone just reboots.
Sent from my SCH-I500 using Tapatalk
Can't lie - Karma's a *****
Try going back to stock and starting over.
foxfire450 said:
Try going back to stock and starting over.
Click to expand...
Click to collapse
please be sure you read my post in its entirety and not bits and pieces.
i did finally get the latest CM7 installed and its running ok.
havent tried to do other things in CWM yet
akellar said:
Can't lie - Karma's a *****
Click to expand...
Click to collapse
you aint kidding...
but
its a phone, my life doesnt end if my phone goes to hell
just wierd, i have never lost clockwork before.
v_lestat said:
please be sure you read my post in its entirety and not bits and pieces.
Click to expand...
Click to collapse
In fairness, it's not immediately clear what you did after getting CWM Orange 3 installed---and really, ROM Manager should only ever be used on our phones if you're using the latest (CWM 4) on an MTD ROM.
That said: IF you think you need to do this (it sounds like if you got CM7 installed, you don't, but offering the advice all the same): take foxfire450's advice. Then do the entire process all over again. I've heard of people having issues with a lagfux or MTD removal unless they did the process twice. You might even consider the RFS Formatter if you're still having trouble.
Again though, that's all largely academic if you're running fine now. *shrug* Up to you to try if you think it's worth bothering at this point.
Hello everyone. It seems like the issue is getting worst and I think I've narrowed down the problem... Now I just need a solution and we can all be happy
So sometimes my phone decides to restart itself and it will not boot back up. The only solution is to remove the battery and try again. It could be solve after a couple tries in the past, and now I find myself sitting for half an hour + trying to get this phone running again. I do have clockwork installed, and it seems like my issue is with my SD card. When trying to mount/unmount my SD card via clockwork, there is an error doing do. Sometimes I can't access my pictures because of the same problem. Does anyone know if there is anything I can do to remedy this situation?
Thanks!
ritzbits said:
Hello everyone. It seems like the issue is getting worst and I think I've narrowed down the problem... Now I just need a solution and we can all be happy
So sometimes my phone decides to restart itself and it will not boot back up. The only solution is to remove the battery and try again. It could be solve after a couple tries in the past, and now I find myself sitting for half an hour + trying to get this phone running again. I do have clockwork installed, and it seems like my issue is with my SD card. When trying to mount/unmount my SD card via clockwork, there is an error doing do. Sometimes I can't access my pictures because of the same problem. Does anyone know if there is anything I can do to remedy this situation?
Thanks!
Click to expand...
Click to collapse
are you using a custom rom or kernel?
I used to, but now it is just stock rom rooted
Edit: I lied, seems like when I restored, the kernal stayed the same.... I assume I can just flash a stock kernal over my modded one?
ritzbits said:
I used to, but now it is just stock rom rooted
Click to expand...
Click to collapse
have you tried redownloading the rom and reflashing it?
Note the edit above. Just checked my settings and it looks like I still have my old kernal..( non stock) I dont seem to be able to find a stock kernal anywhere... Do you happen to know where I can find one?
theres probably a version of the stock rom floating around with the stock kernel already included. check the developement threads.
Stock rom, check stickies in General section.
Sent from my Nexus S using XDA App
I reverted everything back to stock with the exception of the bootloader still being unlocked. I thought the issue was fixed, and I have not had issues with the phone since. Until today when I decided to restart it. Same issues as before not being able to mount the sd card, which seems to be required to boot. Any ideas? Is the sd card in the nexus s actually there? Maybe it came loose?
My One X restarts when I'm in the Google Play app and while using the built in browser. It seems to be data related... Also I get no error or anything of that nature, it just freezes (stops responding to any input whatsoever the capacitive buttons don't respond either) and it just restarts and goes through the HTC and AT&T load screens. Any ideas as to why my phone keeps restarting after a bit of use on the market, browser, etc... I've sent in my original phone thinking it might've been defective. Turns out the one they sent me did the same thing. Mind you they sent me a refurbished one. So I don't know if its a problem isolated to the original shipments of HOX's since I got mine via a pre-order and this is probably the same batch since the AT&T rep said they had no new devices to ship to me as a replacement.
Any ideas?
I've gone through a few HOXs and have never had a single reboot on any of them. My suggestion to you would be to wipe everything (data, cache, dalvik) and reflash your ROM.
_MetalHead_ said:
I've gone through a few HOXs and have never had a single reboot on any of them. My suggestion to you would be to wipe everything (data, cache, dalvik) and reflash your ROM.
Click to expand...
Click to collapse
How exactly would I go about doing that. I used the clockwork recovery mod on my Aria back when I had that. But from what I understand the HOX doesn't have that yet and attempting to use ROM Manager or anything that uses it would brick my phone.
We have clockwork mod and TWRP recoveries. I take it you are on a stock ROM then? Are you rooted?
Oh, and never use ROM Manager. Ever.
_MetalHead_ said:
We have clockwork mod and TWRP recoveries. I take it you are on a stock ROM then? Are you rooted?
Oh, and never use ROM Manager. Ever.
Click to expand...
Click to collapse
Yeah I'm rooted (on the stock ROM) and I managed to get my bootloader unlocked.
I take it you haven't flashed any mods right? I'd get clockworkmod flashed on your phone and then wipe and flash CleanROM SE. It's very close to stock, perfectly stable (I haven't had a single force close except for one youtube one a long while back right after flashing), and it has some great mods and tweaks. If you are still having reboots, then I would RUU back to stock, see if they are still there and if they are, get it replaced.
_MetalHead_ said:
I take it you haven't flashed any mods right? I'd get clockworkmod flashed on your phone and then wipe and flash CleanROM SE. It's very close to stock, perfectly stable (I haven't had a single force close except for one youtube one a long while back right after flashing), and it has some great mods and tweaks. If you are still having reboots, then I would RUU back to stock, see if they are still there and if they are, get it replaced.
Click to expand...
Click to collapse
Sorry, didn't see this (http://briefmobile.com/how-to-install-cwm-recovery-on-htc-one-x-att) on the index. Thanks for the help.
xChurchx said:
Sorry, didn't see this (http://briefmobile.com/how-to-install-cwm-recovery-on-htc-one-x-att) on the index. Thanks for the help.
Click to expand...
Click to collapse
Yep, that's the one. Happy to help.
Radio
If your issues were mostly data related its probably a radio issue. Be sure to flash a new radio. If I'm not mistaken most roms don't include the radio. I like the latest AT&T as well as 1.88. Much better than 1.73 or 1.85. you can flash it just like a rom if it's in zip format. There's a thread in development with radio In the title. Normally first page.
xChurchx said:
My One X restarts when I'm in the Google Play app and while using the built in browser. It seems to be data related... Also I get no error or anything of that nature, it just freezes (stops responding to any input whatsoever the capacitive buttons don't respond either) and it just restarts and goes through the HTC and AT&T load screens. Any ideas as to why my phone keeps restarting after a bit of use on the market, browser, etc... I've sent in my original phone thinking it might've been defective. Turns out the one they sent me did the same thing. Mind you they sent me a refurbished one. So I don't know if its a problem isolated to the original shipments of HOX's since I got mine via a pre-order and this is probably the same batch since the AT&T rep said they had no new devices to ship to me as a replacement.
Click to expand...
Click to collapse
I had this exact problem. EXACT. Does it happen on WiFi only? try turning it off.
EDIT: this happened to me on two different HOXs, one just after i updated to 1.82, and the other, stock from the store on 1.85. I was able to narrow it down to the fact that our home wifi was unprotected with a hidden SSID. as soon as we changed it to WPA it worked fine, and continues to.
I am unlocked and have the recovery of twrp 2.3.3.0. I'm having problems with about every single rom I flash. I wipe everything as you are suppose to and the flash appears to go well but usually right away after the rom boots up the system becomes unresponsive. I have to hold my finger over a button for a couple seconds for it to acknowledge a touch and things just don"t run right.
Its like either the system is almost locked up or the touchscreen just hardly works.... one of the two. I made a backup of my original asus setup and if I restore it the tablet works just fine. I've tried hydro, cm 10.1, blackbean 7, and one or two I'm forgetting. AOKP RC1 is the only custom rom that gives me no problems at all in this regard, unfortunately its an unfinished rom, no camera and my battery dies like crazy with it...
The 2nd best running rom that I really like from what I have seen is blackbean 7. Runs great for first few minutes but after playing a game for a bit or doing some other things and having it run just great all the sudden the dreaded problem occurs and the only fix is a reboot for it to work for a while longer. So frustrated at this point as I have flashed so many roms and resetup so many things just to find myself doing it again trying to fix this and find a rom that works for me.
Any ideas at all on what could do this? Is the difference in the kernels the reason why AOKP RC1 and Asus original work but none of the others? Or does it have to do with my recovery? Fairly certain I have the correct most recommended one with twrp 2.3.3.0 and the process went fine. Any ideas greatly appreciated. I really just want to be able to run blackbean. And knowing that most all roms will not work for me is rather disturbing in regards to the future. Really wanting to like my new tf300t but its making it hard:silly:
Try to downgrade your recovery.
Use this : openrecovery-twrp-2.3.1.0-tf300t-JB.blob
and take a feedback after, thanks
I really appreciate that you took the time to give me something to try but I'm afraid it didn't work. Process went fine I'm on 2.3.1.0 twrp but same problem. First rom I've tried instant non-responsive. Any other ideas?
I've been using ClockWorkMod Recovery on my TF300T, and it's been great. (Used it to upgrade my ROM to CM 10.1.) No issues at all.
If you need instructions for getting it installed on a TF300T, check out my second-to-last post on thoughtsontechnology.com. (NONE of the work is mine, I just compiled the instructions and links in one spot for easier access. Most of the work came from XDA contributors, they've been really great.)
Most roms need 5 to 10 mins to stabilize after a new install, usually as they are building media storage files, etc. Are you giving them enough time?
Failing that I can only think your microsd has something corrupt on it. Boot with it out.
Well I tried cwm again flashed it no problem installed rom no problem but no fix. So guess we have established it definitely isn't the recovery at this point...
Yes I've given roms several reboots and lots of suffering them working for 10min to only fail again for another reboot... So its not that. Still the only Rom that will work is my backup of the original asus and the AOKP RC1. Trying it without the external sdcard right now.
Well no joy on the removal of the external sdcard
Have you tried a full wipe before installing? You must have some thing on the data partition causing this. I
sbdags said:
Have you tried a full wipe before installing? You must have some thing on the data partition causing this. I
Click to expand...
Click to collapse
Not sure what a full wipe is? I wipe cache/dalvik system format data and have even tried formatting the sdcard once several roms ago. One thing I have noticed since I am trying so many roms all the time is the sdcard file structure seems odd as I have at the root of the sdcard a 0 directory that continues to be added to. Currently it goes sdcard/0/0/0/0 to actually get to where I have things stored like music, downloads. Is this normal? Its strangely repetitive.
Personally I think you should stop using TWRP if you're having all these issues. Just flash CWM and have fun
touchscreen
This thread is a couple months old, but i am having the same problem. After installing a lot of different roms, both stock based and cm/AOKP. I let the rom stabilize and after a few hours or even minutes the touch screen has a mind of its own. It lags, double touches or fails to respond at all. I m on twrp 2.4.1.0. Was this issue ever resolved? Should I try old version recovery or cwm? I restored rooted stock us10.4.2.20 and the issue is gone. Is it possible that installing a rom changed the touch screen firmware? I am open to suggestions as I have spent alot of time on this with no luck. Thanks!
What version CWM would u suggest as this is probably my next move?
Showme1 said:
This thread is a couple months old, but i am having the same problem. After installing a lot of different roms, both stock based and cm/AOKP. I let the rom stabilize and after a few hours or even minutes the touch screen has a mind of its own. It lags, double touches or fails to respond at all. I m on twrp 2.4.1.0. Was this issue ever resolved? Should I try old version recovery or cwm? I restored rooted stock us10.4.2.20 and the issue is gone. Is it possible that installing a rom changed the touch screen firmware? I am open to suggestions as I have spent alot of time on this with no luck. Thanks!
What version CWM would u suggest as this is probably my next move?
Click to expand...
Click to collapse
Sounds like you have a hardware fault if the issue persists across multiple firmwares.
Also, OP said his SD card directory structure was strange. I'd format both internal and external SD in recovery (in addition to wiping and factory reset) before you flash.
Thanks! Wiping internal has seemed to do the job. Still would like to know what the issue was. I was thinking it was the touch panel firmware, but thought that would be in /system
Sent from my SGH-I747 using xda app-developers app