Related
Droid Explorer is the #1 Open Source Android device manager for Rooted devices.
Device Requirements
Rooted Android Device with busybox
Guide to installing busybox on the Droid
PC Requirements
Windows (looking for a developer to help create UI for mono)
.NET Framework 3.5 SP1
Some plugins require Java Runtime Environment and Java Web Start
Confirmed Devices
All Devices have been rooted and busybox installed
HTC Dream / G1 / ADP1
HTC Sapphire / Magic / MyTouch 3G / ADP2 / Ion
HTC Hero / G2 / CDMA Hero
Google Nexus One
Motorola DROID
Samsung Galaxy / i7500
Acer Liquid
HTC EVO
Features
Includes the required windows USB drivers - you will be prompted to install the drivers during installation if running vista/7
Auto setup of Android SDK tools and drivers during install
Use an existing Android SDK if you already have one set up
Multiple Device Support
No need to mount SD card to access files
Copy any file on the device to PC
Copy files to clipboard
Copy update to device and auto-apply
Drag & Drop copying from Explorer to Droid Explorer
Auto detection of connected/disconnected device
Open files on PC
Plugin Framework
Application Manager
Right Click APK to install/uninstall
Take screen shots of device (landscape & portrait)
Open right from "My Computer" (a lot like how WinMobile is with active sync)
SQLite Manager Plugin
Uses System Icons for files displayed in explorer
Familiar Explorer like UI, including an Explorer like location bar
Android Screencast plugin
Install/Uninstall APK files right from explorer
Standalone plugin runner
Window 7 JumpLists for plugins
DesktopSMS plugin - Send SMS messages from your desktop
Service can be controlled now from the options dialog (can create the service if you do not use the installer)
Backup plugin for the "Bare Bones" Roms
Run shell scripts on the device by double clicking them
{
"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"
}
I'd like any thoughts you may have for other features to add to Droid Explorer. Report bugs or request features here or on the project issue tracker.
Web Installer (x86)
Requires internet connection to download android sdk tools
x86 Serivce will not work on x64 OS
Web Installer (x64)
Requires internet connection to download android sdk tools
Use this install if running a 64 bit OS
Standalone Installer (x86)
Does not require internet connection. Larger download.
Standalone Installer (x64)
Does not require internet connection. Larger download.
Use this install if running a 64 bit OS
Older Releases
Source Code Available at CodePlex
Change log 0.8.7.0
Can now use existing SDK instead of the "trimmed" version
Settings stored in the registry now check both Local Machine and Current User
Lots of other little fixes
Change log 0.8.6.0
fixed missing file in the standalone installer
added check for minimum .net framework version in to bootstrapper (v3.5sp1)
increased the service start/stop timeout in the bootstrapper from 30 seconds to 60 seconds
removed initial strings from download panel labels of bootstrapper
htc desire / bravo icon added for attached devices - thanks to beadza for identifying the device
added ability to only install the SDK Tools by running install with /sdk switch
sdk install mode checks if DE is installed, if not, it switches to full install mode
bart plugin now also checks the sd-ext mount point for the license.
added the sd-ext app paths as valid application paths
added sd-ext app paths to the application backup plugin
removed anda.pk plugin as the site is dead.
screencast plugin changed to pull the jnlp file directly from the trunk of the project. If there
is an error, it falls back to a "local" file
fixed issues with spaces in folder names
motorola backflip icon added for attached devices - thanks to zibiza for identifying the device
new screenshot app that handles all resolutions. Uses new methods to get the framebuffer data
adjusted the RGB565 class to better handle other devices for screenshots
started to implement communicating with adb over TCP like ddms does.
acer liquid icon added for attached devices - thanks to fyodor0218 for identifying the device
started working on the ability to use existing sdk (not yet an option, but soon)
Change log 0.8.5.1
Fixed typo in the final step when uninstalling
Fixed x64 issues for windows 7 x64 - still broke on Vista x64 & XP x64 (sorry people, i'm still working on it!)
Default button for bootstrapper changed to the "next" button instead of cancel
added incredible icon for attached devices
added nexus one icon for attached devices
added galaxy S (gt-i9000) icon for attached devices
added acer liquid icon for attached devices
updated the samsung moment icon
added a new "open" version of the moment - rename in the assets directory to "moment.ico" to use.
Change log 0.8.5.0
android screen cast updated to load the lastest build from the trunk
changed publish to use skydrive share instead of the api from the msbuild tasks
added platform tools 2.2
added sdk tools r6
updated repository.xml
added help video link when the device cannot be found
attempting to fix the registry read issues with XP SP3 x64 and Vista x64
removed the "fade out" of the expandos from the treeview to remove the flicker
fixed the issue with opening offscreen
fixed workitem:10275, changed "Close" to "Finish" in the description of the final step of installer
fixed the "hanging" of trying to delete a file. added the '-f' switch to never prompt.
Change log 0.8.4.3
Fixed the install / start up issues caused by the platform tools having a typo in the file name
Change log 0.8.4.0
Fixed issue with cyanogen 4.2.14.x
fixed issue with bart manager plugin license (sorry for the delay)
added 2.1 r1 platform tools
added usb drivers r3 - adds support for nexus one
fixed issue with install plugin crashing if application is already installed.
Change log 0.8.3.0
Fixed bug with device not identifying recovery mode
Display QR code to purchase bart manager if license not found.
mount partitions in recovery mode to find bart manager license
bart manager now attaches to process to output the info
another attempt to set as root when starting for non-adp devices
There is a known bug with droid explorer detecting a device already "connected" going in to recovery mode.
Flash recovery now works in any mode, not just recovery
bart manager license now available for purchase on market.
Change log 0.8.2.3
Drivers removed for windows XP until XP issue with the drivers can be resolved.
added device icon for the nexus one / passion
Code setup to allow some plugins to be purchased.
The .net 3.5 check has been removed for the time being until a better solution can be implemented.
build published via [url:MSBuild Deployment Tasks|http://mdt.codeplex.com]
some bugs fixed here and there
What happened to 0.8.2.2? - Windows locked the directory when I was building that version so it failed and I couldn't delete it to rebuild so I skipped it.
Change log 0.8.2.1
Fixed install issues with 0.8.2.0 - should install for x86 and x64
Change log 0.8.2.0
created a WiX custom action library for checking for the android usb drivers
install logging is now merged in to one file and off by default. use /l[og] to turn on logging
tools will always be downloaded/extracted during install. This lets the tool update to newer tools if needed
fixed delete file when the file name has a space in the file name.
sdk tools upgraded to r4
fixed bug in uninstall if the service did not exist on the machine
should now successfully check for the android usb drivers and install them if revision 2 is not installed.
remember location of "open file dialog"
added code that should check for .net 3.5 sp1 before "crashing" for not having it installed.
added check that the user is installing the correct version (x86 or x64) for their system
Change log 0.8.1.0
added a splash screen so the user is aware that the app is running right away
.NET Framework 3.5 SP1 check added to installer.
apk shell extension now uses the path stored in the registry for the tools.
added logging to the install process
kill all adb processes before attempting to cleanup the sdk path during install.
apk seems to not be working, still debuging the issues. it will be back.
defined a platform constant to the project scripts, x86: PLATFORMX86, x64: PLATFORMX64, ia64: PLATFORMIA64
fixed bug with reading / writing to the registry in x64. now looks in HKLM\Software\WOW6432Node\
fatal errors are now caught and user given option to restart app, close app, or report bug
there is still a bug with installing the driver, the check isnt working so the driver still needs to be installed manually.
Change log 0.8.0.1
fixed installer issue where it crashed if you do not have a proxy set up
x64 installer has issues. - Tempory Fix - Will fixed in next release
Change log 0.8.0.0
added the r2 windows usb drivers, which add support for droid and other devices
added new checks for the drivers. Checks for dream/magic/sholes - these are the devices that google defines in the .inf file.
images moved to external resources library
changed the installer images to be more "custom"
removed need for droid explorer to require "run as administrator" - Yay!
the bootstrapper now handles starting the service. This makes sure the sdk is setup before it starts.
bootstrapper is self contained, the msi is an embedded resource and all referenced assemblies are ILMerged
repository file is hosed on the droid explorer google code site, it is based on the same one that google uses for the android sdk setup
the tools are also hosted on the google code site, this is so the download size is smaller, since all unused bits are removed.
A fully standalone version of install is also available. No need for internet access to install.
boot strapper support uninstall - setup.exe /uninstall
removed reference to the "common.shared" assembly.
added a properites dialog for folders/files
properties dialog shows security settings as well.
fixed icons in context menu for new folder/file
Change log 0.7.12.0
fixed the error that anda.pk plugin logs when it starts because it did not implement "Runnable"
shell extension for apk files so the apk icon displays in explorer - based on http://code.google.com/p/apkshellext/
seems there is a bug in some APKs that dont display their icon, nor do they display the default icon.
registers and unregisters the shell extension on install/uninstall
driver check now works better in the installer
removed some tools menu items that have been replaced by plugins
Installer now gives "options" on what features to install
changed default apk icon to be the "android package" icon
fixed bug with launching ddms and hierarchy viewer
fixed bug launching the google applications backup plugin
added methods to the core command runner to make a mount point read/write and readonly
added icon for the motorola droid
added icon for the samsung moment
added icon for the htc droid eris
Change log 0.7.11.0
USB Drivers installed - This is still in "alpha", should only install them if you need them. please report any issues. It doesn't actually install the drivers, it places them in the driver store, when the device is attached, and the new hardware wizard displays, selecting "automatically install (recommended)" should find the drivers automatically. This installs the 1.6 drivers.
fixed logcat not starting
created a new logcat console that colorizes the log entries
save the logcat output (minus the log level indicator (W/I/D/E/))
support for android screencast 0.2
Change log 0.7.10.1
Fixed crash on device going from connected to disconnected state
Change log 0.7.10.0
Sign Package plugin (signs zip file with test keys)
modified IPlugin to now have methods for creating the toolstrip button and menu items
DroidExplorer.Core.Plugin.PluginHeler added. Contain default static methods for creating the toolstrip button and menu
and.apk now a plugin instead part of "core"
started a contacts manager
started a tool to export facebook contacts from official application to android contacts
added "recovery" as device state.
now "attaches" while in recovery mode.
screenshot now works in recovery mode.
screenshot rotates the current image before refreshing when switching between landscape & portrait
flash recovery image now a plugin - only active when in recovery mode
some bug fixes that I don't remember the exact details on
Change log 0.7.9.0
new shell console enhanced
getprop wrapped to get device properties
explorer icon now attempts to load an icon of the device
- Known devices:
- Bahamas (Tattoo)
- GT-I7500 (Galaxy)
- Hero (G2/Hero)
- Sprint Hero (do not yet know what it identifies itself as in ro.product.device may just show normal hero)
- cliq (need to verify what ro.product.device returns)
- Saphire (MyTouch3G/ION/Magic)
- Dream (G1/ADP1)
- Pulse (need to verify what ro.product.device returns)
- Zii Egg (need to verify what ro.product.device returns)
Device properties viewable in options->environment->known devices->[device-serial]->properties (only when device is connected)
fixed bug with screenshot image being landscape but window portrait.
fixed bug with large icons not always showing the right icon
Change log 0.7.8.0
Desktop SMS now launched from officially signed jar file
Plugin tool strip disabled / enabled when device disconnected / connected
SymLinks and Directories can now also be renamed
F2 starts file/link/directory rename
Executable files now run if double clicked (open from context menu)
Shell Console (could still be buggy so the normal shell window is still available)
double clicking sh scripts run them
plugins that are registered as a file type handler will show up in the right click menu for the file
Change log 0.7.7.0
Renaming of files (folders and links coming)
Google Application Backup (GAB) plugin added
GAB supports HTC's ADB1 update packages (containing system.img), pulling from the device or from normal update.zip
Screen shot plugin supports portrait & landscape modes (use button or right click image)
Screen shot threaded so it doesn't "hang"
Change log 0.7.6.0
Fixed screen shot plugin from opening off screen if droid explorer is maximized or positioned on the right of the screen.
Check for the USB Driver version and download the tool set based on that. If you select the sdk yourself, you must select the correct tools yourself.
USB Driver Version info available in Options->Environment->Android SDK
Speed up of navigating to different directory. Reduced the number of LS calls that are made to build the tree and listview
Change log 0.7.5.0
Fixed plugins executing when loading within Runner
Fixed bug with additional plugin getting the same changed values as other plugin.
Change the SDK path from the Options dialog (requires restart of application)
Fixed bug with apk's not displaying.
Fixed Batch Installer not "showing"
provided a way to manually install, start and stop the droid explorer service - for non-installer users
added ability to save debug output to a file
moved debug window filter buttons to the right
debug window will display below DE if there is room, otherwise, it will display at the top of the screen
added plugin to launch DesktopSMS. Requires the DesktopSMS Server APK be installed on the device - Currently usinging a signed jar by me, hopefully the developer will sign his version.
can now copy symlinks files to clipboard
Change log 0.7.4.0
Changed the SdkInstallDialog to use a WebRequest instead of the WebClient. Hopefully this will help some peoples issues...
Window settings are now saved and reloaded.
Remembers the folder view state (large icon, details, etc)
added --color=never to directory listing command. this should fix the issue people with Heros are having
moved the options dialog tree config to its own file, as it really isnt configured by the user.
added batch installer plugin (alpha) that can install/uninstall multiple apk's at one time.
added logging info for droid explorer. (saved in %USERAPPDATA%\DroidExplorer\logs)
it should also handle "unhandled" errors better
wired up Tools menu items
Added property to indicate if a plugin can be ran by the Runner
Jumplist items added for runnable plugins
Change log 0.7.3.0
app.manifest added to projects. requestedExecutionLevel = requireAdministrator. This means in Vista/Win7 it will prompt w/ UAC. I can not get around this at this time.
this is because in order for the service to use the same settings as the application, i need to save them in the install directory.
The sdk tools, if downloaded, is no longer stored in the user directory, it is stored in the install directory, see above for the reason.
Known devices moved back to HKLM for the same reasons above.
New Options form added.
Device manager now part of options dialog
plugins can now reside in any directory as long as it is added to the plugins settings
plugins can now be enabled or disabled from the options dialog
Service is now working because of the requireAdministrator change.
DroidExplorer.Runner added - a tool that can execute a plugin; usage: DroidExplorer.Runner.exe /type=Full.Plugin.Class.Name,Plugin.Assembly.Nam/any /additional /args
if the type argument is not specified, then it will display a plugin selection dialog.
Installer plugin. This is launched by the runner when an APK file is opened in Explorer.
Registry settings to register .apk files to open with DroidExplorer.Runner /Installer (create with MSI installer)
.apk files can be installed by double clicking them or by right clicking and selecting "Install"
.apk files can be uninstalled by right clicking and selecting "Uninstall"
the initial device selection dialog is only required if more then 1 device is connected.
If you have set up to use the SDK tools by downloading the tools and put them in your user application data directory, when launched, it will prompt you to re-setup the tools. They are not stored in the user directory because the Service can not access that directory.
Just realized the bug with the device name not showing in the titlebar/addressbar. This is already fixed and will be in the next release.
Future Features you will see in Droid Explorer
Complete integration with the Managed Android Debug Bridge. R
Root will not be needed, at least for copy file operations. Things like flashing recovery, and deleting from /system will still require root.
Busybox dependency will be dropped.
SQLite Database Manager to replace the feature lacking plugin that exists now.
Faster navigation when changing directories
What features do you want to see?
A few weeks ago when the Android-on-HD2-hype started i made this small app. This piece of software was inspired by GenYDualboot (author: YOZGATG) so some credit should go to him...
To make it clear: I wrote this software by myself (basic4ppc) from the scratch so no code or other intellectual property has been stealed.
ANDROID BOOTCAMP v1.1
System Requirements:
* WVGA (VGA/QVGA not supported!)
* WinMob 6.5.X (not tested on WinMob 6.5)
* min. NETCF 2.0
* a SD-card containing working Android-build
Basic Functionality:
* WinMob based Android loader
* possible to "boot" ANDROID or to stay in Windows
* possible to "autoboot" with countdown (10sec)
* possible to choose if CLRCAD.EXE is loaded prior to HARET.EXE or not
* Autodetection of HARET.EXE and CLRCAD.exe on the SD-Card (checks if files are present in root or "\Android")
* possible to modify the path to your Android-build by changing the path in the registry
* possible to boot at systemstart (the app puts itself to "launch52" in the registry)
* possible to save your settings
* fully functional on non-WWE-Roms (checks the registry for the name of your sd-card)
* full multi-language-support (by editing the "language.ini"; at this time only german an english are buildin)
* full landscape/rotation support
* fully skinable (by modifing the PNGs in the app-folder, i'm going to release a GTX based skin or some other skins if it's wanted by the community)
* new: change font color (black/white)
* new: switchable progressbar (showed during countdown)
* new: ClearAndroid! removes Android-related junk-/tempfiles and cache!
* new: TotalClean! totally ereases your Android environment (for a clean upgrade to a new build) - USE WITH CARE!
Disclaimer:
This piece of software is free and can freely be downloaded here. You are allowed to modify, cook in or distribute my work as long as you give me some credit.
YOU ARE NOT ALLOWED TO CHARGE ANY KIND OF FEE NEITHER FOR THIS SOFTWARE ALONE NOR BY INCLUDING IT OR ANY MODIFICATIONS OF IT INTO A ROM/ANDROID-BUILD OR ANY OTHER "SERVICE"!
(see threat "STOP THE STEALING" in the Android subforum for more details...)
I'm not responsable for any kind of damage or data loss on your device. The software is provided as it is and you are going to use it on your own risk.
Credits:
* the developers here and at htc-linux.org for HARET.EXE/CLRCAD.EXE and for their amazing work!
* YOZGATG for GenYDualboot
Roadmap / future functions to come in Android Bootcamp v1.2 (if wanted by the community):
* GUI-overhaul to a nicer / modern look
* add possibility to directly downloading latest zImage from the git or from cotulla's build to your Android-installation-folder
* add support to change background directly within the app
* add support for skin-changing directly within the app
* add support for checking for newer program versions
* add support to select androit installation (if more than one installation present on SD)
* add possibility to "clean" SD-Card when rebooting to WinMobile (deletion of REC-files and the "Lost+Found" folder) integrated into v1.1!
* add option "TOTALCLEAN" (ereasing all android related files and folders incl. thumbnails/cache/etc) integrated into v1.1!
More inf
o to come....
Feel free to make your suggestions!
FAQ / Userguide
Q: How do I install Android Bootcamp?
A: Just download the CAB attached to the firs post and install it to your device. It's recommended to put it into your phone-storage not to the sd-card.
Q: How do I boot into Android?
A: Click on the Android-button (the picture).
Q: The Android-button is greyed out and the app says "no Android!"
A: Make sure that there is a sd-card plugged into your device containing Android in the root or in the "\Android" subfolder. Also HARET.EXE/zHARET.EXE is required in the same folder to successfully boot Android. On program-start the app checks the registry ("HKLM\Android Bootcamp\") for a valid path to HARET.EXE/zHARET.EXE. If HARET not found or existing the app checks the rootfolder of your sd-card and after that the "\Android" subfolder. If you want to modify the path to your own needs go to the registry and alter the value "Haret" in the key "HKLM\Software\Android Bootcamp".
Q: How do I make sure that CLRCAD.EXE is started prior to HARET.EXE
A: Click on the checkbox next to activate CLRCAD or select the option in the settings-menu. On program-start the app checks the registry ("HKLM\Android Bootcamp\") for a valid path to CLRCAD.EXE. If CLRCAD not found or existing the app checks the rootfolder of your sd-card and after that the "\Android" subfolder and after that it takes the CLRCAD.EXE in the Android-Bootcamp program folder. If you want to modify the path to your own needs go to the registry and alter the value "CLRCAD" in the key "HKLM\Software\Android Bootcamp".
Q: How do I stop the countdown?
A: Just tap on the countdown-message or tap on the checkbox next to "activate AutoBoot".
Q: How do i activate/deactivate AutoBoot?
A: Check or uncheck the checkbox next to "activate AutoBoot" or select the corresponding option in the settings-menu.
Q: What does "execute at Boottime" mean?
A: The App makes 2 entries to the registry ("HKLM\init\Launch52" and "HKLM\init\Depend52"). These entries make sure that Android-Bootcamp is started during the WinMob boot procedure with the saved settings as soon a possible. Please note that the boot process does not stop and continues loading system processes after Bootcamp is started. I suggest also to check the "AutoBoot" option so that Android/WinMob is loaded automatically after 10sec. To disable this option uncheck the option (registy changes made immediately - no "save settings" is needed)
Q: How do I save my settings? Why are my settings not saved?
A: Your settings are not saved automatically - choose "Save settings" in the settings-menu prior to booting Android or closing the app.
Q: How do I activate the landscape support?
A: Landscape and screen-rotation is fully supported by the app itself but it's possible that you have to add the app to the rotation-whitelist. If you don't know how to do this - google for TouchTools or BSB-Tweak. With the help of these apps you can enable rotation service easily to any program.
Q: The program gives me the error-message "No Registry-values found, create them now?"!
A: Possibly you deleted one/some reg-values needed by the app. Just click to "YES" and all settings/RegKeys will be created with default values.
Q: I'm not naturally speaking english/german. How do I add my own language?
A: This can be done very easily by modifing the file "language.ini" in the Android Bootcamp - program folder. Please make sure that the first line is the name of the language and that the ini's structure isn't altered (NO SPACES between value, "=" and translation!!)
Q: How do I add my own skin?
A: Modify the PNG-files in the Android Bootcamp prgram folder to your own needs after making a backup of the orginal files (recommended). Feel free to post your files compressed to a ZIP-file here!
Q: I still don't get "execute at Boottime" to work!!
A: First be aware of the fact that the "execute at Boottime"-option puts the Android Bootcamp app into the row of the startup processes (look at the regkey "HKLM\init\" for all processes loaded automatically at systemstart!). Also note that by loading Bootcamp the startup-process doesn't stop. That means the system starts Bootcamp and continues loading the remaining systemprocesses afterwards and probably puts Android into the background without the ability to bring it to foreground again (it's not listed in some task-managers). So it's recommended that not only " "execute at Boottime" but also "AutoBoot" is selected. These options enable Bootcamp to load at startup and to boot either into WinMob or Android (depends on your settings saved) and EXIT after the countdown gone to zero.
Here is a detailed guide:
1. make sure that a sd-card containing a functional android build is plugged into your hd2 (Android AND HARET present!)
2. start Android Bootcamp
3. select "Autoboot"
4. select Android as Autoboot-OS (tap the radiobutton below the androidbutton or select the corresponding option in the settingsmenu)
5. select "execute at boottime"
6. save your settings
When the system starts Android Bootcamp is loaded. If an Android-SD-Card is present Android will boot after 10 sec regardless if Bootcamp is in fore- or background. If no Android-SD-Card is plugged in, WinMob is selected automatically, System will boot after 10 sec and Bootcamp quits.
This should work for you.
If you still encounter problems check your registry after you checked the "execute at boottime" option. 2 new values should be in the RegKey "HKLM\init": "Launch52" and "Depend52" - If they are not present something went wrong. You can also try to change the valueNAMES from "Launch52" to "Launch62" and "Depend52" to "Depend62" respectively.
Q: Is it possible if you can code it so it can find CLRCAD and Haret in the "cm6-htcleo" folder for the CyanogenMod release / in some other custom folder?
A: Yes, it's already possible - open your registry with a regeditor and go to the key "HKLM\Software\Android Bootcamp". Check and edit the VALUE "Haret" and put the FULL PATH to your HARET.EXE / zHARET.EXE in there. After this modification Bootcamp should be able to find your Android-Installation. The feature of selecting a custom folder is added with the next release of Bootcamp.
NOTE: Be aware that "CleanAndroid!" and "TotalClean!" doesn't work with custom Android folders - these two options look for an Android-environment in the root of your storage card or in the "Storage Card\Android" folder respectively. So keep an eye on those two (probably dangerous) features, so that not the wrong files get lost...
SKINS
Q: How do I install a skin?
A: Download the zipped skin-file here and extract all files to the Android Bootcamp program folder overwriting the orginal files.
Q: How do I add my own skin?
A: Modify the JPG/PNG-files in the Android Bootcamp program folder to your own needs after making a backup of the orginal files (recommended). Make sure that your files have the same dimensions and keep their file format! Feel free to post your files compressed to a ZIP-file - I will add them here!
NOTES:
* GTX-based skin is beta/for testing only and does not look very good - better version will be uploaded with the next program version (see text color issue above)
* Text color can't be changed a this time - going to add an option in the next version to switch between black/white fixed in v1.1
* there is some minor picture-misallignment regarding the android button. This is already fixed in the code an will be included in the upcomming update fixed in v1.1
nice work! good to see several alternatives out there for dual booting
Don't need it...
But really great job!
Pretty GUI !
beautiful my fav booting app so far,
thanks
hi, thanks for the nice app, but could you please include autoclean or auto delete of the "android" folder on sdcard as it tampers with rootfs when re booting.
thanks
bR
Best Dual boot for Android/Winmo out there at the moment.
essojay said:
hi, thanks for the nice app, but could you please include autoclean or auto delete of the "android" folder on sdcard as it tampers with rootfs when re booting.
thanks
bR
Click to expand...
Click to collapse
Please explain this issue to me because i don't have this kind of problem in my setting. Do you want to have an option to "automatically clean" the root/android folder of your sd-card after rebooting (to WinMob)? What kind files should be cleaned? I easyly could add an option to clean the "*.REC" files and the "LOST+Found" folder if this is wanted.
each time you reboot into windows and want to getback into Android, you have this complaint about rootfs not found , and the fix is to delete the "android" folder on the sdcard, this folder is auto generated. this happen each time you reboot and want to get back to android. There is a thread about this somewhere...
http://forum.xda-developers.com/showthread.php?t=736306&highlight=rootfs
bR
essojay said:
each time you reboot into windows and want to getback into Android, you have this complaint about rootfs not found , and the fix is to delete the "android" folder on the sdcard, this folder is auto generated. this happen each time you reboot and want to get back to android. There is a thread about this somewhere...
http://forum.xda-developers.com/showthread.php?t=736306&highlight=rootfs
bR
Click to expand...
Click to collapse
Hmm, I looked at the given threat and this issue seems strange to me. I never had this kind of problem and this could be BECAUSE my Android-installation resides in the folder "SD-CARD\ANDROID". Darkstone and Dani recommend to put their builds (Froyo) into the Android subfolder and not directly to the root-folder of the sd-card.
Adding a option to clear or to delete the android folder seems not acceptible to me because - like I said - many people including myself have their Android installation in this specific folder and consecutively would destroy their Android environment.
But i'm considering to add a TOTALCLEAN-feature so the user can easily prepare the sd-card for a new android build by ereasing his android installation and all corresponding files and folders (thumbnails, cache, etc.) without the need of formatting the sd-card.
Epic
Very nice GUI! I will be giving this a try. Seems like a good time to experiment with some different flavors of Android...Weekend Project! w00t!
Yes Ironheart...am going to try the sdcard/android way and let you know.. just read somewhere about everything in the android folder.. thanks.. will let you know
bR
really nice man, i will jump ship to your loader
Sorry, i checked "Boot at bootime" option but the program is not run automatically on startup
Zell Dinch said:
Sorry, i checked "Boot at bootime" option but the program is not run automatically on startup
Click to expand...
Click to collapse
First be aware of the fact that the "execute at Boottime"-option puts the Android Bootcamp app into the row of the startup processes (look at the regkey "HKLM\init\" for all processes loaded automatically at systemstart!). Also note that by loading Bootcamp the startup-process doesn't stop. That means the system starts Bootcamp and continues loading the remaining systemprocesses afterwards and probably puts Android into the background without the ability to bring it to foreground again (it's not listed in some task-managers). So it's recommended that not only " "execute at Boottime" but also "AutoBoot" is selected. These options enable Bootcamp to load at startup and to boot either into WinMob or Android (depends on your settings saved) and EXIT after the countdown gone to zero.
Here is a detailed guide:
1. make sure that a sd-card containing a functional android build is plugged into your hd2 (Android AND HARET present!)
2. start Android Bootcamp
3. select "Autoboot"
4. select Android as Autoboot-OS (tap the radiobutton below the androidbutton or select the corresponding option in the settingsmenu)
5. select "execute at boottime"
6. save your settings
When the system starts Android Bootcamp is loaded. If an Android-SD-Card is present Android will boot after 10 sec regardless whether Bootcamp is in foreground or or not. If no Android-SD-Card is plugged in, WinMob is selected automatically, System will boot after 10 sec and Bootcamp quits.
This should work for you.
If you still encounter problems check your registry after you checked the "execute at boottime" option. 2 new values should be in the RegKey "HKLM\init": "Launch52" and "Depend52" - If they are not present something went wrong. You can also try to change the valueNAMES from "Launch52" to "Launch62" and "Depend52" to "Depend62" respectively.
my contribution to the theming
ironheart said:
Future functions to come in Android Bootcamp v1.1 (if wanted by the community):
* add possibility to directly downloading latest zImage from the git or from cotulla's build to your Android-installation-folder
* add support to change background directly within the app
* add support for skin-changing directly within the app
* add support for checking for newer program versions
* add possibility to "clean" SD-Card when rebooting to WinMobile (deletion of REC-files and the "Lost+Found" folder)
* add option "TOTALCLEAN" (easy preparation of your SD-Card without formatting by ereasing all android related files and folders incl. thumbnails/cache/etc)
* add support to select androit installation (if more than one installation present on SD)
Click to expand...
Click to collapse
+1 Want have
[/QUOTE]
voiceofid said:
my contribution to the theming
Click to expand...
Click to collapse
Nicely done! going to put your skin to post#3...
Thank you!
EDIT:
I testet your theme and i had to lightly modify it to keep text-readability (blur filter, less light, htc-logo removed)... i hope you are ok with my modifications. Still good job done (added to skins)
HD2_Noob said:
+1 Want have
Click to expand...
Click to collapse
Some of the new features are already working in my beta-build und are going to be released to public soon (ETA for final 1.1-release maybe 1-2 days)...
Stay updated!
[TOOL] Mass Apk Installer /system install [OSX Linux Windows] v2.2 Update 2/4/2017
Apk mass installer is back and better than ever. Many things have been going on and development of the app has left behind but the project has started again.
First of all new support for other OS have been implemented including Linux and Osx , Windows has already been supported since version 0.
Now mass apk installer can also make backup's of android phones backing up apks from phone. Backup's can also exported to a zip file and even encrypted with AES 256 bit encryption. Installing apk's to phone from zip and encrypted files is also supported
Also there is support to store apk info and metadata in sqlite database this feature is beta
Last but not least apk mass installer has a new home in github the link is below
https://github.com/binary-signal/mass-apk-installer
Hi
This application automatically installs apk's to android phone or to /system partition with a few clicks
1.Extract the contents of the archive
2.Copy the apk's you want to install into the apk directory
3.Enable Unknown Sources in phone settings and USB debugging
4.Double click run.bat or run.sh
5.Wait....
6.Enjoy
Simple as that
Last Update 2/4/2017
Table of contents:
0x2: Software Description
0x3: How to use this software
0x4: Change Log
0x2: Software Description
This software automates the installation and backing up of apk's, Android applications to your Android phone. It
uses the adb interface provided by Google to install / back up applications via command line prompt to the
phone
0x3: How to use this software
Important Notice: In order the program work successfully you MUST have installed the usb drivers
for your phone model !
0x4: Change Log
v 2.2 Major update of code and new features
Added support for Mac OS X
Improved support for Linux
Added new feature back up phone apk's
Added zip archive support for backup's and install's features
Added AES 256 encryption to backup's
Removed feature apk installation to /sys partition
Added support for Android Nougat
v 1.5 Code maintenance
Fixed a bug when trying to create a directory already existed returned errors
Added some new future's overide the adb check state and refactored the dummy install process for apk's
In the new version the new future's will be added and manipulated via command line arguments
For now the new futures are experimental and not available to stable release only on beta release
v 1.4 Fixed an error about naming of apk'files containing space
character. Now the non valid apk names are fixed auto
matically and space character is replaced with '_' character
before installation.
v 1.3 Fixed some errors in messages while program was running
Now the apk folder ins't necessary to have only apk files, The program automatically separates
the apk's in the folder and installs them.It will skip non apks files
Installation size info is available now
Removed some unnecessary dll files from root folder
Wait for adb server a few seconds before try to install anything just to make sure the phone is connected
Wait for user input (Enter) to exit program
Update documentation
v 1.2 Now it is able to install apk's to /system partition. This future is extremely dangerous use it at your own rick
Update messages during runtime
v 1.1 Update Documentation, minor bug fixes
Please leave comments for this app Thank U !
USE THIS SOFTWARE WITH YOUR OWN RISK !!!!!!
Sounds good.
Is ther option to install system/app partition too?
That would be nice!
Cheers!
Taavi
Sent from my MT15i using Tapatalk
Until now no , but in the future i might code something like that !
KarmaToBurn said:
Until now no , but in the future i might code something like that !
Click to expand...
Click to collapse
Just finished the new version fix some bugs and now you can install your apk's to
/system partition ! Cheers !
KarmaToBurn said:
Just finished the new version fix some bugs and now you can install your apk's to
/system partition ! Cheers !
Click to expand...
Click to collapse
Nice!! Thanx
Sent from my MT15i using Tapatalk
this is awesome, i definitely need this ..thanks man
Thanks. Where download link??
KarmaToBurn said:
Hi
This application automatically installs apk's to android phone or to /system partition with a few clicks
1.Extract the contents of the archive
2.Copy the apk's you want to install into the apk directory
3.Enable Unknown Sources in phone settings and USB debugging
4.Double click run.bat or run_sys.apk if you want to install to /system partition
5.Wait....
6.Enjoy
Simple as that
The app can run in Windows Xp SP2, Windows Vista and Windows 7 both x86 x86_64 arch
More Detailed Info
Read me file for apk install
Table of contents:
0x1: Contact Information
0x2: Software Description
0x3: How to use this software
0x4: Archive Contents
0x5: Change Log
0x1: Contact Information
You can sent requests, bugs and anything you want at: [email protected]
0x2: Software Description
This software automates the installation of apk's, Android applications to your Android phone. It
uses the adb interface provided by Google to install application via command line prompt to the
phone
0x3: How to use this software
After downloading the rar file apkinstall.rar extract the contents of the archive in your desired
directory, for example C:\Users\User\Desktop\apkinstall. Then then open the newly creates directory.
You will notice there are a couple of file and some folders.Put tou apk's into tha apk folder and
then double click the run.bat. A console will appear and install automatically every apk you put in
the apk folder. After install the console will exit and you are done. Unplug your phone and enjoy
your new apps.
Important Notice: In order the program work succesfully you MUST have installed the usb drivers
for your phone model ! For sony erricson just install pc companion. This sofware was tested in
Windows Vista x86/x86_x64 & Windows 7 x86/x86_x64, propably Windows Xp SP2 and above is supported.
0x4: Archive Contents
apkinstall.rar -+
|- ADB -+
| |-adb.exe
| |-adblinux
| |-adbmac
| |-AdbWinApi.dll
| |-AdbWinUsbApi.dll
|-apk -+
|-AdbInterface.dll
|-apk_mass_install.exe
|-DriverInstaller.dll
|-run.bat
|-run_sys.bat
Notes: '+' sign is for directories
0x5: Change Log
v 1.2 Now it is able to install apk's to /system partition. This future is extremly dangerous use it at your own rick
Update messages during runtime
v 1.1 Update Documentation, Minnor bug fixes
Please leave comments for this app Thank U !
You can download the app from here
code.google.com/p/mass-apk-installer/
USE THIS SOFTWARE WITH YOUR OWN RISK !!!!!!
Click to expand...
Click to collapse
ph.miki said:
Thanks. Where download link??
Click to expand...
Click to collapse
Look agen
taaviu said:
Look agen
Click to expand...
Click to collapse
blind, sorry
Awesome
Is there an option to install the apks to the external SDcard instead of to the internal SDcard?
Thanks.
No offense to the OP for his work...but couldn't something like this be done with a single line batch script? (granted it would only install and not anything extra)
for /f %%a IN ('dir /b Apk\*.apk') do adb install Apk\%%a
OMG you really DO understand our needs!
Aweeesomeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee!!!
This is damn funny.. an 'application' (Android) based on linux with a fancy wrapper/GUI and all these folks are making these really cool toys that are for... A WINDOWS MACHINE.
My head hurts
Awsome.
My apps are the reason why I hate flashing new roms. It's just a pain.
But I will definitely be more inclined to trying new things now thanks to this thanks a lot *beginning process*
KarmaToBurn said:
Hi
This application automatically installs apk's to android phone or to /system partition with a few clicks
1.Extract the contents of the archive
2.Copy the apk's you want to install into the apk directory
3.Enable Unknown Sources in phone settings and USB debugging
4.Double click run.bat or run_sys.apk if you want to install to /system partition
5.Wait....
6.Enjoy
Simple as that
The app can run in Windows Xp SP2, Windows Vista and Windows 7 both x86 x86_64 arch
More Detailed Info
Read me file for apk install
Table of contents:
0x1: Contact Information
0x2: Software Description
0x3: How to use this software
0x4: Archive Contents
0x5: Change Log
0x1: Contact Information
You can sent requests, bugs and anything you want at: [email protected]
0x2: Software Description
This software automates the installation of apk's, Android applications to your Android phone. It
uses the adb interface provided by Google to install application via command line prompt to the
phone
0x3: How to use this software
After downloading the rar file apkinstall.rar extract the contents of the archive in your desired
directory, for example C:\Users\User\Desktop\apkinstall. Then then open the newly creates directory.
You will notice there are a couple of file and some folders.Put tou apk's into tha apk folder and
then double click the run.bat. A console will appear and install automatically every apk you put in
the apk folder. After install the console will exit and you are done. Unplug your phone and enjoy
your new apps.
Important Notice: In order the program work succesfully you MUST have installed the usb drivers
for your phone model ! For sony erricson just install pc companion. This sofware was tested in
Windows Vista x86/x86_x64 & Windows 7 x86/x86_x64, propably Windows Xp SP2 and above is supported.
0x4: Archive Contents
apkinstall.rar -+
|- ADB -+
| |-adb.exe
| |-adblinux
| |-adbmac
| |-AdbWinApi.dll
| |-AdbWinUsbApi.dll
|-apk -+
|-AdbInterface.dll
|-apk_mass_install.exe
|-DriverInstaller.dll
|-run.bat
|-run_sys.bat
Notes: '+' sign is for directories
0x5: Change Log
v 1.2 Now it is able to install apk's to /system partition. This future is extremly dangerous use it at your own rick
Update messages during runtime
v 1.1 Update Documentation, Minnor bug fixes
Please leave comments for this app Thank U !
You can download the app from here
code.google.com/p/mass-apk-installer/
USE THIS SOFTWARE WITH YOUR OWN RISK !!!!!!
Click to expand...
Click to collapse
download link?
Omnichron said:
download link?
Click to expand...
Click to collapse
Look my previous post
Sent from my MT15i using Tapatalk
Excuse my ignorance but does this require adb to be installed?
popoyaya said:
Excuse my ignorance but does this require adb to be installed?
Click to expand...
Click to collapse
NO.
Sent from my MT15i using Tapatalk
You could just use flashtool too. (except for installing to system partition)
Guide:http://imgur.com/a/MBe5a
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?
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.