I fear I may have bricked my phone while trying to flash a custom rom. I had TWRP installed. I used it to flash LineageOS and everything seemed to be going correctly, but then I rebooted the device and it after showing the initial splash screen it just turned off again. It only shows the splash screen now if I hold down Volume down and the Power button for 20 seconds. It doesn't boot into recovery mode or download mode and I don't understand why. I don't know if there's anything that could be done in a situation like this, but if anyone might be able to help I'd really appreciate it. The device is still in warranty, but when you turn it on it says that it's not running stock software so I don't know good of an idea it would be to try to get a replacement unit. I've done that before, successfully with another samsung phone I had about 7 years ago.
mimshipio said:
I fear I may have bricked my phone while trying to flash a custom rom. I had TWRP installed. I used it to flash LineageOS and everything seemed to be going correctly, but then I rebooted the device and it after showing the initial splash screen it just turned off again. It only shows the splash screen now if I hold down Volume down and the Power button for 20 seconds. It doesn't boot into recovery mode or download mode and I don't understand why. I don't know if there's anything that could be done in a situation like this, but if anyone might be able to help I'd really appreciate it. The device is still in warranty, but when you turn it on it says that it's not running stock software so I don't know good of an idea it would be to try to get a replacement unit. I've done that before, successfully with another samsung phone I had about 7 years ago.
Click to expand...
Click to collapse
Seems it's completely bricked and will need to reflash in EDL mode
TheExploitedOne said:
Seems it's completely bricked and will need to reflash in EDL mode
Click to expand...
Click to collapse
How do I boot into edl mode?
mimshipio said:
How do I boot into edl mode?
Click to expand...
Click to collapse
Usually through test points in the back of your device. If your able to get into recovery/main OS try adb reboot edl. If not you can able make or buy a deep flash cable that sets the device into EDL mode
TheExploitedOne said:
Usually through test points in the back of your device. If your able to get into recovery/main OS try adb reboot edl. If not you can able make or buy a deep flash cable that sets the device into EDL mode
Click to expand...
Click to collapse
I opened the device but there's no documentation on where the test points are. Will any EDL cable work? As I mentioned already, the device does not boot beyond the bootloader, no matter what.
mimshipio said:
I opened the device but there's no documentation on where the test points are. Will any EDL cable work? As I mentioned already, the device does not boot beyond the bootloader, no matter what.
Click to expand...
Click to collapse
Yep it's definitely in EDL. When you plug it in do you see Qcom HS-USB 9008 (or 9006) or just Qcom USB bulk or similar? If so then that's a good sign that you can recover, but you'll need a programmer that works with your device. Yes a deep flash cable should do the trick if not already in edl
TheExploitedOne said:
Yep it's definitely in EDL. When you plug it in do you see Qcom HS-USB 9008 (or 9006) or just Qcom USB bulk or similar? If so then that's a good sign that you can recover, but you'll need a programmer that works with your device. Yes a deep flash cable should do the trick if not already in edl
Click to expand...
Click to collapse
When I plug it in nothing happens at all. Thanks for the help. I think I'll buy a cable on amazon and see if it works :good:
mimshipio said:
When I plug it in nothing happens at all. Thanks for the help. I think I'll buy a cable on amazon and see if it works :good:
Click to expand...
Click to collapse
Do you not see anything in device manager or hear a connection? Unless your on a different chipset because the PBL cannot be corrupt by software. You're welcome! If you need further help please do send me a PM and we can go from there
TheExploitedOne said:
Do you not see anything in device manager or hear a connection? Unless your on a different chipset because the PBL cannot be corrupt by software. You're welcome! If you need further help please do send me a PM and we can go from there
Click to expand...
Click to collapse
When I plug it in nothing happens at all. If I try to turn it on while it's plugged, I get the charging screen but that's it.
mimshipio said:
When I plug it in nothing happens at all. If I try to turn it on while it's plugged, I get the charging screen but that's it.
Click to expand...
Click to collapse
Hmm seems it can boot into the kernel. Do you know the specs of the device? If it's Qualcomm I can go have a look around and see what I can find to point you into the right direction
TheExploitedOne said:
Hmm seems it can boot into the kernel. Do you know the specs of the device? If it's Qualcomm I can go have a look around and see what I can find to point you into the right direction
Click to expand...
Click to collapse
It's SoC is a proprietary Samsung chip. All Samsungs use proprietary chips afaik. The A10 uses the Exynos 7884.
mimshipio said:
It's SoC is a proprietary Samsung chip. All Samsungs use proprietary chips afaik. The A10 uses the Exynos 7884.
Click to expand...
Click to collapse
I thought they would have implemented a special mode of operation if you got into a brick like that. If the device comes on with the charger then it's probably not fully bricked. I've seen other threads that have had the same issue so you may have to check them out
TheExploitedOne said:
I thought they would have implemented a special mode of operation if you got into a brick like that. If the device comes on with the charger then it's probably not fully bricked. I've seen other threads that have had the same issue so you may have to check them out
Click to expand...
Click to collapse
Really? where have you seen other people with this issue? I've looked on the A10's forums but I found nothing. Could you send me some links?
mimshipio said:
Really? where have you seen other people with this issue? I've looked on the A10's forums but I found nothing. Could you send me some links?
Click to expand...
Click to collapse
Try to look for other devices and search deeply good sir you may find what you need. I use Qualcomm devices because we have a special EDL mode and I have a programmer for all my devices to restore in the case of a hard brick like yours. I've been able to use custom tools to create a restore firmware like the Zone 2 (LG) and flash the device far enough to get it into download mode to flash the KDZ
mimshipio said:
Really? where have you seen other people with this issue? I've looked on the A10's forums but I found nothing. Could you send me some links?
Click to expand...
Click to collapse
You'll need to search with other devices or just in general. I seen posts about it being in some USB mode but Samsung probably don't have that implementation
Hello,
I am currently facing the same problem. Were you able to solve the problem?
Related
Is there any hope? I was trying to install LiquidSmooth Jellybean 4.1.2 RC8. I did a backup of the stock ROM before doing so using CWM 6.0. But now it won't even go into download mode. I plug it in via USB as the screen won't even turn on and it keeps flashing that it's plugged in, then it's not, then it is, etc.
I had used the files from AndroidJinn without reading the reviews at the bottom.
How screwed am I?
MoronDroid said:
Is there any hope? I was trying to install LiquidSmooth Jellybean 4.1.2 RC8. I did a backup of the stock ROM before doing so using CWM 6.0. But now it won't even go into download mode. I plug it in via USB as the screen won't even turn on and it keeps flashing that it's plugged in, then it's not, then it is, etc.
I had used the files from AndroidJinn without reading the reviews at the bottom.
How screwed am I?
Click to expand...
Click to collapse
How did you try to get into download mode? Power+volume down and then releasing the power button while still holding volume down?
Edit: Maybe this post will be helpful?
http://forum.xda-developers.com/showthread.php?p=24539068
Sent from my SAMSUNG-SGH-I717
developweb said:
How did you try to get into download mode? Power+volume down and then releasing the power button while still holding volume down?
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
Yes, won't even do that. No samsung boot logo either.
developweb said:
How did you try to get into download mode? Power+volume down and then releasing the power button while still holding volume down?
Edit: Maybe this post will be helpful?
http://forum.xda-developers.com/showthread.php?p=24539068
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
I'm facing quite the hard brick. $1.60 for a jig won't kill me, now to buy it. But is there anything else I can try?
I would try to find out exactly what caused this before attempting to fix it. Has the recovery that you used been reliable and tested enough to ensure it didn't cause any troubles? I compiled twrp for this device and I can tell you that recovery is a pain to build correctly.
gimmeitorilltell said:
I would try to find out exactly what caused this before attempting to fix it. Has the recovery that you used been reliable and tested enough to ensure it didn't cause any troubles? I compiled twrp for this device and I can tell you that recovery is a pain to build correctly.
Click to expand...
Click to collapse
Yes it has. Haven't had issues yet. But it happened specifically with this ROM, and the page is full of brick warnings. Not even the samsung logo comes up. Booting to recovery or download doesn't work.
MoronDroid said:
Yes it has. Haven't had issues yet. But it happened specifically with this ROM, and the page is full of brick warnings. Not even the samsung logo comes up. Booting to recovery or download doesn't work.
Click to expand...
Click to collapse
I hope you can work it out. With my own I have not had any major problems to troubleshoot. Mostly things that a battery pull or an odin flash could fix. Although I have had a couple times that I was unable to get into recovery and simply removing my otterbox and retrying did the trick. ( Buttons getting worn out on the otterbox cover? )
Sent from my SAMSUNG-SGH-I717
developweb said:
I hope you can work it out. With my own I have not had any major problems to troubleshoot. Mostly things that a battery pull or an odin flash could fix. Although I have had a couple times that I was unable to get into recovery and simply removing my otterbox and retrying did the trick. ( Buttons getting worn out on the otterbox cover? )
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
I just want to let you know, for the sake of your galaxy note, do NOT flash the 4.1.2 Liquidsmooth Jellybean RC8 ROM from the androidjinn site. It permabricks phones, down to the recovery, and even blocks download mode.
MoronDroid said:
Yes it has. Haven't had issues yet. But it happened specifically with this ROM, and the page is full of brick warnings. Not even the samsung logo comes up. Booting to recovery or download doesn't work.
Click to expand...
Click to collapse
plug it into the computer and see what it is enumerated as in the device manager.. if it shows up as "Qualcomm HS-USB QDLoader" .. youre hard bricked . I have a riff box if you need a JTAG
sinasiadat said:
plug it into the computer and see what it is enumerated as in the device manager.. if it shows up as "Qualcomm HS-USB QDLoader" .. youre hard bricked . I have a riff box if you need a JTAG
Click to expand...
Click to collapse
It appears as Qualcomm CDMA Technologies MSM. Close enough. Lol.
Have you done jtag repairs on these before?
MoronDroid said:
It appears as Qualcomm CDMA Technologies MSM. Close enough. Lol.
Have you done jtag repairs on these before?
Click to expand...
Click to collapse
yea.. a couple. I own one. and have the i717 jig for the riff box so it snaps on no soldering
sinasiadat said:
yea.. a couple. I own one. and have the i717 jig for the riff box so it snaps on no soldering
Click to expand...
Click to collapse
I'm tempted to send it to you. I've been using a semi-broken droid 3 for a while.
I'll send you a private message.
I followed the instructions provided at the MEGA UNBRICK something thread situated here http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108/
Anyway, when I hold the volume-up button for 10 seconds, followed by plugging the Onyx with the PC, the system does't detect the device. What can I do now? And is there any alternative method to unbrick a hardbricked phone? I urgently need help
If you installed the drivers and the computer is not reckognizing the device, that's bad news. How did you manage to accomplish that?
aredpanda said:
If you installed the drivers and the computer is nota reckognizing the device, that's bad news. How did you manage to accomplish that?
Click to expand...
Click to collapse
I don't know. And ijust in case if you were being sarcastic, I used the same computer to replace the recovery of this phone.
Im not being sarcastic. The problem with the Android modding scene is that people got too used to blindly following steps without really knowing how they are affecting their devices. In order to get better chances at getting help, you'll need to describe what and exactly how you were altering your phone.
aredpanda said:
Im not being sarcastic. The problem with the Android modding scene is that people got too used to blindly following steps without really knowing how they are affecting their devices. In order to get better chances at getting help, you'll need to describe what and exactly how you were altering your phone.
Click to expand...
Click to collapse
I was using Bliss ROM with BluSpark kernel. Anyway, I downloaded 2 ROMS today, Sailfish OS and the stock H2OS for OPX. I wiped the phone and first flashed the Sailfish OS, but the phone was stuck in a bootloop which only was showing the oneplus logo and the text "Powered by Anrdoid". After that, I entered recovery, and did the normal pre-flash wipe again. This time I flashed the H2OS, but after I gave "Reboot to System", my phone just wont do nor display anything. Hardbricked, dead
Can you boot it into recovery? Your bat may be dead from extensively flashing stuff, so plug the phone to the power cable and press and hold VolDown+Power for some good 30s, then you can conclude your phone wont boot into recovery and maybe need an unbrick.
aredpanda said:
Can you boot it into recovery? Your bat may be dead from extensively flashing stuff, so plug the phone to the power cable and press and hold VolDown+Power for some good 30s, then you can conclude your phone wont boot into recovery and maybe need an unbrick.
Click to expand...
Click to collapse
Yeah, it didn't boot into recovery
Does the led light up when you plug the phone to the wall? If it does let it charge for an hour before attempting anything else.
After that and before trying anything else, make sure driver signature check is off and test mode is on. This varies slightly for Windows 7/8 vs 8.1/10. Which version are you running?
aredpanda said:
Does the led light up when you plug the phone to the wall? If it does let it charge for an hour before attempting anything else.
After that and before trying anything else, make sure driver signature check is off and test mode is on. This varies slightly for Windows 7/8 vs 8.1/10. Which version are you running?
Click to expand...
Click to collapse
No, it doesn't
aredpanda said:
Does the led light up when you plug the phone to the wall? If it does let it charge for an hour before attempting anything else.
After that and before trying anything else, make sure driver signature check is off and test mode is on. This varies slightly for Windows 7/8 vs 8.1/10. Which version are you running?
Click to expand...
Click to collapse
I turned off the signature check, W8
If your led doesnt light when your phone is plugged to the wall, this is behind the hard unbricking procedure and your phone is indeed, dead.
Sent from my ONE E1003 using Tapatalk
This issue has been resolved via PM,
Can a mod please close this thread?
No idea what it could be besides corrupt firmware which I've never heard of happening before. The Qualcomm utility should work just fine. Leave it plugged in for an hour or two and see if anything happens
Did you install the qualcomm drivers? If not do it again carefully with driver enforcement off. It works like a charm. Have bricked my device twice as of now and it worked.
Hello,
I root a lot of phones and would like to have a way of unbricking my phone if it's hard bricked. By "hard bricked" I mean a phone that will not boot into Download/fastboot mode nor recovery mode. I know OnePlus has a special MSM download tool for this but what about other phones? I know that EDL mode can be used to recover from a hard brick but is this mode on Qualcomm varients of Samsung and Pixel phones? When I research about it all the phones that it talked about are Xioami phones and I don't have any Xioami phones. Also what about Exynos devices? I heard there is an Exynos USB mode for unbricking Exynos devices but how do I boot into this mode or use it? The same way as using EDL mode? Should I buy an EDL cable? Or should I get something else?
Assuming it's not a motherboard failure, a few phones can be revived with a USB Jig, a tiny device that plugs into the USB port and puts the phone into Download Mode to reinstall the stock firmware.
Mr. JAVI said:
Assuming it's not a motherboard failure, a few phones can be revived with a USB Jig, a tiny device that plugs into the USB port and puts the phone into Download Mode to reinstall the stock firmware.
Click to expand...
Click to collapse
What about Non Samsung devices? (Mainly referring to Pixels bc OnePlus already has an unbrick method)
JJcoder said:
What about Non Samsung devices? (Mainly referring to Pixels bc OnePlus already has an unbrick method)
Click to expand...
Click to collapse
I've never owned a Google Pixel so I hesitate to give any advice but maybe the link below will be of some help.
https://www.reddit.com/r/essential/comments/f8b0vk/force_edl_mode_superhard_brick/
Mr. JAVI said:
I've never owned a Google Pixel so I hesitate to give any advice but maybe the link below will be of some help.
https://www.reddit.com/r/essential/comments/f8b0vk/force_edl_mode_superhard_brick/
Click to expand...
Click to collapse
Thanks! I will probably get an EDL cable, and for Samsung I might get a USB jig.
JJcoder said:
Thanks! I will probably get an EDL cable, and for Samsung I might get a USB jig.
Click to expand...
Click to collapse
Your very welcome @JJcoder. I once had a Soft/hard bricked Sammy (dm-verity and a drk fail). I tried mt TWRP backups and flashing the factory firmware to no avail. Long story short, I finally fixed it but it was time consuming and frustrating (lol) but on the bright side I did learn alot in the process. Hope you fix your phone and best of luck
Edl flash tool
can someone please help hard bricked brand new moto edge nothing will do anything no matter what try black screen. i'll pay someone to help please!! thanks
ThirteenSeasons said:
can someone please help hard bricked brand new moto edge nothing will do anything no matter what try black screen. i'll pay someone to help please!! thanks
Click to expand...
Click to collapse
If you have a pc, see if it's in EDL Mode
Is my device in EDL Mode?
sd_shadow said:
If you have a pc, see if it's in EDL Mode
Is my device in EDL Mode?
Click to expand...
Click to collapse
it is so how do i fix please???!!1 i'll legit pay you whatever want lol
sd_shadow said:
If you have a pc, see if it's in EDL Mode
Is my device in EDL Mode?
Click to expand...
Click to collapse
it is how do i fix
ThirteenSeasons said:
it is so how do i fix please???!!1 i'll legit pay you whatever want lol
Click to expand...
Click to collapse
??
ThirteenSeasons said:
it is how do i fix
Click to expand...
Click to collapse
You have 2 possible options
1. You can wait several days for the battery to die, then connect to a wall charger.
It may boot normally, this is the safest thing to try.
2. Use a blankflash there is one available for XT2061(burton) devices
https://mirrors.lolinet.com/firmware/moto/burton/blankflash/
download the blankflash, unzip it and
run the blank-flash.bat
If the blankflash works, the device will reboot, you may need to reflash firmware with fastboot or LMSA
sd_shadow said:
You have 2 possible options
1. You can wait several days for the battery to die, then connect to a wall charger.
It may boot normally, this is the safest thing to try.
2. Use a blankflash there is one available for XT2061(burton) devices
https://mirrors.lolinet.com/firmware/moto/burton/blankflash/
download the blankflash, unzip it and
run the blank-flash.bat
If the blankflash works, the device will reboot, you may need to reflash firmware with fastboot or LMSA
Click to expand...
Click to collapse
I accidently flashed moto g power into it when it's edge +... What if neither of those fix it? It's been unplugged for days. Idk if the bttrys dead cause no screen... Do you think fixable ?
ThirteenSeasons said:
I accidently flashed moto g power into it when it's edge +... What if neither of those fix it? It's been unplugged for days. Idk if the bttrys dead cause no screen... Do you think fixable ?
Click to expand...
Click to collapse
Ok, that's info you should have shared first.
Letting the battery die won't help.
Your only option is blank flash, but no guarantee that it'll work.
Not sure how to proceed here. I had a very recent twrp installed, flashed a new ota firmware update as I have successfully a couple of times, phone restarted to twrp, I decrypted, it flashed the firmware fine then went to restart.
And that's it, completely dead, battery was at least 50% charged.
I can't enter recovery, power button held for one minute does nothing, vol+ and power, nothing, vol- and power, nothing, vol+ and vol- nothing.
Plugging in my charger, nothing, plugging into a laptop and pc, nothing. Took the back off and disconnected the battery and left it over night, nothing.
Bootloader was unlocked and usb debugging enabled.
Anyone have any other ideas what I can try here?
Also tried bridging the contacts for edl mode with battery disconnected and plugged it into USB but nothing.
Very tricky to do this though as you need 4 hands and it's possible I'm not making contact on both pins, purchased a cheap edl/deep flash cable as a last resort, if that doesn't work then I think it is toast.
Does your device have a file you’d an flash in edl (Eg. Firehose)?
Arealhooman said:
Does your device have a file you’d an flash in edl (Eg. Firehose)?
Click to expand...
Click to collapse
I may have found a couple of resources but I'm unsure of the procedure, is there any chance you could provide me with some information, I'm stumped on how to proceed.
Johnnio said:
I may have found a couple of resources but I'm unsure of the procedure, is there any chance you could provide me with some information, I'm stumped on how to proceed.
Click to expand...
Click to collapse
From what I gathered you need to find a special “firehose” or like file that allows yout o flash it in edl. You seem to have gotten very very lucky because from a simple Google search, I found firehose files. They may or may not work.
https://support.hiunlock.com/index.php?a=downloads&b=file&id=1133 I found this, but I think it may cost money (I don’t want to make a acc, but from browsing the website, it seems it costs 20 dollars, which is a barbain for a device). You are lucky it exists at all though. I do not vouch for the file or site though. You should o research on how trusted it is.
Arealhooman said:
https://support.hiunlock.com/index.php?a=downloads&b=file&id=1133 I found this, but I think it may cost money (I don’t want to make a acc, but from browsing the website, it seems it costs 20 dollars, which is a barbain for a device). You are lucky it exists at all though. I do not vouch for the file or site though. You should o research on how trusted it is.
Click to expand...
Click to collapse
Thank you, I will have a good read and look at other sources.
I'd love to know how the hell this happened, had the device for years now and flashing with zero issues.
Johnnio said:
Thank you, I will have a good read and look at other sources.
I'd love to know how the hell this happened, had the device for years now and flashing with zero issues.
Click to expand...
Click to collapse
Yeah, must have amde a small mistake, or ahd a corrupt file
“EDL is an interface of Qualcomm chipsets, used to flash fastboot ROMs. It is used for unbricking purposes so it is allowed on many phones but it's been locked down on most recent Android models.
The screen will appear black and it will appear that the device is turned off, but to verify that this is not the case, we need the tools in EDL mode. The most famous is QFIL (Qualcomm Flash Image Loader), a proprietary software, but on GitHub there are many alternative open source projects.”
https://www.thecustomdroid.com/qualcomm-edl-mode-guide/ the beginning of this article explains edl mode very well
Arealhooman said:
https://www.thecustomdroid.com/qualcomm-edl-mode-guide/ the beginning of this article explains edl mode very well
Click to expand...
Click to collapse
Excellent, thanks again for your input.
Johnnio said:
Excellent, thanks again for your input.
Click to expand...
Click to collapse
Yep, reach out if you have more questions, and keep me updated with if you managed to save your device.
Arealhooman said:
Yep, reach out if you have more questions, and keep me updated with if you managed to save your device.
Click to expand...
Click to collapse
Will do
I am late here, but just want to add i also had same issue
And edl can be fix with xiaomi third party tools with little fee to provide you authorized rom flash to boot phone from edl