Hello everyone. Recently, I used this tutorial: http://forum.xda-developers.com/showthread.php?t=2392762 to obtain Cm11. What happened was when I tried to unlock the bootloader, and used adb commands to execute the files on my root. After I did reboot, the phone wouldn't turn on. No signs of life, can't boot into recovery mode. I've done the tutorial before on this phone, and I reverted back to stock. Now that I'm doing it again it won't work. I think it may be hardbricked. When I plug it into my PC, I can go to device manager and the PC will recognize it as a Qualcomm driver. I really want to fix this problem without needing to call LG or get repair for it. I looked at some tutorials and found this one: http://forum.cyanogenmod.org/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/ I'm not sure if this'll work for me. Can someone please provide me with some help with this situation.
Related
Hello,
I had installed the Franco Kernel on my N4 some months back. I recently got the 5.0 Lollipop OTA update but i could not install it. I read somewhere that i needed to install the stock kernel to get Lollipop installed. So i got the factory image of 5.0 for N4 from google and manually tried to flash with some Kernel flasher app i dont recall the name. THAT WAS THE WORST DECISION I EVER TOOK.
Now my phone is stuck in fastboot mode. I can go to recovery and all. Whwn i try to start up my phone i can only see a black screen.. i downloaded adb but the problem is I HAD NOT TURNED ON USB DEBUGGING. I searched the net for a week,asked my friends who all said that i should throw away my old( i dont consider it old) phone and get a new one. I have come here with a lot of hope. I bought the N4 so as to use it for atleast another year .
Adb doesnt recognize my phone. Pc says "Android Device". Please help me. Im saving for getting my sister a laptop and i just cant afford another decent reliable phone.
You do not need USB debugging for fastboot mode. when cionnected is should say android device and some serial number.
USB debug mode is when the android OS is running not fastboot mode
if it does not when connected at the prompt type fastboot devices
follow the install instructions here and it should get you device back. (in the commands remember to replace the file names with the lollipop names)
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
I have brought back at least 10 devices from my own doing and from people that screw up their phone and not know what they are doing.
Good luck
Ok i will follow it. I currently have the 4.2.2 image file. Yes in fastboot mode PC recognizes it as Android Device. Lets hope i can do it I dont need USB debugging right ?:silly:
I dont know how i should thank you and this forum. I love you guys, you helped me when i had lost all hopes of getting my phone back i love you guys <333333333333333333333333333333333333333333333333333333333333333333
Glad it worked. Just spread the love on the forums.
I learned by reading here and glad to help others.
TWRP is still installed and magisk as well, but now it's not rooted and the bootloader is still locked. I am so confused about how this happened, does anyone have any ideas why this happened, or what I can do to repair it? The phone still works but it won't update and it's a little wonky. msm download tool doesn't even recognize it. thank you for any help!
EDIT: now it won't boot up to anything, only boots into the bootloader, won't go into recovery or anything. please help! haha
msmdownload tool, grab the one fitting to your phone, see in Guide News section
The msmtool won't even recognize it, that was the first thing I tried
RMA
I faced a similar issue but I was able to get it working through the MSM tool. Make sure you are holding the volume up and volume down for 15 seconds before connecting it to MSM. It should work if you follow the guide.
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
Hello guys,
I'm fairly certain I'm stuck in an un-debrickable state but I'll ask just in case. My phone is F800K.
I was toying around with LGUP in order to downgrade and root my phone. So far, so good.
I then tried to update to the latest android 9 again, but keep the root active. That's where things started to go south, so I decided to go back.
I followed a couple of "back to stock" guides but now I'm screwed.
- The phone does not boot.
- Download mode is broken, the phone doesn't connect to my computer while in download mode, so it's unusable.
- TWRP is gone. When I try to boot to recovery after yes both times I get nothing. Not the stock recovery and not TWRP, it just tries to boot as usual.
- Can't seem to go back into fastboot either. I tried VOLDOWN + plug-in the phone about 200 times now, to no avail.
Is there another way that I'm missing ?
Thanks.
growiel said:
Hello guys,
I'm fairly certain I'm stuck in an un-debrickable state but I'll ask just in case. My phone is F800K.
I was toying around with LGUP in order to downgrade and root my phone. So far, so good.
I then tried to update to the latest android 9 again, but keep the root active. That's where things started to go south, so I decided to go back.
I followed a couple of "back to stock" guides but now I'm screwed.
- The phone does not boot.
- Download mode is broken, the phone doesn't connect to my computer while in download mode, so it's unusable.
- TWRP is gone. When I try to boot to recovery after yes both times I get nothing. Not the stock recovery and not TWRP, it just tries to boot as usual.
- Can't seem to go back into fastboot either. I tried VOLDOWN + plug-in the phone about 200 times now, to no avail.
Is there another way that I'm missing ?
Thanks.
Click to expand...
Click to collapse
It does sound like a hard brick... you said fastboot is hosed, do you have access to adb in any way?
Sent from my moto g(6) play using Tapatalk
None that I know of, that's the issue. If I had access to either fastboot, adb or download mode, I could most likely salvage this, but I can't seem to be able to.
The weirdest thing is the broken download mode, I couldn't find anybody with the same issue...
growiel said:
None that I know of, that's the issue. If I had access to either fastboot, adb or download mode, I could most likely salvage this, but I can't seem to be able to.
The weirdest thing is the broken download mode, I couldn't find anybody with the same issue...
Click to expand...
Click to collapse
On my lg tribute HD (ls676) fastboot was removed by lg themselves on Android 6.0.1 quietly with a security update and download mode never worked right for me. Without access to fastboot, adb or even diag mode it really sounds like you have a hard brick. if i can find a solution of some kind, I'll definitely let you know.
Sent from my moto g(6) play using Tapatalk
What would "diag mode" be and how can I check if I can access it ?
Small update for people who stumble upon this thread, I managed to save my phone by using the Qualcomm Test Point, see here: https://forum.xda-developers.com/showpost.php?p=81697447&postcount=128
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.