Develop Bugs

i747 Hard Bricked: QHSUSB - DLOAD : Needing a debrick.img

SGH-I747 (4.1.2 i747's please)/ SGH-i747m( If you have a official 4.3 i747m, please post a debrick.img) only:
Hi, I recently hard bricked my phone into QHSUSB DLOAD and I am going to attempt repairing it through the SD Card boot method.
http://forum.xda-developers.com/editpost.php?do=editpost&p=47431259
I need a debrick.img to flash to the SD card in a Linux OS.
I would have gotten it myself but my phone is obviously dead. I found one before on XDA, but it did not work on my device and it gave me an error in the Linux terminal when it should not have.
-snip-
The end of the 3rd boot-loader stage in mmcblk0 is at 77.3 megabytes. If you are going to help out using your device, try to refrain from uploading an image with a different ROM other than root.
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.img bs=2m count=81054925
The count is the amount of bytes. I am not sure if it is meant to be 1000 bytes=kilobyte or 1024 bytes=kilobyte. The count above is for 1024.
I need someone to install the Galaxy S III unified toolkit, and pull the first 7 partitions from mmcblk0 ,which is where the third bootloader stage ends.(Don't upload a heavily modified device please) http://www.skipsoft.net/?page_id=213 Once you get the files, PM me.
If anyone has a link to a working one, please post that. If you want to get your own image to help me, go ahead.
Thanks guys.

Sorry for the bump... I just need the device running again since the state it's in, it CAN be unbricked.

99ytrewq9111 said:
Sorry for the bump... I just need the device running again since the state it's in, it CAN be unbricked.
Click to expand...
Click to collapse
what happened?

winosxbuntu said:
what happened?
Click to expand...
Click to collapse
I tried to unlock what I thought was a locked bootloader(I could only enter bootloader through ADB)
I found an article that says ezunlock works on all S III's.
It corrupted my bootloader,and my phone gives off no signs of life except "Device QHSUSB-DLOAD not recognized" when plugged in.
This means the motherboard/processor wasn't able to boot from the hard disk, so then it tries the SDcard if it matches the phone close enough.
I need someone to use their rooted i747 to dump the first 77.3 megabytes of "mmcblk0". That contains the firmware and bootloaders. With that, i can burn it to an sdcard in a linux operating system and plug it into my phone.

99ytrewq9111 said:
Sorry for the bump... I just need the device running again since the state it's in, it CAN be unbricked.
Click to expand...
Click to collapse
99ytrewq9111 said:
I tried to unlock what I thought was a locked bootloader(I could only enter bootloader through ADB)
I found an article that says ezunlock works on all S III's.
It corrupted my bootloader,and my phone gives off no signs of life except "Device QHSUSB-DLOAD not recognized" when plugged in.
This means the motherboard/processor wasn't able to boot from the hard disk, so then it tries the SDcard if it matches the phone close enough.
I need someone to use their rooted i747 to dump the first 77.3 megabytes of "mmcblk0". That contains the firmware and bootloaders. With that, i can burn it to an sdcard in a linux operating system and plug it into my phone.
Click to expand...
Click to collapse
find a download link for this http://forum.xda-developers.com/showthread.php?t=1746665 (samsung galaxy s3 toolkit) which can help you fix your phone
if that does not help take it to mobiletechvideos.com and they will fix it for you REASONABLE PRICE
its XDA you will get the help you deserve PLUS i have never encounted that kind of problem HOPE TO GOD IDONT but again am sure an SD-CARD that can write firmware/system IS VALUABLE/USEFULL compared to nothing and that means there is hope left to fix bad code :laugh:

winosxbuntu said:
find a download link for this http://forum.xda-developers.com/showthread.php?t=1746665 (samsung galaxy s3 toolkit) which can help you fix your phone
if that does not help take it to mobiletechvideos.com and they will fix it for you REASONABLE PRICE
its XDA you will get the help you deserve PLUS i have never encounted that kind of problem HOPE TO GOD IDONT but again am sure an SD-CARD that can write firmware/system IS VALUABLE/USEFULL compared to nothing and that means there is hope left to fix bad code :laugh:
Click to expand...
Click to collapse
Thanks for that link! It looks very promising, and I can probably find a stock boot.IMG in there. I will work on tomorrow. If I succeed, I'll edit the OP and make a debrick guide for this drvice forum. A word of advice, try not to mess with your bootloader or you end up like me

winosxbuntu said:
find a download link for this http://forum.xda-developers.com/showthread.php?t=1746665 (samsung galaxy s3 toolkit) which can help you fix your phone
if that does not help take it to mobiletechvideos.com and they will fix it for you REASONABLE PRICE
its XDA you will get the help you deserve PLUS i have never encounted that kind of problem HOPE TO GOD IDONT but again am sure an SD-CARD that can write firmware/system IS VALUABLE/USEFULL compared to nothing and that means there is hope left to fix bad code :laugh:
Click to expand...
Click to collapse
Hi, the toolkit didn't fix my phone, but its defiantly a step up. Since I'm assuming you have the toolkit installed that you suggested it, could you do me a favor?
It will be a bit easier using the toolkit to extract the partition files. If you could pull the first 7 partitions from "mmcblk0" of your device through the toolkit, it will probably set the next step to fix my phone. (Assuming you have a 16g i747... I don't really know)
You don't have to do this of course.
Thanks man.

Bump. Can anyone help out? All I need is the first 7 partitions.
Sent from my GT-I9300 using xda app-developers app

99ytrewq9111 said:
Bump. Can anyone help out? All I need is the first 7 partitions.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
either try using this link http://forum.xda-developers.com/showpost.php?p=27239761 am pretty sure it works for all S3 models, either way on the I747 forum it has been removed, the download link does not work........ so use this
it will work, it may not work but for the time being use this toolkit and also search forums or Google on how to fix this without, i think i found some answers after i had an emmc brick with my S2 but i did not have an SD card to re-write firmware to work again on my phone so i bought the S3 and its awesome

winosxbuntu said:
either try using this link http://forum.xda-developers.com/showpost.php?p=27239761 am pretty sure it works for all S3 models, either way on the I747 forum it has been removed, the download link does not work........ so use this
it will work, it may not work but for the time being use this toolkit and also search forums or Google on how to fix this without, i think i found some answers after i had an emmc brick with my S2 but i did not have an SD card to re-write firmware to work again on my phone so i bought the S3 and its awesome
Click to expand...
Click to collapse
The problem is I need a working phone to pull the partitions. :/ I tried to use the boot image, but it had an error writing while in the linux.

99ytrewq9111 said:
The problem is I need a working phone to pull the partitions. :/ I tried to use the boot image, but it had an error writing while in the linux.
Click to expand...
Click to collapse
This one worked for me http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172

I have a similar problem Hard Bricked after update to 4.3 tried to flash my phone Backup 4.1.2 and died can not log in or recovery nor danlold.Is there any solution.

Bradkirk said:
This one worked for me http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172
Click to expand...
Click to collapse
Did you use an i747 or a i747m device?
If a i747m image works on an i747, it will basically fix all of my problems.

spensa said:
I have a similar problem Hard Bricked after update to 4.3 tried to flash my phone Backup 4.1.2 and died can not log in or recovery nor danlold.Is there any solution.
Click to expand...
Click to collapse
What message appears on your computer when you plug it in?
If it says QHSUSB-DLOAD, you are in faint light.
It stands for Qualcomm High Speed USD Download Mode.
What is means that your processor(qualcomm), is trying to boot, but it cannot find proper drivers for the hardware.
It will then look for something to boot from in the SDcard.
Here is a thread on how some other people were able to do it : http://forum.xda-developers.com/showthread.php?t=2439367

I have an I747M technically. I went for an actual I747M image just in case there was a slight difference. in the thread that one came from though there should be one for the actual att device if you look through it.
and just to confirm, yes the phone was blank and unresponsive. showing up as QHSUSB-DLOAD before i loaded that img onto my external SDcard. and I am using the same phone currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Bradkirk said:
I have an I747M technically. I went for an actual I747M image just in case there was a slight difference. in the thread that one came from though there should be one for the actual att device if you look through it.
and just to confirm, yes the phone was blank and unresponsive. showing up as QHSUSB-DLOAD before i loaded that img onto my external SDcard. and I am using the same phone currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately that's the download I found that didn't work.
Thanks for trying though

damn! the only other help I can offer then, is that there is a pretty good thread on this over in the d2tmo section. someone there wrote a little tool to easily download the relevant data. might help you on your quest. or at least make it so you could ask someone that doesnt know ADB. best of luck!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

99ytrewq9111 said:
What message appears on your computer when you plug it in?
If it says QHSUSB-DLOAD, you are in faint light.
It stands for Qualcomm High Speed USD Download Mode.
What is means that your processor(qualcomm), is trying to boot, but it cannot find proper drivers for the hardware.
It will then look for something to boot from in the SDcard.
Here is a thread on how some other people were able to do it : http://forum.xda-developers.com/showthread.php?t=2439367
Click to expand...
Click to collapse
when connected to the computer written QHSUSB-DLOAD,

spensa said:
when connected to the computer written QHSUSB-DLOAD,
Click to expand...
Click to collapse
OK , take out your battery and tell me your model number(Behind battery). And what phone company do you use?
Did you possibly save a NANDROID on a computer?
( if you have i747m, you can fix your phone, but its hard to do( I havnt done it yet)
Download this image http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172 (thanks to @Bradkirk )
Follow these directions using that image above^^^ http://forum.xda-developers.com/showthread.php?t=2439367
You need to install a Linux operating system (Ubuntu works) to run the commands.
Edit:! According to the T-Mobile thread, you might need a debrick.IMG from a phone on 4.3
Once I know your phones model number, I can edit the main post and ask for you phone model's images.

99ytrewq9111 said:
OK , take out your battery and tell me your model number(Behind battery). And what phone company do you use?
Did you possibly save a NANDROID on a computer?
( if you have i747m, you can fix your phone, but its hard to do( I havnt done it yet)
Download this image http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172 (thanks to @Bradkirk )
Follow these directions using that image above^^^ http://forum.xda-developers.com/showthread.php?t=2439367
You need to install a Linux operating system (Ubuntu works) to run the commands.
Edit:! According to the T-Mobile thread, you might need a debrick.IMG from a phone on 4.3
Once I know your phones model number, I can edit the main post and ask for you phone model's images.
Click to expand...
Click to collapse
I took it to a service to repair

[Q] Nexus 7 k008 brick

Hi.
Unfortunately bricked my nexus 7 K008,
I am able to go to fast boot but then when I try to load recover the tab gets stuck on Google logo.. This brick happend during update to new firmware.
I have tried the 1 key tool to try to restore to any kind of ROM but the device doesn't show up.
please point me in the right direction. As I have tried many different searches but all pointing to the one click tool which will only work if I can get my tab to turn on.
All help is appreciated.

https://developers.google.com/android/nexus/images

You did not brick your nexus 7. Flash the factory image with fastboot. Do not use toolkits.

_MetalHead_ said:
You did not brick your nexus 7. Flash the factory image with fastboot. Do not use toolkits.
Click to expand...
Click to collapse
thanks for all your reply and the link, unfortunately i cannot find a compilled version of the nexus7 fastboot tool in the android opensource project site, kindly also need help there... sorry very new to this.
thanks

gangooparsad said:
thanks for all your reply and the link, unfortunately i cannot find a compilled version of the nexus7 fastboot tool in the android opensource project site, kindly also need help there... sorry very new to this.
thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2588979

gangooparsad said:
thanks for all your reply and the link, unfortunately i cannot find a compilled version of the nexus7 fastboot tool in the android opensource project site, kindly also need help there... sorry very new to this.
thanks
Click to expand...
Click to collapse
There is no nexus 7 version, fastboot is fastboot. Motorola has a modified version (xda'ers call it mfastboot) that alters file size restrictions but even that one works with all devices. All that said, the link that khaytasus posted ^ has what you need.
Sent from my iPhone 6 using Tapatalk

I think I bricked my girls D851

Hey guys, long story short I can't use LG Flash Tool, or Odin as it won't even pick it up. All that happens when I press power is that it goes right to TWRP and I can't even restore a backup because it says the partitions don't exist. What should I do??? Thanks
Someone PLEASE HELP ME!!!
Eric

I had the same issue on my n7. Took me a week to fix. Had to end up restoring stock image. Then start from scratch and reroot.
Sent from my LG-D851 using Tapatalk

The Apostle said:
I had the same issue on my n7. Took me a week to fix. Had to end up restoring stock image. Then start from scratch and reroot.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Can you elaborate on how to do it exactly please?

The process will be different depending on your device. You need to get the stock image for your particular variant of the G3 and flash it.
Google either "unbrick LG G3" or "flash LG G3 stock image" or "TWRP, partition does not exist LG G3".
The process I used on the N7 will be different than the one on this device. I actually had to use ADB and CMD command prompts for the N7.
ADB is Android Debugging Bridge. You may need to Google that as well and watch some YouTube videos. Some if them can be very helpful.

The Apostle said:
The process will be different depending on your device. You need to get the stock image for your particular variant of the G3 and flash it.
Google either "unbrick LG G3" or "flash LG G3 stock image" or "TWRP, partition does not exist LG G3".
The process I used on the N7 will be different than the one on this device. I actually had to use ADB and CMD command prompts for the N7.
ADB is Android Debugging Bridge. You may need to Google that as well and watch some YouTube videos. Some if them can be very helpful.
Click to expand...
Click to collapse
Thanks bro but its all good now thanks to @1619415. He went wayyyy out of his way to help me get this resolved.

djerick3 said:
Thanks bro but its all good now thanks to @1619415. He went wayyyy out of his way to help me get this resolved.
Click to expand...
Click to collapse
NP, bro glad I could help also thanks for the shout out

^^^^ proof XDA isn't full of aye holios. LOL.

Constructing 16gb TOT file

Hey all,
I recently did the misfortune of flashing a nexus 5 bootloader on my nexus 5x -- right before I was going to send it in after getting my replacement for a cracked screen no less.
I found a thread here talking about how to recover it but it only hosts the applicable TOT file for a 32 gb device.
Is there any knowledge or documentation on creating that TOT file myself? I have a fully functioning 16 gig 5x that was sent to replace the (now) bricked one.
Thanks in advance!

Have you tried just flashing the 32 gig TOT to see if you can get the bootloader back? Its worth a try. The phone cant get any deader.

PiousInquisitor said:
Have you tried just flashing the 32 gig TOT to see if you can get the bootloader back? Its worth a try. The phone cant get any deader.
Click to expand...
Click to collapse
I'd like that as a last resort -- I'm just not versed enough in this kind of restore process to say whether or not that would make things worse.
Has that kind of thing been attempted before?

Don't flash a 32GB TOT on a 16GB phone. It will ease all software and leave the phone in firmware update mode. My phone is stuck in firmware update and needs a 16GB TOT. Hope somebody post one soon.

Eldgrim070 said:
Don't flash a 32GB TOT on a 16GB phone. It will ease all software and leave the phone in firmware update mode. My phone is stuck in firmware update and needs a 16GB TOT. Hope somebody post one soon.
Click to expand...
Click to collapse
You flashed the 32GB TOT? While the wrong TOT may screw with the partition sizes, it may fix the bootloader and stock recovery. So, have you tried to enter fastboot mode or recovery since doing it? Let us know what you find.
Also, will you please post a picture of the firmware update screen?
Here is a case of the 32 GB TOT working on a 16 GB 5X. Note you need to flash the full N OTA to fix the borked partitioning. Note the useful info starts on page 4 post 37.
http://forum.xda-developers.com/nexus-5x/help/device-locked-t3355549/page4

The USB port on a laptop matters. Using the USB 3 port would make my Nexus 5x reboot half through flashing. Using the USB 2 port, I successful flashed the device. Everything is good now.

Eldgrim070 said:
The USB port on a laptop matters. Using the USB 3 port would make my Nexus 5x reboot half through flashing. Using the USB 2 port, I successful flashed the device. Everything is good now.
Click to expand...
Click to collapse
So did you flash the 32gb tot to a 16gb phone?
Sent from my SM-G930V using Tapatalk

Eldgrim070 said:
Don't flash a 32GB TOT on a 16GB phone. It will ease all software and leave the phone in firmware update mode. My phone is stuck in firmware update and needs a 16GB TOT. Hope somebody post one soon.
Click to expand...
Click to collapse
Did you find the solution? I'm in the same problem

Same here... any news?

johnrovich said:
Same here... any news?
Click to expand...
Click to collapse
Just flash the 32GB tot file then flash an Android N beta OTA (probably would work for FULL non-beta OTA as well)
The 32GB tot file includes
PrimaryGPT
modem
boot
recovery
system
BackupGPT
The only things that are specific to the 32GB model ore the PrimaryGPT and BackupGPT, which are the GUID partition tables.
It won't ruin your phone to have the wrong partition tables since it basically only affects the user partition.
Once you install the Android N beta OTA update.zip it will fix up the GPT tables for you.
Please also notice the above is not a typo, the 32GB TOT file is *missing* the vendor partition, so I would advise flashing a full build of something after flashing the TOT file to get things working.
Also if you are just looking at flashing the TOT file because you trashed your EFS partition due to TWRP restore bug, do *NOT* flash the the TOT file. It will just make your life more difficult because it will lock your bootloader and then the real fix of restoring old EFS backup or writting zeros to EFS partition becomes more difficult.

Nexus 5x stuck at google screen [Potentially Hard-bricked]

*** The issue is resolved!!! Thanks to xda, the solution is provided in the link in the comments.***
Couple of days ago I got this OTA notification that Android 7.1 preview is available for update. As my phone is rooted I started the manual update procedure. After the flashing was finished, I restarted the phone and then I saw it was stuck at the Google screen. Just stuck, no response. Seemed unusual to me.
Let me tell you that I have been modding my Nexus 5 for about two years. I am familiar with most of the tweaks that can be done to a Nexus device. Nexus 5 served me amazingly. I bought Nexus 5x 3 months ago.
So, after it was stuck I restarted. Still stuck. I will tell you step by step what I did then:
1. Flashed the OS 7.1 again (I dunno why, the flash.all script doesn't work for me, so I always do that manually) - result is the same.
2. Last October update (NBD90W) was available in the folder so I flashed that - same result.
3. I downloaded the previous one (NRD90S) and flashed that - same result.
4. I locked the phone and unlocked again to erase everything (not sure if that's a good idea), then flashed the OS again - same result.
5. Then I tried LGUP and the tot files to give it the factory version. LGUP detects the phone, started installing. When the installation is finished and the phone restarted - same result.
6. Now that I gave it the factory version the phone got locked!
7. I searched google for hours but couldn't find a way to unlock it as the OS is not booting and I cannot turn USB debugging on!
8. Then I tried the default recovery mode (Android recovery, from the recovery screen Power + volume up) as it doesn't require unlocking the device. Wiped the cache and restarted - same result.
9. My phone is detected by the pc and ADB. So, I wiped everything and tried ADB sideload and get this error E: footer is wrong
10. I tried Nexus root toolkit. It detects the phone in fastboot mode, then restarts it and then it again is stuck on the Google screen.
I am extremely depressed!
I am from Bangladesh and there is no authorized LG servicing center here. So, I can't ask for their help.
All that I did over the past two years was the awesome threads of xdadevelopers. So, a big thumbs up for you guys . :good:
I learnt from the web that phone can be hard bricked if a wrong bootloader is flashed. That's impossible for me as I always remove the factory image extracted files after flashing is done from the ADB>platform-tools folder.
Now, is the phone hard-bricked? If it is, what to do with it? Will replacing the motherboard get my phone back? Any kind of suggestion will be very much appreciated.

Bummer. This sounds a lot like what I just posted here: http://forum.xda-developers.com/nexus-5x/help/req-help-bootloop-7-1-1-beta-ota-enter-t3486957
I really hope someone has an idea how to fix this...

Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766

what is your model H790 or H791
16 or 32 GB?

DC_Knight said:
Bummer. This sounds a lot like what I just posted here: http://forum.xda-developers.com/nexus-5x/help/req-help-bootloop-7-1-1-beta-ota-enter-t3486957
I really hope someone has an idea how to fix this...
Click to expand...
Click to collapse
Well, I don't get bootloops, my phone is just stuck at the Google screen and I can enter recovery mode (lying Android with red exclamation mark), from there I can enter Android recovery mode, where ADB sideload is available.
harihacker said:
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
Click to expand...
Click to collapse
Like I mentioned in point 5, I did exactly that as mentioned in this link.
Duckscreen said:
what is your model H790 or H791
16 or 32 GB?
Click to expand...
Click to collapse
It's H791, 32 GB.

There is no more reply
I need to know one thing. Will replacing the motherboard fix the phone? Anyone??

jadu45 said:
There is no more reply
I need to know one thing. Will replacing the motherboard fix the phone? Anyone??
Click to expand...
Click to collapse
How about trying to get a replacement if you're still within the 1 year warranty?
Sent from my Nexus 5X using Tapatalk

EeZeEpEe said:
How about trying to get a replacement if you're still within the 1 year warranty?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
"I am from Bangladesh and there is no authorized LG dealer/servicing center here. So, I can't ask for their help."
I'm on my own...

jadu45 said:
"I am from Bangladesh and there is no authorized LG dealer/servicing center here. So, I can't ask for their help."
I'm on my own...
Click to expand...
Click to collapse
Ah my bad. TL;DR on my end.
Sent from my Nexus 5X using Tapatalk

Please say something about replacing the motherboard. It's very very pricey, so I want to be sure -_-

sounds like its hardware problem, contact seller to replace it. if not going to happen, then buy a new phone from a company that does have a dealer in your country to warrant. aside of camera, the specs of other phones at this price range are better

That thought is also roaming around my head, still Nexus is Nexus!

What's the price going for the 5X over there? It's as low as $280 here in the US which is easy better then it's original.
Sent from my Nexus 5X using Tapatalk

Try the tutorial here. It's little bit different from the original thread ,
as @bardhi92 said, THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
Well, for my case, eventually I successfully bring my N5X alive. The tricky part is to enter Android System Recovery (hold Power + Volume Up) after flashing TOT.

questionquince said:
Try the tutorial here. It's little bit different from the original thread ,
as @bardhi92 said, THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
Well, for my case, eventually I successfully bring my N5X alive. The tricky part is to enter Android System Recovery (hold Power + Volume Up) after flashing TOT.
Click to expand...
Click to collapse
Thanks for this, it looks interesting and I definitely didn't try that. I'm at office right now, I'll let you know after trying this.

harihacker said:
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
Click to expand...
Click to collapse
There was a difference in the method here and I didn't realize that before; as it was written at the bottom. Sorry about that. I'll try this method and let you know. Thanks!

jadu45 said:
There was a difference in the method here and I didn't realize that before; as it was written at the bottom. Sorry about that. I'll try this method and let you know. Thanks!
Click to expand...
Click to collapse
Goodluck, and let us know the result.. :fingers-crossed:

A warranty is a warranty, it doesn't matter what country you're in or where the repair place is. People in Canada send stuff to the USA for warranty issues all the time. I'd get on the phone with LG until I heard what I wanted, but I'm a stubborn old goat lol.

ShishkaBerry said:
A warranty is a warranty, it doesn't matter what country you're in or where the repair place is. People in Canada send stuff to the USA for warranty issues all the time. I'd get on the phone with LG until I heard what I wanted, but I'm a stubborn old goat lol.
Click to expand...
Click to collapse
Well, there is no authorized dealer here; I had to buy it from a local shop. So, there is no warranty!

harihacker said:
Like DC_Knight said, please try the TOT method given here. Hope it works.
http://forum.xda-developers.com/nexus-5x/help/tutorial-how-unbricked-nexus-5x-16gb-t3481766
Click to expand...
Click to collapse
questionquince said:
Try the tutorial here. It's little bit different from the original thread ,
as @bardhi92 said, THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP
Well, for my case, eventually I successfully bring my N5X alive. The tricky part is to enter Android System Recovery (hold Power + Volume Up) after flashing TOT.
Click to expand...
Click to collapse
Both of you provided me the link. I don't know who you are, but I if I find you you guys are going to have a treat for sure. I literally cried when I got my phone back. Thank you guys. Thanks xda!