Sometime we do get in troubles but that doesnt mean its the manufacturer or the support.
Lets be positive and try to solve issue one by one. So by the pic I assume you’re able to connect the device in upgrade mode, next you’re getting this error.
Can you check if the usb cable is causing the device to disconnect in the middle of the process. Else I would recommend you download the latest android rom again and extract it and attach it to the burning tool. As I suspect img issue here.
Also please share the connect error code from this image.
[19:40:10 129][HUB2-5][Inf]--------------ERASE BOOTLOADER------------
[19:40:10 229][HUB2-5][Inf]–start SendIdentifyCmd
[19:40:15 229][HUB2-5][Err]–IOCTL_IDENTIFY_HOST_Handler ret=-116 error_msg=libusb0-dll:err [control_msg] sending control message failed, win error: The I/O operation has been aborted because of either a thread exit or an application request.
[19:40:15 229][HUB2-5][Err]–Identify status failed
[19:40:15 236][HUB2-5][Err]–[0x00101004]Erase bootloader/Lowper/Identify/Error result
[19:40:15 236][HUB2-5][Inf]–Close device handle 0x00000f30
Tried downloading different files, different cables, different computers.
It’s just a piece of unstable crap.
I’m just going to toss it in the trash. It’s dead weight. Rarely updated and just creates problems all the time. Better buy a couple of cheap X96 Max boxes that are faster and half the price and just work out of the box without getting headaches…
Every firmware update has been trouble so far… if there even was a firmware update in the first place… Tried Oreo once… didn’t even want to install packages… It’s just hopeless with these devices.
For what it is worth, I have had no issues flashing the VIM1. I have found that getting in to upgrade mode successfully is largely a matter of timing on key presses. Humans are seldom good clocks or timers.
I did not intend to say it was complicated, it isn’t. If you are getting the tool to recognize your VIM1, then getting into update mode is not the problem. Forget my suggestion about erasing the eMMC, I don’t want to be the cause of further frustrations.
Hope you find the solution.
After that I flashed superceleron’s Custom Android Pie(Normal), went right in.
I don’t know why yours is taking so many attempts, but it can be done.
By the way, these errors are not unique to Khadas products, but a product of the AML USB Burning Tool.
What i did…
1.) Open tool and load image, set to Erase all.
2.) Pushed and held power button, connected USB cable to the PC, held power button until the tool reported Connect success.
Clicked Start in the tool, when it failed I clicked stop, then clicked start again, repeated until it was successful.
Using the Burn Card Maker to update from micro SD card.
After all of that, I downgraded to the latest 7.1 again.
Using the Burn Card Maker, I loaded superceleron’s Custom Android Pie(Normal) in to the Burn Card Maker. I set the option in the burn Card Maker to Forcefully Erase All and made the card.
I ejected the card after the tool was done. With the USB-C cable removed from the VIM1, I inserted the card in to the VIM1’s card slot, held the power button and connected the USB-C(for power) cable to the VIM1, While holding the power button I immediately pressed the reset button for 2 seconds and released the reset button, held the power button for 10 seconds and released it. The screen goes black for a few seconds and then the Update screen with the little Android guy(see picture below) came on the screen, the progress bar advanced, when it was done the VIM1 rebooted. After a few seconds it started booting superceleron’s Custom Pie. Worked with out issue.
What I figured is that the Low_power thingy must mean the USB doesn’t get enough power. I tried ALL USB ports on both my AMD MSI B450M board AND my Dell laptop. But when I finally got my MSI GS60 laptop from the office to home, IT WORKED.
The strange thing is that I use the same USB ports that don’t work with the Khadas for my X96 Max boxes… so there is that…
So glad to hear you were successful.
In the future, if you have issues with the USB update method, you can try the SD card update method using the Burning Card Maker, as defined in my post here, the last paragraph.
The custom ROMs from @superceleron are nice and as Gouwa said, they offer more features than the stock Android, as well as some tweaks to improve performance in some areas.
As he offers the ATV version you will have the option of using AndroidTV if that appeals to you.
Have a look at superceleron’s post on those ROMs for more information.
1.) Custom Android Pie ROM.
2.) Custom AndroidTV ROM.
There was no way of using the burning tool for me with my SD cards. I only have 64gb and 128gb cards and the windows format tool which is forced by the tool is not willing to format it in FAT32 since they are big.
I tried but it was a no go with exfat or ntfs.
I’ll try the custom rom then. I looked at stock and it’s very empty in the settings section.
Formatting larger SD cards to FAT32 can be done in Windows 10(may require 3rd party app/program). I do not have any cards 64GB or larger to test on at the moment. However, if you do a search you will find solutions for that. Some are on Youtube too.
Not sure if the SD formatter will do it, but worth checking in to.