yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Original Android Development] revanmj:
Unfortunately mounting adopted storage still doesn't work. But error message changed from "failed to mount adopted storage" in 3.0.0 to "failed to setup adopted storage decryption" in your version.
[Galaxy S 5 Original Android Development] DirkStorck:
Just have update my recovery using your version for klte. I must say MTP works perfect! Thank you so much! :D :highfive:
[Galaxy S 5 Original Android Development] ZioGTS:
WOW! Can't wait to try it! Thx [MENTION=5672995]jcadduono[/MENTION] you're the man! ;)
[Galaxy S 5 Original Android Development] Hayatzada:
where to download twrp 3.0 (your build with mtp working)
[Galaxy S 5 Original Android Development] thejester123:
"Click here for free cookies"
[Galaxy S 5 Original Android Development] nikosma:
Thank you very much!!!!!!! It works on G900F.
[Galaxy S 5 Original Android Development] JohnLouise:
Hello, I'm currently on the TWRP 3.0.0 can I install the fixed version by just simply flashing zip or do I need to wipe cache and dalvik cahce? Thanks in advance.
[Galaxy S 5 Original Android Development] thejester123:
Just flash zip and reboot to recovery ;)
[Galaxy S 5 Original Android Development] jcadduono:
is it still working with: https://idlekernel.com/twrp/klte/3.0.0-2/

i fixed partition sizes and disabled secure erase (looking at logs, klte doesn't support it without Odin's help) so it should wipe a bit faster
[Galaxy S 5 Original Android Development] thejester123:
The first build wipes partitions very quickly, I will flash 3.0.0-2 and see how fast it is :)
[Galaxy S 5 Original Android Development] revanmj:
3.0.0-2 Still has "Failed to setup adopted storage decryption" error and won't mount SD card formatted as such :(
[Galaxy S 5 Original Android Development] jcadduono:
I'm experimenting with encryption on hlte right now. I think I sort of have it working, so I might be able to port that to klte eventually. I'm not sure whether it will work with CM13 or not though, might only work with TouchWiz.

Update: nope this didn't work at all. try 3.0.0-3 though, it does enable software encryption for adopted storage. it might need more work, not sure.
[Galaxy S 5 Original Android Development] Hayatzada:
The first build wipes partitions very quickly, I will flash 3.0.0-2 and see how fast it is, THANK YOU for this great work,
[Galaxy S 5 Original Android Development] tdunham:
Update to my previous, TWRP unable to run:

Contemplated running full factory odin restore but ended up formatting internal data storage in Philz recovery/mounts & storage and that wiped out any residuals that were preventing TWRP from running. FYI - this wipes internal SD so make sure you backup first before attempting the same fix.

Cheers - TD
[Galaxy S 5 Original Android Development] Mod57:
This is happening to me too thanks for offering a solution. I'll give it a try this evening.

Worked like a charm, thanks a lot for taking time to share this with the rest of us.
[Galaxy S 5 Original Android Development] casonswag:
I saw there a new twrp update does this phone have it yet?
[Galaxy S 5 Original Android Development] superleeds27:
Looks like it

http://techerrata.com/browse/twrp2/klte
[Galaxy S 5 Original Android Development] Echelonblue:
Don't flash this on Sm g900f it will brick the device.

Sent from note 2
[Galaxy S 5 Original Android Development] Dark_Avenger:
This is not true. Flash (with mobile odin ) and use it for couple of days without any problem.
[Galaxy S 5 Original Android Development] Echelonblue:
Ok I flashed the img what flashify and the device rebooted in download mode. That's where it went wrong

Tried it with mobile odin. Works.

Just one little problem TWRP doesn't ask for a encryption password when booting. When FDE is enabled. So it isn't possible to mount the data partition. This is the same issue the previous version had.

Sent from note 2
[Galaxy S 5 Original Android Development] Droid9684:
Pit file for G900V Developer Edition?

Hello does anyone have a PIT file for the Verizon S5 Developer Edition? Thanks. I'll be sending it out to Samsung to get the bootloader unlocked after accidentally locking it trying to use JODIN on Mac.
[Galaxy S 5 Original Android Development] xda23:
When I back up my rom dont I back up everything except efs? Thanks In advance!!!
[Galaxy S 5 Original Android Development] kevincop:
where's my backups?

I have this TWRP version running on my S5 and I just backed up my boot, system, data, but can't find the backup in the TWRP folder on my SD card (which is where it says it will save it before you slide to backup). Actually, I can't find the past 3 backups I made! I'm not sure what exactly is the issue. I have about 4-5 backups there, but the dates are off. They show January, and this TWRP wasn't even available back then. So what's going on? What am I missing? And why did it not write the backup to the SD card since it showed success?
[Galaxy S 5 Original Android Development] fabiokino:
Full device encryption

Same problem here: SM-G900F with full device encryption on stock rom, the recovery doesn't seem to dectect encryption. The log says:

E: Could not mount /data and unable to find crypto folder.

E: Unable to mount '/data'

...

Any news?
[Galaxy S 5 Original Android Development] Echelonblue:
Still not solved

Still the same problem with the latest update.

Don't know if it has to do something with it. But some apps like encpasschanger. And others also don't work. Could it be that the header or other information is stored in a different manner?
[Galaxy S 5 Original Android Development] xda23:
Did you guys back up everything except efs? Then your back up will be in the twrp file in es file folder you download it from Google play.:)
[Galaxy S 5 Original Android Development] rockingondrums:
For future reference, don't ever say something bricked your device if you're still able to

boot the phone

AND run an app from that phone. That is literally the opposite meaning of "bricked." Bricked means NOTHING on screen. No recovery, no download mode, no bootanimation running over and over, nothing. Maybe the vibrator inside will hum. Maybe.
[Galaxy S 5 Original Android Development] Echelonblue:
Thx for the info

In correct term I meant a soft brick. For your your reference na Hard brick
[Galaxy S 5 Original Android Development] ianigm:
Works well as usual coming from S4 to S5. Good work!:cool:
[Galaxy S 5 Original Android Development] fifamaniac:
Hi all.

Can someone tell me please wich device i must choose to install twrp on a samsung galaxy s5 european version?

When i tap select device, it gives me A68...

Thanx for your replies!
[Galaxy S 5 Original Android Development] culson_35:
What model is

XtroStoLite 4.4.2 (SM-G900T)
[Galaxy S 5 Original Android Development] fifamaniac:
Galaxy s5 SM-G900F

Thanx
[Galaxy S 5 Original Android Development] culson_35:
http://techerrata.com/browse/twrp2/klte

XtroStoLite 4.4.2 (SM-G900T)
[Galaxy S 5 Original Android Development] revanmj:
Unfortunately 3.0.0-3 still shows "Failed to setup adopted storage decryption" error. I would gather more logs if you would tell me how (never did it for recovery so I don't know about anything besides this simple console accessible via navbar button).
[Galaxy S 5 Original Android Development] jshare:
I flashed 3.0.0.0 (t03g) on my n7100 on Friday, flashing directly from inside 2.7.0.0.

The new UI is a big improvement. Is it possible to change color? I have a bright orange theme as opposed to the blue theme seen in the screenshots.

There seems to be a few minor bugs but I can't reproduce them consistently yet. For example, I did a full backup and then restored that backup, but instead of rebooting right away, I wanted to return to the main menu. Didn't matter, when I pressed the home button at the bottom of the screen, the phone rebooted anyway to System.

Another one I've seen is if charging the phone while completely off (just seeing the green battery on screen), if I unplug the charging cable and then reinsert, the phone will sometimes boot into recovery.
[Galaxy S 5 Original Android Development] jcadduono:
I think you missed

http://xdaforums.com/showthread.php?t=1938733
[Galaxy S 5 Original Android Development] nickveldrin:
I can also confirm that 3.0.0-3 gets "E:Failed to setup adopted storage decryption" error.

In my case, I also tried formatting my sdcard as portable from within my ResurrectionRemix, booted into TWRP, formatted the sdcard from there, booted back into ResurrectionRemix, converted the card to adopted storage, and booted back into TWRP.

No difference, and still cannot access the adoptable storage from TWRP.
[Galaxy S 5 Original Android Development] 0kti:
New version available

Tapatalk S5
[Galaxy S 5 Original Android Development] Minotaur:
New version reboots my phone when I try to tap any of the options in Recovery mode. Using klteduos version.
[Galaxy S 5 Original Android Development] ipharus:
Same for klte
[Galaxy S 5 Original Android Development] jcadduono:
yeah it's a test build, waiting for someone to provide kmsg and recovery.log
[Galaxy S 5 Original Android Development] ipharus:
I didn't manage to get the last_kmsg but here is the recovery.log
[Galaxy S 5 Original Android Development] jcadduono:
has crash stopped happening with https://idlekernel.com/twrp/klte/3.0.0-5/ ?
[Galaxy S 5 Original Android Development] Minotaur:
Unfortunately not for me, with klteduos build at least.

Where would the logfiles be located?
[Galaxy S 5 Original Android Development] ipharus:
still crashing :angel:

trying to get recovery log

got it, attached
[Galaxy S 5 Original Android Development] jcadduono:
connect with adb (in twrp),

cat /proc/last_kmsg > /sdcard/twrp_last_kmsg

dmesg > /sdcard/twrp_kmsg

grab those files from sdcard
[Galaxy S 5 Original Android Development] Minotaur:
Damn, I don't have any adb stuff installed on this computer.

Also, I have my SD as adopted storage, so it may not work anyway?
[Galaxy S 5 Original Android Development] ipharus:
tried that, but no luck :

root@:/ # cat /proc/last_kmsg > /sdcard/backups/last_kmsg.txt

sh: cat: /proc/last_kmsg: No such file or directory
[Galaxy S 5 Original Android Development] ipharus:
deleted
[Galaxy S 5 Original Android Development] jcadduono:
ok try -6 i forgot to enable last_kmsg (make sure you get the kmsg from after crashing with -6)
[Galaxy S 5 Original Android Development] ipharus:
Still no joy, recovery log attached, no last_kmsg in proc
[Galaxy S 5 Original Android Development] jcadduono:
ya sorry recovery.log is useless since the first one (i just wanted to check some mounting changes), it doesnt show reasons for rebooting

not sure why /proc/last_kmsg doesnt exist, it's enabled

solved the issue, lol, made the same changes to usb init on my own devices tree and ran into the same problems, was just missing disable of usb before trying to change mode resulting in usb driver crash
[Galaxy S 5 Original Android Development] ipharus:
I suspected as much, dho yet kept hoping you could do some magic on them. Tried another time to get a kmsg but still no luck. reboot into recovery, boot back to system, no last_kmsg in proc :confused:
[Galaxy S 5 Original Android Development] jcadduono:
yeah both kernels need last_kmsg enabled (system and recovery)

try https://idlekernel.com/twrp/klte/3.0.0-7/

i fixed an issue with usb init.rc that was causing a crash at the time of button loading
[Galaxy S 5 Original Android Development] ipharus:
I'll try it as soon as I get home.

It works ! :victory: No more reboots, I didn't flash anything (yet), but navigation was smooth.

last_kmsg thingy is still not working for me dho.

I'm on ResurrectionRemix with CM13 Boeffla kernel (beta 14) and since you mentioned kmsg is kernel related I reverted back to stock RR kernel.

Recovery log attached (still hoping for magic, it does seem to work :good:)
[Galaxy S 5 Original Android Development] mauriicio21:
All fine here, flash 2-3 files and works

Enviado de meu SM-G900F usando Tapatalk
[Galaxy S 5 Original Android Development] Minotaur:
Pressing buttons works for me as well.

However, the "Failed to setup adopted storage decryption" message is still present.
[Galaxy S 5 Original Android Development] j1gga84:
When I want to restore my modem I get the following error: extractTarFork() process ended with ERROR: 255

I am using TWRP 3.0.0-3 of [MENTION=5672995]jcadduono[/MENTION], what could be the matter?

regards
[Galaxy S 5 Original Android Development] jcadduono:
you're out of date
[Galaxy S 5 Original Android Development] j1gga84:
You mean out of date of the recovery build?

What is the newest? 3.0.0-6?

Regards

Sent from my SM-G900F using german Tapatalk 4
[Galaxy S 5 Original Android Development] mauriicio21:
3.0.0-7
[Galaxy S 5 Original Android Development] cowgaR:
TWRP and adopted storage (Android 6.0) troubles

Hello all,

GS5 klte version running CM13 here (which runs perfectly fine on this device) with TWRP 3.0

I jumped the ship and select adopted storage Marshmallow feature to test it out with 64GB Sandisk Extreme Pro card. Android formatted it to ext4, encrypted my microSD card and because I have choosen to move data from my phone (in adopted storage wizard) the default storage became my microSD card (which is much slower than internal I know) to install all future applications, store their data, downloads etc....

I wanted to flash today's CM13 nightly after doing this, but TWRP 3.0 won't see anything in sdcard folder (or data\media\0 for that matter) only an empty TWRP folder. I assume all is encrypted on my microSD hence why, but it should at least see the internal storage of the phone (which should not be encrypted and shares same sdcard folder).

Any solution how to easily download/flash nightlies now (autoupdate failed...)?

Thank you
[Galaxy S 5 Original Android Development] ipharus:
I also made the switch to adopted storage, and selected the external SD as my primary storage. There is indeed no way (yet) to access the data on the external SDcard. So I copy the files to be flashed to /data/media/0 with rootexplorer, reboot to recovery and flash from there.

Works for me, good luck.
[Galaxy S 5 Original Android Development] nunofgrd:
I have cmw recovery ,never never have problems
[Galaxy S 5 Original Android Development] kris_l:
Hi what is the difference between twrp 3

0.0-0 and 3.0.0-7?
[Galaxy S 5 Original Android Development] Dennys_Santos:
Full MTP Enabled :laugh: :laugh: :laugh:
[Galaxy S 5 Original Android Development] aeonix_05:
Finally! That is why Im keeping from updating and staying with KT TWRP because of MTP. Where to enable?
[Galaxy S 5 Original Android Development] DirkStorck:
It's automatically enabled. Only need to plugin the USB cable
[Galaxy S 5 Original Android Development] Crussader:
MTP works on SD card as well? I've tried it but I could only access the Internal memory through MTP.
[Galaxy S 5 Original Android Development] aguarello:
[MENTION=5672995]jcadduono[/MENTION]

Will you finally make this official TWRP? :laugh:
[Galaxy S 5 Original Android Development] jcadduono:
yeah i guess so..i was hoping to find a fix to the adopted storage problem before pushing it out as official :(

(im also waiting on another change to be accepted before that, which is restoring to read only partitions, so modem backups arent broken)
[Galaxy S 5 Original Android Development] haggertk:
It seems like decryption isn't working at all, at least for me. This could impact adopted storage since all adopted storage is encrypted, independent of whether /data is.

Is there anyone using this latest with encrypted userdata?
[Galaxy S 5 Original Android Development] revanmj:
I recently bought Nexus 5X and from reading its forum I think that TWRP's support for decrypting data was meant for /data, not SD cards (I think it works a little bit different). So there may lay the source of the issue on klte.
[Galaxy S 5 Original Android Development] haggertk:
The official TWRP builds work great for jfltevzw and d2vzw, both with adopted storage and encrypted userdata. There has to be something not quite square in the device tree or TW options. I haven't had time to dig in and see what's going on just yet.

KT recovery handles the encrypted userdata, but obviously not adopted storage.
[Galaxy S 5 Original Android Development] Dennys_Santos:
I am using the version 3.0.0-7 and not being able to restore a backup, occurring the error:

extractTarFork() process ended with ERROR: 255

Any idea how to solve the problem?
[Galaxy S 5 Original Android Development] j1gga84:
Does this error occur while trying to restore modem? If yes that is a known problem.

Regards

Sent from my SM-G900F using german Tapatalk 4
[Galaxy S 5 Original Android Development] Dennys_Santos:
Yes!!! :crying:

So the solution for now is not backup or restore modem?
[Galaxy S 5 Original Android Development] j1gga84:
I don't know if it works with official 3.0.0-0 but yes, you can only backup but not restore at the moment.

More important for me is that backup and restore of EFS works.

You can flash the modem anytime with ODIN.

Regards

Sent from my SM-G900F using german Tapatalk 4
[Galaxy S 5 Original Android Development] mauriicio21:
using 3.0.0-7 with official 6.0.1 900M i cant see micro sd :/

something has changed with update
[Galaxy S 5 Original Android Development] Dennys_Santos:
Me too the same problem! :crying: :crying: :crying:

Apparently it's an incompatibility with the Bootloader MM.

I hope that developer can solve this problem.
[Galaxy S 5 Original Android Development] Minotaur:
Are you using the SD as adopted storage?
[Galaxy S 5 Original Android Development] mauriicio21:
Nop

Installed marshmallow and twrp didnt see mine external storage, with solid explorer i can see

Enviado de meu SM-G900M usando Tapatalk
[Galaxy S 5 Original Android Development] !crazy:
Does previous version of TWRP work?
[Galaxy S 5 Original Android Development] Minotaur:
I'm pretty sure that even 3.0.0-0 worked under MM for me - could see the entire SD contents without a problem (while I was using the SD as external storage)
[Galaxy S 5 Original Android Development] Dennys_Santos:
Yes, work fine on 3.0.0-0, but MTP not.

Thanks dude.
[Galaxy S 5 Original Android Development] mauriicio21:
3.0.0-7 mtp works

Enviado de meu SM-G900M usando Tapatalk
[Galaxy S 5 Original Android Development] venkatsiddhartha:
do u guys TWRP recovery for samsung galaxy s5(SMG900H). .. .?
[Galaxy S 5 Original Android Development] Dennys_Santos:
Yes my friend, MTP works from 3.0.0.-1 to version 3.0.0-7 and they all work in perfect ROMs Lollipop (5.0 or 5.1.1), but when you install a ROM Marshmallow 6.0.1 the recovery no longer recognizes the SD card, because there is a mismatch even with MM 6.0.1 :crying:

So you have to go back to the official version 3.0.0-0 so you can make backups or install anything that is in located in Sd Card. :(

But we already know that the MTP is not active in fotne code version 3.0.0-0, at least for now is this; waiting out an updated version. :fingers-crossed:

A big hug "Brazuca".

"Fora Dilma, fora PT"
[Galaxy S 5 Original Android Development] ad0dh67:
uhm :rolleyes: i use twrp 3.0.0.7 and use mm 6.0.1 s7 port with mm bootloader and i can install from sd card
[Galaxy S 5 Original Android Development] Dennys_Santos:
Here I have tried several times and failed to make the TWRP recognize the SD Card.

My installation process:

1) I installed the oficial ROM Stock "TTT-G900MUBU1CPC3" by Odin

2) After finishing the installation I installed TWRP 3.0.0-7 by Odin.

3) Soon after installed Root (file BETA-SuperSU-v2.68-20160228150503.zip)

4) Kept all the time necessary for the ROM is completed in the first boot.

After I finished the configuration of the applications I went back to the Recovery to install some MOD's I have and was no longer recognizing the SD card, so I had to go back to version 3.0.0-0

So...

Before you were the Bootloader LP 5.1.1, correct?

You do not directly installed a ROM Stock Official MM 6.0.1?

So you decided to install a new bootloader MM 6.0.1 and 6.0.1 MM Modem and only then install the ROM port S7.

ROM Insanity S7 v1.5 or Sixperience S7 v1 ?

Or could describe the sequence that made?

You must have some difference from my installation process" :eek: :eek:
[Galaxy S 5 Original Android Development] ad0dh67:
i use sixperience rom, all i did was flash bootloader and modem with odin, turned of autoreboot before flashing and turned on update bootloader. pulled out batery, waited 10 sec then did go strait to twrp recovery, advanced wipe, flashed rom, wipe cache and reboot phone. i use cpb2 mm modem and bootloader. g900f ;)
[Galaxy S 5 Original Android Development] j1gga84:
TWRP 3.0.1-0 was released ;)

Regards

Sent from my SM-G900F using german Tapatalk 4
[Galaxy S 5 Original Android Development] DirkStorck:
[MENTION=5672995]jcadduono[/MENTION] will you release you version with MTP enabled of TWRP 3.0.1-0? :fingers-crossed:
[Galaxy S 5 Original Android Development] j1gga84:
Also the brightness control does not work with 3.0.1-0

I don't know why this is not already fixed..

Regards

Sent from my SM-G900F using german Tapatalk 4
[Galaxy S 5 Original Android Development] aosp:
https://idlekernel.com/twrp/klte/testing/twrp-3.0.1-1-klte.img

https://idlekernel.com/twrp/klte/testing/twrp-3.0.1-1-klte.tar.md5

https://idlekernel.com/twrp/klte/testing/twrp-3.0.1-1-klte.zip
[Galaxy S 5 Original Android Development] DirkStorck:
[MENTION=2838735]aosp[/MENTION] are these the MTP fixed versions?

---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ----------

@jcadduono would it for you be possible to make your MTP fix in a recovery for another device like the lt03wifiue?
[Galaxy S 5 Original Android Development] aosp:
Only [MENTION=5672995]jcadduono[/MENTION] can answer that question ;)
[Galaxy S 5 Original Android Development] HrRodan:
Adopted storage

The adopted storage can still not be accesed in 3.0.1. Is one of the unofficial versions working in this regard?
[Galaxy S 5 Original Android Development] yurividal:
MTP work with this?
[Galaxy S 5 Original Android Development] It_ler:
Your last link should be

https://idlekernel.com/twrp/klte/testing/twrp-3.0.1-1-klte.zip ... typo I guess [emoji6]

Signature:

Device:

SGS5 (SM-G900F)

ROM:

AllianceROM v10

Kernel:

Stock XXU1BOH4 kernel

Recovery:

TWRP recovery

Modem:

XXU1BOJ1

---------- Post added at 17:59 ---------- Previous post was at 17:49 ----------

Yes, MTP working fine here with this version. [emoji106]

Signature:

Device:

SGS5 (SM-G900F)

ROM:

AllianceROM v10

Kernel:

Stock XXU1BOH4 kernel

Recovery:

TWRP recovery

Modem:

XXU1BOJ1

---------- Post added at 18:01 ---------- Previous post was at 17:59 ----------

Brightness control works in aosp's TWRP 3.0.1-1.

Signature:

Device:

SGS5 (SM-G900F)

ROM:

AllianceROM v10

Kernel:

Stock XXU1BOH4 kernel

Recovery:

TWRP recovery

Modem:

XXU1BOJ1
[Galaxy S 5 Original Android Development] kris_l:
Hi, would it be possible to add support for tar.md5 firmware file? Same as in flashfire - with option which partition to flash?
[Galaxy S 5 Original Android Development] Crussader:
Funny all these users asking if MTP work without testing themselves....
[Galaxy S 5 Original Android Development] DirkStorck:
I think the process and percentage gets shown a bit false with latest TWRP ;)
[Galaxy S 5 Original Android Development] Dennys_Santos:
This generates an error (-1) at the end of any ROM installation operation or Backup / Restore using version 3.0.1-1

unmount of /system failed (-1): Device or resource busy.

----------

I managed to identify the problem, this version does not support F2FS file system. :( :( :(

Please implement this feature!
[Galaxy S 5 Original Android Development] jcadduono:
that's not true, but it it only happening with f2fs restore?

i really can't help anyone without having logs, so if you wanna be useful, then grab some (restore something small maybe, and install a rom that causes that problem)