Database Develop

Booting a Windows 7/Vista/(XP?) Installation from a USB Key (Tutorial)

The following is meant to save you a lot of time, health and annoyance,
I've done this with both Windows 7 (x86 and x64) and Windows Vista.. didn't check XP.
Instead of burning 9000 bootable DVDs for every new OS/SP that's out... you can just boot your installation from a USB key. thus far, a 4GB one suffices for every operating system i can think of.
let's go.
1. run CMD
2. type "diskpart"
3. connect your USB Key
4. type "list disk" (you will see a list of all available storages)
5. type "select disk #" # being your USB Key drive number.
6. type "clean"
7. type "create partition primary"
8. type "select partition 1"
9. type "active"
10. type "format fs=fat32"
11. after the format is complete, type "assign"
12. exit all cmd windows and copy all files from your windows ISO to the key.
13. load your bios and set the USB key to be the first choice in the booting sequence. the installation should load...
14. cheers.
15. later.
P.S. I have a friend who's trying to write a Toshiba Flash BIOS version which can boot from SD.. this actually means that you'll have an SD card on standby with a windows installation and you'll be able to format your comp easily.
thankfully, if you have a 4GB one, you'll also be able to create a small data image of your comp with a few applications.. and maybe some outlook data/bookmarks.
I don't trust he'll be successful with this.. and not because i distrust his abilities but because this is EXTREMELY hard to do. Hope is always welcome tho.

Thanks!
Thjis is very usefull info
I´ll try to install windows 7
Cheers,

Whoever tries Windows 7, go for build 7100. DO NOT INSTALL 7105,7110 or 7068!

Also, the installation using the USB Key turns out to be about 1.5-1.7 times faster than from a DVD.

A similar method (SD card) I used to install Win XP on my netbook. I can tell you one thing though, it's not the easiest thing to do on a computer
Cheers

Please write how you did that. thanks

nir36 said:
Please write how you did that. thanks
Click to expand...
Click to collapse
I'll do but for the moment I'm at work.
Ok, I'm back from work and apparently something is wrong with xda server (page loades very slow) and I can't upload the procedure, so it's going to be a long page.
This procedure worked for my Asus 1000H (I have tried two other methods and failed) and what is more important, I found it on internet, so it's not my procedure.
"Here's a good guide to installing Windows XP on your EEEPC.
Hardware you'll need
1.) A USB memory key. 1GB is recommended, but if your going to use a custom nLite installation of Windows XP, then you can get away with a 512MB one.
2a.) A SD Memory Card. Any size will do, even if you have a 16MB one laying around, that's heaps.
OR
2b.) A Second USB memory key. Any size. (It should be noted I've only tried this with the SD card option)
3.) A Windows XP SP 2 Installation CD.
Software you'll need
1.) Download physdiskwrite. A small utility to use for creating a boot disk for our XP installation.
http://m0n0.ch/wall/physdiskwrite.php
2.) A boot disk image.
http://freepctech.com/pc/002/files010.shtml
Grab the one called 'MS Windows XP System Setup Disk'.
Step 1: Creating a SD boot disk
Create a temporary directory on your PC and unzip physdiskwrite.exe into this folder.
Using your file compression program (WinRAR, WinZip, 7Zip etc) extract the file "WXPBOOT.IMA" to the same folder as physdiskwrite.exe.
NOTE: The wxpboot.exe is not an archive, programs such as WinRAR may throw an error, but still extract at least 'WXPBOOT.IMA'.
Insert your SD or your 2nd USB memory key into your PC.
Next go to into disk management of your PC by going into:
Control Panel --> Administration Tools --> Computer Management --> Disk Management
Make a special note of the drive number (not the letter) of your SD card or USB memory key.
Next open a command line and navigate to your temp directory where physdiskwrite.exe is located.
Type: physdiskwrite -u wxpboot.ima
WARNING: It will list all of your drives and ask you which one you want to write to. BE VERY CAREFUL HERE.
You need to make sure you aren't writing to any of your actual hard disks.
It should only take a few seconds. This device becomes your 'boot disk'.
Step 2: Copying XP to your USB memory key
Take your windows XP installation CD and stick it in your DVD/CD drive.
Copy the folder 'i386' to your USB key (the first one, not the one you put your boot disk onto).
If you are using a standard XP SP2 CD without using nLite, it will be around 550MB to put on.
I'd highly encourage anyone doing this to grab nlite at http://www.nliteos.com to cut down the size of your Windows XP size.
Remove unwanted or unneeded utilites and applications to save room. (I was able to cut the CD size down to 325MB without to much sacrifice).
This USB key becomes our 'Windows Disk'.
Step 3: Preparing EEEPC
Insert your SD boot disk into the SD card slot, or USB port if it's a memory key.
Boot your EEEPC and go into it's bios by hitting F2 when it first switches on.
Change 'OS Insallation' to 'Start'. Hit F10 to save and exit.
As soon as the EEPC restarts hit escape to load the boot loader.
At the memu choose either your SD card if you used that, or the USB mem key.
It shouldn't take long and at some point will ask you to hit any key to continue.
When you finaly reach a command prompt you should see:
'A:\'
Type: fdisk
When asked if you want to enable large HDD support just hit Y or enter.
It should show several non-DOS partitions, and a DOS partition named BIOS. We want to wipe all these.
Once you've wiped all three partitions create a new partition DOS partition. Save and exit.
Restart your EEEPC (ALT+CTRL+DEL will do the trick here) and boot back into your boot disk again.
This time at the command prompt:
Type: format c: /s
Once it's formated ensure that the boot linux boot loader is gone by typing:
Type: fdisk /mbr
Your SSD should now be bootable to DOS without a boot disk.
Step 4: Installing XP Pro
Insert your Windows USB memory key into the left hand side USB port . The reason for this is that the boot disk assigns this port as 'D:\'.
Reboot your EEEPC back into the boot disk. Once there:
Type: d:
Type: cd i386
Type: winnt
The Windows XP installation should start. The first part will be windows copying temp files to your SSD drive.
Windows may ask you where the i386 folder is. Just make it's pointed to the 'D:\i386' directory.
When it's finished copying these files and is about to reboot, remove your USB memory key/s, and or SD memory card from the EEEPC as you won't require these anymore.
Reboot your EEEPC. You should see a windows boot loader appear that shows:
Windows
Windows XP Install/Upgrade (Or something to that nature).
Just let it boot on it's own, it will automatically start the next phase.
Now you should see the normal Windows XP installation start. When it asks you would you like to convert your HDD to NTFS, you should say yes.
From that point on, it should be a normal XP installation.
Once it's complete and booted into windows the first time, restart the EEEPC, go into the bios by hitting F2 and change 'OS Installation' to 'Finished'.
It's recommended to install the ACPI driver, and then the chipset driver before other drivers.
Hopefully by this stage your in your fully functioning Windows XP EEEPC!
Just remember if you want to return at anytime back to the original image, you can create a new bootable restoration disk from the included EEEPC DVD.
One last thing. To remove the boot loader at the start of loading windows (where it asks you where you'd like to boot) go to:
Right Click My Computer->Properties->Advanced->Startup and Recovery
Make sure "Windows XP" is your default OS, and untick the "Time to display list of Operating Systems."
The EEEPC will then boot straight into Windows."
Cheers

thank you very much

Official ubuntu 12.04 for nexus 7

Hey guys, Today Ubuntu was released for the nexus 7 for both 16GB and 8GB models, it obviously requires unlocked bootloader but it is working! heres a guide i pulled form Ubuntu Wiki.
Leave Any comments below on sucess or fails!!!
I Will Be Posting up updates when newer versions are released.
Press The Thank Button if it worked for you!!!
-------------------------REMEMEBR!!! I AM NOT RESPONSIBLE FOR ANY BRICKS OR DAMAGES TO YOUR DEVICE!!!!!!-------------------------------
What you will need:
Nexus 7 Tablet (8GB or 16GB)
Standard MicroUSB Cable (should come with the device)
Ubuntu Nexus 7 Desktop Installer installed on your development system
Ubuntu 12.04 LTS or Later
Optional
Micro USB Host Cable (OTG Cable) - used for attaching keyboard, mouse, etc. Directions on how to get and use one of these are towards the bottom of this page.
Ubuntu Nexus 7 Desktop Installer
A simple one-click installer has been provided, and is available in a PPA.
sudo add-apt-repository ppa:ubuntu-nexus7/ubuntu-nexus7-installer
sudo apt-get update
sudo apt-get install ubuntu-nexus7-installer
Usage instructions for the installer are provided below.
Unlocking the Nexus 7
The Nexus 7 ships with a locked bootloader. You must unlock it in order to flash different images to the device. Fortunately, this is a trivial process, and you only need to do it once.
Warning: Unlocking the bootloader erases all data and resets the device to factory defaults.
Reboot the Android device into the Android boot loader. To do this, hold the volume down button and press the power button. Continue holding the volume down and power buttons until you see the boot loader UI. The device now displays the boot loader GUI, which looks like this:
Verify fastboot lists the device:
$ sudo fastboot devices
1234567891234567 fastboot
Start the bootloader unlock process:
sudo fastboot oem unlock
You are prompted on screen to unlock the bootloader on the Android device screen. Follow the on-screen directions to continue. Your screen should now look like this:
Complete the process by rebooting:
sudo fastboot reboot-bootloader
Or simply press the power button.
Installing Ubuntu on Nexus 7
Once all setup has been completed, the installation can start. To install, ensure the Nexus 7 is in fastboot mode, plug it into your computer (and make sure NO OTHER DEVICES are plugged in).
Find the installer in the dash (search for 'nexus'):
This will provide a Graphical Interface for installing Ubuntu. This tool will download the latest image automatically, and flash it accordingly. The flashing step should take about 2 minutes. Once the flashing is complete, the device will reboot and finish the installation. This step can take 10-15 minutes.
Returning your Nexus 7 to Stock Android
Warning: Disconnect ALL other mobile devices connected from your computer or they might get erased too. This will erase ALL DATA on your Nexus 7.
In case anything happens while developing, the system image for Nexus 7 can be found here: https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
After downloading the above tarball, uncompress it with the following:
tar zxvf nakasi-jro03d-factory-e102ba72.tgz
Then, place your machine into fastboot mode and run the resulting script:
cd nakasi-jro03d/
sudo ./flash-all.sh
You may get the following warnings, which you can ignore, the restoration will continue anyway.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
Troubleshooting the Install
If you have problems installing the image, please use the following troubleshooting steps:
Detach the USB cable, restart the tablet back into fastboot mode, and re-attach the USB cable.
If problems persist, reboot your host PC.
If you still have issues, try a different USB cable.
If you have a 16G tablet, try using the 8G image.
If you still have issues after doing all this, return the image to stock using the directions above and re-try.
If none of that works, ask a question on Ask Ubuntu using the mobile tag, or ask for help in the #ubuntu-arm channel on freenode. If you believe it's a bug, file a bug against ubuntu-nexus7 in Launchpad.

For Future Use
For Future Use

For Future Use 2
For Future Use 2

For Future Use 3
For Future Use 3

For Future Use 4
For Future Use 4

I know this question will get asked sooner or later.
So I will ask
Is there a way to get it working on Windows?

at the moment, a windows method is not avaliable to my knowledge, but when installing it, it downloads the images and i think you might be able to take the images from the install and run it though windows fastboot like normal, but again i have not tried. also performance is not bad, can be laggy at times but its fine to use. Cheers.

This has already been posted and you can just use fastboot to flash the userdata and boot img

This is a great step forward for linux however, Will this effect my CWM Installation?
I want to know if I can make a full ROM backup the current stock I have modded etc then restore it via CWM to remove ubuntu.

yes, at the moment it wiped my whole device and all, so make sure back everything up externaly first before doing this.

I use an RPM distribution, so I will wait a bit. But it is really interesting!!!!
And just for dream: next step: grub!

We already have this thread here
http://forum.xda-developers.com/showthread.php?t=1957561
...and you just simply copy/pasted this from here anyway:
https://wiki.ubuntu.com/Nexus7/Installation
Closed

unknown device in device manager

Hi
I have HTC one that couldn't be recognized by my pc
running under windows 7 by usb
I have : VId = 0000 and pid = 0000 in : le chemin d'acces à l'instance du périphérique :
USB\VID_0000&PID_0000\6&189D988F&0&4
knowing that I have installed the last version of HTC Sync manager,
usb debogging is enabled in my htc ,
sorry for my poor english
thank you for your help

hm911 said:
Hi
I have HTC one that couldn't be recognized by my pc
running under windows 7 by usb
I have : VId = 0000 and pid = 0000 in : le chemin d'acces à l'instance du périphérique :
USB\VID_0000&PID_0000\6&189D988F&0&4
knowing that I have installed the last version of HTC Sync manager,
usb debogging is enabled in my htc ,
sorry for my poor english
thank you for your help
Click to expand...
Click to collapse
Take a look at FAQ Q#2 on getting your phone recognized.

majmoz said:
Take a look at FAQ Q#2 on getting your phone recognized.
Click to expand...
Click to collapse
Hi @majmoz
steel not finding my problem in this FAQ

hm911 said:
Hi @majmoz
steel not finding my problem in this FAQ
Click to expand...
Click to collapse
Did you follow the steps in FAQ Question #2? Can you use a different port, cable or computer? Depending on what you want to accomplish, you could use Linux on a USB!
HOW TO USE LINUX FOR FASTBOOT & ADB VIA USB
This guide originally posted by @Danny201281
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219​Linux is your friend; if your drivers are not working the chances of getting them working again without the phone booting are slim. But Linux doesn't need drivers to talk to your device.
Go here: http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3
Then go here: http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD
Then use these files to create a bootable Linux USB drive with at least a 2 GB persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from USB.
MOVING YOUR FILES TO UBUNTU
Once booted you should be at a screen with options to "Try Ubuntu” or "Install Ubuntu". We don’t need to Install anything so just choose "Try Ubuntu" and the computer will boot to the Ubuntu Desktop (If you get a popup saying "system has encountered an error" or something similar just cancel and ignore it, it should have no effect on what we need to do as it is due to missing Linux OS updates we don’t need). On the left of the screen you'll see the Dock. Open the orange folder icon near the top this is the Home folder. It’s where we need to put any files we need to work with such as a rom.zip you want to push to the device or recovery.img files for flashing.
To get your files here is a simple drag and drop process. In the top left of the Home folder you'll see the drive structure of you pc under devices. Choose your PCs hard drive and Right-Click then" Open in a new window". Locate your .zip or .img files and drag them into the home folder. Now wait for the copy process to complete and rename them for easier typing later, e.g., rom.zip, firmware.zip or recovery.img etc.
USING ADB AND FASTBOOT
First you need to install adb fastboot; this is easy just 3 commands in the terminal. Thanks to Webupd8 team.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Make sure your connected to the internet and press Ctrl+Alt+T to open the terminal then type or copy and paste the above commands one at a time waiting for each to complete their output. It may seem to have stopped at times but be patient when the prompt returns to normal enter the next command and when there all done you’re ready to use adb and fastboot.
Once you've moved all the files you need to the home folder that’s it you’re ready to go. Close everything down on the desktop (optional) and press Ctrl+Alt+T this will open the terminal now connect your phone with the USB cable. All fastboot commands need to have the "sudo" prefix added at the start, e.g.
fastboot flash recovery recovery.img becomes sudo fastboot flash recovery recovery.img
fastboot devices becomes sudo fastboot devices
However, adb should work basically the same as on windows. If you do have problems with normal adb commands adding “sudo” can help here as well.
Click to expand...
Click to collapse

No OS on phone! OTG USB / conncetion to PC not recgonized! Seeking Help

In the past 3 months or so I noticed that my Mi5 3GB 32GB is not recognized by my PC anymore. I didn't care too much because I hardly connect my phone to PC.
I was running the lastest xiaomi.eu Rom unrooted.
So on Thursday, I deleted my OS by mistake, therefore I do not get past the Mi Logo.
I can boot into TWRP Recovery & Fastboot however, there is not code when using CMD adb/fastboot devices such as 1cwe3f23.
Also, I read about the EOL method aka test point method, to force a connection as Qualcomm driver with no success. Different PCS dont recognize any drivers.
The battery is not an issue because I can easily charge my phone to 100% and it can hold its charge, therefore I do not think it is a battery related issue.
What i did so far :
- used 3 differenct USB C cables and PC -> phone still not recognized
- Installed all lastest driver on Drivers -> phone still not recognized
- tried to use the test points method -> phone still not recognized
- tried Miflash tool -> phone is still not recognized
- tried Mi PC Guide -> didn't work either
Then I read somewhere that I can use a OTG cable with a pen drive
- OTG storage is not recognized in TWRP recovery and cannot be selected. [OTG STORAGE 0MB even if different pen drives are connected]
SO my Main problem is not the phone itself, it is that I cannot get any data onto the internal memory because I can't get past TWRP.
Please help me out since I really struggling with this problem for the past 7 days and I'm desperate now for any kind of help.
Greetings and thanks in advance.

amando1991 said:
SO my Main problem is not the phone itself, it is that I cannot get any data onto the internal memory because I can't get past TWRP.
Click to expand...
Click to collapse
What do you mean by "can't get past TWRP"? Is it that you can't flash any ROM to system?
You have fastboot and TWRP, so things are likely fine. Rather than use Windows, you might have more luck running linux inside VirtualBox (plenty of guides around XDA). If you can sudo fastboot devices in linux, you should be good to go. Otherwise, the error reporting is often richer/simpler in linux.

Hi bro
same as me, 4 days ago...
system, vendor error
flashing stock rom miui9 via twrp
although the error twrap will only provoke usb computer,
if it works usb computer, try flashing by using miflash...
goodluck
Sory bad englis

moo113 said:
What do you mean by "can't get past TWRP"? Is it that you can't flash any ROM to system?
You have fastboot and TWRP, so things are likely fine. Rather than use Windows, you might have more luck running linux inside VirtualBox (plenty of guides around XDA). If you can sudo fastboot devices in linux, you should be good to go. Otherwise, the error reporting is often richer/simpler in linux.
Click to expand...
Click to collapse
I did as you recommended and used Ubuntu. However also there the system didn't recognize the phone when plugged. It may because I am not fully familiar with Ubuntu. I would appreciate if you could point me in the direction of a tutorial.
same as me, 4 days ago...
system, vendor error
flashing stock rom miui9 via twrp
although the error twrap will only provoke usb computer,
if it works usb computer, try flashing by using miflash...
Click to expand...
Click to collapse
could you be more precise please? How did you overcome not having a PC conncetion?
Currently, I am not able to transfer any kind of data to the phone either by PC or OTG. Furthermore, the internal storage is completely empty after wiping everything by mistake.
I have twrp working fine, but without any data on the device, I cannot use it. Also, the device only stays in fastboot for roughly 20 secs before it turns off.
any help is welcomed. Thank you
EDIT : I got Ubuntu to work but its the same process. My phone is not recognized and running the command adb devices gives me
"list of devices" .... thats not! Nothing ! usally there is the code Phones ID but nothing there

amando1991 said:
EDIT : I got Ubuntu to work but its the same process. My phone is not recognized and running the command adb devices gives me
"list of devices" .... thats not! Nothing ! usally there is the code Phones ID but nothing there
Click to expand...
Click to collapse
A number of different issues could be here.
#1 Firstly, ensure you've installed openvm tools and reboot. This should enable things like hardware pass through.
$ apt-get install open-vm-tools open-vm-tools-desktop
$ sudo init 6
Then, follow these instructions for the pass through (may be slightly different, but very similar) https://forum.xda-developers.com/showthread.php?t=570452
#2 Type "adb" and see what version is in use in the first line of output. If it's 1.0.0.32 or older, it might be an issue. Try installing the following packages:
$ sudo apt-get install android-tools-fastboot android-tools-adb
You might need to find a newer version elsewhere, Ubuntu repos are often old. Google around for 1.0.36 or newer. This could solve your issue.
#3 Ensure you have the necessary rules for the Mi 5. There's a few different hardware models. The Arch Wiki can walk you through it better than I can: https://wiki.archlinux.org/index.php/android#Connect_device (ignore the package hyperlinks, they're arch-specific). Only do this if you've properly configured the pass through from #1. Do F"igure out device IDs" and then "Adding udev Rules". Instead of the "udevadm" command run
$ sudo service udev restart
If you're still not detected, no idea.

moo113 said:
A number of different issues could be here.
#1 Firstly, ensure you've installed openvm tools and reboot. This should enable things like hardware pass through.
$ apt-get install open-vm-tools open-vm-tools-desktop
$ sudo init 6
Then, follow these instructions for the pass through (may be slightly different, but very similar) https://forum.xda-developers.com/showthread.php?t=570452
#2 Type "adb" and see what version is in use in the first line of output. If it's 1.0.0.32 or older, it might be an issue. Try installing the following packages:
$ sudo apt-get install android-tools-fastboot android-tools-adb
You might need to find a newer version elsewhere, Ubuntu repos are often old. Google around for 1.0.36 or newer. This could solve your issue.
#3 Ensure you have the necessary rules for the Mi 5. There's a few different hardware models. The Arch Wiki can walk you through it better than I can: https://wiki.archlinux.org/index.php/android#Connect_device (ignore the package hyperlinks, they're arch-specific). Only do this if you've properly configured the pass through from #1. Do F"igure out device IDs" and then "Adding udev Rules". Instead of the "udevadm" command run
$ sudo service udev restart
If you're still not detected, no idea.
Click to expand...
Click to collapse
Thank you again for the help!
Unfortunately, it appears that my device is still not recognized by either Ubuntu or Win10.
I Have taken the necessary steps to install Ubuntu and update the adb drivers (1.0.39) but still no luck so far.
It really pisses me off since I was stupid enough to wipe the internal storage ☹ and not I am not able to transfer any data to the devices again.
Any other out of the box ideas?

amando1991 said:
Thank you again for the help!
Unfortunately, it appears that my device is still not recognized by either Ubuntu or Win10.
I Have taken the necessary steps to install Ubuntu and update the adb drivers (1.0.39) but still no luck so far.
It really pisses me off since I was stupid enough to wipe the internal storage ☹ and not I am not able to transfer any data to the devices again.
Any other out of the box ideas?
Click to expand...
Click to collapse
You configured the USB pass through to your Ubuntu host? Double check you followed #3, and then run sudo fastboot devices. That step is tricky for some.
Reconnect your phone to your Ubuntu host (in fastboot) and run "dmesg -T", see what errors are present. If you have no errors, I would image it's a configuration issue. Other than that I'm out of ideas.

moo113 said:
You configured the USB pass through to your Ubuntu host? Double check you followed #3, and then run sudo fastboot devices. That step is tricky for some.
Reconnect your phone to your Ubuntu host (in fastboot) and run "dmesg -T", see what errors are present. If you have no errors, I would image it's a configuration issue. Other than that I'm out of ideas.
Click to expand...
Click to collapse
OMFG!!! First of all, thank you for support and your patience. I really appreciate it.
HOWEVER, all it was is that the USB PORT was full of dust( literally tons!) which appears to have allowed to charge the phone but seemed to have cloaked up some part of the responsibile for a usb connection to a computer.
Stupid me should have known this because the usb port was kinda wobbly which I had mistaken for degradation using the phone for almost 2 years
MANY THANKS!

moo113 said:
What do you mean by "can't get past TWRP"? Is it that you can't flash any ROM to system?
You have fastboot and TWRP, so things are likely fine. Rather than use Windows, you might have more luck running linux inside VirtualBox (plenty of guides around XDA). If you can sudo fastboot devices in linux, you should be good to go. Otherwise, the error reporting is often richer/simpler in linux.
Click to expand...
Click to collapse
Hey , I was researching about my issue and came up to this. I'd be really glad if you can sort me out with this. I have the same mobile , by mistakenly wiped out the phone including the internal storage , my pc does not detect the device , and whenever i go to fastboot mode to try something like miflash , it goes back to twrp after 15 seconds. Also , i tried several OTG's but none of them get detected on TWRP , and I am stuck on this thing for almost a week now . Please guide me on how to sort this out . i basically just downloaded adb files , miflash , etc from the internet and never reinstalled them. also i used several usb c cables to connect to pc and even then device manager does not detect it . thank you . i would really appreciate your reply.

*TUTORIAL* Install MacOS Monterey on Unsupported MacBooks

Hi
Here we go again
Lets install Monterey on Unsupported Devices
Disclaimer
I am not responsible if things on your end go downhill
Only use this method if your MacBook is not up to par with Monterey specifications
Prerequisites
MacOS Monterey Bootable USB
16GB USB
( Look at my other posts if you do not have the "Bootable USB" )
​SETUP​​
1. We need to download micropatcher from GitHub.. ( MicroPatcher Download )
2. Plug your boot-able MacOS Monterey USB Drive into the computer
3. Open up mac terminal and type sudo
4. Open up the micropatcher folder and drag and drop the ( Install-SetVars.sh ) file into the terminal and then you need to drag and drop the ( USB with Monterey boot drive ) on the desktop into the terminal and press enter key...
5. Once that finished, go back into the micropatcher folder, find ( Micropatcher.sh ) file, drag and drop into the terminal, and then drag and drop the USB on the desktop into the terminal again and press enter.
6. When that is finished, quit terminal and eject USB, and power off Mac.​
Click to expand...
Click to collapse
INSTALLATION SECTION​​
7. Now we are ready to install, Plug USB into mac, power on, and hold option key while the computer boots up.
8. Select EFI Boot and press enter key... Your Mac will shut down, power on again and press option key again while booting
9. Now select Install MacOS 12 and press enter.
10. Select Language and press arrow key
11. Click on Disk Utility and press continue.
12. Click on view (top left) and select show all devices
13. Now select the drive you want Mac OS 12 to install to and erase with the following parameters
Name- Macintosh HD
Format- APFS
Scheme- GUID Partition Map
Erase and click on done, then close disk utility.
14. Click on Install MacOS 12 and continue... Continue with the installer... Select Macintosh HD and continue...
MacOS Monterey Is being Installed Your Mac will restart Several times
Once Installed, continue with the initial setup until you reach the home screen
15. Now you will need to change the USB Stick name to Install macOS Big Sur
16. Open terminal window and type sudo, then open up USB and drag and drop ( patch-kexts.sh ) file into the terminal, press enter key, and type your password.
17. Once this has finished inside the terminal, YOU HAVE TO RESTART YOUR MAC​
Click to expand...
Click to collapse
We are done here
Till next time
Cheers
​

Really thanks!!!!
Gone try it as soon as I can and let you know how things went!

#mcl said:
Really thanks!!!!
Gone try it as soon as I can and let you know how things went!
Click to expand...
Click to collapse
Ok awesome. Just make sure you follow each step carefully

Ok, will be very careful

Hey!
Finally I decided to upgrade , and I am pretty happy for doing that. Even though I didn't expect this now animations are way faster, and Safari is so much faster. On big sur it lagged so much that I couldn't even use it.
However there is feature that I was hoping to be able to use but got unfortunately discover it just isn't available.
I would really like to have low power mode on my Mac, but it just doesn't appear any where in the OS.
What I found on the web is that it only works on early 2016 models and later.
Would it be possible for you to add a patch so they Mac thinks it's form 2016 so low power mode is available?
I think that way it should work but maybe you have a better idea...

Hey!
So I decided to install macOS Monterey on a 15" MacbookPro with dual graphics(in this case, I have the GT 750M).
I followed the other's guide you made and everything works great.
However as soon as I reboot into the USB, during the boot, the apple logo and progress bar glitches out and become tiny. This persists when I get into Monterey recovery everything is sill tiny.
Anyway I tried to continue and it seems to install the OS, however when it ends the installation, the boot screen never ends, it get stuck and I know the installation is complete because I can hear Macos voiceOver function, saying how to use if I need, but on screen I only see the loading bar and the apple logo. I tried restarting and nothing.
I also return to Big sur and then re do everything, got the same result.
Any help is welcome, and thanks in advance!

#mcl said:
Hey!
So I decided to install macOS Monterey on a 15" MacbookPro with dual graphics(in this case, I have the GT 750M).
I followed the other's guide you made and everything works great.
However as soon as I reboot into the USB, during the boot, the apple logo and progress bar glitches out and become tiny. This persists when I get into Monterey recovery everything is sill tiny.
Anyway I tried to continue and it seems to install the OS, however when it ends the installation, the boot screen never ends, it get stuck and I know the installation is complete because I can hear Macos voiceOver function, saying how to use if I need, but on screen I only see the loading bar and the apple logo. I tried restarting and nothing.
I also return to Big sur and then re do everything, got the same result.
Any help is welcome, and thanks in advance!
Click to expand...
Click to collapse
Well, I got to say I havent seen this happen before... its probably something to do with graphic divers compatability. I will do some research and see if I can find a fix for you.

Nameless Foe said:
Well, I got to say I havent seen this happen before... its probably something to do with graphic divers compatability. I will do some research and see if I can find a fix for you.
Click to expand...
Click to collapse
Ok thanks in advance for your time

#mcl said:
Ok thanks in advance for your time
Click to expand...
Click to collapse
No worries

Hey!
So finally the issue is finally fixed.
I tried to install Monterey using OpenCore legacy pacher and got the same result, however, it turns out I didn't see the warning when installing Monterey on this Mac(11,3). As it turns out when the installation is done you need to reboot in safe mode so the Mac don't use the Nvidia card.
Though, now with the latest version of OpenCore ( 0.4.7), it fixes that issue(on 0.4.6 you would have to reboot on safe mode).
Now when the installation is done it reboots it just and just works out of the box, and it automatically patches the system so you are able to use the Nvidia card without having to do extra steps.
So if anyone is interested in Installing Monterey on an unsupported Mac, visit their webpage, as everything is well documented, easy to follow and has an extensive list of supported devices.

Thanks for the news. When this guide was uploaded, this was the one of the earliest ways to get Monterey on unsupported devices