Help with bricked SAMSUNG GALAXY S4 AT&T - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Hi guys,
Over about an year ago I SIM unlocked a SAMSUNG GALAXY S4 AT&T. Several weeks ago it stared showing a gray lock on the bootscreen, but it would boot up. Now it just won't boot up or anything. Computer can't detect it. Plugging it into a wall socket does not do anything. It's not the battery I tried with another one. I honestly can't remember if I rooted the phone when I sim unlocked it. I also can't remember his Android version, maybe it was 4.2.x or 4.4.x .... I just don't remember, it was more than a year ago.
What I noticed was that if I remove the battery, leave it out for a while and then plug it back in I have about a 3-second window where the screen turns on and shows the gray lock again. After that it turns off.
I've been reading online, but I can't find a definite answer. Some say it's a USB port problem, others say it's a hard brick.
Please guys, help.

Sounds like a hard brick. Plug it in without the battery. different port at least.. then check device manager and if you see something like "QLoader 9008" under COM PORTSor something similar, then its telling you it cannot communicate with the motherboard.. Qfuse blew.. and chances are the version was 4.4.2. I mean the screen will not turn on at all, no boot, no recovery, i mean if odin doesnt detect it.. then it's a hard brick in more than one way. Sometimes this happens. they call it sudden death syndrome lol.. and since you did some minor modification (please, sim unlock is basically routine now) you are correlating it with that. If Odin does detect it, which it will show "COM:#HERE Added!" or whichever.. then you have a shot.. you might need to use some brick files if you can get the phone into download mode. I mean there's other options like getting a new EMMC or... JTAG types of stuff, quick soldering.. it's a fuse that blew when updating whatever it was updating... or.. it just died. That also happens.
there are other ways to fix it if it shows up like that.. usually getting a debrick image with that exact same OS that he had, boot loader and all.. it has to be a class 10 (or better) sd card.. you simply use something like win32has to match the speed of the boot process and if it is fried, then after about 60-90 seconds, you'll get a boot screen. 16GB is optimal.. or 32GB. Remember... class 10 or better. 10 MB/s minimum speed, usually. Sometimes you'll get away with a crappy card but at least try to do 16 or 32.. there's so much info about it. You just need to use win32 disk imager.. it'll write it to the SD card. FAT32 obviously is the needed file system at the very least. You can also use linux, which is what I actually prefer, but if you're in windows, then just use win32 disk imager. don't try to open the debrick image. just.. look for it.

Related

[Q] Tattoo Bricked

Hello,
I tried to update the radio and the SPL version on my Tattoo. Everything went fine until I had to reboot my phone. It shut down alright, but it never powered on again.
These are the following problems I am having with my Tattoo at the moment:
Cannot power on phone.
Cannot boot into recovery mode.
Cannot boot into FastBoot.
When I connect it to my computer via USB, nothing happens.
The only thing that it's responding to is when I connect my it to my charger.
Does anyone have a solution or is my phone dead forever?
Thanks ahead!
bump? anyone?
Send it back to HTC. If anyone can do anything about it they can. There's nothing else you can do. Sorry
boo.. that sucks..
Well, thanks anyway
Ehm, I don't want to post a New Thread so I'm gonna ask here:
Does anyone have the pinout for the Tattoo?
Take a look at this. I guess they fix such things (but you never know if they just are after your money. http://www.ort-jtag.com/index.php
Yeah I saw that already. Also, there is a file name Tattoo Jtag on their website in the Support section. However, to access that section you have to enter your products serial number (which is I'm guessing the phone's serial number). I have tried several serial numbers (including mine) and all of them were 'invalid' so I never checked the files out.
Also, they only have one thing in the shop which is a kit and it costs $330 so no thanks
I have a similar problem, I would like to share my knowledge although I must be completely out of way.
My experience is based on the BeagleBoard and Angstrom so I really don't know the HTC HW and Android at all...
- The device boots from an xloader that instructs the device how to proceed with the boot
- the bootloader takes place (great u-boot in the beagleboard ?? in the HTC phone) the bootloader allows for ROM or kernel+rootfs flashing and much more
- now the kernel is loaded.....
User mode applications do not allow to have access to the memory area where xloader and u-boot lie so they should be safe all the time to allow for device reflashing.
So we should have access to the device via bootloader anytime if we knew how... maybe somebody can help us further.
Fabio
Same here...Exact same issue...No Recovery mode...No USB Connectivity, Screen turns on but is blank, alhough I did see Tattoo popping up initially but not any more...All I can see is the LCD back light turns on...Battery does charge...Also when I try to enter Recovery mode screen keeps blinking as if it is trying to restart again and again...Someone help
similar problem here, but i get absolutely no response from the phone, it doesn't even recognize the charger. do i just throw it away and buy a decent one or is there a solution?
Sparky the only way for now to fix that click is to bring it to some service point that have that ort jtag, because only way to fix that is to writte new boot sector on phone . Im sure that i know at least 2 services that have ort jtag in Novi Sad . Look for marvel *Miroslav in Ns, or send me private message
same thing happened to me
just this morning, and in desperation I tried hard to remove the batt cover (prob pressed some of buttons, I felt a jerk and ho it was back in amon ra`s recovery, nect time I just removed the battery waited for 30 secs, then press off&home and hold it till recovery came back) but for good half hour NO REACTIONS , ABSOLUTE BRICK, nothing when I put the usb in PC or in socket, dead screen, no sounds and no reaction to ANY combination of keypress. I guess you could call me lucky (in last few days I flashed at least 3 versions of froyo roms, this afternoon I bought =8GB class4 Kingston, formated it in PC FAT32 default size, copied EVE. from my 2gig rom then just turned it down (yes I am brave) and put the 8gig in tattoo, it works like a charm (finger crossed it will continue)
So is there an available Jtag for the Tattoo yet?
I'm in the same situation. No recovery no fast boot, Damm!
I`ve update psfreedom with psgroove_hermes_v4 zip file then my tattoo reboot and now I only get the Tatto title screen but nothing happends.
Somebody have clue to give back life my phone.
Thanks!
if you can get to the title screen, that means you can connect it to your pc via USB and recover from a backup (I hope you made one)
Hello, I connect my tattoo to my pc, but usb connection is not available yet.
Is There is a way to activate usb when my phone blocks in tattoo logo??
Thanks for reply.
payasi35 said:
Hello, I connect my tattoo to my pc, but usb connection is not available yet.
Is There is a way to activate usb when my phone blocks in tattoo logo??
Thanks for reply.
Click to expand...
Click to collapse
You have to enter in fastboot.
Hold volume down and turn on phone.
Cheers
Sorry but as i said before, I can't access to recovery menu neither fast boot menu.

[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

N7 2012 [WiFi] Grouper - Bricked or the Flash Memory just failed?

Ok, so to start off I'm very familiar with Nexus Root Toolkit an its many graceful features & its ablity to bring the N7 from the brink of destruction (Soft -Brick) "AS LONG AS YOUR PC CAN DETECT THE DEVICE".
Here's the issue.. I was in TWRP (Multi-ROM) just renaming 1 of the Secondary ROMs to more friendly names, I hadn't done any flashing of any zips or roms for a few boots, I just booted into Recovery to do some renaming of Secondary ROMs that I had installed a few nights before but I had been in an out of several different one's just making sure they were all working so anyway.. after I was done renaming, I reboot the system & it just went F'ing blank.. now nothing.. there's no back light, no bootlogo, nothing happens at all when I plug in the charging or hold the power button with or w/out the vol-+ keys, I've checked the battery connection, it was snug but I removed it over night.. still nothing, I'm just clueless.. Before we jump on the NRT do a factory wipe & restore, when I plug it into Windows it instantly pops up with the "Device has Malfunctioned" not the "installing adb drivers" or anything like it has so many times before.. either Im over thinking this an the answer is so simple Im blinded by rage over how much this p1sses me off that it was working fine one moment an then just reboots to blank nothingness.. even if I take the battery out an try plugging it directing into the pc via the OEM usb cable it gives the same error with or w/o the battery in .. the toolkit cant even see it cause windows cant establish what the hell it is.. And yes I've tried installing every android driver possible.. the N7 was primarily for my wife to read e-books on.. so i rarely played with it.. an it was new sealed in the box just bought last year around this time so i can't believe the Flash Memory is shot already, if anyone could throw me their 2 cents it would be greatly appreciated , this is so frustrating but I think its BRICKED.. or at least some tiny flash chip is toast..
its the - N7 2012 Grouper WIFI Only model -
p.s. I apologize for the slight harsh tone, I'm just upset with this issue.. I got this particular tablet with the knowledge an understanding that it was the (almost) un-brickable tablet, yet I managed to do it.. If by some chance I get it to fire up, I will definitely let ya know.. But I have read alot of posts an my guess is somehow I managed to mess up the nvflash an now the memory chip or something is corrupt beyond a NRT Factory reset.. but again it was at almost full battery when i rebooted from within the TWRP Menus & I wasn't flashing anything previous to me being in my Main Rom which was stock rooted 4.4.4 de-bloated, playing a game called Empire 4 Kingdoms for like a 1/2 (just getting my daily's) before i decided to check out my Secondary Roms an rename a few because I wanted to started playing around with them to test how the same game played on different flavors or Android..
phnxnvrdies said:
Ok, so to start off I'm very familiar with Nexus Root Toolkit an its many graceful features & its ablity to bring the N7 from the brink of destruction (Soft -Brick) "AS LONG AS YOUR PC CAN DETECT THE DEVICE".
Here's the issue.. I was in TWRP (Multi-ROM) just renaming 1 of the Secondary ROMs to more friendly names, I hadn't done any flashing of any zips or roms for a few boots, I just booted into Recovery to do some renaming of Secondary ROMs that I had installed a few nights before but I had been in an out of several different one's just making sure they were all working so anyway.. after I was done renaming, I reboot the system & it just went F'ing blank.. now nothing.. there's no back light, no bootlogo, nothing happens at all when I plug in the charging or hold the power button with or w/out the vol-+ keys, I've checked the battery connection, it was snug but I removed it over night.. still nothing, I'm just clueless.. Before we jump on the NRT do a factory wipe & restore, when I plug it into Windows it instantly pops up with the "Device has Malfunctioned" not the "installing adb drivers" or anything like it has so many times before.. either Im over thinking this an the answer is so simple Im blinded by rage over how much this p1sses me off that it was working fine one moment an then just reboots to blank nothingness.. even if I take the battery out an try plugging it directing into the pc via the OEM usb cable it gives the same error with or w/o the battery in .. the toolkit cant even see it cause windows cant establish what the hell it is.. And yes I've tried installing every android driver possible.. the N7 was primarily for my wife to read e-books on.. so i rarely played with it.. an it was new sealed in the box just bought last year around this time so i can't believe the Flash Memory is shot already, if anyone could throw me their 2 cents it would be greatly appreciated , this is so frustrating but I think its BRICKED.. or at least some tiny flash chip is toast..
its the - N7 2012 Grouper WIFI Only model -
p.s. I apologize for the slight harsh tone, I'm just upset with this issue.. I got this particular tablet with the knowledge an understanding that it was the (almost) un-brickable tablet, yet I managed to do it.. If by some chance I get it to fire up, I will definitely let ya know.. But I have read alot of posts an my guess is somehow I managed to mess up the nvflash an now the memory chip or something is corrupt beyond a NRT Factory reset.. but again it was at almost full battery when i rebooted from within the TWRP Menus & I wasn't flashing anything previous to me being in my Main Rom which was stock rooted 4.4.4 de-bloated, playing a game called Empire 4 Kingdoms for like a 1/2 (just getting my daily's) before i decided to check out my Secondary Roms an rename a few because I wanted to started playing around with them to test how the same game played on different flavors or Android..
Click to expand...
Click to collapse
UPDATE STATUS - If I plug it into the pc without the battery i get a windows driver install box that says "Installing APX..." does this indicate the NVFlash is corrupt or is there a way to get out of apx mode.. im not familiar with that mode .. only ADB & fastboot..
Update 2 - After reading lots, I've come to conclude its hardbricked, must have had an error in memory or whatever.. its stuck in APX mode so im going to replace the whole MB with a working 32GB [model me370t] & start over .. maybe ill not install so many ROMS via multirom.. just a few - THREAD BE CLOSED - I'm done here, good luck to anyone with similar results

Phone died, but I have another one. Any way to clone it to save the other?

Sorry for the confusing title. English is not my native language.
What happened is that I wanted to install Lineage OS on my phone (It have root+USB debugging and its in MM), but since I'm a noob, I ended up briking it.
It happened at the step where you should unlock the bootloader. In some way I could not achieve it, so I assumed it was because I did not know the "aboot partition" of my phone.(I still don't know what that is xd)
Long story short, I flashed the file "aboot.img" (which should go in "mmcblk0p5") in some other partition.
Yes, I know now how stupid I am ;-;
Now the phone is totally bricked.
No recovery mode, Download mode, Fastboot or Firmware mode (of which I'm aware) works. It does not even show the LG logo.
However, the phone responds to being connected to the pc (it vibrates!). It is even recognized in the Device Manager panel, as "LGE androidnet usb serial port (COM <any number>)".
It also responds when the battery is removed being connected by displaying an image on the screen.
So I conclude that the phone is not totally lost?...
The other part of the situation is that I have a spare Spirit. It's exactly the same as the other one, but it works (albeit the wifi deactivates itself every 5 seconds since a hit, so it's not useful for me).
And I was thinking if there is any way to make an exact copy of the other device or something like that? (like in a computer) Or use it in some way to save my main Spirit.
I mean, it's completely functional, apparently. It has a problem in the partitions, sure, but it seems that there is still some way to access the phone, right?
I know I'm new in this (I have some experience with computers, but little to nothing with Android devices), so I'm sorry if I just said a lot of stupid things.
But I would appreciate some help
Thank you very much for reading
nzkn said:
Sorry for the confusing title. English is not my native language.
What happened is that I wanted to install Lineage OS on my phone (It have root+USB debugging and its in MM), but since I'm a noob, I ended up briking it.
It happened at the step where you should unlock the bootloader. In some way I could not achieve it, so I assumed it was because I did not know the "aboot partition" of my phone.(I still don't know what that is xd)
Long story short, I flashed the file "aboot.img" (which should go in "mmcblk0p5") in some other partition.
Yes, I know now how stupid I am ;-;
Now the phone is totally bricked.
No recovery mode, Download mode, Fastboot or Firmware mode (of which I'm aware) works. It does not even show the LG logo.
However, the phone responds to being connected to the pc (it vibrates!). It is even recognized in the Device Manager panel, as "LGE androidnet usb serial port (COM <any number>)".
It also responds when the battery is removed being connected by displaying an image on the screen.
So I conclude that the phone is not totally lost?...
The other part of the situation is that I have a spare Spirit. It's exactly the same as the other one, but it works (albeit the wifi deactivates itself every 5 seconds since a hit, so it's not useful for me).
And I was thinking if there is any way to make an exact copy of the other device or something like that? (like in a computer) Or use it in some way to save my main Spirit.
I mean, it's completely functional, apparently. It has a problem in the partitions, sure, but it seems that there is still some way to access the phone, right?
I know I'm new in this (I have some experience with computers, but little to nothing with Android devices), so I'm sorry if I just said a lot of stupid things.
But I would appreciate some help
Thank you very much for reading
Click to expand...
Click to collapse
I had a same problem like you and i had to send it for a motherboard replacement.

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

Categories

Resources