Re: Multiboot Recovery CD AiO

1 view
Skip to first unread message
Message has been deleted

Agathe Thies

unread,
Jul 9, 2024, 7:34:14 AM7/9/24
to contraftvoluc

I don't really know why that happened, since I haven't done any changes to my laptop, didn't install anything, etc, it just suddenly decided that it can't boot windows. I don't really know what to do, so I tried to get into windows recovery mode, however I'm not sure how to do that. Technically, I should shut down my laptop right after it starts, and after I do that 3 times, windows should automatically enter recovery mode. However, that didn't really work. I tried shutting it down right as the laptop opened, and it didn't work. I tried shutting it down right after I chose to boot into win10, that didn't work either. I tried shutting it down after the black screen appeared, that didn't work either.

Multiboot Recovery CD AiO


DOWNLOAD https://ckonti.com/2yX7lG



So, how can I enter windows recovery mode when dual booting? And, do you have any other suggestions that I can try besides booting from an USB stick and trying to recover from there or install windows again?

It then replaces the customsettings.ini and bootstrap.ini under the Deploy\Control folder to make the deployment process automatically default to the second task sequence meant for the recovery drive. This is where the issues start.

I have a Lenovo Thinkpad X1 Carbon with Windows 10 and a BitLocker-encrypted drive. I installed Ubuntu dual-boot recently and didn't realize I was supposed to disable BitLocker during the installation. Now every time I reboot Windows I have to enter a recovery key (which fortunately I was able to obtain from Microsoft's website). I tried disabling BitLocker and rebooting a few times afterward, then re-enabling it, but it still asks for a recovery key afterward. Any idea how to fix this?

I am using a dual boot Ubuntu/win7 machine. My win 7recovery partition is around 20GB, since I have created recovery disks I am assuming I no longer need it my windows partition is only small I was thinking to delete the recovery and add an extra 20GB to my Win. Is my thinking sensible there?. The recovery partition shows as the 1st partition on my hard disc. I'm a bit concerned that by moving the starting position of my Win partition to the start of the hard disc I will make win 7 'lost' and unable to boot. I am fairly new to ubuntu and haven't used a dual boot machine before. I know I use GRUB 2 to boot either windows or ubuntu but I can't remember if I 'loose' the win7 partition and use the recovery disks wether MBR will then overwrite grub. I'm basically concerned it could become very messy and just looking for some advice as the best way to go about it. Any ideas, in n00b language?

I removed the Recovery Partition from my Dual Boot laptop, but I haven't tried to use the recovery disks yet, so I don't know what they do in terms of MBR and existing partitions. However I can say that deleting the partition hasn't affected my Windows or Ubuntu install.

I used Wubi to install Ubuntu without a CD or USB. I cannot get my (username - password) combination to work even though I'm 100% sure I typed them in correctly when installing via Wubi. I read this password-non-recognition is a common issue with wubi and that I can find out my username and password through some command line thing within recovery mode. I have a dual-booted setup with windows 7 and Ubuntu in separate partitions. So when trying to access recovery mode I hold down the left-shift-key as soon as a press enter when choosing "ubuntu" as my operating system. When I do this, nothing happens and I load in to the login screen (after around 15 seconds).

I cannot get to the screen that lets my choose to boot in recovery mode (I think this screen is called GRUB?) I read that "Boot-Repair" might somehow fix this issue, but I do not have access to a USB or CD that I can use to install "Boot-Repair."

I mostly followed [these instructions][1] for how to set up dual-booting on my macbook, and everything seemed fine, up to the very last step. Now when I reboot the system (even if I hold command-R) I don't get any rEFInd boot menu or recovery mode, it just boots to the Ubuntu partition and I have no way of booting into OSX, which means this is now just a single-boot option Ubuntu machine.I suspect it may be because during the OSX partitioning, I created two partitions, and then consolidated them into one during the Ubuntu installation phase.

I failed to follow the instructions (sorry if that's the reason for why it failed) on the openwrt site, where I got the links to the images from. Instead I started by uploading the recovery firmware through the OEM web interface. After that, it booted in recovery mode and I carried on with installing the upgrade image. However on the next boot (and every reboot since), it boots again in recovery mode. I have read some posts where such problems are described, but the problems they were facing back then seem to have been resolved since.

When that Intel Mac boots, it does so using the latest firmware installed. In the example of 11.4 and 11.5.2, that will be the firmware installed with 11.5.2, and that remains even if the 11.5.2 system is removed from that Intel Mac. Similarly, I believe that the version of recoveryOS in the Recovery volume will be the latest, that accompanying 11.5.2, which remains if 11.5.2 is removed.

1) -15-linux-data-recovery-tools-the-professionals-choice/
2) -things/10-linux-rescue-tools-for-recovering-linux-windows-or-mac-machines/
3) -rescue-recovery-tools/
4) -best-linux-distributions-to-recover-dead-computers-data-linux-data-recovery
5) -a-boot-repair-live-usb-disk-drive-in-ubuntu-linux-mint-and-elementary-os.htm

Hi, I wished to clone acer laptop HDD to new SSD. macrium reflect home v6 recovery iso with winPE10 64bit.
win 7 home premium dual boot with win 8.1 pro.
visual bcd shows win 7 and win8.1 loaders as well as eight "windows recovery environment" loaders (including reference to win10 upgrade folder).

Prior to cloning the multiboot mechanism not necessarily working as expected; Initially sometimes stalls when booting, "solved" by using Disk Management to remove the drive letter from the (other) alternative (ie win7 or win8-1 ) OS partition.
Booting to win7 using Win8 multiboot menu, would need laptop to restart again before booting into win7.

After cloning and with error 0xc000000e reported, attempts to change Path of Win8.1 loader via visual BCD fails reporting cannot write to store. Visual BCD, auto recovery option cannot find the Win8.1 root partition when searching for missing operating systems.

Boot again with Reflect's winPEv10+reflectrecovery then " Fix Windows Boot Problems". It locates both win7 and win8-1 operating systems. At end of wizard, the Restart dialog pops up although behind it a dialog shows 2 items without a tick just a "processing" circle. Restart and laptop now boots into win8.1 however all other multiboot items lost. only win8.1 loader remains (i believe with different guid now).

Can someone point me to the code where the file in the USB stick is checked so maybe I could find for an alternative. Maybe with adding content to it we can arrange something that when the box is rebooted a second time when enigma2 2 is not started the box automatically can go to recovery.

I thought at startup_recovery on usb as an easy way to go back into recovery without flashing a new kernel or connecting a serial cable or messing with ssh. It's use is to let you choose a new image if you entered into blackhole or vti that doesn't support multiboot at all.

It have a gui, i wrote some patch to make it work on vuplus, but isn't compatible with STARTUP_xx of most implementation of multiboot implemented in enigma2... since it needs the vuplus driver is diffucult to make it to fit the kernel partition.

If you do not care about Secure Boot then in the disabled state it does not interfere with Bitlocker and I was able to start Windows from systemd-boot without having to enter the recovery code every time. On the other hand, by issuing my own efi-keys (using `sbkeys`) and signing kernel image + boot loader I was able to achieve a working dual-boot setup with Secure Boot enabled. However, this made Bitlocker unhappy and he started demanding the recovery code on every boot. Finally, I was able to achieve both Secure Boot and happy Bitlocker by abolishing the boot loader and using UEFI itself for booting both Windows and Linux.

I followed mostly arch wiki for installation [1] and setting up Secure Boot [2] so I won't dive in many details in the following (see also [3]). This was done on Dell Precision 5550 laptop with already installed Windows and enabled Secure Boot and Bitlocker with TPM. Make sure to write down the Bitlocker recovery code somewhere, you will most definitely need it! My steps were:

2. Install Arch as usual by following the wiki page and encrypting with LUKS [4] it in process. Here I first installed systemd-boot and checked that I can boot both Windows and Linux without problems. However, I was not able to make systemd-boot work with the Secure Boot because (as I understand) this messes up the boot process and Bitlocker starts demanding the recovery key on every boot. I later uninstalled the systemd-boot and use UEFI itself to start both Windows and Linux, so probably its installation is not necessary at all.

Note the recovery menu does not need to be re-flashed unless you have an issue or theres an update. Recovery zip files are released with every image build, but please note you DO NOT have to re-flash or update the recovery menu unless needed.

At the time of writing this guide re-flashing the recovery menu is not removing or affecting the installed images. Note this could change in a future update cause you to loose of the images you have installed and setup.

AX Technology HD61 purchased from World-of-Satellite.co.uk will have the latest Multiboot recovery menu pre-flashed at time of purchasing. The current latest revision is bootmenu r311.

1) Download latest recovery menu from OpenViX, OpenATV or wherever you wish to download from. Can be download from OpenViX downloads HERE. At time of writing this guide latest zip release is 'openvix-5.3.023.release-ax61_recovery_emmc.zip', again you DO NOT have to re-flash or update this Multiboot recovery menu with every release.

2) Unzip the file to your desktop. You will have the following files:

'hd61' directory
recovery_ax61_lies.mich
recovery_ax61_READ.me
bootargs.bin
fastboot.bin

3) Format a USB stick MAX 8GB FAT32.

4) Copy all the files and 'hd61' folder to root of USB stick.

5) Power off the AX HD61.

6) Connect USB stick to REAR USB 2.0 port, behind front flap.

7) Hold down rear RESET reset button (next to tuner inputs).

8) Power on whilst holding down reset button. Keep holding down the RESET button until FLSH appears on front display.

9) Be paitient, once successful the AX HD61 will reboot into the recovery menu.

10) You'll see various options, to not go off topic simply select 'Boot 1. LINUX_1' to boot into the image installed into slot 1. Screen will look similar as below, note you can see the revision number bottom left corner (example screenshot).

aa06259810
Reply all
Reply to author
Forward
0 new messages