Database Users

[Q] [HELP] LG G2 D802 in coma - Really Deep, Hard and Seriously Bricked

A few posters here claim that the G2 is unbrickable - but I think I can challenge that. It started off with me wrongly flashing the Cloudy ROM 3.0 - what I didn't realise only till later was that it was intended for the Korean variant of the G2. Dummy move indeed.. I had previously taken the necessary precautions and took a full titanium backup and ROM backup onto a USB drive via TWRP - I previously ran Cloudy ROM 2.2 with Dorimanx Kernel on KK 4.4.2.
Right now, the phone doesn't seem to power on via buttons. When I plug it to the PC via the USB, I get "QHSUSB_BULK" as an unknown device only.. no black screen while on, no drives or COM port.
First off I want to be clear that I know I and only I am responsible for bricking my phone - The reason I'm in this mess is completely down to my stupidity, and trusting 'educated guesses' instead of confirming specs black of white. Just wanted to be clear in case anyone gets the wrong impression.
So this is more or less the sequence of events;
1. After flashing, I got stuck in fastboot mode.. (can't find the link) I followed one post where I needed to flashed .img files via the Fastboot CLI (similar to ADB). I used the images from the LG G2 D802 16GB in europe. source.. It was a toss up between the EUR and non EUR, and so I made the first of my so called 'educated guesses' that sent this phone deeper into the ground.
2. Something went wrong as when I rebooted the phone (had no idea what had gone wrong at the time), I got no logo. After some time, I noticed the screen on with a black background. when plugged into the pc, the QHSUSB_BULK would appear and with it a bunch of drives that Windows thought needed repairing. so I followed This .. I installed ubuntu, booted to terminal so I don't get those auto discovery pop ups, I used the images recommended there for my device (again, it seemed to make sense to use the same that the OP was using for my LG G2 D802 16GB in europe... After I rebooted, it was to my horror that the screen didn't even turn on, with no drives being detected via USB.. just the QHSUSB_BULK. This is what made me realise that the culprit was most probably using wrong images rather than improperly executing the instructions.
3. I opened the phone and tried shorting some capacitors where I'm supposed to see the drives again to no avail. I even tried shorting the capacitors ends as described here to no avail. I done a good full hour shorting the hell out of those capacitors (the post says to keep at it till it works cos it can sometimes be a bit tricky) but I saw no change. I would like to try the DL mode described there but I can't figure out what I have to ground from the images shown in the post regarding the "BOOT CONFIG".
This is basically the state the phone is in at the moment. so to recap:
No bootloader,
no recovery,
no fastboot,
no download mode,
no drives when in QHSUSB_BULK mode,
no COM port.
From the multitude of unbricking guides here, I gather that I either need to see that bunch of drives again when via USB or a COM port. I tried installing Qualcomm drivers, thinking that if the pc recognises the device, I might get the pc to identify the COM port, but the driver couldn't be installed for the QHSUSB_BULK device (got some error.. I can update this post later).
I tagged this post as a question.. i'm sure there's a question here somewhere...
HELP?!

bump.
Could really use a little help... anything

kuwlij said:
bump.
Could really use a little help... anything
Click to expand...
Click to collapse
You can ask @somboons
he came from deep hard bricked.
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
http://forum.xda-developers.com/lg-g2/development-d802/tools-mini-srk-tool-d802-t3098163
:good:

.
...

When I first tried to enter QHUSB_BULK mode on mine, I took ages. Seriously, ages. It kept not showing the drives. Important thing to remember, in my opinion, is to use Linux (latest Ubuntu in my case). If you keep trying, eventually they will pop up for a split second. I can't remember how I did it, but you have to use a partition tool, I think, to get it to freeze the positions of the drives. Then, once it's 'mounted' them, you can try (and keep trying) to flash to each partition.
Mine was well and truly screwed, so I flashed a blank partition table on, then flashed each image onto that. It took a lot of trial and error, though, because it kept not showing the drives.

furzewolf said:
When I first tried to enter QHUSB_BULK mode on mine, I took ages. Seriously, ages. It kept not showing the drives. Important thing to remember, in my opinion, is to use Linux (latest Ubuntu in my case). If you keep trying, eventually they will pop up for a split second. I can't remember how I did it, but you have to use a partition tool, I think, to get it to freeze the positions of the drives. Then, once it's 'mounted' them, you can try (and keep trying) to flash to each partition.
Mine was well and truly screwed, so I flashed a blank partition table on, then flashed each image onto that. It took a lot of trial and error, though, because it kept not showing the drives.
Click to expand...
Click to collapse
Mine was exactly the same I also had a blank partition table.. Anyway just keep trying because It took me a while to get mine working.. I was trying to short the capacitors but it seems to be quite hard sometimes especially if you aren't carefull.. Because you can start to mess with the soldering of the capacitors and it'll be harder after that.. It happened to me..
Anyway here's something I've wanted to ask everyone, after I sucessfully put my phone back to life, it seems like the middle button isn't working, the LED and the volume rockers are fully working, but if I ever press the power button after some time it shutdowns just like if I pressed and hold for a while, has anyone got this problem? It seems like the flex cable or something is damaged but i wanted to be sure it's really damaged or just something I could solve.. thanks and sorry for the off topic..

kuwlij said:
bump.
Could really use a little help... anything
Click to expand...
Click to collapse
This
HTML:
http://forum.xda-developers.com/showthread.php?t=2582142
saved my D802.Take time to read all post

[Q] DemiGod Crash Handler : Critical Error! Plzz Help Someone

my phone LG G2 D802 International Version was running perfectly fine i tried to flash another rom by LG FlashTOOL and in the first i got soft bricked on that fastboot screen i recoverd it by ADB (fastboot.exe)
fastboot erase recovery
fastboot erase laf
fastboot flash laf laf.img
and then i tried to reflash it then i got this mesg on screen
---------------------------------------------------------------------------
Critical Error!
---------------------------------------------------------------------------
DemiGod Crash Handler : Critical Error!
Press Key to Choose Dload Mode or Reboot
1) Volume up : Dload Mode.
2) Volume Down: Reboot.
If u choose Dload Mode.
please do following action.
1) Dload Mode. please Connect USB
2) Get the Ram Dump image using QPST Configuration.
-------------------------------------------------------------------------
Board Info
Rev. : 1.1 speed.pvs : 1.1 Serial : 01e862cf934fc622
Please Help me somebody ... i cant afford to buy new phone i just bought this phone a week ago ..

Having same issue ! XDA forum experts always helped me with every situation with my phones. Expecting help this time as well from you experts.

Same here, enyone can help, i stuck with the sam message, presing vol- just rebots, and vol+ sends message "jump to download mode" but i cant flash stock firmware

i have the same problem any help ??

I have the same issue too, can anyone help?

I heard that this can help you guys. Use the search option there and try to fix it. Actually i had the same problem few months ago, but for me mew motherboard was the solution... If you're device is under warranty send it saying it failed while taking OTA. Good luck...

lg g2 critical error
I have done a flash to my g2 32gb d802 and it suddenly entered into critical error not going into any of thefastboot mode or download mode even though it is giving me options.....please any one help me out to get my phone back to normal ........

PM me if you guys need help.

I had the exactly same problem, and I had to go to afterservice center to repair. Engineer told he would wipe everything and install new rom. but He failed to write rom so he simply changed mainboard.
At first I had thought about open my g2 and makes it go into qualcomm download mode by short-circuit.
the reason I didn't was my warranty was still available.
I tried every method to make it boot into recovery or download mode but I failed. In my opinion, you may try short-circuit method for last solution. In this situation, even linux doesn't mount rom's storage section. Only if you can make G2 recognized in Linux, G2 will revive.
good luck.

xmayhemreturnsx said:
PM me if you guys need help.
Click to expand...
Click to collapse
i still don't know what to do HELP

yassou92 said:
i still don't know what to do HELP
Click to expand...
Click to collapse
The best way to go if you do not have a warranty is to short circuit the board and get into Qualcomm ... 9006 mode. However, when you get the demigod error plug in you usb and click up and it should start download mode even though it doesn't show it.

xmayhemreturnsx said:
The best way to go if you do not have a warranty is to short circuit the board and get into Qualcomm ... 9006 mode. .
Click to expand...
Click to collapse
How do you short the pins? There's a guide here on xda but it's so difficult to undestand. I need to know how can I short the pins.
it should start download mode even though it doesn't show it.
Click to expand...
Click to collapse
No, it doesn't. I try to use flashtool but it doesn't recognize the phone. No download mode in any method I tried

I got into this error after I had previously recovered into qhs_usb9006_bulk mode from a hard bricked D801, by shorting the capacitors on the main board. After entering qhs_usb9006, I used srk tools 2.1 for my phone, and after they finished, I tried entering download mode, only to get into this error. I really don't know what it is to say about this. Everything turned wrong with this phone, it went from simply failing a .kdz, to stock .tot, to hard brick, and now to this error, whereas it should've just enter the download mode, as for the 99,99% of the others. Any help would be really appreciated. Thanks.
L.E. I shorted the capacitors again (the one i the middle, like I did the first time, when i got into 9006 mode. 5000 and 5004 didn't work for some reason). This time I got into dload mode, which is 9008. I'll try to recover the phone from here, with this method:
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830

i had this problem while trying to return to stock. Fixed it by following this guide http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404 . it needs some hardware tampering though. i tried and tried but i cant flash the phone any other way. the way i understand this is due to bootloader being corrupt.

I installed autorec from playstore solved all the problems

Than you! autorec worked for me too

Can someone post a KK baseband for D801 (T-Mobile)? I'm on D80120a software version with unknown IMEI and baseband (the phone is a D801 refurbished into D802, I more than hardbricked it by flashing wrong .kdz, got it recovered through shorting pins, 9008 mode, got download mode, D80120a stock, root, twrp, after a very long and painful process of about 1 month). Now I have to make use of QPST, but I have to obtain a valid baseband first. Of all links I've stumbled upon, only 5% or less of them are still working, so I only have one flashable modem, in twrp recovery, which corresponds to D801 jb version.
http://downloads.codefi.re/autoprime/LG/LG_G2/G2_modems
cloudyfa kk_baseband_D801 only make my phone restarts like crazy.
I'm simply stuck and pray for some devine help.
Thank you.

Weird enough, I flashed a canadian modem and I got both baseband and IMEI. Why did I do that in the first place? Because I remembered that before all these things happened to my phone, the baseband was M8974A-AAAANAZM-1.0.190082, which corresponds to D803. So I said to myself what can happen by flashing the wrong modem? Boot loop, easily fixable with the phone in it's current state. But again, after 1 month of trouble with the phone, I'm back to what exactly started it in the first place: phone seem to work OK but it has 2 huge problems: WiFi extremely weak (2 meters away and a wall or 5 meters away and no wall a and I lose the signal in both cases; the 2nd is wit the GPS - 20-30 meters error). No idea how should I adapt the radio to Europe region (by keeping the canadian one and change the settings, if it's even possible/fixable this way or if this even does make any sense).

I had to do a hard brick fix to get it into the QSUSB mode to flash TOT.

Have you tried using LG Support tool to put it back to stock?
Sent from my LG-F350K using XDA Free mobile app

lg g2 trying to unroot

Hello all,
usually i deal with my problems by searching the forum, though this time i am really worried as i cant find anything to my help.
You see something went bad with the screen and because the phone is rooted, i cant get it fixed (it is still in warranty), nor can i use it (the touch sucks).
So i am trying to get it unrooted.
So i have downloaded LG mobile support tool and the drivers, i enter the phone to download mode and nothing happens. i get all the time errors. Also, in the lg mobile support tool, i see a software update. Should i do it? I cant though because the start upgrade button is greyed out, and the "LGD802" sign on the left pane is flushing like its trying to verify my g2. Also, should i wait for like 10 minutes or so when i enter download mode for the bar seen at the phone to be completed before the whole process? Lastly, the most of times the lg mobile support tool crashes on the pc.
Please help me folks... :/

spirios1992 said:
Hello all,
usually i deal with my problems by searching the forum, though this time i am really worried as i cant find anything to my help.
You see something went bad with the screen and because the phone is rooted, i cant get it fixed (it is still in warranty), nor can i use it (the touch sucks).
So i am trying to get it unrooted.
So i have downloaded LG mobile support tool and the drivers, i enter the phone to download mode and nothing happens. i get all the time errors. Also, in the lg mobile support tool, i see a software update. Should i do it? I cant though because the start upgrade button is greyed out, and the "LGD802" sign on the left pane is flushing like its trying to verify my g2. Also, should i wait for like 10 minutes or so when i enter download mode for the bar seen at the phone to be completed before the whole process? Lastly, the most of times the lg mobile support tool crashes on the pc.
Please help me folks... :/
Click to expand...
Click to collapse
Where did you buy it, it sounds like the symptoms of a frankenphone. There is a post about it, some sellers flash d802 firmware on a d800 and it causes similar problems with screen, IDK about the LG mobile flash tool.
.

3r4s3r said:
Where did you buy it, it sounds like the symptoms of a frankenphone. There is a post about it, some sellers flash d802 firmware on a d800 and it causes similar problems with screen, IDK about the LG mobile flash tool.
.
Click to expand...
Click to collapse
I bought it 1 year ago, although i immediately flashed cloudy's rom. i cant understand though why every now and then the screen becomes unusable.

spirios1992 said:
I bought it 1 year ago, although i immediately flashed cloudy's rom. i cant understand though why every now and then the screen becomes unusable.
Click to expand...
Click to collapse
If you are brave enough you could try taking it apart and swabbing all the conections, I don't know if that would help but some people say it helps them. And the screen could just be faulty, you never no, before I took it apart I would try reflashing rom, doing the stock touch firmware update thing, then if it still don't work try flashing a kdz for the model number physically inside your phone not the one in the system info, and then I would take it fully apart, and put it back together then if it don't work, replace the screen.

the thing is i cant really interact with the screen to reflash the rom, its inresponsive. and my lg mobile support tool randomly crashes i hook my phone up the pc and it starts the download drivers part

spirios1992 said:
the thing is i cant really interact with the screen to reflash the rom, its inresponsive. and my lg mobile support tool randomly crashes i hook my phone up the pc and it starts the download drivers part
Click to expand...
Click to collapse
Try a different computer, you could use a USB otg cable to hook a mouse up to your phone if your having issues with touch screen to reset it.

try in different pc and differenrt dll

LG G2 D802 No Display, Bricked, Recovered

Hello,
This is my first post on this forum so hello everyone! This forum has helped me numerous times with various devices, it is a valuable source of information and the people here seem very helpful. I have searched but cant find a thread relating to my current issue so I decided to start a thread and hopefully get some answers.
Ill try to keep this short while still providing enough information, first things first my device is a D802T 32GB model. Timeline of steps ive taken are as follows.
-Running Ressurection Remix ROM
-Downloaded ROM update and flashed with TWRP
-Device would get to "Upgrading Apps" step then restart half way through, back to upgrading app, restart again and so on
-Flashed stock ROM with LG Flash tool 2014, Froze at 49%
-Tried again to flash Stock ROM, this time it froze at 10%
-This caused the phone to loose Download mode & Recovery.... HARD BRICKED
-Phone would show as Qualcomm HS-USB 9006 in device manager
-Used Ubuntu to flash Partitions
-Must have flashed wrong partitions, after I flashed them the phone seemed to be 100% bricked with no signs of life at all
-Managed to jump pins on chip inside phone to get it into Qualcomm HS-USB 9008 mode
-Downloaded BIN_LGD802AT-00-V10b-SEA-XX-SEP-04-2013-32G+0 TOT File and extracted partitons
-Used BoardDiag to re flash Partitions I extracted from TOT file above
-Phone now seems 100% fixed except for one issue NO DISPLAY!
The phone boots, I hear the boot sound, the touch screen works as it should but I have no display whatsoever not even a black screen. My question is can flashing partitions cause you to loose display but the phone still boot and retain digitizer function?
I repair phones for a bit of extra money on the side so I know what im doing but I wanted another opinion or two before I go ordering parts. Does this sound like I may have damaged something while jumping the pins or could it be the partitions I flashed? Also if I have damaged something how can I tell if its the screen or if I damaged the charge port flex as this carry's the display signal. Keep in mind everything else works on that lower board such as the USB port etc. It seems a massive coincidence I loose display after flashing partitions but then again I was fiddling with the insides but I have done that many many times before so what are peoples thoughts on this?
I appreciate anyone who takes the time to help

42 views and no one has any ideas at all?

Sorry m8.....the last time i had 9006 brick i flashed correct partitions and got my phone working through TOT.......
You could try a new flex cable or even a new screen to diagnose whether its a hardware problem, black screen usually indicates damaged LCD connector pins on LCD panel or flex cable.
Also having "white tv noise" indicates a damaged flex cable.
Next time you have 9006, use this! https://www.youtube.com/watch?v=_d5b_osUTug
You don't need Ubuntu and you have less chance of super bricking.

Hey mate thanks for replying,
I did try that method but kept getting an error (something about cannot find file specified) so I just went the Ubuntu method. I did plan on just ordering a new screen but wanted to be a bit more certain of the issue first. I wish I had of kept my old damaged screens so I could fit one to determine if the screen really is the issue.
I didn't need to touch the bottom part where the LCD flex cables plug onto the board but stranger things have happened, unfortunately the G2 doesn't seem to be very popular in my area as I dont know anyone else that has one that I could possibly put my motherboard in to know for sure its the screen.
I might completely disassemble it and inspect it under a magnifier to make sure I haven't knocked any resistors or anything off the board, ill probably end up just ordering a screen as it seems the only way to know.
Thanks for your help

Hardbrick on Samsung J5 J500fn What options are?

Phone was hard bricked using standart program Odin, it was bricked because i added 1 flash file needed, to 4 sections BL,AP,CP,CSC same file for each section, it's supposed to be only at AP, and its flashed with green PASS, what is surprising to me that nothing prevented to flash it, after it pass, phone black screen, no recovery or anything, just common hard brick "qhsusb_bulk" thing.
I tried load recovery from microsd 32gb, but nothing happens at all, still black screen, maybe i need correct debrick image?
What other options are for this phone?

Sorry to not have any help but I've done the exact same thing as you have to the exact same phone. Ticked all four sections in Odin instead of just AP. Got the green PASS and then the phone went dead. I must have misunderstood something in the instructions I was reading but it was too late. D'oh. Hard brick. I've been messing around with debrick files trying to get it to boot but not having any luck so far. I was using Odin in the first place to try and bring my phone back from "Custom Binary Locked by FRP" which randomly happened to my phone when I put it on after not using it for a while, never used any root stuff before now (the only other person I could find online who got the FRP error without rooting anything had eMMC failure, so my phone could be toast anyway.) I'll come back here if I have any luck with the debricking files.

DeTovergieter said:
Sorry to not have any help but I've done the exact same thing as you have to the exact same phone. Ticked all four sections in Odin instead of just AP. Got the green PASS and then the phone went dead. I must have misunderstood something in the instructions I was reading but it was too late. D'oh. Hard brick. I've been messing around with debrick files trying to get it to boot but not having any luck so far. I was using Odin in the first place to try and bring my phone back from "Custom Binary Locked by FRP" which randomly happened to my phone when I put it on after not using it for a while, never used any root stuff before now (the only other person I could find online who got the FRP error without rooting anything had eMMC failure, so my phone could be toast anyway.) I'll come back here if I have any luck with the debricking files.
Click to expand...
Click to collapse
This is basicly exactly my situation you mentioned from Odin to FRP lock screen 1:1 match, i was thinking that eMMC failed to, becouse tried Sdcard method, qfil flashing, absolutly nothing works, last thing im waiting to try is usb JIG i ordered, if you find any information or do any progress, be sure to share it, i will do it to if i find anything success, but if JIG wont work, than i suspect that eMMC failed, or phone have liquid damage somewhere, becouse USB sometimes disconnected randomly multiple times, and show Unknown device error on win10, also i took phone to repair shop, said i need reflash becouse bricked, he didnt fixed to, maybe not experenced at that,only things like replace screens

Well, I'm sure you, like me, have made absolutely zero progress on this device since nothing seems to work with it. The J5 SD cards don't work, you can even make your own debrick from a stock rom, but these didn't work for me either. No response at all of any kind to any SD card.
Presumably it should work like in this video, the LG here isn't responsive to anything, shows up as "Qualcomm HS-USB QDLoader 9008" then the SD card goes in and BOOM, device back. Also, that guy seems to be in the "old QDLoader mode" just like us so in theory I don't see any reason for the SD card to not work, maybe we just haven't found the right one?
Annoyingly, if Samsung ever released their files like the firehose (which I doubt they would) or they got leaked, then QFIL would work. But as it stands we don't have those files so we can't do anything with QPST/QFIL except see that it's the only thing that can communicate with the J5 in that state.
I'm not sure what a USB jig does, but looking on Google it seems like it just simulates button presses to hold the combination for Download Mode?

DeTovergieter said:
Well, I'm sure you, like me, have made absolutely zero progress on this device since nothing seems to work with it. The J5 SD cards don't work, you can even make your own debrick from a stock rom, but these didn't work for me either. No response at all of any kind to any SD card.
Presumably it should work like in this video, the LG here isn't responsive to anything, shows up as "Qualcomm HS-USB QDLoader 9008" then the SD card goes in and BOOM, device back. Also, that guy seems to be in the "old QDLoader mode" just like us so in theory I don't see any reason for the SD card to not work, maybe we just haven't found the right one?
Annoyingly, if Samsung ever released their files like the firehose (which I doubt they would) or they got leaked, then QFIL would work. But as it stands we don't have those files so we can't do anything with QPST/QFIL except see that it's the only thing that can communicate with the J5 in that state.
I'm not sure what a USB jig does, but looking on Google it seems like it just simulates button presses to hold the combination for Download Mode?
Click to expand...
Click to collapse
Im still researching, i even used same method to make own debrick image, i tried multiple versions, latest 6.1 android, than latest 5.1 android, even tried first firmware 5.1 released, still absolutly no reaction to phone, not even vibrate or anything, tried press multiple times button combinations, tried few SD cards, 32gb with 10speed, absolutly nothing at all, looks like we are on exactly same situation, im stil trying things, now probably will be USB jig, combination with MicroSD, im just waiting on few USB jigs i ordered, for few dollars, its usefull to have anyway for other situations, so if i found any sign if life i will definetly share here, becouse if my would work, definetly your would work to, i have no idea why its does absolutly nothing, i tried even diffrent battery from other phone, still same, and before i tried use Qualcom flash QFIL, try flash some unofficial firmwares, but looks like Samsung phones not very good at that, only LG or others its designed for that, basicly no infomation about Samsung phones, even no repair services online.so if you find any progress be sure to share it, i would definetly do it, if i discover anything.

I have the same problem as you. My sister was using a Samsung Galaxy J5 (2015) and the battery was growing bigger meaning that it could be dangerous. So we left that one smartphone in the corner without a battery. Well, after my Nexus 5 had a problem too, I decided to get back to my J5 that I gave to my sister. I had to buy a new battery for it so I did. When the battery arrived, I tried to turn it on, but it wasn't turning on. I connected it using a USB cable in my computer but instead of displaying the device's name, it displayed as QHSUSB_BULK. When I was asked to install drivers for the device, I did so, and the name changed to Qualcomm HS-USB QDLoader 9008 (COM8). I went it to a repair shop and they said it might be the freakin' screen!!! I mean, what? People all over the Internet having the same issue with me say that it is a hard brick. Hard brick has NOTHING to do with the screen, correct me if I am wrong. I also saw somewhere that I can only fix my device if only I replace the motherboard entirely (because replacing specific part of the motherboard is kind of dangerous and can cause even more problems...) I have no idea. I need help. I want to try flashing firmware with my SD card, but I have no image for my SM-J500FN device. I feel hopeless. They encourage me to buy a new smartphone. Something "modern". But what I know is that today's devices are more "brick-able" that those of old times. I want to install TWRP Recover again and finally root my device. I know how to do that to my Galaxy J5, but I can't do that when my smartphone is not turning on at all. It doesn't even vibrate!!

Retr0.Hacker said:
I have the same problem as you. My sister was using a Samsung Galaxy J5 (2015) and the battery was growing bigger meaning that it could be dangerous. So we left that one smartphone in the corner without a battery. Well, after my Nexus 5 had a problem too, I decided to get back to my J5 that I gave to my sister. I had to buy a new battery for it so I did. When the battery arrived, I tried to turn it on, but it wasn't turning on. I connected it using a USB cable in my computer but instead of displaying the device's name, it displayed as QHSUSB_BULK. When I was asked to install drivers for the device, I did so, and the name changed to Qualcomm HS-USB QDLoader 9008 (COM8). I went it to a repair shop and they said it might be the freakin' screen!!! I mean, what? People all over the Internet having the same issue with me say that it is a hard brick. Hard brick has NOTHING to do with the screen, correct me if I am wrong. I also saw somewhere that I can only fix my device if only I replace the motherboard entirely (because replacing specific part of the motherboard is kind of dangerous and can cause even more problems...) I have no idea. I need help. I want to try flashing firmware with my SD card, but I have no image for my SM-J500FN device. I feel hopeless. They encourage me to buy a new smartphone. Something "modern". But what I know is that today's devices are more "brick-able" that those of old times. I want to install TWRP Recover again and finally root my device. I know how to do that to my Galaxy J5, but I can't do that when my smartphone is not turning on at all. It doesn't even vibrate!!
Click to expand...
Click to collapse
Im sure its hardware failure, nothing can be done, i tried alot things, nothing worked, not even small progress, phone just dead, tried usb jig, tried to use every recover image from all firmwares, nothing worked, only fix to this phone is replace motherboard, but to access motherboard you need remove screen first, i give up on this phone, not worth time, tried everything, ether motherboard replacing or just get new phone

Vkrs said:
Im sure its hardware failure, nothing can be done, i tried alot things, nothing worked, not even small progress, phone just dead, tried usb jig, tried to use every recover image from all firmwares, nothing worked, only fix to this phone is replace motherboard, but to access motherboard you need remove screen first, i give up on this phone, not worth time, tried everything, ether motherboard replacing or just get new phone
Click to expand...
Click to collapse
Well, they suggest me to get a new smartphone because if I get to replace the motherboard it will be too expensive and maybe not worth it... I guess I will have to give up too, even if I loved that one... Thank you friend.

Retr0.Hacker said:
Well, they suggest me to get a new smartphone because if I get to replace the motherboard it will be too expensive and maybe not worth it... I guess I will have to give up too, even if I loved that one... Thank you friend.
Click to expand...
Click to collapse
Probably happened same thing like to you, i received phone from female, who used daily, it was already had this issue, definetly she didnt do anything software related things like flash, so im guessing hardware failed, thats why nothing you can do, only fix is most likely motherboard replacement, but at this point is not worth it, becouse will cost half phone price, so i rip"ed this phone, writed it off, its laying for parts, did what i can, tried all methods, usb jig worked on every samsung i have, s5, j5 2016, but execpt this one, this means is definetly phone dead, also tried to recovery with microsd, every single firmware, from 5 android to 6, all versions, created recovery, and none of them worked, also tried on few microsds, and absolutly was no progress, not even vibrate, dead entire time