Related
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.
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.
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.
- I saw the Android L dev preview ported over to the nexus 4, so i decided to root my phone.
- Here is what i did at first I downloaded an app and did a one click root it did work but being a novice I also wanted to have a custom recovery without any hassle.
- So I downloaded Wugs Nexus root toolkit and firstly I undid the previous root, then using this program I re-rooted and installed a custom recovery.
- I went on to install "L-Mako-b5-bunny-stew-and-kool-aid.zip" at first my playstore wouldn't work and I was getting a persistent error (error 920) so I reinstalled the rom and it started working.
- So here I am thinking I'm done and there aren't any other problems left to fix.
- Last night I went to sleep while my phone battery was at 3%, I think it fully drained and now it won't boot or even charge. Have I hard bricked my phone and what can I do to fix this?
thanks, please help me!
Edit: I've also charged the phone for
- 1 hour
-Over night
- There is no response while charging, holding power, holding power & vol down, connecting to computer gives nothing
I might have messed up big time?
mufc786 said:
- I saw the Android L dev preview ported over to the nexus 4, so i decided to root my phone.
- Here is what i did at first I downloaded an app and did a one click root it did work but being a novice I also wanted to have a custom recovery without any hassle.
- So I downloaded Wugs Nexus root toolkit and firstly I undid the previous root, then using this program I re-rooted and installed a custom recovery.
- I went on to install "L-Mako-b5-bunny-stew-and-kool-aid.zip" at first my playstore wouldn't work and I was getting a persistent error (error 920) so I reinstalled the rom and it started working.
- So here I am thinking I'm done and there aren't any other problems left to fix.
- Last night I went to sleep while my phone battery was at 3%, I think it fully drained and now it won't boot or even charge. Have I hard bricked my phone and what can I do to fix this?
thanks, please help me!
Edit: I've also charged the phone for
- 1 hour
-Over night
- There is no response while charging, holding power, holding power & vol down, connecting to computer gives nothing
I might have messed up big time?
Click to expand...
Click to collapse
1. Hold power+both volume buttons, while charging, for 10 seconds.
2. Try using a different charger.
3. Go to a gsm service...
abaaaabbbb63 said:
1. Hold power+both volume buttons, while charging, for 10 seconds.
2. Try using a different charger.
3. Go to a gsm service...
Click to expand...
Click to collapse
I bought it 2nd hand from Cex (second hand retailer in UK). Luckily I still had 2 months of warranty left so they've taken it in for repairs. I don't know if they'll find out it's hard bricked (if it is), or not.
Unfortunately happened to me, too, yesterday, while rebooted my Nexus 4. It doesn't boot. The LED blink once, red, and nothing. The worst thing is it's the Service page from LG Romania website "is not available". Now I'm digging the web to find a solution
okay guys screw CeX (second hand UK retailer with 1 year warranty on ALL electronics). I took my supposed dead nexus 4 to them and the guy took it in for repairs (I'm 2 months from the end of my warranty). So they take it in and I go in 2 weeks later as they haven't updated me on the progress.
Get into the store and the guy pulls my phone out. He says because it has a crack on the back they can't book it in for repairs. I ask him why did they take it in if it wasn't going to be booked in, his reply, well its obvious no one would fix a phone with a crack in it! This guy was the goddamn manager.
So since about 2/3 weeks my phone's been dead I haven't touched it. I'll try again tomorrow but hopefully it will start working. Wish me luck.
And is it possible to hardbrick a phone because its battery dies out AND the ROM/Bootloader can't allow the device to charge?
I was sitting on my couch yesterday, and my nexus 10 froze up. This is pretty normal as it freezes up alot and i have to hold the power button down for 10 seconds and restart it. But it went to the bootloader screen and now its stuck in there. I have never rooted my device or have never even attempted to, my device has been stock since day 1. Pushing the RECOVERY MODE, RESTART BOOTLOADER, START buttons do nothing but restart the device into bootloader. I have searched up and down these forums for a solution and cannot find anything, everything thats related with this problem is because of a ROOT, once again i did not root or have ever attempted to root my device. please help. here is a youtube video with the problem. BTW my device is not recognized in windows either.
Edit: so i cant post a video cause im new on the sight. Im really stuck on what to do here.
razrus said:
I was sitting on my couch yesterday, and my nexus 10 froze up. This is pretty normal as it freezes up alot and i have to hold the power button down for 10 seconds and restart it. But it went to the bootloader screen and now its stuck in there. I have never rooted my device or have never even attempted to, my device has been stock since day 1. Pushing the RECOVERY MODE, RESTART BOOTLOADER, START buttons do nothing but restart the device into bootloader. I have searched up and down these forums for a solution and cannot find anything, everything thats related with this problem is because of a ROOT, once again i did not root or have ever attempted to root my device. please help. here is a youtube video with the problem. BTW my device is not recognized in windows either.
Edit: so i cant post a video cause im new on the sight. Im really stuck on what to do here.
Click to expand...
Click to collapse
So if you hold both volume buttons + power button, then select "Recovery Mode" with the power button, it just reboots back to that same exact bootloader screen? You don't see the Android laying on it's back with a red exclamation mark over him?
Sent from my Nexus 6 using Tapatalk
charesa39 said:
So if you hold both volume buttons + power button, then select "Recovery Mode" with the power button, it just reboots back to that same exact bootloader screen? You don't see the Android laying on it's back with a red exclamation mark over him?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I was finally able to get it to a screen by holding the down volume + power that says "downloading do not turn off target nexus 10", but that still did nothing. Thats the only thing that it will let me do besides constantly rebooting to the same bootloader screen, no matter which option i choose.
razrus said:
I was finally able to get it to a screen by holding the down volume + power that says "downloading do not turn off target nexus 10", but that still did nothing. Thats the only thing that it will let me do besides constantly rebooting to the same bootloader screen, no matter which option i choose.
Click to expand...
Click to collapse
That's the Samsung Download Mode, which is different from the bootloader. Could it be possible that your volume button may be stuck, and that's why it keeps bringing you back to the bootloader? I mean, you should at least be able to boot into Recovery Mode. If not, the only solution I can think of is unlocking the bootloader and flashing the factory image. Maybe your partitions got corrupted somehow?
charesa39 said:
That's the Samsung Download Mode, which is different from the bootloader. Could it be possible that your volume button may be stuck, and that's why it keeps bringing you back to the bootloader? I mean, you should at least be able to boot into Recovery Mode. If not, the only solution I can think of is unlocking the bootloader and flashing the factory image. Maybe your partitions got corrupted somehow?
Click to expand...
Click to collapse
I dont think the volume button is stuck, when i select recovery it just restarts and vibrates twice. When i power it off and start it it vibrates once, dont know if that helps. I also remember my battery being below 15% when it froze up. My device has froze up alot since the day i got it, is that normal? maybe it did destroy the partitions.
razrus said:
I dont think the volume button is stuck, when i select recovery it just restarts and vibrates twice. When i power it off and start it it vibrates once, dont know if that helps. I also remember my battery being below 15% when it froze up. My device has froze up alot since the day i got it, is that normal? maybe it did destroy the partitions.
Click to expand...
Click to collapse
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
charesa39 said:
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
Click to expand...
Click to collapse
Really? Never froze? mine would freeze all the time, especially watching youtube videos, i just thought it was normal haha, maybe something was actually wrong with it this whole time. Ive had it for a little over a year now. The battery did die when i left bootloader on over night, but automatically started itself up into bootloader when it had some charge. i might just contact google at this point to see what they say, like i said i never have rooted it or did anything other then normal usage. maybe they can help me.
charesa39 said:
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
Click to expand...
Click to collapse
Really? Never froze? mine would freeze all the time, especially watching youtube videos, i just thought it was normal haha, maybe something was actually wrong with it this whole time. Ive had it for a little over a year now. The battery did die when i left bootloader on over night, but automatically started itself up into bootloader when it had some charge. i might just contact google at this point to see what they say, like i said i never have rooted it or did anything other then normal usage. maybe they can help me.
So I called google and they transfered me to samsung, and samsung transferred me to google. no one seems like they could possibly help me. This is frustrating and i dont think ill buy another nexus tablet, or anything nexus for that matter. i dont even think i can sell this on ebay at this point, and if someone were to be able to get it up and running, all my data might still be on there. ARRRGGGHHH ive never owned something that has "bricked" and not been able to fix it. this one looks hopeless.
razrus said:
So I called google and they transfered me to samsung, and samsung transferred me to google. no one seems like they could possibly help me. This is frustrating and i dont think ill buy another nexus tablet, or anything nexus for that matter. i dont even think i can sell this on ebay at this point, and if someone were to be able to get it up and running, all my data might still be on there. ARRRGGGHHH ive never owned something that has "bricked" and not been able to fix it. this one looks hopeless.
Click to expand...
Click to collapse
That sucks. I can empathize as I (and I'm sure plenty of others) know how it feels to get the runaround. Always frustrating. Well, I am thinking the only shot at possibly getting it working again is to unlock the bootloader and flash a factory image. Chances are always good that with a Nexus (barring any hardware issues), flashing a factory image will get it running again. That's why it's Nexus only for me, as Nexus devices are virtually unbrickable. Not sure if you have any experience with Fastboot and ADB. If not, I'm sure you can find some useful research tools on the interwebs and here on XDA. Once you understand it, here are a couple threads with some simplified installers: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2317790. Do keep in mind that UNLOCKING THE BOOTLOADER ERASES YOUR DATA, so you will lose everything on your N10. But at this point, it's all about getting it working again so you're not stuck with a $300 paperweight.
charesa39 said:
That sucks. I can empathize as I (and I'm sure plenty of others) know how it feels to get the runaround. Always frustrating. Well, I am thinking the only shot at possibly getting it working again is to unlock the bootloader and flash a factory image. Chances are always good that with a Nexus (barring any hardware issues), flashing a factory image will get it running again. That's why it's Nexus only for me, as Nexus devices are virtually unbrickable. Not sure if you have any experience with Fastboot and ADB. If not, I'm sure you can find some useful research tools on the interwebs and here on XDA. Once you understand it, here are a couple threads with some simplified installers: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2317790. Do keep in mind that UNLOCKING THE BOOTLOADER ERASES YOUR DATA, so you will lose everything on your N10. But at this point, it's all about getting it working again so you're not stuck with a $300 paperweight.
Click to expand...
Click to collapse
Is it possible to flash even though it's not recognized by windows?
razrus said:
Is it possible to flash even though it's not recognized by windows?
Click to expand...
Click to collapse
It's not recognizing it because you need the drivers so it knows it's connected in bootloader mode.
charesa39 said:
It's not recognizing it because you need the drivers so it knows it's connected in bootloader mode.
Click to expand...
Click to collapse
i have the device up and working now! Thank you so much for you help! I had to unlock my device with the nexus root toolkit after installing that usb fix you suggested, then i had to flash it, but the 5.1 update would get stuck in a bootloop, so i installed 4.4 and it worked. Lost all my data but thats ok. Thanks so much.:highfive:
Edit: Google play was not working, tried updating android software and it got stuck in the bootloop again. will try and tweak it more tomorrow, im gunna look for other custom firmwares as well, dont have to have stock anymore.
razrus said:
i have the device up and working now! Thank you so much for you help! I had to unlock my device with the nexus root toolkit after installing that usb fix you suggested, then i had to flash it, but the 5.1 update would get stuck in a bootloop, so i installed 4.4 and it worked. Lost all my data but thats ok. Thanks so much.:highfive:
Edit: Google play was not working, tried updating android software and it got stuck in the bootloop again. will try and tweak it more tomorrow, im gunna look for other custom firmwares as well, dont have to have stock anymore.
Click to expand...
Click to collapse
That's great to hear. I'm glad it came back to life. :good: Although, I wouldn't suggest using a toolkit. In my experience from what I've seen around these forums, they tend to cause more harm than good. It's good if you understand everything that's going on, and they can prove useful for devices that have really complex unlocking and rooting procedures, but Nexus devices are so easy to unlock and flash manually. I always flash each image file manually so if something goes wrong, I know exactly where it went wrong and how to fix it. The Google Play issue you mentioned is a perfect example. Flashing manually also helped me learn the basics of Fastboot and ADB. So if you want to stay on stock 5.1, I would recommend reflashing the factory image manually. I always use this thread to help me out in case I forget something: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. Although it's for the Nexus 6, it's the same procedure for the Nexus 5, Nexus 10, Nexus 7, etc. That's the real convenient thing about Nexus devices as well, as they are all pretty much flashed the same way. Should all be really simple since you already have the drivers set up from installing the toolkit. Good luck! And have fun with your newly revived N10.