TWRP 3.1 Backup and restore Direct to pc using ADB - OnePlus 3 Guides, News, & Discussion

TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
1.vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
2.adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
3.tweak MTP startup routines (mdmower)
4.support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
5.support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
6.better indicate to users that internal storage is not backed up (Dees_Troy)
7.improve automatic determination of TW_THEME (mdmower)
8.minimal getcap and setcap support (_that)
9.try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
10.shut off backlight with power key (mdmower)
11.timeout during FDE decrypt (Dees_Troy and nkk71)
12.support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
13.boot slot support (Dees_Troy)
14.TWRP app install prompt during reboot (Dees_Troy)
15.support for AB OTA zips (Dees_Troy)
16.support new Android 7.x log command (Dees_Troy)
17.update recovery sources to AOSP 7.1 (Dees_Troy)
18.numerous bugfixes and improvements by too many people to mention
Download:
https://twrp.me/
or use TWRP from play store
Backup & restore commands:
1.adb backup --twrp
2.adb restore (name of the backup file)
VIDEO GUIDE:
https://youtu.be/clBVD6QOpRQ

Related

[MOD][RECOVERY] All-F2FS for GT-I9190|GT-I9192|GT-I9195 [TWRP 2.8.6.0 & Philz Touch]

[MOD][RECOVERY] All-F2FS for GT-I9190|GT-I9192|GT-I9195 [TWRP 2.8.6.0 & Philz Touch]
Hi!
Here I'll try to explain how to use F2FS partitions on your Galaxy S4 Mini.
This is for "All-F2FS" that mean that /system, /cache, /data and /external SD are formatted with F2FS, keep in mind that this can work only with a compatible kernel and ROM.
About F2FS
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk (Hangul: 김재극) at Samsung for the Linux operating system kernel.
The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Samsung chose a log-structured file system approach, which it adapted to newer forms of storage. F2FS also remedies some known issues of the older log structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. Because a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), Samsung also added various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms.
Warning
* You agree to use this MOD/Guide on you own risk and I don't take any responsability if you encounter any issue or if your personal data is lost
Requirements
Your S4 Mini, GT-I9190 or GT-I9195 or GT-I9192 (serrano3g, serranolte, serranods)
An external MicroSD card or a PC (for backup/restore)
Preinstalling Steps
Backup of your personal data to an external SD card or PC (photo, music, ringtones, etc).
Make a full nandroid (just in case that you want to rollback to EXT4) and copy to your PC.
Download and copy to your External SD Card TWRP or Philz Touch with full F2FS support. (Downloads on Second Post)
Download and copy to your External SD Card latest version of f4ktion kernel or use one with All-F2FS support.
Download and copy to your External SD Card CarbonROM with F2FS support, or you can test on your favorite ROM, take in mind that using F2FS on External SD Cards will require F2FS support on your ROM of minivold for vold managed volumes. (Downloads on Second Post)
How can you test your favorite ROM?
I'll include this time CarbonROM with support for F2FS, on upcoming builds you'll need to edit manually the updater-script.
You need to edit updater-script on the zip file, you need to change the following:
Look for:
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
And change it for:
Code:
run_program("/sbin/busybox", "mount", "/system");
Look for:
Code:
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
And change it for:
Code:
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/msm_sdcc.1/by-name/system");
Installation Steps (Clean Install)
1) Install your favorite recovery and reboot to recovery.
For TWRP
1.1) Go to Settings and select "Force data and cache wipe functions to use F2FS" and if you want F2FS support on /System partition, select "Include system partition"
1.2) Now go to Wipe menu and select Format Data and type "yes" (Warning this will format Data partition and your Internal Storage, so please don't forget to make a backup of your personal data)
1.3) Optional, select Advanced Wipe menu and check System and Cache partitions to convert to F2FS respectively.
For Philz Touch
1.1) Go to Mounts and Storage and select "toggle f2fs <-> ext4 migration"
1.2) Select format /data and confirm, now select format /data and /data/media (/sd, confirm, choose f2fs option and confirm again.
1.3) Optional, you can select format /system and format /cache to convert to F2FS respectively.
2) Install your ROM as usual, then flash your GApps and f4ktion kernel in this order.
3) Restore your personal data to your internal SD Card.
If you don't want to make a clean install, you can convert /data partition to F2FS using and restoring a /data nandroid backup.
Installation Steps (Restoring /Data partition)
1) Install your favorite recovery and reboot to recovery.
For TWRP
1.1) Make a nandroid of /data partition.
1.2) Go to Settings and select "Force data and cache wipe functions to use F2FS" and if you want F2FS support on /System partition, select "Include system partition"
1.3) Now go to Wipe menu and select Advanced Wipe menu and check Data, swipe to confirm wipe.
1.4) You can restore your /data nandroid now.
1.5) Optional, you can select format /system and format /cache to convert to F2FS respectively and install a new ROM.
For Philz Touch
1.1) Make a custom nandroid of /data partition.
1.2) Go to Mounts and Storage and select "toggle f2fs <-> ext4 migration"
1.3) Select format /data and confirm, now select format /data and /data/media (/sd, confirm, choose f2fs option and confirm again.
1.4) You can restore your /data nandroid now.
1.5) Optional, you can select format /system and format /cache to convert to F2FS respectively and install a new ROM.
How to check if you have correctly formatted partitions to F2FS?
Through terminal do:
Code:
su
mount | grep f2fs
Through adb do:
Code:
adb shell
su
mount | grep f2fs
Also you can check F2FS's status by doing:
Code:
cat /sys/kernel/debug/f2fs/status
Or just install DiskInfo app
Credits
@Dees_Troy for TWRP
@ktoonsez for F2FS mod
@Phil3759 for Philz Touch
TWRP 2.8.1.0 F2FS MOD
GT-I9190
GT-I9192
GT-I9195
Philz Touch F2FS
GT-I9190
GT-I9192
GT-I9195
F4k said:
Look for:
Code:
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
And change it for:
Code:
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/msm_sdcc.1/by-name/system");
Click to expand...
Click to collapse
Do I need to do this part if I want to keep my system partition as Ext4 but wanted my data and cache partition as F2fs?
Thanks in advance
Envoyé de mon unknown en utilisant Tapatalk
Darktitor said:
Do I need to do this part if I want to keep my system partition as Ext4 but wanted my data and cache partition as F2fs?
Thanks in advance
Envoyé de mon unknown en utilisant Tapatalk
Click to expand...
Click to collapse
This step is if you want /system partition as f2fs, you can use f2fs on whatever you want.
If you don't edit updater-script, your /system partition will be formatted as ext4
Just a quick question, is this Carbon in this post the same as the latest build you have just released? Or is this one with an altered updater-script?
Phenom2122 said:
Just a quick question, is this Carbon in this post the same as the latest build you have just released? Or is this one with an altered updater-script?
Click to expand...
Click to collapse
It's the same but with modified updater-script, this version will format /system partition as f2fs, the one on Carbon's thread as ext4.
All formatted f2fs and everything flashed and running smoothly thanks f4k
Sent from my GT-I9195 using XDA Premium 4 mobile app
From now on we should unzip the rom file and change tha script to have f2fs?
Hope random reboots to stop..
Everything fine with clean install.. One bug tha colors in recent calls with tha black theme
Στάλθηκε από το GT-I9195 μου χρησιμοποιώντας Tapatalk
@F4k nice splash screen you have in your twrp recovery, also glad you added the "force wipe to use f2fs option " this way I can use the twrp themes without the need for additional changes to it.
Sent from my GT-I9195 using Tapatalk
Since doing a format of /data and /data/media Philz works correctly the first time with settings in mnt/shell/emulated/0/clockworkmod. After doing a reboot into recovery later, suddenly it has created a mnt/shell/emulated/0/0/clockworkmod and it seems to be randomly reading settings from either location ie. sometimes it will correctly launch Aroma, sometimes it wont. This is a very strange error because I went back to one of the older Philz versions and the same problem persists.
Will try out TWRP now.
can I format /system with f2fs and then just make a restore? or I have to install a new rom?
chacox said:
can I format /system with f2fs and then just make a restore? or I have to install a new rom?
Click to expand...
Click to collapse
You can try it, I tested several combinations restoring nandroid backups and they worked fine.
But I suggest you to made a full nandroid just un case.
Sent from my GT-I9190
F4k said:
You can try it, I tested several combinations restoring nandroid backups and they worked fine.
But I suggest you to made a full nandroid just un case.
Sent from my GT-I9190
Click to expand...
Click to collapse
ok, I will try right now! and Ill let you know if it works in that way, thanks for your great job!
update: yeah it worked in that way! I have f2fs in every partition! thanks
Does FSFS support symlinks?
If so, how to access FSFS formatted sdcards on /storage/sdcardX directly w/o fuse layer on top?
aguaz said:
Does FSFS support symlinks?
If so, how to access FSFS formatted sdcards on /storage/sdcardX directly w/o fuse layer on top?
Click to expand...
Click to collapse
To use F2FS on external sd cards, ROM needs to have F2FS support on minivold for vold managed volumes, my CarbonROM builds support it.
External storages are vold managed volumes, this is my external sd card formatted as F2FS:
Code:
/dev/block/vold/179:33 on /mnt/media_rw/sdcard1 type f2fs (rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,background_gc=off,user_xattr,inline_xattr,acl,active_logs=2
F4k said:
External storages are vold managed volumes, this is my external sd card formatted as F2FS:
Code:
/dev/block/vold/179:33 on /mnt/media_rw/sdcard1 type f2fs (rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,background_gc=off,user_xattr,inline_xattr,acl,active_logs=2
Click to expand...
Click to collapse
My understanding is that the mount point on /mnt/media_rw/sdcard1 is for internal use only. Apps however use the additional mount point on /storage/scdard1 . This mount point has a fuse layer on top, which prevents the use of symlinks on eg ext4 formatted cards. (see here: http://forum.xda-developers.com/showthread.php?t=1442729)
So I'm wondering if F2FS can be accessed by apps natively w/o fuse layer in order to use symlinks. That is of course assuming F2FS supports symlinks itself.
Recovery doesn't seem to support encrypted partitions properly (acts like they don't exist), also some weird input glitches... Doing more testing...
After using TWRP for a while I decided to go back to Philz, this time without reformatting or restoring any old settings. Everything is working perfectly now, something crazy must have happened with my old settings, I suspect with 'Sd Card Target'.
Thank you very much for this F4k. Besides the addition of F2fs support, previously the latest version available to us was 6.41.6, very nice to have such an up to date version now I seriously would donate if I had the means to, and as soon as I actually have some money in my bank account for a change I definitely will be doing so
dulemars said:
Recovery doesn't seem to support encrypted partitions properly (acts like they don't exist), also some weird input glitches... Doing more testing...
Click to expand...
Click to collapse
I don't added crypto support yet to TWRP
i've a problem with system partition.
i use twrp recovery. i've do a clean install format data, i've cheked in Advanced Wipe System and Cache partitions to convert to F2FS, wiped system and cache, i've install last cyanogen nightly and... in diskinfo data is f2fs, cache is f2fs but system is ext4.... why? what's wrong?
thanks

F2FS in MIUI

Hi, wouldn't it be sufficient to switch to a custom kernel with f2fs driver to be able to run MIUI with a f2fs file system? It is even possible? With LineageOS you still cannot use f2fs on the /system partition (maybe in the initial ramdisk there is no f2fs driver ?) but at least /data and /cache partition, also on MIUI. Is there a way to do that?
I'm trying without success, installed a custom kernel which claims to have f2fs support, formatted the cache partition in f2fs to do some testing, typed the 'df' command in the linux shell but no cache partition is displayed.
Using f2fs on the /system isn't a good idea to begin with, the /system is a read only partition so you wouldn't benefit from anything that f2fs gives.

Mounting and exploring an .img of an encrypted OP3T /data partition?

Hello xda community and OP3(T) users!
In April I created an image of my f2fs /data partition according to this hint:
https://stackoverflow.com/questions/26967862/how-to-make-an-image-of-android-partition-to-your-pc
This was successful and a *.img file sized 53+ GB now resides safely and quietly on an external hard drive.
Now I want to mount as well explore it with my Linux laptop. ))
How do I do this? Which tools and commands are needed?
P.S.: in the past this partition was also encrypted and decrypted via a simple 3x3 pattern by TWRP as well as before a ROM boots....

How to decrypt internal storage when downgrading

I am on Fi PPWS29.69-39-6-11 rom (August 1, 2020 security patch). I want to downgrade to PPWS29.69-39-6-6. But after flashing PPWS29.69-39-6-6 rom is internal storage encrypted. Before flashing 6-6 i disabled encryption (lock screen -> none), but internal storage still encrypted after downgrading. Any solution to decrypt internal storage without wiping user data?
TWRP can decrypt the storage, so you can try making a backup in there and restoring it after you downgrade. But you may have better luck using Titanium Backup (you will need root).

TWRP Helper for /data/media backup

Magisk 20.4, Magisk Manager 8.0.4, TWRP 3.4, LineageOS 17.1 Kuntao/Lenovo P2
[re-wording edit]
My question is why does TWRP Backup show *inc* /data/media when TWRP Helper doesn't appear to be installed? I thought the helper module was what made this happen.
It's working but I'd like to understand why in order to feel confident with it.
[/edit]
Phone shows rooted in Root Checker Basic. Tried to install TWRP Helper module but it failed and doesn't appear in the installed modules list. Reason for installing is to be able to do a full backup with TWRP (before doing LineageOS updates which have a nasty habit of trashing the phone).
However, in TWRP backup the Data partition already says "inc. /data/media" anyway instead of the usual exc. I thought that was what TWRP Helper was for. But if it's not installed what have I misunderstood?
Thanks.
Hello, I have the following problem: my device is Samsung SM-G9006V with root rights, the operation system is LineageOS 16. I want upgrade it to LineageOS 18. But first I made Nandroid Backup with the "TWRP Helper" (repo from Magisk). The upgrade ended in a loop from LineageOS, I means: LineageOS boot up to its logo, then crashes and starts again. I flashed LineageOS 17 but the same thing happens.
I restored Nandroid Backup, but had problems with my data on the external SD card (it is adaptive to the internal storage, not mobile), namely: the data are on the SD card, I can see it in TWRP Recovery Explorer in
/external_sd /media/0, but LineageOS does not bind (does not mount) it. My data on the SD card lay like a stone.
One more thing: when restoring data, TWRP says in the beginning in protocol:
unable to find partition for path “/”.
There is only one error in file /tmp/recovery.log:
I: Failed to load image from indeterminate013, error -1
Can someone tell me:
1. Why does Nandroid not work for my data on an external SD card. Or how can I manually mount or link the data from the external SD card into the system (for example: mount -o rw / dev / device_externe_SD_Card / sdcard or
ln -s / external_sd / media / 0 / data / media / 0 or ???)
2. And why does upgrade end in the system loop
thanks

Categories

Resources