Can anyone PLEASE help??
My partner opted to do a suggested update on her S5, but didn't notice the wifi was off. The phone seemed to have done the update, but shortly after it rebooted itself, then again, then again. The frequency of reboot got quicker and quicker and now it loops between the Galaxy S5 splash screen and the SAMSUNG logo, but doesn't go any further.
I managed to boot the phone into reset mode, cleared the cache and then did a factory reset, but that did nothing to prevent the boot loop.
I then downloaded Odin (ver 10.3.7) and what I believed to be the correct firmware (G900FXXS1CPLV_G900FVFR1CPJ1_G900FXXU1CPIW_HOME.tar.md5).
Having checked the battery was charged, I followed the instructions of connecting the phone via USB, loading the md5 in the AP, checking Auto Reboot and F-Set time in the options and clicking the Odin Start button. I had removed the battery, replaced it and then booted it into the update mode (Power, Home, Volume Down, then volume up) with the screen confirming I was in the right place (....do not unplug.... etc).
The file loaded, (green bar at top of the Odin window on my PC) and Odin reported success. I then disconnected the phone, booted in recovery mode, reset the cache and then did a clear data, factory reset.
The same symptoms prevail, STUCK IN BOOT LOOP!!!!
The only thing different is that if I plug it into the USB on my PC, after a while the phone tries to turn itself on and goes into either a boot loop or freezes on the Galaxy S5 Splash screen or the SAMSUNG Logo.
I am charging another battery (just in case that is in some way to blame) and will try again to replace the firmware, but could I be missing something, do I need to do anything with PIT (I thought this was all taken care of by Odin using the MD5 file) or is there some other test I can perform that will show if the phone is fried???
MANY THANKS for looking!
ur going correct, try to reflash it again through odin and dont disconnect phone until it boots into system, it is taking some good time, so just wait and dont do anything this time like clearing anything or restoring. i hope ull get success.
THANKS - but...
Thanks Rayzen, I will try the whole thing again, but I think there is something more to this than a firmware fault!
There and gone again
OK, so on the 4th attempt I got the phone to take the firmware using Odin, it reported success and the phone rebooted itself (several times) and eventually appeared to boot to a new factory reset.
I put in a SIM card and entered my email and google account details and left it charging over night. This morning when I tried to use it, the screen froze and then it rebooted itself. Hey presto, the phone is back to square one with a boot loop.
ANYONE (please) got any suggestions?
THANKS
No one??
same here, same symptoms, same feeling.
when flash gone right... i feel lucky.. but for half hour only, rebooted and angain in boot loop.
I cannot even boot in recovery. flashed TWRP. from 5 boots in recovery only 1 success.
When trying to wipe phone in TWRP - it hangs.
still trying to install some other (custom) rom. still no success.
hope never dies
same things happened here! now cant get samsung galaxy s5 to boot...............
Are you sure your using right firmware? as it took me a few versions before it booted last time this happened?
Could any please confirm what is the right firmware for samsung galaxy s5 900F
It took another 6 or 7 attempts, left it over night and was about to trash it when it booted.
I then received a 'software update available' message and tried installing it. First attempt put the phone back into boot loop so I reflashed it again using Odin.
That worked immediately the over the network software update installed and now phone is 100%
Very frustrating but I got there!
glad you fixed it! ive tried three different firmwares and still nothing.
trying this one atm
G900FXXU1ANE2_G900FEVR1AND1_G900FXXU1ANE2_HOME.tar
oh and how long do they take to boot when there are sitting at the samsung glowing screen?>
I'm in UK and used what (I had to guess) was the best firmware.
I'll let you know which version it was when I get home tonight.
BUT I had all the problems with a single version and it eventually came good.
I read somewhere that overwriting a different core (from specific providers) with generic firmware, could lead to a world of pain until it gets full replaced... not sure if that's a good description (or has any fact to it) but it seemed to be re-loading and re-loading and re........ for ages, finally cracked it.
well mines booted now!but getting constant errors about samsung push!
If it'still booted, you'very made progress!
Push issues are mentioned elsewhere and can (eventually be sorted) but if you have a booted phone you should be able to get an over the air software update installed from the service provider....?!
Hey guys,
Looking for some advice, I will try and it explain whats happening clearly.
So, last friday while I was using phone it shut down attempted to restart vibrated twice attempted restart again. So in my attempt to repair I booted into recovery mode wiped cache and booted into safe mode this took 2 attempts before finally booting into safe mode. I then reset phone back to factory settings, while it was installing apps from backup, the phone crashed. Eventually I got it all working again with apps that I used on day to day basis minus the appsvthat rarely got used.
Fast forward 6 days back to square one with the restarting. Been working perfectly since I fixed it last week. So what do you guys reckon the issue is?
Thanks
Ps the phone has never been rooted
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, one week ago I received the Axon 7 mini from Gearbest, since then I haven't used it that much, but yesterday while watching a youtube video it turned off suddenly and when I tried to turn it on it just gotted stuck in the zte logo. After several tries, and trying of wiping the data and doing the factory reset (what gave error messages such as "can't mount"...), I decided to update it to from the sd card using firmware of the russian zte. After that the phone could pass the zte logo and start the configuration screen slowly, but started to rebooting, it took me several trys till I could finish the set up, but the problem was still, then I tried to do the factory reset as well as data wipe now succesfully, but the rebooting and slowness still there, so I can't do anything because I can't finish the setup correctly, and even the only way to turn off the phone without the boot loop is inside the menu of android recovery. I hope you can help me, thanks.
I flashed the ROM Ressurection Remix onto my phone to get a newer Android version since the model is quite old. Everything worked perfectly for over two years. Then while browsing, my phone crashed and got into a bootloop and restarts after showing the Samsung Logo. After manually removing the battery and putting it back repeatedly it boots up somehow. I couldn't reproduce what was happening back then.
After that it crashes in irregular intervals for no apparent reason and every time I could get it to boot properly by turning off and on for a long period of time.
Now I got the same problem and I wanted to get rid of the bootloop, so I decided to flash it with a new version of Ressurection Remix. I updated TWRP via Odin and had much trouble to get into recovery mode since my phone was crashing at the Samsung logo. As I got into recovery I made a factory reset and flashed the new rom. But as soon as my phone started to reboot after the flashing, it crashes again and the loop starts once again. Again, I searched for another Rom and used LineageOS but the problem persists.
Now I'm out of options, I can't even get into recovery mode by now.
Could anybody help me out?
Kolon22 said:
I flashed the ROM Ressurection Remix onto my phone to get a newer Android version since the model is quite old. Everything worked perfectly for over two years. Then while browsing, my phone crashed and got into a bootloop and restarts after showing the Samsung Logo. After manually removing the battery and putting it back repeatedly it boots up somehow. I couldn't reproduce what was happening back then.
After that it crashes in irregular intervals for no apparent reason and every time I could get it to boot properly by turning off and on for a long period of time.
Now I got the same problem and I wanted to get rid of the bootloop, so I decided to flash it with a new version of Ressurection Remix. I updated TWRP via Odin and had much trouble to get into recovery mode since my phone was crashing at the Samsung logo. As I got into recovery I made a factory reset and flashed the new rom. But as soon as my phone started to reboot after the flashing, it crashes again and the loop starts once again. Again, I searched for another Rom and used LineageOS but the problem persists.
Now I'm out of options, I can't even get into recovery mode by now.
Could anybody help me out?
Click to expand...
Click to collapse
Hey. I have same problem. I can just boot the Phone with bootloader. Anyone have an idea about this?