Starting with Android L/Lollipop/5.0, full device encryption will be enabled by default, and for good reason. However, we slightly more security-conscious/paranoid SGS3 users have had problems for a while with using custom ROMs and keeping our encryption, as the main custom recovery with support for encryption --- TWRP --- has some incorrect build flags and other problems that aren't considered a priority. However, thanks to the very same bug report and discussion on the issue on TWRP's pages, someone found a solution which I can confirm works for me as well: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/247#issuecomment-52651670
One option would be to check whether CWM Recovery supports your device. Then you'll have access to MiniVold in recovery mode and you can mount encrypted partitions through adb. I prefer the TWR method of just typing in my password, but as long as that does not work on my Galaxy S3, this does:
adb shell
setprop ro.crypto.state encrypted
vdc cryptfs checkpw 'your passphrase here'
mount /dev/block/dm-0 /data
and when you're done backing up/installing a zip
umount /data
Click to expand...
Click to collapse
For Windows users, here's a batch file you can use to automate this process:
Code:
adb shell setprop ro.crypto.state encrypted
adb shell vdc cryptfs checkpw "%~1"
adb shell mount /dev/block/dm-0 /data
Save it under whateveryouwant.bat and then give it the password as a parameter (if the password contains spaces, enclose it in quotes).
Caveat: I've found some operations will unmount /data, which for some reason cannot then be re-mounted by any combination of these commands. Workaround is to just reboot Philz Touch Recovery / CWM Advanced Recovery, re-mount, and continue.
Hi there,
after I had some big problems to restore a twrp backup I want to now what this app makes and why this app
is also there after a full wipe of my device.
the twrp restore error
Code:
==> extracting: //data/app/com.android.vending-1/ (mode 40777, directory)
tar_extract_file(): failed to extract //data/app/com.android.vending-1/ !!!
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/CB5A2225SH/2017-12-02--18-34-09_cm_amami-userdebug_511_LMY49M_b59f978a25_te/data.ext4.win000'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/CB5A2225SH/2017-12-02--18-34-09_cm_amami-userdebug_511_LMY49M_b59f978a25_te/data.ext4.win000' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
I:Set page: 'action_complete'
overlay_display_frame failed, overlay play Failed
If I make a full wipe in twrp this files are on my data partition:
Code:
1|[email protected]:/data/app # ls
com.android.vending-1
com.android.vending-1.apk
com.android.vending-2
com.android.vending-2.apk
1|[email protected]:/data/app # ls -la com.android.vending-*
-rw-rw-rw- root root 0 2017-07-20 12:59 base.apk
-rw-rw-rw- root root 0 2017-07-20 12:59 com.android.vending-1.apk
-rw-rw-rw- root root 0 2017-07-20 12:59 base.apk
-rw-rw-rw- root root 0 2017-07-20 12:59 com.android.vending-2.apk
127|[email protected]:/data/app # rm -rf com.android.vending-*
rm: com.android.vending-1/base.apk: Permission denied
rm: com.android.vending-1: Operation not permitted
rm: com.android.vending-1.apk: Operation not permitted
rm: com.android.vending-2/base.apk: Permission denied
rm: com.android.vending-2: Operation not permitted
rm: com.android.vending-2.apk: Operation not permitted
As you see even as root I can't delete this. Can anyone explain me what this is for?
TIA Micha
Micha_Btz said:
Hi there, after I had some big problems to restore a twrp backup I want to now that this app makes and why this app is also there afer a full wipe of my device...
Click to expand...
Click to collapse
I don't have this device but, I had noticed that your device is an amami (Xperia Z1 Compact).
So your best bet is to post this question within one of the following threads that may hopefully be helpful to you.
https://forum.xda-developers.com/showthread.php?t=2631291
https://forum.xda-developers.com/showthread.php?t=3614936
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
I didn't know what's going wrong but the only way was to format the data partition. Keep in mind that /deata/media should be backed up.
TWRP compiled from the latest omnirom 9.0 branch with support for Android Pie (9) and its encryption/decryption (backward compatible with older Android versions).
Tested:
Decrypting Pie data partition (with pattern) - Works
Flashing a zip file - Works
MTP - Works
Nandroid backup/restore - Works
Everything else works fine, but use on your own risk!
The build IS UNIFIED (for OP5 and 5T, based on the blu_spark device tree).
This TWRP is treble compatible!
Download:
https://www.androidfilehost.com/?w=files&flid=281621
Source code:
https://github.com/engstk/android_device_oneplus_cheeseburger
https://github.com/omnirom/android_bootable_recovery
Credits: @eng.stk @Dees_Troy
And the whole TWRP/Omnirom team
It works great, thank you!
Mirrors here! (including themed, un-unthemed, treble and non-treble versions)
Thanks. It works.
Hey, quick question, i'm on DU (8.1) and my device says "Device is decrypted" , does this mean i don't have to wipe data in order to flash a 9.0 ROM? Thanks in advance!
Fechinator said:
Hey, quick question, i'm on DU (8.1) and my device says "Device is decrypted" , does this mean i don't have to wipe data in order to flash a 9.0 ROM? Thanks in advance!
Click to expand...
Click to collapse
A data wipe is always recommended while switching between major Android versions to avoid running into issues, minor or major.
I can't use twrp since it can't recognize my password
can this build fix this problem ??
Works perfectly just like your Roms
Thank you very much
the link to download doesn't work!
Sent from my [device_name] using XDA-Developers Legacy app
sharaq said:
the link to download doesn't work![/url]
Click to expand...
Click to collapse
Issue is definitely at your end. I just tested downloading and it went fine. It's an AndroidFileHost folder link.
Works good. Tested on crDroid Pie.
Thank you for this.
Seems Afh is having some issue here too.
Sent from my ONEPLUS A5000 using Tapatalk
Tried again, working now. ( ಠ◡ಠ )
I have an encrypted device, i want to stay encrypted after installing pie ROMs, is this recovery keep my device encrypted or it will remove the encryption? Need some guidance
Alipk52 said:
I have an encrypted device, i want to stay encrypted after installing pie ROMs, is this recovery keep my device encrypted or it will remove the encryption? Need some guidance
Click to expand...
Click to collapse
You will remain encrypted if the ROM supports encryption but this recovery is experimental according to the title
Aroma OpenGApps 9.0 arm64 breaks when starting to install. On Oneplus 5, Lineage OS 16.0 experimental by codeworkx.
Works for me using pixen2 rom !
siankatabg said:
TWRP compiled from the latest omnirom 9.0 branch with support for decrypting the Android Pie (9) encryption (backward compatible with older Android versions).
Tested:
Decrypting Pie data partition (with pattern) - Works
Flashing a zip file - Works
MTP - Works
Nandroid backup/restore - Works
All else should work fine, but the whole recovery is experimental, so use on your own risk!
The build should be unified (for OP5 and 5T, based on the blu_spark device tree), but it was tested only on Oneplus 5! This TWRP is treble compatible.
Download:
https://www.androidfilehost.com/?w=files&flid=281621
Source code:
https://github.com/engstk/android_device_oneplus_cheeseburger
https://github.com/omnirom/android_bootable_recovery
Credits: @[email protected]_Troy
And the whole TWRP/Omnirom team
Click to expand...
Click to collapse
Working perfect on PixEn2 9.0
Tried this recovery out with Oxygen OS 8.1 Beta 19, magisk 17.2 beta. When I go to recovery -> Backup -> Select everything and try to make a backup, everything goes fine until the very last minute, when the "createTarFork() process ended with ERROR: 255" error pops up followed by "Backup Failed. Cleaning Backup Folder.". Here is the last few lines from the recovery.log for reference.
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.apps.messaging/1538020684432.png' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.apps.messaging/1538020684442.png' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.apps.messaging/1538020684447.png' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.dialer' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
found policy '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.dialer' - '1CE0' - '0cbd0fc0ceed9bb2'
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.dialer/1537817225643.png' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.dialer/1537817225646.png' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.dialer/1537817225650.png' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.contacts' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
found policy '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.contacts' - '1CE0' - '0cbd0fc0ceed9bb2'
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.contacts/1537954281562.png' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.contacts/1537954281602.png' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
I:addFile '/data/system_ce/0/shortcut_service/bitmaps/com.google.android.contacts/1537954281623.png' including root: 1
==> set selinux context: ubject_r:shortcut_manager_icons:s0
I:addFile '/data/system_ce/0/recent_images' including root: 1
==> set selinux context: ubject_r:system_data_file:s0
found policy '/data/system_ce/0/recent_images' - '1CE0' - '0cbd0fc0ceed9bb2'
I:addFile '/data/system_ce/999' including root: 1
==> set selinux context: ubject_r:system_data_file:s0
failed to lookup tar policy for '/data/system_ce/999' - '2507fb304b76812a'
I:Error adding file '/data/system_ce/999' to '/data/media/0/TWRP/BACKUPS/33e1533a/2018-09-27--09-49-58/data.ext4.win010'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/33e1533a/2018-09-27--09-49-58/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/33e1533a/2018-09-27--09-49-58/recovery.log
Click to expand...
Click to collapse
Any help in identifying and sorting this out is greatly appreciated. I would like to install the Pixen Pie and would like to take a full backup before proceeding.
Hi Im new here,
the swap button order missing
edited: and also sim card on off
srikaran said:
Tried this recovery out with Oxygen OS 8.1 Beta 19, magisk 17.2 beta. When I go to recovery -> Backup -> Select everything and try to make a backup, everything goes fine until the very last minute, when the "createTarFork() process ended with ERROR: 255" error pops up followed by "Backup Failed. Cleaning Backup Folder.". Here is the last few lines from the recovery.log for reference.
Any help in identifying and sorting this out is greatly appreciated. I would like to install the Pixen Pie and would like to take a full backup before proceeding.
Click to expand...
Click to collapse
After waiting and further searching and all, I came to know that deleting the so called 999 folders does the trick where it lets you backup in twrp. So, I created a del999.sh script with the following commands in it
Code:
rm -rf /data/system/999
rm -rf /data/system_ce/999
rm -rf /data/system_de/999
rm -rf /data/misc/999
rm -rf /data/misc_ce/999
rm -rf /data/misc_de/999
rm -rf /data/user/999
rm -rf /data/user_ce/999
rm -rf /data/user_de/999
In twrp, I navigated to Advanced - Terminal. In there, typed the following commands
Code:
cd sdcard
chmod +x del999.sh
./del999.sh
After this navigating to twrp and back up works just fine.
To restore however, the same steps worked for the most part. However, I had to do a factory reset first, followed by a reboot to recovery followed by del999 and then restore worked. Trying to boot into the system now, fingers crossed, hopefully everything will work as expected.
Device: OnePlus 5T (dumpling)
OS: crDroid v6.5
Firmware: firmware_H056_oneplus5T
TWRP Version: 3.3.1-20190908-0-codeworkx-signed-forcedecrypt
Add-ons: Magisk-v20.4 and MinMicroG-NoGoolag-2.7-beta2.
Hello XDA Fourm,
Every time I go to do a backup; I get an error upon backing up the "Data" partition. Here is a snippet of the "recovery.log" TWRP produced:
Code:
I:addFile '/data/per_boot' including root: 0
==> set selinux context: u:object_r:system_data_file:s0
failed to lookup tar policy for '/data/per_boot' - '3ceb982b622fe097'
I:Error adding file '/data/per_boot' to '/data/media/0/TWRP/BACKUPS/[REDACTED]/2020-04-22--23-01-37_QQ2A200405005_release-keys/data.ext4.win'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/[REDACTED]/2020-04-22--23-01-37_QQ2A200405005_release-keys/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/[REDACTED]/2020-04-22--23-01-37_QQ2A200405005_release-keys/recovery.log
Things I have tried:
Backing up everything except the "Data" partition. Back up completes successfully.
Reflashing TWRP.
Any help is appreciated.
Hi,
I'm facing the same issue.
Did you find any solution for this issue?
THX
Use TWRP file manager and go to "/data/per_boot" and delete the folder "per_boot" and try backup again it will work
Thank me later
I have a Poco F3 Global, and I currently am running TWRP 3.5.2_11-Nebrassy.
If I tap Reboot and it shows my Current Slot as A, then under Mount I see the following:
System, system_ext, Product, Vendor, ODM, Metadata, Data, Cust, and Firmware
And I can check each of them. I can also perform Wipe -> Format Data -> yes.
But if I boot into Slot B, and tap Mount it doesn't let me click the checkmarks for System, system_ext, Product, or Vendor.
And if I try to execute Wipe -> Format Data -> yes it shows "Failed to mount" in red for all of the following:
'/system_root', '/system_ext', '/product', '/vendor' (Invalid argument)
(Some of them are in there multiple times)
Running cat /etc/fstab in B outputs:
Code:
/dev/block/sda18 /metadata ext4 rw 0 0
/dev/block/sda35 /data f2fs rw 0 0
/dev/block/sda29 /cust ext4 rw 0 0
/dev/block/bootdevice/by-name/modem_b /firmware vfat rw 0 0
/dev/block/sda22 /persist ext4 rw 0 0
/usb_otg vfat rw 0 0
Running cat /etc/fstab in A outputs:
Code:
/dev/block/dm-2 /system_root ext4 ro 0 0
/dev/block/dm-3 /system_ext ext4 ro 0 0
/dev/block/dm-1 /product ext4 ro 0 0
/dev/block/dm-4 /vendor ext4 ro 0 0
/dev/block/dm-0 /odm ext4 ro 0 0
/dev/block/sda18 /metadata ext4 rw 0 0
/dev/block/sda35 /data f2fs rw 0 0
/dev/block/sda29 /cust ext4 rw 0 0
/firmware vfat rw 0 0
/dev/block/sda22 /persist ext4 rw 0 0
/usb_otg vfat rw 0 0
For both A and B going to Wipe -> Advanced Wipe it only shows Dalvik / ART Cache, Metadata, Data, Internal Storage, and USB-OTG
I can still install an OS, but that is finicky at times.
How can I fix my B Partition?
Solved it:
Download the MiFlash Tool, and the Fastboot version of the Stock ROM. Extract the contents of the zip (and within the zip the tar file) to a directory without spaces in it (I just extracted it directly to C: drive). Open MiFlash, click Select and choose the directory you just extracted. At the bottom of the MiFlash app select "Clean All", NOT "Clean all and Lock" (unless that's what you want). Click Refresh (if phone doesn't appear, make sure your phone is in fastboot mode and connected to PC). Then click Flash. Mine failed the first time with some error about "Antirollback check error". If you get this you have to manually edit the "flash_all.bat" file within the extracted directory and remove the lines that don't start with "fastboot", then save the bat file, and restart the flash. It took MiFlash 604 seconds to complete, and ended with a status of "error: Not catch checkpoint, ..., flash is not done" you can ignore that, or remove that checkpoint in the MiFlash configuration settings. My phone restarted and booted into the stock ROM.
following had the same errors when i mistakenly ignorantly wiped system etc while trying to flash a rom