Well, I broke my phone.
My earpiece boost stopped working and I could barely hear on the phone, the new Facebook app was crashing Facebook constantly and I was getting random reboots yesterday so I figured I would go for something new.
Because this was my first rom on my S4, I figured I should go back to stock first, bad idea. I loaded Odin up, went to flash the stock firmware to install the newest version of Sacs rom, and it failed right at NAND write start!!
I even went online and downloaded a newer firmware (February) and that failed also. I can't do the emergency fix in Kies and I can't use the other option in Kies because it says my serial is incorrect
I don't know what to do at this point, but I desperately need my phone ASAP in case my boss calls me.
Any help appreciated.
April
Well you REALLY don't give much info.
What version of Android were you on when you got your phone?
Do you have the T version of the phone or just the standard.
What ROM are you talking about 'bening your first'?
How did you install it?
What file did you try and Odin?
It is recommended you read, read some more, search and then read some more to keep just such things from happening.
Just a wild guess but you tried to Odin a .tar to a version 'previous' to the version you started with.
OR you tried to Odin a .tar for the wrong model - tried a non T .tar on a T model or vice-versa
Search for the FULL NAE .tar if you are on the 'standard' model and Odin that one.
Or, if on the T variant, hit up those threads, find the lates .tar and Odin that.
@aprilx
So great to see you posting back after asking for help.
So cool when people contribute to what worked and didn't so that others can be helped and help to contribute to the community at large.....
Oh, wait you didn't.
Guess all is good.
smmmeeesh.
Sorry, I worked 16 hours yesterday, so checking the forums was the last thing on my mind considering I got up at 5am and got home at 9:30pm.
I figured out what it was, after trying a million different things. I found a MJA stock firmware and I was able to flash that, and now I finally have Kitkat on my device.
Related
Hello all!
My wife just bought the Galaxy S in Mexico city, It came loaded with a lot of the carrier crap, and with some blocked apps.
I unbranded the phone through Odin and loaded the JM8 firmware, for leave it ready to some froyo ROM.
I am new using the Odin tool, and its way of flashing (I came from wizard-kaiser-X10), but i believe i get it working quite well.
Now, I need some advice, when I was trying to flash JPM the Odin application keeps running trying to install the modem .bin, and just hangs in there.
I got a couple of Phone-!-PC screens, but I was able to get in to download mode, but every time I tried to flash JPM or JP6 I get stuck in there.
I just read the whole Readme pin topic, but I cant get any answer to this prolem, so if anyone can point me to right direction its going to be very much appreciated.
I believe I have to gain root access in the actual firmware installed and then flash JPM, is this right?
PD I was very scared at the first Phone-!-PC screen, but the can easily get in to downlad mode after leaving the battery out for a couple of minutes. XD
I tried to install CWM earlier today and its gone wrong and now i get the dreaded error message
Firmware upgrade encountered an issue etc
Kies wont recover it either.
Now im hoping i can get it going again quickly
Just from skimming through here while trying to pack i gather i need to use odin to reflash the stock firmware.
I wouldnt normally ask but could some nice person spoon feed me given the circumstances of time constraints
Gavin01 said:
I tried to install CWM earlier today and its gone wrong and now i get the dreaded error message
Firmware upgrade encountered an issue etc
Kies wont recover it either.
Now im hoping i can get it going again quickly
Just from skimming through here while trying to pack i gather i need to use odin to reflash the stock firmware.
I wouldnt normally ask but could some nice person spoon feed me given the circumstances of time constraints
Click to expand...
Click to collapse
All you need to do is search google. No one spoon feeds you in real life so no one shouldn't spoon feed you here also.
http://forum.xda-developers.com/showthread.php?t=2261573
You need to follow these instructions but you need to download your correct firmware.
Sent from my SAMSUNG-SGH-I337
Use Odin to flash stock firmware by following this guide, I assume that you have the i9505, if so then flash this CWM,
thanks i need to find the right rom now
thanks fingers crossed
EDIT
im guessing this is the right rom
I9505XXUBMEA_I9505OXXBMF1_XEF.zip
thanks guys weve done it!
its resurrected!
cheers
I stuffed my phone up again and thought id post here instead of making a new thread.
flashed the latest modem which in turn has for some reason fubored all my dialling out and messages etc so i cant use the phone for anything other than browsing .....
I9505XXUBMEA_I9505OXXBMF1_XEF.zip<<<<<<<<<<<<this is what i used last time and it didnt work this time
so ive now tryed this one I9505XXUFNB8_I9505BTUFNB3_I9505XXUFNB8_HOME.tar.md5
my phone is a sim free s4.
the second one appears to work but wont get passed the lock screen with out continuous errors. (i note i now have the knox label in the bootloader)
How do i find the latest stock rom for my phone? so i can start again?
thanks
I had exact same issue so i falshed XXUFNB9 from sammobile and now im rooted runnin cm11 m9 .
Do suggest UNISTALLING samsung usb drives from pc and reinstalling fresh new ones for your device snd then flashing. I flashed 4 different firmwares. It was only until i reinstalled s4 usb drives my phone becsme alive. Dunno how but i reckon usb drives is the issue
Hello. I have been searching for hours like a mad man on Google for a solution to my problem, but i'm having no luck. Excuse the nooby nature of this post please. So I rooted my Galaxy S4 and I am trying to get it back to stock by flashing the AT&T md5 onto my phone (Galaxy S4 SGH-I337) through ODIN and it fails every single time. Initially, with ODIN 3.07, it would return something like fail (auth). Then I tried with ODIN 1.85, but that version returns "Complete(Write) operation failed." In addition, I attempted Kies but it too failed (no specific error code), and now the phone wont boot. It says that the firmware upgrade encountered an issue. I am not able to access stock recovery or TWRP because it will automatically go to Download Mode with "Could not do normal boot" in the top left corner if I in any way attempt to access it. I am using the stock cable with USB Debugging enabled. I also tried two different computers, two different cables (one being stock of course), and tried every single usb port on both computers. What went wrong? I will give you my upmost respect if you can solve this. I also am absolutely willing to supply any information you may need. Just ask. (Please don't be bricked. Please don't be bricked)
-With kind regards, Branden.
Let me guess you had the att mf3 firmware and tried retoring by flashing the MDL firmware via odin? You said md5 so I assume mdl? You might at this point still be able to fix it visiting a best buy near you if it has a samsung center. Also att store can reflash mf3.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click Here throw this thread in the MF3 pile... guys we got another noob here, take a trip to your closest best buy and hope the samsung experience will flash the mf3 update for u
You mention md5, which as febby assumed I'll assume to be mdl, and twrp. Do you have mdl firmware on your phone and did you have twrp installed. Assuming you had twrp you were probably on mdl firmware. If so, I would re-download the firmware and try again. It would help if you could explain where Odin is failing too.
jd1639 said:
You mention md5, which as febby assumed I'll assume to be mdl, and twrp. Do you have mdl firmware on your phone and did you have twrp installed. Assuming you had twrp you were probably on mdl firmware. If so, I would re-download the firmware and try again. It would help if you could explain where Odin is failing too.
Click to expand...
Click to collapse
I never actually got TWRP working. I flashed it through Goo Manger and I was never able access it (It went to download mode with "Could not do normal boot" in the corner). Does this change the type of firmware I was on? In both cases of ODIN, the newer version (3.07) fails immediately after you start the process at around NAND Write start. It returns Fail (auth). In the older version (1.8.5), it reports that the write operation failed. I attached screenshots of both cases.
If you never got twrp to work then I'm almost positive you have mf3 firmware. You're best bet is best buy and have them re-flash the firmware.
Astrophysicist789 said:
I never actually got TWRP working. I flashed it through Goo Manger and I was never able access it (It went to download mode with "Could not do normal boot" in the corner). Does this change the type of firmware I was on? In both cases of ODIN, the newer version (3.07) fails immediately after you start the process at around NAND Write start. It returns Fail (auth). In the older version (1.8.5), it reports that the write operation failed. I attached screenshots of both cases.
Click to expand...
Click to collapse
There is no way to fix your problem currently so like jd1639 said, take it to best buy to the Samsung Experience area and tell them Samsung Kies firmware update fail and it did this to your phone. Thats what I did yesterday, they flashed it and I have my phone working again.
gandes said:
There is no way to fix your problem currently so like jd1639 said, take it to best buy to the Samsung Experience area and tell them Samsung Kies firmware update fail and it did this to your phone. Thats what I did yesterday, they flashed it and I have my phone working again.
Click to expand...
Click to collapse
Okay. I thank everybody for their assistance. You are very helpful people. I will head down to best buy and see what they can do for me.
Astrophysicist789 said:
Okay. I thank everybody for their assistance. You are very helpful people. I will head down to best buy and see what they can do for me.
Click to expand...
Click to collapse
Your welcome
And just so everyone knows...md5 is part of the package name I believe... (.tar.md5) or could be referring to md5 checksum...anyways as was mentioned and you acknowledged, best buy is your best bet
Sent from my SGH-I337 using Tapatalk 4
Hey guys I used oden to flash back to stock amdl and then a att update keep trying ro come threw durring the night I noticed.it downloadwd went into recovery and was on flash update I hit no instead and rebooted now I noticed my baseband changed to amdb . update is back again and I now hit remind me later is this the update witch will lockbootloader
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
ralphie1267 said:
Hey guys I used oden to flash back to stock amdl and then a att update keep trying ro come threw durring the night I noticed.it downloadwd went into recovery and was on flash update I hit no instead and rebooted now I noticed my baseband changed to amdb . update is back again and I now hit remind me later is this the update witch will lockbootloader
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Yeah it is the dreaded one! Root your device and flash a custom ROM or use titanium backup to freeze the update apps.
Sent from my SGH-I337 using Tapatalk 2
Hi all,
I am really hoping someone can help me. I have a Sprint Samsung Galaxy S4 (Non T version) that appears to be soft bricked. My phone was hanging on the yellow Sprint screen so after other procedures, I decided to try and ODIN a stock version. What I had before all this happened was MK2 (knox) stock with only CF Auto Root. I downloaded the MK2 stock ROM from XDA and tried to ODIN. It failed. It got through the majority of the process and then at the very end it said FAILED. Now if I try and boot the phone, it automatically goes into the firmware error screen. So I still have the ability to ODIN but it always fails. I have also downloaded the NAE stock ROM from XDA and tried that too. I have tried using Odin 3.07, 3.09, and even 1.85. All fail. On the screen I sometimes get these messages as the ODIN process fails. Either a start [2xx, 1440] and next line BAR [2xx, 1440], or I get a start and then a sw rev check fail fused 5 binary 4. These are all in red letters just underneath the download mode details. I really don't know what to do. Please help me recover my phone. Any help is greatly appreciated. Thanks so much!
IF your phnone was on an NAE firmware you will probably have problems going back to MK2.
Search for the NAE firmware .tar and try that.
@SuperG03
So great to see you posting back after asking for help.
So cool when people contribute to what worked and didn't so that others can be helped and help to contribute to the community at large.....
Oh, wait you didn't.
Guess all is good.
smmmeeesh.
leaderbuilder said:
IF your phnone was on an NAE firmware you will probably have problems going back to MK2.
Search for the NAE firmware .tar and try that.
Click to expand...
Click to collapse
As I mentioned in my OP, I tried the NAE firmware with multiple attempts on various editions of Odin. All without success.
leaderbuilder said:
@SuperG03
So great to see you posting back after asking for help.
So cool when people contribute to what worked and didn't so that others can be helped and help to contribute to the community at large.....
Oh, wait you didn't.
Guess all is good.
smmmeeesh.
Click to expand...
Click to collapse
I'm sorry, it's been like a day and a half and I've been trying like crazy to figure out how to fix this thing... Not sure how fast you expect me to reply, but I do appreciate any and all help.
SuperG03
Just really wondering if you attempted the suggestions. And or what you've done to get it to work.
It gets old trying to assist people, especially when they make it sound so urgent, and then never hearing back.
Hope you get it working.
Good luck!
leaderbuilder said:
Just really wondering if you attempted the suggestions. And or what you've done to get it to work.
It gets old trying to assist people, especially when they make it sound so urgent, and then never hearing back.
Hope you get it working.
Good luck!
Click to expand...
Click to collapse
I definitely understand trying to help and not ever hearing back would get annoying... However, for the first like half a day I checked back at this thread every hour or 2 and it had a lot of views but not any replies. Even as of now, there hasn't been a reply with a suggestion of what to do that I haven't already stated I did try in my OP (you suggested NAE and I had been trying that already). I do appreciate you at least trying though.
SuperG03
SuperG03 said:
Hi all,
I am really hoping someone can help me. I have a Sprint Samsung Galaxy S4 (Non T version) that appears to be soft bricked. My phone was hanging on the yellow Sprint screen so after other procedures, I decided to try and ODIN a stock version. What I had before all this happened was MK2 (knox) stock with only CF Auto Root. I downloaded the MK2 stock ROM from XDA and tried to ODIN. It failed. It got through the majority of the process and then at the very end it said FAILED. Now if I try and boot the phone, it automatically goes into the firmware error screen. So I still have the ability to ODIN but it always fails. I have also downloaded the NAE stock ROM from XDA and tried that too. I have tried using Odin 3.07, 3.09, and even 1.85. All fail. On the screen I sometimes get these messages as the ODIN process fails. Either a start [2xx, 1440] and next line BAR [2xx, 1440], or I get a start and then a sw rev check fail fused 5 binary 4. These are all in red letters just underneath the download mode details. I really don't know what to do. Please help me recover my phone. Any help is greatly appreciated. Thanks so much!
Click to expand...
Click to collapse
So now I would like to reply as to try and help anyone else that might have had something similar to this happen to their phone. I DID FIX my phone but using a CRAZY method that I have no good idea of why it worked. So here goes...
LONG VERSION (Short Version below for those that don't want to read about all my trials and efforts):
So as I mentioned I was on MK2 before the problem started. I tried to ODIN the MK2 Stock ROM I downloaded here but it failed. So then I decided ok maybe the issue was the older ROM, so I downloaded the NAE Stock ROM and tried to ODIN that. Again, failed. Now both of these 2 tries got far into the process before they failed. So again, through reading various posts here and on other forums it was suggested to try with other version of ODIN (I had been trying 3.07). I then tried the MK2 ROM again but with ODIN 3.09 but it failed almost immediately. That is when I noticed the lines "SW Rev Check Fail Fused 5 Binary X" every time it tried and failed. My guess is that this has something to do with the whole not being able to downgrade ROMs at any point and since I had almost completed the NAE stock ROM ODIN flash, it was stuck only with the option for NAE. So then onto trying NAE with ODIN 3.09. Once again, got most of the way done but failed toward the end of the system.img.ext4 part. I kept noticing that on the screen, almost as soon as I started the ODIN process it would output a line saying Start [220, 1440] and then soon after a line saying BAR [224, 1440]. Now I still have no idea what any of that means, but it was always failing, mostly toward the end of the flash. I then tried other ODIN versions including 1.85. All with the same results. I was at a loss. At that point I got desperate and decided I wasn't even going to try and save my DATA and thought maybe the partitions got corrupted so I found the NAE PIT file from these forums and attempted to ODIN both the PIT and the PDA with re-partition option. Once again, all attempts with all ODIN versions failed, with the same START and BAR messages showing up. I then broke down and decided to post here for help. I kept reading but everyone kept just saying in other threads about maybe KIES interfering if it was active in anyway, etc. so I check my processes and there were no KIES ones running. At that moment something occurred to me about another process by which to flash that I remember from my Galaxy S2 days. That was Heimdall. So, I decided to go on a mission to learn how to use Heimdall myself without a ready package. I finally learned how and decided to try it. I had to extract out all the .bin and .ext4, etc files out of the NAE tar and load them up manually. I started to flash and it looked to be working but then alas, it failed similarly to how ODIN did. I was at my wits end by this point. However, something occurred to me when I realized that the .tar had all these independent files in it that ODIN just tried to do all together. So here is what I did that finally WORKED. I used ODIN 3.09 with the NAE PIT file and the NAE ROM PDA file. I checked only Re-Partition and unchecked all others. I then watched exactly what ODINs log said was being flashed to the phone and what failed. I kept re-flashing until I got passed the system.img.ext4 file and the it failed on one of the others. I made note at which files out of the 13 that came from the .tar file were sent by ODIN successfully before it failed. I then closed ODIN and restarted phone in download mode and went to Heimdall. I used Heimdall to manually select only the remaining files left of the 13 that DID not go through successfully. I then flashed those I think 3 or 4 files and it said it was successful. I then rebooted my phone and to my SHOCK the phone booted up successfully and went into the OS as if it was factory wiped and ready for first time use. I was a bit bummed about having to redo all my settings, etc again and losing my old Text Messages, etc, but was so happy to have my phone back up and running. Thanks for reading this whole thing (I know it was quite long) and I hope it helps someone else out of a similar jam.
SHORT VERSION:
GET NAE Stock ROM
GET NAE PIT File
GET ODIN 3.09
GET Heimdall
YOU WILL LOSE YOUR DATA
Step 1) Use ODIN 3.09 (Run as Admin) and load up PIT file and PDA. Uncheck everything but RE-Partition
Step 2) (Hard Part) Keep flashing over and over again until you get at least the system.img.ext4 part to go through before ODIN says FAIL (It should fail on another file, like hidden.img.ext4 or NON-HLOS.bin
Step 3) Scroll through the ODIN log on the left and note every file that was successful. Basically any files it says was successful until the last one that it stops at and says FAIL
Step 4) You will need to extract out the contents of the NAE Stock ROM tar file to another directory
Step 5) Use Heimdall frontend (Run as Admin) and use the flash tab
Step 6) Load the PIT file into Heimdall as that is required for anything. But DO NOT use RE-Partition option
Step 7) Click Add and select each of the remaining files with their appropriate Partition Name and browse for those files from the ones you extracted from the tar. There are 13 files total from the tar file. Just load up (Add) starting with the file that failed in ODIN and then load up whichever ones that did not show up on the ODIN log at all. Click Start and cross your fingers
Step 8) If all went well, the phone should reboot and be up and running. If not you might have to start at Step 1 and try again
Step 9) Jump For Joy that your phone is Alive and working again!!!
Once again, I wanted to share my experience with everyone in hopes that it will help someone else out. I have no idea why I had to go to such great lengths of combining 2 versions of FLASHING and doing it piece by piece, but that is for greater minds then me to either know or figure out. I'm just happy my phone is working again! Good luck to anyone else having a similar issue.
SuperG03
Hello All,
First let me say I've used xda for a number of previous rootings (moto G, moto X), but this was my first attempt with an ATT Galaxy S7 (SM-G930A).
I was able to root the phone without a problem following the exceedingly useful guides posted here. I was set to start removing all the bloatware from the phone manually, when I saw a ROM had been made with the bloatware removed. I attempted to install the Deodexed & Debloated Stock ROM, with the guide at droidviews.
I installed the ROM through FlashFire without a problem. When I went to Download Mode to install the G930A_PF2_Stock_Modem_Recovery_Bootloader.tar.md5 via ODIN, the installation hung.
Now I am softbricked. I can boot into Download or Recovery, but that's it.
I have tried flashing the phone with virtually every stock ROM I can find, but all to no avail. If I am running the PrinceComey ODIN I get a dismatch error; if I am running the latest ODIN it hangs on SetupConnection.
I have installed and reinstalled the Samsung Drivers, performed a factorty reset from Recovery, followed every guide I can find online to return my phone to Stock, all to no avail.
If anyone can offer any assistance, I would be truly grateful. I'm simply trying to get back to Stock (I can then refollow the steps to root and remove the bloatware myself).
Thank you in advance for any assistance that can be offered. This seems like a brilliant forum!
There is a thread with a member with the PK1 files. PM him for a link. This is the latest ROM from AT&T. His name is @QRhinehardt
Try using different versions of Odin. I used odin 3.12 and not the modified version. There is also another version that will ignore the checksum. I softbricked my phone a couple of days ago, this is how I fixed it.
svfusion said:
There is a thread with a member with the PK1 files. PM him for a link. This is the latest ROM from AT&T. His name is @QRhinehardt
Try using different versions of Odin. I used odin 3.12 and not the modified version. There is also another version that will ignore the checksum. I softbricked my phone a couple of days ago, this is how I fixed it.
Click to expand...
Click to collapse
Thank you very much for your reply. I do think the issues is the incorrect firmware - I've used other versions of ODIN and it get a FAIL! (Auth) error after the attempt at .system.img.ext4. I did some research on that and saw some suggestions to use the original pit file. Still to no avail. That said, I do now know the latest version of ODIN has no problems writing to my phone (given the appropriate permissions and files) so if I can get the right firmware I may well be on track.
Thank you again for the tip, and a very Merry Christmas!
barabaskid said:
Thank you very much for your reply. I do think the issues is the incorrect firmware - I've used other versions of ODIN and it get a FAIL! (Auth) error after the attempt at .system.img.ext4. I did some research on that and saw some suggestions to use the original pit file. Still to no avail. That said, I do now know the latest version of ODIN has no problems writing to my phone (given the appropriate permissions and files) so if I can get the right firmware I may well be on track.
Thank you again for the tip, and a very Merry Christmas!
Click to expand...
Click to collapse
Are you running Odin as administrator?
Sounds like your phone has a newer firmware than what is currently available to download here.
QRhinehardt said:
Sounds like your phone has a newer firmware than what is currently available to download here.
Click to expand...
Click to collapse
That was indeed the issue! Fortunately a kindly user shared the correct firmware, and the phone is up and running. Many thanks to all!
i need help with this too
barabaskid said:
That was indeed the issue! Fortunately a kindly user shared the correct firmware, and the phone is up and running. Many thanks to all!
Click to expand...
Click to collapse
can i get the correct firmware? my s7 g930a is stuck in a bootloop