Q10 Pro Hangs at Himedia screen.

[nitgoon]

Hi,

I've just gotten my Q10 Pro. Booting it up for the first time, it shows the Himedia logo on a black background. Waited a half hour or so in case it was doing some initial setup of some kind, but no progress seemed to occur. The LED says "boot". Could not power it off without unplugging it. I then tried to update the firmware with the  5.1 -> 7 firmware, following the directions. If ever the button on the back is pressed with a paperclip, the screen displays "0000" instead of "boot", but not further progress is made. I have left it overnight, and nothing ever gets beyond the black "Himedia" screen.

Is there anything I can do?

Thanks

[nandish]

Unplug power. Press the upgrade button, then insert the power supply plug into the slot while holding the upgrade button.

[nitgoon]

Thanks for the suggestion. This causes the unit to boot to the Himedia screen as well. Unfortunately, it doesn't make any progress either.

I previously had a KDlinks A300 (aka, Q10) and have had experience updating that without issue.

[nitgoon]

Attempted the method here: http://www.futeko.com/newforum/index.php?topic=1622.15

Still no luck. Never gets beyond the himedia screen. Plugging in a USB drive with light indicator suggests USB are powered. Harddrives spin up when plugged in. I'm guessing the flash is just completely fried including any backup/recovery memory.

[futeko.com]

If you bought it from us then email us with your order info and we will probably fix it under warranty.

If not then I would expect the method you've already linked to work. Make sure you are shorting the pins on the PCB correctly and the USB stick has the special recovery files on it. http://www.futeko.com/newforum/index.php?topic=1622.msg14469#msg14469

[nitgoon]

Nope, I  did not buy it from you.

Yes, I shorted the pcb and had the recovery files on the usb.

(To be clear, I am not demanding help or anything. Just hopeful that there will be a resolution besides returning it to this reseller, who probably does not have another unit, and waiting longer to get one elsewhere. It seems to me that a recovery module should always be functional in this type of device, but I have no idea how exactly this one works or if there is non-corruptible recovery memory used for reflashing, etc. I'm thinking no, though, since I've never made it to an android screen).

[futeko.com]

I am surprised the recovery procedure as detailed in the forum post does not work. It should at least start the firmware install process, regardless of the state on internal flash. Shorting the PCB pin causes the Q10 Pro to boot from the bootloader on the USB stick.

Beyond that process, I don't know of another recovery process.

[nitgoon]

Very strange indeed.

Should shorting the pin show me the android screen regardless of what is on the drive? Just wondering if I can narrow down whether the problem might be due to the shorting not working properly, or some issue with the USB. For the former, I can try cleaning the contacts or using some other metal piece to connect them. For the latter, I'm not sure. I've tried two USB thumb drives and one FAT32 HDD. Maybe I'll try a full format on a thumb drive, or try to find another one somewhere.

The contact points that are circled in the diagram are definitely the correct two, right?

I appreciate the responses, thanks.

edit: And there is no preference for one usb slot, right? I'm just using the center one, as in the image in the tutorial (though I'm sure it doesn't matter).

[futeko.com]

Shorting the pin will only show you the Android screen if the contents of the USB stick are recognised as valid so the device can boot from them.

The update files should be on a GPT/FAT32 formatted USB flash drive (not HDD).

The info in the forum post is accurate. If you follow the instructions and image exactly it should work. I'm not sure if USB port matters (I think not) but I always flash using the middle USB 2.0 port as shown on the photo.

[nitgoon]

Thanks again. Will give it a few more tries this evening.

I've seen a few other people with this 'himedia hang' problem, including the thread where you posted that nice tutorial. However, I don't know the outcome of any of those cases. Have you gotten boxes back (that are not completely dead with no A/V) that you couldn't recover with this method?

Edit: Any easy way to check if this is actually a chinese model? That could explain the problem...

[futeko.com]

Thanks again. Will give it a few more tries this evening.

I've seen a few other people with this 'himedia hang' problem, including the thread where you posted that nice tutorial. However, I don't know the outcome of any of those cases. Have you gotten boxes back (that are not completely dead with no A/V) that you couldn't recover with this method?

Edit: Any easy way to check if this is actually a chinese model? That could explain the problem...

Yes we have reflashed several boxes using the linked to method.

Chinese vs European Q10 Pro: http://www.futeko.com/newforum/index.php?topic=1175.msg9321#msg9321

[march11]

I tried to update the firmware to the latest available 31-05-2019 but now my Q10 pro is stuck on “Himedia logo” screen. I tried to go-back to this configuration as described in a past post:

“Q10 PRO ANDROID 5.1 TO ANDROID 7 MIGRATION FIRMWARE” and “Q5 + 10 Pro Recovery Boot Files”

Nothing works. I do not remember which firmware version I had before this unsuccessful update, android version was 7 since I have coloured circle during the update (right?)
s/n of my device is HMDB501607006832, NOT bought from futeko in November 2016. My question is: which firmware should I try to restore? My aim was to update it to the last firmware release but at least now I would like to have it work back.

I saw the procedure where I need to dissasemble the device, but before doing that I would like to be sure about configuration to flash or if there is any other way to fix the device. Thanks

P.S.: I wrote an email last week to mail@futeko.com but i got the delivery failed message since "maximum retry queue age reached"

[stl]

Try to install official 2.0.3