[Nexus 5X Q&A, Help & Troubleshooting] ptruman:
Just chiming in.

I had a 5X which keeled over under bootloop - but luckily I had my files. Google replaced it. Just before Pixel 3 came out, the replacement died too, with bootloop - and I managed to get the restricted core image onto it, but that stopped the fingerprint and NFC reader working.

The other surviving 5X in the house (from Xmas 2015) died 2 days ago - and it died suddenly (in hand, being used) and went to black screen.

It was squawking 8003 mode on USB, but no other response (lights/screen etc) and here is what we managed to do...

1) Let the phone go entirely flat overnight. This prompted the red LED to start flashing when power was pressed.

2) Plugged phone into computer USB, started charging. Hit power, and (briefly) got the Google splash screen and about 2 seconds of bootanim, before lockup, then back to black (no bootloop)

3) Let phone go flat again (didn't take long) - back to red LED on power press

4) Start charging the phone - this got rapid flashing red LED, and then eventually the battery charge animation

5) Wait till phone was full, disconnect power

6) Stick phone in freezer (-17C) for 5-10 mins

7) Plug phone into PC (cable out of freezer door) whilst holding the power and up keys - this got us LG download mode, ONCE.

8) Hold power button on phone for 10 seconds to trigger a shutdown, then immediately switch to holding vol down (with power) - this got the Android screen mode

9) Select recovery mode with vol keys, hit power

10) At recovery mode, hold power and press vol + to get the fastboot menu

11) Select "Mount /system" with the vol keys and hit power.

12) Select "Reboot" with the vol keys and hit power

13) Phone started booting but bootlooped

14) Transfer phone to electric oven set at 80 - cable still out of door

15) Wait a bit - phone will progress along boot (and loop) till it eventually starts - entering your code/key/pin is "fun" with hot glass

16) Wait till phone shuts itself down (thermal protection mode) - remove phone from oven

17) Start phone with power key again (it will be hot!)

18) Phone SHOULD start - unlock it and put USB to file transfer mode

19) Download everything you can, as fast as it will allow (we pulled 812 files off successfully)

20) Once everything is down, attempt reboot - it will probably lock again

Since then we are back to stage 1/2 - I have acquired the firehose file from Aryk's archive (paid the $4.44) but it does NOT have a patch0.xml. I have built one from the 5X 32GB TOT file I found, and it does talk to Sahara, but ultimately I'm getting:

2019-01-13 09:54:57.211 Binary build date: Nov 21 2017 @ 02:53:37
2019-01-13 09:54:57.212 QSAHARASERVER CALLED LIKE THIS: 'E:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\User\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2019-01-13 09:54:57.213 Sahara mappings:
2019-01-13 09:54:57.213 2: amss.mbn
2019-01-13 09:54:57.214 6: apps.mbn
2019-01-13 09:54:57.214 8: dsp1.mbn
2019-01-13 09:54:57.215 10: dbl.mbn
2019-01-13 09:54:57.215 11: osbl.mbn
2019-01-13 09:54:57.216 12: dsp2.mbn
2019-01-13 09:54:57.216 16: efs1.mbn
2019-01-13 09:54:57.217 17: efs2.mbn
2019-01-13 09:54:57.217 20: efs3.mbn
2019-01-13 09:54:57.218 21: sbl1.mbn
2019-01-13 09:54:57.218 22: sbl2.mbn
2019-01-13 09:54:57.218 23: rpm.mbn
2019-01-13 09:54:57.219 25: tz.mbn
2019-01-13 09:54:57.219 28: dsp3.mbn
2019-01-13 09:54:57.220 29: acdb.mbn
2019-01-13 09:54:57.220 30: wdt.mbn
2019-01-13 09:54:57.220 31: mba.mbn
2019-01-13 09:54:57.221 13: C:\temp\LG\Nexus-5X-32_gb\prog_emmc_firehose_8992_lite.mbn
2019-01-13 09:54:57.221
2019-01-13 09:54:57.222 09:54:56: Requested ID 13, file: "C:\temp\LG\Nexus-5X-32_gb\prog_emmc_firehose_8992_lite.mbn"
2019-01-13 09:54:57.222
2019-01-13 09:54:57.223 09:54:57: 273568 bytes transferred in 0.329000 seconds (0.7930MBps)
2019-01-13 09:54:57.223
2019-01-13 09:54:57.223
2019-01-13 09:54:57.224
2019-01-13 09:54:57.224 09:54:57: File transferred successfully
2019-01-13 09:54:57.225
2019-01-13 09:54:57.225
2019-01-13 09:54:57.225 NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
2019-01-13 09:54:57.226
2019-01-13 09:54:57.226
2019-01-13 09:54:57.227 09:54:57: Sahara protocol completed
2019-01-13 09:54:57.254 Sending Programmer Finished
2019-01-13 09:54:57.254 Switch To FireHose
2019-01-13 09:54:57.255 Wait for 3 seconds...
2019-01-13 09:55:00.256 Max Payload Size to Target:49152 Bytes
2019-01-13 09:55:00.257 Device Type:emmc
2019-01-13 09:55:00.257 Platform:8x26
2019-01-13 09:55:00.257 Disable Ack Raw Data Every N Packets
2019-01-13 09:55:00.258 Skip Write:False
2019-01-13 09:55:00.258 Always Validate:False
2019-01-13 09:55:00.259 Use Verbose:False
2019-01-13 09:55:00.260 Start Get Flash Infomation
2019-01-13 09:55:00.262 ***** Working Folder:C:\Users\User\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2019-01-13 09:57:58.028
2019-01-13 09:57:58.029 Base Version: 17.11.16.14.34
2019-01-13 09:57:58.030 Binary build date: Nov 21 2017 @ 02:53:33
2019-01-13 09:57:58.032 Incremental Build version: 17.11.21.02.53.33
2019-01-13 09:57:58.033
2019-01-13 09:57:58.034 09:55:00: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
2019-01-13 09:57:58.035 ************************************************
2019-01-13 09:57:58.035 E:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM3 --getstorageinfo=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
2019-01-13 09:57:58.037 ************************************************
2019-01-13 09:57:58.037
2019-01-13 09:57:58.038 09:55:00: INFO: Current working dir (cwd): C:\Users\User\AppData\Roaming\Qualcomm\QFIL\COMPORT_3\
2019-01-13 09:57:58.038 09:55:00: INFO: Showing network mappings to allow debugging
2019-01-13 09:57:58.039 09:55:00: INFO: User wants to talk to port '\\.\COM3'
2019-01-13 09:57:58.040
2019-01-13 09:57:58.041
2019-01-13 09:57:58.041	_____
2019-01-13 09:57:58.042	| ___|
2019-01-13 09:57:58.042	| |__ _ __ _ __ ___ _ __
2019-01-13 09:57:58.043	| __| '__| '__/ _ \| '__|
2019-01-13 09:57:58.043	| |__| | | | | (_) | |
2019-01-13 09:57:58.044	\____/_| |_| \___/|_|
2019-01-13 09:57:58.044
2019-01-13 09:57:58.044
2019-01-13 09:57:58.045 09:57:58: {ERROR: It took 177.23400000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable}

My first two dead 5Xs would bootloop, indicating a core separation issue. This one appears to be more of an eMMC separation fault - Sahara cannot talk to the memory, at all. All we have is the Qualcomm microcode running on the port. With a chilled/heated phone, the eMMC is accessible, but recovering the handset isn't going to work long term, as it will separate again when it settles to ambient temperature.

Hopefully the above assists someone getting their data off.

I've included the partition.xml, rawProgram0.xml and patch0.xml files built using GPTAnalyzer.py and GPTParser.py - these may (or may well not) help you!

View attachment 4685592

View attachment 4685593

View attachment 4685594