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.
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.
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).
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.
I've dealt with a few bricked phones in the past that have been a simple fix through ADB/Recovery, but this one really perplexes me.
So I get work, place my phone on the desk, and a few minuets into the day I see it re-boot out of the corner of my eye. It's not something to be expected but this has happened a few time over the 5 months I've had this phone so I think nothing of it.
But 5 minuets later its still looping on the Google logo. So hold down the sleep button to shut it down, still loops. The only thing I have done to this phone is unlock the bootloader through the command prompt and install a stock Nougat image straight from Google
Using the hardware keys I can get into the the bootloader, but that's it. "Recovery Mode" option sends the phone back into a loop so I can't reset the phone to factory (though ideally I would like to save the thousands of photos on the device) or enable USB Debugging as I can't get into Android.
I have Googles Android USB Driver installed, Windows 10 chimes when I plug it in, It appears in Device Manager as "Android Bootloader Interface" but I have not been able to get it to show in the terminal with ADB. I have also tried on a Windows 7 and OSX Laptop.
I am completely dumbfounded, any help/ideas would be amazing!
Thank you
BrickOfNexus said:
I've dealt with a few bricked phones in the past that have been a simple fix through ADB/Recovery, but this one really perplexes me.
So I get work, place my phone on the desk, and a few minuets into the day I see it re-boot out of the corner of my eye. It's not something to be expected but this has happened a few time over the 5 months I've had this phone so I think nothing of it.
But 5 minuets later its still looping on the Google logo. So hold down the sleep button to shut it down, still loops. The only thing I have done to this phone is unlock the bootloader through the command prompt and install a stock Nougat image straight from Google
Using the hardware keys I can get into the the bootloader, but that's it. "Recovery Mode" option sends the phone back into a loop so I can't reset the phone to factory (though ideally I would like to save the thousands of photos on the device) or enable USB Debugging as I can't get into Android.
I have Googles Android USB Driver installed, Windows 10 chimes when I plug it in, It appears in Device Manager as "Android Bootloader Interface" but I have not been able to get it to show in the terminal with ADB. I have also tried on a Windows 7 and OSX Laptop.
I am completely dumbfounded, any help/ideas would be amazing!
Thank you
Click to expand...
Click to collapse
Hi... There is no available fix for the moment. Check this thread. You are not alone
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528/page19
BrickOfNexus said:
... Using the hardware keys I can get into the the bootloader, but that's it. "Recovery Mode" option sends the phone back into a loop so I can't reset the phone to factory (though ideally I would like to save the thousands of photos on the device) or enable USB Debugging as I can't get into Android....
Click to expand...
Click to collapse
Unfortunately @5.1 is right. The common denominator of the BLOD (many threads on this) is the inability to get into recovery mode by any means. ADB doesn't work unless in recovery. Without ADB you will not be able to pull anything off the phone. At least you are unlocked so you can try some tools and/or manually attempt to fastboot boot or fastboot flash a custom recovery and get ADB working, but chances are almost non-existent. Some ppl have been able to briefly get back into recovery on completely full charge, but it seems to start boot looping again shortly afterwards from recovery. Hopefully you were using Photos and synced recently. If you bought direct from Google, contact them even if out of warranty. If they won't help you or you didn't buy from Google, approach Huawei for an RMA.
I was in your situation and was able to flash the full stock image (flash-all.bat command) even though my device didn't show up on ABD--but maybe I just got lucky. I thought there was no chance it would work but it did. Some people reported getting out of the boot loop using Skipsoft's tool but most likely you will need to RMA the device if it's still under warranty from Huawei. Sorry to hear you have been added to this club. There are a lot of lemon 6Ps that die because of hardware issues (according to Google) and they clearly don't care because they never recalled the affected devices. I was hoping it was just the early generation phones but if yours is 5 months old that means the problem is persisting. None of these things might still be running in a couple years which is ridiculous for a premium phone. Makes you think twice about buying another phone from Google since they threw 6p owners under the bus rather than offering 6P owners a credit or something for their defective 6Ps. Good luck. At this point I think people need to create a class action suit against Google. That's the only way people got repairs or compensation from Apple the numerous times they pulled stuff like this with defective products. Why should Google get away with selling what they themselves admit is a defective phone?