Database Users

Stuck in APX mode won't boot or turn on / charge - any fix yet?

TL;DR: Any way to fix/flash a Nexus 7 that reports it's in APX mode to Windows yet, that won't do anything else?
Backstory: I've had a 2012 Nexus 7 32gb since the day it came out (Oct 2012 or so?). Worked great for a year, loved it! Had AOKP on it, unlocked/rooted, used tons of apps, never a single problem. And then one day while I was using it to play music while charging it, out of the blue, it hard shut off while it was running, rebooted and shut off during boot and... never turned on again. Wouldn't indicate a charge, wouldn't turn on, couldn't get it to respond to any power or volume key presses, nothing.
I called Asus, and they agreed it needed to be repaired. I sent it to them, they sent me back the same unit, repaired, and said they swapped the mainboard out in the repair notes. Worked great, except the device was completely wiped, relocked, unrooted, and they removed my nice Stenheil screen protector.
I was without it long enough that I got used to not having it. Since it was completly back to stock, I decided instead that I would sell it when I found a good buyer (friend, etc), and buy the new 2013 Nexus 7 instead. I found a friend who wanted it a few days ago.
Today's Issue: I charged it over night last night so it was on a full charge this AM. I saw that I was still running 4.3 on it (hadn't really used it since I got it back in November), so I did the factory/official "OTA" update to 4.4.2 this AM. Went flawless, no issues, booted up fine. I updated all the apps on it, also worked fine.
I then decided to do a Factory Reset on it, (Thru Backup/Reset IN android, NOT Recovery). I went thru the confirmations/warnings, and then it said "Shutting Down..." and, it shut down. I let it sit for a few minutes, expecting it to boot back up (it never did). I tried to turn it on, nothing. I tried ALL combinations of power + volume, + charging cable in/out, etc. Everything possible, trust me, I scoured the web for new combinations and timing ,etc. No matter what, I never got ANYTHING on the display, no charging indicator, no recovery or bootloader, nothing. It's like the display is dead. The battery was fully charged this AM after being charged overnight so I know the battery wasn't even close to low. It's like it's completely dead no matter what I do.
I then tried to hook it up to my PC, which is setup for ADB etc, couldn't see it in ADB. In Device Manager though, it's showing as being in APX mode? So I tried holding power down for 10 seconds with it connected, and it DOES disconnect from windows, and a few seconds later, it shows up again, again in APX mode. Nothing ever appears on the display. Holding VOL down or all three buttons while plugging into PC never changes anything, no matter what, it ALWAYS shows in APX mode.
From what I'm reading online, this is a sign that the bootloader is missing or corrupt, and, that there isn't a fix for that unless you first backed up your crypto "blob" using Flatline (which I didn't even know about till today). I'm hoping that maybe what I've read is out of date? Is there perhaps a way to fix or flash this yet?
The whole thing makes little sense. All I did is update it, then reset it, all officially supported/normal things, on a bone stock tablet. It seems more like they didn't ACTUALLY fix it the first time it went back to them....
Help? AFAIK the tablet is now out of warranty. I just want to sell it and get the 2013 model! The tablet is in perfect shape, it's been used with a screen protector and case since day 1 - not a single scratch on the screen or case. :crying:

i'll take the silence to mean I'm screwed, right? :crying:

I don't know how, but it seems your bootloader is gone. (corrupted sector on the nand,maybe)
You can't do much without the proper blobs.
If I were you, would try to send it back to Asus. They are the only ones who can repair it.

Wow I can't believe it's been two months, but, I still have this tablet, still not working, Asus won't fix it for a reasonable price... anything changed on this in the last two months?
It seems like it should be possible to do something... maybe I'm just optimistic.
I want a 2013 Nexus 7 but it's hard to pull the trigger knowing my very lightly used gen1 model failed twice now.

There is no way to produce an universal blob and device specific blob creation is working so there is little to no reasons for further development.

You could fit a new motherboard 32gb ones are expensive but the 16gb are a lot cheaper
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.

They're readily available on eBay - $35 for a used 16GB motherboard, and $50 for a 32GB board. That's how I fixed my APX bricked N7...

Whoever stumbles across my late entry, if the N7 won't boot after empty battery, no button combinations work and PC shows only APX mode - take off the back housing (it's pretty easy to do) and disconnect and reconnect the battery cable, this let me boot it up immediately...
(my N7 however was plugged over night to charge before I attempted this unplug but actually didn't show up the charging indicator and wasn't bootable, surprisingly it was charged already half when I finally could boot it up)
Sent from my OnePlus5T using XDA Labs

Apparently it is possible without having done the backup first, at least for some people.
https://forum.xda-developers.com/nexus-7/general/tutorial-how-to-unbrick-nexus-7-blob-bin-t4083879

Phone suddenly hard-bricked. No recent flashing.

Hi everybody,
What Happened:
My phone has suddenly become totally unresponsive. I have been using it most of the day, it was sitting at around 70% the time that it happened, but it is now a totally black screen. I had just taken it out of my pocket and it was suddenly like this.
The only idea I could come up with as to why this happened is that I charged it off of a JBL Charge 2 last night. I'm not sure if that may have messed with the battery, but I do find it odd that it's totally unresponsive while plugged in.
I was running android 7.1.1 DP2, with the ElementalX kernel 4.0 I believe. I was also rooted with SuperSU. What's really odd is that I hadn't done anything new recently besides install uTorrent and VLC media player. Otherwise, my routine has not changed one bit. Up to when the phone actually died, I hadn't even used either of these new apps the entire day.
What I've Tried:
I have tried plugging it in via AC, via USB, I've tried booting into recovery or fastboot, but there is zero response from the phone. No indicators on the screen, no LED blinks, no vibrations, nothing.
What I'll Try:
If anyone has any experience with this happening, I could use some advice. Otherwise I'm just going to wait it out, consider an RMA I guess. However, my device did have the bootloader unlocked and was rooted, so.... I hope it comes back by itself.

My advice is to keep it plugged in, or see if there is a response on the computer perhaps on fastboot, upon using the bootloader keys. I haven't had this, just a few suggestions. Good luck!
PS: A RMA will probably be needed, there are much more experienced people around here. Sure you may get replies later.

Good luck?problem all nexus 6p!!! Lg responds repay helps, hawuei what to do? problem arises with nogaut not be our fault, how to fix this? My phone now in service but to be fair this? warranty and having to wait ..

Phone finally booted after 3 day boot loop..

I decided to start a thread because I noticed there were multiples about this issue. So 3 days ago I was on Facebook when my phone randomly froze. I pushed the power button, and that's when it began bootlooping. I instantly tried booting into recovery with no success. I was hopeful, however, because I could still access the bootloader. I got on my computer and began researching the issue and steps I could take to fix it. I tried every method out there and was unsuccessful. I ended up buying a Pixel today off Craigslist and am loving it so far. So anyway since my Pixel came with the OEM charger, and I had been using a non-oem ever since I had my 6P, I decided to plug in the OEM and see what happens. Within the first hour my 6P began to get very hot, almost to the point where I couldn't even hold it in my hand. Keep in mind the phone was still consistently boot looping the whole time. So I decided to unplug it. Well I left it sitting and went about my business and when I came back to my bed I noticed it was doing the Google boot animation!!!! I started freaking out! After it booted up I finished the tutorial stuff and just let it sit on the home screen for a second. I noticed the battery was low so I figured I would plug the charger back up and let it charge. Well in the time it has taken me to write this post, it just started boot looping again... Lol. So I just unplugged the charger AGAIN, to see if it will boot up again. To me, it seems like there might be a hardware issue with my battery. Anyway, my 6P was rooted and running nitrogen OS (wasn't running the latest build but was 7.1.)

what are the exact symptoms? and does it boot into bootloader and recovery if not what is it physically doing?

dontbeweakvato said:
what are the exact symptoms? and does it boot into bootloader and recovery if not what is it physically doing?
Click to expand...
Click to collapse
As of now it is still boot looping and no it doesn't boot into recovery. Only symptoms I've noticed is the phone starts to get extremely hot when I plug in the OEM charger that came with my Pixel. I figured they were the same so that's why I decided to use it since it was OEM.

I had a 6p that bootlooped eternally couldnt access boot or recovery, I sent it in and they sent a new one. Board was damaged.
I also had a nexus 5 that bootlooped and it turned out to be a bad power botton. the internal connection was broken so it would get power and lose power all in the same second, off and on but too fast to see other than seeing a bootlooping device. that was fixed with a new power button which had to be soldered on.
if not on warranty you could take to a cell phone repair shop maybe they might be able to fix the issue.

dontbeweakvato said:
I had a 6p that bootlooped eternally couldnt access boot or recovery, I sent it in and they sent a new one. Board was damaged.
I also had a nexus 5 that bootlooped and it turned out to be a bad power botton. the internal connection was broken so it would get power and lose power all in the same second, off and on but too fast to see other than seeing a bootlooping device. that was fixed with a new power button which had to be soldered on.
if not on warranty you could take to a cell phone repair shop maybe they might be able to fix the issue.
Click to expand...
Click to collapse
It is under warranty, but the sad part is that I no longer have the receipt for it. I got the phone off Craigslist and the guy gave me the original box and receipt but I managed to lose it. I haven't been able to get it to fully boot back up again since last night. I'm not that worried about it anymore because I already have a new phone, but I wouldn't mind if it were to some how fix itself lol.

e1ement08 said:
It is under warranty, but the sad part is that I no longer have the receipt for it. I got the phone off Craigslist and the guy gave me the original box and receipt but I managed to lose it. I haven't been able to get it to fully boot back up again since last night. I'm not that worried about it anymore because I already have a new phone, but I wouldn't mind if it were to some how fix itself lol.
Click to expand...
Click to collapse
my first bootloop years ago i thought the same.
it wont fix itself. its not a software isssue because youd be able to at least boot into bootloader. it sucks to hear the truth but thats the truth.
its a hardware issue and you could take it to a repair shop because they will inspect and fix. small drops that dont harm the device can ultimately cause small breaks in the solder joints so who knows what is wrong without inspection

Nexus 6p - bricked?????

Hi all,
Hopefully this wasnt covered before- I used the search function and it didnt return any results, at least not for my specific scenario.
I've had this 6p for about 18-20 months roughly. Been my best phone by far, and I've been very happy with it(normally i replace my phones every 8-12 mos because I need the latest and greatest lol).
About six months ago I threw PureNexus on there with I believe Flash kernel. Worked flawlessly, and I've been really happy with it.
About a week ago, it powered off on its own but i had it in my back pocket so I just assumed it was an accidental reboot. However, this morning, I woke up, threw it on the charger for about 30 minutes, got to about 60%, and unplugged it. While I was using the browser, it froze up for a minute then shut down. No bueno. Cannot get it to power back on. No power light while charging. I did what others have had luck with, holding power, and/or power/down for several minutes, still nothing.
I reached out to Project Fi, and they want a 500 dollar hold to send me out a refurb replacement. I know they release the funds in approximately 12 days but we had a recent death in the family and I just cannot afford to have 500 bucks locked up, especially right now. Spoke w a supervisor, apologized, but said nothing they can do.
On a whim, I plugged it into the pc, and it DOES detect it but its the dreaded QHSUSB_BULK under 'other devices'. So that tells me its at least got power, but, I'm unsure if just trying to use adb(i havent in a while, not since i did the initial rom install but im sure i can find instructions) to attempt to throw the base image back on there, will work, or which direction to go.
I found this but I dont think its for my specific phone but thought maybe there was a set of instructions for this particular phone similar to these:
https://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
I have seen several reports of this error happening when flashing the wrong rom, or using the wrong image, but never just all of a sudden when its been running like a champ.
any thoughts? thanks in advance.

Nexus 6p is plagued with issues like shutting down at certain percentages and the dreaded bootloop of death. You could get in contact with Google heard even people out of warranty having success. Could also have a shop replace the battery in some cases that fixed the shutdowns.

If it doesnt boot up at all I can't help you. If you can get to bootloader, flash stock image, un-root, re-lock your phone. see if it boots. I had to do all this, this morning. Phone would just shut off at 80%, reset and hang at the google sign. I could only get to into the main system with a hard reset every time. then it would reset and lock up. So i reverted it to stock and we will see how it goes. So far its been 6 hrs and no random resets and its in full use.

Yea, the problem is, I cant. Its not even a boot loop. Just looks like its dead. Held the power button down for roughly 10 minutes out of desperation.
The odd thing is, if i plug it into my pc it shows how i mentioned in my initial post. So it must have juice even though the power light/etc isnt on and it doesnt show charging.
Last hope I think i have is to run it out of battery leaving it on the table, then hope somehow when i plug it into charge, that resets it somehow since it was dead, and maybe clears whatever the issue is. Very odd considering it was working fine until this.

Your phone is stuck in the EDL mode when its detected as QHSUSB__BULK. There are solution for this but i dont know if this solution is combined with data loss or not and i try to find that out recently. I also still dont know how to fix that with linux.
Here two howtos:
https://forum.xda-developers.com/nexus-6p/general/guide-how-to-bring-to-life-dead-nexus-t3581948
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838

Dead & unresponsive 6P help.

So a couple weeks ago my Nexus 6P died.
I had just taken it off charge and it froze then just died. Became unresponsive and I can't boot it or boot it into recovery. So I have a paper weight at the moment.
Ever since, there has been a couple instances where I got the phone to boot into the Google logo and it will freeze there. Either that, or it will get into the loading animation and freeze on that. It will not turn off until I turn it off myself.
I've only been able to do this a couple times with it being on charge for an hour, unplugging it and plugging it back in whilst holding the power button. Trying to get into recovery with this method has proven unsuccessful.
When left until there is no charge on the phone, I am able to invoke the red blinking lights on the notification led by holding down the power button in any variation (e.g. vol down + power, vol up + power, etc)
The question is if anyone else has come across this issue before and if there is any fix?
I do not believe this is BLOD. Maybe fried mobo or maybe battery is bad.
I can't RMA the device back to Google as I bought the phone whilst I was working in Japan and I bought it from Google Japan and I am know back in the UK.
So they apparently follow local warranty. I've spoken to them about 3 times about this and refuse to budge. Huawei are also no help as I bought the device from overseas, they said they aren't allowed to send any devices from Asia to their UK service centre.
So I'm kinda stuck. Any help would be greatly appreciated.

CookieDude_2332 said:
So a couple weeks ago my Nexus 6P died.
I had just taken it off charge and it froze then just died. Became unresponsive and I can't boot it or boot it into recovery. So I have a paper weight at the moment.
Ever since, there has been a couple instances where I got the phone to boot into the Google logo and it will freeze there. Either that, or it will get into the loading animation and freeze on that. It will not turn off until I turn it off myself.
I've only been able to do this a couple times with it being on charge for an hour, unplugging it and plugging it back in whilst holding the power button. Trying to get into recovery with this method has proven unsuccessful.
When left until there is no charge on the phone, I am able to invoke the red blinking lights on the notification led by holding down the power button in any variation (e.g. vol down + power, vol up + power, etc)
The question is if anyone else has come across this issue before and if there is any fix?
I do not believe this is BLOD. Maybe fried mobo or maybe battery is bad.
I can't RMA the device back to Google as I bought the phone whilst I was working in Japan and I bought it from Google Japan and I am know back in the UK.
So they apparently follow local warranty. I've spoken to them about 3 times about this and refuse to budge. Huawei are also no help as I bought the device from overseas, they said they aren't allowed to send any devices from Asia to their UK service centre.
So I'm kinda stuck. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Some more information would be useful like do you have an unlocked bootloader and have debugging enabled?

DEVILOPS 007 said:
Some more information would be useful like do you have an unlocked bootloader and have debugging enabled?
Click to expand...
Click to collapse
Unfortunately I don't have the bootloader unlocked nor have I got debugging enabled (I don't think).
Its pretty much as it was outta the box. Only things I tinkered with was enabling dev options in the settings but that is as much as I've done really. But haven't messed around with any of those settings.
The device is all stock.

CookieDude_2332 said:
Unfortunately I don't have the bootloader unlocked nor have I got debugging enabled (I don't think).
Its pretty much as it was outta the box. Only things I tinkered with was enabling dev options in the settings but that is as much as I've done really. But haven't messed around with any of those settings.
The device is all stock.
Click to expand...
Click to collapse
Did you enable OEM unlocking if you enabled Dev options?

DEVILOPS 007 said:
Did you enable OEM unlocking if you enabled Dev options?
Click to expand...
Click to collapse
I don't think so. Sorry, I'm not super technical.

Not wanting to make a new thread when this seems to be relevant; I appear to be experiencing the same issues as the OP.
I was at work and I noticed that my phone had switched off. I assumed it had ran flat and I hadn't noticed so plugged it in when I got home to no avail. The following day I was playing with the power button; holding it down for a period and pressing thinking it might be a loose connection and eventually it did turn back on but only for a few hours and since then the only response I get is a red LED when pressing the power/volume button whilst on charge.
I have replaced both the battery and the charging port/daughter board but this does not appear to have resolved the issue. Is there something I am missing or is my phone now a very expensive paperweight? If that is the case this will be the second Nexus device I owned which died in similar circumstances not long out of it warranty; I had a Nexus 6 which died after a year which I replaced with the 6P and it may be that the same thing has happened.
Any help, advice or suggestions anyone can give would be much appreciated!
Edit: Answering a question asked previously with regards to more information my bootloader is unlocked however I can't remember if USB debugging was enabled. I have a feeling that it is disabled as a work around for Magisk Hide and passing SafetyNet.

CookieDude_2332 said:
I do not believe this is BLOD. Maybe fried mobo or maybe battery is bad..
Click to expand...
Click to collapse
BLOD is a bad motherboard. If you can't access Recovery and are bootloader locked, you're at the end of the road.

Have you tried to keep it plugged in then hold the volume down button and power button at the same time, and hold it hard for a while and see if it goes to the recovery partition.
Otherwise, why don't you bring to a hardware store and talk to someone?
GLHF!:crying:

So I've spoken to Huawei on a whim and found out that my phone is under warranty so I am waiting on a return delivery envelope to go to one of their Service Centres however I would like to at least try to restore back to stock and re-lock the boot loader as I have managed on a few occasions to get the phone to boot to the 'Google' logo before it would then shut down. I have since plugged the phone in to my laptop and "QHSUSB__BULK" appears in Device Manager.
I have Wugfresh's NRT 2.1.9 but this does not pick up fastboot or adb. Is there any other tool I should be aware of or a driver I haven't got installed? Is this something anyone has come across or managed to resolve before?

beejkitsune said:
So I've spoken to Huawei on a whim and found out that my phone is under warranty so I am waiting on a return delivery envelope to go to one of their Service Centres however I would like to at least try to restore back to stock and re-lock the boot loader as I have managed on a few occasions to get the phone to boot to the 'Google' logo before it would then shut down. I have since plugged the phone in to my laptop and "QHSUSB__BULK" appears in Device Manager.
I have Wugfresh's NRT 2.1.9 but this does not pick up fastboot or adb. Is there any other tool I should be aware of or a driver I haven't got installed? Is this something anyone has come across or managed to resolve before?
Click to expand...
Click to collapse
Leave it just the way it is. You're stuck in QC 9008 diagnostic mode. Perfect for sending the phone back. Don't worry about it.

v12xke said:
Leave it just the way it is. You're stuck in QC 9008 diagnostic mode. Perfect for sending the phone back. Don't worry about it.
Click to expand...
Click to collapse
Thanks for the advice. I'm just waiting on them sending me the jiffy bag to send my device out to them.
I'm not holding my breath on them actually fixing or replacing it as I have done a DIY battery replacement a little while ago (though I did replace with an OEM battery) but I figure it's worth a shot and worst case scenario I'll hold out for Oct 4th and hope the Pixel 2 XL rumours are right and it will have a similar screen design to the Galaxy S8+.
I love the look of the Infinity Display but will not have a Samsung.

beejkitsune said:
...I love the look of the Infinity Display but will not have a Samsung.
Click to expand...
Click to collapse
Totally agree.

beejkitsune said:
Thanks for the advice. I'm just waiting on them sending me the jiffy bag to send my device out to them.
I'm not holding my breath on them actually fixing or replacing it as I have done a DIY battery replacement a little while ago (though I did replace with an OEM battery) but I figure it's worth a shot and worst case scenario I'll hold out for Oct 4th and hope the Pixel 2 XL rumours are right and it will have a similar screen design to the Galaxy S8+.
I love the look of the Infinity Display but will not have a Samsung.
Click to expand...
Click to collapse
Final update. Apparently Huawei are struggling with a parts shortage and don't know when parts will be come available so they have offered me a "Limited Edition" Gold Mate 9. I'm not entirely happy about this arrangement as I really loved my 6P but they have had my 6P for about six weeks and I haven't had a fully working phone since August 18th so I'm left with little other choice since I can't afford the P2XL.
Thanks for your help and in general to everyone in the 6P threads who have helped me out of the past 18 months.