Related
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
Help!
My Nexus 7 screen randomly cracked (no touch input) and I have to send it back to Asus for RMA, I have managed to use Wug's Toolkit to flash stock and unroot, but when I try to re-lock the bootloader with the tool a message pops up on the Nexus 7 screen asking me to allow the connection, but I can't because if I take out the USB cable to put in my OTG mouse, the message goes away!
I've tried Airdroid but that doesn't work, please help otherwise Asus will say my warranty is voided :crying: :crying:
Thank you
Alan
Keydogg1 said:
Help!
My Nexus 7 screen randomly cracked (no touch input) and I have to send it back to Asus for RMA, I have managed to use Wug's Toolkit to flash stock and unroot, but when I try to re-lock the bootloader with the tool a message pops up on the Nexus 7 screen asking me to allow the connection, but I can't because if I take out the USB cable to put in my OTG mouse, the message goes away!
I've tried Airdroid but that doesn't work, please help otherwise Asus will say my warranty is voided :crying: :crying:
Thank you
Alan
Click to expand...
Click to collapse
Mine cracked for no reason too!!
did you have screen lifting problems maybe?
What does RMA stand for? Can you get a new one for this?
And looks like we have the same problem...maybe try with a usb extender? Or bluetooth mouse
RMA is just the returns procedure, but the guy on the phone said I have a chance of getting it repaired through warranty if it's a screen defect (which it is, i have never damaged it!).
I don't have a bluetooth mouse
What exactly is the difficulty with putting the tablet into bootloader mode and using a single fastboot command to relock the bootloader? You don't need a mouse or even a working screen to do that.
If you installed a toolkit on your PC, then you also have fastboot installed too - the toolkit is mostly just a wrapper around the fastboot (and adb) program(s).
Probably you can simply just repeat what you tried with the toolkit but starting with the tablet in bootloader mode. (But don't quote me on that, I don't use toolkits).
BTW, it is not the *current* condition of the bootloader lock state that determines the validity of your warranty - if you unlocked the boot loader at any time in the past, your warranty is voided.
bftb0 said:
BTW, it is not the *current* condition of the bootloader lock state that determines the validity of your warranty - if you unlocked the boot loader at any time in the past, your warranty is voided.
Click to expand...
Click to collapse
Im not too sure about that...
I talked to my local htc service and they say that they dont care what was done before it, they just want it in the condition in which they sold it to me.
mrsofa said:
Im not too sure about that...
I talked to my local htc service and they say that they dont care what was done before it, they just want it in the condition in which they sold it to me.
Click to expand...
Click to collapse
I get that. It makes no business sense for Asus to go all CSI on every tablet that comes in the door for repair, although I'm pretty sure they could tell quite easily whether a tablet has been previously unlocked if they actually wanted to. (No matter what state it is in when they receive it).
My point was about the T&C's (legal terms) that owners agree to in the click-through dialogs when they unlock their tablet. What folks "get away with" is a separate issue.
I'm pretty sure that XDA's policy is to encourage people to act in a stand-up fashion. Agreeing to terms and then later doubling back on them reflects poor character.
Unlocking or re-locking the bootloader doesn't involve the touch screen at all... everything is done with the buttons on the right hand side of the Nexus 7.
(Re-locking doesn't even require the buttons- just fastboot oem lock).
It's also debatable whether unlocking the bootloader actually violates warranty... see the screenshot attached (from my last N7 OEM unlock).
- note the use of the phrase...
may void warranty
'May' is a highly subjective word, that covers a whole multitude of sins.
Rgrds,
Ged.
Well, I suppose to avoid any shed tears I should have just pointed out that the information the OP sought - and now answered - can be posed in a way that completely avoids making XDA look like a place that encourages questionable behavior, or that people that offer technical assistance are complicit in those behaviors.
For instance:
"Hi! My Nexus 7 has a cracked screen so I am unable to use the touchscreen. I would like to lock the bootloader. (insert part about toolkit) How do I go about doing this?"
Note the complete lack of mention of warranty or RMA - it is completely irrelevant to the technical part of the discussion anyway & keeps XDA's nose clean.
cheers
Sorry buddy, I didn't mean any offence or to tarnish XDA's reputation - I love this place!
Ged - With regards to the command. I have always used toolkits (newb!) so didn't know how to execute a command whilst it was in fastboot mode, but I've just figured that our and it worked! Thank you very much mate
Keydogg1 said:
Sorry buddy, I didn't mean any offence or to tarnish XDA's reputation - I love this place!
Ged - With regards to the command. I have always used toolkits (newb!) so didn't know how to execute a command whilst it was in fastboot mode, but I've just figured that our and it worked! Thank you very much mate
Click to expand...
Click to collapse
You are most welcome...
Fastboot (and adb) is the easiest way of doing these sorts of things, rather than using a toolkit - although fastboot isn't currently an option for me, as I've relocked my bootloader and am running my device rooted (by exploit) and a custom ROM flashed via TWRP, which I flashed via the 'dd' command in Terminal Emulator. Thanks to bftb0 for info on how to do that... I was astonished when it worked. You can tell I'm still learning stuff here.
--------
Apologies from me as well, bftb0, regarding 'questionable behavior' and those 'complicit in those behaviors'... it's a fair point well made. XDA is too good and valuable a place to have it's reputation sullied by posts which encroach into areas of dubious legality, so I will confine my future posts to technical matters only... insofar as my current level of knowledge allows.
Rgrds,
Ged.
Did you get it repaired?
My service sent mine to the Czech republic, where they sent me a bill of 218€
Luckily it was just a sample, so the didn't do nothing.
I called the service, and they said that they will not repair the device with warranty and that I have to pay..
By the way im from Slovenia, and had some bad experiences with the htc service, so it's just probably here.
They sent the device back home... so now Im stuck -.-
So u no gonna tell i you got it repaired?
I have a rooted Nexus 7 running JDQ39. It is no longer recognized by my laptop or desktop, regardless of the cable I use. I have used the same laptop/desktop for months without issue. I think it's a hardware failure but I'm open to suggestion.
Anyway, I bought it through the Playstore so I called them for support and they said they could see that I "may be using a rooted device" and told me that I would have to contact the manufacturer or carrier but if unroot and still encounter the issue they will be glad to "take a look". They followed the conversation with the email below.
So it's interesting (but not surprising) that they can tell remotely.
Anyway, any suggestions on how to get back to stock/unrooted without a PC connection?
Thanks
[email protected]
X:XX PM (7 minutes ago)
to me
Hey there Xxx,
Thanks for contacting Google Play! According to our records, it appears you may be using a rooted device. Unfortunately, our ability to troubleshoot issues with rooted devices is limited. They may have altered functionality depending on how the device has been modified and we're not able to see what's happening with the device. For assistance with rooted devices, we recommend contacting your device manufacturer or carrier. However, if you unroot your device and still encounter this issue, please let me know and I will be happy to take a look.
If your device isn't rooted, please let me know, and I'm happy to see what I can do to assist you further. Thank you for your understanding.
Thanks,
Click to expand...
Click to collapse
I dont know about "calling in". But if you downloaded any app requiring root from the play store to that device, it would be a dead giveaway. Titanium backup, super su, rom manager............and the list goes on. That is most likely the reason the last line says "If you're not rooted". They are not "calling in", but simply looking at thier records (app history).
To the main problem, have you tried an alternate cable? I see you have tried multiple pc's, so the cable is the next step. That possibility needs to be eliminated before you can move on to a hardware and/or software failure.
Sent from my Nexus 7 using xda premium
junksecret said:
I have a rooted Nexus 7 running JDQ39. It is no longer recognized by my laptop or desktop, regardless of the cable I use. I have used the same laptop/desktop for months without issue. I think it's a hardware failure but I'm open to suggestion.
Anyway, I bought it through the Playstore so I called them for support and they said they could see that I "may be using a rooted device" and told me that I would have to contact the manufacturer or carrier but if unroot and still encounter the issue they will be glad to "take a look". They followed the conversation with the email below.
So it's interesting (but not surprising) that they can tell remotely.
Anyway, any suggestions on how to get back to stock/unrooted without a PC connection?
Thanks
Click to expand...
Click to collapse
I'd agree with the person above: they likely flagged some root-requiring apps you have on your device and went by that. Google's policy on roots is pretty forgiving, though, to say the least.
In any event, there are some on-device methods you could pursue, but we need to know more about your setup on that side as well. In a similar vein as to what previous poster asked (namely about testing computers and cables), could you link us the method you used to root your device and also post what recovery you're using (stock, TWRP, CWM, etc.) and if you have your bootloader unlocked?
Rirere said:
I'd agree with the person above: they likely flagged some root-requiring apps you have on your device and went by that. Google's policy on roots is pretty forgiving, though, to say the least.
In any event, there are some on-device methods you could pursue, but we need to know more about your setup on that side as well. In a similar vein as to what previous poster asked (namely about testing computers and cables), could you link us the method you used to root your device and also post what recovery you're using (stock, TWRP, CWM, etc.) and if you have your bootloader unlocked?
Click to expand...
Click to collapse
Thanks for the reply, I think I've exhausted the cable and usb port/pc/drivers as the cause. I actually now remember I hooked it up to my stereo and plugged into a cheap charger and got a pretty good spark at the micro usb and the tablet shut off. I left it plugged in and powered back up and thought all was fine. I now think that may have fried something in the micrco usb although it does charge thru it.
I think I rooted using wugfresh's rootkit, this is my 3rd N7 so not positive. I do have the bootloader unlocked and am running CWM Touch recovery.
Any links to a no-pc back to stock would be great!
Thanks
junksecret said:
Thanks for the reply, I think I've exhausted the cable and usb port/pc/drivers as the cause. I actually now remember I hooked it up to my stereo and plugged into a cheap charger and got a pretty good spark at the micro usb and the tablet shut off. I left it plugged in and powered back up and thought all was fine. I now think that may have fried something in the micrco usb although it does charge thru it.
I think I rooted using wugfresh's rootkit, this is my 3rd N7 so not positive. I do have the bootloader unlocked and am running CWM Touch recovery.
Any links to a no-pc back to stock would be great!
Thanks
Click to expand...
Click to collapse
Sent from my Nexus 7 using xda premium
Now we are getting somewhere. It seems you may have shorted a data pin when you plugged it in. I personally never use cheapo chargers. You could try replacing the USB port. If i am not mistaken, it is not soldered to the motherboard, but instead is soldered to its own harness and connected to the mobo via flex cable.
Running (was) a stock rooted N7 v1 on 4.3. Bought a data recovery tool off of the play store to try and recover some photos I had deleted. At some point it rebooted into safe mode, my battery was running low and I shut it off to let it charge. Now it's dead in the water. Stuck in APX mode. I am asking if there is anyway to breathe life back into this tablet.
The tablet does nothing on the screen, period, no matter what you do. When plugged in to a computer it sometimes registers as an unknown device, sometimes APX. None of these get you anywhere. Toolkits on these forums won't recognize the device, installing the android development kit and drivers does nothing, executing commands from the command line is worthless because the device won't register. I do not have any "blobs" and have no clue at this point even what they are or what they could have done for me had I made them.
I've searched this forum and found bits and pieces here and there and wanted to start a thread dealing solely with devices stuck like this and what has or hasn't worked and get others input if warranty service was done and the state your tablet was in when you sent it in (locked/unlocked, rooted etc).
Anyone stuck here will have probably tried the same things as I have but here is is a minor rundown...
1) Every button combo press known to man for short, medium, and extended periods of time.
2) Charging with the Original charger/cable for 1 hour, then button presses then charging for 12 hours.
3) Same as above but with different aftermarket chargers at different amperages.
4) Uninstalling and deleting drivers. Trying different drivers. Getting the Android drivers etc.
5) Trying every toolkit on the forums to no avail because the device won't register.
6) Checking to make sure the battery cables are seated correctly.
7) Screaming and yelling at your new paperweight.
My hope here is that I've missed some important thread about recovery and someone can point me in the right direction. Failing that, if I should get a new mobo or try and send it in for warranty service in the state it's in.
Any help would be much appreciated.
Sent from my Rooted Frameworked SCH-I545 using xda app-developers app
I don't know what you tried before to revive your tablet and what the tool did to get you into this state, but generally APX mode can be left by pushing the power button *only* for about 10-20 sec, as long as there us enough power within your battery and the hardware / software is working / consistent.
Sent from my Nexus 7 using xda app-developers app
I don't think I've ever seen anyone in here describe a situation where they observed the tablet in bootloader mode without seeing *something* on the screen.
And as you found out through your reading, using "nvflash" on the N7 is only useful at this time for folks that made prior disaster recovery preparations. So, APX mode is of no use to you (at this date 12/2013).
So, until you see something happen on that screen, drivers on a PC are of no value to you anyway.
It is really unfortunate that the N7 doesn't have a physical charging indicator - that makes it difficult to distinguish between a tablet which is truly borked vs. one that refuses to boot simply because the battery isn't charged.
Holding down a specific button combo (iirc Pwr+VolUp) during an attempt to get "something, anything" to happen will put the tab into APX mode, so it isn't particularly diagnostic that you have observed APX mode once or twice.
Really about the only way to know if the battery in a non-responsive N7 is charged or not is to put it in another tablet or measure the open-circuit voltage. (About 4.15v fully charged & about 3.5v discharged)
The reason that I mention this is that there have been a few reports from users in similar straits as you that report something like "I don't know what happened, but I tried it a few days later and all of a sudden the tablet booted up". Almost every one of those reports involved mentions of low battery conditions, just as your narrative does.
I don't know what file recovery program you used, but I suspect that is a red herring . It might have to have root privileges in order to read raw partitions, and might even want the tablet in safe mode to minimize write activity by *other apps* while it does it's forensics, but it certainly isn't going to recover files by writing in raw mode on a mounted, live filesystem - it would do all it's writing through normal kernel syscalls. That's the long way of saying that a low battery is more likely to be the original source of your troubles.
So what to do now? I think the first order of business is to figure out if your battery is charged or failing to take a charge. If it really is well charged, then a warranty return is probably in your future.
If you can't find a second N7 or a voltmeter, then you could try just leaving it on the charger for a couple of days... but that really is just a "grope about in the dark, wing & prayer" kind of strategy.
good luck
Button sequences & USB Identifiers (VID/PID pairs):
http://forum.xda-developers.com/showthread.php?t=2133986
You are in the same situation I was in - nothing shows up on screen. I got APX drivers to finally install (had to search all over the internet to find them) and that STILL didn't help. I was never able to get it to come back. Nothing ever showed up on the screen.
No combination of button presses helped. I finally gave up and, since my N7 was still under warranty, I RMA'd it back to ASUS. It took about 3 weeks, but I got it back with a new motherboard installed on it.
It was borked and your's sounds the same way as mine. Just either register your N7 on the ASUS website and RMA it that way, or call it in over the phone and RMA it that way. Hopefully, you still have the box your N7 came in because you'll need the serial number.
Others have stated you can get it by opening the back, but that will void your warranty. I do believe you MUST have the serial number, so find the box and get it from there.
Also, you'll definitely lose everything that was there, especially if they replace the motherboard. So hopefully, you backed it up. I backed mine up just before it got borked, so I was lucky.
Good luck!
I am wary of trying to do the battery swap. I went and bought a new version after it crashed but I would be voiding both warranties to try the battery swap.
I do have the serial number if I want to try and get service.
I have done some reading about "deep discharge" battery issues and I suspect this may be a part if it but I have tried leaving it plugged in for days and nada.
I don't know if there is a way to "shock" or jump start the charging process and I am going to put the multimeter on it tomorrow and see what I get.
Thanks for everyone's input. I will keep you up to date.
Sent from my Rooted Frameworked Verizon Galaxy S4 on MJ7 using the XDA App.
My nexus 6p suddenly won't start, I've had my phone since May 2016 so more than a year now.
I've flashed a custom ROM onto it, I'm sure this isn't a software issue because it's been running fine since I bought it (and flashed it) and I followed all the instructions correctly.
I've read through this thread and tried the solutions there, hold the power button for longer than usual (a few minutes), hold the volume down button and power together, hold the volume down button then charge it, now hold the power button. I tried all 3 solutions which worked for many in that thread, but not me.
This all started 2 days ago, with no changes software-wise and using the same configuration as when I first flashed it, I opened the app HERE Maps and then my phone froze, totally stuck and unresponsive, restarting was no good, I had to go into TWRP and wipe the cache and dalvik cache, and it booted fine.
Today, same thing, I opened up HERE Maps and it got stuck again, I now notice that it takes longer than usual to start up via the power button, and wiping the cache and dalvik cache does not work anymore, it stucks on boot.
Now, my phone is not able to start at all. I think this is a hardware-related issue.
So quick recap:
1. Opened HERE Maps and gets frozen
2. Wiping cache and dalvik cache no longer works, stuck on boot.
3. Phone not able to start at all.
I am out of warranty period-wise, but I also custom it, so obviously my warranty is out the window. I need some insight from you guys here at XDA before I buy another costly phone.
someRandomSamaritan said:
...Now, my phone is not able to start at all. I think this is a hardware-related issue...
Click to expand...
Click to collapse
You're probably correct. Since you are unlocked and have a working Recovery mode, you may be have some success with the 4 core fix/workaround. Have you attempted a factory reset? Formatted partitions and flashed a full ROM using the flash-all.bat script?
v12xke said:
You're probably correct. Since you are unlocked and have a working Recovery mode, you may be have some success with the 4 core fix/workaround. Have you attempted a factory reset? Formatted partitions and flashed a full ROM using the flash-all.bat script?
Click to expand...
Click to collapse
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
someRandomSamaritan said:
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
Click to expand...
Click to collapse
Can you access recovery or bootloader mode?
If within warranty, contact google/Huawei depending on where you purchased the phone from.
You could try telling google that your phone is bootlooping for a potential out of warranty RMA.
someRandomSamaritan said:
No, I really mean can't start it. Absolutely zero. I can't get it to boot, oddly enough it did work a few times until it doesn't respond at all.
How am I suppose to do anything software-related if there's no electricity? I have zero options, maybe there's something new I could try?
EDIT: I forgot to mention that my battery was 100% full charge when this happened. At this point I think either the battery suddenly died or the power button is broken
Click to expand...
Click to collapse
Is it recognized at all when you plug a data cable to your PC? Your phone may be stuck in Qualcomm's EDL mode. Search.
No recovery mode, no TWRP, not within warranty, plug in data cable into PC not detected (makes sense, it's not powered on after all)
You could try telling google that your phone is bootlooping for a potential out of warranty RMA.
Click to expand...
Click to collapse
This is a possible option..I'll try that tomorrow when it's morning
Anything else I could try? I think the most obvious methods are not available for me with this kinda situation
someRandomSamaritan said:
No recovery mode, no TWRP, not within warranty, plug in data cable into PC not detected (makes sense, it's not powered on after all)
Click to expand...
Click to collapse
If your phone is in EDL mode, there is no indication the phone is on. No boot, no lights, no noise (except from the PC when the USB driver loads). You may want to try several long power button only holds (several minutes) with the phone plugged into your PC. I suppose it is also possible the power switch is bad, but you would be the first I've heard of. Unless you bought your phone directly through Google you will get nowhere with them. They will direct you to Huawei and you said you were out of warranty.
v12xke said:
If your phone is in EDL mode, there is no indication the phone is on. No boot, no lights, no noise (except from the PC when the USB driver loads). You may want to try several long power button only holds (several minutes) with the phone plugged into your PC. I suppose it is also possible the power switch is bad, but you would be the first I've heard of. Unless you bought your phone directly through Google you will get nowhere with them. They will direct you to Huawei and you said you were out of warranty.
Click to expand...
Click to collapse
Okay, this is helpful, you guys seems to think it is in EDL mode (which I haven't heard of until now), I'll try this and hopefully a driver loads or something
EDIT: nope, no drivers are loading, doesn't seem to be anything new in device manager, no device plug in sound, how sure are you that I'm in EDL mode?
It did work a few times yesterday (being able to boot into TWRP and wiping cache and dalvik cache), but now I'm not so lucky, it doesn't work anymore. I don't believe my phone is completely dead for some reason, I still do believe it can be saved. Hopefully I'm right :|
If I plan on buying a new phone, should I buy another 6p? I love the look and feel of it, and it's easy to mod. I can't really go and get another different phone because I prefer purenexus ROMs than any other, it's just simple and clean, problem is, what if another year from now my new 6p breaks? How can I trust that the new phone won't break the exact same way?
What if I end up buying a new 6p every 1 year or so? I'm starting to question the reliability of the 6p, is what I'm facing a very common issue?
someRandomSamaritan said:
If I plan on buying a new phone, should I buy another 6p? I love the look and feel of it, and it's easy to mod. I can't really go and get another different phone because I prefer purenexus ROMs than any other, it's just simple and clean, problem is, what if another year from now my new 6p breaks? How can I trust that the new phone won't break the exact same way?
What if I end up buying a new 6p every 1 year or so? I'm starting to question the reliability of the 6p, is what I'm facing a very common issue?
Click to expand...
Click to collapse
I wouldn't recommend the nexus 6p. I would have a look at the latest pixel 2. They have project treble.
Your issue is different than most others. Most n6p with issues are bootlooping devices.
I have the same exact problem and have tried all sorts of fixes...
This is a serious problem most likely on Huawei's end. All I was doing was charging my phone and using facebook and my phone freezes...
BadBoy2K7 said:
I have the same exact problem and have tried all sorts of fixes...
This is a serious problem most likely on Huawei's end. All I was doing was charging my phone and using facebook and my phone freezes...
Click to expand...
Click to collapse
Did you managed to solve it in the end or ended up RMAing the phone away and getting a new one?
I wouldn't recommend the nexus 6p. I would have a look at the latest pixel 2.
Click to expand...
Click to collapse
Pixel 2 is some expensive thing, out of my budget
someRandomSamaritan said:
Pixel 2 is some expensive thing, out of my budget
Click to expand...
Click to collapse
Then you should look for alternatives. Perhaps OnePlus 5T, etc.
I think I'm out of luck, my phone seems to be dead
As a last resort, I do plan to take it to a phone repair shop and see if they could do something, maybe the battery died? Unlikely but it's worth trying
I tried what was suggested here, plug the phone to a PC and see if a drivers loads or if detected by device manager, or if hearing connect/disconnect sound. Nothing, no signs. Anything else to try by myself?
someRandomSamaritan said:
I think I'm out of luck, my phone seems to be dead
As a last resort, I do plan to take it to a phone repair shop and see if they could do something, maybe the battery died? Unlikely but it's worth trying
I tried what was suggested here, plug the phone to a PC and see if a drivers loads or if detected by device manager, or if hearing connect/disconnect sound. Nothing, no signs. Anything else to try by myself?
Click to expand...
Click to collapse
Repairmen in China have been repairing nexus 5x and 6p by resoldering the cpu. I wish I knew a way to contact a reliable english speaking repair centre.
I was facing bootlooping problem with my Nexus 6P and bootloader was locked so was unable to flash ROM by any mean.
So I tried following few threads and did "fastboot continue" and my device is not showing any sign of power since then. When connected to PC then no USB connection is there.
Is there any suggestions that can solve issue?
someRandomSamaritan said:
Did you managed to solve it in the end or ended up RMAing the phone away and getting a new one?
Click to expand...
Click to collapse
No. Unfortunately this happened to me last month and ive had the phone for almost 2 years now. Its sad because others are having the same issue and I think the hardware is faulty
I just called up a local phone repair and they said from their experience of repairing nexus 6p phones, most (if not all) of them had dead motherboards. The technician told me to get a new model of a phone and skip the 6p as it is a poorly built phone.
I consider saving up for a pixel..
NoobInToto said:
Repairmen in China have been repairing nexus 5x and 6p by resoldering the cpu. I wish I knew a way to contact a reliable english speaking repair centre.
Click to expand...
Click to collapse
Ive heard of people baking motherboard on Nexus 5x and many other phones to reflow the solder.