Database Users

[Q] i9500 rebooting into s4 logo even download mode is rebooting

my galaxy s4 is always boot looping into Samsung galaxy s4 screen. only the download mode screen appears but it reboots again after 5 seconds and keeps on rebooting . any help ?

Do you run with stock or custom recovery? Have you tried to (re-)flash a custom recovery (CWM highly recommended)?

slytidar said:
my galaxy s4 is always boot looping into Samsung galaxy s4 screen. only the download mode screen appears but it reboots again after 5 seconds and keeps on rebooting . any help ?
Click to expand...
Click to collapse
I had this problem once. I had to clear all user data,cache,dalvik and intall everything again

Chalao said:
Do you run with stock or custom recovery? Have you tried to (re-)flash a custom recovery (CWM highly recommended)?
Click to expand...
Click to collapse
thanks for the replay
i flashed a custom recovery. this happened later on. but now that the download mode is rebooting it slef and recovery isnt coming, i dont think i can flash a recovery..

MarceloSiciliano said:
I had this problem once. I had to clear all user data,cache,dalvik and intall everything again
Click to expand...
Click to collapse
cannto do it :/

slytidar said:
thanks for the replay
i flashed a custom recovery. this happened later on. but now that the download mode is rebooting it slef and recovery isnt coming, i dont think i can flash a recovery..
Click to expand...
Click to collapse
Hm, if I understand you correctly, you can boot into download mode but it just lasts a couple of seconds before it reboots on its own, right? You cannot boot into recovery as the screen simply stays black. Can you boot successfully into /system or does it bootloop as well?
Sounds like a hardbrick to me, the only thing I can think of before sending your phone in for repair is to pull out the battery for 1 hour or so, reinsert it and boot directly into download mode and see if it stays there. If it does, flash a custom recovery using Odin and check whether you can boot into it afterwards.

Chalao said:
Hm, if I understand you correctly, you can boot into download mode but it just lasts a couple of seconds before it reboots on its own, right? You cannot boot into recovery as the screen simply stays black. Can you boot successfully into /system or does it bootloop as well?
Sounds like a hardbrick to me, the only thing I can think of before sending your phone in for repair is to pull out the battery for 1 hour or so, reinsert it and boot directly into download mode and see if it stays there. If it does, flash a custom recovery using Odin and check whether you can boot into it afterwards.
Click to expand...
Click to collapse
well i cannot boot into download mode long enough to flash a recovery and i cant boot into system either .. maybe a hardware problem ?

slytidar said:
well i cannot boot into download mode long enough to flash a recovery and i cant boot into system either .. maybe a hardware problem ?
Click to expand...
Click to collapse
Looks like it, did you try pulling out the battery for 1 hour and follow the steps as suggested above?

Chalao said:
Looks like it, did you try pulling out the battery for 1 hour and follow the steps as suggested above?
Click to expand...
Click to collapse
now trying

I'm having the same problem here
dead phone, can't boot into recovery, automatically restarts seconds after going into download mode, it doesn't even charge, battery logo comes out aaaand restart, and it keep going
any help?

Im also having the same problem as of this last night.
cannot boot into recovery.
boots to download mode first screen but when I attempt to press volume up to accept, it reboots.
as soon as i put the battery in it cycles through the samsung logo.
tried removing memory card but didnt help.
tried keeping battery out overnight, nothing.
last thing i changed was flashing --> http://forum.xda-developers.com/showthread.php?t=2201860. did this about 2 days ago.
not sure if that has anything to do with it?

Ares1000101 said:
Im also having the same problem as of this last night.
cannot boot into recovery.
boots to download mode first screen but when I attempt to press volume up to accept, it reboots.
as soon as i put the battery in it cycles through the samsung logo.
tried removing memory card but didnt help.
tried keeping battery out overnight, nothing.
last thing i changed was flashing --> http://forum.xda-developers.com/showthread.php?t=2201860. did this about 2 days ago.
not sure if that has anything to do with it?
Click to expand...
Click to collapse
I think it has nothing to do with it
I'm, I was actually, on stock everything, rom, kernel and recovery

30 68336826
OK so I left my phone without a battery in it for the afternoon, just got back home and gave it a try.
It booted. No idea why or what actually went wrong.
Lets hope it doesn't happen again!

OK, So the point that the phone just start booting just the moment the battery is inserted got me thinking
IS IT THE POWER SWITCH?
and indeed it's, the power switch is stuck on, although I can feel the click when I push, still, seems like something is wrong with it
so I tried to suck it out, hit the phone softly few times while the power switch is facing the ground
inserted the battery, aaaand, it didn't start booting, pressed the power softly, and horaaaaay, it's working

Had the same issue and indeed I knocked the power button several times and it worked very well. Thank you! You saved my day

black heart said:
I'm having the same problem here
dead phone, can't boot into recovery, automatically restarts seconds after going into download mode, it doesn't even charge, battery logo comes out aaaand restart, and it keep going
any help?
Click to expand...
Click to collapse
same problem please help!

vaibhav2296 said:
same problem please help!
Click to expand...
Click to collapse
I have similar problem... and identified its power button.
How i identified is as phone switched on i hold menu button and volume down button together and
it booted in download mode, for download mode you have to keep pressing power button, volume
down button and menu button but it went without pressing power button.. so i assume that its power
button.
Try it... hope will identify your problem

same Problem
Hello!
I have the same problem, and disassemble the cell and saw that the button will operate properly .
Someone has managed to get out of this problem?

thanks a lot... i was facing same problem... i hit ma phn near power switch...again n again... it worked... love u xda

whoa, I just got this problem recently, because some of bezel around my phone has cracked, then I try to glue it roughly.
at the other hand, I tried to install new kernel. I tought that kernel make my phone bricked. then I found this thread. so I open my case. and found my glue sticked to the power button, remove it and. voilaaaa~
thank you XDA. you never cease to amaze me. lol

if all else fails? Recovery bootloop issue.

here my issue.. so I'm using cm12.1 on my Canadian gaxaly note 3, and Im trying to reset my phone, which I thought would be just fine if I went to settings, then hit reset data function. in which it rebooted my phone, and tried to take me into recovery for whatever reason (likely to reset the phone..?) and its almost stuck there. it flashes like it tries to boot recovery and shows the team win logo for 2 seconds then shuts off and then displays the team win logo for 2 seconds and etc. etc, I tried to get it to download mode with no cigar, whatever button combination I do it always ends up booting recovery. cant turn it back on or anything. I plug it into my computer and it seems to not recognize it. I'm with virgin mobile right now and it's an almost 2 year old phone (got it the day after black Friday), so I'm guessing I'm out of luck for the manufacturer and the virgin mobile's help. Anyway I can fix the issue? any help would be appreciated.

Do you have access to a USB jig for force the phone into download mode?
What happens when you try to boot into download mode? Are you holding down the volume down, power and home button long enough?

nithiiyan25 said:
here my issue.. so I'm using cm12.1 on my Canadian gaxaly note 3, and Im trying to reset my phone, which I thought would be just fine if I went to settings, then hit reset data function. in which it rebooted my phone, and tried to take me into recovery for whatever reason (likely to reset the phone..?) and its almost stuck there. it flashes like it tries to boot recovery and shows the team win logo for 2 seconds then shuts off and then displays the team win logo for 2 seconds and etc. etc, I tried to get it to download mode with no cigar, whatever button combination I do it always ends up booting recovery. cant turn it back on or anything. I plug it into my computer and it seems to not recognize it. I'm with virgin mobile right now and it's an almost 2 year old phone (got it the day after black Friday), so I'm guessing I'm out of luck for the manufacturer and the virgin mobile's help. Anyway I can fix the issue? any help would be appreciated.
Click to expand...
Click to collapse
Flash "CWM/Philz" recovery for your phone model and go-to recovery mode by some step:
1. Pull out batery.
2. Push in again.
3. Press "volume up + home + power" and wait ~5second.
4. You in recovery mode

I recommend flashing 2.8.7.1 TWRP if you can get into download mode in order to flash another ROM. CWM is outdated and no longer being updated.
If you want to flash back to stock, grab the latest stock ROM from sammobile.com.

Galaxy S5 is stuck in boot loop after flashing factory in odin

Ok, it's been about 5 hours now and I have gotten no where with this phone.
My wife was complaining about her S5 being too slow. Trying to squeeze the life out of her phone for just a couple of more months, I thought that installing Lineage OS would give the old phone a good speed boost.
I got as far as getting TWRP to boot, but other than that the phone was in a boot loop. So I gave up and downloaded the latest factory odin flash. It's the T-mobile variant (SM-G900T) and I made sure to get the right image. I flashed it using Odin3 v3.12.
The problem is that after flashing the factory image, the phone is still in a boot loop. Now I can't even get into recovery holding power + vol up + home. I can still get into download mode.
I am at a lost right now. I promised my wife that I would have her phone working by the morning, and we can't really afford to get her a new phone right now. Please help if you can.

You have two options:
1. Either get into recovery and do a factory reset. Just try to hold Vol+, Power and Home long enough.
2. Or flash a factory low_ship firmware from download mode via Odin. It will erase everything.
https://drive.google.com/file/d/0B5WdcBhSEt-_MW15TS14UmlzbzA/view?usp=sharing
Will keep it for a while there.
There are 4 files, be sure to put them to appropriate slots in Odin.

bbsc said:
You have two options:
1. Either get into recovery and do a factory reset. Just try to hold Vol+, Power and Home long enough.
2. Or flash a factory low_ship firmware from download mode via Odin. It will erase everything.
Will keep it for a while there.
There are 4 files, be sure to put them to appropriate slots in Odin.
Click to expand...
Click to collapse
The factory low ship firmware did not work. It is still stuck in a boot loop. I'm getting a feeling that the phone is done for.

Have you applied 4 files in Odin?
The first boot may take up to 15 minutes so be patient.

bbsc said:
Have you applied 4 files in Odin?
The first boot may take up to 15 minutes so be patient.
Click to expand...
Click to collapse
Yes, I applied all 4. When the phone rebooted it said it was entering recovery, but after 30 seconds it restarts and continues to boot loop. I am not even able to enter recovery by holding vol up and home when it powers on.

zstabile15 said:
When the phone rebooted it said it was entering recovery, but after 30 seconds it restarts and continues to boot loop.
Click to expand...
Click to collapse
It's normal after low_ship firmware that it enters recovery and reboots again.
But what do you mean by "boot loop"?
The phone must continue to boot, you should see the logo for rather a long time and a blue LED light.
Just wait for 15 min.

bbsc said:
It's normal after low_ship firmware that it enters recovery and reboots again.
But what do you mean by "boot loop"?
The phone must continue to boot, you should see the logo for rather a long time and a blue LED light.
Just wait for 15 min.
Click to expand...
Click to collapse
It never enters recovery, it reboots before that happens.

Stuck on Linux penguin screen while booting, cannot force power off

EDIT: Thankfully I could resolve this issue on my own fairly easily. My battery drained relatively quickly, and the issue didn't repeat when I tried booting again.
Hi XDA developers community,
Using some of the guides on this fantastic website I flashed LineageOS on my A2017G a few months ago. Now I tried reverting back to stock by flashing the B03 Oreo zip file in EDL mode (this guide).
The first reboot was already successful: I powered the phone on via the power button, then went through "can't be checked for corruption" screen, then got into the screen with Tux (Linux penguin), pressed volume up to go to recovery just to be sure, and rebooted from there into Android.
Although instead of starting the setup process Android dropped my right into the lock screen. I assumed that was because I hadn't factory reset yet and my data partition still had garbage data (that was step 18 of the guide btw). So, I powered off, from Android, and tried booting into recovery mode again to do the factory reset. However, now, after the Android corruption warning screen, the Linux Tux screen just stays there. Recovery mode doesn't appear, neither did it boot into Android. I can't even force power off by pressing the button (I pressed 80 seconds straight, no effect). No combination of volume and power buttons does anything, even pressing and holding it.
Right now I plan to let the battery drain on its own to get the device to power off. That's probably gonna take some days because the battery is completely charged. Is there some other possibility to make it go faster? Maybe heat the battery up from the outside with a hair dryer? I would rather not open the phone up and take the battery out, because I don't have a heat gun and I'm also worried I'm gonna leave scratch marks or something (the process seems quite rough).
And also, when the battery is drained, is there any recommendation on what I should do? Simply try again, going into recovery mode? Flash the EDL file again?
Thank you for reading all this, and I'd be so glad for any help.

I'm having this screen too, I'm trying to gsi, but none works, only lineage 16, but it gives error and closes the system at 16, and at lineage 15 the battery is being drained very quickly
Any rom stock I try to flash via edl gets in bootloop on the penguin screen, I can do the flash via edl from a los rom with 15.1 with oki twrp, some bugs, but would like to return to stock, can anyone help us?

same issue
Hello there
I have the same issue, can you please help ?
Thank you in advance
prasnel

kangalioo said:
EDIT: Thankfully I could resolve this issue on my own fairly easily. My battery drained relatively quickly, and the issue didn't repeat when I tried booting again.
Hi XDA developers community,
Using some of the guides on this fantastic website I flashed LineageOS on my A2017G a few months ago. Now I tried reverting back to stock by flashing the B03 Oreo zip file in EDL mode (this guide).
The first reboot was already successful: I powered the phone on via the power button, then went through "can't be checked for corruption" screen, then got into the screen with Tux (Linux penguin), pressed volume up to go to recovery just to be sure, and rebooted from there into Android.
Although instead of starting the setup process Android dropped my right into the lock screen. I assumed that was because I hadn't factory reset yet and my data partition still had garbage data (that was step 18 of the guide btw). So, I powered off, from Android, and tried booting into recovery mode again to do the factory reset. However, now, after the Android corruption warning screen, the Linux Tux screen just stays there. Recovery mode doesn't appear, neither did it boot into Android. I can't even force power off by pressing the button (I pressed 80 seconds straight, no effect). No combination of volume and power buttons does anything, even pressing and holding it.
Right now I plan to let the battery drain on its own to get the device to power off. That's probably gonna take some days because the battery is completely charged. Is there some other possibility to make it go faster? Maybe heat the battery up from the outside with a hair dryer? I would rather not open the phone up and take the battery out, because I don't have a heat gun and I'm also worried I'm gonna leave scratch marks or something (the process seems quite rough).
And also, when the battery is drained, is there any recommendation on what I should do? Simply try again, going into recovery mode? Flash the EDL file again?
Thank you for reading all this, and I'd be so glad for any help.
Click to expand...
Click to collapse
My phone is like u "zte axon 7 a2017g " version oreo b03 please tell me the guide that u used to install lineage os and the tools please !!!
i just want to install unloack my bootloader , flash twrp , install lineage os so on ; please give me just the guide that u use !

afef said:
My phone is like u "zte axon 7 a2017g " version oreo b03 please tell me the guide that u used to install lineage os and the tools please !!!
i just want to install unloack my bootloader , flash twrp , install lineage os so on ; please give me just the guide that u use !
Click to expand...
Click to collapse
Sorry, I don't remember

kangalioo said:
Sorry, I don't remember
Click to expand...
Click to collapse
u don't remember if the guide is for marshmallow or naugat a 2017 g or i can use guide for a2017 u !

afef said:
u don't remember if the guide is for marshmallow or naugat a 2017 g or i can use guide for a2017 u !
Click to expand...
Click to collapse
what

kangalioo said:
EDIT: Thankfully I could resolve this issue on my own fairly easily. My battery drained relatively quickly, and the issue didn't repeat when I tried booting again.
Click to expand...
Click to collapse
Mine didn’t reboot at all after completely draining the battery several times. Same result, blocked on penguin screen, no way to get into a menu to flash anything ?

kangalioo said:
what
Click to expand...
Click to collapse
My phone is "zte axon 7 a2017g" version oreo b03 , i want to find guide make me unloack bootloader , flash twrp , install lineage os ; i just want for if u can remember if what can proch me i can use because the only guides exist are for a2017u or a 2017 g marshmallow or naugat
or if u can tell me if i can downgrading from oreo to marshmallow without unloack bootloader to use the guide exist for marshmallow !

afef said:
My phone is "zte axon 7 a2017g" version oreo b03 , i want to find guide make me unloack bootloader , flash twrp , install lineage os ; i just want for if u can remember if what can proch me i can use because the only guides exist are for a2017u or a 2017 g marshmallow or naugat
or if u can tell me if i can downgrading from oreo to marshmallow without unloack bootloader to use the guide exist for marshmallow !
Click to expand...
Click to collapse
As I said, I don't remember. I'm using a different phone altogether since half a year.

So because only a Tux logo appeared on the screen, my guess as to what happened is that while the Android Bootloader, also called "aboot" was booting the Linux kernel that Android runs off of, before the kernel could display the splash screen that appears when you power on the device, it encountered a critical error that either aborted the boot process, or caused the kernel to go into a kernel panic. Now as to why it displayed the Tux logo, it probably did that because when it crashed, it tried mapping the framebuffer to the display instead of keeping in hidden by default to show you the kernel buffer logs for you to troubleshoot the problem but instead, it shows the iconic Linux penguin that is usually hidden when the kernel boots.

S5e won't boot

I am at a loss here. After almost 2 years of working flawlessly, my s5e won't boot.
The screen got frozen while using anydesk, and had to force a restart (power button + up and fown volume buttons).
I can see the Samsung logo for less than a second, and then it switches off. Without touching anything, after some seconds the same thing happens.
I tried charching it and similar behaviour: i see charging circle for less than a second, and off again.
I AM AT A LOSS.
I managed to boot it pressing power+volume_up buttons and this is what i see (attached). It can stay like that for a long time so I guess battery and it's connection to the tablet are fine.
PLEASE ANY HELP WOULD BE VERY WELCOME
UPDATE:
I have tried MANY things in the 6 hours since I wrote this post. I am able to put the tablet in download mode and ODIN (and my PC) recognizes it. I am able to flash VBMETA but now TWRP (fail).
At some point the tablet rebooted in normal mode (why?) but got frozen again and had to reboot it.
Anyone can point me to how to recover it? I don't mind right now to loose what is in the internal memory.

Did you try to hard reboot (power_button + volume_down ) for more than 9 seconds.
If did not work then you may have to charge the phone? If its fully charged try to flash stock rom using Odin. When your device does not boot that means the stock firmware is corrupted and needs to be flashed again. That happened to me before and now my phone is working fine. Wanna know how to flash it? Look it up online!

Abd El-Rahman El-Batal said:
Did you try to hard reboot (power_button + volume_down ) for more than 9 seconds.
If did not work then you may have to charge the phone? If its fully charged try to flash stock rom using Odin. When your device does not boot that means the stock firmware is corrupted and needs to be flashed again. That happened to me before and now my phone is working fine. Wanna know how to flash it? Look it up online!
Click to expand...
Click to collapse
I did try a hard reboot. Same result. I already rooted and installed a custom rom on it (first thing i did).
Twrp is installed but I'm unable to boot to it.
Any more ideas?

iruiz2 said:
I did try a hard reboot. Same result. I already rooted and installed a custom rom on it (first thing i did).
Twrp is installed but I'm unable to boot to it.
Any more ideas?
Click to expand...
Click to collapse
Listen up carefully. There is a truck to boot into recovery. When you hard reboot screen will turn black then show logo. While screen is
Black quick hold vol up button and power.
Worked on my galaxy a10. Tell meh the results bro

Abd El-Rahman El-Batal said:
Listen up carefully. There is a truck to boot into recovery. When you hard reboot screen will turn black then show logo. While screen is
Black quick hold vol up button and power.
Worked on my galaxy a10. Tell meh the results bro
Click to expand...
Click to collapse
It just loads the screen attached in my first post.

Try flash via Odin, it still in download mode with this warning.

The tablet was still covered by warranty so I called the seller and they took it to a Samsung repair store. They replaced the motherboard, so I guess it was not recoverable.
The bad news is that they updated to android 11, I was quite happy with old 9.0 because I had TWRP and Magisk working.
Thank you for all that tried to help.