I was trying to flash emuelec to a 32 gb sandisk card to turn my android tv box into an emulator setup, but when it gets to 98% of the verification stage, I get the notice that the flash failed. I check my pc, and the drive letter no longer shows up. When I remove and replace the drive, the drive letter shows up and it’s labeled as emuelec, but with a capacity of 511 MB with only 18.6 MB free. I went ahead and continued with the setup instructions (copying a file from the file tree and pasting/renaming it in the root), inserted it in the box and booted it up, but it ignores the card and goes straight to the regular android box startup. Any suggestions? (I’ll copy/paste log files as soon as I figure what and where I’m looking!)
Hey Tom,
Depending on the information in the image that you are trying to flash into the SD Card, partitions are usually created by the OSs. The image takes only the space that it needs and that is how a partition is created (drive letter).
The OS flased into the SD Card, might be ignoring the rest of the available space in the SD card (stays unformatted), and that’s why you may not see it.
Regarding the failing at 98% I can suggest you to open the balenaEtcher console (Ctrl + Shift + I) and see if there are any errors in the process
What setup instructions are you actually trying to follow?
regards Juan
1 Like
Hello
I was trying to pull this tutorial off:
Turn A Cheap Android Tv Box Into An Emulation PowerHouse - How To Run EmuElec From SDhttps://youtu.be/eXfultzENjY
I’ve managed a few other tutorials, including one on turning an old pc into a chromebook, and turning an old pc into a media center, using the same method, more or less: flashing a thumbdrive or sd card, using etcher, booting the pc from that card. As a matter of fact, the SD card I was using this time was one I had used before to do just that, and had an older version of Emuelec on it already. I don’t think it worked for the PC, so it had sat around for a few months until I decided to try this tutorial on my Android tv box. I’m not sure if the problem is the newer version of emulec I tried to use, or the sd card, or some glitch with Etcher (which has worked before doing pretty much this same thing), or what.
Not sure if this helps any, but:
-1608953489550.log (20.3 KB)
Hi, the error suggests that there is an issue with the SD card at this image location. It will be best to check whether this is the case with another SD card. Can you please try that and let us know how that goes?
I tried again, two more times, actually. I got a 2 pack of 32 gb sd cards. I tried one and got the same error at around the same point during the verification process, but I didn’t save that particular log. I just tried again with the second card from the two pack, and got the same error around the same point. Here is that log:
-1609190752741.log (18.9 KB)
Hello @tomrog
I’ve tried flashing this image (EmuELEC-Amlogic-ng.arm-3.9-Generic.img) on a 32GiB SD card on a Windows 10 PC, it worked fine.
Verification errors might happen in some case on Windows when something writes data on a partition between the moment the data is written and read again for verification by Etcher. This might only happen with ntfs or fat partitions. Most of the time it’s Windows creating a “System Volume Information” folder.
So your SD card was most probably flashed fine.
When I remove and replace the drive, the drive letter shows up and it’s labeled as emuelec, but with a capacity of 511 MB with only 18.6 MB free.
This is totally expected. The emuelec image contains one 512MiB fat partition and a 32MiB ext4 partition (that will be resized when the device boots). Windows only sees the fat partition.
inserted it in the box and booted it up, but it ignores the card and goes straight to the regular android box startup
My guess is that you need to do something to make your device boot from the sd card. The video you linked mentions pressing a button while the device boots.