Amlogic Image Burning Tool v.1.6.2.2 (Released 2013-05-15) Attached File _USB-Burning-Tool.zip 6.91MB 9001 downloads. Modes description: - none - recommended mode; do not erase nand (user data will be safe); flash new firmware - erase old system, reset and re-burn - recommended mode; erase. Nov 10, 2011 in recovery, try the option 'install zip from SD card' and then navigate to that zip file, select it, let it install, reboot. 'install zip from SD card' is.

You can use Amlogic USB Burning Tool to flash firmwares from a Windows PC to Android devices powered by Amlogic processors. Download Amlogic USB Burning Tool v2.0.7.2 from,. Download Amlogic USB Burning Tool v2.0.5.15 from. Download previous version from. How to use Amlogic USB Burning Tool 1. Download Amlogic USB Burning Tool v2.0.7.2 (9.57 MB). Extract the archive and run setup_v2.0.4.3.exe file to install the tool.

Start the USB_Burning_Tool. Click on File->Import image and select your specific.img firmware for your Amlogic device. Make sure that your Amlogic device is powered off, with the USB OTG port connected to your PC. Use a toothpick to press the recovery button, and power the device.

The USB burning tool should automatically detect your device. Now click on the ‘Start’ button button to proceed with the firmware update which should last several minutes. Follow for more help. Did this article help you? If so, please tell me in a comment what do you think about it. Don’t miss any of our future video tutorials, follow us on. Add us in your circles on.

Watch our photo albums on Subscribe now to our.

So I've recently rooted my phone and tried a ROM or two. I find it really handy that you can use TWRP recovery to install another ROM from the SD card, you don't need to have it connected to a PC. However, on my device (HTC One S) I need to flash a different boot.img file for every ROM as well, so I still need to hook my phone up to my PC to switch ROMs. If I don't do this, it just gets stuck on the loading screen. Then I must use the command fastboot flash boot boot.img from the folder where boot.img is located. Is it possible to flash this boot image with TWRP or any other way without using fastboot over USB? What needs to be done is to bundle the boot.img and construct a new zip file suitable for flashing via ClockworkMod or TWRP.

Pre-requisites: • a Linux environment that has the usual development packages, such as Java installed. ( It can also apply to other platforms, just be careful that the instructions here indicating the path used below, uses a forward slash /, so flip that around to be a back slash for Windows environment especially!) • adb command line tool installed. • `testsign.jar', for signing the zip file so that the recovery can authenticate and verify it is a valid archive otherwise recovery will report corrupt archive or similar.

• update-binary command line, that is internal for usage with the flashable script. (This can be found with any flashable zip, the important thing is to extract that binary and deposited in the structure of the directory as shown) • zip command line tool. Assuming your directory is called workdir, for discussion, lets call this the working directory, copy the boot.img into that directory, and create the following directory structure - META-INF/com/google/android, this is important! And within the META-INF/com/google/android, copy the binary application called update-binary into that directory. So the directory structure should be like this: + workdir/ + +--+ boot.img +--+ META-INF/ + +--+ com/ + +--+ google/ + +--+ android/ + +-->update-binary +-->updater-script As for the updater-script, copy the contents of the following below: ui_print('Please wait, boot.img being flashed.' ); show_progress(0.1, 0); assert(package_extract_file('boot.img', '/tmp/boot.img'), write_raw_image('/tmp/boot.img', 'boot'), delete('/tmp/boot.img')); show_progress(0.1, 10); ui_print('It is now safe to reboot!:)'); Remember: Do not get confused here, the updater-script as shown, should be left alone and as-is, so do not try flip the forward-slash to a back slash if doing this under Windows environment. Go back to the parent of the directory structure, i. Ftp 1 Pscp Executive Branch. e.

Outside of workdir and do the following, we're going to create a zip file from this: zip -r my_custom_flashable_boot_unsigned.zip workdir/ which is a recursive function, this will zip up everything into the file called my_custom_flashable_boot_unsigned.zip. Finally, to sign the zip file, issue this: java -classpath testsign.jar testsign my_custom_flashable_boot_unsigned.zip my_custom_flashable_boot_signed.zip Then its a matter of pushing that across the SDCard as in adb push my_custom_flashable_boot_signed.zip /sdcard/ and manually go into recovery and specify that zip archive (i.e. My_custom_flashable_boot_signed.zip) in which it will perform the flashing for you.

I about two weeks ago, and with the firmware I had, online firmware update was not enabled, and the company only released.IMG firmware for, a windows only tools that’s not well designed, and requires some procedure that vary slightly from boxes to boxes which in some cases forces to buy a male to male USB cable. I’ve now started also based on Amlogic S912 processor, online firmware update is not working either, and again I only managed to find for the box on GeekBuying. However, I’ve been informed that “USB Burning Tool” firmware can now be flashed through a micro SD card, or USB flash drive with all recent Amlogic TV boxes, so I’ve tried this method instead of R-Box Pro, and decided to report my experience in this post made by user Calc. I’ll show instructions in Linux (which could be further streamlined), and then Windows. Linux Method After downloading and extracting the rar’ed firmware file (twice), I ended up with a single img firmware files (aml_s912_q6330-R-BOX-PRO-3gddr-mac-20161015.img). First we’ll need to have a tool to extract some files from the firmware. Create aml-upgrade-package-extract.c with the code below which and slightly modified it to parse the firmware filename.

Lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 931.5G 0 disk ├─sda1 8:1 0 915.9G 0 part /media/hdd └─sda2 8:2 0 15.6G 0 part sdb 8:16 0 111.8G 0 disk └─sdb1 8:17 0 111.8G 0 part / sdc 8:32 0 931.5G 0 disk └─sdc1 8:33 0 931.5G 0 part /media/jaufranc/SEAGATE EXTENSION sdd 8:48 1 3.8G 0 disk └─sdd1 8:49 1 3.8G 0 part /media/jaufranc/6106-E11B sr0 11:0 1 630M 0 rom /media/jaufranc/CanonEOS285W loop0 7:0 0 75M 0 loop /snap/ubuntu-core/423 loop1 7:1 0 4.3M 0 loop /snap/canonical-livepatch/17 loop2 7:2 0 4.3M 0 loop /snap/canonical-livepatch/15. Sudo umount / dev / sdX * Now make sure no other USB devices or SD card are inserted in the TV box, and insert your bootable (micro) SD card or USB flash drive into the TV box. If your TV box is fully bricked, you have nothing to do, and the update should start straightaway, but if it is partially bricked or just working fine, you still need to press the recovery button, apply power, and release the button in order to enter recovery mode. The upgrade should then start automatically as shown below.

Patiently wait for the update to complete and you should be all good. Please note that I first tried with a USB flash drive, and the method did not work. Once the update is complete, you’ll see the “Android success” logo. At this point, remove the micro SD card, and power cycle the board to complete the final steps of the update, and within one or two minutes you should get the Android launcher. If instead the firmware ends with “Android failure” logo showing a red cross, verify your firmware MD5 (e.g.

With md5sum in Linux) to make sure it’s not corrupted. If it is, re-download the file and/or re-copy the file to the micro SD card. Windows Method If you are a Windows user it’s much easier as you just need to use Burn_Card_Marker tool (bootcardmaker.exe), which you can download. The documentation shows the interface as shown below.

But after starting the program in Windows 7, and changing language with the top menu, second option to English, it stayed in Chinese language and looked like the screenshot below instead. [ Update: After changing the Language to English, select the third option in the top menu to apply the change restart the app, and it will be in English.] It’s not really a big issue, but you can still select your SD card device (F: drive in my case), load the file, and press “Make” button to start create a bootable recovery (micro) SD card. You’ll get a “Success!” pop-up window and the end, and the content of the SD card will show the firmware, and the two aml_sdc_burn files.

Now you can insert the micro SD card in the TV box, enter recovery menu with the pin hole or other method for your TV box, and firmware update will start automatically. I too cannot make the SD Upgrade work I spent 4 hours last night using the tools and step described above. I insert the 4gb SD card and press the reset button – I get a green android with red cross only. If I remove the SD and go to recovery, I navigate to the SD card but the.IMG file is not visible at all I am assuming because it is looking for a.ZIP file instead Life would be ALOT EASIER if they simply provided the.ZIP version instead (right)??? There would be no need for SD burn tools. I am trying to re-download the IMG file again and go through the steps again. I have no idea why!

Can someone provide feedback? Hello, I have a question about my boxes for anyone that might be able to help. I have purchase 4 separate Mini M8S II S905X boxes that have identical pre-installed setups. They came with Kodi 16 installed and I updated ONE of them to Kodi 17. After this ALL of the installed content associated with Kodi was gone. Being a newbie to these type boxes but a veteran of computer world, I spent weeks of “finding” the required installation procedures and files out of all the “crap” all over the internet, then installing all the accessories, a new skin, figuring out customizing new skin, testing all the apps (which Kodi has now shut off access to some in version17), and setting the cache correctly with ares wizard. Now finally down to the question: Is it somehow possible to download my entire systems settings, programs AND zip files COMPLETELY from this machine to a SD card and then install ALL that info including settings on these 3 other identical machines?

Or use a USB to USB cable and somehow copy the system from the one to the other? If so ANY instructions or links would be GREATLY appreciated! This would undoubtedly save me a week of setup on each machine. I did a backup of this machine on a USB stick. Using the system backup AND then the Kodi backup. Then inserted the USB into the other machine.

It wouldn’t find the backup file. I then installed Kodi 17 on the second machine and tried again. I also tried backup with ares wizard and still the second machine would not use the backup. Yes, However I lose ALL my custom skin settings, favorites list, optional programs, ect., PLUS the last 4 weeks of work just to start all over again, no thanks I’m looking to copy my entire ROM to SD and then copy that to the 3 other identical machines. So far I’ve tried: 1. ROM Manager, (which was GREAT at fixing permissions to everything and I’m pretty sure it accomplished rooting.

It has the option of Installing ROM from SD card, but NOT to save current ROM to SD card.) I also don’t really understand how to use it which may be my problem on this one. TWRP Manager (which states upon startup that the program is NO LONGER able to choose SD for backup and MUST use the ROM drive which makes NO sense. 4.7 GB of info backing up to an 8 GB ROM with 4.7 GB already there. Not sure how that would even work.

Superuser which seems to just want you to upgrade to PRO to even use it so is USELESS to me. Thanks for this input, but I am not trying to ONLY back-up just the Kodi program. I purchased 4 identical Amlogic S905X boxes. After 4 weeks of customizing 1 of them, I now want to “copy” the ENTIRE BOXE’S ROM from this 1 machine to the other 3 directly, with USB, OR with SD. Kodi PLUS ALL the other base programs other than Kodi that come on before Kodi.

I see many ways of downloading other peoples AND update.img files for this machine. I am trying to find out if there is any program or hardware which will copy this particular box’s ENTIRE SYSTEM. Then put it on the other boxes.

It seems that this (should) be possible. After all the producer made 1 and then copied that system to thousands after it. Would this technology make it out to the public or is it just done by the manufacturer ONLY? Thanks again! The MBOX’s main backup won’t load into another machine either. Sorry I misunderstood. Normally companies develop the firmware using an SDK, commit changes to a version control repository, and then build the firmware image from that SDK before flashing it to the board.

They don’t flash the image to a board, then make some modifications there, and read it back. There might be a way, but I just don’t know it. You could use dd to backup the complete eMMC flash, and then dump it on another device. This could word, but this could also brick your target device.

The guys at freaktab are very good at this, but I think they do the changes inside the firmware image, instead of the doing it on the box. You could ask on their forums if you have not done so already. Just have to say how pleased I am to see some source code. I received a H96 Pro+ a couple of days ago and decided to upgrade the firmware shortly after getting the box up and running. In exploring the procedure for performing the upgrade, I was shocked at how many folk are willing to download an executable from some file-sharing site and run it on their workstation. That’s putting a lot of trust in several parties. My workstation is just too important to me for that kind of recklessness.

But your snippet of C source is perfectly readable. I don’t have to trust it, because I can understand exactly what it is doing. Thanks for sharing it. I’ll sleep more soundly tonight. Hello, I do it for my bricked MINI M8S PRO 2G/32G s912 but burning failed I change erase_flash on aml_sdc_burn.ini file to “1” but after few houres a screen is blocked with message “upgrading” I also tried with USB BURNING TOOL but i have this error after few seconds: [23:22:06 454][HUB3-2][Inf]————-ERASE FLASH———– [23:22:06 454][HUB3-2][Inf]–disk_initial 1 [23:22:06 454][HUB3-2][Inf]–Send command success [23:22:07 641][HUB3-2][Err]–failed:[23:22:07 641][HUB3-2][Err]–Check command return failed Any idea?

Regards [23:22:07 673][HUB3-2][Err]–[0x30201004]UBOOT/Disk initialize/Send command/Error result. Hi, First of all; thank you for sharing this information! I tried creating a bootable sdcard (8GB microsd) using the instructions below. But for some reason the card becomes unreadable/unmountable with these parameters. Sudo umount /dev/sdd1 sudo dd if=aml_sdc_burn.UBOOT of=/dev/sdd bs=1 count=442 sudo dd if=aml_sdc_burn.UBOOT of=/dev/sdd seek=1 skip=1 bs=512 sync Not sure what I am doing wrong. I checked the dd manual and information on this website: but that did not make clear for me how I should change the command to work with my particular card. Could someone please guide me in the right direction?

I have no access to a windows machine; was thinking about running the bootcardmaker.exe tool in Wine or another VM but the link to the file on Mediafire seems to be expired. Any help would be much appreciated.