Boot Loop for Galaxy S5 (G900T) - Never rooted - Galaxy S 5 Q&A, Help & Troubleshooting

Today, my mom's GS5 became stuck in a boot loop and I don't know how it happened since it's her phone and neither does she. I believe it is running 5.1.1 but I could be off by an update or two. The phone is NOT rooted and has never had any software customizations at all.
When booting, the green android pops up for maybe two-tenths of a second saying "installing system update..." and then it quickly changes to saying "no command" at which point the white screen with "T-mobile" comes up and gets stuck there, giving off a small vibration every 13 seconds.
I know the battery was low when this starting happening, so maybe the phone could have been installing an update and the battery died during it, but my mom didn't initiate an update as far as she knows (she's not too tech savy), but I can't say with any certainty how it happened.
I have already tried removing the battery. I can boot into recovery mode and I tried wiping the cache but that didn't fix anything. I can't boot into safe mode.
If anyone has any solutions or ideas, I'd greatly appreciate it! I'm hoping to not have to wipe the internal memory because there are a ton of prom pictures on there from just last weekend that were just taken and haven't been backed up, so my mom really wants those back. I know I've managed to flash my Droid Razr M before when it was rooted and stuck in a bootloop and I managed to keep my internal data somehow, so I'm hoping it is possible
Thanks in advance for any help!

Related

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

[Q] Nexus 7(2012) stuck in fast boot mode, bricked?

Have a standard Nexus 7(2012), 18m old. OTA upped to Android 4.4.4. a month+ ago. Never rooted. From then on it has lasted a week or less before freezes/reboots while using apps or even nothing at all.
Have undertaken boots to fastboot mode (android on its back, door open but no red triangle) and then entered recovery mode to wipe system cache and then do a factory reset. This sometimes progresses thru startup restoring apps ok. Sometimes it crashes part way thru. Often get background Chrome and Maps crashes of late as it redownloads my old apps.
Google HW support line recommended this course of action until last time when desperate Indian woman out of her depth tried to say it was a hardware fault and palmed me off on Ausus(uk) saying they did a 2yr warranty... which I think they don't. Still to investigate that one.
The reboots kicked off again today. So did the usual: did a cache clear then factory reset and it restarted. Now it crashed while the Android coloured balls still rotating! And forcing into fast mode to do a 2nd factory reset failed as when I select Recovery Mode it now says "Booting failed" in small letters at the top and dumps u back in Recovery mode, though less the Android logo on its back. Cannot restart bootloader either, same error. Rebooting just freezes with "Google" displayed.
Have I "bricked it" somehow. How to I get past this?
As a novice, I have got Nexus Root Toolkit v1.8.5and tried to reflash to stock 4.4.4 rom on it. But bootloader is locked, as it is delivered, and it will not unlock it. (read from The Definitive Guide on How to Restore Your Nexus 7 Tablet (Even if You've Bricked It from nexus7 wonderhowto site)
Anyone got any info on what to do here? Better reflash tool/instructions? Is it hardware problem? Do Asus uk do a 2yr warranty that I need after 18months? Is this tablet permanently a dead parrot?
Any help, I am desperate here. Thanks

Stuck in Boot Loop (Recovery mode doesn't work)

Hi, I replaced the battery in my Moto X Pure edition and when I tried to power it on it just kept restarting. The phone would not power on before the battery was replaced and was basically bricked. Anyway, I can't get it to boot into recovery mode or show the exclamation point. I can open the bootloader but it seems to just ignore it and after I exit it nothing changes. I don't know what to do. If any of you know please help!
P.S. I never reflashed the ROM or anything everything is stock.
Similar issue
I am unable to get TWRP to load on my phone, I woke up two days ago and had seemingly powered off overnight despite it being on a charger and the notification light was still on (I'm using lineageOS 14.1 so the light under speaker grill is functional) after powering the phone on I started getting Google play services stopped working messages. Trying to fix it I cleared the cache for the app and rebooted, the issue persisted so I decided to load a back up through TWRP but it will not load for me. It just loops the loading screen for TWRP. Any useful ideas or insights would be greatly appreciated.

Verizon S7 Keep Freezing When booted into Android

Hi everyone.
I've got a g930v last year, someday it freezes itself, I really haven't done anything, It just keeps freezing when it passed the booting logo screen, even boot into safe mode...
I've done factory reset, even re-install the stock rom on it...
I would be grateful if any idea comes up...
attached video for ref

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!

Categories

Resources