Related
In brief:
The N4 is stuck on the whirling circles during boot. It is likely due to some broken bit of hardware. I would like to determine where it's stuck. After that I can decide if repair is possible or if I don't need that feature and it can be skipped one way or another or toss the brick altogether.
In full:
While out of town S.O. dropped the phone and the digitizer shattered. She said the screen appeared to still work, but no input was possible. She ordered a new digitizer and dumped it on me to repair, little realizing the difficulty of replacing only the digitizer. Still, I gave it the ol' college try on a slow day at work, heating the glass shards to yield the glue and get them off the screen. After installing new digitizer I was not surprised that I had damaged the screen and just a few colored stripes displayed.
So I ordered and installed a digi/lcd assembly and I now have a functioning screen and digitizer. The problem is the system won't completely boot and is stuck on the infamous whirling circles. I am fairly certain that during boot some device is being queried and is broken, and the boot has no timeout to skip it and move on. I would like to know where it's stuck. I *think* the way to do that is to somehow direct kernel messages out the phone's USB so I can use PuTTY to display them on a workstation. I do not know how to do that. If there's some other way, like getting the messages to display on the phone's screen, I don't know that either. Hence my post.
The techie bits:
Long story short here's a summary of relevant actions I've done so far.
Phone still goes into the mako bootloader and I can use fastboot.
Used TWRP recovery to wipe everything (including itself)
Flashed factory 4.4.2 OS
Reinstalled TWRP recovery and had it root for me
I now have two ways to access the phone - fastboot when in the stock mako bootloader, and adb when I fire up TWRP.
Now what can I do to find where the system boot is hanging? Suggestions welcome.
first thing to look at - proximity / light sensors connector . phone will not boot if they are disconnected from mainboard.
RolF2 said:
first thing to look at - proximity / light sensors connector . phone will not boot if they are disconnected from mainboard.
Click to expand...
Click to collapse
I will check that. Thanks for the reply.
Edit: I just checked, and you were right on the money. The tab with the connector for that device had flipped under the mainboard so I didn't connect it. All fixed now and I have a working phone. I owe you a couple beers. Thanks.
Hi, you are lucky
I have a similar problem.
Yesterday i restarted my phone and >problem, stuck at X-boot-logo<
Already tried different roms.
Can get into fastboot-mode and therefore can have ADB with CMW-recovery.
I replaced my screen a few months ago.
Already checked proximity sensor cable.
btw:
at the beginning, one time I got it to "optimizing apps...", but it was stuck at "starting apps"
How can I see if my proximity/light sensor is dead?
can I use the Nexus 4 serial?
Any other solution?
Regards
You can try to downgrade to stock 4.2 android, phone most likelly will boot, but looks like you have lost your IMEI.
RolF2 said:
You can try to downgrade to stock 4.2 android, phone most likelly will boot, but looks like you have lost your IMEI.
Click to expand...
Click to collapse
OK, I'll try to go back to 4.2.
Anything I can do if I really lost IMEI?
I think you could be right.
I rebooted my phone because i got no network connection. (even after airplanemode on/off)
---------- Post added at 07:05 PM ---------- Previous post was at 06:45 PM ----------
OK, 4.2 booted successfully
Thanks.
but phone does not connect to network.
IMEI seems to be lost (*#06# shows nothing for imei)
What do you think about restoring IMEI with dd-command from "somewhere"?
take a look here : http://forum.xda-developers.com/wiki/LG_Nexus_4/Partition_Layout
do you have baseband version unknown too ?
if yes, first I would try dd mmcblk0p1 (modem / radio.img) and only after that next step would be m9kefs1/mmcblk0p8 , m9kefs2/mmcblk0p9 = IMEI
this is only speculation, never tried that ...
RolF2 said:
take a look here : http://forum.xda-developers.com/wiki/LG_Nexus_4/Partition_Layout
do you have baseband version unknown too ?
if yes, first I would try dd mmcblk0p1 (modem / radio.img) and only after that next step would be m9kefs1/mmcblk0p8 , m9kefs2/mmcblk0p9 = IMEI
this is only speculation, never tried that ...
Click to expand...
Click to collapse
no baseband too.
imei empty, not zero
I don't think dd mmcblk0p1 would be useful as it is only the radio.img.
You can find it in the stock image
The first step now is backupping the efs-partitions
do you mean directly writing IMEI to it?
I can try to copy the IMEI(or all partitions) from my brother's phone to mine
Thx
don't hurt to try dd modem partition first, maybe it's corrupted in some way ... why it's unknown ?
Hi, I have a G2 I need some help with. This is a partial repost from [HELP THREAD][Noob Friendly].
Just got a LG G2 for my wife (wedding anniversary). It arrived by post yesterday, yay I though, I got a couple of weeks to sort it out. Am trying to transition her from her old iPhone4S over to Android, and from checking things out, it looked like the OptimusG3 rom was the way to go, in terms of a nice interface.
I shoulda slowed down and been more meticulous with the process, but anyway… I have little knowledge of these things, but have managed to flash custom ROMS to a couple of devices before (HP Touchpad, Ainol Fire), noting that any problems I’d previously encountered were usually due to skipping or not following steps properly.
G2 model is D802. Kitkat 4.4.2 installed by default. From an ebay seller - back case, software and printed instructions all say D802. Opening the back case, internal bottom left corner says D801/D803.
Tried to follow guide here http://forum.xda-developers.com/show....php?t=2788077
Tried to root as per here http://forum.xda-developers.com/show....php?t=2448887
I think the root went through ok, although I had to try more than once (had other stuff happening in the background so not paying 100% attention).
Tried to flash TWRP as per here http://forum.xda-developers.com/show....php?t=2633941
Didn’t seem to be able to get this working.
Uncertain at this point if I was properly rooted, so redid it with https://towelroot.com/ - which seemed to be fine
Then tried to install TWRP with Autorec: http://www.droidviews.com/install-twr...
Which seemed to be successful, and I’m sure I picked the D802 TWRP recovery file, but THIS IS WHERE THE TROUBLE REALLY BEGAN - on reboot to recovery the trouble started – no logo, I’m just seeing a black screen with vertical lines that change for a bit, then go static.
My understanding now (thanks to Art Vanderlay) is this is probably the result of me having a JDI panel - so now I need to reflash a JDI kernal to fix the LGIT kernal that Autorec installed.
I can't read the screen at all - it is just black with white lines and change a bit before going static. I have tried to connect the phone up to the computer in DOWNLOAD mode using the VOLUME UP and ATTACH USB CABLE technique.
When I do this, the computer beeps to let me know a device is attached, and a ADB device turns up in device manager - but then nothing else thinks a device is attached, including SimpleTool, LGFlashTool2014, PDANET (which does say device connected to begin with, but then doesn't proceed any further), ADB (via commandline), MinimalADB, or Linux.
I have tried various permutations and combinations of:
1. different USB ports
2. different USB cables
3. different computers (x3)
4. different drivers (from various places, including LG website, SimpleTool, PDANET). (I even tried a Verizon G2 driver just for the hell of it)
5. two different LINUX distros
...and nothing seems to see the G2.
Any suggestions very very welcome, cos I'm out of ideas.
Did you manage to find a solution to that problem. I am having the same problem
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
Hi everyone, i have a G2(D802) which i have used for 5 years. Yesterday, when i turn off the screen then try to turn on it didn't. I tried to reset with holding power button like 20-25 seconds. It stucked at LG logo. After many reset nothing happened. Then this morning i could was able to open my phone, so i thought it was a problem about software things, so i backuped everything and change my rom(i was using Lineage 14.1 ) to Resurrection Remix. But same thing happened, when i turn off the screen it has gone again. So i decided to install stock rom back. But this time when i used Flash Tool 2014 and appropriate KDZ, it stacked at 4%, after trying different cables, ports,windows 7/xp and programs (like LG Mobile Support Tool, LG Up) in Device Manager it seemed as : "qualcomm hs-usb qdloader 9006" and no recovery mode no download mode, when i google this problem i found it named with "qhsusb_bulk" and i found this article and successfully recover download mode. Now in Device Manager it seems as "LGE AndroidNet USB Serial Port".
TLDR: I can only open download mode, no recovery, it stacked LG logo, when i use Flash Tool 2014 or LG Mobile Support Tool with different KDZ/TOT it stacked at 4%. What should i do? What's wrong with my phone? I need your help urgently because i have no other phone. Thank you for reading.
metobayrak said:
Hi everyone, i have a G2(D802) which i have used for 5 years. Yesterday, when i turn off the screen then try to turn on it didn't. I tried to reset with holding power button like 20-25 seconds. It stucked at LG logo. After many reset nothing happened. Then this morning i could was able to open my phone, so i thought it was a problem about software things, so i backuped everything and change my rom(i was using Lineage 14.1 ) to Resurrection Remix. But same thing happened, when i turn off the screen it has gone again. So i decided to install stock rom back. But this time when i used Flash Tool 2014 and appropriate KDZ, it stacked at 4%, after trying different cables, ports,windows 7/xp and programs (like LG Mobile Support Tool, LG Up) in Device Manager it seemed as : "qualcomm hs-usb qdloader 9006" and no recovery mode no download mode, when i google this problem i found it named with "qhsusb_bulk" and i found this article and successfully recover download mode. Now in Device Manager it seems as "LGE AndroidNet USB Serial Port".
TLDR: I can only open download mode, no recovery, it stacked LG logo, when i use Flash Tool 2014 or LG Mobile Support Tool with different KDZ/TOT it stacked at 4%. What should i do? What's wrong with my phone? I need your help urgently because i have no other phone. Thank you for reading.
Click to expand...
Click to collapse
hi there.. unfortunately LG did a mess in my opinion! After buying G2 and G Pad I will never buy LG again because of this..
anyway, assuming you're doing everything as described into the guides (like port COM 41, copy the right DLL file etc) there is one thing I would try in your situation: trying with a different PC, in particular a Windows 7 / XP one..
also I read that sometimes this issues was randomly gone after trying and trying and trying and trying and trying..! If available I would also try different KDZ firmware (but be sure it's for your model.. as long as it is it doesn't matter if it's JB, KK or LP)
brainvision said:
hi there.. unfortunately LG did a mess in my opinion! After buying G2 and G Pad I will never buy LG again because of this..
anyway, assuming you're doing everything as described into the guides (like port COM 41, copy the right DLL file etc) there is one thing I would try in your situation: trying with a different PC, in particular a Windows 7 / XP one..
also I read that sometimes this issues was randomly gone after trying and trying and trying and trying and trying..! If available I would also try different KDZ firmware (but be sure it's for your model.. as long as it is it doesn't matter if it's JB, KK or LP)
Click to expand...
Click to collapse
Thank you for your suggestion, after several hundred attempts i successfully go back to stock rom(an Indian stock rom which i found it in storagecow link), but the problem is; when i turn off the screen, i can not open again, and it restarts and stuck at lg logo. After hundred times reset, phone started normally, then i flash a twrp recovery (with autorec) and go recovery. This time twrp said Unable to Mount System,Storage etc. so twrp shows internal storage: 0mb and all folders(data,sdcard,system etc.) empty. I mean define this problem is very hard and i think it is very rare problem. I'm not sure which part of the phone is the problem. I don't know is this a hardware problem or a software(like wrong partition or something like that) problem.
metobayrak said:
Thank you for your suggestion, after several hundred attempts i successfully go back to stock rom(an Indian stock rom which i found it in storagecow link), but the problem is; when i turn off the screen, i can not open again, and it restarts and stuck at lg logo. After hundred times reset, phone started normally, then i flash a twrp recovery (with autorec) and go recovery. This time twrp said Unable to Mount System,Storage etc. so twrp shows internal storage: 0mb and all folders(data,sdcard,system etc.) empty. I mean define this problem is very hard and i think it is very rare problem. I'm not sure which part of the phone is the problem. I don't know is this a hardware problem or a software(like wrong partition or something like that) problem.
Click to expand...
Click to collapse
so ROM is flashed but no files are anywhere? Did the same happens when you browse the device with the windows command Prompt / Linux Terminal?
Yea anyway weird, maybe you can see if this tool has original partitions for your model: https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 - please pay attention if you do it and backup the partitions you have atm before
brainvision said:
so ROM is flashed but no files are anywhere? Did the same happens when you browse the device with the windows command Prompt / Linux Terminal?
Yea anyway weird, maybe you can see if this tool has original partitions for your model: https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 - please pay attention if you do it and backup the partitions you have atm before
Click to expand...
Click to collapse
I used this tool when my phone showed in Device Manager as : "qualcomm hs-usb qdloader 9006" and it worked, today when i opened my phone(after install stock rom again) i kept the screen always open. After 5 minutes, suddenly screen gone and stuck at lg logo. Now I think that the problem is definitely hardware. Because i did nothing and phone was connected with a cable to my pc. If the solution is to change a part(like the processor) inside the phone, I will write here what the problem part is. Thank you again.
metobayrak said:
I use this tool when my phone showed in Device Manager as : "qualcomm hs-usb qdloader 9006" and it worked, today when i open my phone(after install stock rom again) i kept the screen always open. After 5 minutes, suddenly screen gone and stuck at lg logo. Now I think that the problem is definitely hardware. Because i did nothing and phone was connected with a cable to my pc. If the solution is to change a part(like the processor) inside the phone, I will write here what the problem part is. Thank you again.
Click to expand...
Click to collapse
pretty sure it's the mainboard, I saw it's the first part of the G2 that gives problem after a while
brainvision said:
pretty sure it's the mainboard, I saw it's the first part of the G2 that gives problem after a while
Click to expand...
Click to collapse
I found the problem part. It's the eMMC chip. I disassemblied the phone and heat the relevant chip (on my motherboard the chip named as Toshiba) with hot air gun. My phone worked properly for 1 minute, then gone again.
metobayrak said:
I found the problem part. It's the eMMC chip. I disassemblied the phone and heat the relevant chip (on my motherboard the chip named as Toshiba) with hot air gun. My phone worked properly for 1 minute, then gone again.
Click to expand...
Click to collapse
you know what: I think my device has the same issue, eMMC is damaged.. I'm not using the G2 as primary or secondary device anymore but from time to time I like to flash something and using it.. but it's almost one year that when stuff I have no error but when I boot the device and start using it I have random reboots.. but they are totally random and almost happen when installing one app, using a system app or something like that. it happens with both stock firmware both with custom ROMs.. basically I have to flash and using the device for a day and if I have less then two reboots in that period I go on..
I'm not an expert about hardware matters, do you mind linking me a video on YouTube about what have you done with the airgun? Also I tried to search for spare eMMC but I wasn't able to find any (some time ago) so the option would be to change the motherboard.. did you find something instead?
brainvision said:
you know what: I think my device has the same issue, eMMC is damaged.. I'm not using the G2 as primary or secondary device anymore but from time to time I like to flash something and using it.. but it's almost one year that when stuff I have no error but when I boot the device and start using it I have random reboots.. but they are totally random and almost happen when installing one app, using a system app or something like that. it happens with both stock firmware both with custom ROMs.. basically I have to flash and using the device for a day and if I have less then two reboots in that period I go on..
I'm not an expert about hardware matters, do you mind linking me a video on YouTube about what have you done with the airgun? Also I tried to search for spare eMMC but I wasn't able to find any (some time ago) so the option would be to change the motherboard.. did you find something instead?
Click to expand...
Click to collapse
This is the video I get help with: https://www.youtube.com/watch?v=ft8V5yrQFic
this guy did this for g3 but doing for g2 also works. This is definitely a temporary solution. It works maybe just 1 minute (like me) or 1 hour if you are lucky maybe 1 month. Changing motherboard is primary solution but it is expensive and worthless. I think that is chronic problem for LG G series. There is no proper heat dissipation on the motherboard. They have just put thin metal plates. Maybe you can try after the heating process, just put a thermal pads the relevant chipsets. You can see from this video: https://www.youtube.com/watch?v=HMdvG6w7etU
metobayrak said:
This is the video I get help with: https://www.youtube.com/watch?v=ft8V5yrQFic
this guy did this for g3 but doing for g2 also works. This is definitely a temporary solution. It works maybe just 1 minute (like me) or 1 hour if you are lucky maybe 1 month. Changing motherboard is primary solution but it is expensive and worthless. I think that is chronic problem for LG G series. There is no proper heat dissipation on the motherboard. They have just put thin metal plates. Maybe you can try after the heating process, just put a thermal pads the relevant chipsets. You can see from this video: https://www.youtube.com/watch?v=HMdvG6w7etU
Click to expand...
Click to collapse
I thought about applying something (couldn't imagine what however) on the internal back of the cover but not because of the issues I have but simply because the device get hot very soon! I'
But basically you are saying that this issue related to the eMMC is not because the chip is damaged but only for the temperature it reaches?
brainvision said:
I thought about applying something (couldn't imagine what however) on the internal back of the cover but not because of the issues I have but simply because the device get hot very soon! I'
But basically you are saying that this issue related to the eMMC is not because the chip is damaged but only for the temperature it reaches?
Click to expand...
Click to collapse
Yes, because of the eMMC chip is damaged. But the crux of the problem is processor heats and cause of no proper heat dissipation this damages other chipsets. Thermal pad solution must be done after chip replacement.
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