for convenience i used boot to coreelec app in there the second option “first boot”
was i supposed to go to recovery instead of update?
the remote doesnt work in recovery when i tried it yesterday.
CE recovery does the initial steps for normal boot later.
Your step was fine and correct.
are there so many different revisions of this box? or is it my stick? i could try my other usb 3 stick. is rufus ok?
It was all good with first 2 tests when you uploaded a folder.
The last test should boot complete CE as recovery/update but for some reason it doesn’t. There is something still mising.
the folder from another boot, if it helps. different stick, powered usb hub this time. but with the recovery and kernel you’ve send last time
does it matter that it’s logging mount long before the usb devices are detected?
or is that just how it gets output?
<12>\[ 1.613103\] init: ### mount filesystem LABEL=COREELEC …
<5>\[ 3.071353\] scsi 0:0:0:0: Direct-Access USB SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6
Not really. It just wait until it is available as you can see few lines
LABEL=COREELEC: Can't open blockdev
1 Like
New day, new options.
Please test same usb stick but copy this 2 files on it. No need for any files just observation how it behave.
stuck at the mi logo for longer than 3 min
This is actually good news.
Please use this image and if it stuck for 2 minutes check if you have ssh access.
After 2 minutes then again upload midebug folder if have any files.
I can only try it out later today.
1 Like
I hope we hear the result 
ssh access via network? the box did not connect with my network while showing the mi logo
was i supposed to edit the dtb.img? i ask because this time it was the same size as s7d_s905x5m_xiaomi_3rd_gen.dtb and i didnt bother because of that.
i will make a 2nd try with edited dtb.img
DTB was already included correctly s7d_s905x5m_xiaomi_3rd_gen.dtb.
Ok, no more tests needed: it doesn’t work 
Very hard to do such bring-up remotely. There is hope for one day but for now it’s not possible.
would it be easier if i would send you the box?
Ok, for last time try previous image with this 2 files and upload midebug folder.
Also check if connected to network. Just in case …
something is of with my usb stick. i will try all three things again.
ok, so same behavior with the other stick and without the powered usb hub. with just the image it only creates the all.txt and with the kernel and recovery file it restarts after an few seconds and boots into google tv
Thank you.
Over and out 
thank you for your effort