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
Related
Hi Guys,
I had rooted my phone using motochopper then yesterday I received OTA update. Everything seems to be fine then later I started getting Samsung Text-to-Speech engine has stopped working everytime I opened Gallery. It was very frustrating, so I did factory Reset. After Factory reset when I go to last screen to startup my phone(Learn about Key Features:Air view, Air gesture) and click Finish. I get "Unfortunately Settings has stopped" error. I found the stock firmware here hxxp://galaxys4root.com/galaxy-s4-stock-firmware/ But every time I use Odin I get PIT Partition not found.
Please help guys, I am stuck, don't know what to do now. :crying:
You can get the stock firmware from the "Development" section and also a step-by-step guide how to do it...search the development section for it. You can also find a lot of information about the issue you are having with the "stopped settings" error, again you can search for the info. I would also suggest you research ODIN to make sure you have the correct boxes checked so you don't hard brick your phone. Good luck.
i had the same exact issue and tried ODIN. didint work. i used to KIES to restore my firmware and it works again! try using KIES.
scott14719 said:
You can get the stock firmware from the "Development" section and also a step-by-step guide how to do it...search the development section for it. You can also find a lot of information about the issue you are having with the "stopped settings" error, again you can search for the info. I would also suggest you research ODIN to make sure you have the correct boxes checked so you don't hard brick your phone. Good luck.
Click to expand...
Click to collapse
I checked all appropriate settings for ODIN before upgrading the firmware. I got the same error all the time. I will research "Stopped Settings" error and let you know if I find anything. Thanks for the quick response.
kuraijay said:
i had the same exact issue and tried ODIN. didint work. i used to KIES to restore my firmware and it works again! try using KIES.
Click to expand...
Click to collapse
Hi I am choosing "Firmware upgrade and initialization" option to download the firmware. I put my phone into recovery mode as per steps mentioned and click "Start Upgrade" it takes around 40-50 minutes to download the firmware, then after sometime I get failed to connect to the phone. It's weird the "Start Upgrade" option is only enabled after I properly connect the cable and Kies have recognized the phone. Then why after some time it would say failed to recognized please try again?
zukaa12 said:
Hi I am choosing "Firmware upgrade and initialization" option to download the firmware. I put my phone into recovery mode as per steps mentioned and click "Start Upgrade" it takes around 40-50 minutes to download the firmware, then after sometime I get failed to connect to the phone. It's weird the "Start Upgrade" option is only enabled after I properly connect the cable and Kies have recognized the phone. Then why after some time it would say failed to recognized please try again?
Click to expand...
Click to collapse
weird mine never said enter recovery. what i did was plugged in my phone and i did the ""Firmware upgrade and initialization" then it gose through all the agreements and downloads the firmware. then it'll auto boot in to download mode for the install. are you using the stock usb? which port are you using on your computer? is KIES up to date? do you have the right drivers?( then again i think kies will install them but just in case) try already being in download mode.
also you can try this http://forum.xda-developers.com/showthread.php?t=2261232
I tried same at&t stock firmware but this time I used Odin 3.0.7 like Adam recommended in another post to upgrade and it worked like a charm. Before I was using Odin 1.8.5 and I was getting Missing PIT partition error all the time.
Thanks all for the quick response.
kuraijay said:
i had the same exact issue and tried ODIN. didint work. i used to KIES to restore my firmware and it works again! try using KIES.
Click to expand...
Click to collapse
I get different errors trying to flash stock ROM in Odin too. Missing PIT error mostly. Now phone is stuck at bad upgrade screen. Kies won't detect phone to use that method to restore either. Any other suggestions??
stumpmuncher said:
I get different errors trying to flash stock ROM in Odin too. Missing PIT error mostly. Now phone is stuck at bad upgrade screen. Kies won't detect phone to use that method to restore either. Any other suggestions??
Click to expand...
Click to collapse
Read the post above yours. Use the latest Odin 3.0.7.
-Sent from my Samsung Galaxy Note II using Tapatalk 2
What NOT to do with a new S4
RMXO said:
Read the post above yours. Use the latest Odin 3.0.7.
-Sent from my Samsung Galaxy Note II using Tapatalk 2
Click to expand...
Click to collapse
Did. Wouldn't have appealed for help without first making sure I followed the OP's instructions perfectly. I know the rules. I read the other posts before posting. I'm here for 2 things: To learn how to get the most potential out of my devices and to contribute from my experiences when I can. Thanks for your prompt reply though...
EDIT: solution to my stuck phone problem was solved by visit to ATT store for replacement. I can tell you what happened to my 7 day old device that brought it to the point where it would not load through Kies or Odin:
Eager to remove Samsung & ATT bloat stuff, I rooted using motochopper then used Titanium Backup to remove all ATT related apps & some of the Samsung apps. I got the unlock icon on lock screen as others have after root. I removed Superuser and replaced with SuperSU. Unlock icon went away and phone status went back to official. This is when I started noticing the Samsung text-to-speech program would frequently FC during the launch of few apps. Internet would also FC during certain operations. I read of others having success installing the stock ROM with ODIN and decided to give it a try. At first I got the no PIT error then finally after a few repeated attempts it moved past that point but then failed for some other reason during installation. I did notice a little activity on the progress bar on my device during Odin flash, but when the flash failed, that was it. My device was locked up. My PC & Kies would detect the device but could never connect or mount the device. My guess is that some of the Samsung apps I deleted were tied to the Samsung engines and the lack of their presence somehow caused FCs. Comments and questions appreciated.
Got the same Odin Mode Recovery Kies problem, No Pit fixed with ODIN 3.07 used PDA and loaded normal firmware.
Hey guys. Ive had a note 3 before in the past and have used the Root DelaVega to root successfully. This was early in the year. I sold my old note 3 for an HTC One. Well today i traded my HTC One back for a note 3 as i missed the Note 3. As soon as i came home i attempted to use the Root DelaVega method to foot (just like i did before) and immediately it failed.
I have been stuck on a screen saying "firmware update encountered an issue - select recovery in Kies" so i tried Kies 3.2 however it says my device is not compatible. Come to find out after doing research (talking to the original owner i traded my HTC One for) the Note 3 i have is on the latest version of KitKat 4.4.2 that is not compatible with the Root DelaVega method or any root method - so i screwed that up. I can successfully boot in and out of download mode. Ive tried to flash N900XXUDNA6 4.4.2 in Odin several times, it begins then fails almost immediately and the bar on the phone itself (in download mode) begins then freezes shortly after beginning. Ive also tried to flash N900XXUDNC1 JellyBean thru odin and get the same results - almost immediately fail and the blue status bar on the phone freezes when it barley begins. What else can i do??? am i totally screwed? Ive been researching and trying to fix this for 6 straight hours now! My gf is about to kill me for being online so long Is there anything i can do at this point? Am i stuck.
Do you know what Region the phone was originally? I had a similar issue and I had to get the Hong Kong (in my case) version of a stock ROM and flash that to get things working again. Not all partitions are the same - you might need a PIT file to match your original region and then flash the ROM.
What info do you get in DL mode?
Journyman16 said:
Do you know what Region the phone was originally? I had a similar issue and I had to get the Hong Kong (in my case) version of a stock ROM and flash that to get things working again. Not all partitions are the same - you might need a PIT file to match your original region and then flash the ROM.
What info do you get in DL mode?
Click to expand...
Click to collapse
Yes the phone is for AT&T so it's US. When I go into DL mode Knox counter is still 0x0. Is there a certain firmware I need then to match with the AT&T model? Or a pit?
jthornton71707 said:
Yes the phone is for AT&T so it's US. When I go into DL mode Knox counter is still 0x0. Is there a certain firmware I need then to match with the AT&T model? Or a pit?
Click to expand...
Click to collapse
Go to Sammobile and see if you can find the version you had, sounds like an older JB if kingo app didn't trip Knox. Reflash that using ODIN.
I don't know if there was a problem with American bootloader, see if there's an AT&T Note 3 forum. Might find answers there...
jthornton71707 said:
Hey guys. Ive had a note 3 before in the past and have used the Root DelaVega to root successfully. This was early in the year. I sold my old note 3 for an HTC One. Well today i traded my HTC One back for a note 3 as i missed the Note 3. As soon as i came home i attempted to use the Root DelaVega method to foot (just like i did before) and immediately it failed.
I have been stuck on a screen saying "firmware update encountered an issue - select recovery in Kies" so i tried Kies 3.2 however it says my device is not compatible. Come to find out after doing research (talking to the original owner i traded my HTC One for) the Note 3 i have is on the latest version of KitKat 4.4.2 that is not compatible with the Root DelaVega method or any root method - so i screwed that up. I can successfully boot in and out of download mode. Ive tried to flash N900XXUDNA6 4.4.2 in Odin several times, it begins then fails almost immediately and the bar on the phone itself (in download mode) begins then freezes shortly after beginning. Ive also tried to flash N900XXUDNC1 JellyBean thru odin and get the same results - almost immediately fail and the blue status bar on the phone freezes when it barley begins. What else can i do??? am i totally screwed? Ive been researching and trying to fix this for 6 straight hours now! My gf is about to kill me for being online so long Is there anything i can do at this point? Am i stuck.
Click to expand...
Click to collapse
Hi mate,
if you are stuck, maybe you can try this.
http://forum.xda-developers.com/show....php?t=2701062
it's a way to unbrick your software.
and if the older owner of your N3 said it's on the latest firmware of kitkat.
maybe your problem is the firmware in the sammobile were before the firmware you have install on your device via OTA update.
Yours firmware came throw out via OTA update and with some reason you can't see any latest firmware USA N900A in sammobile.
try the method in the link and reply if you have been successful.
cumps
Ik Knox is 0×0,then u can try samsung service centre ?
Sent from my SM-N900 using XDA Premium 4 mobile app
I know this isnt the right place for this thread, but i lost my other login credentials and had to start fresh, so Im posting here....
Device: SM-T230NU
Problem: I used a website outside of XDA to root my device. I followed the instructions precisely too, I than unplugged the device hoping that replugging and restarting odin would fix the problem i have/had as displayed by the picture. I than tried rebooting the device, and got this error message: Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. Well I downloaded Kies 3, and much to my surpise I got an error message about the samsung galaxy tab 4 7.0 not being supported by Kies 3. I am now downloading Kies 2.6, so I can atleast get this device booting normally.
If you knew this was not the place to post, why did you post a question here? A play by play of your device root is not of much interest to anyone! I hope you got it fixed up anyway!
It's been fixed. I found an alternate DL site that had Odin in the package..I used ODIN to run cf_auto_root which created that firmware upgrade issue...I had to Odin firmware from the links I found on these forums...it's rooted now though
Hello everyone,
2 weeks ago I rooted my Galaxy Note 4 sm-n910f using root online with KINGO.After the root, I used the phone normally and nothing went wrong.After my battery was low, I I switched off the phone to charge the battery. Once the battery was 100%, I turned it on, and the problem started, it was a bootloop. I tried to do all kinds of reset in recovery, but nothing worked.My ROM was 5.1.1 and here in sammobile I downloded 6.0. 1 to flash with odin. After unzip I got errors saying that the file was corrupted but I ignored the errors and kept the file broken with WINRAR.after put the phone in download mode and flash with Odin when it reached in aboot .mbn he stopped for over 1 hour, i removed the phone and i was still having the errors. So, I tried to download other firmware from here and from other site, but I do not know why all the files for my phone model are corrected pted, and all gave the same error.With a version more recent odin, he stops at Nand write start for hours.I tried to download a file that did not give an error, but still the same problem.Thus, I tried to download 4 files to hide according to other site tutorials, but it is still stuck in aboot.mbn.After using the samsung tool (Z3X), and when blinks with this tool, everything starts okay, and then I get the boot.img error time So, in fact when I turn on my phone, I get the following message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again ".I tried with KIES and Smart Switch, but the phone is not even recognized, but my KIES is I have the latest version and I have the model drivers installed. So, my phone is dead or there is a way to fix this problem.
jochri3 said:
Hello everyone, 2 weeks ago I rooted my Galaxy Note 4 sm-n910f using root online with KINGO.After the root, I used the phone normally and nothing went wrong.After my battery was low, I I switched off the phone to charge the battery...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2866810
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hi All,
So, I have spent 2 days trying to get my Galaxy s8+ back to normal. However, I seem to only have made it worse. It all happened when I decided to change the /data partition from ext4 to another format and then back again to get the /data partition to mount in TWRP after flashing Pascal Rom. However when I rebooted, nothing worked, no boot up screen, no recovery, no life, but all I could get was download mode. It then must of froze up after another restart and I couldn't get anything for 12 hours or so.
The next step I tried once i got download mode again was to flash stock firmware for the G955F, I can't remember the version of this firmware, but I still had nothing change. So then i flashed the latest firmware from SamFirm's downloading client, which was G955FXXU2CRF7 - Australian Optus Branded Firmware (OPS). I was able to get as far as the "hello start screen" and then my phone restarted, it then tried to upgrade my system again, then started "erasing" and then it rebooted and I still had the same issue, nothing but download mode and still no recovery, it still wouldn't turn on. So I flashed the latest International/Unbranded Australian firmware (XSA) - G955FXXU3CRGH, still the same result. I now can't go back to the OPS version of firmware because I get the Check error with the bootloader (since it's a more recent version), so I can't go backwards. I also can only flash "Official Binaries" now. Oh and to make things worse, I read that Odin Option "Nand Erase" just erased user data, so I thought I might as well try it, and as a result, I now can't flash even the (XSA) firmware because of ODIN failing and I now have an "An Error has Occurred while updating the device software. Use the emergency recovery function in the smart switch PC Software.". I am a bloody idiot :good: . Oh, I have tried multiple versions of Both Samsung Kies & Smart Switch (Which both had the option for "recovery & initialisation"), however, I get a message that my device is unsupported after adding in my device model and S/N. I tried a PIT file and then found out it's now included in all the latest firmware img files.. so yeah lol. Fun times. Soooo I feel like I am out of Options, nothing I do is working. The worst of all this is my wife is not happy haha which means after years of tinkering with android phones (flashing custom ROMS, Kernels, Root Solutions, e.c.t ), this may be the end of the road for me if I can't fix this phone. I really hope this thread isn't true too : https://forum.xda-developers.com/galaxy-s8+/help/sm-g955fd-access-download-mode-t3748228
So Please, someone help me out if it is at all fixable even if it requires opening the phone up lol.
The stats i have on download mode are the following:
RMM State as Prenormal
OEM Lock: OFF
FRP Lock: OFF
CARRIER_ID: OPS (which is super weird because it only accepts XSA to be flashed :S )
Secure download: Enabled
System Status: Custom
Warranty Void: 1
Current Binary: Samsun Official
If you need more, just let me know.
Ok, quick update: I have got rid of the error that I mentioned. I managed to flash XSA firmware again, it went to the blue Andriod is updating the system screen, then started "erasing" then rebooted and nothing again, still only download mode available. Nothing happens when I try to turn it on or try recovery mode.
This firmware you mentioned XSA - G955FXXU3CRGH i would double check. As far as I know Australia doesn't have a version 3 bootloader yet whether unbranded.telstra or Optus.
Quick Update: Maybe Fixed now!
Even though no one has replied yet, as it's only been an hour or so. I just wanted to let anyone else know who is experiencing a similar issue in the future on how to possibly fix it.
This was a real nightmare, however quick disclaimer, I am not responsible for any damage incurred to your device/property by following my instructions.
So the way I have fixed it, is I flashed the AP file only (from the firmware zip i had downloaded from SamFirm) with "Auto Reboot" Off. When ODIN finished, I held the Vol Down + power button, to reset it. It gave me a blue "No Command" Screen, I then waited and it then went black and the recovery screen appeared. I cleared the cache, rebooted to bootloader, which it didn't turn back on, so I left it because I thought it was the same thing. Came back 10 mins later and turned it on (or hard restarted, can't remember) and it worked. It booted!
I did soon learn it looks like it was having a charging problem because it had no charge and kept telling me there was water in the port (even though it was dry), I restarted it again after putting it on a wireless charging pad and it is seeming fine so far with the USB charger. So big note to anyone in the future, that it could be possibly bugging out with charging as well if you can't get it back on. I did have the device tell me here and there the last two days that there was water in the port when it was off. So kinda weird.
I know this all sounds a little hocus pocus, superstitious almost, but hey, my phone is working, so maybe replicating my actions may just help lol. :cyclops:
spawnlives said:
This firmware you mentioned XSA - G955FXXU3CRGH i would double check. As far as I know Australia doesn't have a version 3 bootloader yet whether unbranded.telstra or Optus.
Click to expand...
Click to collapse
Oh right, well, I did hear that SamFirm is not supported anymore, as that's where that firmware came from. Maybe it's dishing out incorrect firmware now? Possible the structure of where ever it is getting its firmware from (pretty sure it's pulled from samsung) has possibly been altered?
Just for reference I use www.updato.com for downloading firmware it is usually up to date. No reference to the firmware you mentioned (not for Australia anyway)
The screenshot I took: Imgur link:
https://imgur.com/a/lqyzWW7
Interesting I'll keep a lookout for it. Still on nougat 7.0 (XSA) no plans to upgrade yet until some issues are fully resolved ( out of beta stage that is ).
spawnlives said:
Interesting I'll keep a lookout for it. Still on nougat 7.0 (XSA) no plans to upgrade yet until some issues are fully resolved ( out of beta stage that is ).
Click to expand...
Click to collapse
Yeah, it's seeming to work now, but my fast charge isn't working. However, my other oreo ROM didn't work with fast charge either. So i am unsure if it is my phone or an orio bug :/ lol
Well at least you got it working and not using as a door stop
that was really sad story man.....
spawnlives said:
Well at least you got it working and not using as a door stop
Click to expand...
Click to collapse
Yeah haha, so glad it's not a door stop haha