Nov 27, 2024 10:18
check home directory ~/RECOVERED_FILES
Nov 27, 2024 10:18
here is example usage for testdisk (little complicated) the red files on that screenshot are deleted ones android.stackexchange.com/a/219364 see you tomorrow, it's late
Nov 27, 2024 10:18
with this tools you can scan your internal storage and your adoptable storage for deleted files as well. photorec is more powerful, binwalk the deepest file search. testdisk has also some options to restore deleted files but that tool is more for repairing partition tables and maybe just as good as extundelete
Nov 27, 2024 10:18
to create such image (if don't have already) run that command while connected in TWRP: 'adb pull /dev/block/dm-0 data.img' or if not encrypted 'adb pull /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userda‌​ta data.img'
Nov 27, 2024 10:18
yes that will scan for deleted files based on inodes. you can also run these tools on your internal storage data.img
Nov 27, 2024 10:18
you should run extundelete or testdisk or photorec or binwalk on /dev/mapper/crypt1 maybe there can be some files recovered (search for that keywords here or www)
Nov 27, 2024 10:18
if 1) is possible that seems the best option
Nov 27, 2024 10:18
but what about the files in sd.img?
Nov 27, 2024 10:18
on the last step, can you please double check disk usage of sd.img? are there files in it? (if you already have sd.img skip creating again and start with kpartx) when mounted run df -h /media/xubuntu/fa6c4c4c-846e-4c6f-8c02-e93cf5ebf448 or find -type f /media/xubuntu/fa6c4c4c-846e-4c6f-8c02-e93cf5ebf448
 
May 16, 2023 19:56
(for apps whose uid differ after inserting)
May 16, 2023 19:53
@dandreye taking out MicroSD card is indeed dangerous, as the package manager purges apps android cannot access. once inserted back, all app data may be deleted from MicroSD card accidentally
May 16, 2023 18:47
@dandreye don't take a sledgehammer to crack a nut. mounting SD card as /data would decrease performance and the unused internal storage is a waste. Link2SD will move it on app base, it can even mix, move only apk and leave app data
May 16, 2023 18:15
if you don't rely in encryption use Link2SD instead. instead of 2nd partition it's possible to loop mount a file into /data/sdext2
May 16, 2023 18:15
your question suggest that adoptable storage is supported. if you can use private it should work for mixed too, but I have no experience
May 16, 2023 18:15
TWRP does the same as you manually do in linux, it decrypted adoptable storage with /data/misc/vold so no need to disable encryption at all
May 16, 2023 18:15
SM-A320FL is FDE regardless of the android version, so no need to disable encryption
 
May 10, 2023 06:32
No, D2D transfer does not require root.
May 9, 2023 13:03
2 days ago, by alecxs
hopeless because you don't have access to database forum.xda-developers.com/t/…
May 9, 2023 13:02
@KaanAyhanoğulları clone to rooted phone and inspect note.db with
May 9, 2023 07:24
118
A: How do you extract an App's data from a full backup made through "adb backup"?

KariOr with a one-liner: ( printf "\x1f\x8b\x08\x00\x00\x00\x00\x00" ; tail -c +25 backup.ab ) | tar xfvz -

May 9, 2023 07:23
on linux / WSL2 the backup.ab ZLIB DEFLATE can be extracted without Java or OpenSSL, if you skip the encryption password.
May 9, 2023 07:11
unfortunately the app 'com.miui.notes' doesn't have the flag android:allowBackup="true" in its manifest. Therefore only phone clone apps can access the app data.
May 9, 2023 07:07
@KaanAyhanoğulları it's fine to ask in chat, that's what it is for ;)
May 7, 2023 12:04
No​ ​ ​ ​ ​ ​ ​
May 7, 2023 12:04
this is not about recovery of deleted files. it's one single existing file note.db only D2D transfer apps have access to. you cannot copy it to PC yourself
May 7, 2023 12:04
rooting requires factory reset. you need backup of app that can restored afterwards.
May 7, 2023 12:04
hopeless because you don't have access to database forum.xda-developers.com/t/…
May 7, 2023 12:04
you can mention the package name and android version
 
Mar 8, 2023 19:28
Feb 6 at 21:46, by alecxs
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Senectus et netus et malesuada fames ac turpis. Justo nec ultrices dui sapien eget. Fames ac turpis egestas integer eget aliquet. Fermentum posuere urna nec tincidunt praesent. Pellentesque pulvinar pellentesque habitant morbi tristique senectus. Tortor at risus viverra adipiscing at in tellus integer feugiat. Lectus nulla at volutpat diam ut venenatis.
Mar 8, 2023 19:27
@Abhishek open notepad editor, copy this piece of random useless text into, save as txt file on your (encrypted) adoptable storage. copy file back to PC and open with text editor. let us know what is inside.
Feb 27, 2023 10:48
@AbhishekRawat the chatroom will closed on inactivity
 
Feb 28, 2023 02:27
@RoyHinkley consider self-answer your question and mark as solution
Feb 28, 2023 02:25
@RoyHinkley I read some post about another Samsung model yesterday where the user states the bootloader unlock warning delay takes 5 min - I thought it was a typo and he meant 5 sec xD
Feb 27, 2023 18:15
also check 'su' from terminal or adb shell and check magisk logs
Feb 27, 2023 17:53
"Never just flash only AP, or else Odin may shrink your /data filesystem size. Flash AP + BL + CP + HOME_CSC when upgrading."
Feb 27, 2023 17:50
@RoyHinkley actually my suggestion was to repack patched boot + vbmeta + vbmeta_samsung with LZ4 into AP and flash BL AP CP CSC on unlocked bootloader, because that is closer to the official instructions.
Feb 27, 2023 15:29
should not make a difference. you can also use --format ustar
Feb 27, 2023 14:54
tar -o -vcf vbmeta.tar boot.img vbmeta.img
Feb 27, 2023 14:52
@RoyHinkley seems bsdtar defaults to posix - hence the pax header. although I didn't had any issues on magisk, it should for sure work on ustar
Feb 25, 2023 12:53
tar -H gnu -vcf vbmeta.tar boot.img vbmeta.img
Feb 25, 2023 12:50
GNU tar works fine to me. either you have an alias somewhere or you have specified incompatible options like xattrs, pax or posix. this should work:
Feb 24, 2023 22:52
@RoyHinkley seems you have used some incompatible GNU tar options. try with busybox tar.
Feb 24, 2023 22:11
boot.img + vbmeta.img + vbmeta_samsung.img = patched.tar
Feb 24, 2023 22:09
You have three patched files now. pack all three files together into one tar for flashing. there is no order to keep as each file has back its own name.
Feb 24, 2023 22:05
after patching both tar files like in the video, extract both tar files and rename the incognito vbmeta.img back to vbmeta_samsung.img (that one from formerly vbmeta_samsung.tar, don't mix up these two)
Feb 24, 2023 21:53
vbmeta_samsung.img -> vbmeta.img + boot.img = vbmeta_samsung.tar
Feb 24, 2023 21:52
vbmeta.img + boot.img = vbmeta.tar
Feb 24, 2023 21:51
@RoyHinkley yes, but 3. and 4. should contain identical file names (for different files)