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.
py-starbound - Python package for working with Starbound files.
A tiny hack to read white-on-black on Kobo ebook readers.
Usage
There are three ways to contol nightmode:
- Long-press the LIGHT / HOME button on your device to toggle
- Write into the /tmp/invertScreen fifo-interface
- Send y to set nightmode to ON
- Send n to set nightmode to OFF
- Send t to toggle
- define action 'toggleNightMode' on a (configurable) level of brightness and set and maintain that brightness level through Kobo UI for a (configurable) number of seconds
Comment mettre en place un environnement de développement pour Kobo ?
un lanceur de script via ouverture d'image dans Nickel ;)
Hey everyone can some one help me locate the right firmware for this box please.. some one told me its a generic box but i dont have a single clue locating the
I fixed this issue for several of my colleagues by running the following two commands:
git config --global url."https://github.com/".insteadOf git@github.com:
git config --global url."https://".insteadOf git://
One thing we noticed is that the .gitconfig used is not always the one expected so if you are on a machine that modified the home path to a shared drive, you need to ensure that your .gitconfig is the same on both your shared drive and in c:\users[your user]\
Tu te demandes sans doute ce qui est arrivé avant que tu débarques ici. Eh bien des tas de trucs, à dire vrai. On a évolué, on est devenu des êtres humains, et c’est là que les choses se sont gâtées...
Via Shaarli
You can move the entire C:\Users folder to a different drive pretty easily after windows is installed:
-
Boot to the installation media, and get to the command prompt (I believe you need to click repair first)
-
Use Robocopy to copy C:\Users to D:\Users: robocopy c:\Users d:\Users /mir /xj /copyall
...:. a. /mir tells robocopy to mirror the directories, this will copy all files and permissions
...:. b. /xj is very important, this tells robocopy not to follow junction points. If you forget this, you will have a lot of trouble.
...:. c. /copyall will copy all the attributes includings ACL and Owner info
-
Verify that the files successfully copied
-
Delete c:\Users
-
Create junction that points to d:\Users: mklink c:\Users d:\Users /j
That's it. I've been using this process since Vista went RTM with no problems.
About
fusée framboise is a custom bare-bones Raspbian image that has a systemd Unit that loops modshipd.sh of fusee-launcher.
How-to
Ingredients
A Raspberry Pi Zero (any RPi works, but the Zero tends to run off of any power bank)
A power bank (for powering the RPi)
A non-powered USB hub (why?)
A USB-A to C cable (don't get a no-brand one: it may not have a needed resistor, and it may wreck your Switch or your USB source)
A USB-A to Micro cable (for RPi power)
A USB Micro to USB-A Female cable (only for the RPi Zero: for plugging in the USB hub)SD Setup
Download a fusee-framboise image.
Flash it to your RPi's SD card. (If you don't have a flasher software installed, I recommend Etcher.)Cables!
Plug the USB Micro to USB-A Female cable into the RPi. (only for RPi Zero)
Plug in the USB hub into the USB-A Female cable.
Plug in the USB-A to C cable into the USB hub.
Plug in the USB-A to Micro cable into the USB hub, and into the RPi.Usage
You should just be able to plug in your Switch, put it into RCM, and the payload should automatically launch.
Replacing the payload
To replace the payload, you have two methods: (both need sudo)
Replace fusee.bin in /etc/fusee-launcher/ with another payload. (recommended)
Copy another payload into /etc/fusee-launcher/, change modchipd.sh to point to it, and restart the fusee-launcher service, or reboot.Networking
You can change the payload over the air. Here's how to do it: (your RPi needs wireless, and you'll need a mobile/normal hotspot to do this)
Set a root password with "sudo passwd", and take note of it.
Change your default pi user's password from "raspberry". (optional, recommended)
Turn on SSH: it's in Interfacing Options of raspi-confiig.
Configure your Pi to connect to your phone's network.
Reboot to connect to it, run ifconfig, and take note of the settings.
Set a static IP based on your ifconfig data.
Take note of your static IP. (you should probably take note of it on your phone)
Use an app that supports SFTP to connect to your RPi with the new root password. (iOS)