yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] sekk:
And the method for all android version on this device is the same? Flashing .tar file using Odin?
[Galaxy S 4 i9505 Original Android Development] mattgyver:
You shouldn't even need to do that. You could use the official TWRP Manager to flash it to recovery without the need for Odin.
[Galaxy S 4 i9505 Original Android Development] sekk:
But I've never rooted my phone before. My s4 is still "original", the only thing I've done is buying a new front glass.

What to do in this case?
[Galaxy S 4 i9505 Original Android Development] mattgyver:
In that case, you'd want to search XDA for your specific S4 model's rooting process. There are a lot of different models of the S4. You could also search for whatever carrier you have S4 root. Example: "SGH-I337 root" or "ATT S4 root". It'll matter whether you've ever taken an over-the-air update, also.
[Galaxy S 4 i9505 Original Android Development] ...kuba...:
Hi, I saw that for newer models eg Galaxy S7, after installing TWRP installs no-verity-no-encrypt_ashyx patch " To disable forced encryption, mount internal storage(DATA) and disable dm-verity", does not dm-verity exist in s4??
[Galaxy S 4 i9505 Original Android Development] burnersk:
I am getting 404 not found errors, when I try to download TWRP (Americas and Europe mirrors): https://twrp.me/samsung/samsunggalaxys4internationalqualcomm.html
[Galaxy S 4 i9505 Original Android Development] ripee:
Please try the unified build linked right below the main link. That error is from TeamWin transitioning my builds from jfltexx to jflte, which is compatible with all Qualcomm variants, not just F, G, and M919.

If no one reports any stability or performance issues, TeamWin will release a proper official build, whose link I will update in the OP.
[Galaxy S 4 i9505 Original Android Development] smartt699:
no touch screen

boots up properly but the touch screen doesn't work. any idea?
[Galaxy S 4 i9505 Original Android Development] ripee:
Please provide more details. Does the touchscreen work with earlier twrps? Does it work in your rom? Which twrp version are you flashing on top of? Did you delete the twrp settings file like I wrote above?
[Galaxy S 4 i9505 Original Android Development] smartt699:
works with 3.0.2 jfltetmo nothing afterwards
[Galaxy S 4 i9505 Original Android Development] smartt699:
I've tried from stock same thing after half a second I'm unable to press anything. Can't unlock too. The back button seems to work that's it.
[Galaxy S 4 i9505 Original Android Development] ripee:
Please answer the questions I posed above. If you haven't tried everything that I mentioned in my questions, please do so.
[Galaxy S 4 i9505 Original Android Development] flyingsaucer75:
Same issue here I've tried also unified build. I've gt i9505 black edition. It doesn't happens always... It's a random issue. Maybe I've noticed this, if you have flashed something from external sdcard and you have not reselected internal sdcard also without flashing anything next time you boot inside twrp you have this weird issue. Just my 2 cents. Maybe related to mount points inside twrp.
[Galaxy S 4 i9505 Original Android Development] cavinrocks:
Hi, I installed TWRP on the S4 of a friend of mine. Just flashing TWRP via ODIN did not work, I think it was because I didn't unlock the bootloader before. Some tutorials for unlocking the bootloader did not work properly, so I used the "Unified" TWRP from the OP and then it worked perfectly! If someone has the same problems.
[Galaxy S 4 i9505 Original Android Development] Alan90:
good recovery update stability and replacing what cwm did is critical
[Galaxy S 4 i9505 Original Android Development] Pilac_III:
Same for me here! S4 jfltexx
[Galaxy S 4 i9505 Original Android Development] everett1911:
Same here too, S4 i9505g

Ok so I found out on my phone at least that the touchscreen works if you boot with no sd card in the sd card slot. Then you can plug in a sd card and do you thing. I hope that works for others.
[Galaxy S 4 i9505 Original Android Development] magicphone:
Is this the support thread? I have a hand-me-down S4 with god knows what recovery, and an obsolete, custom OS. I would like to flash the latest TWRP on it. I followed the manual as far as I could to no avail. My S4 is more than likely rooted.

By the way, I started with the TWRP app. I couldn't really find a manual for it so I don't 100% understand what it does at all, but for sure I was able to find all kinds of jflte** TWRP ROMs (are these recovery images called ROMs as well?) except for the ROM for my specific device (jfltexx).

Should I post this here at all? I know the layout of the XFA Forums is super confusing. At least to me.
[Galaxy S 4 i9505 Original Android Development] ripee:
Yes, this is the support thread. I am very sorry to hear about the daunting task of making sense of the inordinate amount of information on XDA.

From what you wrote, you are definitely in the right place :) As this is the TWRP thread, I woukd like to focus on getting you up to speed with the latest version. To answer your question, TWRP is a recovery, not a ROM. ROMs are the Android systems themselves. Think of the recovery as the starter motor of a car, while the ROM is the rest of the engine.

In order to assist you in the most straightforward way possible, please first tell me if you will be using a Windows PC, Mac, or Linux, with which to install TWRP and your ROM of choice onto your S4.
[Galaxy S 4 i9505 Original Android Development] magicphone:
ripee, thanks for getting back with me! Just to quote from your first post:

So TWRP isn't a recovery ROM, it's just a recovery. OK. Or maybe the proper terminology doesn't matter that much.

I'm on Linux. So this is the support thread for TWRP, the command line method, but the manual suggested, if I understood correctly, that first I should try the app. Meanwhile I figured out my hand-me-down S4 is rooted (obviously) and here's what I've written to the TWRP app support thread. If that's the app support thread.

Long story short, from the app's description it isn't clear to me what the app is supposed to do. I only assume it should install the latest TWRP to my phone with one or two clicks. My phone is rooted. I've found all kinds of S4 variants (jflte**) mentioned in the app, except for it mentioning my exact type of S4 (jfltexx). So how to proceed? Thanks!
[Galaxy S 4 i9505 Original Android Development] ripee:
You're taking the information listed under "XDA:DevDB Information" too literally. This is inserted as part of creating a thread as a DevDB and inserts the reference to its being a ROM because I created this thread in the S4 subforum.

With all due respect to TeamWin, forget the TWRP app! I will explain each and every step for you in this thread, but first please indicate the operating system on the computer you would be able to use with which to flash TWRP onto your S4, as this is the safest way of doing so.
[Galaxy S 4 i9505 Original Android Development] scott1256ca:
I need some help here. I have a galaxy s4 sgh-i337m running android 5.01

Once upon a time this phone was rooted with a stock rom, but I reinstalled a stock rom and never rooted again.

I'm trying to install twrp, but when I reboot, I just see the default screen.

I installed kies 3.1 and then ran odin 3.13

I'm trying to install from twrp-3.2.3-0-jfltecan.img.tar which I got from here

https://dl.twrp.me/jfltecan/

Here is the output from odin

ID:0/003> Added!!

<ID:0/003> Odin engine v(ID:3.1301)..

<ID:0/003> File analysis..

<ID:0/003> Total Binary size: 9 M

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> NAND Write Start!!

<ID:0/003> SingleDownload.

<ID:0/003> recovery.img

<ID:0/003> RQT_CLOSE !!

<ID:0/003> RES OK !!

<ID:0/003> Removed!!

<ID:0/003> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

Looks to me like it should have succeeded. But when I restart (home, vol up, power), I get the android system recovery screen. No twrp

I admit to being a noob to this stuff. Can you tell me what I'm doing wrong?

Thx
[Galaxy S 4 i9505 Original Android Development] Leone/kyleproxx:
I think you have to be rooted first.
[Galaxy S 4 i9505 Original Android Development] ripee:
Download and flash "jflte".tar, not jfltecan ;)
[Galaxy S 4 i9505 Original Android Development] scott1256ca:
Thanks for trying. Still doesn't work
[Galaxy S 4 i9505 Original Android Development] ripee:
Sorry, I forgot one important detail: when flashing TWRP from unrooted stock, you have to do it with the back cover off. This is because, as soon as Odin finishes flashing TWRP, and your phone vibrates, you have to pull the battery.

The reason for this is that the stock firmware will automatically re-flash its own stock recovery, negating the original flashing, which is what you reported.

You can then go straight into TWRP by booting with the volume up + home + power button combination, and releasing all three buttons as soon as you see "Samsung Galaxy S4 SGH-I337M".
[Galaxy S 4 i9505 Original Android Development] scott1256ca:
ok, I figured it out. I had to disable reboot in odin and boot immediately into recovery. So all is good now (I think).

Edit:

I guess I should have refreshed before I posted this. Thx got it :)
[Galaxy S 4 i9505 Original Android Development] ripee:
I find that pulling the battery is an easier step to take than digging through Odin's settings ;)
[Galaxy S 4 i9505 Original Android Development] eTaurus:
I have the same problem as these other guys. My touch screen works with TWRP 3.1.1.-0, in my ROM it even works with newer versions. No touch functionality with TWRP 3.2.1-0, 3.2.2-0 and 3.2.3-0, both the jfltexx and the unified variant. I'm flashing on top of the last working version. My phone is a I9505, maybe "black edition".

I tried to delete the settings but it made no difference. The only difference I see is on the first screen when the device boots. When installing a version newer than 3.1.1-0 there is no red text reading "Recovery is not SEandroid enforcing".

I hope there is a solution to this problem because I would like to install Pie on my phone.
[Galaxy S 4 i9505 Original Android Development] Finchy11:
Still no solution for touchscreen not working after 3.1.1?
[Galaxy S 4 i9505 Original Android Development] sinoukevin:
could not do a normal boot

so i'v did everything and the odin says it was a success but i have this msg when ever i want to enter the recovery mode (COULD NOT DO A NORMAL BOOT) and instead i find myself in the download mode
[Galaxy S 4 i9505 Original Android Development] SrJardel:
Removing the battery and booting in TWRP once will fix the stock re-flash for good or do I need to flash TWRP everytime I want to use it on stock non-rooted jlfte?
[Galaxy S 4 i9505 Original Android Development] bioc21:
Thank you very much Ripee. I was trying the Jlftecan TWRP, many different versions for the SGH-I337M but yours worked. It was flashed through ODIN. I did while being on a custom rom, and already having Clockworkmod installed and device rooted.

Thank you!
[Galaxy S 4 i9505 Original Android Development] droiduzr2:
Hey, I am having the same issue as you were. Can you link me to the exact TWRP you used or write the name of it.

Thanks!

I used the TWRP --- Download twrp-3.2.3-0-jfltexx.img

Use the ODIN version also.
[Galaxy S 4 i9505 Original Android Development] bioc21:
Hi Droiduzr2, for sure the twrp-3.2.3-0-jflte.img.tar

I am sorry I can't post links yet.

Are you using the most recent version of Odin?
[Galaxy S 4 i9505 Original Android Development] Gaeldrin:
Hi, I would like to bump this, facing basically exactly the same issue on my GT-I9505 (European version). Touch works in twrp-3.1.1-0-jfltexx.img and in ROM (OptLOS 14.1) even with twrp-3.2.3-0-jfltexx.img but I get no touch in the new recovery (tried the unified twrp-3.2.3-0-jflte.img too). Wiping data, dalvik, cache and internal storage leads to warning about system partition staying read-only and touch still not working. Tried with empty slots for both SD and SIM too.

I remember touch not working on various points in past too (for example some AROMA installers for ROMs). I can help with testing easily, I am a developer myself, just never did anything with Android.
[Galaxy S 4 i9505 Original Android Development] !hed0n1st:
Same issue for me... TWRP versions further than 3.2.0 are affected by this "touchscreen" issue.

As i am totally unable to understand what could be wrong, i have two questions :

1) Could it be related to a conflict between TWRP and the ROM installed ? I actually have the latest official 14.1 LineageOS on my i9505. Maybe users starting from stock ROMS do not encounter this. Something like a problem between TWRP and the LineageOS touchscreen "pilot" ...

2) If so, there are many custom ROMS for S4 i9505. Do they all use a generic "pilot" for touchscreen, or maybe some use customised ones ? The idea being to flash a ROM not using the same "pilot" as the LineageOS 14.1 jftexx official, then flash TWRP 3.2.3 and then be able to flash PIE based ROMS.

Maybe this "pilot" idea is dumb... don't know if it's correct for android.

Thanks for interest and maybe replies, sorry for my english.

Thanks for your work.

I noticed the disappearance of the red text about "SEandroid Enforcing" too on the revovery bootscreen...
[Galaxy S 4 i9505 Original Android Development] Gaeldrin:
Hello !hed0n1st (and possibly others). I've done some research on this issue and I am pretty sure that the problem is caused by a teeny tiny bit different hardware. I've got screen replaced, the new one is definitely a Samsung display but possibly for a different flavour of SGS4 or something. The original Samsung kernel handles it without problem but some customized kernels (like the ones used in new versions of TWRP) have problems.

I have managed to successfully install Pie on my i9505 using this recovery (found in an old AOSP thread) but my touch issues (touch not working after screen goes off) were present in all the JDCT Pie ROMs I tried (AOSP Ext, OptLOS, RR, DOT) so I have settled on OptLOS 15.1 for now. Ironically, the recovery itself has the same issue (touch not working after screen goes off) but it is possible to use it to flash everything without ever turning screen off. :D

As for your questions, the "pilot" you speak about is basically the kernel, that handles (or fails in handling) the hardware, touchscreen included.

There should not be any way of ROM and recovery conflicting since they are both basically independent "operating systems" on your phone.*

Changing the kernel seems like a good way to fix this issue. From what I understand, it should be pretty easy to put working kernel in any ROM (kind of "unzip->replace-one-folder->zip" process) but I don't have the time to try learning and debugging that on my own right now.

* On some phones (like SGS4), when you flash custom recovery on stock ROM, the stock ROM will try to revert the recovery back to stock. It is an interaction but not collision in the way you mean it.
[Galaxy S 4 i9505 Original Android Development] !hed0n1st:
Thanks for your explanation as it will save me a lot of unsuccessfull tries.

Will try to browse github repos for major changes between 3.1 and 3.2 according to your words. I know i'm a dreamer :fingers-crossed:
[Galaxy S 4 i9505 Original Android Development] droydr:
Just an FYI: I have a SGH-M919 (tmobile) for USA and the 3.2.3.0 version for jfltetmo does not boot into recovery on my M919. It just freezes at the Samsung splash screen whenever you try booting into recovery.

The jfltexx version for 3.2.3.0 does work on my M919 however. I haven't tried flashing a Pie ROM yet with it and just wanted to make sure it was safe to use the twrp 3.2.3 jfltexx version on my jfltetmo first.

Also, is there a reason the jfltetmo version for twrp 3.2.3.0 does not work on the jfltetmo? I've never installed a non-jfltetmo version of anything before on my jfltetmo so I just wanted to ask. Thank you.
[Galaxy S 4 i9505 Original Android Development] ripee:
Save yourself the worry and just use the unified jflte build. The other variants' twrps were built using outdated sources.
[Galaxy S 4 i9505 Original Android Development] droydr:
Which one is the "unified jflte build"? The OP contains a link to this page:

https://twrp.me/samsung/samsunggalaxys4internationalqualcomm.html

But from there, you still have to select a model and I don't see anything that says "unified build". Thanks!
[Galaxy S 4 i9505 Original Android Development] ripee:
International, Americas & China

Sorry, the TWRP page has been consolidated into a single collection of all these related builds, but the unified one is at the top.
[Galaxy S 4 i9505 Original Android Development] mohayta:
Hi, i was just trying to upgrade from 14.1 to 15.1. I needed to upgrade my twrp aswell as it was 3.1.1. I wiped everything except internal storage and flashed "twrp-3.2.3-0-jfltexx.img". I rebooted into recovery just to see my touchscreen is not working. I am in a position where i have no adb connection to my phone via pc, no OS installed on my phone and a touchscreen which started to not function after twrp flash. I have no idea where to start fixing this. Can anyone show me the way? Id appreciate it so much.
[Galaxy S 4 i9505 Original Android Development] ripee:
Pull the battery, boot into Download mode, flash 3.1.1 via Odin or Heimdall. Try again with twrp 3.3.0 jflte.
[Galaxy S 4 i9505 Original Android Development] stomarti:
My i9505 also has touchscreen issues. Before lock I manage to use the recovery in the following way:

twrp-3.2.3-0-jfltexx.img: When I touch the twrp splash screen on startup, the touchscreen is working afterwards.

twrp-3.3.0-0-jflte.img: Touchscreen is working. When I touch the twrp splash screen on startup, it won't work.

Besides, the touchscreen is working with twrp-3.1.0-0-jfltexx and lineage-14.1-20190212-nightly-jfltexx, even after locking.

If I can provide any logs, please tell me.
[Galaxy S 4 i9505 Original Android Development] ripee:
Because the exact same sources were used for both twrp-3.2.3-0-jfltexx and twrp-3.3.0-0-jflte, any discrepancies have to do with the updated twrp codebase.
[Galaxy S 4 i9505 Original Android Development] gkmac:
I too am blessed with an unresponsive touch screen with TWRP versions 3.2.0 and onward on my i9505, with the previous versions up to 3.1.1 working absolutely fine.

Have tried removing the SD card and/or SIM card, touching the TWRP splash screen logo, reflashing versions 3.2.3 and 3.3.0 in both the official TWRP app and in TWRP 3.1.1 itself, rebooting into recovery via the shutdown menu, rebooting normally while holding volume-up and home, powering the phone down completely and then booting while holding volume-up and home... all to no avail.

The touchscreen never even worked the very first time it was booted.

Admittedly wiping the whole of /data would be a bit drastic at the moment, but I thought I had found the TWRP settings file. I tried removing it in the Terminal using these commands...

cd /storage/emulated/0/TWRP/
rm .twrps

...which caused something about the system partition being read-only to appear on the next attempt, but the touchscreen is still unresponsive.

Can you confirm if the file I rm'd above was indeed the TWRP settings? If so, would they have been the 3.1 and/or 3.2 settings?
[Galaxy S 4 i9505 Original Android Development] EddoWagt:
Can anybody help me here? Trying to flash twrp with odin, but keep getting stuck on "recovery.img", tried different twrp versions, different versions of odin, usb ports, cables... nothing is working
[Galaxy S 4 i9505 Original Android Development] haustier:
OptLOS 15.1 is working for you?

Hi Gaeldrin,

i have exactly the same touchscreen issue. Did OptLOS 15.1 work for you? How did you settled back - old stock before?

After flashing to OptLOS 15.1 the touchscreen issue seems to be exist - at least on my device.

Going back to 14.1 or Stock Rom solves the issue.

My device has also a replaced, but original samung display - i guess it is a driver issue.

Any help or tips?
[Galaxy S 4 i9505 Original Android Development] graeffrocker:
Is there a tutorial for resize the /system folder in the rom through the twrp? Thx
[Galaxy S 4 i9505 Original Android Development] black.kahder:
Today I tried to update the TWRP on my old SGH-M919/jfltetmo. I downloaded the TWRP images from the official TWRP site.

The jfltetmo image doesn't work, but the jflte version does.

Given that the jfltetmo image doesn't work on the jfltetmo device, shouldn't it be removed?

Thank you for your support ripee.
[Galaxy S 4 i9505 Original Android Development] ripee:
Old builds remain up for posterity or whatever :P but the important thing is the unified jflte works.
[Galaxy S 4 i9505 Original Android Development] side:
the screen issues from twrp are fixed but changes are not pushed. i guess [MENTION=6005084]ripee[/MENTION] will have to cherrypick the new commits (when they are pushed) and rebuild/release again the build
[Galaxy S 4 i9505 Original Android Development] rjt2291:
Has the touch fix been merged yet? Doesn't look like a new build is available yet.

I also keep seeing people trying 3.2 and 3.3 on their devices and it not working. If the JFLTE version is unified, I think the others should probably be taken down, or at least just the dead versions, like 3.2 and higher for SGH-M919/JFLTETMO, they all fail to boot. 3.1 works "okay".
[Galaxy S 4 i9505 Original Android Development] ripee:
CHANGELOG

3.3.1-1: Bootloader check added for all compatible variants of jflte!

* Screen shutoff still doesn't work.
[Galaxy S 4 i9505 Original Android Development] mpit88:
3.3.1-1 does not ask for the password of an encrypted partition on an i9505. With 3.2.3-0 it works.
[Galaxy S 4 i9505 Original Android Development] wilsonhlacerda:
[MENTION=6005084]ripee[/MENTION] just a guess: maybe this is related to what arco68 wrote here about I9295 original (non unified) official TWRP:

https://xdaforums.com/showpost.php?p=79928753&postcount=24

By the way, arco68's one is working fine on encrypted I9295, I'm using it right now. Later I'll try your new unified.
[Galaxy S 4 i9505 Original Android Development] ripee:
Have you tried decrypting in 3.2.3, flashing 3.3.1, and re-encrypting?
[Galaxy S 4 i9505 Original Android Development] mpit88:
No, i wasn't trying anything to get it to work. I just downgraded to 3.2.3.

Edit: I'm using Optimized LineageOS 16.
[Galaxy S 4 i9505 Original Android Development] ripee:
Ok well the nature of these updates is that sometimes the way something is done is slightly changed that isn't fully compatible with the old way of doing the same thing, which is why I suggested decrypting, updating, and re-encrypting. It doesn't matter what rom you're using.
[Galaxy S 4 i9505 Original Android Development] stomarti:
On my device touchscreen issues got fixed in:

i9505-Optimized-LineageOS-16.0-Version11.0

TWRP-JDCTeam-3.3.1.0-build2.img

or official LineageOS-16.0
[Galaxy S 4 i9505 Original Android Development] darkglobe87:
I may be being a moron, but I can't get odin to do anything with the twrp .tar, I just get succeeded 0, failed 0. Could someone please kindly point out the giant obvious step I'm missing? Having an excrutiatingly bad day lol