Search the Community

So, I'm not really sure wtf I did. But I removed my manjaro partition from my computer because I no longer needed it (I was using sigmod to test tf2 missions but now the server allows us to do that on their behalf) and I jut removed that partition but in BIOS it's still named manjaro. And without the USB plugged in it sends me to grub rescue. I did try fixing it on my own which kinda worked. I just followed some tutorial and I think bcdboot c:\windows /s D: (which was the USB /f UEFI and I also did that but with volume 3 which I think was system restore. So I CAN get into windows and I am IN windows. So my real question is... How tf do I make the bootloader windows and remove ANY trace from manjaro.

PROXMOX is a fantastic free and open Linux KVM hypervisor (with the option of a subscription - not required) but it's not without it's caveats. If when you installed PROXMOX you opted to create a ZFS rpool for the OS be that a mirror (RAID1), striped mirror (RAID10) or any combination of parity (RAID50, 51, 60, 61) you will find the installer creates more than a ZFS partition on each disk. It creates two additional partitions these being a 1MB BIOS boot partition and a 512MB EFI boot partition. nvme0n1 259:6 0 447.1G 0 disk ├─nvme0n1p1 259:7 0 1007K 0 part ├─nvme0n1p2 259:8 0 512M 0 part └─nvme0n1p3 259:9 0 118.7G 0 part Now these p1 & p2 partitions play an important role in allowing the hypervisor to boot. This is known as the bootloader. Without it the BIOS has no way of knowing where the OS is even though it's there in it's entirety on p3. This is where ZFS has the caveat. If you're like me and you've suffered a few disk failures you'll be familiar with this output: pool: rpool state: DEGRADED status: One or more devices could not be used because the label is missing or invalid. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Replace the device using 'zpool replace'. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J scan: scrub repaired 0B in 00:00:44 with 0 errors on Sun Jun 11 00:24:48 2023 config: NAME STATE READ WRITE CKSUM rpool DEGRADED 0 0 0 mirror-0 DEGRADED 0 0 0 nvme0n1p3 ONLINE 0 0 0 4849641676990992824 UNAVAIL 0 0 0 was /dev/nvme3n1p3 errors: No known data errors In this scenario one SSD in a mirror used to boot the server has failed. Now ZFS makes it pretty easy to restore this by just replacing the SSD and resilvering with the appropriate command but it will only restore partition #3. nvme0n1 259:6 0 447.1G 0 disk ├─nvme0n1p1 259:7 0 1007K 0 part ├─nvme0n1p2 259:8 0 512M 0 part └─nvme0n1p3 259:9 0 118.7G 0 part nvme3n1 259:6 0 447.1G 0 disk └─nvme0n1p3 259:9 0 118.7G 0 part At this stage ZFS is happy, it's hunky-dory, it's walking on sunshine...but what would happen if we were to lose nvme0n1? Well, everything would keep running fine. Until you shut the server down or rebooted. At that stage it doesn't matter that you had a ZFS backup of your boot drive ZFS didn't copy the bootloader. Your data is still there. It exists but you'd have to recover the bootloader partitions. To avoid having to do that what I want to demonstrate are the steps required to re-create and initialize the bootloader partitions with a real example. Before you resilver the array you'll want to run the commands: sgdisk /dev/nvme0n1 -R /dev/nvme3n1 sgdisk -G /dev/nvme3n1 Be careful to replicate any capitalized letters such as -R and -G as capitals can issue different operation to their lowercase counterparts. What this has done is taken a new disk from this: nvme3n1 259:0 0 447.1G 0 disk To this: nvme3n1 259:0 0 447.1G 0 disk ├─nvme3n1p1 259:1 0 1007K 0 part ├─nvme3n1p2 259:2 0 512M 0 part └─nvme3n1p3 259:13 0 118.7G 0 part Now note all it has done is created/copied the partitions. We still need to re-write the partition data over to the new disk. From here we can start resilvering our ZFS array: zpool replace -f rpool 4849641676990992824 /dev/nvme3n1p3 And check-in on how the progress is doing: pool: rpool state: DEGRADED status: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state. action: Wait for the resilver to complete. scan: resilver in progress since Sat Oct 14 17:31:37 2023 37.3G scanned at 764M/s, 24.5G issued at 502M/s, 37.3G total 24.7G resilvered, 65.73% done, 00:00:26 to go config: NAME STATE READ WRITE CKSUM rpool DEGRADED 0 0 0 mirror-0 DEGRADED 0 0 0 nvme0n1p3 ONLINE 0 0 0 replacing-1 DEGRADED 0 0 0 4849641676990992824 UNAVAIL 0 0 0 was /dev/nvme3n1p3/old nvme3n1p3 ONLINE 0 0 0 (resilvering) errors: No known data errors Once this completes that is p3 taken care of but p1 & p2 still aren't configured. To do that we first need to know weather PROXMOX is being booted with GRUB or SYSTEMD-BOOT. The easiest way to find out for sure is to know which boot menu you see when the server is turned on. One of these two screens should look familiar to you: If you see the blue screen then your server boots using GRUB. If you see a black screen then your server boots using SYSTEMD-BOOT. You may also check from the OS without rebooting using: efibootmgr -v This will return a lot of information but you should see a line resembling one of the following: Boot0005* proxmox [...] File(\EFI\proxmox\grubx64.efi) Boot0006* Linux Boot Manager [...] File(\EFI\systemd\systemd-bootx64.efi) These should be self explanatory. If you see GRUB you are using GRUB. If you see SYSTEMD you're using SYSTEMD. From here you will use the corresponding command to configure your bootloader: GRUB: grub-install /dev/nvme3n1 SYSTEMD: proxmox-boot-tool format /dev/nvme3n1p2 proxmox-boot-tool init /dev/nvme3n1p2 And you're done. If you are so inclined as to test if this actually worked you can shutdown the server and remove the healthy drive you copied the boot data from. Turn the server on and see if it boots from the new drive you just formatted and copied all the system data to. If everything went well the server should boot as normal. I hope this helped.

Every time I try to install Ubuntu the GRUB bootloader fails to work and doesn't show any of my boot options. So, I can install Ubuntu but I can't get into ubuntu. I installed Pop os and I was able to boot into it from uefi by pressing f12 on my keyboard. The problem is that Pop os is giving me issues with not having the right resolution for my display and my aux port won't work with it. So, I decided I want to try stock Ubuntu. I then learned that Pop os used systemd-boot instead of Grub and that is why it booted and ubuntu didn't. So, I was wondering if after installing ubuntu to my drive, is there a way to boot from a live usb and access my installation using the live usb and change my bootloader from grub to systemd-boot in terminal?

so I was installing Arch Linux the other day because I want to do soem linux ricing yes. I did a successful install on my old lenovo legion y7000 laptop but it is not my main device and I want Arch Linux on my custom build PC. I followed the Arch Wiki and everything went well in the installation process until the last bit of installing grub bootloader. Since I am dualbooting Windows and Pop!_OS initially and is about to do a "triple-booting" with Arch Linux added to the list, I used os-prober to auto-detect other systems and add to the grub bootloader entries. It did detect Pop!_OS when I mounted the partition and did not find windows since I didnt mount it and I dont need it in my grub bootloader entries. Now the problem is, from the output of os-prober, only popos is detected, even though the arch linux base system is installed and mounted. Even after I used the command to summon the grub.cfg, from the boot options under Arch linux root partition /mnt/boot/EFI/grub/grubx64.efi (if I recall correctly) there is no sign of Arch linux whatsoever. It was just popos, popos advanced options and uefi firmware settings. pls provide some solutions thanks

So I unlocked my bootloader successfully using techmesto's free boot loader unlock tool (Link to the guide) and i wanted to flash a twrp recovery. But when I boot into fastboot using "adb reboot bootloader" command and then try the "fastboot devices" command i get no output. But when I try "adb devices" in normal boot I get an output of my device's serial number. I also found out that some how techmesto's tool is able to recognize my device when in bootloader mode. I already tried various drivers from hmd gobal, google and universal adb drivers still no change and also tried it with different cables and different usb ports and finally tried it after a clean windows install too but no luck. so can anyone help me out of this situation as it's frustrating that I can't still do anything even after unlocking my bootloader after waiting all this time.

So I'm working on a project right now... I've got a "spare" computer that I am working on installing older versions of Windows on. Currently, I have (working) copies for Windows 11, Windows 7, and Windows XP Professional installed. All are x64 copies. After installing XP, the computer will either boot to A: A older Windows boot loader (not the newer blue-screened one from Windows 10) that gives the option to boot from Windows 7 or 11 B: Boots to Windows XP only Since drives can only be created with a maximum of 4 partitions, Windows 7 and Windows 11 are housed on an SSD (1 EFI partition, 1 System Partition, 1 Windows 11 OS partition, 1 Windows 7 OS partition) and the XP install is housed on a separate partition on a HDD. I know that is likely the issue (Bootloader for 7 and 11 wont read off 2 different drives), since it wants to boot off one drive or the other. The order of which they were installed was: Windows 11, then 7, then XP. I realize now that it might have made sense to do that in the reverse order, but oh well... My question is, what should I do to make the bootloader show all three Windows versions and ensure it boots to the loader? Surely there is some way it can show the operating systems on multiple drives in the bootloader... or maybe the default windows bootloader can't read XP? I have looked at installing a boot loader such as rEFInd, but I can't seem to find a (safe) file download for that... I've heard that older versions of Windows have compatibility issues with other loaders like GRUB (maybe I am wrong), so I am looking for something that is compatible. Would love any help y'all can offer! To get this out of the way, since I know some are going to ask: yes, I know that VMs are likely a more reliable solution. However, this is a project primarily for fun (and running older software) so I am not interested in VMs since this is not my main PC and I prefer running it fully off the physical hardware.

I have a Oppo Reno3 Pro CPH2036 which has an expired warranty so I decided to root it. I need to access the bootloader. I have tried some methods: - Volume up + Power Button : just boot like normal - "adb reboot bootloader" and "adb reboot-bootloader" : also boot like nomal I cannot get into bootloader/fastboot mode to unlock it with fastboot command on my computer (with my phone plug in though usb).

Hey guys, last year I asked if I can unlock the bootloader and root my phone without the permission code from Huawei (which they don´t offer anymore) and didn´t get any positive response. Now I looked again and it seems they removed this code since EMUI 9.1. So I searched for any conformation and just found this https://ministryofsolutions.com/2021/08/huawei-p30-lite-bootloader-unlock-mar-lx1a-lx1m-lx2a-lx2b-lx3a-al00.html They offered unlock codes before as far as I know, but they don´t do it anymore. I saw some sketchy videos on youtube with p30´s with custom os installed, but I´m absolutly not convinced of it. I don´t want to brick my phone so does anyone of you guys have some experience with it since 2021/22 or just can confirm that it is indeed possible ? I searched on XDA as well, but I couldn´t find any post since 2020. Thanks for help

I am mainly a macOS user but I have a desktop with Windows that I occasionally use. Now I wanted to try Linux and decided to install Arch on a thumb drive using the GUI Installer. Everything went well. I managed to boot on the iso thumb drive and then I went ahead and selected another thumb drive for the installation. In the beginning it went very quick but it is stuck on the boot loader for hours now. Is that normal or is something wrong? Thank you very much for you help already :)

Hi guys, last year I tried UBUNTU and I loved it, I had it installed on a 100GB partition on my laptop's 1TB SSD and was really enjoying learning about Linux and how to use the terminal. One day I allowed windows to update and it wiped my ability to duel boot into UBUNTU, in what was basically a tantrum I deleted and cleared the partition back to normal but I miss tinkering!! Could someone please ELI5 how to prevent windows update from ruining my fun and my ability to duel boot into Linux - I want to be able to Duel boot and I want UBUNTU on a small 50-100GB partition but I am open to any and all other suggestions. Thanks so much in advance. J

I am try to put /e/ os om my motorola edge 30, but i have messed it all up. I was flowing this https://doc.e.foundation/devices/dubai/install I got to 'Temporarily Booting a custom recovery using' i did [adb reboot bootloader] and somthing whit adb but i dont know what. So now i cant start or reset the photo its in a boot loop i see the MOTO logo and it stuck. Can some on help me put a new os on the phone?

Is there a reputable guide on how to install TWRP on the Samsung Galaxy A71? Because all I found was a guide by "Myphoneupdate.com" and I'm not quite sure if they're to trustworthy. I also couldn't find a guide on XDA for this.

How can I replace the background on GRUB2. I've been looking all over the internet but nothing seems to help. It's annoying because I hate seeing such a bland bootloader. The image I'm trying to make as the background will be attached. I'm still new to the workings of Linux and GRUB.

on a Oreo Nexus 6P. No matter what I do, I get to this point and nothing shows my device as fastboot. I've tried everything I can find on the internet. Ive reinstalled drivers. I've reinstalled while at the fastboot menu (Power button+vol. down). I've tried it on two different PCs. USB 2.0 and 3.0. I've tried it in recovery mode, regular mode. I've tried all the drivers out there and driver installing tools. I've done this on a windows 10 machine and a windows server 2016 machine, same results on both. No matter what I do my device never lists in fastboot devices and because of this I can't flash anything or unlock bootloader. My device manager looks like this Im so stuck I don't know what is wrong. Can anyone provide some help? First time doing this is it a dumb mistake? It always lists when I do adb devices but never for fastboot.

My Nexus just shut down unexpectedly (happened a couple of times earlier but not this way) after launching the Google App. I don't know that the problem occured specifically in google app only or was by chance. Tried entering into the bootloader but recovery mode is not opening and the device status is showing up as locked. No bootloader options working (except power off). battery level was 52% during its boot crash. Is this a sign of ultimate software failure like corrupted OS or can be resolved (without affecting my personal files)?

Hi All, My grandfather recently got a new desktop that is installed with windows 10 (which he likes) to replace his windows 7 computer from 2008. He has had conflicting help from several people in regard to transfering data (because he knows all the folder names, programs, etc in his old computer). Rather than transfer data, I simply added his old hard drive to his new computer (so the new computer now has 2 HDD's). Now, he can access all of his old files from file explorer> my computer>OS:F. However, I (and He) would like to dual boot his new computer with both windows 10 (which is installed on the new hard drive) and windows 7 (which is installed on the older hard drive, which is now in the same computer). I attempted to use EasyBCD, but his new computer's windows 10 installation was running in UEFI mode, which caused several problems when attempting to dual boot windows 7 (installed under legacy mode). How should/can I fix this so that I can use a bootloader to let him pick between windows 7 and windows 10? (The ones he already has installed with programs and files). NOTES: -These are not custom built machines, both are Dell Studio XPS with proprietary hardware/drivers (for the most part). One from 2008 with a 1st gen i7, the other from 2016 with a 6th gen-skylake i7. -The reason for dual booting is because he adores windows 7, but likes windows 10 and is slowly becoming more familiar with it. He often needs to go back to 7 for certain tasks. -He is NOT computer literate in any way. -Switching the bios from UEFI to Legacy allows me to boot into windows 7, but I can't boot into windows 10 (Changing the boot order yields the error "No OS Detected"). -Currently, the only way I can switch back and forth between 10 and 7 (that I know of) is to switch the BIOS back and forth between legacy and UEFI. Thanks in advance!

Sooo... i"m having problems with re-locking bootloader on moto z play i tried the standard lock command in adb and it said : but that option is gray shaded and locked because plz help

This problem started a few weeks ago : PC randomly freezes (maybe once in a week or more), becomes completely unresponsive and has to be powered off. After that windows can't be booted. It tries to repair the system but always fails. The only thing that helps is plugging in an USB drive with windows image and entering these commands in command prompt: bootrec /FixMbr bootrec /FixBoot bootrec /RebuildBcd After this windows starts working. I've tried formatting my SSD and performing a clean installation a few times but still the problem persists. I've checked SSD with Samsung Magician and it's healthy. Also ran Windows Memory Diagnostics tool to check RAM and it had no errors. I tried using memtest86 but my PC just can't boot it. (boot priority is correct and it tries booting from flash drive but ends up stuck on a black screen with a flickering underscore). My RAM usage seems to be high most of the time (85%+). And after reinstalling Windows a new partition appeared out of the blue. It seems to be from my SSD and is only 500mb. Any ideas what is going on with my PC? Specs: OS: Windows 10 64-bit Motherboard : P7P55 LX (LGA1156) CPU: Intel Core i7 870 @ 2.93GHz Storage: 465GB Seagate ST3500418AS ATA Device (SATA ), 232GB Samsung SSD 850 EVO 250GB (SATA (SSD)) (Windows installation) Graphics: NVIDIA GeForce GTX 970.

I just installed linux mint debian edition 3 (cindy) on a different partition from my windows installation and I went to the default option of putting the linux bootloader on dev/sda. But windows its not listed when I turn on the pc. If I check my bios on the boot priorities I can see that the linux bootloader is set as the first priority and the windows bootloader is set as secondary, if I change this I can boot into windows. Both operating systems work fine. How can I fix this? how can I make windows appear listed on the boot options of the linux bootloader

How can I unlock realme 5 pro bootloader? The app provided for accessing the option is called indepth testing but it doesn't work on the latest Android 10 update (I think it's for Android 9 and is not yet updated for 10 but who knows how long that might take) and without it I cant find a single way to unlock the bootloader

Hello there! I wanted to unlock the bootloader of my Xiaomi Redmi Note 5 (the global version, aka AI dual camera, the more confusing your naming scheme is, the better, right?). Not necessarily to flash a different ROM, but according to a tutorial I found, it is possible to enable Camera2 API, which is, for some reason, disabled on this device, despite being enabled on most other, often even cheaper devices. Doing so requires an unlocked bootloader. I've done everything according to this tutorial (https://c.mi.com/thread-1635834-1-1.html), up until the step where you connect the phone to your PC. Unfortunately, the program was unable to detect my phone. The tutorial says that if this happens, you need to install the USB driver. So I've done everything according to this other tutorial (https://c.mi.com/thread-1625831-1-0.html), again, up until the step where you connect the phone to your PC. However, computer management doesn't detect it either. There should be an Android device under the other devices tab, but for some reason, all it can see is an unknown device, which is probably my old webcam, for which I don't have a driver either. Updating its driver with the file I got from the Xiaomi website doesn't work, obviously (but I tried anyway, just in case). Also, the MI unlock app has a driver install feature, which apparently does nothing. When I try to use it, it prompts me to connect the device. If I connect it while it's on, it says something, but closes immediately, giving me no time to read it, so I've made a screenshot before it did. It asks you to switch your device to fastboot mode and then connect it to your PC, which makes sense since the tutorial on their website requires this as well. Unsurprisingly, doing so does nothing and the app is still unable to detect the phone. Seriously, as much as I like Xiaomi, F them for this! Any advice on how to make it work?

I own a corsair m65 pro RGB. it randomly stopped working overnight. this is my support ticket to corsair: my m65pro rgb was working perfectly fine last night, today it randomly stopped working. After doing some research i found people saying that it might be stuck in bootloader mode. I've had the mouse for 7 months and its been perfectly fine till now, CUE does not detect anything, the mouse rgb doesnt light up and nothing works. i can see the laser light up on the sensor but its really dim. I've tried it on another PC and it doesn't work there too. under HID devices in device manager i see :Corsair composite virtual input device" it stays even after unplugging the mouse. windows does not make the device connected or disconnected sound either. thanks after a few emails back and forth, i got the instructions to hard reset the mouse, I'm posting this here so if anyone has a problem they can get it fixed without giving up and buying a new one(I've seen people have the same problem and then abandon the mouse). if your mouse does the same, please contact corsair support and you should have a fix for it pretty quick(you'll have to replace the firmware file through some steps). good luck note: I'm not a corsair employee. I'm just sharing my experience to help other people.

So yesterday i came across the problem where i deleted my 50GB partition that was reserved for Linux. I was thinking at the time i should reverse the boot loader over at the Ubuntu terminal, because the way i got into Ubuntu first time about a week ago is if i setup the bootloader to launch grub via command from Windows CMD, and it actually took me to the GRUB Screen so i was able to launch linux from that, but long story short i didn't think of reversing that in the terminal and after deleting the Linux partition in windows and restarted(WHICH I WAS SO STUPID, i knew the consequences was coming to me), i messed up my EFI boot loader and i couldn't get into windows anymore, and i tried every single Boot rec and BCD command out there on the forums of different variety websites. So how can i avoid screw ups like this is in the future so i don't have to reinstall windows cleanly on my SSD? And Also, the Linux partition was separate from 1TBB HDD, so it wasn't even near my SSD windows installation at all, but i still had to reinstall windows and i couldn't really successfully fix the windows boot loader.

I'm using a cheap huawei phone ,while I'm putting aside money to buy a new phone, (Y5 2018 DRA-L01) and the performance is literally unbearable, huge stutters, phone becomes inrensponsive really often, has a hard time picking up Wi-Fi signals and the UI is really slowing the phone down. Because of all of these reason I decided that it's better to change the OS and then reinstalling the stock ROM before selling it. However I can't find the Bootloader Unlock Key anywhere, since Huawei stopped sending them, and the only solution seems to be to pay 35$ - 55$. Is there any way I can do this for free?

Hello guys recently I tried to unlock the bootloader on my old Lenovo Vibe K5 Note(a7020a48) to Install twrp recovery and then root the phone with magisk. I have done everything in other forums to install unlock the bootloader but everytime I try with adb platform tools it shows the following error: FAILED (remote: download for partition 'recovery' is not allowed) Can anyone tell me how to unlock the bootloader thanks in advance! <3 NOTE: OEM UNLOCK is enabled / USB debugging too I've preformed a factory reset on the device and the error still persist