[Q] Galaxy s4 SGH M919 Tmo weird boot loop - General Questions and Answers

Hi, I am very new to this stuff so please excuse any dumb questions or improper terms.
I was attempting to install CM 12 on my GS4 running 4.4.4. Google search "install android 5.0.2 lollipop on tmobile galaxy s4" and click on the true android one. (XDA prevents me from posting outside links)
I tried to install TWRP recovery by downloading TWRP manager from the Play Store. I selected my phone and installed the package that ended in .zip. It alerted me that something was wrong so canceled it and installed the other package ending in .img. This one installed. Then it asked me if I wanted to reboot into recovery now. I did so and my phone turned off and turned back on.
It showed the normal Samsung logo with the blue "recovery booting" text. It never booted into recovery mode.
If I hold down the power button my phone turns off, and then a few seconds later it turns back on, right into the recover booting loop.
If I take out the battery and put it back in, it does not turn on automatically, but if I press the power button it goes into the loop.
I love my phone and I'm really nervous. Is my phone bricked? PLEASE HELP!!!

Related

My Galaxy Tab 7.0 plus (GT-6200) suddenly died, help please!

The unit has been used for about 2 months and remains quite new. It was quite stable before. Yesterday night, about half an hour after plugged in for charging and with WiFi Hotspot turned on for sharing 3G data to another netbook, the unit suddenly rebooted itself. It then stopped at the start-up screen and remained there for several minutes. I kept holding the power button for a few seconds to turn it off but it then automatically reboot itself afterwards, and stopped at the start-up screen again. It means that even complete turning off is not possible.
Trying to enter into recovery mode showed the following few lines:
# MANUAL MODE #
-- Updating application...
Copying Common Apks.
Click to expand...
Click to collapse
and then it automatically rebooted again. It means that it can't enter into recovery mode normally.
It was possible to enter into download mode. And it was the first time this machine went into download mode. I run Odin Downloader and flashed the official stock ROM. After showing "Pass", the device rebooted itself. Unfortunately, it still stopped at the start-up screen, just showing "Samsung Galaxy Tab 7.0 plus". It is really troubesome. I have experience playing several Android devices before and it is the first time I face such troublesome problem.
The device is an official product. The biggest problem is that the original purchase invoice was lost and most likely that I couldn't get official support, repair service or replacement.
May I ask if anyone would kindly provide me some help or advice. Thanks!
Instead of going into download mode go into recovery mode and see if there are any errors. Your scenario is sounding very similar to the one I had in the past.
I just ran into a nasty snag at boot logo as well. nandroid, stock kernel and factory reset were no help. Try Odin back to Stock, it still may not get past boot logo, hold vol up and power to get into recovery and factory reset. Hope it works for you.
Unfortunately I was unable to get into recovery mode even after odin flashing stock ROM.
It rebooted itself a few seconds after displaying some lines of text. I can't see the normal recovery menu.

[Q] HELP! International Version Samsung S3 won't boot up

Hello guys, my apology if I open this thread somewhere. I just couldn't find a perfect thread to post about these issues. My International Version Samsung Galaxy S3 won't boot up after I root it with ODIN. The rooting was fine as I was able to download some apps in google play for root users. Eventually, I restarted my phone & there you go! It didn't boot up, all I see was a samsung logo & then my phone dead again. I got into recovery mode(home + power + ctrl up), i tried 'wipe data/reset factory" but still to no avail after I reboot my device, it will take me to the start up set-up of samsung (just like when you unbox your phone, the set up message shown when you 1st turn on your phone) but I stucked on the language, after I select language, my phone hangs & dead again. I can get into download mode too (home+power+cntrl dwn) but it will just stuck me to "downloading... do not turn off target'. Can somebody help me with this? I read about flashing & stuff but I just dunno how to do it though I tried but using SGS3 toolkit but again I am stuch at waiting for debugging... ANy help is appreciated.. Thanks

Strange Rom Manager/Clockwork Mod problems

I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
somesortofthing said:
I have a rooted Verizon Wireless Galaxy S3, for reference. So today I decided to attempt to install Cyanogenmod and searched for something to install it on my phone. I found Rom Manager on the Play Store and installed it, and went into it. I installed Clockworkmod and flashed it, and everything went reasonably well until I rebooted my phone. At this point, it automatically booted into Recovery Mode, or at least tried to. What it really did was display the screen with the Samsung logo and "RECOVERY BOOTING....." at the top in blue letters. Then, it shows a screen with a yellow warning triangle, which gave me the "System Software not authorized by Verizon Wireless has been found on your phone" message, saying "SECURE FAIL:KERNEL" at the top. Now, after a bit of searching, I had found that I should flash a factory image, so I connected my phone to my computer, and that's when the strange stuff began. First, my phone started vibrating approximately once every second for a short amount of time(about 0.1 second) and my computer wasn't detecting it. When I tried to turn my phone on, it just displayed the normal first boot screen and then nothing else happened, and it went back to a black screen.
I've looked all over the place, but I can't find anyone that has encountered my problems and I have no idea how to proceed.
Click to expand...
Click to collapse
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
ShapesBlue said:
Were you on either of the locked bootloaders of 4.3 or 4.4.2? If so your issues lies there to begin with. No custom recovery other than safestrap will work with the locked bootloaders. Your lucky you didn't hard brick it
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
Well, can I somehow get my phone into working order? Because it's as good as bricked right now.

[Completed] SGS4 i9505 / TWRP 2.8.1.0 / CM12.1-20150519 / Bricked

Hello guys.
I do have an SGS4 i9505 which runs on CM for more than two years now.
In February 2015, I've installed TWRP 2.8.1.0 then CM12 and the associated GAPPS.
Today, May 20th, I did the update to CM12.1-20150519 from the updater of my phone (Settings, About..., CyanogenMod).
Unfortunately, since then, my phone does not want to boot anymore. It keeps boot looping. I can see the (nice) "Samsung Galaxy S4 i9505" screen but nothing more.
I can access the Download Mode but only for a couple seconds, then the phone shuts down.
I can press the VolDown + Power button to try to access my recovery (TWRP 2.8.1.0 as I previous mentioned), I do thee the same "Samsung Galaxy S4 i9505" screen bith the "recovery access" in blue in the top left corner of the screen, but that's all.
Have you guys any idea how I could skip this loop and proper reinstall ? Is my phone hard bricked ?
Thanks in advance,
Daga.
XDA Visitor said:
Hello guys.
I do have an SGS4 i9505 which runs on CM for more than two years now.
In February 2015, I've installed TWRP 2.8.1.0 then CM12 and the associated GAPPS.
Today, May 20th, I did the update to CM12.1-20150519 from the updater of my phone (Settings, About..., CyanogenMod).
Unfortunately, since then, my phone does not want to boot anymore. It keeps boot looping. I can see the (nice) "Samsung Galaxy S4 i9505" screen but nothing more.
I can access the Download Mode but only for a couple seconds, then the phone shuts down.
I can press the VolDown + Power button to try to access my recovery (TWRP 2.8.1.0 as I previous mentioned), I do thee the same "Samsung Galaxy S4 i9505" screen bith the "recovery access" in blue in the top left corner of the screen, but that's all.
Have you guys any idea how I could skip this loop and proper reinstall ? Is my phone hard bricked ?
Thanks in advance,
Daga.
Click to expand...
Click to collapse
Hello, and welcome to XDA! It is possible that you needed to update your bootloader as well as the rom, hence the bootloop. You can get help by asking your question in this help thread: http://forum.xda-developers.com/galaxy-s4/help
If you can access your bootloader, your phone is not lost at all. You can flash factory firmware, or perhaps simply flash the latest bootloader, or the recovery back. There is plenty of information on how to do this here: http://forum.xda-developers.com/showthread.php?t=2265477
Good luck!

S6 stuck in bootloop! Help!

Hello!
My S6 is rooted with Xtrestolite (2.3 I think). It has been like this for a long time, maybe a month. Then today, I simply powered off my phone. 1 hour later when I tried to power it up again, it got stuck in a bootloop. It keeps cycling between the 'Samsung Galaxy S6' screen and the screen where it shows 'Samsung' with blue things coming off it. I also have Xposed installed but I'm not sure if it's anything to do with that.
I have tried Power + Vol Down but it just continues and I also got into recovery (only when plugged in to the charger) but it didn't do anything either. Any suggestions as to what it could be? It's really important that my phone is working tonight.
Thanks!
Let me just go straight to the point your (s6 soft bricked ) all you need to do is to flash the firmware get it from. http://forum.xda-developers.com/galaxy-s6/general/stock-firmware-official-stock-firmware-t3086387 ....its up to 1gb file
**Flash with latest Odin3** link http://www.mediafire.com/?to0epiiccqx56jd
**Samsung smart switch**
**USB cable with PC**
See more guides from http://www.w0lfdroid.com/2015/04/H...rmware-on-Samsung-Galaxy-S6-S6-Edge.html?m=1

Categories

Resources