What happens is, my Nexus 7 will sometimes not awaken from a sleep state. Pressing and/or holding the Power/Lock button does nothing when this happens. The button otherwise works fine.
Faced with this dilemma, I tried to boot into recovery by holding Power/Lock+Volume Up+Volume Down. This needs to be held for about ten seconds to get a response out of the device. I haven't flashed or rooted, but I did update to 4.1.1. On successfully "booting into recovery", the Nexus 7 skips recovery and boots straight into the Google splash screen, after which it functions normally.
I thought this might have been a one-off issue, but it just happened again.
Is this just a software bug in 4.1.1, or is it faulty hardware? The unit is otherwise fine, no lifting bezel, speaker problems, dead pixels, etc. The next shipment of Nexus 7's isn't meant to get here until midway through August, but rather than hanging onto mine I'd prefer to have the security of a refund or guaranteed replacement if I can get one.
Bought locally in New Zealand.
Bump.
I'm going to take it back to the retailer to talk to them about it - I haven't done anything to the device other than updating to 4.1.1, so it can't be a firmware thing? I suppose it could be a buggy app, but I can't think of a reason why a buggy app would basically crash the Nexus 7 to the point where it won't turn on without using the recovery key combination.
If anyone has any input I'd love to hear it, I'm totally lost.
Related
Yesterday I have updated my TF101/US to 9.2.1.17 (not rooted, serial B50) and now my power button does not work at all. I cannot either shut it off (I can hold it for minutes, nothing happens), nor can I wake it up (the only possibility is to plug in the power). Reset to factory setting does not help
I talked to Asus, they suggested to send it to RMA, but I want to try to discharge it completely and check whether it helps.
Will keep this post updated if I find out something more.
Update: battery discharge did not fix the issue. Going to send the device to RMA.
Thanks for this post, this if for no other reason is why I will be dealing with my random reboots (they only occur once a week or so, if that often, for me so not a big problem, not like a broken power button would be) rather than updating the patch. However, this belongs in general or Q&A not development
Also for me you have to call assistance for a RMA: i could understand that power button does not turn off screen, but i can't understand, a part an hardware problem, how it does not shut down keeping power button down or why it does not turn on.
Yes, that sounds like hardware issue, but that must be very weird coincidence.
The complete story is that I just received device from RMA yesterday (LCD backlights were broken). I turned it on, it happened to have ICS already (it was sent with Honeycomb) and I was able to install all my software. Then a message re. new OTA update poped up, I decided to upgrade, and right after that power button stopped to work.
Yes, that can be hardware issue as well, that is why it goes to RMA. If I were 100% sure that this is software issue, I would wait some days hoping that ASUS will release bugfix for it.
Hmmm..the device will not power on if it is shut down? (How would you know this unless you shut down, and then can't turn it back on I don't know).
I re-read this and it is unlikely IMO that a firmware update could break your hardware, but I guess if a computer virus can break nuclear centrifuges anything is possible? Could be a coincidence..I feel for you, I had an over-discharge issue one night and my TF didn't want to boot up, and then flashed the red battery on the screen, but for those first few seconds my heart wasn't beating..I get the same feeling when I get a bad flash too lol
Luckily, the device wakes up when you plug the charger in. So, currently my choice is either to keep it running (disable sleep) or to have a charger and plug the charger in when I need to wake it up.
The bad thing is that the RMA "cycle" takes about two weeks.
Maybe it isn't a coincidence..
http://forum.xda-developers.com/showthread.php?t=1546640
Mine started this about two weeks ago before I picked up the update today... I thought i was the only one until I saw this post
I have misunderstood something: post says WAKE ON not TURN ON, ok this could be software related, but long press power button should be FORCE A SHUT DOWN...
Click this link on how to remove the front bezel. Then you can check the inside power switch to see if it's working:
http://www.techrepublic.com/photos/cracking-open-the-asus-eee-pad-transformer-tf101/6270147
That's the way I fixed my TF101 after I dropped it and the power button got stuck in the chassis.
Also read this thread:
http://forum.xda-developers.com/showthread.php?t=1391254
I think this is a solution to your problem, if it's not software related, which I doubt.
I get the same problem all the time, I leave it sitting for a couple hours come back and it won't turn on or off...
I also sometimes get the non functioning power button. I cannot consistently replicate it.
Sometimes it happens after it sleeps for awhile.
Sometimes it turns on when I open the tablet up while connected to the dock.
I have to hold the power button until it reboots itself. This is annoying after while. And even getting more so.
I'm also having a power-on related issue since the ICS update but didn't want to start a whole new thread for it. Ever since the update my Transformer boots into CWM by default. If I power it down completely then press the power button the EEE Pad logo flashes on the screen, I hear an audible "click" (best way I can describe it) from the device and it boots into CWM. If I select "Reboot device now" from the CWM menu it boots right back into CWM.
The only way to boot properly now is to hold the volume down/power buttons until the menu comes up to choose between Android and recovery and choose Android. (It actually defaults to this so I can just let it sit 10 seconds or so)
Any ideas?
Headcase_Fargone said:
I'm also having a power-on related issue since the ICS update but didn't want to start a whole new thread for it. Ever since the update my Transformer boots into CWM by default. If I power it down completely then press the power button the EEE Pad logo flashes on the screen, I hear an audible "click" (best way I can describe it) from the device and it boots into CWM. If I select "Reboot device now" from the CWM menu it boots right back into CWM.
The only way to boot properly now is to hold the volume down/power buttons until the menu comes up to choose between Android and recovery and choose Android. (It actually defaults to this so I can just let it sit 10 seconds or so)
Any ideas?
Click to expand...
Click to collapse
exactly same problem as me now. holding volume down and power is the only way to start it up if it has been left alone for awhile. since the update.
nosup4u said:
exactly same problem as me now. holding volume down and power is the only way to start it up if it has been left alone for awhile. since the update.
Click to expand...
Click to collapse
Apparently it's a pretty common issue with the new version of CWM, as explained in this here thread.
So far the only solutions I'm seeing involve ADB commands or flashing a custom ROM.
fixed for now....
I had the same issue the power button would only cold power off the device. The only way to power back on is by connecting the charger.
I solved it for no in the following way which i do no recommend to anyone. I have opened the device and disconnected the battery for 5minutes. After connecting it back the device powered on with the power button as it should.
In my opinion it looks as if there's some power related controller that was "hang" and ignored the power button .
Any ideas ? Asus ?
So, a few days ago, I started having some problems with my stock Nexus 7 (not unlocked, no ROMs or anything like that). Some apps just wouldn't open, they would force close within a second of opening. Anyway, I think it might have stemmed from the game "Let's Golf 3", as problems started after playing that, and when going back in to it after a day of issues, a message appeared saying "Unfortunately, launcher has stopped" - it gave me the option to report or cancel, but whatever I pressed, the message popped back up. I pressed the sleep button, which seemed to turn my Nexus off somehow.
Then, when trying to to turn my Nexus back on, it just stays on the 'X' screen. I have done a factory wipe through the fastboot menu a few times, but it still stays stuck on the 'X' screen. To turn it off, I hold down the power button, but it just starts the process again automatically. The only way to actually turn the device off is through the fastboot menu.
I have seen talk of 'factory image' and drivers etc... but I am not too comfortable with that sort of thing. I know the basics of troubleshooting devices, but not much more. I am very wary of doing anything more than what the device provides me with.
Any idea how I can get my Nexus started, or am I going to have to look for a replacement?
If all else fails, then flash stock rom. If you're reluctant to do it the fastboot way, use toolkits. But it is very easy to flash a new stock rom. Go try it.
Leonhan said:
If all else fails, then flash stock rom. If you're reluctant to do it the fastboot way, use toolkits. But it is very easy to flash a new stock rom. Go try it.
Click to expand...
Click to collapse
Is that not for rooted devices?
Flashing the factory image for my N7, how do I know which version my nexus is? i.e. 4.1.2 (JZO54K) or 4.2.1 (JOP40D)?
AW: [Q] Nexus stuck on 'X' screen, even after full wipe
Gawge said:
Flashing the factory image for my N7, how do I know which version my nexus is? i.e. 4.1.2 (JZO54K) or 4.2.1 (JOP40D)?
Click to expand...
Click to collapse
Use the one you like, just choose the right one for grouper -> nakasi (wifi only) or nakasig (with simcard)
4.2.1 is the latest Android version...
Sent from my Nexus 7 running Android 4.2.1
mihahn said:
Use the one you like, just choose the right one for grouper -> nakasi (wifi only) or nakasig (with simcard)
4.2.1 is the latest Android version...
Sent from my Nexus 7 running Android 4.2.1
Click to expand...
Click to collapse
I too had the same problem. Tried everything. Finally gave it to ASUS service centre in Nehru Place. They will replace the mother board. May take 15 more days. So sad!
Okay, now the thing won't even turn on.
Holding the power button, and other combinations, nothing happens. No image comes up when charger is put in.
Feel like the thing is dead. Probably going to have to get it fixed or find a replacement. Don't want to spend too long without my Nexus
Gawge said:
Okay, now the thing won't even turn on.
Holding the power button, and other combinations, nothing happens. No image comes up when charger is put in.
Feel like the thing is dead. Probably going to have to get it fixed or find a replacement. Don't want to spend too long without my Nexus
Click to expand...
Click to collapse
FYI,
The tablet can "play possum" when it is in APX mode. (Which is easily entered from a cold start condiition with Vol-Up+Power) By that, I mean the device is on, but absolutely nothing ever appears on the screen. The only way to detect this is to plug it into a computer and the unknown APX device (USB Hardware Id VID_0955&PID_7330 ) will show up.
The only way to exit that mode is to hold the power button down continuously for 15-18 seconds. [size=+1]IF[/size] that happens, pressing the Vol-Down button immediately after the Google logo appears will pop you into Fastboot mode.
But, given that you have prior experience with other odd happenings on the tablet, the above hypothesis is a long shot, I'm more inclined to say "It's dead, Jim".
If everything fails let it sit for 3 hours on the charger (as long as it is not overheating or something) and try a few more things one last time before you ship it out.
bftb0 said:
FYI,
The tablet can "play possum" when it is in AVX mode. (Which is easily entered from a cold start condiition with Vol-Up+Power) By that, I mean the device is on, but absolutely nothing ever appears on the screen. The only way to detect this is to plug it into a computer and the unknown AVX device (USB Hardware Id VID_0955&PID_7330 ) will show up.
The only way to exit that mode is to hold the power button down continuously for 15-18 seconds. [size=+1]IF[/size] that happens, pressing the Vol-Down button immediately after the Google logo appears will pop you into Fastboot mode.
But, given that you have prior experience with other odd happenings on the tablet, the above hypothesis is a long shot, I'm more inclined to say "It's dead, Jim".
If everything fails let it sit for 3 hours on the charger (as long as it is not overheating or something) and try a few more things one last time before you ship it out.
Click to expand...
Click to collapse
Yeah, cheers, I have it on charge now, and i'll give it one last go.
What is the best way to fix/replace it? I bought it from Argos - will they take it back (bought back in December)?
Gawge said:
Okay, now the thing won't even turn on.
Holding the power button, and other combinations, nothing happens. No image comes up when charger is put in.
Feel like the thing is dead. Probably going to have to get it fixed or find a replacement. Don't want to spend too long without my Nexus
Click to expand...
Click to collapse
Service centre seems to be the only solution. My sympathies!
Gawge said:
Yeah, cheers, I have it on charge now, and i'll give it one last go.
What is the best way to fix/replace it? I bought it from Argos - will they take it back (bought back in December)?
Click to expand...
Click to collapse
Call Asus first. Make sure to let them know it is less than 2 months old. If they want you to perform the return through the original retailer, they will tell you. But it's best to eliminate any other middlemen if that is possible, as I suppose that the tablet ultimately goes back to Asus anyway.
(Might be different through other channels, e.g. PlayStore - I dont know).
So, I got one of the original 8GB Nexus when they first launched, I unlocked and moved away from stock for a while. I later passed it on to my other half and flashed it back to stock. Since then it's started to exhibit strange behavior and since updating to 4.3 it seems to have given up the ghost and now will only boot to stock recovery (I can't even access the bootloader itself, it goes straight from the Google screen to the android on his back with a red exclamation mark).
I didn't do the update myself, so I'm not sure if it was the actual update that's the culprit - have there been any incidents of 4.3 bricking devices?
Anyway, I can't get the menu to come up when it's in the stock recovery, when I press power and volume down the screen just dims or lights up, nothing else.
At this point, am I just screwed in so far as recovering the Nexus myself and would Google even consider an RMA with it being unlocked?
Sorry for the wall of text guys, I'd really appreciate any insight or advice.
First, if you got it when first launched, your 1 year warranty is up. It was released mid July 2012 (in the US).
Second, if it doesn't display anything, they can't know.
Do a search for 'flashing factory image', or 'unbrick Nexus 7', download and follow instructions.
You can start with this :
http://www.nexus7nexus10.com/forum/...ore-your-nexus-7-s-factory-state-windows.html
Barring a damaged emmc or serious software issues that should fix it.
Good night everybody, I'm dipping my toes into phone/tablet repairs and I have a strange case with a Nexus 7 32GB model, first it was stuck at the Google screen that has a open padlock, after flashing it with Android 4.2.2(JDQ39) and updated the bootloader from 3.12 to 4.18 it finally started working, but if I turn it off after 5 seconds the tablet boots up by itself, the power button is working fine, and I can lock and unlock the screen just fine using the power button, any ideas of what it can be?
My first idea was to do all the updates up to Android 5.0.2 hoping that it might solve the problem.
Best regards and thanks in advance.
It reboots and then works normal?
Really weird
Yes, I reboots and is working perfectly, except for the touch-screen, already tried 3 new digitizers and no sign of life out of them, works with no problem with a mouse.
I friend of mine told me that it is supposed to reboot when the power button is pressed for a long time, but I can't find evidence of that information googling around.
Hello friends,
My LeEco Le Pro3 (727) bricked two days ago and I haven't had any luck turning it back on. It was running LineageOS 8.1 latest official build with an unlocked bootloader, Magisk 16.0, TWRP 3.2.1, and OpenGapps ARM64 8.1 nano. Immediately prior to bricking I was setting it up for bluetooth with my car and was trying to run Google Maps through voice command. As I directed Google Maps to take me to a location, the phone froze, the screen got all "fuzzy" and I got the dreaded blue screen of death.
From that point on I have not been able to turn the phone back on. When I press the power button it will vibrate every 5-10 seconds as though it will turn on but it never does. Ive tried everything I can think of to get to work again including:
- Pressing power button for 2 min, 5 mins, 10 mins
- Pressing power button + vol up (recovery) for 2 min, 5 mins, 10 mins
- Pressing power button + vol down (fastboot) for 2 min, 5 mins, 10 mins
- Pressing power button + vol up + vol down (QFIL MODE) -> Installing Qualcomm driver, downloading "FlashOne2.0", flashing all versions of "qfil files" that I could find but still unable to boot up
- Pressing all different button combinations while plugged in to computer/charger
- Using different cords/chargers/usb ports
- Leaving it to charge overnight/full day then trying to boot up
- Leaving it sitting not charging for a full day then trying to boot up
At this point I'm starting to think it might be a hardware issue but who knows..
Any advice/suggestions would be greatly appreciated.
Thank you.
Where did you buy it from.
I don't have much to add here it seems like you have done everything that you could
Let's clear this up no fashboot right.
Only one thing to try hold power down then plug in USB.
Sent from my LEX727 using xda premium
My one did the same, the issue was motherboard. You should send it back to repair.
mchlbenner said:
Where did you buy it from.
I don't have much to add here it seems like you have done everything that you could
Let's clear this up no fashboot right.
Only one thing to try hold power down then plug in USB.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Thank you for the reply.
It was purchased from a local retailer here in the United States through Google Express. Fortunately I should still be able to return it for a full refund but I would rather have a working phone than my money back.
No flashboot either. It's like the phone just decided to quit working one day. Tried holding power while plugging in USB as well and no change.
marik1 said:
My one did the same, the issue was motherboard. You should send it back to repair.
Click to expand...
Click to collapse
The conclusion I'm reaching at this point too. I'll see what the return policy.
Well if it will not turn on it is hardware issue you should be able to return it.
Sent from my LEX727 using xda premium
That is so strange. The screen going fuzzy like that is indicative of a hardware issue, IMO. I saw that on my laptop once, but that was because I hit the screen too hard. Never seen a BSOD on an Android device before. TIL.
I assume you've already tried an adb logcat. Were you using the original LeEco cable? I heard it has issues since it's not up to spec. 99% hardware failure, but I can't help but think it has something to do with driver communication confusing the device and causing hardware failure (?) if that's even possible.
Just a final update for those curious.
After leaving the phone alone for two days I plugged it into the charger and low and behold it started vibrating and booted up by itself. It was running a Chinese developers editions 720 rom due to the QFIL File I had flashed in my earlier in my attempt to fix it. Battery was drained so I let it charge for a while and everything was fine until I attempted to restart the phone. As the boot animation was loading, I got the blue screen of death for a second time.
I took a quick picture, the phone shut off itself off, and same as before it wouldn't boot again. As other users have suggested it appears to be a hardware issue, likely with the motherboard. Fortunately I was still able to return the phone (purchased through Google Express via a local retailer) and received a full refund. I've since bought another Le Pro3 (727) and hopefully when that one comes in, it won't have any issues.
Thanks to all the users who left suggestions/tips.
shyboi122 said:
Just a final update for those curious.
I've since bought another Le Pro3 (727) and hopefully when that one comes in, it won't have any issues.
Thanks to all the users who left suggestions/tips.
Click to expand...
Click to collapse
You bought the same phone again? :good: You're courageous, lol.
i been experiencing the exact problem like your on my x720, as i boot up the system or enterting the recovery mode the screen go fuzzy on loading screen and shut itself off completly, i can still able access fastboot. As i left it for a while the phone will be able to almost finish the boot then ending it all with a blue screen.
Have anyone found a way to fix this DIY since my phone has past the guarantee plan ?