Customization Tool 2.0.7

[atvbca]

It doesn't have anything to do with the aml_link_list file, you just can't use the Amlogic Customization Tool to rebuild Nougat firmware, it doesn't pack the system image properly. Currently the only way to modify Nougat firmware is in Linux (pick your flavor), but I don't know of any guides and it's too much for me to explain right now, sorry.

I realize it's been a while since you posted this. I have been trying to make changes to an amlogic img (Nougat) Every time i make changes the aml_list_link file almost doubles in size. The original amlogic img file is 888mb. If i make changes and pack it on a windows pc i get 903mb. If i make the same changes in ubuntu using wine i get 887mb. in either case once i flash the img using the usb burn tool the box just sits on the logo screen and never finishes booting.

I would like to figure out what you are doing different to get your images to work properly.

1. My first questions are what version of ubuntu linux are you using? (i use 16.04 desktop)

2. What version of the Amlogic Customization Tool are you using?

3. What version of wine are you using? (i believe i'm using 2.04 , but there is a newer version)

[qq3y6]

I realize it's been a while since you posted this. I have been trying to make changes to an amlogic img (Nougat) Every time i make changes the aml_list_link file almost doubles in size. The original amlogic img file is 888mb. If i make changes and pack it on a windows pc i get 903mb. If i make the same changes in ubuntu using wine i get 887mb. in either case once i flash the img using the usb burn tool the box just sits on the logo screen and never finishes booting.

I would like to figure out what you are doing different to get your images to work properly.

1. My first questions are what version of ubuntu linux are you using? (i use 16.04 desktop)

2. What version of the Amlogic Customization Tool are you using?

3. What version of wine are you using? (i believe i'm using 2.04 , but there is a newer version)

I might have found a solution, I don't know if I've just been lucky or if it's a real fix. It looks like it's related to the aml_link_list file, and restoring the original one before each packing worked for me so far.

I made a backup of the aml_list_link file of the original ROM and before each packing I run a tiny script which deletes the one in /tmp/level2/system and puts the original back in. It prevents it from growing at each build, and might fix the corrupt/undersized IMG bug.

[scooter2014]

https://www.google.ca/amp/www.droidv...-twrp-2-8-4-0/

Gives option to switch from zip to img files now. Been like that for a bit.

[bluesmanuk]

Can easy just switch from zip to img install in Trwp. Flashed many img in it before that why it good to have.

Is this a recent TWRP feature to be able to flash .IMG files?

Wasn't something I was aware of.

[scooter2014]

Can easy just switch from zip to img install in Trwp. Flashed many img in it before that why it good to have.

[j0rdie]

Burn card maker is an app for your PC that you use to burn an image file to flash your box.

You will never be able to flash a .IMG file through TRWP as it is a full image, not an update as such.

It worked using the Burn Card Maker Tool. Merged the 2 files using the customisation tool

[qq3y6]

well thank you for your help. i appreciate you trying.

It will probably need extracting by another method, the ones that devs use.

I have tried many combination of options in the customisation tool but it always crashes when extracting the system partition.

[bluesmanuk]

It will probably need extracting by another method, the ones that devs use.

I have tried many combination of options in the customisation tool but it always crashes when extracting the system partition.

[qq3y6]

Thanks for your help.

I downloaded it from chinagadgetsreviews

Your image file is too big at 1.3Gb and that it why the Customisation tool is crashing when you try to unpack every element.

Anything over around 1.1Gb is highly likely to have issues in the tool.

How did you come across it in the first place?

Did you create it?

[bluesmanuk]

Can someone help me unpack an IMG

I tried many times to unpak it, but customization tool just crashes after a minute or so of unpacking.

Here is the IMG and url to download... p201.s905.mxqpro4k.img.7z >> http://tinyurl.com/y84hbctu

When you get it open, please only remove org.xbmc.kodi.zip (423 MB) from \system\_preinstall and then repack it.

Thank you for your help.

Your image file is too big at 1.3Gb and that it why the Customisation tool is crashing when you try to unpack every element.

Anything over around 1.1Gb is highly likely to have issues in the tool.

How did you come across it in the first place?

Did you create it?

[qq3y6]

Can someone help me unpack an IMG

I tried many times to unpak it, but customization tool just crashes after a minute or so of unpacking.

Here is the IMG and url to download... p201.s905.mxqpro4k.img.7z >> http://tinyurl.com/y84hbctu

When you get it open, please only remove org.xbmc.kodi.zip (423 MB) from \system\_preinstall and then repack it.

Thank you for your help.

[bluesmanuk]

I already have a stock rom with root and working twrp. The issue is I cant flash the modded rom through twrp as its an img file.

Will the current twrp flash the burn card maker image file

Burn card maker is an app for your PC that you use to burn an image file to flash your box.

You will never be able to flash a .IMG file through TRWP as it is a full image, not an update as such.

[j0rdie]

The burn card maker just flashes a firmware image, so whatever recovery is in the image will get flashed.

Once you have a working Android setup then you can go forward to install TWRP etc

I already have a stock rom with root and working twrp. The issue is I cant flash the modded rom through twrp as its an img file.

Will the current twrp flash the burn card maker image file

[bluesmanuk]

Will give it a try tonight.

Will the burn card maker make a TWRP flashable zip as I no longer have the stock recovery installed?

Or do I have to reflash the stock recovery first to use the SD card?

The burn card maker just flashes a firmware image, so whatever recovery is in the image will get flashed.

Once you have a working Android setup then you can go forward to install TWRP etc

[j0rdie]

Use the burn card maker method, where you can use an sd card to flash.

Will give it a try tonight.

Will the burn card maker make a TWRP flashable zip as I no longer have the stock recovery installed?

Or do I have to reflash the stock recovery first to use the SD card?