Closed vbajs closed 7 months ago
ok, i will fix
The error seems to be caused by no system.img being generated and the script skips directly to br packaging which fails due to no system.img found (this is suggested by the line Error Function: datbr
)
Upon attempting to now pack as raw img, the actual culprit is now revealed below
Welcome to the new MIO-KITCHEN
This tool is free forever
Initialization time : 1.545649899999944 Seconds
FsPatcher: Load origin 3075 entries
FsPatcher: Add 0 entries
[Warn] / has too much data.
ContextPatcher: Load origin 3077 entries
ContextPatcher: Add 0 entries
Start packing: system [erofs]
Compression format: lz4hc,1
version: 1.x
D:\ak\MIO-KITCHEN-SOURCE-win\Cherish-OS-v5.2-20240123-1229-sweet-OFFICIAL-GApps\config\system_file_contexts: line 2 has invalid file type u
D:\ak\MIO-KITCHEN-SOURCE-win\Cherish-OS-v5.2-20240123-1229-sweet-OFFICIAL-GApps\config\system_file_contexts: line 2 has invalid file type u
<E> erofs: failed to open file contexts "D:\ak\MIO-KITCHEN-SOURCE-win\Cherish-OS-v5.2-20240123-1229-sweet-OFFICIAL-GApps\config\system_file_contexts"
Try '/AMD64/mkfs.erofs --help' for more information.
mkfs.erofs 1.7.1-g64fa6832
Packaging system succeeded!
Additionally, this is what is listed at at line 2 of system_filecontexts
`/lost+found u : o b j e c t r : r o o t f s : s 0 A workaround is to delete the spaces between, such as it appears like such
/lost+found u:object_r:rootfs:s0`
wtf?
I do not know what happened, but now git pulling into latest commit 43a94e6faa97f3312001164cd61b37dc0a60f3c0 has fixed this issue
MIO-KITCHEN Source was used @ 2a9922ffacb41c16c18c95c05909861c742ab00e Running Windows 11 and did the following steps to run
When attempting to pack any partition as either ext4 or erofs, the following error occurs
I have additionally checked my hard drive for any errors or failures and there seems to be no issues at all at my end I could, if needed, assume that the original ROM zip somehow got corrupted and I can re-download it