Hi folks,
After weeks of gruesome trial-and-error, trying all sort of guides, I am obliged to turn to you guys for wisdom in my matter.
I possess two identical Samsung S5 demo units. After a couple of days, I've decided to flash the firmware of both of these smartphones with regular S5 firmware, so I can use them as regular wifi-only smartphones, using the following guide:
http://forum.xda-developers.com/showthread.php?t=2733083
I followed the instructions, and everything went smoothly, for the first S5. But then, when I tried to do the same process on the second one, after successfully flashing in Odin, the phone entered some sort of bootloop, where a blue text appears saying "recovery boot", and nothing else happens; in which I simply cannot enter recovery mode. Due to the fact that the process succeeded previously, I have no backup.
What I would like to know is a way out of this state, either through a different firmware, or any other methods you can throw at me.
There are many threads that focus on this same issue I have run into. I am posting this now because there isn't anything that has been posted this recent. I literally spent three days trying to find a solution.
What I did to mess this up with my S4 I337m Fido phone.
1. Odin install TWRP recovery. This seemed to work fine. I think I had to flash it twice to get it to work but I could boot to recover no problem.
2. CF-Auto Root
This process worked up to the point where you are suppose to reboot the phone and open the Su App and allow it to write permissions. This failed to work. Every time I booted my phone it would lag out and tell me SU app failed to open.
3. Flashed Slim KAT anyway...bad idea but I figured I would follow proper steps and flash. Everything was fine except for WIFI...yes everything seemed to be running smooth except for WIFI. This was obviously unacceptable.
4. Flashed stock ROM for my S4 which I received from a thread and then updated with Kies to obtain fully stock. This by the way is a suggested fix from many threads but this is where the sounds stopped working!!! Yes WIFI was good but SOUND was gone!!! WTF!
5. Flashed like 4 different froms ranging from CM11 to Mokee ROM....Nothing worked.
FIX! So I downloaded my stock rom from Sammobile.
No I flashed this via ODIN and rebooted and then did an update from Kies...This did not work to resolve the ISSUE of No Sound for me! What I had to do to fix this was to do a "Firmware Upgrade and Initialization" in Kies! What this does is ask you for your MODEL# and SERIAL# under your BATTERY. This then gets the firmware specifically for your device from Samsung. This updated my phone to 4.4.2 and everything works better then when I originally got my phone.
Again their are other threads that lay most of this stuff out but the last tweak I did not read and tried out of desperation. I hope this helps at least one person. I will continue to try and root my device because I am crazy like that. I have been an XDA user for 8 years now and enjoy custom ROMS on every android device I have come across. I cracked this S4's screen a month ago and they said warranty was void so to hell with Stock **** lol
I thank the XDA community with all my heart for giving me restless nights of modding fun. I have learned a lot from all of you and appreciate your time.
Hi
I today tried to flash my S5 using this Firmware: -
http://click.xda-developers.com/api... | Samsung Galaxy S 5 | XDA Forums&txt=MegaNZ This is the firmware in the 2nd post on the "[SM-G900F] S5 Firmware Thread "
This is the Official Stock Rom for my device and was under the impression it was not country specific.
I had Lollipop installed already from when it was first released and as always used Odin (3.09 in this instance) to flash. It flashed without problem. I have just been away for 2 weeks and in the meantime, my wife flashed her S5 through Wifi after getting popups reminding her to do so. She had no difficulty upgrading from KitKat to Lollipop either.
However a massive PITA for me was that I could not mute the volume as easily as I could with KitKat and when my wife showed me she could do it, after her upgrade, I simply had to upgrade, her version being the same as the one quoted above.
So this morning I downloaded the file and proceeded to flash (again using Odin 3.09). It got all the way but at the end, just before writing, I got "Fail" - it had completely failed and I was stuck in the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." screen." I had never seen this before and thought I'd bricked my phone.
After searching in vain for a solution on this forum, I got nowhere fast. However I wondered if I could take the battery out, replace it to a blank screen and try going into "download mode" once more.
I could indeed! So I then downloaded the same file (I presumed) from Sammobile, to see if I could start over. It worked!!!! And more importantly, I too can mute my phone's volume - Happy Days !!!
But it seems (and from Googling) some of your firmware files are corrupt. Not my PC as I checked the file before using it to ensure it was binary correct.
So I am reporting this officially because I can see no other threads on this subject - maybe in a specific post but not, that I can see, in a specific thread.
I have been a member here for some years and never had an issue like this - your firmwares have been always ok until now. They are faster to download which is why I use them. The Sammobile file took 2 hours to download on their free service but it was fine, unlike the one above.
Any thoughts ?
roz
This is a new phone (galaxy s5 active SM-G870A as it says on the back sticker) i got a couple days ago that has never been dropped, been exposed to moisture, or had any physical damage. I upgraded to android 4.4.4. and decided to downgrade to 4.4.2. through the stock firmware i got from multiple sources (sammobile and a couple others to make sure). It successfully flashed, i factory reset/deleted cache, successfully booted up and the screen will not respond anymore. I Had no issues with it prior to this. I reflashed through odin (ap slot) as mentioned several times to make sure. Has anyone have similar problems or can someone point me to a forum with a solution? I suppose it's technically not soft bricked since the buttons respond and the screen works besides not responding to touch so i am somewhat lost in finding a solution.
I'm completely at a loss at this point.
I attempted to root my Samsung S7 (AT&T) with Odin, and received an error. This is my first time ever rooting a phone, and I am generally oblivious to this kind of stuff. I disconnected the phone, and it began bootloop. I loaded it into download mode, and attempted to reset to stock. However, I have had endless issues trying to flash the stock firmware to my phone. At one point I unplugged the device once again, and I received the "use Emergency Restore" error screen. I tried to restore with Smart Switch, but I was not able to access my S/N (box is nowhere to be found, managed to find a S/N on Samsung's website since I registered it but Smart Switch wouldn't take it). So, I figured trying to restore with Odin was my last option. I have tried at least 3 different Odin versions, both modified and not, and not a single one of them has worked. I've received Complete(write) errors, Model Dispatch Fail errors, and Re-Partition errors. I've tried about 3 different firmware files as well, and while I think the one I have right now is most recent, none of them seem to be working. I thought maybe an issue I was encountering was that USB debugging or whatever it's called was disabled, but I have no way of telling because I cannot boot my phone.
I was fiddling around with all of this from 11pm to 6am last night, and picked it back up as soon as I woke up. I've been freaking out about this for hours.
I feel like I'm running in circles here. I don't understand what I'm doing wrong. I'm recovery bootlooped as well. The only thing I can boot is download mode.
I wasn't very cautious with this process, and I am completely unfamiliar with most lingo on these forums and the whole process in general. I really regret trying to do this. So -- is there anything else I can try to do to fix it? Or is my phone bricked for good??? I'm endlessly frustrated and have honestly felt like crying a few times over this. I shouldn't have messed with something I know nothing about. :crying:
I thank you for your patience in dealing with me as a beginner + appreciate any help you're able to give.
Cheers.
aerialslam said:
I'm completely at a loss at this point.
I attempted to root my Samsung S7 (AT&T) with Odin, and received an error. This is my first time ever rooting a phone, and I am generally oblivious to this kind of stuff. I disconnected the phone, and it began bootloop. I loaded it into download mode, and attempted to reset to stock. However, I have had endless issues trying to flash the stock firmware to my phone. At one point I unplugged the device once again, and I received the "use Emergency Restore" error screen. I tried to restore with Smart Switch, but I was not able to access my S/N (box is nowhere to be found, managed to find a S/N on Samsung's website since I registered it but Smart Switch wouldn't take it). So, I figured trying to restore with Odin was my last option. I have tried at least 3 different Odin versions, both modified and not, and not a single one of them has worked. I've received Complete(write) errors, Model Dispatch Fail errors, and Re-Partition errors. I've tried about 3 different firmware files as well, and while I think the one I have right now is most recent, none of them seem to be working. I thought maybe an issue I was encountering was that USB debugging or whatever it's called was disabled, but I have no way of telling because I cannot boot my phone.
I was fiddling around with all of this from 11pm to 6am last night, and picked it back up as soon as I woke up. I've been freaking out about this for hours.
I feel like I'm running in circles here. I don't understand what I'm doing wrong. I'm recovery bootlooped as well. The only thing I can boot is download mode.
I wasn't very cautious with this process, and I am completely unfamiliar with most lingo on these forums and the whole process in general. I really regret trying to do this. So -- is there anything else I can try to do to fix it? Or is my phone bricked for good??? I'm endlessly frustrated and have honestly felt like crying a few times over this. I shouldn't have messed with something I know nothing about. :crying:
I thank you for your patience in dealing with me as a beginner + appreciate any help you're able to give.
Cheers.
Click to expand...
Click to collapse
If you can at least get into download mode, then simply flash it with the latest STOCK firmware for your particular model.
That will bring it back to life, and you can attempt rooting it again, if you dare
aerialslam said:
I'm completely at a loss at this point.
I attempted to root my Samsung S7 (AT&T) with Odin, and received an error. This is my first time ever rooting a phone, and I am generally oblivious to this kind of stuff. I disconnected the phone, and it began bootloop. I loaded it into download mode, and attempted to reset to stock. However, I have had endless issues trying to flash the stock firmware to my phone. At one point I unplugged the device once again, and I received the "use Emergency Restore" error screen. I tried to restore with Smart Switch, but I was not able to access my S/N (box is nowhere to be found, managed to find a S/N on Samsung's website since I registered it but Smart Switch wouldn't take it). So, I figured trying to restore with Odin was my last option. I have tried at least 3 different Odin versions, both modified and not, and not a single one of them has worked. I've received Complete(write) errors, Model Dispatch Fail errors, and Re-Partition errors. I've tried about 3 different firmware files as well, and while I think the one I have right now is most recent, none of them seem to be working. I thought maybe an issue I was encountering was that USB debugging or whatever it's called was disabled, but I have no way of telling because I cannot boot my phone.
I was fiddling around with all of this from 11pm to 6am last night, and picked it back up as soon as I woke up. I've been freaking out about this for hours.
I feel like I'm running in circles here. I don't understand what I'm doing wrong. I'm recovery bootlooped as well. The only thing I can boot is download mode.
I wasn't very cautious with this process, and I am completely unfamiliar with most lingo on these forums and the whole process in general. I really regret trying to do this. So -- is there anything else I can try to do to fix it? Or is my phone bricked for good??? I'm endlessly frustrated and have honestly felt like crying a few times over this. I shouldn't have messed with something I know nothing about. :crying:
I thank you for your patience in dealing with me as a beginner + appreciate any help you're able to give.
Cheers.
Click to expand...
Click to collapse
Did you finally recover your phone? I'm in the same problem here since yesterday and feel your frustration right now. My phone is a Samsung S7 model SM-G930A from AT&T.
I found this thread https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039 and I following the "Return to stock part", now downloading the firmware. Hope it helps.
I'm stucked in the blue screen "An error ocurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". Of course I try the Smart Switch but says that my model is not supported!
How can you recovered the download mode? I press the on/off button for some seconds and the screen turn of, but it turn on again with the freaking blue screen "An error ocurred while updating the device software. ...". I tried all the possible button combinations.
Thanks and good luck.
Stock firmware
Make sure when you go into download mode and flash that plugging the phone in is the LAST thing you do. I.e. plug phone in only after it is in download mode and only after you open Odin. Secondly, make sure you flash the STOCK firmware, as in Android Marshmallow v6.0.1 . Additonally, make sure that the re-partition option is NOT ticked, and also you might want to try turning off auto-reboot, and just hold the power button after unplugging once the status bar is all the way full and Odin says complete. Also, you need to make absolutely sure that you're getting the firmware for your exact device. I.e. SM-G930A stock firmware is NOT compatible with SM-G930F models. You could also try reinstalling the Samsung drivers. I just flashed to stock firmware then updated back to Nougat yesterday, mostly without a hitch by following these guidelines. There is a download page on rootmygalaxy with all the stock firmwares, that's what I used (I'd link but I just registered here). There is a very helpful guide on droidviews about how to update to Nougat 7.0 once you have finished flashing the stock firmware.
If I were you, I would just avoid rooting altogether. Rooting for me caused very bad performance and battery life, and it wasn't really worth the trouble. Sure, getting in-app-purchases for free was nice but I never tried flashing a custom ROM or anything because most of the stories I read involved soft bricks, bootloops, etc.
Hopefully not having USB Debugging and OEM unlock ticked doesn't brick your phone, I'm doubtful that it will. For the poster above me, make sure your phone is all the way off, the download mode button combo is vol. down+power+home all at the same time, and hold them. A screen should pop up saying press vol. up to continue. If you're still having problems, I regret to say that I am also relatively new to this and I am not all that knowledgeable.
I just made a post about my unrooting process, hopefully it helps!
https://www.youtube.com/watch?v=o6ryOQepX2Q Video shows booting into Download Mode. Or take it to a Best Buy that has a Samsung Sales section.