[flashrom] Re: BIOS update fails on a Minix Z100-0db device

[Robert]

Hi Alex,

I'm not using Windows, and I do not plan to, thank you.

What is this product key? Is it a product key for the Windows 
'license' or? How do I back up the product key, just copy out from 
the BIOS?

What is ME state? Why would I disable it, what is it for?
Is it a write protection feature for the BIOS?

thank you,
Robert

On Tue, 2025-01-07 at 10:54 +0800, Alex Lui wrote:
> Dear Robert,
>
> The product key is stored in the BIOS, when connected to the internet
> will automatically activated at running Windows 11 Pro.
>
> Did you disable ME state before flashing the BIOS?
>
> Goto 'advanced' page and click 'Ctrl+F1' to show hidden option.
> Disable the ME State by path: Advanced > PCH-FM Configuration > ME
> State > Disable
>
> Best Regards,
> Alex Lui
>
> Minix Group Company Limited
> Minix Forum: https://theminixforum.com
>
> -----Original Message-----
> From: Robert [mailto:[e-mail]] 
> Sent: Monday, January 6, 2025 8:20 PM
> To: Alex Lui ; [e-mail]
> Cc: [e-mail]
> Subject: Re: BIOS update fails on a Minix Z100-0db device
>
> Thank you Alex, this is very useful info.
> So if I am on 0161 now, do I have to go 0171 then 0181 then 0191?
>
> One more question: how do I back up the product key exactly?
> I already tried to update to 0181 with flashrom, but that failed,
> then reverte to 0161 with flashrom that succeeded. I hope I did not
> erase the product key?
>
> regards,
> Robert
>
> On Mon, 2025-01-06 at 11:25 +0800, Alex Lui wrote:
> > Dear Robert,
> >
> > Many thanks for contacting us.
> >
> > What is the currently BIOS version (project version) on NEO Z100-
> > 0dB?
> > When booting, press the "DEL" key repeatedly to enter the BIOS 
> > homepage. See attached pic.
> >
> > AD0J0151 or AD0J0161 cannot be directly updated to AD0J0181 or
> > AD0J0.191 in UEFI. It must be updated to AD0J0.171 first.
> >
> > AD0J0171 BIOS for Z100-0dB can be downloaded from link below:
> > https://mega.nz/file/fvRkSIgJ#riNMb_bjsuTePo_l0Co1aWsCLTZTVAbNAw1j3vQC
> > 5WQ
> >
> > File name: Z100-0dB-BIOS-171_UEFI.zip
> > File size: 18.4 MB
> >
> > AD0J0181 BIOS update under UEFI for Z100-0dB can be downloaded from
> > link below:
> > https://mega.nz/file/T64FwaDR#Ic4a69ntKaoF2RrXLDcMM94x1Gt1YYkezWPediBW
> > XtY
> >
> > Please note: Please back up the product key when updating BIOS
> > under 
> > UEFI, as this will erase the product key stored in the BIOS.
> >
> > Look forward to hearing from you soon.
> >
> > Best Regards,
> > Alex Lui
> >
> > Minix Group Company Limited
> > Minix Forum: https://theminixforum.com
> >
> > -----Original Message-----
> > From: Robert [mailto:[e-mail]]
> > Sent: Sunday, January 5, 2025 2:44 AM
> > To: [e-mail]; [e-mail]
> > Cc: [e-mail]
> > Subject: BIOS update fails on a Minix Z100-0db device
> >
> > Hi guys,
> >
> > I tried to update the BIOS on my Minix Z100-0db device so that I
> > can 
> > boot a Linux UEFI from the NVME disk. Pls. see below:
> > As per
> >
> > https://theminixforum.com/index.php?threads/guide-updating-bios-uefi-u
> > sing-gnu-linux-no-windows-needed.6905
> >    I downloaded the newest image for Minix:AD0J0181.bin
> >    (well download zip, decompress)
> > 2. I booted the device from an archlinux install USB and copied the
> >    new image there so I can access it
> > 3. I installed flashrom to the arch install OS (pacman -S
> > flashrom),
> >    the version is 1.5.1-1, compiled Dec 20 2024 4. I made a backup
> > of 
> > the current version:  flashrom -p internal -c
> >    "Opaque flash chip" -r my_backup_bios_AD0J0161.bin ... so far so
> > good ..
> > 5. I attempted to upload the new binary:  flashrom -p internal -c
> >    "Opaque flash chip" -w my_backup_bios_AD0J0161.bin
> >
> > issue follows:
> >
> > Opened /dev/mtd0 successfully
> > Found programmer flash chip "Opaque flash chip"
> > linux_mtd_wp_read_cfg: ioctl Operation not supported Failed to
> > unlock 
> > flash status reg with wp support.
> > Reading old flash chip contents... done.
> > Updating flash chip contents... linux_mtd_erase: MEMERASE ioctl
> > call 
> > returned -, error: Input/output error Erase/write done from 0 to 
> > ffffff Write Failed!Uh oh. Erase/write failed. Checking if anything
> > has changed.
> > Reading current flash chip contents... done.
> > Apparently at least some data has changed.
> > Your flash chip is in an unknown state.
> > Get help ...
> >
> > Retried with -f, which in turn again changed something, but same 
> > outcome.
> > I did not try to put back the original image so far, it would
> > probably 
> > give me the same
> >
> > The device is still on sitting in the arch install shell, I
> > increased 
> > the install disk size and added a few packages to help with the 
> > possible fix, since I believe if I would try to reboot, the device 
> > would be lost, and I would likely have to replace it.
> >
> > I am a long time linux user, can try any workaround or optionally
> > even 
> > allow ssh access to the device.
> > Can someone please give me some hints about where to go from here.
> >
> > Appeciate your time,
> > Robert