yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] ripee:
Ahh, that's because I used the android-7.1 branch in the omnirom/android_bootable_recovery repo to build the lineage-based twrp. I'll use the android-8.1 branch and post a link.

Edit:

twrp-3.2.1-0-jfltexx_from_lineage.img

twrp-3.2.1-0-jfltexx_from_lineage.tar

This should be the proper version 3.2.1-0. :P
[Galaxy S 4 i9505 Original Android Development] Szwajowy:
Yep, it's proper version and it's working just fine with my SD Card's :P
[Galaxy S 4 i9505 Original Android Development] ripee:
So that means that I have to re-build my twrp repo based on the lineage jf-common repo rather than an older branch of the twrp repo.

Thanks very much for your testing and feedback! :) I'll let you know when my next build is ready.

For the time being, I'll rename it to twrp-3.2.1-0-jfltexx and change the links in the OP to point to it.
[Galaxy S 4 i9505 Original Android Development] Szwajowy:
No problem. I'm at your service ! :)
[Galaxy S 4 i9505 Original Android Development] ripee:
twrp-3.2.1-0-jfltexx_trial.img

twrp-3.2.1-0-jfltexx_trial.tar

I went over each and every file in my repo and made the code align with the LineageOS jf-common repo. The only major change I made was to use the system.prop from Lineage because mine was too minimal.
[Galaxy S 4 i9505 Original Android Development] Szwajowy:
Still nothing, maybe we will move it to private message, because it may be a long yourney xd
[Galaxy S 4 i9505 Original Android Development] ripee:
If you wish to go to pm, fine, but this way other people will know why the SD card isn't mounting. I have to think of what to try next...
[Galaxy S 4 i9505 Original Android Development] ripee:
I added the following lines to BoardConfig.mk:

TW_INTERNAL_STORAGE_PATH := "/data/media/0"
TW_INTERNAL_STORAGE_MOUNT_POINT := "data"
TW_EXTERNAL_STORAGE_PATH := "/external_sd"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "external_sd"

This was taken from an older TWRP branch.

twrp-3.2.1-0-jfltexx_trial_2.img

twrp-3.2.1-0-jfltexx_trial_2.tar
[Galaxy S 4 i9505 Original Android Development] Szwajowy:
Still same problem, nothing changes.
[Galaxy S 4 i9505 Original Android Development] ripee:
This time, I removed the above lines and replaced them with this one:

TW_USE_TOOLBOX := true

twrp-3.2.1-0-jfltexx_trial_3.img

twrp-3.2.1-0-jfltexx_trial_3.tar
[Galaxy S 4 i9505 Original Android Development] Szwajowy:
That's not it. :/

EDIT: Try this - TW_INCLUDE_NTFS_3G := true
[Galaxy S 4 i9505 Original Android Development] stylemessiah:
Im just wondering why anyone would be trying to use an ntfs formatted sdcard or would you fiddle about to add support for it....never in all my years of android have i ever wanted to, let alone needed to access ntfs on an adroid device

An android device is an android device, leave its sdcard formatted to a proper mobile filesystem 100% supported by the kernel (hint: ntfs isnt)

If youre taking an sdcard formatted to ntfs in and out of a device to attach it to a completely different OS (Windows) youre doing android and mobile devicing wrong

I wouldnt waste a second of my life trying to shoehorn something thats not supposed to be there into TWRP, but thats just me
[Galaxy S 4 i9505 Original Android Development] Szwajowy:
Yea, it is suported by official TWRP and OP wants to be maintainer of official TWRP 3.2.1, but bringing NTFS suport is obsolet ? Seems right..
[Galaxy S 4 i9505 Original Android Development] stylemessiah:
Main point being the very first version worked 100% for a correctly formatted sdcard, which would cover 99.999 recurring% of people out there...since then theres been god knows how many versions to try and meet the needs of exactly 1 person

Madness

That 1 person should format their sdcard to a sane filesystem like the other 99.999% recurring and get on with life
[Galaxy S 4 i9505 Original Android Development] ripee:
Ok I made the change and I'll run a build in the next couple hours.

I'm all for maximizing compatibility, even for the 0.00001% of users ;) If this doesn't work, no idea what else to try.

Edit:

twrp-3.2.1-0-jfltexx_trial_4.img

twrp-3.2.1-0-jfltexx_trial_4.tar

This includes the above line.
[Galaxy S 4 i9505 Original Android Development] ripee:
You're referring to the very first TWRP image under the link to my BasketBuild that I posted in the OP? Because the image that's under the link right now is the lineage-based twrp, which understandably works 100% but cannot be submitted for official support given TeamWin's requirement of a their Jenkins builder being able to build from a dedicated repo.
[Galaxy S 4 i9505 Original Android Development] Szwajowy:
NTFS is working, SD Card is recognized and I can choose it.

ExFat is not working :/

EDIT: Actually in TWRP based on lineage source, ExFat was working and NTFS not, sooo xd
[Galaxy S 4 i9505 Original Android Development] ripee:
Perhaps removing

TW_NO_EXFAT_FUSE := true

would help? trial_5 is coming up.

twrp-3.2.1-0-jfltexx_trial_5.img

twrp-3.2.1-0-jfltexx_trial_5.tar
[Galaxy S 4 i9505 Original Android Development] Szwajowy:
You know what ?...

All working now ^^ Both ExFat and NTFS, great work :)
[Galaxy S 4 i9505 Original Android Development] ripee:
Great! I'll update the TeamWin repo and ask them to run a test build. I'll update the OP and post an announcement when it's ready.

For now, I'll rename trial_5 to the regular file name and update the links in the OP.
[Galaxy S 4 i9505 Original Android Development] ripee:
[MENTION=5660616]Szwajowy[/MENTION], have you had a chance to try the preview build? Any differences in performance or stability from my build?
[Galaxy S 4 i9505 Original Android Development] Szwajowy:
I think everything is okay. :)
[Galaxy S 4 i9505 Original Android Development] ripee:
Great! I'l ask TeamWin to cook a proper official build :D
[Galaxy S 4 i9505 Original Android Development] darkrevlis:
The twrp link from the OP is the last test with all possible formats working?
[Galaxy S 4 i9505 Original Android Development] hougga:
Morning!

So the new build is working very well with Oreo and previous OS (KK L N ??)

Have a nice journey mates !
[Galaxy S 4 i9505 Original Android Development] Exodusnick:
will there also be for the i9515?
[Galaxy S 4 i9505 Original Android Development] visio999:
Hi Guys,

thank you very much for your hard work. At the moment, I got a Galaxy S4 (Model: GT-I9505; FCC ID: A3LGTI9505) with TWRP 3.0.2.0 (JFLTEXX).

If I'm trying to update either via Odin or via TWRP to a newer version (3.1.1.0 or 3.2.1.0), the phone isn't able, to boot into recovery anymore. After going

back to 3.0.2.0, everything is working properly again. Anyone a suggestion, what I'm doing wrong? Thanks very much for your help :)

Edit:

Maybe, it's because of outdated firmware. Currently, I'm using I9505XXUHOJ2: https://www.sammobile.com/firmwares/galaxy-s4/GT-I9505/DTM/download/I9505XXUHOJ2/60888/

Am I able, to install I9505XXUHQK1 from ripee or will it break the phone?

Edit2: I installed I9505XXUHQK1 and everything's working perfect :) Thanks for your great work!
[Galaxy S 4 i9505 Original Android Development] PREM1Z:
Hi!

Thank you for your work, but something wrong with this version. When i want to install los 14,1 ver10 aroma with 3.2.1 twrp, its not install just done message after 1-2 second. With 3.1 its properly installed. Can u check for this what is wrong?
[Galaxy S 4 i9505 Original Android Development] BobLoblawslawblog:
Hi,

Since upgrading to the latest TWRP 3.2.1.0 on my i9505, the touch interface in recovery doesn't work. It hasn't crashed as I can see the temperature reading moving.

I had 3.1.1.0 running and touch working fine, then back in December upgraded TWRP when the new version was released. Soon discovered there was a build issue causing freeze (https://xdaforums.com/showpost.php?p=74816373&postcount=1256) so reverted back to 3.1.1.0.

I checked checksum of downloaded image, and flashed 3.2.1.0 recovery via steps in the original post of this thread.

Next logical step anyone? Reflash the .img via ODIN perhaps?
[Galaxy S 4 i9505 Original Android Development] ripee:
Sorry but I'm not entirely clear as to what's working and what's not. Did updating your bootloader and modem fix 3.2.1? Was your phone unable to boot into recovery on 3.0.2 with the old bootloader, but did boot on the new one? Is it the same with 3.2.1, could not boot into recovery with the old bootloader but could with the new one?
[Galaxy S 4 i9505 Original Android Development] triads:
dd install method doesn't work

The dd install method described in https://twrp.me/samsung/samsunggalaxys4internationalqualcomm.html does not work:

On my GT-I9505 with LineageOS 7.2.1 (bootloader and modem are XXUHQK1) there is no /dev/block/bootdevice/by-name/recovery device, and hence the of=... part of the dd command just fails.

[MENTION=6005084]ripee[/MENTION]:

Please provide a working description for the dd install method.

Can we use Heimdall to flash twrp and if so, what are the exact steps?

Thank you.
[Galaxy S 4 i9505 Original Android Development] ripee:
Replace that line with:

/dev/block/platform/msm_sdcc.1/by-name/recovery

It's in recovery.fstab in the source repo. I'll update the info on the site.

You can use Heimdall, which is why I linked it in the OP. I believe the instructions are in the link as well.
[Galaxy S 4 i9505 Original Android Development] triads:
Thanks for the clarification on the correct use of the dd of=... argument.

As for your Heimdall link in the OP: The link points to the Heimdall download site and does not provide further information on flashing a recovery image. But Google is your friend ;) ... I've found the following post on stackexchange.com which fully addresses my question: https://android.stackexchange.com/questions/97304
[Galaxy S 4 i9505 Original Android Development] jojolafrite:
Hi, i face the same issue with 3.2.1.0.

At first boot, touch is working fine. Second reboot (from recovery, key combo or from Lineage reboot menu), touch doesnt work anymore. I have to flash again the recovery with Odin to get touch working.

I tried to flash 3.2.1.0 from recovery (3.1.1.0), Odin 3.09, Odin 3.13. No matter the method, the result is the same, touch doesnt work on second reboot

touch is working fine on 3.1.10

My phone is a i9505
[Galaxy S 4 i9505 Original Android Development] ripee:
If it works the first time, but not after rebooting, it may be caused by twrp not saving its settings file properly. The best way to fix this is to clean flash completely, including wiping the data partition. The settings for 3.1 and 3.2 are saved separately, and the settings don't translate particularly if there is enough of a difference in the source code. This is most likely the case with my builds because I created my sources from scratch, borrowing from LineageOS's repos and not from older TWRP repos. I did it this way because the most recent Lineage code is proven to work on an ongoing basis, with more recent Lineage builds than the date of TWRP 3.1's release.
[Galaxy S 4 i9505 Original Android Development] jojolafrite:
Thanks for your reply.

I bought this phone two days ago. It had stock ROM and stock kernel. I flashed twrp 3.2.1.0 with Odin, then I booted into the recovery (on the first boot touch was working properly) then i performed a complete wipe (all partitions were checked) then I installed lineage OS from twrp. Then I tried to wipe dalvik cache from TWRP (second boot on recovery) and as the touch wasn't working, I had to flash again twrp with Odin, and touch was working OK after the flash. Then on the second boot, the issue appeared again. As I didn't want to flash twrp each time I had to boot to recovery, I downgraded to 3.1.1.0

Thanks for the job you're doing on 3.2.1.0 and for your support, i hope my feedback helps
[Galaxy S 4 i9505 Original Android Development] ripee:
Flash 3.2.1-0 then save the logs on an sd card. It's under the Advanced menu.
[Galaxy S 4 i9505 Original Android Development] ripee:
[MENTION=4867526]jojolafrite[/MENTION], do you have any problems in using my twrp?
[Galaxy S 4 i9505 Original Android Development] jojolafrite:
Still facing the touch issue :) you asked me for the recovery.log, so I've posted it after flashing 3.2.1.0 from 3.1.1.0
[Galaxy S 4 i9505 Original Android Development] ripee:
Ahh, I totally forgot that I asked you for a log lol ok I'll take a closer look at it as soon as I can.
[Galaxy S 4 i9505 Original Android Development] Catscratch:
Thanks.

Today I flashed latest version through twrp itself without problems.

Everything is working.
[Galaxy S 4 i9505 Original Android Development] jojolafrite:
My firmware is I9505XXUHOJ4, build date is 21.10.2015, maybe i should update it to solve the touch issue
[Galaxy S 4 i9505 Original Android Development] ripee:
Your firmware has nothing to do with the stability of twrp, but you might as well update it, why not? May I ask why you're trying to flash cm-12? Lineage-14.1 does exist for the i9505 ;)
[Galaxy S 4 i9505 Original Android Development] jojolafrite:
I never tried to flash cm12. I went from stock rom (or at least what appeared to be stock rom when i bought the phone) to LOS 14.1, downloaded from lineage website

Indeed I see in the recovery.log the following lines, but i have no idea why it prompts this while I'm with the last LOS 14.1 update:

ro.cm.device=jfltexx

ro.cm.display.version=12-20170517-UNOFFICIAL-jfltexx

ro.cm.version=12-20170517-UNOFFICIAL-jfltexx

ro.cm.releasetype=UNOFFICIAL
[Galaxy S 4 i9505 Original Android Development] ripee:
Did you wipe all the partitions in twrp 3.1? If not, cm-12 could be left over from a previous flashing a long time ago. Did you buy the phone new or used?

Go back to twrp 3.1 and wipe all partitions except the sd card. Then try flashing 14.1 from the sd card.
[Galaxy S 4 i9505 Original Android Development] ripee:
Unified jfltex twrp 3.2.1-0!

I have linked my unified jflte twrp build in the OP. Our thanks to JDCTeam for the inspiration and jf-common device tree.
[Galaxy S 4 i9505 Original Android Development] velosa:
has support for oreo?
[Galaxy S 4 i9505 Original Android Development] ripee:
Yes, just like jfltexx 3.2.1-0 also supports oreo.

Speaking of oreo, I know a TWRP thread is no place to post a rom link, but I'm strictly testing the waters with this one: lineage-15.1-20180513-UNOFFICIAL-jflte.zip

I won't have access to an i9505 to test it myself for a few weeks. This is the local manifest I used to build it, my thanks to JDCTeam for the device trees and blobs, which I subsequently modified slightly both for it to compile with the official jf kernel and to remove their non-lineage extras. I am in no way unaffiliated with JDCTeam so please DO NOT report any problems with this build to them. I will remove this post once I have more time to dabble in the rom's sources in the next little while.
[Galaxy S 4 i9505 Original Android Development] velosa:
I have one and I will test the rom. Thanks
[Galaxy S 4 i9505 Original Android Development] velosa:
[MENTION=6005084]ripee[/MENTION]

I installed the rom very quickly, first thing was an inrregular boot. that is, the screen went black for a bit and then started normally. second question, I am using the QK1 modem and the sim card is not recognized. version of unknown baseband, I do not know why.
[Galaxy S 4 i9505 Original Android Development] angelillom:
Compañero instale el TWRP 3.1.2.0 y una rom 7.1.2 Nougat , bueno probe varias Nougat en mi S4 Gt i9505 pero ahora tengo un par de problemas , si lo apago tengo que entrar desde Recovery ...reiniciar y entra el sistema pero al apagar lo intentas encender y aparece la bateria pero nada y despues lo pones a cargar y en ocasiones carga pero otras veces lo en chufas y no carga sino que se come la bateria ., es decircomo si no estuviese el cable puesto , hay algo de Sofware ..... pero no se si ten dra algo que ver con el "Boot_Loader" , pero no se

Ayuda , Porfavor

MUCHAS GRACIAS y espero me podais aconsejar
[Galaxy S 4 i9505 Original Android Development] velosa:
[MENTION=6005084]ripee[/MENTION]

Hi, on the first page this is in the changelog that the last recovery is 3.2.1-1. But in the official page the last one is to 3.2.1-0.
[Galaxy S 4 i9505 Original Android Development] ripee:
I will fix this discrepancy. I must've had another device's twrp in mind.
[Galaxy S 4 i9505 Original Android Development] angelillom:
Ante todo MUCHAS GRACIAS y si no corresponde aquí este mensaje porfavor decicme donde enviarlo .

Versión Banda Base XXUGNG8

Compañeros instale la Rom 7.1.2 Nougat Resurrection Remix Os v5.8.5 - 2018-03-20 jftexx y lo instale desde cero, borrando todo, con TWRP 3.1.2.0 y tengo instalado Magisk Manager 16.4 sin ningun Substrato , instale gapps - arm 7.1 pico 20180506.zip no he modificado el Kernel solo esta Rooteado como e mencionado antes , el movil es un SAMSUNG GALAXY S4 Gt i9505 pero ahora tengo un par de problemas que me tienen desesperado, tengo que entrar desde Recovery ... reiniciar sistema y enciende , Si lo apagas y lo intentas encender aparece la batería pero no arranca el móvil de modo normal y corriente como devería hacerlo, es decir con el móvil apagado y despues lo pones a cargar y en ocasiones no carga como si no hubieras enchufado el cargador. ........ tienes que reiniciar y conectar el cable desde el arranque hay que vigilar que no se ha desconectado, hay algo que no se como reparar ... pero no se si es TWRP o la Rom

Ayuda, Porfavor

MUCHAS GRACIAS y espero me podais aconsejar? porque no se como solucionarlo
[Galaxy S 4 i9505 Original Android Development] workingmachine:
Screen timeout does not work

[MENTION=6005084]ripee[/MENTION]

Thank you for your working on TWRP.

Backup and recovery with TWRP 3.2.1.0 works well.

Unfortunately the screen timeout feature does not work.

To reduce the screen wear of the oled display it is better to switch the screen off during the long backup process.

Please get the screen timeout feature working again.
[Galaxy S 4 i9505 Original Android Development] ripee:
Can anyone else confirm this bug?
[Galaxy S 4 i9505 Original Android Development] droidman99:
i have the same bug
[Galaxy S 4 i9505 Original Android Development] ripee:
Please follow Dees-Troy's instructions in this thread and post the output here. [MENTION=2638973]bigbiff[/MENTION], could you please shed some light on this issue? Would TW_NO_SCREEN_BLANK := true help in this case?
[Galaxy S 4 i9505 Original Android Development] workingmachine:
Output:

~ # [6nfind /sys -name brightness

/sys/devices/virtual/sec/sec_touchkey/brightness

/sys/devices/platform/mipi_samsung_full_hd.2305/lcd/panel/panel/brightness

/sys/devices/platform/msm_fb.526593/leds/lcd-backlight/brightness

/sys/devices/platform/i2c-gpio.12/i2c-12/12-0066/max77693-led/leds/leds-sec1/brightness

/sys/devices/platform/i2c-gpio.12/i2c-12/12-0066/max77693-led/leds/torch-sec1/brightness

/sys/devices/platform/i2c-gpio.16/i2c-16/16-0020/leds/button-backlight/brightness

/sys/devices/platform/i2c-gpio.21/i2c-21/21-0030/leds/led_b/brightness

/sys/devices/platform/i2c-gpio.21/i2c-21/21-0030/leds/led_g/brightness

/sys/devices/platform/i2c-gpio.21/i2c-21/21-0030/leds/led_r/brightness

~ # [6n
[Galaxy S 4 i9505 Original Android Development] ripee:
[MENTION=5247843]velosa[/MENTION], go ahead and try the 3.2.1-1 build that's linked in the OP. [MENTION=7551530]Lenny Bard[/MENTION] confirms that screen brightness is fixed, but the screen still doesn't turn off after a set amount of time.
[Galaxy S 4 i9505 Original Android Development] ripee:
[MENTION=5247843]velosa[/MENTION] [MENTION=7551530]Lenny Bard[/MENTION], please test 3.2.2-1 in the OP. I didn't merge the brightness slider into the official repo in time for 3.2.2 because I want to wait until we fix the screen shutoff as well.

Perhaps 3.2.2-1's screen shutoff may work anyway?
[Galaxy S 4 i9505 Original Android Development] Lenny Bard:
For me Screen timeout still doesn't work in 3.2.2-1..
[Galaxy S 4 i9505 Original Android Development] Adidas108:
true.
[Galaxy S 4 i9505 Original Android Development] ripee:
What was the latest version in which screen shutoff worked? Please give me all 4 digits of the version number so I can focus on the exact branch in the old sources.
[Galaxy S 4 i9505 Original Android Development] h.m.k.:
Screen timeout still doesn't work in 3.2.3-0
[Galaxy S 4 i9505 Original Android Development] ripee:
And it hasn't worked since 2.8.4.0, which was from the cm-11.0 era, when the an older kernel was used. At this point, unless I figure out a fix in the kernel, my twrp device tree is as good as it can be.
[Galaxy S 4 i9505 Original Android Development] h.m.k.:
Interesting thing: screen timeout from DualBootPatcher9.3.0.r806 BootUI work! Maybe there is a solution in its sources?
[Galaxy S 4 i9505 Original Android Development] flyingsaucer75:
Hi to everyone!! I've a i9505 black edition I've upgraded twrp from 3.1.1.0 unofficial to install RR Oreo 8.1 to 3.2.3.0 it's normal that twrp gives an unable to locate /preload partition for backup calculations during a full backup?

Thanks in advance for a kindly response.

Best regards

Tony
[Galaxy S 4 i9505 Original Android Development] andy hall:
I did a backup this morning using 3.2.3-0 and did not have any issues, on a 9505 jfltexx.
[Galaxy S 4 i9505 Original Android Development] koyo:
There really isnt a thread for Titanium Backup but I've had a problem where when you try to install the update.zip, it seems to install but yet the apps don't appear on the phone. Does this update fix that or is that a Titanium Backup problem? It seems to only happen on Oreo as Nougat roms does it perfectly.
[Galaxy S 4 i9505 Original Android Development] flyingsaucer75:
Thanks for helping which is your installed ROM?
[Galaxy S 4 i9505 Original Android Development] andy hall:
ResurectioRemix N from [MENTION=1711160]Buff99[/MENTION]
[Galaxy S 4 i9505 Original Android Development] Slavestate:
Rad worked on my Straight Talk SM-S975L running LOS 15.1! Took a few reboots before the touch screen worked in recovery, but rebooted to the system, made sure it worked, rebooted into recovery, and touch screen was back (the unofficial 3.1.1.0 did that once in awhile as well so I think its just a SM-S975L thing). I tried using 3.2.2.0 a few days ago and all I got were boot loops into Download mode hahaha.
[Galaxy S 4 i9505 Original Android Development] raffux3:
good morning, can I install it on Samsung S4 i9515??
[Galaxy S 4 i9505 Original Android Development] ripee:
Unified build!

Please test the new build linked in the OP. It's compatible with the following variants:

jactivelte, jflteatt, jfltecan, jfltecri, jfltecsp, jflterefreshspr, jfltespr, jfltetfnatt, jfltetfntmo, jfltetmo, jflteusc, jfltevzw, jfltexx, jfltezm, jftddxx
[Galaxy S 4 i9505 Original Android Development] h.m.k.:
Installed and GUI works, I nothing else tested
[Galaxy S 4 i9505 Original Android Development] Diabolik2770:
jvelte

hi guys, it works on s4 i9515 jvelte ??

attached is the latest recovery jvelte android 5.1
[Galaxy S 4 i9505 Original Android Development] Diabolik2770:
jvelte

I tried to install UNIFIED BUILD twrp-3.2.3-0-jflte.img on i9515 jvelte

recovery has started but no button works
[Galaxy S 4 i9505 Original Android Development] flyingsaucer75:
Here it's the same I've a black edition s4 I must remove battery restart in download mode and reboot phone, then sometime if I try recovery again it works sometimes not
[Galaxy S 4 i9505 Original Android Development] Diabolik2770:
i'm use power button for restart on download mode without remove battery
[Galaxy S 4 i9505 Original Android Development] mattgyver:
Has anyone created a loki patched version of 3.2.x? I tried following instruction to loki patch it, but after flashing it, and rebooting recovery, my jflteatt/i337 reboots to the patched twrp 3.1.1-0 I had before flashing. I don't think I'm doing anything wrong with the patching procedure, but doesn't flash right even if loki_tool says complete..

EDIT: never mind. I figured out my problem. I'll upload a lokied version in case anyone else needs it.
[Galaxy S 4 i9505 Original Android Development] sekk:
Does this twrp version(3.2.3-0) work on android Lollipop( 5) ? I haven't updated my phone
[Galaxy S 4 i9505 Original Android Development] mattgyver:
TWRP works outside of Android version. It should work as long as it's for your device.