跨平台 Spotify 汽车工具包 (superbird)
This toolkit re-implements most of the functionality from frederic's scripts.
The key difference here, is that this tool uses pyamlboot instead of the proprietary update binary from Amlogic,
which allows it to work on many more platforms!
Everything in images/ came directly from frederic's repo.
The purpose of this tool is to provide useful, working examples for how to use pyamlboot to perform development-related tasks on the Spotify Car Thing.
Contributions are welcome. This code is unlicensed: you can do whatever you want with it.
pyamlboot is Apache-2.0, libusb is LGPL-2.1
NOTE: This is not working well on Windows anymore due to issues with libusb, I suggest using Linux or macOS.
None. You definitely can mess up your device in ways that are difficult to recover. I cannot promise a bug in this script will not brick your device. By using this tool, you accept responsibility for the outcome.
I highly recommend connecting to the UART console, frederic's repo has some good pictures showing where the pads are.
Make backups.
This tool tries to replace the proprietary update binary from Amlogic, and it covers enough functionality to be useful for superbird.
However, dumping partitions is MUCH slower.
The original tool from Amlogic manages to read directly from the mmc, without having to first read it into memory,
so it is a lot faster at about 12MB/s or about 7 minutes to dump all partitions.
Unfortunately, we cannot currently replicate this method using pyamlboot.
Instead, to dump partitions we first have to tell the device to read a chunk (128KB) into memory, and then we can read it from memory out to a file, one chunk at a time.
The copy rate for reading is about 545KB/s, and in my testing on Ubuntu x86_64 it takes about 110 minutes to dump all partitions!
The same thing must be done in reverse to restore a partition, but writing is much faster, and we can use larger chunks (512KB),
so copy rate for writing is about 4.9MB/s, and it takes about 17 minutes to write all partitions.
Partitions 2MB and smaller can be written in a single chunk, but using 2MB chunks for larger partitions eventually fails about 300MB through; I have not yet figured out why. In the meantime, it seems that 512KB chunks work well for larger partitions.
The only requirements to run this are:
You need to install pyamlboot from github master branch because the current pypy package is too old,
and is missing bulkcmd functionality.
Tested on aarch64 and x86_64
On macOS, you must install python3 and libusb from homebrew, and execute using that version of python
brew install python3 libusb
/opt/homebrew/bin/python3 -m pip install git+https://github.com/superna9999/pyamlboot
/opt/homebrew/bin/python3 superbird_tool.py --find_deviceroot is not needed on macOS
Tested on aarch64 and x86_64
On Linux, you just need to install pyamlboot.
However, root is needed on Linux, unless you fiddle with udev rules, which means the pip package also needs to be installed as root
sudo python3 -m pip install git+https://github.com/superna9999/pyamlboot
sudo ./superbird_tool.py --find_deviceTested on x86_64, but it seems really difficult to get this working consistently on Windows. I recommend Linux or macOS.
On Windows, setup is a little more involved. First download and install python for windows (tested with 3.10 and 3.11). Then you need to install drivers; I have included windows/USB_Burning_Tool_setup_v2.0.9.exe, which includes the needed driver.
The actual USB Burning Tool is not useful for Car Thing, but it includes the right driver.
Next you need to install a couple extra packages:
python -m pip install git+https://github.com/superna9999/pyamlboot
python -m pip install pyusb
python -m pip install libusbYou also need to add to add to your PATH:
rem NOTE: Python310 for python 3.10.x
%LOCALAPPDATA%\Programs\Python\Python310\Lib\site-packages\libusb\_platform\_windows\x64This stackoverflow post has a good visual explanation of how to edit PATH in Windows 10
And finally, you should be able to run the tool
python superbird_tool.py --find_deviceConfirm things actually work by connecting device in USB Mode (hold buttons 1 & 4 while connecting), and then entering USB Burn Mode:
python superbird_tool.py --burn_mode…There are four possible boot modes
This is what you get if you hold buttons 1 & 4 while plugging in the device.
The UART console will print:
G12A:BL:0253b8:61aa2d;FEAT:F0F821B0:12020;POC:D;RCY:0;USB:0;In this mode, the device shows up on USB as: 1b8e:c003 Amlogic, Inc. GX-CHIP
This is a special uboot image, which we can interact with via usb.
The UART console output will typicaly end with:
U-Boot 2015.01 (Jan 21 2022 - 08:55:34 - v1.0-57-gec3ec936c2)
DRAM: 512 MiB
Relocation Offset is: 16e42000
InUsbBurn
[MSG]sof
Set Addr 11
Get DT cfg
Get DT cfg
set CFGWhich indicates it is ready to receive commands
In this mode, the device shows up on USB as: 1b8e:c003 Amlogic, Inc.
If USB Burn mode is not enabled at every boot, or if you use --continue_boot, the device will boot up normally and launch the Spotify app.
In this mode, the device does not show up on USB.
If you use --boot_adb_kernel, a modified kernel and image will be uploaded to the device (non-persistent), which enables USB Gadget.
The USB Gadget can be configured to provide adb (like an Android phone), among other possible functionality including rndis for usb networking.
In this mode, the device shows up on USB as: 18d1:4e40 Google Inc. Nexus 7 (fastboot)
Please do NOT try to use fastboot with superbird device, there is potential to brick it.
I have provided an S49usbgadget, which can be placed on the device at /etc/init.d/S49usbgadget (make it executable).
This is a modified version of what frederic provided,
where I added a lot of comments, and added rndis function, to allow usb networking in addition to adb.
Please read it carefully before using.
You can try this host setup script to configure a Linux machine as host. I am using a RockPi-E with Armbian Community Kinetic 22.10 with success
As an example (on Linux), here are steps to enable persistent adb and usbnet, disable a/b booting, and disable charger check, on a fresh device.
…--enable_uart_shell is really only meant to be run on a fresh device. It will rewrite initargs env var, removing any other changes you made like using a particular system partition every boot.--disable_avb2 will ALSO enable the uart shell; consider using that instead.--disable_burn_mode, then boot to USB Mode (hold 1 & 4), and use --burn_mode, followed by --boot_adb_kernel, it will fail with an error about device tree--enable_burn_mode, let it boot to USB Burn Mode automatically, then use --boot_adb_kernel, it works fine--boot_adb_kernelI have provided a (very barebones) script to generate a standalone superbird_tool binary using nuitka.
You need to install nuitka, zstandard and ordered-set packages from pip to use it.
On Linux, you also need to install patchelf from your system package manager. ex: sudo apt-get install -y patchelf
I have not tested this much yet, just a neat idea for now.
Compilied binaries include images/ so they should work fine standalone.
暂无开放 Issues,或尚未同步最近议题。