Database Users

[Q] Some doubts with Google RMA Nexus 4 - RED LED issue, Nexus 4 dead.

First than nothing, sorry for my bad english.​
My N4 got bricked, the problem seems to be the battery because when plug in to the AC charger the LED blinks red and nothing else happens, other members have the same problem.
There is few post about it
- http://forum.xda-developers.com/showthread.php?t=2050811
- http://forum.xda-developers.com/showthread.php?t=2011328
- http://forum.xda-developers.com/showthread.php?t=2048066
- http://forum.xda-developers.com/showthread.php?t=2077331
So after try everything my nexus 4 seems to be dead, I decide to RMA but I don't know some details, and maybe you can help me
First, what I think I have to do:
I live out of USA, so I shipped my N4 to my cousin, he was who bought the N4, when he get my N4 then he will do the steps that Google tell him.
My doubt is:
1 - My bootloader is unlocked when my N4 start with the issue, perhaps Google can not turn on the device and be aware of it because the phone is fried, so if they can not detect that the bootloader is unlocked my RMA is free? (Assuming you have the bootloader unlocked means forfeiting RMA)
2- If they detect that my bootloader is unlocked, they will ignore this? Google will send me a replacement device? Although i going to be charged again (Assuming that Google is left with the charge of money they make to your account which remain in hold)
3- The replacement device is now yours? Or is just four use while Google check the original device?
4- How long take the whole process ?
So, this is all my questions by the moment, thank you and sorry for bad english, I used a little bit of Google Traductor.

D3m0x said:
First than nothing, sorry for my bad english.​
My N4 got bricked, the problem seems to be the battery because when plug in to the AC charger the LED blinks red and nothing else happens, other members have the same problem.
There is few post about it
- http://forum.xda-developers.com/showthread.php?t=2050811
- http://forum.xda-developers.com/showthread.php?t=2011328
- http://forum.xda-developers.com/showthread.php?t=2048066
- http://forum.xda-developers.com/showthread.php?t=2077331
So after try everything my nexus 4 seems to be dead, I decide to RMA but I don't know some details, and maybe you can help me
First, what I think I have to do:
I live out of USA, so I shipped my N4 to my cousin, he was who bought the N4, when he get my N4 then he will do the steps that Google tell him.
My doubt is:
1 - My bootloader is unlocked when my N4 start with the issue, perhaps Google can not turn on the device and be aware of it because the phone is fried, so if they can not detect that the bootloader is unlocked my RMA is free? (Assuming you have the bootloader unlocked means forfeiting RMA)
2- If they detect that my bootloader is unlocked, they will ignore this? Google will send me a replacement device? Although i going to be charged again (Assuming that Google is left with the charge of money they make to your account which remain in hold)
3- The replacement device is now yours? Or is just four use while Google check the original device?
4- How long take the whole process ?
So, this is all my questions by the moment, thank you and sorry for bad english, I used a little bit of Google Traductor.
Click to expand...
Click to collapse
1.you have to call google for an rma
2.in my case, the send me a new one, including an envelope and the freightpapers for the old one
3. they authorize 349 euro on your credit card, but they just authorize it,they dont take it
4.if you receive the new device, you have to send the old device back to them within 21 days, otherwise they will take the 349 euros from your credit card
5. pray that they cant turn it on and you are good to go and you dont have to pay for it
6. in betwen 14 days you can keep the new device, dont know how they handle it over 14 days sorry
hope i could clearify some things lol

I live in Germany, had similar problems and doing the rma rightnow, too.
The replacement nexus 4 that you will get is yours. Until they checked your first nexus 4, they block the money for your replacement.
If your warranty isn't valid or the defect isn't covered by the warranty they will charge you for the replacement device.
Let's hope they cannot turn our devices on to check for an open bootloader

pa.pn2 said:
1.you have to call google for an rma
2.in my case, the send me a new one, including an envelope and the freightpapers for the old one
3. they authorize 349 euro on your credit card, but they just authorize it,they dont take it
4.if you receive the new device, you have to send the old device back to them within 21 days, otherwise they will take the 349 euros from your credit card
5. pray that they cant turn it on and you are good to go and you dont have to pay for it
6. in betwen 14 days you can keep the new device, dont know how they handle it over 14 days sorry
hope i could clearify some things lol
Click to expand...
Click to collapse
Qin-Root said:
I live in Germany, had similar problems and doing the rma rightnow, too.
The replacement nexus 4 that you will get is yours. Until they checked your first nexus 4, they block the money for your replacement.
If your warranty isn't valid or the defect isn't covered by the warranty they will charge you for the replacement device.
Let's hope they cannot turn our devices on to check for an open bootloader
Click to expand...
Click to collapse
Thank you guys! Really helped
Lesson learned: After root, ALWAYS block your bootloader

D3m0x said:
Thank you guys! Really helped
Lesson learned: After root, ALWAYS block your bootloader
Click to expand...
Click to collapse
Dont take a chance ! If you didn't send your device yet...
plug it into PC while holding ( VOL - )! JUST VOLUME DOWN ! no POWER KEY !
and when in fastboot mode, do :
Code:
fastboot oem lock
Dont take any chances ! ... They are super genuis ! I guess they can do anything to check the LOCK status !

miku3191 said:
Dont take a chance ! If you didn't send your device yet...
plug it into PC while holding ( VOL - )! JUST VOLUME DOWN ! no POWER KEY !
and when in fastboot mode, do :
Code:
fastboot oem lock
Dont take any chances ! ... They are super genuis ! I guess they can do anything to check the LOCK status !
Click to expand...
Click to collapse
Well bro, my phone its on the way to USA, but when my cousin get it, I'll tell that and lets see what happends...

I had no issues on 1836. I was on it all late last night. It was until I opened that benchmark app that went haywire.

Mentioned this in the other thread as well, but any idea what bin your CPU is?

Hey guys im in the same boat currently doing RMA. I have no red LED phone wont charge or turn on so hoping that Google cant either and Warranty holds.
No idea what bin I am im afraid. I have a hunch its fast or faster as I couldn't run matr1x v4.0 kernel and other people who also couldnt were fast bin (think it was due to the voltage tables).

RED LED fixed
hey guys, i've read a lot of threads about this red led issue and having the only solution was to RMA it.
just remebered the time when i had a RED LED after replacing my framework.apk that i have found in one the forums, after replacing the framework.apk, my phone cant respond to anything (screen touches and even power and volume button was not working) and after a minute my phone turned off. and i cant get it to turn on so i was panicking a bit knowing that i cant RMA my phone cause i only had my phone from my mother in UK and i'm in philippines so i plug my phone on the wall then the LED flashes RED ......
to make the long story short i tried everything to revive my phone and wugfresh's toolkit saved it, after a couple things the toolkit manages to flash the stock rom on my phone i was relieved.
that was just my experience, hope it help you guys

dannaoj said:
hey guys, i've read a lot of threads about this red led issue and having the only solution was to RMA it.
just remebered the time when i had a RED LED after replacing my framework.apk that i have found in one the forums, after replacing the framework.apk, my phone cant respond to anything (screen touches and even power and volume button was not working) and after a minute my phone turned off. and i cant get it to turn on so i was panicking a bit knowing that i cant RMA my phone cause i only had my phone from my mother in UK and i'm in philippines so i plug my phone on the wall then the LED flashes RED ......
to make the long story short i tried everything to revive my phone and wugfresh's toolkit saved it, after a couple things the toolkit manages to flash the stock rom on my phone i was relieved.
that was just my experience, hope it help you guys
Click to expand...
Click to collapse
Exactly what did you do in Wugfresh's toolkit to save it?

reaper000 said:
Exactly what did you do in Wugfresh's toolkit to save it?
Click to expand...
Click to collapse
i used the "flash stock +unroot"
shaded the soft-bricked/boot loop

Sent my device in for RMA over a week ago. Bootloader was unlocked and custom rom loaded. Same red light problem everyone else is having. Also ordered my replacement device which is still on back order.Charges have now cleared my credit card so no worries just in case anyone is worried they will not honor the warranty because you have unlocked and rooted the phone .Called google to find out where my replacement device is yesterday and they said that even the rma devices are on back order for 1 to 2 more weeks which really sucks!

So basically everyone here crashed their car ,it was their own fault, car not had an insurance and you expect to get a new one pretending it was manufacturing fault ?
Sent from my Nexus 4 using xda premium

You make too many assumptions, friend.
1. Not everyone browsing this topic has crashed their phone. I popped in while searching for Wug and toolkit, for instance.
2. It's their own fault: you know what "everyone here" did? Their phone use, their setup?
2a. It may not be manufacturing issue as much as a design flaw. Microsoft's Xbox "circle of death" comes to mind; this could be LG's version of that.
The Nexus line is known as the dev's phones, and devs push limits; that's inherent to development. Even experienced devs like Faux have had red LEDs.
The inability to yank the battery as a hard reset has always troubled me in this kind of environment. I hope Google's next phone corrects this
Sent from my Galaxy Nexus using Tapatalk 2

MattSkeet said:
So basically everyone here crashed their car ,it was their own fault, car not had an insurance and you expect to get a new one pretending it was manufacturing fault ?
Click to expand...
Click to collapse
Mine Nexus got the red led just now, never rooted, everything stock
[Update: after sometime connected to the computer the battery charging icon appeared and it booted]

Update on my RMA process. I noticed today that I have a new pending $299 authorization on my card and I am trying to find out why. The original $299 authorization that was placed on my card when I first started the RMA has now cleared because I had already sent the defective device back for repair and a few days later the pending charge went away. Now I am wondering why in the hell they placed a new $299 charge again even though my replacement device has not even shipped! Google has really dropped the ball on this whole nexus 4 situation!

If you take it apart and actually take the battery out, as a proper hardware reset, will that work? Anyone tried this?

Meleagru said:
If you take it apart and actually take the battery out, as a proper hardware reset, will that work? Anyone tried this?
Click to expand...
Click to collapse
Well, here's a thread that I started that addresses that question directly:
http://forum.xda-developers.com/showthread.php?t=2103451

Here's an update; it seems one brave soul did pull the Nexus 4 battery. Check out this thread : http://forum.xda-developers.com/showthread.php?t=2111947
Sent from my Nexus 4 using Tapatalk 2

Nexus 7 Bricked, No response

Ok well skip this first part if you don't want a story,
I got my nexus around febuary as a gift for my birthday as a little toy and music, I went right ahead and unlocked the bootloader and rooted it for future use as well as going ahead and putting TWRP on it with multirom for ubuntu tinkering but never bothered flashing a new android and only flashed a new kernal to be able to tweek the clock speeds and never bothered with that ether becuase the nexus was fast enfough for everything i could throw at it.
Now a few days ago I decided to do a factory reset from TWRP to put a stock rom on it and clean everything off it, Then it just refused to boot BUT i still had bootloader access so all was well and i used the lazy option and oppted to use the nexus toolkit and told it to just flash the stock rom onto it. It finished then i went to restart it and it died.
Now since that death it will not boot, it will not get to the bootloader or recovery menu, it wont respond to any buttons at all, It won't dispaly the chargeing icon when pluged it nor will the screen turn on at all and to top it all off even when i plug it into my laptop it will not even notace it at all.
I have seen simlar problems but none exactly the same, I tryed to return it today but to put it lightly pc world are a bunch of asshats who woudent exchange or repair it becuase the receipt was slightly damaged so returning it isent an option.
Feel free to call me an idiot and everything but for any help at all I thank you in advance.

You should still be covered under the 12 month warranty from Asus with the warranty card you got along with your device.

Username invalid said:
You should still be covered under the 12 month warranty from Asus with the warranty card you got along with your device.
Click to expand...
Click to collapse
Will they not not just tell me to go to the resaler?
My headset from asus broke and they told me I had to set up the rma with the online resaler i bought it from here.

There's no harm in atleast going to the Asus website and make an account then register your tablet.

Username invalid said:
There's no harm in atleast going to the Asus website and make an account then register your tablet.
Click to expand...
Click to collapse
I've done so now, but I hold no hope with the support asus offers

Bricked My 6P, But Not Sure Why/how.. Any help is appreciated

I'm pretty lost on this one and after hours of searching, have not the slightly clue how (or if) to fix it...if it can even be fixed.
Past few days I've noticed the phone randomly rebooting, some of the times it says my battery is 0% when it's almost full. Today I went to go wipe it and reflash Pure Nexus. While wiping and flashing it, it ended up in a boot loop. I've tried everything to get the phone back up and running. I've tried attempting to flash different ROMs, the stock images (tried T and Q), doing a hard reset, factory reset. Literally everything under the sun that I know to do or have looked up.
Right now the most my phone will do is turn on, shows the Google screen, the reboots and repeats. Sometimes when the phone is off, I have to hold the power button for a minute or 2 to get it to turn on. Still, can only get in the bootloader, but can't get it to boot further than that.
Any help is appreciated, I'm at a loss on this one....and phoneless. :crying:

Pretty weird, if nothing works you should flash stock images, lock bootloader and RMA.

Techno Peter said:
Pretty weird, if nothing works you should flash stock images, lock bootloader and RMA.
Click to expand...
Click to collapse
I also tried to lock the bootloader and re-unlock it, with no luck. Called Google and they weren't any help, least outside of what I've already tried. I'll be calling Huawei tomorrow when they open.
As of now, it seems when I unplug my phone, it just turns off. I plug it back in, it goes into bootloop (without me hitting power button). Sort of wondering now if the battery just took a dump?

The phone started acting funny every since I tried to Android N. I'm going to attempt to try flashing N again, just for kicks.

I found a USB charger at work. While not a fast charging one, it was enough to allow my phone to boot up. Apparently there is something wrong with the battery some how. When it booted up, it showed I still have 48% of battery left so I took it off the charger. About 5min after booting it shut down again. Now that it's on the charger again, it'll boot back up and now shows 1% of battery.
I can't figure out for the life of me what the deal is. Looking like I'll need to lock the bootloader and RMA it back for warranty and get a properly operating phone. I'm curious how quick this will happen to get a working phone? I'm up for an upgrade through Sprint, think at this point it's best to go get a new phone to use in the meantime since I have no old phones to use in the meantime. If Huawei gets me a new phone within 14 days I can take the new one back and rock on with Nexus. Kind of sucks, but just my luck.

InfiniteReality said:
I found a USB charger at work. While not a fast charging one, it was enough to allow my phone to boot up. Apparently there is something wrong with the battery some how. When it booted up, it showed I still have 48% of battery left so I took it off the charger. About 5min after booting it shut down again. Now that it's on the charger again, it'll boot back up and now shows 1% of battery.
I can't figure out for the life of me what the deal is. Looking like I'll need to lock the bootloader and RMA it back for warranty and get a properly operating phone. I'm curious how quick this will happen to get a working phone? I'm up for an upgrade through Sprint, think at this point it's best to go get a new phone to use in the meantime since I have no old phones to use in the meantime. If Huawei gets me a new phone within 14 days I can take the new one back and rock on with Nexus. Kind of sucks, but just my luck.
Click to expand...
Click to collapse
That's exactly what you should do. Most probably the battery is dead or malfunctioning. Charge it with that spare charger for a few hours, then restore stock and lock the bootloader. Finally, turn it up for RMA.
I never had a single out-of-the-box issue with any of my 5 Nexus devices. I hope the replacement that you receive will be up to the satisfaction.

Techno Peter said:
Pretty weird, if nothing works you should flash stock images, lock bootloader and RMA.
Click to expand...
Click to collapse
DJBhardwaj said:
That's exactly what you should do. Most probably the battery is dead or malfunctioning. Charge it with that spare charger for a few hours, then restore stock and lock the bootloader. Finally, turn it up for RMA.
I never had a single out-of-the-box issue with any of my 5 Nexus devices. I hope the replacement that you receive will be up to the satisfaction.
Click to expand...
Click to collapse
Thanks for the confidence. I'll do just as suggested and return it.
I'm up for an upgrade, although I have to do online so I don't have to pay an extra $30/month for a phone I'll sell after getting my 6P back. I hate sprint not letting me do it in the store, such a PITA. If I do online I can just get the discount and sign a 2yr contract which is fine with me. Any idea if they will ship a new phone so I'm not without a phone for week(s)?

InfiniteReality said:
Thanks for the confidence. I'll do just as suggested and return it.
I'm up for an upgrade, although I have to do online so I don't have to pay an extra $30/month for a phone I'll sell after getting my 6P back. I hate sprint not letting me do it in the store, such a PITA. If I do online I can just get the discount and sign a 2yr contract which is fine with me. Any idea if they will ship a new phone so I'm not without a phone for week(s)?
Click to expand...
Click to collapse
Sorry, but I never had any experience with an international carrier like Sprint, so can't say. Someone here would be able to answer this better than me. :highfive:

Thanks for the quick reply. I'll call Huawei here in a few and start the process and find out. Fingers crossed they will ship a new phone, even with a temp hold on the money while I send this broken one back. I'll post what I find out, just in case anyone else is curious and searching for the answer.

Random boot loop, can't get anywhere in recovery

I was on the latest CM13 nightly (was waiting a bit to go to 14.1) So I went to bed last night and my phone did a reboot as I was setting my alarm. Didn't think too much of it, crap happens. I waited for it to come back fully into the OS, which it did, checked my alarm. Noticed something strange I got the CM Updater notification in the statusbar ("There are new updates available" - CM14.1-12-02 or something), which I thought was weird that's the first time it's said that, and I've checked the CM Updater before and since the 14.1 switch there's been nothing there. As it should, I imagine, not try to update major versions like that. Anyways I dismissed it and went to bed (this entire thing is PROBABLY entirely unrelated, but I found it's timing interesting at least).
Woke up a few hours later to my phone getting really hot, and stuck in an infinite boot loop. It never gets passed the first Google screen. If I let it go it'll sit there for several minutes and maybe reboot. I was able to get into the bootloader, choosing Boot Recovery though sends me back to the Google bootup screen where it never progresses, doesnt have the blue text in the top that says booting into recovery..
Was able to get into the phone with fastboot so I tried flashing the latest recovery I had installed TWRP-3.0.2-2-angler. Still wouldn't boot into it, sometimes it would get to the TWRP recovery loading page, and then sit there for a couple minutes, then reboot.Tried flashing it a few times with fastboot with no success.
Erased userdata with fastboot, then did a full factory reflash of several images, MDB081 - MTC20l (factory images I know I've used in the past to recover, had them saved). Rebooted and I still can't get into the OS (stuck at first Google logo). Interesting the stock recovery though loads.
Flash an older TWRP recovery I had saved twrp-2.8.7.2-angler . Was able to get into recovery finally - kind of. Sometimes it still locks up and wont let me swipe to enter TWRP. The first time it let me in it asked me for my decryption password - I didn't have a password - had a swipe and fingerprint setup only. Got in again and first thing I tried doing honestly is erasing (formating) all my data, thinking if I'm going to have to warranty this phone or sell it broken, I want to make sure my data is wiped. Also I figure after that I can try to reinstall CM etc like I would a completely fresh build. It complained about not being able to mount the partition and locked up in TWRP then eventually auto rebooted. Got in again and tried to do a basic wipe, it said it cant find /sdcard then said it wiped, and then froze, auto rebooted again after a few seconds.
To note : All fastboot commands seem to execute with "OKAY" status, no errors reported anywhere, it always finds the device too.
I can't seem to get anywhere with this phone. Everything I try to do in recovery is met with freezes and reboots. It seems like maybe the internal emmc has taken a dump.
Problem is I'm literally 3 days out of the 1 year warranty from when I received my phone, and having tried to work with Huawei support previously, I'm 100% certain they won't help. I came across a few threads on here similar to mine recently without any real resolution other then RMA'ing it. I figured I'd post here for a last desperate attempt if anyone has any other suggestions, because I don't know what I'll do. The Pixel XL is ungodly expensive, and conveniently out of stock. And I don't think I could talk myself into buying another Huawei anytime soon after this.
Any suggestions?

the.root said:
I was on the latest CM13 nightly (was waiting a bit to go to 14.1) So I went to bed last night and my phone did a reboot as I was setting my alarm. Didn't think too much of it, crap happens. I waited for it to come back fully into the OS, which it did, checked my alarm. Noticed something strange I got the CM Updater notification in the statusbar ("There are new updates available" - CM14.1-12-02 or something), which I thought was weird that's the first time it's said that, and I've checked the CM Updater before and since the 14.1 switch there's been nothing there. As it should, I imagine, not try to update major versions like that. Anyways I dismissed it and went to bed (this entire thing is PROBABLY entirely unrelated, but I found it's timing interesting at least).
Woke up a few hours later to my phone getting really hot, and stuck in an infinite boot loop. It never gets passed the first Google screen. If I let it go it'll sit there for several minutes and maybe reboot. I was able to get into the bootloader, choosing Boot Recovery though sends me back to the Google bootup screen where it never progresses, doesnt have the blue text in the top that says booting into recovery..
Was able to get into the phone with fastboot so I tried flashing the latest recovery I had installed TWRP-3.0.2-2-angler. Still wouldn't boot into it, sometimes it would get to the TWRP recovery loading page, and then sit there for a couple minutes, then reboot.Tried flashing it a few times with fastboot with no success.
Erased userdata with fastboot, then did a full factory reflash of several images, MDB081 - MTC20l (factory images I know I've used in the past to recover, had them saved). Rebooted and I still can't get into the OS (stuck at first Google logo). Interesting the stock recovery though loads.
Flash an older TWRP recovery I had saved twrp-2.8.7.2-angler . Was able to get into recovery finally - kind of. Sometimes it still locks up and wont let me swipe to enter TWRP. The first time it let me in it asked me for my decryption password - I didn't have a password - had a swipe and fingerprint setup only. Got in again and first thing I tried doing honestly is erasing (formating) all my data, thinking if I'm going to have to warranty this phone or sell it broken, I want to make sure my data is wiped. Also I figure after that I can try to reinstall CM etc like I would a completely fresh build. It complained about not being able to mount the partition and locked up in TWRP then eventually auto rebooted. Got in again and tried to do a basic wipe, it said it cant find /sdcard then said it wiped, and then froze, auto rebooted again after a few seconds.
To note : All fastboot commands seem to execute with "OKAY" status, no errors reported anywhere, it always finds the device too.
I can't seem to get anywhere with this phone. Everything I try to do in recovery is met with freezes and reboots. It seems like maybe the internal emmc has taken a dump.
Problem is I'm literally 3 days out of the 1 year warranty from when I received my phone, and having tried to work with Huawei support previously, I'm 100% certain they won't help. I came across a few threads on here similar to mine recently without any real resolution other then RMA'ing it. I figured I'd post here for a last desperate attempt if anyone has any other suggestions, because I don't know what I'll do. The Pixel XL is ungodly expensive, and conveniently out of stock. And I don't think I could talk myself into buying another Huawei anytime soon after this.
Any suggestions?
Click to expand...
Click to collapse
It's an ongoing thing with these 6P's and 5X's. Some have been able to fully recover and others like myself were not. Here is a guide that might be able to help you if you haven't come across it yet. Good luck..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page6
Check Warranty Status:
http://consumer.huawei.com/us/support/warranty-query/index.htm

BIGSAMDA1ST said:
It's an ongoing thing with these 6P's and 5X's. Some have been able to fully recover and others like myself were not. Here is a guide that might be able to help you if you haven't come across it yet. Good luck..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page6
Check Warranty Status:
http://consumer.huawei.com/us/support/warranty-query/index.htm
Click to expand...
Click to collapse
Thanks. I came across that. I tried flashing MMB29P as well as several other factory images without success. My problem now it seems no matter what I flash I cannot get back into recovery anymore. Even if it's stock or if it's TWRP (any version - including 3.0.2.0 as they suggest), so I don't really get passed step 4-5 in that guide. I guess she only had so many reads left in her, sigh.
WEIRD @ warranty link. It says from my S/N that it's valid until 2017-02-17. I don't know how, I purchased it 2015-10-22, it shipped 2015-11-24, and I got it 2015-11-30. Unsure how/why that would've gotten extended until February. I'm concerned they'll get it back then deny it once they figure that out, or figure out it's been unlocked/flashed. When I first got the phone i had issues with it charging, I narrowed it down to the USB C->C cable being faulty, and contacted Huawei. They absolutely refused to replace just the cable. Said I had to ship the whole phone back and it'd take AT LEAST 3-4 weeks to get it back. I argued with several people on the phone there (their support 100% refuses to give you their name or transfer to their supervisors btw), and finally asked google support to pull some strings and get in contact with someone there to replace a simple freaking cable - no one cared at all - spent several hours trying and got nowhere. I'm /done with Huawei. I think my best bet is to probably find out how well that American Express extended warranty claim works, I've never actually had to use it before. IDK what I'll do after that. Sad this is a common problem with these phones exactly one year out, so even if I wanted to buy a used one on eBay I'd risk the same thing shortly thereafter.
I'll keep the phone powered off for a while and try some more flashing later see if I can get back into recovery to try the rest of his steps in that article. It's not looking promising anymore.

Well being that it's a known issue, like I said, I myself ran into this fiasco, had phone rooted and running custom rom. I myself couldn't get into recovery but was able to flash all factory images and relock bootloader manually. I then called Huawei and played dumb telling them that I had updated my phone to the latest firmware via OTA and then it went into bootloop. They never asked if it was unlocked and I never volunteered to tell them either. I had bought my 6P through Best Buy and still had receipt Incase they'd asked for it which they didn't. All they did was ask for IMEI # along with Ser # and verified that it was still under warranty, then they emailed me a return label. I shipped phone to them and in a matter of like a week or so I had a brand new device in hand. Build date on it was August, 16, 2016. So far running good but let's see for how long.

BIGSAMDA1ST said:
Well being that it's a known issue, like I said, I myself ran into this fiasco, had phone rooted and running custom rom. I myself couldn't get into recovery but was able to flash all factory images and relock bootloader manually. I then called Huawei and played dumb telling them that I had updated my phone to the latest firmware via OTA and then it went into bootloop. They never asked if it was unlocked and I never volunteered to tell them either. I had bought my 6P through Best Buy and still had receipt Incase they'd asked for it which they didn't. All they did was ask for IMEI # along with Ser # and verified that it was still under warranty, then they emailed me a return label. I shipped phone to them and in a matter of like a week or so I had a brand new device in hand. Build date on it was August, 16, 2016. So far running good but let's see for how long.
Click to expand...
Click to collapse
Hmm interesting. Maybe their US support has improved since last year. So it was brand new not refurbished? Did you get the full retail box set? I bought mine directly through Huawei, so I would like to think that they would have accurate warranty data, but perhaps not. I will consider RMA'ing it to them if it's really a new one. It's either that or a 550$ refund from my credit card company. I haven't tried fastboot lock yet, will do that when I give up on all else lol (and need to return it), but hopefully that will work if the rest of the emmc is hosed.

Yeah, mine came in a new box, sealed like day one. I was surprised thought I'd be getting a refurbished device but I can honestly say it was a brand new one. And I don't blame you on trying to get the device to a working state. I tried everything and it's mother before giving up and finally relocking bootloader and sending it in.

BIGSAMDA1ST said:
Yeah, mine came in a new box, sealed like day one. I was surprised thought I'd be getting a refurbished device but I can honestly say it was a brand new one. And I don't blame you on trying to get the device to a working state. I tried everything and it's mother before giving up and finally relocking bootloader and sending it in.
Click to expand...
Click to collapse
Just called them. They won't accept it back without a proof of purchase. I have to send in the proof of purchase before they'll approve the RMA and then I get the shipping label/information. And "they can't look it up by S/N, doesn't matter if the website says it's in warranty". LOL. Sounds about right from what I remember of their support. They say their website is inaccurate, and cant ever verify/lookup that I bought the product directly from them. Maybe I'll try back tomorrow to see if someone else will help but it's unlikely from the sounds of it. She did say this is very common problem however, knew all about it.

Damn, That truly sucks..I would definitely give them a call again and see if I get a different rep. I was lucky with the one I got, he basically knew it was an ongoing thing and really didn't give me a hard time. He didn't even ask for a receipt, about the only thing he asked was that if the bootloader was locked or unlocked and when I told him it was locked, he then proceeded with the RMA procedure.

BIGSAMDA1ST said:
Damn, That truly sucks..I would definitely give them a call again and see if I get a different rep. I was lucky with the one I got, he basically knew it was an ongoing thing and really didn't give me a hard time. He didn't even ask for a receipt, about the only thing he asked was that if the bootloader was locked or unlocked and when I told him it was locked, he then proceeded with the RMA procedure.
Click to expand...
Click to collapse
Yeah I played dumb and all, didn't help. She didn't ask me any real questions she was convinced of the problem just from my description. She also said it's 12 months from the date I purchased it and not when I received it in the mail (so since they took 5-6 weeks to get it to me - preorder madness - I don't get that time back in the warranty) lol. Not like it matters now, just to further comment on how crappy their support/warranty is (in my experience).
I'll follow up if I have any more luck unbricking the device or warrantying it for that matter.

Good luck on either with the warranty or bringing it back to life.

I also have problems such as your support Huawei says four weeks of waiting

Got a recovery image to boot finally (after like 10x attempts at flashing one). Tried doing the nandroid backup as that guide suggests, says it cannot find/mount /sdcard and freezes/reboots. Tried going into wipe -> advanced and repairing internal storage and data and it was an invalid partition or something. Tried repairing system and it locked up again. Tried formatting them with fastboot and didn't work. Tried installing the latest 7.0 factory image for the hell of it, nadda. Relocked the bootloader successfully. Giving up. Filed an claim online with my credit card company (most do a +1 year extended warranty), we'll see how that goes, if I get lucky they'll approve the claim and let me keep the phone. May pick up a used 5x or something.

the.root said:
Got a recovery image to boot finally (after like 10x attempts at flashing one). Tried doing the nandroid backup as that guide suggests, says it cannot find/mount /sdcard and freezes/reboots. Tried going into wipe -> advanced and repairing internal storage and data and it was an invalid partition or something. Tried repairing system and it locked up again. Tried formatting them with fastboot and didn't work. Tried installing the latest 7.0 factory image for the hell of it, nadda. Relocked the bootloader successfully. Giving up. Filed an claim online with my credit card company (most do a +1 year extended warranty), we'll see how that goes, if I get lucky they'll approve the claim and let me keep the phone. May pick up a used 5x or something.
Click to expand...
Click to collapse
I would stay away from the 5X as well..lol They are going through the same thing the 6P is going through. It's all over Reddit and XDA as well. I'm currently using the 6P but I'm waiting on the One Plus 3T to arrive. I have a few other devices to play with but I'm still using the 6P waiting for the 7.1.1 update to drop in a few days to see how that goes.

BIGSAMDA1ST said:
I would stay away from the 5X as well..lol They are going through the same thing the 6P is going through. It's all over Reddit and XDA as well. I'm currently using the 6P but I'm waiting on the One Plus 3T to arrive. I have a few other devices to play with but I'm still using the 6P waiting for the 7.1.1 update to drop in a few days to see how that goes.
Click to expand...
Click to collapse
Oh what the **** . That sucks. My wife owns a 6P and my son has a 5x. So our house is a ticking time bomb of failure. Maybe I'll buy a Note 7 and finish the job. I have my old Nexus One and Tmobile G1, both still power on last time I checked. I've gotten rid of all other past cell phones we've had unfortunately. Used to have so much trust in the Nexus lineup

the.root said:
Oh what the **** . That sucks. My wife owns a 6P and my son has a 5x. So our house is a ticking time bomb of failure. Maybe I'll buy a Note 7 and finish the job. I have my old Nexus One and Tmobile G1, both still power on last time I checked. I've gotten rid of all other past cell phones we've had unfortunately. Used to have so much trust in the Nexus lineup
Click to expand...
Click to collapse
Lmao.. Yeah I would stay away. Also you have to throw in the fact that the devices only have support until at least Sept. of 2017, then unless you're flashing custom roms your basically stuck.

BIGSAMDA1ST said:
Lmao.. Yeah I would stay away. Also you have to throw in the fact that the devices only have support until at least Sept. of 2017, then unless you're flashing custom roms your basically stuck.
Click to expand...
Click to collapse
Yeah I mean I've always liked the Nexus devices because they always seem to have a good strong developer/modding community. I don't know the definition of a stock - anything. I recently converted my wife & son over to Nexus from Samsung's because I got frustrated with how they now lock down their phones. I have no doubt the 6P/5x (if they survive that long lol) will still be one of primary devices in this community to receive new OS/etc (cyanogenmod/whatever) well past the September EOL. Just look at the older Nexus phones still some of the first to receive the CM14.1 builds.

the.root said:
Yeah I mean I've always liked the Nexus devices because they always seem to have a good strong developer/modding community. I don't know the definition of a stock - anything. I recently converted my wife & son over to Nexus from Samsung's because I got frustrated with how they now lock down their phones. I have no doubt the 6P/5x (if they survive that long lol) will still be one of primary devices in this community to receive new OS/etc (cyanogenmod/whatever) well past the September EOL. Just look at the older Nexus phones still some of the first to receive the CM14.1 builds.
Click to expand...
Click to collapse
Exactly.. That's why I'm still keeping mine and hoping it doesn't decide to go on the fritz again.

Oneplus sent me a bricked 6t

So I just received a brand new Oneplus 6t like 20 minutes ago. Open the box and it won't turn on. I assume its dead so I plug it in and no response. Left it that way for 10 minutes and nothing happens.
I plugged it into my computer and it shows up in device manager as Qualcomm HS-USB QDLoader 9008. Did Oneplus forget to flash the firmware to my phone?? Is there anyway I can fix this now or do I have to wait for them to send me another and send mine back?

aeppacher said:
So I just received a brand new Oneplus 6t like 20 minutes ago. Open the box and it won't turn on. I assume its dead so I plug it in and no response. Left it that way for 10 minutes and nothing happens.
I plugged it into my computer and it shows up in device manager as Qualcomm HS-USB QDLoader 9008. Did Oneplus forget to flash the firmware to my phone?? Is there anyway I can fix this now or do I have to wait for them to send me another and send mine back?
Click to expand...
Click to collapse
Did you try to boot into recovery?
FWIW,my T-Mobile version was somewhat slow to boot on the 1st attempt,but,afterwards,no problem...

KOLIOSIS said:
Did you try to boot into recovery?
FWIW,my T-Mobile version was somewhat slow to boot on the 1st attempt,but,afterwards,no problem...
Click to expand...
Click to collapse
It won't boot at all, hold power for 1 minute and no response

aeppacher said:
It won't boot at all, hold power for 1 minute and no response
Click to expand...
Click to collapse
Gotcha,guess it's kinda difficult to boot into recovery if it's not there....... just thought I'd ask,for others to benefit should they run into the same issue.
Definitely falls under the warranty,guessing you'll have no problem getting a replacement,or,getting everything installed on that one & returned to you.
Please keep us posted on your outcome. :good:

KOLIOSIS said:
Gotcha,guess it's kinda difficult to boot into recovery if it's not there....... just thought I'd ask,for others to benefit should they run into the same issue.
Definitely falls under the warranty,guessing you'll have no problem getting a replacement,or,getting everything installed on that one & returned to you.
Please keep us posted on your outcome. :good:
Click to expand...
Click to collapse
Contacted customer service, they said they will open a ticket and try to get back to me within 24 hours. Abysmal service from Oneplus yet again

aeppacher said:
Contacted customer service, they said they will open a ticket and try to get back to me within 24 hours. Abysmal service from Oneplus yet again
Click to expand...
Click to collapse
Been there myself w/the infamous brickloop on the OG 1+1,someone from here @ XDA came up w/the fix & a few days later,OnePlus magically "solved" the issue,just added a few needless lines of code to distinguish it from the original fix.
Yeah,I spent several hrs spanning over a week w/OnePlus on Team Viewer,not fun,hoping your outcome goes much smoother & in less time.

Same here. Mine worked for about an hour. Then it turned itself off. Now I can't get anything out of it. Tried holding down the power button, holding down vol. up, vol. down, etc. Nothing. Trying to work through this with support.
lsusb recognizes a USB device -- Qualcomm Gobi Wireless Modem. But that's it. adb does not see it.

That sucks, that's the reason i have a 6t now. I ordered a p3xl and it was doa. Line got stuck processing the return. So i cancelled and bought this.
Good luck

I will say that once I got it setup initially and then ran the system update that it did not reboot after hit reboot and I couldn't get it to come on for a while. I thought the update had bricked it. But I kept fiddling with it every once in a while holding down the power button and it came back to life. So who knows.
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app

aeppacher said:
So I just received a brand new Oneplus 6t like 20 minutes ago. Open the box and it won't turn on. I assume its dead so I plug it in and no response. Left it that way for 10 minutes and nothing happens.
I plugged it into my computer and it shows up in device manager as Qualcomm HS-USB QDLoader 9008. Did Oneplus forget to flash the firmware to my phone?? Is there anyway I can fix this now or do I have to wait for them to send me another and send mine back?
Click to expand...
Click to collapse
Uh oh, the iconic Qualcomm 9008, a fix is very rare and very device specific for this issue. So basically yeah, OnePlus forgot to write anything to the storage, more than likely you don't have a recovery mode either. Just send it back and get it replaced.

Is there a charging indicator on this phone? Just curious. My phone is still dark/dead. Dealing with support on getting a replacement. But I'm wondering about the charging indicator. I get absolutely nothing. Is there supposed to be a battery charging icon on the screen, when the phone is off but plugged in?

gnunotme said:
Is there a charging indicator on this phone? Just curious. My phone is still dark/dead. Dealing with support on getting a replacement. But I'm wondering about the charging indicator. I get absolutely nothing. Is there supposed to be a battery charging icon on the screen, when the phone is off but plugged in?
Click to expand...
Click to collapse
Yes there is supposed to be a battery indicator. Mine doesn't do anything and is confirmed defective. Returning it and getting another.

Well I ended up "fiddling with it" enough that it came back to life. It started up when I held down the vol. down and power buttons. I had tried that a hundred times before, along with other combinations. No idea why it worked this time. I hope this doesn't happen again. Thanks, everyone.

aeppacher said:
So I just received a brand new Oneplus 6t like 20 minutes ago. Open the box and it won't turn on. I assume its dead so I plug it in and no response. Left it that way for 10 minutes and nothing happens.
I plugged it into my computer and it shows up in device manager as Qualcomm HS-USB QDLoader 9008. Did Oneplus forget to flash the firmware to my phone?? Is there anyway I can fix this now or do I have to wait for them to send me another and send mine back?
Click to expand...
Click to collapse
I have the same problem just 1 hour after I unboxed it! i'm so unlucky

GeoffreyLH said:
I have the same problem just 1 hour after I unboxed it! i'm so unlucky
Click to expand...
Click to collapse
Don't panic dude. If you have the qualcomm thing when you plug into a computer you might actually be fine. I managed to fix mine (after ordering a replacement ironically). Basically the device is permanently stuck on and you can't do anything til the battery drains entirely. The mode is ignoring the power button.
After mine died completely the power button would get it into a state where it would say its out of battery and to charge. After charging I was able to boot to bootloader (which was already unlocked wtf) and flash the images in the dump someone posted under general one by one.
When it booted it worked partially, fingerprint was ****ed. At this point try to update and it will fail saying partial update failed, try full update. Once this was done it flashed all partitions. The reason for this is my device had the bootloader unlocked but critical wasn't unlocked and it wouldn't let me unlock it saying it already was unlocked, so when I flashed the images from the dump I couldn't flash critical images. The full signed update from the system flashed these critical partitions and its fully working. I am still sending it back because I don't know whether to trust the device.
Update me if this works for you!

this literally just happened to me...i almost crapped myself. i fiddled with the buttons for a bit, and it came back.

I would try to send it back and see if they can send another one out.

aeppacher said:
Don't panic dude. If you have the qualcomm thing when you plug into a computer you might actually be fine. I managed to fix mine (after ordering a replacement ironically). Basically the device is permanently stuck on and you can't do anything til the battery drains entirely. The mode is ignoring the power button.
After mine died completely the power button would get it into a state where it would say its out of battery and to charge. After charging I was able to boot to bootloader (which was already unlocked wtf) and flash the images in the dump someone posted under general one by one.
When it booted it worked partially, fingerprint was ****ed. At this point try to update and it will fail saying partial update failed, try full update. Once this was done it flashed all partitions. The reason for this is my device had the bootloader unlocked but critical wasn't unlocked and it wouldn't let me unlock it saying it already was unlocked, so when I flashed the images from the dump I couldn't flash critical images. The full signed update from the system flashed these critical partitions and its fully working. I am still sending it back because I don't know whether to trust the device.
Update me if this works for you!
Click to expand...
Click to collapse
I reached the live chat support, they told me to charge it for 2 hours and try to boot it but it doesn't work, now I assume it is fully charged so it will take an eternity for the phone to drain, I think I have no choice but to ask for a replacement unless it boots up until then. Anyway the phone is actually detected by Windows so there might be some hope..

jaben2 said:
That sucks, that's the reason i have a 6t now. I ordered a p3xl and it was doa. Line got stuck processing the return. So i cancelled and bought this.
Good luck
Click to expand...
Click to collapse
Whoa, you saved some good money!

Hey Guys,
I just received the Oneplus 6T - The battery went off, I tried to charged it but no signal . When I plug it into my computer, it shows up it shows up in device manager as Qualcomm HS-USB QDLoader 9008.
I don't understand why I can not charge it ? Does anyone get something ?