Related
I think I fucced up pretty badly this time...
I was on LOS, wanted to get back to stock, for some reason wiped and rebooted...
Infamous DFU mode. I can't get to FTM (tried power + vol down and it only turns on, scrolls a little and turns off), and I wasn't able to use axon7tool using zadig. No recovery at all, no fastboot, nothing...
I've installed QDLoader 9008 drivers and MiFlash actually recognizes the... thing. Can anyone tell me if this is worth trying/what I have to do? Thanks
P.S I have no way of returning it to ZTE
Edit: The miflash thing didn't work as expected, can't find programmer file
Look like you kill yourseft this time.
You have to enter EDL with any cost, or at less FTM - let batttery drain up and try again.
Otherwise, people say somethings about a DIY EDL cable, but I not really sure
tamahouse02 said:
Look like you kill yourseft this time.
You have to enter EDL with any cost, or at less FTM - let batttery drain up and try again.
Otherwise, people say somethings about a DIY EDL cable, but I not really sure
Click to expand...
Click to collapse
I've found this QPST thing from Qualcomm, also heard that the only thing missing is the programmer which is not released. It detects my device, reports it is a Sahara Memory Dump, and that's pretty much that. I hope that people is actually looking into this
Also I noticd that in the first seconds when it is seemingly installing, it says it is a Sahara Download. Does that help?
I also wanted to know, is there a main thread for this sort of thing? I've seen @tenfar 's thread but there is nothing to do on A2017G's
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
I know you're already active in this thread, but I don't know if you understand it in depth. You must open your device to enter into edl mode. In edl you can flash twrp and are back in business. So your only way to enter edl is to open your brick as described.
Thank you, however i wanna be extra cautious here. When I have to connect the test point to ground, do I connect it with the SIM slot? What is valid as ground?
If MiFlash recognizes it you should be able to flash a stock Rom. The I have the A2017U so I could be wrong
supergear said:
If MiFlash recognizes it you should be able to flash a stock Rom. The I have the A2017U so I could be wrong
Click to expand...
Click to collapse
It's all done, thank you though. I disassembled the whole thing and did the short to ground thing, and after literally 30 tries it flashed the damn thing
Guys need help....I recently bought a Samsung S8 (t-mobile version) without knowing much of its history thinking it had a deeply discharged battery, but after a good 10 hrs on the charger it still won't turn on, no LEDs, no vibration, nothing, a complete black screen so it will NOT boot into recovery or download mode. However, it does seem to take a charge as the back side does get a bit warm when charged. When plugged into the PC (Win 10) it does not get recognized under My PC but I hear the USB plug-in chime and under the Device Manager, I get "Qualcomm HS-USB QDloader 9008" on COM port 3. From what I've found online, seems like I will need the original S8's complete eMMC image and load it onto the sdcard and recover it that way, even if it's possible.
Can anyone help/guide me in the proper direction? Really hoping to recover this device. This might even help others who may have or will brick their S8's. Hope we can find root soon if that's what's needed to fix this. Thanks a lot in advance
Anyone?! There has to be someone who can help me out here....
Display broken? For not getting an image when you plug in the power?
Have you tried pressing volume-down+bixby+power button for a full 10 seconds?
Verstuurd vanaf mijn SM-G955F met Tapatalk
Root is definitely not what you need to fix this device, root would be something to access the system on a fully functional device to begin with. Maybe try the Odin carrier switch method and see if that recognizes the device.
Where did you buy the device and what did they say was wrong with it? Do you have no option of returning it because it very well my have been messed with and have Knox tripped anyways.
Bisquit-02 said:
Display broken? For not getting an image when you plug in the power?
Have you tried pressing volume-down+bixby+power button for a full 10 seconds?
Verstuurd vanaf mijn SM-G955F met Tapatalk
Click to expand...
Click to collapse
Display is in like new condition, not even a blemish. No image upon power or on the wireless charging pad, the battery does get a bit warm when charging for few hours.
Yes, I have tried that exact combo for a good 60 seconds but nothing.
Either the battery is dead or a loose connection on the charger outlet.
Either way, it doesn't charge.
Verstuurd vanaf mijn SM-G955F met Tapatalk
whoamanwtf said:
Root is definitely not what you need to fix this device, root would be something to access the system on a fully functional device to begin with. Maybe try the Odin carrier switch method and see if that recognizes the device.
Where did you buy the device and what did they say was wrong with it? Do you have no option of returning it because it very well my have been messed with and have Knox tripped anyways.
Click to expand...
Click to collapse
The reason I commented about root was then someone can get a backup of the eMMC or a backup of the bootloader, so I can flash that, if that possibly fixes it. From what I can understand, something got corrupted and for that reason the device will not boot at all (nothing on the screen), so Odin is out of the question, since the device has to be in the Download mode for Odin to recognize it.
What I have found from further reading is that I can use QFIL (Qualcomm Flash Image Loader) to flash stock firmware since it recognized the S8 on COM port 3 when connected and QFIL recognized "Qualcomm HS-USB Qloader 9008" message, but what I have seen is people using MBN files (firehose.MBN) and an XML file to revive the phones. I've tried looking for those files even within the S8's stock firmware (AP, BL, CSC) but nothing.
Is there anyone who has experience working with QFIL who can guide me or provide with the files I need to flash this device back to stock.
Bisquit-02 said:
Either the battery is dead or a loose connection on the charger outlet.
Either way, it doesn't charge.
Verstuurd vanaf mijn SM-G955F met Tapatalk
Click to expand...
Click to collapse
Appreciate your input but it does charge
taj786 said:
Appreciate your input but it does charge
Click to expand...
Click to collapse
If u can return it go do it, thats not a issue that can be solved here im guessing is a hardware conection/display issue. If u cant reach download mode then i think u cant get help here
This is not hardware issue or anything like it. What youve done, same as I have, is wiped the download and recovery partitions of the phone. QFIL can fix this, but same as you I have not found the required files. I did find the programmer firehose but its an efl. I can not find the meta file it apparently needs. Did you ever fix this
taj786 said:
Guys need help....I recently bought a Samsung S8 (t-mobile version) without knowing much of its history thinking it had a deeply discharged battery, but after a good 10 hrs on the charger it still won't turn on, no LEDs, no vibration, nothing, a complete black screen so it will NOT boot into recovery or download mode. However, it does seem to take a charge as the back side does get a bit warm when charged. When plugged into the PC (Win 10) it does not get recognized under My PC but I hear the USB plug-in chime and under the Device Manager, I get "Qualcomm HS-USB QDloader 9008" on COM port 3. From what I've found online, seems like I will need the original S8's complete eMMC image and load it onto the sdcard and recover it that way, even if it's possible.
Can anyone help/guide me in the proper direction? Really hoping to recover this device. This might even help others who may have or will brick their S8's. Hope we can find root soon if that's what's needed to fix this. Thanks a lot in advance
Click to expand...
Click to collapse
No no no, display is fine, odin will not help you. Your phone is in a mode called edl. This happens when your bootloader is corrupt or unbootable for some reason. The bad news is this typically called a hard brick, as it requires special software to recover from that isnt available typically to the public.
Absolutely agree with the poster who said try and return it. This mode is very difficult to recover from, if its at all possible. There are tools that some of us have that might be able to recover it, but they havent worked on v2 bootloaders so far. The sdcard stuff doesn't work with the s8 as it was turned off due to security issues.
Let me know if you cant return it and I'll see what i can do, but no promises
partcyborg said:
No no no, display is fine, odin will not help you. Your phone is in a mode called edl. This happens when your bootloader is corrupt or unbootable for some reason. The bad news is this typically called a hard brick, as it requires special software to recover from that isnt available typically to the public.
Absolutely agree with the poster who said try and return it. This mode is very difficult to recover from, if its at all possible. There are tools that some of us have that might be able to recover it, but they havent worked on v2 bootloaders so far. The sdcard stuff doesn't work with the s8 as it was turned off due to security issues.
Let me know if you cant return it and I'll see what i can do, but no promises
Click to expand...
Click to collapse
Looks like I've done the same thing with S8+ G955F. I was trying to fix an FRP issue and flashed a mixture of Nougat 7.0, combination and CRED BL and now it just shows black screen, can't get to download mode. This was all done with Odin.
Bisquit-02 said:
Display broken? For not getting an image when you plug in the power?
Have you tried pressing volume-down+bixby+power button for a full 10 seconds?
Verstuurd vanaf mijn SM-G955F met Tapatalk
Click to expand...
Click to collapse
taj786 said:
Guys need help....I recently bought a Samsung S8 (t-mobile version) without knowing much of its history thinking it had a deeply discharged battery, but after a good 10 hrs on the charger it still won't turn on, no LEDs, no vibration, nothing, a complete black screen so it will NOT boot into recovery or download mode. However, it does seem to take a charge as the back side does get a bit warm when charged. When plugged into the PC (Win 10) it does not get recognized under My PC but I hear the USB plug-in chime and under the Device Manager, I get "Qualcomm HS-USB QDloader 9008" on COM port 3. From what I've found online, seems like I will need the original S8's complete eMMC image and load it onto the sdcard and recover it that way, even if it's possible.
Can anyone help/guide me in the proper direction? Really hoping to recover this device. This might even help others who may have or will brick their S8's. Hope we can find root soon if that's what's needed to fix this. Thanks a lot in advance
Click to expand...
Click to collapse
Good morning, my S8 and the same happened to me, to downgrade the oreo to the nougat; I did a JIG with resistors; When you download the keys, the JIG does not work on time, then after; I do not know how to say why.
then it means im doomed.. im experiencing the same shiiit
\
Hey
So I was flashing android 7.0 to an S8 and it completely died, this is how completely:
- No screen/LED/vibration motor
- No safety/recovery/download mode (and don't ask about button combos, I've tried them all)
- No USB recognition from device manager (not even as exynos in other devices, just nothing)
- USB jig does nothing
- It is however recognised by wireless chargers (but I doubt that has any real significance)
At this point my question is would a JTAG even work on it? Or is my only hope a complete motherboard replacement?
S8 Hard bricked
A_Bad_Marksman said:
Hey
So I was flashing android 7.0 to an S8 and it completely died, this is how completely:
- No screen/LED/vibration motor
- No safety/recovery/download mode (and don't ask about button combos, I've tried them all)
- No USB recognition from device manager (not even as exynos in other devices, just nothing)
- USB jig does nothing
- It is however recognised by wireless chargers (but I doubt that has any real significance)
At this point my question is would a JTAG even work on it? Or is my only hope a complete motherboard replacement?
Click to expand...
Click to collapse
hello!
same happened to me ......dont worry i will help u....
i think u flashed aosp rom
phone is not hard bricked its still not turned off believe me........
do the following:
donot charge phone for atlesat 24 hours .......
after 24 hours try to boot into download mode press button for like a minute it will work in multiple tries,,
immediately flash twrp and when flashed successfully suddenly press vol down + bixby + power it will boot into recovery
charge for 1 -2 hours , clear system and every thing if you have backup thats good other wise flash firmware......donot turn in till flashing the system and data in recovery mood......boot into download mood from recovery and there you go....if still a problem inbox me
Thanks, I'll give it a shot
ok let me know then
Jtag dead phone to life and rewrite IMEI
I had the same thing, sent it to Fonefunshop in England, they said they could fix it, the didn't even open it as discovered by the guys who fixed it and is necessary to use jtag.
Fonefunshop said eMMC chip was bad, which is not true, but that led me to search for someone to replace the chip. I found A2Z cellular in Ottawa, Canada. They got the phone to boot up, but IMMEI was null( I did this trying to flash back to stock after TWRP screwed up). They rewrote original IMEI , now phone works like new. These guys are amazing.
http://a2zcellular.com/
Thank you all for the advice.
But I have now managed to unbrick and reflash the firmware. khawarjaved's advice turned out to be what fixed it in the end.
That was close, nearly lost £30
A_Bad_Marksman said:
Thank you all for the advice.
But I have now managed to unbrick and reflash the firmware. khawarjaved's advice turned out to be what fixed it in the end.
That was close, nearly lost £30
Click to expand...
Click to collapse
I have been through that situation man.... So always ready to help, ??
Hi pros
I'm in kind of a similar situation....I think I flashed MY 950U PIE with wrong BL
This phone is dead....Doesn't boot...no download mode....No recovery mode....
When connected to pc....device manager Recognises device as QUALCOMM HS USB 9008
Any way to brig it back to life...?
Your phone is connected in edl download mod. It will accept special files which will allow it to boot to download mode and let you flash stock firmware
The tool used for this is emmcdl.exe
It has to come with phone specific files
No idea where to get it. Ask people here, those who root phones. They know.
Hello!
THink I have bricked my phone, but just checking before I go through what I suppose is a long process with oneplus.
Looking for any help. I had a working device - unlocked bootloader and installed TWRP and magisk using MauronofrioTool. ok - however, I found out I couldn't use a fingerprint security option on that would have been anoying. So... Long story short. I used MauronofrioTool to relock bootloader. Oops - so that didn't work. THen found out I couldn't do anything except stare at g.co/ADH message on my screen. Couldn
't get to fastboot or TWP. ANyway, so I managed to up and down volume and enter into TWRP. Was still connecting to the tool, so I downloaded factory Zips and tried to install via tool after unlocking - Seemed to be working ... but it stopped mid way through a process and hasbn't come back! NOthing at all. I wonder if I could have triggered an OEM thing? ANyway - literally nothing no buttons work no screen action. I see a QUSB_BULK_CID:etc number when connecting the phone, but that is it. No fast boot or any other actions available.
PLease, pretty devastating, Anyone know if I can do anything?
I'm no pro but I use this tool which helped me:
henk-jan said:
I'm no pro but I use this tool which helped me:
Click to expand...
Click to collapse
Thank you. I feel I am little past this stage now though.. Also trying the brick reprieve software . Just can't get my computer to recognise the phone now. No ability to get to emergency download path - think it is my crappy cihinese pc (old Huawei tablet basically) or Windows via apple that have me stranded.
**********SOLVED
THe crappy Chinese language Windows tablet worked as the unbrick OP said WIndows would. Must be a kink in the Windows via Mac that could get me into the situation, but not out.
Very relieved... Even though I still am not 100% sure what I actually ended up clicking to get it to register and connect with the unblock tool (which of course was in Chinese) hahaha.
Cheers
CHeers though
Glad you got it sorted out! Cheers
Need Help, please
Just received my OnePlus 8 pro, decided to Root and unlock the bootloader---this went fine.
I then went and upgraded to Android 11 DP3.
I'm now only able to get into Fastboot. at points it will try to boot but only get to the logo screen and then goes black.
When the phone boots up, it goes to Qualcomm CrashDump Mode.
I've been attempting to solve this for half the day with no luck. I've tried Msmtool, but it doesn't recognize the device, even after loading drivers again.
Is there a way to load a ROM from fastboot mode?
Hoping someone can assist, this is super frustrating and I would appreciate any help, please.
Rick
rickhurl said:
Just received my OnePlus 8 pro, decided to Root and unlock the bootloader---this went fine.
I then went and upgraded to Android 11 DP3.
I'm now only able to get into Fastboot. at points it will try to boot but only get to the logo screen and then goes black.
When the phone boots up, it goes to Qualcomm CrashDump Mode.
I've been attempting to solve this for half the day with no luck. I've tried Msmtool, but it doesn't recognize the device, even after loading drivers again.
Is there a way to load a ROM from fastboot mode?
Hoping someone can assist, this is super frustrating and I would appreciate any help, please.
Rick
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-8-pro/how-to/rom-stock-fastboot-roms-oneplus-8-pro-t4083997
cultofluna said:
https://forum.xda-developers.com/oneplus-8-pro/how-to/rom-stock-fastboot-roms-oneplus-8-pro-t4083997
Click to expand...
Click to collapse
Thanks so much. I ended up getting Msmtool to work. Although my device wasn't on (black screen) and it didn't fully show up in the tool, I decided to start the process anyway and it began to load.
I've been on here for over 10 yeas (XDA) I've just lost my account info and made a new one.
Thanks for taking the time to respond. Much appreciated.
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