yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] bryantjopplin:
Give me a few minutes. Ill have a new one updated soon.
[Verizon Samsung Galaxy S 4] Mythodix:
Awesome thanks! I'll check it out tonight when I have time to experiment!
[Verizon Samsung Galaxy S 4] bryantjopplin:
Here it is. It's a menu based batch file that uses adb to push it to mmcblock0p21. It seems to work in TWRP or in Android for me. If it doesn't work, you can install image from FILES folder via twrp itself.

Main:

https://www.mediafire.com/download/pz2ci288vit6z11

Backup:

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

I'll start using media fire from now own.
[Verizon Samsung Galaxy S 4] Mythodix:
Says "permission is denied" for the mmcblk0p21. Man this blows it's impossible for me to get any method working
[Verizon Samsung Galaxy S 4] bryantjopplin:
Are you rooted?

And primarily are you on mdk?

These two are a must.
[Verizon Samsung Galaxy S 4] Mythodix:
I am rooted and I'm not sure what the mdk is.
[Verizon Samsung Galaxy S 4] bryantjopplin:
The only bootloader for the vzw s4 that can have twrp without safestrap.

In terminal emulator do this

getprop|grep boooader

Does is say mdk in it?

---------- Post added at 11:21 PM ---------- Previous post was at 11:20 PM ----------

Similar to this
[Verizon Samsung Galaxy S 4] Mythodix:
It does not say MDK. This is what I got

http://i.imgur.com/aYIHj1Z.png
[Verizon Samsung Galaxy S 4] bryantjopplin:
Yeah you have OF1 and is NOT unlockable. This option will not work for you. Safestrap might work on that model, idk for sure, but that's where I would start.
[Verizon Samsung Galaxy S 4] nanodan:
These links are still invalid. They are using the ellipses.
[Verizon Samsung Galaxy S 4] bryantjopplin:
Updated the link and now it works. Working on a true site now. Don't won't to use the work one as we have a vps.

https://www.mediafire.com/download/pz2ci288vit6z11
[Verizon Samsung Galaxy S 4] nanodan:
Link worked, app worked. Thank you very much!
[Verizon Samsung Galaxy S 4] bryantjopplin:
Sweet thanks!
[Verizon Samsung Galaxy S 4] Mythodix:
lol of course this would be an issue. Anyways thanks for the help. I'll just end up waiting for the S8 then really start playing with this phone.
[Verizon Samsung Galaxy S 4] bryantjopplin:
S8 will be locked as well lol
[Verizon Samsung Galaxy S 4] Jalh:
[/COLOR]

hey, is there a way or guide to follow to I could loki future twrp releases ?
[Verizon Samsung Galaxy S 4] flamadiddle:
To avoid the hassle of loki, you can flash new TWRP images directly using Flashify (not to be confused with FlashFire). I just updated from 3.0.2 to 3.1.0. No problems. Just make sure your build.prop identifies your phone as jfltevzw.

https://xdaforums.com/showthread.php?p=67503259#post67503259
[Verizon Samsung Galaxy S 4] Plitskin5:
you sir are a hero. I just updated my TWRP before I wanted to go to sleep, and welp, I am still up flashing stock mdk because of this.
[Verizon Samsung Galaxy S 4] droidzer1:
Tried flashing the 3.1.1.0 to a Galaxy S4 VZ SCH-i545 with the TWRP app and now it says Start Up Failed - Your device didn't start up successfully. Use the Verizon Software Repair assistant ...... This phone was rooted and working perfectly....
[Verizon Samsung Galaxy S 4] bryantjopplin:
Just restart in the to the os then flash new recovery
[Verizon Samsung Galaxy S 4] droidzer1:
Was fighting with it for a couple hours and finally pulled recovery out of an OC1 tar and flashed it and got it running again. Oddly it booted once when I tried putting an NC5 kernel on it with Odin (which I think it had along with OC1 for the rest of the system). But after that it kept coming up with the "Failed start up" I was even trying (I was desperate :mad: ) the Verizon Update Assistant with it's Repair Assistant but it failed to install without errors and failed to run at all - no SURPRISE as it's Verizon. Note that I am a computer tech with several decades experience and my computer is a finely tuned machine that runs everything short of crapware. I do have it locked down pretty tight but something was failing in the VZ setup.

I've got Flashfire on it and have a backup with that but it's worthless if you can't get booted so wish I could get any version of TWRP on it but apparently that can't happen if you have an OC1 Rom on it? It might have been good to have that info in the opening post here if that is true.

I've had this phone awhile and probably knew TWRP wasn't an easy intall but with some 40 phones I tend to forget sometimes what works on what :o
[Verizon Samsung Galaxy S 4] bryantjopplin:
Yeah if you flash a bad img it will constantly reboot into the recovery until you tell it to restart from the bootloader (or odin can't remember)
[Verizon Samsung Galaxy S 4] droidzer1:
Yeah It didn't even boot into recovery as there was none. Pwr + vol up + home = Start up failed . The TWRP image was good but I had forgotten you can't flash TWRP if you are beyond the MDK bootloader. Everything after that is locked so I think it would be IMPERATIVE to have that info in the OP as it would save a lot of soft bricked phones. Love TWRP recovery but the TWRP app - ummm so-so - never had any luck with it. It would be nice if it detected a VZ locked bootloader so it doesn't brick your phone.
[Verizon Samsung Galaxy S 4] bryantjopplin:
Oh you are not on mdk makes sense.
[Verizon Samsung Galaxy S 4] bilgerryan:
Backup your backup to PC. Odin stock tar from www.sammobile.com, root again, flash backup with Flashfire.
[Verizon Samsung Galaxy S 4] droidzer1:
Oh I did get it fixed - mentioned elsewhere all I had to do was extract the recovery.img from a stock ROM and flash it and everything was okay. Still think it should be mentioned in the OP about not flashing TWRP to an S4 which has locked bootloader or anything after MDK.
[Verizon Samsung Galaxy S 4] kriss20:
Can someone help me remove jfltevzw gt9500 from my s4 Verizon
[Verizon Samsung Galaxy S 4] bryantjopplin:
Yeah I was confused as well
[Verizon Samsung Galaxy S 4] kriss20:
I tried to root my GT-I9500 but I failed many time but each time I boot it into download mode I see this

Product Name: SCH-I545

Current Binary: Samsung Official

System Status: Custom

Reactivation Lock: Off

CS8-CONFIG-LSB: 0×30

Secure Download: Enable

eMM: Burst Mode Enable

pls help me to correct it to SCH-I545 not GT-I9500 and root it also.
[Verizon Samsung Galaxy S 4] bryantjopplin:
So your saying you have a sch-i545 with a 9500 rom? What is your bootloader? Do you have terminal emulator? If so try getprop|grep bootloader in the terminal.
[Verizon Samsung Galaxy S 4] kriss20:
My bootloader: I545VRUGO1

PDA: 1950XXUHOG1
[Verizon Samsung Galaxy S 4] bryantjopplin:
Hmm you must have been running safestrap with an international rom. That bootloader is not unlocked. Try finding some older threads that have that factory ROM and set it back and use towelroot. Or just try towel root if you haven't updated it, it could work. I'm not sure of this particular bootloader.
[Verizon Samsung Galaxy S 4] Joe_6pak:
HELP! I tried to install the image for the latest TWRP recovery and am now getting the dreaded "System Software not authorized..." Verizon yellow triangle! I can start the phone ONLY if I hold Volume Down and Home when powering up! I never had these problems before I decided to use the app. This sucks - I have no custom recovery! AAAAGH!
[Verizon Samsung Galaxy S 4] bryantjopplin:
Try this within Android since your recovery is gone.

Of course unzip and run as admin.

110 ppl have downloaded and has had success. As long as you have root you should be fine.

https://www.mediafire.com/download/pz2ci288vit6z11
[Verizon Samsung Galaxy S 4] Joe_6pak:
Never mind - crisis averted. Used Flashify as suggested in Post #593 and it worked perfectly. Mucho thanks gomangoman! Thanks also to bryantjopplin for offering help!
[Verizon Samsung Galaxy S 4] generalnod:
Hello,

i have an S4 with an MDK bootloader that earlier today soft bricked ("System software not Authorized"... error) when I used the TWRP app to upgrade it to the latest 3.1.1(?). , from 2.6.3(?). I tried flashing some recoveries via odin with no luck and had to restore stock firmware and reroot.

Can anyone advise how to successfully install a current TWRP on the MDK S4, I'm wary of the app at this point and not seeing good feedback about it in general. I'm sifting through the threads here trying to sort out the best answer but if someone knows off the top of their head would appreciate the help.

cheers
[Verizon Samsung Galaxy S 4] bryantjopplin:
Are you rooted???

---------- Post added at 10:01 PM ---------- Previous post was at 09:59 PM ----------

I believe this still works if you have root. Actually you still have twrp right???

Try this.

https://www.mediafire.com/download/pz2ci288vit6z11
[Verizon Samsung Galaxy S 4] generalnod:
yep re-rooted and ready to go. TWRP is not installed anymore as I had to restore stock MDK firmware.

I was rooted previously, used many different ROMS, the TWRP app method didn't work, not really inclined to do the same thing twice so.... I see a lot of people referencing using Flashify

I"ll google on the file you linked thanks
[Verizon Samsung Galaxy S 4] bryantjopplin:
That is twrp I lokied myself. That is a file I created so no googling really lol. Just extract and run back file to put newest twrp on it.
[Verizon Samsung Galaxy S 4] DuckRuckus:
Deleted
[Verizon Samsung Galaxy S 4] DuckRuckus:
You are the man!!! Thank you so much!!! :good::good::good:
[Verizon Samsung Galaxy S 4] bryantjopplin:
No problem man.
[Verizon Samsung Galaxy S 4] kudos1uk:
Deleted, wrong forum.
[Verizon Samsung Galaxy S 4] Ibuprophen:
Just an FYI for those who may not be aware...

There's an update available on the Official TWRP website to "v3.2.2-0"...

Enjoy!

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[Verizon Samsung Galaxy S 4] JohnFranks:
Much appreciated! Your handy little utility saved the day!
[Verizon Samsung Galaxy S 4] bryantjopplin:
Is that the newest TWRP out for s4? I have not even looked lol

---------- Post added at 10:38 PM ---------- Previous post was at 10:37 PM ----------

Well I see the 3.2.3.0 is out. Might have to update this lol

---------- Post added at 10:39 PM ---------- Previous post was at 10:38 PM ----------

Haha NVM 338 dls now.
[Verizon Samsung Galaxy S 4] JohnFranks:
No worries... Seems like every time I try to update TWRP I end up with a refresher course on kernal flashing / reverting my phone to stock. Your 3.1 worked fine for upgrading LineageOS so I'm leaving it. lol. Thanks again!
[Verizon Samsung Galaxy S 4] Jalh:
I've must be doing something wrong or twrp is providing faulty loki'ed recoveries. I'm trying to go from a loki'ed 3.1.0.0 to the ["loki'ed" 3.2.3.0 as per twrp website](https://dl.twrp.me/jfltevzw/twrp-3.2.3-0-jfltevzw.img.html) When I boot into recovery, select install, then install image, pick the 3.2.3.0 flash to recovery and everything goes to normal . I boot into the lineage normally, then i try to boot into recovery and end up with the "system software not authorized by verizon wireless has been found on your phone" etc etc etc. What am I doing wrong here ?
[Verizon Samsung Galaxy S 4] iwearthebelt:
I ended up with the same problem. Just wanted to update the recovery on my old S4 because I hadn't done it in a long time. I did figure out that if you manually boot into bootloader, the once there you can press the volume up button and it will boot normally. If you figure out a fix for it please let me know, thanks!
[Verizon Samsung Galaxy S 4] Jalh:
Yeah, I was able to reflash my old recovery and things went back to normal. I hope someone could chime in and help. I was wondering is there is a way to manually Loki the new twrp releases so I could do so and try again.
[Verizon Samsung Galaxy S 4] iwearthebelt:
I'm sure there's a way to do it, if you know how to Loki the recovery. I don't know how to do it though. Did you flash the old recovery with fastboot? I made the mistake of updating the recovery with the twrp app. Which version of TWRP did you go back to?
[Verizon Samsung Galaxy S 4] Jalh:
I flashed the 3.2.2.0 with the official twrp. When shot hit the fan, I rolled back with the official twrp app to 3.1.1.0 I got from earlier this thread.

I found a thread describing how to Loki recoveries.IMG. I'm gonna try to make a script to automate it for new recoveries.
[Verizon Samsung Galaxy S 4] iwearthebelt:
Cool, wish I had the time to sit down a try to do that as well. If you figure it out let me know so I can give it a try.
[Verizon Samsung Galaxy S 4] bryantjopplin:
I have manually lokied the flashes. there is something wrong with them. It just boots to the twrp splash screen.

---------- Post added at 09:37 PM ---------- Previous post was at 09:34 PM ----------

No you dont flash the old recovery for sure. You need the aboot.img as well as the recovery.img. i have a flash.zip that i made that well loki the recovery from a lokied recovery. if that makes sense. So basically within working twrp, i flash the new twrp without rebooting then flash my zip. It lokies the new img. Then i can do a dd if of command and pull the img. thats how i got the imgs for my batch file to install them. But definitely something up with twrp.
[Verizon Samsung Galaxy S 4] iwearthebelt:
Yeah I'll have to mess around with it when I get some time, I'm on the road most of the week so I can only carry so many devices with me. Right now I have my Nexus 6P and 5X with me and Magisk had an update today but neither phone will take it. I manually downloaded the zip and flashed it in TWRP but all that did was put my phone into a boot loop. I'll have to figure out what's going on with that first.
[Verizon Samsung Galaxy S 4] bryantjopplin:
You will have to run the uninstaller per tjw instructions. Also disable all add-ons for magisk and test one by one
[Verizon Samsung Galaxy S 4] Ibuprophen:
Just an FYI in case you weren't aware.

TWRP v3.3.0-0 was just released.

Some notable changes were made too... :eek:

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle" AND Nickname for "My Ex-Wife"}.
[Verizon Samsung Galaxy S 4] Ibuprophen:
Just providing some additional information about the recent TWRP release.

The following are 2 locations reflecting any form of recently released Changelogs...

1) TWRP does provides an (uncomfortably brief) Changelog/bullet list here:

https://twrp.me/site/update/2019/04/15/twrp-3.3.0-0-released.html

2) The following is an excellent article with an outline of the new changes by the XDA News Editor in Chief:

https://www.xda-developers.com/twrp-3-3-0-release/

Enjoy and Good Luck!

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle" AND Nickname for "My Ex-Wife"}.
[Verizon Samsung Galaxy S 4] Ibuprophen:
I just wanted to let everyone know that TWRP v3.3.1-0 was just released a few days ago for this device.

The following link is to their brief Changelog /Announcement regarding this release.

https://twrp.me/site/update/2019/05/22/twrp-3.3.1-0-released.html

Enjoy and Good Luck! :)

~~~~~~~~~~~~~~~

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Verizon Samsung Galaxy S 4] Ibuprophen:
I wasn't sure if anyone was aware of this but, Official LineageOS 16.0 builds for the jfltevzw device began rolling out a few days ago.

https://download.lineageos.org/jfltevzw

It looks as though the following is the Official LineageOS 16.0 support thread for them too.

https://xdaforums.com/showthread.php?t=3954912

Good Luck! :)

~~~~~~~~~~~~~~~

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Verizon Samsung Galaxy S 4] HowardZ:
It looks like the Offical TWRP app does not even list our phone anymore.

Sad...
[Verizon Samsung Galaxy S 4] Ibuprophen:
That's weird...

The jfltevzw is not listed within the following link of Samsung devices...

https://twrp.me/Devices/Samsung/

... and it's available (and kept up-to-date) on the following download link within the Official TWRP website for the jfltevzw device

https://dl.twrp.me/jfltevzw/

This is important since the Official LineageOS for the jfltevzw was just recently re-added with the LineageOS 16.0.

This is something that [MENTION=912474]Dees_Troy[/MENTION] may want to look into.

Also, the Official TWRP App lists the devices from the first link (above) which is why it's missing.

You should be able to obtain the latest version of TWRP for the jfltevzw on the second link (above).

Good Catch! :)

~~~~~~~~~~~~~~~

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Verizon Samsung Galaxy S 4] HowardZ:
TWRP has bitten me too many times by not be LOKI'd.

I used to LOKI it myself, but recently screwed it all up, and had to load all the MDK original firmware, root it, etc.

Way way too much work because he doesn't want to LOKI it.

When TWRP someday needs updating, I'll go look for CWM or something else.
[Verizon Samsung Galaxy S 4] Ibuprophen:
I understand you... Some individuals prefer certain criteria that some are happy with as is.

I've never really gotten into the realm of "Loki" but, I only have a general understanding about it.

_____

Also, for everyone else here too...

The TWRP situation just got the attention from one of the Official TWRP Maintainers as reflected on the following thread post.

https://xdaforums.com/showthread.php?p=80109455

EDIT: The following thread post provides an "IMPORTANT" clarification by the same Official TWRP Maintainer...

https://xdaforums.com/showthread.php?p=80109567

... In short, there's a UNIFIED TWRP build for the "jflte" that includes the "jfltevzw" device.

I would like to refer everyone who uses using the TWRP for the jfltevzw device to go to the following Official TWRP thread for the jflte device that's inclusive with the jfltevzw device as well.

[RECOVERY][OFFICIAL] TWRP 3.3.1-1 [jflte] by ripee

Thanks for your time and understanding with this! :)

~~~~~~~~~~~~~~~

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Verizon Samsung Galaxy S 4] HowardZ:
I just download twrp 3.2.3-0, lokied it, and the Verizon S4 can never boot up the recovery - it hangs.

I downloaded twrp 3.1.1-0, lokied it, and it works.

I suspect that all versions of twrp after 3.1.1-0 DO NOT WORK, because the developer never tests what he builds.

After all, if he did test, then he'd have to LOKI it, and we would not need to LOKI it. So he must just build twrp without trying it on a real phone.

As I said before, someday if/when 3.1.1-0 just won't handle the latest LineageOS, then it's time to use a different recovery.

Our Verizon S4 is just not supported anymore by TWRP.
[Verizon Samsung Galaxy S 4] HowardZ:
OK,

I have found that the solution is to download from this webpage:

https://eu.dl.twrp.me/jflte/

I downloaded twrp 3.3.1.1

This appears to be a UNIFIED S4 TWRP build for all the variants of the S4.

I assumed it has not been loki'd and so I loki'd it.

It boots up, and appears to work.

I did a LineageOS 16.0 update with it - rebooted into TWRP, did the update, rebooted back to LineageOS system.

For those that need it loki'd, my dropbox:

https://www.dropbox.com/s/w6mxda3rd7sgiaa/twrp-3.3.1-1-jflte-lokied.img?dl=1
[Verizon Samsung Galaxy S 4] Ibuprophen:
[MENTION=4581832]HowardZ[/MENTION], The link you had provided, though not incorrect but, is to the EU server for TWRP. Those in the US uses a different server link.

The following are now the Official threads that reflects them to be unified ones for the various jflte device variants...

[OFFICIAL] [NIGHTLIES] LineageOS 16.0 by npjohnson

[RECOVERY][OFFICIAL] TWRP 3.3.1-1 [jflte] by ripee

... Those are where you'll be able to obtain Support and Guidance for the jfltevzw device from each one.

I hope that I had explained this okay via text... :thumbup:

Good Luck!

~~~~~~~~~~~~~~~

Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
[Verizon Samsung Galaxy S 4] ismatovvsanjarbek:
Hi, My s4 failed twrp flash. How to unlock bootloader jfltevzw? I need help. Recovery broken!!!!
[Verizon Samsung Galaxy S 4] XfrostX:
Yeah I'm running into the same issue. Unable to boot into recovery after using it once. Any solutions yet?
[Verizon Samsung Galaxy S 4] drt054:
Made a backup and restored it after flashing one of the alpha AOSP roms. When I went to restore, thought i lost it. But came across it but the date said it was in 1970. Not a big deal but restored back to stock no issues.

---------- Post added at 03:33 AM ---------- Previous post was at 03:27 AM ----------

I just been using goomanager's boot to recovery command.
[Verizon Samsung Galaxy S 4] oc3rulz:
do we know if we have fastboot permissions (after root) to just flash the recovery.img via fastboot using ADB? if not I am gonna try
[Verizon Samsung Galaxy S 4] firsttimer44:
I

Goomanager is fine but what if we happened to flash a rom and it bootloooped? How would we get back into recovery?

I made a back up of stock but I'm too scared to flash something in fear of a never ending bootlooop and not being able to get back into recovery.

Edit: nvm I'm a noob and figured it out. Hold volume up + home + power. As soon as it vibrates let go of the power button but continue holding the other two.
[Verizon Samsung Galaxy S 4] Eric214:
well before you put in a recovery you should get the stock odin file so you can use odin to flash it back from the PC. Then you'd root again and flash recovery and could then restore your current backup you had before the new rom flash. That is the pain in the ass way of doing it. That is why I was asking how to enter recovery from boot not Goo manager.
[Verizon Samsung Galaxy S 4] Mercutio5:
So easy. Thank you TWRP.
[Verizon Samsung Galaxy S 4] bik2101:
I think I must be stupid, because I can't figure out how to get this installed through goo manager. I searched twrp then downloaded the one for verizon...and now I'm not sure what the next step is.
[Verizon Samsung Galaxy S 4] holla420:
Go into goo manager go to settings look for install open recovery script. Wait for it to download. Once its done hit boot into recovery and that's it. :cool:
[Verizon Samsung Galaxy S 4] bik2101:
thanks! will give that a try
[Verizon Samsung Galaxy S 4] theboo7:
I missed it about three times. Soon after it downloads (took me 15mins over wifi), you'll see a little pop up at the bottom of screen saying something along the lines of "Recovery Installed"
[Verizon Samsung Galaxy S 4] cybertec69:
On my S3 it takes about 3 min for a ROM like CM 10.1, the stock ROM takes a bit longer. I always choose the external Micro SD card location, then I copy and paste the file to my PC "just in case". TWRP is fantastic.
[Verizon Samsung Galaxy S 4] coolsilver:
Have any of you with boot loops had TWRP try to fix root for you?

I've backed up, installed a mod and had it ask if I wanted to fix. I said NOOOOOO.

I still have root and no issues.
[Verizon Samsung Galaxy S 4] bik2101:
for what it's worth, i said yes and have no issues also.
[Verizon Samsung Galaxy S 4] imablackhat:
I had it fix and have no issues and it hasn't prompted again since.