Database Users

please,want to return to my original boatloader

i nserted a file named sgt-boatloader-patch-v1.00 apk to my galaxy tab 7 p1000 to break my phone protection but after installation, my phone screen became a logtudinal coloured line before start and cannt go to recovery mood or reboot, please help me to remove this boatloader and return my phone to work. as also the pc and kies cannt recognize my tab p1000

It you cannot get into download mode, then congratulations. You have got yourself a brick, and your Galaxy Tab is "GAME OVER".

IcedCube said:
It you cannot get into download mode, then congratulations. You have got yourself a brick, and your Galaxy Tab is "GAME OVER".
Click to expand...
Click to collapse
This pretty much. If you can't get into download mode by powering off the tab and trying to turn it on via Vol Down + Power, then it may indeed be bricked.
I believe there was 1 person who flashed the wrong kernel or something, and couldn't see anything on-screen, but was able to get into download mode (I think he had the wrong graphics driver), but idk.
If your tab is bricked though, you'll either have to checkout the "Unbrickable" mod, find someone else to perform the unbrickable mod for you, or talk to Samsung about it.

The main thing is to get into Download mode. Normally you see the Android-at-work screen in this mode, but there are other screens, and these will work as well. The Phone ! PC screen, though worrying, is a Download mode as well. Even a black screen showing nothing may be a Download screen. See for instance this helpful topic by k0sh.
That said, flashing a bootloader, or messing (patching) with one is one of the very few ways to hard brick your Tab...
If you can get the Tab recognised by Odin or Heimdall (remember to install their drivers first) in Download mode, you're good to go (flash that is). Heimdall has a Close PC screen function that's very handy, and may get you to boot a bricked Tab. Remember to charge it 4 hours or so before trying anything, even if it doesn't seem to show or do anything.
Reflashing to a ROM known to be able to boot is good if you can go to Download mode. Overcome can do this. Follow the flash to stock guide in this thread. I don't know if this will work for all Tabs, but it certainly works for a European GSM tab.

i also have the problem with "logtudinal coloured line" after patch the bootloader. but i can enter the download mode (power off,volume down+home+power on) and can see the 'android on work' logo.
i surf back the bootloader thread and found this.
"DO NOT USE THIS ON THE GINGERBREAD RELEASES ! THE SAMSUNG GINGERBREAD RELEASES DO HAVE SIGNED BOOTLOADERS, BUT THEY ARE NOT LOCKED. In other words, you can still flash custom kernels and such, and the bootloader patch will only break things, not fix them."
well, my gtab p1000 is 2.3.3 (dxjpi).
and the question, how to get back the original bootloader? i've read that bootloader come with rom. but doesn't really understand it (android newbie).

Flash the whole stock official rom
Sent from my GT-P1000 using XDA

priyana said:
Flash the whole stock official rom
Sent from my GT-P1000 using XDA
Click to expand...
Click to collapse
here what i did.
THIS IS MY EXPERIENCE WITH MY GALAXY TAB P1000 AND TRY IT (IF YOU WANT TO) WITH YOUR OWN RISK!
- downloaded "XXJQ1_2.3.3_P1000.zip" that included with ODIN3 1.3 and "gt-p1000_mr.pit".
- get gtab to dowload mode (android at work logo), run ODIN3 1.3 and COM detected.
- select pit and pda file (P1000XXJQ1_P1000XXJQ1_P1000XXJPZ_HOME.tar). using default settings (no re-partition), click start.
- odin result:-
<ID:0/029> Added!!
<ID:0/029> Odin v.3 engine (ID:29)..
<ID:0/029> File analysis..
<ID:0/029> SetupConnection..
<ID:0/029> Initialzation..
<ID:0/029> Get PIT for mapping..
<ID:0/029> Firmware update start..
<ID:0/029> boot.bin
<ID:0/029> Sbl.bin
<ID:0/029> param.lfs
<ID:0/029> gt-p1000_mr.pit
<ID:0/029>
<ID:0/029> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
- gtab reboot, now got "phone and computer logo link with exclamation mark in between. bricked my galaxy tab).
- then i look at ODIN3 1.3, device still detected. close ODIN3 1.3.
- downloaded "CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.zip" and "Odin3 v1.7.zip".
- run ODIN3 1.7, device detected. select pda file "CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar" (and i make sure the re-partition is NOT SELECTED).
- start, and here is the result:
<ID:0/029> Added!!
<ID:0/029> Removed!!
<ID:0/029> Added!!
<ID:0/029> Removed!!
<ID:0/029> Added!!
<ID:0/029> Odin v.3 engine (ID:29)..
<ID:0/029> File analysis..
<ID:0/029> SetupConnection..
<ID:0/029> Initialzation..
<ID:0/029> Get PIT for mapping..
<ID:0/029> Firmware update start..
<ID:0/029> zImage
<ID:0/029> Removed!!
<ID:0/029> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
- my galaxy tab now reboot, and now i dont see the "horizontal coloured line" @ boot screen @ animation messy one.
- using bootloader patch, checked the status. result:-
signed: pbl, sbl_backup
not signed: sbl, kernel
device condition nothing unusual, normal. i think i have repaired the bootloader back to original stock jq1.

Flashing a "full ROM" will amongst others flash the boot loader to the Tab. A full ROM is a ROM that includes all the parts necessary to create a bootable and working system on a possibly corrupted or otherwise non-working system. Your first attempt flashed the boot loader (boot.bin, sdl.bin), but failed on something else. It seems you repaired that by flashing a kernel. So yes, you have restored the boot loader.

ableeker said:
Flashing a "full ROM" will amongst others flash the boot loader to the Tab. A full ROM is a ROM that includes all the parts necessary to create a bootable and working system on a possibly corrupted or otherwise non-working system. Your first attempt flashed the boot loader (boot.bin, sdl.bin), but failed on something else. It seems you repaired that by flashing a kernel. So yes, you have restored the boot loader.
Click to expand...
Click to collapse
yes. at first i am so worried and curious to try repair the bootloader. after searching here in xda related to rom and bootloader,ive gained some confidence to do so. but,what is the "phone-triangle-pc" logo means?

It is just another "download" mode.
Sent from my GT-P1000 using XDA

You usually get this when something goes wrong during a flash, like when the flash doesn't even start, and you reboot the Tab. It seems that in such a case the Tab can't get to the normal download mode, and shows this image to let you know something's wrong. However, Odin in this mode is still able to connect to the Tab, so luckily you can flash again. That's why it's called a soft brick, and not a hard brick, because it can be fixed by software.

[Q] Issues installing ANY custom recovery on

NOTE: I'M STILL ON 4.2.2
So I've already rooted my device using motochopper and had no issues, but now I'm trying to install a custom recovery to no luck. I prefer TWRP but every time I try to install via Odin it fails with this message:
<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)
I've installed the latest drivers and ran ODIN as admin. I tried an older version of TWRP and even ODIN but end with the same result.
When I try via GooManager, it finds the correct version and takes me to the download page, but after the countdown it never downloads and eventually times out.
So then I decided to go CWM via RomManager. It found the correct CWM recovery image and said the install was successful, but when I try to boot into recovery I get the standard Android recover screen with "reboot system" etc.. with the little Android robot with a red triangle coming out of him.
Every method I've tried is failing and I can't figure out why

h_smith said:
NOTE: I'M STILL ON 4.2.2
So I've already rooted my device using motochopper and had no issues, but now I'm trying to install a custom recovery to no luck. I prefer TWRP but every time I try to install via Odin it fails with this message:
<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)
I've installed the latest drivers and ran ODIN as admin. I tried an older version of TWRP and even ODIN but end with the same result.
When I try via GooManager, it finds the correct version and takes me to the download page, but after the countdown it never downloads and eventually times out.
So then I decided to go CWM via RomManager. It found the correct CWM recovery image and said the install was successful, but when I try to boot into recovery I get the standard Android recover screen with "reboot system" etc.. with the little Android robot with a red triangle coming out of him.
Every method I've tried is failing and I can't figure out why
Click to expand...
Click to collapse
I'm assuming you are AT&T SGH-i337?
If so, are you using the LOKI'd versions?
If you don't know what that means, I suggest you do a search and some reading.
If you know what it means and have used the correct version, may be someone else can help.

Sounds like nothing is able to write to the recovery partition. You might consider flashing the stock firmware with odin and starting over.

jd1639 said:
Sounds like nothing is able to write to the recovery partition. You might consider flashing the stock firmware with odin and starting over.
Click to expand...
Click to collapse
so is there something wrong I may have done to cause this? I wish GooManager would just download and install as I've had luck using it in the past but it won't for some reason.

scott14719 said:
I'm assuming you are AT&T SGH-i337?
If so, are you using the LOKI'd versions?
If you don't know what that means, I suggest you do a search and some reading.
If you know what it means and have used the correct version, may be someone else can help.
Click to expand...
Click to collapse
Yes I'm on the AT&T version. I got the LOKI files from here

What baseband?
Sent from my i337 MF3 using tapatalk.

I'm not sure how much damage you have already done to your recovery partition so you made need to ODIN AMDL stock onto your phone before anything will work. However, here is the TWRP page for this device that also gives instructions on how to install via ADB or Terminal Emulator. Make sure you read EVERYTHING!
http://www.teamw.in/project/twrp2/174
Once you get TWRP working, you can flash a compatible version of CWM if you want to.
For future reference NEVER do anything to your phone that you don't read about here on XDA or at least see that people on XDA have tried it and verified it to work. Most sites (I'm not positive about the one you linked) just copy the information from XDA and claim it is there own. Usually, screwing it up some how. So never trust anything outside of XDA or that isn't directly linked to XDA. An example of something to trust is with the TWRP site. You can trust it as long as you make sure you have the correct information and version for your phone. That is your responsibility.
Also, make sure you search and read before asking questions or advice. Most information is already posted and you need to read about everything you are trying to do to your phone. If you follow these guidelines, you should do OK. If you try to cut corners or not search and read, you will end up in a mess. Good luck.

[Q]Flashing Lollipop help

i have been trying to install stock Lollipop on my device. i have followed both http://www.androidpit.com/how-to-get-android-5-0-lollipop-on-the-galaxy-note-3 and http://techbeasts.com/2015/02/14/update-galaxy-note-4-n910f-android-501-lollipop-official/ to the letter. This is also my fourth or fifth time using Odin. Every attempt has failed. i have tried Odin 3.10, 3.09, and 3.07 and got the same results:
Code:
<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> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone's download screen gave thisd message:
Code:
Secure Check Fail : sbl1
until i switched from "N9005XXUGBOB6_N9005XEOGBOA4_XEO" to "N9005XXUGBOA5_N9005XEOGBOA4_XEO" and also freezing any anti-theft app that may be locking my device somehow. Now the screen says:
Code:
Secure Check Fail : aboot
i am rooted (running Omega 24) and to be sure, i re-flashed auto-root
i have tried 4 different USB cables
No USB hubs, i am connected directly to my PC
Firewall, AntiVirus, and Anti Malware software are all off.
i have run Odin as admin
Reactivation Lock is not ticked
Some other things me screen says that may be of some help are:
Code:
QUALCOMM SECUREBOOT: ENABLE
followed by some coupling of letters and numbers and:
Code:
Write Protection: Enable
i am hoping that a factory reset can be my very last resort. i am contemplating reflashing my current Omega ROM and then retrying this.
Any ideas?
EDIT: Factory Reset did not change anything

Is your device unlocked or branded?

Joku1981 said:
Is your device branded or unlocked?
Click to expand...
Click to collapse
It should be unlocked. i unlocked it a while ago when i flashed my first ROM. i have been flashing Omega roms ever since. i cannot imagine my phone would lock itself back up...

billybag said:
It should be unlocked. i unlocked it a while ago when i flashed my first ROM. i have been flashing Omega roms ever since. i cannot imagine my phone would lock itself back up...
Click to expand...
Click to collapse
Odin gave you fail in the NAND. This mean that you have lost plenty of files in EFS. Try to restore your OMEGA backup.

Joku1981 said:
How you unlocked it? By IMEI or other method?
Click to expand...
Click to collapse
Damn, i don't remember. It seemed so long ago. i don;t suppose there is a way to check...
EDIT: while attempting a restore of a nandroid backup, i noticed something. The following backup files were missing:
.android_secure.vfat.tar and
.android_secure.vfat.tar.a

i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.

billybag said:
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
Click to expand...
Click to collapse
Do you have any EFS backup?

billybag said:
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
Click to expand...
Click to collapse
If you want to flash stock LP, I would just bite the bullet and do it and first get a working system. Then install Recovery and re-root - I use TWRP.tar file so I can flash it in Odin and the SuperSU zip file that I then flash in Recovery.
You don't say which N3 you have but are you sure you have the right ROM for it?
Did you turn off the phone and remove the battery for a bit THEN go into download mode?
Are you using v3.09 of ODin PC?
I've done mine twice for other reasons since LP came out - I untick the auto-reboot so after I flash the stock firmware I can flash TWRP - then it's boot into Recovery and install my custom ROM (I use Temasek's CM12) PA GApps and the SuperSU.zip, then set up the phone - usually I then Restore only Data from my latest TWRP backup but on occasion I've DL'd Titanium from Ply and used that to Restore my apps from extSD.

Journyman16 said:
If you want to flash stock LP, I would just bite the bullet and do it and first get a working system. Then install Recovery and re-root - I use TWRP.tar file so I can flash it in Odin and the SuperSU zip file that I then flash in Recovery.
You don't say which N3 you have but are you sure you have the right ROM for it?
Did you turn off the phone and remove the battery for a bit THEN go into download mode?
Are you using v3.09 of ODin PC?
I've done mine twice for other reasons since LP came out - I untick the auto-reboot so after I flash the stock firmware I can flash TWRP - then it's boot into Recovery and install my custom ROM (I use Temasek's CM12) PA GApps and the SuperSU.zip, then set up the phone - usually I then Restore only Data from my latest TWRP backup but on occasion I've DL'd Titanium from Ply and used that to Restore my apps from extSD.
Click to expand...
Click to collapse
That is what i am having problems with. i know how to flash custom roms. i was also able to flash stock KK when it came out. It is stock lollipop that i cannot get to flash. i am using an SM-n9005 (tmobile). i am going to try different firmware downloads (CSCs) and see what that does.
Also, i have tried Odin versions 3.07, 3.09, and 3.10

billybag said:
That is what i am having problems with. i know how to flash custom roms. i was also able to flash stock KK when it came out. It is stock lollipop that i cannot get to flash. i am using an SM-n9005 (tmobile). i am going to try different firmware downloads (CSCs) and see what that does.
Also, i have tried Odin versions 3.07, 3.09, and 3.10
Click to expand...
Click to collapse
Do you know your original firmware? I'm wondering because some versions have different sized partitions and flashing another type causes fails. i.e. I had a HK S3 and had to flash a PIT file before I could use European firmware. Might it be something along those lines?

Have practically the same situation...
The furthest I've got is the following
Code:
<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> 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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
But again, with any version of odin and any firmware (lollipop or kitkat) i'm trying to flash, it stucks with
Code:
<ID:0/003> Complete(Write) operation failed.
PS I also have
Code:
QUALCOMM SECUREBOOT: ENABLE
Write Protection: Enable
and my phone was originally locked to spanish vodafone.

Sorry for the delay. i just got around to giving it another shot and it worked. i found an official, made for TMOBILE, version of the firmaware.
Code:
N900TUVUFOB6_N900TTMBFOB6_TMB
for anyone else that may be having trouble. You can find it here: http://www.sammobile.com/firmwares/download/43850/N900TUVUFOB6_N900TTMBFOB6_TMB/
i was using n9005 firmwares, which is usually fine except int his case i needed a tmo one.
Thanks again for everyone's input. Hopefully this post can help someone else out now.

Phone won't boot, even into recovery mode

Hi all, im desperate for help here!!
I flashed Dr Ketans Rom to my Note 4 a couple of days ago but decided to try to go back to stock today due to a bug with my email. Anyway, a long story short, my phone failed the flashing process with odin whilst trying to flas the latest stock firmware from sammobile and then my phone refused to start up again.
I now get a screen telling me the firmware up grade process went wrong but I cant even reboot into recovery to install anything else.
I have tried flashing both TWRP and Philz recovery but both just flash the title screen on and off but never load up.
I have tried 2 firmware versions from sammobile and both end in fail, it seems like I cant flash any firmwares with odin which is a right pain because I cant get to recovery to install a zip file....
Please help, Im sooooo stuck!
Edit - this is the log from Odin if it helps anyone... Ive now tried software 4.4.4 also but nothing works.
<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> 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> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

I downgraded from that ROM (I'm guessing it was the S7 Edge ROM) to KK 4.4.4 a few days ago.
I think your problem is, that you haven't reinstalled the correct Bootloader and Modem files before you went back to KK.
I used the ones found here http://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
And everything worked.
What I did was, download the files and download the 4.4.4. firmware from SamMobile (the one I used is this (a BTU link, which is for the UK):
Code:
http://www.sammobile.com/firmwares/download/39930/N910FXXU1ANK4_N910FBTU1ANK2_BTU/
Direct link: http://dl.sammobile.com/OlFYQy8rLD1ULys8RzcnTUVYLzE9JkUpKyVXKDE8PFoOARlJUyA5RStXVEc1UlNHTVFaQ1NJEgkJHQBNSVpeQEZRXUM./N910FXXU1ANK4_N910FBTU1ANK2_BTU.zip
Then wipe your current setup in TWRP.
Reboot the download mode.
Install the Bootloader and Modem files in Odin.
Install the KK firmware in Odin.
Reboot and install TWRP in Odin.
Then either restore a previous KK backup or start from a clean slate.

0-0-0 said:
I downgraded from that ROM (I'm guessing it was the S7 Edge ROM) to KK 4.4.4 a few days ago.
I think your problem is, that you haven't reinstalled the correct Bootloader and Modem files before you went back to KK.
I used the ones found here http://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
And everything worked.
What I did was, download the files and download the 4.4.4. firmware from SamMobile (the one I used is this (a BTU link, which is for the UK):
Code:
http://www.sammobile.com/firmwares/download/39930/N910FXXU1ANK4_N910FBTU1ANK2_BTU/
Direct link: http://dl.sammobile.com/OlFYQy8rLD1ULys8RzcnTUVYLzE9JkUpKyVXKDE8PFoOARlJUyA5RStXVEc1UlNHTVFaQ1NJEgkJHQBNSVpeQEZRXUM./N910FXXU1ANK4_N910FBTU1ANK2_BTU.zip
Then wipe your current setup in TWRP.
Reboot the download mode.
Install the Bootloader and Modem files in Odin.
Install the KK firmware in Odin.
Reboot and install TWRP in Odin.
Then either restore a previous KK backup or start from a clean slate.
Click to expand...
Click to collapse
Thanks very much for your reply!
My problem now is that I cant reboot into any recovery (it sends the phone into a bootloop) and now Odin doesn't recognise my phone. Ive tried 2 versions of Odin and 3 cables all with no luck, strange as it used to connect fine.

sudburys said:
Thanks very much for your reply!
My problem now is that I cant reboot into any recovery (it sends the phone into a bootloop) and now Odin doesn't recognise my phone. Ive tried 2 versions of Odin and 3 cables all with no luck, strange as it used to connect fine.
Click to expand...
Click to collapse
No problem, at least it bumped your thread.
I'm sorry, I don't know the answer to your questions.
All I can suggest is taking it to a phone shop/service centre to have it reset. I appreciate that isn't always possible.
Hopefully, someone will help.

0-0-0 said:
No problem, at least it bumped your thread.
I'm sorry, I don't know the answer to your questions.
All I can suggest is taking it to a phone shop/service centre to have it reset. I appreciate that isn't always possible.
Hopefully, someone will help.
Click to expand...
Click to collapse
No probs...
Thanks for the try anyway

Tried to install TWRP, messed up bootloader - Not sure what to do next

I pulled out my old Verizon Galaxy S4 with the intention of getting a ROM on it that had XPosed. After some Googling, saw KingRoot supported it, so I used that app to root it. Then I tried to get TWRP installed. Their website said you could do it from their TWRP Manager app, so I tried that. It *said* it succeeded, but after that, my phone couldn't even boot at all.
So then I read up on using Odin to fix it. I tried to flash TWRP recovery from Odin (even finding a .tar version was a PITA), but I got this:
Code:
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Now, it boots normally, but I can't get into Recovery any more.
All I really want to do is get some custom recovery on there. Or even back to normal at this point. But I don't know how. I also tried flashing Clockwork Mod, but that didn't improve anything. What should I be doing now? Go back to stock and start over? Or am I installing the wrong recoveries from Odin (the TWRP one wasn't on their official download page, they only have .img files there, not tars). Or what?

Your first mistake was that you used Kingoroot. CF-Autoroot should be supported on your S4. As to the recovery, you want the latest version of TWRP, here. Download the 3.0.2-0 tarball (.tar), open Odin, select the PDA slot and point Odin to the tarball, then flash. That should resolve your recovery woes.

Make sure your TWRP is for that phone model. Verizon phones have locked bootloaders which make modifications harder.

Since the OP installed Clockworkmod, I have to assume his bootloader is one of the ones that can be exploited. But a good point, and I edited the link in my last post accordingly.

Strephon Alkhalikoi said:
Your first mistake was that you used Kingoroot. CF-Autoroot should be supported on your S4. As to the recovery, you want the latest version of TWRP, here. Download the 3.0.2-0 tarball (.tar), open Odin, select the PDA slot and point Odin to the tarball, then flash. That should resolve your recovery woes.
Click to expand...
Click to collapse
That link doesn't have any tarballs. Only image files. I couldn't find the tars on their site at all, and the only one I could find was one someone had as an attachment in a thread. No clue if it's the right one, though.
Strephon Alkhalikoi said:
Since the OP installed Clockworkmod, I have to assume his bootloader is one of the ones that can be exploited. But a good point, and I edited the link in my last post accordingly.
Click to expand...
Click to collapse
I tried to install Clockwork Mod, but it didn't work. I got the fail message above when trying to install the tar via Odin, and when I tried to use their app, it did the same thing the TWRP Management app did - it said it succeeded, but now I can't boot into recovery.

Do not install Clockworkmod. It's no longer maintained and has problems with more current ROMs. Install TWRP using that tarball you found on the forums. I believe TWRP on Verizon has no tarballs as it's expected to be installed using the TWRP Manager or a similar app in the Play Store.
If this does not work, you may have to start from scratch. Hopefully you kept a copy of the ROM with the exploitable bootloader so you can reinstall if necessary.