I had just finished flashing and configuring crash rom v19, when my phone suddenly powered off.
Now it's not the first time I flash a new rom to my note 3 by any means, but this is a first.
Now my phone won't power on if not plugged in, and even then it powers on for less than a second, long enough to see the battery charging picture or the note 3 logo.
Recovery won't boot, but download mode works flawlessly, I pulled out odin3 with the stock ROM for my sm-n9005, checked the regin was right and everything, and after flashing using odin all I got was my phone rebooting over and over again trying to access recovery, then it booted no problem to the samsung logo, played the tune and even showed me my lockscreen for a second, and it's back to rebooting itself every 3 seconds.
Anybody have any idea what I'm facing here?
Edit: First thing tomorrow morning I'm going to take it to a store to try a new battery
@E-Chan42.
You can try this out.
I am not sure will this fix your problem.
First, charge your phone for 3 hours. Second, hard reset your phone then flash Stock firmware using ODIN.
amk19 said:
@E-Chan42.
You can try this out.
I am not sure will this fix your problem.
First, charge your phone for 3 hours. Second, hard reset your phone then flash Stock firmware using ODIN.
Click to expand...
Click to collapse
I've had my phone plugged in for a short while, but since it keeps vibrating, showing an empty battery picture turning off, vibrating and so on every second I'm not sure charging will actually difference to my issue, still thanks for the input and I'll give it a try.
Ohm....
Then I guess it must be a Battery issue.
Give it a shot. Let's see if that works.
Took it in to my retailer and samsung guy restored the original ROM with Odin just as I did, when it didn't work he sent it off under garantee, thanks for your help! I'll update when I get a word back!
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....?!
Hallo,
i hope someone can help me here.
After a low battery my phone doesnt turn on any more. After some research i thought it might by the "death battery problem". So i but the phone on Laptop Charge port for 6 hours and i got it booted in to system.
But only for some seconds and it turned of again. So i decided to buy a new battery. Installed it and tried to boot. Sometimes it bootet in to System, sometime just got Blackscreen. I tried hard reset in it showed some errors. That was some days ago. Now it boots and everytime blackscreen. I tried also longer presses like 10 secs and 60secs. I tried fast press for hard reset with boot logo. I have no detection on Windows. I never rooted the phone and it has still stock rom. Must be the latest kitkat 4.4.2 i guess. I checked every cable. No charge led or logo.
Hey dude check out my video https://youtu.be/rpmbk9RFE_U there is step by step instruction how to reflash your rom... Just watch im here for any questions.
Please help! My S5 Neo was in a drawer for a few months after the LCD got smashed. I recently bought a new LCD assembly and connected it to make sure it worked before fitting and it was fine. However, the phone immediately started doing a software update but was interrupted after a few seconds as the battery was dead. Now the phone won't power up or boot into download mode or recovery. When I plug the phone in to its charger, the LED flashes red but nothing is displayed on the screen. I had a new battery for it and charged it in another device but still no joy. I've been messing around with old galaxy phones for a couple of years now, flashing custom ROM's etc, so I wanted to just re-flash a stock ROM into it but there's no way I know of performing this without getting the device into recovery or download mode. Does anyone have any ideas? The device is totally stock and hadn't even been rooted. I'm currently using an S4 Active running Lineage OS 17.1 so I'm not desperate for a phone, but I loved my S5 and really would like to get it up and running again. It never once had any problems.
It's been a few months but it would either get stuck in the "Galaxy A36" screen or during the "SAMSUNG" screen and after some time just reboot itself on its own, like again and again. A single time it actually went into the OS but crashed after about 15 seconds and never did the same thing ever again. Since then it's been really unpredictable. Sometimes it turn on, sometimes it doesn't react, no matter what kind of buttons you push. Not being able to see the battery state doesn't help either.
Got this phone from a coworker. He's not the type of person to fiddle around with the system, so he didn't try to install a different firmware or anything. I can imagine something went wrong while updating (when did it last get an update though...) or while installing some kind of app or catching a virus. Or maybe the motherboard is just fried, that would be my guess actually.
So, what did i try next? Recovery mode... it seemed to be loading something and crashed shortly after. Next up i tried getting KIES and Smart Switch to work with it, but no response. Got the USB drivers atleast and ODIN connects with it. Tried flashing it with the original firmware. For some reason it failed the first couple of times (i've been reading battery has to be atleast 50% for it to work) but a day later after charging for long time it "worked" and shown me a green PASS. However it still didn't boot up, no matter how long i waited.
Tried recovery mode again but it just shows me a passed out Android man, lol. Tried booting up and sometimes got some messages in red like "Custom binary blocked by FRP lock" and "Recovery is not seandroid enforcing" whatever that means. I know ODIN has some more options, to wipe internals but i'd rather save everything on there. Running out of ideas here. Anyone?