« first day (2 days earlier)      last day (16 days later) » 

Roy Hinkley
Roy Hinkley
14:45
@alecxs I am executing tar as such:

`tar -cvf file_out.tar file_one_in.img file_two_in.img`
@alecxs I'm using Windows 10 that ships with bsdtar.


`tar --help
tar(bsdtar): manipulate archive files
First option must be a mode specifier:
-c Create -r Add/Replace -t List -u Update -x Extract
Common Options:
-b # Use # 512-byte records per I/O block
-f <filename> Location of archive (default \\.\tape0)
-v Verbose
-w Interactive
Create: tar -c [options] [<file> | <dir> | @<archive> | -C <dir> ]
<file>, <dir> add these items to archive
-z, -j, -J, --lzma Compress archive with gzip/bzip2/xz/lzma
alecxs
alecxs
@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
tar -o -vcf vbmeta.tar boot.img vbmeta.img
Roy Hinkley
Roy Hinkley
15:02
@alecxs Forgive me, but is there a difference between tar -o -vcf vbmeta.tar boot.img vbmeta.img and tar -ovcf vbmeta.tar boot.img vbmeta.img ?
alecxs
alecxs
15:29
should not make a difference. you can also use --format ustar
Roy Hinkley
Roy Hinkley
16:08
Both files patch when using those options. I have used Odin to apply the first patch, but have to power down and boot again into Odin mode between each file application. Is that what you would expect? If I don't power down and reboot, then Odin hangs on SetUpConnection segment.
@alecxs Well, there appears to be progress in that while I am still presented with the Warning Not Official Samsung, I am able to get into recovery menu and factory reset. Having said that, after factory reset and reboot, the device still hangs for a long time (~ 2-3 minutes) on Warning Not Official Samsung screen when trying to boot into the new image. I will be testing if I do indeed now have root. Thank you for you guidance.
Roy Hinkley
Roy Hinkley
16:49
@alecxs Unfortunately, I do not have root access. It boots and displays unofficial for ~2-3 minutes then continues into Android. So, I think the vbmeta needs to be an empty image, and maybe vbmeta_samsung needs to be empty as well? Going to give that a go and see how it works out.
 
1 hour later…
alecxs
alecxs
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 24 at 7:34, by alecxs
topjohnwu.github.io/Magisk/install.html#instructions
"Never just flash only AP, or else Odin may shrink your /data filesystem size. Flash AP + BL + CP + HOME_CSC when upgrading."
alecxs
alecxs
18:15
also check 'su' from terminal or adb shell and check magisk logs
 
2 hours later…
Roy Hinkley
Roy Hinkley
19:49
@alecxs There are actually 4 files 2 boot.img, vbmeta.img, and incognito vbmeta.img. So, does it matter which boot.img I use?
@alecxs One other question. When comressing the files back into lz4, which options do you suggest?
 
2 hours later…
Roy Hinkley
Roy Hinkley
22:07
@alecxs Great news, I finally got root access without bricking it! Thank you for your guidance. What worked you ask? Well after all that messing around with tar and lz4, I decided to go back to the original instructions and just wait out the not official software screen.
It stays on that screen for some time, but once it boots into Android, do all the other things and voila - just like he states. The nuance to getting it to work is to NOT uncheck auto-reboot in Odin - let it auto-reboot, do not need to factory reset (unless recovery menu display I guess), reinstall Magisk and then let it reboot.
The Not official Samsung screen delay combined with recovery menu directive is what kept throwing me. If the instructions were updated to at least mention that screen, it probably would have worked on my first attempt. THANK YOU so much for your help.

« first day (2 days earlier)      last day (16 days later) »