Database Users

[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.

Black lines on the screen

I messed up with my LG G2 D802 and i need help because i believe it's a software problem.
When i was installing the latest cm12.1 nightly, after trying a few other roms, i also installed, by mistake, an old jb bootloader/bootstack.
As result the phone entered in Bootloop, but not a normal bootloop, on the screen start appearing some crazy interferences and then the phone boot up, but the screen not. The phone made sounds and the touchscreen work, but the screen was black/off.
I've managed to solve the problem with an unbrick method, but now i have a huge problem: the screen, on the rigth side, from the top to the botton has 6/7 black lines. I have no idea how to solve this and if is a hardware problem ... I've read it's an kernel problem, not hardware, but don't know how to solve the problem :/
Picture:
https://meocloud.pt/link/58d13900-ffa8-4114-8957-8c4b973bad1a/IMG_20150916_020454.jpg/

I feel your pain
Hi mate
Same thing happened to me.
Background info: I had successfully upgraded to CM12.1 , was running fine for a few days then I wanted to update my TWRP, updated the recovery and just went to check that I had OTG cable support then boom, boot loop.
It didnt just loop it just loaded loaded loaded, then the screen made some funny sounds. and then shut down. I hard reset to recovery and reinstalled CM12.1 and was able to successfully exit the loop. but damage to screen had occurred in the exact same place, and method right side of the screen.
Tried rinstalling original jellybean software from my backup. no success, and also flashing other versions of CM12.1 nothing.
After some research I saw that this is a manufacturing fault and that this occured quite often. it appears that the best solution is to buy a new screen as it is the actual hardware that is damaged in the screen digitizer. I might be wrong, and I pray that I am because I want to fix it too. in the end I just bought a new note 4 (not note 5 as i wanted SDcard storage). Phone was 2 years old and a new screen costs a fortune. But i miss my little G2 and its super fast speed and simpleness. :crying::crying:
If someone else has the solution to this problem on the forum we are all ears.

Noobly flashed Yotaphone 2 constantly shows the yotaphone loading screen

I am a total beginner in flashing.....but i tried it myself and now the Yotaphone 2 ist constantly loading the "YotaPhone" loading screen. I flashed it with the yotaflasher, after downloading the "4.4.3-S01-003-EU1.0.3.51a.zip" file in the flasher app. Then i selected "flash device" and the app did it's job. Now the phone is constantly loading the mentioned screen :-/
I bought it from China, so i have the y206 with android 4.4.2. If anyone could help me... I would appretiate it very much
There are many threads about this problem, but my phone is passing the "powered by android" screen... so i don't know how to progress.

when I had this situation about a week ago it helped when I got into recovery mode and wiped dalvik/ART

keeeper said:
when I had this situation about a week ago it helped when I got into recovery mode and wiped dalvik/ART
Click to expand...
Click to collapse
Thanks for the fast reply keeper. The phone doesn't let me reach that mode. I had to wait until the battery died, but if i charge the phone it immidiately boots and ends up loading the "YotaPhone" screen non-stop

Firmware update
i flashed it now with the "5.0.0-RU1.1.99.zip" and exited the yotaflasher.....now it froze in the "powered by android" screen. Let's see what happens

SwantherOne said:
i flashed it now with the "5.0.0-RU1.1.99.zip" and exited the yotaflasher.....now it froze in the "powered by android" screen. Let's see what happens
Click to expand...
Click to collapse
Disconnect the battery for some time and flash system manually. Follow this thread:
http://forum.xda-developers.com/yotaphone-one/help/y2-bootloop-to-recovery-t3509883/page1

Problem(s) solved
After flashing it to the newest EU build i tried to enter your mentionedode again. After some tries i finally reached it (volume up + power button). I cleared all possible data and selected the reboot options......some minutes later the phone load the lollipop Settings Screen
Thanks for your help keeeper, I appreciate it very much :highfive:!!!

Autocorrect
Excuse the autocorrect fails.... Have to get used to this phone ^^

Stuck on encryption lock screen, won't boot PLEASE HELP

Hey everyone,
So my phone died and then I got it charged and turned on and it booted up to the encryption lock screen where it says to start up your device, enter your pin. So I enter my pin and then its says, "verified" and then "starting android". and then a padlock appears on the screen, it opens, and there's like a load up circle going around it. At first, I let the phone sit to see if it would do anything but after an hour, I figured something is wrong. I dont know why this happened, I think I might have accidentally turned on the secondary encryption, but this really sucks, I don't want to have to factory reset and lose all my pictures and data. I can boot into recovery mode but sometimes when i turn it on it shows a screen that says installing update and has like a google ring looking thing that should be spinning around but it looks like its glitching out, after that screen it will go to a no command screen, and then it will eventually reach recovery mode. I really hope someone can help or knows what is going on because, I really dont want to lose all my stuff.
Thanks for your time
I tried posting link but im new, if you look up s7 edge frozen encryption, its the first link , another person describes the same issue.

I had this issue. In recovery, tell it to clear the delvic cache. Then try a reboot.
It too a few attempts before the phone would not boot directly into recovery. But once i got it to do a normal boot, it started normally.
Then after it's running, back it all up, boot into recovery, and do a system restore.

Hi I wonder if anyone can help me. I restarted my phone, it asks for my pin which I enter correctly. It then gets stuck on spinning padlock. I've tried a soft reset (I think that's what it's called, holding down power and volume keys). It restarts, I enter pin, it says starting android then gets stuck again. I'm not very tech minded (typical girl). Can anyone help. I'd rather not lose all my photos and apps. Thank you so so much in advance. Toni x

I am facing the same issue, but with a Samsung Galaxy S8.
- Safe mode: doesn't boot
- Recovery mode: works, clear cache doesn't solve the problem.
So since nothing worked to make it work (except the Factory Reset, but I didn't tried this option), I decided to wait in the padlock screen. After 3 hours the phone started.
I guess that the phone is decrypting some big file during startup. Indeed, some days before before this problem happens, I downloaded some big files via torrent (~2-4 GB video files).
I'll delete these files and make some tests to understand the source of this problem.

Have same issue after recent update, tried clearing cache and safe mode but didn't help, been on padlock for about 10 hours now, any solutions/experiences?
ps: on stock rom with stock recovery, no root or anything of that sort at all.

Have exactly the same issue..Please help
After recent update, tried clearing cache and safe mode but didn't help, been on padlock for about 10 hours now, any solutions/experiences?
ps: on stock rom with stock recovery, no root or anything of that sort at all.

SM-G935A Stuck in multiple different loops

Howdy, all! This is my first post on XDA, and it comes after days of frustration. I'm relatively new to the back-end of phones, especially android. What happened is this:
About 4 or 5 days ago, I woke up to my phone completely dead, despite being plugged in. I tried turning it on, and got stuck on the "Samsung Galaxy S7" screen for a while, and then finally a blue screen with the android logo saying "Installing update." That process seemed to end rather abruptly and then went back to the first loading screen, followed by a black screen, then "Samsung," and repeat. At this point I tried plugging the phone in to see if smart switch would detect it... and this is where my ineptitude with phones starts to show.
I didn't realize that smart switch has an emergency recovery mode under "file," (*sigh*) so when my phone didn't show up on the main screen I assumed the worst. After some google-searches, I went in to clear the cache through Android Recovery. I was still trying to save my data at this point, so I didn't just erase everything and start fresh. I regret that now.
After clearing the cache, I rebooted the system through the menu, and was stuck in loop with the first screen being all black, except for some blue text in the upper left hand corner saying, "Recovery booting." The screen would then flash back to a blue screen with the android logo and "Installing system update," and then go black and repeat the whole process. Getting back into the recovery menu was sporadic after this, but was possible occasionally. This is where my ineptitude REALLY starts to show...
Despite having my current rom version displayed to me multiple times on the recovery menu, I neglected to write it down or record it in any way. Instead, I googled "SM-G935A stock firmware," and was able to find a presumably helpful link on these forums guiding me on flashing stock oreo files through Odin. I say presumably, because in the hands of someone who actually has knowledge on this subject, the thread was incredibly helpful. In my hands, however, it seemed to create a monster. I flashed the stock files downloaded from the link, and all looked good- Odin gave a solid pass, and the phone rebooted to the normal initial two loading screens. And then disaster- another boot loop. But this time, I have no idea what firmware used to be on my phone before I started fooling around.
At this point, I've had one near success with a flash of SM-G935AUCS8CRK1 through Odin where I actually got a blue LED indicator for the first time, as well as the AT&T logo and chime. Now, however, it seems that I either get stuck in that loop, or back to the original "Recovery Booting," "Installing Update," loop.
The phone is not rooted. I don't have a custom recovery installed, and I'm not even sure if I ever got around to enabling developer mode through the OS settings.
ANY help is appreciated. I'm pretty sure I've made the problem significantly worse than it was originally, but I've at least learned a lot in the process- hopefully I won't mess things up this badly in the future! Thanks for taking the time to read through this mess!