Possible Bricked Phone? Please help! - LG G5 Questions & Answers

I was flashing the rom Flumics for my LG G5 H850 using twrp, although I already had resurrection remix, but it was not fast charging which is why I decided to switch. Long story short, i managed to get my phone to keep booting into twrp, after searching for a fix i typed some commands into the terminal to leave twrp, however it seemed that I had no os so now i boot into the device is corrupt. It cannot be trusted and will not boot. I tried to use LGUP to flash stock rom although my phone was not detected and while trying to reflash twrp through adb, it seemed my phone had it bootloader locked again. So i went to flash the unlock.bin file, although it says ERROR!! Bootloader unlock key write fail. Any suggestions?

Related

CWM Bootloop

I KNOW I SHOULD POST THIS IN MY NON-EXISTANT DEVICE FORUM,
but there is like no community there and I figured I would get a faster answer here.
I have an LG Mytouch Q C800 and I accidentally applied an OTA update with CWM installed. Since then I have been in a CWM bootloop, unable to boot into normal android. I dont think I can access fastboot or ADB. I have tried reflashing the stock ROM and everything. Can anyone help?
Yoyomah20 said:
I KNOW I SHOULD POST THIS IN MY NON-EXISTANT DEVICE FORUM,
but there is like no community there and I figured I would get a faster answer here.
I have an LG Mytouch Q C800 and I accidentally applied an OTA update with CWM installed. Since then I have been in a CWM bootloop, unable to boot into normal android. I dont think I can access fastboot or ADB. I have tried reflashing the stock ROM and everything. Can anyone help?
Click to expand...
Click to collapse
man the same thing happende to me, the only way i could partially recover my phone was flashing clockwork mod and from there install Cianogenmod 9, then in recovery mode conected to the pc via cable and typed:
"adb reboot bootloader"
once in Fastboot mode typed:
"fastboot boot boot.img"
where boot.img is the file contained in the cyanogenmod .zip file, doing this i managed to boot the rom and use my phone, the problem is that anytime it restarts it gets stuck in the boot loop again, and i have to repeat the process for it to boot again, i think is a bootloader problem since i have virtually done anything else, i think that the OTA update from tmobile changes something on the bootloader and it forces recovery/update boot always, and since the OTA never was completed it never got back to it's original state, its´s just my theory, i´m looking into it, but for now my phone works!.
Solution
I found a solution for the lg c800 bootloop, se my post: http://forum.xda-developers.com/showpost.php?p=39453347&postcount=10

Please Help! I have soft bricked my OnePlus X!!

Hi. I have had the OnePlus X for a very long time, and I have recently bricked .
Ok, here it goes :fingers-crossed:. I had a OnePlus X running CM13 with TWRP but a locked bootloader. I decided to try cyanogenmod recovery but soon realized it was terrible.
I was unable to flash img. files and the UI was unappealing to me. However at that point I was able to reboot into my ROM (CM13) with no issues. Knowing this, I thought that the only way I could get TWRP back was through a fastboot command (fastboot flash recovery recovery.img).
For me to execute that command, I needed to unlock my bootloader first, so I took all the necessary steps in the developer options settings menu. I then booted into fastboot mode and executed this command: fastboot oem unlock. This was my big mistake, as I read up after that you should not unlock bootloader on a custom recovery.
After executing this command, it booted me into recovery. I tried many times without success to wipe data and flash a rom zip via external sd card but they never worked. To make things worse, I was unable to boot up the device. Whenever I tried to power on the device, it booted straight into recovery. I am able to boot into fasboot and recovery, but that is pretty much it. Can someone please help me? I am willing to donate.
If you were able to flash the Cyanogen recovery with a locked bootloader you should be able to flash the official OPX recovery as well. You can download that from this link: https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
Then you should be able to unlock the bootloader!
Or if @Tanner1294's doesn't help, flashing stock rom via fastboot will surely help..
PS: Don't ever flash anything on a locked bootloader.

Moto G 1st gen stuck in bootloader (loop) after trying to install custom rom

Phone unlocked but not rooted.
I managed to install TWRP and proceeded in installing a custom rom (followed by the gApps suite). After rebooting I ended up stuck in Bootloader, no matter what I do. Every option in Bootlader only reboots me in Bootloader.
I tried accessing the Recovery mode through adb (which still works and recognises the device) after re-flashing it, but when I use the "fastboot boot twrp.img" command, it give me "FAILED (remote failure)".
I spent the night trying to find a solution. I'm desperate, truly. Can someone help me?

softbrick

need some help i have curtana model. I successfully unlocked the bootloader then i went to flash the eu rom but it failed in twrp. i tried to reboot the phone but I got the system is destroyed screen. I still have access to fastboot but no recovery nor the os also. I tried to flash the stock rom with the flash tool but I've never had a success flashing a rom. the tool stays in flashing mode without a fail or success state. i left it all night and nothing happened. when in fastboot I'm still able to run fastboot commands but i cant flash manually any kind of recovery i still get the system destroyed screen.
do I still have hope to boot this device or not

K7 LGUP tool times out when trying to flash .tot file

I found (on this website) an LGUP tool (version) that is for the MS330. So it works (albeit not so consistently). The LGUP tool was able to flash a .kdz file after several trials. Apparently when LGUP connects, it puts the MS330 in bootloader mode, waits 15 seconds for the device to respond and then begins flashing.
Now, here's the problem. I have a .tot file I'd like to flash. When trying to flash a .tot file, 15 seconds is not enough time for the device to respond, and I get an error for what appears to be an asynch error. That is to say, the MS330 took a second or two more that the 15 seconds to respond saying, yes I'm in bootloader mode.
Is there any way to give it a bit more time? Surely the members who use LGUP tool would have encountered this behavior, and would have found a solution.
Tried changing ports, cables, computers. No improvement
Words of wisdom, anyone?
BigZ1 said:
I found (on this website) an LGUP tool (version) that is for the MS330. So it works (albeit not so consistently). The LGUP tool was able to flash a .kdz file after several trials. Apparently when LGUP connects, it puts the MS330 in bootloader mode, waits 15 seconds for the device to respond and then begins flashing.
Now, here's the problem. I have a .tot file I'd like to flash. When trying to flash a .tot file, 15 seconds is not enough time for the device to respond, and I get an error for what appears to be an asynch error. That is to say, the MS330 took a second or two more that the 15 seconds to respond saying, yes I'm in bootloader mode.
Is there any way to give it a bit more time? Surely the members who use LGUP tool would have encountered this behavior, and would have found a solution.
Tried changing ports, cables, computers. No improvement
Words of wisdom, anyone?
Click to expand...
Click to collapse
What is going on? Wierd error/problem here.
OK! All of this above is OBE. I managed to get the bootloader unlocked, so I am now free to load custom roms. Well, sort of. I rooted the system, and tried to install TWRP from the playstore. When I got to the part about flashing recovery with the TWRP image, it fails. Just says Flash failed.
So, I went back to using adb and fastboot. I used "flashboot flash recovery TWRPfilename". That worked. Then "adb reboot recovery" took me to TWRP. So far, so good. When I shut down the phone and use the power/volume keys to boot into recovery, I get the stock rom recovery, not TWRP. If I connect the usb cable and use "fastboot reboot recovery" I get TWRP
What is going on here? Anybody who has a clue, please share your thought of the problem and/or possible fixes.
Thanks!
BigZ1 said:
What is going on? Wierd error/problem here.
OK! All of this above is OBE. I managed to get the bootloader unlocked, so I am now free to load custom roms. Well, sort of. I rooted the system, and tried to install TWRP from the playstore. When I got to the part about flashing recovery with the TWRP image, it fails. Just says Flash failed.
So, I went back to using adb and fastboot. I used "flashboot flash recovery TWRPfilename". That worked. Then "adb reboot recovery" took me to TWRP. So far, so good. When I shut down the phone and use the power/volume keys to boot into recovery, I get the stock rom recovery, not TWRP. If I connect the usb cable and use "fastboot reboot recovery" I get TWRP
What is going on here? Anybody who has a clue, please share your thought of the problem and/or possible fixes.
Thanks!
Click to expand...
Click to collapse
One more tidbit of info. I tried flashing TWRP (installed from the playstore) several times. At first all I got was Flash Failed. Now (for no apparent reason) it was able to flash the TWRP file. So I thought I'd test it out. No change. Still can't boot into recovery by using vol-and pwr. Still takes me to stock rom recovery. But (same as before) adb reboot recovery takes me right to TWRP, and it's working fine.
I am not doing any data wipes, formatting, changing permissions, etc. . Anybody have any experience with this problem, or any thoughts on how to fix it????
BTW, this is for an LG K7 MS330m1.

Categories

Resources