Bricked / Soft Bricked Phone ? Tried everything - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

I REALLY hope anyone can help. I am desperate. I have been trying to unbrick my phone since last night. I have tried everything... I have been all over this forum.
I had a rooted Canadian Rogers S4 (I337M) with a google edition 4.3 rom.
I tried to flash the default rogers stock rom, however got an odin fail. I have been unsuccessful trying to restore the phone.
I have tried MF3.tar and MK2.tar (as per Ted's posts), however keep getting odin fail.
Can anyone help or suggest something?
<OSM> Please wait..
<OSM> I337MK2_Full_Odin_Tar.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

Go to sammobile.com and download the firmware for the Rogers i337m. You'll have to register but it's free
Edit, make sure you're using the cable that came with your phone. Use the usb ports in the back of your pc, usb 2.0 not 3.0. And keep trying. Odin can be finicky
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Go to sammobile.com and download the firmware for the Rogers i337m. You'll have to register but it's free
Edit, make sure you're using the cable that came with your phone. Use the usb ports in the back of your pc, usb 2.0 not 3.0. And keep trying. Odin can be finicky
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Downloading now...

n3gkiwi said:
Downloading now...
Click to expand...
Click to collapse
You'll download a zip file. Use 7-zip to extract a .tar.md5. Use that in Odin, PDA slot
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app

Still failed. Is it my modem.bin?
<OSM> I317MVLALJ2_I317MOYAALJ2_I317MVLALJ2_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> modem.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1

Odd, I tried odin 3.07, 3.09, and 1.85.... keeps failing. Any ideas?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1

I think you need to install your modem first. Extract the modem.bin file from the tar.Md5 file you downloaded from sammobiile.
Make a copy of .tar.md5 file. Rename it to .tar. open with 7zip, extract modem.bin file. flash this modem.bin file twice using odin. put it in phone slot and uncheck autoreboot in odin.
After successful flashing of modem in odin flash the firmware tar.md5 by putting it in pda slot of odin.
Try using Odin 3.07. I had the same prob when I was going back from goldeneye to stock firmware.This did the magic.
Good Luck

So i go it working finally however when the phones restarted however android.process.acore keeps stopping?
Phones says "Unfortunately, the process android.process.acore has stopped."
Any ideas?
Edit: Went into recovery and did a wipe/factory reset. Hopefully that works

n3gkiwi said:
So i go it working finally however when the phones restarted however android.process.acore keeps stopping?
Phones says "Unfortunately, the process android.process.acore has stopped."
Any ideas?
Edit: Went into recovery and did a wipe/factory reset. Hopefully that works
Click to expand...
Click to collapse
Did you wipe your data/cache and dalvik before you flashed the stock image? If you continue to have problems try that before you flash again, if you google the statement about infortunately, there is lots of posts about your data....

Related

Xmit Write fail with ODIN

Hey guys,
I've been having some issues with an international rom on my W8 and i decided to go back to stock with odin. As i was flashing i realized that everytime i would reboot, even after a factory reset, or data/system/cache wipe, all my file and folders were not erased. So i booted into TWRP and wiped internal SD and all the other stuff, then flashed back stock rom with odin and now i keep getting this error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910W8VLU1ANJ3_N910W8OYA1ANJ3_N910W8VLU1ANJ3_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Click to expand...
Click to collapse
Basically i start flash process and about 30 seconds in i hear the phone disconnect and i get the fail. I know it's not a bad firmware download as i've lready flahsed it 5 times today, i know it's not cable, or USB port because until i wiped internal SD i did not have any issues. Now, i can still access download mode, but i cannot access recovery because it tells me "firmware upgrade encountered an issue. Please select recovery mode in kies and try again." When i connect it to kies, it simply says phone not supported and doesnt show up under emergency recovery.
Anybody know how to get me out of this mess??
weird, my note 4 cable was causing the issue. I took my old S2 cable and it worked. Thanks anyways

[Q] ODIN fails at the end to transfer ROM to S4, says added, fail and removed

Allo,
I finally found the ROM for Galaxy S4 SGH-I337M and the CF auto root.
ROM file : I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.tar.md5 (Virgin mobile, lollipop 5.0.1)
CF Root : CF-Auto-Root-jfltecan-jfltevl-sghi337m.tar.md5
The problem is that ODIN transfers the image to the phone but fails at the very last bytes. It says added, fails, removed.
Odin 3.09 is used, autorebbot and F.Reset are ticked. Nothing else.
What am I doing wrong???? What is required to have a sucessful upload?
Need help, phone is bricked.
I just flashed this file with odin 3.04, no problems except I had to flash it twice to change baseband, and my carrier is fido, so I had to change csc. I have seen recommendations here to use that version of Odin with this particular model, never failed me. Also, I use my original Samsung cable for Odin flashes, seen posts that cheap cables make a difference. and make sure you have all the correct drivers installed. I can't help other then that, sorry, limited knowledge myself, but the search button is your friend, all kinds of answers on the forums.
pcote_xda said:
Allo,
I finally found the ROM for Galaxy S4 SGH-I337M and the CF auto root.
ROM file : I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.tar.md5 (Virgin mobile, lollipop 5.0.1)
CF Root : CF-Auto-Root-jfltecan-jfltevl-sghi337m.tar.md5
The problem is that ODIN transfers the image to the phone but fails at the very last bytes. It says added, fails, removed.
Odin 3.09 is used, autorebbot and F.Reset are ticked. Nothing else.
What am I doing wrong???? What is required to have a sucessful upload?
Need help, phone is bricked.
Click to expand...
Click to collapse
99% of all Odin errors are solved by the following:
- Different usb port
- Different cable
Allo,
I followed the instructions provided by JesterDoobie and I took note of the advise provided by Lennyz1988.
It works my friends, thank you for your support. At the end, I had to use a Samsung genuine cable to reach a complete and successful upload of the ROM.
With a third party cable, it would transfer but at the end (99% completed) it would indicate in red FAILS and the ODIN messages were:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<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> 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!!
With the procedure and Samsung cable = home run.

Any way to root/or downgrade from OH1 on SPH-720T?

Please is there any way to downgrade or root the sph-720t on android 5.0.1 OH1 Update. I swear I hate this update, and I'm urged to downgrade back to 4.4
maurs4216 said:
Please is there any way to downgrade or root the sph-720t on android 5.0.1 OH1 Update. I swear I hate this update, and I'm urged to downgrade back to 4.4
Click to expand...
Click to collapse
Copy latest SuperSU zip to SD card
Flash TWRP through Odin(uncheck reboot in Odin), disconnect USB, pull battery.
Reboot directly to TWRP
Flash SuperSU zip in TWRP
Boot phone and open SuperSU app to complete rooting process.
mattzeller said:
Copy latest SuperSU zip to SD card
Flash TWRP through Odin(uncheck reboot in Odin), disconnect USB, pull battery.
Reboot directly to TWRP
Flash SuperSU zip in TWRP
Boot phone and open SuperSU app to complete rooting process.
Click to expand...
Click to collapse
I've tried flashing twrp through doing several times with no success. Could it be because I flashed the full update (recovery, bootloader and rom)? I got the update straight from sam mobile
maurs4216 said:
I've tried flashing twrp through doing several times with no success. Could it be because I flashed the full update (recovery, bootloader and rom)? I got the update straight from sam mobile
Click to expand...
Click to collapse
No, that wouldn't stop you from flashing TWRP, what error did you get? Which version of TWRP did you try? Did you try different USB ports and/or cables?
mattzeller said:
No, that wouldn't stop you from flashing TWRP, what error did you get? Which version of TWRP did you try? Did you try different USB ports and/or cables?
Click to expand...
Click to collapse
Yes I've tried different usb ports/cables. Im on windows 8.1 and using odin v3.10. So far I've tried flashing twrp 2.8.4.0 and 2.8.0.0 both this error:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also tried cwm/philz touch and got errors:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.15.4-jfltespr.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
maurs4216 said:
Yes I've tried different usb ports/cables. Im on windows 8.1 and using odin v3.10. So far I've tried flashing twrp 2.8.4.0 and 2.8.0.0 both this error:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also tried cwm/philz touch and got errors:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.15.4-jfltespr.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I had problems flashing stock using Odin 3.10, give Odin 3.09 a try
mattzeller said:
I had problems flashing stock using Odin 3.10, give Odin 3.09 a try
Click to expand...
Click to collapse
Nah still got the same error on Odin 3.09
maurs4216 said:
Nah still got the same error on Odin 3.09
Click to expand...
Click to collapse
Hmmm, maybe the drivers? I have gone as far as formatted my computer reinstall windows and then reinstalled Samsung drivers just to make sure the computer wasn't the issue, turned out it was. Do you have another computer you could cleanly install the Samsung drivers and try flashing on that one?
King root probably works...
You can try King root and then replace King root with supersu. Check this out... https://www.youtube.com/watch?v=BVvmGs_q6n8
mattzeller said:
Hmmm, maybe the drivers? I have gone as far as formatted my computer reinstall windows and then reinstalled Samsung drivers just to make sure the computer wasn't the issue, turned out it was. Do you have another computer you could cleanly install the Samsung drivers and try flashing on that one?
Click to expand...
Click to collapse
K94U said:
You can try King root and then replace King root with supersu. Check this out...
Click to expand...
Click to collapse
Solved my issue today, and everything is working now! I used odin 1.85 with a samsung usb cable, flash twrp and supersu, thanks for you guys' help tho:good:

Flashing original Samsung firmware failing on cache.img in Odin

I've tried flashing the original Samsung roms on both Windows 7 & 8.1, on Odin 3.07, 3.09, 3.10.7 all failed in the same manner.
Flashing fails as soon as the system tries to flash cache.img.
Code:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone is the SM-N900 Exynos variant.
h3llb3nd4 said:
I've tried flashing the original Samsung roms on both Windows 7 & 8.1, on Odin 3.07, 3.09, 3.10.7 all failed in the same manner.
Flashing fails as soon as the system tries to flash cache.img.
Code:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone is the SM-N900 Exynos variant.
Click to expand...
Click to collapse
Udpate your Samsung drivers or simply install Kies 3. Try again then.
Joku1981 said:
Udpate your Samsung drivers or simply install Kies 3. Try again then.
Click to expand...
Click to collapse
I did install both Kies and Kies3, also made sure they weren't running. No avail. :/
h3llb3nd4 said:
I did install both Kies and Kies3, also made sure they weren't running. No avail. :/
Click to expand...
Click to collapse
Maybe is for that. Uninstall both. Only install now Kies 3 and try flash the firmware again.
* Are you sure that is the correct firmware for your device?
Your cache partition is most likely corrupted, just use the correct pit file for your n900 whilst flashing the rom.
Sent from my SM-N9005
Right, the issue was that I didn't flash the correct Pit file. But that's for another time.
NEW ISSUE!
In trying to solve the bad flash, during one of the flashes I checked NAND erase all. Now I just got the phone and have no EFS backups. is there any chance of fixing this? I don't have custom recoveries. Or do I have to send it in to Samsung?
The device boots fine, but I seemed to have wiped the phone's IMEI and baseband. The device can't register sims.

[Critcal help] please i delete my Phone system and i can not flash official frimware

hi please help me
i have a big problem in my Note 4 Samsung SM-N910C
i was rooting my phone by twrp... after some time i wanna delete root so i enter mY twrp then suddenly
wipe all
1-cach
2- Dalvik cach
3- System
4- Data
5-Internal storgae
6-Micro Sdcard
so i delete the phone system so it is not work again stuck only on twrp and when i try to install N910CXXU1COH4_N910COXA1COH4_N910CXXU1COH4_HOME.zip from sdcard it failed
and when i tried to install from Odin 10 N910CXXU1COH4_N910COXA1COH4_N910CXXU1COH4_HOME.tar.MD5
give me failed
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
so please how to fix it
My phone stuck only on Samsung note 4
Not sure if this will solve the issue, but read what I put here: http://forum.xda-developers.com/note-4/help/soft-bricked-note-4-n910f-t3306402
Thought I bricked my n910f, and all is good now!
But i do not have any stock frimaware on my phone i already delete the system
webby93
my odin log data
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910CXXU1COH4_N910COXA1COH4_N910CXXU1COH4_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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I didn't either, I completely wiped it.
What i think happened with me is that odin did put the stock firmware on even when it said it failed after like 5 mins. Then the allsamsungrecovery fixed the rest to let it boot up.
The only issue could be that your odin doesn't seem to have got quite as far as mine did. Can you only enter download mode and that's it?
i can enter download mod
but when i select the frimeware stock
The odin data appear log failed
and on the phone appeared : “SW REV CHECK FAIL DEVICE 2 BINARY 1”.
I'm really sorry, I don't think I'll be able to help any further. My knowledge is just from problem solving the few cases I've had to solve my self. Hopefully someone else can help you here.
Just Flash Lollipop 5.1.1 via odin which have coj5 or upgrade bootloader
you can't downgrade from coj5 bootloader you flash coh4 rom therefore you get error
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
flash this rom through odin complete stock and debloted firmware
download from here
https://docs.google.com/uc?id=0B8-hfA9ycQNoazRkV2xjNThWNWc&export=download
Best Regards,

Categories

Resources