Related
The only way that I've found to allow Windows to recognize more than just the first listed SD partition is to install drivers to make the card a Local Disk instead of a Removable Disk.
This would be extremely useful for users who run the SD version of CM7, where the image creates a four partitions with the 4th being all of your user data.
Here is the tutorial on how to modify and install the Local Disk drivers:
http://www.getusb.info/usb-hack-turn-a-usb-stick-into-a-hard-drive-or-local-disk/
In theory, if you use a USB to SD adapter, this should work, but it's not working for me. I thought all XP drivers were compatible with Windows 7, but maybe that isn't correct.
Anyone else want to give it a shot?
Ahh, the old hitachi drivers. I posted a guide about them some weeks ago. They will work on Windows 7, just not the 64bit version of it. Where exactly are you having problems with it?
Sent from my 8086 using xda retrograde.
I have problems exactly where you say. It seems that the drivers aren't compatible with my 64bit operating system.
Any chance I could modify the driver to make it work?
Solar.Plexus said:
The only way that I've found to allow Windows to recognize more than just the first listed SD partition is to install drivers to make the card a Local Disk instead of a Removable Disk.
This would be extremely useful for users who run the SD version of CM7, where the image creates a four partitions with the 4th being all of your user data.
Here is the tutorial on how to modify and install the Local Disk drivers:
http://www.getusb.info/usb-hack-turn-a-usb-stick-into-a-hard-drive-or-local-disk/
In theory, if you use a USB to SD adapter, this should work, but it's not working for me. I thought all XP drivers were compatible with Windows 7, but maybe that isn't correct.
Anyone else want to give it a shot?
Click to expand...
Click to collapse
What happens if you install a 32-bit Windows XP virtual machine on you 64-bit system. Would that allow you to use XP the drivers?
I don't have an XP .iso handy at the moment to run in VirtualBox, but I'm going to test this on an XP OS and a Windows 7 x86 OS within a day or two.
Solar.Plexus said:
I don't have an XP .iso handy at the moment to run in VirtualBox, but I'm going to test this on an XP OS and a Windows 7 x86 OS within a day or two.
Click to expand...
Click to collapse
You can download the XP Virtual Machine from the Microsoft web site -- it's free.
PJLLB said:
You can download the XP Virtual Machine from the Microsoft web site -- it's free.
Click to expand...
Click to collapse
Except I didn't pay Micro$oft the big bucks for Professional or Ultimate. I'm running Home Premium on my desktop which doesn't allow XP Mode. Stupid Windows...
I will check it using another OS shortly.
If you're going to use a virtual machine, then why don't you just use Ubuntu? It will mount everything just fine.
slgooding said:
If you're going to use a virtual machine, then why don't you just use Ubuntu? It will mount everything just fine.
Click to expand...
Click to collapse
Because they want a solution which doesn't require dual booting and is immediately available. Unfortunately the crap support for other file systems will continue to be a big problem for them. (EDIT: Or did you mean to run Ubuntu in a virtual machine?)
Running Ubuntu or PC-BSD or any other more FS robust OS in Oracle's VirtualBox (which is free and relatively easy to use) is probably the best solution for many here.
I know all partitions and all file systems mount in Ubuntu, but the point of this is to get multiple partitions to be readable/writable in Windows, since the majority of users run this as their main OS. The idea of running XP in a virtual machine was simply to check and see if the drivers were compatible; the idea was not meant to be a permanent solution.
As for Windows mounting Linux file systems (Ext2 and Ext3 specifically), this would be my next step. I believe the solution does exist. Check out the freeware Ext2IFS and ExtFsd if you're interested. I haven't gotten the chance to try them because I'd like to get multiple Microsoft partitions readable first.
Anyway, after trying a USB drive and a SD card in an MMC reader on both a 32bit Windows 7 Home and XP Home this morning, I have not been successful.
I can confirm that the USB Local Disk drivers are in fact compatible with both of these operating systems, but Windows is still recognizing the drives at Removable Disks instead of Local Disks. I will try to work on it a bit more in a little while.
Total Commander has support for ext bases file systems.
So, can cm7 use an ext sd file system just like fat 32?
slgooding said:
Total Commander has support for ext bases file systems.
So, can cm7 use an ext sd file system just like fat 32?
Click to expand...
Click to collapse
I believe so. In fact, the SD card version of CM7 final uses two ext4 file systems, one of them being the partition used for the "internal storage."
Solar.Plexus said:
I believe so. In fact, the SD card version of CM7 final uses two ext4 file systems, one of them being the partition used for the "internal storage."
Click to expand...
Click to collapse
I'm able to manually mount the sdcard as ext4, however CM7 doesn't recognize the sdcard, and won't mount it for me.
Does anyone know what we need to change to get CM7 to recognize an ext4 sdcard?
Thanks!
Little bit of a thread hijack going on, but that's okay.
Is your vold.fstab mounting the correct partition?
Okay, so I got all the different partitions of my SD card to mount this morning, even an Ext3 file system. I might do my own How-To later for the CM7 users on here and so that it appears using more tags in someone's Google search.
Solar.Plexus said:
Okay, so I got all the different partitions of my SD card to mount this morning, even an Ext3 file system. I might do my own How-To later for the CM7 users on here and so that it appears using more tags in someone's Google search.
Click to expand...
Click to collapse
Sorry for resurrecting an old thread but I need to know: Did you ever document somewhere how you got this working under Windows 7 64-bit?
I'm in the same boat as you, needing to be able to mount and read an ext2 partition on my Windows 7 64-bit. I've got the necessary drivers that'll let me read ext2 and above but having access to that 2nd partition while the card is in my Windows laptop is where I'm stumbling.
Any pointers would be much appreciated.
In fact, I actually did manage to find the drivers for x64 Win7. Check out post #7 of this thread right here to see the details.
Im fully aware that this is more for the development of the Ubuntu Touch, yet because I wanted to start developing, I ended up attempting to dual boot Ubuntu 13.10 alonside Windows 8 to create a proper developing enviornment to learn more about kernel/AOSP build development. VMs wont cut it, as I was advised.
I ended up being able to dual boot Ubuntu 13.10 alongside Windows 8. I had troubles creating a partition for Ubuntu and seemed to have accidentally formatted the biggest drive, which I believe was where the Windows 8 OS was stored. I successfully put Ubuntu on there, installation working smoothly, or so I thought. Upon restart, I entered the GRUB boot selector. I first attempted to enter the Ubuntu OS, which brought me to a black writable page. I restarted the HP and tried booting into Windows 8. It gave me the error that the OS is missing. Now Im stuck in the bootloader and cant access my PC. I have an HP Dv6-6033cl laptop with a 750 hard drive I believe. Any help is appreciated.
Ouch.
If you formatted the Windows partition from NTFS over to ext3 and put Ubuntu on that partition... You've pretty much guaranteed you'll be starting over from scratch.
Ouch.
Before doing anything drastic, get a friend to burn a copy of System Rescue CD for you. Enter Bios and set Boot from CD as the first choice, then boot the Rescue disk. Inspect your drive with the G-Parted tool and find out where you stand with the various partitions.
If your Windows (the partition all the way to the left in the GUI) was indeed formatted to something like ext3, I'm not sure what can be done. If it is still NTFS and you have a Windows CD you can attempt a repair. There are programs out there that will help recover lost files if you can restore Windows, such as iCare Data Recovery.
Did I say "Ouch?"
Ouch.
It may just be a bad flag in the GRUB. Let's hope so. Otherwise... Ouch.
Well this is what it looks like so far:
I know I have two options; completely boot Ubuntu OS or Windows. Only issue is, Id rather not lose all my data.
*Please note - I am not IT trained - this is my amateur advice as someone who has had similar issues. Others (including trained persons) may have wildly different opinions on how you should proceed. I offer this advice in hopes it helps you recover your computer. I can make no guarantees. Proceed at your own risk. This is in no way superior to seeking a qualified repair at a reputable shop which would be the optimal solution.
OK it looks like you didn't overwrite/reformat your Windows partition. It does have issues. (It's labeled sda1/system.) The boot flag is missing, That's likely a bad GRUB install. The used and unused numbers don't add up so it's not being read correctly (possible damaged registry). sda4 is most likely the factory recovery partition for Windows.
Did you make a Recovery Disk? Tell me you did and you can find it...
If it was me, I'd do the following.
Insert your Recovery Disk and attempt a Windows repair
Assuming you can boot into Windows after the repair: make a full set of Backup disks
Make note of how much space Windows and associated program/files are using on the hard drive - you'll want this for reference later
If you have a Recovery Disk and a set of Backup disks you can get back to where you are at any time
Boot into System Rescue CD again, start GParted and begin work on your partitions
Your partitions are nonsensical - partition sda2 (Ubuntu) is only 200 MB which is way too small to be of any use for a working OS, you should probably wipe out partitions sda2, sda3, sda5 and the unallocated space - if it were me I'd take out sda4 as well (you have Recovery disks and you want that space)
Format all the partitions you are reclaiming as NTFS (for now) - Merge all contiguous partitions
Now you can make two separate and distinct choices:
EITHER
A) Keep your Windows install (sda1) and move it to the beginning of the drive (left side of the graphic representation bar) - Moving can cause data corruption (so they warn, but I didn't have an issue when I did this) - moving the partition will save you a lot of time
OR
B) Erase your current Windows by formatting sda1 as a new NTFS partition and merging it with the other space - you should then have one seamless NTFS partition - Use your Recovery and Backup disks to reinstall Windows and recover program/files - This takes longer, but a clean install is always nice.
If you use A) from above, you should have a free 124 GB partition at the end of the hard drive for your Ubuntu install. You can format it as ext3 or ext4 (using GParted) before installing Ubuntu... Or you can just let Ubuntu format it during the install.
If you use B) from above you should decide how much space you want for Ubuntu. Leave enough room for Windows to grow, but give ample space for Ubuntu as well. Create a new partition at the end of the drive in the size you've chosen for Ubuntu and format it as ext3 or ext4. Install and recover Windows files/programs to the NTFS partition at the beginning of the hard drive. Install Ubuntu to the ext partition at the end of the hard drive.
Good Luck!!!
I ended doing a full boot of Ubuntu, since I formatted my Windows 8 partition. I messed up pretty badly, but doing a full install of Ubuntu saved my computer. Unfortunately, I did lose my files. I believe so anyway. Thank you anyway. I will keep this tabbed and refer it to anyone that ever has any issue as I did!
xTurtlex said:
I ended doing a full boot of Ubuntu, since I formatted my Windows 8 partition. I messed up pretty badly, but doing a full install of Ubuntu saved my computer. Unfortunately, I did lose my files. I believe so anyway. Thank you anyway. I will keep this tabbed and refer it to anyone that ever has any issue as I did!
Click to expand...
Click to collapse
According to the screen cap you showed, it looks like Windows is still salvageable... Or did you do something else after the screen cap was snapped?
I completely formatted the hard drive to run Ubuntu. I doubt its salvageable without a huge fee.
RumoredNow said:
According to the screen cap you showed, it looks like Windows is still salvageable... Or did you do something else after the screen cap was snapped?
Click to expand...
Click to collapse
I came across a forensic tool called TestDisk. I have an external hard drive I can use to back up all my lost files onto. Viable solution?
Ok just advice if your installing Ubuntu. When you get asked how u want to install ubuntu always hit 'something else' that's the safest way.
If u have windows installed ... then I feel sorry for you lol
After installing ubuntu on another partition on windows hdd you find only ubuntu is able to boot
Why not just edit grub config,
Add
Title windows
Set root='hd*,msdos*'
Chainloader +1
That will add an option under ubuntu boot screen [grub] to boot windows boot loader [dual booting]
Partitioning advice;
The reason to separate so much is iit makes it 100x easier to restore/backup if something goes wrong. [Ubintu once gave me an error after fresh install using a disk]
sda1 /boot
sda2 /
sda3 /home
sda4 /swap
sdb1 windows
sdb2 storage space to share between OS's
sd** [only good if you use linux alot] extra hdds in a lvm [turns all spare hdds into one folder e.g 1tb 500gb 250gn hdds will become a 1.75tb folder]
Another example of why to hate Windows 8. They started securing the boot loader to make it extremely difficult to dual boot another OS with it. I used to like Windows but it seems to get worse with each iteration.
Sent from my SGH-M919 using xda app-developers app
lalec said:
Another example of why to hate Windows 8. They started securing the boot loader to make it extremely difficult to dual boot another OS with it. I used to like Windows but it seems to get worse with each iteration.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Yup but its been crap since the original dos code was found in the bin.
So its been worthless from the start winxp was just about bare able.
Main problem with windows though is why should we have to pay for half ass work and then pay to patch up the holes with antivirus's
When I can install linux free be more secure and be free to change any part of os I please.
Sent from my GT-I9505 using xda app-developers app
Remix OS is mounting and writing to every partition on my computer. Is there a way I can stop this? I only wanted it to access two of the six partitions.
Drive 1 part 1: Ext 4 Linux root.
part 2: Ext 4 Linux home.
part 3: Ext 4 Large file storage.
Drive 2 part 1: NTFS Win 7
part 2: Fat 32 Remix (50 gig)
Part 3 Linux backup
I installed remix with only drive 2 connected. After connecting drive 1 and rebooting. Remix mounts and writes to every partition.
Thanks for any assistance.
I experienced this. I solved it by encrypting the drives of the other OS's. Not a direct solution, but it may help you.
All the best,
Dan
Thanks for your response. I thought of that, but it seems a bit of a pain to get around what should be a simple problem. If I do come up with a simple solution I will post it here.
If you use lvm for linux install. It won't mount.
Thank you for your response. I've never used LVM, but after reading about it it sounds like a great idea. Especially because I multi-boot 3 or more operating systems. I enjoy trying different flavors of Linux and other operating systems like remix OS.
We give a certain amount of trust to software Developers. When an operating system mounts and writes to every drive, to me it puts a big question mark in the trust category. That's why I got on top of this. I'm not suggesting that developers of remix OS are doing anything they should not , but the potential for abuse is there.
I think remix OS is an excellent project and I wish that developers much success. They need to give you a method of unmounting permanently drives on your system that you don't want it to access. Remix also needs to break its dependency on Windows. Right now it is part operating system and part windows program.
cssr said:
Remix OS is mounting and writing to every partition on my computer. Is there a way I can stop this? I only wanted it to access two of the six partitions.
Drive 1 part 1: Ext 4 Linux root.
part 2: Ext 4 Linux home.
part 3: Ext 4 Large file storage.
Drive 2 part 1: NTFS Win 7
part 2: Fat 32 Remix (50 gig)
Part 3 Linux backup
I installed remix with only drive 2 connected. After connecting drive 1 and rebooting. Remix mounts and writes to every partition.
Thanks for any assistance.
Click to expand...
Click to collapse
Hi if you have system R/W enabled you can simply go to root command line and type pm disable com.jide.filemanager
This has stopped the unwanted access for me. I use Solid Explorer instead.
Hope this helps
Well I feel like an idiot. I have not used fat32 in about 15 years ( running Win98 then ) I forgot about the 4g limit, so reformatted remix partition to NTFS and reinstalled. Also as sharktm pointed out there is a simple way to fix this problem.
http://forum.xda-developers.com/remix/remix-os/completely-hide-partitions-remix-os-t3482161
Is there any guide or tutorial on how to setup a dual boot when Remix OS for PC is already installed on primary partition and wanting to install a second OS (Windows) on remaining empty disk space (NTFS)?
You might find some hints here https://goo.gl/N9S9zE
---------- Post added at 08:01 AM ---------- Previous post was at 07:46 AM ----------
Should maybe add that the only diifference is that you will have to prepare the partitions using live media. Windows and Linux installers do the job, or GParted on a Linux USB-stick
The only difference with what?
You will want to shrink the partition to be able to create and format a ntfs partition on the disk space not needed by RemixOS. Don't think you can do that from inside RemixOS. If you already have empty space outside the RemixOS partition, you can just install to it - so then I don't understand you question.
Sent from my Nexus 9 using Tapatalk
hallergard said:
You will want to shrink the partition to be able to create and format a ntfs partition on the disk space not needed by RemixOS. Don't think you can do that from inside RemixOS. If you already have empty space outside the RemixOS partition, you can just install to it - so then I don't understand you question.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
Yes, that's correct: I already shrunk this space and NTFS formatted it.
If I install a whatever other OS there on this partition - let's say WIN7 - how will I be able to select from where my computer will boot up when tuning it on?
If my primary partition has Remix and the secondary Win7 - at some point I will need to make a choice with which one I want to boot up my computer, right? My question is: how do I manage this dual boot choice?
Because my main boot on primary partition is currently Remix (and not Win).
OK, now understand that the question was about bootloaders. Assume you are using Legacy MBR rather than UEFI GPT. Windows prefers to be in the first partition on MBR - which you can achieve by moving the RemixOS partition with some cloning app like Clonezilla, or by using GParted in Linux. But it is possible to have Windows in the second position: I would use the Ranish Partition Manager, which allows you to change the position of the boot flag right after the Bios https://goo.gl/1bLYEE
Yep, that's it!
Many thanks for your ideas and the excellent resource site I discovered at the same time.
It happens I installed Remix OS on a laptop's FULL 500MB HD... and now I somehow regret the move.
Simply because this is too much wasted space for Android and there is a lot of empty space that I can use for something else.
Before installing I only changed in the BIOS the UEFI to legacy, and this, as far as I understand, should be MBR probably.
So, at this point, everything works fine. I could leave it as is.
But as I love running into complications and learn from them, I try to find something to do with some 300 MB disk space Android will never need for what I'm doing with it.
So, I much like your idea of changing the position of the boot flag but first I'll need to have a closer look at your video and better understand the process.
And also want to be sure my disk is MBR, if I find a way to securely verify that.
What steps would you suggest taking at this point?
And what option would you rather suggest - moving Remix OS or using Ranish?
Sounds like MBR if you do not have an EFI partition. I would go for Ranish, but I think you should consider wiping the drive, installing Windows 7 (suggest downloading the free ISO which includes SP1 from Microsoft) and reinstall RemixOS. Moving the drive is a quite tedious task. Then you can decide which bootmenu to use. I never learnt how to put RemixOS onto the Windows bootmenu (as I think Linux Grub2 is so much easier), but I am sure somebody can tell you howto. Or use the RemixOS bootmenu - by the way, which one are you using now Grub, Grub2 or something else? Or use Ranish!?
After double checking, it appears my partition is still UEFI...
Seems I was wrong with that.
Many thanks for your help and I think I'll follow your advice and start over again...
PS: I currently use GRUB2
hallergard said:
You might find some hints here https://goo.gl/N9S9zE
Click to expand...
Click to collapse
Very helpful page, thanks for this!
Is there a way to convert a disk from GPT to MBR without losing data?
NO. But are you sure that your disk is GPT? Windows diskmgmt.msc or in Linux GParted.
Yes, 100% sure.
Maybe you should leave it as GPT. Main advantage for you would be quicker boot times and probably not having to reinstall RemixOS. How many partitions do you have? Which one is RemixOS and which is EFI? Do you see the grub2 menu (or is delay 0 sek)?
Sent from my Nexus 9 using Tapatalk
A single partition for Remix, the primary one.
Grub2 has a delay set to 0 but I can see it when I press F8.
So you have a GPT disk but have made a Legacy install, not a UEFI install. If you now make UEFI installation of Windows 7 you will probably not see your grub2 menu (even if changing the time) so you would loose booting into RemixOS. What you can do then is to reinstall RemixOS as a uEFI install on top of your present without formatting if possible. Just the same before reinstalling copy over the big data.img file to the Win-7 partition, and if you had to format, you can copy it back. data.img holds all your app installations etc.
I'm not sure I well understand. My disk is GPT and my PC's BIOS is set to support Legacy disks.
Remix was initially installed on a ext4 partition on the whole HDD.
Where is that data.img file?
In any case, my idea is not Win7 but, for particular reasons, I want to install WinXP at main partition and Remix on dual boot.
What would you recommend without, if possible, having to re-install all Android settings, data and apps?
The data.img file resides in the root folder RemixOS of the Remix partition. You can not see it from inside a booted RemixOS, but you can see it if your mount the partition from outside, easiest from Linux (could be from Live Media), but also from an active Windows partition (if you install a third party driver such as Ext2Fsd.exe).
I am not sure if you can install Windows XP on a GPT disk at all, not even in Legacy mode. You can always try, and if you do succeed you will be able to install Ext2Fsd, and copy data.img to your XP partition as backup.
In Legacy mode Win-XP would overwrite the drive's mbr which means that you could boot Windows-XP but not RemixOS. So how to add RemixOS to your Windows boot menu? I was thinking that if you install EasyBCD you would be able to add RemixOS as a Linux partition - but I am not sure if that will work. Probably this choice will be greyed out when EasyBCD notices that you haved a GPT disk. I never learnt how one are supposed to add to the Windows boot menu, using "Bcdedit" - maybe someone else can teach you.
So with Win-XP my advice is to redo from scratch and install Win-XP on the first partition of the MBR drive and RemixOS on the second.
Many thanks for your patience and sorry if I'm taking too much of your time but I find your comments very constructive and might also be helpful for other members here..
I now realize that my previous message was not very clear, and probably also not complete:
I was meaning that I wanted to start over again, by formatting my disk in MBR (2 partitions) and by keeping all my existing Remix settings and apps as they are.
For the first point, I think it's quite straight forward: I just format my disk and create 2 new partitions.
Knowing that I'll install WinXP on the first one and Remix on the second, what formats would you recommend for those partitions?
Then, for restoring my existing settings and apps, I understand that I'll need to copy and later restore at same location the file data.img - possible using a live boot USB such as Ultimate Boot CD (I prefer Windows tools)? I tried with Ubuntu Live USB but was unable to gain access to root...
I found some Android apps that are doing backup/restore of settings and apps data but your idea with data.img sounds better.
Will this single file do somehow the same job and contain all Android-Remix settings and app data+settings?
Now, the missing part of the instructions is what will happen next, after WinXP is installed at the primary partition?
How to install Remix on the secondary one and how to dual boot when turning the PC on?
I would really appreciate if you may follow-up with this. Many thanks!
I recommend NTFS for XP and ext4 for Remix.
Let me explain about data.img v. data folder. Remix is a kind of Linux system and the data and system folders will not function on NTFS or FAT32. Therefore there is the alternative data.img, one big bundle file with all the content of the data folder inside, this to be used when installing with a Windows system using the installer exe file. To get the data folder instead of the data.img you have to 1.) create a USB stick from the ISO file - I use Rufus.exe in windows 2.) edit the kernel command line (hit TAB) and add "INSTALL=1" and 3.) install to an ext4 partition. I usually prepare and format to ext4 beforehand, so I answer No to format, but you should format here. https://youtu.be/e-4lgdjT-4Q (the root folder used to be called RemixOS-date, but is now only RemixOS).
I have assumed that you have been using the official windows installer and thus have the big data.img file. And you have to rescue it before you format the disk, by copying the file, or cloning the partition (making a partition image) - probably in either case to a USB drive - to later reuse after partitioning of the drive. I would be interested to hear if you actually can install Windows XP on your present second partition, because if you can do that, it would be the easiest way to rescue the data.img file. And if you fail to install XP no harm is done.
Code:
Now, the missing part of the instructions is what will happen next, after WinXP is installed at the primary partition?
How to install Remix on the secondary one and how to dual boot when turning the PC on?
I suggest you do Remix first. Either restore the partition image and proceed with the XP installation. Or install RemixOS, do not add "INSTALL=1" but format to ext4, Yes to grub (and grub2 if asked) and yes to system directory as read/write, and when asked to Run Android or Reboot, choose reboot. Rebooting will probably not work, but don't worry, just proceed with the XP installation.
In XP copy install Ext2Fsd and EasyBCD. Start Ext2fsd and give the second partition and drive letter, say D:. You will now be able to mount D: and copy over the data.img file (replace if you managed to boot) to the RemixOS folder (don't need to this in the cloning case). Run EasyBCD and third down Add New Entry, then second tab for Linux, add a name RemixOS and choose the drive and tap add entry. Go back to second down Edit Boot Menu and change Count down to something like 6 seconds and save. Now try rebooting, you should get a boot menu, chose RemixOS. And if it is not working, contact me so that we can edit out the Remix boot menu file.
I am a pensioner with plenty of free time, so I am only glad to help out.
Thanks for this.
OK for "NTFS for XP and ext4 for Remix" but I'm bit confused for the remaining...
I initially installed Remix by following this guide.
So yes, it's the official Win installer.
Now, for the remaining I still don't get it on how to backup this data.img file or folder... and also what the next steps you suggest are.
I don't well understand what you mean by working from within XP.
First I don't have XP installed yet because I really don't know how to install it on second partition and second if I ever was able to do this without touching my current Remix installation why should I backup/restore the data.img file? I mean that makes sense only if I have to start over again.
So, I'm really sorry but I'm lost at this point.
For the time being, I only have a Remix installation that works.
What should I do next precisely?
I have been looking around the Linux community for the most perfect distro out there, that turns my old computer into a speed machine (unlike RAM hogging windows). I finally achieved it with Korin OS and Ubuntu (yes, I installed them both simultaneously to try them both) on an original windows Vista machine, because the only way to get to windows 10 from Vista was to create a bootable USB from Linux since I didn't have another computer laying around. Little did I know, I was wrong.
I used Gparted on a USB drive (my bios is set to read for other drives before it boots the internal) and ended up formatting my entire KORIN OS drive to NTFS, because that's windows.
Long story short, the reboot popped up with a rescue grub message and the command lines are too complex for me to understand, so I thought to myself... Why don't I just install Ubuntu 20.04 over it because that is the file system grub supports and I know how to use it.
Power button clicks, screen flashes, Ubuntu loads. Grub rescue is now gone.
Moral of the story: If you are wanting to go from Linux to Windows with a partition editor in UEFI or BIOS, split your SSD partitions to cut off the Linux distro at 15GB available and make the rest of it empty. Then format the empty chunk for NTFS and insert the windows USB. This will ensure rescue grub doesn't come up and you can easily use windows tools to unify the partitions after it is successfully installed and booted.
Thought I'd put my success story out there because I've read maybe 200 articles of people that don't know anything about it.
Thanks for sharing your experience
always dual boot windows and linux as newbie, you don't know what dragons are in linux