I have Cyanogenmod 11 installed in my device, and I tried encrypting it. Everything was ok, it went til 100 % and passed the Samsung Galaxy S3 Neo startup screen, but now it's stuck in bootloop, with the Cyanogenmod blue arrow going in circles. It's been like that for more than 20 minutes, so I know it exceeded it's time of booting. I encrypted my phone 2 times already, the first time with the settings in Cyanogenmod, and it got stuck in bootloop, so I took out the battery and put it back on booting my phone in recovery mode (I use TWRP), and formatting the data on my phone. All the data was wiped. the second time I encrypted the phone using terminal emulator, and the same thing happened: it's stuck in bootloop. Now, I'm not asking how to unbrick my device, because that I know, I'm asking how can I encrypt it without it getting stuck in bootloop.
Related
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.
Got a problem with my samsung galaxy s5. A few days ago it was working fine but occasionally randomly rebooted itself. It was be on a bootloop then it will boot up normallly after while.
Randomly the phone had ended up in a bootloop which it is not able to recover from.
i tried using the recovery mode, but that doesnt work. The phone will boot up the first logo after while, but usually it will boot up to a white screen, then will constantky repeat and never end. The screen is working fine, i do not know why it is booting to white screen.
My phone did that with stock ROM bootloop, I found a good ROM and cm12, soz I didn't answer your question that well. But to me the white screen your getting sounds likes you've deleted your boot loader, but don't take my word for it as I'm not a XDA developer, but I'd try and reload boot loader, but wait till you get a reply from xda
ok so first off this phone was brand new when i got it 6 months ago. no matter what rom i flash or kernel combo, my phone always ends up 'freezing' up on me. after sitting there staring at the unresponsive phone i will either yank the battery or keycombo reboot. upon trying to boot again it doesnt get past the red and blue writing about enforcing whatever just sits there. so i boot to twrp but it hangs at splash screen if i wait a long time it will eventually go but im talking like 30 mins. weird right? when i do get back in i can restore a backup or wipe, clearing cache and dalvik does nothing it just sits at boot logo. and flashing kernels does nothing. what could be doing this?
So, I wanted to get some ideas here before I install the required things to try and sideload the stockrom, but here is the situation..
The wifes S5 on Wind mobile (yea, freedom..) started randomly rebooting a few weeks ago, and up to a couple days ago, become more frequent. I went ahead and booted into twrp and did a factory reset. The phone is completely stock, except for twrp. We do have a nandroid backup on the sd card.
Anyway, the reset seemed to have fixed the issue at first, but shortly the reboots started again, became more frequent as time went on, up until today; wife comes home with the phone stuck in a bootloop. Won't go past the Samsung Galaxy boot screen.
I was going to re-flash the stock rom I got off sammobile or whatever, but the phone wont boot into recovery now. TWRP blue backdrop shows, then phone reboots 5 seconds or so later, and bootloops.
I'm out of ideas. I'll try and do an ADB sideload.. or, Odin, maybe. Luckily the phone is able to get into Download mode.
Could this be hardware related? I have a feeling there's some sort of damage due to her dropping the phone quite often. Never cracked a screen though. Amazing.
Hello,
I'm currently experiencing a bootloop on my phone, it gets to the resurrection remix logo screen during boot then restarts. I've tried booting into recovery and download mode. When I try to boot into recovery it loads the factory reset screen as usual but when I say yes to the reset in order to launch TWRP it just goes to the LG logo, then remix and restarts all over. I got into download mode one time since this started but since then I've made countless attempts to boot into it again and can't.
What I was doing right before this happened is, I recently completely wiped my phone, flashed stock firmware, wiped, then installed resurrection remix. Everything was going perfect, it started no problem, I went through and cleaned up some apps I didn't want etc normal setup steps then I used the power menu to boot into recovery instead of just using the hardware keys and the bootloop started.
Besides the not booting, the other major issue here is that it never stays connected to the pc via adb long enough to do any actions or flash a single file. By the time the pc sees it and adb sees it, I have roughly 2 seconds before it restarts again.
I really really really need any help I can get please ASAP as this is my mom's phone and she needs it for work in 4 hours. This issue started about four hours ago and I've been trying to fix it ever since. I feel like I have looked everywhere on here and through google but probably missed the solution. Before you ask, I'm 28 not a teenager and work in IT as a career for the last 12 years so don't get the wrong impression. She asked me to work on it because I had set it up a few months back with a lollipop version of resurrection remix and magisk, but in the last month or so she was having really poor performance and issues with settings crashing and a few other apps.
I hope you don't need any more info from me, if you do however I'll be here trying to fix it until she goes to work at least. I really could use the help and would greatly appreciate it.
Thank You