This is my first post in this community. So, please forgive me if my question looks duplciated. I searched, by myself, quite a time but can’t find exact same problem I have.
Let me ask my questions in two separate parts: easy/simple one and complicate one.
First, I’d like to know if I can use Khadas burning tool for Windows (VIM3 Burning Tools for Windows) for flashing Android 11 images to VIM3 Pro device instead of the instruction listed in [VIM3 Flashing Guideline](참조 보드 사용 | Android 오픈소스 프로젝트 | Android Open Source Project)?
Actually I had used the tool for burning Android 9 image which is a single image file (update.img) and each partition images are not seperated.
Second, I’d like to know what is the best practice to capture VIM3 USB device while running the Ubuntu as VirtualBox guest OS over the Windows host OS?
The reason I ask the 1st question is because it looks I have complicate problem to make my Ubuntu detect the VIM3 USB properly. Sometimes it detect it as Amlogic only which is working for u-boot image flashing but the other times it is detected as Google Nexus device which is working for adb only.
Host OS: Windows 11
VirtualBox: 6.1.26 (with Extension Pack installed)
Guest OS: Ubuntu 18.04
What I found is to flash the u-boot image in the Ubuntu, I need to first make my VIM to enter upgrade mode by the key combination (Power + Reset) before starting the VB guest OS. Then, the linux detects the Amlogic vendor ID correctly as followings:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 1b8e:c003 Amlogic, Inc.
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
However, adb or fastboot command looks not working under this state. So, the flashing task fails at the 3rd step as the VIM3 USB is disconnected (there’s a disconnection sound from Windows):
./tools/update write u-boot_kvim3_noab.bin 0xfffa0000 0x10000 (completed)
./tools/update run 0xfffa0000 (completed but USB disconnection sound heard)
./tools/update bl2_boot u-boot_kvim3_noab.bin (failed)
So, I re-started from the beginning with pyamlboot script pyamlboot script and it looks successful:
$ boot-g12.py u-boot_kvim3_noab.bin
Firmware Version :
ROM: 3.2 Stage: 0.0
Need Password: 0 Password OK: 1
Writing u-boot_kvim3_noab.bin at 0xfffa0000…
Running at 0xfffa0000…
AMLC dataSize=16384, offset=65536, seq=0…
AMLC dataSize=49152, offset=393216, seq=1…
AMLC dataSize=16384, offset=229376, seq=2…
AMLC dataSize=49152, offset=245760, seq=3…
AMLC dataSize=49152, offset=294912, seq=4…
AMLC dataSize=16384, offset=65536, seq=5…
AMLC dataSize=1110384, offset=81920, seq=6…
However, the next command looks stuck and just waing the device:
$ fastboot oem format
< waiting for any device >
Remaing steps cannot be done.
Because I have all the Android 11 images already via successful compiling and Windows burning tool is detecting VIM3 board, I’d like to just use the tool if possible or I’d like to know how to configure the VirtualBox USB configuration to flash the images to my VIM3.
Any suggestion will be highly appreciated.