Related
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
I just did legend fail.
Been on stock MK2 (MF3 sideloaded to upgrade MK2), then i decided to go back to 4.2.2 stock since i really did not like the 4.3, did not make any research, so i odin the MF3 files and tried to flaash, but got an error in first 5 sec. Now every time i switch on the phone its saying i have to make upgrade through KIES, what sounds work w/o luck.
I know we dont have 4.3 odin files yet and not sure we will have them, but is there any way still to get this device to work ? Or its absolutely broke ?
Would appriciate any help ty
If Samsung experience at best buy has the new update, you could try to see if they could help. If not, I feel you are in for a wait.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I did the same thing on my SGH-I337M. Kies was a waste of time. I used Odin, downloaded the newest 4,3 firmware and reflashed it in update bootloader section only. Took about 8 minutes but saved my phone. Knox won't let us downgrade so we are sad at the moment.
can any1 please share this file bootloader of MK2 so i can flash it throu odin to make the device to work, would appriciate any further info or help ty. w/o phone for 3 days already
HiTideBlastoise said:
If Samsung experience at best buy has the new update, you could try to see if they could help. If not, I feel you are in for a wait.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I know you used the xda app so you probably didn't notice the OP is located in Athens, Greece. So no dice
Yeap got the phone from my bro he is leaving in Rochester, if i would know that he sent me At&T and its as block as it is now, i would spent money to buy it from Amazon Germany, internatioonal fully functional =) but my luck
Since we got the 4.3 update closing our download funtion in phone, will we be able to flash through odin the stock 4.3 MK2 to re-stock bricked sgs4 ? like you can do with MF3?
I am asking since currently i am w/o phone and waiting for someone to post the stock MK2, but will that for sure make it work normal excluding its blocked downlaod etc. ? just curious
Same thing happened to me.. I worked for hours and finally just tried flashing the I337 PIT file thru Odin in the Pit option.. It said failed but I pulled the battery and rebooted into recovery then restarted.. Google for the pit file.... I have the full zip MK2 file but you have to have the MD5 files for Odin
Sent from my GT-N8013 using xda app-developers
If i will flash PIT file i will be able to enter recovery ? since know the only option i have is download mode, and kies recovery (what is useless)
When u flash PIT with fail and enter recovery what did you do next ? the device booted normally ?
Where can i find this PIT ?
Ty for the help
So let me ask this so I do not make a similar mistake. Yesterday I used odin to go to mf3 then sideloaded mj9,. If I have the file for mk2. Can I just side load it even though im on mj9?
nomikSqash said:
If i will flash PIT file i will be able to enter recovery ? since know the only option i have is download mode, and kies recovery (what is useless)
When u flash PIT with fail and enter recovery what did you do next ? the device booted normally ?
Where can i find this PIT ?
Ty for the help
Click to expand...
Click to collapse
When I flashed the PIT file, I just took a chance and tried to boot it, and it allowed me to boot normally. It also allowed me to enter recovery
---------- Post added at 06:52 PM ---------- Previous post was at 06:50 PM ----------
blackguy101 said:
So let me ask this so I do not make a similar mistake. Yesterday I used odin to go to mf3 then sideloaded mj9,. If I have the file for mk2. Can I just side load it even though im on mj9?
Click to expand...
Click to collapse
Yes, you should be able to sideload or flash the zip through recovery.. With all these fails at updates, I wish I would have stayed at what I had and not messed with it..lol.. It seems nothing is guaranteed and it's always a risky chance when you flash something..
I decided to update to 4.3 and didnt like it so i stock flash 4.2 back via odin. flash said "pass" but now i have knox on recovery. Im guessing i have the new bootloader. 4.2 flash on but with errors like wifi wont toggle on & on every reboot i get an erro "kernel seandroid is not reonforsing" or something like that...so now im stock on 4.3 :/
blackguy101 said:
So let me ask this so I do not make a similar mistake. Yesterday I used odin to go to mf3 then sideloaded mj9,. If I have the file for mk2. Can I just side load it even though im on mj9?
Click to expand...
Click to collapse
The mistake i made was to go downgrade from 4.3 to 4.2.2 do not make it since we do not have files for ODIN flash 4.3.
There is full 700 mb file witch you can easily sideload, if u get any error just go back to odin to flash stock MF3 and then sideload MK2, worked for me w/o problem but pls do not downgrade !
If i were you i would not go 4.3, TW is much more bugged for me, and phone feels way different thats why i wanted to go back to 4.2.2
nerdyblonde said:
When I flashed the PIT file, I just took a chance and tried to boot it, and it allowed me to boot normally. It also allowed me to enter recovery
---------- Post added at 06:52 PM ---------- Previous post was at 06:50 PM ----------
Did not get it, i need to get the PIT file, but when can i get it to flash through ODIN if we do not have files for odin yet ?
Click to expand...
Click to collapse
I was able to downgrade... kinda..
I had my own epic fail when bell's update came out.
Flashed stock/counter reset.
Got OTA update no prob.
Rooted - Deleted too much bloat... (didnt backup) MY EPIC MISTAKE.
Thought "oh ill just start again"
Odin Back to 4.2.2 FAIL!!!
Stuck.. kinda
found someone with the international version in the same issue that odin flashed files from another carrier and was able to fix his situation...
so i went to http://www.sammobile.com/firmwares/ and downloaded the NEWEST date 4.2.2 rom for my 337m, which happened to be Dominican Republic carrier.
Flashed the DR version successfully in odin, and had no sound, no mic, no wifi.
I was then able to Odin flash 4.2.2 from bell... but still had no sound, no mic, no wifi....
the only real fix was LUCKILY within 24 hours of the OTA release, the odin file was posted to sammobile and saved my ass... all works now.
Played with the 4.3 update for a couple hours, then went back to 4.4 builds... LOL
At least i got to use my captivate again for a few calls for a day. that was nice.
Really have no idea how i an fix this w/o odin files.
umm you cant.
Problems solved, any1 who will have the same issue as me:
Had MK2 update installed and wanted to downgrade to 4.2.2 and failed to kies update, just flash the attached filed, it will fail you in download mode, but after 2-3 tried, just restart the device, and it will normally boot into 4.3 =)
Ty for all the help, and info best regards !
nomikSqash said:
Problems solved, any1 who will have the same issue as me:
Had MK2 update installed and wanted to downgrade to 4.2.2 and failed to kies update, just flash the attached filed, it will fail you in download mode, but after 2-3 tried, just restart the device, and it will normally boot into 4.3 =)
Ty for all the help, and info best regards !
Click to expand...
Click to collapse
That's the file I had used before too.. I posted it on another guys post.. Glad it worked for you
http://forum.xda-developers.com/showthread.php?p=47586777
This is the complete guide on how to flash back from 4.2.2. Even that 16 gig pit file won't even work on some peoples phone. Use this guide and it will help you get back to 4.3. First mj9 than you can sideload mk2.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
---------- Post added at 08:15 PM ---------- Previous post was at 08:13 PM ----------
nomikSqash said:
Problems solved, any1 who will have the same issue as me:
Had MK2 update installed and wanted to downgrade to 4.2.2 and failed to kies update, just flash the attached filed, it will fail you in download mode, but after 2-3 tried, just restart the device, and it will normally boot into 4.3 =)
Ty for all the help, and info best regards !
Click to expand...
Click to collapse
That file I gave you won't help if your stuck with incomplete flashes. For people who were experiencing the problem I had use that guide posted by gtj0 and you'll get your phone back to normal.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Hi Guys and Gals,
I have an ATT Samsung Galaxy S4 SGH-i337 with Android 4.2.2 but I can't get the 4.3 update via OTA. I tried forwarding the date to update to MK2 but it says my software is up to date. I tried using Kies today, but it won't show any updates.
Anyone have a method of upgrading from MF3 to MK2 that is not OTA?
Please let me know if someone can help me with a step by step guide.
Thank you!!
RIQUISIMO said:
Hi Guys and Gals,
I have an ATT Samsung Galaxy S4 SGH-i337 with Android 4.2.2 but I can't get the 4.3 update via OTA. I tried forwarding the date to update to MK2 but it says my software is up to date. I tried using Kies today, but it won't show any updates.
Anyone have a method of upgrading from MF3 to MK2 that is not OTA?
Please let me know if someone can help me with a step by step guide.
Thank you!!
Click to expand...
Click to collapse
I have the same problem, sometimes it will find an update and download only to do nothing. I think this is a problem with att's crap servers/update system.
RIQUISIMO said:
Hi Guys and Gals,
I have an ATT Samsung Galaxy S4 SGH-i337 with Android 4.2.2 but I can't get the 4.3 update via OTA. I tried forwarding the date to update to MK2 but it says my software is up to date. I tried using Kies today, but it won't show any updates.
Anyone have a method of upgrading from MF3 to MK2 that is not OTA?
Please let me know if someone can help me with a step by step guide.
Thank you!!
Click to expand...
Click to collapse
Adb sideload
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
AT&T OTA Failboat
I've tried three times now to update my wife's S4. The first time the download started, then just disappeared. No warnings or errors. Tried updating and it said to wait 24 hours. Next day I started the download again. It got to 23% then said interrupted. Clicked the software update again and it started again, but stopped at 24% saying download failed. Then it said to wait another 24 hours.
Fast forward to tonight and I tried it again. I got 100% of the download only to get a screen that said Software Update Interrupted and to try again in 24 hours. The wife doesn't want me to root her phone, so I'm trying to do this the "normal" way, but AT&T and Samsung seem intent on not letting this happen. If the file got to 100%, is it still on the phone somewhere? If not, is there a link to download the update so I can sideload it and instructions on where the file must be placed?
Endbringer42 said:
I've tried three times now to update my wife's S4. The first time the download started, then just disappeared. No warnings or errors. Tried updating and it said to wait 24 hours. Next day I started the download again. It got to 23% then said interrupted. Clicked the software update again and it started again, but stopped at 24% saying download failed. Then it said to wait another 24 hours.
Fast forward to tonight and I tried it again. I got 100% of the download only to get a screen that said Software Update Interrupted and to try again in 24 hours. The wife doesn't want me to root her phone, so I'm trying to do this the "normal" way, but AT&T and Samsung seem intent on not letting this happen. If the file got to 100%, is it still on the phone somewhere? If not, is there a link to download the update so I can sideload it and instructions on where the file must be placed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=47905776&postcount=657
There's the link I know the threads are so cluttered you can't find it but you have to find the instructions to sideload which is in the general section mj6 to mj9
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I was able to get the OTA on the second try. What worked for me was to leave the phone on the charger and enabling the "stake awake while charging" option in the developer options. Don't forget to turn that option off after the upgrade.
My sgh-i337 was stuck in a bootloop where twrp wasn't working, but using Odin didn't work either. What I ended up doing was upgrading the firmware in Kies, which worked, but it stayed on mdl firmware. It completely wiped my system. No data whatsoever (except my external sd card) and no root. I stupidly upgraded to mf3, because I didn't know that AT&T had locked down the bootloader. When I realized this, I went straight back to Kies and tried to do the upgrade again, but I didn't realize that it was solely for mdl. So my phone got stuck in "Firmware upgrade an issue. Please select recovery mode in Kies & try again." There is a yellow caution sign in the middle, with two dots going to the left with a phone at the end, and two dots to the right of the sign with a computer at the end. In the upper left-hand corner, there is the Odin Mode dialogue:
"ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
The only thing I can boot to other than the above mode is Odin Mode, but because my phone is no longer rooted, this does me no good. I can't boot to recovery mode, either. When the phone is off (from taking the battery out or holding the power button), by pressing the power button, it goes to the firmware upgrade issue screen. In another thread, it mentioned booting to the confirmation to boot to Odin, and pressing the volume down button to restart, but this takes me right back to the firmware upgrade issue screen.
Please help me!!!!!
P.S. Someone mentioned taking it to the AT&T retailer because it is no longer rooted, but I want to see if I can avoid this because the warranty might be voided because it was rooted.
You'll have to flash the mf3 firmware now. Use Odin. Google mf3 tar files xda
jd1639 said:
You'll have to flash the mf3 firmware now. Use Odin. Google mf3 tar files xda
Click to expand...
Click to collapse
Odin doesn't work because it is no longer rooted. Thanks for the reply though.
txk623 said:
Odin doesn't work because it is no longer rooted. Thanks for the reply though.
Click to expand...
Click to collapse
You don't need to be rooted to use odin
jd1639 said:
You don't need to be rooted to use odin
Click to expand...
Click to collapse
Thanks a lot.
I added MF3.tar mirror on my thread http://forum.xda-developers.com/showthread.php?t=2573080 . And u don't need to be root to use Odin..... if u would like to upgrade to 4.3 mk2 this thread might also help you .......goodluck.....
SWYPED_FROM_S4_MF3_REDVENOM
I am currently trying to get the 4.4.4 update to either go through or stop asking. At the moment it fails every time I try to install it. I assume this is because I was rooted but when trying to use safe strap (tried 3.72 and 3.75) to install jelly beans build 6 I kept getting a black screen on boot. I also tried to flash cynogen with the same issue. All I want to do at this point Is go back to stock so the update will go through or get jellybeans to install properly. Any advice would be appreciated. Thanks.
factory reset and odin a fresh copy of 4.4.2. Reroot then install your rom. Why would you ever go to 4.4.4 where you will not have root.
Root really wasn't that important to me. I was interested in custom roms but when I couldn't get one to load decided it was the only way to get rid of those annoying update requests.
Sent from my SM-N900V using XDA Free mobile app
Also I have no PC
Sent from my SM-N900V using XDA Free mobile app
timothyjon86 said:
Also I have no PC
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
You are on NC4 yes? If so you need a pc and you need to odin the unified firmware that is why you got the black screen. Also no jellybeans for you your stuck on all of the current NC4 based roms.
to take the NK1 update will also require a pc and is also non root able or reversible.
To get rid of the update notices freeze sdm.apk using titanium backup pro.
Brick
Hey guy's I'm sorry to not just post my own but I'm new to the forum and it wont let me. A few days ago I unrooted my note 3 for the new 4.4.4 update and updated it. Midway through the update it said error and when it rebooted it just stuck at the note 3 custom logo. I've tried resetting it, flashing it, and even just putting on some custom rom. But nothing works and when I download the 4.4.2 firmware from sammobile it's literally nothing, I open it and it is a 0 byte file. A 0 byte file that too all day to download. When I attempt to flash anything I get the error sw rev check fail : [aboot]fused 3 > binary 1. I don't know why or how to get it back up and running. Sammobile seems to be the only place I can even find the right files and it doesn't have the 4.4.2 that I originally had on my note. Can I flash to the new 4.4.4? What do I do? Please help, sorry for not making my own post.
Kevkas12 said:
Hey guy's I'm sorry to not just post my own but I'm new to the forum and it wont let me. A few days ago I unrooted my note 3 for the new 4.4.4 update and updated it. Midway through the update it said error and when it rebooted it just stuck at the note 3 custom logo. I've tried resetting it, flashing it, and even just putting on some custom rom. But nothing works and when I download the 4.4.2 firmware from sammobile it's literally nothing, I open it and it is a 0 byte file. A 0 byte file that too all day to download. When I attempt to flash anything I get the error sw rev check fail : [aboot]fused 3 > binary 1. I don't know why or how to get it back up and running. Sammobile seems to be the only place I can even find the right files and it doesn't have the 4.4.2 that I originally had on my note. Can I flash to the new 4.4.4? What do I do? Please help, sorry for not making my own post.
Click to expand...
Click to collapse
Nobody should want to be touching 4.4.4 with a 10 ft pole it does nothing substantial unless you own a smart watch or want to lose root. That said I think your at the point of no return. Your going to have to odin NK1 to your phone not NC4 the partial update seems to have hit your bootloader with the NK1 locked bl. I would try going into download mode first and checking if it is updated if it is you will then need to odin NK1 if it is not NK1 and it is still nc2 or nc4 look for a mirror to that odin file. But I'm sure your bootloader got updated and that is why it is now rejecting the 4.4.2 you're attempting to load.