Allows to unpack and repack AMLogic images for Android 7 without the Customization Tool - natinusala/linux-amlogic-toolkit
So, AMlogic have a horrible way of dropping support for their tools. Decided to make a few of my own. More stable, more efficient and (no longer opensourc…
In the spirit of the Pure Nexus Project, these custom ROMs prove that less can be more. The goal is to keep true to Google's vision and use the bare minimum of OEM or third-party apps or add-ons, which can be added à la carte by the user as needed. The Nano variant also serves as the foundation for the TVStock ROMs, which deliver the pure Android TV experience using the Open GApps TVStock Package.
TVStock variant includes:
Open GApps TVStock Package
All contents of the Nano Nexus variantNano Nexus variant includes:
Open GApps Nano Package
Google Now Launcher (replaces Lighthome Launcher)
Google Chrome Browser (replaces AOSP Browser)
Google Legacy Camera (replaces AOSP Camera)
Google Desk Clock (replaces AOSP Desk Clock)
Google WebView (replaces AOSP WebView)
File Manager v3.0.0 and Sound Recorder v6.0.1 from CyanogenMod/LineageOS
Terminal Emulator for Android v1.0.70 by Jack Palevich
TWRP Recovery 3.1.1-0 from TeamWinI also had a bricked H96 Pro Plus (3gb RAM / 16Gb flash), after trying to unroot the device with SuperSU.
I spent many, many hours reading many, many threads and i eventually found the solution. So a big THANKYOU to everyone who has posted problems and solutions. Without your help my H96 Plus + would still be bricked.
Initially, my box wail fail at the H96 Pro logo, but for some reason wouldn't even output to HDMI, with only a feint blue LED.
This is what I learnt.....
-
no HDMI output doesn't mean it is totally bricked
-
it took me a while to work out that only 1 usb socket on the box works (closest to the SD card)
-
usb burning tool 2.0.8 worked fine
-
laptop must use usb 2.0 (usb 3.0 does NOT work!)
-
there is NO NEED to connect the box to a power supply. The eMCC h96 flash can be powered and accessed from the laptop usb 2.0 alone
-
the laptop usb 2.0 will sometimes reduce power output if it doesn't see activity for a few minutes (so try unplugging/replugging if failure)
-
the connection between h96 and laptop can be started 3 ways and is not fussy
option 1. click start on the laptop with usb already connected
option 2. connect the usb with the flash process already started
option 3. use a paperclip to reset the box with the usb already connected and flash process started -
all the above methods will cause the flash process to restart
-
it is VERY important to try lots of dfferent ROM's!!
-
sometime a ROM will stop a 2% every time
-
some ROMs will appear to stop at any random point (2%, 10% 90% etc.) each time it is run. I thought this was a problem with power, or usb cable, but it was just the WRONG ROM!
-
the "aml_7.1_s912_q9377-H96PROPLUS_mac-20170422" rom didn't work for me, and crashed out at random %
-
after about 10 ROMS , "aml_7.1_s912_q9377-H96PROPLUS_LP_KDMC_mac-20171010" worked with success!!
My method;
- start laptop and load USB Burning tool 2.0.8
- open ROM 20171010 above (MAC licence issue already fixed)
- click start
- connect box to laptop with correct usb sockets
- flash process auto starts
- success!! - unplug usb
- click stop
- connect h96 to tv and power on - first boot took about 5 minutes
Image works with SD cards and USB drives.
Regular firmware in the device is NOT CHANGED.
When you replace the dtb file can be run on any device with Amlogic chip S905 s905x s912
When you first start the system, the root user password is 1234
The minimum media size - 4 GB
https://yadi.sk/d/pHxaRAs-tZiei
Option how to start (Activation multi-boot).
** Manual run Systems **
Now all images Armbian and LE has all the files for activate the multi-boot. Anything in addition to download and copy to media is not required.
- Download the image for your device
- Unpack
- Burn the image on the medium
- boot into Android
- open the app "Update&Backup"
- click on "Select" local update and chose the file on the removable media (aml_update.zip) aml_autoscript.zip
- start "Update"
- System will reboot twice and start running the system from external media.
- If after 7-10 minutes on the monitor not to receive any messages on system startup. Turn off TV box and manual copy into the first partition BOOT (FAT) the file "dtb.img". On the media there is a directory "dtb" from where you can take the file and copy it to the root of /boot rename it to "dtb.img".
Need to pick up the option for the file system will run. Pay attention, after you add\change the dtb file, you need to try to run the system and waiting to run 7-10 minutes. If not happened, repeat with a different dtb file.
Attention !!!! On models with S802 S805 S812. Activation multi-boot is possible ONLY with SD card (activation of the USB stick is NOT WORKING). After a one-time activation procedure is multi-boot, run a variety of systems is possible from ANY storage media (SD cards and USB storage devices).
The choice of shell to start (Mate\XFCE or KODI).
On the screen enter username and password (in lightdm) in the upper right corner of the screen there is a menu where you choose which GUI to run. The list will be three items (two rows with kodi) and the last line mate. Select mate (something opposite mate was the point), then enter the username and password. The system remembers the last selected mode. If at the next login or what not to choose in this menu, system at the entrance will trigger the option that was turning off in the previous session.
Install to eMMC (NAND)
Kernel 4.16 does not support internal eMMC memory. Do not attempt to install to the eMMC. You get problems.
To install Armbian in the internal memory, you must execute multiple commands. We strongly recommend TO PreRUN create a full backup of the entire contents of the internal memory. This will allow you to return to the current state of the firmware at any time. To create a complete backup you need to execute commands.su -
(enter passwd root)
ddbr
The running tip backup script
After creating the backup, to install to internal memory (eMMC) of the command being executed
Pay attention, if you not are sure that you will be able to solve possible problems from the installation of the internal memory (eMMC), do NOT PERFORM these commands.
su -
(enter passwd root)
./install.sh
or
nand_sata_install
Setup HDMI out.
The configure script video output hdmi.sh reside in a directory on a FAT partition (on a running system, this partition is automatically mounted to the /boot directory). This script can be changed. To change the screen resolution from 720p to 1080p, you need to uncomment the line "#mode=1080p60hz" and comment out the line "mode=720p60hz". Similarly, you can change the color depth from the default 24 to 32 (bpp=24). Note that with 32 bit color significantly changes the desktop. In this script you can place the commands you want to run WebMin , Doker, ask line to run the USB port (if necessary), configure, sound card, etc.
On Wifi.
run as root user one of these commands in the terminal
An example command to load module “dhd” or “wifi_dummy” or "ssv6051" or "wlan" etc.
modprobe dhd
or
modprobe wifi_dummy
or
modprobe ssv6051
or for QCA9377
modprobe wlan
After verification of the selected module, if everything is working correctly, you can add it to the autorun list (add string name of the module in the file /etc/modules).
Remote control.
How to add support for remote control. To use it you need to add the correct file “remote.conf” in the /boot directory or /etc/amremote. By default, some of the images already include several predefined files (in the /boot directory). To use it you need to rename one of the files in “remote.conf”. Additionally I have uploaded the deb package “amremote.deb”, which can be installed in your current system (do not download the complete image).
Before installing, delete all remote.conf files: rm /boot/remote.conf.* Now you can install the package: sudo dpkg -i aml-amremote....
After installing this package you need to run in a terminal “service amlogic-remotecfg status” and add (rename) the correct file 'remote.conf".
Auto login
Add line to /etc/lightdm/lightdm.conf.d/11-armbian.conf
[SeatDefaults]
autologin-user=username
autologin-user-timeout=delay
Additional information
http://forum.khadas.com/t/armbian-kodi-ubuntu-debian-for-sd-usb-emmc/825
Wiki
Information to enable multi-boot on the WiKi is outdated, use to activate the multi-boot description from this post in the beginning.
https://github.com/150balbes/Amlogic_s905/wiki
Other versions of images with different Linux systems.
if mmcinfo
then
if fatexist mmc 0:1 u-boot.bin
then fatload mmc 0:1 82000000 u-boot.bin
echo @@@@@@@@@@@@@@@@@@@@@@@@ erase spiflash : need about one minute @@@@@@@@@@@@@@@@@@@@@@
sf probe 2
sf erase 0 600000
sf write 82000000 0 60000
echo @@@@@@@@@@@@@@@@@@@@@@@@ erase nandflash @@@@@@@@@@@@@@@@@@@@@@
nand erase 0
reset
fi
fi
It might be very rare (actually it happened to me only once, few months ago, while doing "dev work" and I had no RS232 cable, I locked myself out because of a bad rom flashing) but if your device seems dead and refuses to boot to recovery using the bottom located pinhole as trigger to enter recovery (see CWM or TWRP threads for more infos about entering recovery) don't be afraid because, unless you suffer of an hardware failure, you will be able to unbrick it using this MicroSD rescue method.
mmcinfo
fatload mmc 0 0x82000000 u-boot.bin
sf probe 2
sf erase 0 60000
sf write 0x82000000 0 60000
sf erase 0x100000 0x8000
reset
In the spirit of the Pure Nexus Project, these TVStock Nexus ROMs deliver the pure Android TV experience using the Open GApps TVStock Package (https://github.com/ope
In the spirit of the Pure Nexus Project, these TVStock Nexus ROMs deliver the pure Android TV experience using the Open GApps TVStock Package (https://github.com/ope
Android TV Box, something went wrong and I bricked it somehow. It dind't boot up anymore, I could enter the recovery menu from micro SD card with stock firmware on it, but it was impossible to flash the firmware, I got always the same errors, something like:
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_log.txt
The easiest way to solve this, without need of short circuit of the NAND pins, is to use Amlogic BootcardMaker to make a bootable micro SD card with your device stock firmware, in my case I needed Vigica C90T 20150211 FW.
So download Amlogic BootcardMaker, download your device stock firmware, launch the application with administrator rights, select your micro SD card as removable disk to be used, tick 'To partition and Format', then Click 'Open' and choose u-boot.bin from your device stock firmware package. Now press 'Make' button and when it's done just copy all the firmware files to micro SD card (aml_autoscript, factory_update_param.aml, firmware.zip, recovery.img, u-boot.bin, unlock_autoscript).
Now insert the micro SD card in your Amlogic device and power on. You will be able to enter into recovery and the firmware will be flashed automatically. When the TV BOX reboots, remove the micro SD Card, this step is very important, wait 4-5 minutes and the update will completed. Next, follow the regular procedure and flash back to your stock firmware if this was from another Amlogic device, everything should be back to normal now.