Database Develop

Flash process in Odin hangs

Hi everybody!
This is my first posting here, I hope it's in the right category. I've used the search function, found similar problems but no one facing the same issue. I wanted to upgrade to Android 2.3.3 (2.3.4) using Odin. I tried three different Firmware releases but none worked. This is what happens in Odin:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_XWJVI_Sbl.tar.md5 is valid.
<OSM> PHONE_XXJVO.tar.md5 is valid.
<OSM> CSC_DBTJV2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> param.lfs
<ID:0/006> zImage
I tried with and without repartition. Sometimes the process stops at the SetupConnection line, sometimes at zImage when obviously the kernel should be installed. When in download mode, I see a blue progress bar starting to move across the phone screen, but soon later the whole display turns green/blue/white (it always had a different color) with no more text. Hours later Odin finally displays a FAIL message.
I tried firmware versions I9000XXJVQ and I9000XXJVR from samfirmware.com with 512 PIT file. I recognized some Kies-Thread running in the background on my Win7 machine, which I killed to prevent any problems.
In another forum I was told this issue might be related to some lagfixes installing ext4. When I read that it came to my mind that I indeed had installed the voodoo lagfix in February - I had completely forgotten about that. However, is there a chance to recover the phone? Putting it into DL mode is the only thing that works. Any help is appreciated!

Can you go in recovery mode to disable the lagfix? and when you use the 3 part file always check re-partition.

Had similar problems with Windows 7 x64, 2 in 3 flashes would fail.
Try another pc if possible with Xp.

kuribo67 said:
Can you go in recovery mode to disable the lagfix?
Click to expand...
Click to collapse
Well, I tried, but I did not succeed - (Hold Vol up + Power on) but I'll try again. Is it absolutely necessary to remove the lagfix? As mentioned before someone told me that ext4 might be causing those problems. However, I though the sd was repartitioned (when checkbox is ticked) and the firmware is a kind of disk image which is installed and thus overwrites the existing file system?

aileron79 said:
Well, I tried, but I did not succeed - (Hold Vol up + Power on) but I'll try again. Is it absolutely necessary to remove the lagfix? As mentioned before someone told me that ext4 might be causing those problems. However, I though the sd was repartitioned (when checkbox is ticked) and the firmware is a kind of disk image which is installed and thus overwrites the existing file system?
Click to expand...
Click to collapse
it's vol up + home button + power on, but don't release the button untill your are in the menu.
A stock firmware is made for RFS partition not ext4, i think it's that the problem, but i may be wrong.

Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_XWJVI_Sbl.tar.md5 is valid.
<OSM> PHONE_XXJVO.tar.md5 is valid.
<OSM> CSC_DBTJV2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> param.lfs
<ID:0/005> zImage
<ID:0/005> boot.bin
<ID:0/005> Sbl.bin
<ID:0/005> factoryfs.rfs
Thank you all so far! Well, it almost worked - at least kind of. I tried it a couple of times, rebooted the PC, rebooted the phone, reinstalled drivers, used another USB port. After a couple of retries it stopped at "factoryfs.rfs" - which obviously contains the file system. This makes me guess that it does not matter which FS currently is installed as it gets overwritten by this factoryfs-thing. Please correct me if I am wrong!
Still, any help on this topic is gladly appreciated!

when you flash pda in odin the file system is over-written and reverts to rfs.
Try without re-partition ticked. Also after several attempts your battery may have no juice left in it: pull the battery, let it sit a couplce of minutes and then plug it in and see if it will re-charge -- may not, you might be stuck at download and odin.
Flash an older 2.2 firmware first: pda. phone and csc, don't bother with the pit file and don't bother with re-partition -- this is just to get you back and working, you can then charge the battery and update to jvr after.
Also check the thread on unbricking the phone -- most issues with flashing are recoverable, its just persistence.

lgsshedden said:
when you flash pda in odin the file system is over-written and reverts to rfs.
Try without re-partition ticked. Also after several attempts your battery may have no juice left in it: pull the battery, let it sit a couplce of minutes and then plug it in and see if it will re-charge -- may not, you might be stuck at download and odin.
Click to expand...
Click to collapse
Well, I tried to flash with and without repartition/pit-file. The download process hangs at different stages. I doubt it has to do with the battery, as the phone has been attached to the PC for almost three days now, I guess the battery is charged then...?
[/QUOTE]
Flash an older 2.2 firmware first: pda. phone and csc, don't bother with the pit file and don't bother with re-partition -- this is just to get you back and working, you can then charge the battery and update to jvr after.
Also check the thread on unbricking the phone -- most issues with flashing are recoverable, its just persistence.[/QUOTE]
To which of the thousands of unbricking threads do you refer? I read something about a tool which puts the phone into recovery mode, from where I can format the sd. However, I can't get to recovery mode by pressing vol up, home + power, i just can enter download mode. I have tried various firmwares, neither did work...
Thanks for your help so far, maybe you can give me another hint on the thread you're talking about?

Try rebooting the phone,rebooting the pc,use a different usb cable(this part made it work for me), and try again. Hope it helps man cause i've been down that road and it sucked bricked my sgs 2 times but thankfully revived it because heimdall one click un-brick oh and 1 more thing if you use 3 files check re partition
Sent from my GT-I9000 using xda premium

Mate, try a full 3 file flash and a pc with Win XP 32-bit and ODIN 1.83
Worked for me
Good luck flashing !!

Thank you all guys, it worked - even though it was none of the tips provided here. I have no clue what the problem was, I moved to another PC, it took me three tries to flash the phone.
- The second PC was Win7 64bit as well.
- I used the original cable (tried with another one as well, no difference)
- I used just the drivers without any Kies installation.
- I used a SINGLE FILE FLASH with Android 2.2.1 first (which I was then unable to boot as it stuck with the S symbol during boot)
- Flashed 2.3.4 afterwards - worked.
My phone has never ever been running so smoothly before, even with lag fixes!
Unfortunately, my external SD makes troubles, but let's see how to fix that.
My note to all of you guys facing similar problems:
Some say, use PIT and repartition, some say, don't
Just don't care - for me it finally worked without (single file flash). Try all possibilities.
Some say, install Kies, just because of the drivers, some say, install the drivers without Kies
Just don't care - try either option, it might work - for me the drivers without Kies finally worked but I have no clue if that had any impact.
Some say, use another USB cable, some say use the original one
Just don't care - try different cables if possible, in my case there was no difference.
Some say, use the USB port closest to your MB, others say, try various USB ports
Just don't care - try different ports, the behavior cannot be reproduced, each try the flashing process got stuck at another stage - independent of the USB port used.
Some say, try another computer with another OS
Good choice - that made it working in my case. Even though the other machine was nearly the same with exactly the same OS installed. Also, I have successfully flashed my phone with the first one before.
Thanks guys, you're the best! And give Android 2.3.4 a try, it's FAST and SMOOTH!

[Q] Can only use 'Download Mode'

Hi guys and girls.
I've been frantically searching XDA for the last few hours for a definitive answer, but to no avail, so thought it's about time I just asked!
I have in my possession a Samsung Galaxy S19000, that will only go into download made.
Here's how it happened........
This morning, I was given the phone by my brother in law and asked to root it and upgrade it to a newer/better rom. When it was passed
to me, it was.....
Firmware: 2.2.1
Baseband: 19000XXJY
Kernel: 2.6.32.9
[email protected] #1
Build: FROYO.XXJPY
After a successful root and upgrade, the phone ended up like this...
Firmware: 2.3.7
Baseband: 19000XXJVK
Kernel: 2.6.35.14-g3088622
Build: CyanogenMod-7.2.0-galaxysmtd
The new Rom, as nice as it was, wasnt what he wanted, so he asked me to restore it back to it's stock state. I went into CMW and did a restore, but it failed, and now the phone will only go into download mode.
I've tried flashing a stock rom via Odin, but it got as far as the 'Nand write' stage, then hangs.
Kies doesn't show up the device in 'Emergency firmware recovery' either.
I no all is not lost, so I'm not giving up. Any help will be much appreciated.
:fingers-crossed:

Can you post the whole Odin Log?
Normally this happen when the partitions on the embedded multi media card gets corrupted for whatever reason, also known as the emmc.
Maybe it helps to flash the pit file to repartition.

To add.....
When the phone is off, it displays the 'phone and computer with an explanation mark triangle inbetween symbol', and Kies doesnt recognise it. When I enter download mode, Kies hangs at 'Connecting' for.....well..ever! So atleast I know it's recognised by my PC (ish) and it isn't completely dead :silly:

I had the same thing with the triangle a few months ago.
I just flashed a Stock Firmware with Repartition. Just be sure with Odin that you have ticked the right things Afterwards it worked.

Thankyou for you reply, and sorry for the delay posting back. God damn new user restrictions!!!
KUN1 said:
Can you post the whole Odin Log?
Click to expand...
Click to collapse
Heres what Im getting...
Code:
<ID:0/009> Added!!
<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> KIES_HOME_I9300XXDLJ4_I9300OXADLJ4_368423_REV00_user_low_ship.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> boot.img
<ID:0/009> NAND Write Start!!

First try it with Repartition. If that doesn't work, you may have a look at this thread http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12

KUN1 said:
First try it with Repartition.
Click to expand...
Click to collapse
You'll have to excuse me, I've never had problems problems before, so I've only had to use the PDA box till now.....
Is that the re-partition tick box, or the re-partition PIT file box??
KUN1 said:
If that doesn't work, you may have a look at this thread http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Click to expand...
Click to collapse
Christ that looks involved doesn't it! I think that be a last resort as it looks like I'll need to clear a day in my diary before I start!

For the moment you can ignore the second thread
Find a 3 File (PDA, Phone, CSC) Firmware ( maybe samifirmware.com ) , then download the 512 pit file for the GALAXY S! and the flash the Firmware with pit file and repartition.

KUN1 said:
For the moment you can ignore the second thread
Find a 3 File (PDA, Phone, CSC) Firmware ( maybe samifirmware.com ) , then download the 512 pit file for the GALAXY S! and the flash the Firmware with pit file and repartition.
Click to expand...
Click to collapse
SOLVED
I couldnt sleep, so decided to have another bash at getting this phone going again.
Many many thanks to KUN1 for hunting down and PM'ing me the necessary Odin MD5 and PIT files to use for the method he posted above.
:victory:Success:victory:
You've been a life saver sir :good:

haha no problem

[Q] Distorted screen + won't boot

Hey guys,
Last night I looked at my phone (which had been on charge for a while) and noticed that it was on the first S3 boot screen. So I assumed it had crashed and got stuck whilst rebooting, so I held the power button to reset it.
Problem is, it came back to the same screen, except this time the black background of the image was distorted - lots of red/green/blue dots on it. So I tried again, and it came back even worse... The third time, it settled on a completely distorted image and is now seemingly stuck like that.
The phone isn't booting, so far as I can tell. If I try to boot to recovery, I just see the same screen. If I boot into download mode, it actually works - the screen is no longer corrupt and it responds to button presses. (Although itnerestingly if I continue to hold Home + Vol Down + Power once the download screen appears, then it does distort).
I have tried plugging it into my PC. I don't see it as a MTP device (no suprises there), and ADB can't find it. It is however recognised by odin. I tried flashing a stock rom via odin, but it complained that there was no PIT found. (Which if I understand if something to do with the partitioning of the device.
Any ideas on how to solve this? Should I find a PIT image for my phone and flash that and the ROM together?
For background, my phone is a i9305 and was running paranoid android (4.2, IIRC).

Dont touch pit
First flash stock rom via Odin

JJEgan said:
Dont touch pit
First flash stock rom via Odin
Click to expand...
Click to collapse
When I try that, I get the following error:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXALI5_I9305EVRALI5_I9305BVALI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
That was why I was wondering about the PIT file.
I have also added some pictures (they're pretty low resolution, unfortunately). The first is what I see when I try to boot normally - lots of white and black bands (the yellow and purple you can see is just an artefact of my crappy webcam). The second image is download mode, where I continued to hold down the buttons after it loaded, causing it to reload with the corrupted image (again, this is a bit distorted by the webcam - the text and image aren't blurred).

no access to system and recovery,i doubt theonly way is download mode.just try an stock rom with pit files,agree that the issue have something to with the partition.if you have backup the whole system,even flash a new rom,youdata will be back easy and soon ,so nothing to worried and no way else to go,good luck.
Sent from my GT-I9305

As pit breaks more phones than it fixes its not recommended .
But your phone has no pit so you you have choices .
Warranty void so it would have to be a service repair .
Or you can try flashing a pit file yourself if it fails you will need to buy a new motherboard .

I´ve had the same Problem on my S1.
I Flashed a whole Package from Samsung Stock Firmware ( PIT MODEM PDA ) in Odin.
After that it worked again, i´ve needed some try´s but after that everythin was normal.
Darkangel 142

Darkangel142 said:
I´ve had the same Problem on my S1.
I Flashed a whole Package from Samsung Stock Firmware ( PIT MODEM PDA ) in Odin.
After that it worked again, i´ve needed some try´s but after that everythin was normal.
Darkangel 142
Click to expand...
Click to collapse
Do you mean specifically that you had the same error in odin, or that your S1 had the distorted screen too?

Well, I tried flashing the i9305 pit file and had no luck. The re-partitioning failed to start at all, so it didn't ruin the motherboard, at least.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXALI5_I9305EVRALI5_I9305BVALI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Back to orange/samsung it is!
Thanks for your suggestions/help, everyone.

Any joy?
Hi,
I've posted about the same problem. Completely stuck on who to deal with and can fix it How weird to have happened so close and exactly same with black screen then stuck on white, Wonder if others are out there.
Link: http://forum.xda-developers.com/showthread.php?t=2526821

stuck screen
i have the same problem with my s3 and i couldn't do the download mode. im planning to restore on stock rom but i don't know how to fix this issues.
thanks,

einjelhart said:
i have the same problem with my s3 and i couldn't do the download mode. im planning to restore on stock rom but i don't know how to fix this issues.
thanks,
Click to expand...
Click to collapse
Hi mate,
If you can't get in to Download Mode because of boot loop:
Try forcing it by holding all 3 buttons until it turns off, should come up.
Failing that, you can eBay Galaxy USB Jig that plugs in and forces Download Mode.
If you can get to Download Mode, I have written a solution to flash just the ROM.
You can read my solution by following the Link above your post
Have a great day!
-Shaz

Same problem with my s3 ,but Odin doesn't recognise my device ,please help

Debanshu bebartta said:
Same problem with my s3 ,but Odin doesn't recognise my device ,please help
Click to expand...
Click to collapse
I had these prob before; device not recognize in odin, distortion screen with colorful line, stuck at boot logo & splash screen.. I tried flash lot of thing possible to fix it but all fail. Suddenly everything working fine after changing new battery.. Lol. Or maybe im just lucky.
Sent from my GT-I9305 using XDA-Developers mobile app

[Q] Can't Flash S3 (GT-I9305)

Hi,
I've been searching the net and this forum for a fix, it seems like a few people have had the same issue as me, but either their post is unanswered or they say they've fixed it but never say how.
My phone one day went into a infinite loop of the Samsung Splash screen and I tried fixing it by googling the issue (Over 5 months ago) which may have caused more issues for my phone in the end. I remember entering recovery mode and wiping everything on the phone, then nothing I did could fix the thing.
So I just stopped touching it and left it to collect dust and used my old iPhone 3. My iPhone 3 is now broken and I've come back to my S3, so at the moment:
I can't enter recovery mode on my phone (It just won't start in recovery mode at all)
I CAN enter download mode
I've tried using ODIN (v3.09, 3.07, 1.85) and changing multiple USB ports and I was finally able to get my phone to show up on Odin.
I then downloaded the stock firmware from sammmobile website (It took forever to download) Which I made sure was the right model (GT-I9305) and Carrier (Optus, Australia)
Which is filename: I9305XXALI5_I9305OPSALI5_I9305XXALI5_HOME.tar.md5
I tried flashing that firmware with Odin (All 3 versions) [I reset the phone and Odin after every failed attempt]
and I would get this error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXALI5_I9305OPSALI5_I9305XXALI5_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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
That was WITHOUT having a PIT file included and also the only things ticked were 'Auto Reboot' and 'F. Reset Time'.
Then I searched all over the internet and came across this PIT Partition file
the filename is: m3xx_i9305.pit
which I then used in the PIT section of Odin WITH and WITHOUT the previously mentioned Firmware and I would then get this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXALI5_I9305OPSALI5_I9305XXALI5_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
Click to expand...
Click to collapse
It would just sit on Get PIT for mapping for a very long time, longest I left it was an hour.
So I can't get it working that way, I also tried ADB Bootloading in the CMD prompt, but the device could never be found that way.
So after spending about 5 hours on this I'm resorting to just asking anyone on here for some help.
Thank you!
Phone Details:
Samsung Galaxy S3 GT-I9305
ODIN MODE:
Product Name: GT-I9305
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Knox Warranty Void: 0
RP SWREV:
Computer Details:
Windows 8.1 Pro
Intel 2700k @ 3.5Ghz
16gb Ram
Samsung USB Drivers Installed
If there is any additional information required please let me know. This is my first time posting here, so If I did anything wrong please let me know.
Thank you.

Unkiejay said:
Hi,
I've been searching the net and this forum for a fix, it seems like a few people have had the same issue as me, but either their post is unanswered or they say they've fixed it but never say how.
My phone one day went into a infinite loop of the Samsung Splash screen and I tried fixing it by googling the issue (Over 5 months ago) which may have caused more issues for my phone in the end. I remember entering recovery mode and wiping everything on the phone, then nothing I did could fix the thing.
So I just stopped touching it and left it to collect dust and used my old iPhone 3. My iPhone 3 is now broken and I've come back to my S3, so at the moment:
I can't enter recovery mode on my phone (It just won't start in recovery mode at all)
I CAN enter download mode
I've tried using ODIN (v3.09, 3.07, 1.85) and changing multiple USB ports and I was finally able to get my phone to show up on Odin.
I then downloaded the stock firmware from sammmobile website (It took forever to download) Which I made sure was the right model (GT-I9305) and Carrier (Optus, Australia)
Which is filename: I9305XXALI5_I9305OPSALI5_I9305XXALI5_HOME.tar.md5
I tried flashing that firmware with Odin (All 3 versions) [I reset the phone and Odin after every failed attempt]
and I would get this error:
That was WITHOUT having a PIT file included and also the only things ticked were 'Auto Reboot' and 'F. Reset Time'.
Then I searched all over the internet and came across this PIT Partition file
the filename is: m3xx_i9305.pit
which I then used in the PIT section of Odin WITH and WITHOUT the previously mentioned Firmware and I would then get this:
It would just sit on Get PIT for mapping for a very long time, longest I left it was an hour.
So I can't get it working that way, I also tried ADB Bootloading in the CMD prompt, but the device could never be found that way.
So after spending about 5 hours on this I'm resorting to just asking anyone on here for some help.
Thank you!
Phone Details:
Samsung Galaxy S3 GT-I9305
ODIN MODE:
Product Name: GT-I9305
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Knox Warranty Void: 0
RP SWREV:
Computer Details:
Windows 8.1 Pro
Intel 2700k @ 3.5Ghz
16gb Ram
Samsung USB Drivers Installed
If there is any additional information required please let me know. This is my first time posting here, so If I did anything wrong please let me know.
Thank you.
Click to expand...
Click to collapse
I've read you tried with different USB ports, OK, but did you try with a different USB cable when you use ODIN ? A brand new one ?

Wood Man said:
I've read you tried with different USB ports, OK, but did you try with a different USB cable when you use ODIN ? A brand new one ?
Click to expand...
Click to collapse
i am facing the same exact same probelm. i tried with different usb ports and cable results are the same . please someone help
:crying:

Errors with ATT S5 Active

I recently screwed up my S5 active and am desperate for help.
I only ever really occasionally screw with the OS, and I did a poor job of documenting what I did with this phone, so I will do my best to recollect exactly the state.
The phone is an AT&T Samsung Galaxy S5 active, model G870A
The recovery was some kind of robot icon that would show for maybe ~10 seconds at the start of boot (not a regular android, more square). I've tried searching for it to, as yet, no avail.
I'm fairly certain that the image I put on the device was KoolKit_S5_Active_V1.1.0.
I cannot recall if I used safestrap, towelroot, twrp, or some combination of these in order to get the above on the device. I have copies of each sitting in a folder I created for the phone.
The other day, SuperSU said it needed the binary updated. Me, being dumb, wanting the notification to go away, decided to appease it. It asked if I wanted to do so using recovery. I figured this would be easier, so I clicked "yes". And then my life got a lot more stressful.
When the phone boots now, it goes into ODIN mode and displays the message "android could not do normal boot. ODIN MODE".
I cannot get it to any other screen. Recovery, download mode, whatever. (I'm pretty sure this is download mode, but I cannot initiate any mode, it just goes into this).
I've been poking around on these forums. The first suggestion I thought might work was to use ODIN to (re?) flash towelroot. Or TWRP. I forget which one I tried, but it wound up resulting in a failure in ODIN, and a message on the screen stating something along the lines of "sys rev check fail no version".
I am very confused about what I need to be flashing using ODIN, but I have managed to cobble together that it has to be through ODIN.
I don't necessarily need links, I can find those, and I may already have the files. I'd really like to know which files it is that I need.
Do I need a firmware? What is the file format for that? tar.md5? etc.
Ideally I'd just like to get back to a regular run mode where my worst problem was a wonky USB port. I would deeply appreciate it if anyone could get me in that direction.
Thank you

It's working.
I plugged it in, tried to flash a PIT file. That failed. Apparently one does not flash those alone.
The screen said something like "check failed : PIT" ...
I went here:
http://forum.xda-developers.com/showthread.php?t=2799754
Followed the instructions. Got a failure. (This was, stupidly and fortunately, without restarting phone after pit failure).
Phone rebooted like nothing was ever wrong.
ODIN log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
Click to expand...
Click to collapse
P.S.: Previously unidentified robot was safestrap:
http://img.wonderhowto.com/img/96/6...hwiz-launcher-your-samsung-galaxy-s5.w654.jpg

Im glad you could fix it.
I also have a problem with a AT&T S5 active, the phone has horrible screen lag (even the booting screen is slow)
I tried doing a factory reset and also doing a downgrade to kit-kat using Odin, but the problem persists