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

[hyborian]

hi~
thanks for your effort to help other users.

however I found someone got a simpler way.

it is to
1. rename /data/media into /data/intmem
2. refresh size in backup
3. make nandroid
4. rename back /data/intmem into /data/media

it worked perfectly for me, for many times.

Hmmm, I can create a macro to rename it for me. It will be more than 1 button operation, but I'm fine with that. Thanks.

P.S. *edit* I just realized I already have a macro to move my media files to my SD Card either on a schedule or to press a button. Anyway, thanks for the developer of this.

 

[bggold]

I just tried to inplace patch twrp-3.2.3-1-crosshatch for pixel 3 xl and it says it successfully patches both slots but on restart it is rebooting to fastboot mode with the reason error booting boot.img.

Can get back by flashing stock boot.img, twrp and magisk.

Thanks

 

[kdrag0n]

I just tried to inplace patch twrp-3.2.3-1-crosshatch for pixel 3 xl and it says it successfully patches both slots but on restart it is rebooting to fastboot mode with the reason error booting boot.img.

Can get back by flashing stock boot.img, twrp and magisk.

Thanks

I'm looking into this, same issue on my crosshatch. Stay tuned.

 

[amon-san]

works fine with in place patching on my Galaxy Tab S (SM-T805)
but the status messages are only updated in english language. if your twrp is set to another language, you might be confused because the status says without data/media while in fact the patch works and backs up incl. data/media.
Galaxy S8(sm-g950f) in place patch did not work. but manual patch and flash did. otherwise the same language issuses present.

 

[kdrag0n]

works fine with in place patching on my Galaxy Tab S (SM-T805)
but the status messages are only updated in english language. if your twrp is set to another language, you might be confused because the status says without data/media while in fact the patch works and backs up incl. data/media.
Galaxy S8(sm-g950f) in place patch did not work. but manual patch and flash did. otherwise the same language issuses present.

This is stated. Read the OP or in-app help.

Are you rooted properly? I tested this on an SM-G955FD and it worked perfectly fine.

 

[amon-san]

This is stated. Read the OP or in-app help.

Are you rooted properly? I tested this on an SM-G955FD and it worked perfectly fine.

Must have overlooked it then. ^^

Rooted properly with magisk and BusyBox installed in both cases. But using a newer version magisk on the s8.

 

[ccchan234]

I'm looking into this, same issue on my crosshatch. Stay tuned.

u see,
"making a patch" method is more complex than the
"rename" method.
so now some phones cant use ur patch.


however, i am fair and i think that
ur patch may use with
open recovery script,
which is auto boot to recovery and make
a nandroid.
in this, the renaming method cant be used,
and have to use ur patch.



different method suit different situation,
for me, renaming is simpler and better.
but in one day if i need use open recovery script,
i have to use ur patch then.

 

[AnonVendetta]

I'm getting a "Could not find a /media in image". I already read some of this topic and I'm aware that others have already reported this issue. I have a ZTE Axon 7, so the error isnt limited to just Samsung device. I have tried patching official TWRP image, as well as unofficial images, I get the same error no matter what. I've also tried in-place patching of my currently installed TWRP, same result.

 

[kdrag0n]

Tipatch v1.7 has just been released to fix several crashes and bugs, add support for the Pixel 3/XL, and more. Get it on GitHub, XDA Labs, or Play Store.

It will take a bit to roll out to everyone in the Play Store, so be patient.

Changelog:

​ ​ ​ ​ • Added support for Pixel 3 and Pixel 3 XL
​ ​ ​ ​ • Improved speed of LZMA compression
​ ​ ​ ​ • Added support for XZ compression
​ ​ ​ ​ • Added support for new boot image format (thanks @osm0sis for implementing it in C)
​ ​ ​ ​ • Fixed some crashes with LZMA compression
​ ​ ​ ​ • Updated libraries
​ ​ ​ ​ • Added partial translations in Arabic, German, Dutch, Chinese, and Portuguese (thanks translators!)
​ ​ ​ ​ • Improved app theme
​ ​ ​ ​ • Fixed bugs and crashes
​ ​ ​ ​ • Revised app text and messages

Translations are now closed because my Crowdin trial has expired, and I am not planning to pay for it at this time. Thanks to everyone who helped translate!

Happy patching!

 

[bggold]

That fixed it on the pixel 3 xl.

Patched in place no issues.

Thanks

 

[m0han]

Tipatch v1.7 has just been released to fix several crashes....

is this known to work with themed recoveries like batik? thanks.

 

[me7tarfeek]

@kdrag0n.. You are best…
Very nice tool… was looking for this long time ago..
It worked nicely…

Thanks

 

[kdrag0n]

is this known to work with themed recoveries like batik? thanks.

I don't know, never tried one myself because none of my devices have any. I'd assume so, the UI message patches might fail but it's not critical. If the patch succeeds it should be fine, even if the Backup screen doesn't update (the app will display a warning if any of the message patches failed).

 

[maqo314]

I just realized the most recent lite versions (v1.6 and v1.7) request android.permission.INTERNET and android.permission.ACCESS_NETWORK_STATE. This was not the case before (v1.5 and lower), please fix this so that no unnecessary permissions are requested.

 

[kdrag0n]

I just realized the most recent lite versions (v1.6 and v1.7) request android.permission.INTERNET and android.permission.ACCESS_NETWORK_STATE. This was not the case before (v1.5 and lower), please fix this so that no unnecessary permissions are requested.

That's because I switched to Sentry for crash reporting. Previously I filled Crashlytics' few simple methods with dummy code, but Sentry has a much more complex and advanced API I am leveraging that will require much more work to re-create with dummy code. The Sentry code is disabled and never called upon in the lite version, though it is still there.

I'll try to work on completely eliminating it soon, but there's no guarantees because of a lack of time.

 

[maqo314]

That's because I switched to Sentry for crash reporting. Previously I filled Crashlytics' few simple methods with dummy code, but Sentry has a much more complex and advanced API I am leveraging that will require much more work to re-create with dummy code. The Sentry code is disabled and never called upon in the lite version, though it is still there.

I'll try to work on completely eliminating it soon, but there's no guarantees because of a lack of time.

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.

 

[bggold]

Works fine with twrp-3.2.3-2 on pixel 3xl.

Thanks

 

[TiTiB]

@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

Sent from my SHT-W09 using XDA Labs

 

[stofl]

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

 

[TiTiB]

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

Just a thought. Is your device encrypted? Not sure how this would effect the process, but figured I'd throw in my two cents.

Sent from my SHT-W09 using XDA Labs