Related
So, i tried flashing the lollipop upgrade with flashfire and bricked my phone.
When I boot s4 into bootloader mode it says
" SAMSUNG custom" with a unlocked paddle lock. then next screen says "exclamation mark in Yellow triangle" underneath; System software not authorized by AT&T has been found on your phone......
When I boot my s4 into Downloading mode windows gives me this...
"the last USB device you connected to this computer malfunctioned, and windows does not recognize it"
(all computers I've tried, different cables, different ports)
I know many people have asked this same question, but I've tried all the options.
after looking up usb Code 43 Error, the Samsung driver is telling windows that the device is malfunctioning.
is ther anyone who can help me?
K so from what I read quickly uve installed a non Loki patched kernel? Or non stock kernel and u cant get computer to see the phone? You could try loading up the stock kernel or a lokied one u know works on an SD card if u have one and flash threw recovery. I read one guy was able to get in to recovery after multiple trys so u might wanna try that. I'm just going off of what I've read I'm a lucky one and don't have to deal with a locked bootloader so I might be just blowing smoke just an idea.
xstokerx said:
K so from what I read quickly uve installed a non Loki patched kernel? Or non stock kernel and u cant get computer to see the phone? You could try loading up the stock kernel or a lokied one u know works on an SD card if u have one and flash threw recovery. I read one guy was able to get in to recovery after multiple trys so u might wanna try that. I'm just going off of what I've read I'm a lucky one and don't have to deal with a locked bootloader so I might be just blowing smoke just an idea.
Click to expand...
Click to collapse
I'm pretty sure i damaged the bootloader recovery. my best bet is to somehow get through with USB.
Well if u cant get back into recovery and usb can't see on PC then I don't know what to suggest that really sucks I feel sorry for u I been there bricked a few phones and it sucks
I just bought a BNIB Note 3.
Samsung Note 3: SM-N900W8
Symptoms: Won't turn on, no lights, no load screen, no recovery mode, no download mode.
When I hook the phone up to the PC via USB it does vibrate and sounds the connection ringtone
What I was doing when this happened:
I had just recently rooted using "KINGRoot" - checked root and it was successful
I installed "TWRP" and booted into recovery mode and it was a success as well(I didn't actually run here yet)
***I installed and opened "Flashfire" to Flash the LINEAGE OS to my Rom buuut I didn't actually select the Lineage pack and I accidently pressed FLash(insert expletive here) *****
So Flashfire went through it's loading and when it was done it shut off and then the symptoms started.
It's a Note3 from Bell with all of their bloatware on it and I wanted to clean it all off and run a clean/efficient Note 3 cell with Rogers. I'm not looking to keep any of the data currently on the phone as there isn't anything currently on it. I just want to be able to install Lineage and use my Note.
I've searched for 30 hours pretty solid so far and unfortunately I haven't come across a clear solution. Can anyone give me a diagnosis and a tutorial or a link to a fix.
I'm open to loading from MicroSD, USB Jig, Samsung Kies....anymore information you require from me as away and I'll get back ASAP
Dead battery would be first check .
JJEgan said:
Dead battery would be first check .
Click to expand...
Click to collapse
Battery - I did the "spin" test on the battery and it doesn't show any physical characteristics of an overheated(bulged) battery. I'm going to test fit my battery into another note3 and I'll respond asap.
JJEgan said:
Dead battery would be first check .
Click to expand...
Click to collapse
I tried the battery in another Note3 and my battery is 52% charged and had no issues booting the tester phone.
I have the phone being tested for any Hardware issues right now.
If it's not a hardware issue will I be able to force a Rom(whether OEM Firmware or other) to install via MicroSD or USB jig?
When the phone is connected to a Windows machine, does a new device appear in device manager?
Have you tried to force it into download mode with a USB jig?
For flashing ROMs to the sm-n900w8, the simplest method is to flash TWRP, boot to TWRP, wipe everything, and flash the desired ROM.
If nothing works, you could take it to a cell repair shop and hopefully have it repaired with a jtag cable or a similar method.
audit13 said:
When the phone is connected to a Windows machine, does a new device appear in device manager?
Have you tried to force it into download mode with a USB jig?
For flashing ROMs to the sm-n900w8, the simplest method is to flash TWRP, boot to TWRP, wipe everything, and flash the desired ROM.
If nothing works, you could take it to a cell repair shop and hopefully have it repaired with a jtag cable or a similar method.
Click to expand...
Click to collapse
No, the PC doesn't see the phone.
The USB jig or MicroSD force is something I'm researching to try next(feel free to provide any good links to set up a jig(I've done this with Ubuntu on my laptop but this has a more intimidating feel to it)). The Tech at the shop I took it to test the hardware says "the motherboard" is broken and he'll fix it for $60.
For future considerations I'll learn to use TWRP flashing ROMs.
If the shop is offering to fix it for $60, they may be just force-flashing the firmware with something like an Octopusbox.
The USB jig may force the phone into download. If it doesn't, I don't think you'll have a choice but to pay to have it flashed. Unfortunately, Samsung will not help as rooting would trip the knox counter.
USB jig ebay are the usual cheap source.
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 I am posting in Q&A because I'm a new XDA user, I was not allowed to post in the dev channel.
I have an Essential phone that has been working great for the past few years, no issues, and it was running standard build receiving OTA updates, until the very last update, which soft bricked the phone.
The phone was never enabled in developer mode while in Android, and now, I can't boot the phone into android at all. The only thing I can do is get into fastboot.
Fastboot state shows DEVICE STATE - locked
Any commands I try to unlock flashing, or change slots, anything at all, I get the error that the device is locked so all commands to unlock fail.
Is there any way to unlock device state from fastboot? I saw a youtube video showing a way to use a chopped USB cable to enter emergency / EDL mode for Qualcomm-based Android devices, but have not seen anyone post that this was successful with the Essential
Does anyone know of any method to be able to unlock flashing from fastboot? Or any other method to un-brick an essential? I've attempted everything, on both Mac and PC, nothing works.
On mac or PC, I can query the device in fastboot and get a response, I just can't do anything to unlock anything!!
Many thanks in advance for any suggestions!
Same problem
Same thing happened to me. Same day as you. I can get fastboot but not adb but since the device is locked I can't flash. I've only had the phone about 6 months so I contacted customer support and they offered to replace the phone.
It might be a known issue because they didn't even try to address the fact that I could get fastboot connected but not adb. They just offered to replace.
Thanks for the info! I am -at least in this case- unfortunately an early adopter. I bought two essentials at the beginning of the pre-release.
Essential support checked my serial number and said the phone was out of warranty.
Has anyone been able to force the Essential into EDL mode to recover that way? It looks like you have to latch one of the USB pins to ground, or 5V, but I haven't found any detailed instructions on how to make this work on the essential...
Thanks again
Justin
I'm sure things have changed and I'm wrong, but if you can get into the fastboot menu can't you just cycle through the options until you get to recovery and then flash an official release from Essential?
I may be thinking of LG or something but this should be possible as long as it's newer than the current software installed because it will see it as an official update and allow the flash.
Thanks but unfortunately, when I try and do that, the phone just does the same thing, it hangs forever on the initial boot screen white Android text with the circle/square logo...
That's why I've been looking into the more direct hardware version of forcing the phone into EDL mode, which is supposed to be possible with all Qualcomm based phones.
I've just not found the time yet to find a USB-C cable I'd be happy to cut in half and short the pins on! Which is why I was hoping someone might have tried this with an essential before to know if it was successful before I start trashing good cables
Thanks again for your reply!
JB
justinbaird said:
Hello I am posting in Q&A because I'm a new XDA user, I was not allowed to post in the dev channel.
I have an Essential phone that has been working great for the past few years, no issues, and it was running standard build receiving OTA updates, until the very last update, which soft bricked the phone.
The phone was never enabled in developer mode while in Android, and now, I can't boot the phone into android at all. The only thing I can do is get into fastboot.
Fastboot state shows DEVICE STATE - locked
Any commands I try to unlock flashing, or change slots, anything at all, I get the error that the device is locked so all commands to unlock fail.
Is there any way to unlock device state from fastboot? I saw a youtube video showing a way to use a chopped USB cable to enter emergency / EDL mode for Qualcomm-based Android devices, but have not seen anyone post that this was successful with the Essential
Does anyone know of any method to be able to unlock flashing from fastboot? Or any other method to un-brick an essential? I've attempted everything, on both Mac and PC, nothing works.
On mac or PC, I can query the device in fastboot and get a response, I just can't do anything to unlock anything!!
Many thanks in advance for any suggestions!
Click to expand...
Click to collapse
I have the exact same problem,
My phone is stuck on Essential log when I turned it on,
I can access Bootloader normally but the device is locked so I cannot flash it,
Recovery is corrupted, when I try to star it, it shows only the the Essential log and freeze so I can not format or wipe or sideload.
OEM Locked and unchecked
USB Debugging is unchecked
and I can't flash anything,
Did you managed to unlock it through Fastboot command or any other way ?
I wish I can just login to the recovery or unlock it so I can flash it clean,
Kindly help me if you found a way out
Thank you
I have a Tmobile OnePlus 6T, hard bricked.
Mine gives the usb device malfunctioned error. I have installed, uninstalled and reinstalled the qualcomm usb drivers. It recognizes the phone in the device manager as USB DEVICE DESCRIPTION FAILED. The MSM tool wont recognize it, and my phone wont boot in any other mode except EDL. It will not boot to bootloader or anything. Funny thing is, all I was trying to do was convert the T-Mobile version to international which I've done before. During that process, it hung at "recording downloading time". I let it go for 20 minutes, according to the guide it is supposed to take 5. I canceled the process, (I had done this one other time before, and it booted just fine) and now nothing works. I am not a noob at this. I can restore through fastboot if I could get it to boot into fastboot. I could restore through recovery via sideload if I could get it to boot into recovery. Please help.
*Moderators, I have searched high and low through the forums and I cannot find a thread with this problem that has any steps to solve it. I found one thread with a similar description but it is a year old, has no replies and the author managed to fix his phone on his own, with no description of how he did so.*
Txdude35 said:
I have a Tmobile OnePlus 6T, hard bricked.
Mine gives the usb device malfunctioned error. I have installed, uninstalled and reinstalled the qualcomm usb drivers. It recognizes the phone in the device manager as USB DEVICE DESCRIPTION FAILED. The MSM tool wont recognize it, and my phone wont boot in any other mode except EDL. It will not boot to bootloader or anything. Funny thing is, all I was trying to do was convert the T-Mobile version to international which I've done before. During that process, it hung at "recording downloading time". I let it go for 20 minutes, according to the guide it is supposed to take 5. I canceled the process, (I had done this one other time before, and it booted just fine) and now nothing works. I am not a noob at this. I can restore through fastboot if I could get it to boot into fastboot. I could restore through recovery via sideload if I could get it to boot into recovery. Please help.
*Moderators, I have searched high and low through the forums and I cannot find a thread with this problem that has any steps to solve it. I found one thread with a similar description but it is a year old, has no replies and the author managed to fix his phone on his own, with no description of how he did so.*
Click to expand...
Click to collapse
The other of the previous post probably figured out how to get the device recognized by the computer. I would say see if you can use another computer/cable and see if it still has the same issue, if it does i'd probably be concerned about the device health. If the issue is gone on the other PC though then you likely have something wrong with either drivers or usb hardware on your PC. I would assume you've already tried using a different USB cable and port with your current PC.