Burning Tool no Device

[gcvanasel]

This is only the Media Device so if you have gone into explorer you would see a device called VIM there

[Terry]

It can boot the device when the power line is work and the data line is broken
It can’t enter the update mode when the Type-C data line is broken.

[gcvanasel]

So there is nothing we can do? Any other suggestions? Sending the box back to GeekBuying is not an option for me as shipping would cost me over 200 USD

[barhom]

So Terry what do you suggest we do now then? I dont think the data line is broken because it was recognized when android was booted.
@gcvanasel also tried the SDCARD method with no luck. I have not tried that yet.

[gcvanasel]

@barhom

I dont think the data line is broken because it was recognized when android was booted.

Correct same with me

[Terry]

You can update the rom via SD card following this

[gcvanasel]

I already tried that doesn’t work for me. VIM doesn’t enter Update Mode, screen remains black

[Terry]

which version of your rom? Nougat or Mmallow?
You can have a try for Mmallow

[gcvanasel]

Let me try Mmallow. Ill post feedback once completed

[vrabac]

If you have Serial Console cable maybe you can check what is going on.
This method

[gcvanasel]

Tried Mmallow still nothing black screen. Not sure what is next I do not have a serial console cable

[gcvanasel]

Is there Nothing else??

[gcvanasel]

@Gouwa

Can you try again with new methods belows:1) Try to Erase the EMMC first, if the emmc is blank, VIM will boot into upgrade mode automatically when the USB-C cable is connected 2) Try with a new USB-C cable if you have one which is used by mobile phone 3) Try to use uSD card to upgrade for your VIM.

We will follow up this until you got the problem resolved!

This actually bricks the device so if you have the same issue as me and @barhom then don’t follow this advice your device will not be usable

[vrabac]

@gcvanasel
Are the driver really installed on your system?
Check this guide from Driver Installation but use Khadas provided Burning Tool installation file. Re-run installation as Administrator.

[vrabac]

This is log from Serial Console:
holding power button, press restart for 1sec, hold power button until you see “VIM” on your monitor, count 5sec more and release. This is what i get.

Start read misc partition datas!
info->attemp_times = 0
info->active_slot = 0
info->slot_info[0].bootable = 1
info->slot_info[0].online = 1
info->slot_info[1].bootable = 0
info->slot_info[1].online = 0
info->attemp_times = 0
attemp_times = 0
active slot = 0
wipe_data=successful
wipe_cache=successful
upgrade_step=2
[OSD]load fb addr from dts
[OSD]fb_addr for logo: 0x7d851000
[OSD]load fb addr from dts
[OSD]fb_addr for logo: 0x7d851000
[CANVAS]addr=0x7d851000 width=3840, height=2160
amlkey_init() enter!
amlkey_init() 71: already init!
[EFUSE_MSG]keynum is 4
[BL31]: tee size: 0
[KM]Error:f[key_manage_query_size]L507:key[usid] not programed yet
[KM]Error:f[key_manage_query_size]L507:key[mac] not programed yet
[KM]Error:f[key_manage_query_size]L507:key[deviceid] not programed yet
gpio: pin GPIOAO_2 (gpio 102) value is 0
detect upgrade key
gpio: pin GPIOAO_2 (gpio 102) value is 0
InUsbBurn
[MSG]sof
Set Addr 6
Get DT cfg
Get DT cfg
Get DT cfg
set CFG
Get DT cfg
Get DT cfg

Reboot button, and press Ctrl+C to stop autoboot:

Start read misc partition datas!
info->attemp_times = 0
info->active_slot = 0
info->slot_info[0].bootable = 1
info->slot_info[0].online = 1
info->slot_info[1].bootable = 0
info->slot_info[1].online = 0
info->attemp_times = 0
attemp_times = 0
active slot = 0
wipe_data=successful
wipe_cache=successful
upgrade_step=2
[OSD]load fb addr from dts
[OSD]fb_addr for logo: 0x7d851000
[OSD]load fb addr from dts
[OSD]fb_addr for logo: 0x7d851000
[CANVAS]addr=0x7d851000 width=3840, height=2160
amlkey_init() enter!
amlkey_init() 71: already init!
[EFUSE_MSG]keynum is 4
[BL31]: tee size: 0
[KM]Error:f[key_manage_query_size]L507:key[usid] not programed yet
[KM]Error:f[key_manage_query_size]L507:key[mac] not programed yet
[KM]Error:f[key_manage_query_size]L507:key[deviceid] not programed yet
gpio: pin GPIOAO_2 (gpio 102) value is 1
Product checking: pass!
Hit Enter or space or Ctrl+C key to stop autoboot – : 0
kvim#
kvim#
kvim#
kvim#run update
InUsbBurn
[MSG]sof
Set Addr 8
Get DT cfg
Get DT cfg
Get DT cfg
set CFG
Get DT cfg
Get DT cfg

Every time device is found correctly:

[Gouwa]

@vrabac

Are the driver really installed on your system?Check this guide from Driver Installation but use Khadas provided Burning Tool installation file. Re-run installation as Administrator.

Hi, @gcvanasel @barhom can you follow what vrabac mentioned above to check again?

[vrabac]

as this is developer board an Serial Console cable is a must have. maybe @barhom have one and can check what is wrong with device. @gcvanasel already wrote he don’t have one, but maybe someone from your friend do have an.

[gcvanasel]

Thanks @vrabac for the suggestions although I have followed the exact same steps someone posted on FreakTab unfortunately no result. The drivers are definitely installed. Is it possible to create a bootable SD in windows like http://docs.khadas.com/develop/CreateBootableSDCard/

[vrabac]

There is an howto where some windows tool are used. I don’t know if this works, but always use image khadas provided.

I don’t know which VIM version does @barhom have (non-pro or Pro), but maybe there is something wrong with non-pro version and entering upgrade mode.

@Gouwa is upgrade mode same as recovery system? and how to enter recovery system? From above logs i posted regarding serial console i don’t see anything about recovery.

[Gouwa]

@gcvanasel

Is it possible to create a bootable SD in windows like http://docs.khadas.com/develop/CreateBootableSDCard/

It’s for Linux PC, and for Windows users, please follow the Upgrade via uSD Card on Windows.