Database Users

Bootlooping LS980, previously rooted, stock recovery.

Ok, so i rooted my LS980 from day 1. A week later, I dropped my phone and cracked half my screen Regardless,the phone was working fine for a month or so. Then..... Along came the LS980ZVA update.... My phone kept telling me that the update was downloaded and ready to install. I kept ignoring it of course.
So one day, after work, I pull my phone out of my pocket and it begins to boot, stays alive for a minute or so(with zero signal and no touch input), and then begins to boot loop. I assume that my phone managed to update in my pocket, so I tired to boot to TWRP and restore a backup. This only sent my phone back into the bootloop
Next, I tried restoring my phone back to stock with the LG Flash tool. Long story short..... Half the time while in download mode, my phone will say it's rooted and the other half will say unrooted. And now im STUCK WITH STOCK RECOVERY!!!! I managed to get usb debugging enabled and can change my PC connection mode before it loops, but so far no rooting method works and I can't get any ADB commands to work.
Every time I issue an adb command it returns "error closed."
I can get into download mode, stock recovery, and can manage to get the phone to stay booted for a maximum of around two minutes or so...
What can i do!!!???!?!?!?!? My software still says i'm on on ZV7 firmware.... What can I do with stock recovery, no remaining nandroid backups, no adb, and a bootloop...? Maybe there's a solution utilizing linux...?
Any help would be sooooooooo appreciated!!!

[Q] I somehow lost my recovery?

So I was running CWM (Philz) I believe, and I had been running into issues while on rooted 4.2.2 D800 stock ROM. There were force closes and random reboots, etc. I've only installed xposed mods. I've also used android tuner to adjust some of the build.prop and kernel presets.
However, after my phone got stuck in what I thought was a boot loop, I finally got it up and running. What happened next was odd. I tried booting into recovery -> the "LG" splash screen showed up and it went into another infinite boot loop.
I'm assuming I somehow corrupted or lost my recovery. Any advice on what to do? I don't know if I should follow the original instructions for flashing a recovery here - http://forum.xda-developers.com/showthread.php?t=2633150.
Edit: Jesus christ my phone infuriates and confuses the hell out of me. After attempting to enter the recovery again, I am now stuck in a permanent boot loop. The last time I fixed it was by turning my phone off....and then *WAITING*.
What? That doesn't make sense you say? Of course it doesn't. But that's still what worked. I waited 12 hours, and then tried turning it on again. When I did, oh look, the AT&T screen!
CONFUSING. help please...
Double edit (Hard Mode): Going into download mode when I'm in this constant bootloop = nothing happens. That little icon that says "Download Mode" with the 5 blue circles just stays there, and my laptop ends up not recognizing anything. This happened the last time too, and all I was able to see on my laptop was "QHSUSB_BULK". I thought this meant that I would have to do a complete wiping process through Linux (found on another thread somewhere), but apparently waiting 12 hours also fixed the problem.

Storm Bricked and Fastboot Broken

Hi all,
I got my Wileyfox storm running stock CMOS 13.0 in April and had no problems for about a month. Eventually, I got a pop-up notification with an "Incremental Update" for the phone. I downloaded it and when ready to install, I did so - or at least tried. The update finished and booted into recovery for some reason. At the time I didn't question it and just rebooted the phone from recovery. This led to a boot hang on the "Cyanogen Mod Ready" boot screen.
After searching around for a fix I eventually tried to flash over the stock ROM via Fastboot - which for some reason errored on emmc_appsboot and the phone rebooted itself - with a penguin instead of the Wileyfox boot logo and STILL hangs on the Cyanogen screen. I can also now not boot into fastboot and not boot to fastboot from recovery either (which I CAN still boot to).
Does anyone have any ideas on how to fix this ASAP??? Help would be greatly appreciated!
Many thanks.

I've finally found something that works, unplug the battery for a day or two, then plug in and charge and turn on and might boot properly. Frustrating having to do it every time you get into the bootloop hang and doesn't work every time but still probably salvageable.....I discovered after being bricked for 14 months.

XT1564 unable to reboot properly for OTA

I have a stock moto x play whose hardware sku is XT1564. It's on android ver 5.1.1 and system version is 23.21.25.lux_lra.en.US
I have not performed any soft mods or alterations, be it root or bl unlocking.
The only thing that I would think is different than normal is that the phone is encrypted, so it asks for password whenever it boots up.
I got a notification to update to 24.74.5.en.US a few days ago and decided to try doing it today.
It downloads the update fine and when I press on the notification for it to start the update process where it says it needs to perform a reboot to update it goes into a "phone will reboot in 10 seconds" screen and when countdown finished it shows the "shutting down..." popup that appreas when you try to shutdown the phone.
Then the phone stays with that popup until it finally shutsdown like 4 minutes later on what appears to be a hard shutdown because it doesn't reboot. I have to manually power it on and then the phone starts up normally asks me for my password and about a minute after android fully loads the phone tries to shutdown again without any input. And then it just keeps doing that until I boot the phone into fastboot and try to get it to bootloader, where it shows the dead android logo with a red yield sign and promptly shutsdown. Then when I start the phone normally it shows an "update unsuccessful" screen.
Anyone have any idea what might be the problem?
I've been thinking it might be the encryption but IDK. Also I've checked the thread with the firmware versions and couldn't find mine there. Is there a way I could dump mine for backup in case I **** something up trying to get OTA to work.(without unlocking bootloader and rooting, of course)

Now the update has stopped appearing and I can't get it to recognize there being an update for this device.
Fudge!

Verizon Galaxy S7 only booting to a white "Verizon" screen

My wife's S7 is only booting to the verizon logo (with the little colored circles moving below). Long story short:
1) I was trying to back up her pictures to my PC and all of them disappeared from her phone when I drug them to my PC (6 months of pics). Not sure how that happened.
2) In my panic, I downloaded an application called DR. Fone which professed to be able to get the pics back.
3) After installing the app and connecting the phone, I started the recovery process, which rebooted the phone to a "downloading" screen and then booted to the Verizon logo I have been trapped on ever since.
I have tried powering off, rebooting, clearing the cache from recovery to no avail. I have a feeling that this app altered the bootloader or firmware and now I'm stuck.
Booting into recovery ends up with a "No Command" error. I can get into the Android Recovery menu from there ... but I don't want to wipe it just yet.
Any ideas what could be keeping me stuck on that screen?
Pleeeeaaaaasseee help!

Install this rom, connect to your computer with the verizon upgrade assistant running after the rom is installed. The verizon upgrade assistant should see the phone and you can update it from there.