Related
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.
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
Has anyone any idea on how to get out of this situation. Device totally unresponsive, screen is black blank and displays nothing irrespective of button press combinations, including EDL. Not that its of any consequence now but this was achieved by my flashing a data file onto and overwriting the "aboot protected partition"
Device cannot be switched "on" and therefore is not recognized by windows device manager. Windows has all drivers installed i.e. ZTE - Qualcomm - Qualcomm EDL, although this is rather a moot point considering the device won't switch on.
The following files are still alive both on my device external SD card and in a windows "C:" folder --- B20 file, B27 file, B29 file, B15 file, plus a TWRP backup. To repeat myself all and every button combination has been used to no effect.
I rather much doubt that I shall get an answer to this question but has anyone any idea as to how I can get in the position where I can flash any of the above files?
Attempt to put it in edl mode I believe there is an unbrick guide somewhere around here. Aboot is related to bootloader so your phone is bricked.
Do you hear any sound from the PC when you connect the phone? This is particularly important because with the "wrong" driver enabled your device may not show in Device Manager, but it most likely, may have booted into EDL mode. Please check this and post back. If there's a sound on connect, there is hope. Nothing ZaDig and the new unbrick guide can't help you fix. I was in a similar hopeless situation a few weeks back but I resolved it with the help of the unbrick guide.
@george241312 ... @KwesiJnr ... I appreciate your answers and thank you for bothering to reply.
george ... Sad to say I was fully aware of what I was doing when I overwrote the "aboot" partition and anticipated ending up in something like my present situation. I have one final line of help to try before giving up all together.
Kwesi ... The only sound my device made was agonizing screams as I totally bricked it.
THANK YOU ALL BUT NO MORE REPLIES IF YOU PLEASE - CONSIDER THIS MATTER CLOSED ..... The device is dead due to my own stupidity and I will just live with that.
Try connecting the phone to another computer or wall charger ?
First of all, I would like to point out that the XDA Developers website has made this problem harder than it needed to be. This post is originally from Stack Exchange, but people said I would have more luck here with this problem. But every little thing I do it a problem. Try to use a proxy on the website? Nope. Try to post this in the Samsung Galaxy S7 section, where it's SUPPOSED to be? Nope. I know it's all to prevent spam, but I mean come on. Be a little lenient here. Anyways, I'm done with my rant. Back to the post.
I have made the mistake of trying to root my phone. Which is fine, but it's a lot more complicated than I thought it was, but since I have asperger's, once I start something, I feel like I have to finish it.
I have a Samsung Galaxy S7 (SM-G930U) with Sprint. I've heard that these phones are EXTREMELY difficult to root. Some even call it impossible. But I can at least try.
I ended up getting tunneled down a endless loop of tasks to complete before I actually root my phone, for preparation. One of the things I must complete is I have to install a TWRP Recovery Image in case of failure. But in order to do that, I have to unblock the bootloader.
To do this, I am using Platform Tools, with includes ADB (Android Debugging Bridge), and Fastboot. I connect my phone to my PC via USB cable, open the CMD, and type:
adb reboot bootloader
Once I do this, my phone reboots into the bootloader, just like it should. Normally, the next step I would take would be to type in:
fastboot oem unlock
When I do this, I am left with the message:
< waiting for any device >
I'm assuming that means that it's not detecting my phone at all. It's odd though, because it was able to detect my device perfectly fine whenever my phone was booted normally, but when I go into the bootloader, it doesn't detect my phone anymore.
After hours of searching around the internet, I found that a potential problem could be the drivers of my phone that are installed on my PC.
Sure enough, if I open up the Device Manager, when in the bootloader, under Universal Serial Bus Controllers, I found the driver "SAMSUNG Mobile USB CDC Composite Device", with a little yellow arrow next to it on the icon.
If I double-click on the entry, in the "Device Status" box, it will say:
This device cannot start. (Code 10)
An invalid parameter was passed to a service or function.
Code 10 means that Windows is saying "There's a problem, but I don't know what." And well, I'm stumped by this.
The drivers work perfectly fine if I'm booted normally, which is why I'm confused. In the meantime, I'll continue my rampage across the internet for a solution to this problem that actually WORKS.
If you're wondering, I using Windows 10.
TheEthanMaverick said:
First of all, I would like to point out that the XDA Developers website has made this problem harder than it needed to be. This post is originally from Stack Exchange, but people said I would have more luck here with this problem. But every little thing I do it a problem. Try to use a proxy on the website? Nope. Try to post this in the Samsung Galaxy S7 section, where it's SUPPOSED to be? Nope. I know it's all to prevent spam, but I mean come on. Be a little lenient here. Anyways, I'm done with my rant. Back to the post.
I have made the mistake of trying to root my phone. Which is fine, but it's a lot more complicated than I thought it was, but since I have asperger's, once I start something, I feel like I have to finish it.
I have a Samsung Galaxy S7 (SM-G930U) with Sprint. I've heard that these phones are EXTREMELY difficult to root. Some even call it impossible. But I can at least try.
I ended up getting tunneled down a endless loop of tasks to complete before I actually root my phone, for preparation. One of the things I must complete is I have to install a TWRP Recovery Image in case of failure. But in order to do that, I have to unblock the bootloader.
To do this, I am using Platform Tools, with includes ADB (Android Debugging Bridge), and Fastboot. I connect my phone to my PC via USB cable, open the CMD, and type:
adb reboot bootloader
Once I do this, my phone reboots into the bootloader, just like it should. Normally, the next step I would take would be to type in:
fastboot oem unlock
When I do this, I am left with the message:
< waiting for any device >
I'm assuming that means that it's not detecting my phone at all. It's odd though, because it was able to detect my device perfectly fine whenever my phone was booted normally, but when I go into the bootloader, it doesn't detect my phone anymore.
After hours of searching around the internet, I found that a potential problem could be the drivers of my phone that are installed on my PC.
Sure enough, if I open up the Device Manager, when in the bootloader, under Universal Serial Bus Controllers, I found the driver "SAMSUNG Mobile USB CDC Composite Device", with a little yellow arrow next to it on the icon.
If I double-click on the entry, in the "Device Status" box, it will say:
This device cannot start. (Code 10)
An invalid parameter was passed to a service or function.
Code 10 means that Windows is saying "There's a problem, but I don't know what." And well, I'm stumped by this.
The drivers work perfectly fine if I'm booted normally, which is why I'm confused. In the meantime, I'll continue my rampage across the internet for a solution to this problem that actually WORKS.
If you're wondering, I using Windows 10.
Click to expand...
Click to collapse
I am having similar problems with my Galaxy S7. In order to make any significant changes, the bootloader MUST be unlocked FIRST. Hence, the dilemma, if you can't make changes without an unlocked bootloader, and you can't unlock the bootloader, what can be done.
As far as I know Samsung devices simply don't have no fastboot support. Refer to Odin flashing tool instead.
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