yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Original Android Development] Ibuprophen:
To add to response...

If you're flashing the Recovery via Odin, be sure your using the "twrp-3.2.1-0-klte.IMG" file. DO NOT use the "twrp-3.2.1-0-klte.IMG.TAR" for Odin.

Make sure your placing the TWRP file within the PDA/AP and keep everything else as is (its default settings).

Sometimes using a different USB Cable and/or a Different USB Port on your computer can do the trick. The device communication with the PC can be picky/touchy where a simple thing like a different cable/port can do the trick.

Good Luck!

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

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[Galaxy S 5 Original Android Development] negativman:
I tried to search, but I did not find a discussion of the problem of firmware recovery on the last TWRP. Backup does, but does not restore - can not mount the modem. Who faced? How is it solved?
[Galaxy S 5 Original Android Development] jdrch:
I encrypted my klte and now when I boot into TWRP I get "Error parsing XML file" after I enter my encryption password.

Any idea how I get TWRP back to working again so I can restore my backup?
[Galaxy S 5 Original Android Development] etriganm1:
Hey guys i seem to have a problem with touch when i flash my twrp recovery. I tried to port other recoveries but still touch wont work.

My device is wiko k-kool

Mt6580M,199dpi 480*854 screen resolution 1GB ram and 8GB rom gpu is Mali 400p

....any help on the way forward would be appreaciated
[Galaxy S 5 Original Android Development] BruceElliott:
SuperSU 2.82 SR5

Another question,

Is the subject root flash the best to use with TWRP 3.2.1-0? (I realize that the subject SuperSU is old, but it is for Galaxy S5 TMO 6.0.1 stock, so no issues with new Android or phone versions.)

If I flash it from TWRP, will it provide me with root access from within the TWRP environment without first booting to Android? ( I need to be able to modify, add or delete any file from any directory from the command line in TWRP.)

Also, does the current TWRP environment provide the same or better shell capabilties as the old Busybox? I.e., is there any need to flash Busybox like in the old days?

Thanks!

Bruce
[Galaxy S 5 Original Android Development] BruceElliott:
Please disregard the two requests for assistance above. I believe that I have a handle on the solution after working through a Linux bash shell tutorial last night. TWRP appears to support the command line environment very nicely. Great job!

I will post the problem resolution when complete.

Thanks,

Bruce
[Galaxy S 5 Original Android Development] dgriffi:
TWRP backup goes fine. Restore does nothing.

I have two Galaxy S5 G900T phones, each with TWRP version 3.2.1 and the latest nightlies of LineageOS. I want to backup one phone and restore to the other. The target phone has been wiped to "stock" status. Doing a backup like this: "adb backup --twrp boot system data cache misc sdcard" on the source phone works fine. I get a backup.ab file of an appropriate size on my Linux desktop computer. There, I'm running adb version 1.0.36 as installed through Debian 9's repositories . When I do "adb restore backup.ab", the restore runs, but nothing is actually written to the target phone. The backup runs and terminates as though the restore completed, but when I rebooted the target phone, it was still showing LineageOS freshly-wiped. None of my apps or data is there. Each of these backups and restores were done after booting into TWRP.

What went wrong?
[Galaxy S 5 Original Android Development] fitittome:
Untick the option to auto reboot in Odin. At the green pass., either hold down power for 10 seconds to power off or pull battery.
[Galaxy S 5 Original Android Development] dgriffi:
I didn't ask that question. I was asking about taking a nandroid backup on one phone and restoring to another, both phones being Galaxy S5 G900T models.
[Galaxy S 5 Original Android Development] BruceElliott:
How to "Re-enable" or "Un-hide" An App From TWRP Environment

Hi All,

TWRP 3.2.1-0 KLTE works fabulously for me on G900T Android 6.0.1 stock; thank you TWRP maintainers! Just a nooby-like question: Would it be possible to add package manager functionality to TWRP such that pm commands could be executed from the TWRP environment? Let's suppose that a boot-critical system app/process is disabled via Titanium or by executing pm commands from ADB while the Android OS is running. Upon re-boot the phone is stuck at a boot screen. At that point it would be nice to be able to re-enable the boot-critical system app to recover, rather than having to re-flash to stock and/or wipe /data and restore. Is there some other way to accomplish the same end result? Part of my problem with understanding this is that I do not know how package manager marks/flags an app as "disabled" or "hidden." It must be more complicated than simply resetting an app's Linux file "executable" bits. Maybe the states of "disabled," "hidden," or "normal" are stored in an SQLite database or XML file which could be edited? Any ideas are much appreciated. --Bruce
[Galaxy S 5 Original Android Development] Legitsu:
all titanium does is rename the apk or change the permissions

find the app with twrps file manager and rename it back /fix the permissions
[Galaxy S 5 Original Android Development] BruceElliott:
Thank you for the reply, I really do appreciate it. However, that is not quite how it works as I finally figured out.

Titanium executes the shell command: pm disable {package_name}. That command calls the package manager. The package manager then edits the text file "package-restrictions.xml" found in /data/system/users/0 to delete the terms [enabled= "3"] and [enabledCaller= "shell:0"] for each disabled app that needs to be re-enabled.

So, to answer my own question: yes, one can re-enable an app from within TWRP even though the TWRP shell does not include a package manager. You must open the .xml file indicated and edit out the terms listed above. Presto, the app is re-enabled when you reboot into Android.

Titanium is a clever and handy way to accomplish this from with the Android environment without having to use adb to execute package manager commands.

Best,

Bruce
[Galaxy S 5 Original Android Development] Nerva:
I'm running the latest TWRP 3.2.1.0 on my S5 -- is there a reason this thread hasn't been updated since 3.1.1.0?

I was looking at flashing the GApps Aroma variant, but see in the info on it that it is known to crash with TWRP 3.2.1.0. Is it Aroma or TWRP that needs to be fixed? Also, is the reason this thread is for 3.1.1.0 perhaps because it's the latest version that works with Aroma?
[Galaxy S 5 Original Android Development] fubo73:
The suggested TWRP for aroma flashing is 3.0.0.0.
[Galaxy S 5 Original Android Development] Nerva:
OK thanks. I'm currently running TWRP 3.2.1.0, so I think I'll stick with GApps-config instead of risking Aroma.

But I'm still curious, why does the first post of this thread have 3.1.1.0 instead of 3.2.1.0? Is there a problem with 3.2.1.0 and they're recommending 3.1.1.0?
[Galaxy S 5 Original Android Development] tdunham:
If I'm not mistaken, don't you have to go into settings on Ktoonsez version of TWRP and set the timezone or something to get the date & time to set properly?

Also, I'm not sure exactly where the TWRP folder is hidden on internal SD but I've found that a format of internal storage may be necessary to clear that out if having issues with TWRP and especially if going to a custom version (like KT's).
[Galaxy S 5 Original Android Development] Wheemer:
Yeah I forgot about setting timezone after I did a full wipe, oops...
[Galaxy S 5 Original Android Development] carbonize:
Well change of thread title shows that 2.8.0.0 has been released.
[Galaxy S 5 Original Android Development] xda23:
Do you have a link to the mod. Thanks. :)
[Galaxy S 5 Original Android Development] carbonize:
The changelog for 2.8.0.0 days something about fixing the time so try the update first.
[Galaxy S 5 Original Android Development] Dark_Avenger:
Yes... tested and confirm that the date/time issue is fixed in TWRP 2.8.0.0. Only brightness control is still not working.
[Galaxy S 5 Original Android Development] melorib:
Flashed 2.8.0 and it doesnt work properly, touch screen is erratic, it was very difficult to be able to install again KT2.7.1 version :confused:
[Galaxy S 5 Original Android Development] Dark_Avenger:
Power off your phone completely and boot again in TWRP. This solves the issue for me.
[Galaxy S 5 Original Android Development] lightninbug:
Anyone confirm MTP works in latest build?
[Galaxy S 5 Original Android Development] melorib:
I did that the second time, still didnt work, KT2.7.1 works fine, date and all...
[Galaxy S 5 Original Android Development] Dark_Avenger:
On my Windows 7 x64 no drivers found for "MTP USB Device" and "SAMSUNG_Android".
[Galaxy S 5 Original Android Development] tdunham:
Apparently not yet. If anyone does figure out the driver issue, please share with us. Windows sees the device, however there doesn't seem to be a driver available for it yet.

Also, if anyone would like a recovery flashable zip, I posted a link to it HERE.
[Galaxy S 5 Original Android Development] tangcla:
Didn't help me either - 2.7.1.0 works fine, 2.8.0.0 has erratic touch input.

Maybe deleting /sdcard/TWRP folder might help...
[Galaxy S 5 Original Android Development] tdunham:
Deleting /sdcard/TWRP does delete the config file I think and is probably a good idea.

The phone still seems to require a poweroff after flashing 2.8.0.0 so it can properly create the new config file though. We're still trying to figure out the proper sequence but the complete power off after flashing seems to be a necessity on this version.
[Galaxy S 5 Original Android Development] tangcla:
Will the touch screen issues still persist after a power cycle? Or will it go away for good?
[Galaxy S 5 Original Android Development] tangcla:
Update - deleted TWRP folder, flashed 2.8.0.0, took out battery, booted into recovery - touch issues are still there.

I have a G900I, if that helps.
[Galaxy S 5 Original Android Development] tdunham:
Some have said it may not take for several tries.

---------- Post added at 06:30 AM ---------- Previous post was at 06:20 AM ----------

Edit: I mean power down and try again. Not reflash.
[Galaxy S 5 Original Android Development] tdunham:
I believe I found a workaround for the touch interface issue in TWRP v2.8.0.0.

We're testing it out right now. I'll post a link as soon as it is available.
[Galaxy S 5 Original Android Development] Echelonblue:
no mounting or asking pass for encrypted /data

no mounting or asking pass for encrypted /data

from the first version untill now it isn't possible for me to mount /data

normally twrp asks the PW when booting the recovery (have this on mij N7100 note 2, Nexus 7 2013 wifi) but the version on my SM-G900F doesn't ask for it.

So i cant backup data.

Any sollutions for this?

I already posted this issue some pages ago. I realy like this recovery. I would love to have it working on my s5.
[Galaxy S 5 Original Android Development] mabmed:
Can any one make a zip file please? Thank you.
[Galaxy S 5 Original Android Development] swiftbones74:
3,2,1-0 works flawlessly, and is what you need to have if you intend on running any Oreo ROMs. The thread just hasn't been updated. Also Aroma is very dated and overrated.(personal opinion) Aroma hasn't been updated in years and will not work with most newer ROMs.
[Galaxy S 5 Original Android Development] Nerva:
OK thanks. I think I've figured out gapps-config anyway, and it lets me plan what's being installed/uninstalled in advance, rather than having to do it during the installation with Aroma.
[Galaxy S 5 Original Android Development] Nerva:
Another question: I see TWRP has options for USB backup/restore. I'm wondering if/how that works for devices with microUSB connectors rather than USB-C? With USB-C, there's no fixed server/client relationship, so I could connect a USB-C external drive to the phone and transfer files with it. But I'm not clear on how you do that if your phone has a micro-B connector.
[Galaxy S 5 Original Android Development] Ibuprophen:
That's for using a USB OTG (On-The-Go) for external storage like USB Stick Mounts and others.

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

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[Galaxy S 5 Original Android Development] 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.
[Galaxy S 5 Original Android Development] Ibuprophen:
I'm just curious if anyone else has experienced the following...

First of all, I did update the TWRP Recovery to v3.2.2-0 successfully on my G900V device.

If you enter the TWRP settings and, on the first screen/tab, scroll down to the last one that states "Use SHA2 for hashing" and the box (by default) is selected (turned on).

With that stated...

No matter how many times I unchecked (turned off) this specific box/option, when I boot back into TWRP, that specific option is selected again.

It doesn't seem to be a big deal or show stopper for me but, I've tried various ways on turning this off and it reverts back to being selected again.

Though, I first updated TWRP via the image file within TWRP itself without any problems and after noticing the above happening, I then reinstalled TWRP using the Odin method successfully and it was still doing it.

Sorry for the long explanation but, I just wanted to provide you with what I had done so there's no question regarding my performing a certain action that was already performed.

I'm just curious as to anyone else experiencing this as well and to let [MENTION=912474]Dees_Troy[/MENTION] know as well (though he may not respond to me specifically but, as long as he's aware of this as well).

When i get around to updating TWRP on my other devices, I'm going to try this out and see if it's going on with them as well.

Thank you all for your time, patience and understanding with this buggy issue... :)

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

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[Galaxy S 5 Original Android Development] thegreatkazoo:
im on 3.2.1-0 and did a full backup with adaptive storage on. But its really not there. This new update address the storage but whathappens to the backup i cant see or use??

the almost 8gb of space is being used but i can't find it.
[Galaxy S 5 Original Android Development] Ibuprophen:
I apologize if this is off topic but, I'm not sure if anyone is aware that haggertk had just posted the following "Official LineageOS 15.x" thread for the klte device! :eek:

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

Enjoy!

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

Sent using The ClaRetoX Forum App on my SM-G900V device.
[Galaxy S 5 Original Android Development] godofsalt:
...Yet another update in July, for TWRP 3.2.3 ! Had heard that I needed this for 8.1 Roms....

My issue, (after re downloading a few times, switching Different laptops, Wiping everything on the phone) I have an issue with the Latest...

I have been on LOS 15.1, for Galaxy S5 (xx.x900P) Once its on the phone IT does seem to work. Awesome

However, on many tries, When flashing a ROM, I get an error that, during the "Flashing process" it reads that it can not Mount /System. All in RED, and now what you have is a phone with everything on it, but TWRP 3.2.3 does not seem to actually do anything with the System Partition. Heck, I have even gone back to Stock Rom, just to get it working. Even from there, TWRP 3.2.3 just ends with an error, that it can not Mount the System Partition. going back a step, and not the latest.

Yes, the latest one, is supposed to handle OTA's , they fixed it again, however, if it cant mount the system, it is NO Good ....

Yeah, just my 2 cents here! for 2 days, trying to update me phone, its been 2 weeks , since I updated LOS15.1 and seen what is new, I want that on me phone, but presently, w/3.2.3 it is NOT going to happen....
[Galaxy S 5 Original Android Development] TheFixItMan:
Maybe your system is mounted as read only - on first boot of twrp swipe to allow system modifications or goto mounts & untick mount system as read only
[Galaxy S 5 Original Android Development] godofsalt:
well, one thing I did noticed, was the fact that in the Past 2 build prior 3.2.1 and 3.2.2, they both had that Warning. You had to Swipe to be able to fully use the Recovery .

Now this newer TWRP 3.2.3 did not have that warning. I have went in, to setting, and mounting, and such. Just maybe, it was not fully working with the System Partition (Did notice that the System was Unchecked. so I made that one, (blue box now!) Doing a back up, of this stock Firmware now.

I just for the life of me, what really going on....

thanks for the help so far.
[Galaxy S 5 Original Android Development] jdrch:
The last time I saw this error it was because I'd tried enabling device encryption within LOS. It works for some people, but in my experience TWRP has trouble handling encrypted volumes and partitions.

IIRC I think I fixed it by wiping System, Data, Cache, and Recovery, then flashing TWRP using Odin, and then restoring System and Data from my most recent Nandroid backup.

Check the klte LOS dev thread or my post history for exactly what happened when I had that problem.
[Galaxy S 5 Original Android Development] €D.:
Hi :)

I just got an old SM-G900F, that - surprisingly - is working fine!

I'd like to have a multi boot setup with the latest Stock (rooted) and some AOSP Oreo, but therefore I need a custom recovery first.

Currently the phone is on Stock lollipop (G900FXXU1BOD3) and asking me to update to Marshmallow (What I'd actually prefer).

But is it still possible to flash TWRP through ODIN then?

And how do I know wether my bootloader is locked and I need to do this (-> https://jdrch.wordpress.com/2016/04...genmod-13-0-on-the-verizon-samsung-galaxy-s5/ ) or I can just flash straigh through ODIN?
[Galaxy S 5 Original Android Development] fitittome:
Yes, 900F is unlocked. Ensure you are on latest Samsung stock first, to ensure baseband is upto date.
[Galaxy S 5 Original Android Development] €D.:
Thanks for the quick answer!

I'll do the update then ;)

It is nice, that there is still activity for that truly great phone :cool:
[Galaxy S 5 Original Android Development] haoyangw:
Download the .tar twrp file from twrp.me, and flash thattar through odin :) like you would flash a stock ROM tar.md5, same slot
[Galaxy S 5 Original Android Development] drewcu:
I have searched XDA and Google and cannot find the answer to my question below regarding my S5 G900V (KLTE).

I would like to restore an EFS partition made on TWRP 3.0.0 to see whether it helps my Unknown Carrier issue on custom ROMS (stock is fine). However, on TWRP 3.2.3 the EFS partition(s) don't show up and instead show the error "Unable to locate partition by backup name: 'efs1' / 'efs2' / 'efs3'." If I go back to TWRP 3.0.0 , these EFS partitions show up, but I don't know if it is safe to flash these considering the error on the new version and reports via Google of EFS/IMEI corruption relating to TWRP 3.0.2-1.

So please advise if you think it is safe to flash these older EFS partitions on TWRP 3.0.0 made on the same old version. The goal is to avoid IMEI corruption and fix my issue with Unknown Carrier on custom ROMS by using the oldest EFS backup I have from 2016.

Thank you!
[Galaxy S 5 Original Android Development] Ibuprophen:
I just wanted to follow up on the following post that I had made in this thread...

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

I had found that this issue (posted above) was also present on various other devices as well.

I had also submitted this issue (via Google Plus) on the TWRP page to the attention of [MENTION=912474]Dees_Troy[/MENTION] there (with screenshots and such).

After approximately a month (during which other individuals there also confirmed this as well), Dees_Troy had finally read and acknowledged that issue.

Dees_Troy also read and acknowledged 1 other issue and a feedback too...

The other issue was regarding my receiving an unreachable response email resulting from the fillable from on the twrp.me website (for submitting questions and issues to them). Others had this issue as well.

The feedback was regarding my suggestion about TWRP also performing annual surveys similar to what the Lineage Team does each summer.

Thank you very much for your time and understanding with this. Let's keep our fingers crossed! :)

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

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.
[Galaxy S 5 Original Android Development] kurtn:
Hi [MENTION=4828250]Ibuprophen[/MENTION], got my first klte. TWRP installation was frustrating! The lineageOS wiki recommended heimdall. But heimdall 1.5.0 does not work and 1.5.2 is only for self compilers.

Looks like best known method is via Odin?
[Galaxy S 5 Original Android Development] Ibuprophen:
Unfortunately, you can't just install TWRP straight out in this manner...

For my G900V, I had to carefully read and followed the instructions on the following thread to determine if I can, what to do and how to do it in regards to unlocking the bootloader and install TWRP.

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

For my G900T (I'm using now), it had TWRP already installed back when I had purchased it (fortunately).

Also, to be honest, I've actually used various Samsung devices for years and have actually never had/needed to use Heimdall. I've got nothing against it and I'm sure that it works for various individuals and tasks but, I have very little knowledge of it.

Good Luck!

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

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.
[Galaxy S 5 Original Android Development] suolrihm:
I got a klte (G900F) some months ago and had no Problems flashing TWRP with Heimdall, also following the LineageOS Wiki Page (flashed via Heimdall on openSuse Tumbleweed). Why was it frustrating exactly?
[Galaxy S 5 Original Android Development] kurtn:
Some message like pit download fail
[Galaxy S 5 Original Android Development] suolrihm:
Like i said, i had no problems on Linux with Heimdall. Sadly i can't tell which Heimdall release i used, since i switched the OS. If you use Windows just use Odin, should be less trouble but also, always check your USB connection
[Galaxy S 5 Original Android Development] zooorgie:
I have a Samsung Galaxy S5 that I earlier intalled TWRP on, rooted and flashed Lineage 15.1

The problem I have ist that every time Lineage is uppdating, the TWRP is deleted.

And root also.

The version here is 2.7 and the version I found before is newer 3.2.3

Why use an old one ?
[Galaxy S 5 Original Android Development] fubo73:
This never happens to me. I have TWRP 3.2.3, when I update through updater, no problem (it also reinstall magisk) and TWRP is still there. Although, I prefer to do it manually.
[Galaxy S 5 Original Android Development] buntbart:
I can't access the data via MTP when I connect the G900F in recovery mode to my Laptop running Xubuntu 18.04. The TWRP version is twrp-3.2.3-0-klte

When I connect the klte, it appears in Xubuntu's file manager, but when I want to mount it, I get an error message: "Connection is closed". I have installed several klte and it is the same for all of them. So it can't be because of this device.

At first I thought it was only Ubuntu, because with Xubuntu 16.04 data exchange via MTP works. But now I have connected a Xiaomi Redmi 4x with current TWRP to the 18.04-PC and there it worked immediately without problems. Even with an old Galaxy Nexus (maguro) everything works fine. So the error must have something to do with the TWRP version for the klte.

Any ideas?