Database Users

[HELP]Soft bricked. Odin stuck on factoryfs.img e Cwm error

My Galaxy only enters in download mode, and when I try to flash a rom with odin, it stucks on factoryfs.img. Either rom with only 1 file or with 3 files and PIT file. It's able to flash kernel, but, when I try to flash a rom with CWM, an error occurs. I tryed to flash lpy, lc1, lc3 with odin and criskelo ics lpy and alba lpy

Hi, did you select the repartition box when using the pit file?
This happened because you didnt do the 4 wipes. You should flash a stock rom according to your actual base. I.e. if your actual kernel is lc1 then flash lc1.
Also, prior to this remove your battery for 5 minutes. Hope this helps. Please post your results.
Enviado desde mi Samsung Galaxy S2 ICS con AndyX ROM v9.0 usando Tapatalk 2

conanjf said:
My Galaxy only enters in download mode, and when I try to flash a rom with odin, it stucks on factoryfs.img. Either rom with only 1 file or with 3 files and PIT file. It's able to flash kernel, but, when I try to flash a rom with CWM, an error occurs. I tryed to flash lpy, lc1, lc3 with odin and criskelo ics lpy and alba lpy
Click to expand...
Click to collapse
What Rom were you on prior to attempting to flash with PC Odin?
Also, what did you do to cause the Note to be able to boot just into download mode?

Did you perform a wipe from any ICS leak or XXLPY prior to encountering this problem?
(read the sticky post at the top of this forum...)

I was using xxLPY official, but I didnt like it. And i dont remember what I did to brick the device haha... But I tried to flash with odin, all the ways possible, with pit file, only 1 file, 3 files, 3 files with pit. But what I really could flash, was the kernel only. And after flashing the kernel, i tried to flash with cwm, 2 differents roms

another person bricked their device while using Pc Odin. Non with Mobile Odin yet

I saw many posts from people who bricked the note, but now one could unbricked the phone =/

I bricked my note flashing a rom in recovery mode =/

try going back to stock gb..... check my sig...

antiguangenius said:
try going back to stock gb..... check my sig...
Click to expand...
Click to collapse
I tried to flash n differents stock gbs, no one successfully. I tried diferent ways to, 1 file or 3 files gb roms, with pit file or not, with repartition tick or dont...
But I think there is no way to fix that =/

conanjf said:
I tried to flash n differents stock gbs, no one successfully. I tried diferent ways to, 1 file or 3 files gb roms, with pit file or not, with repartition tick or dont...
But I think there is no way to fix that =/
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/showthread.php?p=23052721#post23052721
then flash gb again

I'll try now

<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Rooted_Stock_Odex_N7000XXLC1.tar.md5 is valid.
<OSM> MODEM_N7000XXLB2_REV_05_CL1106002.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OXALC1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.img
<ID:0/003> NAND Write Start!

stuck =/

superbrick. Head to samsung service and tell them that your phone died when you tried to do factory reset.

Yes, another Superbrick....
Service centre is your only option now mate, sorry.

conanjf said:
I tried to flash n differents stock gbs, no one successfully. I tried diferent ways to, 1 file or 3 files gb roms, with pit file or not, with repartition tick or dont...
But I think there is no way to fix that =/
Click to expand...
Click to collapse
ok try this. if u flash all 3 or 1 files and it didnt work, flash the pit file. only the pit file. tick re partition, auto reboot and reset f.time.
after that, reboot the phone and reboot windows/mac. enter download mode, and flash the 3 or 1 file rom that u have. let me know if it work.

Just bricked mine from criskelo super stable build. flashed cm9 nightly rebooted and no power at all. usb dont see it either. So off to repair store. Dont do what I did

So no, do es anyone think that lpy is safe? Because i remember Many people saying that it was totally safe because it was oficial and not a leak
Really samsungs engineers must look ti what they are doing, it shouldnt be too difficult ti revert to gb eMMC driver
Sent from my GT-N7000 using xda premium

Ashren81 said:
ok try this. if u flash all 3 or 1 files and it didnt work, flash the pit file. only the pit file. tick re partition, auto reboot and reset f.time.
after that, reboot the phone and reboot windows/mac. enter download mode, and flash the 3 or 1 file rom that u have. let me know if it work.
Click to expand...
Click to collapse
I did, stuck again on factoryfs.img =/

Bricked Device

I got a S4 today and I rooted it, and flashed CWM recovery, backed up the firmware, rebooted and everything was good. I updated the phone an hour so later and the boot hung on yellow Sprint screen. I rebooted into recovery and re-flashed my backup but that didn't fix the device. Now I've been trying to flash back to stock using Odin and this is what I see.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/004> Added!!
I was on 4.3 when this all started so I am attempting to flash the MK2 file back on my device. I removed the drivers, and re-installed and that made no difference. Any advice would be great.

Did you accept an OTA? Or did you try to flash a stock MK2 ROM?
I'd say flash an older tar if possible, especially if you plan to root again or install a custom ROM. The MK2 bootloader has KNOX enabled, so any root/custom ROM installs trip the counter.

sorry if this doesn't help, but have you tried different versions of odin? also tried different usb ports? idk what you're flashing or if this is what you want, but there's a stock mk2 rom on this thread if you wanna' try that. http://forum.xda-developers.com/showthread.php?t=2575470

I believe it updated via OTA after I activated it today. This was before I rooted. I am currently trying to flash the MK2 Rom. I've also tried MJA which is older. Is there an different older one that could work? I am planning on rooting again, but was going to run the stock rom for the time being. I've never an a touchwiz rom so I'm interested in trying it.
I have tried 3.09, 3.07, 1.85 for versions of Odin. All the same error.
I'm able to flash TWRP recovery from Odin without the error, but not the stock rom which is a bit confusing to me.

When you say
I updated the phone an hour so later
Click to expand...
Click to collapse
what did you 'update' it to and how? And even why?
Did you run Odin 'As administrator'?
What version of Odin are you using? 1.85 and 3.07 seem to work well.
Are you using a new USB cable? I've seen LOADS of issues with USB cables (ports too)
---------- Post added at 10:58 PM ---------- Previous post was at 10:57 PM ----------
Try and boot to stock recovery and do a factory reset.
Oh and also you are not BRICKED, you're just borked.

leaderbuilder said:
When you say what did you 'update' it to and how? And even why?
Did you run Odin 'As administrator'?
What version of Odin are you using? 1.85 and 3.07 seem to work well.
Are you using a new USB cable? I've seen LOADS of issues with USB cables (ports too)
---------- Post added at 10:58 PM ---------- Previous post was at 10:57 PM ----------
Try and boot to stock recovery and do a factory reset.
Oh and also you are not BRICKED, you're just borked.
Click to expand...
Click to collapse
I updated some apps and rebooted. Always find that this best after a lot of app updates.
Odin running as admin on Win 7 64. Mostly been using 3.07. USB cable is the new one that ship with the phone.
I've been looking for a stock recovery I can flash with Odin but can't seem to find one. Can you provide a link? Maybe I'm just missing it?

Are you flashing the full MK2 including boot? There's some thing where the phone refuses to boot into an MK2 ROM unless you've updated the bootloader as well.

I got the full rom from here: http://forum.xda-developers.com/showthread.php?t=2601443 I also tried flashing MJA too and I get the same message in Odin. I'm sure that I have the MK2 bootloader as it shows my knox being 0x1.

Since you are on MK2 already try using the 3.09 version of odin. It seems to work best with MK2. Also, if you have the MJA tar file try that one. Either MJA or MK2 should flash on your phone.

cruise350 said:
Since you are on MK2 already try using the 3.09 version of odin. It seems to work best with MK2. Also, if you have the MJA tar file try that one. Either MJA or MK2 should flash on your phone.
Click to expand...
Click to collapse
I re-downloaded Odin 3.09, USB drivers (using 1,5,29), the rom and attempted to flash again and get the same error in Odin. Same result with MJA too.

benpfeil said:
I re-downloaded Odin 3.09, USB drivers (using 1,5,29), the rom and attempted to flash again and get the same error in Odin. Same result with MJA too.
Click to expand...
Click to collapse
Hmm, you're doing or missing something because in the last week or so there have been about five or ten people with close to the same issue (HELP, I'M BRICKED, MY LIFE IS OVER...etc.) and we've mangaged to get them all work. I've posted dozens of replies to those people and they've been able to get up and running following others and my advice(s).
Spend some time and go through the first few pages of the Q&A, Help forum and read all the way through some of the similar posts. Then try what is suggested in them.
You will resolve your issue. IF you don't, just warranty your phone or grab an iPhone.

I broke down and stopped into Sprint tonight. I had tried the process on 3 different PC's and still no luck. They tried to flash it and weren't able to as well. The woman in the store told me they could not exchange it because they do not have the phone yet. I was confused by this. The phone that I have has "Sprint Spark" on it which is a tri-band phone and the stores do not have it yet. My company has a large plan with Sprint and we get our phones shipped directly to us. She said I would have to have my procurement person request a new phone for me. My model is actually SPH-L720T. My guess is that this was causing my issues.
Thank you to you all who tried to help out.

My model is actually SPH-L720T. My guess is that this was causing my issues.
Click to expand...
Click to collapse
YEP!
That would be the problem.

leaderbuilder said:
YEP!
That would be the problem.
Click to expand...
Click to collapse
Just wasn't making any sense to me up until then. I've done numerous phones and never had any issue before so I was just baffled.
Trying to find a MK5 rom that will download. Working on one now that is pulling in at < 200 KB/s.

benpfeil said:
Just wasn't making any sense to me up until then. I've done numerous phones and never had any issue before so I was just baffled.
Trying to find a MK5 rom that will download. Working on one now that is pulling in at < 200 KB/s.
Click to expand...
Click to collapse
I didn't think XDA had a forum up yet for SPH-L720T.

Sammobile.com has the mk5 tar file for the 720T.
Sent from my icrap 2 using Tapatalk HD

[Q] ADB or Terminal Emulator Help Needed

Hello,
I am trying to update the recovery on my wife's S4.
I'm following these instructions, but I can't seem to get it to work in either Terminal Emulator or ADB. Any instructions will be much appreciated.
Originally Posted by stevey500 View Post
I am on locked-bootloader MF3.
I have had a broken/non-bootable recovery menu since I started tinkering with modifying MF3 bootloader.
I followed this guide and did it all within my stock rooted touchwiz rom using terminal emulator and it worked perfectly. I didn't even have to run the last .sh, just simply dd'd the stock recovery.img image to its appropriate location.
So, bootable people with MF3 bootloader and broken recovery menus... do this:
http://d-h.st/AuY put this image file on your internal storage.
Run this command in ADB (type adb shell to get to shell) or go to terminal emulator and enter this:
su -c "dd if=/storage/sdcard0/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
You should have a fully working stock recovery menu now.
Click to expand...
Click to collapse

tarikakleh said:
Hello,
I am trying to update the recovery on my wife's S4.
I'm following these instructions, but I can't seem to get it to work in either Terminal Emulator or ADB. Any instructions will be much appreciated.
Click to expand...
Click to collapse
What boatloader/baseband are you on. Also what version of android. Depending on what you're on this may not apply to you.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

When you say update, do you mean flash the stock recovery or a custom one? Because this method is only to restore the stock recovery. You can't get a custom one.
Sent from my SGH-I337 running GPE

drock212 said:
What boatloader/baseband are you on. Also what version of android. Depending on what you're on this may not apply to you.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Don't have the phone with me right now, but I know it is 4.2.2 MF3.

DeadlySin9 said:
When you say update, do you mean flash the stock recovery or a custom one? Because this method is only to restore the stock recovery. You can't get a custom one.
Sent from my SGH-I337 running GPE
Click to expand...
Click to collapse
Stock recovery. I am trying to update without losing data. I was advised to unroot, then update OTA but update wasn't working, no response when checking for update.. Problem is at one point I tried to flash TWRP through Goo and I broke stock recovery, which I need now to update.

tarikakleh said:
Stock recovery. I am trying to update without losing data. I was advised to unroot, then update OTA but update wasn't working, no response when checking for update.. Problem is at one point I tried to flash TWRP through Goo and I broke stock recovery, which I need now to update.
Click to expand...
Click to collapse
There's somewhere around here where someone posted just the recovery partition of the odin tar file. That can be flashed through odin and you'll regain your recovery. The reason ota doesn't work is because it needs recovery to install... Google search how to recover stock recovery for nb1 or whatever bootloader you're on and an XDA thread should come up
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

drock212 said:
There's somewhere around here where someone posted just the recovery partition of the odin tar file. That can be flashed through odin and you'll regain your recovery. The reason ota doesn't work is because it needs recovery to install... Google search how to recover stock recovery for nb1 or whatever bootloader you're on and an XDA thread should come up
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, I did do a search, and the original post of this thread had the instructions. The problem is, I'm not sure I'm using the proper syntax in either ADB or Terminal Emulator. Kind of needed a walk-through or a bit more details on the instructions.
What I've done:
1) Downloaded the file via above link.
2) Placed it into internal storage of my phone under "sdcard0"
3) Ran the following string in Terminal Emulator exactly as written:
su -c "dd if=/storage/sdcard0/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
Click to expand...
Click to collapse
At this point it says it cannot find the file. I am not certain that this is the problem, but the file is named "mf3-recovery.tar.md5", whereas, in the string above it's named "recovery.img". Am I supposed to extract it some way, or rename it?
When it comes to this stuff, due to my limited knowledge, I try not to improvise. If it is not in the guide, I don't do it.

tarikakleh said:
Thanks, I did do a search, and the original post of this thread had the instructions. The problem is, I'm not sure I'm using the proper syntax in either ADB or Terminal Emulator. Kind of needed a walk-through or a bit more details on the instructions.
What I've done:
1) Downloaded the file via above link.
2) Placed it into internal storage of my phone under "sdcard0"
3) Ran the following string in Terminal Emulator exactly as written:
At this point it says it cannot find the file. I am not certain that this is the problem, but the file is named "mf3-recovery.tar.md5", whereas, in the string above it's named "recovery.img". Am I supposed to extract it some way, or rename it?
When it comes to this stuff, due to my limited knowledge, I try not to improvise. If it is not in the guide, I don't do it.
Click to expand...
Click to collapse
Ok cool you found the tar file... This can be flashed through odin actually and it will restore your recovery without touching anything else or you can extract the tar file on your desk top, this will give you the img file then that can be placed into internal storage just like in the instructions. Before placing there though just rename the img file to recovery or just leave it as is and remember it. The string would be as follows
Su -c dd if=/storage/sdcard0/whatever you named the duke. of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Give that a try again since its a tar file it can be flashed through odin
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

tarikakleh said:
Thanks, I did do a search, and the original post of this thread had the instructions. The problem is, I'm not sure I'm using the proper syntax in either ADB or Terminal Emulator. Kind of needed a walk-through or a bit more details on the instructions.
What I've done:
1) Downloaded the file via above link.
2) Placed it into internal storage of my phone under "sdcard0"
3) Ran the following string in Terminal Emulator exactly as written:
At this point it says it cannot find the file. I am not certain that this is the problem, but the file is named "mf3-recovery.tar.md5", whereas, in the string above it's named "recovery.img". Am I supposed to extract it some way, or rename it?
When it comes to this stuff, due to my limited knowledge, I try not to improvise. If it is not in the guide, I don't do it.
Click to expand...
Click to collapse
The .tar.md5 file looks like it's an Odin flashable file. To use the dd command you need the .img file. recovery.img I'd probably in the.tar.md5 file but I'm not familiar with it. Do you have a link to the mf3 tar file?
Sent from my Nexus 5 using XDA Free mobile app

drock212 said:
Ok cool you found the tar file... This can be flashed through odin actually and it will restore your recovery without touching anything else or you can extract the tar file on your desk top, this will give you the img file then that can be placed into internal storage just like in the instructions. Before placing there though just rename the img file to recovery or just leave it as is and remember it. The string would be as follows
Su -c dd if=/storage/sdcard0/whatever you named the duke. of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Give that a try again since its a tar file it can be flashed through odin
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Awesome thanks! I'll let know what happens. Need to get my hands on wife's phone first.

jd1639 said:
The .tar.md5 file looks like it's an Odin flashable file. To use the dd command you need the .img file. recovery.img I'd probably in the.tar.md5 file but I'm not familiar with it. Do you have a link to the mf3 tar file?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Here is the link. http://d-h.st/AuY

drock212 said:
...or you can extract the tar file on your desk top, this will give you the img file then that can be placed into internal storage just like in the instructions...
Click to expand...
Click to collapse
Seems like I need my hand held with every step of this process!
To extract the img from the tar, I did the following:
1) extracted with 7-zip
2) left me with a "recovery.bin"
3) dropped that file into sgs2oext4
4) in diskinternals linux reader, I select "mount image"
For step 4, I don't get a mount.
I think the problem is with step 3, the recovery.ext4.img file is 0KB, I've left it running on sgs20ext4 for at least 30 minutes and nothing changed.
How am I screwing up?

tarikakleh said:
Seems like I need my hand held with every step of this process!
To extract the img from the tar, I did the following:
1) extracted with 7-zip
2) left me with a "recovery.bin"
3) dropped that file into sgs2oext4
4) in diskinternals linux reader, I select "mount image"
For step 4, I don't get a mount.
I think the problem is with step 3, the recovery.ext4.img file is 0KB, I've left it running on sgs20ext4 for at least 30 minutes and nothing changed.
How am I screwing up?
Click to expand...
Click to collapse
You might only be able to use odin to flash since its a tar file already
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

drock212 said:
You might only be able to use odin to flash since its a tar file already
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Will this preserve the data/settings on the phone?

tarikakleh said:
Will this preserve the data/settings on the phone?
Click to expand...
Click to collapse
I read on another forum where the same tying happened to another guy and he flashed just the bootloader through odin and it did not touch any of the other partitions (data/settings) but since I have not done this myself I can not guarantee it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

If you flash recovery in Odin it will not wipe your device
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
If you flash recovery in Odin it will not wipe your device
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Tried flashing using ODIN 1.85 and I get FAIL!. "Auto Reboot" and "F. Reset Time" are checked.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> mf3-recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

tarikakleh said:
Tried flashing using ODIN 1.85 and I get FAIL!. "Auto Reboot" and "F. Reset Time" are checked.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> mf3-recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try a different usb port and cable. Odin can be finicky
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Try a different usb port and cable. Odin can be finicky
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Tried it using multiple ports, 2 cables (1 original), and two computers. Same results...

tarikakleh said:
Tried it using multiple ports, 2 cables (1 original), and two computers. Same results...
Click to expand...
Click to collapse
Try odin 3.09 could just be the version of odin being weird
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
---------- Post added at 10:13 PM ---------- Previous post was at 10:03 PM ----------
Ok dumb question but I have to ask... You put the phone in download mode (power off... Then power on holding volume down home key and power) then plugged it in while odin was up? If so then try this
http://forum.xda-developers.com/showthread.php?p=46775016
Stock recovery img file for mf3 and adb instruction on how to install
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
---------- Post added at 10:22 PM ---------- Previous post was at 10:13 PM ----------
tarikakleh said:
Tried it using multiple ports, 2 cables (1 original), and two computers. Same results...
Click to expand...
Click to collapse
Found it!!!!! Ok using odin 1.85 you can flash each part of the firmware separately. Put phone in download node plug into pc while running odin and flash just the recovery but put it in the recovery slot of odin
http://forum.xda-developers.com/showthread.php?p=46943588
This helped me when I did the same thing as you while on mf3
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Bootlooped

I'm not exactly green her, but i tried to run wicked v4 rom using safestrap to install. I am soft bricked, am able to acces recovery, download mode. I'v searched and downloaded, redownloaded, and downloaded again a list of packets that, when used with din will allow me to down grade to mk2 i believe so that i can access my device and start the process over again. I can not for the life of mrick my deice that has been down 2 dayse find the right mirror that will allow me to unbrick my device that has been down 2 days. help please, and it is appreciated.
p.s
i can not access the SS home screen and i do have a nandroid back up. thanks in advance

half way there
got beyond that point.. now odin keeps failing during the flashing process.
<OSM> Please wait..
<OSM> I337MK2_Full_Odin_Tar.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

What firmware version where you on? You may not be able to flash mk2
Sent from my Nexus 5 using XDA Free mobile app

frmware
jd1639 said:
What firmware version where you on? You may not be able to flash mk2
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
i was on i337nc1 firmware......
i had tried to flash wicked rom, and it is sayng that i need to connect to kies to reinstall custom firmware but kies is not registering the phone at present

zavien said:
i was on i337nc1 firmware......
i had tried to flash wicked rom, and it is sayng that i need to connect to kies to reinstall custom firmware but kies is not registering the phone at present
Click to expand...
Click to collapse
Alright, some of this will help http://forum.xda-developers.com/showthread.php?p=55338138
Download the nb1 tar file. Flash that in Odin
Sent from my Nexus 5 using XDA Free mobile app

thanks
jd1639 said:
Alright, some of this will help http://forum.xda-developers.com/showthread.php?p=55338138
Download the nb1 tar file. Flash that in Odin
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
downloading it now!!! much appreciated in advance

[Q] Need help real bad

By mistake i deleted my secsettings apk know i cant acces my settings so i did a foactory reset trying to fix it and lost my root icant install nothing i tried flashing back to stock with odin but fails my phone is att galaxy s4 on 4.2.2 if i reamember right cant look a the settings
this is the fail when i try the stock 4.2
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
im in the proses of downloading 4.4 as shown in the reply below

Do you remember if your where on mdl or mf3 4.2.2? Or could you use cwm or twrp or did you need safestrap?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Do you remember if your where on mdl or mf3 4.2.2? Or could you use cwm or twrp or did you need safestrap?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No to the first ? I dont have cwm or twrp on my phone and dont know what safestrap is im a nood thanks for youre interest in helpping me hope i could get my phone working

Psantana said:
No to the first ? I dont have cwm or twrp on my phone and dont know what safestrap is im a nood thanks for youre interest in helpping me hope i could get my phone working
Click to expand...
Click to collapse
Since you're not using any custom roms I'd flash this in Odin http://forum.xda-developers.com/showthread.php?p=50912149. This will also update you to 4.4.2.
I'm guessing Odin failed before because you were using an older firmware version than your device is on.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Since you're not using any custom roms I'd flash this in Odin http://forum.xda-developers.com/showthread.php?p=50912149. This will also update you to 4.4.2.
I'm guessing Odin failed before because you were using an older firmware version than your device is on.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I will try that and see what happens thanks

jd1639 said:
Since you're not using any custom roms I'd flash this in Odin http://forum.xda-developers.com/showthread.php?p=50912149. This will also update you to 4.4.2.
I'm guessing Odin failed before because you were using an older firmware version than your device is on.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
now the one thing i cant do is access the settings so no usbdebugging will it still flash

Psantana said:
now the one thing i cant do is access the settings so no usbdebugging will it still flash
Click to expand...
Click to collapse
Yes, you don't need usb debugging enabled for Odin
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Yes, you don't need usb debugging enabled for Odin
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
you are a android god it worked thank you very much

Psantana said:
you are a android god it worked thank you very much
Click to expand...
Click to collapse
no problem, flash you're back up and running
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
no problem, flash you're back up and running
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
know time to learn how to flash twrp so i can back it up

Psantana said:
know time to learn how to flash twrp so i can back it up
Click to expand...
Click to collapse
You're not going to be able to flash twrp. You can only use safestrap as a custom recovery.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You're not going to be able to flash twrp. You can only use safestrap as a custom recovery.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
ok ill look into that