First, a crucial app (TickerHistory) kept FC'ing and then the phone would reboot. I booted into recovery and fiddled around with odin for the first time, and now the phone won't boot at all.
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.
Hello everyone.
I had been using my T-Mobile S4 for close to two years. Had been running custom ROM this entire time with not much problems. The worst I've had only required a simple re-flash.
This time, the phone randomly shut off as I was messaging someone. Any attempts to boot it will result in it being stuck at either the "Samsung Galaxy S4" screen or the screen after, and then bootloop. It is worth noting that there was not a set amount of time before it freezes.
It took me a few tries before getting into recovery mode, and I have tried clearing the cache as well as data, but it still would not work.
For the last resort (after a couple hours of troubleshooting and flashing roms), I decided to re-partition the phone with the stock pit file along with stock ROM through Odin. Odin said everything finished successfully, but the bootloop is still going on. Nothing has changed.
Is it a hardware problem that I am experiencing? What is the next step that I should be taking, besides using up the warranty?
Update: On some boots, it would result in artifacts on the screen.
Sometimes it would actually boot into the "Optimizing apps" screen, but it would randomly shut off and continue with the bootloop again...
So pissed off and annoyed now....
Attempted to upgrade to marshmallow, then tried root over and over again. I get that it's a wip, but no such luck. Eventually I got annoyed and decided to just wait so I tried downgrading back to 5.1.1. For some reason now trying to root that results in boot loop as well (even tried older supersu). After a couple attempts with no such luck, tried to install stock back and now before even trying to root, the device doesn't want to boot up properly anymore.
I tried fastbooting bootloader, boot, recovery, and system, once I try to staRte up normally, android boot logo goes through but the first startup "upgrading apps" goes through its list and right after finishes, says "starting apps" but almost immediately boots back to the boot splash screen, where the process repeats itself over and over.
Trying to reflash everything results in same issue now. I've tried at lEast 4 times. Have I bricked my brand new nexus player?
Hoping for some answers so I can sleep on it. Pissed off and annoyed now. Ugh.
Figured it out. Didn't know how to bring up commands in recovery mode. Had to factory wipe system and cache.
Sorry for the wasted post. Mod please delete this if possible. Thanks.
So I was going through instagram like every other day when suddenly my phone boots and the boot just looped and looped... Then I made the hard decision of resetting my phone completely. Did cache wipe and data wipe and thought that it would work now but nope. Still in boot loop. Then when I got home I thought that I'm going to Odin and installing the stock ROM from this site. Then I continued to install the ROM, NEE version (since I live in Finland), and it got installed. Booted and looped. Looping and looping and looping right next to me. I tried using Samsung Kies but it was not doing anything when I was in download mode. Tried the emergency thing but nothing popped up to the list that it should have popped on. Don't know what I have done or what my phone has done. I didn't have root at the time it started the looping nor I have now and don't plan to get it again. Didn't have any other recovery than the stock recovery and have never used triangle away. Suggestions?
Using Odin, flash a rom with a pit file. That should repartition the phone and, hopefully, solve the issue.
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.