{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
Welcome to TWRP for the Samsung Galaxy Z Fold2 5G. Samsung were kind enough to release the kernel source code ahead of the device itself, which enabled me to have TWRP ready and waiting when the courier rang my doorbell with my new phone. It's not often that a device sees a day 0 TWRP release.
The image of TWRP available here will work on all F916B, F916N and F9160 devices.
Installation
Only proceed if you are comfortable with low-level device management and are capable of recovering an unbootable device, should an unforeseen mishap occur.
Unlock your device's bootloader and then install the recovery image below. If you use Odin to flash it, remember to rename the image recovery.img and tar it before flashing. You will also need to flash a neutralised vbmeta.img image if you have not already disarmed verified boot.
Post-installation
The Z Fold2 5G utilises proprietary file-based encryption (FBE) in its factory state for the user data partition. TWRP cannot decrypt this, however, so it must be removed. Otherwise, you will not be able to perform back-ups and restores.
To remove encryption from your device, please use TWRP to flash the Samsung multi-disabler and then format /data again. You must use at least v2.5 of the multi-disabler.
Latest releases
These builds are stable and known to perform well on many users' devices.
Android 11 (CTLL firmware)
twrp-f2q-3.5.0_10-A11_3_ianmacd.img
Android 10 (BTJ1 firmware)
twrp-f2q-3.5.0_10-2_ianmacd.img
Known issues
TWRP is displayed only on the device's main (inner) screen.
Haptic feedback does not work.
Source
TWRP device tree for the Galaxy Z Fold2 5G (F916B)
Kernel source code for the Galaxy Z Fold2 5G (F916B)
TWRP source code
Support
For support or just to talk about the device amongst friends, please join our small Telegram group dedicated to the full range of Galaxy foldable devices.
Support may also be found in the more general Samsung TWRP/root group.
XDA:DevDB Information
TWRP for the Samsung Galaxy Z Fold2 5G, Tool/Utility for the Samsung Galaxy Z Fold2
Contributors
ianmacd
Version Information
Status: Production
Current Production Version: 3.5.0-1_ianmacd
Production Release Date: 2020-12-29
Created 2020-09-16
Last Updated 2021-01-25
Changelog
2021-01-25 3.5.0_A11-3
Fix spurious attempt to perform digest authentication when flashing .apk file.
2021-01-25 3.5.0_A11-2
TWRP will now include files named Magisk.apk, app-release.apk or app-debug.apk in the list of flashable .zip files. This is to accommodate the new packaging of Magisk as a payload within the manager app.
2021-01-19 3.5.0_A11-1
First release for Android 11.
With kernel built for CTLL firmware.
2021-01-19 3.5.0-2
Merge post-3.5.0 release bug fixes.
2020-12-29 3.5.0-1
Update to TWRP 3.5.0.
2020-12-23 3.4.0-3
Fixed bug that causes unmounting of System when Advanced menu is entered.
2020-12-20 3.4.0-1
First production release.
Working MTP implementation.
2020-11-06 3.4.0-1a20
Fixed image back-up of Optics partition.
logcat is now enabled in recovery.
With kernel built for BTJ1 firmware.
2020-10-07 3.4.0-1a17
With kernel built for BTIA firmware.
2020-09-29 3.4.0-1a15
Ignore touch sensor input from front screen.
Align camera recess within status bar.
2020-09-15 3.4.0-1a12
Day 0 TWRP release.
@ianmacd My Fold 2 5G is model number F916U1. Your topic and posts say this TWRP is for F916B version - is F916B the only supported Fold 2 5G model?
Apo11on said:
@ianmacd My Fold 2 5G is model number F916U1. Your topic and posts say this TWRP is for F916B version - is F916B the only supported Fold 2 5G model?
Click to expand...
Click to collapse
The U models have their bootloaders locked. The B version is an international (korean?) version which can have it's bootloader unlocked.
Correct me if I am wrong
Apo11on said:
@ianmacd My Fold 2 5G is model number F916U1. Your topic and posts say this TWRP is for F916B version - is F916B the only supported Fold 2 5G model?
Click to expand...
Click to collapse
similar topic discussed in TG group, FYI
ME（Vincent Li）：Hi Ian! @ianmacd I have a silly question wanna ask: is it compatible to flash your twrp image into my F9160(Chinese variant) model after rooting?
Click to expand...
Click to collapse
鱿鱼：[In reply to Vincent Li]
I think you’ll need to check the partition structure before flashing if I remember correctly
Click to expand...
Click to collapse
ME：[In reply to 鱿鱼]
I'm not sure whether I understand correctly or not that the partition structure would be the same across different variants (aka F916B/916U/F9160 etc.) as long as they share the same model name like Z Fold2 5G, although those variants might have different firmwares or kernels with which may affect this twrp image working properly?
Click to expand...
Click to collapse
Ian Macdonald：[In reply to Vincent Li]
I don't know how the F9160 differs from the F916B. The firmware would certainly be different, but the recovery environments need not be.
You don't have much to lose by trying it. If it doesn't work, just flash the stock recovery back.
You could also request kernel source code for your model from Samsung; then we can compare them. As of now, only the F916B has source code available, because I requested it before release.
Click to expand...
Click to collapse
Apo11on said:
@ianmacd My Fold 2 5G is model number F916U1. Your topic and posts say this TWRP is for F916B version - is F916B the only supported Fold 2 5G model?
Click to expand...
Click to collapse
@ianmacd Houston, do you readme? Can you please confirm the list of devices, supported by your build? Over.
Here is a full list of mounted partitions on my F916U1 - hope it helps.
Code:
$ cat /proc/mounts
/dev/block/dm-4 / ext4 ro,seclabel,relatime,i_version 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=5378544k,nr_inodes=1344636,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600,ptmxmode=000 0 0
none /dev/memcg cgroup rw,relatime,memory 0 0
none /dev/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
none /dev/cg2_bpf cgroup2 rw,nosuid,nodev,noexec,relatime 0 0
none /dev/cpuctl cgroup rw,nosuid,nodev,noexec,relatime,cpu 0 0
none /dev/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent 0 0
none /dev/stune cgroup rw,nosuid,nodev,noexec,relatime,schedtune 0 0
none /dev/freezer cgroup rw,relatime,freezer 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
tracefs /sys/kernel/debug/tracing tracefs rw,seclabel,relatime 0 0
bpf /sys/fs/bpf bpf rw,nosuid,nodev,noexec,relatime 0 0
pstore /sys/fs/pstore pstore rw,seclabel,nosuid,nodev,noexec,relatime 0 0
tmpfs /mnt tmpfs rw,seclabel,nosuid,nodev,noexec,relatime,size=5378544k,nr_inodes=1344636,mode=755,gid=1000 0 0
tmpfs /mnt/secure/asec tmpfs rw,seclabel,relatime,size=5378544k,nr_inodes=1344636,mode=700 0 0
tmpfs /mnt/sde tmpfs rw,seclabel,relatime,size=5378544k,nr_inodes=1344636,mode=700 0 0
/dev/block/bootdevice/by-name/persist /mnt/vendor/persist ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0
/dev/block/bootdevice/by-name/efs /mnt/vendor/efs ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0
/data/knox/secure_fs/enc_media /mnt/shell/enc_emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1000,fsgid=1000,gid=9997,multiuser,derive_gid,default_normal,reserved=20MB 0 0
/data/media /mnt/runtime/default/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid,default_normal,reserved=20MB,unshared_obb 0 0
/data/media /mnt/runtime/read/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid,default_normal,reserved=20MB,unshared_obb 0 0
/data/media /mnt/runtime/write/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid,default_normal,reserved=20MB,unshared_obb 0 0
/data/media /mnt/runtime/full/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid,default_normal,reserved=20MB,unshared_obb 0 0
tmpfs /apex tmpfs rw,seclabel,nosuid,nodev,noexec,relatime,size=5378544k,nr_inodes=1344636,mode=755 0 0
/dev/block/loop2 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0
/dev/block/loop2 /apex/com.android.conscrypt ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0
/dev/block/loop3 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0
/dev/block/loop3 /apex/com.android.apex.cts.shim ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0
/dev/block/loop4 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0
/dev/block/loop4 /apex/com.android.runtime ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0
/dev/block/loop5 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0
/dev/block/loop5 /apex/com.android.media ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0
/dev/block/loop6 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0
/dev/block/loop6 /apex/com.android.media.swcodec ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0
/dev/block/loop7 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0
/dev/block/loop7 /apex/com.android.resolv ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0
/dev/block/loop8 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0
/dev/block/loop8 /apex/com.android.tzdata ext4 ro,dirsync,seclabel,nodev,noatime,i_version 0 0
/dev/block/platform/soc/1d84000.ufshc/by-name/metadata /metadata ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0
/dev/block/dm-5 /product ext4 ro,seclabel,relatime,i_version 0 0
/dev/block/dm-6 /vendor ext4 ro,seclabel,relatime,i_version 0 0
/dev/block/bootdevice/by-name/apnhlos /vendor/firmware_mnt vfat ro,context=u:object_r:firmware_file:s0,relatime,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/bootdevice/by-name/modem /vendor/firmware-modem vfat ro,context=u:object_r:firmware_file:s0,relatime,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/bootdevice/by-name/dsp /vendor/dsp ext4 ro,seclabel,nosuid,nodev,relatime,i_version 0 0
/dev/block/dm-7 /odm ext4 ro,seclabel,relatime,i_version 0 0
/dev/block/dm-8 /prism ext4 ro,seclabel,relatime,i_version 0 0
/dev/block/dm-9 /optics ext4 ro,seclabel,relatime,i_version 0 0
none /acct cgroup rw,nosuid,nodev,noexec,relatime,cpuacct 0 0
none /config configfs rw,nosuid,nodev,noexec,relatime 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0
/dev/block/bootdevice/by-name/sec_efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0
/dev/block/bootdevice/by-name/carrier /carrier ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0
/dev/block/bootdevice/by-name/dqmdbg /dqmdbg ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0
/dev/block/bootdevice/by-name/spu /spu ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0
/dev/block/bootdevice/by-name/keydata /keydata ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0
/dev/block/bootdevice/by-name/keyrefuge /keyrefuge ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0
/dev/block/bootdevice/by-name/omr /omr ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0
/dev/block/bootdevice/by-name/userdata /data f2fs rw,lazytime,seclabel,nosuid,nodev,noatime,background_gc=on,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,active_logs=6,reserve_root=32768,reserve_core=1280,resuid=0,resgid=5678,usrquota,grpquota,alloc_mode=default,fsync_mode=nobarrier 0 0
tmpfs /storage tmpfs rw,seclabel,nosuid,nodev,noexec,relatime,size=5378544k,nr_inodes=1344636,mode=755,gid=1000 0 0
/data/media /storage/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid,default_normal,reserved=20MB,unshared_obb 0 0
tmpfs /storage/self tmpfs rw,seclabel,nosuid,nodev,noexec,relatime,size=5378544k,nr_inodes=1344636,mode=755,gid=1000 0 0
$
Apo11on said:
@ianmacd Houston, do you readme? Can you please confirm the list of devices, supported by your build? Over.
Click to expand...
Click to collapse
It will work on the F916B. It may also work on the F9160 and the F916N.
As far as US versions are concerned, the U and U1 models have locked bootloaders that can only be unlocked using a paid service. Once that has been done, this version of TWRP may work on them.
I can't say with any more certainty than that, because my own device is the international model, the F916B.
Even if this version doesn't work on the 9160, the N, the U and the U1, it wouldn't be a huge amount of work to make those work, too; probably just a question of replacing the kernel with one specific to those devices.
ianmacd said:
It will work on the F916B. It may also work on the F9160 and the F916N.
As far as US versions are concerned, the U and U1 models have locked bootloaders that can only be unlocked using a paid service. Once that has been done, this version of TWRP may work on them.
Click to expand...
Click to collapse
Do you happen to know of this paid service or where it's available? Depending on the price, I would be willing to consider paying to have the phone unlocked if that's what needs to be done.
WyldOne91 said:
Do you happen to know of this paid service or where it's available? Depending on the price, I would be willing to consider paying to have the phone unlocked if that's what needs to be done.
Click to expand...
Click to collapse
+1 was going to ask the exact same question
WyldOne91 said:
Do you happen to know of this paid service or where it's available? Depending on the price, I would be willing to consider paying to have the phone unlocked if that's what needs to be done.
Click to expand...
Click to collapse
I have never used this service and cannot vouch for its effectiveness or safety.
https://labs.xda-developers.com/store/app/tk.zwander.galaxyunlock
ianmacd said:
I have never used this service and cannot vouch for its effectiveness or safety.
https://labs.xda-developers.com/store/app/tk.zwander.galaxyunlock
Click to expand...
Click to collapse
Thanks for the warning, at the very least I'll check it out.
Hi @ianmacd
how would we go about flashing gsi roms with the new twrp since system slot is now gone
---------- Post added at 06:04 PM ---------- Previous post was at 06:03 PM ----------
Hi @ianmacd
how would we go about flashing gsi roms with the new twrp since system slot is now gone
TheUndertaker21 said:
Hi @ianmacd
how would we go about flashing gsi roms with the new twrp since system slot is now gone
Click to expand...
Click to collapse
You have to flash the super partition now. The System partition is a logical partition inside the super partition, along with Vendor, Product and Odm.
ianmacd said:
You have to flash the super partition now. The System partition is a logical partition inside the super partition, along with Vendor, Product and Odm.
Click to expand...
Click to collapse
Oh word
Is there a tool that can turn these system img into super partition?
Thanks again
ianmacd said:
It will work on the F916B. It may also work on the F9160 and the F916N.
As far as US versions are concerned, the U and U1 models have locked bootloaders that can only be unlocked using a paid service. Once that has been done, this version of TWRP may work on them.
I can't say with any more certainty than that, because my own device is the international model, the F916B.
Even if this version doesn't work on the 9160, the N, the U and the U1, it wouldn't be a huge amount of work to make those work, too; probably just a question of replacing the kernel with one specific to those devices.
Click to expand...
Click to collapse
Can confirm for the F916U that it does not work. At least in Odin it gets stuck on "File Analysis" and nothing happens.
EDIT: Nevermind it works fine on F916U
Chickenbone20 said:
Can confirm for the F916U that it does not work. At least in Odin it gets stuck on "File Analysis" and nothing happens.
Click to expand...
Click to collapse
Did you rename the image recovery.img and tar it? You don't stand a chance of it working if you didn't do that.
3.4.0-1a15 released.
I have just released a new alpha build of TWRP.
This one fixes the issue of touch sensor input from the front screen not being ignored. If you experienced any ghost touch input issues when using TWRP while holding the device in your hand, this is the reason.
I can't access to files on storage or sdcard so i can't flash anything... how can i resolve this?
Just curious what the chances are that this work will develop into granting us mortals the ability to root and install custom roms?
@Chickenbone20
wondering if you unlocked the bootloader or without it? i am in the process of buying us model or international model.
Thanks
Related
i m going to show you my mount :
Code:
# mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioch
arset=utf8 0 0
/dev/stl12 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=u
tf8 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset
=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.speedsoftware.rootexplorer-1 vfat ro,dirsync,nosui
d,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859
-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
i try to recover my efs partitions with odin but nothing to work ,
i transform my backup stl5.rfs > efs.rfs > efs.tar
for using with odin : make a error invalid binary model
so i don t know how to repair this issue
thank you to help me !!!!
There's no way to restore the efs to this device
This was sent from a Galaxy Ace. Problem?
so how i can repair that ?
just with box?
You cannot repair the efs partition
Sent from my GT-S5830 using xda premium
i dont think is not posible to repair this issue ...
if i have one backup ? like stl5.rfs
i try with terminal but no working ...
may be just only with box like z3x i can to repair ...
or someone can to tell me how to recover like 000000 imei ?
thank you
celica7 said:
i dont think is not posible to repair this issue ...
if i have one backup ? like stl5.rfs
i try with terminal but no working ...
may be just only with box like z3x i can to repair ...
or someone can to tell me how to recover like 000000 imei ?
thank you
Click to expand...
Click to collapse
The Galaxy Ace has a closed up efs partition that until the best of devs do not know how to recover . It's useless to ask , just send it for repair .
This was sent from a Galaxy Ace. Problem?
Good morning, lovely HTC ONE owners!
Yesterday, I manually deleted a folder from my HTC ONE containing an important file. I have tried finding a software or app to restore that folder, but it seems that none of them can detect the symlinked pseudo SD card of the HTC ONE.
Is there any chance to get back my data? In the future, I will use the app 'Dumpster', which only throws files into a special trash bin where files can be restored if necessary...
SecUpwN said:
but it seems that none of them can detect the symlinked pseudo SD card of the HTC ONE.
Click to expand...
Click to collapse
which filesystem?
We need to know which file you deleted
tryin said:
which filesystem?
Click to expand...
Click to collapse
Thanks for helping, guys. The HTC ONE doesn't have an SD card, thus only offering 32 GB of internal memory. I guess that part has no filesystem, correct me if I'm wrong.
matt95 said:
We need to know which file you deleted
Click to expand...
Click to collapse
A file inside a folder with the extension *.bck - it was a settings file created by another app. It is important to me because it contains phone numbers I have not written down. What to do?
I don't think you'll get it back man....
matt95 said:
I don't think you'll get it back man....
Click to expand...
Click to collapse
Darn. Maybe it's gods will. For other peeps reading this: Install DUMPSTER to avoid deletion without being able to recover files. This recycle bin will keep your deleted files for a set amount of time and delete them for good afterwards. If I had only known this app before, this wouldn't have happened.
SecUpwN said:
...32 GB of internal memory. I guess that part has no filesystem, correct me if I'm wrong.
Click to expand...
Click to collapse
No filesystem..!? Mmm it sound a bit strange... .
There are some nice tools for data carving, take a look at Foremost and Scalpel. Quite easy to use, could recover your files...
tryin said:
No filesystem..!? Mmm it sound a bit strange... .
There are some nice tools for data carving, take a look at Foremost and Scalpel. Quite easy to use, could recover your files...
Click to expand...
Click to collapse
I got an HTC with 32 GB internal storage, you tell me which file system this thing has, please. ^^ You receive a big THUMB UP for your recommendations, are there recommendable APPS for recovery?
SecUpwN said:
I got an HTC with 32 GB internal storage, you tell me which file system this thing has, please. ^^ You receive a big THUMB UP for your recommendations, are there recommendable APPS for recovery?
Click to expand...
Click to collapse
:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/timer_group cgroup rw,relatime,timer_slack 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/com.nuance.swype.dtc-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/stericson.busybox.donate-2 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.gameloft.android.ANMP.GloftA8HM-2 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-3 /mnt/asec/com.eclipsim.gpstoolbox.pro-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-4 /mnt/asec/com.koushikdutta.backup.license-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
/dev/block/dm-5 /mnt/asec/com.eightyeightgames.tenmillion-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p35 /system ext4 ro,seclabel,noatime,nobarrier 0 0
/dev/block/mmcblk0p37 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc 0 0
tmpfs /data/qcks tmpfs rw,seclabel,relatime,size=20480k,mode=750,gid=1000 0 0
tmpfs /data/efs tmpfs rw,seclabel,relatime,size=20480k,mode=750,gid=1000 0 0
tmpfs /data/secure/data tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/mmcblk0p36 /cache ext4 rw,seclabel,nosuid,nodev,noatime,nobarrier 0 0
/dev/block/mmcblk0p22 /devlog ext4 rw,seclabel,nosuid,nodev,noatime,nobarrier,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p31 /firmware/mdm vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p16 /firmware/q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
@BenPope, what's that supposed to be?
SecUpwN said:
@BenPope, what's that supposed to be?
Click to expand...
Click to collapse
That would be the list of filesystems, their mount points and parameters on my phone.
As you can see, it's not as simple as "a filesystem".
It is possible, try this guide: htc phone photo file recovery
hope this helps.
jackthomas251 said:
From phone it's much more complicated.
Click to expand...
Click to collapse
But not impossible?
Re: File Recovery after Deletion
I have also done this kind of mistake previously then my friend told me about Remo Android Recovery software and seriously it worked for me as a miracle. I got back all my accidentally deleted photos. You can give a try to this to recover your deleted folder. Hope you will get success.
This topic is like more than a month old, I guess there's nothing to rescue anymore. But thanks for the hints, everyone should install DUMPSTER beforehand.
Even worse.... I deleted storage/emulated/0 folder on my htc one
Ok. So check this ish..... I was tryna free up room on my htc one, so i went into file manager, was lookin for unnecessary stuff to delete, and thats when i notice.. Inside the emulated folder are 2 folders, one named "0" and one named "legacy" so after going back and forth one to the other... I realized that the same exact files and folders as the other, so my retarded asss deleted one thinking it was a whole duplicated folder. Ok, yeah, i messed that one up bad. How could i be so stupid? So i looked up some claims of some solutions, downloaded the pc software they swore would recover everything. Nada... Zip. Zero... What can i do? The htc one is no removable sd card or battery and my phone is not rooted.... Please get back at me on this... Im beginning to think,an htc csr or one of the smartest phone dudes on this forum will know how or what to do... :crying::crying::angel:
Oh yeah i forgot....
I think i should add that when i deleted the 0 folder, it wiped the legacy one as if it were its mirror or something
datbitch said:
I think i should add that when i deleted the 0 folder, it wiped the legacy one as if it were its mirror or something
Click to expand...
Click to collapse
Sorry pal, no chance to recover anything. If you continued to use your phone after erasing all of that, it has been overwritten multiple times already. To make sure such thing does not happen again, install ES File Explorer and enable the RECYCLE BIN in the options - thus, you can recover deleted files easily. And for cleaning your device, always use SD Maid.
Ok, there seems to be very little information regarding rooting this particular model. I am infinitely irked by the stupid Samsung copy/paste bug with the only options to fix are wipe(which I did once and the bug returned), root or return/buy new device.
Wipe I did once. Bug returned. Return? Ugh...that is a severe PITA to do here (went through it once with a bad GT 7"). Rooting is the next...err...'easiest' option. The problem is, there is little information on XDA regarding this particular model. I saw one thread that started but the user never followed up with giving out his partitions info. So here is mine and hopefully some kind soul will help me root this (f)sucker and all will be well and right with the world again. I'm not really looking for extra features(althoughthey would be a nice perk), I just want to fix this copy/paste issue (and maybe the stupid sporadic switch from wifi-to-4G without requiring a reboot).
Partition info:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=111 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p24 /system ext4 ro,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p28 /data ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p25 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p27 /preload ext4 ro,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p21 /efs ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p13 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/mmcblk0p17 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
Please let me know if there is any other info needed.
DragonDon said:
Ok, there seems to be very little information regarding rooting this particular model. I am infinitely irked by the stupid Samsung copy/paste bug with the only options to fix are wipe(which I did once and the bug returned), root or return/buy new device.
Wipe I did once. Bug returned. Return? Ugh...that is a severe PITA to do here (went through it once with a bad GT 7"). Rooting is the next...err...'easiest' option. The problem is, there is little information on XDA regarding this particular model. I saw one thread that started but the user never followed up with giving out his partitions info. So here is mine and hopefully some kind soul will help me root this (f)sucker and all will be well and right with the world again. I'm not really looking for extra features(althoughthey would be a nice perk), I just want to fix this copy/paste issue (and maybe the stupid sporadic switch from wifi-to-4G without requiring a reboot).
Partition info:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=111 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p24 /system ext4 ro,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p28 /data ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p25 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p27 /preload ext4 ro,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p21 /efs ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p13 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/mmcblk0p17 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
Please let me know if there is any other info needed.
Click to expand...
Click to collapse
im not sure if this is going to help you but http://forum.xda-developers.com/showthread.php?t=2679066
Thanks Quantra! That just may come in handy.
Well as the title says, while installing twrp I erased cache. Now recovery loops, so how do I rebuild my cache? Does anyone know? I'm rooted, S-off, running stock KK up to date.
godzilla61 said:
Well as the title says, while installing twrp I erased cache. Now recovery loops, so how do I rebuild my cache? Does anyone know? I'm rooted, S-off, running stock KK up to date.
Click to expand...
Click to collapse
Reinstall twrp?
Sent from my lunar powered Inverted ViperONE using Tapatalk 2
That was the first thing I tried, no-joy!
godzilla61 said:
That was the first thing I tried, no-joy!
Click to expand...
Click to collapse
Re flash the stock kitkat update. Clearing your cache shouldn't have broke recovery or the rom. You either wiped something you shouldn't have and didn't tell us or somethings broken with your copy of TWRP
Kraizk said:
Re flash the stock kitkat update. Clearing your cache shouldn't have broke recovery or the rom. You either wiped something you shouldn't have and didn't tell us or somethings broken with your copy of TWRP
Click to expand...
Click to collapse
Some folks execute a "fastboot erase cache" after flashing a recovery. Do not do that! Instead, either "fastboot format cache" or leave it alone. The fastboot erase cache command just blows the file system away and leaves you with an unmountable /cache partition until it's formatted (wipe will do that if you end up with errors about 'cannot mount /cache').
Click to expand...
Click to collapse
The second quote is from the dev, now on to my question, how do I rebuild my cache partition? There has to be a way without loosing everything....
godzilla61 said:
The second quote is from the dev, now on to my question, how do I rebuild my cache partition? There has to be a way without loosing everything....
Click to expand...
Click to collapse
rebuild your cache partition? or your cache filesystem? two totally different things.
if your disk is wrecked (partitions no longer valid) you're likely into RUU.
If your disk is fine (partitions are there, just no file system), TWRP should boot fine, it'll just piss and moan about /cache not being there. If it keeps restarting to the curtain (the TWRP graphic while booting) no big deal -- adb should still be up. If it does come up, you can 'wipe cache' and it'll rebuild the file system for you. Either that or use fastboot to format it.
Either way -- if you actually placed interesting stuff on /cache (why would you do that?), it's gone. The cache partition is 99% useless to users, so it would surprise me if you put stuff there.
Here's what I'd do:
1) Boot TWRP (get my 2.7.1.1 version, fastboot flash it, start it up);
2) plug the phone into usb:
3) adb shell
4) mount
copy/paste what that last command says and let's see what's really up. If TWRP won't boot, you have bigger problems than you lead us to believe.
Ok, more info: phone works. no recovery it just keeps showing the curtain over and over...... So now ADB....can't do a thing with it. Can't fastboot flash anything.....error: cannot load 'openrecovery-m7wls-2.7.1.1-06-05-2014' so what now?
[email protected]:/ $ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
none /dev/timer_group cgroup rw,relatime,timer_slack 0 0
/dev/block/mmcblk0p37 /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/mmcblk0p39 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto
_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p38 /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered
0 0
/dev/block/mmcblk0p22 /devlog ext4 rw,seclabel,nosuid,nodev,noatime 0 0
/dev/block/mmcblk0p30 /carrier ext4 rw,seclabel,nosuid,nodev,noatime,grpid,data=
ordered 0 0
/dev/block/mmcblk0p33 /firmware/mdm vfat ro,relatime,fmask=0000,dmask=0000,allow
_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro
0 0
tmpfs /data/qcks tmpfs rw,seclabel,relatime,size=20480k,mode=750,gid=1000 0 0
tmpfs /data/efs tmpfs rw,seclabel,relatime,size=20480k,mode=750,gid=1000 0 0
/dev/block/mmcblk0p16 /firmware/q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_
utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro
0 0
tmpfs /data/secure/data tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_i
d=1023,default_permissions,allow_other 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,use
r_id=0,group_id=0,allow_other 0 0
[email protected]:/ $
Click to expand...
Click to collapse
godzilla61 said:
Ok, more info: phone works. no recovery it just keeps showing the curtain over and over...... So now ADB....can't do a thing with it. Can't fastboot flash anything.....error: cannot load 'openrecovery-m7wls-2.7.1.1-06-05-2014' so what now?
Click to expand...
Click to collapse
I have no idea why you think /cache is your problem:
"/dev/block/mmcblk0p38 /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0"
It mounted fine.
As for flashing TWRP, you have to give fastboot an actual file:
"error: cannot load 'openrecovery-m7wls-2.7.1.1-06-05-2014"
The file is (assuming you didn't rename it) "openrecovery-m7wls-2.7.1.1-06-05-2014.img" -- there's an extension on the end.
If you did rename it, then you didn't place the file where you have fastboot. Either give the *full path* to the .img file, or move (or copy) it to the directory in which fastboot exists.
Thanks for taking the time to help! This gave me a reason to update my tool box for android. It's funny I never had to use a file ext. before when installing. It was that simple! So twrp is up and running again, I wonder why it was looping.....for another time perhaps. Thanks once again tdhite!!!
So i followed the guide on how to unlock bootloader, flash twrp, all that stuff, and i try to flash the pixel experience rom then i get this error. I searched up some solutions, i found one that said to change the file system to ext4 but that didn't work so im out of ideas, hope someone here can help me with it.
just reboot to recovery from twrp
amrsy said:
So i followed the guide on how to unlock bootloader, flash twrp, all that stuff, and i try to flash the pixel experience rom then i get this error. I searched up some solutions, i found one that said to change the file system to ext4 but that didn't work so im out of ideas, hope someone here can help me with it.
Click to expand...
Click to collapse
Hi.
Did you fix it?
I've tried to install my first ROM on my Xiaomi MI5s but I did not get it.
I installed the TWRP and then followed the steps of installation in the Lineage website.
I tapped on "Format Data", but I found these messages:
"failed to mount data" and "device or resource busy".
Then I tried to reboot the device and go into TWRP again and it is not there anymore. Instead, it is the xiaomi recovery.
What am I doing wrong?
I have also tried to go to WIPE -> ADVANCED WIPE -> select 'DATA' -> REPAIR OR CHANGE FILESYSTEM -> CHANGE FILESYSTEM -> EXT4, but the same error
---------- Post added at 12:16 AM ---------- Previous post was at 12:15 AM ----------
febin92 said:
just reboot to recovery from twrp
Click to expand...
Click to collapse
Is that the solution?
I was getting issues like that when I was decrypting. I found that after every new step to reboot system.
For example.
Repair data, reboot system,
After format data, reboot system,
Then wipe data , reboot system,
Then do a restore, reboot system,
You need to remount as RW. This goes for Vendor/Data/System etc.
While in TWRP type:
Code:
adb shell
cat /proc/mounts
You will get something along these lines:
Code:
rootfs / rootfs rw,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /mnt tmpfs rw,seclabel,nosuid,nodev,noexec,relatime,mode=755,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime 0 0
none /config configfs rw,relatime 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/bootdevice/by-name/vendor_a /v ext4 ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr,errors=remount-ro 0 0
/dev/block/sda13 /data ext4 ro,seclabel,relatime,resgid=1065,stripe=2,data=ordered 0 0
/dev/block/sda13 /sdcard ext4 rw,seclabel,relatime,resgid=1065,stripe=2,data=ordered 0 0
In my case TWRP was saying:
Code:
TWRP failed to mount vendor device or resource busy
TWRP failed to mount data device or resource busy
Whatever your case is just remount the partition partition that's throwing errors as RW to fix the problem.
For example:
Code:
mount -o rw,remount /dev/block/bootdevice/by-name/vendor_a
mount -o rw,remount /dev/block/sda13
This remounted both vendor and data as RW and TWRP no longer gives errors. :good: