Database Info

[Q] Phone not recognizing USB cord at all

I'm running Darky's 6.0 Rom with xcaliburinhand's kernel. I began to realize my phone wouldn't charge when I plugged it into the charger. I tried flashing to stock using odin but once I'd get into download mode via the long-press menu when pressing the power button (because other methods that involve plugging in the cord and pushing buttons doesn't work since it's not recognizing the cable). I don't think it's a faulty cable or port since everything was working before I flashed the ROM. Anyone have any ideas on how to get the computer to recognize the phone so I can flash stock??
edit: When I do plug in the phone to the computer, I'll sometimes get a message saying the device isn't recognized.
(And yes I do have drivers installed.)
Also, I tried flashing other ROMs via CWM but I get error messages on all that I try. Such as can't mount .dev/block/st19 and can't mount SYSTEM
Edit: After a while I've noticed that it in fact is charging but the battery icon doesn't show it's charging. And in settings it shows it's not charging. But battery level is increasing

Have you tried a different computer to see if the usb port is bad?
Sent from my SAMSUNG-SGH-I897 using XDA App

Does it charge when you plug it into an ac adapter? You can also try reinstalling the drivers and see if that helps and/or try a different usb port. I've had issues with the drivers before.

Also try a different cable. My cable became defective somehow where xp no longer recognized it, yet would still show charging on the phone. All was back to normal after I got another "data/sync" cable.
Sent from my SAMSUNG-SGH-I897 using XDA App

I don't have a different computer to try it on but I've tried different ports. It's not the computer because it still won't show it's charging when I plug into the wall. And yes I think it does charge when it's plugged into a wall but it doesn't show it or turn on when I plug the cord into the phone. I don't think it's hardware. It has to be software since it just happened when I flashed the ROM. Also whenever I open contacts I get a force close of acore (a little off-topic, but still another issue). I also have tried reinstalling drivers. But also, it doesn't work when plugged into a wall charger. So it's definitely nothing with the computer

I just need to know if anyone knows how to force the computer to recognize the phone so I can flash to stock and hopefully that'll resolve the issue
update: I also tried v7 via CWM and no luck still.

Well I update xcaliburinhand's kernel by transferring it over bluetooth and that installed fine over CWM. Then I tried updating Darky's rom to v7 and that worked too. I booted up and got a million FC's. Tried to get into recovery and it just sits at AT&T screen. It's very tricky to even boot up the phone, and even when I do I can't do anything because of all the Force closes. I can't get back into recovery mode with any button combinations and when i try via the power long press I can get into download mode fine, but I still have the issue with the computer not recognizing it, so it's useless. Anyone have any ideas????? I'm getting sick at staring at this AT&T boot screen for so long. I have no idea of what to do next. Someone please help!!

Sorry to say it, but it sounds like your phone has serious hardware problems.

opcow said:
Sorry to say it, but it sounds like your phone has serious hardware problems.
Click to expand...
Click to collapse
Is there nothing I can do? Because I'm pretty sure I'm way past return date, and I didn't have a warranty.

well it sounds that you have messed it up. your installation is probably wrong somewhere, in fact i am even sure, but i dont want to hurt anybody.
do a clean install from scratch starting everything with ODIN (ie download mode)
first off all load a ancien but correct kernel, because in fact you don't even know what you lagfix is. load one of the zenkins kernels (ya-ok) no matter one of the recent ones.
start and go back into recovery, and adjust lagfix to ext4 only. not ext4/ext2
don't use not either the integrated voodoo.
it will format everything.
the again into recovery and disable lagfix
that will then reformat everything into rfs, that what it's needed.
then you go again into reboot and flash one of the ancien .tar files like xwjpa.
and then it shoudl startup.
and you can take it from there.

zoubidou said:
well it sounds that you have messed it up. your installation is probably wrong somewhere, in fact i am even sure, but i dont want to hurt anybody.
do a clean install from scratch starting everything with ODIN (ie download mode)
first off all load a ancien but correct kernel, because in fact you don't even know what you lagfix is. load one of the zenkins kernels (ya-ok) no matter one of the recent ones.
start and go back into recovery, and adjust lagfix to ext4 only. not ext4/ext2
don't use not either the integrated voodoo.
it will format everything.
the again into recovery and disable lagfix
that will then reformat everything into rfs, that what it's needed.
then you go again into reboot and flash one of the ancien .tar files like xwjpa.
and then it shoudl startup.
and you can take it from there.
Click to expand...
Click to collapse
Please read earlier posts... I cannot get into recovery mode and the computer won't recognize download mode.

mikel.canovas said:
Is there nothing I can do? Because I'm pretty sure I'm way past return date, and I didn't have a warranty.
Click to expand...
Click to collapse
Unless you have a bad USB cable causing all the weirdness with both charging and the PC connection, but that wouldn't explain all the other strange errors. It sounds to me like the phone is terminally ill.

opcow said:
Unless you have a bad USB cable causing all the weirdness with both charging and the PC connection, but that wouldn't explain all the other strange errors. It sounds to me like the phone is terminally ill.
Click to expand...
Click to collapse
Doesn't there have to be a way to revert to stock if it's all because of the ROM? I really don't want to just give up and throw away a semi-new Captivate and have to break contract to buy another one.

mikel.canovas said:
Doesn't there have to be a way to revert to stock if it's all because of the ROM? I really don't want to just give up and throw away a semi-new Captivate and have to break contract to buy another one.
Click to expand...
Click to collapse
I've seen no accounts of bad flashes causing problems like you described. Particularly the phone not being detected in download mode and the AC charging funkiness. Besides, you already tried reflashing it and not only did that not help, it revealed all sorts of other symptoms.

opcow said:
I've seen no accounts of bad flashes causing problems like you described. Particularly the phone not being detected in download mode and the AC charging funkiness. Besides, you already tried reflashing it and not only did that not help, it revealed all sorts of other symptoms.
Click to expand...
Click to collapse
Ok. Thanks. If anyone else has any other ideas. Please post

I've had the Captivate for around 4 months. Does anyone know if I short out the phone and say it got really hot then shut off, they will exchange it?

mikel.canovas said:
I've had the Captivate for around 4 months. Does anyone know if I short out the phone and say it got really hot then shut off, they will exchange it?
Click to expand...
Click to collapse
Or you could just rob a liquor store and use the proceeds to buy a new one.

[Q] nvflash unbrick problem...hopeless brick?

I was running my TF with prime v1.5 and an overclock kernel (at 1.4GHz variable rate with setCPU). It all worked like a charm. Then the unlock screen froze and the screen went dark.
I have tried everything to reboot but nothing works (including volume- + PWR for CWM, etc).
I can get into APX mode though and I have tried nvflash with the nvflash version prime 1.5. However after working for several steps the process stops each time with this message:
failed executing command 14 NvError 0x30012
command failure: create failed
I am not sure what to do at this point and I am thinking the TF is irreversibly bricked.
Here are my questions:
1. Anything I can do to fix this with nvflash? I was thinking of trying v1.4 of prime but I am doubtful it will make any difference.
2. If it is truly bricked is there any way I can wipe the system in APX mode before maybe sending it in for service?
3. Anyone have any experience with ASUS service on this? I believe that I have technically voided the warranty with the root/mods.
Thanks for the help.

mike infinity said:
I can get into APX mode though and I have tried nvflash with the nvflash version prime 1.5. However after working for several steps the process stops each time with this message:
failed executing command 14 NvError 0x30012
command failure: create failed
Click to expand...
Click to collapse
That doesn't look healthy. I take it that error comes up on the TF itself, or is it on your computer?
mike infinity said:
1. Anything I can do to fix this with nvflash? I was thinking of trying v1.4 of prime but I am doubtful it will make any difference.
Click to expand...
Click to collapse
Assuming you followed the steps exactly as laid out and you still got problems (like the above error, for instance), you could be in trouble. Perhaps the overclocking you performed killed it? Not sure.
mike infinity said:
2. If it is truly bricked is there any way I can wipe the system in APX mode before maybe sending it in for service?
Click to expand...
Click to collapse
I'm not sure there is, I think APX mode is only for flashing a new ROM.
mike infinity said:
3. Anyone have any experience with ASUS service on this? I believe that I have technically voided the warranty with the root/mods.
Click to expand...
Click to collapse
Yes you have voided the warranty, manufacturers of Android devices in general don't look too kindly upon you rooting their devices and trying to claim warranty, given that it's your risk not theirs. A bit like seeing if your TF would survive a drop from a tall building on purpose, and then trying to claim warranty if it breaks as if it's their fault .

you should try the 1.4 nvflash because the 1.5 didnt work for me too. There are some files missing i assume.
The description u just gave seems more like hardware failure than software. Anyway worth to try since u get to apx.
Good luck m8
Link to download 1.4:
http://www.sdx-downloads.com/devs/roach2010/flash_roms/

The error comes up on the computer, not the TF.

sounds like you have fried your hardware...but I am no expert or hacker. I have loaded kernel celsym blades, running at 1.4 well, doing a lot of stuff running fine so it shoulnt have done anything. I would recommend PMing the developers of Prime and Kernels the development section, if someone there is able to answer?

mike infinity said:
The error comes up on the computer, not the TF.
Click to expand...
Click to collapse
Sounds more like the .img files are not in the right place. Make sure the system.img, boot.img and recovery.img files are in the same directory as the nvflash files. Cheers.

MasterfullDON said:
sounds like you have fried your hardware...but I am no expert or hacker. I have loaded kernel celsym blades, running at 1.4 well, doing a lot of stuff running fine so it shoulnt have done anything. I would recommend PMing the developers of Prime and Kernels the development section, if someone there is able to answer?
Click to expand...
Click to collapse
The OP already said that CWM isn't working.

UPDATE:
I used the nvflash version of prime v1.4 and the process completed successfully! Not sure what the problem was with v1.5 (I had the correct files in the correct folder in the process). When I replaced with v1.4 nvflash completed successfully and the system rebooted.
However, there now seems to be another problem: When the system boots up it asks me to plug in the charger as the battery is low....It then shuts down even though the charger is plugged in.
I did plug in the TF when it was bricked (APX only)...but I am guessing it was not charging at the time.
Now that it is re-imaged and is able to boot, I assume it would be able to recharge. This does not seem to be the case.
Any thoughts?

mike infinity said:
UPDATE:
I used the nvflash version of prime v1.4 and the process completed successfully! Not sure what the problem was with v1.5 (I had the correct files in the correct folder in the process). When I replaced with v1.4 nvflash completed successfully and the system rebooted.
However, there now seems to be another problem: When the system boots up it asks me to plug in the charger as the battery is low....It then shuts down even though the charger is plugged in.
I did plug in the TF when it was bricked (APX only)...but I am guessing it was not charging at the time.
Now that it is re-imaged and is able to boot, I assume it would be able to recharge. This does not seem to be the case.
Any thoughts?
Click to expand...
Click to collapse
Are you trying to charge via USB? If so this won't work (not very well, at least), you have to be plugged into the wall to charge.

I am using the power supply. I have checked all of the connections to make sure the box that plugs into the AC is solid, etc.
I have noticed a few threads on bad charging units...maybe mine got fried somehow (although seems like a strange coincidence for both my charger and the TF to get bricked simultaneously...the TF was recharging at the time it was bricked).
I am going to spend $20 and get a dynex charger that others report to work with the TF. If it doesn't I will return it.

UPDATE:
Well, I got the dynex dx-ua for $10 (open box)...and now my TF is working perfectly again! I will now begin the process of reinstalling my apps and getting back to v1.5 with CWM.
I'm not sure what gives with the power supply...maybe that was the issue from the beginning and not the v1.5 + overclock...or maybe the overclock killed the PS as well as caused the brick? I don't see how it could cause a brick since the TF seems to work normally now with no hardware failure (except the PS).
Anyway I guess these forums are a blessing and a curse. On the one hand we get great mods that greatly enhance the user experience in some cases and we get fixes when things go wrong. On the other hand we get the potential for bricking and voiding the warranty.
I am liking this dx-ua charger from dynex. It has connectors for every device in my collection. A small bonus after a week of believing my TF was toast.

mike infinity said:
UPDATE:
Well, I got the dynex dx-ua for $10 (open box)...and now my TF is working perfectly again! I will now begin the process of reinstalling my apps and getting back to v1.5 with CWM.
I'm not sure what gives with the power supply...maybe that was the issue from the beginning and not the v1.5 + overclock...or maybe the overclock killed the PS as well as caused the brick? I don't see how it could cause a brick since the TF seems to work normally now with no hardware failure (except the PS).
Anyway I guess these forums are a blessing and a curse. On the one hand we get great mods that greatly enhance the user experience in some cases and we get fixes when things go wrong. On the other hand we get the potential for bricking and voiding the warranty.
I am liking this dx-ua charger from dynex. It has connectors for every device in my collection. A small bonus after a week of believing my TF was toast.
Click to expand...
Click to collapse
This is just my suggestion so take it as you will, but i would VERY strongly suggest flashing stock and running this unmoded for a few weeks. I know it would be a pita to reinstall your apps twice, but if there really is a problem with the hardware, it might rear its head again. This way, if you need to rma it, you are completely stock.

I'm not sure what gives with the power supply...maybe that was the issue from the beginning and not the v1.5 + overclock...or maybe the overclock killed the PS as well as caused the brick? I don't see how it could cause a brick since the TF seems to work normally now with no hardware failure (except the PS).
Click to expand...
Click to collapse
The overclock may include upping the voltage to the cpu. This might have caused the load on the power supply to be too high to power the unit and charge the two batteries, and burnt out the power supply.

AustinMartin said:
The overclock may include upping the voltage to the cpu. This might have caused the load on the power supply to be too high to power the unit and charge the two batteries, and burnt out the power supply.
Click to expand...
Click to collapse
This is my guess as well.
The tablet did freeze on the lock screen as well...yet the hardware seems none the worse for wear with the new power supply.

[Q] Only hboot works (partly) until I drain the battery

Hi guys, I'm not on the ICS wave yet, my old problem keeps bugging me. What happened:
I have a B70 Transformer. It rooted OK, then I flashed Prime with OC kernel. Seemed to work fine until one day it didn't wake up from sleep. Battery was full, cause I just unplugged it from the charger. No power up, no recovery, nothing. The only thing that worked was powering up in hboot (VolUp+Pwr). It then identified as a USB device when I connect it to a pc and the moment I try to do anything with nvflash the tablet cut communication with no explanation and died (I'm runnig Linux and followed the system log) until I power it with VolUp+Pwr again.
I found a way to reset it: leave it on hboot until battery drains completely, then plug the charger and the transformer magically wakes up. I was happy to have a workaround, but after a couple of weeks this thing started to happen every other day and the tablet spent more time draining battery in hboot than actually working...
At some point I flashed revolver and things went back to normal! I was using standard kernel, not OC one this time. Until yesterday, when I flashed the Revolver OTA that arrived. Flash was OK, rebooted and started using the tablet then bam.... dead...
It's again running the drain procedure now, I guess tomorrow I'll be able to power it up again. One thing I noticed is when I flashed the first time and now, I left the SD card in the slot after I was done flashing. When I installed Revolver last time I removed the SD card right after it booted and the OS was running just fine. Do you think this may be connected to the problem?

Hey, quick question. What command are you using in Linux to test your TF being connected via usb? Mine doesn't even show up in lsusb
Thanks.

I open a terminal and do a tail -f /var/log/messages
you see new devices announced and when they drop too

Yes thanks, already tried that but I never got anything at all. I'm starting to worry that it could be my main board is dead or something.

[Q] Phone doesn't charge, reboot freezes

G2x running Cm7.2RC and trinity.
On occasion (3-5 times per week), I'll plug my phone in to charge at night only to see that it is not charging. When I try to reboot, I get the rebooting screen which then freezes and requires a battery pull. When the phone is then rebooted after the pull, everything works fine. Anything I can do to fix this?

wcpatton said:
G2x running Cm7.2RC and trinity.
On occasion (3-5 times per week), I'll plug my phone in to charge at night only to see that it is not charging. When I try to reboot, I get the rebooting screen which then freezes and requires a battery pull. When the phone is then rebooted after the pull, everything works fine. Anything I can do to fix this?
Click to expand...
Click to collapse
Charging is controlled from the Kernel. I'd suggest trying a different Kernel. Faux's kernels might help, or stick with stock kernel?

New2my8125 said:
Charging is controlled from the Kernel. I'd suggest trying a different Kernel. Faux's kernels might help, or stick with stock kernel?
Click to expand...
Click to collapse
Faux's kernerls have never worked well with my phone, maybe the newest are better. Thanks.

I think Harsh also has a CM7 Kernel you can give a stab at as well. He's got a good CM9 Kernel, but I think he also sprinkled in there mix a CM7 version as well. Check out his Kernel thread in the Dev forums.
EDIT: http://forum.xda-developers.com/showthread.php?t=1843518
Please visit that thread. I had the wrong one listed earlier..

Just following up here that Harsh's kernel screwed up my phone pretty good. Had to use the full clean up tool to restore the correct partitions. Was pretty ugly. Trying clean CM7.2 for now.

Try going into developer settings and selecting "keep screen on while charging " than when you charge it just tap the power key to shut the screen off. May or may not help. All my cm7 battery woes were helped by changing that setting and staying outta airplane mode.
Sent from G2x running BuROM v0.2 (root; mod stock 2.3.4) w/ faux's GB kernel 014b2-ext4.

justjackyl said:
Try going into developer settings and selecting "keep screen on while charging " than when you charge it just tap the power key to shut the screen off. May or may not help. All my cm7 battery woes were helped by changing that setting and staying outta airplane mode.
Sent from G2x running BuROM v0.2 (root; mod stock 2.3.4) w/ faux's GB kernel 014b2-ext4.
Click to expand...
Click to collapse
I've had that checked since I got my phone and I still have the occasional time where I plug the charger in and the phone just says, "Screw you pal. I'm not charging!". It happens to me MAYBE once a month. I can deal with that.
That option helps curb the blank SoD's more than the "Not charging" issues.

The kernel screwed up my SD card too. Had to transfer everything to computer hd then format the sd then move everything back. What a pain. I think things are back to normal now though.

[Q] TF700 completely dead and unresponsive

HI guys,
So I'm posting this as a vain last resort hoping that someone has had an issue like this before (and resolved it..)
I've had a tf700 for 6 months now. Never had any major issues with it hardware-wise.
About a month ago I got tired of waiting on Asus to update the firmware (and do something about the dreaded lag) so I unlocked and started using CM10.1 nightlies. Everything was vastly sweeter!
Yesterday, tablet was around 50% charge so I plugged it in for the train ride home. 10 minutes later I went to unlock it and ...nothing..nada...zip.
I figured it had locked up so I tried a soft reset. Then i noticed there was no indicator light even though it was plugged in.
Cue an increasingly desperate sequence of trying ever reset option I could find:
Power for 10, 20, 30, 60 secs... nothing.
Power + down vol... nothing.
Power + up vol... nothing.
Pinhole Reset button... nothing.
Plugged into pc ... nothing (not detected by PC)
Checked the charger was working on the dock ... all OK there.
Tried docking the tablet .. no effect.
Tried charging through the dock ... nothing.
Tried leaving it plugged in overnight... nothing.
Basically, there is no sign of life at all (including charging indicator light).
I'm presuming I'll have to go down the RMA route but thought I'd throw it out there for opinions / suggestions.
Thanks
Orko

Ouch.
When not even the charging light comes up... I think you indeed have an RMA to call in. I'm sorry for your loss.

Today I also have the same problem.
On the train on my way to my work i read my newspaper on my tablet, put it of to go to my work, 10 minutes later when I push the power to put it on, NOTHING.
Long press, even everything listed above, nothing happens even no charging led.
I have put cleanrom on the tablet and that worked fine, no more lag much faster, nog random reboots, but now I don't have any warrenty because it is unlocked.
I am really dissapointed now, buying a new one without unlocking is really no option because the standaard TF700 is way too slow.
700 euro waisted...
http://forum.xda-developers.com/images/icons/icon9.gif

Had you both used an overclocked kernel? Which kernel was in use anyway?

MartyHulskemper said:
Had you both used an overclocked kernel? Which kernel was in use anyway?
Click to expand...
Click to collapse
Hadn't messed with the stock kernel ... think the firmware was 10.4.4.23

Had you both plugged them in to charge on the train? Could the cause be dirty power frying something in the tablet?
Sent from my SCH-I535 using Tapatalk 2 Beta-5

carteje said:
Had you both plugged them in to charge on the train? Could the cause be dirty power frying something in the tablet?
Sent from my SCH-I535 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Mine was in my office..... Plugged in to a surge protector for good measure.
I see some painful (and expensive) RMA action in my future

This just happened to me as well. I plugged it in last night, and when I went to use it today... nothing. Completely unresponsive, no charging light indicator or anything. Though mine was completely stock, still locked and un-rooted.

Funny that earlier this morning, I had a crack;ing sound from my unit as well, and it acted up afterward. I ascribed it to fooling around with H's kernel too enthusiastically -- I sincere hope we haven't gotten an epidemic of fried Infinities on our hands. The digital equivalent of the zombie apocalypse. :S

Wow another user pm'ed me yesterday with the exact same issue. Unit just died. No power to boot.
How can 4 people all suffer the same problem in one day???? :silly:

sbdags said:
Wow another user pm'ed me yesterday with the exact same issue. Unit just died. No power to boot.
How can 4 people all suffer the same problem in one day???? :silly:
Click to expand...
Click to collapse
Mine went into a bootloop. I struggled to get out of it, because most of my files reside on the microSD and not on internal storage (some older files and backups live there). I was on data2sd initally, but decided to flash normally to determine the problem (suspecting a damaged partition on the microSD) -- the moment I removed the microSD card, the unit would boot fine, but after inserting it again, bootloop. I only saw the very first ASUS logo, before the revolving circle comes up, for just a few seconds, and reboot -- rinsed and repeated that sequence a few times while I was recovering my jaw from the floor. Whenever I flashed the data2sd mod for CROMI, I was screwed, obviously. I have flashed over a dozen times -- one of the definitions of clinical insanity is repeating behaviour while expecting a different outcome every time. You go figure. Fortunately, it was only temporary (at least, I'd like to think so, thank you!).
In the end, I ended up keeping a normal and perfectly functional install, for I still had the 2.5h commute to home from the night shift -- yes, this was towards the end of a night shift :S -- so I could at least read for a bit.
After fomatting everything yet again -- including giving the microSD a digital meltdown with gParted -- I finally got it working again, although I lost nearly all new data since the last backup. Those were mostly pictures from Reddit (earthp*rn, anyone?) and some TED talks, so while extremely annoying, it's not like I have lost pictures of my children or something...
Whew... It sure was an exciting day. Off to sleep now. G'night, people!

wtf? that is strange indeed. I thought it was just a bad power source but the surge protector post threw me off. that sucks, if there is a digital ghost running around which I wouldnt doubt, better keep your tabs protected. I also have heard my tablet crack and pop a coulpe of times since havig flashed multiple roms and kernels on it but nothing with the on mechanism breaking. maybe try going to one of those electronic fixer upper places nd see if they can open it up and see what components got fried

*Caution with the overclocking to everyone that's trying it.
Download and install an app that keeps an eye on processor temps.
My tablet runs hot OC'ed so I got in the habit of watching out for extremes.

Wel,
My kernel is TF700: Clemsyn 1.5 - 1.8ghz 650GPU Kernel and I use it always on 1.5ghz.
when It happened it was not connected to a charger, I just put it of on the train and tried to put it on 10 minutes later.
I don't do anything special with my tablet, just reading pdf, newspaper, foto's mail and facebook.
I always put it in a pretective sleeve, I always handle it with care.
And now just SUDDEN DEATH the only way I can call it, because I did not do anything special.
I would like to remove the battery, I kinow for smartphones when nothing happens then a removal of the battery helps. But can't do that here.
:crying:

Is there no way you can make the battery empty so it will do a reset ?
where can you find the serial number on the tablet

Zuran said:
where can you find the serial number on the tablet
Click to expand...
Click to collapse
On the sticker near the charging port that says "S/N:".

TF700 dead
I have the same problem. My infinity is unlocked so the warranty is void. One day it just turned off. It will not charge. No charge light. I've tried everything listed here but nothing. I tried a new charge cable, nothing. I even replaced the battery, still nothing. Disappointing for sure. I guess I'll keep it around until someone finds a cure. I'm gonna have to replace it, but definitely not anything else Asus.

My Infinity died too. After unlocking and rooting, I flashed the cleanrom with the 1,8ghz kernel. Everything was fine when I booted for the first time. Used the balanced profile to start with, but since the device felt very laggy and slow, I tried the normal profile. Didn't help, so I tried rebooting it with the new reboot menu I got on the powerbutton. Then the Infinity died. No charging light, no nothing. I ran it for about 10 min on the balanced, and like 5 min on the normal profile.

Mine died with about 30% battery. I clicked a notification and it went black. No charging light. No USB sound from PC when connected. No vibrate. Nothing. Was about 4 days from bestbuy return window closing. Returned no problem.
It was rooted and running stock kernal and had only been on for a few minutes.
Sent from my HTC PH39100 using xda app-developers app

It seems it is happening to people who run the overclocked kernal. So I will probably stay away from all oc kernals over reading this thread because I once had it on my tf700 but will never again. Sorry you guys lost your tablets
Sent from my ASUS Transformer Pad TF700T Infinity using Tapatalk HD
Rom: CleanRom 3.4.4