Related
I'm trying to upload an APK with ADB+Eclipse into a (real device) HTC Legend from a virtual machine with XP Pro guested on a real machine with Win7 x64.
I installed USB Driver, modified it to support HTC Legend, then set HTC Legend with USB Debug... in VM XP Pro I see into ADB the HTC Legend connected (I think so...)
Code:
C:\android\android-sdk-windows\tools>adb devices
List of devices attached
HT03SNX02682 device
I think that HT03SNX02682 is the serial number that ADB give to my device, correct?
Then I try to upload from Eclipse using run configuration of Eclipse...
but this is the log...
Code:
[2010-06-14 13:02:23 - HelloWorld21] ------------------------------
[2010-06-14 13:02:23 - HelloWorld21] Android Launch!
[2010-06-14 13:02:23 - HelloWorld21] adb is running normally.
[2010-06-14 13:02:23 - HelloWorld21] Performing android.helloworldapp21.HelloWorld21 activity launch
[2010-06-14 13:03:15 - HelloWorld21] WARNING: Application does not specify an API level requirement!
[2010-06-14 13:03:15 - HelloWorld21] Device API version is 7 (Android 2.1)
[2010-06-14 13:03:15 - HelloWorld21] Uploading HelloWorld21.apk onto device 'HT03SNX02682'
[2010-06-14 13:03:21 - HelloWorld21] Failed to upload HelloWorld21.apk on device 'HT03SNX02682'
[2010-06-14 13:03:21 - HelloWorld21] java.io.IOException: Unable to open sync connection!
[2010-06-14 13:03:21 - HelloWorld21] Launch canceled!
if I try to install from prompt dos with adb install... the process doesn't stop (stall?).
I tryed also to see logcat but seems doesn't log nothing... (I'm newbie in android dev)
thank in advance for your help
I had the same problem, even if with my emulator.
Occasionally, the Device view in the Eclipse DDMS would list many copies of the device, all of them Offline, and I wouldn't be able to run anything on the device if I tried to plug it back in.
What seems to fix this is running
adb kill-server
from the command line. It cleans up the list of Offline devices and allows me to run applications on the device again.
Hope it works,
Now works on 32bit and 64bit Linux
Just a quick guide on how to configure Linux for file transfers using MTP. I wrote the instructions and config for Ubuntu Natty 32bit and 64bit, though the same process will work on other platforms - the only real difference being the package manager commands and possibly the config file locations.
The attached files are for the Galaxy Tab 10.1v but should work for the 10.1g / 10.1 as well. See the end of the post to learn how to modify this config to work for other devices.
How to configure for gMTP and other Media Sync tools
1) Install aptitude
Code:
sudo apt-get install aptitude
2) Install mtp-tools and mtpfs
Code:
sudo aptitude install mtpfs mtp-tools
3) Download the attached file ( View attachment 98-gtab.zip for 32bit Linux or View attachment 98-gtab.rules-AMD64.zip for 64bit Linux ) to your desktop.
4) Extract the 98-gtab.rules file to your desktop
5) Copy the rules file to /etc/udev/rules.d/
Code:
sudo cp ~/Desktop/98-gtab.rules /etc/udev/rules.d
6) Reboot
7) Connect your Tab
8) Run the following command to confirm it is working:
Code:
ls /dev | grep gtab
...which should return "gtab" if successful. If not, follow the "Modifying" guide below.
9) Download / install gMTP
Code:
sudo apt-get install gmtp
10) Open gMTP and select "connect" from the menu
11) Hit the thanks button
12) Go nuts!
Setting up for Automount (Optional, but recommended)
***You must have completed Steps 1-8 above before proceeding***
1) Edit your fstab file to add your gtab:
Code:
sudo gedit /etc/fstab
2) Add this to the end of the file:
Code:
#gtab
mtpfs /media/gtab fuse user,noauto,allow_other 0 0
3) Save and exit
4) Open fuse.conf for editing:
Code:
sudo gedit /etc/fuse.conf
5) Find the following line and remove the #
Code:
#user_allow_other
6) Save and exit
7) Open and edit the groups file:
Code:
sudo gedit /etc/group
8) Find the details for the group 'fuse' and append your username to the end of the line eg.
Code:
fuse:x:104:<YOUR USER NAME>
9) Save and exit
10) Create the folder to mount your Tab:
Code:
sudo mkdir /media/gtab
11) Take ownership of the folder:
Code:
sudo chown <YOUR USER NAME>:users /media/gtab
12) Reboot
13) Plug in your Tab.
14) Click on the Places menu and click gtab.
15) You're in business!
Modifying for other devices
If the above doesn't work immediately on the 10.1g / 10.1 (I have only tested on the 10.1v), you can easily edit the rules file to support your device.
1) Install lsusb
Code:
sudo apt-get install lsusb
2) Run lsusb
Code:
lsusb
3) Check the output of this command to find your device. The 10.1v is shown like this:
Code:
Bus 001 Device 010: ID 04e8:6860 Samsung Electronics Co., Ltd
4) Make a note of the Vendor and Product IDs. In the example above, the vendor ID is 04e8 and device ID is 6860 (note 04e8:6860 in the output).
5) Open the rules file for editing (if it's not already in /etc/udev/rules.d, copy it there now)
Code:
sudo gedit /etc/udev/rules.d/98-gtab.rules
6) Find this line:
Code:
ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="6860", MODE="0666" SYMLINK+="gtab"
7) Replace the Vendor ID (04e8) and Product ID (6860) with the ones that you got from step 3 above.
8) Save and exit
9) Reboot
10) Follow step 7 onward in the first guide above
11) Hit the thanks button
If you modify it for a particular device, please post the contents of your new 'rules' file here.
32bit RULES FILE:
Code:
ACTION!="add", GOTO="gtab_rules_end"
SUBSYSTEM!="usb|usb_device", GOTO="gtab_usb_end"
ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="6860", MODE="0666" SYMLINK+="gtab"
LABEL="gtab_usb_end"
LABEL="gtab_rules_end"
64bit RULES FILE:
Code:
ACTION!="add", GOTO="gtab_rules_end"
SUBSYSTEM!="usb|usb_device", GOTO="gtab_usb_end"
ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="6860", MODE="0777" SYMLINK+="gtab"
LABEL="gtab_usb_end"
LABEL="gtab_rules_end"
Tested, walked through the steps to my friend (Skype ). Works 100% on Linux Mint too
Everything worked for me up to the GMTP part - I can grep through /dev and I can see the "gtab" device there. But GMTP insists "Detect: No raw devices found."
I'm still running Maverick, but I added the maverick-backports repo, which has gmtp, so I would think it would work.
This is a Samsung Galaxy Tab 10.1v (from Google I/O). Any ideas?
EDIT: I also tried the automounting option with FUSE. Attempts to cd into it with bash or open it from the Places menu in GNOME both give the message "Transport endpoint is not connected".
EDIT again:
OK, I disabled USB Debugging and now have a different set of problems. mtp-detect sees the device now, but the message upon running it is:
Code:
libmtp version: 1.0.3
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
04e8:6860 @ bus 2, dev 26
Attempting to connect device(s)
ignoring usb_claim_interface = -16ignoring usb_claim_interface = -22PTP_ERROR_IO: Trying again after re-initializing USB interface
inep: usb_get_endpoint_status(): Device or resource busy
outep: usb_get_endpoint_status(): Device or resource busy
usb_clear_halt() on IN endpoint: Device or resource busy
usb_clear_halt() on OUT endpoint: Device or resource busy
usb_clear_halt() on INTERRUPT endpoint: Device or resource busy
LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Unable to open raw device 0
OK.
Konklone said:
Everything worked for me up to the GMTP part - I can grep through /dev and I can see the "gtab" device there. But GMTP insists "Detect: No raw devices found."
I'm still running Maverick, but I added the maverick-backports repo, which has gmtp, so I would think it would work.
This is a Samsung Galaxy Tab 10.1v (from Google I/O). Any ideas?
EDIT: I also tried the automounting option with FUSE. Attempts to cd into it with bash or open it from the Places menu in GNOME both give the message "Transport endpoint is not connected".
Click to expand...
Click to collapse
Can you post the output from 'lsusb' ?
re the "Transport endpoint is not connected" - I just got this same error on 64bit Natty. Will try and see if I can find out why..
Ah, just saw your reply. I edited my post up above, but the gist is - you can't do this while USB Debugging is enabled. The Tab has to be running its "MTP Application".
Now I'm getting the stranger errors above. I'm going to try mounting it with FUSE now to see if that helps for some reason.
EDIT: For the record, I'm using the correct vendor and product IDs in my rules file:
Code:
ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="6860", MODE="0666" SYMLINK+="gtab"
Konklone said:
I edited my post up above, but the gist is - you can't do this while USB Debugging is enabled.
Click to expand...
Click to collapse
You may be right. When I wrote this guide, I was using a VM. It is possible that the fact that I was using both MTP and ADB at the same time has something to do with how VMWare presents the devices to the guest OS.
Now I am using 'bare metal' Natty 64 bit and have the same problem as you.
I have to go out for a while but will look at it again when I get back.
EDIT: Just tried mtp-detect and it is finding the device. I suspect USB Debug is not the issue, but I'll leave it in your capable hands - really got to go now
EDIT2: See here http://www.usb.org/developers/devclass_docs/MTP_1.0.zip OK - Im really REALLY going now. Back online in a few hours
I couldn't get anywhere until I turned off USB debugging. When USB debugging is enabled, I *can* use adb to get into the shell, see files, install apps, etc. I can even transfer files over adb, through the command line! Can you get MTP to detect it with USB debugging enabled?
With USB debugging off, I have once in a great while (only twice in all my attempts) while gotten mtp-detect to connect to the device and print sane output describing the device. Even when those happened, running the command immediately again didn't connect correctly, and gave me the same error messages I was getting before. Both times I got it to connect, it was soon after plugging in the cable, but it doesn't happen every time.
Intermittent heisenbugs are the worst, yet I don't think I have a busted cable, given that adb works perfectly consistently.
Maybe I should try this again after updating to Natty...I'd been meaning to do it anyhow...
EDIT: One thing I notice is that on the Tab, when the "MTP Application" is running after plugging in, the 5-dot "in progress" animation is extremely choppy, as if the device were very very busy. If the device were very very busy for some reason, this could explain why a successful connection can happen only once in a great while. I'll try rebooting the device, I guess.
EDIT2: I rebooted the device, and I removed the USB extension cord I was using, but neither helped, still getting the same intermittent success. (I got mtp-detect to connect to it a few more times - all soon after plugging in the cable, and none were repeatable without unplugging and replugging it in.) The animation actually wasn't choppy before, that's just how it looks - 5 discrete animation frames, one for each dot.
Something interesting though: this time I had the Tab resting on my knee, and I felt a haptic buzz after running mtp-detect on one occasion. I looked down and saw the MTP Application restart itself. Then I ran mtp-detect again and I felt 3 haptic buzzes in quick succession, followed by a successful detection and output. But when running mtp-detect *again*, no dice.
This is messed up.
Messed up indeed.
Konklone said:
Can you get MTP to detect it with USB debugging enabled?
Click to expand...
Click to collapse
Yes, both work simultaneously on 32bit Natty
Note that you have to unmount the gtab for mtp-detect to work. I compared the output from mtp-detect on the 32bit working VM and the 64bit non-working 'bare metal' machine and the output was identical. I suspect this means that mtpfs is not where the problem is
Re the strange problem with haptic feedback - I have had mine power off all by itself when testing some different parameters in the rules file.
[64bit working]
OK. Problem solved... kind of. There seems to be some kind of bug in fuse which requires the filesystem to mount with higher permissions to run properly (at least on Natty AMD64)
If you use the new 64bit rules file I have attached, it should work. Basically it uses 777 permissions instead of 666. Not great, but working nonetheless.
New rules file for 64bit:
Code:
ACTION!="add", GOTO="gtab_rules_end"
SUBSYSTEM!="usb|usb_device", GOTO="gtab_usb_end"
ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="6860", MODE="0777" SYMLINK+="gtab"
LABEL="gtab_usb_end"
LABEL="gtab_rules_end"
EDIT: If someone wants to experiment with lesser permissions and see what the minimum is and post back, that would be helpful for all.
Sigh, thank you for taking so much time to help me so far, but I wonder if I'm a lost cause.
I spent a bunch of today finishing my upgrade to Natty, including a full wipe and reinstall. (I have a 32-bit machine, btw.) Now I can't even get it to detect my MTP device at all (mtp-detect says "No raw devices found."), with or without debugging enabled.
One possibly important topic - it's really surprising to me that yours works either way, because lsusb shows that a different product ID is exposed to the host, depending on whether debugging is on or not. With debugging disabled, it's 6860, like your example. With debugging enabled, it's 685e. When I run lsusb, only one of those will show up, never both. So if yours is the same device, I have no idea how your rules file could be agnostic to debugging being enabled. If yours is not, then that might explain our different experiences.
Anyway, I've Thanks'd all your posts in this thread, solved or not. I appreciate your help.
Konklone said:
With debugging enabled, it's 685e. When I run lsusb, only one of those will show up, never both
Click to expand...
Click to collapse
You're more than welcome.
I noticed that in Windows, both devices appear in device manager. That is a very strange problem you have discovered.
I just posted instructions and files to give you root access! Might take your mind off the MTP issues for a while
Who knows... the problem might just go away
Konklone said:
One possibly important topic - it's really surprising to me that yours works either way, because lsusb shows that a different product ID is exposed to the host, depending on whether debugging is on or not. With debugging disabled, it's 6860, like your example. With debugging enabled, it's 685e. help.
Click to expand...
Click to collapse
Are you sure? On my device its the other way around. Without debugging its 685e and with debugging its 6860?
ajvogel said:
Are you sure? On my device its the other way around. Without debugging its 685e and with debugging its 6860?
Click to expand...
Click to collapse
Ok I got it working on my device, I switched on usb debugging in settings. lsusb now returns 6860 and I am able to mount the galaxy tab using the process outlined above.
This is craziness. Is my Galaxy Tab a rare mutant piece of hardware who had its USB numbers switched?
Also - I noticed that Ubuntu somehow automounts my tablet and can read/write to its disk, through a Nautilus plugin. But I still get nothing with mtp-detect. I don't understand how the world works.
I've also got an I/O tablet (updated to 3.1) and I followed this tutorial, so thanks for the help you provided! I managed to copy some files to the device but it ended up freezing my computer (running Ubuntu 10.10).
So I unplugged the tablet, and saw that effectively those few pictures and pdf files had been copied to the device successfully. Pictures are in the Gallery, pdf can be read with Aldiko... but the funny thing is that when I mounted again the tablet -using Ubuntu again- it shows all folders as empty!
That is, 0 files in all tablet folders.
I tried "showing all hidden files" with Nautilus. No luck, nothing is shown. Went to the folder using command line, did an ls -la (just in case who knows! maybe it would show something!). No luck either, directories are apparently empty and have "1 January 1970" as modification date... if it helps.
I can see the files inside the folders using ADB but it's obviously not ideal, specially compared with simply using Nautilus.
Does it happen to you too?
Anyone get this working? I'm having the same exact issues as Konklone. I'm on Maverick and tried the different udev rules and it still doesn't work. I'm gonna be pissed if I have to buy the stupid Samsung USB adapter just to get USB mass storage.
[ASK]Noobs need solution
gMTP tells me that there is no device. Any ideas?
I'm having the same issue. First try I was able to plug in and mount to my netbook. Tried to plug into my mac and it didn't work. Hasn't worked since then, i'm considering doing a factory reset.
I'm running Ubuntu 10.10 64-bit. Note that you do have to enable backports to install gmtp.
Edit /etc/apt/sources.list, uncomment the lines with:
Code:
deb (http-url) maverick-backports main restricted universe multiverse
deb-src (http-url) maverick-backports main restricted universe multiverse
Run
Code:
sudo apt-get update && sudo apt-get install gmtp
I had to unplug the device and replug it back in a couple of times before gmtp would connect to it properly. It seems to be pretty flaky.
Wow...........
This is nonsense ..... is there a way to enable USB Mass Storage or are we completely hosed with MTP?
[Project dormant unless someone else picks it up]
NOTE: This is a chroot for the Webtop, not the Android+VNC chroot method.
Hi everyone, this is my first guide (I'm not sure I can call it that yet, or if this is in the right section) so bear with me.
I tried the Debian chroot guide (http://forum.xda-developers.com/showthread.php?t=1093790), and I really liked the idea, but I had too many apt-get issues and it often crashed my Webtop, so I tried building my own Ubuntu Lucid chroot using rootstock, but internet didn't work.
I later saw this: http://forum.xda-developers.com/showthread.php?t=1184161, but the links were dead and the scripts it referenced were out of date. I'll sort of combine the two guides here since Backtrack actually works surprisingly well.
Just on a side note though, I haven't fully tested the Backtrack tools, but the only thing I haven't found to work are the wireless tools.
Let's start!
Required:
-Rooted Atrix (with Blur based ROM)
-LXTerminal installed on Webtop
-Enough free space (around 4 GB just for room)
-7-Zip
-Some Linux/Unix distro native or in a VM
1. Install the easy-signed.zip from the Debian chroot guide:
http://forum.xda-developers.com/showthread.php?t=1093790
but the other files aren't needed.
Make a folder called WebTopMOD (case-sensitive) on either external or internal memory for later.
2. Look here for reference: http://forum.xda-developers.com/showthread.php?t=1184161, but the links are dead. Active links are here:
Part 1: http://www.mediafire.com/?x9cgxzdx84vc6uj
Part 2: http://www.mediafire.com/?xaoidipkg1o7vgo
Part 3: http://www.mediafire.com/?po3nznbxgvdipur
Use 7-Zip to uncompress the three files (called bt.7z.001,002,003) and you'll get a bt.img.
Full bt.img in a zip:
DL from Mega or from Google Drive
3. The image isn't usable in this state yet, since the image is formatted with ext2, and we need ext3.
Copy the image over to your Linux VM or computer on a easy-to-find directory, and open up a Terminal window (usually CTRL+ALT+T).
In Terminal, type this in:
Code:
cd <directory where you put bt.img>
mkdir tmp tmpbt
sudo mount -o loop bt.img tmpbt
dd if=/dev/zero of=linuxdisk count=0 bs=1MB seek=4096 (This is the size of the chroot image you want, in MB)
mkfs.ext3 linuxdisk (just type y when it asks)
sudo mount -o loop linuxdisk tmp
sudo cp -rf tmpbt/* tmp
sudo umount tmp
sudo umount tmpbt
[Sorry, made a mistake twice] Copy the newly made linuxdisk file to a directory named WebTopMOD on your internal memory or sdcard-ext (folder and file names are case-sensitive).
4. Start Webtop, then open LXTerminal, then start the chroot by typing in:
Code:
/usr/sbin/linux
and after it loads for a bit, you'll get an xterm window with the shell for Backtrack!
If you want to quit the Gnome session, closing xterm doesn't work, since by issuing the commands to kill the webtop processes, it also kills the webtop window manager, and if you do close it there's some kind of weird glitch with a small popup window constantly disappearing and reappearing. (It'll be a WIP for now I guess, the only full solution is to reboot your Atrix). It seems to have to do with the way the linux command mounts the chroot disk under loop50, I'll try and make something to fix this later.
-----------------Extras moved below-----------------------
Pictures:
Chromium Running
BT Desktop (Gnome)
BT Desktop with AIW
THANKS TO:
k.taylor89 for the original Backtop Method
SystemR89 for the Debian chroot and scripts to make this work
The original developers of the Backtop chroot image
And any others I may have forgotten!
Extras:
If you want a GUI (Gnome):
k.taylor89 said:
You first need to kill off all the webtop crap do this by typing the following in xterm.
"ps ax|grep awn|awk '{print $1}'|xargs kill"
"ps ax|grep panel|awk '{print $1}'|xargs kill"
Then start gnome by typing "gnome-session" in xterm.
Click to expand...
Click to collapse
If you want to take it step further and start Gnome after bootup, this isn't a full solution yet but you could edit your start-oshwt-1.sh and 2 scripts so that the chroot automatically starts on bootup without anything else in Webtop, and from there start gnome-session. I'm testing that now.
Installing Apps:
Since this is based off of Ubuntu Lucid, you can install anything from the Lucid repos, you just have to fix the sources list since the Backtrack sources don't seem to work.
Code:
sudo cp /etc/apt/sources.list /etc/apt/sources.list.old (Backup just in case)
sudo nano -w /etc/apt/sources.list
Comment out (#) any line with the backtrack servers, and uncomment any line with the Ubuntu repos.
Press Control+X, Y, then Enter, then run apt-get update to update the repos.
Apps like Chromium install and run without a hassle (just run apt-get install chromium-browser), but I actually get the error "Bus error" for some reason when Chromium remains idle, it seems to be an unsolved bug in the version of Chromium for armel devices in the Lucid repos, if anyone else has a fix, please do tell.
First.
I think its only for lapdock ..........
3n3rg1c said:
First.
I think its only for lapdock ..........
Click to expand...
Click to collapse
Oh sorry yeah I forgot to mention that. I mean I guess if you have the mod that lets you use Webtop anywhere, that'll work too.
Hi,
The "Part 3: http://www.mediafire.com/?po3nznbxgvdipu" doesn't work.
Could you fix it.
Thank you.
sintoo said:
Hi,
The "Part 3: http://www.mediafire.com/?po3nznbxgvdipu" doesn't work.
Could you fix it.
Thank you.
Click to expand...
Click to collapse
Oh sorry I copied the link incorrectly, updated in OP.
i've gotten it running on my ubuntop model, when i ran it from the terminal it would not give me any issues when closing it back up. is there a way to only launch the gnome panel? running: gnome-panel in the terminal didn't work
etruj said:
i've gotten it running on my ubuntop model, when i ran it from the terminal it would not give me any issues when closing it back up. is there a way to only launch the gnome panel? running: gnome-panel in the terminal didn't work
Click to expand...
Click to collapse
I'm not sure if there is a way to start just gnome panel because of the way the chroot is implemented, since to run gnome-panel, an X session must already be running within the chroot and I need to figure that out.
My first two times i lUnched the session the wallpaper would flicker and then just the panels would come up. Now i get hit with the errors and loop pop ups. Maybe there is a way to launch the session then kill everything but the panel?
Sent from my MB860 using xda app-developers app
etruj said:
My first two times i lUnched the session the wallpaper would flicker and then just the panels would come up. Now i get hit with the errors and loop pop ups. Maybe there is a way to launch the session then kill everything but the panel?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
The workaround I found worked so far was to modify the start-oshwt-2 script so that it would run a very slightly modified version of the script that automatically starts gnome-session (gnome-panel alone is really stubborn, still haven't figured that out) and doesn't start whatever window manager in WebTop to avoid flickering errors and panel only errors (but of course you don't have access to anything from the actual WebTop, but you could also have start-oshwt open a Terminal window from WebTop too).
Can you attach the script?
Sent from my MB860 using xda app-developers app
etruj said:
Can you attach the script?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Just rename it to linux, and copy it to wherever you like on your Atrix. You can also copy it to a directory within your terminal path.
This isn't my script, it's from the Debian chroot, just modified to automatically start gnome-session (credit to SystemR89)
You might need to chmod +x the file.
Also, if you want to start it automatically from start-oshwt-2.sh, make sure you copy the file to a directory within the terminal path, and add the line
Code:
sfalv -i "linux"
and comment out any other line that starts a different X window manager.
running "sudo gnome-panel" gives me the panel while staying inside the original ubuntop. i think i can just swap out that one line in your script to get it working. thanks! also noticed my chrome crashes after a few minutes, ill post the error code and screen grabs soon but was wondering if you ever experienced anything like it?
etruj said:
running "sudo gnome-panel" gives me the panel while staying inside the original ubuntop. i think i can just swap out that one line in your script to get it working. thanks! also noticed my chrome crashes after a few minutes, ill post the error code and screen grabs soon but was wondering if you ever experienced anything like it?
Click to expand...
Click to collapse
Yes, in fact. It's a bus error, and I tried to fix it, but the fix doesn't work (and it only seems to affect Chromium).
Sorry for bumping such an old thread, but I was wondering if anyone wanted to take this project over, since I don't have an Atrix anymore and don't have anything to work with.
Thanks.
How to install OSX Mavericks (10.9.4) as a Windows 8.1 VirtualBox VM
Please note, this thread is only meant to share some personal notes
on what I did and how to get this working. It is not meant as a
support thread. In fact, I will not respond to any support questions.
The links found here will provide you with more information than you
could ever beg for.
Almost exactly one year ago, I posted some instructions on how to
install OSX Mountain Lion into a VirtualBox (VB) VM, running on an
old Windows Vista AMD laptop. This time I'll show you (briefly) how
to install OSX Mavericks to an Intel Laptop running Windows 8.1.
The installation procedure is divided into a few steps.
1. Pre-installation preparation
2. Install the Niresh OS X Mavericks (10.9.0) distribution.
3. Install the Official Apple OS X Mavericks (10.9.4) Update Combo
4. Post installation instructions
Some important Hackingtosh references:
Here is a mega-thread on OSX how-to's and help related items.
http://www.insanelymac.com/forum/topic/298027-guide-aio-guides-for-hackintosh/
Especially the section on DSDT and SSDT:
http://www.insanelymac.com/forum/topic/298027-guide-aio-guides-for-hackintosh/#entry2027250
http://www.insanelymac.com/forum/topic/286092-guide-1st-generation-intel-hd-graphics-qeci/
http://lifehacker.com/the-always-up-to-date-guide-to-building-a-hackintosh-o-5841604
1. Pre-installation preparation
Basic Hardware Info
Before you attempt to install your OSX into a VirtualBox VM (guest),
you need to find out some details about your own machine (host). Why?
Because every new OS X is depending on the Hardware to be very
"maxed out" and specific. You need to tune your VB VM to behave similar
to a real Apple machine in order to make the OS X think your machine
hardware is a real Mac. In addition, some PCI devices are passed on and
through to the VB VM engine.
For example, for a half decent running Mavericks installation,
you need to have at least 2-4 processor cores, 4 GB RAM and 30 GB HD
in your VM. Then your host need some memory as well... Then to get
correct audio, video, network, USB etc you need to know exactly what
HW your host have AND how that is presented by VB to a VM guest.
So how do you do that?
On your PC/Laptop (host):
Code:
[SIZE=2]Windows: Use [URL="http://www.hwinfo.com/"]HWiNFO64[/URL] + [URL="http://rweverything.com/download/"]RW-Everything[/URL] + (Windows) [I]Device Manager [/I]
Linux: Download and run a Live Linux distro and copy the
output of [I]dmesg[/I] and [I]lspci, lsusb[/I], respectively.
[/SIZE]
For this laptop we have:
<TBA>
From host HWiNFO64, we found:
Code:
[SIZE=2]Audio Adapter: Intel Lynx Point PCH - High Definition Audio Controller [C2]
Audio Controller Hardware ID: PCI\VEN_8086&DEV_8C20&SUBSYS_11CD1043&REV_05
Audio Codec Hardware ID: HDAUDIO\FUNC_01&VEN_[COLOR=Red][B]10EC[/B][/COLOR]&DEV_[COLOR=Red][B]0668[/B][/COLOR]&SUBSYS_00000000
DeviceInstanceId: HDAUDIO\FUNC_01&VEN_10EC&DEV_0668&SUBSYS_104311CD&REV_1000\4&6BFDCFC&0&0001
[/SIZE]
We then look up these PCI IDs at one of the websites:
pci-ids or pci-database.
There we find that the host physical Audio Codec is a: Realtek ALC668 [10EC:0668]
So if we had a real Hackingtosh, we would have to find or make and
install the AppleHDA.Kext that has been built and tweaked to
correspond to this driver. Here are some relevant links:
http://www.insanelymac.com/forum/files/file/203-applehda-alc662-1092/
http://www.insanelymac.com/forum/files/file/148-109-gm-applehda-for-alc662/
http://www.insanelymac.com/forum/files/file/128-109-dp7-applehda-for-alc662/
http://www.insanelymac.com/forum/files/file/6-applehda-for-alc662/
On the VirtualBox VM (guest):
Boot up or install any minimal OS like Windows, Linux and use the
same method as above, but now running in the VM. As you will see,
the detected hardware will look different. That is basically
how OSX will see it as well.
So to help you along we'll jump ahead and I just show you
what an installed guest OS will see in terms of Audio HW.
I've ignored all other HW, since audio is what causes most
trouble to OSX guests.
On OSX 10.9.4 (Intel HD Audio):
Code:
[SIZE=2]# sudo lspci -m -v
Device: 00.05.0
Device: 82801FB (ICH6) High Definition Audio Controller
SVendor: [B]SigmaTel[/B]
SDevice: Device 7680
# sudo lspci -m -n -vvv
Class: 0403
Vendor: 8086
Device: 2668
SVendor: [B]8384[/B]
SDevice: [B]7680[/B]
[/SIZE]
On Linux Mint (ICH AC97):
Code:
# sudo lspci -b -nn -v
00:05.0 Multimedia audio controller [0401]: Intel Corporation 82801AA AC'97 Audio Controller [8086:2415] (rev 01)
Subsystem: Intel Corporation Device [8086:0000]
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at d100
I/O ports at d200
Kernel driver in use: snd_intel8x0
On Linux Mint (Intel HD Audio):
Code:
[SIZE=2]00:05.0 Audio device [0403]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller [8086:2668] (rev 01)
Subsystem: SigmaTel Device [[COLOR=Red][B]8384:7680[/B][/COLOR]]
Flags: bus master, fast devsel, latency 64, IRQ 11
Memory at f0804000 (32-bit, non-prefetchable)
Capabilities: [50] Power Management version 2
Kernel driver in use: snd_hda_intel[/SIZE]
On Windows 7 (Intel HD Audio):
Code:
[SIZE=2]Audio Controller Hardware ID: PCI\VEN_8086&DEV_2668&SUBSYS_[B]76808384[/B]&REV_01
Audio Codec Hardware ID: HDAUDIO\FUNC_04&VEN_0000&DEV_0000&SUBSYS_00000000[/SIZE]
Clearly the guest driver presented is a SigmaTel with PCI ID: 8384:7680.
Further research reveals it is based on a: SigmaTel STAC9221 [8384:7680]
Thus, for any audio success on running OSX on a VirtualBox VM, we need
to find a Kernel Extension (Kext) that is compatible with this driver.
The best way is to find a tweaked AppleHD.Kext to match this driver.
HOWEVER! Lo-and-behold! The Realtek (!) linux sources seem to suggest
that this driver is used in several Macs:
From: ..\alsa\alsa-kernel\pci\hda\patch_sigmatel.c:
Code:
[SIZE=2]
/* Apple Intel Mac (Mac Mini, MacBook, MacBook Pro...) */
SND_PCI_QUIRK(0x8384, 0x7680, "Mac", STAC_INTEL_MAC_AUTO),
...
/* codec SSIDs for Intel Mac sharing the same PCI SSID 8384:7680 */
static const struct snd_pci_quirk stac922x_intel_mac_fixup_tbl[] = {
SND_PCI_QUIRK(0x106b, 0x0800, "Mac", STAC_INTEL_MAC_V1),
SND_PCI_QUIRK(0x106b, 0x0600, "Mac", STAC_INTEL_MAC_V2),
SND_PCI_QUIRK(0x106b, 0x0700, "Mac", STAC_INTEL_MAC_V2),
SND_PCI_QUIRK(0x106b, 0x0e00, "Mac", STAC_INTEL_MAC_V3),
SND_PCI_QUIRK(0x106b, 0x0f00, "Mac", STAC_INTEL_MAC_V3),
SND_PCI_QUIRK(0x106b, 0x1600, "Mac", STAC_INTEL_MAC_V3),
SND_PCI_QUIRK(0x106b, 0x1700, "Mac", STAC_INTEL_MAC_V3),
SND_PCI_QUIRK(0x106b, 0x0200, "Mac", STAC_INTEL_MAC_V3),
SND_PCI_QUIRK(0x106b, 0x1e00, "Mac", STAC_INTEL_MAC_V3),
SND_PCI_QUIRK(0x106b, 0x1a00, "Mac", STAC_INTEL_MAC_V4),
SND_PCI_QUIRK(0x106b, 0x0a00, "Mac", STAC_INTEL_MAC_V5),
SND_PCI_QUIRK(0x106b, 0x2200, "Mac", STAC_INTEL_MAC_V5),
{}
};
...
{ .id = 0x83847680, .name = "STAC9221 A1", .patch = patch_stac922x },[/SIZE]
So when you first boot and install your Niresh Mavericks, you should
probably leave out any Audio related hacks, and certainly avoid
installing the VooDooHDA related Kext. It's possible (and I didn't
bother to check) that audio would then work out-of-the-box as well.
Finding a suitable "distro"
Next, you need to find and download a suitable ISO version of the
OSX Mavericks Installation disk. Apple uses the DMG format to
distribute all their installation "Disks". So to avoid having to
mess with the conversion of a 3.5+ GB DMG image to ISO, we just
try to find a torrent of one already made. But because of the
inherent complications of booting and setting up your own
"Hackingtosh" from a vanilla (original) Apple disk, we prefer to
use one that come as a distribution ("distro") which is more
flexible and much more likely to install from first try. And
usually have some sort of support forum connected to it.
One such distro is that from Niresh. We will use that one.
It is important to mention that, today Apple OS X Maverick is free
of charge for download and use, but you need an OSX based computer,
in order to get it from the Apple Store. And if you're willing to
jump through the Apple hoops, you can also get the latest
OSX Yosemite (10.10.0) and try that. But you need to signup
to the Apple Store with a credit card! So I just used my untraceable
NSA credit card to signup. It has a picture of Obama and the Logo of
Google on it. In the states you can usually find those in the bottom
of some randomly selected Kellogg's Corn-Flakes Packages.
2. Installing the Niresh OS X Mavericks distro
Fortunately all this hard work has already been described in great
detail on the MacBreaker website in:
"How to install OS X Mavericks in Virtualbox with Niresh"
However, before you go there and rush through the instructions, please
listen to this first. If you're a smart-ass who think you can outsmart
the apple bootloaders and the many precise VirtualBox settings needed
to boot OSX, you are very likely to fail and will have serious booting
trouble and subsequent OSX driver issues. And as with all Apple products,
if you're not an expert yourself, nobody will/can help you, especially
since Googling any OSX related installation issues will give you millions
of hits.
So take good time to read every step in those instructions and carefully
examine all the screenshots to know exactly how you have to setup and
tune your VirtualBox VM to your device. I will provide some additional
pictures on a few things I found working for my setup.
You need to signup (or find a torrent) to download the file:
"Niresh Mac OS X Mavericks 10.9 with AMD & Intel USB"
This OSX distribution works on both Intel and AMD based machines, and
can be run on native Hackingtoshes, VirtualBox and VMware machines.Very Important Note:
OSX Mavericks is now free from the Apple Store, so if you are looking for the latest update, or original distribution, don't try to use this. This is a distribution that is made to be run on Hackingtoshes or VMs. It is not up-to-date nor maintained in any way. That's why it is in ISO format and not in native Apple DMG. If you already know you want to use VMware, then perhaps you're better off trying to use the VMware Mavericks Image.
Google for: "OS_X_Mavericks_10.9_Retail_VMware_Image"
Converting a DMG to ISO:
If you want to convert a DMG to ISO from within OSX run the following,
in an OSX Terminal:
Code:
[SIZE=2]cd Desktop
sudo hdiutil convert ./InstallESD.dmg -format UDTO -o InstallESD
mv InstallESD.cdr InstallESD.iso[/SIZE]
or:
Code:
[SIZE=2]sudo hdiutil makehybrid -iso -joliet -hfs -o OSXMavericks.iso OSXMavericks.dmg[/SIZE]
I found the following "script" on the web. It is used to convert a Yosemite
DMG image to ISO. But it doesn't look like a real script, so probably it should
be entered one item at the time. (Also, I can't find the original author. So if you are, just let me know an I'll give you credit for it.)
Code:
[SIZE=2]# ==============================================================
# 10.10 How to make an ISO from the Install.app
# ==============================================================
# Mount the installer image. It assumes that the installation app is called "Install OS X Yosemite.app"
# located in your "Applications" folder. If not, change the first command accordingly.
hdiutil attach /Applications/Install\ OS\ X\ Yosemite.app/Contents/SharedSupport/InstallESD.dmg -noverify -nobrowse -mountpoint /Volumes/install_app
# Convert the boot image to a sparse bundle
hdiutil convert /Volumes/install_app/BaseSystem.dmg -format UDSP -o /tmp/Yosemite
# Increase the sparse bundle capacity to 8GB to accommodate the packages
hdiutil resize -size 8g /tmp/Yosemite.sparseimage
# Mount the sparse bundle for package addition
hdiutil attach /tmp/Yosemite.sparseimage -noverify -nobrowse -mountpoint /Volumes/install_build
# Remove Package link and replace with actual files
rm /Volumes/install_build/System/Installation/Packages
cp -rp /Volumes/install_app/Packages /Volumes/install_build/System/Installation/
cp -rp /Volumes/install_app/BaseSystem.* /Volumes/install_build/
# Unmount the installer image
hdiutil detach /Volumes/install_app
# Unmount the sparse bundle
hdiutil detach /Volumes/install_build
# Resize the partition in the sparse bundle to remove any free space
hdiutil resize -size `hdiutil resize -limits /tmp/Yosemite.sparseimage | tail -n 1 | awk '{ print $1 }'`b /tmp/Yosemite.sparseimage
# Convert the sparse bundle to ISO/CD master
hdiutil convert /tmp/Yosemite.sparseimage -format UDTO -o /tmp/Yosemite
# Remove the sparse bundle
rm /tmp/Yosemite.sparseimage
# Rename the ISO and move it to the desktop
mv /tmp/Yosemite.cdr ~/Desktop/Yosemite.iso
[/SIZE]
VirtualBox Installation Instructions:
Follow the MacBreaker installation instructions EXACTLY. When
installing on a Haswell based PC host, you MUST run the VBoxManage
commands to make your VM think it has an older/supported processor.
Before trying this, or if you get an error, make sure:
That your Windows system PATH contains both your Windows home directory and the VirtualBox
program directory:
a) "%HOMEDRIVE%%HOMEPATH%;" and
b) "C:\Program Files\Oracle\Virtualbox"
.
That after creating your OSX VM, that you close VirtualBox and restart it, in order to make all
the new settings take effect and get registered in the *.vbox file, used by VBoxManage.exe.
The location of the *.vobx settings file is the same as where you have the VB images.
(This used to be VirtualBox.xml in VB < 4.0.)
To test, open a CMD or Cygwin shell as administrator and run:
Code:
VBoxManage.exe list hostcpuids
...
If it works without any error, go on and change the CPU ID of the VM where you're installing OSX with:
Code:
[SIZE=2]VBoxManage.exe modifyvm "name_of_your_vm" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff[/SIZE]
(Technically you're entering: [--cpuidset <leaf> <eax> <ebx> <ecx> <edx>].)
If you're having trouble, you can also edit <name_of_your_vm>.vbox file
directly, by adding/removing the following lines:
Code:
[SIZE=2] <CpuIdTree>
<CpuIdLeaf id="1" eax="1787" ebx="2048" ecx="2147484169" edx="126614527"/>
</CpuIdTree>
[/SIZE]
(As you can see these are the same values in Dec as those in Hex above.)
When successful, restart VirtualBox to make sure your changes has
taken effect. After starting the properly setup OSX VM on a Haswell
machine, the only bootflag you may want is: "-v" for verbose bootup.
3. Install the Official Apple OS X Mavericks (10.9.4) Update Combo
Go into the OSX control panel and disable automatic updates. Then go to Apple Store and
download the latest Mavericks Combo Update. Updating should not change any of your
working settings, but to be safe, make a snapshot before doing this. Once downloaded,
just open and run the update. Installation will take a while.
4. Post installation instructions
So now that you got your basic OSX system running, the first thing to
do is to make a VirtualBox Snapshot, so that you can revert to this
point in case any of the subsequent procedures fails or mess up your
working system.
Once you are up and running with your virtual OS X machine you need to
do a couple of housekeeping tasks to ensure your virtual machine does
not freeze. Firstly go to "System Preferences" and select "Energy Saver"
and set "Computer sleep:" and "Display sleep:" to Never and also uncheck
"Put hard disks to sleep when possible", "Wake for Ethernet network
access" and "Allow power button to put the computer to sleep". In
"Desktop & Screen Saver" set "Screen Saver" to "Start after:" Never.
Then there are 3 things everyone have to have:
Shared folders between the host and guest OS.
Shared clip-board data, so that you can copy/paste between host and guest OS.
Change the default Display size
Since the VirtualBox maffia refuse to release the Guest Additions (GA)
for OSX, we have to work around these issues. Or if you are a brave OSX
developer, you can try to patch and compile the GA from their sources
and if you're successful, don't forget to share and give us a way to
send you some gold donations.
Folder Sharing
Folder sharing is most easily accomplished by setting up a network
share between host and guest OS. There are many ways and variations
on how to do this. But what most instructions miss, is that you would
probably like to keep your host more secure than your guest. This
means that the guest should be configured as the server and the
host as a client. (Which is contrary to most simpler instructions.)
So here are 3 easy ways to accomplish this.
1. Use Windows 8.1 and OSX internal file sharing capabilities.
2. Use Dropbox to share a folder and enable LANsync to make it fast.
3. Use one of the 3rd party tools below.
Of these, I prefer to use something where I don't need to depend on
an internet connection and having to sign up with any new services.
The easiest way I found to accomplish folder sharing using method (1)
was to use Windows 8.1 built in NFS functionality. To use this, you
need to enable NFS sharing of a folder in your OSX VM and then mount
this folder in your W81 host.
Setup OSX NFS (guest):
(Thanks to linoceros post at FreeBSD.org forums.)
(a) Check your network conection with 'ifconfig" and note your IP
on the local network. (I use a bridged-ethernet interface.)
(b) Read the OSX man pages for "export".
"The -alldirs flag allows the host(s) to mount at any point
within the file system, including regular files if the '-R'
option is used on nfsd."
Click to expand...
Click to collapse
(c) Find the UID and GID of the OSX user you are using.
Code:
[SIZE=2]$ id
uid=501(eva) gid=20(staff) groups=20(staff),
...
[/SIZE]
(d) Edit the file: /etc/exports (usually not present.)
In this file, the syntax is basically:
<shared folder> <options> <client IP>
$ sudo vi /etc/exports
Code:
[SIZE=2]/Users/eva/Desktop/winshare -mapall=501:20 -alldirs 127.0.0.1[/SIZE]
(You may need to change this for more security...)
(e) Edit the file: /etc/nfs.conf (usually already present.) And add the following line:
$ sudo vi /etc/nfs.conf
Code:
[SIZE=2]...
nfs.server.mount.require_resv_port = 0[/SIZE]
(f) Then let NFS know you've made a change by running:
$ nfsd update
Setup on Win8.1 (host):
(g) Now go to your Windows host and in "This PC" (or equivalent)
left-click and select "Add a network location". You will be asked to
provide a an "internet or network location". There you simply write
the IP you noted in step (a) and the "shared" folder you selected
in step (d). Written in windows notation as:
\\192.168.1.102\Users\eva\Desktop\winshare\
NOTE: Do not try to "edit" the files in the share. The behavior is a
bit unpredictable, so it's better to copy to another location and
then back again after edit. Not sure at the moment why that is...
Clip-board sharing
To keep things simple we should limit ourselves and be satified
with copy/paste operations. Just like before, here there are many
variations on KMS (Keyboard-Mouse-Screen) sharing solutions from
3rd parties. Even Apple themselves has a lame solution called
"Back To My Mac" that require you to sign up to, and use iCloud
before being able to have all your stuff snatched up by Apples
NSA employees. Here are the links.
[1] "How to set up Back To My Mac..."
[2] "Set up and use Back to My Mac"
[3] "Set up security options for Back to My Mac"
BUT No thanks! Let's find another solution.
So what we need, is a way to only share the clipboard data over
the local network. We don't need mouse sharing as all that already
works great in VB, unfortunately its not so easy to find something
with only clipboard sharing. So we choose the most easy one, which
means the one with best instructions, and that is ShareMouse.
The most popular and free ones are:
Code:
[SIZE=2][URL="http://www.keyboard-and-mouse-sharing.com/index.html"]ShareMouse[/URL] (cross-platform mouse-keyboard-file share)
[URL="http://synergy-project.org/"]Synergy[/URL] (cross-platform mouse-keyboard-file share)
[URL="https://github.com/coralw/share-clipboard"]ShareClipboard[/URL] ([URL="http://nodejs.org/"]Node.js[/URL] based OSX/WIN clipboard sharing)
[/SIZE]
Other solutions to consider.
Code:
Ducto R6 (cross device file/clipboard share) http://www.msec.it/dukto/
IP.SHARE (web based file/clipboard share) http://www.ipshare.net/
ClipboardSync (Google Chrome Clipboard Sync) [instructions] https://github.com/mihaip/clipboard-sync
Installation of ShareClipboard:
ShareClipboard depend on the Node.js API which can be downlaoded and
installed from HERE. It's available for all platforms and need to be
installed on each VM. One done, it is easy to starts the clip-board
sharing. There are two ways to use this:
1. Use as client-to-client sharing.
2. Use a server to act as a redirector, broadcasting the clipboard
text from a ShareClipboard client to the other ones, while the
server clipboard is left untouched.
To use ShareClipboard with Clients only (1):
Code:
[SIZE=2]a) Install the copy-paste module with the Node Package Manager*:
npm install copy-paste
b) Open a terminal and run the script with one of the following:
node share-clipboard.js
node share-clipboard.js <IP_ADDRESS>
c) If you haven't specified the IP address in the previous step,
connect other Share Clipboard (or Share Clip) instances to
this instance .
d) Now you can copy among the Share Clipboard clients.
[/SIZE]
To use your host as the ShareClipboard Server (1):
Code:
a) Open a terminal and run the script with:
node share-clipboard-server.js
b) Connect the ShareClipboard clients to the server IP.
c) Now you can copy among the Share Clipboard clients.
* Reagrdless of the BS written on their FAQ, "npm" IS a Node package manager.
Changing Display size
To change the default video/display size, from 1280x1024 (or 1024x768)
to 1920x1080, you need to edit the OSX bootloader plist.
1. Use Finder to open the file: /Extra/org.chameleon.Boot.plist
in Editor or use Terminal App in shell with:
Code:
sudo vi /Extra/org.chameleon.Boot.plist
2. Then between the <dict> and </dict> tags, in the file, insert the
following lines:
Code:
[SIZE=2] <key>Graphics Mode</key>
<string>1920x1080x32</string>
[/SIZE]
3. Save and shutdown VM, but keep VirtualBox open.
4. Similarly as above, open an administrative CMD/Cygwin shell and issue the command:
Code:
[SIZE=2]vboxmanage setextradata "name_of_your_vm" "CustomVideoMode1" "1920x1080x32"[/SIZE]
5. Restart VirtualBox.
PS. I found 1600x900x32 in non-scaled mode, more useful on this Laptop.
Additional Enhancements and Fixes
To remove window flickering in Safari, remove the zero byte file:
/Library/Preferences/com.apple.windowserver.plist
Good Luck!
< Let there be even more dragons>
I have installed OSX Mavericks 10.9 using VMware Workstation.
my first intention was to install OS X 10.9 on an external HDD and boot it from there instead of "virtual", but couldnt find answers.
I have intel , BTW.
Booting Yosemite (10.10.x) Public Beta 2 in VirtualBox
Just for the hell of it, I decided I wanted to run the latest Yosemite Public Beta 2 in a VirtualBox VM under Windows 8.1. After all sorts of trouble, I finally learned that Yosemite has implemented more compatibility changes that blocks older Apple hardware from using it. So the way to work around is to hack your VM in such a way that it acts like recent Apple HW. Fortunately, VirtualBox is very flexible in this area, but very poorly documented and extremely poorly supported, as Oracle (VirtualBox) forum have decided to avoid any forms of Apple litigation's, by simply banning any questions related to running OSX on any HW not from Apple.
So here I will present the simple steps to get Yosemite to run on a recent (Intel) Haswell-based Windows 8.1 host. There are two ways to do this.
Use another Mac/Hackingtosh to download the latest Public Beta (PB) or Developer Preview (DP) from Apples Developer/Beta site. You need to sign up and so on. Then run script to convert into DMG format.
Download an already made bootable Yosemite Public Beta in DMG format from some torrent site.
Once you have obtained (1) or (2) you're ready to install your Yosemite VM.
Do the following:
For Option 1
<TBA>
For Option 2
First download your Yosemite Public Beta in bootable DMG format from your favorite torrent site. In my case it was called YB2VB.dmg. Then create your new VirtualBox VM according to:
Code:
- Create a VM disk with > 40 GiB
- Under [I]General > Basic:Version[/I], use "Mac OS X (64bit)"
- Under [I]System > Motherboard[/I]
: [I]Base Memory,[/I] select 6 GiB VM RAM
: [I]Chipset[/I], use PCIIX
: [I]Extended Features[/I], select all to use EFI, ACPI, and UTC
- Under [I]System > Processor[/I], select only 1 CPU
- Under [I]System > Acceleration: Hardware Virtualization[/I], select all.
- Under [I]Display > Video:Video Memory[/I], use 128 MB, and do [B]not[/B] select any Extended Features (2D/3D)
- Under [I]Storage > Storage Tree[/I], select the "Empty" (CD icon) and go to:
"CD/DVD Drive" selector and click on the right-most CD icon for a
drop-down menu. On that menu, browse to and select your [B]*.dmg[/B]
image you downloaded above. Also select the "Live CD/DVD" option.
- Save and close VirtualBox.
Next you need to tune VB to impersonate some recent Apple HW.
First re-start VirtualBox. Once started, run an administrative command shell and run these:
Code:
VBoxManage.exe modifyvm "YourVMname" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff
VBoxManage setextradata "YourVMname" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3"
VBoxManage setextradata "YourVMname" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"
VBoxManage setextradata "YourVMname" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "IHateApple"
VBoxManage setextradata "YourVMname" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"
VBoxManage setextradata "YourVMname" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1
Close VB for changes to take proper effect. Restart and start you VM.
Be very patient, and after some error messages your OSX should bootup
to start the setup process.
Formatting the (new) VM disk/parition
Once the boot process start loading, you'll have to select language and then the boot disk to use. But since you don't have a boot disk, but only the mounted CD-ROM (DMG) image, you'll have to go into Disk Utility and format the VM disk partition and give it a name like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and
Now you can exit DIsk Utility and continue installing by selecting your new disk...
Once installation is finished, the system will reboot and you will be asked a few setup questions. After that the following assistant will aks you signup. Forget it by force closing it.
Then you can run the System Information App to find what you got:
and the Terminal App to see what kernel you're using:
You can now Google yourself senseless to tweak your new OSX to all the requirements you need. Keep an eye on the Mavericks post above as a guide or reference. However, before doing so, you may want to download and install the latest updates and the latest Beta, which is Beta 3 (at the time of this writing.)
Good Luck!
VGA
does anyone know any kext i can use for virtualbox VGA ? The graphics performance on the OS X VM is too low.
renatofdds said:
does anyone know any kext i can use for virtualbox VGA ? The graphics performance on the OS X VM is too low.
Click to expand...
Click to collapse
What do you mean "too slow". Works just fine for me. Maybe you have a slow PC and not enough RAM allocated for you VM. If you wanna find the driver used, look in the drivers detected on any VM guest OS, like linux or windows.
E:V:A said:
What do you mean "too slow". Works just fine for me. Maybe you have a slow PC and not enough RAM allocated for you VM. If you wanna find the driver used, look in the drivers detected on any VM guest OS, like linux or windows.
Click to expand...
Click to collapse
The 3D performance of the generic driver (VESA) uses a software rasterizer wich is too low on performance. I have assigned 8GB of RAM and 4 cores to the VM, on an i7 Haswell, its not insufficient hardware.
Try executing launchpad and you will know what i'm talking about.
@renatofdds Unfortunately I don't think a kext could fix that problem. It seem to be either a poor video driver from Oracle, or wrong cpuid settings, that doesn't allow for native correct 3D graphics on the processor. (I have the same setup as you.) So my best bet is that you head over to the Virtualbox support forum at Oracle, and look under "OSX" guest on "OSX" hosts. And see how they do it, or ask for help there. (They don't allow for OSX guests on Win hosts.)
E:V:A said:
@renatofdds Unfortunately I don't think a kext could fix that problem. It seem to be either a poor video driver from Oracle, or wrong cpuid settings, that doesn't allow for native correct 3D graphics on the processor. (I have the same setup as you.) So my best bet is that you head over to the Virtualbox support forum at Oracle, and look under "OSX" guest on "OSX" hosts. And see how they do it, or ask for help there. (They don't allow for OSX guests on Win hosts.)
Click to expand...
Click to collapse
OK man, tks for the suggestion.
If you're getting the following error
Code:
emulator: ERROR: x86_64 emulation currently requires hardware acceleration!
Please ensure Intel HAXM is properly installed and usable.
CPU acceleration status: Unable to open HAXM device: ERROR_FILE_NOT_FOUND
go to intel's website and download HAXM
some people are reporting issues with the win10 anniversary update so YMMV.
ajpettit said:
If you're getting the following error
Code:
emulator: ERROR: x86_64 emulation currently requires hardware acceleration!
Please ensure Intel HAXM is properly installed and usable.
CPU acceleration status: Unable to open HAXM device: ERROR_FILE_NOT_FOUND
go to intel's website and download HAXM
some people are reporting issues with the win10 anniversary update so YMMV.
Click to expand...
Click to collapse
You don't need to go to intel's site. You can do this:
Go to RemixOSPlayer folder > remixemu > haxm-windows_v6_0_3 > run intelhaxm-android > select your desired RAM amount and complete the procedure.
Try launching RemixOSPlayer.exe again and it should work this time.
This didn't work for me on my miix 700.
and if the still presists, go to bios settings and enable "Virtualization Technology" from there! it will worK!
virtualization is enabled, but haxm says it isn't. any ideas?
intel i5-4460
16gb ram
win 8.1 64bit
wow, this Remix OS player plays smoothly on my dell 9350
My processor is AMD...I'm also getting this Intel error, I also get it when trying to boot Remix OS for PC. BOO!
Unfortunately, AMD doesn't HAXM, which Android Studio requires. Remix OS Player is based on Android Studio. Sorry to be the bearer of bad news... If there is news on this though, I'll update here. Thanks!
match_stick said:
My processor is AMD...I'm also getting this Intel error, I also get it when trying to boot Remix OS for PC. BOO!
Click to expand...
Click to collapse
ToXiC said:
and if the still presists, go to bios settings and enable "Virtualization Technology" from there! it will worK!
Click to expand...
Click to collapse
Confirmed - in BIOS settings (under "configuration" tab I believe) "Intel: VT" needs to be enabled. If it still doesn't work, try installing HAXM again by running remixemu\haxm-windows_v6_0_3\intelhaxm-android.exe.
Seems to be working for me now.
donwload from intel. os remix included file is v6_0_3\interhaxm-android.exe. but from intel was 6.0.4
I was able to 'install' the haxm.
Command Prompt(Admin) type bcdedit /set hypervisorlaunchtype off （Disable Hyper-V，Windows Phone Emulator will not work）, then "Restart Your PC".
I guess you install Visual Studio, this is because Windows Phone SDK opens during installation caused by Hyper-V, Windows Phone Emulator SDK needs to be realized with Hyper-v virtualization.
Note: bcdedit /set hypervisorlaunchtype auto （Enable Hyper-V）
https://software.intel.com/en-us/an...-execution-manager-end-user-license-agreement
There was a few window 10's that the binaries where corrupt. You can check to see if yours is corrupt by just using rar.