Hi there.
I got my Note3 N9005 yesterday, and it had a slight problem : it didn't have cursive recognition for my native langage.
So I decided to get a local firmware for it.
I was in MK1. (JB 4.3 ; Hong Kong version)
I downloaded my local firmware, version MK2, with the XEF product I want.
I launched Odin V3.07. Chose PDA. Didn't check any other boxes. Connected the phone in DL mode.
And "Start".
And I got the following error :
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXXDMK3_N9005XXUDMJ7_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.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>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What I understand is that I have an EXT4 partition and that Odin cannot write on it.
Since then, I have used many other versions of Odin, including 1.85 which is supposed to overcome that peculiar problem on the Note 3.
I'm currently downloading MJ7 firmware on Sammobile hoping to try another firmware, and also a Kitkat NC2 version.
Any other idea ? Thanks !
EDIT : may my phone be "region locked", making it impossible to flash a local firmware ?
Try with MJ7 version :
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMJ7_N9005OXXDMJ4_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Ext4)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
No better result.
Ok.
It's been fixed. I downloaded a MK1 HongKong rom and it worked flawlessly.
Tried Factory reset and new flash of XEF rom : fail.
Went back to MK1 TGY. Working.
Will try to see what I can do to bypass this limitation.
Not sure but you might want to check specs of your phone. If I remember correctly, the HK version comes with 16GB whereas the European version with 32GB of internal memory.
This might be the reason that you can only flash HK fw.
Envoyé de mon GT-N5120 en utilisant Tapatalk
LuMe96 said:
Not sure but you might want to check specs of your phone. If I remember correctly, the HK version comes with 16GB whereas the European version with 32GB of internal memory.
This might be the reason that you can only flash HK fw.
Envoyé de mon GT-N5120 en utilisant Tapatalk
Click to expand...
Click to collapse
Thanks for the warning. However I did check and everything is fine, with 32 Gb of memory, Qualcom processor, 3 gb of ram, etc. ^^
Sorry my bad. I was convinced that the HK version had only 16GB of internal memory.
Envoyé de mon SM-N9005 en utilisant Tapatalk
5396492 4380
LuMe96 said:
Sorry my bad. I was convinced that the HK version had only 16GB of internal memory.
Envoyé de mon SM-N9005 en utilisant Tapatalk
Click to expand...
Click to collapse
You are not the only one. Someone else told me that. It happens that Samsung DID make a version for HK with only 16 Gb of memory. But it was just at first. Now, all versions are availble in HK.
More info about my problem and how to solve it :
http://www.cultofandroid.com/53963/save-galaxy-note-3-failed-kitkat-update-odin-tip/
Related
Hi,
I;ve posted this issue before but no one answered my previous thread ( T_T )
the issue still hasn't changed.
Trying to flash a Australian ROM on to my N9005.
getting this error in odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENE3_N9005VAUENF1_N9005XXUENE3_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> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing EU ROM's are fine as I'm currently using the UK 4.4.2 ROM N9005XXUGNG1
Please HELP; as it seems I cant use 4G with this ROM
you cant flash older fw, NG1 is new dont downgrade to older
Both 4.4.2
Thanks for reply!
Yes I'm aware that you can't downgrade.
Both ROM'S are 4.4.2 it just always fail at the same point no matter what.
The only thing that is different is one ROM is branded and one isn't
The one I'm trying to flash is Vodafone.
soulzsium said:
Thanks for reply!
Yes I'm aware that you can't downgrade.
Both ROM'S are 4.4.2 it just always fail at the same point no matter what.
The only thing that is different is one ROM is branded and one isn't
The one I'm trying to flash is Vodafone.
Click to expand...
Click to collapse
Your current version is GNG1 while the rom being flashed is ENE3 (older).
Try to flash the newer one.
vndnguyen said:
Your current version is GNG1 while the rom being flashed is ENE3 (older).
Try to flash the newer one.
Click to expand...
Click to collapse
N9005XXUGNG1 this was released in August
N9005XXUENE3 this was released in July
so I can't flash to a release that was a month old?
I thought that as long as the boot loader was the same version I could flash freely?
soulzsium said:
N9005XXUGNG1 this was released in August
N9005XXUENE3 this was released in July
so I can't flash to a release that was a month old?
I thought that as long as the boot loader was the same version I could flash freely?
Click to expand...
Click to collapse
Not sure if they have the same bootloader version?
You can only check for the bootloader version after install it.
vndnguyen said:
Not sure if they have the same bootloader version?
You can only check for the bootloader version after install it.
Click to expand...
Click to collapse
They are both KitKat 4.4.2 so I'm assuming yes
soulzsium said:
They are both KitKat 4.4.2 so I'm assuming yes
Click to expand...
Click to collapse
I'm not too sure, sorry. You have to check for the bootloader version.
Or you can also flash the modem (baseband) separately.
soulzsium said:
Hi,
I;ve posted this issue before but no one answered my previous thread ( T_T )
the issue still hasn't changed.
Trying to flash a Australian ROM on to my N9005.
getting this error in odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENE3_N9005VAUENF1_N9005XXUENE3_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> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing EU ROM's are fine as I'm currently using the UK 4.4.2 ROM N9005XXUGNG1
Please HELP; as it seems I cant use 4G with this ROM
Click to expand...
Click to collapse
The problem is your original pit file. As you can see problem is related to hidden partition that is to small for the image from your room that you want to flash(is the place where of in is stopping and give you error). To solve this you need to flash a pit file compatible with the room that you want to flash. What exactly do you want to achieve flashing this room anyway? ..
---------- Post added at 06:56 PM ---------- Previous post was at 06:39 PM ----------
If just LTD is your problem then check this:
<br />
Use ES File explorer or your favorite root explorer and go to data/property and find the persist.radio.lteon.xml file. Open it in Text Editor and if the value that is written is false, change it to true. Save and exit and reboot. Got the options back. Done.<br/>
Hello, I hope you could help me.
I tried to flash original rom with Odin, so I could install cwm and root, but that's what happened... It's bricked now...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNG1_N9005GBLGNG1_N9005XXUGNG1_HOME.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> 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> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks!
Emil
does it start normally???certainly no so flash again with odin and get last 3.09 version
from which rom version are you starting???
rayman95 said:
does it start normally???certainly no so flash again with odin and get last 3.09 version
from which rom version are you starting???
Click to expand...
Click to collapse
I bought it yesterday. It said it needed update, so I updated , this update is from July 2014.
It was working fine, I wanted to install recovery and flashed original rom, and then it started giving me those error messages with Odin 3.09.
I've tried Odin 3.07, the same result.
Then I found a polish, 4 files stock rom (BT, Phone, PDA and CSC) it passed, but I locked it and it doesnt work good. Sometimes it does not start... What can I do?
Thanks in advance!
Emil
emilloparski said:
Hello, I hope you could help me.
I tried to flash original rom with Odin, so I could install cwm and root, but that's what happened... It's bricked now...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNG1_N9005GBLGNG1_N9005XXUGNG1_HOME.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> 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> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks!
Emil
Click to expand...
Click to collapse
What did you select in Odin, which buttons? PDA? Or which? That could've bricked it...
emilloparski said:
Hello, I hope you could help me.
I tried to flash original rom with Odin, so I could install cwm and root, but that's what happened... It's bricked now...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNG1_N9005GBLGNG1_N9005XXUGNG1_HOME.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> 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> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks!
Emil
Click to expand...
Click to collapse
i got desame error but ive already done with this probem. TRY tO CHANGE STOCK FIRMWARE YOU HAVE TRYING TO FLASH (THE FIRMWARE YOU HAVE TO DOWNLOAD IS NEAR IN YOUR COUNTRY NOT FAR IN YOUR COUNTRY) TRY NH1 FIRMWARE. if i help you press thanks.
emilloparski said:
Hello, I hope you could help me.
I tried to flash original rom with Odin, so I could install cwm and root, but that's what happened... It's bricked now...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNG1_N9005GBLGNG1_N9005XXUGNG1_HOME.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> 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> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks!
Emil
Click to expand...
Click to collapse
Well, it didn't pass. go to samobile and download your region's firmware and try again. Which bootloader did you use? KK? If you took KK you might have to try and solve the issue with bootloader. If you don't care about root, try installing another kernel and install CWM. Might fix it.
Did you tick 'Re-Partition' in Odin?
Pagnell said:
Did you tick 'Re-Partition' in Odin?
Click to expand...
Click to collapse
Ignore this one. Do NOT tick Re-partition.
Pagnell... if you want to be helpful, as least fully state what you are trying to tell.
Your question might make him tick that selection.
Solved. I was told that any stock rom from my region would work. Since I bought it and live in Bulgaria, I tried the BG one. Didn't match. Itried it 4-5 times. Then I tried highly recommended polish one which was older, but it locked my phone ( btw it's a polish imported phone ). Then I tried last german, last Bulgarian and last UK. Didn't help. Until I finally tried last Slovakian which worked and it' similiar to the last Polish that I was planning to test after that. So Slovakian Telekom finally worked. And I was about to try it even earlier, but there was this recommended 4 file polish one that everyone was talking about that "works"
Hi everyone,
Tried installing HK version of Lollipop onto my Australian Note 3 using Odin. encountered an error and ended up soft bricked.
Searched various forums and posts and tried to flash the Telstra N9005XXUENE3_N9005TELENE1_N9005XXUENE3_HOME.tar.md 5 which is the stock rom I had on it before.
However Odin keeps failing with this error message:
ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENE3_N9005TELENE1_N9005XXUENE3_HOME.tar.md 5 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> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Have tried everything! please help!!
please try flashing again, but use a lollipop pit file for your device. (PIT file is not the same for HK Version and N9005)
how did you go flashing hk version. i want to update to stock lollipop but im not sure what version to use. will latest do? i have a telstra sm-n9005.
CheapMerc said:
how did you go flashing hk version. i want to update to stock lollipop but im not sure what version to use. will latest do? i have a telstra sm-n9005.
Click to expand...
Click to collapse
Hi,
HK version was no good...I ended up using the Polish version which worked fine.
Try that one.
mukid728 said:
Hi everyone,
Tried installing HK version of Lollipop onto my Australian Note 3 using Odin. encountered an error and ended up soft bricked.
Searched various forums and posts and tried to flash the Telstra N9005XXUENE3_N9005TELENE1_N9005XXUENE3_HOME.tar.md 5 which is the stock rom I had on it before.
However Odin keeps failing with this error message:
ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENE3_N9005TELENE1_N9005XXUENE3_HOME.tar.md 5 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> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Have tried everything! please help!!
Click to expand...
Click to collapse
try to download the latest stock rom for your mobile in sammobile. After that try to flash via ODIN
hello
i have been flashing roms for ages now and really never had such a problem like this before , i am on sweet rom , model number N910U ( new zealand ) , i need to go back to stock rom cause there to been a hardware problem with the camera, thought i better get back to stock before i take it in .
i have unsuccessfully trying to unroot via odin ( Odin3 v3.09) tried using this firmware "BRI-N910UXXU1BOGB-20150731100307" and even had worse luck with this one " CTI-N910UXXU1BOE1-20150721100509" (fails in a few seconds)
seems to have failed just before it gets to hidden.img
heres the log :
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910UXXU1BOGB_N910UZZT1BOGB_N910UXXU1BOGB_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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Hello,
I have the same problem on the S5+ and for the moment i don't find solution for this problem. I think CSC is causing this error and my advice is to install samsung phone info to find CSC and download right firmware for your phone. After that you can try to reinstall with Odin the firmware .
Sent from my SM-G901F using Tapatalk 2
I am trying to flash a stock rom on my Note 4 Exynos Version, with odin I have tried the latest version as well as some older ones. I have tried flashing both kit kat & lollipop but always get the same error. I have usb debugging ticked.
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
why is this happening?
Ta
Any help guys?
@home said:
Any help guys?
Click to expand...
Click to collapse
you are facing a locked bootloader as we all are (both exy and snap) the only solution to fix your bootloop is to install apps like phone info then find out what your phone PDA version is then find the exact PDA from Sammobile or if you you are Having an 910C flash latest COJ5 rom or if you are on 910H try installing COJ4 rom (just download and install the latest frimware from sammobile or ... and you will be just fine )
ArmanFGT said:
you are facing a locked bootloader as we all are (both exy and snap) the only solution to fix your bootloop is to install apps like phone info then find out what your phone PDA version is then find the exact PDA from Sammobile or if you you are Having an 910C flash latest COJ5 rom or if you are on 910H try installing COJ4 rom (just download and install the latest frimware from sammobile or ... and you will be just fine )
Click to expand...
Click to collapse
I followed your instructions and this is what I'm getting. Now what I need to do further? Previously I was using Sixperience ROM.
<ID:0/003> Added!!
<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> modem.bin
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
sirius_gamer said:
I followed your instructions and this is what I'm getting. Now what I need to do further? Previously I was using Sixperience ROM.
<ID:0/003> Added!!
<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> modem.bin
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
well , i dont really know what the XmitData_write is , as i havent seen it since my s4 (everything was fine) ..
i think wiping would solve the Prob...
or maybe USB cable or odin version (+drivers)
2. if nothing works around ... try using KIES emergency updating ... its always the sweety
odin3 v 3.12
i have same problem;
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> 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.1203)..
<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> 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> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
sdstc said:
odin3 v 3.12
i have same problem;
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> 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.1203)..
<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> 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> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
problem is using UN-OFFICIAL USB CABLE
use FACTORY CABLE FIXes problem
sdstc said:
problem is using UN-OFFICIAL USB CABLE
use FACTORY CABLE FIXes problem
Click to expand...
Click to collapse
@sdstc is right you can fix __XmitData_Write with changing the cable
i used an original sammy cable and it didnt work. than i used another sammy cable and then it just worked
my device was a Tab S btw no note 4 or s4
bu arada cok sagol sdstc kardes
TimurAlaskara_TR said:
@sdstc is right you can fix __XmitData_Write with changing the cable
i used an original sammy cable and it didnt work. than i used another sammy cable and then it just worked
my device was a Tab S btw no note 4 or s4
bu arada cok sagol sdstc kardes
Click to expand...
Click to collapse
i all the time face with that error and i forgot use original cable
(ne için teşekkür?)
sdstc said:
i all the time face with that error and i forgot use original cable
(ne için teşekkür?)
Click to expand...
Click to collapse
Sen olmasan telefon hala bozuktu cunku sjsjsj
help plz
sdstc said:
problem is using UN-OFFICIAL USB CABLE
use FACTORY CABLE FIXes problem
Click to expand...
Click to collapse
<OSM> Please wait..
<OSM> N910CXXS2DQG1_N910COXA2DPH1_N910CXXU1DPC1_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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)