Related
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.
Hi all, I've found that when I leave my Player on sleep for a while, I am unable to wake it back up. I've tried pressing the hardware button, the remote buttons, etc. The led is on, but there's no output or sound response from my TV. I have to unplug the NP and plug it back in. Probably a user error, but what's the process to wake the system?
Thanks in advance!
Sent from my SM-N910V using XDA Free mobile app
Action123 said:
Hi all, I've found that when I leave my Player on sleep for a while, I am unable to wake it back up. I've tried pressing the hardware button, the remote buttons, etc. The led is on, but there's no output or sound response from my TV. I have to unplug the NP and plug it back in. Probably a user error, but what's the process to wake the system?
Thanks in advance!
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
I am experiencing something similar, it started with restarts, then it would not boot without the button on the bottom and now it says no signal. Tried connecting it to the pc, pc installed drivers, and if you unplug a cable it says cable unplugged.
Action123 said:
Hi all, I've found that when I leave my Player on sleep for a while, I am unable to wake it back up. I've tried pressing the hardware button, the remote buttons, etc. The led is on, but there's no output or sound response from my TV. I have to unplug the NP and plug it back in. Probably a user error, but what's the process to wake the system?
Thanks in advance!
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Bumping as I still haven't found a solution.
yep, mine does the same thing, every day i have to reboot it as the screen is black and the device is unresponsive
MIne I have to unplug the HDMI and plug it back in then magically there is a signal. I tried setting never go to sleep and that did not hep. Did anyone upgrade to 5.1.1? does that fix anything?
Bump. Got mine a few days ago and the same thing happens.
It's still on and running. It's still a little warm under the button. But no matter what I do with the remote or button or TV, nothing happens. The only way to get it back up is to unplug/plug the hdmi or power cable.
I've got the same problem, but I've unplugged everything and still nothing, tried different TVs, Different HDMi leads still nothing. Going to contact Ausu or go back to where I purchased it tomorrow. was loving catching up with Game of Throne haha
malctron said:
I've got the same problem, but I've unplugged everything and still nothing, tried different TVs, Different HDMi leads still nothing. Going to contact Ausu or go back to where I purchased it tomorrow. was loving catching up with Game of Throne haha
Click to expand...
Click to collapse
You think it's just a defective device?
Maybe I should return mine as well.
I'm taking mine back tomorrow hopefully. If I can find the receipt
malctron said:
I'm taking mine back tomorrow hopefully. If I can find the receipt
Click to expand...
Click to collapse
Did you get a replacement? Did it work?
Action123 said:
Hi all, I've found that when I leave my Player on sleep for a while, I am unable to wake it back up. I've tried pressing the hardware button, the remote buttons, etc. The led is on, but there's no output or sound response from my TV. I have to unplug the NP and plug it back in. Probably a user error, but what's the process to wake the system?
Thanks in advance!
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Quoting you so you get a notification
Did you find a solution? Was it your TV, HDMI cable, or the unit itself?
DonDizzurp said:
Quoting you so you get a notification
Did you find a solution? Was it your TV, HDMI cable, or the unit itself?
Click to expand...
Click to collapse
Still no solution. Tried 3 different ROMs and it's the same thing with each one. Could it be a firmware problem? I mean I shouldn't have to reboot it every time it goes to sleep. The hardware button on the bottom has no effect. I'm slowly giving up.
DonDizzurp said:
Did you get a replacement? Did it work?
Click to expand...
Click to collapse
Hey, sorry for the delay, been busy.
But yeah I got my new nexus. Rang Asus with some struggle as the serial on the product wasn't matching up on the system. Useful haha
Then they said it would take 29 days to get a fix or replacement.... I then said I'll take it back to where I got it which in my case was Argos.
Took it back told them the problem, girl looked at me completely confused. Think I lost her at bootloader haha. But I might as well tell them how to explain to do a factory reset which I couldn't do anyway. Then got my replacement. Which I'm leaving in the box as I want to be a geeky guy and do a unboxing video this time haha.
I found if you turn the TV on and off again it will work.. no need to get up and pull the HDMI cable
I noticed this issue didn't happen with 5.0 but happened with 5.1.1 so I'm hoping a new update will fix it.
Random question but on 5.1.1 how do we get sideloader? As I can't find it on the store
Doesn't matter was being an idiot.
malctron said:
Random question but on 5.1.1 how do we get sideloader? As I can't find it on the store
Doesn't matter was being an idiot.
Click to expand...
Click to collapse
A sideloader? If you are asking how to sideload, you boot into the recovery and then choose install from sideload, then use the "adb sideload" command.
malctron said:
Random question but on 5.1.1 how do we get sideloader? As I can't find it on the store
Doesn't matter was being an idiot.
Click to expand...
Click to collapse
That has absolutely nothing to do with this thread
LOL
Also, you sideload using ADB
Turn on USB debugging, install the ADB driver on your PC, then use the adb command "adb install apkname.apk"
No need for root or recovery.
DonDizzurp said:
I found if you turn the TV on and off again it will work.. no need to get up and pull the HDMI cable
I noticed this issue didn't happen with 5.0 but happened with 5.1.1 so I'm hoping a new update will fix it.
Click to expand...
Click to collapse
This doesn't work on my setup. But pulling the HDMI cable works.
This problem appeared on my Nexus player about a month ago, it was working perfectly until that time.
It looks like a problem with the HDMI CEC. Even if I put my NP in "Never sleep mode" as soon as I turn off the TV it will not then wake when I turn the TV back on.
Well, in my case at least, that is not accurate. When I turn the TV on, nothing appears on the screen nor is there any audio, but the NP is still responding to commands and working. I can blindly start a YouTube video from the highlights section while the TV is still "blanked" and when I toggle the HDMI cable connection the I can see that the NP was functioning "correctly" other than it wasn't outputting anything to the HDMI port.
I would say that the "fault" is just likely to be on the TV not implementing HDMI CEC correctly, but everything WAS working correctly until recently and the only changes are on the Nexus Player side of the equation.
DonDizzurp said:
That has absolutely nothing to do with this thread
LOL
Also, you sideload using ADB
Turn on USB debugging, install the ADB driver on your PC, then use the adb command "adb install apkname.apk"
No need for root or recovery.
Click to expand...
Click to collapse
Haha I know told you it was random yeah I did that after I sent it. Couldn't delete the message sorry haha
Problem solved?
Before you take the device back to the store, I believe the problem is the TV; even those of you who tried multiple ones. I did the same thing; tried a different TV. However, in my case, it works. When I hooked mine to a newer TV, the device wakes up fine. I read in other forums (searched "HDMI won't wake up device") and to my surprise, there are other forum where people complained about the same with other devices. Apparently, something related to the HDMI port (maybe the version of HDMI?).
I'm usually good at recovering my devices since I've had various Android devices since 2010. I'm stuck with how to recover my Shield since it doesn't have a physical buttons. How can I boot directly into the bootloader or recovery? I've done it a few times by accident by rubbing my finger across the power button but can't figure out how to do now. ADB or Fastboot won't detect it at all, I just get a black screen and my TV says "no output".
I had rooted my Shield but kept the stock OS and had TWRP installed but saw no use for root. The 1.4 OS update had been sitting on my homescreen for weeks so I finally decided to revert back to stock and upgrade. I flashed the stock bootloader via fastboot and then flashed the system image but didn't touch userdata. After booting up some things would be goofy (Netflix would get to either 25% or 99% and the audio would play but the video would be stuck on the loading screen, Grid streaming would load the game but would display a green screen but the audio would play in the background) but I didn't want to wipe it yet because I didn't backup Kodi yet.
I saw that there was a 2.0 OS update available and I knew it should work now since I had the stock recovery so I downloaded it and applied it, it verified the image and then rebooted to the stock recovery and proceeded to flash the image. It got about 99% (or maybe 100% done, I wasn't paying attention) and then next thing I notice I just saw a black screen. I thought maybe it was upgrading something or reinitializing something so I waited about 5 minutes and still nothing. Rebooted and got the same thing.
Anyone know if this is recoverable or should I just RMA it?
I'm in the same boat. I was running pure stock from day one (only bought this thing two weeks ago).
After installing 2.0 update last night, the device powers on (green light) but no signal from HDMI. Tried another TV and bypassed receiver (as per forum suggestion).
Computer does not detect when connected with USB. Tried to do HW boot into recovery, does not seem to work.
I have started the RMA process but I'm still trying to get this thing to boot into recovery.
Seems like this has happened to a few other users also over at the geforce forums.
try to reflash it with nvidia images.
if you cant boot to fastboot try this.
HW method:
- Disconnect power cable
- Insert USB OTG cable and make sure to connect other end to a host PC
- Connect power cable to SHIELD
- Quickly start pressing power button for ~3 seconds
- Do not hold the button and connect power supply afterwards
- HDMI TV should be always connected to SHIELD
Alternative method:
- Perform software shutdown on SHIELD by holding Power button for 10 seconds
- Connect USB OTG cable to SHIELD
- Start pressing power button for 3 seconds
- HDMI TV should be always connected to SHIELD
brando56894 said:
Seems like this has happened to a few other users also over at the geforce forums.
Click to expand...
Click to collapse
I did the RMA, only took a few days. The new unit came and auto-updated to 2.0. It worked fine.
I spoke with support today regarding the update, they had this to say;
[12:51:41 PM] : Only few devices, which already had some issues, got bricked with 2.0 update. This was already predicted by NVIDIA, just to get those devices replaced for the customers.
[12:52:45 PM] : Few devices had some hardware issues, but they were working fine. To make that issue prominent and get them detected and to replace them, NVIDIA has released 2.0 update.
[12:53:34 PM] : For other devices, 2.0 update will add many new features and will boost the performance. But for those lot, it will brick them
[12:55:38 PM] : It was a strategy from NVIDIA to provide perfect devices to our customers
Click to expand...
Click to collapse
Take that with a grain of salt of course.
Defective is defective I guess... the RMA was fast at least.
So they bricked the defective ones on purpose just to get them out of use?
I'm in the process of RMAing mine now, they want a lot of information hahaha
God this from support since mine have black screen, it did not help me and my are sent for rma but i might help other.
As part of troubleshooting steps, please try the below mentioned steps and see if that fixes the issue.
-> Unplug all the cables and keep the device off for good 2-3 minutes.
-> Plug the Power cable, controller through USB (Wired) and Ethernet cable to the ATV. Do not connect HDMI cable.
-> The device will power on. Keep it idle for about 5 minutes and keep tapping A button on the controller. Continue tapping for about a few seconds.
-> Now leave the device is this state without the HDMI cable for good 15 to 20 minutes and plug the HDMI cable.
-> See if the ATV displays any output.
I just got my replacement unit, so I'm good. I have two shield controllers now
brando56894 said:
I just got my replacement unit, so I'm good. I have two shield controllers now
Click to expand...
Click to collapse
Sent from my SM-G925K using XDA Free mobile app
bunny0007 said:
God this from support since mine have black screen, it did not help me and my are sent for rma but i might help other.
As part of troubleshooting steps, please try the below mentioned steps and see if that fixes the issue.
-> Unplug all the cables and keep the device off for good 2-3 minutes.
-> Plug the Power cable, controller through USB (Wired) and Ethernet cable to the ATV. Do not connect HDMI cable.
-> The device will power on. Keep it idle for about 5 minutes and keep tapping A button on the controller. Continue tapping for about a few seconds.
-> Now leave the device is this state without the HDMI cable for good 15 to 20 minutes and plug the HDMI cable.
-> See if the ATV displays any output.
Click to expand...
Click to collapse
Where or from which sources you get this tutorial information?
Sent from my SM-G925K using XDA Free mobile app
visitor29 said:
Where or from which sources you get this tutorial information?
Sent from my SM-G925K using XDA Free mobile app
Click to expand...
Click to collapse
Nvidia tech chat support, before they made a rma on my box.
But just got my replacement box today
How hard was it to get a replacement? I am afraid to do anything to mine. Asked nvidia if unlocking the bootloader or rooting the device voids the warranty since they show you how on their website. Their response was that doing either allows them to reject your return under warranty. Just looking for anyones input on their encounter with doing a rma if something should happen.
You may have screwed yourself over by telling them that you did that. I had mine rooted and unlocked also, except mine was unrooted when it bricked itself but the bootloader was still unlocked. I made not mention of rooting/unlocking and it was extremely simple to get a replacement.
No mine is still stock. Just received a replacement from amazon since it bricked itself doing the 2.1 update. Was just wondering what they had to say about the situation. Was consindering flashing the 2.1 full rom, but was worried what would happen if it bricked and had to do a rma. Would not say anything to them about unlocking the bootloader or flashing it. Was wondering if they could detect if anything was modified on it since I see everyone gets a black screen and can't access the console with fastboot. Do they have some way of accessing the system or are they also locked out like we are? Just want to be sure I can get a rma if something happens. A $300 Pro model is a lot to screw up. Support was great to work with, but didnt get as far as a rma since it was still in amazon's 30 day return window. Got a new one in 2 days since I have prime. I just asked what there policy was and not mentioned anything about a bad console.
---------- Post added at 06:13 PM ---------- Previous post was at 06:07 PM ----------
Its just a shame that they offer the tools for developers, but turn around and say that it voids the consoles warranty.
I'm sure they are able to use a UART bridge (serial console) to get into it but I doubt they care enough, like I said mine had an unlocked bootloader but I haven't heard anything back from them yet regarding it.
OMG I fell to their trick to brick my device.... I just did my RMA today, they asked me to do alot things; speed test, model number, turn off, unplug power and hdmi, hold power for 30 sec, plug in power for 2-3 mins, plug in hdmi, then found out no signal on my screen...I assumed it's brick now. i attempted to revive the unit but it doesn't seem to work... Then they had me filled out form, provide snapshot of p/n and s/n numbers... and send them my invoice of purchase.
every time it gets new firmware it loses netflix 4k and this is the fix for it
bunny0007 said:
God this from support since mine have black screen, it did not help me and my are sent for rma but i might help other.
As part of troubleshooting steps, please try the below mentioned steps and see if that fixes the issue.
-> Unplug all the cables and keep the device off for good 2-3 minutes.
-> Plug the Power cable, controller through USB (Wired) and Ethernet cable to the ATV. Do not connect HDMI cable.
-> The device will power on. Keep it idle for about 5 minutes and keep tapping A button on the controller. Continue tapping for about a few seconds.
-> Now leave the device is this state without the HDMI cable for good 15 to 20 minutes and plug the HDMI cable.
-> See if the ATV displays any output.
Click to expand...
Click to collapse
Hi all,
I have the Shield Pro, running 5.1, and it won't start
It was working fine yesterday, but when I got home from work this evening, it was unresponsive. The power light was stuck on, but would not respond to any controller input or, as far as I can tell, any USB input.
I pulled the power out, and plugged it back in, and the light came on instantly. No display on the TV. I plugged it into my PC, but Windows doesn't see anything attached (I have tried multiple cables). If I hold the power button for five seconds, the device just turns off. If I touch the power button even just briefly, the green light comes back on. I can't get into Fastboot or anything. There is no HDMI output at all.
This is, naturally, really quite annoying.
However, after having it hooked up to my PC via USB for a while (not sure how long, sorry!), my computer bleeped like it does when a new USB device has been discovered, and bingo! I now have an "APX" device, with no drivers installed.
So. Who knows about APX mode for this thing?
I'm pretty sure APX is a low level recovery mode.. I recall reading that elsewhere.
go to the developers nvidia site amd search on how to reflash via apx
yeah, I had to use it on my old LG Optimus 2X, back in the day. There's nothing on the nVidia developer site about using it though
unfnknblvbl said:
Hi all,
I have the Shield Pro, running 5.1, and it won't start
It was working fine yesterday, but when I got home from work this evening, it was unresponsive. The power light was stuck on, but would not respond to any controller input or, as far as I can tell, any USB input.
I pulled the power out, and plugged it back in, and the light came on instantly. No display on the TV. I plugged it into my PC, but Windows doesn't see anything attached (I have tried multiple cables). If I hold the power button for five seconds, the device just turns off. If I touch the power button even just briefly, the green light comes back on. I can't get into Fastboot or anything. There is no HDMI output at all.
This is, naturally, really quite annoying.
However, after having it hooked up to my PC via USB for a while (not sure how long, sorry!), my computer bleeped like it does when a new USB device has been discovered, and bingo! I now have an "APX" device, with no drivers installed.
So. Who knows about APX mode for this thing?
Click to expand...
Click to collapse
Apx mode ( and yes without drivers - couldn't even find around in Internet...) on pc ×device manager× shows me on my 500gb console when I removing internal shdd and connected with pc whiteout shdd (one day nothing to do and decide need open and have look what is inside in console...shdd, motherboard, cooler etc) . Another words sounds those symptoms very similar with my tests, but in my case that was mine experiments/investigations/discovery and your looks like you have some serious storage problem or kind of problem relaited with - can't read os or even bootloader which is on 500gb shdd or flash memory modul on 16gb.
Sent from my nokia 3310 using XDA Free mobile app
unfnknblvbl said:
yeah, I had to use it on my old LG Optimus 2X, back in the day. There's nothing on the nVidia developer site about using it though
Click to expand...
Click to collapse
after googling for a bit , i saw some references to the shield tablet, i think someone had an APX driver, maybe you could try that?
I could do, but APX mode is really, really dangerous. You need to know byte offsets and all that :S
unfnknblvbl said:
I could do, but APX mode is really, really dangerous. You need to know byte offsets and all that :S
Click to expand...
Click to collapse
if you know apx and you have all necessary stuff from Nvidia (which is not provided for public) you can replace internal drive or even ssd by installing bootloader, recovery, os etc straight on new drive from pc which is main factor why we can't swap them so easily, like 1 - 2tb drive or ssd - which would be fantastic ?. P.s. Something simular protection is for Xbox360 drives.
Sent from my Nokia 3310 using XDA Free mobile app
if that's the case you might have to send it for a warranty repair.. better not playing around if it's under warranty.
an idea for apx
move your shdd from shield and connect to pc then use this program(R-Studio 8.0) or other to restore date on u shdd I think it most work good luck
---------- Post added at 09:36 PM ---------- Previous post was at 09:22 PM ----------
I have tab p7500 and have this problem apx only jtag help me in apx mode you should now wish sbl for tegra x1 and have nvflash for shield pro sorey for my English the easy way use jtag or tray to restore data in shdd
would there be a way to just dd- flash a new recovery withthe hdd removed from the unit? I am having te same no logo, no bootloader issue and am trying to either find apx drivers (non-existent) or a workaround. There has to be a way.....
i have the same question. My intrest is more in tinkering with the tegra x1 exploit in order to get a different root solution not contingent on nvidias closed source crap. I'm running a 2015 foster model and it is getting increasingly difficult to find tutorials on that system specifically with the newer updates. +i am interested in learning the process to exchange the hdd and mopy and manipulate the widevine keys that don't work on mine after the forced 7.2.3 update that occured with all update sofware removed from my system that also fried my controller with a botched firmware update that is blacklisted and not mentioned on the internet except people asking and all replies deleted. you know general unfettered access to the system without the bootloaders say so . All of this should now be possible now that the real hackers have gotten involved and decided they want to promote this exploit for homebrew it has caused several low level apx drivers to popup in corners ive found myself in from time to time if somebody will just get them to do it for the shield tv instead of the shield tab and the switch it is proven to work.
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?