Develop Bugs

[Q] i fell into a river

... and yeah i had my One X with me and thats why im posting here... and I don't have insurance!! :crying:
The good news is that after the miraculous rice trick, it mostly works, there are just few things that i discovered are still failing:
The digitizer has a blind area in the middle of the screen
The buttons at the bottom are not working.
The rest of the phone is working, internet, wi-fi, gps and i can even made phone calls.
So, after trying the official instances, meaning going to my cellphone vendor an complained about it without mentioning the river part of the story, they took it for about two weeks, and i just got it back yesterday, and the only outcome of it was a nice pic as a proof of the water damage, so surprise surprise, it was declare out of warranty. The annoying bunus is that while in their checking I got an extra failure: The volume buttons are now not working. To be honest, that failure was there the first time i turned the phone after the incident, but after 2 days in rice they were working allright
And no having volume buttons really sucks! because I can wolk around no having buttons with Button Savior, but for this to be fully working, requires the phone to be rooted, and to be root I have to get to the bootloader, and to do that I have to press the - volume button, did i mentioned that is not working???
So here my first question? Is there any way to root a phone without the volume keys??
The OTA that is running in my phone is 2.17, and from the forums I've read here to root it I need as a firs step go through the HTCdev.com procedure, but again that requires the use of the damn volume key!
Now for the part of the digitizer, I ordered one online, quite cheap, so pretty sure the quality is not the best, but for now thats what I can afford, thought that if thats a succes I can invest in a better one later. And I was planning to be brave and fix it myself, but again reading some forums around here, I found that apparently is quite hard to separate the LCD from the screen, and the LCD might get broken. So, I'm wondering if this is just about been very cautious while doing the fix, or is just impossible to separate this 2 parts without breaking the LCD??
Kind of what I want is to get any advises in this matter, how can I recover most of the functionality of my phone? is it possible? I've been a passive user of xda forums for years, and this is actually my first post.
Thanks for any help guys!!

To reboot in bootloader, connect it through ADB and type in command "adb reboot-bootloader"

4ndr01d3 said:
... and yeah i had my One X with me and thats why im posting here... and I don't have insurance!! :crying:
The good news is that after the miraculous rice trick, it mostly works, there are just few things that i discovered are still failing:
The digitizer has a blind area in the middle of the screen
The buttons at the bottom are not working.
The rest of the phone is working, internet, wi-fi, gps and i can even made phone calls.
So, after trying the official instances, meaning going to my cellphone vendor an complained about it without mentioning the river part of the story, they took it for about two weeks, and i just got it back yesterday, and the only outcome of it was a nice pic as a proof of the water damage, so surprise surprise, it was declare out of warranty. The annoying bunus is that while in their checking I got an extra failure: The volume buttons are now not working. To be honest, that failure was there the first time i turned the phone after the incident, but after 2 days in rice they were working allright
And no having volume buttons really sucks! because I can wolk around no having buttons with Button Savior, but for this to be fully working, requires the phone to be rooted, and to be root I have to get to the bootloader, and to do that I have to press the - volume button, did i mentioned that is not working???
So here my first question? Is there any way to root a phone without the volume keys??
The OTA that is running in my phone is 2.17, and from the forums I've read here to root it I need as a firs step go through the HTCdev.com procedure, but again that requires the use of the damn volume key!
Now for the part of the digitizer, I ordered one online, quite cheap, so pretty sure the quality is not the best, but for now thats what I can afford, thought that if thats a succes I can invest in a better one later. And I was planning to be brave and fix it myself, but again reading some forums around here, I found that apparently is quite hard to separate the LCD from the screen, and the LCD might get broken. So, I'm wondering if this is just about been very cautious while doing the fix, or is just impossible to separate this 2 parts without breaking the LCD??
Kind of what I want is to get any advises in this matter, how can I recover most of the functionality of my phone? is it possible? I've been a passive user of xda forums for years, and this is actually my first post.
Thanks for any help guys!!
Click to expand...
Click to collapse
well, unfortunately i think that you can't unlock your bootloader without at least the power + button in fact here you will need power + button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and yes, it s very hard to separate the lcd from the digitizer but there are very good video guides on how to disassemble it...take a look over here
http://www.youtube.com/watch?v=ceHw6mezG60

Thanks but still stuck!
I got the HTC unlock code thanks to Kroutnuk, unfortunately matt95(BTW, thanks for your reply) is correct and after following that path I got stuck in the image that he posted and with no volume buttons, there is not way I can confirm that I want to unlock, and the only button i can use is the power one that just cancel everything. Is there any way with adb(or anythin else) to trigger the event of pressing the up volume button?

Well I'm sorry to hear what happened to you..and yes I agreed with matt..it's hard to make everything working flawless without
having the need to push the power button..really sorry man..
All I can say if you have some funds go to the booth nearby and repair your hox..

My wife had the exact same thing with an old Sony Ericsson. We too got a letter back with a nice photo of the water damage. I took the phone apart and gently scraped off the white oxidisation residue and voila, the phone worked. Her dad now has it, it's 6 years old and still working. Not bad for a phone that was classed as 'unrepairable'. If the photos show where the damage is, then you could have a go at fixing it yourself, gently and carefully though!. Hope you get it fixed.
Sent from my HTC One X using xda app-developers app

Thanks guys for your comments. Freddy1X, the power button is working, is the volume buttons that are not.
To answer one of my question it is possible to simulate the volume up key with adb:
Code:
adb shell input keyevent 24
The problem is that by the time the confirmation is asked adb cannot connect the device, and therefore is not possible to generate those events, I suppose is because is in the bootloader, so the system is not fully up, or something in this lines??
EDIT: Reading about adb, the way that it works is by running a service in the phone, which I assume implies that android has to be running and therefore it wont work while in the bootloader
Death Of Rats, my next step is doing what you suggest, is just that as you now jus opening the One X is kind of a mission, so I'm trying as much progress through software as possible. But thanks for the hope!!

4ndr01d3 said:
Thanks guys for your comments. Freddy1X, the power button is working, is the volume buttons that are not.
To answer one of my question it is possible to simulate the volume up key with adb:
Code:
adb shell input keyevent 24
The problem is that by the time the confirmation is asked adb cannot connect the device, and therefore is not possible to generate those events, I suppose is because is in the bootloader, so the system is not fully up, or something in this lines??
EDIT: Reading about adb, the way that it works is by running a service in the phone, which I assume implies that android has to be running and therefore it wont work while in the bootloader
Death Of Rats, my next step is doing what you suggest, is just that as you now jus opening the One X is kind of a mission, so I'm trying as much progress through software as possible. But thanks for the hope!!
Click to expand...
Click to collapse
Ahhh..my mistake..I said the wrong button..lol..
I don't want to give you much hope, but if in some way you got your hox volume button working, please share with us..

AT&T HTC ONE X recover contact and pics. PHONE UNLOCKED
I have a water damaged AT&T HTC ONE X unlocked the phone has a water damaged screen but i had the screen replaced and it still doesn't work, so im sure its a internal problem and if someone has a solution im all ears. My issue is my contacts first and then maybe pics but they are not a big deal at all, but would be nice. Can anyone help with this. Phone comes on works fine all the buttons light up just screen is black.

JAhRocky said:
I have a water damaged AT&T HTC ONE X unlocked the phone has a water damaged screen but i had the screen replaced and it still doesn't work, so im sure its a internal problem and if someone has a solution im all ears. My issue is my contacts first and then maybe pics but they are not a big deal at all, but would be nice. Can anyone help with this. Phone comes on works fine all the buttons light up just screen is black.
Click to expand...
Click to collapse
hate to say this but your lcd backlight has gone, the problem is that the back light cant be replaced with a new lcd it is a chip on the mother board which needs to be replaced, it the 220 charger as shown in the link bellow, but thay are really hard to get hold of, a r6 chip out of a iphone 3g will do the job but you will need some one with good soldering experience to do it as believe me its tight in there,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, http://www.google.co.uk/url?sa=i&so...-KucrVU_zKjt_vvUnSC--6mw&ust=1374868583378513
pics in the 9th post down of the link but have a read of the hole link it will help

Sudden power off solved with new battery !!!

Finally tested it today and it really works!. The real fact is on web you always find that "it should" be the battery, and a battery change "whould" solve it, well I have to try it and it really does, so you should get a battery somewhere ( check out I found 2 places on www, dunno if I can put the links please say If I can do so ) and get your phone alive again! ( I'm so happy :laugh: )
Here are 2 dissasemble videos; one from our friend "danieldp1990" and one in russian HD. Whould reccomend use both of them since as nice as the russian video looks, they're missing some parts.
The most hard part is to remove the battery since it's glued and you don't wanna do much strenght since you have the display right below it, so make it slowly.
Danielp thread:
http://forum.xda-developers.com/showthread.php?t=2346031
HD video:
http://www.youtube.com/watch?v=tX_rClLNUU8
Best of luck for the ones that have no warranty left!
PS: I think we can stop looking for soft / alternative solutions.

:thumbup:
Sent from my C6503 using Tapatalk

Remove the battery
Chonwey said:
Finally tested it today and it really works!. The real fact is on web you always find that "it should" be the battery, and a battery change "whould" solve it, well I have to try it and it really does, so you should get a battery somewhere ( check out I found 2 places on www, dunno if I can put the links please say If I can do so ) and get your phone alive again! ( I'm so happy :laugh: )
Here are 2 dissasemble videos; one from our friend "danieldp1990" and one in russian HD. Whould reccomend use both of them since as nice as the russian video looks, they're missing some parts.
The most hard part is to remove the battery since it's glued and you don't wanna do much strenght since you have the display right below it, so make it slowly.
Danielp thread:
http://forum.xda-developers.com/showthread.php?t=2346031
HD video:
http://www.youtube.com/watch?v=tX_rClLNUU8
Best of luck for the ones that have no warranty left!
PS: I think we can stop looking for soft / alternative solutions.
Click to expand...
Click to collapse
:good::good::good:
Now are 3 disassembly videos; one from "danieldp1990" and 2 in russian

I just replace the battery on my phone and the issue of the phone turning off all the sudden. I was pretty easy to do......the hard part the original battery being glued to the back of the phone. That's some sticky tape!

Any idea if the same issue will happen to the new battery?
Sent from my C6506 using XDA Premium 4 mobile app

My Xperia ZL just started doing this sudden shutoff thing but it seams to be getting worse, it's gotten so bad that when you boot up the phone it shows the SONY logo then immediately shuts off. When I plug it into the wall charger the LED lights up RED and then the SONY logo then reboot over and over(Bootloop). But yet i'm able to get it into fastboot and flashmode fine and can flash ftf through Flashtools with no problems i'm wondering if this could be a simple battery problem or if it's a software error. If anyone could help it would be greatly appreciated.

There are loads of posts about this issue on Sony's official forum. Looks like you either have to send it to Sony or put a new battery in.
Sent from my C6506 using XDA Premium 4 mobile app

I finally replaced the battery in my zl, and it fixed the issues of not powering on. But the new battery appears to be having issues. Sometimes it went charge. It will fluctuate percentages, for ex it would go from 58 to 56 to 60 to 55 etc.. It's been acting crazy. Even on various roms. I restored an old backup of miui I had, and it seems more stable, but still won't charge full. The replacement battery was a Sony oem one so I'm not Sue what's up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my C6506 using Tapatalk

please i having same power problmes with my xperia, can you pm where did you get the battery from, i cant find a reliable place that sell them

cubanito08 said:
please i having same power problmes with my xperia, can you pm where did you get the battery from, i cant find a reliable place that sell them
Click to expand...
Click to collapse
http://pages.ebay.com/link/?nav=item.view&id=111348441443&alt=web
Sent from my XT1032 using Tapatalk

maybe its the same problem i have but not sure, ny phone wont pass the Sony screen and turn off unless its connected to a charger or usb, rest works fine, now if its not connected it stays on until u use any app then it shutsdown, then i need to connect to charger to start again, u guys think its the battery ? already flashed retail 4.3 then back to 4.2.2 then back to 4.3 just to make sure wasnt software issue, and i see other people had same problem and fixed it with a battery and no my phone has no warranty since i bought it on one of those simple mobile little stores where stuff is open

cubanito08 said:
maybe its the same problem i have but not sure, ny phone wont pass the Sony screen and turn off unless its connected to a charger or usb, rest works fine, now if its not connected it stays on until u use any app then it shutsdown, then i need to connect to charger to start again, u guys think its the battery ? already flashed retail 4.3 then back to 4.2.2 then back to 4.3 just to make sure wasnt software issue, and i see other people had same problem and fixed it with a battery and no my phone has no warranty since i bought it on one of those simple mobile little stores where stuff is open
Click to expand...
Click to collapse
Ya it's your battery
Sent from my C6506 using Tapatalk

thanks i guess ill get a new battery and hope it fix it

cubanito08 said:
thanks i guess ill get a new battery and hope it fix it
Click to expand...
Click to collapse
It WILL fix it.
Sudden power off, Not powering on unless charger attached, missing signal/signal problems, ultimately not even powering on with charger is the whole same issue = Crappy Sony battery ( programmed obsolescence )
Now it's happening again to me. Will NEVER buy a Sony product again in life.

Chonwey said:
It WILL fix it.
Sudden power off, Not powering on unless charger attached, missing signal/signal problems, ultimately not even powering on with charger is the whole same issue = Crappy Sony battery ( programmed obsolescence )
Now it's happening again to me. Will NEVER buy a Sony product again in life.
Click to expand...
Click to collapse
Hmmmm... That's very helpfull... Just got all the things that u listed up. But i still love sony?... And good things is i already search and learn how to change xperia zL battery.. Easy and simple. $26 for ori battery and $10 for back cover. LoL???
Sent from my C6502 using XDA Free mobile app

rayzaweirdooo said:
Hmmmm... That's very helpfull... Just got all the things that u listed up. But i still love sony... And good things is i already search and learn how to change xperia zL battery.. Easy and simple. $26 for ori battery and $10 for back cover. LoL
Sent from my C6502 using XDA Free mobile app
Click to expand...
Click to collapse
So you like being scammed, good for you
Ppl like you are the ones empowers companies to keep doing that scam.

ghost6022010 said:
My Xperia ZL just started doing this sudden shutoff thing but it seams to be getting worse, it's gotten so bad that when you boot up the phone it shows the SONY logo then immediately shuts off. When I plug it into the wall charger the LED lights up RED and then the SONY logo then reboot over and over(Bootloop). But yet i'm able to get it into fastboot and flashmode fine and can flash ftf through Flashtools with no problems i'm wondering if this could be a simple battery problem or if it's a software error. If anyone could help it would be greatly appreciated.
Click to expand...
Click to collapse
sir i'm also having exactly the same problem, now i wanted to know how you corrected this problem,
pls reply me if you see this post as i spend my so many day and night in correcting my phone but no luck.
wating for reply....
---------- Post added at 06:33 PM ---------- Previous post was at 06:29 PM ----------
ghost6022010 said:
My Xperia ZL just started doing this sudden shutoff thing but it seams to be getting worse, it's gotten so bad that when you boot up the phone it shows the SONY logo then immediately shuts off. When I plug it into the wall charger the LED lights up RED and then the SONY logo then reboot over and over(Bootloop). But yet i'm able to get it into fastboot and flashmode fine and can flash ftf through Flashtools with no problems i'm wondering if this could be a simple battery problem or if it's a software error. If anyone could help it would be greatly appreciated.
Click to expand...
Click to collapse
sir , i'm having exactly same problem as of yours, i spend so many days and night on my phone by reading forums and follow steps to correct my phone but till now no luck.
could you pls help me if you got the solution for your problem...
waiting for reply...

hard bricked my phone

Hey Guys, long time reader never posted. I think i may have hard bricked my brand new 5X. I am not new to flashing ROMs I have had great sucess with my old Nexus5 for year (now I have to revert to that phone for now)
I was running Cyanogenmod then decided to try Catalysm. All was wokring fine and then i decide to just reflash to stock. I downloaded the correct factory image went into terminal like usual (linux) executed sudo ./flash-all in the correct folder and it went through the process in about a second then the phone turned off and my terminal screen said waiting for device. After waiting a while i tried turning the phone on got nothing. unplugged the phone tried volume down and power all the regular stuff to make the phone turn on. Plugging it into the charger shows nothing and I cant get into the bootloader.
I have never had an issue like this before I cant figure out flashing stock image would brick my phone? Am i totally screwed with warannty?
Thanks for any help gusy.

Maybe a to simple question.
How long was it ago? Maybe it's stick stuck in the loop with the screen off and maybe you have to wait it out.

If the phone dropped dead they can't even get into it to void your warranty, which I doubt they would do anyway. Let the phone sit for a little bit with it plugged in just so you can relax for a few minutes. Just hold the power button until it turns on. If it won't turn on at all then contact Google for a replacement device.

brick
bobby janow said:
If the phone dropped dead they can't even get into it to void your warranty, which I doubt they would do anyway. Let the phone sit for a little bit with it plugged in just so you can relax for a few minutes. Just hold the power button until it turns on. If it won't turn on at all then contact Google for a replacement device.
Click to expand...
Click to collapse
This just happened about an hour or so ago. Well i was thinking the same thing with the phone looping and no screen but it doesnt feel warm like its on. Also adb devices doesnt list it as on although i would imagine boot looping it would not see the device. Ive tried letting it charge for about a half hour with no luck. should I try letting it sit over night on the charger or off the charger in case its looping and i need it to die eventually?
I just reflashed the stock firmware on my old nexus 5 with no issues, its working fine i did that to make sure it wasnt an error i made.

Interesting, did you check the md5?,
I've never had success with flashall.bat it never worked, I end up extracting the archive and read the commands in flashall.bat and do it manually, worked for me,
When connected to pc does the pc drivers come up and disconnect due to device unplugged?( not sure if it displays on linux

republicano said:
Interesting, did you check the md5?,
I've never had success with flashall.bat it never worked, I end up extracting the archive and read the commands in flashall.bat and do it manually, worked for me,
When connected to pc does the pc drivers come up and disconnect due to device unplugged?,
Click to expand...
Click to collapse
I just figured out what happened. I flashed the nexus 5 flash-all rather then the nexus 5x (wow really dumb mistake). I found the hammerhead folder in the nexus5x folder i flashed from.
Now what?

If you can't get the phone to turn on you're out of luck.

Hey had something simmilar that my phone blank and unresponsive. No turning off. But maybe battery gone empty? try to leave phone longer under changer like for 1-2h or so. ANd the red led should be on showing phone battery gone full empty.

thanks for the help
Czepek said:
Hey had something simmilar that my phone blank and unresponsive. No turning off. But maybe battery gone empty? try to leave phone longer under changer like for 1-2h or so. ANd the red led should be on showing phone battery gone full empty.
Click to expand...
Click to collapse
Yea I am going to leave it for a day to make sure if its boot looping it will shutdown, then I am going to charge it for a day and try to turn it on see where i end up.

kmsgli said:
Yea I am going to leave it for a day to make sure if its boot looping it will shutdown, then I am going to charge it for a day and try to turn it on see where i end up.
Click to expand...
Click to collapse
Also, holding the power button for a few minutes to see if it eventually boots

You need to read the flashall.bat and see what the first commands were, as I think the bootloader maybe the first
Sorry but I doubt it will come back to life, if it bricked at fastboot flash bootloader, then reboot and failed to turn on to flash the rest,
It may need jtag service or you need to find something similar to this post below
forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800

lsusb
republicano said:
You need to read the flashall.bat and see what the first commands were, as I think the bootloader maybe the first
Sorry but I doubt it will come back to life, if it bricked at fastboot flash bootloader, then reboot and failed to turn on to flash the rest,
It may need jtag service or you need to find something similar to this post below
forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
Click to expand...
Click to collapse
So with my phone plugged into my latop (linux) i run lsub with it plugged in and with it not plugged in and the differnce is this;
Bus 002 Device 031: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
my compuer is recognizing the device somehow but its the wrong name?

kmsgli said:
So with my phone plugged into my latop (linux) i run lsub with it plugged in and with it not plugged in and the differnce is this;
Bus 002 Device 031: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
my compuer is recognizing the device somehow but its the wrong name?
Click to expand...
Click to collapse
Sounds about right, that thread is for lg g2 and was just for display purpose, I not 100% sure if you can go through lg process on lg nexus,
Since the phone is also new I have not found any information on emmc fix.
You will have to go here and see if you can get help, but I think it will be some time till its released/leaked, you may have to pay to get it serviced.sorry about your Christmas present
forum.gsmhosting.com/vbb/f606/

Call Google and get it replaced. They are very good about that stuff.

kmsgli said:
I just figured out what happened. I flashed the nexus 5 flash-all rather then the nexus 5x (wow really dumb mistake). I found the hammerhead folder in the nexus5x folder i flashed from.
Now what?
Click to expand...
Click to collapse
Let Google know what happened, they're usually pretty good with that stuff and will probably let you RMA it. Google generally expects people to root their device, even though damaging the device while doing so is not technically covered under warranty they will probably help you out.
If 1 rep says no, call back and try another one. You can find countless examples online of people in your situation who Google helped out. Good luck!

Thanks guys
Thanks for all the help guys, I really apprecaite it, this site is really a great site full of people who want to help. ( im used to car forums where people call you an idiot any chance they get).
Ill post back if google did in fact help me out I will just wait for monday as I want to make sure if the phone is on for some reason with a weird screenless boot loop it has time to die and I can make sure I cant get it to boot myself.

Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.

kmsgli said:
Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.
Click to expand...
Click to collapse
So I guess that means it was so damaged even LG's equipment couldn't read any software/firmware details from the phone. Lucky for you. Just curious, what excuse did you give LG to make them think it wasn't caused by a software modification?

That's just it I was 100% honest and told them I accidentally flashed the nexus 5 image rather then the 5x image and bootloader was first on the flashall script. The girl who took the initial call didn't understand what I was saying so she typed exactly what I told her in the notes. I have to assume LG has a facotry cable that can flash the correct bootloader in seconds and the phone is back to new again.
really happy with LG service!!!!!

Nexus 5x shut off and won't turn on

If I posted this in the incorrect place or there is something related to my issue, I apologize in advance.
I've been searching here and all over the internet and no progress yet so I decided to make a new account here just to see if anyone can help me because I'm out of ideas right now.
This morning my Nexus 5x (Non-rooted Nougat) woke me up like every morning, after dismissing the alarm I left it on my bed and when I came back to grab it later I noticed it shut off.
Here are the facts and what I have tried so far:
- Battery level was almost full
- I tried to turn it on but nothing happened, not even the Google logo
- Connected it to power and no icons or any response at all
- Left it connected for like an hour and tried to get it into recovery mode
- I was able to get into fastboot mode a few times but after electing "start" or "recovery mode" the Google logo comes up and then shuts off again right after.
- Tried getting into recovery mode after leaving it charging for a while again but I couldn't even get into fastboot this time, no signs of life at all.
- Disconnected the battery for a few minutes and tried to get into fastboot mode again, this time it worked but same thing happened. (Google logo then shuts off)
- Tried connecting it to my PC but doesn't show up on Linux nor Windows, on Windows it makes the sound like I connected a peripheral but that's pretty much it.
- I have USB debugging enable but never accessed my stuff through usb connection because I have had this issue before where it is connected but it won't show up or it shows up but won't let me access the files even though the phone is unlocked.
At this point it just won't do anything and I ran out of ideas. I just want to at least recover some pictures and information I have in it that isn't backed up, if anyone can help me I would greatly appreciate it.
Thanks in advance

It sounds like you might have encountered the hardware bootloop issue. This is theorized to be caused by bad solder for the eMMC chip or bad eMMC chip. This was an acknowledge problem on a related model LG phone, but hasn't been acknowledged for N5x.
If you are under warranty, you should start the replacement process before it runs out.
If you want to try something that sounds crazy but has worked for some people, put the phone in the freezer for 15 minutes then see if it boots. If it does, quickly back up as much data as you can, then wipe the phone in preparation to RMA exchange.

Just boot to bootloader (fastboot) then unlock it and flash a factory image... u can find many guides to this operation on the XDA

sfhub said:
It sounds like you might have encountered the hardware bootloop issue. This is theorized to be caused by bad solder for the eMMC chip or bad eMMC chip. This was an acknowledge problem on a related model LG phone, but hasn't been acknowledged for N5x.
If you are under warranty, you should start the replacement process before it runs out.
If you want to try something that sounds crazy but has worked for some people, put the phone in the freezer for 15 minutes then see if it boots. If it does, quickly back up as much data as you can, then wipe the phone in preparation to RMA exchange.
Click to expand...
Click to collapse
At this point, I'm willing to try anything. Thanks

driss.sadok said:
Just boot to bootloader (fastboot) then unlock it and flash a factory image... u can find many guides to this operation on the XDA
Click to expand...
Click to collapse
If it's a hardware issue like sfhub suggested, I don't think this will fix it.

PennyScissors said:
If it's a hardware issue like sfhub suggested, I don't think this will fix it.
Click to expand...
Click to collapse
Same here... cannot enter recovery mode, so flashed new rom stock rom.
The flashing was fine but it didn't help.

guys if u can get to the bootloader, sure it can be fixed.. everything is possible with the fastboot, u can fix any issue. if it's a hardware issue the bootloader wouldn't work as well.

Re Nexus 5X won't turn on - I've had same issue
PennyScissors said:
This morning my Nexus 5x (Non-rooted Nougat) woke me up like every morning, after dismissing the alarm I left it on my bed and when I came back to grab it later I noticed it shut off.
Here are the facts and what I have tried so far:
- Battery level was almost full
- I tried to turn it on but nothing happened, not even the Google logo
- Connected it to power and no icons or any response at all
- Left it connected for like an hour and tried to get it into recovery mode
- I was able to get into fastboot mode a few times but after electing "start" or "recovery mode" the Google logo comes up and then shuts off again right after.
- Tried getting into recovery mode after leaving it charging for a while again but I couldn't even get into fastboot this time, no signs of life at all.
- Disconnected the battery for a few minutes and tried to get into fastboot mode again, this time it worked but same thing happened. (Google logo then shuts off)
- Tried connecting it to my PC but doesn't show up on Linux nor Windows, on Windows it makes the sound like I connected a peripheral but that's pretty much it.
- I have USB debugging enable but never accessed my stuff through usb connection because I have had this issue before where it is connected but it won't show up or it shows up but won't let me access the files even though the phone is unlocked.
At this point it just won't do anything and I ran out of ideas...
Click to expand...
Click to collapse
I've had the same problem with my 5X, except my alarm didn't even go off! I woke up 15 minutes late to see the boot screen "enter your pattern to start Android". I entered my pattern and it looked like it was going to boot up but when I went back to it it was blank. Tried again, got to the Google loading dots and it switched off again and I haven't been able to power it up since. No bootloader, nothing. Tried all the troubleshooting steps on the Nexus Google Support pages (I did post a link but because I'm new it won't show, so just Google "Nexus Support") and nothing worked. I also knew the battery was fully charged because it had been on charge overnight and when I did get to the 'enter your pattern' screen, the battery icon in the notification bar was full.
I requested a call back from Google and nothing happened so I tried the chat and they said it sounded like a hardware issue and are sending me a replacement device within the next 3-5 working days. Good that they're replacing it. Bad that it happened on a device less than a year old and they only offered £10 Play Store credit by way of compensation, when I've had to spend £15+ on a PAYG sim card to use in my old phone in the meantime because the nano sim in my 5X was too small and I've spent over an hour and half this afternoon wasting my time with troubleshooting and waiting for a call back... Not really the customer service I expected from Google for what appears to be a hardware issue. If you bought the phone from Google, my advice would be to get in touch with Google Support and they should replace it under warranty.

danielledowns01 said:
I've had the same problem with my 5X, except my alarm didn't even go off! I woke up 15 minutes late to see the boot screen "enter your pattern to start Android". I entered my pattern and it looked like it was going to boot up but when I went back to it it was blank. Tried again, got to the Google loading dots and it switched off again and I haven't been able to power it up since. No bootloader, nothing. Tried all the troubleshooting steps on the Nexus Google Support pages (I did post a link but because I'm new it won't show, so just Google "Nexus Support") and nothing worked. I also knew the battery was fully charged because it had been on charge overnight and when I did get to the 'enter your pattern' screen, the battery icon in the notification bar was full.
I requested a call back from Google and nothing happened so I tried the chat and they said it sounded like a hardware issue and are sending me a replacement device within the next 3-5 working days. Good that they're replacing it. Bad that it happened on a device less than a year old and they only offered £10 Play Store credit by way of compensation, when I've had to spend £15+ on a PAYG sim card to use in my old phone in the meantime because the nano sim in my 5X was too small and I've spent over an hour and half this afternoon wasting my time with troubleshooting and waiting for a call back... Not really the customer service I expected from Google for what appears to be a hardware issue. If you bought the phone from Google, my advice would be to get in touch with Google Support and they should replace it under warranty.
Click to expand...
Click to collapse
I contacted Google and they didn't help me at all because my warranty expired last month, they literally just told me to put in a repair request at the LG repair webpage....this sucks

My experience exactly...
My wife's Nexus 5 exhibited the exact same symptoms this morning. It's been running perfectly for 20 months and today it died, and we're unable to even get into the bootloader screen or power on the phone.
Taking your advice, we put it in the freezer for 15 minutes and were able to perform a factory reset wiping all data from the phone. We are going to take advantage of Google's Christmas 2017 promotion and return the Nexus 5X and buy a Moto 4X. They require you perform a factory reset before returning the phone in order to receive a credit for the returned Nexus 5. Thank you so much for the help!
Dennis
sfhub said:
It sounds like you might have encountered the hardware bootloop issue. This is theorized to be caused by bad solder for the eMMC chip or bad eMMC chip. This was an acknowledge problem on a related model LG phone, but hasn't been acknowledged for N5x.
If you are under warranty, you should start the replacement process before it runs out.
If you want to try something that sounds crazy but has worked for some people, put the phone in the freezer for 15 minutes then see if it boots. If it does, quickly back up as much data as you can, then wipe the phone in preparation to RMA exchange.
Click to expand...
Click to collapse

https://forum.xda-developers.com/nexus-5x/help/help-nexus-5x-lg-off-to-t3729739
I've just posted this thread overlooking yours. I think this is becoming another common issue. Has the freezer trick worked with anybody else?

I am having the same issue described here. My Nexus 5x went into a Bootloop about one month ago, but I was able to get it working again by going into Recovery Mode. About 4 days ago it went into a constant Bootloop, just showing the Google screen, and I couldnt get back in to recovery mode. I ordered a new phone on Tuesday (Pixel 2) and as long as I am able to do a factory reset I should get a $150 credit when I send this phone back. So, in desperation, I took a chance on the 15 minute freezer trick, and it worked! I was able to get into recovery mode (power + volume down, select Recovery Mode, little dude on his back came up, pushed power + volume up once) and cleared the cache and applied the factory reset. Ridiculous that this phone only lasted 18 months, but if I get the $150 credit I will be happy.

Same problem here -- just froze for a few seconds, powered off, and won't turn back on. Not a boot loop issue as there is no response at all from any buttons. Swapping the mainboard from a working phone powered up without a problem, but obviously that's the other phone's emmc.
I tried the freezer thing and it sort of worked- LCD powered on for a couple seconds, but then shut back off again and even that only happened once. That's progress over the usual absolutely no response though... Anyone have insight into why the temperature would matter? something is overheating that this gives a bit of wiggle room since it starts much colder than usual? maybe a more complex analog electronic situation?
I would happily pull the flash chip off and put it in a emmc reader, but I think I'm out of luck because from what I've read the dm-crypt key is generated from some data stored in in the processor's trust zone thing. I know the "password" but if that's only part of what makes the key and the rest isn't on the flash chip I suppose there's no point in going that route.
I don't care about the hardware surviving; mostly just looking to recover my data. Anyone have suggestions? Hardware debugging direction? I'm willing to buy some electronics test equipment (within reason of course; not picking up a 10000USD rework station for some old photos and contact list...)

d_ckhole said:
Same problem here -- just froze for a few seconds, powered off, and won't turn back on. Not a boot loop issue as there is no response at all from any buttons. Swapping the mainboard from a working phone powered up without a problem, but obviously that's the other phone's emmc.
I tried the freezer thing and it sort of worked- LCD powered on for a couple seconds, but then shut back off again and even that only happened once. That's progress over the usual absolutely no response though... Anyone have insight into why the temperature would matter? something is overheating that this gives a bit of wiggle room since it starts much colder than usual? maybe a more complex analog electronic situation?
I would happily pull the flash chip off and put it in a emmc reader, but I think I'm out of luck because from what I've read the dm-crypt key is generated from some data stored in in the processor's trust zone thing. I know the "password" but if that's only part of what makes the key and the rest isn't on the flash chip I suppose there's no point in going that route.
I don't care about the hardware surviving; mostly just looking to recover my data. Anyone have suggestions? Hardware debugging direction? I'm willing to buy some electronics test equipment (within reason of course; not picking up a 10000USD rework station for some old photos and contact list...)
Click to expand...
Click to collapse
The only way to connect that buddy to PC is to get SoC (CPU) working, so theoretically you can go towards reballing the chip. But I guess it's not an easy thing for such a little chip. Also u will need kinda plate for balls, i think there are no common ones, so u can make it yourself if have a technical education.
Another way is to connect memory right to PC without a phone but with some connector. IDK if there are any available, but this looks much more simple. I actually got the same happened, and tried to heat the plate, but with particular success.
IMHO

orcgoblinsupply said:
Another way is to connect memory right to PC without a phone but with some connector. IDK if there are any available, but this looks much more simple. I actually got the same happened, and tried to heat the plate, but with particular success.
IMHO
Click to expand...
Click to collapse
Here's the reader
https://www.amazon.com/ALLSOCKET-eMMC169-Programmer-Kingston-Interface/dp/B06Y55DKND/
But I assume the problem is I will not be able to generate the encryption key because part of it is in the processor.
If someone has tried this and it definitely works, I'll give it a go. Just don't want to buy the emmc reader and heat gun this chip off if it's certainly a waste of time.

d_ckhole said:
Here's the reader
https://www.amazon.com/ALLSOCKET-eMMC169-Programmer-Kingston-Interface/dp/B06Y55DKND/
But I assume the problem is I will not be able to generate the encryption key because part of it is in the processor.
If someone has tried this and it definitely works, I'll give it a go. Just don't want to buy the emmc reader and heat gun this chip off if it's certainly a waste of time.
Click to expand...
Click to collapse
I've seen a post of a guy who sent his motherboard to china and got reballed it and gained 4gb of ram. Can be wrong, but it was around $50 and a month of time.
---------- Post added at 04:46 PM ---------- Previous post was at 04:40 PM ----------
Actually found the post itself: https://4pda.ru/forum/index.php?showtopic=722679&st=3440#entry68093395 (it's in russian, so u're welcome at translate.google.com) In short - a guy fount a Chinese service and men in the middle who could resend his motherboard to china, it cost him $100

Random Shut Downs & Boot Loops

Hey guys, I hope someone can help me with my current conundrum.
As of late, my phone seems to randomly shut down and will end up boot looping and will continue to do so until I plug it in to charge. My most recent one was when it shut down at 51% percent and just boot looped. When it powered on after I plugged it in the charger, it had 10% battery life left.
Is there any way I can fix this situation? It happens on every ROM I flash along with the kernel.

caitsith810 said:
Hey guys, I hope someone can help me with my current conundrum.
As of late, my phone seems to randomly shut down and will end up boot looping and will continue to do so until I plug it in to charge. My most recent one was when it shut down at 51% percent and just boot looped. When it powered on after I plugged it in the charger, it had 10% battery life left.
Is there any way I can fix this situation? It happens on every ROM I flash along with the kernel.
Click to expand...
Click to collapse
I have exactly the same problem on a locked unrooted HTC 10. I thought first this was a battery problem (my battery is dead and lasts less than an hour) but I think this is related to the last update to 2.41.708.31. The shut down also affects certain apps : settings and login information seem to be wiped out by the shutdown.

Same problem here (stock/unrooted). Started to get problems shortly after the July security patch update.
Phone often crashes when battery falls below 40% - it then bootloops or won't switch on until charger is plugged in.
Tried the old trick of holding volume up and down + power button for a few minutes, in an attempt to reset the battery. The battery fell from 100% to 70%, charged it back up to 100% but still experiencing the same problems. A
Next step will be to try a factory reset but I suspect it'll do nothing to help.
Sent from my SM-N930F using Tapatalk

pnnorth said:
Same problem here (stock/unrooted). Started to get problems shortly after the July security patch update.
Phone often crashes when battery falls below 40% - it then bootloops or won't switch on until charger is plugged in.
Tried the old trick of holding volume up and down + power button for a few minutes, in an attempt to reset the battery. The battery fell from 100% to 70%, charged it back up to 100% but still experiencing the same problems. A
Next step will be to try a factory reset but I suspect it'll do nothing to help.
Sent from my SM-N930F using Tapatalk
Click to expand...
Click to collapse
If factory reset does not work, you could S-0ff the phone and take it back one or two RUU versions to a stable one.

pnnorth said:
Same problem here (stock/unrooted). Started to get problems shortly after the July security patch update.
Phone often crashes when battery falls below 40% - it then bootloops or won't switch on until charger is plugged in.
Tried the old trick of holding volume up and down + power button for a few minutes, in an attempt to reset the battery. The battery fell from 100% to 70%, charged it back up to 100% but still experiencing the same problems. A
Next step will be to try a factory reset but I suspect it'll do nothing to help.
Sent from my SM-N930F using Tapatalk
Click to expand...
Click to collapse
Same exact problem here.
Lately the battery life is awful, started to think that battery has deteriorated, however the phone suddenly boot loops and switches on only after plugged in, and same thing happens even in 30-40%. Battery percentage calibration seems WAY OFF lately.
Stock rom, latest official update
Sent from my HTC 10 using Tapatalk

Same issue here, I thought it was a defect in the charging circuit. Better stop my colleague now, before he tries to open my phone...
---------- Post added at 12:16 PM ---------- Previous post was at 12:05 PM ----------
Suddenly my phone is charging again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It was completely dead before.

I've had the same issue, battery running down in the space of 2-3 hours of light-moderate use, and bootlooping when attempting to power back on. I've found that if you go into recovery mode you can at least get it to boot up again without plugging into charger, but the last time I tried it my battery had said like 50% when the phone crashed and 15% when it booted again. I was starting to think maybe battery gone bad, too. Thinking about maybe going to a 3rd-party ROM to see if the behavior stays or if it gets any better.

Mine does the same. I tried wiping it and starting again - but given up on it and put it in drawer. Now using my wifes old S6.
Would like to know if this is hardware or software to see if it can be resurrected.

We have 2 HTC 10s at our house. Same issue. Sounds like software based on this thread.
GPS in Android auto is garbage now as well. This is all recent and it impacts both phones.
USA unlocked.
Sent from my HTC 10 using Tapatalk

I hope guys you can help me, I've the same problem, and I want to convert my HTC 10 (stock international version) to US unlocked, it been years since I modified any android phone (I destroyed my last one) and I'm afraid to do the same to my HTC 10, so if there is Noop step by step of how to do that I would be grateful.

US versions software is jacked. Would not recommend it right now.
Sent from my HTC 10 using Tapatalk

bglf83 said:
US versions software is jacked. Would not recommend it right now.
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
I call BS on this.
Tell me, what exactly is so "jacked" about it?
It's ahead of WWE with Google security updates. And I've always stayed up to date with US Unlocked firmware with no issues whatsoever.
EDIT: If you are basing this assumption on this thread:
post#2 is from someone with Hong Kong firmware
post#3 is from someone on GiffGaff which is in the UK and using the o2 network
post#4 is someone on Verizon, so probably Verizon firmware (although it could be US Unlocked)
post#5 is someone on Cosmote which is a Greek based carrier (and probably someone with the same WWE/European firmware as the person you replied to)
US Unlocked firmware is just fine, and it gets updated more frequently than WWE
---------- Post added at 06:16 PM ---------- Previous post was at 06:09 PM ----------
saw man said:
I hope guys you can help me, I've the same problem, and I want to convert my HTC 10 (stock international version) to US unlocked, it been years since I modified any android phone (I destroyed my last one) and I'm afraid to do the same to my HTC 10, so if there is Noop step by step of how to do that I would be grateful.
Click to expand...
Click to collapse
First things first, you need S-Off for this.
After you've gained S-Off, change your CID to BS_US001 (in download mode: fastboot oem writecid BS_US001)
Then change your MID to 2PS650000 (in download mode: fastboot oem writemid 2PS650000)
Then run the latest US Unlocked RUU which you can download from here.
Scroll down to the "Manual System Upgrade Instructions" on that link and read them. The RUU download is after the instructions.

I am full stock on 2 phones with random reboots. It's jacked.
Battery only gets 1 hour of screen on time ate this point
Sent from my HTC 10 using Tapatalk

bglf83 said:
I am full stock on 2 phones with random reboots. It's jacked.
Battery only gets 1 hour of screen on time ate this point
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Okay, but have you tried other firmwares; like WWE for instance; to see if there is a difference? If not, than you have nothing to base the claim not to use US Unlocked because it is "jacked", as you put it. And if you have, you should have provided the info on the best firmware to use.
Just sayin........
I have no random reboots, and I have no battery drain. I'm on US Unlocked. No issues ever with it. Always flashed the latest firmware as soon as it came out.
I would assume that this issue isn't firmware based, but is because of some other issue.

Here's my battery stats. They'd be better, but I often stream music over BT at work. No issues.

xunholyx said:
View attachment 4327059
Here's my battery stats. They'd be better, but I often stream music over BT at work. No issues.
Click to expand...
Click to collapse
My average SOT was well over 4 hrs when new. Yours is average 3.
I have 2 fully stock phones. I should not have to mod them to make them work. Prior to September patches, both phones were stable.
Sent from my HTC 10 using Tapatalk

knochnkopf said:
I've had the same issue, battery running down in the space of 2-3 hours of light-moderate use, and bootlooping when attempting to power back on. I've found that if you go into recovery mode you can at least get it to boot up again without plugging into charger, but the last time I tried it my battery had said like 50% when the phone crashed and 15% when it booted again. I was starting to think maybe battery gone bad, too. Thinking about maybe going to a 3rd-party ROM to see if the behavior stays or if it gets any better.
Click to expand...
Click to collapse
Did rooting and installing a ROM (Viper10 ect) Work?,
I've had the same problem as everybody else with the random bootlooping (Stock WWE (UK) 2.41.401.41).
We really shouldn't have to root our phones to fix a problem HTC made with their Nougat update.

6thEnvy said:
Did rooting and installing a ROM (Viper10 ect) Work?,
I've had the same problem as everybody else with the random bootlooping (Stock WWE (UK) 2.41.401.41).
We really shouldn't have to root our phones to fix a problem HTC made with their Nougat update.
Click to expand...
Click to collapse
I haven't had a chance to put a different ROM on my phone yet but I've also started having issues with Bluetooth connecting but then within a couple seconds the device reverts back to playing audio from the phone speakers and the volume controls don't show that i'm connected to bluetooth audio, even though I've tried 2 different bluetooth speakers. Seriously considering installing PureFusion again this weekend.

I have the same issue with the lastest Tmobile US firmware/software, mine goes into a bootloop around the 40% mark. I've just experienced similar behavior on a Samsung Tablet, I replaced the battery in it and all was well again.

fmedrano1977 said:
I have the same issue with the lastest Tmobile US firmware/software, mine goes into a bootloop around the 40% mark. I've just experienced similar behavior on a Samsung Tablet, I replaced the battery in it and all was well again.
Click to expand...
Click to collapse
I agree with you. Some of the batteries that got put into the 10 probably snuck through quality control from whoever manufactures them.
---------- Post added at 09:54 AM ---------- Previous post was at 09:50 AM ----------
Have any of you tried resetting your battery sensor and calibrating your battery?
Instructions are in this thread after UPDATE in the OP: https://forum.xda-developers.com/htc-10/help/whats-current-battery-capacity-t3538773