Odin 1.85 I get yellow on COM9.
I was trying KG4 and it failed.
I now get this trying KG4...
<ID:0/009> Removed!!
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_T959VUVKG4_CL385158_REV00_user_low_noship.tar.md5 is valid.
<OSM> T959VUVKG4-Phone-CL1037720.tar.md5 is valid.
<OSM> SGH-T959V-CSC-TMB-VIBRANTP.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009>
<ID:0/009> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
SOOOOOOO..... I searched and someone said do KC1 since it's asimple 1 file flash.....
I click PDA and select the KC1 file. I click start and it runs for a few minutes.
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_KC1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> zImage
<ID:0/009> NAND Write Start!!
<ID:0/009> param.lfs
<ID:0/009> factoryfs.rfs
<ID:0/009> cache.rfs
<ID:0/009> data.rfs
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then I get FAIL.
If I reboot I get the TMobile Galaxy S screen stuck.
It's a new AT&T.
Help and thanks in advance. 3 hours of searching and flashing and still no go.....
hammermedia said:
Odin 1.85 I get yellow on COM9.
I was trying KG4 and it failed.
I now get this trying KG4...
<ID:0/009> Removed!!
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_T959VUVKG4_CL385158_REV00_user_low_noship.tar.md5 is valid.
<OSM> T959VUVKG4-Phone-CL1037720.tar.md5 is valid.
<OSM> SGH-T959V-CSC-TMB-VIBRANTP.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009>
<ID:0/009> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
SOOOOOOO..... I searched and someone said do KC1 since it's asimple 1 file flash.....
I click PDA and select the KC1 file. I click start and it runs for a few minutes.
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_KC1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> zImage
<ID:0/009> NAND Write Start!!
<ID:0/009> param.lfs
<ID:0/009> factoryfs.rfs
<ID:0/009> cache.rfs
<ID:0/009> data.rfs
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then I get FAIL.
If I reboot I get the TMobile Galaxy S screen stuck.
It's a new AT&T.
Help and thanks in advance. 3 hours of searching and flashing and still no go.....
Click to expand...
Click to collapse
wait what phone do you have?
AT&T Branded Infuse 4G
:FACEPALM!!!!!!!: Let me tell you what section you are in.
Samsung Galaxy S 4G
Galaxy S 4G Q&A
Congrats. You have a paperweight. You need to find the Infuse 4G STOCK ROM better to check that devices forum.
No comment
Wow.
Sent from my SGH-T959V using XDA Premium App
and this is why i asked lol cause i read it just wanted to make sure that what i read was right lol thanks krylon and honk so i wasnt the only one that saw that
I've been flashing ROMs on phones for 6 years and this is a first.
The reseller I bought this thing from said it would take the Galaxy S ROMs. He will be getting a call tomorrow.
The Infuse forum had a ROM and I'm already back running.
hammermedia said:
I've been flashing ROMs on phones for 6 years and this is a first.
The reseller I bought this thing from said it would take the Galaxy S ROMs. He will be getting a call tomorrow.
The Infuse forum had a ROM and I'm already back running.
Click to expand...
Click to collapse
it does take galaxy s roms so long as there made for your device nottttttttttt another device
lmfao!!!!!! epic fail, you've been trolled
I like how krylon360 was the first to facepalm, haha. :x
Good to know your phone is running again though. Next time, be sure to use the proper ROMs, or else you'll just get a really fancy paperweight.
In addition to that, make sure you do research before you believe anything a reseller says. They'll sometimes say anything to sell you.
Related
Hi, I am using Canadian version, I have tried every method on internet, but nothing is working.
Each time, I tried to use Odin to root, I get the following error
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hltecan-hlteub-smn900w8.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>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is it the problem of new firmware?
Can someone give me some hints?
Thanks a lot.
Possible fix
jiang01yi said:
Hi, I am using Canadian version, I have tried every method on internet, but nothing is working.
Each time, I tried to use Odin to root, I get the following error
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hltecan-hlteub-smn900w8.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>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is it the problem of new firmware?
Can someone give me some hints?
Thanks a lot.
Click to expand...
Click to collapse
I had the exact same problem and after digging around I found out that it was most likely because I had the option "Reactivation lock" (Under Security) on, after turning it off the CF-Auto-Root worked fine. I hope that helps.
Hello, this is a bit embarrassing seeing as how this is my first post here on XDA.
My issue is that I rooted my 4.4.2 Verizon SCH-i535 galaxy s3 and I bricked it. I know, I was extremely stupid for trying to do this while half-awake at 2 in the morning LOL... but i ended up with a screen stating that "this device has detected a software not authorized by verizon wireless, please go to a branch to get help"
When I use Odin to try and flash any ROMs, this is the result:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ODINRecovery.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> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
InuyashaITB said:
Hello, this is a bit embarrassing seeing as how this is my first post here on XDA.
My issue is that I rooted my 4.4.2 Verizon SCH-i535 galaxy s3 and I bricked it. I know, I was extremely stupid for trying to do this while half-awake at 2 in the morning LOL... but i ended up with a screen stating that "this device has detected a software not authorized by verizon wireless, please go to a branch to get help"
When I use Odin to try and flash any ROMs, this is the result:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ODINRecovery.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> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
check out this thread
http://forum.xda-developers.com/showthread.php?t=2791801
you may be able to get away with just flashing the booloader/recovery zip in the second post
good luck
I'm trying to flash a Bell Note 2 i317m in Odin and it keeps failing. The current firmware on the phone is 4.4.2 and trying to flash 4.3. Phone is still fully functional if I reboot. The error on the phone is "sw rev. check fail device 3 binary 2"
Log from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLUCMK5_I317MOYACMK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> sboot.bin
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
If anyone can help it'd be greatly appreciated. Thanks in advance.
I'm new to this and I bricked my phone pretty quickly. I'm trying to return it to stock. I have the MD5 file from sammobile. Whenever I try to start the process in Odin v3.10 (I've tried other versions and other MD5 files) I get
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I've been all over different forums trying to find any way to fix my problem but I can't get anything to work. Literally any help would be fantastic!
Hi
Have S8+ -- SM-G995F
Attempting to root my S8+ --
Using odin version 3.12
Together with this file: CF-Auto-Root-dream2lte-dream2ltexx-smg955f.tar.md5
Following steps from this site: wccftech.com/how-to-root-galaxy-s8-plus/
This is the Log form Odin:
<ID:0/009> 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/009> Odin engine v(ID:3.1203)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> recovery.img
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Nothing has happened for an hour. Phone still connected.
In a mild state of panic.
Any help much appreciated. Is there a graceful way out?
Thanks and cheers
Chexote said:
Hi
Have S8+ -- SM-G995F
Attempting to root my S8+ --
Using odin version 3.12
Together with this file: CF-Auto-Root-dream2lte-dream2ltexx-smg955f.tar.md5
Following steps from this site: wccftech.com/how-to-root-galaxy-s8-plus/
This is the Log form Odin:
<ID:0/009> 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/009> Odin engine v(ID:3.1203)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> recovery.img
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Nothing has happened for an hour. Phone still connected.
In a mild state of panic.
Any help much appreciated. Is there a graceful way out?
Thanks and cheers
Click to expand...
Click to collapse
Go over to the S8+ sampawnd thread it's now locked but I'm sure there's something there that would help you in your situation. A lot of nonsense in there it's going to take some sifting through the junk but I'm sure you'll find your answer. Good luck...
Update .. solved
Problem solved. Disconnected phone from computer. Did a soft reboot power+volume down for about 20secs. Phone rebooted ok. Works ok.
Chexote said:
Problem solved. Disconnected phone from computer. Did a soft reboot power+volume down for about 20secs. Phone rebooted ok. Works ok.
Click to expand...
Click to collapse
Good glad your back in business..