I was actually going to flash a stock lollipop rom from Saudi Arabia this morning but little did I know, I didn't know what are the procedures to manually flash it on odin. So I followed sammobile.com's instructions. I went to download mode in my phone and then I start it. And it showed an error in odin but I have not copied it to be able to distinguish what's really the problem. Being a noob, I unplugged my phone and tried to repeat the procedures but now it won't boot, can't even go to download/recovery mode, vibrates with an interval of 2 seconds and the screen stays black.
1. Am I able to fix this?
2. If yes, can somebody help me.
Edit: My phone was actually rooted 4.4 kitkat
Boot it normally, It'll say something like this "Firmware upgrade failed. Connect to Kies to restore firmware". Leave it like this and connect it to your computer and Open Odin it should say Added! in the white info box. now you can start flashing again the firmware.
Related
I just got this phone alittle over a month ago. Today at work, my phone randomly shut down and started continuously restarting. The phone will vibrate and boot the logo, then turn into a black screen, vibrate again, and restart. I had not modified my device at all. Just downloaded your typical apps like anyone else. I already tried taking out the battery and letting it sit and booting in recovery mode and wiping the cache and restoring to factory settings. I also tried to use odin to flash what i think is my firmware onto the device. I wasn't able to figure out the firmware of the device before I did it so i sort of guessed based on the model. Though all i did for this is download what i thought was the firmware, put it in odin3.4, entered download mode and plugged my device in and let it download. I didnt do any rooting or enable debugging/disable debugging before i used odin. Did I miss a step? Does anyone have any suggestions of something I else do. I am so confused on how this happened to my phone!
Hi guys first i want you to know that my english is bad...
My phone is G900K - SpaceX Rom 5.0
I am using SpaceX Rom 5.0 for weeks and it is buggy, i experience random boot,app crash,fast battery drain and freezes.
Yesterday i reboot my phone and after "Android is Starting" i got message that System Crash or System UI i am not sure what it is but it has System word in error report. Then my phone didn't start so i remove the battery and put it again. After pressing on the Power on Button my S5 starts and i notice the Blue Light in Upper Left didn't Light Up and my phone didn't boot to 2nd Samsung Logo. When i press Power On Button my S5 will turn on and 1st Samsung Logo will appear then It will Turn Off then Vibrates then goes back to 1st Samsung Logo it keeps repeating. Also i try Recovery Mode but i can't enter to it my phone will repeat the same process as i Turn On my phone. I can go to Download Mode, And i flash Stock Rom and after flashing Stock Rom there's a blue text in upper left Recovery Booting... but its not booting into recovery, It will just turn off again then vibrates then goes to 1st Samsung Logo.
If anyone experiencing the situation right now you can comment​
Same issue here. My phone is stuck at RECOVERY BOOTING. Is there anyone who can fix this issue? Thanks.
Boot to download mode (Vol down & Home & Power)
Flash stock ROM from sammobile .com with ODIN
Instructions under the download on their site
Go into download mode and do a firmware upgrade and initialisation through kies3. You will need your serial number and model number( on the white sticker behind the battery. in kies3 go tools> firmware upgrade and initialisation, then follow the on screen steps. I used this when I soft bricked my note 2 when I had it, I personally find it's the best way to restore a samsung device.
You should try first with kies3, it did help me to recover from custom ROM installation.
If it fails, flash stock with Odin3 from phone download mode is your last option.
I'm having the exact same issue! Been trying to flash the stockfirmware, but still stuck in recovery booting loop! Even trying to get into recovery mode has it looping. Kiess 3 says that my serial number is invalid, so matter which number I put in too. Hoping for some help!
*Detection* said:
Boot to download mode (Vol down & Home & Power)
Flash stock ROM from sammobile .com with ODIN
Instructions under the download on their site
Click to expand...
Click to collapse
This Doesn't Work !! Odin Shows PASS message. But the phone dosn't boot. Gonna try usng Kies
boomie0123 said:
I'm having the exact same issue! Been trying to flash the stockfirmware, but still stuck in recovery booting loop! Even trying to get into recovery mode has it looping. Kiess 3 says that my serial number is invalid, so matter which number I put in too. Hoping for some help!
Click to expand...
Click to collapse
Mine is the SM-G900W8 with Telus, so if we have the same model, I could probably give you my serial number cause I never had issues with mine. I know I have read places that sometime when people get stuck in recovery like that, they do a factory wipe and cache wipe in the stock recovery to get it to boot.
This same thing is happening with my s5 Verizon.. Need help to fix this i've tried flashing via odin, factory reseting..nothing worked
Can anybody help me please....thanks
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....?!
Hi,
My galaxy S4 decided to poop itself yesterday. I was browsing my emails and the phone restarted by itself. . but then it kept restarting over and over again (Boot loop). The phone felt hot, so i took the battery out and left the phone for a while.
Once i put the battery back in, the phone kept boot looping. I managed to get it into safe mode and make sure all my photos were safe – I've just returned from a holiday in Hawaii, so this was very important to me.
After i was able to make sure photos were backed up on the computer, i cleared the cache partition and even did a hard reset. The phone kept boot looping. My phone now gets stuck on the "Samsung Galaxy S4 GT I9505" start up page. I read about issues with the power button, so even atempted to open the phone up and wiggle the power button around a bit by squeezing it with some tweezers. This made no difference. I've even swapped batteries and tried charging it.. this also doesn't work. Currently my phone has the "Samsung Galaxy S4 GT-I9505".
I have been on whirlpool forums and it was suggested that i reinstall the firmware through odin.. i did, but with great difficulty and many attempts. My phone was able to boot up and i was able to send one message and make one phone call before it went into bootloop again or just switches off and doesn't want to be switched back on again. When the phone was on, no sound was apparent when a phone call/text message came through for testing. I've retried dowloading the software on odin, but when i try to switch my phone on it says "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again".
I've also tried putting the phone on the charger and no sound or green battery coloured animation comes up on the screen now.
Please somebody help
It was the latest stock firmware from sammobile.com that was flashed to the phone? Was the phone factory reset from stock recovery before booting the phone after fllashing with Odin?
As far as I know it was the latest unbranded firmware from sammobile.com.
A factory reset was one of the first things I did after starting the phone up in safe mode and trying to recover files.
The phone has never previously been tampered with. I've only ever upgraded the software through WiFi or Samsung kies. Using Odin was a learning experience for me.
Maybe the factory reset needs to be done from the recovery screen rather than from the ROM settings?
The factory reset was originally performed from the recovery screen. I can no longer get into recovery mode though. It only seems the phone wants to get into download mode
Have you tried flashing a ROM designed for a particular carrier in your country?
This is going to sound silly.. But I thought that's what I was doing when I went through Odin and got the firmware from sammobile.com
Which version of Odin and firmware was flashed?
What errors occurred during the flash process according to the Odin log?
Tried flashing with a pit file?
Hello community,
A good friend of mine asked me to support him with his "bricked" Note 4.
I tried now for a few hours (usually im experienced with stuff like that) without any success.
Downloadmode is accessable. Odin (3.09) says most of time 'pass'.
I flashed the following stock roms:
N910FXXU1DRI2_N910FOXA1DRI1_DBT_(Germany) [We are from germany] 1 File.
Odin tells me: pass, Phone reboots in recovery mode, installs a system update, processbar filled half, "earasing", reboot into recovery and display stuck on black after retry to install a system update.
I already tried to debrick - after reflash the PIT file, the Note4 stuck in the Note4 Splashscreen with a blue LED blinking but nothing more happens. [Debrick XDA Thread] (should it?)
I tried also the N910FXXU1ANK4_DBT_4Files Firmware but same behavior (black screen after system update - the phone must turned on since the power button doesnt react - I need to pull of the battery for reboot).
Any hint for me what Im doing wrong? This devices drives me crazy ...
Is the device hardware broken maybe? What do you guys think?
Thank you for reading
Best regards
/nepixl
Have you tried to install a custom recovery instead first?