I have had nothing but issues trying to use this software to update the firmware on my ATT S3. I'm new to Android (From Apple) and I'm still a noob but I have rooted and I have been trying all kinds of different ROMS. I cannot update my phone because I am getting the dreaded "Communication failed" error that more than a few people are getting.
One fix is to install latest update through Kies - but I can't seem to accomplish that. Am I able to update my firmware using Odin? I really haven't figured out much about Odin, I only rooted my phone with it once and that was easy and I din't learn a lot about Odin.
Can I use Odin to update firmware? If so how do I go about getting firmware file and whats the quick of it?
Thanks! :good:
jackryan57 said:
I have had nothing but issues trying to use this software to update the firmware on my ATT S3. I'm new to Android (From Apple) and I'm still a noob but I have rooted and I have been trying all kinds of different ROMS. I cannot update my phone because I am getting the dreaded "Communication failed" error that more than a few people are getting.
One fix is to install latest update through Kies - but I can't seem to accomplish that. Am I able to update my firmware using Odin? I really haven't figured out much about Odin, I only rooted my phone with it once and that was easy and I din't learn a lot about Odin.
Can I use Odin to update firmware? If so how do I go about getting firmware file and whats the quick of it?
Thanks! :good:
Click to expand...
Click to collapse
What firmware are you trying to update to? Once your phone is rooted and your "trying all kinds of different ROMS" I question your need for Odin. Unless your trying to go back to a bone stock ROM I'd think that you would want to use whatever custom recovery that you've installed (CWM or TWRP) to install a ROM. I'm not going to link to it but I can guarantee that if you search for it here or on Google you'll find several guides to Odin.
rcook55 said:
What firmware are you trying to update to? Once your phone is rooted and your "trying all kinds of different ROMS" I question your need for Odin. Unless your trying to go back to a bone stock ROM I'd think that you would want to use whatever custom recovery that you've installed (CWM or TWRP) to install a ROM. I'm not going to link to it but I can guarantee that if you search for it here or on Google you'll find several guides to Odin.
Click to expand...
Click to collapse
Well, here's the thing. ATT has pushed out updates and I'm not getting them. I know some updates improve things - like call quality etc. Since I am not getting these I'm worried that I am missing out. I have uninstalled EVERY SINGLE ROM I have tried because of one issue: everyone I talk to on my phone hears an echo of their voice, it's so bad they tell me they have to hang up. It only does this on custom ROMs. So, I would like to be able to get these updates...not sure if I am making sense or not. Since Kies is such an incredibly horrible piece of software, I was hoping there was another way I could update my phone?????
Got ya, you should be able to use Odin to install the stock ROM. I think it's Sam Mobile? that you can register at and get the latest stock firmware. Again, search for the best way but it's doable.
I have searched countless threads for assistance. I have been able to root every phone I've had. I am finally having an issue with my GS4 from AT&T. I bought it back in May, but had to go out of the country for work before I could root it and I just got back this last week. It had received the updates from the server so it is now running the I337UCUAMF3 build. I ran Motochopper, but it said failed and no SU. I have tried utilizing Odin to revert back to the original firmware so that I can try running Motochopper, but when I try it shows fail when in the middle of running the program. I tried factory reset from within android and the stock recovery, but it just reverts back to the latest firmware. I tried going through Kies, but it won't do a recovery and says that it is only through the phone server. I have downloaded 10's of gigs of firmwares, motochoppers, loki flashes, etc.... I am officially lost and would love any assistance someone could offer, cause I would really like to get a better ROM installed like on my other phones.
Thank you
Read the gs4 forum. The info is there. You cant revert back to a later firmware. You can't use Loki or motochopper. All you can do now is root mf3 firmware and that process just became available a few days ago. Stop what your doing and read read and read.
Sent from my SAMSUNG-SGH-I337 using xda premium
venomoussniper said:
I have searched countless threads for assistance. I have been able to root every phone I've had. I am finally having an issue with my GS4 from AT&T. I bought it back in May, but had to go out of the country for work before I could root it and I just got back this last week. It had received the updates from the server so it is now running the I337UCUAMF3 build. I ran Motochopper, but it said failed and no SU. I have tried utilizing Odin to revert back to the original firmware so that I can try running Motochopper, but when I try it shows fail when in the middle of running the program. I tried factory reset from within android and the stock recovery, but it just reverts back to the latest firmware. I tried going through Kies, but it won't do a recovery and says that it is only through the phone server. I have downloaded 10's of gigs of firmwares, motochoppers, loki flashes, etc.... I am officially lost and would love any assistance someone could offer, cause I would really like to get a better ROM installed like on my other phones.
Thank you
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?p=44165374#post44165374
You are on MF3 build which means this is only root method that will work, but be careful what you do after rooting, currently there is no custom recovery available for the MF3 build due to locked bootloader and loki being patched and there is not any Odin images to restore stock firmware if need be yet. Once you upgrade to MF3 from MDL, there is no way to go back either.
Hope this helps!
Thank you so much for your help!! Much appreciation to all the techs out there for making all these sweet ROMs and roots!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.
GreatGrizzwald said:
I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.
Click to expand...
Click to collapse
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
http://www.sammobile.com/
absinthesummer said:
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
Thank you very much for the advice. I am downloading the firmware now. baseband version is showing i317ucama4. Right now the phone is not activated with AT&T, is there a way I could test if I will be able to get cellular data before going to AT&T and activating it?
Click to expand...
Click to collapse
Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.
Just use your father's sim card. Either it connects to the GSM network or it doesn't.
absinthesummer said:
Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.
Click to expand...
Click to collapse
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?
1425
rangercaptain said:
Just use your father's sim card. Either it connects to the GSM network or it doesn't.
Click to expand...
Click to collapse
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.
GreatGrizzwald said:
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?
Click to expand...
Click to collapse
It sounds like the phone was updated previously to either 4.3 or 4.4.2, which have Knox and that pesky counter. Technically you can't directly downgrade, so be sure you're downloading firmware that is 4.3 or higher. I didn't realize sammobile only went to MA4 for US AT&T. (In a pinch you can use Canadian firmware, but we have other links for stock firmware). Also, don't worry too much about Kies. It can be helpful, but honestly I could never get my note 2 recognized by kies either.
When I get back from taking my kids to school, I'll gather some links that will help you revive this phone Links below:
@GreatGrizzwald:
More recent links to stock firmware: STOCK PACKAGES TO MK6 This is LJ2 (4.1.2), MK6 (4.3) and up. He's got all the stock firmwares, available for flashing either in recovery on via odin. I've highlighted the one I would use in the attached screenshot (MK6- ODIN)
He also has a thread for NE5 (The latest firmware, 4.4.2) HERE
So if MK6 doesn't work, try NE5. One of those two has to work. You're dad already updated to either 4.3 or 4.4.2, I don't know which so start with 4.3 (MK6) and if it doesn't work try 4.4.2 (NE5)
On those two threads, he has a TON of links that will be helpful to you in getting back to stock also.
And here's a reference page with some useful links: One Stop Shop
This one is dedicated to downgrading back to LJ2 (4.1.2) from 4.3+, it MIGHT come in handy for you: Downgrade Instructions
If you have trouble with the stock firmware, you can also try Chainfire's CF Auto Root. It's stock firmware but it's rooted. Try the other firmwares by Zen Arcade first though CF AUTO ROOT
We'll get it going for you The stock firmware will re-flash the modem and all the configuration files so you're data should work again. Then you can do whatever you want, root, recovery, flash other stuff, or leave it stock. You got this
---------- Post added at 07:51 AM ---------- Previous post was at 07:09 AM ----------
GreatGrizzwald said:
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.
Click to expand...
Click to collapse
Also you have to figure out if it's software or hardware. I'm inclined to believe it's software so I think if you get it back to stock you'll be good. If it was hardware, it wouldn't even recognize a sim being inserted (recently repaired an htc one mini with this problem, it needed a new Sim tray, thankfully it was only $20).
But it sounds more like a bad flash corrupted some of those important files and configurations controlling data connections, it's all good, if it's software it can definitely be fixed. If it were hardware it could still be fixed it would just be a bit more time consuming.
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Thank you for all this, I will start working with it today. You have been a huge help.
GreatGrizzwald said:
Thank you for all this, I will start working with it today. You have been a huge help.
Click to expand...
Click to collapse
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!
1100
absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.
GreatGrizzwald said:
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.
Click to expand...
Click to collapse
That is great news! I'm so glad it's working for you. Enjoy your (new-to-you) note 2 and keep those files on hand in case you need them in the future!
absinthesummer said:
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!
Click to expand...
Click to collapse
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?
GreatGrizzwald said:
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?
Click to expand...
Click to collapse
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.
absinthesummer said:
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.
Click to expand...
Click to collapse
Awesome, that makes a lot more sense now. Thanks again.
Hey I forgot you don't have custom recovery. Anyway, I sent you PMs,and you can do a search of this very forum- use the search term "update" or "ota" and you will find a LOT of threads on boot failures after OTA. Most people got their phones back.
If you can't get into DL mode (Vol-, Home, Power), try getting into the stock recovery (Vol+, Home, Power) because you should/could be able to factory reset the device from there. Also hold the button combo longer than usual. If one recovery option (DL mode) isn't working, than theoretically the other should still be accessible, through which you can adb sideload to the device or try factory reset. I know it's frustrating, but you're not the first nor the last to have an OTA go wrong ;/ We'll get ya back up & running.
You're not the only one in trouble after that update: http://forum.xda-developers.com/galaxy-note-2-att/help/todays-update-soft-bricked-phone-t2939649
Hi, I've got this one Note 4 that's had loads of trouble presumably since the last security update.
Baseband Version: N910AUCS2EQD1
Android: 6.0.1
Have seen the instructions and all as to how to go about downgrading BUT one site I came across with the original stock firmware downloads outright state how:
""DO not ever try to downgrade from any newest Android 6.0.1 Marshmallow updates back to an older 6.0.1 build version""
'and so I'm lost. Should trying to then reinstall the same Baseband version atop what's already there a good first alternative? ...that is, just in case it was never upgraded properly in the first place? Or is that not even possible?
Is trying to downgrade at all a futile pursuit?
Would truly appreciate any suggestions, help, direction...heck, anything! Thanks in advance.
I downgraded from 6.0.1 epk5 to 5.1.1 with no problem.
Not sure about qd1.
As long as you have the odin firmware, I see no problem.
Can i downgrade note 4 n910a from marshmallow to lollilop,please help me i am in great trouble because marsmallow update is very bad with a lot of reboot issue ,battery drain.
Once you are on QD1 you will not be able to go back to anything lower than that firmware. The bootloader is now at the latest version and has blown one of those imaginary "e-fuses" so that you can not go back in time to any other vulnerable OS. I just tried today to go from EQD1 to EPK5 and It would not flash and would fail every time whilst using the latest Odin. So good luck on finding anything on getting you back to another firmware version but at this time I do not believe there is anything that will move you back to the firmware you want. If you do happen to find something or make your own exploit do tell @sanaullahkhan371 If you are on QD1 you are not going to be able to downgrade if you are on PK5 you can try the Odin downgrade method that will5 presumably used but if you are not in this firmware use case you are SOL.
will5 said:
I downgraded from 6.0.1 epk5 to 5.1.1 with no problem.
Not sure about qd1.
As long as you have the odin firmware, I see no problem.
Click to expand...
Click to collapse
Hi,
Can you please let me know how did you downgrade? Is it straight away flash to 5.1.1 or did you follow any steps?
I am also planning to downgrade. Anyways, I stopped using Note 4 after update to 6.0.1 as it was switching off every now and then due to update. Might as well make this phone usable to take photos and as a video player for my kid
Thanks
roxster said:
Hi,
Can you please let me know how did you downgrade? Is it straight away flash to 5.1.1 or did you follow any steps?
I am also planning to downgrade. Anyways, I stopped using Note 4 after update to 6.0.1 as it was switching off every now and then due to update. Might as well make this phone usable to take photos and as a video player for my kid
Thanks
Click to expand...
Click to collapse
I just odin to this firmware N910AUCU2DOI2-5.1.1 It s available somewhere on this forum.
Read how to odin if you never used it. In this case you need to unzip the file and load AP, BL, CP and CSC files on odin and flash.
Was running 6.0.1 epk5 previously.
will5 said:
I just odin to this firmware N910AUCU2DOI2-5.1.1 It s available somewhere on this forum.
Read how to odin if you never used it. In this case you need to unzip the file and load AP, BL, CP and CSC files on odin and flash.
Was running 6.0.1 epk5 previously.
Click to expand...
Click to collapse
Thanks a lot buddy! :good:
My note 4 was also running on 6.0.1 EPK5. Found the 5.1.1 firmware and followed your instructions to downgrade. My phone came back to life and is usable now.:victory:
No more switching off abruptly! I wont update anymore since all the apps which I use are working fine with current version of Android.
braindead444 said:
Once you are on QD1 you will not be able to go back to anything lower than that firmware. The bootloader is now at the latest version and has blown one of those imaginary "e-fuses" so that you can not go back in time to any other vulnerable OS. I just tried today to go from EQD1 to EPK5 and It would not flash and would fail every time whilst using the latest Odin.
Click to expand...
Click to collapse
Were you ever able to flash back to an older version from QD1? Others have said that the bootloader was not incremented in QD1.
spocko said:
Were you ever able to flash back to an older version from QD1? Others have said that the bootloader was not incremented in QD1.
Click to expand...
Click to collapse
Were you able to downgrade from EQD1 to 5.1.1? I am on EQH1 and I am not able to downgrade
somani09 said:
Were you able to downgrade from EQD1 to 5.1.1? I am on EQH1 and I am not able to downgrade
Click to expand...
Click to collapse
I'm also on EQH1. I have never tried to downgrade. I was just curious if it was possible, in case a root method was discovered that only worked on older versions. But I've just learned to live without root. EQH1 works fine for me.
I had the infamous freeze/reboot/shutdown issue with 6.0.1 and I wasn't sure if that was the issue but I downgraded to 5.1 and have fewer issues now. The phone runs just fine, except it does not reboot. You have to do a soft reset every time. But with the Wakelock app, at least it runs.
roxster said:
Thanks a lot buddy! :good:
My note 4 was also running on 6.0.1 EPK5. Found the 5.1.1 firmware and followed your instructions to downgrade. My phone came back to life and is usable now.:victory:
No more switching off abruptly! I wont update anymore since all the apps which I use are working fine with current version of Android.
Click to expand...
Click to collapse
Hi can i ask if u still have that firmware file