Can't install HAXM on WIndows 2012 Standard - Other Tools & General Discussion

I'm trying to install HAXM on Windows 2012 Standard and every time I get the message:
"This computer meets the requirements for HAXM, but Intel Virtualization Technology (VT-x) is not turned on."
I have tried all found solutions and it still won't install:
* I have the latest BIOS version
* VT-x and VT-d are turned on in BIOS
* Hyper-V is not installed / disabled
* I've tried "bcdedit /set nx AlwaysOn" and reboot
* CrystalCPUID and Intel detection tool of VT-x shows that its on
* there Isn't any anti virus software installed on the machine ( I heard it made problems to others)
Any help would be appreciated greatly.

Related

intel bay traill linux support?

hi everyone
ı' am new in here.
ı want to ask does INTEL BAY TRAIL (z3XXX) support to install linux installing? or not why ? (because bootloader or another thing etc..)
There is some variant of windows tablets on market but can ı install ubuntu, arch linux etc? does it support?
sorry my bad englısh
1a) UEFI/BIOS support. looks like for the Asus T100, Asus only gave a 32-bit UEFI bootloader, so there are hacks to go around it. not sure about other devices like Dell Venue 8 Pro (I don't have that much money to buy so many devices)
1b) Secure Boot option to be disabled. If you can't disable Secure Boot, there are ways to get around it (some distros provide a signed UEFI shim that preloads before grub2, but you'll have to get that shim working with 32-bit bootloaders if you hit the problem above in 1a)
2) SoC support. Intel has submitted the Bay Trail SoC to the linux kernel. However, there are still some parts missing (eg open source video driver xf86-video-intel has it somewhat supported with bugs)
here is my WIP on getting ubuntu working on my Asus T100.... only major thing missing is graphics driver, everything else (besides sound) is working
http://forum.xda-developers.com/showthread.php?t=2500078
Baytrail T100 grub won't boot kernel
paperWastage said:
1a) UEFI/BIOS support. looks like for the Asus T100, Asus only gave a 32-bit UEFI bootloader, so there are hacks to go around it. not sure about other devices like Dell Venue 8 Pro (I don't have that much money to buy so many devices)
1b) Secure Boot option to be disabled. If you can't disable Secure Boot, there are ways to get around it (some distros provide a signed UEFI shim that preloads before grub2, but you'll have to get that shim working with 32-bit bootloaders if you hit the problem above in 1a)
2) SoC support. Intel has submitted the Bay Trail SoC to the linux kernel. However, there are still some parts missing (eg open source video driver xf86-video-intel has it somewhat supported with bugs)
here is my WIP on getting ubuntu working on my Asus T100.... only major thing missing is graphics driver, everything else (besides sound) is working
http://forum.xda-developers.com/showthread.php?t=2500078
Click to expand...
Click to collapse
Having a hell of a time getting ubuntu to get past grub.
Tried both Asus T100, and Dell Venue 8 Pro
Rufus (GPT for UEFI + FAT + 64 kb+ bootable disk using ISO Image)
Tried x86_64: ubuntu 13.04, 13.10, Fedora 20
All 6 Combinations, Boot into Grub, but grub throws the following error message every time, when booting the kernel:
"Can't Terminate EFI Services", and go back to grub.
Tried both boot loader binaries: - bootia32.ubuntu_13.04_x64.zip, and bootia32_normal_configfile.zip
From main thread: http://forum.xda-developers.com/showthread.php?p=46861952#post46861952
After that grub error, USB devices are all disabled.
Not sure how to debug further, seems like a grub EFI issue, but can't confirm.
Tried grub debug, using "set debug=all", and the error occurs right after the EFI map is displayed.
Please advise on how to proceed - how can this happen on both T100 and V8P?
M$ ruined baytrail by requiring 32 bit EFI, on a 64 bit system!
I could be wrong, but I thought I remembered seeing a 32 efi folder in Ubuntu GNOME 14.04. I'm not positive because I used the 64 bit installation on my HP Pavilion x2 2-in-1. It has the bay trail graphics. I stumbled upon this thread because I was looking for improved driver support. Right now the only thing not working on my installation (besides bluetooth) is display brightness control.
BayTrailSucks said:
"Can't Terminate EFI Services", and go back to grub.
Click to expand...
Click to collapse
I saw this log from time to time when I've used binaries you've mentioned.
So I've recompiled grub myself from sources taken from: ftp.gnu.org/gnu/grub
I've used version 2.00
To compile grub I've used commands:
./configure \
--with-platform=efi --target=i386 --disable-nls \
--disable-grub-emu-usb --disable-grub-emu-sdl --disable-grub-emu-pci --disable-grub-mkfont \
--disable-device-mapper --disable-libzfs --disable-werror
sed -i -e '/gets is a/d' grub-core/gnulib/stdio.in.h
make -j 2 MAKEINFO=true
make -j 2 install MAKEINFO=true
and then to prepare bootloader binary I've executed:
i386-grub-mkimage -o bootia32.efi -O i386-efi -p /boot/grub ntfs boot cat efi_gop efi_uga elf fat linux keylayouts \
memdisk minicmd ext2 extcmd part_bsd part_gpt search search_fs_file chain \
loadbios loadenv memrw mmap msdospart scsi loopback
For kernel tests I've used kernel 3.12 from kernel.org and 3.13.0-rc8 from repository: git://people.freedesktop.org/~danvet/drm-intel
Kernel 3.12 booted fine when I've added 'video' parameter as was mentioned in paperWastage thread.
For kernel 3.13.0-rc8 I've to revert one commit, see more info in bug 71977 at bugs.freedesktop.org
After I've updated xf86-video-intel to 2.99.907 and libdrm to 2.4.52 I was able to run X server with acceleration:
# glxinfo | grep ren
direct rendering: Yes
GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control,
GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read,
GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control,
GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read,
OpenGL renderer string: Mesa DRI Intel(R) Bay Trail x86/MMX/SSE2
GL_NV_conditional_render, GL_AMD_draw_buffers_blend,
What about hardware accelerated video playback
What about hardware accelerated video playback?
vshalimo said:
What about hardware accelerated video playback?
Click to expand...
Click to collapse
It works. I can use GPU accelerated decoding in vlc compiled with libva support.
-bash-4.2# vainfo
libva info: VA-API version 0.34.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /kanapi_packages/libva-master/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_34
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.34 (libva 1.2.2.pre1)
vainfo: Driver version: Intel i965 driver - 1.2.3.pre1
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Simple : VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
Battery status
Patch for kernel for battery status has been just added to bug 69011 in kernel bugzilla (I can't put link here)
and it works on ASUS T100TA:
cat /sys/class/power_supply/BATC/uevent
POWER_SUPPLY_NAME=BATC
POWER_SUPPLY_STATUS=Discharging
POWER_SUPPLY_PRESENT=1
POWER_SUPPLY_TECHNOLOGY=Li-ion
POWER_SUPPLY_CYCLE_COUNT=8
POWER_SUPPLY_VOLTAGE_MIN_DESIGN=3750000
POWER_SUPPLY_VOLTAGE_NOW=4174000
POWER_SUPPLY_CURRENT_NOW=1172000
POWER_SUPPLY_CHARGE_FULL_DESIGN=8180000
POWER_SUPPLY_CHARGE_FULL=9595000
POWER_SUPPLY_CHARGE_NOW=9316000
POWER_SUPPLY_CAPACITY=97
POWER_SUPPLY_MODEL_NAME=SR Real Battery
POWER_SUPPLY_MANUFACTURER=Intel SR 1
POWER_SUPPLY_SERIAL_NUMBER=123456789

[FIX] Windows 8.1 Fastboot/Flashmode/ADB for Sony and Samsung devices

As you all may now, Microsoft pushed the new driver stack in Windows 8.1 so ALL (not only USB 3.0) devices must provide a BOS descriptor. Sony ADB and Fastboot doesn't, so Windows fails to enumerate the device which is reported in Device Manager as error code 43.
This also may help if you have a USB drive or mouse and it stopped working after you upgraded from Windows 8 to Windows 8.1.
Microsoft said that the fix will come in February but for people who don't want to wait I prepaired a dirty solution:
Microsoft published the update.
proof - see attachment.
THE PROBLEM IS NOW FIXED BY THIS UPDATE: http://support.microsoft.com/kb/2917929 - USE IT INSTEAD OF MY FIX!
Here is my old (dirty) solution:
HTML:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I repeat this is a REALLY DIRTY solution that may harm your system, personal data, hardware and/or cat.
Here are the steps:
0. Have a Linux or Windows LiveCD just in case something goes wrong
1. Download and extract files from attachment
2. Navigate to the folder corresponding to your system version (x86 = 32-bit, x64 = 64 bit)
3. Right-click franken-usb.bat and click "Run as Administrator"
5. Wait for it to finish and reboot the system. If everything went fine, you will boot your system successfully
6. Install ADB/Fastboot drivers just like on Windows 8
7. Connect your phone in Fastboot mode to your USB 2.0 port and check if it works
8. Enjoy and wait for official fix
How does it work:
It's not any kind of magic - it just replaces Windows 8.1's usbhub.sys and usbport.sys with Windows 8's ones.
Old files don't check for BOS descriptor so Fastboot can work.
Script updated - it should now actually copy the files but please double check if files were copied to C:\Windows\system32\Drivers!
Hope it helps you!
Regards!
So far it works (both adb and fastboot) on my computer. But it was necessary to copy these files manually.
Thank you! :good:
!! success !!
thank u bro , working great on win 8.1 pro 64 bit , fastbooted sony xperia LWW and flashed kernel like before ! :laugh:
just need to copy files manually though but that was so easy .:victory:
thanks! working perfectly 8.1 64bit
you're my hero
Looks like it works reading those comments! Gonna try it tomorrow!
Sent from my LT30p using xda app-developers app
EDIT:
doesnt work for me! It now doesnt show the driver blabla it shows s1 fastboot. And the phone doesnt stay in fastboot
EDIT 2:
nevermind fixed it with installing drivers via flashtool.
Thankyou my hero!
Works on me too! Thanks!
awesome!! you are my hero!!!!:good:
works on windows 8.1 x64 usb 2.0
thanks great fix
I only needed to replace manually files, but yes! Now it works perfectly on Win8.1 x64 on USB2.0 computer!
My problem finally solved, thanks to you janek2012! :good:
Steph310 said:
I only needed to replace manually files, but yes! Now it works perfectly on Win8.1 x64 on USB2.0 computer!
My problem finally solved, thanks to you janek2012! :good:
Click to expand...
Click to collapse
Yea me too replaced manualy, but all works fine. At last phone connect in fastboot and flash
Dobra robota @janek
yes working good with replace manually files
thanks bro
Finally Success!!
You are on the top of my "Good Guys" list!! After manually copying the two files, fastboot is now working on my Win 8.1 x64 USB 2 computer. Nothing else worked. I tried editing the registry, updated USB drivers, replaced with universal drivers, intel drivers and nothing worked except your solution.
Many thanks.
janek2012,
Many thanks for this workaround - it saved me having to wait for Microsoft's fix to perform the update to Windows 8.1. I would recommend that you update your archive with a more reliable "restore" script, or at least update your initial post with the information. Rather than moving the .bak files back into place, it makes much better sense to utilise Windows Resource Protection/sfc. These two commands will repair the two files:
Code:
sfc /scanfile=%systemroot%\system32\Drivers\usbhub.sys
sfc /scanfile=%systemroot%\system32\Drivers\usbport.sys
If the integrity violations are not repaired correctly, future hotfixes/updates from Microsoft that contain updated USB drivers (including the specific fix for this issue) may fail to install.
thnakyou so much man.....wasted my whole day for this,now i got fastboot usb..
Did not work for me, now left with no functional usb ports. How do I restore the .bak files?
Thanks SO MUCH for this!!!!
I had tried everything and only your solution works!!!
Art2Fly said:
Did not work for me, now left with no functional usb ports. How do I restore the .bak files?
Click to expand...
Click to collapse
Just navigate to \windows\system32\drivers, and move the current usbhub.sys and usbport.sys (should be v6.2.9200.16384)
and then rename
usbhub.sys.bak to usbhub.sys and
usbport.sys.bak to usbport.sys
(should be v6.3.9600.16384)
Then reboot.
Worked without any problems (had to manually coppy the files to the system32\driver folder )
sorry, but can't hit the Thanks-Button more than one time
Using HDH with HBoot: 0.85.0024
Win8.1 (Install from scratch - no update installation) 64Bit
intel 4th Gen
ADB was working with no problem from very begining but the Fastboot I got just working after this nice and easy tutorial/fix
Thanks a tonne
Today my Win 8.1 64bit install updates from microsoft, and fastboot/flashmod work without this fix
Art2Fly said:
Did not work for me, now left with no functional usb ports. How do I restore the .bak files?
Click to expand...
Click to collapse
just copy the two files in this zip and manually replace them with the one in system {to open drivers, just press windows+r and type drivers and press enter}
ALWAYS HAVE A BACKUP
DeadMan2k said:
Today my Win 8.1 64bit install updates from microsoft, and fastboot/flashmod work without this fix
Click to expand...
Click to collapse
Yes!
Just Install FlashTool Driver

See phone's battery status on computer screen

I have made a program to display the percentage of your phone on your computer. Requirements:
[*]Computer that can run bash - Linux WILL work, Mac might.
[*]USB-to-phone cable
[*]ADB enabled on phone
Has been tested on the following:
LG P716 Jelly bean stock- One Works the other doesn't
LG P716 KitKat - Works
LG P500 with CM11 (by mukulsoni)and rooted- Works
Samsung S3 stock - Doesn't work
HTC One S (Thanks LS.xD)
Samsung Galaxy Ace II (Thanks LS.xD)
To run, use
Code:
cd,
to navigate to the folder containing the files then the Terminal folder. After that run
Code:
./BatteryStatus.sh
Your help is greatly appreciated to porting it to Windows/Mac and adding new devices. If you have got screenshots or working devices, feel free to tell me or pm me about these. I will add them to this list.
Secondary mirror: http://www.mediafire.com/download/n2qbb537jpn22p3/batteryStatus.zip (contains both terminal & alpha graphical version)
Warning:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
A lot.
XDA:DevDB Information
BatteryStatus, Tool/Utility for all devices (see above for details)
Contributors
wilk.gr76
Version Information
Status: Stable
Created 2015-04-02
Last Updated 2015-04-02
wilk.gr76 said:
I have made a program to display the percentage of your phone on your computer. Requirements:
Computer that can run bash
USB-to-phone cable
ADB enabled on phone
Has been tested on the following:
LG P716 Jelly bean stock- One Works the other doesn't
LG P716 KitKat - Works
LG P500 with CM11 and rooted- Works
Samsung S3 stock - Doesn't work
Your help is greatly appreciated to porting it to Windows/Mac and adding new devices. Screenshots are coming soon
XDA:DevDB Information
BatteryStatus, Tool/Utility for all devices (see above for details)
Contributors
wilk.gr76
Version Information
Status: Stable
Created 2015-04-02
Last Updated 2015-04-02
Click to expand...
Click to collapse
I'll give other linux versions a try later this day helping you to figure out on which linux environments it works. Read out the battery level (with terminal) works on both of my phones, so you could add them to the supported list as found in my signature.
On 32bit Linux Mint KDE: CMD + GUI (find all libs but crashes) work with both phones. So the error occured as the 32bit libs can't be handled correctly on a 64bit os for GTK even with multiarch activated.
LS.xD said:
I'll give other linux versions a try later this day helping you to figure out on which linux environments it works. Read out the battery level (with terminal) works on both of my phones, so you could add them to the supported list as found in my signature.
On 32bit Linux Mint KDE: CMD + GUI (find all libs but crashes) work with both phones. So the error occured as the 32bit libs can't be handled correctly on a 64bit os for GTK even with multiarch activated.
Click to expand...
Click to collapse
The graphics is done through Zenity. I just checked, Zenity has problems running on 64-bit systems. You might want to try installing zenity like this:
Code:
sudo apt-get install zenity:i386
and then changing the code in the .sh file from ./zenity to zenity. Might work, might not. My computers are all 32-bit.
wilk.gr76 said:
The graphics is done through Zenity. I just checked, Zenity has problems running on 64-bit systems. You might want to try installing zenity like this:
Code:
sudo apt-get install zenity:i386
and then changing the code in the .sh file from ./zenity to zenity. Might work, might not. My computers are all 32-bit.
Click to expand...
Click to collapse
I'dgive it a try, but you actually removed the GUI version and I have it not stored. The screensgots are attached.
EDIT: Zenity:386 can't be installed on my 64bit system due to not resolveable dependencies.
LS.xD said:
I'dgive it a try, but you actually removed the GUI version and I have it not stored. The screensgots are attached.
Click to expand...
Click to collapse
Just changed it. You can use the mediafire link or the in the downloads tab, graphical.zip
Thanks for the screenshots!
UPDATE: As Microsoft will support BASH in the Anniversary (a.k.a. Redstone I) update, it will be compatible with all 3 'big' platforms. Yay!

.net 3.5 installation

I can't install .net framework 3.5 on my dell laptop..i've tried all the steps in google....using group policy editor....by enabling it on program and features ....by offline installation...by uninstalling security updates....also by using dism command....while using dism command it says log file not found...but when i go through the path its there..~! For offline installation i have not found sources/sxs/ folder on my C: drive.....my laptop is 64bit 8.1 pro ...i'm behind this for almost 1 month...!
Note: while installing most of the pc says "install this feature" but mine says " download and install this feature"
When i connect to internet its not downloading anything...!
Hello mate, this link may be useful. Btw if it is enabled in program features already that means you already have it installed 0_0.

Can NOT install blissos

HW: x86 PC (intel integrated graphic card + NVIDIA graphics card)
SW: Blissos 14.3 (since nvidia card is poorly supported on x86 android, in android-x86_64_defconfig, comment out all NOUVEAU related configs)
Prerequisite: In BIOS, video setup -> IGD (expect to use intel graphic card)
Steps:
1) Install Ubuntu 20.04
2) Use rufus to write .iso image into U disk
3) Insert U disk into x86 PC, reboot x86 PC
4) From boot options, if choose 1st option to start Blissos directly // it's OK to start
5) From boot options, if choose installation of blissos // Why?? display screen is black, can't see any log output, after a while, blocked here, have to ctl+alt+del to reboot system
6) Power off x86 PC, unplug the NVIDIA graphics card
7) Start X86 PC again, it's OK to install Blissos!
8) Power off x86 PC again, plug the NVIDIA graphics card
9) Start X86 PC again, it's still OK to install Blissos!! // Why??
QA:
In step 5, since display screen is black, can't see any log output, it's difficult to know what is happened, could you please check it and give some comments?
After step 6 ~ step 9, if NOT change BIOS to default setting, it's OK to install Blissos for further installations,
for my special enviroment, NVIDIA graphics card of most x86 PCs can't be unplugged, how can I handle this case?
Dear experts, @electrikjesus and @HMTheBoy154 , could you have a look at this issue? thanks a lot

Categories

Resources