[LINUX][TOOL] Android 9.0 partition repack tool!

[bumerc]

bc-tool
A small tool for repacking the main partitions system, vendor, odm and product.

- In this project make_ext4fs has been replaced by e2fsdroid and mke2fs
Advantages over make_ext4fs - reduced sparse-image size

- This tool is only intended for Linux users
- Windows support is not provided

Full integration of the bc-tool (Android 9) in afck

preparation

• Install git

Code: Select all

sudo apt update
sudo apt install git

• clone afck-Project

Code: Select all

git clone https://github.com/anpaza/afck.git

• Install dependencies

Code: Select all

sudo apt install android-tools-fsutils
sudo apt install device-tree-compiler

update *-02b
- Android 10-Q support (experimental)
- added cleanup menu
- added mod-inspect
- added encrypted IMG support
- fixed negative partition size
- other bug fixes
- automatic detection of incompatibility sepolicy
(This function is indispensable when working with faulty custom ROMs, or combine/port two different ROMs)

how to install

• Download bc-tool-update-pie-q-02b

bc-tool-update-pie-q-02b.tar.xz

• Extract bc-tool to afck

Code: Select all

tar xvJf bc-tool-update-pie-q-02b.tar.xz -C ~/afck

• Download ingredients

Code: Select all

cd ~/afck/ingredients
./01-get-it-all
cd ..

How to use
(Read bc-tool/readme.md file for more information)
- List of available mod's

Code: Select all

make mod-help

[ricklar]

Full integration of the bc-tool (Android 9) in afck

Update works great! It's fabulous that it is integrated now. Thank you so much!

And actually reading the ReadMe files does actually help for understanding the usage of the Tool. So, for others that want to use the Tool read the README files!

[mohy]

the download link of bc-tool is not correct, it says File is in owner's trash...

[em3ka]

the download link of bc-tool...

https://forum.freaktab.com/forum/tv-pla ... epack-tool

[bumerc]

the download link of bc-tool is not correct, it says File is in owner's trash...

is updated, thanks for the hint

[ath156]

I try to only alter the language/region parameters for this custom rom https:...............
It unpacks OK. When trying to run "mod-partition-all" it stops with an error about sepolicy. Running "make mod-sepolicy" fixes the error.
But when finally trying to burn it by USB burning tool, although it seems to load successfully until some point, it always gives me a boot loop (returning constantly to TWRP).
The original custom rom burns always successfully.
Is there something I can do about it?

[bumerc]

[mention]ath156[/mention]
this has nothing to do with the bc tool anymore, partitions that you want to combine are not compatible with each other.

[ath156]

[mention]ath156[/mention]
this has nothing to do with the bc tool anymore, partitions that you want to combine are not compatible with each other.

Thank you for your reply.
I am sorry but I was not able to fully understand what you are saying. Are you saying that the original custom rom is made in a "special" way (not according to specifications) therefore bc tool isn't able to combine them in the same way? If in some way I was able to not make the sepolicy check, would it be possible to get a functionig rom as the original?
Sorry but I am just trying to understand what "make mod-sepolicy" actually does and under what circumstances this function leads to properly made images (as by finishing this action successfully I got the impression that the rom wil be OK to burn).
Thank you in advance.

[bumerc]

I have described mod-sepolicy in the readme.md file, this function compiles and replaces precompiled_sepolicy binary if one of the two sha256sum files, which are located in the odm and system partitions, does not match. However, this does not mean that the partitions are coordinated with each other, as a ROM developer you have to do this yourself if necessary.

[ath156]

I have described mod-sepolicy in the readme.md file, this function compiles and replaces precompiled_sepolicy binary if one of the two sha256sum files, which are located in the odm and system partitions, does not match. However, this does not mean that the partitions are coordinated with each other, as a ROM developer you have to do this yourself if necessary.

Thank you very much for clarifying it.