yashsingh1/xdaforums huggingface dataset:
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
https://xdaforums.com/android/software-hacking/updated-android-img-tools2019-t3891887
[Android Stick & Console AMLogic based Computers] beta.0:
So you fixed the no boot issue with S912 firmware in v6?
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
There was an issue? did it include a vendor partition by any chance? as far as i can tell it was only vendor and possibly DTB that had issues
[Android Stick & Console AMLogic based Computers] beta.0:
There's no vendor partition, it's an Android 7.1.2 firmware. I just unpacked and repacked to img file without making any changes to system and it gets stuck on the boot logo every time. It seems like system is not packing right because it happens way too fast but the log shows all partitions as being packed successfully. Is there some debugging I can do to help you solve this?

Here's the problem firmware: http://www.bee-link.com/forum.php/forum.php?mod=viewthread&tid=41741&extra=page=1

Same issue with Avaltech ROM based on the same firmware: https://drive.google.com/drive/folders/1T4ItFiXoaQ_mBa5_EZkS8IEePLsymnM9
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
PM me for a link to a test build, im sure it should fix all issues
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Guys, there will be a donate version of customization upon next release aswell, it will have extra features, more support aswell as on the fly and exclusive updates, the free version will still be functional for 8.1
[Android Stick & Console AMLogic based Computers] romcrazy:
Hello glad I found this here, Hey xanny sir I have been pestering you since yesterday on your freaktab thread. I can follow the incoming 6 version here. I hope it corrects my issue. Ricky sir, my s905x2 firmware if i unpack and repack without any changes, gets stuck on boot logo and goes to bootloop. I am hoping v6 will help me solve this. Thanks
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
It definately does :)

I was testing on S905x2 firmware and fixed any residing issues
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Anyone looking to get the donate version simply donate HERE

and email rickyd.engineering@gmail.com and supply your email address you donated from!
[Android Stick & Console AMLogic based Computers] romcrazy:
oh thanks i am waiting for the release of new version, meanwhile if you could release a play store working version of poison rom too, it would save me the hassle of tinkering with this tool altogether.
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
It definately wouldnt be a system error, im assuming its a DTB issue thqt was pointed out earlier, for some reason i have to append null data to conpensate for the loss of size, i can fix this easily
[Android Stick & Console AMLogic based Computers] beta.0:
Another thing I forgot to mention, the original firmware img is 1.08 GB but the repacked img is 2.03 GB. Something aside from the DTB issue must be amiss.

Could it be something to do with this being a device with 3GB of memory? Why is there no img2simg line in the log file? Did you just forget to append it?
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
The size issue is a small code issue due to implementing Xannytechs suggested method of preserving the size, this however will have to be changed because of the simple fact the size will change if stuff is removed or added
[Android Stick & Console AMLogic based Computers] Hellera:
Hello [MENTION=5105831]Ricky Divjakovski[/MENTION], I installed your latest firmware on a Tanix TX3 mini, I like a lot your work, very good! But I have a problem, I think a big one for me... So,if I'm watching a movie with Kodi and I pause it for a while, lets say 5-10 minutes, of course, the screensaver is doing his job, but it will exit the movie... so, if I did not have a bookmark in the movie I must start it from the beggining... I think it's not normal, is frustrating... What should I do, what can be done? Can you help me with this problem? Thank you very much.

Oh, one more question... after I stop completely the tv box, the display is still working... "boot"... Only if I'm unplugging the power cord it shutdown completely.
[Android Stick & Console AMLogic based Computers] Xannytech:
Hi Ricky, be careful, the partitions have to be recompiled with the size they had, or the rom will not boot or you should change the whole firmware partitioning, the problem is always the same, i took that line from the user message :

make_ext4fs -L system -T 1548525880.96948 -S "tmp\level2\file_contexts" -l 2147483648 -a system "tmp\level2\system.img" "tmp\level2\system"

as i corrected in your script days ago, the compiling should be:

make_ext4fs -L system -T 1548525880.96948 -S "tmp\level2\file_contexts" -l 2147483648 -s -a system "tmp\level2\system.img" "tmp\level2\system"

You NEED to compile back the image to sparse, the compiling line lacks of the right parameters (-s), leave the size of the partition as i told you or you'll get problems.

So the issue is caused by the lack of a parameter ;) not by the size.
[Android Stick & Console AMLogic based Computers] beta.0:
Hijacking threads is against forum rules. This thread is for AMlogic Tools. Please post in the thread for the firmware you're asking about.
[Android Stick & Console AMLogic based Computers] Hellera:
Ok, I think I was not carefull, I apologize.
[Android Stick & Console AMLogic based Computers] beta.0:
But if you add stuff to system and it exceeds the original partition size then it would have to recalculate the proper size. So leaving the size alone would not be a proper solution. Unless I'm missing something?

So I was right that it's not converting to sparse. The sparse conversion step happens way too fast to have succeeded (~3 seconds). I've been building custom roms for years with my own linux kitchen and I know from experience that it takes longer to convert to sparse than to pack the final image.
[Android Stick & Console AMLogic based Computers] Xannytech:
The memory your device assign to system or vendor is predefined in other files, if you try to modify system size youll get a unfunctional firmware.

in Android 7.1.2 system was 2Gb, on oreo now is 1,5 Gb, vendor is not fixed, Beelink not following google rules do stupid things and has just a 250mb partition, other devices uses 512 or 1,5gb depending on the device memory size 2gb, 3gb, i nver saw ultil now a fw with a 4gb vendor+system.

It's possible to change the device partitioning but too much work has to be done and it's really unnecessary, it's simpler to stay in manufacturer decided partitions sizes.

Anyway what you don't get is: you got for example 2gb of system space, if your system is 200mb the system will be 200mb, if you exceed the 2gb the recompiling will create a unfuncional image. From Oreo what is not essential google system has to be in Vendor partition, so it's easyer for google to update the Android system without vendor customization. So 2gb or 1,5gb are more than enough.

If the partition size is been recalculated by the kitchen, and the "cook" exceed the device physical memory what happen? Unfunctional firmware.

NOTE:

I do not wanna open android developing lessons so i omitted some infos deliberately ;) and i simplified things 'cause we are talking about amlogic firmwares.
[Android Stick & Console AMLogic based Computers] beta.0:
I already knew about the size limit on system, ran into the issue many times, the vendor stuff is all new to me though. I was just wondering how hard it would be to resize the system partition and your answer sums it up. "It's possible to change the device partitioning but too much work has to be done and it's really unnecessary, it's simpler to stay in manufacturer decided partitions sizes."

Thanks for the semi detailed explanation! :)
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
I actually made a class to regenerate/write the partition table a while back, i was almost complete but i found it quite useless and problematic so i never pushed forward with it, it did this without the need to unpack the DTB, it read each byte formed an array after the "partition" header was found, however re-writing i always found myself writing the new partition table to early or late so it may definately be a worthy option if i finish this class
[Android Stick & Console AMLogic based Computers] SlightlyNoobish:
Remove.conf

Hey Ricky,

Thanks for making these great tools.

I Tried extracting an IMG file from the custom ROM and it failed.

The program crashed right after it said failed to open Kernel. Any tips?

Is this related to me opening the file that was created for an SD card???

How would I go about recompiling SD card contents to a singular IMG if I don't have original image?
[Android Stick & Console AMLogic based Computers] beta.0:
Just unzip the custom ROM zip file first and inside you'll find update.zip or upgrade.zip or something similarly named. Open that zip with the Customization tool and it should work. It can open img files, SD zip files and even OTA based zip files and convert them to img (USB Burning Tool) or SD zip (flash from recovery) format.
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
We are now able to modify the partition table!
[Android Stick & Console AMLogic based Computers] Xannytech:
that's really cool :good: put a disclaimer about it or we have to provide a tutorial :D
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Most definately, the image sizes are also repacked using the length provided from this so its pretty much impossible for any issues and if a company follows googles guidelines of not is not going to be a factor
[Android Stick & Console AMLogic based Computers] SlightlyNoobish:
Cool thanks
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
that is irregular, extract the update-frontline file then try unpacking that with my tool
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
As i pretty much just modified my source i forgot to add the -s param

For now you are able to check the DTB with an editor, search for "partitions" and convert the hex size of the partition to decimal, this is a much more efficient way of doing this so regardless of any manufacturer/distributor modifying the partition sizes this will get to the bottom of it

In V6 my tool will do this programatically, so far ive made a class to extract/insert the partition table from the DTB and a class to convert the values to decimals so its pretty much done aswell as the abillity to modify the table(will be in donate version)

Im in the process of making core modifications to the tools aswell as prep the donate version as much as i can, so i appologise if im not very active in this thread but i am working around the clock to get these
[Android Stick & Console AMLogic based Computers] Xannytech:
very very good idea Ricky :good:
[Android Stick & Console AMLogic based Computers] beta.0:
Good work my friend! Modifying partition sizes will come in handy.
[Android Stick & Console AMLogic based Computers] guppys@cogeco.ca:
Newbie

Can anyone please point me in the place to replace the crap launcher on a rom with a custom one i have? I have unpacked the rom level 1 and 2, i have found the file "medialauncher", that i want to replace.....next?

Thanks.

D
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Delete it and replace it with the launcher .apk you want
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Test version of 6.0.0 has proven quite powerful and with 0 bugs, the tool no longer depends on unpacking the kernel to get file_contexts on 8.x, the partition sizes are no longer guessed anymore but pulled from the DTB and the bug that doesnt save the DTB is in the process of being fixed, i may change a few things in terms of the editor
[Android Stick & Console AMLogic based Computers] y7htgd:
Download links do not work

Hi. Do you have any other links to your wonderful looking tools? Clicking on a link brings you back to the download page. Thanks in advance!
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
V6.0.0 is not up as of yet, you can download 5.5.0 from the downloads page otherwise wait a day or 2 for V6 with alot more fixes
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
V6.0.0 ETA is within 2 days! most is complete!
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Debugging has been really well, im expecting to release V6.0.0 within the next 12 hours.

Edit: Next 3 hours it should be available for download
[Android Stick & Console AMLogic based Computers] zusatzmetall:
I'm looking forward to your new version and what you've conjured up a nice new.
[Android Stick & Console AMLogic based Computers] N'ayam Amarsh'e:
Great work Ricky!
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Enjoy the release of v6.0.0 everyone!
[Android Stick & Console AMLogic based Computers] huffmybrd:
What's the difference between v6 free vs donate version?
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Donate version has vendor support, adblocking, partition table editing, and a standard unpack/repack utillity, not much at the moment but donators get pre-releases, more features will be dedicated to their version of the tool and they are notified via email when there is a new build available, i also offer the support i can
[Android Stick & Console AMLogic based Computers] lvbaal:
Hi Ricky,

While trying to install custom rom on my ATV box I think I may have bricked the device; because I could not get AMLogic_Burning_Tool to connect to the device because of drivers not being installed on my PC during installation of AMLogic_Burning_Tool (turned out it was required to have the device connected to the PC while installing the tool), I tried to flash the custom rom using SDCard in stead of USB.

Now the device does not boot anymore, neither to recovery, nor to system.

Then I retried the AMLogic_Burning_Tool (having the driver installed after all). But this does not succeed. I attach the log file from this here: https://mega.nz/#!urxAyKAL!mXtOisRN2BuuZBVnsNgCF7I1QCQpsemcFFlvvLXsn78

Do you suppose I could revive the box using one of your tools maybe?

Could you point me in the right direction?
[Android Stick & Console AMLogic based Computers] lvbaal:
Quick question about SD Burn Card Maker: I've selected an input image file 1,35GB in size. After pressing Create, the program starts reading the input file. So far, so good. However, after some time the program says ¨Not responding¨ in Task Manager, where status remains ¨Copying upgrade package¨. Also in file explorer I see the file being written to the SDCard growing and growing in size. At the moment it's 2,8GB. It has been running for about 15 minutes now.

Is this expected behaviour? Should I just wait for completion (or error)?
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
A video guide on making a custom firmware and some other goodies has been made :)

For making your own check out my youtube video, dont forget to subscribe for more content!

https://www.youtube.com/watch?v=FFqZsJLjYbg
[Android Stick & Console AMLogic based Computers] derwoodbones:
Still not working for me

I still cannot get it to work with 6.0.0, Trying to use on the Vorke Z6 Plus

Operating System: Android 7.1.2

CPU: Amlogic S912 Octa core ARM Cortex-A53 1.5Ghz

GPU: ARM Mali-T820MP3 GPU

RAM: 3GB DDR3

ROM: 32GB eMMC5.0

I am running Windows 10 Pro, Unpacking Level 3 and when you click on User Interface you get Fatal Exception
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Hey please submit logs through PM or email, as for this issue, you can click continue, it doesnt effect the use of the tool its a bug where the image for a UI picture box is not properly being disposed
[Android Stick & Console AMLogic based Computers] derwoodbones:
I apologize still waking up need more coffee, I removed the log from post and thx for the response, I will check and see if I can still make it work.
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
i will release an accomodating over the next few days, i will also have a launcher submission part soon aswell for people to submit launchers to add wallpaper support
[Android Stick & Console AMLogic based Computers] woodsy45:
v6.0.0 Donate - Working good

[MENTION=7352884]ricky_[/MENTION]Divjakovski you have worked wonders with this version of Customization Tool. Thank you very much for all the time and effort you have put into getting it working. :good:

I have made a quick and quite drastically changed version of the stock rom for my H96 MAX X2 and it recompiled to img without problem, flashed first time with Burning Tool and then installed OK.

As mentioned this was a quick test and main mods were removing most of Google apk's, changing launcher, removing the noisy bootanimation and adding power button and screen saver to system/app.

TWRP replaced stock recovery and Magisk Manager 7.0.0 was included in the preinstall folder which enabled downloading and patching with Magisk 18.1. All worked well.

Tomorrow I will explore the tool in depth and start to modify a stock rom properly:laugh:!

I'm over the moon with this:)

Cheers
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Happy you like it, few minor bugs but nothing that effects functionality, as mentioned earlier i will release an accommodating update then after that attempt to complete 9.0 support.

A lot has changed in 9.0, system partition is no longer just the system partition but more or less the root partition, the kernel and recovery doesn't have a ramdisk anymore and there is a new partition similar to vendor so expect V7.0.0 to be a little sloppy but not to worry, i went from being behind in supporting android versions to being ahead.

I already have some 9.0 binaries built and all that's left to build is e2fsdroid, then i'm able to finish 9.0 support.

In the meantime if anyone sees a 9.0 amlogic firmware please do notify me, i'm gonna need all the 9.0 firmware i can get to add proper compatibility!

Enjoy guys and thank you to everyone who has contributed to the project so far!
[Android Stick & Console AMLogic based Computers] Jerryjr200:
TWRP recovery to UB Burning tool

Thank you for the tools is there a way to tack a recovery that was created with twrp and make it usable in the usb burning tool

for A T95 S1

Thank you
[Android Stick & Console AMLogic based Computers] gabrielpc:
Hello and thanks to Ricky for his Amlogic tools.

I recently bought a JXD S18 mini tablet which has an Amlogic AML8726-M3 chip and with instructions from another site I managed to backup its recovery, (involving the command cat proc/mtd in order to find it) but when I try to port TWRP with the Amlogic Flash Tool, it goes up quickly to 40% but gets stuck there, so the porting never gets complete.
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
This is because my RecoveryConverterAPI library is broken, im in the process of fixing this aswell as the repack to .zip and compressed logo.bmp files in the .gz format, i have also been working on somewhat 9.0 support, however this may be a while before the tools are fully adaped to support 9.0(full treble)
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
you should be able to replace the recovery and then select advanced packing options and only pack the recovery :)
[Android Stick & Console AMLogic based Computers] spocky12:
Hi Ricky,

Thanks for your awesome work. I'm running into an issue with 6.0 : this update from Xiaomi MiProjA1 crashes the new CustomizationTool (it used to work fine on 5.5.0) upon opening (even only "unpack level 1").

Here are the log details:

DEBUG INFO -----------------------------------------------------------------------
Windows name: Microsoft Windows 10 Professionnel
x64 Architecture: True
PC Architecture: AMD64
Path of the program: C:\Users\spocky\Desktop\proj\tools\AMLogicTools_V6.0.0\
----------------------------------------------------------------------------------

[CUSTOMIZATION_TOOL] : Unpacking C:\Users\spocky\Desktop\rainman_1218.zip to level 1..
[CUSTOMIZATION_TOOL] : Rescursive delete "C:\Users\spocky\Desktop\proj\tools\AMLogicTools_V6.0.0\tmp"
[CUSTOMIZATION_TOOL] : LEVEL 1 ---------------------------------------
[CUSTOMIZATION_TOOL] : Splitting partitions from package..
[UNPACKER] : Unpacking upgrade zip
[SHELL] : sdat2img "tmp\level1\system.transfer.list" "tmp\level1\system.new.dat" "tmp\level1\system.img"

I can also confirm that recovery porting gets stuck to 40%, but you seem to be already aware of this issue.
[Android Stick & Console AMLogic based Computers] guppys@cogeco.ca:
image

Can I capture an image from the boxes i have? if not, how do ensure i have the right image before i burn the wrong one?

thx. D
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
trial and error, almost impossible to brick these devices
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Thanks for the report, Xiaomi firmwares seem to be encrypted, simg2img is unable to handle the encrypted stuff
[Android Stick & Console AMLogic based Computers] spocky12:
Did you change simg2img since 5.5.0 (it worked fine then : I didn't use it to repack a full firmware, but unpacking up to level 3 was definitely possible) ? Or is that linked to a feature you added in 6.0 ?
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
i did change simg2img with the version i built, your able to swap the simg2img binary from v5.5.0 to v6, let me know if it resolves the issue
[Android Stick & Console AMLogic based Computers] spocky12:
No, unfortunately, if I replace simg2img.exe with the old one, the problem persists.
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Can you link me to the firmware? i will look into this and have it fixed for you next release(in about 2 days)
[Android Stick & Console AMLogic based Computers] I1V1A1N:
Hi i did and launched android 9 using Project Treble phhusson.They run on my box X96 .Only a little slow down the system may be due to the fact that the size of the systems has become small .And so it runs and works.

https://github.com/s1a1g1e1r1t/AOSP_android_9.0_Amlogic_s905x/projects

https://github.com/s1a1g1e1r1t/Lineage_android_9.0_on_amlogic_s905x/projects

Good luck to you
[Android Stick & Console AMLogic based Computers] spocky12:
Thanks ! It was already linked in my bug report ;) Here it is.
[Android Stick & Console AMLogic based Computers] Jerryjr200:
Thank you Ricky i have given up on this thing if you would like to have it i would be happy to mail it to you I believe you have my email. I can always get i have 3 other boxes anyway.
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
As i suggested, its close to impossible to brick these boxes, short circuit is much more of a possibility
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Thank you for this
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Good news, i ported official respack V3 to cygwin and got a successful build, meaning full abillity to modify the bootlogo will be available next build
[Android Stick & Console AMLogic based Computers] Mashtetsov:
Hello, could anybody please advise - I have Nexbox A95X A2 device (S912) and the stock firmware (both android 6 & 7) do not contain amcodec, adding libamcodec.so to /system/etc/public.libraries.txt in android 7 do not help - amcodec appears in SPMC but no video (only sound), it seems that codec files or other are missing. Any suggestions how I can fix this maybe using customization tool? Thank you for your help.
[Android Stick & Console AMLogic based Computers] beta.0:
amcodec has not been used since S905X CPU and onward. You don't need it, pretty sure hardware decoding happens automatically.