Closed anuwrag closed 2 years ago
I forgot a part of the guide. LOL
Going to add it now, sorry for that
@anuwrag added. You're missing the testsigning line.
You can do that directly, no need to start over. Let me know if this fixes it. Thanks!
When trying to run the testsigning line I get this error:
PS E:\Development\Android\Surface Duo> bcdedit /store Y:\EFI\Microsoft\BOOT\BCD /set {default} testsigning on
The set command specified is not valid.
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.
Is there a way to boot into UEFI mass storage after dism EFI into Y:/?
Currently, I have to mkfs. f32 and then copy DuoBoot EFI
@JengaMasterG
When trying to run the testsigning line I get this error:
The command is right 🤔 Here's my output:
C:\Windows\System32>bcdedit /store X:\path\to\my\boot\BCD /set {default} testsigning on
Operation completed.
Are you running the cmd in administration mode? 🤔
@anuwrag
Is there a way to boot into UEFI mass storage after dism EFI into Y:/?
Well, actually, yes. You must add a boot entry to the EFI BCD pointing to the dev menu, I'm working on adding a guide for this Meanwhile, feel free to enter the DuoWOA group on telegram, I'll be glad to help you there directly: Link!
@JengaMasterG
When trying to run the testsigning line I get this error:
The command is right 🤔 Here's my output:
C:\Windows\System32>bcdedit /store X:\path\to\my\boot\BCD /set {default} testsigning on Operation completed.
Are you running the cmd in administration mode? 🤔
I was using Powershell, but I'll try that in admin mode and then cmd after!
@anuwrag @JengaMasterG
is this solved? Can I close this?
Sorry, yes! It's solved
Solved! 👍
After installing the X: and Y: drive, I flashed the Drivers and rebooted using fastboot boot boot.img.
I landed up on Recovery screen displaying the digital signature of the file couldn't be verified. File\...\qxppx8180.infarm64... ***.sys Error: 0x....428.
Is there a way to bypass the digital signature?