APP ❯ TWRP ❯❯ Tipatch • Backup internal storage • v1.6

pol-der

Senior Member
Nov 30, 2018
200
31
38
@kdrag0n I looked to the /tmp/recovery.log file and saw this error.

Error opening: '/system/addon.d' (Not a directory)

I searched some on the internet and they are saying delete that file and try. Should i delete that? Is it important file for system or not?
 

kdrag0n

Senior Member
Feb 19, 2016
563
1,475
133
kdrag0n.dev
Does it also work when the recovery is on boot.img partition?
Yes if it's an A/B device.

I have a xiaomi pocophone f1 which is using official TWRP version twrp-3.2.3-2-beryllium ..... https://dl.twrp.me/beryllium/ i have installed the latest version, 3.2.3-2....

will i have any issues?

need confirmation, please.
No, it should work fine.

@kdrag0n I am getting this error while trying to take backup "createTarFork() process ended with ERROR=255" after patching your file. How can i fix this?

---------- Post added at 09:17 PM ---------- Previous post was at 09:13 PM ----------

[/COLOR @kdrag0n And one more thing how can i uninstall this patch? I mean how can i revert this process?

I don't know, I've never had an issue like that.

The app backs up the previous recovery image before patching. It also features an "undo patch" button. You can choose to either restore the backup or undo the patch from the action menu just like when you patch it.
 

bggold

Senior Member
Sep 13, 2013
1,049
359
103
Edit: I was able to flash and boot 3.2.3-4 once from recovery and tried tipatch and it stuck at the white Google screen. Thought it was tipatch but after seeing a report of the same issue with no tipatch I reflashed 3.2.3-4 without tipatch and it won't boot to recovery.

Apparently it is not an issue with tipatch.

Tipatch does not work yet on twrp 3.2.3-4 for pixel 3 xl and most likely the pixel 3.

It patches successfully but hangs on boot to recovery at the initial Google screen.

I have notified the dev already of the issue.
 
Last edited:

bggold

Senior Member
Sep 13, 2013
1,049
359
103
Edit: I was able to flash and boot 3.2.3-4 once from recovery and tried tipatch and it stuck at the white Google screen. Thought it was tipatch but after seeing a report of the same issue with no tipatch I reflashed 3.2.3-4 without tipatch and it won't boot to recovery.

Apparently it is not an issue with tipatch.

Tipatch does not work yet on twrp 3.2.3-4 for pixel 3 xl and most likely the pixel 3.

It patches successfully but hangs on boot to recovery at the initial Google screen.

I have notified the dev already of the issue.
Works fine on the fixed 3.2.3-4 for crosshatch.
 
  • Like
Reactions: kdrag0n

hyborian

Senior Member
Oct 25, 2017
1,155
344
83
@kdrag0n, I am also having the same problem as Stofl - "Recovery partition not found. Try to use a recovery image file instead."

This is on my Xiaomi Note 4X MTK, Android 6, ZCX TWRP v3.0.2 for Redmi Note 4 MTK (Nikel).
Tipatch v1.7 downloaded just today from xda

Code:
su -c ls -l /dev/block
brw------- root     root     253,   0 2019-04-26 13:55 dm-0
brw------- root     root       7,   0 2019-04-26 13:55 loop0
brw------- root     root       7,   1 2019-04-26 13:55 loop1
brw------- root     root       7,   2 2019-04-26 13:55 loop2
brw------- root     root       7,   3 2019-04-26 13:55 loop3
brw------- root     root       7,   4 2019-04-26 13:55 loop4
brw------- root     root       7,   5 2019-04-26 13:55 loop5
brw------- root     root       7,   6 2019-04-26 13:55 loop6
brw------- root     root       7,   7 2019-04-26 13:55 loop7
brw-rw---- root     system   179,   0 2019-04-26 13:55 mmcblk0
brw-rw---- root     system   179,  32 2019-04-26 13:55 mmcblk0boot0
brw-rw---- root     system   179,  64 2019-04-26 13:55 mmcblk0boot1
brw-r----- root     system   179,   1 2019-04-26 13:55 mmcblk0p1
brw------- root     root     179,  10 2019-04-26 13:55 mmcblk0p10
brw-rw---- root     system   179,  11 2019-04-26 13:55 mmcblk0p11
brw-rw---- root     system   179,  12 2019-04-26 13:55 mmcblk0p12
brw-rw---- root     system   179,  13 2019-04-26 13:55 mmcblk0p13
brw-rw---- root     system   179,  14 2019-04-26 13:55 mmcblk0p14
brw-rw---- root     system   179,  15 2019-04-26 13:55 mmcblk0p15
brw------- root     root     179,  16 2019-04-26 13:55 mmcblk0p16
brw------- root     root     179,  17 2019-04-26 13:55 mmcblk0p17
brw-rw---- root     system   179,  18 2019-04-26 13:55 mmcblk0p18
brw------- root     root     179,  19 2019-04-26 13:55 mmcblk0p19
brw-rw---- root     system   179,   2 2019-04-26 13:55 mmcblk0p2
brw------- root     root     179,  20 2019-04-26 13:55 mmcblk0p20
brw-r----- root     system   179,  21 2019-04-26 13:55 mmcblk0p21
brw-rw---- root     system   179,  22 2019-04-26 13:55 mmcblk0p22
brw------- root     root     179,  23 2019-04-26 13:55 mmcblk0p23
brw------- root     root     179,  24 2019-04-26 13:55 mmcblk0p24
brw------- root     root     179,  25 2019-04-26 13:55 mmcblk0p25
brw------- root     root     179,  26 2019-04-26 13:55 mmcblk0p26
brw------- root     root     179,  27 2019-04-26 13:55 mmcblk0p27
brw------- root     root     179,  28 2019-04-26 13:55 mmcblk0p28
brw------- root     root     179,  29 2019-04-26 13:55 mmcblk0p29
brw------- root     root     179,   3 2019-04-26 13:55 mmcblk0p3
brw------- root     root     179,  30 2019-04-26 13:55 mmcblk0p30
brw------- root     root     179,  31 2019-04-26 13:55 mmcblk0p31
brw------- root     root     179,   4 2019-04-26 13:55 mmcblk0p4
brw------- root     root     179,   5 2019-04-26 13:55 mmcblk0p5
brw------- root     root     179,   6 2019-04-26 13:55 mmcblk0p6
brw------- root     root     179,   7 2019-04-26 13:55 mmcblk0p7
brw------- root     root     179,   8 2019-04-26 13:55 mmcblk0p8
brw-rw---- root     system   179,   9 2019-04-26 13:55 mmcblk0p9
brw------- root     root     179,  96 2019-04-26 13:55 mmcblk0rpmb
brw------- root     root     179, 128 2019-04-26 13:55 mmcblk1
brw------- root     root     179, 129 2019-04-26 13:55 mmcblk1p1
brw------- root     root     179, 130 2019-04-26 13:55 mmcblk1p2
brw------- root     root     179, 131 2019-04-26 13:55 mmcblk1p3
drwxr-xr-x root     root              2019-04-26 13:55 platform
drwx------ root     root              2019-04-26 13:55 vold
brw------- root     root     254,   0 2019-04-26 13:55 zram0

/dev/block/bootdevice/by-name: No such file or directory

/dev/block/platform/*/by-name: No such file or directory
 
Last edited:
  • Like
Reactions: Ir09036542800

kdrag0n

Senior Member
Feb 19, 2016
563
1,475
133
kdrag0n.dev
@gongoscho, which TWRP are you using for Poco F1, official one ? Are you able to backup System and Vendor and Restore without problems ? Normally, we have to back up System Image and Vendor Image to be able to restore without errors. Thanks.

---------- Post added at 06:58 AM ---------- Previous post was at 06:44 AM ----------



---------- Post added at 07:56 AM ---------- Previous post was at 06:58 AM ----------

@kdrag0n, I am also having the same problem as Stofl - "Recovery partition not found. Try to use a recovery image file instead."

This is on my Xiaomi Note 4X MTK, Android 6, ZCX TWRP v3.0.2 for Redmi Note 4 MTK (Nikel).
Tipatch v1.7 downloaded just today from xda
Here's a command that will give more detailed and useful output:
Code:
su -c find -L /dev/block -type b
 

hyborian

Senior Member
Oct 25, 2017
1,155
344
83
Here's a command that will give more detailed and useful output:
Code:
su -c find -L /dev/block -type b
Here is the result :

Code:
/dev/block/dm-0
/dev/block/vold/public:179,129
/dev/block/vold/disk:179,128
/dev/block/mmcblk0p31
/dev/block/mmcblk0p30
/dev/block/mmcblk0p29
/dev/block/mmcblk0p28
/dev/block/mmcblk0p27
/dev/block/mmcblk0p26
/dev/block/mmcblk0p25
/dev/block/mmcblk0p24
/dev/block/mmcblk0p23
/dev/block/mmcblk0p22
/dev/block/mmcblk0p21
/dev/block/mmcblk0p20
/dev/block/mmcblk0p19
/dev/block/mmcblk0p18
/dev/block/mmcblk0p17
/dev/block/mmcblk0p16
/dev/block/mmcblk0p15
/dev/block/mmcblk0p14
/dev/block/mmcblk0p13
/dev/block/mmcblk0p12
/dev/block/mmcblk0p11
/dev/block/mmcblk0p10
/dev/block/mmcblk0boot1
/dev/block/mmcblk0boot0
/dev/block/mmcblk0rpmb
/dev/block/mmcblk0p9
/dev/block/mmcblk0p8
/dev/block/mmcblk0p7
/dev/block/mmcblk0p6
/dev/block/mmcblk0p5
/dev/block/mmcblk0p4
/dev/block/mmcblk0p3
/dev/block/mmcblk0p2
/dev/block/mmcblk0p1
/dev/block/mmcblk0
/dev/block/mmcblk1p3
/dev/block/mmcblk1p2
/dev/block/mmcblk1p1
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p31
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p30
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p29
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p28
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p27
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p26
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p25
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p24
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p23
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p22
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p21
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p20
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p19
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p18
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p17
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p16
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p15
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p14
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p13
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p12
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p11
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p10
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0boot1
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0boot0
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0rpmb
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p9
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p8
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p7
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p6
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p5
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p4
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p3
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p2
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0p1
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p31
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p30
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p29
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p28
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p27
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p26
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p25
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p24
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p23
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p22
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p21
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p20
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p19
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p18
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p17
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p16
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p15
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p14
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p13
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p12
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p11
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p10
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p9
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p8
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p7
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p6
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p5
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p4
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p3
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p2
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-num/p1
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/flashinfo
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/otp
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/cache
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/cust
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/keystore
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/tee2
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/tee1
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/lk2
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/lk
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvram
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/scp2
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/scp1
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/md3img
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/md1arm7
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/md1dsp
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/md1img
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/proinfo
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/oemkeystore
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/seccfg
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect2
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect1
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/metadata
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvdata
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvcfg
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/expdb
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/para
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery
/dev/block/platform/mtk-msdc.0/11230000.msdc0/mmcblk0
/dev/block/platform/mtk-msdc.0/11240000.msdc1/mmcblk1p3
/dev/block/platform/mtk-msdc.0/11240000.msdc1/mmcblk1p2
/dev/block/platform/mtk-msdc.0/11240000.msdc1/mmcblk1p1
/dev/block/platform/mtk-msdc.0/11240000.msdc1/by-num/p3
/dev/block/platform/mtk-msdc.0/11240000.msdc1/by-num/p2
/dev/block/platform/mtk-msdc.0/11240000.msdc1/by-num/p1
/dev/block/platform/mtk-msdc.0/11240000.msdc1/by-name/second_part
/dev/block/platform/mtk-msdc.0/11240000.msdc1/by-name/android_meta
/dev/block/platform/mtk-msdc.0/11240000.msdc1/by-name/shared
/dev/block/platform/mtk-msdc.0/11240000.msdc1/mmcblk1
/dev/block/mmcblk1
/dev/block/zram0
/dev/block/loop7
/dev/block/loop6
/dev/block/loop5
/dev/block/loop4
/dev/block/loop3
/dev/block/loop2
/dev/block/loop1
/dev/block/loop0
 
  • Like
Reactions: kdrag0n

AeonFlux1603

Senior Member
Feb 1, 2019
188
164
0
@kdrag0n I truly commend and thank you for your continued support and updates to this great tool, including your prompt addition of LZMA compression support for those custom TWRP builds that require LZMA. I have used Tipatch on a myriad of Android devices and TWRP versions, both on custom and official upstream builds. Tipatch has never failed me yet. You have created a long-needed resolution to TWRP's de facto lack of full Data backup support. It won't be a goldmine by any means, but I will be donating at least a couple of beers to your cause later today, in appreciation and support of your amazing work on Tipatch. Best wishes to you @kdrag0n.
 
Last edited:

pribinakk

Member
Jun 11, 2009
17
1
0
Hello, does anyone able to patch this recovery?
https://androidfilehost.com/?fid=673368273298944051
It gives me constantly errors, something with /media folder.

Please let me know if it's possible, because it will save my time - i have three devices Galaxy Tab S2 (T719), i can use another recoveries, but this one fits to my specific needs, i was excited with tipach to do full backups (tested)... but BANG! this recovery was not patched....why? any help?
 

kdrag0n

Senior Member
Feb 19, 2016
563
1,475
133
kdrag0n.dev
Hello, does anyone able to patch this recovery?
https://androidfilehost.com/?fid=673368273298944051
It gives me constantly errors, something with /media folder.

Please let me know if it's possible, because it will save my time - i have three devices Galaxy Tab S2 (T719), i can use another recoveries, but this one fits to my specific needs, i was excited with tipach to do full backups (tested)... but BANG! this recovery was not patched....why? any help?
That's a widespread issue affecting many devices, most of which are made by Samsung. I'll look into it for the next version of Tipatch but can't guarantee a fix, especially because none of my devices are affected.
 

pribinakk

Member
Jun 11, 2009
17
1
0
That's a widespread issue affecting many devices, most of which are made by Samsung. I'll look into it for the next version of Tipatch but can't guarantee a fix, especially because none of my devices are affected.
thank you, i have to say i had no issues with tipatch- patching twrps for this samsung device.... this recovery is important for me, because it's modified to turn off samsung data encryption, but on the other hand i'm getting errors when trying to patch this recovery with tipatch :/ so the question is can you help me with fix? and when we can when expect newer version to try it out? thank you
 

bggold

Senior Member
Sep 13, 2013
1,049
359
103
thank you, i have to say i had no issues with tipatch- patching twrps for this samsung device.... this recovery is important for me, because it's modified to turn off samsung data encryption, but on the other hand i'm getting errors when trying to patch this recovery with tipatch :/ so the question is can you help me with fix? and when we can when expect newer version to try it out? thank you
Out of respect for the devs we don't ask for eta's. When they get to it they get to it.
 
  • Like
Reactions: kdrag0n