Bootloop Issue - LG K7 Questions & Answers

I have the MetroPCS variant of the LG K7 (LGMS330) and I deleted the boot partition like an idiot. I was using fastboot commands and used "fastboot erase boot" because I had previously installed TWRP as the boot partition (Also an accident but I didn't know it at the time). So as the smart cookie that I am, I decided that erasing the boot partition will solve my problems...but it made it worse.
And now the phone boots up to the LG logo and turns off immediately, if I could access fastboot then it would be great, can anyone assist me with this problem? Thank you in advance!

Related

(HELP ME) atrix won't go past M logo

So I have a rooted, unlocked atrix 4g running nottachtrix 1.3.1 (which is based off of 2.3.6 and the 4.5.141 OTA). anyway, the phone worked fine for a couple of weeks after i bought it. SOOOO I bought a lapdock just to use for long car rides and stuff (big screen movies). after about three days with the lapdock the phone started acting up so I wiped dalvik/factory restore/wipe data and reflashed Nottachtrix. Then it would boot up to Motoblur registration and after 2 seconds, shut off. So I did the restore process again and now the phone will only boot to the M logo.
I can pull up the "fastboot" menu but it won't actually open those options. For example, if i choose android recovery, the phone will stay on the M logo and say "starting android recovery" but it won't ever get to the recovery. This applies for all the fastboot options and also for just booting up normally (just stays on the M logo forever).
I read somewhere ( i think it was here) that some people are having a similiar problem and it can be fixed by using RSD and flashing an sbf (would that be alright with my unlocked 4.5.141?) and the problem originates from a problem in the webtop partition (which makes sense considering my recent use of webtop). However, as I can't get into rsd can someone help me? has anyone else had this problem?
Sorry didn't mean to thank you. My hyper kitten did that.
one of the thread i read earlier about a problem similiar to mine, someone did the same thing (accidentally thank someone)
Needs to be a way to unthank. Lol. Hope you get your problem fixed.
bumpo
I would try flashing the 2.3.6 sbf using rsd lite. That would at least get you back to stock, and you could start over.
I also use nottachtrix and I have no troubles, so I do not think it is your problem.
After flashing, if that doesn't fix it for you, you are ready for warranty, and they are being very generous with replacement at the moment. But go straight to Motorola, not where you bought it. If you bought it used, don't offer that info, they don't even ask that question.
Good luck.
Have you tried going to fastboot mode directly while booting up. (Volume up)
I faced similar issue while flashing a rom (no dock though).
Deleted the data (fastboot -w), wiped the caches, and luckily it worked. Then I could go into recovery and flash another rom.
Sent from my Moto Atrix using Tapatalk
except i can't get into fastboot or rsd. it will show that option and say "starting Rsd protocol" but it won't actually start the rsd protocol (atleast my computer doesn't recognize it)
i can get into CWM recovery, though i have to turn it on, selecet android recovery, and then plug it into the lapdock.
DO NOT USE RSD UNLESS UR LIFE DEPENDS ON IT.
if u can get to recovery and fastboot then do this via fastboot.
All CRAP REMOVING
fastboot erase boot
fastboot erase system
fastboot erase webtop
fastboot erase userdata
fastboot erase cache
fastboot erase preinstall (not required)
fastboot -w (redundant, wipes userdata and cache)
and if possible reflash ur recovery too (might be the problem maker.
and then re-download ur favorite ROM and flash again.
I had such problems in gobstoper (bell stock) and this trick helped me a lot.
now i do this all the times.

Kernel crash, boot loop, nothing works!

I've had my Optimus G rooted for a while now, and I had recently updated to Cyanogenmod 11 M3 and after a few weeks of good use, my phone crashed for no reason. There was a green screen that said Kernel Crash, demigod fail or something and some other stuff. Told me to press up to do this, down to do this, power to do this…. Anyways the phone wouldn't boot up after that. It was stuck on the LG logo. I could only get it into fast boot and download mode but from fast boot there was no way to get to recovery or regular boot. I found the TeenyBins post and tried to fix it using both of the .bins they had but at 85% the phone tried to boot up and was stuck on the LG logo again. Then I found the stock .bins and tried to flash them over, yet I got the same result. I've tried everything I can think to do, if anyone has any suggestions, please please help.
Teenybins don't have an OS. Did you try to get into recovery after flashing them? Doing a hard reset after stock bins may get it to boot, but internal storage will be wiped. For future reference in the demigod screen the buttons are backwards.
After flashing Teenybin I can boot into fast boot, but from there when I select recovery it goes back to the logo. Same thing happens if I select the other options. It's the google logo, not the LG logo, because the Teenybin I most recently tried was the alternate file
bowshermatthew said:
After flashing Teenybin I can boot into fast boot, but from there when I select recovery it goes back to the logo. Same thing happens if I select the other options. It's the google logo, not the LG logo, because the Teenybin I most recently tried was the alternate file
Click to expand...
Click to collapse
If you are already in fastboot, download any recovery (CWM or TWRP) extract it, rename it to recovery.img from the zip and then go to the folder where you have adb and fastboot bins and type:
fastboot flash recovery recovery.img
from there you'll be able to access recovery.
Thank you for the help, I was going to try that last night after reading your post but I took it to the AT&T store and they said they would replace it for free (warranty). I appreciate the quick response time.

ZH&K bootloop and can't boot to Recovery mode.

Prologue- Before the bootloop and can't boot to recovery mode
So my ZH&K Odyssey Spin has been affected by malware and viruses. The effect of this is that I can't seem to "Reset to Factory Settings" and it just says "Unmounting Phone Storage". I even tried to enter to "Recovery Mode" and resetting from there but still no luck. Then I read about custom ROMs and flashing your ROM to remove malware and also rooting.
Chapter 1- The flashing, rooting and Custom ROMs
So I learned about rooting my android phone to gain more "admin" privileges and to be able to delete the bloatware in the stock ROM that ZH&K has but I noticed that the virus is included in the ROM so that gave me an idea to download a custom ROM and flash to my mobile phone to remove the bloatware and viruses. I tried doing the SPD Flash tool(UpgradeTool/FactoryDownload) and mounted the ROM for ZH&K Odyssey Spin (My phone hehehe ) and when I started the operation it just sat there doing nothing. So I researched more and found out about the ADB and fastboot methods of flashing ROM. I wanted to to flash TWRP Recovery into my phone but there was no TWRP Recovery available for my device so I "accidentally" downloaded the TWRP Recovery for Motorola G Falcon and after flashing to my device I noticed that I can't access the "Recovery mode".
Chapter 2-The "Bricking"
So when I flashed the 'TWRP Recovery for Motorola G Falcon' I cannot access the Recovery Mode. Take note that I learned about adb and fastbooting. So out of panic I typed "fastboot -w" (a command that wipes your data) into the cmd console. Then it happened when my phone rebooted it will show the "ZH&K" logo and play its animation and also has sound but after that it just stays that way and black screen and bootloop. So I tried to access the Recovery Mode(which is now unaccessible:crying and still shows the logo but does not go in but instead the screen goes black.
Epilogue- The "Begging for Help"
So I don't know what to do at this point and want some assistance for I have searched the net and there is no other problem like mine I even did the Battery pull method to "refresh" the phone but still no luck and some help will be greatly appreciated !
Phone: ZH&K Odyssey Spin
External: 8gb Sandisk
If you want to know something just ask thanks!!!

continuous bootloop

after flashing RR i made a mistake going in fastboot instead of rebooting in system. Tried a forced reboot like any other time i enter in fastboot and my phone is rebooting itself continually, showing the boot logo for a split second and rebooting again. Obviously i cant go in recovery or do anything else. Any solution?
kekkojoker90 said:
after flashing RR i made a mistake going in fastboot instead of rebooting in system. Tried a forced reboot like any other time i enter in fastboot and my phone is rebooting itself continually, showing the boot logo for a split second and rebooting again. Obviously i cant go in recovery or do anything else. Any solution?
Click to expand...
Click to collapse
Did you have a Marshmallow(6.0) ROM before flashing RR?

Tried to Unlock Pixel 2 XL Now Stuck in boot mode!

Hi guys,
I think I made a huge mistake Any help appreciated...
I was following the Magisk and TWRP guides to try and root my phone. I thought it was all going well, but then when trying to flash TWRP, it didn't let me flash it to recovery, it said 'no partisan'. I found on a forum post to try the command 'fastboot getvar current-slot' (this returned a) then 'fastpool flash_a twrp.img'.
I tried this but then TWRP got stuck on the loading screen. I then realised that I couldn't boot into my Android version anymore as I'd flashed TWRP directly onto the boot partition! So I went about trying to flash my stock Android version back onto the phone... I then did this:
'fastboot boot_a boot.img' I stupidly then rebooted. I now am stuck with a perpetually spinning Google loading boot image. I can't launch into recovery mode as I have none, and when holding the power button and volume up it shows an info screen saying "PRESS POWER BUTTON TO PAUSE" and then it goes to the perpetual loading screen again.
I also can't do any more fast booting because adb cannot connect anymore...
Am I completely doomed?
silkt said:
Hi guys,
I think I made a huge mistake Any help appreciated...
I was following the Magisk and TWRP guides to try and root my phone. I thought it was all going well, but then when trying to flash TWRP, it didn't let me flash it to recovery, it said 'no partisan'. I found on a forum post to try the command 'fastboot getvar current-slot' (this returned a) then 'fastpool flash_a twrp.img'.
I tried this but then TWRP got stuck on the loading screen. I then realised that I couldn't boot into my Android version anymore as I'd flashed TWRP directly onto the boot partition! So I went about trying to flash my stock Android version back onto the phone... I then did this:
'fastboot boot_a boot.img' I stupidly then rebooted. I now am stuck with a perpetually spinning Google loading boot image. I can't launch into recovery mode as I have none, and when holding the power button and volume up it shows an info screen saying "PRESS POWER BUTTON TO PAUSE" and then it goes to the perpetual loading screen again.
I also can't do any more fast booting because adb cannot connect anymore...
Am I completely doomed?
Click to expand...
Click to collapse
I ended up eventually un-bricking my phone by booting into safe mode and re-connecting the ADB. I then successfully ran 'flash-all.'

Categories

Resources