Database Users

[Q] BRICKED [SGH-I337M] USING - CF-Auto-Root [CANADIAN MODELS ONLY]

So I followed this thread exactly, for my rogers I337M
[SGH-I337M] CF-Auto-Root [CANADIAN MODELS ONLY]
http://forum.xda-developers.com/showthread.php?t=2293800&highlight=cf+auto+root
and after I started ODIN after selecting the .tar.md5
I got this.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jfltecan-jfltevl-sghi337m.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
And in it says fail on ODIN. And now when I boot up I can't get to my stock OS
only to a screen where it says, "Firmware upgrade encountered an issue. Please Select recovery mode in Kies & try again."
I Can't use my S4 any more . I was wondering if it was because I had a locked bootloader, but the I337M varient should be unlocked right?
I also had the new MG1 firmware before I tried all this, but I saw alot of other MG1 users used this method.
PLEASE HELP, I would be forever grateful.

Are you sure you used the correct version for your model and are you sure you didn't have "repartition" checked in ODIN?

scott14719 said:
Are you sure you used the correct version for your model and are you sure you didn't have "repartition" checked in ODIN?
Click to expand...
Click to collapse
Completely sure.

Can you boot into download mode? If so I would Odin stock firmware and see if that helps. I have used the auto root on a couple different devices and have had no issues.
Sent from my Nexus 10

mymusicathome said:
Can you boot into download mode? If so I would Odin stock firmware and see if that helps. I have used the auto root on a couple different devices and have had no issues.
Sent from my Nexus 10
Click to expand...
Click to collapse
ok so I got the latest firmware for my device.
Build Date: 01.07.2013 -> Region: RWC (Canada (Rogers)) PDA: I337MVLUAMG1 Changelist: 897376 Android: 4.2.2
I got it from this thread
http://forum.xda-developers.com/showthread.php?t=2269304&highlight=flash+stock+firmware
I got back into the download mode (VOLDOWN/HOME/PWR) with the android icon where it says. "Downloading... Do not turn off target!!" plugged in my device got into odin put the stock firmware in PDA and ran then got this.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUAMG1_I337MOYAAMG1_I337MVLUAMG1_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> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
and my device still doesn't work.

Try it a few more times. I've used odin where I got "failed" and then after a few tries got it to work.

jd1639 said:
Try it a few more times. I've used odin where I got "failed" and then after a few tries got it to work.
Click to expand...
Click to collapse
I've tried it 10 times so far with different versions of ODIN just to be sure.. No change. Would me having a USB 1.0 have anything to do with it?

I really have no idea what to do.. I have 1 year warranty left with this phone, and me trying to CF-Auto root was the only thing I've done that could have voided my warranty, but it failed and now that I'm stuck would I still be okay if I took it in for warranty?

PromyD said:
I've tried it 10 times so far with different versions of ODIN just to be sure.. No change. Would me having a USB 1.0 have anything to do with it?
Click to expand...
Click to collapse
Try it on a different computer.

jd1639 said:
Try it on a different computer.
Click to expand...
Click to collapse
agreed. or at least a different usb port. are you using the cable that came with your device? i'm assuming you had usb debugging switched on.

So i've tried it on another computer, but since my device is in download mode it doesn't install any samsung drivers to properly identify and read the S4, so it doesn't work. Can anyone please give me some direct links to download the proper usb drivers on windows for my S4.

http://lmgtfy.com/?q=samsung+galaxy+s4+drivers

Thanks to everyone that helped me troubleshoot and gave me options in figuring out the next step. I used another computer and installed the drivers on to that computer ran odin and cf auto root method and it worked like a charm. :victory:
On the first computer I used, I'm almost completely sure I had the wrong S4 Drivers installed and thats why it didn't work.
Thanks to: scott14719, mymusicathome, jd1639, xBeerdroiDx

Lo
PromyD said:
Thanks to everyone that helped me troubleshoot and gave me options in figuring out the next step. I used another computer and installed the drivers on to that computer ran odin and cf auto root method and it worked like a charm. :victory:
On the first computer I used, I'm almost completely sure I had the wrong S4 Drivers installed and thats why it didn't work.
Thanks to: scott14719, mymusicathome, jd1639, xBeerdroiDx
Click to expand...
Click to collapse
You're welcome. Glad to have helped. It's good you got your phone working again.
Ps, nvm

SGH I337M Bricked as well
I tried to odin to stock firmware after installing wicked rom v7 and KT-SGS4 kernel. the reason I wanted to odin to stock was because wicked rom kept disconnecting my wifi so I gave up. so after flashing it failed (of course) and I couldnt boot into android: "firmware update has encountered an issue..."
here is what odin said after failure:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
This happens all the time for me when reodining to stock, but for some reason, THIS time, it didn't. tried 11 times and got pissed off.
someone PLEASE PLEASE HELP ME!!

Copy a rooted i337M rom to your SD card. Boot into recovery , wipe and flash.
Sent from my SGH-I337M using XDA Premium 4 mobile app

I cannot boot into recovery.

Hey Overclock,
Can you confirm whether your knox flag tripped? and what build are you on? I just want to make sure the knox doesnt trip when rooting

OverclockDaS4 said:
I tried to odin to stock firmware after installing wicked rom v7 and KT-SGS4 kernel. the reason I wanted to odin to stock was because wicked rom kept disconnecting my wifi so I gave up. so after flashing it failed (of course) and I couldnt boot into android: "firmware update has encountered an issue..."
here is what odin said after failure:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
This happens all the time for me when reodining to stock, but for some reason, THIS time, it didn't. tried 11 times and got pissed off.
someone PLEASE PLEASE HELP ME!!
Click to expand...
Click to collapse
Take a deep breath, and try another cable. I find a large portion of flash errors are caused by junky usb cables. If that fails, try another usb port and another pc entirely, if possible. Let us know some more info, someone has already asked, more details the better. Good luck.
Sent from my SGH-I337M

pyrexid said:
Hey Overclock,
Can you confirm whether your knox flag tripped? and what build are you on? I just want to make sure the knox doesnt trip when rooting
Click to expand...
Click to collapse
Knox does trip if you root.... not sure there is any method that doesn't...... guess if its important... do some research.. I couldn't find one when I did mine... used CF-auto..... on i337m

[Q] Boot error

Hi guys,
Please help !
I have a I9505. My phone is stuck in boot with message "Firmware upgrade encountered an issue. Please select recovery mode in Kies ".
When I try Kies emergency recovery noting happens.
I tried to boot in custom recovery (I had TWRP) and no luck.
Download mod is working. I tried to install sock rom with odin (PDA - one tar.md5 file), but it fail.

chemarko said:
Hi guys,
Please help !
I have a I9505. My phone is stuck in boot with message "Firmware upgrade encountered an issue. Please select recovery mode in Kies ".
When I try Kies emergency recovery noting happens.
I tried to boot in custom recovery (I had TWRP) and no luck.
Download mod is working. I tried to install sock rom with odin (PDA - one tar.md5 file), but it fail.
Click to expand...
Click to collapse
If u hv nandroid backup. Try restoring it. It will return u to last stable condition of your phone

re: flash stock firmware
chemarko said:
Hi guys,
Please help !
I have a I9505. My phone is stuck in boot with message "Firmware upgrade encountered an issue. Please select recovery mode in Kies ".
When I try Kies emergency recovery noting happens.
I tried to boot in custom recovery (I had TWRP) and no luck.
Download mod is working. I tried to install sock rom with odin (PDA - one tar.md5 file), but it fail.
Click to expand...
Click to collapse
Most likely you tried to flash the wrong firmware/rom for your phone and that's why it failed.
Your best bet is to download the official stock firmware from http://SamMobile.com
and Odin flash it. Make 100% sure that the firmware you download is the right one
for your specific phone's model.
Good luck!

Tried everything
Misterjunky said:
Most likely you tried to flash the wrong firmware/rom for your phone and that's why it failed.
Your best bet is to download the official stock firmware from http://SamMobile.com
and Odin flash it. Make 100% sure that the firmware you download is the right one
for your specific phone's model.
Good luck!
Click to expand...
Click to collapse
I already tried to install sock rom (tar.md5) from SamMobile, but Odin starts and fail.

chemarko said:
I already tried to install sock rom (tar.md5) from SamMobile, but Odin starts and fail.
Click to expand...
Click to collapse
C`mon guys HELP PLEASE

[HELP] Please
chemarko said:
C`mon guys HELP PLEASE
Click to expand...
Click to collapse
Me again.
When I start ODIN with stock rom with PDA, this is message
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMKF_I9505TMTEMJ4_I9505XXUEMKF_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> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When add re-partition
> Added!!
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Can't open the specified file. (Line: 1992)
<OSM> All threads completed. (succeed 0 / failed 1)

chemarko said:
Me again.
When I start ODIN with stock rom with PDA, this is message
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMKF_I9505TMTEMJ4_I9505XXUEMKF_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> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When add re-partition
> Added!!
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Can't open the specified file. (Line: 1992)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What version of Android u had before flash and what are u trying to flash??
Maybe u can't flash because u had 4.3(KNOX) and u are trying to flash a 4.2 that is possible?
Ops sorry, Its older or newest this version of Android 4.3 that u had?

DefyUser89 said:
What version of Android u had before flash and what are u trying to flash??
Maybe u can't flash because u had 4.3(KNOX) and u are trying to flash a 4.2 that is possible?
Ops sorry, Its older or newest this version of Android 4.3 that u had?
Click to expand...
Click to collapse
I installed few days ago 4.4.2, and CP_I9505XXUFNA5 and BL_I9505XXUFNA5. It has to much bugs so I decided to go back.
I tried to install stock rom from SamMobile with PDA in Odin and got this error.
I flashed just now TWR and GSM_Modem_XXUEMFK_and_LTE_Modem_XXUMFK and some custom rom 4.3 (google edition).
It installed but system keep crashing. I tried couple of roms and same situation. It is crushing all the time.
Could it be problem with bootloader

chemarko said:
I installed few days ago 4.4.2, and CP_I9505XXUFNA5 and BL_I9505XXUFNA5. It has to much bugs so I decided to go back.
I tried to install stock rom from SamMobile with PDA in Odin and got this error.
I flashed just now TWR and GSM_Modem_XXUEMFK_and_LTE_Modem_XXUMFK and some custom rom 4.3 (google edition).
It installed but system keep crashing. I tried couple of roms and same situation. It is crushing all the time.
Could it be problem with bootloader
Click to expand...
Click to collapse
You can no longer downgrade to stock 4.3 mate,thats why your getting this error.. flash the 4.4.2 leak and that should fix your problem.
Sent from Hell ?

chemarko said:
I installed few days ago 4.4.2, and CP_I9505XXUFNA5 and BL_I9505XXUFNA5. It has to much bugs so I decided to go back.
I tried to install stock rom from SamMobile with PDA in Odin and got this error.
I flashed just now TWR and GSM_Modem_XXUEMFK_and_LTE_Modem_XXUMFK and some custom rom 4.3 (google edition).
It installed but system keep crashing. I tried couple of roms and same situation. It is crushing all the time.
Could it be problem with bootloader
Click to expand...
Click to collapse
Repulsa said:
You can no longer downgrade to stock 4.3 mate,thats why your getting this error.. flash the 4.4.2 leak and that should fix your problem.
Sent from Hell ?
Click to expand...
Click to collapse
Oh yes! I forget, I installed FNA1 not FNA5 and i could come back to 4.3 because FNA1 dont have new bootloader... I rode that FNA5 have new bootloader and u can go back to 4.3.
The best choice is how said @Repulsa , U must install FNA5 and after install Philz-touch, CWM or TWR and install any 4.4.2
I hope that we helped to you! :good:
Regards,

Want to root on 4.2.2 MDL

A long time ago I sent my phone in for repairs (screen). I factory reset it and lost root. I don't even remember how I rooted it, it was an automated tool. After it came back from repairs, it still had 4.2.2 and MDL (it was a repair shop not Samsung).
Whenever I reset/turn phone off and back on, I get an error about com.android something, but only then, it works normally after. Due to this error, my phone tries to upgrade but fails (thankfully). I want to root my phone but I'm afraid it will fail because of that error. What exactly should I do next? I asked in another thread and I was told Motochopper was the best tool to root on 4.2.2. I just want to get rid of this error then root, that's it, what should I do next?

Moto chopper should work. I'm guessing towelroot would too. https://towelroot.com
Sent from my Nexus 5 using XDA Free mobile app

But do you think I can just use it the way my phone is now? Someone told me to do a Factory Reset with Odin, but I have no idea how to do that. All the tutorials I find mention downloading something (apart from Odin itself), why would I need to do that if I'm just resetting?
This is the error I get "com.android.phone has stopped working".
I think I've already tried factory resetting with the physical buttons method and I still keep getting that.

SRCP said:
But do you think I can just use it the way my phone is now? Someone told me to do a Factory Reset with Odin, but I have no idea how to do that. All the tutorials I find mention downloading something (apart from Odin itself), why would I need to do that if I'm just resetting?
This is the error I get "com.android.phone has stopped working".
I think I've already tried factory resetting with the physical buttons method and I still keep getting that.
Click to expand...
Click to collapse
Odin flashes the factory firmware, it does a lot more than a factory reset. You need to download the mdl firmware and flash that in Odin. You can get it at sammobile.com. It's a zip file, you need to extract it using 7-zip or win rar. After it's extracted you end up with a .tar.md5 file. That's what you use in Odin.
If you do flash it, the phone will want to update via the ota. You should make sure it doesn't do that by rooting it and freezing out deleting the update apps. There are three files and I don't remember their names
Edit, read this http://forum.xda-developers.com/showthread.php?p=42320391
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Odin flashes the factory firmware, it does a lot more than a factory reset. You need to download the mdl firmware and flash that in Odin. You can get it at sammobile.com. It's a zip file, you need to extract it using 7-zip or win rar. After it's extracted you end up with a .tar.md5 file. That's what you use in Odin.
If you do flash it, the phone will want to update via the ota. You should make sure it doesn't do that by rooting it and freezing out deleting the update apps. There are three files and I don't remember their names
Edit, read this http://forum.xda-developers.com/showthread.php?p=42320391
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you. Last question. Do you think I should flash first or try to root right away?

SRCP said:
Thank you. Last question. Do you think I should flash first or try to root right away?
Click to expand...
Click to collapse
Rooting isn't going to do you any good at this point. Flash first
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Rooting isn't going to do you any good at this point. Flash first
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks.

jd1639 said:
Rooting isn't going to do you any good at this point. Flash first
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Odin failed.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!
What next? I'm trying to find more info.

SRCP said:
Odin failed.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!
What next? I'm trying to find more info.
Click to expand...
Click to collapse
This looks bad. The blue bar on phone moved a bit then stopped and it's stuck there. I tried Odin again and now I get this:
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!

Try a different port on the PC. Use one that is attached to the motherboard. Usually the USB ports on the back of the PC. Then try again

RockRatt said:
Try a different port on the PC. Use one that is attached to the motherboard. Usually the USB ports on the back of the PC. Then try again
Click to expand...
Click to collapse
I restarted the phone and now I'm on the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I did have it connected to a rear usb port, let me change it.

RockRatt said:
Try a different port on the PC. Use one that is attached to the motherboard. Usually the USB ports on the back of the PC. Then try again
Click to expand...
Click to collapse
It worked. Tried a different cable and port. I have all my apps, is that normal? I thought this did a factory reset.

Thanks guys. It worked, I'm rooted .

HELP

<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUGNF1_I9505OXAGNF1_I9505XXUGNF1_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<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> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)

Are you sure you have the right .tar image for your device?
Did you try downloading it again and trying with a fresh copy?

help
what i must do now my phone is in download mode at end stuck what now?

SchawanHD said:
what i must do now my phone is in download mode at end stuck what now?
Click to expand...
Click to collapse
A LOT more detail about what you are trying to do, what you started with, etc etc etc would be helpful.
Was the phone working before?
Are you just trying to update it?
What ROM did you have before? Stock or custom?
Give us the bigger picture here.
If your phone was working before then what you've done shouldn't have killed anything. Pull the battery and reboot and it should start up as normal.
The next thing I'd try (After the 2 things I've already suggested that you didn't check yet) is to uncheck REBOOT AUTOMATICALLY in Odin. When it fails, immediately run the update again. See what happens then.

HELP!
i have before make this Cyanogen mod 10.2 and then i decided to flash to stock rom
now i make an Fullwipe per CWM and then i took The tar of the firmware of my old stock version.
now my phone stuck at end of downloadmode (i'm too scared to pull off battery)
and odin says fail blablabla
CMOD had android 4.3.1 and i took I9505jtexx... 4.4.2

Skipjacks said:
A LOT more detail about what you are trying to do, what you started with, etc etc etc would be helpful.
Was the phone working before?
Are you just trying to update it?
What ROM did you have before? Stock or custom?
Give us the bigger picture here.
If your phone was working before then what you've done shouldn't have killed anything. Pull the battery and reboot and it should start up as normal.
The next thing I'd try (After the 2 things I've already suggested that you didn't check yet) is to uncheck REBOOT AUTOMATICALLY in Odin. When it fails, immediately run the update again. See what happens then.
Click to expand...
Click to collapse
i fullwiped the phone per CWM and try in downloading mode flashing the stock FW via ODin

Do the thing about unchecking auto reboot that i said earlier

Skipjacks said:
A LOT more detail about what you are trying to do, what you started with, etc etc etc would be helpful.
Was the phone working before?
Are you just trying to update it?
What ROM did you have before? Stock or custom?
Give us the bigger picture here.
If your phone was working before then what you've done shouldn't have killed anything. Pull the battery and reboot and it should start up as normal.
The next thing I'd try (After the 2 things I've already suggested that you didn't check yet) is to uncheck REBOOT AUTOMATICALLY in Odin. When it fails, immediately run the update again. See what happens then.
Click to expand...
Click to collapse
ok now what to do phone is in downloadmode stuck ?

Skipjacks said:
Do the thing about unchecking auto reboot that i said earlier
Click to expand...
Click to collapse
but if i pull off battery what will hapen? before flash i fullwiped phone!!!!

SchawanHD said:
but if i pull off battery what will hapen? before flash i fullwiped phone!!!!
Click to expand...
Click to collapse
As long as Odin isn't actively writing to the device, nothing will happen with a battery pull.
You shouldn't have full wiped the phone prior to this.
And please don't make multiple threads to discuss the same thing.
Just try the things I've suggested so far.

Samsung S4 (i9505) bricked. Recovery doesn't work, only download mode.

Hi.
So what I recently did was I plug phone in downlaod mode to pc and install stock firmware (the same that was installed already 5.0.1) using odin. Unfortunetly phone still bricked, recovery doesnt't work. Then i was flash twrp recovery from odin and now phone show me:
recovery is not seandroid enforcing set warranty bit recovery alert. Now I'm thinking about do re-partition and install stock rom again, but i want to save my files.
Maby I'm doing something wrong, please help me.
Sorry for my english ;_;

What is the model # in download mode? Did you use the stock ROM from sammobile.com? Any errors when flashing with Odin?

audit13 said:
What is the model # in download mode? Did you use the stock ROM from sammobile.com? Any errors when flashing with Odin?
Click to expand...
Click to collapse
No errors with flashing, I downloaded rom from stockroms.net, because sammobile download speed is frustrating and...
Model #? I do not understand what you mean. I see only GT-I9505, system status, knox etc.

I would try a firmware from samsung-updates.com or sammobile.com.

audit13 said:
I would try a firmware from samsung-updates.com or sammobile.com.
Click to expand...
Click to collapse
Ok, now i downloaded rom from sammobile.com (goo_gl/os9avL) and flash faild!
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUHPK2_I9505XEOHPL1_I9505XXUHPK2_HOME.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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
What should I do now?

Now i was tried with odin 3.11v and faild again. Previously i used 3.09v.
Code:
<OSM> Enter CS for MD5..
[...]
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!

Was the phone dropped? What happened that needed you to reflash there stock ROM?
Can you flash twrp using Odin?

audit13 said:
Was the phone dropped? What happened that needed you to reflash there stock ROM?
Can you flash twrp using Odin?
Click to expand...
Click to collapse
I need to flash to stock, because phone start restarting itself and sometimes gets bootloop. When I tried enter to recovery mode phone instantly reboot, after few tries recover stop working.

Maybe flash twrp to see if you can get into recovery?

audit13 said:
Maybe flash twrp to see if you can get into recovery?
Click to expand...
Click to collapse
When I flash twrp and enter recovery mode I have this alert:
Code:
recovery is not seandroid enforcing set warranty bit recovery

So the phone stays on that message or something else happens?

audit13 said:
So the phone stays on that message or something else happens?
Click to expand...
Click to collapse
Phon stay on that message and nothing else happeneds. Any tips?

Sounds like there could be a problem with the phone's internal memory chip. You could take it to a cell repair shop to see if they can flash the firmware using a jtag cable or octopus box.

audit13 said:
Sounds like there could be a problem with the phone's internal memory chip. You could take it to a cell repair shop to see if they can flash the firmware using a jtag cable or octopus box.
Click to expand...
Click to collapse
Hmmm. What you think about flashing system with re-partition option? It make sense?

You can try flashing with a pit file. Make sure you get a pit file that matches the phone's internal memory size.

audit13 said:
You can try flashing with a pit file. Make sure you get a pit file that matches the phone's internal memory size.
Click to expand...
Click to collapse
OK, when I do this, there is no way to save my files? Do you think, service can keep my internal data?

It's going to be very expensive to try and recover data, especially if the internal memory chip is damaged.