I think I bricked my S5 trying to update TWRP

[bgg1]

I have a VZW S5 running 4.4.1, rooted, with TWRP (don't remember which version, possibly 2.6.1). I wanted to do a full backup straight to an OTG USB drive, and it seemed like I needed an updated version of TWRP to be able to mount the OTG drive. So I installed the TWRP app and tried to flash the latest version (I believe it was twrp-3.2.1-0-klte.img, but I can confirm when I get home). After I selected the file and accepted, I rebooted to recovery from the TWRP app. And I got a screen that says:
RECOVERY BOOTING
SYS REV CHECK FAIL: NO VERSION
SECURE: SECURE VERSION FAILURE (recovery.img)
I get that screen if I power off and back on, or if I hold vol up and home when powering up. Either way, the phone then goes to a second screen with a large yellow triangle on it, and SECURE FAIL: RECOVERY in the upper left. Under the triangle it says System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help.
If I power on while holding vol down and home, I get
WARNING!
A custom OS can cause critical problems in phone and installed applications...
Vol. up CONTINUE
Vol. down CANCEL
Hitting vol. down restarts as above. Vol up gets me to a screen that says:
Odin mode
Product name SM-G900V
Current Binary Samsung official
System status Official
Reactivate Lock (KK) off
Qualcom Secureboot: Enable (CSB)
AP SWREV: S1, T1, R1, A1, P1
UDC Start
Downloading

I'm hoping that this means that I haven't completely killed my phone. What I would like to do is get it working again and rooted. All of my apps/data have been backed up with TiBu, so I figure restoring data should be easy once I'm back up. Ideally I would like to get the phone running something higher than Kit Kat (which was my original goal in all this, as a few apps I use no longer support KK.

Thanks in advance!

 

[TheFixItMan]

I have a VZW S5 running 4.4.1, rooted, with TWRP (don't remember which version, possibly 2.6.1). I wanted to do a full backup straight to an OTG USB drive, and it seemed like I needed an updated version of TWRP to be able to mount the OTG drive. So I installed the TWRP app and tried to flash the latest version (I believe it was twrp-3.2.1-0-klte.img, but I can confirm when I get home). After I selected the file and accepted, I rebooted to recovery from the TWRP app. And I got a screen that says:
RECOVERY BOOTING
SYS REV CHECK FAIL: NO VERSION
SECURE: SECURE VERSION FAILURE (recovery.img)
I get that screen if I power off and back on, or if I hold vol up and home when powering up. Either way, the phone then goes to a second screen with a large yellow triangle on it, and SECURE FAIL: RECOVERY in the upper left. Under the triangle it says System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help.
If I power on while holding vol down and home, I get
WARNING!
A custom OS can cause critical problems in phone and installed applications...
Vol. up CONTINUE
Vol. down CANCEL
Hitting vol. down restarts as above. Vol up gets me to a screen that says:
Odin mode
Product name SM-G900V
Current Binary Samsung official
System status Official
Reactivate Lock (KK) off
Qualcom Secureboot: Enable (CSB)
AP SWREV: S1, T1, R1, A1, P1
UDC Start
Downloading

I'm hoping that this means that I haven't completely killed my phone. What I would like to do is get it working again and rooted. All of my apps/data have been backed up with TiBu, so I figure restoring data should be easy once I'm back up. Ideally I would like to get the phone running something higher than Kit Kat (which was my original goal in all this, as a few apps I use no longer support KK.

Thanks in advance!

The screen you described is download mode
You enter it by holding Vol down home button power button

Download the latest firmware for your device from sammobile.com and then flash it via odin whilst your phone is in download mode & connected to the PC via USB by putting the firmware in the AP section of odin

 

[bgg1]

I thought so, but it just looked different than i remember it. Although last time I entered that was a few years back.
Is there a specific firmware that I should choose so I can re-establish root?
Also, is there any way to access data on the phone that I didn't have a chance to back up yet?

 

[bbsc]

Try to flash this via Odin first and see if the phone boots:
link removed

Unzip it first, of course.
Use AP slot in Odin.

 

[bgg1]

Actually i was about to post that after trying unsuccessfully to flash all sorts of TWRP versions, I finally decided I have no choice and have to flash the firmware. I chose the 4.4.2 NCG, because it's what I thought I was running before. After flashing and rebooting, my lock screen wallpaper was the same as I had left it. Cautiously optimistic I swiped the screen, and lo and behold, everything was intact! Except root, which i easily regained with towelroot. Only issue is I do not have TWRP any more. What's the best way to regain that?

 

[bgg1]

Try to flash this via Odin first and see if the phone boots:
https://mega.nz/#!3hNhEAoY!vkI12WptC0_OWiN4hpTxo5R_6KCLBJ76vUvvd98NL80

Unzip it first, of course.
Use AP slot in Odin.

Can't access this site from work. What is this?

 

[bbsc]

Can't access this site from work. What is this?

That was APA1 firmware only, without system partition.
Forget it if flashing ANCG gave you the necessary result.

You cannot directly flash TWRP at the moment because of the locked bootloader.
If you really need root, it would be wise to install Memory Brickbug Test from the Market and determine the CID of your phone.
It will help to plan the future actions.

BTW, there's a nice G900V section on the forum.

 

[bgg1]

So I have root again from towelroot. I don't remember how I originally did it, but I previously had TWRP, but never an unlocked bootloader. Does that make sense?

 

[bbsc]

I previously had TWRP, but never an unlocked bootloader. Does that make sense?

It's impossible on SM-G900V.
Most likely you had SafeStrap Recovery, they look similar.
But SafeStrap Recovery is a part of the system partition, not a real recovery as TWRP.

Unlocked bootloader on SM-G900V looks like on the screenshot (MODE: Developer)

 

[bgg1]

So I meant to post here but you beat me to it. On my drive home the other day it hit me that I had safestrap. Because once you boot to recovery it looks like TWRP, and it's been so long since first installing it, I simply forgot.
Anyway, at this point I regained root with towelroot, but was having difficulty installing safestrap, until I realized that I hadn't installed busybox or supersu. Finally got thos going, and after a couple of hours of multiple slowdowns, freezes, and crashes, I finally got everything back. So now I'm rooted and safestrap is back.
Questions:
Prior to this whole mess I had backed up the recovery image from safestrap. Is there any reason to restore that if everything seems to be working?
Also, I believe that TWRP can mount an OTG USB. Can this be done with safestrap?
Thanks

 

[bbsc]

Prior to this whole mess I had backed up the recovery image from safestrap. Is there any reason to restore that if everything seems to be working?
Also, I believe that TWRP can mount an OTG USB. Can this be done with safestrap?

I don't see any reason to repair a working thing.
Don't remember exactly, but seems it worked, for some version at least.

Again: install eMMC Brickbug Check from the market and see the CID of your phone.
It can be 11 or 15.
If it is 15 then you'll be able to unlock bootloader and flash TWRP.

 

[bgg1]

It is 15.
I think I'd like to get up to lollipop just for some app compatibility issues. I've seen a few different approaches. Any way to do this without wiping? or is that just wishful thinking? Besides the ability to flash ROMs (not a major interest for me, as with bloatware disabled or removed I kind of like Touchwiz), and install TWRP (again, not sure I need it if I can use safestrap for recovery), should i still look to unlock the bootloader? Better to do that now or after upgrade?
Thanks