Related
Hey, I got my transformer yesterday, and for some reason this is the 2nd time this has happened, fully charged battery, but the device won't power on. Attempted to plug into power but no dice. Held the power button for 30 seconds, nothing, held the power and volume up and nothing. Yesterday when this happened I plugged it into my computer (Windows) and held the power and up buttons and it turned on though it could have been windows detecting the drivers. Anyone else having this? Any suggestions? I haven't had a chance to test again and see if I can bring it back through that trick yet, but I will. Then I'll try a factory reset and see if it resolves the issue. I would hate it if this is a defective unit, that's for sure esp since they are so backordered. Outside of that I love the device.
naturefreak85 said:
Hey, I got my transformer yesterday, and for some reason this is the 2nd time this has happened, fully charged battery, but the device won't power on. Attempted to plug into power but no dice. Held the power button for 30 seconds, nothing, held the power and volume up and nothing. Yesterday when this happened I plugged it into my computer (Windows) and held the power and up buttons and it turned on though it could have been windows detecting the drivers. Anyone else having this? Any suggestions? I haven't had a chance to test again and see if I can bring it back through that trick yet, but I will. Then I'll try a factory reset and see if it resolves the issue. I would hate it if this is a defective unit, that's for sure esp since they are so backordered. Outside of that I love the device.
Click to expand...
Click to collapse
when your device isnt coming on, does your computer give you a usb notification? You could be putting it in apx mode on accident.
dcmtnbkr said:
when your device isnt coming on, does your computer give you a usb notification? You could be putting it in apx mode on accident.
Click to expand...
Click to collapse
I will find out in a few. The thing is this has happened when I left the device unplugged and in sleep when driving to/from work. Yesterday plugging it back into the computer brought it to life. Nothing else did. Not sure what apx mode is even.
Sent from my MB860
EDIT: Ok, turns out it get stuck in some weird power mode. I plugged it into the computer with no resolution, when I held the power button for 10 seconds, then waited 5 and pressed it again, the device powered on. I suspect it might be an issue involving detecting WiFi access points when driving or something else. I'll Factory Restore and see what happens.
try turning off screen lock.
naturefreak85 said:
I will find out in a few. The thing is this has happened when I left the device unplugged and in sleep when driving to/from work. Yesterday plugging it back into the computer brought it to life. Nothing else did. Not sure what apx mode is even.
Sent from my MB860
EDIT: Ok, turns out it get stuck in some weird power mode. I plugged it into the computer with no resolution, when I held the power button for 10 seconds, then waited 5 and pressed it again, the device powered on. I suspect it might be an issue involving detecting WiFi access points when driving or something else. I'll Factory Restore and see what happens.
Click to expand...
Click to collapse
I had that sometimes in the first day I had it, after that it hasn't happened. No factory reset, just make sure to do a hard shutdown (powerbutton 10 sec~) while it's booted and it should fix the issue.
seshmaru said:
I had that sometimes in the first day I had it, after that it hasn't happened. No factory reset, just make sure to do a hard shutdown (powerbutton 10 sec~) while it's booted and it should fix the issue.
Click to expand...
Click to collapse
Yea, it had happened once already, and again. I'll be testing today when I leave work, factory reset and see what happens. Should it continue, I'll go to the next step. I'm just not sure what it is. Interesting bug to say the least.
naturefreak85 said:
I will find out in a few. The thing is this has happened when I left the device unplugged and in sleep when driving to/from work. Yesterday plugging it back into the computer brought it to life. Nothing else did. Not sure what apx mode is even.
Sent from my MB860
EDIT: Ok, turns out it get stuck in some weird power mode. I plugged it into the computer with no resolution, when I held the power button for 10 seconds, then waited 5 and pressed it again, the device powered on. I suspect it might be an issue involving detecting WiFi access points when driving or something else. I'll Factory Restore and see what happens.
Click to expand...
Click to collapse
From the way you are describing getting it to work again, it sounds like you were in apx mode...
dcmtnbkr said:
From the way you are describing getting it to work again, it sounds like you were in apx mode...
Click to expand...
Click to collapse
I still don't really know what APX mode is, from the limited things I have seen about it, in order to get into such, the device has to be powered off first. As far as I can tell, my device isn't randomly powering itself off and automatically going into APX mode. This happens without me touching the device. When I did the power off and on today, it wasn't plugged into the computer at all. There was no recognition from the computer that the device was plugged in.
Well as of today, my EEE Transformer is dead. Will not power on the screen, Asus offers a repair of 14 business days, unacceptable.
Powering on issue
Woah...I was scared to death when mine didn't turn on the next morning that I got the device. Charged it for an hour and try to turn on again, nothing.
Holding the buttons several different ways that I know how to reset it didn't work. Finally I held the button down for more than 10 seconds. Wait a few seconds, then it powered on. Why didn't they make a hard reset since you can't remove battery!??? Hope this is just some fluke and could be updated with firmware.
nxp3 said:
Woah...I was scared to death when mine didn't turn on the next morning that I got the device. Charged it for an hour and try to turn on again, nothing.
Holding the buttons several different ways that I know how to reset it didn't work. Finally I held the button down for more than 10 seconds. Wait a few seconds, then it powered on. Why didn't they make a hard reset since you can't remove battery!??? Hope this is just some fluke and could be updated with firmware.
Click to expand...
Click to collapse
Alas, mine didn't get resolved with that, computer detects it now, but no screen response. Asus tells me 14 business days to fix then says try to restore it with the Kernel Source Code. Unfortunately I can't see a way to do such from the folder and they decided to disconnect me.
There is a bug with the default lock screen that makes it so the screen doesnt power on occasionally. In order to work around this you need to disable the lock screen in the settings, or change it from the default one.
Obviously in order to do this initially it needs to be powered on and so you can see it. Therein lies your problem of course. To get around this, charge up your device so you know it has power, use the force power off method (10-12 second press of the power button), wait a few seconds (30+), then power on the device normally (5-6 second press of the power button).
If your screen doesnt come on after that, try a couple more times. It really is an RMA job if it continues to fail. If it does come on, let it boot up to the lock screen, and dont let the screen go off, keep it 'alive', unlock the device and change the lock screen in the options, to either be switched off, or to anything other than default.
This wont work for everyone, as obviously a few may actually have duff screens, but for some of you, it may just be the lock screen bug you are getting unlucky with.
Yea, I seem to have not only the lock screen bug but a defective screen. Unacceptable to me, but hey, what can I do? I've been disconnected 5 times so far, waiting on a manager and will be requesting a faster resolution than what they are offering me. (10-14 Business days is unacceptable)
stuntdouble said:
There is a bug with the default lock screen that makes it so the screen doesnt power on occasionally. In order to work around this you need to disable the lock screen in the settings, or change it from the default one.
Obviously in order to do this initially it needs to be powered on and so you can see it. Therein lies your problem of course. To get around this, charge up your device so you know it has power, use the force power off method (10-12 second press of the power button), wait a few seconds (30+), then power on the device normally (5-6 second press of the power button).
If your screen doesnt come on after that, try a couple more times. It really is an RMA job if it continues to fail. If it does come on, let it boot up to the lock screen, and dont let the screen go off, keep it 'alive', unlock the device and change the lock screen in the options, to either be switched off, or to anything other than default.
This wont work for everyone, as obviously a few may actually have duff screens, but for some of you, it may just be the lock screen bug you are getting unlucky with.
Click to expand...
Click to collapse
naturefreak85 said:
Yea, I seem to have not only the lock screen bug but a defective screen. Unacceptable to me, but hey, what can I do? I've been disconnected 5 times so far, waiting on a manager and will be requesting a faster resolution than what they are offering me. (10-14 Business days is unacceptable)
Click to expand...
Click to collapse
i am in the same boat as you, luckly i picked up the acer for the weekend because i didnt think i was going to get the asus. glad i did
I'm waiting on hold with Asus to see if they will do an Advance Repair, basically I get put on the line for the full price of the device until they declare mine broken since the return period on the Acer is 14 days at best buy. Quite outside of the repair period.
kenshin0088 said:
i am in the same boat as you, luckly i picked up the acer for the weekend because i didnt think i was going to get the asus. glad i did
Click to expand...
Click to collapse
what is the number you are calling, when i called they had almost no idea what i was talking about. they kept asking me if when i am pluged into the wall if thre was a light on the chager when there is no light lol i think they thot i had a laptop or netbook
18886783688 Option 2 Option 2 Option 5
kenshin0088 said:
what is the number you are calling, when i called they had almost no idea what i was talking about. they kept asking me if when i am pluged into the wall if thre was a light on the chager when there is no light lol i think they thot i had a laptop or netbook
Click to expand...
Click to collapse
did you find out anythinig from asus?
kenshin0088 said:
did you find out anythinig from asus?
Click to expand...
Click to collapse
Had to escalate it up to management and expressed I wanted an advance repair and was willing to give them my credit card number so they could place a hold on the card for the amount of a replacement until they got mine. Has to be escalated above the rep should hear back in a couple hours. If not I have an extension and will call back
Sent from my MB860
they are having me download the source code and try and force it to the transformer we will see if it works will report back
Hi everyone, just got the tablet today and set it up at work, played with it for bit and everthing was working fine.
Got home about 2 hours ago and now when I wake it from Sleep, the touch screen is not responding at all. Have tried everything, power is 98%, plugged into a PC, did the hard reboot, even wiping the data to start setup again. But all to no avail.
The screen isn't responding at all. Its very frustrating as I want to play with it some more!!!
Hope someone has experienced this and can help.
had the same issue once...i turned it off and left it for about 5min...turned it on and the screen works again...
this hasn't occured since then..probably just a system glitch..
Happened to me once, reset the device and it worked. Now it happened again and its been unusable for a day. If it doesn't work tonight, the $hit is going to hit the fan...
Are you stuck at the lock screen immediately after booting because the unlock function doesn't respond to touch? If so, I'm having the same situation. I really hope that waiting a few minutes does the trick...
Edit: even did a full wipe and the thing is still unresponsive. I assume this is a very bad sign. FML.
Have you guys contacted ASUS support? They will probably have you RMA it. How long did you guys have it before this happened? Now I'm worried that mine will do the same thing.
ASUS support did want to RMA my TF that was having this problem. However, after leaving it off for a couple hours, I went to turn it on to wipe out all my account settings and the touchscreen started working again.
I have no explanation for why it started working though. The last thing I did before it was magically fixed was go through the normal shutdown procedure by answering the 'do you want to shut down' using the dock's mouse instead of just holding down the power button. Maybe that made a difference?
Blue_Man said:
Are you stuck at the lock screen immediately after booting because the unlock function doesn't respond to touch? If so, I'm having the same situation. I really hope that waiting a few minutes does the trick...
Edit: even did a full wipe and the thing is still unresponsive. I assume this is a very bad sign. FML.
Click to expand...
Click to collapse
This is what happened to me. Stuck at the lock screen, no touch at all. After 4 days of waiting for Asus to reply to my email and several disconnected phone calls, I have returned it to newegg. Since this item is still out of stock I expect to receive a full refund. Which is fine by me. June 8th, here I come.
Same thing happened to me, just returned it to fry's and was able to avoid the restocking fee. Going to get the galaxy tab come june 8th now instead.
Sent from my Xoom using XDA Premium App
I have weird little quirky things like this happen from time to time with my TF, such as having to hit the power button or lock button twice before it works. I think it might be more of a software issue than anything to be honest. Hoping that future updates will correct all of these issues.
I hope its a software issue....
Found a solution that worked for me. I booted into recovery mode by holding vol down and power. then I selected vol up to enter recovery. Then the exclamation point came up with the android robot. I left it like that for a few minutes then held down the power until it resarted.
It booted up like normal, no data lost. I then restarted for good measure. Came right back up like normal, touch screen and all.
Thanks jdmnash. I followed your instructions and it worked like a breeze. Should make this part of a sticky help thread.
Found a solution
Update: Tried every fix I could identify on the forums as I was also draining the battery as suggested on several forums. After 4 days waiting for the battery to drain, I was able to restart the TF and get active responses to the touchscreen. Unfortunately I had performed a reset and wipe earlier so I am having to reload everything. I am happy to have a functioning TF again, but have serious concerns about this failure and this awkward repair method. Additionally, I have still not had a response from ASUS support from 5 days ago.
Mine is constantly doing this. Randomly.
Its as if the daemon for screen touch detection crashes. The rest of the unit is fine but that stops and the only fix is a power button off, then on.
Something is not right here. Its vanilla out of the box, no extra software just the 13 FW update.
Will 3.1 fix this? Hopefully, as it stands, this will have to be returned. It is not fit for purpose, constantly failing.
same problem
Just picked up mine. Out of the box at a cafe it worked just fine. Brought it home and same problem as everyone else in this thread. Have tried all of the suggestions in this thread (except waiting for the battery to die). Even installed the 3.1 update via SD. Still no joy. Guess I'll try a few more things before returning it. My guess is a problem in the supply chain with the capacitors that detect screen touch. Doubt that it can be solved solely through a software update (or if it can it definitely didn't make it into 3.1)
my touch screen stopped working a week ago while i was at school. and i got really pissed and just kept on rebooting it and after like 5 or 6 reboots it started working. Havent had same problem since.
Hmm... thanks for suggestion. Tried booting it about 5 times but still borked. Draining the battery now as my last attempt before taking it back.
Update: I ran the battery down to zero. Charged it up for 30 mins and now it works again. Hope I don't have to repeat that very often.
BTW, the fastest way I could find to run down the battery was to power on while holding down the volume down button. Then just leave it sitting in that state until it reboots itself and then repeat.
Unstable touchscreen
obi-nine said:
Update: I ran the battery down to zero. Charged it up for 30 mins and now it works again. Hope I don't have to repeat that very often.
BTW, the fastest way I could find to run down the battery was to power on while holding down the volume down button. Then just leave it sitting in that state until it reboots itself and then repeat.
Click to expand...
Click to collapse
Hi , After the battery is zero and then 30 minutes charging, in order to make it work , did you discharge it right after 30 minutes or still you keep it charging ?
I got same problem with my TF which is really a disappointment.. I tried to factory reset, reboot ... but still can't make it work. I have to try this trick by draining the battery to zero. Hopefully, I get advise from all of you for this problem ?
Thanks a lot
Can you guys try using ADW launcher and see if things improve?
I think it did for me.
I have a rooted stock phone that stopped working for no apparent reason (no new ROM flashed, no configuration change). It starts, shows the Samsung logo, and immediately reboots. I tried to put it in download mode, when i hold the 3 keys I see the download logo showing up, but it reboots after a few seconds anyway. after a while it will start looping through the battery charge screen (which shows the battery as empty). I tried 2 different batteries with no change. Any idea how to get something working again?
That almost sounds like some sort of power issue. Have you left it sit turned off until the battery was full?
Yes, I left it overnight and it just keeps flashing the battery screen and then resets. I also have an external charger and used it to charge the battery, so it's not an issue with the battery actually being empty.
Have you been able to get the phone into download mode previously?
Have you have dealt with a boot loop and performed an Odin recovery previously? If not, remember it can take a few tries to get download mode to pop up.
If you can't get Odin to go, you might try flashing with Kies.
I am wondering if your phone met with some kind of disaster when you weren't around (trauma or liquid).
anyone747 said:
I have a rooted stock phone that stopped working for no apparent reason (no new ROM flashed, no configuration change). It starts, shows the Samsung logo, and immediately reboots. I tried to put it in download mode, when i hold the 3 keys I see the download logo showing up, but it reboots after a few seconds anyway. after a while it will start looping through the battery charge screen (which shows the battery as empty). I tried 2 different batteries with no change. Any idea how to get something working again?
Click to expand...
Click to collapse
This sounds almost exactly like the problem I had with my Sidekick. In my case, it turned out to be a bad battery and a loose ribbon cable on the motherboard. I'd check those two things.
This happened to me as well, and the three-button method to get into download mode wasn't working. For some odd reason, for me to get into download mode all I have to do is hold down the power button + track pad, and it goes right into download mode... Maybe slightly different model?
Try that - power button + trackpad
Bootloops.
Not a guaranteed fix by any means but for troubleshooting purposes you may want to consider making a USB JIG. It will most definitely help you figure out just how serious the problem is and if it IS software related with a way to get it working again you will need the JIG anyway so its worth a shot. If nothing else you learn a new skill and you're the proud owner of an incredibly useful tool that you can say you made yourself. good luck!
I know this post is kind of old, but it just happened to me last week (same circumstance, a rooted phone, but stock). I ended up just pulling the battery out and pressing the power button a couple times to hopefully drian it and letting it sit for 15 minutes, and then I put the battery back in and it worked again. I now have another rom flashed on it, I hate stock.
I know this forum is ancient, but I'm working on an E-Bay phone with this exact issue. I found the following thread the most useful and informative on the problem:
http://forum.xda-developers.com/showthread.php?t=1996709
Hopefully this helps other.
what i did was hold the power volume and button between the menu n back with the left hand YES HOLD IT UNTILL THE PIT IS UPLOADED. then u can let go then slide in the vattery with the right.while checking off the flash bootloarders on the heimdall with it fixing my phone XD
I had this happen, I dissassembled the phone, and used an alcohol pad to clean the power button area, and manipulated the button a lot, let it dry, reassembled...it still bootlooped.
BELOW IS RISKY BUT WORKED FOR ME
So while the back cover was off (exposing the cicuit board but everything still connected) I inserted the battery and watched it boot loop...during this, I used a flathead screw driver to "short" the power button pins...this let it boot fully, and it has been fine since.
i smacked the phones power button a few times and it worked
I have done hours of searches and can't find the answer to my problem. Hopefully someone here can help.
My GT-N8013 is stuck in the Samsung Galaxy Note 10.1 logo screen. I can't even turn it off without it bringing this screen right back up. It only goes dead when I unplug it and let the battery run out of juice.
I can get it to restart into Odin Download mode, but not into the recovery mode. I can install roms and CWM and stock roms using both Kies and desktop Odin3, and I get "pass" status with no errors, most the time, when I do rom update, but I can't get to the restore screen with the power + volume up button, then releasing the power button and holding down the volume up button only. It just stays on the Logo screen.
I hold down the power + Volume down button and it will restart into the Warning screen that allows me to hit the volume down to go to the download screen or volume up to cancel and restart. Both the volume up and down buttons work for this action so I'm sure the buttons are working okay.
I thought maybe the battery wasn't charging right and that was preventing it from going into recovery mode, but I can charge it for a while and unplug it and the screen will stay on the logo screen for a long time, so I think the battery is okey.
Samsung just said I should send it in, but it is out of warranty and I don't want to put much more money into this devices since it is old and a new version is out now, but I hate to think a great device like this that worked so well for so long is now going to be worthless because I can't figure out how to fix it. Hardware seams to be working fine and just a few days ago, the software was working fine. I'm so confused.
Leading up to these events, I had it turned off for a few weeks because I was traveling and going on airplanes and never ended up using it on the trips so it remained turned off. When I turned it back on, there was a OTA system update that I wasn't sure what it did. Didn't appear to do anything noticeable. Still worked normal. Then a few days later I did a personal data wipe because I was going to sell it and get the new Note 10.1. I went through the new setup process without problems, everything was fine. I sold it to a guy and a day later he contacts me and says it isn't working properly and I've been dealing with this ever since. It didn't appear to have any physical damage and the custom binary download count was at "No" so I don't think he tried to load any custom roms. I don't think this guy is tech savvy enough to do anything but plug it in and use it normal, so I don't suspect foul play.
Any help would be greatly appreciated. Thanks.
Check this
http://forum.xda-developers.com/showthread.php?t=2477626
Sent from my GT-N8013 using Tapatalk HD
I have the exact same symptoms. (No recovery mode / stuck on boot screen even after fresh stock rom installed). Out of the blue after working fine the day before.
Anyone know:
a) of anything further that I can try to resurrect this
b) if I might still have any joy getting warranty service from the shop I bought it from in the UK / Samsung if they send it back to them. I have more than a year left on the 2-year warranty they provided, and have only ever run/attempted to run stock. However as I have been out of the UK my custom binary count has increased to 7 as I have tried to reinstall Stock Roms myself to fix the problem. (However OS version still shows as Samsung Official, not custom)
Thanks so much if anyone can help me
Custom binary 7 = warranty void .
I would try flashing Philz recovery tar through Odin and try recovery mode .
I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
alienjon said:
I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
Click to expand...
Click to collapse
See if you still can get your phone into download, fastboot or recovery mode. Here you can see the button combos: https://m.youtube.com/watch?v=YFaq4g-oa2Q
If you can get to recovery mode, click on wipe cache and reboot. If your phone still is stuck afterwards, go to recovery again. There is an option to wipe and reset the phone. Note that your data will be lost!!! Do it at your own risk. But a reset often is the last working choice when your phone behaves strangely.
If you get none of the three mentioned modes to work, I think your Pixel has a hardware fault.
Hope this helps.
check the charging port first....whether it is charging or not......try to connect to PC
i guess the phone is not charging
So the bottom line is this is still somewhat ongoing, though I’ve confirmed the phone is definitely bricked. I brought it into UBreakIFix and after taking it apart (noting that the device seemed physically in great shape) that there wasn’t anything obviously wrong with any of the particular hardware (they mentioned that replacing the motherboard would likely do it, but it would be about as expensive and effective as buying a new phone anyway...).
I ended up writing back to Google and am in back and forth talks with them now. I’m not sure what they can or will do, but my final answer will have to be getting a new phone one way or the other.