I have a LG G Vista VS880 that I rooted with Kingroot. My next step was to nuke the LAF, go into fast boot and use fastboot oem unllock to unlock the bootloader so I could install custom recovery. I got as far as nuking the LAF when I had to stop and fix dinner for the kids. When I got back to the computer I forgot that I hadn't unlocked the bootloader yet and flashed the custom recovery and a magisk patched boot.img using flashify. Now it will not boot into system or recovery. I can get it to boot into fastboot mode by holding the volume up button while plugging it in but all my fastboot commands are locked. I have searched the forums and have found nothing except some info on getting into QHUSB mode by shorting out the test point but that post was for the G3 and when I took off the back plate the configuration was different and I didnt want to mees my phone up any worse than I already had. I just want to get back to stock and start over. Can someone please help or at least point me in the right direction?!?!?!? I would welcome any assistance!
Related
Hello All!
I got my LG L9 (P765) brick and need your help. It wasn't unlocked or rooted. Also it has original ROM.
It happened after ordinary phone call. The only thing i saw was "LG" lable. After all common methods i tried hard reset and got dead android on the screen with red triangle. Some hours later i flashed new boot, u-boot and recovery but nothing happens. The KDZ method was done today with no positive results after V10 and V20 instalations (even with hard resets). Custom recovery upload results in "Security Error" on title screen.
So guys please help me. What else can be done to make it load at least recovery? Is it possible to root or unlock such device?
If you have locked bl and device is nonrooted you can service your smartphone in LGe services.
L9 is hard to unlock, but you can go into LG recovery by power volume up and home, smartphone will be connected as recovery. By adb you can writte "adb reboot oem-unlock" to enter fastboot mode and unlock bootloader. If your phone will just restart, try this method few times. After you unlock bootloader you will able to flash custom recovery and chance kernel, install custom rom etc.
i have this same trouble and this is not help...
Hi there,
I need your help with my device which I just bricked in a peculiar way...
So, something I flashed was not correct. That resulted in an infinite reboot loop (the logo is shown for half a second and it reboots... endlessly). I just used the volume-up rocker to go into fastboot mode to fix the thing as I usually do. I booted into fastboot and this is where it become weird: I cannot do anything!
If I try to use fastboot continue, the phone reboots endlessly again.
If I try to boot to any img (TWRP or signed recovery or signed boot), the device tells me it cannot because it is locked.
If I try to unlock the bootloader (again, because it was), I am told that I am not allowed to do it. The problem is that I cannot boot into a ROM to go into dev mode to allow this.
If I try to flash things, it obviously doesn't work either as the bootloader is considered locked.
The worse here is that since my phone is "not" hard-bricked, I cannot go into qhsusb_bulk mode and use Qualcomm tools to unbrick the thing.
Can I still do something myself or am I screwed?
Lltp said:
Hi there,
I need your help with my device which I just bricked in a peculiar way...
So, something I flashed was not correct. That resulted in an infinite reboot loop (the logo is shown for half a second and it reboots... endlessly). I just used the volume-up rocker to go into fastboot mode to fix the thing as I usually do. I booted into fastboot and this is where it become weird: I cannot do anything!
If I try to use fastboot continue, the phone reboots endlessly again.
If I try to unlock the bootloader (again, because it was), I am told that I am not allowed to do it. The problem is that I cannot boot into a ROM to go into dev mode to allow this.
If I try to flash things, it obviously doesn't work either as the bootloader is considered locked.
The worse here is that since my phone is "not" hard-bricked, I cannot go into qhsusb_bulk mode and use Qualcomm tools to unbrick the thing.
Can I still do something myself or am I screwed?
Click to expand...
Click to collapse
Still you can do that hard brick recovery method it will work for sure..switch off your phone completely and try to connect qhsusb mode.
I had no idea that I could force the qhsusb mode. It worked indeed. Damn ARM devices with their non-standard way of doing anything...
Hi!
I have a OnePlus X and the year after I bought it, I flashed TWRP and installed Lineage OS. Since then, I've flashed many custom roms on my phone. A few weeks back, I decided to flash Resurrection Remix. The battery life on my phone with resurrection was pathetic so I assumed it could be fixed by flashing a custom kernel (franco kernel). I downloaded franco kernel, copied it to my SD card and powered off my phone.
Instead of pressing the VOLUME DOWN and POWER button simultaneously to enter TWRP, I pressed the VOLUME UP and POWER button by accident and went into Fastboot mode. When in Fastboot mode, I pressed the VOLUME DOWN and POWER button thinking my phone would boot into recovery, but it got stuck in a bootloop.
Now my phone can boot only into fastboot mode by pressing the volume up+power button. Any other combination of buttons and it goes into a bootloop.
All this is completely my fault and I would do anything to try and fix it.
Is my phone soft bricked or hard bricked? ( I have a feeling that it is soft bricked).
I've downloaded the android SDK and Minimal adb and fastboot on my pc. I'm able to run fastboot commands, but when I type 'fastboot oem unlock', I get an error saying
"FAILED (remote: oem unlock is disabled)". I've tried 'fastboot flashing unlock' too, but the screen just says "...". Hence, I'm not able to flash TWRP. I tried flashing even the stock recovery but it wouldn't work.
Is there any other way to unlock the bootloader?
I haven't tried the Mega unbrick guide for a hard bricked OnePlus X yet, since I'm able to boot into fastboot mode. Should I give it a shot?
And lastly, can I recover my phone from this mess or is it permanently bricked?
I would appreciate any help.
Thank you!
Sounds very similar to my situation. I did end up following that guide to get mine going again. The link is broken to get the recovery tool, the 2nd one below is the "minimal" version which isn't supposed to wipe data. That is the one that worked for me. I would backup any data if you can first, no guarantee it wont wipe it. Mine wouldn't boot into the stock rom after, but at least it would get to the stock bootloader (VolDOWN + PWR). From there I was able to adb sideload the stock rom (Install from USB). This completely restored it to stock.
23santosh24 said:
Hi!
I have a OnePlus X and the year after I bought it, I flashed TWRP and installed Lineage OS. Since then, I've flashed many custom roms on my phone. A few weeks back, I decided to flash Resurrection Remix. The battery life on my phone with resurrection was pathetic so I assumed it could be fixed by flashing a custom kernel (franco kernel). I downloaded franco kernel, copied it to my SD card and powered off my phone.
Instead of pressing the VOLUME DOWN and POWER button simultaneously to enter TWRP, I pressed the VOLUME UP and POWER button by accident and went into Fastboot mode. When in Fastboot mode, I pressed the VOLUME DOWN and POWER button thinking my phone would boot into recovery, but it got stuck in a bootloop.
Now my phone can boot only into fastboot mode by pressing the volume up+power button. Any other combination of buttons and it goes into a bootloop.
All this is completely my fault and I would do anything to try and fix it.
Is my phone soft bricked or hard bricked? ( I have a feeling that it is soft bricked).
I've downloaded the android SDK and Minimal adb and fastboot on my pc. I'm able to run fastboot commands, but when I type 'fastboot oem unlock', I get an error saying
"FAILED (remote: oem unlock is disabled)". I've tried 'fastboot flashing unlock' too, but the screen just says "...". Hence, I'm not able to flash TWRP. I tried flashing even the stock recovery but it wouldn't work.
Is there any other way to unlock the bootloader?
I haven't tried the Mega unbrick guide for a hard bricked OnePlus X yet, since I'm able to boot into fastboot mode. Should I give it a shot?
And lastly, can I recover my phone from this mess or is it permanently bricked?
I would appreciate any help.
Thank you!
Click to expand...
Click to collapse
Surely your bootloader is already unlocked isn't it?
You don't actually say what happens when you try to reboot into recovery using fastboot commands. Does that fail too? What happens when you try to flash twrp again? You don't actually say.
That's what I thought too. It would just say 'recovery.img' not found or something like that. But, I followed the Mega unbrick guide and was able to install the stock ROM through the stock recovery. My OPX is alive again!
i'm stuck here. the phone does not go into recovery at all .. stuck on oneplus logo .. I don't know what to do .. any ideas?
---------- Post added at 09:20 AM ---------- Previous post was at 08:24 AM ----------
I managed to get it alive again with this guide
Lg g5 dead while ota update installation.
Everything I plug in a charger or press power button, lg logo appears and then a black screen with an error on top left corner.
After 1-2 seconds phone would restart and goes through this never ending loop.
Phnoe does boot into the recovery mode and except that I'm not sure about anything.
Got it checked at multiple locations but still no luck.
Had this phone laying around for over a year now in same condition.
Don't know what can be done.
Please help!
I'm not sure about the model number but in the inside of back door and on the charging port brick it says Ls992.
hmmm... if i were you, i will just go to flash TWRP recovery and then i custom rom OR even stock rom. I mean, your rom seems completely vanished, so just go to the many guides there are out there, to unlock bootloader, and flash TWRP and a rom
You can probably still boot it into fastboot or download mode, you could try flashing TWRP recovery in fastboot, or the stock firmware .KDZ in download mode.
Yes, fortunately you are only soft bricked. You can boot into download mode and reflash with lgup.
Hello, My phone (Col L29) is currently softbricked and I can only access fastboot and ERecovery, TWRP when flashed won't boot when using the right process to boot and ERecovery cant download the firmware, I've tried flashing various parts of the stock update firmware to no success, if anyone can help that'd be really good!
Thanks
Andrew
Could you confirm what have you done before leading to this condition? May be can help
shashank1320 said:
Could you confirm what have you done before leading to this condition? May be can help
Click to expand...
Click to collapse
before it was bricked I was going through the process to install a new OS, i was using twrp bekerly (view 10) and it froze on the splash screen, so after a few minutes i held the power button and after that i couldn't access the recovery whatso ever.
I've tried ERecovery via wifi and OTG (not sure if i set up the folder correctly for otg of if otg just doesn't work), flashing stock recovery, flashing as many things as i could from the UPDATE.APP (do note that i couldnt flash ramdisk as that command was "not allowed" as with many other partitions), i have also tried wiping then flashing (be that through ERecovery or Fastboot).
When I try to access Recovery (rebooting after flashing, removing USB cable and holding Vol +), it goes to the Device is not trusted screen and then to ERecovery if i don't let go of the vol button.
I've softbricked my Moto G4 before but man, this is a ***** in comparison.
Try to flash the correct twrp via fastboot and should be fine. You may have incorrectly flashed the erecovery to the regular ramdisk_recovery(probably) which may lead to only erecovery and fastboot.
Erecovery doesn't work in most of the cases for many(though i have success rate of over 90%).
Also, flashing cust.img, version.img and vendor.img helps sometime.