Amlogic unpacker windows tool

В теме нет куратора. По вопросам наполнения шапки обращайтесь к модераторам раздела через кнопку под сообщениями, на которые необходимо добавить ссылки.

Сообщение отредактировал derak1129 — 24.03.21, 13:17

Если кому интересно собрал Android 9.0 из исходников от khadas https://github.com/khadas/

Работает:
Включение с пульта
Кнопки пульта работают в системе
Bluetooth
Wifi
Ethernet
Воспроизведение видео

Известные проблемы:
Мерцание при использовании курсора
Пишите что еще

2020-06-27
Обновлен код hwcomposer — исправлены проблемы с черным экраном при смене настроек экрана и при выходе из воспроизведения видео
update_khadas_pie_9377_20200627.img

Это первая прошивка на android 9.0 для устройств на базе S912. Прошивка treble, так что возможна установка gsi ромов в раздел system.

Сообщение отредактировал HighwayStar — 29.06.20, 06:36

Сообщение отредактировал 11asd11 — 05.07.20, 23:19

А вот такой WI-FI+Bluetooth получится прикрутить? AP6630wifi.7z ( 156,49 КБ )

Сообщение отредактировал iCr — 07.07.20, 12:15

Еще вопрос, а в этой сборке поддержка композитного AV-выхода будет?

HighwayStar,

Фактически 3Гб. ОЗУ.
И можно добавить поддержку гигабитных лан?

Доделал u-boot для того чтоб им можно было загружать прошивки на 9 андроиде на устрйоствах с LPDDR3. Пришлось откатить некоторые хаки добавленные khadas и добавить тайминги памяти из ветки android 7.1. Вот исходный код u-boot для android 9.0 для устройств с LPDDR3 https://github.com/Amlogic-Lineage/u-boot/commits/khadas-vims-pie_lpddr

Код u-boot для LPDDR3 не умеет правильно определять размер установленной памяти, поэтому готовые прошивки собраны только для варианта 3 Гб, вроде бы с LPDDR3 таких боксов больше. Ссылки на сборки добавил в исходный пост TAP pro [Android] (Пост HighwayStar #97984308)

LPDDR3 chl: Rank0+1 @ 912MHz
bist_test rank: 0 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 730 rank: 1 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 25 730 — PASS

Сообщение отредактировал Brahner — 10.07.20, 08:40

Добавил сборки для DDR3/DDR4 с поддержкой автовыбора 1/2/3 Gb памяти. TAP pro [Android] (Пост HighwayStar #97984308)

Для DDR3 немного снижена частота, так как некоторые 3Gb боксы используют более дешевую память и не запускаются на 912Mhz

Davietpda выложил бету прошивки под 912-й.

Запустил прошивку Davietpda на 3/32 lpddr3(tx9pro). Загрузчик брал из toxtarparavos.
+ Мерцания в сборке Davietpda нет
+ Одновременно работают пульты от h96pro plus и от ветки tx92(z6, z6 plus, tx9pro и тд.). Как в андройде, так и включение коробки
+ WiFi(qc9377 ) и 1000 ethernet работают
— Но у меня не работает один из usb портов на моей плате
— bluetooth не работает, не включается

Кто проверял, как у Вас?
Образ прошивки на mega
Отдельно архив с загрузчиками lpddr3 из образ toxtarparavos: Менять нужно все. DDR.USB и UBOOT.USB нужны в момент прошивки. bootloader.partition прошивается в пзу и загружает коробку.
bootloader_LPDDR3_Android_9.zip ( 1,58 МБ )

Сообщение отредактировал Brahner — 13.07.20, 14:24

alexesgg,

Поставил на h96pro+ 3/32
Проводная сеть воркает, вайфай тоже.
Бт вроде как нет.
Вообщем то очень неплохо.
Правда видит только 2гб памяти..

[TOOL] Amlogic Unpacker — Windows Tool to Unpack/Repack Oreo Images

Breadcrumb

N’ayam Amarsh’e

Senior Member

THE FOLLOWING GUIDE IS FOR OREO IMAGES.
TO UNPACK AMLOGIC 9.0 PIE IMAGES, WATCH THIS TUTORIAL VIDEO: https://youtu.be/exDD6YOC4HU

Hey Everyone! Many people requested me on forumXperience to make a repacking/unpacking guide for Amlogic Oreo/Pie Images. So yesterday, when I had time I started to create my own windows tool for you guys to unpack and repack Amlogic Oreo/Pie Images.

You can now easily extract files in a few clicks and edit them to flash on your devices!

Very simple to use and it works great and is also faster than stock Amlogic Customization Tool which unfortunately doesn’t support Oreo images.

There may be a few bugs that I am unaware of, so please let me know if you run into any problem. Later, I may add recovery and kernel unpacking option in the tools.
Thanks to Ricky for his Customisation Tools, I used his binaries for this project

The tool is pretty much open for everyone to edit and modify, it has batch scripts so you can easily edit with Notepad and learn the process of Amlogic Unpacking/Repacking manually [emoji23]

[TOOL] Amlogic Unpacker — Windows Tool to Unpack/Repack Oreo Images

Breadcrumb

moksy_1

Member

Our team member just released an Amlogic 9.0 Unpacker on our forum

Sent from my RMX1901 using Tapatalk

N’ayam Amarsh’e

Senior Member

Sorry for the late reply, looks like the reply I sent before didn’t go through.
Here’s the link
https://forum.atvxperience.com/viewtopic.php?f=16&t=1776

Scroll down a bit and I have provided a script for unpacking, you can use that. Also make sure to put all folders in your home directory. Have fun Customizing

moksy_1

Member

Sorry for the late reply, looks like the reply I sent before didn’t go through.
Here’s the link
https://forum.atvxperience.com/viewtopic.php?f=16&t=1776

Scroll down a bit and I have provided a script for unpacking, you can use that. Also make sure to put all folders in your home directory. Have fun Customizing

N’ayam Amarsh’e

Senior Member

Tutorial video for modding Android 9.0 Amlogic Images
https://youtu.be/exDD6YOC4HU

Sent from my RMX1901 using Tapatalk

moksy_1

Member

Tutorial video for modding Android 9.0 Amlogic Images
https://youtu.be/exDD6YOC4HU

Sent from my RMX1901 using Tapatalk

hawkdown77

Senior Member

mohy1376

New member

Sorry for the late reply, looks like the reply I sent before didn’t go through.
Here’s the link
https://forum.atvxperience.com/viewtopic.php?f=16&t=1776

Scroll down a bit and I have provided a script for unpacking, you can use that. Also make sure to put all folders in your home directory. Have fun Customizing

thanks, how can I use this to change boot logo for s905x3 android 9 firmware?
I’ve tried something but I just get upgrade_error.bmp, upgrade_fail.bmp.
and I didn’t get bootup.bmp!

valemal

Member

Hi Nayam thanks for this tool but i got this Error in ramdisk block tying to repack S905X2 boot.img the file. I cant repack/unpack S905X2 boot img. Help me please repack this boot.img

boyriot

Senior Member

sevsman

Senior Member

Sorry for the late reply, looks like the reply I sent before didn’t go through.
Here’s the link
https://forum.atvxperience.com/viewtopic.php?f=16&t=1776

Scroll down a bit and I have provided a script for unpacking, you can use that. Also make sure to put all folders in your home directory. Have fun Customizing

I’m ready to donate as soon as possible, I just have a couple of questions first.
Is there any reason I can’t access the YouTube tutorial about working with android 9 images and is there still support for your donate Kitchen?

thanghn90

Member

I’m ready to donate as soon as possible, I just have a couple of questions first.
Is there any reason I can’t access the YouTube tutorial about working with android 9 images and is there still support for your donate Kitchen?

asadace1

Member

New download link is here

New download link is here

Attachments

lchang.atsoft

Member

Repack for Android 9 Pie

Has anyone had any luck on repacking system or vendor partition for an Android 9 firmware? The YouTube video is private so I can’t watch it. I tried repacking but the generated img causes a boot loop. I haven’t made any modifications (simply unpacking and repacking to test the tool). Any advice? Or is this tool no good for Android 9? Thanks for your help!

N’ayam Amarsh’e

Senior Member

lchang.atsoft

Member

lchang.atsoft

Member

When Android starts for the first time after a ROM flash, there is a screen with a progress bar where Android installs pre-apps. I would like to change the background on that screen but can seem to figure out where it is located. It is probably embedded in an app. Does anyone know? Can you point me in the right direction? Thanks!

lchang.atsoft

Member

Amlogic Logo Partition

Does anyone know, on an Amlogic device, what is the format of the logo.PARTITION? It contains several BMP images such as bootup, upgrade_success, upgrade_error, etc. I want to know how they are packed and what tool I can use to unpack and repack them. Thanks!

wgforward

New member

windxixi

Senior Member

harishkanoje147

New member

I unpacked the android 9 rom successfully but during repack i am facing this error please help me

d
check source folder.
ok

system/lost+found is already removed!
cleanup previous build
[sudo] password for harish:

dtb check ok!
calculate IMG size
Error at ‘/partitions/system’: FDT_ERR_BADMAGIC
size: 0

create ext4 fs.
#################
0+0 records in
0+0 records out
0 bytes copied, 0.000117464 s, 0.0 kB/s
mke2fs 1.43.3 (04-Sep-2016)
mke2fs: Device size reported to be zero. Invalid partition specified, or
partition table wasn’t reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table.

[TOOL] Amlogic Unpacker — Windows Tool to Unpack/Repack Oreo Images

Breadcrumb

N’ayam Amarsh’e

Senior Member

THE FOLLOWING GUIDE IS FOR OREO IMAGES.
TO UNPACK AMLOGIC 9.0 PIE IMAGES, WATCH THIS TUTORIAL VIDEO: https://youtu.be/exDD6YOC4HU

Hey Everyone! Many people requested me on forumXperience to make a repacking/unpacking guide for Amlogic Oreo/Pie Images. So yesterday, when I had time I started to create my own windows tool for you guys to unpack and repack Amlogic Oreo/Pie Images.

You can now easily extract files in a few clicks and edit them to flash on your devices!

Very simple to use and it works great and is also faster than stock Amlogic Customization Tool which unfortunately doesn’t support Oreo images.

There may be a few bugs that I am unaware of, so please let me know if you run into any problem. Later, I may add recovery and kernel unpacking option in the tools.
Thanks to Ricky for his Customisation Tools, I used his binaries for this project

The tool is pretty much open for everyone to edit and modify, it has batch scripts so you can easily edit with Notepad and learn the process of Amlogic Unpacking/Repacking manually [emoji23]

[TOOL] Amlogic Unpacker — Windows Tool to Unpack/Repack Oreo Images

Breadcrumb

Tonian1878

Senior Member

Yes i use 6.0.0 (only for repacking, its useless for unpacking)

try repacking with NAYAMS tool first, ignore the .img it creates and copy just the level 1 contents over to rickys tool «tmp» folder and then repack with Rickys tool.

Member

Yes i use 6.0.0 (only for repacking, its useless for unpacking)

try repacking with NAYAMS tool first, ignore the .img it creates and copy just the level 1 contents over to rickys tool «tmp» folder and then repack with Rickys tool.

Tonian1878

Senior Member

NAYAMS tool only updates the «SYSTEM.partition» and «Vendor.Partition».

you could just copy the repacked «SYSTEM.partition» and «Vendor.Partition» from Nayams level 1 folder. unpack your stock image in Rickys tool (level 1) and then replace the older «SYSTEM.partition» and «Vendor.Partition» with your newer updated ones and then repack.

Member

NAYAMS tool only updates the «SYSTEM.partition» and «Vendor.Partition».

you could just copy the repacked «SYSTEM.partition» and «Vendor.Partition» from Nayams level 1 folder. unpack your stock image in Rickys tool (level 1) and then replace the older «SYSTEM.partition» and «Vendor.Partition» with your newer updated ones and then repack.

When i change the path in the script to:

\system \system\ etc\selinux\plat_file_contexts
and
\vendor\etc\selinux\vendor_file_contexts (in \vendor\etc\selinux\ is a file with the name vendor_file_contexts i dont know if this is the right one)

I can repack the image with no errors.. but my device stuck in a bootloop after flashing the image.

Tonian1878

Senior Member

When i change the path in the script to:

\system \system\ etc\selinux\plat_file_contexts
and
\vendor\etc\selinux\vendor_file_contexts (in \vendor\etc\selinux\ is a file with the name vendor_file_contexts i dont know if this is the right one)

I can repack the image with no errors.. but my device stuck in a bootloop after flashing the image.

Ill retry again tonight and write a more detailed process down.
What device is this for? i’ve only used this method for the A95X Max (8.1).

have noticed 1 annoying flaw as well. the is a 700mb OTA update for A95X Max which basically resets most the system changes i made to the original stock firmware.
Obviously i could ignore the update but am guessing its fixing something.

gonna try and merge the OTA update.zip with the original stock firmware

Member

Ill retry again tonight and write a more detailed process down.
What device is this for? i’ve only used this method for the A95X Max (8.1).

have noticed 1 annoying flaw as well. the is a 700mb OTA update for A95X Max which basically resets most the system changes i made to the original stock firmware.
Obviously i could ignore the update but am guessing its fixing something.

gonna try and merge the OTA update.zip with the original stock firmware

I1V1A1N

Senior Member

N’ayam Amarsh’e

Senior Member

The problem is when I unpack the image with nayams tool and I come to the point where the «file_contexts» file to be created the following error appear: «The system can not find the specified path»

this error appears because the path in the script:

Is wrong. The right path is: \system \system\ etc\selinux\plat_file_contexts and in \vendor\etc\selinux\ is no file with the name «nonplat_file_contexts» .

So if i try to repack the system/vendor.PARTITION it dosent work so i have nothing that i can replace.

When i change the path in the script to:

\system \system\ etc\selinux\plat_file_contexts

\vendor\etc\selinux\vendor_file_contexts (in \vendor\etc\selinux\ is a file with the name vendor_file_contexts i dont know if this is the right one)

I can repack the image with no errors.. but my device stuck in a bootloop after flashing the image.

Good find!
I used the basic file_context method.
Those 2 files are generally found in all nougat and oreo firmwares but those which don’t have it, have to use a different file with a different name.
I’ll let you know all the places where you can find the file_context contents.

Sent from my RMX1901 using Tapatalk

I1V1A1N

Senior Member

N’ayam Amarsh’e

Senior Member

Did you port Lineage to S905X?

Sent from my RMX1901 using Tapatalk

I1V1A1N

Senior Member

Did you port Lineage to S905X?

Sent from my RMX1901 using Tapatalk

bunpbu

New member

Can I Replace the recovery.PARTITION file by my recovery.img file?

———- Post added at 03:22 AM ———- Previous post was at 02:43 AM ———-

I cant Repack.
I Unpack Successful, but when repack, failed at system.PARTITION
my file is here: Google Driver

N’ayam Amarsh’e

Senior Member

Can I Replace the recovery.PARTITION file by my recovery.img file?

———- Post added at 03:22 AM ———- Previous post was at 02:43 AM ———-

I Unpack Successful, but when repack, failed at system.PARTITION

Seems like system.Partition couldn’t be read.
Look in the folders if system.partition is there.
Or try manually entering the commands one by one in CMD, it will help better.
I’ll also be updating the tools for Android 9 soon.

Sent from my RMX1901 using Tapatalk

yumaxx

New member

I encountered such a problem, after repackaging the image, without making changes, the boot stops at such lines:
amlkey_init() 71: already init!
[EFUSE_MSG]keynum is 4
[BL31]: tee size: 0
[KM]Error:fAmlogic unpacker windows toolL507:key[usid] not programed yet
[KM]Error:fAmlogic unpacker windows toolL507:key[deviceid] not programed yet
InUsbBurn
noSof
gpio: pin GPIOAO_2 (gpio 102) value is 1
kvim#

image only unpack and repack without changes
atvX_p212_Oreo.7z

toilatoiok

Member

mohy1376

New member

Seems like system.Partition couldn’t be read.
Look in the folders if system.partition is there.
Or try manually entering the commands one by one in CMD, it will help better.
I’ll also be updating the tools for Android 9 soon.

Sent from my RMX1901 using Tapatalk

I’m using magicsee n5 max firmware (android 9 :N5MAX_MT138B_4GB_upgrade_package_20190702)

In my case, I found plat_file_contexts in \system\system\etc\selinux instead of \system\etc\selinux. but I didn’t find nonplat_file_contexts.

there is a vendor_file_contexts in \vendor\etc\selinux and by that, repack.bat works correctly. but when I use this new image, magicsee gets stuck at the boot logo!

ath156

Senior Member

I have 2 Android 9 custom roms for Android Box H96 plus X2. The one I have installed has everything functioning OK except that the original remote control cannot turn on the TV box once it is fully shutdown.The other one doesn’t have this malfunction.So I am trying to create a new rom by using some level 1 files/partitions from the second rom to the first (I read somewherwe about Bootloader, DDR and UBOOT).

I realized that I need to unpack with your tool both the custom roms Only to level 1.Then I can use Rickys Customization Tool to repack from level 1. In the meantime I have to find which partitions to alter from one to another before repacking (there is no bootloader partition in level1 of my android 9 rom-maybe by another name?).

moksy_1

Member

Hi thanks for this tool but i got this error tying to repack & the file size in only 38mb where it should be 1gb

LOG OUTPUT:
+++++++++++++++++++++++++
Repack System
+++++++++++++++++++++++++
Fichier supprimé — F:\X96 Box\AmlogicUnpackerbyNayam\unpacked\level1\system.PARTITION
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label: system
Blocks: 524288
Block groups: 16
Reserved block group size: 127
error: build_directory_structure: cannot lookup security context for /system/acct

+++++++++++++++++++++++++
Repack Vendor
+++++++++++++++++++++++++
Fichier supprimé — F:\X96 Box\AmlogicUnpackerbyNayam\unpacked\level1\vendor.PARTITION
Creating filesystem with parameters:
Size: 799997952
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 3051
Label: vendor
Blocks: 195312
Block groups: 6
Reserved block group size: 47
error: build_directory_structure: cannot lookup security context for /vendor/bin

+++++++++++++++++++++++++
Repack Image
+++++++++++++++++++++++++
[Msg]Pack Item[USB , DDR] from (unpacked\level1\DDR.USB),sz[0xc000]B,
[Msg]Pack Item[USB , UBOOT] from (unpacked\level1\UBOOT.USB),sz[0xc4000]B,ft[normal]
[Msg]Pack Item[PARTITION , _aml_dtb] from (unpacked\level1\_aml_dtb.PARTITION),sz[0x1c800]B,ft[normal]

[Msg]Pack Item[VERIFY , _aml_dtb] from (unpacked\level1\_aml_dtb.PARTITION),vry[sha1sum 5772c23f11c1e18ed08bcb21617a6ed1e5adda8d]
[Msg]Pack Item[UBOOT , aml_sdc_burn] from (unpacked\level1\aml_sdc_burn.UBOOT),sz[0xd0200]B,ft[normal]

[Msg]Pack Item[ini , aml_sdc_burn] from (unpacked\level1\aml_sdc_burn.ini),sz[0x18a]B,
[Msg]Pack Item[PARTITION , boot] from (unpacked\level1\boot.PARTITION),sz[0x936000]B,ft[normal]
[Msg]Pack Item[VERIFY , boot] from (unpacked\level1\boot.PARTITION),vry[sha1sum 05aca866e459ddeaf075a4acab950996f4557195]
[Msg]Pack Item[PARTITION , bootloader] from (unpacked\level1\bootloader.PARTITION),sz[0xd0000]B,ft[normal]

[Msg]Pack Item[VERIFY , bootloader] from (unpacked\level1\bootloader.PARTITION),vry[sha1sum 6b78f83d1fc3df213f68ffd47fda1026d292bf37]
[Msg]Pack Item[PARTITION , dtbo] from (unpacked\level1\dtbo.PARTITION),sz[0x1b6]B,
[Msg]Pack Item[VERIFY , dtbo] from (unpacked\level1\dtbo.PARTITION),vry[sha1sum 7e63f51086267cbfc7ea71d55d89d967a9d2916a]
[Msg]Pack Item[PARTITION , logo] from (unpacked\level1\logo.PARTITION),sz[0x4d0940]B,ft[normal]
[Msg]Pack Item[VERIFY , logo] from (unpacked\level1\logo.PARTITION),vry[sha1sum b438d6a9bcde664f81a17130689f048577dc8bbe]
[Msg]Pack Item[dtb , meson1] from (unpacked\level1\_aml_dtb.PARTITION),Duplicated for _aml_dtb.PARTITION

[Msg]Pack Item[PARTITION , odm] from (unpacked\level1\odm.PARTITION),sz[0x8304c]B,ft[sparse]
[Msg]Pack Item[VERIFY , odm] from (unpacked\level1\odm.PARTITION),vry[sha1sum e75749dd2daee5f3cc0b0932a8ad456dcda9a216]
[Msg]Pack Item[conf , platform] from (unpacked\level1\platform.conf),sz[0xca]B,
[Msg]Pack Item[PARTITION , product] from (unpacked\level1\product.PARTITION),sz[0x60613c]B,ft[sparse]

[Msg]Pack Item[VERIFY , product] from (unpacked\level1\product.PARTITION),vry[sha1sum d49979fd705bb48220dc7c1ad47fffd92a9e669b]
[Msg]Pack Item[PARTITION , recovery] from (unpacked\level1\recovery.PARTITION),sz[0xf24000]B,ft[normal]

[Msg]Pack Item[VERIFY , recovery] from (unpacked\level1\recovery.PARTITION),vry[sha1sum c4d4b669c74b2f5d3dc152ffd07a1b204c2ec517]
[Msg]Pack Item[PARTITION , system] from (unpacked\level1\system.PARTITION),[ERR]f(AmlImagePack.cpp)L1332:failed to open source file : unpacked\level1\system.PARTITION
Image pack FAILED

The new IMG is in repacked folder. Fingers Crossed