ISSUE RESOLVED NEEDED A GENIUNE CABLE USING A CHEAP CABLE DONT WORK
im on echo rom
my signal is poor so i went to flash a different modem
fnc4 as its a uk based modem
it failed via flashin in odin got the end saying writing failed
<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> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
now im unable to flash any think via odin
tried a full rom
I9505XXUFNC9-OXAFNB8-PRE-ROOTED-KNOX-FREE-ODEX-FULL
<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> NON-HLOS.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added
my download info are
product name gt i9505
current binary samsung officail
system status custom
knox kenerl lock 0x0
knox warrenty 0x1
csb config lsb 0x30
write protection enable
emmx burst mode enabled
i really need some help with this ive never had this issue before i think i may have semi bricked my device
im unable to get into recovery at the moment wont allow me to flash recovery
any help welcome
Related
This is the log of my odin flashing stock rom for galaxy y
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Use another odin file and next time please create these threads in Q/A section
gaurav9822 said:
This is the log of my odin flashing stock rom for galaxy y
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Disable antivirus before open odin .
If don't work . Disable antivirus then reboot pc then open odin.
If still don't unistall antivirus.
Sent from my GT-S5360 using Tapatalk 2
<ID:0/003> Removed!!
<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> 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)
What can i do?
change to philz or twrp or chenglu...
rayman95 said:
change to philz or twrp or chenglu...
Click to expand...
Click to collapse
What is "chenglu"???
xSplashx said:
What is "chenglu"???
Click to expand...
Click to collapse
CWM....
From the beginning it was not installed any recovery, but I found the solution:
You need to be switched on and must be turned off the "reactivation lock".
Hi,
I have a n900w8 with some marshmallow rom (and some kernel I don't remember since I've already wiped all). I've downloaded a original stock rom from sammobile. Unfortunately, the latest version is a lollipop one, not a marshmallow one.
I've read that the bootloader cannot be downgraded after the 5.x. I think I have 5.x or higher bootloader. Are there any chance to install the custom rom? like this one(http://www.sammobile.com/firmwares/download/67302/N900UBUEBOK1_N900UUBEBOK1_UPO)
Kies3 says mi phone is not compatible with it, and kies "standard" doesn't recognise any device.
Odin gives me this error:
<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.1101)..
<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)
Click to expand...
Click to collapse
I've read that editing the TAR file and remove some files (like the boot.img, cache.img, hidden.img. etc). I've tried removing several of them with same (or similar) results.
If I remove the boot.bin, I get this:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<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> cache.img
<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)
Click to expand...
Click to collapse
If I remove cache.img, I get:
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<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> hidden.img
<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)
Click to expand...
Click to collapse
If I remove hidden.bin:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<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> modem.bin
<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
If I remove modem.bin:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<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> param.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> FAIL!
<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've restored a 4.4.4 backup with twrp before doing all that
I'm running out of ideas.
Thank you very much!
leitor79 said:
Hi,
I have a n900w8 with some marshmallow rom (and some kernel I don't remember since I've already wiped all). I've downloaded a original stock rom from sammobile. Unfortunately, the latest version is a lollipop one, not a marshmallow one.
I've read that the bootloader cannot be downgraded after the 5.x. I think I have 5.x or higher bootloader. Are there any chance to install the custom rom? like this one(http://www.sammobile.com/firmwares/download/67302/N900UBUEBOK1_N900UUBEBOK1_UPO)
Kies3 says mi phone is not compatible with it, and kies "standard" doesn't recognise any device.
Odin gives me this error:
I've read that editing the TAR file and remove some files (like the boot.img, cache.img, hidden.img. etc). I've tried removing several of them with same (or similar) results.
If I remove the boot.bin, I get this:
If I remove cache.img, I get:
If I remove hidden.bin:
If I remove modem.bin:
I've restored a 4.4.4 backup with twrp before doing all that
I'm running out of ideas.
Thank you very much!
Click to expand...
Click to collapse
frist of all do a full wipe (cache,dalvik,system,data)
secend flash last modem and bootloader 5.0 i think its PB1
third flash a stock rom
its must working
because i did it
Download the stock ROM for the sm-n900w8 from sammobile.com and flash it in Odin: http://www.sammobile.com/firmwares/database/SM-N900W8/
Flashing in Odin will wipe everything and you should do a factory wipe using stock recovery before booting the newly-flashed stock ROM for the first time.
Odin failed the first time because the ROM you tried to flash has a bootloader that is either not meant for your phone or the bootloader in the ROM is older than the bootloader in the phone. Look like you are flashing the n900 stock ROM, not the n900w8 ROM. You have a Canadian note 3? You can confirm the model # by booting into download mode.
Do nothing it's gonna flash it because I have incurred same problems while flashing from lollipop to kitkat but then I just slept at night and the next morning tried with another USB cable and it worked fine .
It's nothing to do with bootloader because every stock Rom contains bootloader and it will flash it anyhow.
Sent from my SM-N900 using Tapatalk
So basicly I rooted my phone like 3 days ago so yesterday since it was going slow and all. I was trying to revert from rooted 6.0.1 to stock 6.0.1 but I have literaly tried so much stock roms for att on the internet and it failed from model dismatch. But then I found one that matched and odin passed till it failed at system.img.ext4. Here is the log:
<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> 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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And there is an error on the phone:
SW REV CHECK FAIL : [system]Fused 3 > Binary 1
Please help me I just got this one from insurance and if my dad finds out I broke it. I'm going to be toast!!!!
TheAndroidGuy101 said:
So basicly I rooted my phone like 3 days ago so yesterday since it was going slow and all. I was trying to revert from rooted 6.0.1 to stock 6.0.1 but I have literaly tried so much stock roms for att on the internet and it failed from model dismatch. But then I found one that matched and odin passed till it failed at system.img.ext4. Here is the log:
<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> 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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And there is an error on the phone:
SW REV CHECK FAIL : [system]Fused 3 > Binary 1
Please help me I just got this one from insurance and if my dad finds out I broke it. I'm going to be toast!!!!
Click to expand...
Click to collapse
Same issue here, I think you need to find a more recent version of the file - which I can't find at the moment
did you not make a back up before rooting your phone , either on your phone or smart switch so that you can revert to stock rom if needed.
all threads advise backing before flashing in case some thing like this happens.
theandroidguy101 said:
so basicly i rooted my phone like 3 days ago so yesterday since it was going slow and all. I was trying to revert from rooted 6.0.1 to stock 6.0.1 but i have literaly tried so much stock roms for att on the internet and it failed from model dismatch. But then i found one that matched and odin passed till it failed at system.img.ext4. Here is the log:
<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> 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> singledownload.
<id:0/003> boot.img
<id:0/003> recovery.img
<id:0/003> system.img.ext4
<id:0/003> fail! (auth)
<id:0/003>
<id:0/003> complete(write) operation failed.
<osm> all threads completed. (succeed 0 / failed 1)
and there is an error on the phone:
Sw rev check fail : [system]fused 3 > binary 1
please help me i just got this one from insurance and if my dad finds out i broke it. I'm going to be toast!!!!
Click to expand...
Click to collapse
pm me! I just flashed my s7 at&t. I can send you the files
Hey there,
my galaxy s8 went into a bootloop after rooting with TWRP.
Currently on Android 8.0 and the cpu is Exynos.
After using Odin to reflash to stock android it failed numerous times.
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5869 M
<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> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> cm.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Using Odin v3.13.1
marky2458 said:
Hey there,
my galaxy s8 went into a bootloop after rooting with TWRP.
Currently on Android 8.0 and the cpu is Exynos.
After using Odin to reflash to stock android it failed numerous times.
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5869 M
<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> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> cm.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Using Odin v3.13.1
Click to expand...
Click to collapse
Are you using correct firmware for your phone and region or maybe trying to use older version of firmware than what's on your phone.