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
Related
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.
Hi guys!
I think I did something stupid while updating my XT1650-03 to Nougat.
What I did was manually flash stock nougat ROM (retbr) through fastboot, following the instructions within flashfile.xml, but, as I've read some bad things about the updated bootloader I stupidly decided not to flash it. The result is that it won't power up, even though I've tried: pressing power+vol. down; power; plugging the charger; fastboot commmands ( I was hoping it was just the screen that was off); to no avail.
I've noticed that when I plug the usb cable to the computer it plays that sound of connected devices.
Any suggestions? I'm probably going to have to take my device to authorised repair (off warranty, I know), but they usually take weeks to fix anything, so you guys are my best bet for now.
Thanks in advance!
martonto said:
Hi guys!
I think I did something stupid while updating my XT1650-03 to Nougat.
What I did was manually flash stock nougat ROM (retbr) through fastboot, following the instructions within flashfile.xml, but, as I've read some bad things about the updated bootloader I stupidly decided not to flash it. The result is that it won't power up, even though I've tried: pressing power+vol. down; power; plugging the charger; fastboot commmands ( I was hoping it was just the screen that was off); to no avail.
I've noticed that when I plug the usb cable to the computer it plays that sound of connected devices.
Any suggestions? I'm probably going to have to take my device to authorised repair (off warranty, I know), but they usually take weeks to fix anything, so you guys are my best bet for now.
Thanks in advance!
Click to expand...
Click to collapse
Don't even bother going to the service center. The same happened with my device and they refused to give me the warranty. Motorola voids it the moment you get the unlock code. So my device was dead for 3 months. And I fixed it few days back. The good news is that your PC is detecting the device.
I will post the solution with a new thread in few minutes.
Manish54 said:
Don't even bother going to the service center. The same happened with my device and they refused to give me the warranty. Motorola voids it the moment you get the unlock code. So my device was dead for 3 months. And I fixed it few days back. The good news is that your PC is detecting the device.
I will post the solution with a new thread in few minutes.
Click to expand...
Click to collapse
Thank you so much for your reply, it's very much appreciated! I didn't think anyone would reply that soon
I'll wait for your thread!
There ya go
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
So, I'm totally lost.
As I posted in the thread above, even though Manish54 has been very kind to help, that solution did not work for me, so I've been trying to find another way. The thing is, this issue is beyond my comprehension. I'm not new to flashing and stuff, but I am new to moto Z. I understand that I should've been more careful and also have read a bit more before starting to mess with a new device, so feel free to judge me .
For instance, I don't know what fsg.mbm, adspso.bin, BTFM.bin and oem.img are for, since my old phone didn't have those (or at least I didn't need to mess with those), and I also don't know it they're relevant to my problem. If anyone could point me to some info on that, it'd be greatly helpfull.
Besides that, I've found mentions to tools like qualcomm's BoardDiag and QPST QFIL, but I'm not really sure if they apply for my situation, or even if I can manage to adapt the guides I've found to work on the Moto Z.
Any help is very much appreciated!
Thank you!
Solved!
I managed to unbrick my phone.
If anyone needs it, the details are in the thread made by Manish54.
https://forum.xda-developers.com/mo...rick-moto-z-hardbricked-t3590133#post71876064
Is there any way to solve it ?
Hillterpty said:
Is there any way to solve it ?
Click to expand...
Click to collapse
Did you even read the posts?
Ajuda
martonto said:
I managed to unbrick my phone.
If anyone needs it, the details are in the thread made by Manish54.
https://forum.xda-developers.com/mo...rick-moto-z-hardbricked-t3590133#post71876064
Click to expand...
Click to collapse
Amigo tb estou com o meu morto, me ajuda, qual o modelo do seu.
https://uploaddeimagens.com.br/imagens/sem_titulo-jpg--9130
hard brick moto z
Manish54 said:
There ya go
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
Click to expand...
Click to collapse
hello friends, I'm with hard brick on the moto z xt1650-3
due to an update via ota, when my bootloader was unlocked I was in the android oreo (8.0), however I went back to 7.0, due to an update via ota, the device did not call anymore, I tried several blankflash and nothing, I am very annoyed at this, thinking of dropping my hand, I took some assists nobody can solve, I hope someone here can help me, at least inform me something that is useful to recover my cell phone.
my cell phone is still recognized as "qualcomm hs-usb qdloader 9008 (com3)
please join the telegram group:
https://t.me/motozz
Hey, my phone was dead two (brazilian xt1650-03), i spent three days struggling until i could bring him back. Thanks to the help in this forum. Your phone probably has the latest update opls27-76-51-7-july, so it must work:
first, you have to bankflash it with blankflash_OPL_27.76-51, its in the 30+ page topic tutorial here in this forum. Very important, must be in windows 7 or 8, with usb2.0
second, use this rom opls27-76-51-7-july-moto-z. it must work because its the last one. Its not brazilian, evething works fine but the netflix app didnt , but hey, at least our phone is alive again.
The secret is in the version of the firmware instaled before the brick, it must be the rom installed or latest to work
Well, I tried all the "one-click" apps (I don't care if they sell my info) and none work so far...
So it's time to consult XDA. Did it years ago, doin' it now. I'm new here, but you will be happy to know I read all the rules.
Time to fix this chinese piece of crap! This is the only device I own, and I can post all the processor and system info if needed. IDK if the bootload is unlocked or not, but a guy in another post for another RCA tablet mentioned he owned this same one and they said he might not need to unlock it. So IDK. NOTE I HAVE RCT6513W87 WITH NO "M" ON THE END. DIFFERENT MODEL.
So first, what am I gonna need? USB M-2-M?
I don't have any experience using ADB, however.
Don't really know what I'm doing so far.
BUMP
BUMP
BUMP BUMP
BUUUUUUMP
@Lootron
Did you try Dr Fone?
I suggest you consult this thread for more information on rooting with or without one click tools:
https://forum.xda-developers.com/canvas-juice/how-to/guide-unlocking-bootloader-rooting-t3705781
HIT THANKS IF FOUND USEFUL
I just spent the last few hours attempting to connect it to my Windows 10 PC. Nothing. 100% Impossible. Modified registry, edited drivers, tried modified google drivers but it kept saying "Windows has determined that you already have the best drivers for this device" trieda few workarounds for that. Damn, really want this rooted but it seems impossible.:crying:
Lootron said:
I just spent the last few hours attempting to connect it to my Windows 10 PC. Nothing. 100% Impossible. Modified registry, edited drivers, bla, bla, bla. END QOUTE]
Yeah, been there. However there should be a way. There's a five second window of opportunity when you have the USB connected, have the PC in the device manager. I'm willing to bet most of the process is the same when it comes to accessing the device according to Smartman Vartans tutorial for the RCA Viking Pro. I have that, the version before it and I have the Galileo, Build Number (RCT6513W87-ANDROID6.0-V21-V1.23.30-W02). It's about time I do something with it. His method is incredibly complex from the looks of it. But I'm willing to get root at least. Sounds like it's time for experimenting. Okay, I'm in. I'll see if I can pull some resources. Enable Developer settings (tap build 7 times). In The Developer settings turn it on. Turn on OEM Unlocking (to unlock the Bootloader). Turn on USB Debugging. Go down to Select USB configuration and make sure it's at MTP.
---------- Post added at 12:23 AM ---------- Previous post was at 12:07 AM ----------
[/COLOR]The Viking Pro used a SP splash tool to see the device , I've heard it works on this. Also listed was a driver. I'll go look for the frimware hopefully we both have the same. Then there's one thing that's been making me wonder. The Viking Pro uses the exact same motherboard and components as the Acer Icona, which has current 8.0 firmware. I don't see why for the life of me why I can't float that firmware in the RCA. It's an idea. But here's the Viking Pro link,
https://forum.xda-developers.com/android/general/firmware-rca-viking-pro-rct6303w87dk-t3325158
Click to expand...
Click to collapse
I feel forced to leave a note here. Stuck on some double reply mode. Where's the delete button?
Wow!
Hey thanks, I saw you on another forum (unless Casper Young is a common name?) and you said something about usb serials being locked, but I will defintely look into this! THX!
EDIT: BTW, my build number is V08- 1.15.20
I'll bet that's me, and my actual name. Howdy Thar. Yes USB Serials appear locked by manufactuer. When I dig into the data section of my rooted Viking Pro I happened to notice they were somehow locked and I was unable to follow the pathway. I can still try. But what I think you're trying to do is gain access via USB, correct? I talked to Smartman Vartan long ago and we have one interesting delima. Okay so we can gain access, but then what? It's not like we can just throw anything in it. I have 3 different devices The Maven Pro, the Viking Pro (both are rooted) and I got this Galileo Pro. Long story short, I was looking for compatible firmware. Went old school, look at the specs. Not the ordinary ones you find anywhere, the real specs. Go here, https://www.productchart.com/tablets/11121 sign up, yeah, WOW! Okay so I compare a few things, (I'm off exploring the Viking Pro), didn't have the galileo yet. Now, come to find out, the Viking has the same exact motherboard and components as the Acer Icona 10.1 (I forget which specific one). Hmmmm, now that's intresting. Can I, just toss it in there? I don't see why not. Others here suggest otherwise. I don't flash anything without back-up That's item #1 we need if you're gonna follow along. #2? The SP Flash Tool. I have those. Now I gotta open this puppy up and check out the motherboard. Gimmie a couple days I'll get back.
I wish we could use Odin3 but here's what I got For starters. I'll write out the tutorial if I get anywhere. How to run the SP Flash Tool:
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Current SP Flashtool: https://drive.google.com/open?id=1JzB5tzTvQYOGpVfhZNKY22_N-nD-jtDA
Firmware: https://drive.google.com/open?id=1zB1waSYM0iwdobu0jdxP1WJD6r1F8-XI
MTK Drivers: https://drive.google.com/open?id=1wRdulyOKLgeT_VWbhM9tm1-hqtgSL_BD
How to install the drivers:https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
Rooting
If your intention is only to root the device you must first enable Developer Settings and then enable OEM unlock which gives you access to the Bootloader. Now you can flash in a custom recovery and then you will be able to root the device. You cannot do so by any other means. It will reject any attempt to root unless the Bootloader is unlocked!
Casper Young said:
If your intention is only to root the device you must first enable Developer Settings and then enable OEM unlock which gives you access to the Bootloader. Now you can flash in a custom recovery and then you will be able to root the device. You cannot do so by any other means. It will reject any attempt to root unless the Bootloader is unlocked!
Click to expand...
Click to collapse
Ok, I have everything, I THINK I installed the drivers, but I am waiting for it to charge to be sure. Can you be a little more clear on your instructions here? Do I flash the firmware? What order do I do everything? Custom Recovery first? Firmware first? How do I unlock the bootloader when it STILL doesn't regonize the device in ADB?
BTW, I installed the drivers by the SmartmanVartan method.
Lootron said:
Ok, I have everything, I THINK I installed the drivers, but I am waiting for it to charge to be sure. Can you be a little more clear on your instructions here? Do I flash the firmware? What order do I do everything? Custom Recovery first? Firmware first? How do I unlock the bootloader when it STILL doesn't regonize the device in ADB?
BTW, I installed the drivers by the SmartmanVartan method.
Click to expand...
Click to collapse
How do I flash the firmware? SmartmanVartan's method?
MTK drivers
Lootron said:
How do I flash the firmware? SmartmanVartan's method?
Click to expand...
Click to collapse
You have Windows 10 right?
Read this:
https://tehnotone.com/windows-10-mtk-vcom-usb-drivers-for-32-64-bit-drivers-installation-tutorial/
Casper Young said:
You have Windows 10 right?
Read this:
https://tehnotone.com/windows-10-mtk-vcom-usb-drivers-for-32-64-bit-drivers-installation-tutorial/
Click to expand...
Click to collapse
Yesterday, I tried flashing the firmware you linked to, and well, RIP. Bricked. Yours had build number .22, while I needed .15. So now I don't know if I can fix it. BTW Drivers worked and everything else. Did "fastboot oem unlock" and got to the "Do you want to unlock bootloader?" page, BUT the volume keys weren't programmed into it so you can't confirm nor deny. The bootloader needs to patched.
But before I get there, I need you to find a firmware that has .15 in the middle like this: x.15.x
Please, you are my only hope.
PS: I contacted Bogram, who patched the bootloader on the viking pro. If I can get the right firmware, then I can send it to him so he can patch it and I'm there. IF HE DOES IT.
TIA!
Brick
BTW, I think it might be a hard brick. I don't know much about bricking, but it won't even turn on, and the charging light comes on if even it isn't plugged into the outlet (SUPER WEIRD)
EDIT: When flashing, it never said completed. I waited for a really long time and then clicked stop. I really don't know too much of what I'm doing
Woouch!
Lootron said:
BTW, I think it might be a hard brick. I don't know much about bricking, but it won't even turn on, and the charging light comes on if even it isn't plugged into the outlet (SUPER WEIRD)[END QOUTE]
Wow try slowing down a bit. Sorry to hear your having difficulties with your tablet. I didn't expect you to flash it yet. No-one has provided anything to flash into it yet, I thought we were going to go looking. I'm hoping there can be a way to get past a brick. I've been reluctant to flash any of my devices for exactly the reason that you're dealing with. I didn't think to post what my firmware build number was, I'll edit that in.
I'll look for your firmware or ask RCA for it. This might take a bit. What color light is showing. And somehow try getting it to boot to recovery. Where you can reset it. Thats where the back-up is supposed to go also. There can be a variety of combinations to get there. Isn't there a reset hole to the left and a little below the micro sd slot. You may have to have it docked to get to recovery (the Viking Pro is like that). I'll do some research and see what I can find.
Click to expand...
Click to collapse
Casper Young said:
Lootron said:
BTW, I think it might be a hard brick. I don't know much about bricking, but it won't even turn on, and the charging light comes on if even it isn't plugged into the outlet (SUPER WEIRD)[END QOUTE]
Wow try slowing down a bit. Sorry to hear your having difficulties with your tablet. I didn't expect you to flash it yet. No-one has provided anything to flash into it yet, I thought we were going to go looking. I'm hoping there can be a way to get past a brick. I've been reluctant to flash any of my devices for exactly the reason that you're dealing with. I didn't think to post what my firmware build number was, I'll edit that in.
I'll look for your firmware or ask RCA for it. This might take a bit. What color light is showing. And somehow try getting it to boot to recovery. Where you can reset it. Thats where the back-up is supposed to go also. There can be a variety of combinations to get there. Isn't there a reset hole to the left and a little below the micro sd slot. You may have to have it docked to get to recovery (the Viking Pro is like that). I'll do some research and see what I can find.
Click to expand...
Click to collapse
Whoops. Yeah I'm sorry, I've always been a bit hasty. I have looked for my firmware, but would RCA give it to you? I forgot to say my processor is MT6513. Not MT6127.
Well, thanks for spending so much of your time for me though. You have been very helpful. For me, bricking it was a learning experience. I learned a LOT about how android works messing with this tablet, and come on, it was a crap-let I only decided to
"hack" it once we ordered a new one (The keyboard doesn't work anymore)
The day I did it, I got frustrated I couldn't unlock the bootloader, so I wanted to do something else, without thinking about it. LOL. Well, more learning for me!
The only light it ever does it bright blue, and it no longer does it without being plugged into the outlet. Oddly enough, I didn't think to use the reset button, and in device manager it still shows up as preloader device, even though I suspected to be the preloader to be corrupted. There really shouldn't be a reason it won't start now. Also for some reason, ADB never has regonized this device, unless in fastboot mode.
Click to expand...
Click to collapse
Lootron said:
Casper Young said:
Whoops. Yeah I'm sorry, I've always been a bit hasty. I have looked for my firmware, but would RCA give it to you? I forgot to say my processor is MT6513. Not MT6127.
Well, thanks for spending so much of your time for me though. You have been very helpful. For me, bricking it was a learning experience. I learned a LOT about how android works messing with this tablet, and come on, it was a crap-let I only decided to
"hack" it once we ordered a new one (The keyboard doesn't work anymore)
The day I did it, I got frustrated I couldn't unlock the bootloader, so I wanted to do something else, without thinking about it. LOL. Well, more learning for me. [End Qoute]
Welcome to the place where you gotta play it safe. Yes RCA does provide the firmware, here;s your like for that.
https://stockromfiles.com/download-rca-stock-rom/
Now what I don't understand is why RCA implies there's no different versions of the software and you have a possible bricked device. I have a few articles that say even if your bricked you can flash in the software. Here's the tutorial for using the SP flash tool and another software location. The Tutorial makes me wonder though because if you look at steps 1, 2 and 3 they're questionable, especially #3. I'll get back to you in a bit, gotta chore to do.
https://stockromfiles.com/rca-rct65...323c6df5dcc913b1e77a5c8f2bbfe10#comment-53815
Oh, and you have yet to learn about playing with Androids These RCAs don't count. They're completely different from flashing a Samsung Galaxy or any other Androids.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
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?
hey as per my username i'm no good at this but i got this far. so I got all the files together did sd _shadow's guide unlocked bootloader etc., RSA method doesn't work for me so i am trying the regular fastboot option but my phone cant do fastbootd also my CPU is QUALCOMM
so can i run the flashfile.bat via regular fastboot or will it brick my phone.
well forget it i hard bricked it living up to my name.hopefully ill get it fixed
purenoob said:
well forget it i hard bricked it living up to my name.hopefully ill get it fixed
Click to expand...
Click to collapse
bricked can mean several different things.
No sign of life?
Window PC?
sd_shadow said:
bricked can mean several different things.
No sign of life?
Window PC?
Click to expand...
Click to collapse
no sign of life, no power no charge, i'm on windows if plugged in its detected in the device manager.
can this be fixed by anyone i feel really bad, i know it's just a phone but ya know.
purenoob said:
if plugged in its detected in the device manager.
Click to expand...
Click to collapse
That is a sign of life
Is my device in EDL Mode?
sd_shadow said:
That is a sign of life
Is my device in EDL Mode?
Click to expand...
Click to collapse
in device manager it says quadcomm hs-usb qdloader 9008. so by the looks of this it's a candidate for EDL mode .
i don't want to mess up anymore i think ill give this to a technician. gonna be a while is it ok to let the battery die.
came across a blank flash my phone is RETLA but the flash is RETBR does it matter ?
purenoob said:
came across a blank flash my phone is RETLA but the flash is RETBR does it matter ?
Click to expand...
Click to collapse
If the bootloader is unlocked it should be fine.
Don’t worry about the battery, edl is very low power, battery can last weeks, and should still support charging
sd_shadow said:
If the bootloader is unlocked it should be fine.
Don’t worry about the battery, edl is very low power, battery can last weeks, and should still support charging
Click to expand...
Click to collapse
bootloader was unlocked before all of this happened, so does this mean i can use a android 10 back flash or use an android 11 one for avoid trouble again.
sd_shadow said:
If the bootloader is unlocked it should be fine.
Don’t worry about the battery, edl is very low power, battery can last weeks, and should still support charging
Click to expand...
Click to collapse
ok so now i'm getting this error.
Opening device: \\.\COM5 [ 0.002] Detecting device [ 34.509] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error [ 34.510] Check qboot_log.txt for more details [ 34.511] Total time: 34.514s FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
YES!! finally i got it into flashboot mode i just had to hold the pwr button 10 sec and tried blackflash again.
now im gonna dl RSA to get the correct stuff for my phone.
Might be to early to say but Thank you so much for the help!. ill post back later to update you.
update: success on flash still on a11 dont care its working again money saved.
i Wanted to downgrade becuase since this update my YouTube at higher resolutions would stutter and some of my main games started to chug in certain places.
phone lil hotter etc you know the woes oh well its working now thanks a million thanks again.
purenoob said:
YES!! finally i got it into flashboot mode i just had to hold the pwr button 10 sec and tried blackflash again.
now im gonna dl RSA to get the correct stuff for my phone.
Might be to early to say but Thank you so much for the help!. ill post back later to update you.
update: success on flash still on a11 dont care its working again money saved.
i Wanted to downgrade becuase since this update my YouTube at higher resolutions would stutter and some of my main games started to chug in certain places.
phone lil hotter etc you know the woes oh well its working now thanks a million thanks again.
Click to expand...
Click to collapse
Hey just reporting back i thought i could bear with android 11 but i just couldn't. Being really really carefull this time i managed to return to android 10.
Using the fastbootd method before i ignored it and flashed in regular fastboot. So this time i followed every step to a tee.
just wanted you too know and as all always thx sd_shadow.