NEO Z64-A: Instruction for installing the firmware

Hi guys.
Having the same issue as Profix

Stuck on the "Image type X64 is not supported by this IA32 shell

1606682040985.png

Not sure where he changed anything for the flash to work for him.

"I changed the efl shell directory to my USB drive (blk1)
Run startup.nsh command and now I'm loading into droidboot.
I have no control in droidboot.
After CMD partition,ERASE factory and cache.
It just seems to hang."
 
Last edited:
Hallo eveyone, I have the same problem shown in photo by Alefra user. Android seems not to recognize a fat32 partition as a valid media.Can anyone help me?
 

Attachments

  • WhatsApp Image 2021-03-23 at 17.32.05.jpeg
    WhatsApp Image 2021-03-23 at 17.32.05.jpeg
    106.8 KB · Views: 17
Ok, reboot droidboot starts again the same script with the same results. Reboot launch android system ( I lost screen password, yep). the third option, recovery, shows this screen for about 1 minute and starts android again. Power off turn off system. I also tried swapping usb ports between keyboard and pendrive, with the same results. I am confused . I really don't know what to do.
 

Attachments

  • WhatsApp Image 2021-03-23 at 21.17.14.jpeg
    WhatsApp Image 2021-03-23 at 21.17.14.jpeg
    27.9 KB · Views: 6
Read please in the forum, after official bios conversion z64 to w. This gives you a lot more opportunities.
 
https://theminixforum.com/index.php?threads/neo-z64-w-bios.67/

https://files.theminixforum.com/shared/drivers/Z64W-drivers.zip

A little tip from me.
Create a Fat32 Win 10 installation stick with Rufus and a Fat32. Take the Windows build from April 2020 you have to take the Win x86 version. This build is Fat32 compatible up to 4GB. Then upgrade yourself with the latest Win version in Windows to the latest Win version, which is 6GB so I could only install it by upgrading. The BIOS does not recognize Win x64.
Open the EFI Schell in the start menu and start the Win installation manually from there. bootia32.efi.
The BIOS only recognizes Fat32.
If you can't do that, we'll try together, ok.
I am happy to help and we can do it step by step.
 
Last edited by a moderator:
The reason I considered internet speed is because I get the jitters using Smarters with 4K. I noticed Smarters speed test is slower than other apps. When I use something like Blink, 4K comes in fine.
 
I don't understand everything, I'm a bit stupid.
But with the other PC I also had problems with jerking, stopping, don't know. The output is also 4k. Only if it only arrives with HD, does this make sense?
I had connected a 40pin GPIO DVB T2 / C receiver.
I used the software TV Headend via browser, which is also available in Kodi for post-installation.
There it was, increasing the graphics memory the problem, I doubled it and everything went smoothly.
How written the 40Pin GPIO via USB converter ???
 
Back
Top