[Q] Nexus 7 wifi 2012 power button issue - Nexus 7 Q&A, Help & Troubleshooting

Hey guys,
I am having 2012 wifi 8GB N7 for more than yr now and have recently started getting irritating problem making it unusable.
Its behaving as if its power button is continuously pressed even when i am not touching the tablet or sound / power buttons. Its operating on its own to restart, bring power menu in every situation i put it in, like in system standby condition, powered down condition or in bootloader or even in CWM recovery. Its operating function corresponding to power button.
Tablet is out of warranty so i am trying to troubleshoot and fix it myself (as far as i can) and but getting any clues from online available material too. Also out of warranty repairs are costly / worthless if service guy decide to change its PCB.
If anyone has faced similar issue/ got solution/ got it fixed from service guys, please suggest me what can be done. Is it a software issue or hardware issue like.
So far I have tried factory roms of 4.2.2, 4.3, CM versions and AOKP versions in rooted, non rooted, bootloader locked unlocked conditions. And from my understanding its not related to any roms. Heck it shows this erratic behavior even in bootloader mode or in CWM recovery.
Can there be anything which service guys do as far as software is concerned which we cant do, so that i can give them to fix it?

Looks like a hardware issue. The internal part of the button may be loose.
Sent from my AUXUS Nuclea N1 using xda app-developers app

Ain't nobody faced such issue ever? Please guys i need some inputs.
So far i tried disconnecting power/ volume button strip/ cable from motherboard and let it idle for sometime. Even tried booting with that strip removed, but it didnt solve the problem. So my thinking of this strip being the culprit is wrong (from my understanding).

Thought of giving an update to this issue..
Dismantled N7 completely taking help of youtube videos. Booted back up and problem persisted but with extreme low frequency. i.e. power command executed on its own after a long time. So used tablet for half and hr, updated it to 4.4.2 which was not possible in the condition it was in before. Later problem aggravated to initial level again. i.e. continuous restart, no operation possible.
So left tablet in powered off condition for a day. Switched it on again. And could use it for same half an hr without facing any problem. After that problem started troubling again.
If anyone can think of resolution, would appreciate assistance.
Thanks.

Another pleasant update.
Tab was lying unused for months with battery fully discharged. And later when i checked at random without even expecting any change in its condition..... it started perfectly.
And its working without any issue now. Hope this will help someone else facing problem.

Related

[Q] Beware - N7 screen crash while updating to 4.1.1

Hi Guys,
My N7 just arrived and it worked great out of the box - wifi connected, Google account connected. JB 4.1 pre-installed... then...
After about an hour of the tablet being on it came-up with a update request to take it from 4.1 to 4.1.1 - i accepted with the power lead in and power on.
The software lost control on the screen leaving it black with various shades of grey streaks across it. These change when the screen is touched - indicating the software is probably good underneath but the screen visual interface has crashed. Probably the display driver chip needs power cycling, else a feature of 4.1.1 is faulty in hardware?
Does anyone know how to recover from this - as there is no external hardware reset, the battery can't be removed, etc ?
I called Google (Call us at 0800 328 6081) and the guy told me to hold the power button in for 10 seconds which I did but the N7 just went off and came back on the same.
He then told me to hold in vol-up and vol-dwn buttons before holding in the power button. Again the device went off but came back on the same.
I include a picture of the N7 display after the unsuccessful 4.1.1 update.
Image https://docs.google.com/open?id=0B3oSwFvF1cmebXE4S2lvZlNlU0E
Cab
Also beware that lack of pirates is the the cause of global warming...
http://www.forbes.com/sites/erikaan...he-lack-of-pirates-is-causing-global-warming/
Looks like a defective unit. Not sure what pirates have to do with it.
Via my HTC Rezound
CrazyPeter said:
Also beware that lack of pirates is the the cause of global warming...
http://www.forbes.com/sites/erikaan...he-lack-of-pirates-is-causing-global-warming/
Click to expand...
Click to collapse
Thank you for being a productive member of this community, xda would not survive without you.
Sent from the matrix. (or my phone)
Not a good sign that it's doing it in fastboot mode. You can try leaving it in fastboot mode to drain the battery then plug it in and try again. Or, search for the instructions to reapply the stock 4.1 image. If those don't work then RMA it.
That looks very familiar.
A few minutes after the update (which I installed about 10 minutes in to receiving my new Nexus 7) I immediately had a total screen lockup/crash with lovely multicolours.
After that, any subsequent reboot/factory reset, the lockups continued and became more an more frequent until after just a day the device was completely unuseable.
I don't think the update caused it. I think it's factory defective and probably related to a messed-up Tegra 3.
Thanks for the feedback guys - I'm gonna RTM it as advised. A good unit shouldn't go wrong at all when just out of the box with no 'normal' or 'strange' apps added. It just had pure google stock on it.
cabello123 said:
Hi Guys,
My N7 just arrived and it worked great out of the box - wifi connected, Google account connected. JB 4.1 pre-installed... then...
After about an hour of the tablet being on it came-up with a update request to take it from 4.1 to 4.1.1 - i accepted with the power lead in and power on.
The software lost control on the screen leaving it black with various shades of grey streaks across it. These change when the screen is touched - indicating the software is probably good underneath but the screen visual interface has crashed. Probably the display driver chip needs power cycling, else a feature of 4.1.1 is faulty in hardware?
Does anyone know how to recover from this - as there is no external hardware reset, the battery can't be removed, etc ?
I called Google and the guy told me to hold the power button in for 10 seconds which I did but the N7 just went off and came back on the same.
He then told me to hold in vol-up and vol-dwn buttons before holding in the power button. Again the device went off but came back on the same.
Cab
Click to expand...
Click to collapse
Ok, I was about to post this very thing. Mine went red. Bright red. Nothing worked. Took it back to the store and it turned on fine and looked good...until the manager took it and flexed it a bit. Then, bam. Everything flickered and turned red.
So now I have new one (N7 16gig) and its working great. But the alert comes on telling me to upgrade to the 4.1.1. No way in Hell!! It's an hour drive back to the store to get another.
So what's the solution. Anyone else have this happening?
That is a very strange thing to happen. Although I dont think you should tell people to beware of upgrading the tablet because it makes it sound like it will happen to all tablets when upgrading. When I did mine it happened with no issues whatsoever.
jonnyg1097 said:
That is a very strange thing to happen. Although I dont think you should tell people to beware of upgrading the tablet because it makes it sound like it will happen to all tablets when upgrading. When I did mine it happened with no issues whatsoever.
Click to expand...
Click to collapse
I was not telling people to beware of upgrading. I was asking if others had experienced this.
cr2crf said:
I was not telling people to beware of upgrading. I was asking if others had experienced this.
Click to expand...
Click to collapse
So I finally updated the os to 4.1.1 Success. Hoping this little tab keeps going. The more I play with it the more I am glad I got it and not a 10 incher
Were these affected units stock unrooted? As a general rule you always want to revert back to stock unrooted before applying any OTA updates.

[Q] Broken display

Hello all,
(First of all, if you watch the video you will understand what I'm trying to explain here, but I wasn't able to make myself very clear, secondly I don't have support from asus/google in my country)
I've been using my nexus 7 for almost 4 months and haven't had any problems with it until now. When I upgraded to 4.2 I noticed that the speakers sound was strange sometimes, but most of the time it worked just fine. But today something very sad happened
When I unlocked the tablet I realized it was in my sister's user (I was already at launcher's "home"), so I locked it in order to switch to my user, but when I pressed the unlock button, the screen wasn't normal, it went crazy. I couldn't see anything, just shades of black and white (see video above for details). After that I tried anything but the the screen was the same. Something important to mention is that the screen responds normal to touch input, so I can unlock, open menu, recent apps, etc only by knowing where to touch. I'm even able to turn it off by holding power button and then choosing "yes, reboot tablet" without being able to see anything on the screen.
It worth mention that after several reboots, screen locks/unlocks I manege to get the screen to work perfectly for a couple of minutes, but when I locked the tabled the screen stopped working again.
My question is: DO you guys think that this is a screen problem, some wires that aren't well connected or even maybe Android OS problem? And would it worth it to buy a new screen and try to find someone to change it for me or I should just throw it in the trash?
PS: The tablet is completely stock now, just rooted and with busybox, no OC, no GPU OC, etc...
http://www.youtube.com/watch?v=Sna69-GKIYE&feature=g-crec
Try flashing a factory image. If that doesn't work, it's most likely a hardware issue. You should be able to get warranty service if that's the case.
Factory image: https://developers.google.com/android/nexus/images#nakasigjop40d
Edit: Missed the part about no support from Google/Asus. Disregard the warranty statement.
Sent from my Nexus 7 w/ PA and m-kernel
Problem kind of solved
EvanA said:
Try flashing a factory image. If that doesn't work, it's most likely a hardware issue. You should be able to get warranty service if that's the case.
Factory image: https://developers.google.com/android/nexus/images#nakasigjop40d
Edit: Missed the part about no support from Google/Asus. Disregard the warranty statement.
Sent from my Nexus 7 w/ PA and m-kernel
Click to expand...
Click to collapse
Thanks for the answer. I decided to do that (even though I didn't think it would solve the issue).
I turned off the tablet and booted into recovery by holding vol up and down + power and guess what??? when it booted into recovery the screen was perfect again, I could see all information about the tablet, lock state, etc. I decide to reboot it and it has been working normally for a couple of hours from now, I have even made some benchmarks and everything was ok.
Now I'm more confused than before: Hardware or OS problem? The tablet is working now, so I'll just backup all my titanium backup data to my pc and leave USB debugging on, so if the problem returns I'll just flash stock again.
EDIT: After some hours the screen problem returned. I flashed 4.2.1 and the problem was still there. I guess I'll just have to find someone who will open my tablet and see if the wires are properly connected.

[Q] My CM11nightly phone is dead?

Hi all,
I have been coming to this forum for a while now but since I lost my login data I had to re-register and now can't post in the developers section.
My i9505 has one of the latest CM11 nightlies on it, and it worked fine apart from the device switching of for no appearent reason when in its holster (might have been unintentional pushing of buttons, I don't know) and sometimes not booting properly. Usually after some "convincing" by pushing the on button again it would start up eventually.
Today, it switched off again and now seems completely dead. No reaction what so ever when pushing/holding the "on" button, or the recovery or download button combo. When attaching the charger no animation is shown and the device seems to get pretty hot pretty fast.
Does anyone have an idea on what might be wrong, and is there anything I can still try to revive it, or should I just send it in for repairs? If it is dead no one can see there is a custom rom on it, right? So it should be covered by warranty...
Thanks upfront for any help!
Bommeldinges said:
Hi all,
I have been coming to this forum for a while now but since I lost my login data I had to re-register and now can't post in the developers section.
My i9505 has one of the latest CM11 nightlies on it, and it worked fine apart from the device switching of for no appearent reason when in its holster (might have been unintentional pushing of buttons, I don't know) and sometimes not booting properly. Usually after some "convincing" by pushing the on button again it would start up eventually.
Today, it switched off again and now seems completely dead. No reaction what so ever when pushing/holding the "on" button, or the recovery or download button combo. When attaching the charger no animation is shown and the device seems to get pretty hot pretty fast.
Does anyone have an idea on what might be wrong, and is there anything I can still try to revive it, or should I just send it in for repairs? If it is dead no one can see there is a custom rom on it, right? So it should be covered by warranty...
Thanks upfront for any help!
Click to expand...
Click to collapse
As u said if your device "gets pretty hot in a very short time" maybe its a hardware problem(wrong chip)... Maybe some high voltage or someting...
Try a new battery, if that does not work, its dead I think..

Phone suddenly hard-bricked. No recent flashing.

Hi everybody,
What Happened:
My phone has suddenly become totally unresponsive. I have been using it most of the day, it was sitting at around 70% the time that it happened, but it is now a totally black screen. I had just taken it out of my pocket and it was suddenly like this.
The only idea I could come up with as to why this happened is that I charged it off of a JBL Charge 2 last night. I'm not sure if that may have messed with the battery, but I do find it odd that it's totally unresponsive while plugged in.
I was running android 7.1.1 DP2, with the ElementalX kernel 4.0 I believe. I was also rooted with SuperSU. What's really odd is that I hadn't done anything new recently besides install uTorrent and VLC media player. Otherwise, my routine has not changed one bit. Up to when the phone actually died, I hadn't even used either of these new apps the entire day.
What I've Tried:
I have tried plugging it in via AC, via USB, I've tried booting into recovery or fastboot, but there is zero response from the phone. No indicators on the screen, no LED blinks, no vibrations, nothing.
What I'll Try:
If anyone has any experience with this happening, I could use some advice. Otherwise I'm just going to wait it out, consider an RMA I guess. However, my device did have the bootloader unlocked and was rooted, so.... I hope it comes back by itself.
My advice is to keep it plugged in, or see if there is a response on the computer perhaps on fastboot, upon using the bootloader keys. I haven't had this, just a few suggestions. Good luck!
PS: A RMA will probably be needed, there are much more experienced people around here. Sure you may get replies later.
Good luck?problem all nexus 6p!!! Lg responds repay helps, hawuei what to do? problem arises with nogaut not be our fault, how to fix this? My phone now in service but to be fair this? warranty and having to wait ..

HTC U Ultra - Home button keeps failing

Hi all,
Long time no post here!
I have an HTC U Ultra, about one year old, heavy usage. All of a sudden the Home button has started to fail. I have fingerprint scanning enabled, but it doesn't work when the screen is unlocked either, so I'm not sure it is related to the fingerprint scanner, I think it's more a hardware/software issue with the button...
I have followed another thread on this but I'm not able to resolve it.
The only thing that seems to temporarily resolve the issue is to switch it off, give the screen a good wet wipe clean and then switch it back on again. Just rebooting doesn't resolve the issue.
It seems to be getting worse in as much as it seems to be failing more often and increased regularity. I'm reluctant to factory reset it as I'll have to reconfigure it all again and I have read on other threads that it does not resolve the problem. The back and other (don't know what it is called!) button work fine.
Does anyone know what the cause is or shall I send it in for repair?
Thanks in advance for any advice.
Interesting this just started happening to me too , also 1 year and few month old phone and heavy usage.
Not to mention that since day 1 , the charger that came with the phone suddenly stops charging.
I bought another original HTC charger, and it behaves exactly the same.
especially when battery is very low like 10% or less, it don't charge at all.
I regret buying this phone, worst phone I have ever had
gavin watson said:
Hi all,
Long time no post here!
I have an HTC U Ultra, about one year old, heavy usage. All of a sudden the Home button has started to fail. I have fingerprint scanning enabled, but it doesn't work when the screen is unlocked either, so I'm not sure it is related to the fingerprint scanner, I think it's more a hardware/software issue with the button...
I have followed another thread on this but I'm not able to resolve it.
The only thing that seems to temporarily resolve the issue is to switch it off, give the screen a good wet wipe clean and then switch it back on again. Just rebooting doesn't resolve the issue.
It seems to be getting worse in as much as it seems to be failing more often and increased regularity. I'm reluctant to factory reset it as I'll have to reconfigure it all again and I have read on other threads that it does not resolve the problem. The back and other (don't know what it is called!) button work fine.
Does anyone know what the cause is or shall I send it in for repair?
Thanks in advance for any advice.
Click to expand...
Click to collapse

Categories

Resources