Develop Bugs

[ROM] Original docomo SC-02B firmware SC02BOMJJ1

Flash these files in odin with the re-partition checkbox checked, then do a factory reset from the recovery menu. You might get errors about the mmcblk0p3 partition being missing, but that partition is only needed for the dictionary app.
PIT: PIT file for SC-02B
PDA: CODE_SC02BOMJJ1.tar.md5
PHONE: MODEM_SC02BOMJJ1.tar.md5
For reference, here's how I made the backup:
Code:
(on device)
dd if=/dev/block/stl6 of=param.lfs bs=16k
dd if=/dev/block/bml7 of=zImage bs=16k
dd if=/dev/block/stl9 of=factoryfs.rfs bs=16k
dd if=/dev/block/stl10 of=dbdata.rfs bs=16k
dd if=/dev/block/stl11 of=cache.rfs bs=16k
dd if=/dev/block/bml12 of=modem.bin bs=16k
(on my pc)
tar --format=ustar -cf CODE_SC02BOMJJ1.tar zImage param.lfs dbdata.rfs factoryfs.rfs cache.rfs
md5sum -t CODE_SC02BOMJJ1.tar >> CODE_SC02BOMJJ1.tar
mv CODE_SC02BOMJJ1.tar CODE_SC02BOMJJ1.tar.md5
tar --format=ustar -cf MODEM_SC02BOMJJ1.tar modem.bin
md5sum -t MODEM_SC02BOMJJ1.tar >> MODEM_SC02BOMJJ1.tar
mv MODEM_SC02BOMJJ1.tar MODEM_SC02BOMJJ1.tar.md5

Cool. Any note worthy app/function in it?

snapper.fishes said:
Cool. Any note worthy app/function in it?
Click to expand...
Click to collapse
No but if you mess up your SC-02B and want to revert to its original OS, or if you want to extract something from the Japanese OS and put it in your own ROM, this is very useful to have.

I got Samsung Galaxy S/SC-02B with Samsung 19000 firmware; with no IMIE and no base band .I flash it with your [ROM] Original docomo SC-02B firmware SC02BOMJJ1.
IMIE and baseband is back ,but when I put the sim card it say “ no data network found” and no service.
any idia

You SC02 is SIM locked.Find it unlock service in internet.

Thanks so much for this... I live in Tokyo and bricked my SC-02b and this saved my phone!
Much appreciated!

Thank you
i installed the Darkys ROM on my japanese Galaxy S phone..
everything but the phone worked..
this really helped.. i could get my phone back.. but i still want to go back to Darkys or another ROM.. any recommendations anyone?

Currently there are no ROMs, themes, or kernels that will work on our phones perhaps could convince some Dev that their contribution to Japan disaster relief could be something for us to flash.
babakinvan said:
i installed the Darkys ROM on my japanese Galaxy S phone..
everything but the phone worked..
this really helped.. i could get my phone back.. but i still want to go back to Darkys or another ROM.. any recommendations anyone?
Click to expand...
Click to collapse

So i used the above files to flash my phone back to the Original Japanese OS..
Now, it does not recognize the SIM card.
is this because the phone is locked, like the post above suggests?
should i be looking into unlocking the phone? and does anyone recommend any special way to do it?

first of all, thank you for the files that you shared here.
i have a question .. maybe you can help.
i also have a galaxy tab from docomo..
is there a way, to get the modem and dictionary files from the tab to be flashed onto the galaxy s?
your files work , but i cant get the phone to recognize the sim card.
wonder what would happen if i just took it to docomo to get it repaired.. wonder if the warrenty would cover it..

guys did you find the solution for your sim identification problem???
if not then please read my thread i hope it works , for you all !!!!!!!
if it worked then please do something for my thanks meter tooo!!!!!!!!!!

jmaurice said:
Flash these files in odin with the re-partition checkbox checked, then do a factory reset from the recovery menu. You might get errors about the mmcblk0p3 partition being missing, but that partition is only needed for the dictionary app.
PIT: PIT file for SC-02B
PDA: CODE_SC02BOMJJ1.tar.md5
PHONE: MODEM_SC02BOMJJ1.tar.md5
For reference, here's how I made the backup:
Code:
(on device)
dd if=/dev/block/stl6 of=param.lfs bs=16k
dd if=/dev/block/bml7 of=zImage bs=16k
dd if=/dev/block/stl9 of=factoryfs.rfs bs=16k
dd if=/dev/block/stl10 of=dbdata.rfs bs=16k
dd if=/dev/block/stl11 of=cache.rfs bs=16k
dd if=/dev/block/bml12 of=modem.bin bs=16k
(on my pc)
tar --format=ustar -cf CODE_SC02BOMJJ1.tar zImage param.lfs dbdata.rfs factoryfs.rfs cache.rfs
md5sum -t CODE_SC02BOMJJ1.tar >> CODE_SC02BOMJJ1.tar
mv CODE_SC02BOMJJ1.tar CODE_SC02BOMJJ1.tar.md5
tar --format=ustar -cf MODEM_SC02BOMJJ1.tar modem.bin
md5sum -t MODEM_SC02BOMJJ1.tar >> MODEM_SC02BOMJJ1.tar
mv MODEM_SC02BOMJJ1.tar MODEM_SC02BOMJJ1.tar.md5
Click to expand...
Click to collapse
hi,
i have sc-02b flashed to i9000 by my friend and we managed to flashed it with your dumped rom and now his phone was stucked on ntt docomo splash screen..
can you help me sort out the problem?
thanks

http://forum.xda-developers.com/showthread.php?t=1116140
Use this method to update with root to the latest version.
Sent from my SC-02B using XDA

babakinvan said:
i installed the Darkys ROM on my japanese Galaxy S phone..
everything but the phone worked..
this really helped.. i could get my phone back.. but i still want to go back to Darkys or another ROM.. any recommendations anyone?
Click to expand...
Click to collapse
can you tell me Darkys witch rom have you installed ????
please reply

Sco2b file lost
Pls need the files
Pit
Pda
Csc
Tnx

[TUT][DUMP] DUMP Stock ROM (SYSTEM/BOOT/etc) | OneX_SEA_WWE_1.26.707.2_SYSTEM + BOOT

Basically u need adb/android SDK before proceed.
[WITH ROOT ACCESS]
[+] Dump/copy boot.img
Code:
Command prompt :
> adb shell
> su
> dd if=/dev/block/mmcblk0p4 of=/sdcard/boot.img
More partition/img availabe to dump. Will update later.
[WITHOUT ROOT ACCESS]
Currently only /system is usable
1) Android SDK (just need adb)
2) Download busybox
3) Command prompt :
> adb push busybox /data/local/busybox
> adb shell
> cd /sdcard/
> chmod 755 /data/local/busybox
> /data/local/busybox tar cvf sysdump.tar /system
4) Ignore tar: error exit delayed from previous errors'. Is done correctly.
----------------------------------------------------------------------
Just finished dumped my semi-virgin One X system partition from SEA WWE stock ROM .
The file would be OneX_SEA_WWE_1.26.707.2_SYSTEM_DUMP.zip 558.3 MB

Hi,
can you tell me how to dump mine? My phone arrives tomorrow.
Thanks in advance...

@anko
Thread updated with guide.

so, is it true that i can simply download the system dump from the link your provide, and flash it via recovery if i want to go back to stock SEA rom?
by the way, i am using a SEA htc one X too.

ck_looi said:
so, is it true that i can simply download the system dump from the link your provide, and flash it via recovery if i want to go back to stock SEA rom?
by the way, i am using a SEA htc one X too.
Click to expand...
Click to collapse
not sure & never try
it was dumped before i unlock my device.
see here if u want unlock & backup ur stock rom including boot image. do nandroid backup after flashing Interim CWM. Then only restorable. (boot .img still hv to flash thru fastboot to restore or use new method by blubbers)

my current stock is 1.26.707.4
will i be able to flash this and then get update to 707.4 OTA? Just want to make sure i got the right stock rom for my one x.

Picked mine up today going to do system dump of mine its on t-mobile software is 126.110.5
Sent from my HTC One X using XDA

monx® said:
Basically u need adb/android SDK before proceed.
[WITH ROOT ACCESS]
[+] Dump/copy boot.img
Code:
Command prompt :
> adb shell
> su
> dd if=/dev/block/mmcblk0p4 of=/sdcard/boot.img
More partition/img availabe to dump. Will update later.
Click to expand...
Click to collapse
i just dump boot (mmcblk0p4) and system (mmcblk0p12). is that good enough? (maybe recovery partition) I assume i would use fastboot flash to flash this image if I want to revert to stock?

zenkinz said:
i just dump boot (mmcblk0p4) and system (mmcblk0p12). is that good enough? (maybe recovery partition) I assume i would use fastboot flash to flash this image if I want to revert to stock?
Click to expand...
Click to collapse
Yes but RUU 1.26.707.4 is available (at least for our region). better extract *.img directly.

monx® said:
Yes but RUU 1.26.707.4 is available (at least for our region). better extract *.img directly.
Click to expand...
Click to collapse
ok thanks.

I've done Paul's procedure to Unlock + Interim CWM + SU, so now I'm rooted with S-On. After which I've done full backup thru interim CWM recovery prior to uninstalling bloatwares and I'm still now on stock ROM.
How different is this backup then? Back to stock?
Sent from my HTC One X using xda premium

Gday, now this looks like it spits out a tar file, I assume this is flashable through fastboot? I'm just trying to put together a fastboot flashable img of my providers stock rom for another user...
Edit, I might be being stupid, but shouldn't adb pick up the stock rom when connected and booted into rom? Put usb connection into usb host mode...
M.

2nd method works great...
monx® said:
Basically u need adb/android SDK before proceed.
[WITH ROOT ACCESS]
[+] Dump/copy boot.img
Code:
Command prompt :
> adb shell
> su
> dd if=/dev/block/mmcblk0p4 of=/sdcard/boot.img
More partition/img availabe to dump. Will update later.
[WITHOUT ROOT ACCESS]
Currently only /system is usable
1) Android SDK (just need adb)
2) Download busybox
3) Command prompt :
> adb push busybox /data/local/busybox
> adb shell
> cd /sdcard/
> chmod 755 /data/local/busybox
> /data/local/busybox tar cvf sysdump.tar /system
4) Ignore tar: error exit delayed from previous errors'. Is done correctly.
----------------------------------------------------------------------
Just finished dumped my semi-virgin One X system partition from SEA WWE stock ROM .
The file would be OneX_SEA_WWE_1.26.707.2_SYSTEM_DUMP.zip 558.3 MB
Click to expand...
Click to collapse

Does this work on other models?
helloansuman said:
2nd method works great...
Click to expand...
Click to collapse
Hi, I was curious if this worked on other models specifically the xperia arc so-01c. I wish to dump a japanese docomo rom that I guess is pretty rare for English websites. Thanks in advance. AJ

I already have my boot.img and what not just need to dump my boot.img-kernel... How to?

2nd method works great on other phone thankx man!
just tell us one more thing that how to dump boot/kernel in the same is it possible or not ??

[Guide]Modify stock rom and delete bootloader with Knox for Galaxy S4 Mini

Quick and dirty guide on how-to delete bootloader stuff that contain Knox from stock rom ( only works on Jelly Bean ) . On KitKat we have Knox 2.0 which is more harder to conquer
Only use it if u do not have KNOX WARRANTY in download mode
U need : a virtual machine or any linux environment . I use Vmware player + Linux Mint 16 x64
First download the rom from Sammobile and place it on your Desktop in a folder called work in linux
Let`s say we download Russia one for I9192
I9192XXUBMK4_I9192SERBMJ3_SER.zip
U can use this guide on other versions of this phone I9190/I9195
Firmwares that contain MK4/MK5/ML1/ML2/ML4/NA1/NA2 and so on from here have Knox bootloader inside
Only the name will be different but what is inside is the same
Only latest versions of firmware contain Knox Bootloader ( usually the ones released in late november/december 2013 )
Open terminal and type
Code:
cd Desktop
cd work
Now we need to extract it
Code:
unzip *.zip
U will get 2 files
First: I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5
Second: SS_DL.dll
Now again in terminal type:
Code:
rm -rf SS_DL.dll
tar -xvf *.tar.md5
After it will finish to extract we can delete the files we do not need
Code:
rm -rf aboot.mbn - bootloader ( knox included )
rm -rf sbl1.mbn - part of bootloader
rm -rf sbl2.mbn - part of bootloader
rm -rf sbl3.mbn - part of bootloader
rm -rf *.tar.md5
Now we can place it back in an archive. Choose any name u want i had chosen original name for reference only.
Code:
tar -H ustar -c rpm.mbn tz.mbn boot.img recovery.img system.img.ext4 NON-HLOS.bin cache.img.ext4 hidden.img.ext4 > I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar
After comes md5 stuff
Code:
md5sum -t I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar >> I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar
mv I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5
Now transfer it to your windows pc and flash it with Odin Make sure u do not rename the file at this stage or md5 checksum will fail
Double check it before u flash, look inside the archive that u don`t have those files u just deleted Maybe u did not move the correct file
Video of "How to" credit to @Mitko

SilviuMik said:
Quick and dirty guide on how-to delete bootloader stuff that contain Knox from stock rom
Only use it if u do not have KNOX WARRANTY in download mode
U need : a virtual machine or any linux environment . I use Vmware player + Linux Mint 16 x64
First download the rom from Sammobile and place it on your Desktop in a folder called work in linux
Let`s say we download Russia one
I9192XXUBMK4_I9192SERBMJ3_SER.zip
Open terminal and type
Code:
cd Desktop
cd work
Now we need to extract it
Code:
unzip I9192XXUBMK4_I9192SERBMJ3_SER.zip
U will get 2 files
First: I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5
Second: SS_DL.dll
Now again in terminal type:
Code:
rm -rf SS_DL.dll
tar -xvf I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5
After it will finish to extract we can delete the files we do not need
Code:
rm -rf aboot.mbn
rm -rf sbl1.mbn
rm -rf sbl2.mbn
rm -rf sbl3.mbn
rm -rf I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5
Now we can place it back in an archive. Choose any name u want i had chosen original name for reference only.
Code:
tar -H ustar -c rpm.mbn tz.mbn boot.img recovery.img system.img.ext4 NON-HLOS.bin cache.img.ext4 hidden.img.ext4 > I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar
After comes md5 stuff
Code:
md5sum -t I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar >> I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar
mv I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar I9192XXUBMK4_I9192SERBMJ3_I9192XXUBMK4_HOME.tar.md5
Now transfer it to your windows pc and flash it with Odin Make sure u do not rename the file at this stage or md5 checksum will fail
Double check it before u flash, look inside the archive that u don`t have those files u just deleted Maybe u did not move the correct file
Click to expand...
Click to collapse
Is this BMK4 firmware different from previous versions by introducing Knox and improvement of battery? Can we transfer the rpm bootloader to previous version and enjoy the battery consumption improvement?

hobbya said:
Is this BMK4 firmware different from previous versions by introducing Knox and improvement of battery? Can we transfer the rpm bootloader to previous version and enjoy the battery consumption improvement?
Click to expand...
Click to collapse
I think u can yes But i also think some improvements were made in Modem/Kernel
That rpm.mbn file gets flashed in a special partition and does not get overwritten only if u flash a new one from a firmware that contain it. As i mentioned in other forum only last ones does contain it Russia, Brazil, Trinidad MK4

allows downgrade?
Once flashed this firmware without knox, would can move back to a previous version?
I ask that flashing the stock rom of samsung knox is no longer possible downgrade.
Thanks and regards,

Trepanator56 said:
Once flashed this firmware without knox, would can move back to a previous version?
I ask that flashing the stock rom of samsung knox is no longer possible downgrade.
Thanks and regards,
Click to expand...
Click to collapse
Yes u can downgrade as long as u don`t flash new bootloader
Use the tutorial and remove the files from stock rom before flashing. If u already have the new bootloader on phone u are out of luck

SilviuMik said:
Yes u can downgrade as long as u don`t flash new bootloader
Use the tutorial and remove the files from stock rom before flashing. If u already have the new bootloader on phone u are out of luck
Click to expand...
Click to collapse
One question, I flashed the stock thing via Heimdall and my wi-fi is not working. I think it didn't flash the tz.bin, since I saw you say on other thread that it was important for wifi to work in Brazil...
Is there anyway to fix it? Or I got myself screwed?

Dijinn said:
One question, I flashed the stock thing via Heimdall and my wi-fi is not working. I think it didn't flash the tz.bin, since I saw you say on other thread that it was important for wifi to work in Brazil...
Is there anyway to fix it? Or I got myself screwed?
Click to expand...
Click to collapse
Flash it with Odin that tz file and u are good to go
Same procedure as making an kernel from stock or modem
tar -H ustar -c tz.mbn > name.tar
md5sum -t name.tar >> name.tar
mv name.tar name.tar.md5

SilviuMik said:
Flash it with Odin that tz file and u are good to go
Same procedure as making an kernel from stock or modem
tar -H ustar -c tz.mbn > name.tar
md5sum -t name.tar >> name.tar
mv name.tar name.tar.md5
Click to expand...
Click to collapse
Well, we got another problem... Here... I'm on a MAC right now, so my only flashing thingy is Heimdall or ADB...
I tried flashing the tz.mbn file 3 times via Heimdall, it doesn't even open the recovery after I flash it... And wi-fi is never back...
I got ur version of the files and flashed everything again, still, no wi-fi, probably because of the tz.mbn
The funny thing is that Heimdall himself says the file was uploaded to the phone, but it seems it's not "installing" it if u understand what I mean...

Dijinn said:
Well, we got another problem... Here... I'm on a MAC right now, so my only flashing thingy is Heimdall or ADB...
I tried flashing the tz.mbn file 3 times via Heimdall, it doesn't even open the recovery after I flash it... And wi-fi is never back...
I got ur version of the files and flashed everything again, still, no wi-fi, probably because of the tz.mbn
The funny thing is that Heimdall himself says the file was uploaded to the phone, but it seems it's not "installing" it if u understand what I mean...
Click to expand...
Click to collapse
Sorry mate then flash an older file that does not contain Knox Hope u get your Wifi back

SilviuMik said:
Sorry mate then flash an older file that does not contain Knox Hope u get your Wifi back
Click to expand...
Click to collapse
I solved the problem!
If someone else has trouble fixing the Wi-Fi after the flash via Heimdall, here goes!
Flashing TZ partition only won't do anything...you upload the file, but it doesn't seem to get flashed...
The solution is to flash both MODEM and TZ partitions... It seems that when you reflash the modem, the cellphone tends to check for TZ again and TADA! Now it will be there!

Do you think that I could do the same for i9195 ?

Darktitor said:
Do you think that I could do the same for i9195 ?
Click to expand...
Click to collapse
Yes of course Is the same for all 3 models 9190 9192 9195

Great
My friend will be happy
Envoyé de mon GT-I9195 en utilisant Tapatalk

Apparently the contents of S4 (I9505) is same ... I made the change with Ubuntu, it does.
Before to flash, I would like to be sure.
Think it should do as correctly as your model?

franzyroy said:
Apparently the contents of S4 (I9505) is same ... I made the change with Ubuntu, it does.
Before to flash, I would like to be sure.
Think it should do as correctly as your model?
Click to expand...
Click to collapse
I have no ideea about S4 Maybe knox is in other places too like modem or no ideea. I can`t guarantee. On S4 mini is in aboot.mbn sbl1 sbl2 sbl3 ( bootloader )

Thanks for answer!
So, that's the reason you removed the modem.bin file?
What is the risk to try? Except to have the new bootloader.

franzyroy said:
Thanks for answer!
So, that's the reason you removed the modem.bin file?
What is the risk to try? Except to have the new bootloader.
Click to expand...
Click to collapse
I did not remove modem file
modem is named NON-HLOS.bin i keep it
If u have old bootloader ( no knox in download mode ) yes risk is to get new bootloader with knox
Pls check on S4 forums maybe someone did the same as me with S4 and knows more

SilviuMik said:
I did not remove modem file
modem is named NON-HLOS.bin i keep it
If u have old bootloader ( no knox in download mode ) yes risk is to get new bootloader with knox
Pls check on S4 forums maybe someone did the same as me with S4 and knows more
Click to expand...
Click to collapse
On the S4 (I9505), I also have NON-HLOS.bin, but I also have modem.bin file.
Not seen on the S4 forums a subject on that!
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
SilviuMik said:
If u have old bootloader ( no knox in download mode ) yes risk is to get new bootloader with knox
Click to expand...
Click to collapse
Except this risk... This one, I'll have it certainly with the SAV!!
---------- Post added at 03:21 PM ---------- Previous post was at 03:17 PM ----------
Otherwise, I followed your tuto and like I didn't see the modem.bin file, I removed it. At worse, I could flash it after.

franzyroy said:
On the S4 (I9505), I also have NON-HLOS.bin, but I also have modem.bin file.
Not seen on the S4 forums a subject on that!
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
Except this risk... This one, I'll have it certainly with the SAV!!
---------- Post added at 03:21 PM ---------- Previous post was at 03:17 PM ----------
Otherwise, I followed your tuto and like I didn't see the modem.bin file, I removed it. At worse, I could flash it after.
Click to expand...
Click to collapse
Yes of course , better to try then flash all the files and see after
Btw, S4 Mini Knox firmware contains:
sbl1.mbn - part of new bootloader , safe to delete
sbl2.mbn - part of new bootloader , safe to delete
sbl3.mbn - part of new bootloader , safe to delete
aboot.mbn - New Knox bootloader , DELETE
rpm.mbn - Resource power Management link
tz.mbn - Trusted zone ( Wifi won`t work if u don`t flash it together with new Modem )
boot.img - Kernel
recovery.img - Recovery/Download mode
system.img.ext4 - your apps/framework/android
NON-HLOS.bin - modem
cache.img.ext4 - CSC / APN settins / What bloat is to be installed depending on zone / carrier
hidden.img.ext4 - Another "system" part of apps that are too big for /system ( for now almost empty ) on S2 was full of apps
Try and see

Thanks ... I know for the S4(I9505), when we have old bootloader, we must put this (GSM_Modem_XXUEMJ5_and_LTE_Modem_XXUBMH1.zip ) modem for that all works.
Perhaps, I can replace modem.bin and NON-HLOS.bin by those in the zip.

looking for stock rom.zip for Tab 10.5 SM-T805 LTE

I would like to looking for the Stock rom.zip for Tab SM-805 LTE. but can't
please share me if you have or the link for downloading
Thanks so much!

No such thing. Stock firmware comes in a tar package.
samsung-updates.com or sammobile

crownvn said:
I would like to looking for the Stock rom.zip for Tab SM-805 LTE. but can't
please share me if you have or the link for downloading
Thanks so much!
Click to expand...
Click to collapse
You need to download the whole firmware package (which is a .tar archive), extract it, and get system.img
After that, you need to use (on a either linux OS or cygwin/VM with linux) simg2img to unpack the raw partition found in system.img
Code:
simg2img system.img system.raw
Next, you need to mount that raw partition to a premade folder
Code:
mkdir system_unpacked
sudo mount -t ext4 -o loop system.raw system_unpacked
You now have your stock rom unpacked. Pack the files found in system_unpacked in a .zip, add a propper META-INF with a propper updater script and that's all
P.S. Google is your friend in all this process!
P.P.S. if your tablet is already rooted, you can use flashfire on it to directly flash the system.img (as @ashyx mentioned in his great rooting guide)
All in all, good luck! Cheers!:good:

Repack Stock Firmware with Android 10 for Odin

I am trying to de-bload/modify the original stock firmware and flash it to my phone using odin without installing TWRP. I have already successfully flashed Magisks this way. However, all the guides I found on modifying the system.img seem to be outdated and do not work anymore.
Here is my current workflow (all on Debian 10)
Code:
tar xvf AP_*.tar.md5 #from original stock rom package or magisk_patched_*.tar) into sub-directory
lz4 -d system.img.lz4
simg2img system.img system.raw.img #either the Debian version or fresh compile from https://github.com/anestisb/android-simg2img
mkdir sys
sudo mount -t ext4 -o loop system.raw.img sys/
# Do a bunch of changes in the mounted image e.g. delete Samsung bloatware
sudo umount sys/
img2simg system.raw.img system.img
lz4 -B6 --content-size system.img system.img.lz4
tar --owner=1000 --group=1000 -H ustar -cvf AP_modified.tar *
md5sum -t AP_modified.tar >> AP_modified.tar
mv AP_modified.tar AP_modified.tar.md5
Unfortunately, the resulting file does not work because odin hangs or odin finishes and the phone is stuck in a boot loop. Anybody knows what I am missing here. Bootloader is unlocked, as I said, I could successfully flash the modified AP_* from magisk.