yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Original Android Development] !crazy:
TWRP self can handle/flash recovery in img format. That's how I update in the last time (on this device).
[Galaxy S 5 Original Android Development] Sargos76:
do as told you or you will not be able to use your extsdcard, install 3.0.2.0
[Galaxy S 5 Original Android Development] !crazy:
Point taken. He actually asked if he needs to download img or tar file.
[Galaxy S 5 Original Android Development] Sargos76:
simply choose image on recovery and flash the .img file good weekend to all
[Galaxy S 5 Original Android Development] Pjerisimo:
Does 3.0.2-0 support mtp?
[Galaxy S 5 Original Android Development] Sargos76:
yes
[Galaxy S 5 Original Android Development] StoneMonarch:
[IMG="TWRP KLTE"]https://65.media.tumblr.com/b331c2b3aea8e46cc22b175c0cc5309d/tumblr_o6thz6dYvI1uly0m5o1_1280.jpg[/IMG]

So anyone know how to fix this? Cant access the SD card

Running the latest TWRP version as well
[Galaxy S 5 Original Android Development] aguarello:
https://idlekernel.com/twrp/klte/testing/

Grab test2. It's fully working.

Cheers! ;)
[Galaxy S 5 Original Android Development] StoneMonarch:
Oh thank you so much sir

---------- Post added at 06:56 PM ---------- Previous post was at 06:46 PM ----------

Ok so now the SD-Card won't mount and i cant access either internal nor external storage
[Galaxy S 5 Original Android Development] aguarello:
What firmware are you running?
[Galaxy S 5 Original Android Development] StoneMonarch:
Heres the device info screen. and i think the bootloader is BOC1

[IMG="Screen"]https://67.media.tumblr.com/110bac9fc516f4dc0146ab3a825e9062/tumblr_o6tmlhmOC91uly0m5o1_1280.png[/IMG]
[Galaxy S 5 Original Android Development] aguarello:
So your phone isn't a G900F?
[Galaxy S 5 Original Android Development] StoneMonarch:
No, its G900W8
[Galaxy S 5 Original Android Development] aguarello:
This recovery is made specifically for the G900F (klte). That might be the problem. Plus I think your using a Lollipop bootloader with a MM ROM.
[Galaxy S 5 Original Android Development] StoneMonarch:
The G900W8 is klte as well. and if i can get the offical firmware for G900W8VLU1DPD3 is there a way i can get the MM BL and Modem out of it?
[Galaxy S 5 Original Android Development] aguarello:
Oh well I had no idea, I beg your pardon. Yes, indeed you can. Just Google something like "extracting BL and Modem" I know I've read you definitely can.
[Galaxy S 5 Original Android Development] StoneMonarch:
Alrighty thanks very much. ill do so in a few hours, gotta get ready for mothers day. ill let you know how it goes.
[Galaxy S 5 Original Android Development] joiN85:
Twrp 3.0.0-7 stable for g900f with 6.0 bootloader.

Brightness work, mtp work, extsd work! Mod by me
[Galaxy S 5 Original Android Development] decalman:
Loving the new look on the latest release
[Galaxy S 5 Original Android Development] bluesman1306:
Thank you!!! Is it save to downgrade from 3.0.2?
[Galaxy S 5 Original Android Development] joiN85:
You can downgrade recovery safely :good:
[Galaxy S 5 Original Android Development] bluesman1306:
Thank you for your fast answer :)

It seems to fully working exept for the sdcard. Cant't get acess to it. It's fat32 formatted
[Galaxy S 5 Original Android Development] joiN85:
Mount sdcard first and it work

This recovery is for 6.0 bootloader with lollipop bootloader ext sdcard don't work
[Galaxy S 5 Original Android Development] bluesman1306:
Tried the following bootloaders from Alexndr:

https://www.androidfilehost.com/?w=files&flid=18030

BL_G900FXXU1CPD7.tar.md5

BL_G900FXXS1CPC8.tar.md5

BL_G900FXXU1CPB2.tar.md5

Flashed with odin 3.10.6 winxp

ExtSD card is working fine now. But I got bootloops all the time. I tried a clean install, wiped everything, also tried TWRP 3.0.2.test2.

Bootloops all time. Guess I need help :(
[Galaxy S 5 Original Android Development] joiN85:
If you have a lollipop rom installed flash a lollipop bootloader
[Galaxy S 5 Original Android Development] bluesman1306:
no, daily updates cm13.

Did I brick my phone?

---------- Post added at 06:58 PM ---------- Previous post was at 06:14 PM ----------

Is it possible that cm13 needs a lollipop bootloader? Did you mean that with your last post?
[Galaxy S 5 Original Android Development] haggertk:
CM13 requires L bootloader. The kernel merge is huge and ugly (and some of it is probably in blobs, no kernel), and we do still need to provide pre-M compatibility for some of the variants who don't have M yet. Not to mention VZW dev bootloaders.

It's on the list to get fixed, but just flash an L bootloader and you'll be good to go.
[Galaxy S 5 Original Android Development] bluesman1306:
Thank you!
[Galaxy S 5 Original Android Development] Dor71:
Great, thank you.
[Galaxy S 5 Original Android Development] nunein:
Great! Finally mount SD card is working - THX!
[Galaxy S 5 Original Android Development] Dennys_Santos:
Dude!!!

Thank you for sharing this version.

I want to report this also running smoothly on the device G900M :good:

Thanks again... ;)
[Galaxy S 5 Original Android Development] opaco23:
[MENTION=5672995]jcadduono[/MENTION]: About EFS backup, I noticed a backup I took in February

using twrp 3.0.0 included:

efs1.emmc.win
efs1.emmc.win.md5
efs2.emmc.win
efs2.emmc.win.md5
efs3.emmc.win
efs3.emmc.win.md5
modem.emmc.win
modem.emmc.win.md5

But with twrp 3.0.2 (-1 and -2-test1):

efs.ext4.win
efs.ext4.win.md5
efs.info
modem.info
modem.vfat.win
modem.vfat.win.md5

I guess it is caused by changes in recovery.fstab. Could you please explain the

reasons for the change?

Thanks!
[Galaxy S 5 Original Android Development] scamid:
Where do i get a 6.0 bootloader? and do i need to install a kernel?
[Galaxy S 5 Original Android Development] jcadduono:
I took out modemst1/2 partitions from fstab because they are never mounted or written to and shouldn't need to be backed up or restored and are completely unrelated to EFS.
[Galaxy S 5 Original Android Development] sachin7825:
does not work on korean G900L//

any solutions??
[Galaxy S 5 Original Android Development] jcadduono:
no information to go on
[Galaxy S 5 Original Android Development] Dennys_Santos:
View attachment 3754819

Dude!

There were two errors in the process of restoring a backup made with version 3.0.2-0

Can you solve?

Follow the LOG file and an image error.

Thanks.
[Galaxy S 5 Original Android Development] joiN85:
Restore with 3.0.2-0 and after create a backup with my version.

The restore work fine for me with a backup made by my version
[Galaxy S 5 Original Android Development] Dennys_Santos:
Ok!

Thanks.
[Galaxy S 5 Original Android Development] j1gga84:
[MENTION=5672995]jcadduono[/MENTION]

So if I use a MM custom ROM such as CM13.0 that requires LP bootloader I have to use the LP recovery?

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] ionutmaruta:
Installed both versions and I can't entry into TWRP recovery :( I have Andorid 5.0 latest version devbase by [MENTION=7184490]Alexndr.[/MENTION]..

twrp-3.0.2-2-L-klte.img

twrp-3.0.2-2-M-klte.img

The phone always is restarting and trying to entry in recovery mode...without RED message, only yellow message.

The battery must be removed to start de phone in normal mode.

Belive me, if the above versions are final, not working in G900F.

Beside v3.0.2.2-test2 I cand acces de extsdcard :(

V3.0.2.1 is working fine in my device ;) but I see many members which v3.0.2.1 not see the extsdcard. Incredible. In my G900F I can backup/restore from the extsdcard using v3.0.2.1 :)

PS: What is -L- and -M- from the namefile ? Lollipop and Marshmallow ?
[Galaxy S 5 Original Android Development] opaco23:
modemst1/2 partitions contain configuration used by the modem firmware. I believe it can

be corrupted e.g. by flashing a wrong modem firmware. Well, I have my backup, but you're not

doing anyone a favor by excluding it.

Regarding the format change of efs and modem from emmc image to vfat tar, I'm not sure

I like it. But more importantly, newer twrp should be able to restore old backups,

otherwise it's just a nuisance for users. I've not tested so maybe there is no issue,

but if there is then please consider reverting to old format. Compatibility is much

more important than saving a bit of backup file size.

Thanks!
[Galaxy S 5 Original Android Development] DirkStorck:
twrp-3.0.2-2-L-klte doesn't work with my device. Constant reboot into recovery....I am using a LP bootloader and a cm13 based ROM.

Can't go back using Odin because my Lapttop does not recognize my phone in download mode :(

EDIT: Ok, had to change USB-port...noch I am back on twrp-3.0.2-1-klte.

twrp-3.0.2-2-M-klte and twrp-3.0.2-2-L-klte don't boot for me into recovery.
[Galaxy S 5 Original Android Development] ionutmaruta:
Yes me too. I have G900F. Still using 3.0.2.1 ;)
[Galaxy S 5 Original Android Development] xda23:
Do I need to flash the Image or the tar file? Thanks :)
[Galaxy S 5 Original Android Development] Paolonicus:
Is klte the same with SM-G900F

Hi! Sorry to be a bother. I would only like to ask if my S5 variant is the so called klte? I saw it on the other threads, but hesistant to flash.

A little confused with the term. My S5 is a SM-G900F. I am already familiar with this recovery with the Galaxy S3 & S4.

Many Thanks!

BTW: Are there any current issues I should know?
[Galaxy S 5 Original Android Development] melorib:
Found it, they are in a folder inside TWRP/BACKUPS
[Galaxy S 5 Original Android Development] kevincop:
Yeah, that's where they should be, both on the internal memory and the SD card unless you customize that path yourself.

However, my problem still remains and I think I found out why. It has been overwriting my backups due to a bug that TWRP 2.7.0.0 exhibits: it can't set date/time correctly.

Right now for example it's saving my date in backup folder: /external_sd/TWRP/BACKUPS/<id>/2014-01-23--18-06-31 KOT....

The time displayed above is 6:17PM right now, which coincides with army time 18:00 hours.

Normally the minute and second would make a difference, but who knows, maybe it took me the same amount of time to slide to backup as it did before it happened to be overwriting, because my other backups are nowhere to be found. I've restored each one of them, and all are older versions, not the one I know I backed up specifically.

You hear me TWRP devs? You have a bug in this version. Check for date/time bug.
[Galaxy S 5 Original Android Development] carbonize:
So no fixes for it not seeing my microSD card then?
[Galaxy S 5 Original Android Development] pelpa87:
is this working for G900H variant?
[Galaxy S 5 Original Android Development] tdunham:
[MENTION=912474]Dees_Troy[/MENTION]

Would like to see an updated build with a little more support for system/priv-app root system apps folder (I think that might be where the problem may be). We're starting to see issues when doing full restores on our latest Sprint NE5 build.

Symptoms:

On restore, certain system apps start force closing on a full restore.

I used to be able to run the permissions fix to get around that but it doesn't appear that the priv-app folder is being included in the embedded script.

Anything else I can provide, please let me know.
[Galaxy S 5 Original Android Development] melorib:
Another very strange thing, TWRP backups have weird dates, mine are all with Jan 2014 dates, including the one I did this morning :confused:
[Galaxy S 5 Original Android Development] tdunham:
That is a known issue.

The only way around it that I know of is to edit the backup filename right before you start it (the backup filename is editable in TWRP) and give it the correct date.

You can also use the app from the Play Store called TWRP Manager but it wont allow you to backup to external SD and it doesn't give you a choice for the filename but it does give it the correct date. So I don't use that one very often due to those limitations. :rolleyes:
[Galaxy S 5 Original Android Development] melorib:
Thank you :good:

I will rename the file then, no problem...
[Galaxy S 5 Original Android Development] aegeuss:
Guys, I suddenly have a strange problem after Omega Room v7 with new boatloader; wiping cache and dalvik cache in TWRP 2.7.1.0 does not work any more and stuck. I don't know if it also might be related to ktoons custom kernel dated 26.07.2014.

SM-G900F cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy S 5 Original Android Development] jbadboy2007:
Yeah I hope he can or does fix twrp I like it so much more than philz
[Galaxy S 5 Original Android Development] carbonize:
I'd just be grateful if they'd fix the issue of TWRP not seeing my 64Gb card.
[Galaxy S 5 Original Android Development] ragz:
I Am on TWRP 2.7.1.0 and it sees my 64g card always.

Sent from my SM-G900W8
[Galaxy S 5 Original Android Development] carbonize:
Where did you get 2.7.1.0 from since both this thread and the official site only show 2.7.0.0 for the S5.
[Galaxy S 5 Original Android Development] ragz:
http://techerrata.com/file/twrp2/klte/openrecovery-twrp-2.7.1.0-gt-klte.tar

Down load site

http://www.teamw.in/project/twrp2/229

Main site for download options.

Sent from my SM-G900W8
[Galaxy S 5 Original Android Development] carbonize:
Downloaded but in bed so will try it tomorrow.
[Galaxy S 5 Original Android Development] Misterdjus:
If i download the TWRP recovery and flash it with Odin, do i automaticly have root on my device? Or do i miss something :confused:
[Galaxy S 5 Original Android Development] carbonize:
Root is something completely different.
[Galaxy S 5 Original Android Development] ragz:
Did you get it to work?

Sent from my SM-G900W8
[Galaxy S 5 Original Android Development] jcadduono:
k I'll wait till my mom's S5 is available for me to use. Seems that I disabled something in the kernel again that is required to boot, probably debug symbol related.

also gonna attempt to get hw encryption going for cm-13.0

also returning modemst1/modemst2 to efs backups but they will still be incompatible with twrp pre 3.0.2 (you should just flash the old twrp version and restore it, then flash new twrp 3.0.2-2+ and make a new backup once it's released)
[Galaxy S 5 Original Android Development] Minotaur:
https://idlekernel.com/twrp/klte/3.0.2-2/twrp-3.0.2-2-M-klteduos.img didn't work for me. Phone kept bootlooping in to recovery.

Using the latest alexandr ROM (Android 6.0.1) with his latest BL and CP files.
[Galaxy S 5 Original Android Development] jcadduono:
Alright, attempt 2. It seems the issue with the previous version was the ramdisk compression (I'm not allowed to use optimized lc/lp/pb with kernel lzma decompressor)

CyanogenMod 13.0 encryption & hardware encryption IS working now and tested. Glad to get that out of the way finally.

Samsung encryption still does not work, however. (not until we get it fixed in TWRP's main branch)

New download: https://idlekernel.com/twrp/klte/3.0.2-3/

I have separate L (4.4/5.0/5.1 BL) and M (6.0 BL) builds.

Be sure to try the correct one.

Test as many features as you can to ensure everything is working, and provide a recovery.log even if everything is fine.

For example G900L on 6.0 firmware would be: https://idlekernel.com/twrp/klte/3.0.2-3/twrp-3.0.2-3-M-klteskt.tar.md5

G900F on 5.1 firmware would be: https://idlekernel.com/twrp/klte/3.0.2-3/twrp-3.0.2-3-L-klte.tar.md5

Changes since 3.0.2-1:

All devices use klte as ro.product.device - variant specific name is still used in ro.product.name (klte asserts work on all variants)

Switch from XZ to highly optimized LZMA compression (same or slightly faster decompression speed, 800 KB shaved off size to fit future additions)

Lie about SEAndroid state to Samsung bootloader to disable RECOVERY IS NOT SEANDROID ENFORCING message

f2fs driver updated to 2016-05-18 kernel 3.4 sources

last_kmsg should be fixed

CyanogenMod 13.0 crypto libraries added and enabled, AOSP/QCOM encryption does work

Hardware encryption support enabled

modemst1/modemst2 added back to EFS backups

/dev/block/bootdevice should now point to /dev/block/platform/msm_sdcc.1

Marshmallow (6.0) bootloader supported with -M builds, KitKat/Lollipop (4.4-5.1) bootloader supported with -L builds

Old SuperSU installer removed (it should never ask you to install it anymore)
[Galaxy S 5 Original Android Development] bilbonotry:
[MENTION=5672995]jcadduono[/MENTION] : what is the point of lying about seandroid state ? That message is not really annoying isn't it ? And it is better to know what is going on security wise I think
[Galaxy S 5 Original Android Development] jcadduono:
One problem I have is that users flash it and think that the Seandroid message is an error that means it won't boot so I wanted to get that out of the way.

And yes, some users have messaged me saying that it is annoying, and while I did manage to respond back that their complaining of a small cosmetic difference that shows up for 2 seconds only when booting their device into recovery is annoying too, I figure this is the easier way out for me. Lol.

And really, it is TWRP, users should know that it allows root access to everything unencrypted already. :)

It is only lying to the bootloader, not the user space or kernel btw.
[Galaxy S 5 Original Android Development] j1gga84:
[MENTION=5672995]jcadduono[/MENTION]

So to clarify it again, if I use CM13.0 which is based on Android 6.0.1 but requires LP bootloader to boot I need the 3.0.2-3 L, correct?

regards
[Galaxy S 5 Original Android Development] khan78:
So which recovery I should use if I like to install CM13 on my Samsung SM-G900V (Verizon S5)? I am rooted and have unlocked boot loader with TWRP-3.0.2-1-klte recovery and rooted stock rom 5.0 BOG5 version.
[Galaxy S 5 Original Android Development] Dennys_Santos:
You can use the M smoothly, I'm using here ...
[Galaxy S 5 Original Android Development] jcadduono:
I'm not sure M works well on 5.0/5.1 BL, supposedly sdcard will stop showing up in mounts
[Galaxy S 5 Original Android Development] j1gga84:
I wanted to update my ROM with newest 3.0.2-3 LP recovery but after flashing it ended in a bootloop.

After that I flashed 3.0.2-1 again and installation succeeded..

Maybe I have to use MM recovery but I use ResurrectionRemix which is based on CM13.0 and CM13.0 needs a LP bootloader to boot..!?

Regards

Sent from my SM-T805 using german Tapatalk 4
[Galaxy S 5 Original Android Development] jcadduono:
you are absolutely sure you flashed this: https://idlekernel.com/twrp/klte/3.0.2-3/twrp-3.0.2-3-L-klte.tar.md5 ?!

i don't know why it wouldn't boot, it works fine for me on the same phone
[Galaxy S 5 Original Android Development] j1gga84:
Yes I flashed this one but out of recovery and not via ODIN, does that makes any difference?

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] chaoscreater:
I'm on official stock 6.0 ROM on my G900i.

TWRP 3.0.2.0 recognizes my microSD card in nandroid backup, however I can't mount it in recovery.

TWRP 3.0.2.1 does NOT recognize my microSD card in nandroid backup, however I can mount it in recovery.

Update:

Tried 3.0.2.3-M-klte from test branch just now, seems like it fixed the issue! It can recognize my microSD in nandroid backup, as well as mount it via MTP. My microSD is formatted as adoptable storage by the way.

What's weird is that OP mentioned this in one of his posts a few pages back:

If I understand this correctly, the "encryption" here refers to adoptable storage? I'm on stock official G900i 6.0 firmware. So it's weird that the Samsung encryption is decrypted in the latest TWRP 3.0.2.3 test, even though it's not supposed to be working. Not that I'm complaining though!
[Galaxy S 5 Original Android Development] Dor71:
Works great, thank you.
[Galaxy S 5 Original Android Development] j1gga84:
And softkeys are lightened all the time when using M recovery on 5.0/5.1 BL and they do not work (back button), SD card is not visible so I had to flash L recovery and everything works :)

Will 3.0.2-3 become official or only if recovery will run on all bootloaders like 3.0.2-1 ?

regards
[Galaxy S 5 Original Android Development] It_ler:
I have installed above mentioned TWRP (3.0.2-3-L), as I'm still on stock based Lollipop.

Everything seems to work fine, except the aroma file manager.

Just saw the post of another user reporting the same issue (here) ... that's why I wanted to let you know.

If you need more info ... let me know.
[Galaxy S 5 Original Android Development] yurividal:
I am running CM13 (Marshmallow) but on a L bootloader.

Should I use the M or L version?
[Galaxy S 5 Original Android Development] j1gga84:
The L Version, like it is written in the changelog:

Marshmallow (6.0) bootloader supported with -M builds, KitKat/Lollipop (4.4-5.1) bootloader supported with -L builds

regards
[Galaxy S 5 Original Android Development] bilbonotry:
No, encryption means it is not readable without a key. Adoptable storage means SD is part of the system and user cannot access it. I do no think it is encrypted by default.
[Galaxy S 5 Original Android Development] opaco23:
Adoptable Storage implies encryption.

In fact with cm13 it is the only way to encrypt the external SD card. Does Samsung stock ROM support

encryption of "portable" storage?

At first glance 3.0.2.3-L-klte seems to recognize and mount the adopted SD card, however it only mounts

the first partition as VFAT, but in adopted storage the first partition is a 16MB "android_meta"

partition, the real data is on a second "android_expand" partition (GPT is used). Using shell commands

one could even create a mixed setup with three partitions.

[MENTION=912474]Dees_Troy[/MENTION]: I think 3.0.2.3-L-klte does not correctly support adopted storage.

However, it is confusing in adb shell:

~ # df -h
...
/dev/block/mmcblk1p1 60.4G 384.0K 60.4G 0% /external_sd

~ # fdisk -l /dev/block/mmcblk1
Found valid GPT with protective MBR; using GPT
...
Number Start (sector) End (sector) Size Code Name
1 2048 34815 16.0M 0700 android_meta
2 34816 126613470 60.3G 0700 android_expand

~ # cat /proc/partitions
...
179 64 63306752 mmcblk1
179 65 16384 mmcblk1p1
179 66 63289327 mmcblk1p2

I wonder where df gets the size for /dev/block/mmcblk1p1?
[Galaxy S 5 Original Android Development] pepe100:
The new versions use LL and MM kernel for that reason they are not compatible with aroma, the older version uses KK kennel which is compatible with aroma. I personally uses TWRP 3.0.2.0 and it works perfect with aroma.
[Galaxy S 5 Original Android Development] Dennys_Santos:
[MENTION=5672995]jcadduono[/MENTION]

I am using the twrp-3.0.2-3-M-klte version and only encountered a problem when restoring a full backup was not possible to restore the MODEM to have a read-only partition was mounted.

You could fix this little problem?

Attached is the LOG file.

PS: Thank you for your contributions.
[Galaxy S 5 Original Android Development] jcadduono:
cant reproduce and log is empty

also build should be coming up sometime in the next few days on twrp.me, it will use L kernel on both L and M bootloaders thanks to [MENTION=2693412]haggertk[/MENTION] and his discovery of why mmc failed to show up (changed bootloader cmdline)
[Galaxy S 5 Original Android Development] Dennys_Santos:
[MENTION=5672995]jcadduono[/MENTION]

Great news!!!

While we do not have the new code available, I am putting attached other LOG file and an image.

Thanks dude.
[Galaxy S 5 Original Android Development] jcadduono:
seems someone introduced some new code, i have a patch ready to revert some of it and move it to the proper areas

https://gerrit.omnirom.org/#/c/18003/

oh it seems the new klte builds that should support both L and M are up @ twrp.me

version 3.0.2-2 for klte and 3.0.2-1 for variants of klte
[Galaxy S 5 Original Android Development] Bless1:
I've tried the newest twrp 3.0.2-2 and it still doesn't read the micro SD card anybody have any suggestions
[Galaxy S 5 Original Android Development] pepe100:
The version 3.0.2.0. mount correctly the ext micro SD
[Galaxy S 5 Original Android Development] GMan8212:
I am having trouble installing TWRP

---------- Post added at 01:49 AM ---------- Previous post was at 01:45 AM ----------

Could someone help me install TWRP, I have a Galaxy S5 (sprint.) I have taken all of the steps needed but for some reason when I try to boot into recovery it goes into the default recovery mode. :crying::confused: