Want to try WM5.0 out for your self? I originally posted this on ipaqhq.com but I figured this forum is more of a target for such information .
1) Get the emulator from here (login with your MS passport, then enter MSDEVICE when it asks you for a GuestID)
2) Install the emulator.
3) Delete "C:\Program Files\Microsoft\Device Emulator Preview\PPC_2003_SE\PPC_2003_SE_WWE_ARMv4.bin"
4) Go here (or here without genuine advantage check) to download the WM5.0 SDK (it's 174MB so be patient!).
5) Go here to download ZipZag.
6) Install ZipZag.
7) Go here to download MSI extension support for ZipZag.
8) Extract the above file to "C:\Program Files\ZipZag"
9) Run ZipZag and open "Windows Mobile 5.0 Pocket PC SDK.msi" in it.
10) Sort the files by Size (largest to top)
11) Extract the biggest file (sdkfiles.cab)
12) Using winrar open this file.
13) Sort the files by size (again, largest to top)
14) Extract "_208PPC_USA_bin" to "C:\Program Files\Microsoft\Device Emulator Preview\PPC_2003_SE\PPC_2003_SE_WWE_ARMv4.bin" (the file you deleted earlier!)
15) Go to "Start -> Programs -> Microsoft Device Emulator Preview -> Emulate Pocket PC-WM 2003 SE(Cold Boot)" - Note that the smartphone and square versions WONT WORK!
16) WAIT (about 30 seconds) for it to boot. When faced with the new welcome screen, click on it then wait another 30 or so seconds.
17) Enjoy your sneak-peek of WM5.0!
Attached is a proof shot of it working which also illustrates the newest feature - persistant storage! Thats the new "Memory" control panel application!
Cool Thanks
I have my sneak-peek on my QTek 2020
10x !! i'm testing now !
edit - it's work :lol: !! but limited by the low memory.... how to increase this ?
Emulator is great
@all,
I am using the Mobile Device Emulator at work to test applications before installing on real device. It is great. If you have the latest Visual Studio or other development tool then you have the emulator. It is included. The Mobile SDK you have to download.
Greetings,
Bitfrotter
Can u pls send me an e-mail with the files cuz i cant extract and to anything pls mail me at [email protected]
Do you really want a WM5 emulator now, in 2007, when WM6 is already out!
This is a very old thread (notice the 2005 date stamps) and I'm not sure if you thought this thread referred to something else.
Run JB 4.2.2 NATIVE (EFI bios only)
Diualboot with win8/linux/osx. - This is NOT a x86 emu - its bare metal
https://01.org/android-ia/documentation
Required materials:
•1GB or larger USB thumb drive
•A supported target device
•A laptop or PC running Linux, Windows, or Mac OS with working internet connection
Step 1: Back up your existing OS and all data on your device. The Android-IA installer will erase everything and repartition your hard drive automatically.
Step 2: Download the latest installer image for your device from the Downloads page.
Step 3: Prepare the USB thumb drive
Linux users:
•Unzip the downloaded file: `unzip your_installer_file.zip'
•Insert the USB thumb drive into your machine
•Open your terminal application and find the device name of the thumb drive. Run `dmesg' and look near the end for a name like "/dev/sdX" where X is a letter.
•Unmount any partitions that were automatically mounted: `sudo umount /dev/sdX*' (Where X is the letter from above)
•Write the live.img file from the extracted zip to the USB flash: `sudo dd if=live.img of=/dev/sdX bs=1M conv=fsync' (Where X is the letter from above)
Windows users:
•Extract the installer image from the downloaded zip file
•Download "Image Writer" application from https://launchpad.net/win32-image-writer/ and extract it to a folder of your chioce.
•Insert your USB drive into your computer.
•Find the drive letter of your USB drive by opening 'My Computer' on the desktop.
•Run Win32DiskImager.exe from Image Writer's directory.
•In Image Writer's window, select the installer.img you extracted from the downloaded zip
•In Image Writer's window, select your thumb drive's letter that you found in 'My Computer'
•Click "Write" and wait until the process is over.
Mac users:
•Extract the installer image from the downloaded zip file
•Open the Terminal (under Utilities)
•Execute `diskutil list' to get the current list of devices
•Insert your USB drive into your computer.
•Execute `diskutil list' again and determine the device node assigned to your flash media (e.g. /dev/diskN)
•Execute `diskutil unmountDisk /dev/diskN'
•Execute `sudo dd if=live.img of=/dev/diskN bs=1m'
•Execute `diskutil eject /dev/diskN' and remove your flash media when the command completes.
Step 4: Prepare device for installation:
•Set the device to boot from the USB thumb drive (device-specific instructions can be found on the devices page.
•Make sure "UEFI Boot Support" is enabled in the BIOS.
Step 5: Install the system.
• Plug in the USB thumb drive with the Android-IA installer image created in step 1
• Power on the device
• From the boot menu, choose "Install Android to hard disk"
• Wait until the installer finishes
• Unplug the USB thumb drive
• Power off the device by holding down on the power button for 10 sec., then power on the device and choose "Boot Android system" (or let the countdown timer expire)
You're done! Enjoy your Android-IA device.
Click to expand...
Click to collapse
Move post if in wrong section plz...
Sent from nexus 4 AOSP
Hello.
I installed the latest Android-IA (android-4.2.2_r1-ia1) on my Acer Iconia W700, and it works perfectly. The only downside (however, huge one) is the lack of libhoudini - without it half of android apps refuse to load on x86 processor. Which, by the way, scores ~70000 in Antutu (!)...
I searched everywhere, but there's just too little information on both libhoudini as well as Android-IA . Please, can anyone help in porting this library to Android-IA? I know it is not open source, but so are gapps, and Android-x86 already uses libhoudini. So there shouldn't be any real difficulties...
WBR, Draco.
Drakosha said:
Hello.
I installed the latest Android-IA (android-4.2.2_r1-ia1) on my Acer Iconia W700, and it works perfectly. The only downside (however, huge one) is the lack of libhoudini - without it half of android apps refuse to load on x86 processor. Which, by the way, scores ~70000 in Antutu (!)...
I searched everywhere, but there's just too little information on both libhoudini as well as Android-IA . Please, can anyone help in porting this library to Android-IA? I know it is not open source, but so are gapps, and Android-x86 already uses libhoudini. So there shouldn't be any real difficulties...
WBR, Draco.
Click to expand...
Click to collapse
Antutu score 70000!? really? You are using the i5 model?
Drakosha said:
Hello.
I installed the latest Android-IA (android-4.2.2_r1-ia1) on my Acer Iconia W700, and it works perfectly. The only downside (however, huge one) is the lack of libhoudini - without it half of android apps refuse to load on x86 processor. Which, by the way, scores ~70000 in Antutu (!)...
I searched everywhere, but there's just too little information on both libhoudini as well as Android-IA . Please, can anyone help in porting this library to Android-IA? I know it is not open source, but so are gapps, and Android-x86 already uses libhoudini. So there shouldn't be any real difficulties...
WBR, Draco.
Click to expand...
Click to collapse
I remember finding a manual install of libhoudini somewhere but it didnt work. That was with the february version of A-IA, though.
Sent from my 700T using XDA Premium HD app
Drakosha said:
Hello.
I installed the latest Android-IA (android-4.2.2_r1-ia1) on my Acer Iconia W700, and it works perfectly. The only downside (however, huge one) is the lack of libhoudini - without it half of android apps refuse to load on x86 processor. Which, by the way, scores ~70000 in Antutu (!)...
I searched everywhere, but there's just too little information on both libhoudini as well as Android-IA . Please, can anyone help in porting this library to Android-IA? I know it is not open source, but so are gapps, and Android-x86 already uses libhoudini. So there shouldn't be any real difficulties...
WBR, Draco.
Click to expand...
Click to collapse
Did you ever find a solution to this?
DJDrew said:
Did you ever find a solution to this?
Click to expand...
Click to collapse
Hi there
I'd also be glad to hear more about that...From what I could gather so far, there is no fully working ARM translator / libhoudini solutions for android IA. Hence the only solution would be to switch to android x86...
Change dpi and get bluetooth working with android and windows 8.1 at the same time
Do these changes if you are confident in your skills. I'm student and quite busy so if you ask something it can take some time for me to answer. Damages you might do to your system are your own responsibility. I have tested these instructions with Acer W700 on android-4.2.2_r1-ia3 and can confirm that they worked for me.
First changing dpi from original 213 to 160:
1. Get file manager on android like ES file Explorer
2. R/W rights to whole system on android
3. From root go to /system/etc/machine-props/
4. Open acer-w700.prop with ES Explorer and edit line "ro.sf.lcd_density = 213" and change 213 to 160
5. Reboot android and system should now be 160 dpi
Now about that bluetooth. I find it annoying that you have to pair your bluetooth mouse and keyboard again every time when you switch between android and windows 8.1. So I did research and found a way to fix this problem and here's how to do it. I can confirm that this works with Acer bluetooth/cover keyboard and MS Sculpt touch mouse.
1. Pair your bluetooth devices first with android and the with Windows
2. On Windows download PsExec
3.Then from downloaded file copy PsExec.exe in Windows to directory C:\Windows\System32 or to directory where your System32 folder is.
4. Write in the search cmd and run it as administrator
5. Then use command: psexec -s -i regedit.exe
6. Now go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Keys
7. From \Keys you can find your paired bluetooth devices. First there is the devices bluetooh mac address and 32 numbers long linkkey. Now write those linkeys and mac addresses up or copy them.
8. Now everything is set on Windows side. Next boot to android.
9. On android you need again for example ES file Explorer and R/W rights
10. With file Explorer fro root go to /data/misc/bluedroid/
11. Open file called BT_config.xml
12. From text find your devices using mac address
13. When you find you devices mac addres scroll down and you should see line with linkkey and 32 number code.
14. Now take that 32 number code you got from Windows
15 You have to change it little so the linkey works and here how it's done:
for example your Windows linkkey is "12345678qwertyuiasdfghjkpoiuytre" now set it as 8 number clusters like this
"12345678 qwertyui asdfghjk poiuytre"
Now you have to reverse those 8 number clusters
Take the set on far right "poiuytre" and mark it like this "po iu yt re"
Now reverse those pairs like this "re yt iu po"
Now "reytiupo" this is the first line in the new linkkey
Do the same for other three cluster. After it's done this example linkkey looks like this "reytiupojkghdfasuityerqw78563412"
16. When you have your modified Windows linkkey ready you can just replace the old one from the file BT_config.xml
17. Now just reboot android and your keyboard and mouse should work.
I've found that sometimes when switching from Windows to android bluetooth doesn't connect. Just reboot android and your bluetooth devices should connect.
I would have posted this on deveopers site where people visit more often but you need 10 posts and this is my first one so if you can you should link my post there so more people can enjoy these instructions.
Thank you for reading this and don't forget to like it :good:
Anyone know where to find the source code for this?
Hi all ,
This topic is about how to mount your Android device and have it transferring files easily & smoothly using Linux on your PC.
- This topic is related to solving the unstable file transfer between the linux system and MTP file system included in Android version 4.xxx & Higher ( Starting from Ice Cream Sandwich - ICS ).
- All Android version before ICS should not continue reading , as their devices should be read as ( Mass storage Device ) , in other words , the Linux OS will read devices as if it was a USB flash memory.
- The is solution for the laggy Folder opening , Solving the problem of which the files transfer suddenly stops before completing the transfer , specially with big files such as Films , Albums ,...etc.
- I'M NOT SURE that this is going to work with all ICS , JB & Higher devices but the below was tested on a Samsung Tab 2 P5100 device running Jelly bean ( JB ) 4.1.2 official stock ROM , & The below worked perfectly for me.
- Using Linux Mint 14 Cinnamon ( MINT is based on UBUNTU ) / 64 Bit version / Kernel Upgraded _unofficially_ to the latest stable kernel release 3.9.2
1. get Android SDK for Linux from : developer.android.com/sdk/index.html
2. Unpack it to your location
Note: if you have already downloaded Android SDK before, check that the version of SDK tools is latest.
3. turn on Debug mode in your Samsung tab.
4. run the command:
[your location]/android-sdk-linux_x86/tools/ddms
OR just open the folder TOOLS from the extracted folder & Run DDMS ( RUN it normally , Not RUN IN TERMINAL).
5. Click in menu Device -> File Explorer
Here you drag-n-drop your files to any location on your device.
Source (Including snapshots) :
- misha.beshkin.lv/how-to-copy-files-to-samsung-galaxy-ii-tab-from-linux-via-usb/
Thank you & Sorry if my topic looks messy , this is my first time here.
mehrdadfisher said:
This is my own experience as well.
Would it be possible please send me the details.
Click to expand...
Click to collapse
Hi there , wud u plz clarify what do u mean by the details ? , I think the details are already mentioned up there , If you are talking about using the developer's SDK to transfer files.
Featured on XDA-Portal
Hi all !
Welcome to the tutorial of how to install Android x86 !
I've written this extensive guide, it is as detailed as possible and it is written as easy and as understandable for new user.
This guide is, however does not put guarantee of any action you've done outside the guide itself. Anything such as partitioning, OS installing or uninstalling is not guaranteed by me or by anyone at XDA. You're doing this at your own will.
Preparations :
1. Any computer / device that supports installation via flash driver / disc (or have enough space for VM)
2. Any media that is mentioned below (either flash drive, CD / DVD, or VM)
3. Android x86 ISO
4. 2 GB of free or clean partition is recommended (you can use more than 2 GB to increase internal storage)
1. Download Android x86 ISO.
You can download it here
If your device isn't listed there, download Generic ICS build here : Click ! [You need to unzip after download]
The newest KitKat build is unified and it's also generic. It supports wider range of hardware, but it does not support LAN device (yet). You can download it here
Follow the guide with your preferred installation method.
If you're using USB stick / Flash Drive :
2. Download UNetbootin
You can download it here : Click !
On Ubuntu (11.04 and higher, or its derivatives) you can type : sudo apt-get install unetbootin
On Arch (or its derivatives) type : pacman -S unetbootin
3. Run UNetbootin, select the Android x86 ISO
4. Select USB drive (make sure you don't select your HDD partition), then click OK
5. The UNetbootin will copy and install Android x86 live image & installer to your flash drive
6. Reboot your device after the process is completed
7. Boot to Boot Device Selection (in BIOS image), after you entered it, select your flash drive
8. There will be a GRUB menu generated by UNetbootin, select Install Android x86 to hard disk
9. Wait until it loads
10. Select partition to install Android x86
11. If you're unsure, don't format the partition
12. There will be a prompt, 'Install GRUB bla-bla-bla', if you use Windows, select yes. Another prompt will appear, select yes again.
If you've installed GRUB, do not select yes.
13. Another prompt, 'make system r/w', select yes (this enables root and read write access to your system partition)
14. If you're using Android x86 4.0.3 and older, you'll be prompted to install virtual sdcard, input 2GB (maximum size)
15. Reboot your device
If you're using CD / DVD
2. Burn the Android x86 ISO
3. Reboot your device, go to Boot Device Selection menu, select the CD / DVD
4. You will see Android x86 GRUB menu, select Install Android x86 to hard disk
5. Wait until it loads
6. Select partition to install Android x86
7. If you're unsure, don't format the partition
8. There will be a prompt, 'Install GRUB bla-bla-bla', if you use Windows, select yes. Another prompt will appear, select yes again.
If you've installed GRUB select no (installing it will break your GRUB configs)
9. Another prompt, 'Make system r/w', select yes (if you like modifying your Android x86)
10. If you're using Android x86 4.0.3 and older, you'll be prompted to install virtual SDCard, input 2 GB (maximum)
11. Reboot your device
If you're using it as virtual machine :
2. Set up the VM (RAM set to min 512 MB), tweak the configuration to match your need
3. Make sure you've loaded the ISO file in the VM menu, load the VM
4. A GRUB menu generated by Android x86 will appear, select the last option (Installation - Install Android x86 to hard disk)
5. Wait until it loads
6. Create a new partition (Navigate to New, , set to maximum size, navigate to write, done, navigate to quit)
7. Install Android x86 to the new partition
8. Format the partition to ext4
9. Answer 'yes' to 'Install bootloader GRUB bla-bla-bla'
10. Answer 'yes' again to 'make system r/w' (enables root and read write access to your partition)
11. If you're asked for sdcard, then input 2GB (the maximum size is 2GB, if your partition is smaller input suitable size for your partition)
12. Reboot when the process is done
How to add Android x86 to GRUB Menu
For GRUB 1.97 - 1.99 / 2.00
1. To make it easy, install GRUB Customizer
Type these into terminal emulator :
Code:
sudo add-apt-repository ppa:danielrichter2007/grub-customizer
sudo apt-get update
sudo apt-get install grub-customizer
2. Open GRUB customizer, make a new GRUB entry.
3. Open 'Sources' tab, type these :
Code:
[B]set root='(hd0,4)'[/B]
search --no-floppy --fs-uuid --set=[B]root e1f9de05-8d18-48aa-8f08-f0377f663de3[/B]
linux [B]androidx86[/B]/kernel root=UUID=[B]e1f9de05-8d18-48aa-8f08-f0377f663de3[/B] quiet [B]androidboot.hardware=generic_x86[/B] SRC=[B]/androidx86[/B] acpi_sleep=s3_bios,s3_mode
initrd [B]androidx86[/B]/initrd.img
Pay attention for the bolded part, here's what to change :
1. set root='(hd0,4)' : Change the (hd0,4) to partiton Android x86 is installed.
The hd0 means sda, so if you install it to sdb, it'll be hd1 and so on.
The hd0,4 means the partition number, in my case, hd0,4 means sda4. So if you install it on sda6, it'll be hd0,6.
2. --set=root e1f9de05-8d18-48aa-8f08-f0377f663de3 : The random number here is the UUID of partition Android x86 is installed
You must change it to correct UUID, you can easily got UUID by creating new entry in GRUB Customizer then go to Options tab, then select the 'Linux' option in dropdown. You'll see partition dropdown, select your partition. Open the source tab, you'll see the UUID there.
3. androidx86/ : The root of Android x86
Change it into your Android x86 root. You can see what's your Android x86 root by navigating to Android x86 partition, and you'll see a folder name started with 'android', that's the root of your Android x86
4. androidboot.hardware : Your device, of course.
Note : If you're using Android 2.3 - 4.0.3, change it to androidboot_hardware
Here's the list of hardware :
Code:
- generic_x86 : If your hardware isn't listed, use this
- eeepc : EEEPC laptops
- asus_laptop : ASUS laptops (supported ASUS laptops only)
GRUB 2.0 tutorial is the same like GRUB 1.97-1.99.
-------------
FAQ
-------------
Q : Does this work on my device ?
A : Try it ! There's generic build which supports many device.
Q : Which release should I pick ?
A : Generic is recommended (if your device isn't listed in download list), if your device is supported (like EEEPCs for example), pick one for your device. Do take a note that newer builds uses unified image, which means it supports wide range of hardware.
Q : Will this overwrite my old OS ?
A : As long as you install it in different partition and you did the right setup, you are good to go !
Q : Why does my network / touchscreen / mouse / etc, doesn't work ?
A : Mostly this is a driver problem. Try to use newer / older release. If it doesn't work, try different build for other device (there's a chance this will fix your problem)
Q : Does Android x86 works on USB disk (as a Live Image / as an OS itself) ?
A : It does, I have tested it on Gingerbread and ICS release.
Q : Why deep sleep / suspend doesn't work on my device ?
A : This is one of the issue on Android x86. The developer might be working on a fix.
Q : It doesn't work on a VM setup !
A : Check your configuration and virtual disk, Android needs at least 2GB of free space.
Q : Why does games feel choppy when played ?
A : This is because the game uses ARM libs / libraries which is not optimized for Android x86 (which uses ARM to x86 translator by Intel). On newer build, like unofficial Lollipop release doesn't include ARM to x86 translator, so it can't execute any ARM libraries or binaries.
Q : Android 4.4.2 RC-1 hangs on bootscreen (the flashing Android logo / tty1 terminal) !
A : Check your hardware, if you're using x64 probably the x64 isn't supported yet. Also, try using older release.
Q : There's no Play Store !
A : Sometimes, nighlies build (as Custom ROMs user calls it) is uploaded, this type of build doesn't have GApps. Also, if you're using deprecated release (old release), they have Android Market instead of Playstore.
Q : Can you flash .zips in this ?
A : You can, but it's not recommended.
Q : Play Store only have small amount of app !
A : Because Play Store detects your device as Android with a x86 CPU. This kind of CPU isn't widely used by apps in Play Store (most CPU in Android phone is ARM)
wow awesome guide :good:
Desktop
Does this also work on a desktop?
Rami1997 said:
Does this also work on a desktop?
Click to expand...
Click to collapse
Bro, any computer. Be it a desktop, netbook, ultrabook, MacBook, Linux computer, etc
F4uzan said:
Hi All !
I'm going to post a tutorial, how to install Android x86 to your laptop & netbooks (works on Personal Computer too).
So, let's start !
Preparations :
1. A working laptop & netbooks
2. R/W CD / Bootable USB stick (flashdisk)
3. Android x86 ISO
4. Free partition :
- 2 GB for Froyo - ICS
- 8 GB for JellyBean 4.2 - JellyBean 4.3
- 10 GB for KitKat 4.4.2
1. Download Android x86 ISO.
You can download it here : Click !
If your device brand is listed there, download Generic ICS build here : Click ! [You need to unzip after download]
If you're using USB stick :
2. Download UNetbootin
You can download it here : Click !
On Ubuntu (11.04 and higher) you can type : sudo apt-get install unetbootin
3. Run Unetbootin, select the Android x86 ISO
4. Select USB drive (instead of Hard Disk), then click OK
5. The UNetbootin will install Android x86 live image & installer to your USB stick
6. Reboot your device after the installation is completed.
7. Boot to Boot Device Selection (in BIOS image), after you entered it, select USB2.0 / USB4.0 / USB Disk (or something similiar)
8. There will be a GRUB like menu generated by UNetbootin, select Install Android x86 to hard disk
9. Wait until it to load
10. Select partition to install Android x86
11. If you're unsure, don't format the partition
12. There will be a prompt, 'Install GRUB bla-bla-bla', if you use Windows, select yes. Another prompt will appear, select yes again.
If you're using Ubuntu, select no
13. Another prompt, 'Make system r/w', select yes (if you like modifying your Android x86)
14. If you're using Android x86 4.0.3 and older, you'll be prompted to install virtual SDCard, input 1800 MB / 1.8 GB
15. Reboot your device
If you're using CD R/W
2. Burn the Android x86 ISO
3. Reboot your device, go to Boot Device Selection menu, select the CD / DVD
4. You will see Android x86 GRUB menu, select Install Android x86 to hard disk
5. Wait until it to load
6. Select partition to install Android x86
7. If you're unsure, don't format the partition
8. There will be a prompt, 'Install GRUB bla-bla-bla', if you use Windows, select yes. Another prompt will appear, select yes again.
If you're using Ubuntu, select no
9. Another prompt, 'Make system r/w', select yes (if you like modifying your Android x86)
10. If you're using Android x86 4.0.3 and older, you'll be prompted to install virtual SDCard, input 1800 MB / 1.8 GB
11. Reboot your device
I'll add tutorial how to add Android x86 to Ubuntu's GRUB menu. Stay tuned !
There's no screenshot, because the result may vary with your device.
Click to expand...
Click to collapse
Sorry if this has already been asked/answered but would this work on a Surface Pro (1st gen) or a Dell Venue 8 pro?
Windows
raghav kapur said:
Bro, any computer. Be it a desktop, netbook, ultrabook, MacBook, Linux computer, etc
Click to expand...
Click to collapse
And this doesn't delete windows right?
dodgebizkit said:
Sorry if this has already been asked/answered but would this work on a Surface Pro (1st gen) or a Dell Venue 8 pro?
Click to expand...
Click to collapse
Yes, it will work on both. Not sure about the touchscreen and the keyboard covers though
---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------
Rami1997 said:
And this doesn't delete windows right?
Click to expand...
Click to collapse
If you overwrite this Android installation over the Windows, then IT WILL DELETE WINDOWS.
But, if you create separate partitions for Windows and Android, then you can dual-boot.
I suggest that you run Android in a virtual machine rather than installing this way
Cool
Sent from my Nexus 5 using Tapatalk
Sounds great, can't wait to try it on my old laptops, thanks!
If you want Ubuntu Grub entry, see here : https://groups.google.com/forum/#!topic/android-x86/GrPdnpa6XBM
Use Li's kernel from here IF YOU ARE USING 4.4 on an UEFI system (<efivar> KP): https://groups.google.com/d/msg/android-x86/GrPdnpa6XBM/dA1ChqU1vu4J
All credits goes to there owners (not to me ).
GOOD LUCK
BTW, I have Vaio S (SVS 2012) and I can get WiFi working of I boot from legacy mode BIOS from an external HD w/ the original kernel, while it doesn't work of I boot it from UEFI w/ the custom kernel (since it can't boot w/out it) and doesn't work w/ either 4.3.X or 4.2.X. Can someone help me? (using Intel Centrino Advanced N 6235)
Thanks
Interesting
Anyone try to run this as a VM using either VMWare or VirtualBox?
sent from my hsvxo out in cbciioebd
Whoop!! Featured on portal!!
Sent from my LG-E430 using XDA Premium 4 mobile app
14. If you're using Android x86 4.0.3 and older, you'll be prompted to install virtual SDCard, input 1800 MB / 1.8 GB
Could we set more for more space to install apps?
simon_lefisch said:
Anyone try to run this as a VM using either VMWare or VirtualBox?
sent from my hsvxo out in cbciioebd
Click to expand...
Click to collapse
Yep, I did... But when I tried to boot it it shows only attachment and stock on Android logo
Could someone please answer my question please, also can you try the OS before installing it on the hdd, like test it and reboot and then install it
Awesome... wud try it n post screen shots if i can :laugh::good:
i tell you sth.. i was able to make 2gb data partition only... and trying to change data.img in other programs to make it bigger but never succeded.. maybe there is some workaround to make data partition bigger... or to use swap with usb stick or sth..
i had installed android x86 kitkat on usb 8gb drive and works perfectly some apps just had problems with mouse pointer.. (i think those designed for android 2.3) just had this problem with only 2gb data partition...
Bootmgr is missing
unetbootin creates the boot image but my windows laptop doesnt detect it
jarusss said:
Yep, I did... But when I tried to boot it it shows only attachment and stock on Android logo
Click to expand...
Click to collapse
Same thing happened to me with Virtualbox. However, I shutdown the VM, unmounted the iso, and rebooted. After that, it worked. I used the 4.4 version.
Introduction
You probably know already that starting from Android 5.x (Lollipop) compiled roms (aosp,cm,stock) are not compressed anymore the way they used to be on previous android versions. On previous versions all content inside /system folder that has to be extracted within our device was either uncompressed (simple /system folder inside our flashable zip) or compressed in a system.img file, which it is a ext4 compressed file; both of these, anyway, were readable and we could see all system files (app,framework, etc).
The problem comes in >=5.0 versions, this method is not used anymore. Why? Because roms started to be always larger, so it is necessary to compress them even more.
Note : Introduction was taken from here : https://forum.xda-developers.com/an.../how-to-conver-lollipop-dat-files-to-t2978952 by @xpirt so thanks to him
So in order to save myself and others who most port Custom & Stock Roms, i decided to use some part of my time to write this script for easy work done.
What this script does :
It basically Unpack and Repack system.new.dat alongside with file_context.bin convertion which is seen in android 7.0/7.1
ITS USAGE:
NOTE
First Clone the repo.
Make sure that Android_System_Extraction_and_Repack_Tool is located at Desktop
Run "Xtrakt" from it's location in terminal
Copy "file_contexts.bin" from your Rom to "file_context_zone" folder
Use "f" from menu to convert "file_contexts.bin" to text readable "file_contexts"
Copy : system.new.dat, system.transfer.list & file_contexts to "convert-dat" folder.
Use "i" from menu to unpack, which the output will be name as "rom_system" for modifications of apks & files.
Use "y" from menu to repack, which the complete new "system.new.dat", "system.patch.dat" & "system.transfer.list" will be located at "Finish-new.dat" folder
Done !
EXAMPLE:
Again , Make sure that Android_System_Extraction_and_Repack_Tool is located at Desktop
In your terminal, type the following to start the script:
Code:
git clone https://github.com/iykequame/Android_System_Extraction_and_Repack_Tool.git
mv android_system_extraction_and_repack_tool ~/Desktop/
cd ~/Desktop/android_system_extraction_and_repack_tool/
./Xtrakt
OR
Code:
Double-click the Xtrakt file and choose "Run in Terminal" if your OS supports it.
##ALERT!!!##
sudo is requested in the script.
How To Get It {Tool]
Clone from one of the below ;
From GITHUB :
Code:
git clone https://github.com/iykequame/Android_System_Extractrion_and_Repack_Tool.git
From BITBUCKET :
Code:
git clone https://[email protected]/zac6ix/android_system_extraction_and_repack_tool.git
Or
Download zip
AFH
GIT-RELEASE
Sources :
Android_System_Extraction_and_Repack_Tool
GITHUB
BITBUCKET
Threads :
sdat2img 1.0 - img2sdat 1.2
For file_context.bin conversion by: Pom Kritsada @ MTK THAI Developers.
Credit to :
@xpirt
@SuperR.
-all xda threads which helped
-Android Matrix Development - here
-Nana Yaa for her time.
hi, your tool sounds good but it seems it doesnt work.
i press f and nothing happen ..
Use "f" from menu to convert **"file_contexts.bin"** to text readable **"file_contexts"**
Blackball said:
hi, your tool sounds good but it seems it doesnt work.
i press f and nothing happen ..
Use "f" from menu to convert **"file_contexts.bin"** to text readable **"file_contexts"**
Click to expand...
Click to collapse
Sorry for the Late reply !
Directories linking has been fix .
You can go ahead and try again
Thanks for sharing!
Don't work
When i press i ..Don't work.say file missing.but i already put all file..Please help meView attachment 4249470
Doesn't do anything with file_context.bin, doesn't even check if file is there.
oreo supported???
I am getting this error on repacking:-
Code:
WARNING! WARNING!! WARNING!!!
Please Check & Trace Where Errors.
There Is NO rom_system found
file_contexts -->> Missing !
Android SDK -->> not detected !
Please help.
Black_J said:
I am getting this error on repacking:-
Code:
WARNING! WARNING!! WARNING!!!
Please Check & Trace Where Errors.
There Is NO rom_system found
file_contexts -->> Missing !
Android SDK -->> not detected !
Please help.
Click to expand...
Click to collapse
I see that this thread is not supported.
Anyways, I observed that the tool works for file_contexts.bin but not for other options.
So , I followed the other link in the thread for individual commands and was successful.
Works perfectly on Android Pie! Have to do some tweaks, PM me if anyone wants to make this work for Android Pie.