I flashed Lineage OS 16 and after 4 days to a week my phone rebooted into TWRP and is stuck in that loop. I flashed a second time and the same thing happened. When it was functional, it would randomly freeze up, where I could see the notification bar but the rest of the screen would be blacked out and I would have to restart the device.
Any thoughts?
Related
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.
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.
I installed a few days ago AospExtended Nougat ROM, along with Lambda Kernel and Magisk
I worked fine for a few days, apart from Magisk haing a bug with "hide magisk"
Yesterday I plugged in my phone to my PC and I selected MTP mode and, as it was usual, it crashed and rebooted
This has been for me normal behaviour for about a year, so I wasn't worried
But it never booted back
It now boots ad infinitum, loading the LG screen for much more than usual and then launching the Android boot animation and never going into the ROM; I tried leaving it out for about two hours, it just won't boot
I also can't access recovery mode, pressing VolDown+PwrBtn just reboots it and then shuts it off
I was able to get it to boot in download mode but I never used it so I don't really know what I can or should do with it
Is there any way to recover my phone, let alone the data?
Should I just trash it and go buy a new one?
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,
My stock Verizon S7 Edge has been stuck in boot loop and won't load all the way to the OS. I even flashed it via Odin and it is still looping. What do you think is wrong with it? Thanks for your help.
Condition of the phone is great except one day it was in a bag in direct sun and got very hot. 2 days later I started having problems. Always had stock ROM.
More detailed version of events:
June: in hot weather, the phone would randomly turn off and show 0% battery. This happened just a handful of times then it was OK.
August: 2 days after getting quite hot in my bag that I left in the sun, it randomly rebooted and got in a boot loop. I tried troubleshooting guides and eventually had to do a factory reset. This fixed the problem for 5 days, but then it started boot looping and wouldn't load to the OS. Factory reset didn't work.
Today: finally got around to installing stock Verizon Oreo ROM via Odin. Started setting up the phone but now it is boot looping again.