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

kdrag0n

Senior Member
Feb 19, 2016
563
1,475
133
kdrag0n.dev
If the Sentry code is never called you could just remove those permission entries from the manifest and nothing will happen.
It's a better impression when a "trackerless" app which's core functionality doesn't require internet access, does not require android.permission.INTERNET.
Otherwise that's some nasty aftertaste.
Alright, I'll try that and see how it goes.

@kdrag0n thank you for this—very cool. TWRP the way God intended ?

What is the difference between the xda version (2.37MiB) and the Play Store version (1.7MiB)—fetched via Yalp? Both are latest 1071 build.

Thanks
I upload an Android App Bundle to Play Store which is then repacked by Google into APKs which only include the appropriate resources for each set of devices, whereas the generic XDA and GitHub APK contain the resources necessary to run on all devices. Additionally, the Play Store version has the PayPal donation link hidden due to the store policies. That doesn't change the size though.

Tried to tap-patch on Huawei MediaPad X2 and it didn't work. When I click "Patch" I see "Die Recovery-Partition wurde nicht gefunden. Versuchen Sie, eine Recovery-Image-Datei zu verwenden" (Recovery partition not found. Try to use a recovery image file instead.)

Actually I don't want to patch TWRP image as I want to avoid flashing TWRP again (too much hassle).

Tipatch version: 1.7
TWRP: 3.2.1-0
SuperSU: V2.82-SR5-20171001224502
Phone model: GEM-702L
Build: GEM-702LC158B202
EMUI: 4.0
Android: 6.0
Open a terminal and send me the output of the following commands:
Code:
su -c ls -l /dev/block
su -c ls -l /dev/block/bootdevice/by-name
su -c ls -l /dev/block/platform/*/by-name
 
  • Like
Reactions: TiTiB

stofl

Member
Sep 1, 2016
14
1
0
Code:
[email protected]:/ $ su -c ls -l /dev/block
brw------- root     root       7,   0 2018-12-12 13:58 loop0
brw------- root     root       7,   1 2018-12-12 13:58 loop1
brw------- root     root       7,   2 2018-12-12 13:58 loop2
brw------- root     root       7,   3 2018-12-12 13:58 loop3
brw------- root     root       7,   4 2018-12-12 13:58 loop4
brw------- root     root       7,   5 2018-12-12 13:58 loop5
brw------- root     root       7,   6 2018-12-12 13:58 loop6
brw------- root     root       7,   7 2018-12-12 13:58 loop7
brw------- root     root     179,   0 2018-12-12 13:58 mmcblk0
brw------- root     root     179,  40 2018-12-12 13:58 mmcblk0boot0
brw------- root     root     179,  80 2018-12-12 13:58 mmcblk0boot1
brw------- root     root     179,   1 2018-12-12 13:58 mmcblk0p1
brw------- root     root     179,  10 2018-12-12 13:58 mmcblk0p10
brw------- root     root     179,  11 2018-12-12 13:58 mmcblk0p11
brw------- root     root     179,  12 2018-12-12 13:58 mmcblk0p12
brw------- root     root     179,  13 2018-12-12 13:58 mmcblk0p13
brw------- root     root     179,  14 2018-12-12 13:58 mmcblk0p14
brw------- root     root     179,  15 2018-12-12 13:58 mmcblk0p15
brw------- root     root     179,  16 2018-12-12 13:58 mmcblk0p16
brw------- root     root     179,  17 2018-12-12 13:58 mmcblk0p17
brw------- root     root     179,  18 2018-12-12 13:58 mmcblk0p18
brw-rw---- system   system   179,  19 2018-12-12 13:58 mmcblk0p19
brw------- root     root     179,   2 2018-12-12 13:58 mmcblk0p2
brw------- root     root     179,  20 2018-12-12 13:58 mmcblk0p20
brw------- root     root     179,  21 2018-12-12 13:58 mmcblk0p21
brw------- root     root     179,  22 2018-12-12 13:58 mmcblk0p22
brw------- root     root     179,  23 2018-12-12 13:58 mmcblk0p23
brw------- root     root     179,  24 2018-12-12 13:58 mmcblk0p24
brw------- root     root     179,  25 2018-12-12 13:58 mmcblk0p25
brw------- root     root     179,  26 2018-12-12 13:58 mmcblk0p26
brw------- root     root     179,  27 2018-12-12 13:58 mmcblk0p27
brw------- root     root     179,  28 2018-12-12 13:58 mmcblk0p28
brw------- root     root     179,  29 2018-12-12 13:58 mmcblk0p29
brw------- root     root     179,   3 2018-12-12 13:58 mmcblk0p3
brw------- root     root     179,  30 2018-12-12 13:58 mmcblk0p30
brw------- root     root     179,  31 2018-12-12 13:58 mmcblk0p31
brw------- root     root     179,  32 2018-12-12 13:58 mmcblk0p32
brw------- root     root     179,  33 2018-12-12 13:58 mmcblk0p33
brw------- root     root     179,  34 2018-12-12 13:58 mmcblk0p34
brw-rw---- root     system   179,  35 2018-12-12 13:58 mmcblk0p35
brw-rw---- root     system   179,  36 2018-12-12 13:58 mmcblk0p36
brw-rw---- root     system   179,  37 2018-12-12 13:58 mmcblk0p37
brw------- root     root     179,  38 2018-12-12 13:58 mmcblk0p38
brw------- root     root     179,  39 2018-12-12 13:58 mmcblk0p39
brw-rw---- system   system   179,   4 2018-12-12 13:58 mmcblk0p4
brw------- root     root     259,   0 2018-12-12 13:58 mmcblk0p40
brw------- root     root     179,   5 2018-12-12 13:58 mmcblk0p5
brw------- root     root     179,   6 2018-12-12 13:58 mmcblk0p6
brw------- root     root     179,   7 2018-12-12 13:58 mmcblk0p7
brw------- root     root     179,   8 2018-12-12 13:58 mmcblk0p8
brw------- root     root     179,   9 2018-12-12 13:58 mmcblk0p9
brw------- root     root     179, 120 2018-12-12 13:58 mmcblk0rpmb
brw------- root     root      31,   0 2018-12-12 13:58 mtdblock0
brw------- root     root      31,   1 2018-12-12 13:58 mtdblock1
brw------- root     root      31,   2 2018-12-12 13:58 mtdblock2
brw------- root     root      31,   3 2018-12-12 13:58 mtdblock3
brw------- root     root      31,   4 2018-12-12 13:58 mtdblock4
brw------- root     root      31,   5 2018-12-12 13:58 mtdblock5
brw------- root     root      31,   6 2018-12-12 13:58 mtdblock6
brw------- root     root      31,   7 2018-12-12 13:58 mtdblock7
brw------- root     root      31,   8 2018-12-12 13:58 mtdblock8
drwxr-xr-x root     root              2018-12-12 13:58 platform
brw------- root     root       1,   0 2018-12-12 13:58 ram0
brw------- root     root       1,   1 2018-12-12 13:58 ram1
brw------- root     root       1,   2 2018-12-12 13:58 ram2
brw------- root     root       1,   3 2018-12-12 13:58 ram3
drwx------ root     root              2018-12-12 14:20 vold
brw------- root     root     253,   0 2018-12-12 13:58 zram0

[email protected]:/ $ su -c ls -l /dev/block/bootdevice/by-name
/dev/block/bootdevice/by-name: No such file or directory

[email protected]:/ $ su -c ls -l /dev/block/platform/*/by-name
lrwxrwxrwx root     root              2018-12-12 13:58 3rdmodem -> /dev/block/mmcblk0p33
lrwxrwxrwx root     root              2018-12-12 13:58 3rdmodemnvm -> /dev/block/mmcblk0p14
lrwxrwxrwx root     root              2018-12-12 13:58 3rdmodemnvmback -> /dev/block/mmcblk0p15
lrwxrwxrwx root     root              2018-12-12 13:58 boot -> /dev/block/mmcblk0p27
lrwxrwxrwx root     root              2018-12-12 13:58 cache -> /dev/block/mmcblk0p34
lrwxrwxrwx root     root              2018-12-12 13:58 cust -> /dev/block/mmcblk0p39
lrwxrwxrwx root     root              2018-12-12 13:58 dfx -> /dev/block/mmcblk0p32
lrwxrwxrwx root     root              2018-12-12 13:58 dtimage -> /dev/block/mmcblk0p29
lrwxrwxrwx root     root              2018-12-12 13:58 fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              2018-12-12 13:58 hifi -> /dev/block/mmcblk0p26
lrwxrwxrwx root     root              2018-12-12 13:58 hisitest0 -> /dev/block/mmcblk0p35
lrwxrwxrwx root     root              2018-12-12 13:58 hisitest1 -> /dev/block/mmcblk0p36
lrwxrwxrwx root     root              2018-12-12 13:58 hisitest2 -> /dev/block/mmcblk0p37
lrwxrwxrwx root     root              2018-12-12 13:58 mcuimage -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              2018-12-12 13:58 misc -> /dev/block/mmcblk0p19
lrwxrwxrwx root     root              2018-12-12 13:58 modem -> /dev/block/mmcblk0p30
lrwxrwxrwx root     root              2018-12-12 13:58 modem_dsp -> /dev/block/mmcblk0p31
lrwxrwxrwx root     root              2018-12-12 13:58 modem_om -> /dev/block/mmcblk0p17
lrwxrwxrwx root     root              2018-12-12 13:58 modemnvm_backup -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              2018-12-12 13:58 modemnvm_factory -> /dev/block/mmcblk0p6
lrwxrwxrwx root     root              2018-12-12 13:58 modemnvm_img -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              2018-12-12 13:58 modemnvm_system -> /dev/block/mmcblk0p12
lrwxrwxrwx root     root              2018-12-12 13:58 modemnvm_update -> /dev/block/mmcblk0p20
lrwxrwxrwx root     root              2018-12-12 13:58 nvme -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              2018-12-12 13:58 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              2018-12-12 13:58 recovery -> /dev/block/mmcblk0p28
lrwxrwxrwx root     root              2018-12-12 13:58 recovery2 -> /dev/block/mmcblk0p21
lrwxrwxrwx root     root              2018-12-12 13:58 reserved0 -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              2018-12-12 13:58 reserved1 -> /dev/block/mmcblk0p16
lrwxrwxrwx root     root              2018-12-12 13:58 reserved2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root     root              2018-12-12 13:58 securetystorage -> /dev/block/mmcblk0p13
lrwxrwxrwx root     root              2018-12-12 13:58 sensorhub -> /dev/block/mmcblk0p25
lrwxrwxrwx root     root              2018-12-12 13:58 splash -> /dev/block/mmcblk0p9
lrwxrwxrwx root     root              2018-12-12 13:58 splash2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root     root              2018-12-12 13:58 system -> /dev/block/mmcblk0p38
lrwxrwxrwx root     root              2018-12-12 13:58 teeos -> /dev/block/mmcblk0p23
lrwxrwxrwx root     root              2018-12-12 13:58 trustfirmware -> /dev/block/mmcblk0p24
lrwxrwxrwx root     root              2018-12-12 13:58 userdata -> /dev/block/mmcblk0p40
lrwxrwxrwx root     root              2018-12-12 13:58 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              2018-12-12 13:58 vrl_backup -> /dev/block/mmcblk0p2
 

Jubayer Hasan Ovi

New member
Dec 28, 2018
1
0
0
Hello iam Ovi,,,and i'm new here...can you please tell me someone,how can i update my Samsung SM-G532G/DS...If someone tell me then i will try,,i want to do update my phone from 3 months but i can't...if someone please suggest me how to do that from first to last....i am waiting for your suggestio... Please,,Please,,Please
 

HFtcu59

New member
Jan 2, 2019
1
0
0
Tipatch - Google Pixel 3

Good day, I could use some help with installing a Tipatched .img on a Google Pixel 3.

My Pixel 3 is brand new. It is not rooted. The only modifications I'd previously made was successfully installing TWRP (twrp-3.2.3-0-blueline) via instructions from the Google Pixel 3 page on TWRP.ME (I'm new to the XDA forums so I can't post URL)

I downloaded the Tipatch app from the Play store, installed it, and Tipatched the TWRP .img file (had from above link) that I'd previously copied onto my Pixel 3.
I powered off the Pixel 3 and then VolumeDown/Power for Fastboot mode, selecting "Recovery Mode" which boots device into TWRP.
I tap "Install" button, select Tipatched .img and can install it just fine, the problem I believe I'm having is that a Google Pixel 3 doesn't have a Recovery partition per se, so when I installed this Tipatched .img via TWRP, I only had 3 options for "Select Partition to Flash Image": Boot, System Image, Vendor Image.
When I install the Tipatched .img to the "Boot" partition, it installs fine and on reboot, I can indeed Backup my data which now includes Internal Storage, great! BUT a BIG However is that I can't boot back to the OS (Android). Via TWRP, whether I reboot to "System" or "Recovery", or if I just power down the phone for a minute and power it back up, I always boot back into TWRP. The only way I can get back to the OS is to flash the stock boot image via fastboot commands (connected to my PC) which of course, removes TWRP from my Pixel 3 and I have to start again.

One thing I did try when I started over was copying the Tipatched .img to my PC, I then used "fastboot boot ***tipatched.img" which did temporarily boot this version of TWRP to the device; however, when I installed the .zip file (from twrp.me), of course this is the usual normal install of TWRP whose Backup excludes Internal Storage.

I've been trying to troubleshoot this for a few days now with no new success so I'd appreciate some input
 

BeachNYC

Senior Member
Sep 1, 2014
62
24
28
Dude, this app is AMAZING. Does exactly what it says it will do, quickly, cleanly. And even better, it performs a function that was really needed! Operating perfectly on rooted OnePlus 6T with TWRP 3.2.3-12 . Donated....this is way too good an app to get for free. Thank you!
 
  • Like
Reactions: kdrag0n

kdrag0n

Senior Member
Feb 19, 2016
563
1,475
133
kdrag0n.dev
Good day, I could use some help with installing a Tipatched .img on a Google Pixel 3.

My Pixel 3 is brand new. It is not rooted. The only modifications I'd previously made was successfully installing TWRP (twrp-3.2.3-0-blueline) via instructions from the Google Pixel 3 page on TWRP.ME (I'm new to the XDA forums so I can't post URL)

I downloaded the Tipatch app from the Play store, installed it, and Tipatched the TWRP .img file (had from above link) that I'd previously copied onto my Pixel 3.
I powered off the Pixel 3 and then VolumeDown/Power for Fastboot mode, selecting "Recovery Mode" which boots device into TWRP.
I tap "Install" button, select Tipatched .img and can install it just fine, the problem I believe I'm having is that a Google Pixel 3 doesn't have a Recovery partition per se, so when I installed this Tipatched .img via TWRP, I only had 3 options for "Select Partition to Flash Image": Boot, System Image, Vendor Image.
When I install the Tipatched .img to the "Boot" partition, it installs fine and on reboot, I can indeed Backup my data which now includes Internal Storage, great! BUT a BIG However is that I can't boot back to the OS (Android). Via TWRP, whether I reboot to "System" or "Recovery", or if I just power down the phone for a minute and power it back up, I always boot back into TWRP. The only way I can get back to the OS is to flash the stock boot image via fastboot commands (connected to my PC) which of course, removes TWRP from my Pixel 3 and I have to start again.

One thing I did try when I started over was copying the Tipatched .img to my PC, I then used "fastboot boot ***tipatched.img" which did temporarily boot this version of TWRP to the device; however, when I installed the .zip file (from twrp.me), of course this is the usual normal install of TWRP whose Backup excludes Internal Storage.

I've been trying to troubleshoot this for a few days now with no new success so I'd appreciate some input
That's because the Pixel 3 generation uses the newer A/B partition scheme (almost all new devices are using it). Recovery is part of the boot partition. After you flashed the TWRP image to Boot, your system is only able to boot into TWRP because that image is made to do that and only that.

The official TWRP image cannot be installed like this either. You must flash the installer ZIP instead of flashing an image. In order to use Tipatch on A/B devices, I suggest installing TWRP as normal, rooting, using in-place patching on the boot partition, then unrooting. If you really want to avoid rooting even temporarily, boot into TWRP to retrieve the boot image once it is installed with the following command in the terminal or via ADB:
Code:
cat /dev/block/by-name/boot$(getprop ro.boot.slot_suffix) > /sdcard/twrpboot.img
Once you have the image patch it with Tipatch, then flash the resulting image to the boot partition.
 
  • Like
Reactions: HFtcu59

MRNOT

Member
Feb 10, 2017
19
1
0
When I tried to patch it I get an error saying...

"Oops...
Patch #1 failed: could not find /media' in
image. This is probably not a TWRP image."

I'm on a Samsung Galaxy S7 rooted and twrp 3.2.1.0.
 

kdrag0n

Senior Member
Feb 19, 2016
563
1,475
133
kdrag0n.dev
When I tried to patch it I get an error saying...

"Oops...
Patch #1 failed: could not find /media' in
image. This is probably not a TWRP image."

I'm on a Samsung Galaxy S7 rooted and twrp 3.2.1.0.
This is a known issue. Wait patiently for a fix.

Google play game is not working Pie beta 2I have cleared chache and data but still not working
That has nothing to do with Tipatch. Play Games does not use internal storage.
 

bggold

Senior Member
Sep 13, 2013
1,049
359
103
@sanguinesaintly thanks to you, i can backup my Internal Storage now but @kdrag0n should fix the External Data problem. Can't you make a new menu named Data (excl. storage)?
It's probably not that easy. As stated in the twrp forum they will not support this patch. More changes the greater chance of breaking something.

Fastboot twrp it will not have the patch or remove the patch of you want to backup data excl storage.

Just curious why don't you want storage included at times?
 

pol-der

Senior Member
Nov 30, 2018
200
31
38
It's probably not that easy. As stated in the twrp forum they will not support this patch. More changes the greater chance of breaking something.

Fastboot twrp it will not have the patch or remove the patch of you want to backup data excl storage.

Just curious why don't you want storage included at times?
It's my fault. There is a misunderstanding, sorry.
 
  • Like
Reactions: bggold

kdrag0n

Senior Member
Feb 19, 2016
563
1,475
133
kdrag0n.dev
@sanguinesaintly thanks to you, i can backup my Internal Storage now but @kdrag0n should fix the External Data problem. Can't you make a new menu named Data (excl. storage)?
It's technically possible but it's unlikely that I'll ever implement it because it'd be very fragile and prone to breakage across devices.
 

pol-der

Senior Member
Nov 30, 2018
200
31
38
@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?