Database Users

Odin Stuck at Factoryfs.rfs - Can't Odin to Stock

Pulling what little hair I haver left out at this point. 8 hours now, and Odin is stuck during factoryfs.rfs. Never makes it past this point.
I've tried every trick I've come across in XDA and elsewhere (re-starting odin / unplugging & replugging / device drivers / all versions of Odin / etc)
I even tried Heimdall (can't find boot loader files anywhere to plug in to Heimdall Frontend.
I'm lost now, with seemingly every idea tried and failed. Phone will not boot, as Odin fails without finishing.
Anyone faced similar and come through it?
I can get into DL mode just fine...I've googled everything I can think of.

I had that happened before with odin 1.2. Updated to 1.7 and everything worked afterward.
Sent from my SGH-T959 using XDA App

yeah used both versions

sometimes using a different computer solves the problem for me.

Had this happen too. In my case switching to a USB port in the back of my PC rather than one of the ports on the front of my PC case fixed the issue. Try Odin'ing with your other USB ports?

Finally got it working...had a corrupted JFD file...replaced and all is well. Thx for the help

having same problem
I'm having the same problem. What is a corrupted JFD file and how do I fix it?

Ran into the same issue. I checked "Phone Bootloader Update" in odin 1.82 and it finally worked. Not sure why, but I'll take it.

Bandage said:
Finally got it working...had a corrupted JFD file...replaced and all is well. Thx for the help
Click to expand...
Click to collapse
What file is that, and how did you fix it? I am stuck with the same problem and nothing seems to work...

^ check my signature for going back to stock thread. If you have an operational phone, you should be good with my guide.

ccole22653 said:
What file is that, and how did you fix it? I am stuck with the same problem and nothing seems to work...
Click to expand...
Click to collapse
Its the .tar file used for pda sometimes it gets damaged when you download it just need to redownload it
Sent from my SGH-T959 using XDA App

Bandage said:
Pulling what little hair I haver left out at this point. 8 hours now, and Odin is stuck during factoryfs.rfs. Never makes it past this point.
I've tried every trick I've come across in XDA and elsewhere (re-starting odin / unplugging & replugging / device drivers / all versions of Odin / etc)
I even tried Heimdall (can't find boot loader files anywhere to plug in to Heimdall Frontend.
I'm lost now, with seemingly every idea tried and failed. Phone will not boot, as Odin fails without finishing.
Anyone faced similar and come through it?
I can get into DL mode just fine...I've googled everything I can think of.
Click to expand...
Click to collapse
I finally found what the problem was, my stock tar file was not completely downloaded and was 180MB vs 291MB what it should have been. Redownloaded, tried again and it worked perfect. To those that still have the problem, try re downloading the files instead of trying the same one over and over, worked for me ;-)

hi i use to have the same problem. what i do is this.
1) Installed Odin and all the other files in a folder in the root directory of my computer (C:\). Don't know if this helps at all, just covering everything I've done.
2) Took battery out, SIM out and SDcard out.
3) put battery back in....leave phone off.
4) Start Odin using administrative
5) Now here is where I'm different: Hold down Volume up & down at the same time, don't press power.
6) While holding down the volume buttons together, plug the USB (already plugged into computer) into the Phone (Vibrant in my case). Should automatically go into Download mode, no fancy timing here.
7) Select your PIT and PDA (TAR) files
8) Click start....should immediately jump past cache.rfs
9) Leave it all alone until you get the green pass in Odin.
i really dont know if some of the points are important but it work.. i wish that can help you.

blemish31 said:
hi i use to have the same problem. what i do is this.
1) Installed Odin and all the other files in a folder in the root directory of my computer (C:\). Don't know if this helps at all, just covering everything I've done.
2) Took battery out, SIM out and SDcard out.
3) put battery back in....leave phone off.
4) Start Odin using administrative
5) Now here is where I'm different: Hold down Volume up & down at the same time, don't press power.
6) While holding down the volume buttons together, plug the USB (already plugged into computer) into the Phone (Vibrant in my case). Should automatically go into Download mode, no fancy timing here.
7) Select your PIT and PDA (TAR) files
8) Click start....should immediately jump past cache.rfs
9) Leave it all alone until you get the green pass in Odin.
i really dont know if some of the points are important but it work.. i wish that can help you.
Click to expand...
Click to collapse
I have been having the same problem here. I am only able to enter download mode, my phone won´t boot, not even cwm.
I have been trying to install a new rom via Odin but it gets stuck at factoryfs.rfs , I have tried everything even all said in this thread it still wont work. Also tried checked and downloaded several times the files as you mentioned.
Please, if anyone knows what else to try.
PS: I also tried installing other roms rather than darkys resurrection and they would all get stuck in some point during the installation via Odin, really wierd, please help!!!

Dude, you'd be better off starting a new thread in the Q&A section.
Secondly, do a lot more reading. You cannot flash custom ROMs with Odin. Odin is just used for flashing back to stock.

dpaul007 said:
Secondly, do a lot more reading. You cannot flash custom ROMs with Odin. Odin is just used for flashing back to stock.
Click to expand...
Click to collapse
Actually if you read up on DarkyRom, the Darky team makes Odin .tar's of their base roms. So yes you can Odin a custom rom. It's actually easy to make a Odin tar ball of any Samsung TWiz based rom on your phone.

Bandage said:
Pulling what little hair I haver left out at this point. 8 hours now, and Odin is stuck during factoryfs.rfs. Never makes it past this point.
I've tried every trick I've come across in XDA and elsewhere (re-starting odin / unplugging & replugging / device drivers / all versions of Odin / etc)
I even tried Heimdall (can't find boot loader files anywhere to plug in to Heimdall Frontend.
I'm lost now, with seemingly every idea tried and failed. Phone will not boot, as Odin fails without finishing.
Anyone faced similar and come through it?
I can get into DL mode just fine...I've googled everything I can think of.
Click to expand...
Click to collapse
What files are you flashing?? Are you flashing with or without a .pit?

Here is a guide from XDA for Flashing. Its easy to follow and ive never had an issue with it. Good Luck.
http://forum.xda-developers.com/showthread.php?t=1307637

I just plugged my usb into the back and i got past it. sat for the last 2 hours troubleshooting.....

[Q] Returning Galaxy S4 (rooted) for a new one. Please help. (or unroot help)

So yesterday when AT&T announced 50% off of smartphones I was pretty dumbfounded since I got a brand new S4 the day before. But the day I got it I rooted it and did all the other stuff. I will return my S4 for a new one but it's impossible for me to unroot. Everything I've done doesn't seem to work. I used Odin but it stops at the "Get PIT for mapping" stage. I tried deleting SuperSU but that didn't work. It made things worse because it said I'm not rooted but I still am. Now I can't even go to recovery. And I can't even connect to Kies. Can anyone help me unroot my device or help me be able to return my device when it's rooted?

joecereal said:
So yesterday when AT&T announced 50% off of smartphones I was pretty dumbfounded since I got a brand new S4 the day before. But the day I got it I rooted it and did all the other stuff. I will return my S4 for a new one but it's impossible for me to unroot. Everything I've done doesn't seem to work. I used Odin but it stops at the "Get PIT for mapping" stage. I tried deleting SuperSU but that didn't work. It made things worse because it said I'm not rooted but I still am. Now I can't even go to recovery. And I can't even connect to Kies. Can anyone help me unroot my device or help me be able to return my device when it's rooted?
Click to expand...
Click to collapse
I would think the tools section of Kies will have an option that will work. Connection trouble shoot first then emergency recovery. If your phone boots, you should be able to reset it to out of the box state.
If it's still rooted, try triangle away app.
If you go to settings, more, about device, build number, then tap on build number repeatedly it will restore developer options, if it's not shown now. From there you can enable or disable USB debugging. That might help with Odin. Wish I had more answers for ya.
Also try settings, accounts, backup and reset, factory data reset.

fast96 said:
I would think the tools section of Kies will have an option that will work. Connection trouble shoot first then emergency recovery. If your phone boots, you should be able to reset it to out of the box state.
If you go to settings, more, about device, build number, then tap on build number repeatedly it will restore developer options, if it's not shown now. From there you can enable or disable USB debugging. That might help with Odin. Wish I had more answers for ya.
Click to expand...
Click to collapse
Thank you for your answer. I will try it out now. Little more information is that I'm using the Pacman ROM.

joecereal said:
Thank you for your answer. I will try it out now. Little more information is that I'm using the Pacman ROM.
Click to expand...
Click to collapse
Do you know how to enter the download mode? If so then odin should recognize it. I think it's "hold the power button, down volume, and home button" till it instructs you to let got and hit the up volume button. The connect it to the pc for odin.

fast96 said:
Do you know how to enter the download mode? If so then odin should recognize it. I think it's "hold the power button, down volume, and home button" till it instructs you to let got and hit the up volume button. The connect it to the pc for odin.
Click to expand...
Click to collapse
Yes I'm trying the Odin process. It's working so far except it stops at "Get PIT for mapping..." which is here i.imgur.com/z8fnjRd (add png to the end)
Kies is not recognizing my device after troubleshoot. It is stuck at "Connecting..." which prevents me from emergency firmware recovery.
There are two options that will help me the most:
Connecting to Kies and getting a PIT file for Odin

joecereal said:
Yes I'm trying the Odin process. It's working so far except it stops at "Get PIT for mapping..." which is here i.imgur.com/z8fnjRd (add png to the end)
Kies is not recognizing my device. It is stuck at "Connecting..." which prevents me from emergency firmware recovery.
There are two options that will help me the most:
Connecting to Kies and getting a PIT file for Odin
Click to expand...
Click to collapse
Is your phone a US AT&T model I337? There is a stock recovery rom in this forum somewhere, it's a zip file when extracted it will have a tar.MD5 file for use with odin. Or maybe you should use the PDA selection in odin, and uncheck the reboot box.

fast96 said:
Is your phone a US AT&T model I377? There is a stock recovery rom in this forum somewhere, it's a zip file when extracted it will have a tar.MD5 file for use with odin. Or maybe you should use the PDA selection in odin, and uncheck the reboot box.
Click to expand...
Click to collapse
Did you see the imgur picture I posted? I have the tar file and did everything from instruction, but I only need the PIT file.

OK here it is , read the first three posts..... http://forum.xda-developers.com/showthread.php?p=42108461
:fingers-crossed:

fast96 said:
OK here it is , read the first three posts..... http://forum.xda-developers.com/showthread.php?p=42108461
:fingers-crossed:
Click to expand...
Click to collapse
I'm trying something with SuperSu. Thank you for your time.

Did you try going into super su and tried the full unroot option??
Sent from my SGH-I337M using xda premium

thatsupnow said:
Did you try going into super su and tried the full unroot option??
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
I'm going to do it right now. Will this ensure "full" unroot?

thatsupnow said:
Did you try going into super su and tried the full unroot option??
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
I'm following forum.xda-developers.com/showpost.php?p=33949289&postcount=51 this process but before I unroot I cannot access my recovery. If I unroot will I be able to?
I just don't want anymore problems

Why don't you just call cs and get credit for the difference instead of returning it. You're going to get another s4 anyways.

getbuzzin said:
Why don't you just call cs and get credit for the difference instead of returning it. You're going to get another s4 anyways.
Click to expand...
Click to collapse
Yeah I might do that now, but I want to fix everything first then start new.

Everyone I now know what I really want to do. I want to flash the stock ROM. But this is impossible with http://i.imgur.com/z8fnjRd.png "Get PIT for mapping" is stopping me, which is very frustrating.

Just throwing out some ideas. Try a different cable if you got another one. Try plugging into a usb port in back of computer. You could try to re download the file again using a different mirror. Could just be a bad download. Anyways good luck.

getbuzzin said:
Just throwing out some ideas. Try a different cable if you got another one. Try plugging into a usb port in back of computer. You could try to re download the file again using a different mirror. Could just be a bad download. Anyways good luck.
Click to expand...
Click to collapse
Okay, thank you

If it were me (which it's not) I would try kies for factory recovery .
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

getbuzzin said:
Just throwing out some ideas. Try a different cable if you got another one. Try plugging into a usb port in back of computer. You could try to re download the file again using a different mirror. Could just be a bad download. Anyways good luck.
Click to expand...
Click to collapse
Is there a faster file to download? One link says it will download for 4 hours

fast96 said:
If it were me (which it's not) I would try kies for factory recovery .
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
But Kies cannot connect to my device

What did I do wrong? I think I bricked my phone. So upset.

Traded my Mega for a S4 today
Love it
I rooted it, installed TWRP. I have i337m from Rogers. All was well.
I downloaded a Google Edition 4.3 Rom and went into TWRP, Wiped Cache/Dalvik/Data, and Formatted Data
I then went back, installed the Rom.zip
Wiped cache/dalvik
Rebooted.
My phone now goes directly to Odin Mood. Seems as if something partition wise happened.
UPDATE:
I attempted to flash via odin everything back to stock, it made it 1/2 way and got an error. Now I can't do anything, phone just boots to the screen attached. Odin doesnt detect phone, Kies doesn't detect phone.
Am I screwed? I can't believe this, I want to cry. Never have I had issues like this before!!!

Which TWRP version
Did you do the "Format Data" button where you had to select "Yes". If so you lost everything
Get twrp 2.5.0.2 if you get the chance
I never used Odin, so not much help there
Also, I always wipe only Data/System/Caches 2x and have no issues. I do it before flashing any rom/version update etc
I know not much help here. But, maybe an idea on what went wrong--
Good Luck

Yes - Shoot
I see the issue. I was following the guide and it states to do this with CWM, I was thinking I was reading the instructions for TWRP. I had 2.6.3.0 (whatever the newest one is)
I'm downloading the firmware now - will try Odin

You gotta use Odin to restore the firmware, but you can't use kies if you're going custom. You can also use Philz recovery for that. That's what I had and it worked great. It's based off CWM and has touch.

agent929 said:
You gotta use Odin to restore the firmware, but you can't use kies if you're going custom. You can also use Philz recovery for that. That's what I had and it worked great. It's based off CWM and has touch.
Click to expand...
Click to collapse
When attempting to flash with Odin, I'm getting the following error. Any help?
Stuck here right now if anyone has a second.

Edit
Sent from my SAMSUNG-SM-N900A using Tapatalk 5

Got it from here
http://forum.xda-developers.com/showthread.php?t=2269304
Its the Virgin Mobile Canada 4.2.2 firmware from July
My phone is Rogers but is unlocked and I'm using it with Virgin. Can I flash the virgin file rather than Rogers to avoid all the Rogers bloat?
What is the Pit error I'm getting? Did I delete a partition or anything here?
Man that stupid format is a major pain. Won't do that again. I flipped back at the guide page and read the CWM instructions by error.

agent929 said:
I don't think you're using the right firmware. You should be doing the MDL firmware.
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
Click to expand...
Click to collapse
Why would he put MDL on a Canadian phone?

scott14719 said:
Why would he put MDL on a Canadian phone?
Click to expand...
Click to collapse
Oh good gosh I'm very sorry I missed that part.
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4

agent929 said:
Oh good gosh I'm very sorry I missed that part.
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4
Click to expand...
Click to collapse
So I attempted to flash Via Odin 3.0.7 (rogers firmware) and about 1/2 way through something Error'd and now my phone will not do anything but load the following screen attached.
Download mode or recovery does not load. Kies does not detect it. I can't get Odin to detect it either.
Did I screw myself over?
So depressed over this. I just got the phone.

That screen is another form of download mode. If you plug it into Odin at this point will Odin recognize it?

jd1639 said:
That screen is another form of download mode. If you plug it into Odin at this point will Odin recognize it?
Click to expand...
Click to collapse
I'll try again tonight after work.
Last night I could no longer get ODIN to recognize the device.

bigystyle84 said:
I'll try again tonight after work.
Last night I could no longer get ODIN to recognize the device.
Click to expand...
Click to collapse
If you are on MF3, this has worked to get me out of that screen http://forum.xda-developers.com/showthread.php?t=2360859 there is always some risk with flashing anything from Odin, so read through the thread and make sure you are comfortable with it first...
I'm on AT&T U.S. but it worked for me. You should also be able to boot in download mode (with the phone off hold vol down and home, then press power until your phone vibrates and continue holding home and vol down until you see Download mode)...
I hope this helps.

dustyhughes said:
If you are on MF3, this has worked to get me out of that screen http://forum.xda-developers.com/showthread.php?t=2360859 there is always some risk with flashing anything from Odin, so read through the thread and make sure you are comfortable with it first...
I'm on AT&T U.S. but it worked for me. You should also be able to boot in download mode (with the phone off hold vol down and home, then press power until your phone vibrates and continue holding home and vol down until you see Download mode)...
I hope this helps.
Click to expand...
Click to collapse
I have a i337M Canadian phone
And as mentioned, phone will not go into Download mode. I've tried a dozen times to get it into the regular download mode as always, does not work. It just boots to this screenshot almost instantly after hitting the power button.
I've flashed with Odin a dozen times previously with S3 and Note 2 in the past, never any issues.
How could TWRP Format Data cause all this to happen?
I just had my previous phone stolen - I bought this phone yesterday and now this happens. What a great week.

jd1639 said:
That screen is another form of download mode. If you plug it into Odin at this point will Odin recognize it?
Click to expand...
Click to collapse
jd1639 is right, I think the first line of small text says Odin, if I remember correctly.

dustyhughes said:
jd1639 is right, I think the first line of small text says Odin, if I remember correctly.
Click to expand...
Click to collapse
I couldn't get Odin to detect the phone on this screen though.
Odin detected the phone fine when I could get the to regular download mode screen before. Now I can't get to this screen, only what's attached in the screenshot, and I couldn't get Odin to detect it any longer last night.
Can a cable cause this? I am not using the Cable that came with the phone - That wasn't included when I bought it. I'm using a Sony Cable from a Xperia T I used to own.
Why did the Odin flash fail to begin with?
With did Format Data in TWRP cause all this to happen?

bigystyle84 said:
I couldn't get Odin to detect the phone on this screen though.
Odin detected the phone fine when I could get the to regular download mode screen before. Now I can't get to this screen, only what's attached in the screenshot, and I couldn't get Odin to detect it any longer last night.
Can a cable cause this? I am not using the Cable that came with the phone - That wasn't included when I bought it. I'm using a Sony Cable from a Xperia T I used to own.
Why did the Odin flash fail to begin with?
With did Format Data in TWRP cause all this to happen?
Click to expand...
Click to collapse
It's very possible it's the cable. Odin is very finicky on the cable, usb ports, and even computer you use. It works great on my lap top but I can't get it to work on my pc. Do you know anyone who has an s4 and you could borrow their cable. If you can boot into download you are not bricked and can get Odin to fix your phone. It may just take some trial and error. I've also had Odin fail a number of times and then decide to finally work for whatever reason so keep working at it.

jd1639 said:
It's very possible it's the cable. Odin is very finicky on the cable, usb ports, and even computer you use. It works great on my lap top but I can't get it to work on my pc. Do you know anyone who has an s4 and you could borrow their cable. If you can boot into download you are not bricked and can get Odin to fix your phone. It may just take some trial and error. I've also had Odin fail a number of times and then decide to finally work for whatever reason so keep working at it.
Click to expand...
Click to collapse
I'm going to get a Samsung Cable from a friend today and try it again when I get home.

jd1639 said:
It's very possible it's the cable. Odin is very finicky on the cable, usb ports, and even computer you use. It works great on my lap top but I can't get it to work on my pc. Do you know anyone who has an s4 and you could borrow their cable. If you can boot into download you are not bricked and can get Odin to fix your phone. It may just take some trial and error. I've also had Odin fail a number of times and then decide to finally work for whatever reason so keep working at it.
Click to expand...
Click to collapse
Here's some more thoughts:
I've always used firmware from sammobile.com
I've had best luck with odin ver 1.85
One other, use the usb ports in the back of your computer, not the front and no usb hub.

jd1639 said:
Here's some more thoughts:
I've always used firmware from sammobile.com
I've had best luck with odin ver 1.85
Click to expand...
Click to collapse
Cool Thanks
I downloaded the firmware from SamMobile - the latest Rogers firmware.
I will try 1.85

need help guys at&t s4 brick. desperately

hi xda guys this is my story
i have an at&t samsung s4 on android 4.2 i have tried to update it via wifi to 4.4
but no use. a message appear say's " your device is up to date "
i have tied "loki way" it failed
i have tried "odin tool way' it failed it won't complete the process
i have tried samsung kais it fail's too a message says no update for this device
***** i managed to root the device
and then i found the safestrap apk i have insert the TWRP recovery
i have made a backup in case something go's wrong
and i have tries to flash a clean google s4 4.4.4 rom
**** and then the the phone stuck of samsung logo and vibrate often .the TWRP is lost
**** i have tried to recover the the via samsung kias it made it wors
now it have message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
i have tried via odin using the official firmware that i have downloaded. but did not work also
i have tried the kais recovery mode but i did not get the recovery code
help my friend what should i do
nead you help desperately

When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

jd1639 said:
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
Every time I have had and issue with a ROM or forget to flash loki I have no issues just ODIN back to 4.2.2 MDL. I say try it again.

MF3
jd1639 said:
When you try Odin what fails? Are you using the mdl firmware? I assume you're on MDL? You haven't updated the firmware?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon

myounis said:
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
Click to expand...
Click to collapse
YOU DONT FLASH .tar files in recovery ........... i9505 is not your device i337 is yours .. No wonder it bricked ...
this will unbrick your phone FOLLOW INSTRUCTIONS Exactly ... If you are on MF3 your bootloader is locked
http://forum.xda-developers.com/showthread.php?t=2663545
It in the second post ..Full Nb1 update .. Or Mk2 which ever you desire
GalaxyS4-CWM-6.0.4.4-GT-i9505.tar This is not a ROM its a recovery .. I suggest reading a lot more before proceeding .. Your device has a locked bootloader if firmware is MF3 ... Read the Q/A and much more it will save you a ton of time .. You need to flash device specific roms and recoveries else you are gonna crash and burn
If you are on MF3 like you said then you can only flash Safestrap compatible roms .. I need a little more info ???

myounis said:
yes my friend
the device firmware ends with MF3
i think it's MDL
it had a 4.2.2 official firmware
but i tried ti flash this rom using safestrap recovery : "GalaxyS4-CWM-6.0.4.4-GT-i9505.tar"
after that my device stuck in samsung logo screen with vibration
i hop hear from you soon
Click to expand...
Click to collapse
You are on mf3 firmware. Flashing the mdl firmware won't work. That's the problem you're having. I would recommend you upgrade and flash the nb1 tar file. Read this http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 5 using XDA Free mobile app

spirodave said:
YOU DONT FLASH .tar files in recovery ........... i9505 is not your device i337 is yours .. No wonder it bricked ...
this will unbrick your phone FOLLOW INSTRUCTIONS Exactly ... If you are on MF3 your bootloader is locked
http://forum.xda-developers.com/showthread.php?t=2663545
It in the second post ..Full Nb1 update .. Or Mk2 which ever you desire
GalaxyS4-CWM-6.0.4.4-GT-i9505.tar This is not a ROM its a recovery .. I suggest reading a lot more before proceeding .. Your device has a locked bootloader if firmware is MF3 ... Read the Q/A and much more it will save you a ton of time .. You need to flash device specific roms and recoveries else you are gonna crash and burn
If you are on MF3 like you said then you can only flash Safestrap compatible roms .. I need a little more info ???
Click to expand...
Click to collapse
yes my friend
sorry my misstake i have flashed this room : Danvdh-GE-4.4.4-07172014.zip

And it works--

rugmankc said:
And it works--
Click to expand...
Click to collapse
no my friend this rom made my device bootloop / brick
samsung logo only with vibration
***
i think onid is the answer
can any one link me an MF3 stock rom
to try??!!
i can't not find any

I think you missed something--
You can't run aosp roms at all
On MF3 only 4.3 afaik
As mentioned do a lot of reading in those threads before going on--saves headaches--:good:
Best would be to upgrade to NB1, those instructions are in those threads too--:good:

myounis said:
no my friend this rom made my device bootloop / brick
samsung logo only with vibration
***
i think onid is the answer
can any one link me an MF3 stock rom
to try??!!
i can't not find any
Click to expand...
Click to collapse
Im gonna save you a bunch of time ................You are on MF3 ...Your BootLoader is locked ... You can only flash Safe Strap Roms aka HyperDrive or GoldenEye based off stock .. You can only use safestrap to install recovery ... Anything else will render your device useless.
Check the General Section ... Send you a link isn't gonna help ... You need to read multiple threads ...CHECK THE GENERAL SECTION
LOCKED BOOTLOADER= NO AOSP ROMS = ONLY ROMS BASED OFF STOCK
LOOK FOR A THREAD IN THE GENERAL SECTION CALLED DEBRICK

thank for you help all
i have fix it
i have download this link :
https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
from
http://forum.xda-developers.com/showthread.php?t=2502003
and flash it with oden
what a relief
:highfive:

myounis said:
thank for you help all
i have fix it
i have download this link :
https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
from
http://forum.xda-developers.com/showthread.php?t=2502003
and flash it with oden
what a relief
:highfive:
Click to expand...
Click to collapse
:good::good::good:

Same issue but mk2 has me struggling
Sorry to hijack, but I didn't want to start a new thread on this same issue.
I have the AT&T S4 i337 , running MK2. I bought it used, and every time it boots up it shows "safestrap disabled" with 2 buttons below: recovery or system. Recovery button takes you to the TWRP recovery, the other button boots the phone. The phone worked well but the stock rom and bloat were killing me (my previous phones were rooted Epic and Relay). I wanted to root and flash a custom ROM but I wasn't aware of the locked bootloader and mk2/mf3 issues with this phone. Now I am soft bricked, and I've tried many ways to fix (odin, recovery flash,adb ), but it always fails. Here is my path, and what I've tried:
1. I rooted using Saferoot.
2. Tried to flash Philz Touch CWM from SD card in recovery (1st BIG mistake). Didn't work, but didn't brick either.
3. I saw guut13's index and ran backups on twrp recovery and on kies.
4. decided to update (before proceeding with a new rom). tried to OTA update, but it failed.
5. tried to install nb1 (stock odin tar) using heimdall (it couldn't find pit file) and odin (failed to complete write).
6. unrooted (hoping to fix update issues) and then tried Kies firmware upgrade. This process hung and I had to force quit. And thus began the soft brick.
This pattern repeated a few times:
7. flash stock mf3 tar with odin [Complete(Write) operation failed]
8. odin'd mk2 tar , then md1, then mf3 again, all fail to complete write.
9. Phone freezes and will only go into download mode (or bootloop).
10. the ONLY thing that odin can flash is a mj9 recovery file (sometimes). then recovery comes up, I wipe dalvik/cache/system (everything but the sd card) and fix permissions.
11. rinse and repeat. lol
12. I find a jflte pit file that will flash by odin.
13. I start trying stock tars again in odin, hoping the pit helps. same failure.
14. tried to odin an entire mf3 package (bootloader, modem, csc, the works). still same write fail.
15. the only file that flashes other than the pit, is a stock mk2 recovery file.
16. tried to slip a stock mk2 rom zip on my sd and flash from there... failed.
17. installed sdk and tried to sideload, but my computer won't recognize my S4. also can't run adb shell. (yes, i installed the platform tools, and opened prompt window from inside the platform tools folder). {perhaps my vmware fusion (Win8) running on my mac (OS 10.9) is causing a port id issue, but odin connects easily every time....hmm....}
18. Tried rubbing the phone against my head and laughing while trying not to cry, softly whispering "I hate your soul...."
19. Tried 5 different usb cables, including 2 blackberry cables that always connect other samsungs to odin.
20. tried factory reset thru stock recovery , which I can still reach by booting and holding volume up. odd note, this recovery says "i337ucufnb1".
So, I have tried odin-flashing every stock rom for i337 (mdl-nc1), but odin fails to write complete, and my phone says "bar 240, 400" or "sw rev check fail".
What can I try next? I can only think maybe to try using a different PC (not easy since I don't know anyone here but mac users) or smashing the phone under my tire..... would uninstalling safestrap help? I feel like theres a confilct between the stock nb1 recovery and safestrap..... but I can't get in the adb shell to delete it.
anyone had these write fails with odin before? I have always thought no matter what happens, I could always factory wipe and start over with a stock rom in odin, but now, the locksmith says no dice.
Thanks for any advice, I am sure I've forgotten a few details, but I hope I gave enough info for those who wish to assist. Thanks.

I would try to find a Windows pc and flash the nb1 tar in Odin
I'm assuming you're using this but if not it's what you want http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I would try to find a Windows pc and flash the nb1 tar in Odin
Click to expand...
Click to collapse
yeah, 4 years ago I had trouble getting virtual pc's to let my mac and epic both speak odin. But I thought now that they connect easily (and flash pits and some recovery with no prob) it was a better match (as in , vmware's Windows 8, running on a 2.8ghz macbook pro).
What stinks is I have a real pc (old tower running xp) for exactly this purpose, but I never got a licensed version of windows on it and the crap I got off torrents doesnt work anymore. I hate the thought of buying a crap PC OS that I will only use once every 3 years.

Epiclectic said:
yeah, 4 years ago I had trouble getting virtual pc's to let my mac and epic both speak odin. But I thought now that they connect easily (and flash pits and some recovery with no prob) it was a better match (as in , vmware's Windows 8, running on a 2.8ghz macbook pro).
What stinks is I have a real pc (old tower running xp) for exactly this purpose, but I never got a licensed version of windows on it and the crap I got off torrents doesnt work anymore. I hate the thought of buying a crap PC OS that I will only use once every 3 years.
Click to expand...
Click to collapse
Yea, my 16 year old has a crap Mac now all he ever uses is my crap Windows pc to play his games. Go figure.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Yea, my 16 year old has a crap Mac now all he ever uses is my crap Windows pc to play his games. Go figure.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
For a wide selection of games (and upgradable graphics), PC has a definite edge over Mac. PC also has the advantage of being cheaper to buy and upgrade. If I were going to game all day or outfit 50+ employee workstations, PC would be the obvious choice. But for day to day, I still like the way Mac works, hands down. (Tho as PC improves, and Mac continues dumbing down for the masses, this gap is starting to shrink, much like the import vs domestic car market.)
If my old PC tower could run Win8, I would just buy a licensed copy and use that for Odin. But I'm pretty sure it's maxed out at xp, tho it might run vista really slowly, lol. My other option is to try bootcamp to boot up my macbook as an actual Win8 PC, but if that doesnt solve the Odin issues, then I've spent money on a microsoft product I can't even use. I like android phones' customizing options and layout better than iphone (no back button? wtf? lol), so unless android starts making latop OS, I guess I'm stuck in this Mac/android limbo...

Epiclectic said:
Sorry to hijack, but I didn't want to start a new thread on this same issue.
I have the AT&T S4 i337 , running MK2. I bought it used, and every time it boots up it shows "safestrap disabled" with 2 buttons below: recovery or system. Recovery button takes you to the TWRP recovery, the other button boots the phone. The phone worked well but the stock rom and bloat were killing me (my previous phones were rooted Epic and Relay). I wanted to root and flash a custom ROM but I wasn't aware of the locked bootloader and mk2/mf3 issues with this phone. Now I am soft bricked, and I've tried many ways to fix (odin, recovery flash,adb ), but it always fails. Here is my path, and what I've tried:
1. I rooted using Saferoot.
2. Tried to flash Philz Touch CWM from SD card in recovery (1st BIG mistake). Didn't work, but didn't brick either.
3. I saw guut13's index and ran backups on twrp recovery and on kies.
4. decided to update (before proceeding with a new rom). tried to OTA update, but it failed.
5. tried to install nb1 (stock odin tar) using heimdall (it couldn't find pit file) and odin (failed to complete write).
6. unrooted (hoping to fix update issues) and then tried Kies firmware upgrade. This process hung and I had to force quit. And thus began the soft brick.
This pattern repeated a few times:
7. flash stock mf3 tar with odin [Complete(Write) operation failed]
8. odin'd mk2 tar , then md1, then mf3 again, all fail to complete write.
9. Phone freezes and will only go into download mode (or bootloop).
10. the ONLY thing that odin can flash is a mj9 recovery file (sometimes). then recovery comes up, I wipe dalvik/cache/system (everything but the sd card) and fix permissions.
11. rinse and repeat. lol
12. I find a jflte pit file that will flash by odin.
13. I start trying stock tars again in odin, hoping the pit helps. same failure.
14. tried to odin an entire mf3 package (bootloader, modem, csc, the works). still same write fail.
15. the only file that flashes other than the pit, is a stock mk2 recovery file.
16. tried to slip a stock mk2 rom zip on my sd and flash from there... failed.
17. installed sdk and tried to sideload, but my computer won't recognize my S4. also can't run adb shell. (yes, i installed the platform tools, and opened prompt window from inside the platform tools folder). {perhaps my vmware fusion (Win8) running on my mac (OS 10.9) is causing a port id issue, but odin connects easily every time....hmm....}
18. Tried rubbing the phone against my head and laughing while trying not to cry, softly whispering "I hate your soul...."
19. Tried 5 different usb cables, including 2 blackberry cables that always connect other samsungs to odin.
20. tried factory reset thru stock recovery , which I can still reach by booting and holding volume up. odd note, this recovery says "i337ucufnb1".
So, I have tried odin-flashing every stock rom for i337 (mdl-nc1), but odin fails to write complete, and my phone says "bar 240, 400" or "sw rev check fail".
What can I try next? I can only think maybe to try using a different PC (not easy since I don't know anyone here but mac users) or smashing the phone under my tire..... would uninstalling safestrap help? I feel like theres a confilct between the stock nb1 recovery and safestrap..... but I can't get in the adb shell to delete it.
anyone had these write fails with odin before? I have always thought no matter what happens, I could always factory wipe and start over with a stock rom in odin, but now, the locksmith says no dice.
Thanks for any advice, I am sure I've forgotten a few details, but I hope I gave enough info for those who wish to assist. Thanks.
Click to expand...
Click to collapse
my friend
if the mk2 is the same mf3
then download this link : https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE
more details here : http://forum.xda-developers.com/showthread.php?t=2502003
place the 4 files in to odin
and flash them... it worked for me
and if not the same as mf3
look for mk2 ota update build from 4 files
it will reset you phone to factory firmware
i hop it will work for you

Epiclectic said:
For a wide selection of games (and upgradable graphics), PC has a definite edge over Mac. PC also has the advantage of being cheaper to buy and upgrade. If I were going to game all day or outfit 50+ employee workstations, PC would be the obvious choice. But for day to day, I still like the way Mac works, hands down. (Tho as PC improves, and Mac continues dumbing down for the masses, this gap is starting to shrink, much like the import vs domestic car market.)
If my old PC tower could run Win8, I would just buy a licensed copy and use that for Odin. But I'm pretty sure it's maxed out at xp, tho it might run vista really slowly, lol. My other option is to try bootcamp to boot up my macbook as an actual Win8 PC, but if that doesnt solve the Odin issues, then I've spent money on a microsoft product I can't even use. I like android phones' customizing options and layout better than iphone (no back button? wtf? lol), so unless android starts making latop OS, I guess I'm stuck in this Mac/android limbo...
Click to expand...
Click to collapse
Consider installing Win7. Licenses can be had cheaply or just install, use for couple days for Odin (before it license locks) then wipe...
Sent from my SAMSUNG-SGH-I337 using Tapatalk

Possibly Bricked

Recently I wanted to unroot my Galaxy S4 ATT I337 and return back to Stock. It hasn't been my first time doing this, so I knew sort of what I was doing. I used Odin v3.10 and flashed an NB1 tar file and it worked fine, but as it finished flashing it said the device had been removed, showing up as a fail. So I disconnected the cable and tried again, and started getting error messages. I guess it might have had to do something with that, but now it keeps giving me a fail message every time I try to flash with Odin.
My phone now shows this firmware error on default and Odin seems to be failing every time. Is there anyway to fix this, or did I just completely screw this up?

I think you might have just screwed it up. If the device is removed in the middle of flashing with Odin that's not a good thing.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I think you might have just screwed it up. If the device is removed in the middle of flashing with Odin that's not a good thing.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well, I guess this is what I get for flashing so carelessly. I hope that this doesn't happen again.

Daze_ said:
Recently I wanted to unroot my Galaxy S4 ATT I337 and return back to Stock. It hasn't been my first time doing this, so I knew sort of what I was doing. I used Odin v3.10 and flashed an NB1 tar file and it worked fine, but as it finished flashing it said the device had been removed, showing up as a fail. So I disconnected the cable and tried again, and started getting error messages. I guess it might have had to do something with that, but now it keeps giving me a fail message every time I try to flash with Odin.
My phone now shows this firmware error on default and Odin seems to be failing every time. Is there anyway to fix this, or did I just completely screw this up?
Click to expand...
Click to collapse
Are you flashing the official odin?
Did you try the Kies emergency recovery?
Did you try a different cable and port?
I always recommend one directly connected to the motherboard.

BehrendsTech said:
Are you flashing the official odin?
Did you try the Kies emergency recovery?
Did you try a different cable and port?
I always recommend one directly connected to the motherboard.
Click to expand...
Click to collapse
I'm not too sure if I'm really flashing the official odin, but I've used it before and it's worked. I've tried the Kies emergency recovery but when I connected the cable to my phone it showed up as an unsupported device. I've tried two different cables but haven't changed the port.
Although after spending 4 hours searching the Internet for a fix, I actually found a website that showed me how to fix it. It worked well, and now I'm back to stock on my phone. The first few tries actually ended up as a fail, but for some reason the last attempt ended up with my phone actually turning on, and I was thankful to see the startup screen.

Daze_ said:
I'm not too sure if I'm really flashing the official odin, but I've used it before and it's worked. I've tried the Kies emergency recovery but when I connected the cable to my phone it showed up as an unsupported device. I've tried two different cables but haven't changed the port.
Although after spending 4 hours searching the Internet for a fix, I actually found a website that showed me how to fix it. It worked well, and now I'm back to stock on my phone. The first few tries actually ended up as a fail, but for some reason the last attempt ended up with my phone actually turning on, and I was thankful to see the startup screen.
Click to expand...
Click to collapse
Good to hear!