Database Info

[Q] Stuck at Google logo when powering on, can't enter recovery mode

Hey guys,
Few days ago, I woke up and saw my Nexus 5 was out of battery, charged it and when I turned it on it started to update and it was going through with optimising apps ## of ### and when I checked it again, it was stuck on the four circles animation. It got stuck on this screen for quite a while so I powered off, powered on again and now it just stays stuck on the Google logo, what should I do?
I've tried entering Fastboot Mode and selecting Recovery Mode but then nothing happens; screen stays on but stays black. I tried connecting it to my computer so I could backup my files but I can't get it to appear as a Nexus 5 drive and access the folders. Also LOCK STATE - locked [preetty sure I unlocked it back when I first got the phone in 2013 but then I haven't really done anything custom with it]
So I've tried following the steps here: androidforums.com/threads/nexus-5-stuck-in-the-start-up-screen.887612/page-3#post-6817816, but I can't get my device to appear as an adb device, even though i ran the 'fastboot oem unlock' command and it unlocked the Nexus? i.imgur.com/VHHjaVe.png (Android device is showing but 'adb list devices' command doesn't detect anything?)
Ideally I would like to access the Nexus 5 internal storage and just copy paste the folder to my computer to serve as a backup and save files, then flash a new image/factory reset it. I went over to my cousin's place last night to see if he could help as he is more technical than I am but he couldn't flash a new image onto it. I've also unlocked the phone a few times with the 'fastboot oem unlock' command, which changes to LOCK STATE - unlocked, but then if I power off the phone and enter Fastboot Mode again it will show as LOCK STATE - locked.
Also, I'm not sure at this point if the unlocking has wiped whatever data might have been on the phone anyway? [does the internal sdcard get wiped if you run oem unlock? e.g. I had about 6/32GB left on my phone but now it'll just be 31/32 GB because it wiped?]
Thanks, I hope my description of the problem is clear. I have tried googling extensively to see if anyone has experienced similar problems but they're not quite the same (eg. stuck on Google screen bootloop is a power button issue but my phone doesn't constantly reboot and the power button seems fine) [clearing cache or running Recovery mode, but my phone can't run Recovery mode] {Flashing new image but that didn't seem to work either}
Sorry my links don't work, I'm a new user so don't have enough posts here!

Stuck in "Warning Bootlaoder is Unlocked" Loop and Need Help

I have looked at multiple guides on this and other sites, googled and tried stuff and I cannot resolve this problem. Hopefully I am posting in the right place.
I took the jump and unlocked the bootloader on my Moto G first generation, XT1034 successfully. I flashed TWRP 2.8.60.xt1034.zip with adb and this was successful. Then I flashed Super SU 4.6 Update and that was successful. I got into trouble I guess when I tried to flash Cyanogenmod 12.1 nightly. I used TWRP to flash via install. The flash had an error, which unfortunately I didn't write down. I believe it was something to do with a partition. However, it looked like the flash failed. At this point and for hours I have been trying to fix the "Warning Bootloader Unlocked Loop I am stuck in.
I have been able to get into the phone and flash via adb commands. I've tried several commands suggest to fix this that I have found in forums. I have tried flashing several recoveries including an older TWRP per the method in this thread, a clockworkmod - and the original 2.8.6.0.xt1034. When I get into the phone bootloader which is available, I have not been able to access any options in recovery. Pushing the power button on recovery leads to a blank screen sometimes followed by a recovery starting or a Motorola Logo starting up and a couple times a recovery. TWRP has started a couple times, but never gets past the intro screen, where it locks up. clockworkmod (clockworkmod-6.0.4.7-falcon.img started once after flashing through adb and gave me flash options. I tried to sideload, didn't understand, went back and the recovery locked up. These recoveries no longer load at all.
Through all of this the "Warning Bootloader Unlocked" logo screen comes up after plugging into the computer (Windows 8.1).
Example, I open the phone bootloader by waiting for the phone screen to go from the "Warning Bootloader Unlocked" screen to blank - it cycles from logo to blank. If I'm quick the phone and hard boot the phone will boot into bootloader. I connect to the laptop through USB. When I toggle to recovery and hit the power button the screen goes blank, the Motorola Logo pops up, goes blank and then the "Warning Bootloader Unlocked" appears. The Laptop then seems to connect and disconnect as the Warning screen comes on and turns off.
The factory selection just goes to a blank screen.
I would really appreciate some advice on how to get the phone back to a state in which I can work with it and try again. It is very difficult wading through all of the information out there. I've learned a lot through this issue, but can't take it any further.
Thanks, Jeff

Solved - Stuck in "Warning Bootloader Is Unlocked" Loop
This resolution took many hours to figure out, but I finally got there with this guide - http://forum.xda-developers.com/showthread.php?t=2542219, this thread - http://forum.xda-developers.com/showthread.php?p=54855457#post54855457 and this thread - http://forum.xda-developers.com/gen...e-firmware-t3042687/post59139823#post59139823.
I tried RSD Lite on different computers and USB cables I could not get the device recognized. So I ended up with the MfastbootV2 method to reload stock firmware, which I found on the firmware thread above - this was big, as my phone is with Wind Mobile in Canada and the link is the right one. The only thing I picked up from a different website was to use a computer with USB 2 ports. This is what I did, but I don't know one way or the other if USB 2 was needed. .
Can't thank you hard working guys enough for the time you take to put these threads together. I'm back up and running. As a bonus, after a big clean up in the process, my phone is running fast again.
Thanks everyone.

[Completed] Nexus 7(2012) 3G bootloop without an option to fastboot

Hi, people. I hope you can help me.
My problem is that my rooted Nexus 7 (2012) with 3G and kitkat Stock Android suddenly turned into so called brick state. Only Google logo was appearing during the boot, and that will last forever. Then, just for interest, I tried to enter into the recovery mode (Clockwork Recovery v6.0.4.3 for tilapia), but the device did not go into it. The logo of CWM appeared in the middle of the screen and then the device reboots automatically showing the Google logo screen for several seconds and then going into recovery mode with the CWM logo appearing on the centre of the screen, and then reboot again. This recovery bootloop lasts forever or till the battery runs out. I tried to use
Code:
adb devices
and
Code:
fastboot devices
on my nexus 4, everythings works fine (meaning drivers are installed correclty). But
Code:
fastboot devices
for the nexus 7 outputs into
Code:
- waiting for device -
I tried to force the battery to run out and then tried to go into fastboot, but that did not help, the recovery bootloop appeared on its own again. Please, help me, I don't know what to do.
EDIT. I tried to pull out the battery for a half day (disconnect battery connectors) in hope that this will somehow reset the boot options, but this did not help.
Any thoughts?
Also, if the thread is not in the appropriate branch of the forum, please, let me know, probably at correct location I will find more help. Thanks.
EDIT2. I solved the problem by trying to enter the bootloader mode via adb. But to enter bootloader required a liitle bit of humoristic approach. I was pressing UP then ENTER to enter fastboot mode via termianl (#adb reboot-bootloader) for 5 to 10 minutes. When I managed to enter the fastboot, I flashed TWRP recovery for tilapia and the latest 5.1 Lopllipop But it seems there is a bug in the stock recovery because it does not work with NEXUS 7, the last two updates of Kitkat and Lollipop required to flash custom recovery, because the stock one did the bootloop on either Google logo or the animation of "beautiful" circles.
Thanks for reading, hope this might help someone.
from danik

Hi,
Glad to hear it solved
Good Luck!
Thread Closed.

Bricked LG G6 H870, tried it all

Hello everyone,
I have a European H870 and unlocked the bootloader, used ADB/FASTBOOT to install TWRP but could never get to start in recovery because of a warning screen that shows up because it is unlocked.
Couldn't get into recovery from both ADB or by utilizing the keypress method. Vol-down+power --> logo --> release power for 1 sec then back on it. I even tried with other variants of that but could never get into recovery or DL mode. What's the point of unlocking the bootloader if you can't do anything afterwards because of a stoopid warning screen?
I never had that issue with my Samsung Mini S3. But with the LG's that I have, since the bootloaders were locked, the phones display this warning screen upon powering up. I can't be the only one with this issue unless I was doing it wrong. But I wasn't. So...anyway.
So with my G5 H850 I got around this problem by using FASTBOOT FLASH RECOVERY TWRP*.IMG and then FASTBOOT REBOOT before using ADB REBOOT RECOVERY during the boot process to get into recovery before the phone had fully booted.
So I tried the same with the G6 H870, of which I also cannot get into DL mode or recovery because of this screen. The only difference was that there is something different about how the H870 loads the system so that I could not run ADB commands until the phone was already 100% booted and thus rendering my recovery flash useless.
I ended up doing something that caused my phone to always boot into fastboot so I downloaded what I thought at the time was the correct boot.img and flashed it. And now I'm at the current situation where the phone boots past the warning screen and into the logo screen but then stops for a few minutes before rebooting. This process endlessly repeating. It is obvious to me that the boot.img was incorrect.
So what I have done so far is loading all Qualcomm drivers, LG drivers, QFIL and QPST (drivers being installed or uninstalled for each instance that requires them). The problem now is that the phone shows up on a COM port but is is unrecognized to all the different software and thus can I not communicate or flash anything to it.
A couple of unbricking procedures that I tried are:
https://forum.xda-developers.com/lg-g6/how-to/lg-g6-unbrick-method-t3935924
https://androidmtk.com/use-qpst-flash-tool
There were more but I cleared my browser's memory.
So, do I need to invest in an Octoplus device to get past this or is there another way?
Thank you.

Stuck on TWRP's "teamwin" loading screen after years of working normally and no changes

Hello, I've been using this phone for more than a few years now. Reflashed the system a few times over the years and was currently on Ivan_Meler's amazing LineageOS 18.
I saw that a bug on his 19.1 version I was experiencing was potentially fixed, so I started preparing to switch to that.
First order of business was going to recovery and doing a full backup, I had gone into recovery not too long ago.
Except I got boot looped instantly.
The current situation is:
- Model is SM-G930F
- The device is rooted
- Device will not stay turned off, if I force turn off with volume down + power it reboots instead
- Device is able to get into download mode and it seems to work normally
- Device will always boot to recovery, except when I ask to boot to download mode by volume down + power + home (not sure if there is a button combination for specifically booting to system, lmk If there is)
Things I already tried:
- Letting the battery run out completely to hopefully clear some cache -> Device tries to boot to recovery as soon as I plug the charger in
- Using ADB during the stuck splash screen -> Device eventually gets recognized by windows but it throws the generic "Your USB device malfunctioned" error, ADB doesn`t recognize it.
- Rebooting by launching a harmless command in Heimdell -> Device reboots but nothing else changes, still stuck.
- Letting battery run out at different stages, like in the stuck teamwin splashscreen, in the warning message before download mode and in download mode -> nothing changes
Additional information from the moment I tried to get to recovery and got stuck:
- I fat fingered "reboot" instead of turning off the phone, so I just held down volume up + home to get into recovery (I had already done this successfully before).
- My phone has USB debugging turned on
- My phone was plugged to my PC in USB Tethering mode when I tried to get to recovery
- My phone was set to use USB Tethering mode by default when plugged via USB, because I use that function a lot.
- My PC had the ADB server running, but was not actively running anything on device at the time.
I remember having been stuck in this same situation before and being able to recover it without losing data. But I have no recollection of how I did it.
If there was a way to make my phone stop trying to reboot and just turn off, im sure that
I would be able to boot into system, because i dont see how anything could've gotten messed up there since the phone rebooted normally and wasn`t reflashed or anythng
I really didn't want to have to wipe it, since my last full backup was a few months ago.
Do you guys have any suggestions? I was thinking of trying to flash back the exact same TWRP version through Odin, without flashing anything else. And seeing if that fixes it since the version is shown in the teamwin loading screen, would that be safe?

Hi, any progress ? I'm in the very similar situation, but flashing the same TWRP with Odin didn't help and I'm still stuck on TWRP logo. And adb doesn't see the device (neither when I'm in download mode nor when I'm on TWRP logo)

Is the device softbricked?
Try Frp HiJacker
All Samsung Frp HiJacker by Hagard (2017)
All Samsung FRP HiJacker 2017 latest updated tool.This tool 100% working and tested. FRP HiJacker V1.0 Features: * Remove Samsung FRP 2017 in Download Mode (No More Combination Files and No more tricks) * Softbrick fixer *Phone...
forum.xda-developers.com
Had similar problems myself