yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] Droidriven:
If your device has 4.3 or higher then you should have a locked bootloader, that applies to all of Verizon's devices.

The people that are flashing this recovery were rooted and custom flashed before Verizon started putting locked bootloaders in their stock firmware and never took the 4.3 or newer updates, if they had taken the update they wouldn't be able to flash anything as far as I know. The newer devices with locked bootloader can only use Safestrap recovery and modified Stock ROMs, they can't use TWRP/CWM or custom CM or AOSP ROMs.

Ink'd from my KrAkEn'd S3

Are you sure this recovery is for your model number?

What method did you use to flash TWRP 3.0.0-0?

Ink'd from my KrAkEn'd S3

---------- Post added at 06:28 PM ---------- Previous post was at 06:24 PM ----------

No, you should have a locked bootloader, you'll never be able to flash TWRP or custom ROMs, it will hard brick your device if you try it. It won't be repairable either.

Ink'd from my KrAkEn'd S3
[Verizon Samsung Galaxy S 4] Mrgoldenboy:
Rockingham NC thanks for your answer. Now i have on backup TWRP on my phone. i create it with safestrap. How delete this backup?? When i have trying i received message "delete failed". Please have you a solution? What system recorvery can I use?:(

Thanks
[Verizon Samsung Galaxy S 4] Droidriven:
I don't know, I have never used Safestrap, I just know that Verizon Samsung devices have locked bootloader and have to use it instead of TWRP/CWM.

Do a search for:

"How to use Safestrap recovery"

Or

"How to delete backups in Safestrap recovery"

I'm sure there are threads here that explain all of its uses and features.

Ink'd from my KrAkEn'd S3
[Verizon Samsung Galaxy S 4] xc1097:
did both by

1. twrp app. yes i selected vzw gs4 - jflte

2. twrp recovery. downloaded .img and flashed.

both no go. but able to get back to 2.8.7 from the twrp app.
[Verizon Samsung Galaxy S 4] Youdoofus:
does anyone have a link for the safestrap for 5.0 for the S4?
[Verizon Samsung Galaxy S 4] gadget!:
I had a very similar problem trying to install 3.0 on my Verizon S4.

Someone suggested using flashify (from the Play Store). It worked like a charm for me.

sent from a Galaxy far far away.
[Verizon Samsung Galaxy S 4] gomangoman:
I think you mean flashify, not flash fire.
[Verizon Samsung Galaxy S 4] gadget!:
Autocorrect fail ?

Thanks for catching that, I edited my post.

sent from a Galaxy far far away.
[Verizon Samsung Galaxy S 4] Mrgoldenboy:
does anyone have a link for the safestrap for 5.0 for the S4? :(
[Verizon Samsung Galaxy S 4] Droidriven:
This should be what you're looking for

http://xdaforums.com/showthread.php?t=2441441

I'm not seeing anything specifically for 5.0 in the forums.

Ink'd from my KrAkEn'd S3
[Verizon Samsung Galaxy S 4] 3link22:
Work for i545 nc5 or no...
[Verizon Samsung Galaxy S 4] Youdoofus:
btw, even if you brick the device by flashing an unlocked bootloader, its not hardbricked. I "hardbricked" a vzw S3 trying to do exactly that, and all you need is an SD card the same size of the internal storage with the correct bootloader iso mounted to it and itll boot from the external storages bootloader .img. Then all one needs to do is some terminal commands to copy the bootloader img to the internal storage, pull the SD card out and voila. Fixed. Its a uncommon thing to have to recover from, but not all was lost on the S3, and i cant imagine that its different on the S4. I dont recommend flashing the unlocked bootloader, as it WILL brick your device and this method for the S4 is untested, but it worked on the SCH-I535, so i cant imagine it not working on the SCH-I545 as well. Anyways, anyone who bricked it in this manner, and feel that its a paperweight should try this and let us know.
[Verizon Samsung Galaxy S 4] Tech 4 9:
Uh oh...I think I messed up. Tried to update from 3.0.0-0 to 3.0.2-0 through twrp manager. It showed the right partition (as far as I could research) /dev/blockmmcblk0p21 so I hit yes. It said I already had the version installed (but I don't) and reboot was ugly. Scrambled screen and then pink bootloop screen. I was having a heart attack but long pwr button got me rebooted thankfully. Any help appreciated...WHAT HAVE I DONE?! I fear I've messed up twrp altogether. Vruamdk. fat32/ext4. Thanks in advance.
[Verizon Samsung Galaxy S 4] Tech 4 9:
Hello, scared here. Would this work for me? Tried upgrading from 3000 to 3020 through twrp manager. Reboot yields scrambled screen and pink bootloop screen. Luckily pwr button long press got me rebooted. I'm freaking out a bit. Thanks.

And If this will work, could I flashify the twrp 3.0.2-0 zip from current custom rom or would I have to go back to stock? Thanks again
[Verizon Samsung Galaxy S 4] Youdoofus:
i dont know why you wouldnt be able to flash the twrp via odin to get it back where you need it to be. Itll overwrite the current borked img you have
[Verizon Samsung Galaxy S 4] Tech 4 9:
The flash through flashify worked but I sure appreciate the response. I knew how to recover my old nc5 s4 but I'm new to mdk bootloader and don't wanna lose it. For future reference is it the AP slot in Odin?.. same as rom zips? Thanks again.
[Verizon Samsung Galaxy S 4] Youdoofus:
Yep, same slot :) also, in the off chance that you ever flash a full ROM in Odin, recovery and all, do not UNDER ANY CIRCUMSTANCE take the ota. It'll lock your bootloader. Similarly, flashing the wrong Odin tar can too
[Verizon Samsung Galaxy S 4] Tech 4 9:
YES. This is my fear. I've been looking for the proper stock restore tar file but most links are dead. I did find what I think is it but how would I know for sure? And even if I do would the root process still work? I'll see if I can find link for you're confirmation ..? It's buried in one of the 20 threads I'm following. ;) Thanks for input. Any info on preserving a three year old locked eol bootloader is much appreciated.

....and apologies for being off topic.

---------- Post added at 07:40 PM ---------- Previous post was at 07:14 PM ----------

So this is the most optimistic I've found..http://xdaforums.com/showthread.php?p=60419340.. rom link is still alive at least but the loki part I'm not sure about. I don't think this phone was ever loki'd but it is second hand. Whuchya think? (if you don't mind). I've posted in it as well.
[Verizon Samsung Galaxy S 4] Youdoofus:
Wouldn't the sammobile tarballs with the old basebands still have the unlocked bootloaders in them?
[Verizon Samsung Galaxy S 4] Scarface47:
Recovery Fail

Hi all,

i am trying to flash TWRP 2.8.7.0 tar file using odin in download mode and its keep saying fail.

Model S4 Verizon SCH-I545 4.4 VER
[Verizon Samsung Galaxy S 4] Youdoofus:
What recovery do you have currently? Also, when this happens the best thing to do is get a fresh download of the tar.md5 and/or try a different cable

---------- Post added at 08:21 AM ---------- Previous post was at 08:17 AM ----------

Oh, missed a part. Root does still work. I just rooted mine

isnt the 4.4.2 OEM ROM the last one with the unlocked bootloader? if so, wouldnt you be able to use the oldest one on this list?

http://www.sammobile.com/firmwares/database/SCH-I545/
[Verizon Samsung Galaxy S 4] Tech 4 9:
Yq know after your suggestion about sammobile I did go look look but I didn't recognize the MI1 so I wasn't sure if mdk was before or after. Boy it would be cool to know I could retain the ubl or restore if necessary. I softbricked my nc5 hundreds of times but could always Odin out of it. I'd like that same security with this mdk.
[Verizon Samsung Galaxy S 4] Youdoofus:
well, you could remove the bootloader part from the tar.md5 file and flash that via Odin. Heres a thread that touches on this for JB ROMs

http://xdaforums.com/showthread.php?t=2549357

heres the content of that post

Quick and dirty guide on how-to delete bootloader stuff that contain Knox from stock rom ( only works on Jelly Bean ) . On KitKat we have Knox 2.0 which is more harder to conquer

Only use it if u do not have KNOX WARRANTY in download mode

U need : a virtual machine or any linux environment . I use Vmware player + Linux Mint 16 x64

First download the rom from Sammobile and place it on your Desktop in a folder called work in linux

Let`s say we download Russia one for I9192

I9192XXUBMK4_I9192SERBMJ3_SER.zip

U can use this guide on other versions of this phone I9190/I9195

Firmwares that contain MK4/MK5/ML1/ML2/ML4/NA1/NA2 and so on from here have Knox bootloader inside

Only the name will be different but what is inside is the same

Only latest versions of firmware contain Knox Bootloader ( usually the ones released in late november/december 2013 )

Open terminal and type

Code:

cd Desktop

cd work

Now we need to extract it

Code:

unzip *.zip

U will get 2 files

First: I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md 5

Second: SS_DL.dll

Now again in terminal type:

Code:

rm -rf SS_DL.dll

tar -xvf *.tar.md5

After it will finish to extract we can delete the files we do not need

Code:

rm -rf aboot.mbn - bootloader ( knox included )

rm -rf sbl1.mbn - part of bootloader

rm -rf sbl2.mbn - part of bootloader

rm -rf sbl3.mbn - part of bootloader

rm -rf *.tar.md5

Now we can place it back in an archive. Choose any name u want i had chosen original name for reference only.

Code:

tar -H ustar -c rpm.mbn tz.mbn boot.img recovery.img system.img.ext4 NON-HLOS.bin cache.img.ext4 hidden.img.ext4 > I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar

After comes md5 stuff

Code:

md5sum -t I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar >> I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar

mv I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5

Now transfer it to your windows pc and flash it with Odin Make sure u do not rename the file at this stage or md5 checksum will fail

Double check it before u flash, look inside the archive that u don`t have those files u just deleted Maybe u did not move the correct file
[Verizon Samsung Galaxy S 4] Youdoofus:
have you looked at this?

http://xdaforums.com/showthread.php?t=2751461

i dont know if the links are dead, but it might be a place to look

just checked this download, and it works

http://darkmenace.simplified-computing.net/S4/Verizon/Verizon%204.2.2%20Stock%20Restore/Verizon%20SCH-I545%204.2.2%20562219%20Stock%20Restore.tar.md5

and heres the no-wipe

http://darkmenace.simplified-computing.net/S4/Verizon/Verizon%204.2.2%20Stock%20Restore/VRUAMDK_NoWipe.tar.zip
[Verizon Samsung Galaxy S 4] Tech 4 9:
Wow...great info. Thanks so much for all your efforts. Looks like I have quite learning curve as most of that info is gibberish to me. RUN. ME? Lots to learn. ?
[Verizon Samsung Galaxy S 4] Youdoofus:
Hey man, I appreciate that! Also, all I did is exactly what people have done that made this forum awesome to begin with, share info. If you need help understanding this stuff, lemme know!
[Verizon Samsung Galaxy S 4] deviousmrtaco:
Hey guys try this
[Verizon Samsung Galaxy S 4] Tech 4 9:
Anyone know where I can the above only in .tar? Cant believe how difficult it is to find a tar version. Thanks all.
[Verizon Samsung Galaxy S 4] flamadiddle:
Has anyone successfully installed TWRP 3.0.1.0 or 3.0.2.0 on the Verizon Galaxy S4 (jfltevzw)? I've bricked my phone 6 times trying to install them, each time following different official/unofficial instructions..

Installing via CWM = brick

Installing via TWRP manager = brick

Installing via TWRP 2.8.4.0 = brick

Installing via TWRP 2.8.7.0 = brick

Installing via ROM Manager = brick

Installing manually with dd in root terminal = brick

Installing via loki_flash = "This is not a valid loki image"

I've re-downloaded each file over and over, checking the md5 every time. Looks like 2.8.7.0 is the last version that works with this device, unless I'm missing something.

Good thing I have the MDK Odin tar. Re-hacking this phone every time is a pain though.

---------- Post added at 12:35 PM ---------- Previous post was at 12:27 PM ----------

This also bricked my device.
[Verizon Samsung Galaxy S 4] Droidriven:
Are you sure your device is jfltevzw? What stock android version/build number did your device have on it when you started or what stock version does it have now? Is the bootloader locked or unlocked? If it is locked, unlock it then flash, flashing TWRP will not work with locked bootloader.
[Verizon Samsung Galaxy S 4] flamadiddle:
Yes my device is jfltevzw. I've been running Google Play Edition and OctOS-MM ROMs on it (see my signature). MDK baseband, loki'd. The bootloader isn't unlocked because it can't be on this device, but loki gets around that. Notice the error message loki_flash gives above. It only does that for 3.0.1.0 and 3.0.2.0. Works just fine with all previous versions of TWRP.
[Verizon Samsung Galaxy S 4] Droidriven:
You're using other versions of TWRP on a Verizon locked bootloader? I've never heard of that, to my knowledge the vzw locked devices have to use Safestrap or Flashfire and can't use TWRP because it bricks the device. That's interesting, how are these devices able to use any version of TWRP at all on locked bootloader.
[Verizon Samsung Galaxy S 4] flamadiddle:
Thanks to Loki. Previous versions of official TWRP for jfltevzw are loki compatible up to version 2.8.7.0.
[Verizon Samsung Galaxy S 4] JettMartinez:
I was successful with Flashify after failing a couple other ways.
[Verizon Samsung Galaxy S 4] flamadiddle:
Using the .img file, this zip, or something else?
[Verizon Samsung Galaxy S 4] JettMartinez:
I used the .img downloaded from in the Flashify app.
[Verizon Samsung Galaxy S 4] flamadiddle:
I'm not brave enough to try this yet. I really don't want to have to re-hack the phone again. Did those other attempts you mention brick your device like they did mine? I couldn't even get to recovery. I just got a message along the lines of "The software on this phone has been tampered with. Please visit a Verizon service center for help." I could only get to Download mode, which meant I had to ODIN back to stock unrooted MDK every time.
[Verizon Samsung Galaxy S 4] JettMartinez:
Yeah, I was getting that error too. I didn't have to Odin. These where the directions I followed from post #593 in this thread:

"I had the same problem when I tried to flash twrp 3.0.1 from twrp 2.8.7. But it can be fixed. First enter download mode by powering on while holding the volume down key. When you get to the first prompt hit volume down again to cancel. This will cause android to boot. From there I used flashify app to flash twrp 3.0.1 and it worked properly."
[Verizon Samsung Galaxy S 4] flamadiddle:
Crazy. That worked. Looks like Flashify is the only way to get TWRP 3.0.x on this phone. I searched the thread but missed those few posts. Thank you!
[Verizon Samsung Galaxy S 4] Jalh:
Hello guys, I'm currently using the JFLTE-GPE 5.1 and I used goomanager to install that rom. I'm currently trying to install the latest TWRP but I get the "System software not authorized by Verizon Wireless...." msg. I know it gotta be with something about my kernel, but I was wondering if there is a workaround. Or should I just Odin MDK and start from 0 ?
[Verizon Samsung Galaxy S 4] flamadiddle:
Your solution is in the two posts above yours. :)
[Verizon Samsung Galaxy S 4] Jalh:
I tried flashing the image Flishify provides TWRP 2.8.6.0 and once it reboots and tries to go into recovery, it reboots and goes straight to OS. I'm not sure what could I possibly be doing wrong....
[Verizon Samsung Galaxy S 4] flamadiddle:
Flashify gave me the option of 3.0.2-0, downloaded it, and installed it for me. But... Now I remember. I used that GPE ROM for a while too, and I always had to change my build.prop so that apps would know which phone I actually have (GPE ROM sets it to International S4 by default). I had to flash the attached .zip in TWRP after ROM installation every time.

Try flashing DansGPEbuildprop4vzw.zip, and then see if Flashify finds the right TWRP for you.
[Verizon Samsung Galaxy S 4] Jalh:
Just flashed this through flyshify and instead of displaying the "software not authorized," it just reboots and goes straight to OS. I think i this point I'm just gonna Odin TAR MDK, then root and then flash twrp.
[Verizon Samsung Galaxy S 4] flamadiddle:
Did installation succeed, though? What version does it show when you boot into recovery now?
[Verizon Samsung Galaxy S 4] Jalh:
Sorry I dont think I explained myself. Flashify said flash was successful, but once it reboots to get into recovery stays at "booting recovery" for a few seconds and then reboots again into the OS.
[Verizon Samsung Galaxy S 4] Surge1223:
Who maintains this? Do they actually test these? Do they understand how loki differentiates between recovery and boot?

The last two twrp versions I had to loki myself, and one of them I believe was Loki'd to flash boot instead of recovery in the header.

Honesty there is no way who ever maintains twrp for jfltevzw tests the imgs before uploading.

Im a dev, and I only grab the official imgs from your site, and I check them for loki header, and dd them myself, I don't use any apps like flashify or anything, that some are suggesting they are having success with (probabaly because it auto loki's)

I went from 2.4.x all the way to the latest 3.0.2 successfully yesterday, but only because I'm a dev, I know the s4 very well, including the boot process, so it wasn't bad for me. But to an average user, this is poor management.

(p.s. Change the instructions on your website to dd to the by-name/recovery instead of the block device number for recovery)

Users:

Pro-tip: check all twrp images for loki yourself, if not loki'd then loki them using the recovery flag. Don't reboot into recovery after flashing, instead reboot to system one time first then try to reboot into recovery
[Verizon Samsung Galaxy S 4] bryantjopplin:
Your correct the newest ones aren't lokied. Only the 2.8.7 for me. I thought there was a Loki doki zip? Just got my s4 back from someone that had borrowed it.

---------- Post added at 10:21 PM ---------- Previous post was at 10:07 PM ----------

Edit. I was able to use flashify but the TWRP app would not work. Manual flash wouldn't work. Somewhere something is broke.
[Verizon Samsung Galaxy S 4] Surge1223:
I manually loki'd all of the available twrp images starting from 2.8.7.x to the latest, one or two were already loki'd properly, but in each case I never attempted to reboot to recovery after dd'ing the images, I always reboot once normally first.
[Verizon Samsung Galaxy S 4] mrtruckincowboy:
is the newest one loki'd somewhere i can download or you just did it yourself?

---------- Post added at 03:29 PM ---------- Previous post was at 03:26 PM ----------

last post was meant for surge sorry.

I cant find the delete button on here i must be tired
[Verizon Samsung Galaxy S 4] bryantjopplin:
Its fine but the app flashify must have a Loki version as it works for me
[Verizon Samsung Galaxy S 4] 3link22:
For i545 nc5 please?
[Verizon Samsung Galaxy S 4] dragonnet_86:
hi

i have sony xperia z

ineed the last twrp recovery flashaple for locked botloader plz plz plz

thanks alot
[Verizon Samsung Galaxy S 4] Jalh:
Hello surge, would you know how to flash the new TWRP from the GPE ROM ? I few comments back I wan't able to flash it and it might be because I flashed a loki'ed kernel in order to make the rom work a a few updates back. Anyway you could point me out to get back on track so i could flash AICP? Any help is appreciated.
[Verizon Samsung Galaxy S 4] Jalh:
UPDATE:

I was able to flash 2.8.7.0 from the TWRP manager without any issues. I'm not sure what is preventing the installation from 2.8.7.0 UP, but I finally got this to work.
[Verizon Samsung Galaxy S 4] mllora81:
Has anyone been able to flash 3.0.2-0?
[Verizon Samsung Galaxy S 4] FernBch:
When I had my S4 I flashed this one without issue:

https://romhut.com/addons/twrp-3-0-0-0-f2fs-jdc
[Verizon Samsung Galaxy S 4] stroupified:
Thank you! I've been looking all over for a loki version that works :D
[Verizon Samsung Galaxy S 4] Jalh:
Tried that one a few days ago and it seems to be the only working loki'd recovery that works. I'm not sure who is in charge for TWRP recovery for this S4, but they need to look into this issue.
[Verizon Samsung Galaxy S 4] tokuzumi:
Quick question, but what method are people using to flash the recovery? I have the 3.0.0 linked above, and I can't get it to flash via the TWRP app, and if I try to flash via fastboot, I don't see any devices when I type in fastboot devices in the command prompt (win 10).

I was able to get the recovery above to flash. Used the method in the site below;

https://www.progeeksblog.com/twrp-verizon-galaxy-s4-jfltevzw/

I had to modify the path used, as /sdcard/ was not a recognized path. Needed to be /storage/extSdCard/. But I now get "Start Up Failed. Your device didn't start up successfully. Use the Verizon software repair assistant"

I found this thread to fix that issue;

https://xdaforums.com/android/help/galaxy-s4-brick-start-failed-t3320805

But my question remains on how to install the recovery successfully?
[Verizon Samsung Galaxy S 4] bryantjopplin:
3.0.2 twrp for s4

Sent from my Nexus 6 with Pixel XL build.prop
[Verizon Samsung Galaxy S 4] Jalh:
answered in another post.
[Verizon Samsung Galaxy S 4] bryantjopplin:
3.0.2 Loki'ed

Here is a Loki'ed 3.0.2 recovery. I have yet to get a Loki'ed 3.1.0.
[Verizon Samsung Galaxy S 4] bryantjopplin:
Here is a zip file that is to be ran on a windows pc that will flash either the 3.1.0 or 3.0.2 twrp for you.

These are loki'ed btw.

All you need to you is have root for apps and adb endabled and usb debugging enabled.

So this means the newest roms with systemless root updates will not work as there is no root. AFAIK

Just extract and run the RUN_ME_FOOL.bat file located in the folder that was extracted.

Follow the on screen instructions and shazaam!

Also added some features to pull the existing recovery from the system to the sd card and from the sd card to the computer.

This will not fix the root issues with the newest roms tho. Still looking into that.

Any questions please feel free to ask.

BTW, I'm not a dev nor do I write code. I did do some 7zip hustlin tho. I just googled all day today because I was bored.

Main:

http://www.mediafire.com/file/pz2ci288vit6z11/JFLTEVZW_TWRP_SAUCE_V1.1.zip

Backup:

https://www.dropbox.com/s/8bzq5zj482afboj/JFLTEVZW_TWRP_SAUCE V1.1.zip?dl=0

Thanks!
[Verizon Samsung Galaxy S 4] JohnFranks:
Link is broke :(
[Verizon Samsung Galaxy S 4] bryantjopplin:
Updated links

Main:

http://www.mediafire.com/file/pz2ci2...SAUCE_V1.1.zip

Backup:

https://www.dropbox.com/s/8bzq5zj482...0V1.1.zip?dl=0

Sent from my Nexus 6 with Pixel XL build.prop
[Verizon Samsung Galaxy S 4] mllora81:
Confirmed Working!

I can confirm this works. Thanks! I am going to test the Lineage OS build that was just posted today. This is just a backup phone for me but nice to see it getting a fresh breath of air.
[Verizon Samsung Galaxy S 4] HowardZ:
I really hate it when the TWRP flashes a NON-LOKI recovery, and it did it again. It's a pain to fix the phone to boot again.

I WISH TWRP FOLKS WILL LOKI THE RECOVERY so we can use the convenient TWRP app.

I loki'ed it.

https://www.dropbox.com/s/lgrus1ijpiegg1u/twrp-3.1.0.0-jfltevzw_lokied.img?dl=0
[Verizon Samsung Galaxy S 4] HowardZ:
I wonder if anyone has tried encrypting their phones with LineageOS14.1 and then trying to apply LineageOS updates with TWRP?

This was a problem a few years ago, and I have not tried it recently.

I think the problem was that TWRP could not support both Cyanogenmod's encryption and also Samsung's encryption, and it chose to support Samsung.

Has anyone tried this?
[Verizon Samsung Galaxy S 4] bryantjopplin:
Well uploaded a lokied one a few days ago haha, post 663. But anyways to easily fix the phone is to boot to download mode then tell it to reboot, it will skip trying to get to the recovery. Makes it easier IMO.

Sent from my Nexus 6 with Pixel XL build.prop

EDIT : Also uploaded it medafire as the main.
[Verizon Samsung Galaxy S 4] Mythodix:
"This account's links are generating too much traffic and have been temporarily disabled!" Damn Dropbox locked the link because of too much traffic. Have another link?