and tired all the forms of installing win 7 on my shift can figure to make the touch screen and the resolution work at all ..... who ever has installed it plese tell me step by step ..... i have tried since i have both version the net book and the full win 7 thanksss
all the posting i have read have different ways to intall it but none have worked for me ;-(
To get the touchscreen working set the Tablet PC and Human Interface Device Access services to automatic startup at first boot
ok i tried but
can u tell me the steps u took to intall every driver as every oder post here has different ways thanks again for responding
Just enable the two services above in services.msc and follow the normal windows 7 guide.
Get the drivers here
thanks
all working wonderful the best os for my shift
Hello all.
First of all, before people shooting at me and saying "please search", I come from many Google and xda search with "MacOs, download mode, failure vm, virtual machine, odin , kies" in every combination you can imagine and no result.
So, the problem is the following one:
I remarked, with some friends from a french forum that we all succeed to use KIES in a virtual machine and connect the phone:
Click for full size - Uploaded with Skitch
That work like a charm.
Then w wanted to flash, then reboot the phone in Download mode ( yellow android at work ) and then there is a big crash telling us that the device is not recognized:
"unable to connect USB device to virtual machine"
Click for full size - Uploaded with Skitch
I would really be pleased to have more info on this issue and if we are only a little group to have this issue.
For info, I am using MacOS Snow Leopard and the trial of parallels desktops 6.
It doesn't work with VMware Fusion either. Must be something to do with the USB interface on Samsung.. I've heard some people have it going on Virtualbox running on Linux - but not Mac.
Works fine on VirtualBox on Ubuntu.
Why don't you give Heimdall a go? Haven't tried it personally, but OS X is in the list of supported OSes
Maybe I found the explanation , thanks to ed link:
Although Heimdall runs on OS X all Galaxy S phones tested thus far contain a bug in the secondary boot loader that prevents the phone registering itself with OS X. This may change if Samsung release an updated secondary boot loader.
Click to expand...
Click to collapse
Maybe there is the same problem.
Does the secondary boot loader has a link with download mode? If yes, that might be the problem!
profete162 said:
Maybe I found the explanation , thanks to ed link:
Maybe there is the same problem.
Does the secondary boot loader has a link with download mode? If yes, that might be the problem!
Click to expand...
Click to collapse
Saw that today too.. .pretty sure its the issue since it affects all parallels, fusion and virtualbox on Mac OSX.
profete162 said:
Maybe I found the explanation , thanks to ed link:
Maybe there is the same problem.
Does the secondary boot loader has a link with download mode? If yes, that might be the problem!
Click to expand...
Click to collapse
Yes, download mode functionality is provided by the secondary boot loader. If you really desperately want to get it working with OS X then you would need to download the source for, modify and install a custom IOUSBFamily.kext that contains a work-around specifically for the Galaxy S.
The only options for we Mac users right now are to find a Windows machine, install boot camp on your Mac (then point your vmware machine to it to save duplicate Windows wasted space), or possibly find a way to boot from an external drive with Windows (like a thumbdrive or livecd if possible).
distortedloop said:
The only options for we Mac users right now are to find a Windows machine, install boot camp on your Mac (then point your vmware machine to it to save duplicate Windows wasted space)
Click to expand...
Click to collapse
Exactly what i have done. And I HATE it :|
I had this same problem, and I just saw this thread after spending hours last night trying to figure out why XP in Parallels stopped recognizing the phone as soon as it went into download mode. So irritating!
it works for me on VMware 7 + WinXP SP3
because my Win7 64bit PC is crazy it won't recognize the phone randomly, twice it bricked my phone doing the Flash on the Host PC
so after setting up my ROM FLASH VMware machine, now i no longer have problem
stupid windows, no time to mess with the system registry to figure out what is the madness with the USB detection
i'm pretty sure you should have no problem as well if you use VMware 6.5
I posted this in the Heimdall thread but thought I should let followers of this thread know also.
I sent Samsung the OS X USB failure log and since then Samsung have informed me that the Froyo update (specifically the Nordic version released October 15) includes a fixed bootloader which should allow the phone to be recognised in OS X. I'm yet to verify this but hopefully this is the case!
Hello together,
I have a Odys Winpad V10 with Windows 8.1 pre installed.
So i try to install android x86.
but when i come to the boot screen, the screen will be black.
UEFI said that secure boot is off, and i can boot from the Stick android x86 dont start.
I tryed the 5.1, 6.0, and 4.4 Version.
is there a working solution to install android x86 on a uefi tablet?
Thanks alot.
Christian
This is a wrong place to ask for that. You can try asking it there https://forum.xda-developers.com/android/help
Thank you i will try that
Hi there, I installed on my Toshiba Satellite laptop Windows 7 & Android 4.4.4. It works no so bad.
My problem is that the boot is so fast that I can't choose the SO. I don't know how to fix. Anyone can help me. Thanks in advance.
Ed
Which did you install first
That will be the first step
Ie installed Android then win7
Or
Installed win7 then Android
I'm trying out DeX since my computer is down. I'm basically wanting to play a game I have installed on Windows and I've actually never configured WineHQ before.. I've heard there's an Android version and that for my phone, I'll need the ARM version vs the x86 version. Please correct me if I'm wrong about that. I did inadvertantly mess up and get the x86 version but I didn't really see it install so then installed the ARM version.
I launched it, then it hands on SETTING UP WINDOWS ENVIRONMENT.
Does this process even work or is this one of those things where I'd need to have a rooted device?