![]() Other members may know of techniques to unlock USBs that are locked by some mechanism. that was the ONLY unit ever that I encountered that exhibited that 'locked behavior in my 3 decades of use. About a month ago, I ran across a video where I watch someone unlock this type of vendor locking, but, for the life of me, I cannot find it in my history. After repeating attempts over several months using all sorts of techniques found in/out of the forum, I gave up and discarded it. This was a vendor product USB given me that I tried to understand and unlock.to no avail. Several years ago I had a USB stick that, for the life of me, I could NOT unlock. If this is happening with all of your removables, there must be function somewhere in your system(s) that is flipping your removables to a read-only status as if there is a physical switch on the units to make them 'locked'. Or are you saying that when trying to repurpose a removable, GParted wont allow you to do so? When you say "locked up" does this mean you cannot write to them to add ISOs.or something else./ This sound like something going on within your OS(s) that is affecting your removables. Tosim wrote: ↑ Fri 6:09 As you may recall. With this USB arrangement, I directly boot EVERY ISO file and IMG file I put in the BOOTISOS folder. Moral to this story: "Since 2019, all WoofCE PUPs and DOGS boot directly from their ISO files via SG2D without issue while, since Ventoy's introduction, only the 2 mentioned DOG-PUPs do so from Ventoy's Menu listing."īenefit: SG2D boots everything in this forum while Ventoy expresses to boot ALL distro ISO files. There are some recent issues with KLV that are being worked on, currently. I use this USB arrangement for both good housekeeping of all my PUP ISOs and because it is a Frugal setup without any need to extract or corrupt ISO contents. I have tested all 64bit DOGs and WoofCE PUPs they all boot without issue! If there are any boot issues, these would be PUP/DOG distro issues and will have nothing to do with either Ventoy or SG2D. Hit the Enter-key on the SG2D Menu allowing it to discover all ISO filesĮXPECT to boot every ISO file you see. Put ALL of your ISO files in a folder on the USB named 'BOOTISOS' (DONT WORRY Ventoy will find them without problems)Īdd the SuperGrub2 (SG2D) ISO file to your folder with ISOs If you want to circumvent and boot ALL PUPs and DOGs, (in today's versions), you will need to They are Slacko64s beginning v7.0 and all v8+. There is only 2 PUPDOG vintages, thus far, that currently boot OOTB from the Ventoy Menu. It has little to nothing to do with your USB sticks, rather, it a problem that has been around since VEntoy started. You should now be able to load and run the Debian efi installation program successfully.I am having problems trying to boot both 64- and 32-bit versions with Ventoy. This will obviously replace the existing file boo圆4.efi. Rename the file grub圆4.efi to boot圆4.efi: There are two files in this directory: grub圆4.efi and boot圆4.efi. Navigate to the directory /mnt/efi/boot on the usb stick: Sudo mount -t vfat /dev/sdc2 /mnt -o uid=1000 Mount the partition on which the iso file resides (in my case this was sdc2, but this will differ for different setups): Insert the installation stick and type the following command at the prompt to get the path of the partition on which the iso file resides: Note: I think you might need to have disabled Secure Boot first of all for this to work. I finally managed to find out how to edit the iso file to get it to boot. I have installed different Linux distributions in the past and have not had any problem. ![]() The installer works in that mode and would let me go through the installation process. I don't think there is anything wrong with the usb stick or the iso file that I copied on to it. ![]() Could someone tell me how to make the usb key writable, so I can copy and paste that mm圆4.efi file ? However, the usb disk is read-only, and I cannot find a way to copy the necessary file to the stick. It seems that there is a missing file on the installation medium mm圆4.efi which should be in the directory \EFI\BOOT\ on the installation medium. "Failed to open \EFI\BOOT\mm圆4.efi - Not Found" It then says "Something has gone seriously wrong: import_mok_state() failed" and my PC then powers down. If you're using a 32-bit or 32-bit compatible x86 processor, open the Ventoy2Disk.exe app inside the unzipped folder. ![]() When I try to load the Debian installer in UEFI mode I get an error message saying I have put the live iso file on a usb stick by copying it in the way recommended in the installation instruction on the Debian website. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |