yashsingh1/xdaforums huggingface dataset:
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Ive seen your replies, im busy with life in general at the moment and please dont forget, i dont get paid for this project, family comes first, in my spare time i will work on it, but honestly its a very odd issue considering im unable to replicate it or think of what could be causing this issue
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Also yes, its been tested on S905w, S905x and S912 android versions 5.x.x > 8.x.x, ive also had testers go through daunting processes to assure this tools is working

Like i said, if i was getting paid, very different story, this is why im planning on a donate version with theming features and poison optimizations and such..
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Because im strict with mirroring and people using the tools for companies, if they like my tools and can profit from them why should i not get a piece of the pie? ?
[Android Stick & Console AMLogic based Computers] laser212:
I had the same issue with the img form a TX3 pro a little while ago. the problem is the rom you are using i think. it was for me. ( it probably dosent have correct drivers) i had to settle with the TX3 Pro when i got the lan working. still no wifi.
[Android Stick & Console AMLogic based Computers] ErbDroid:
That's cool, now I'm off of Win7 but hopefully the 64 bit signing could be fixed eventually!???

Thanks man :highfive:
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Ill try my best to resolve all bugs
[Android Stick & Console AMLogic based Computers] ubihexor12345:
\

Thank you will be looking forward to it and yes you start the donation thing as well so you can profit from it
[Android Stick & Console AMLogic based Computers] Tonian1878:
i can understand that.

Source code not being updated and now this. does look like your going to lock features or the entire program behind a paywall.

not complaining about someone trying to make money, good luck to you but its not really an open source program like you first said.
[Android Stick & Console AMLogic based Computers] synthone:
[MENTION=5105831]Ricky Divjakovski[/MENTION] I do not blame you - it's ... just kidding ;)

I unbricked my x96 mini using instructions from here (see the photo of selected pins): https://blog.danman.eu/bricking-and-unbricking-vontar-x96-mini/

I still need a working solution to change boot logo and animation in original X96 mini software. Thanks!
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Features will never be locked, theres a reason for everything, sooner or later everyone will see, but for the time its just the way its gotta be.

Still gonna be a free program, but id like more information about the people using it, especially if a manufacturer is gonna be.

Ive also left little bytes of data throughout everything that is touched by my tool, i have no problem with someone using the tool for their own benefit, however if a company is to use my tools for commercial use and their benefit, i should atleast get some recognition.

This is also why i closed the source, i found my tool posted with the exact same code but branded under a different name with no credits or anything..

So this has forced me to close the source and create this new method

Nothings changing, no features will be locked, only think now is to activate the software to be able to use you will need to fill out a form, other than that everyone can still use it
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
If the logo is not displayed, rename bootup.bmp to bootup.gz and extract it
[Android Stick & Console AMLogic based Computers] ErbDroid:
It was open source until like v3, that will still be on GitHub, that 3/4s of this project open source that anyone could fork and try to build on.

I think this was a great move, it allows the people to take, modify, build there own WHILST all the newer features will remain original to Ricky's tools....until someone decides to build on the open source code and add the features or even more themselves if they choose.

This is free for us ALL! this is to stop what we all know would happen ....the official Amlogic tools having a update in the near future that is full of Ricky's features, they would be using Ricky's tool to flash the millions of units they sell per year, profiting on Ricky's hours and hours of work.

Just think all these years they (a multimillion $ company) wont have just "a guy" but a TEAM of people to make there tools and to maintain them, and look at what a **** job they have done!..... Ricky comes along with vision and perseverance.... within 6 months have done more than what they could ever achieve! even improving other closed source tool of theirs like the SD card maker etc, etc.

I honestly think that they are using Ricky's tools already, why wouldn't they be? theyre better! but at least they don't own them still!! if they do want them, which, they should! ....they should buy them! or give this guy the position of "Head of Amlogic Software Development" with a monthly sum in the bank! ...the fact that one random guy from Australia without access to their source code, owns a software package that out-performs the actual companies ten-fold!!!! should be embarrassing to them all! (WELL DONE RICKY!! :laugh:)

I actually really want them to buy these tools so Ricky can profit and put a lot more time back into making something else even better than they did! this is progression! lets be honest... ricky would never of had to make these tools if amlogic already had a decent set and this this project wouldn't exist! this project is their own doing!

Please be gratefull for even being allowed to use them for free this long, they will remain free, just protecting his creation from theft!
[Android Stick & Console AMLogic based Computers] ErbDroid:
[MENTION=5105831]Ricky Divjakovski[/MENTION]

..So I done a little digging around myself! And from what I can find is that aml_image_packer is 32 bit BUT the updater binary inside tools folder is 64 bit, hope this helps mate
[Android Stick & Console AMLogic based Computers] Tonian1878:
i cant criticize this. Thank you for the response
[Android Stick & Console AMLogic based Computers] synthone:
v.4.0

- repacking ok

- system is booting correctly, but no luck with changing boot logo (replacing bmp in level 3 - no result - still showing x96 logo)

v.5.5.0 -

- repacking ok

- device booting with replaced bmp logo in level 3, but always got stuck on it

- cannot unpack any IMG file previously re-packed using CustomizationTool (5.5.0) - stuck on status "Unpacking level2 (Unpacking system)" with high CPU load.

---

Finally, I found a perfect solution - Linux AMLogic Toolkit for Linux: https://github.com/natinusala/linux-amlogic-toolkit

It's working like a charm!
[Android Stick & Console AMLogic based Computers] deetucks:
how to get the box connected to this software if it cannot boot and i dont know the ip address?
[Android Stick & Console AMLogic based Computers] eugene2878:
Hi. Thank you for you great tool. It is very easy to replace Level 2 stuff and get it packed. But. What if I want directly replace boot, bootloader, recovery files in Level 1 folder? Do I need to unpack with level 1 option only?
[Android Stick & Console AMLogic based Computers] billkabb:
on my tx3 mini im triyng to repack ang flash the atvxperience firmware but after boot it is stuck to checking for updates ...
[Android Stick & Console AMLogic based Computers] gatos814:
Hello again

I have some time now to follow the thread and maybe i lost something....

I don't know if anyone have mention it before but it whould be nice if somehow we could add more wifi/bluetooth drivers in similiar firmwares , because time to time there are similiar firmwares better or newer than ours but are useless to use them because of the missing drivers!!!

This whoud be nice if we could do it from your tool with just a button (with a custom script) !!!

I do not know how much possible is this to be done, but i'm pretty sure it could solve a lot of problems !

Also for now , i have to say that i can not port any TWRP recovery with the newer version but only with 3.5.1 (tested only with Android 7 and with all of SoC) !

I don't know if you facing this when trying to port a TWRP recovery but i do!

Anyway , thank you for the good tool of yours!

Keep the good job here!

:good:
[Android Stick & Console AMLogic based Computers] amssmart:
Hello

When I repack my firmware I lost the Ethernet it’s wired any idea to resolve this issues thank you
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Yes this is pretty much one of the last issues left to solve apart from ethernet and zip repacking

As mentioned in the quote before this, this is one of the last issues with the tool, its pretty much perfect but once these 3 are solved i have successfully completed what i have intended to do
[Android Stick & Console AMLogic based Computers] gatos814:
So far you managed to go , at least 2 or 3 steps beyond Amlogic with your tool pack!

If you finally manage to solve one by one the critical issues and add some more extras (like the option of putting and other wifi/bluetooth drivers) will be , for me , one of the best MUST have ,Amlogic tool pack!
[Android Stick & Console AMLogic based Computers] servo386:
I have a fairly broad question that I can't find a straight forward answer to, so I'm asking here since you know amlogic chips inside out.

I've managed to secure a stock recovery which I then ported over to TWRP myself. So I have a TWRP for this device ready to go. What is the generally accepted way of getting this recovery on to the target device, one that does not have root or the custom recovery? As far as I know the list of ways is something like this:

1. Some (all?) amlogic devices let you essentially boot a recovery.img right off an sdcard, without having to flash it over the existing recovery.

2. Use fastboot to boot recovery.img without having to flash over existing recovery (I'm not even sure if fastboot is an option on amlogic devices...)

3. Create an update.zip thats compatible with the stock recovery that flashes only the modified recovery (is this even possible?)

4. Use this burning tool to flash the recovery partition

5. Making an amlogic sd burn card and somehow flashing only the recovery partition (again, don't even know if this is correct)

I don't even know how many of these are accurate, and in all cases, I don't know how to apply these to my device. For instance, in the case of bootloader/fastboot/burning tool, I don't know of any universal way to induce bootloader/fastboot mode on an unknown device. On every machine that its documented for, its already know before had what sequence of buttons/actions you have to do to get the proper bootloader state. On my device, I only know how to boot into recovery (which I understand is not the same thing as bootloader mode...)

Any tips would be very appreciated.
[Android Stick & Console AMLogic based Computers] sack9:
any luck with this? im having the same issue with one of my z69 boxes
[Android Stick & Console AMLogic based Computers] spocky12:
Guess we both have the same questions ;). My main concern would be to test a recovery without flashing it (bricking a 50€ Tv Box is a risk I could take, but for a 1500€ projector it's a bit different :p).

I'll add information and a few questions to yours :

1. I tried copying a recovery.img to a USB key. It didn't automatically boot from it, and holding the 2 remote keys to boot into recovery went into stock recovery indeed, not own my recovery.img.

2. In "Amlogic bootloader console", I saw there's a way to switch between amlogic and fastboot protocol. So fastboot might be supported. Question is, how do we enter it ? I'll try to reverse engineer bootloader to check if there's a way to go to that mode, but I'm not sure what I should search and whether I'll find anything relevant (my IDA skills are a bit rusted).

3. I suppose that's possible to create it. Question is : will the recovery accept to flash it ? In other words, what exactly can be flashed without triggering any "custom firmware" detection ? I suppose it's related to the META-INF folder, containing signatures. As a side note, I managed to put my hands on a stock userdebug recovery. Does the fact that it's built by Xiaomi (thus officially signed) allows more possibility in terms of flashing ? It's contained in a userdebug OTA. Would I be able to edit this OTA, just to remove all other partitions and keep only the recovery ? Once flashed, I suppose it should allow a bit freedom compared to stock recovery.

Thanks for the light any of you might shed on this.
[Android Stick & Console AMLogic based Computers] ggregor:
Android guy on his side with a "?" - On Z69 Plus

I recently bought a "Z 69 Plus" which is based on the Amlogic S912 3gb / 64gb - The button to put it into recovery mode is on the board but covered entire by the top which does snap off showing the button on the no IC side of the board. Holding it while powering up will give me the standard Recovery screen with a Android guy on his side with a question mark. The ADB.exe that I used successfully on a Nexus Player though opens briefly, scrolls quickly and then closes when launched using the USB connector to this device.

What I've found online advocates the USB male to male connector which in conjunction with your Tools software (2/26/18) allowed me to Flash TWRP and backup the device to a microSD card. This is for offline backup only, and I thought that since TWRP was now the Recovery software that the need for the USB connection and Tool was unnecessary.

Turns out that without your USB connection, that the wireless USB keyboard/mouse combo doesn't work, which of course makes TWRP useless. However, once the Tool is active, the mouse and keyboard comes alive.

So now that I have a safety net, I'm wondering what other ROM choices would be compatible with this device? - The stock build does work reasonably well but the wireless internet connection doesn't pass data anywhere close to "fast" typically speedtest is showing downloads at 3-4 mb/sec while a PC next to it pulls from a 2.4 ghz connection at 25 mb/sec through a VPN connection. Most streaming still works most of the time, but there is some stuttering and buffering on some feeds.

The Tool though as built does what you said on devices that you probably never heard of when you built it. It is ironic that I have to ID the device with an IP address when the connection is via USB.

I haven't found much fodder on the device that I have, but with the many different flavors of hardware available it seems like the wild wild west with incremental changes happening daily.
[Android Stick & Console AMLogic based Computers] Tonian1878:
Try the original Amlogic USB Burning Tool (Version 2.1.16 i think)

I've flashed that firmware onto A TX3 Mini before but only with the original USB burning tool.

Firmware works OK but the clock on the box itself didnt work. cant remember if the time was upside down or it just show "Boot" all the time
[Android Stick & Console AMLogic based Computers] thts:
There are patches for the Clock on the www.atvxperience.com/downloads/#link_tab-s905wtab

One for the Vorke Z5 and another for the Tanix TX3 Mini.
[Android Stick & Console AMLogic based Computers] ahkkhan:
Help me Plz Ricky"s

My 280 NEXBOOK NX007HD8G Dead

2 pic full working

AMLogic Devices how to dump & backup NX007HD8G full upgrade.img
[Android Stick & Console AMLogic based Computers] zitto739:
OTA zip file

Hello Ricky,

Thank you for the awesome software.

I repacked my firmware as .zip file. During installation, i get this error:

E:Failed to find META-INT/com/android/metadata in update package.

[IMG="Meta-inf failed"]https://ibb.co/mNKgXq[/IMG]
[Android Stick & Console AMLogic based Computers] fcoaaron89:
Great tool! but I have a question, how can I automate the extraction of logo.img and repacking it? I would like to write a BAT script but don't know what binaries should I call to... I tried with respack.exe and other tools from BIN folder without luck.
[Android Stick & Console AMLogic based Computers] asdfhnbethr:
Hi and many thanks for this great tool. I have an infamous "black pcb" h96+ with crappy gigabit. I read that a solution could be remove cali_val = <0x20000>; from dtb (ok it looks like I know what I'm talking about, but I'm not: just read something...). Now I removed this instruction: is it possible to repack this only and flash it only, without having to reinstall everything on my box? How? Many thanks again!! Alessandro
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Dd all the required blocks

Thats an issue i have not fixed yet, sorry about that

Theres no way of doing so, as i built the binaries from scratch respack.exe is useless without being run under my customization tool

Yes, manually select partitions to pack
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Also sorry i havent been very active, i have been getting drilled at work and also have custody issues with my son, hes in my care fulltime so im fighting time ag the moment
[Android Stick & Console AMLogic based Computers] algdu83:
My dream is have possibility to unpacking zip and remacking to img

but thanks for your big work
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
We are getting there.
[Android Stick & Console AMLogic based Computers] ErbDroid:
Good on you! Good luck and best wishes!!!
[Android Stick & Console AMLogic based Computers] Ricky Divjakovski:
Sorry for lag with the update guys, im currently very busy with a legal matter that must be taken quite seriously, ive had to take time off work to speak with solicitors and lawyers about this matter.

It should all be a little more clear by monday so ill be able to push for the next update quite soon.

Thanks for everyones patience
[Android Stick & Console AMLogic based Computers] algdu83:
hi

Can you make a rom stock from that zip for kII pro s905D please

https://mega.nz/#F!mJ9jxK4C!9Nrwyp95bi0FwGC_zYpWvA

Old rom

mediafire.com/file/ziumcjzvt26q7sb/KII_PRO_20171127.img

thnks
[Android Stick & Console AMLogic based Computers] Tonian1878:
No need to apologise. Family comes first.
[Android Stick & Console AMLogic based Computers] JG420:
x96 mini, 1gb/8gb...can the Amlogic Flash Tool be used to flash twrp? my box did not come pre rooted :(
[Android Stick & Console AMLogic based Computers] bistala:
hello bro, great work with this toolbox, but I have a problem, every time I modify a firmware with your tools at the time of starting the tv box does not pass the screen "looking for updates", I tried skipping the connection part to internet and it freezes, what am I doing wrong? I hope you can answer me

Edit: i have a m8s pro w with amlogic s905w , if I flash the firmware that I have from the box I have no problems, but when I modify it with your tools (I remove unnecessary applications from system / preinstall) and create a new firmware, flash with usb burning tool, start well but stick where comment above
[Android Stick & Console AMLogic based Computers] mick154:
Same problem here so I went back to version 4 and that is working correctly
[Android Stick & Console AMLogic based Computers] ssdist1:
major issues

Hi guys

I have used the latest version 5.5.0 and successfully unpacked img, made modifications, then repacked it to a new img > however, the following has occurred:

1) When modifying an Android 6.0.1 img, it successfully unpacked the img, i made the modifications (simple things like preinstall apps, launcher, build.prop) - the tool successfully creates the new img - however, there is an error when trying to flash the new img using the USB Burning tool. The img also appears rather large (few hundred MB bigger than before).

2) I then read the comments on freaktab that version 5 is not working properly, and all users are having issues with it. People are saying that version 4 is working perfectly.

So ive gone ahead and tried version 4. Version 4 unpacks the img successfully, then i made the changes to the firmware > and packed it to a new img.

The new img flashes successfully and boots up fine > everything works > HOWEVER, none of my changes are present. Bootanimation, apps, launcher, device name > nothing has changed .

After several hours of trying, i realized that the img it creates, is exactly the same size no matter what changes i make (it just gives me the original firmware back, without the modifications i have made).

I then went ahead and tried to create a 'flashable zip' rather than an IMG file, here, i found the problem.

I get the following error messages: "failed to repack kernel, packing will continue without kernel" , "failed to repack the recovery, packing will continue without the recovery".

For some reason, version 4 is unable to repack the img. Even without making any changes > it just gives you the original img.

Here is the firmware i am trying to modify (MEGA Link):

*sorry, as i am a new user i cant post links ; just add MEGA dot NZ /

#!1Oo0mRgD!DjMXeQj8yz4M_moB8EOTSLZW2wpcjMvsrHWPbRhaghk

Any assistance would be greatly appreciated
[Android Stick & Console AMLogic based Computers] thts:
Version 4 does not work with Android 6.0, It never thinks anything changes so it never tries to repack the system at all.

For Android 6.0 try the original Amogic Customization Tool, It had problem with Androd 7+ but 6.0seems to work okay, If that don't work then the only other way I know of is to use the Linux Tools to Modify and repack the .img file

Hope this Helps
[Android Stick & Console AMLogic based Computers] ssdist1:
Thanks for the tips

Unfortunately the original customization tool provides me with an IMG that is half the size of the original (approx 400mb), even without making any changes (just unpacking, then repacking).

Can you help point me in the direction of the Linux Tools you are referring too ? Are these the tools that most AML devs use ?

I use to use the original Customization Tool which works perfectly up until Android 5.1.1 (in my experience) - it seems other devs must be using something else

Cheers
[Android Stick & Console AMLogic based Computers] thts:
I figured out the issue with the U1_Marshmallow_CFW002 img file, After converting the system.PARTITITON file to system.ext4 and running e2fsck -f system.ext4 it was full of errors all files in /system/xbin are cross linked or something Fixed those problems and remade the system.PARTITION file it is now proper and should work with the Amlogic Customization Tool.

See if this one works and please let me know if it doesn't so I can remove it from mega, Thanks

https://mega.nz/#!dzB0XAjJ!k0BgGemAYfWdmgzJAY60_8fAnvb7HgEJXuSM-aA6FRI

Or

For Linux see Below

https://docs.khadas.com/vim1/UpgradeViaUSBCable.html

https://github.com/khadas/utils
[Android Stick & Console AMLogic based Computers] ssdist1:
Thanks heaps for trying to help, it is greatly appreciated. I am not very experienced with Linux so getting it to work with customization tool would be ideal! But if Linux is a must, then i can try..

Unfortunately when i unpack your modified IMG with the original customization tool, inside tmp/level2/ > i am getting a 'system' file (rather than a system folder). And the file is only 1.66mb.

apk, kernel, logo_res, recovery folders are all present inside tmp/level2/. Just the system is missing its folder, and showing as a file instead.

Any clues ?

Cheers
[Android Stick & Console AMLogic based Computers] derwoodbones:
TX5 Pro

Is there currently a working version of this tool for the TX5 Pro box that will successfully unpack, save changes and repack to .img without the loss of Ethernet ?
[Android Stick & Console AMLogic based Computers] kiskaprince:
any new updates?
[Android Stick & Console AMLogic based Computers] thts:
I assume that this is Version 6 of Android?

At the moment the only way to make changes is to use the Linux Tools.
[Android Stick & Console AMLogic based Computers] shinobisoft:
You'll know when an update is posted. I suggest reading comments from the OP within the last few pages of this thread. Asking for ETA's or if/when there's going to be an update is against forum rules.