Winbook TW801 Hidden Menu unlock?

[Maxinator500]

Sorry for the waiting. I have been trying to figure out what is Linux for too long.

Tried compiling on the WinBook under x86 ubuntu, getting this issue

I also encountered this issue and after I solved it I came with that this is a 32-bit specific thing because such an error does not occur when making a 64-bit efi. Since I don't have a suitable system, I couldn't test the IA32 shell, but the other one works fine.
DOWNLOAD

[whoareyou]

Sorry for the waiting. I have been trying to figure out what is Linux for too long.

Tried compiling on the WinBook under x86 ubuntu, getting this issue

I also encountered this issue and after I solved it I came with that this is a 32-bit specific thing because such an error does not occur when making a 64-bit efi. Since I don't have a suitable system, I couldn't test the IA32 shell, but the other one works fine.
DOWNLOAD

Awesome thanks, that boots and I ran the command successfully, i think, and rebooted with the DOS usb inserted, but it seems to still boot in EFI mode, is there another command I need to run to trigger it to boot DOS after running the setup_var_cv command?

[Maxinator500]

Have you set set boot priority order USB item to first in list?

is there another command I need to run to trigger it to boot DOS after running the setup_var_cv command?

I'm not sure if that'll be beneficial, but you can run some more.
Enable USB Legacy - "setup_var_cv System 0x1b 0x01 0x01";
Disable UEFI Boot - "setup_var_cv System 0x3 0x01 0x00".
I wonder if the commands affect something at all.

[whoareyou]

Have you set set boot priority order USB item to first in list?

is there another command I need to run to trigger it to boot DOS after running the setup_var_cv command?

I'm not sure if that'll be beneficial, but you can run some more.
Enable USB Legacy - "setup_var_cv System 0x1b 0x01 0x01";
Disable UEFI Boot - "setup_var_cv System 0x3 0x01 0x00".
I wonder if the commands affect something at all.

When running the commands the output is just:

"Looking for System variable...."

Same as this issue:
https://github.com/datasone/grub-mod-set.../issues/26

so maybe its not actually doing anything?

ran all 3 and rebooted with no change :/

Sorry for this headache and i hope its not been too big of a bother for you!

[Maxinator500]

so maybe its not actually doing anything?

Yeah, it doesn't do anything. Sad. I'll try to fix it today.

[whoareyou]

so maybe its not actually doing anything?

Yeah, it doesn't do anything. Sad. I'll try to fix it today.

Sounds good, looking forward to testing

[Maxinator500]

I've come to the conclusion that when EFI stops at "looking for variable" it means that the requested instance could not be found.
But the "setup_var_cv" function was used, so why is "System" var. store cannot be found? -I don't know. I even checked that in BIOS VSS this exact name is assigned to the correspondent store. So, this is not as in the case of "SystemConfig" that is equal to "Setup".
But I made another couple of EFI shells, in which I removed all commands except for the standard "setup_var", and also changed the GUID and signature name for search. I can be wrong about how this all actually works, thus it's worth checking the presence of the "System" using the command: "lsefivar". Output of this command will help determine the real name. It gives a summary of sizes.

looking forward to testing

setup_var 0x02 0x01

DOWNLOAD

[whoareyou]

I've come to the conclusion that when EFI stops at "looking for variable" it means that the requested instance could not be found.
But the "setup_var_cv" function was used, so why is "System" var. store cannot be found? -I don't know. I even checked that in BIOS VSS this exact name is assigned to the correspondent store. So, this is not as in the case of "SystemConfig" that is equal to "Setup".
But I made another couple of EFI shells, in which I removed all commands except for the standard "setup_var", and also changed the GUID and signature name for search. I can be wrong about how this all actually works, thus it's worth checking the presence of the "System" using the command: "lsefivar". Output of this command will help determine the real name. It gives a summary of sizes.

looking forward to testing

setup_var 0x02 0x01

DOWNLOAD

Okay,

https://photos.google.com/share/AF1QipN1...8xNWRxLWtR

Heres what I see, System is clearly listed there, but getting the same result with setup_var 0x02 0x01 as before...

[Maxinator500]

the same result

Well, then we must admit that the developers from Micro Electronics did a good job. This method also proved to be inapplicable. It was a waste of time but I'm not complaining. I want to tell you that there is no software method left.

[whoareyou]

the same result

Well, then we must admit that the developers from Micro Electronics did a good job. This method also proved to be inapplicable. It was a waste of time but I'm not complaining. I want to tell you that there is no software method left.

Alright, thank you for your attempts! Sorry it was a waste of time!