Droid Explorer - 0.8.8.2 [04/26/2011] - Pizza Party - G1 Apps and Games

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
Samsung Galaxy S Line
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
Older Releases
Source Code Available at CodePlex

Change log 0.8.8.2
New Device selection dialog
all assemblies are now signed again
fixed the "runner" so apk's can now be installed from the machine (along with the other plugins)
when upgrading, and using an existing SDK, the value will now be pulled from the registry, if it exists.
fixed bug in uninstall that would remove the sdk, even if you used an existing sdk
removed anda.pk plugin since the site is dead.
added a link in the bootstrapper (installer) to download the sdk.
refactored some strings to the external resources files in the bootstrapper (installer)
changed the reboot commands to use the adb commands, not the shell commands
fixed rm command to now use busybox as it was passing args that are not supported on the "stock" rm command.
added the sph-p100 device icon
Change log 0.8.8.1
fixed issue that some people experience error durring install about an droidexplorer shell extension.
added sph-m910, htc desire hd (ace), nexus s, and the c8600 icon support
use existing android SDK is now the default and recommended.
added htc vision (Tmobile G2) and the s5830
Change log 0.8.8.0
fixed the issue with latest android-sdk using "platform-tools" directory for adb
fixed screen shot capture to now support 32bpp raw image as well as 16bpp
added other device icons, like the Galaxy S variants
fixed other bugs
Change log 0.8.7.2
fixed issue with the service
minor bug fixes
updated the bread crumb bar
fixed the dragging the window so it doesn't fly off screen
Change log 0.8.7.1
Some refactoring of the settings to keep the Core libraries non-windows dependant.
APK information is now cached for faster loading
Attempting a fix for vista 64 bit and xp 64 bit
fixed the .net 3.5 check
added icon for the EVO (supersonic) - thanks to sanjsrik for identifying the device
added some debugging info to the shell console plugin to see if I can get it working for droid/milestone
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.

dude nice stuff !!! ... cant wait to look through the source to learn some more C# tricks

Errors pulling up list of APK
Code:
[CommandRunner] adb.exe -s HT840GZ23223 pull "/system/sd/app/com.shazam.android.apk" "C:\Documents and Settings\Administrator\Local Settings\Temp\DroidExplorer\com.shazam.android.apk"
[CommandRunner] C:\WINDOWS\platforms\android-1.5\tools\aapt.exe dump badging "C:\Documents and Settings\Administrator\Local Settings\Temp\DroidExplorer\com.shazam.android.apk"
[MainForm] The system cannot find the path specified - System.ComponentModel.Win32Exception: The system cannot find the path specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at DroidExplorer.Core.CommandRunner.RunAaptCommand(AaptCommand command, String args) in g:\Projects\Csharp\DroidExplorer\DroidExplorer.Core\CommandRunner.cs:line 1057
at DroidExplorer.Core.CommandRunner.AaptCommandRun(AaptCommand command, String args) in g:\Projects\Csharp\DroidExplorer\DroidExplorer.Core\CommandRunner.cs:line 944
at DroidExplorer.Core.CommandRunner.GetLocalApkInformation(String apkFile) in g:\Projects\Csharp\DroidExplorer\DroidExplorer.Core\CommandRunner.cs:line 634
at DroidExplorer.Core.CommandRunner.GetApkInformation(String apkFile) in g:\Projects\Csharp\DroidExplorer\DroidExplorer.Core\CommandRunner.cs:line 626
at DroidExplorer.UI.MainForm.BuildListViewItems(List`1 fsiList)
I basically get the above errors in debug for all the apk's, when I try to display them when clicking on the folder hierarchy of /system/app, system/app-private, /system/sd/app/, system/sd/app-private.
currently running CM 4.1.2.1

andonnguyen said:
Code:
[CommandRunner] adb.exe -s HT840GZ23223 pull "/system/sd/app/com.shazam.android.apk" "C:\Documents and Settings\Administrator\Local Settings\Temp\DroidExplorer\com.shazam.android.apk"
[CommandRunner] C:\WINDOWS\platforms\android-1.5\tools\aapt.exe dump badging "C:\Documents and Settings\Administrator\Local Settings\Temp\DroidExplorer\com.shazam.android.apk"
[MainForm] The system cannot find the path specified - System.ComponentModel.Win32Exception: The system cannot find the path specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at DroidExplorer.Core.CommandRunner.RunAaptCommand(AaptCommand command, String args) in g:\Projects\Csharp\DroidExplorer\DroidExplorer.Core\CommandRunner.cs:line 1057
at DroidExplorer.Core.CommandRunner.AaptCommandRun(AaptCommand command, String args) in g:\Projects\Csharp\DroidExplorer\DroidExplorer.Core\CommandRunner.cs:line 944
at DroidExplorer.Core.CommandRunner.GetLocalApkInformation(String apkFile) in g:\Projects\Csharp\DroidExplorer\DroidExplorer.Core\CommandRunner.cs:line 634
at DroidExplorer.Core.CommandRunner.GetApkInformation(String apkFile) in g:\Projects\Csharp\DroidExplorer\DroidExplorer.Core\CommandRunner.cs:line 626
at DroidExplorer.UI.MainForm.BuildListViewItems(List`1 fsiList)
I basically get the above errors in debug for all the apk's, when I try to display them when clicking on the folder hierarchy of /system/app, system/app-private, /system/sd/app/, system/sd/app-private.
currently running CM 4.1.2.1
Click to expand...
Click to collapse
that's because it uses more then just the ADB, it makes use of a lot of the tools within the SDK. It looks like you have ADB setup in your c:\windows\ directory. Currently you have to manually set up the tools path in the environment variables, but in the next release (hopefully tonight) I will have a utility built in that will download, extract and set up the path environment variable with the SDK tools.

camalot said:
that's because it uses more then just the ADB, it makes use of a lot of the tools within the SDK. It looks like you have ADB setup in your c:\windows\ directory. Currently you have to manually set up the tools path in the environment variables, but in the next release (hopefully tonight) I will have a utility built in that will download, extract and set up the path environment variable with the SDK tools.
Click to expand...
Click to collapse
Weird, I've had the environment variables set up just fine for the past 8 months for adb and the sdk. In SYSTEM PROPERTIES > ADVANCED > ENVIRONMENT VARIABLES
Edit: wth they got erased somehow haha. Looks like ill set them up again. Probably good to include them in your next release as a lot of people aren't willing to set up the SDK.

Code:
Descrizione:
Stopped working
Firma problema:
Nome evento problema: CLR20r3
Firma problema 01: droidexplorer.exe
Firma problema 02: 0.5.0.0
Firma problema 03: 4a9d2e95
Firma problema 04: System
Firma problema 05: 2.0.0.0
Firma problema 06: 49d44bf7
Firma problema 07: 3a97
Firma problema 08: 395
Firma problema 09: System.ComponentModel.Win32
Versione SO: 6.1.7100.2.0.0.256.1
ID impostazioni locali: 1040
Win 7 64bit RC1

IronFly said:
Win 7 64bit RC1
Click to expand...
Click to collapse
Did you install the x64 version? The x86 service will not work on an x64 machine. you have to install the x64 version.

just what i was looking for!
thanks for posting

camalot said:
Did you install the x64 version? The x86 service will not work on an x64 machine. you have to install the x64 version.
Click to expand...
Click to collapse
i downloaded this:
DroidExplorer.0.6.0.0.x64.msi
http://de.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=32271#DownloadId=81513

IronFly said:
i downloaded this:
DroidExplorer.0.6.0.0.x64.msi
http://de.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=32271#DownloadId=81513
Click to expand...
Click to collapse
I will dig in to this when I have access to my laptop that is running Windows 7 64bit.

Thanks Camalot!

In windows seven 32bit this same

0.7.0.0 posted, should now start in window 7 x86 & 64bit.

Windows 7 64 bit here
I manually added the SDK and everything and had .6 working
(at least the basics where)
However .7 gets to the screen saying its going to download whats needed, then stops responding
Did a uninstall and re-installed however, same thing

LinkinX said:
Windows 7 64 bit here
I manually added the SDK and everything and had .6 working
(at least the basics where)
However .7 gets to the screen saying its going to download whats needed, then stops responding
Did a uninstall and re-installed however, same thing
Click to expand...
Click to collapse
I'm having this same problem. I can use adb to access my phone but your app simply freezes up.

Jumping back to .6 for now since its working for me
Main thing I love it just viewing me SD without forceing the cell 2 reboot on unmont
that and I connect with Droid Explorer so android screen cast connects easily lol

LinkinX said:
Windows 7 64 bit here
I manually added the SDK and everything and had .6 working
(at least the basics where)
However .7 gets to the screen saying its going to download whats needed, then stops responding
Did a uninstall and re-installed however, same thing
Click to expand...
Click to collapse
same problem.

hmmm. honest, i tested the setup like 90 times. I'll look in to it when i get off work this afternoon. Sorry if it broke your original setup.
There is a manual work around if you want the latest version and bypass the setup.
Create DroidExplorer\sdk\ Directory in User application data directory
- c:\documents and settings\<username>\applicationdata\ on pre-vista
- c:\users\<username>\appdata\roaming\ vista & 7
download http://droidexplorer.googlecode.com/files/android-sdk-tools-1.5r3.zip and extract to that directory
OR copy the platforms and tools directories from the root of your SDK directory to the above path.
The DroidExplorer\SDK directory should now have 2 directories in side, platforms and tools
Restart Droid Explorer
I will change the installer later today to contain this zip file, I just tried to keep the initial installer as small as possible.

it works with the work around.
HTC G1 Dream JF v1.51

Related

[Q] ABD Drivers + Windows 7 issues (plus a couple more questions)

Hello XDA Community.
I'm attempting to install the new RC of CyanogenMod-6 for the Hero CDMA. I'm currently running the stock 2.1 version of Android. I've been following the guides that were referred to in the thread (I tried posting the urls but new users can't do so to prevent spam).
I've successfully rooted my phone and now I'm trying to do a Nandroid backup. I'm running Windows 7 32-bit and have hit a road block with ADB not recognizing my device. I followed the guide put together by Nephron to install the Android SDK. I've spent several hours going through threads and doing google searches looking for the solution. I have debugging turned on and I don't mount my SD drive when I plug the USB cord in. I've used USBDeview as some have suggested to delete current HTC drivers and then reinstall - no luck.
Here is a screen shot of what happens when I plug in my Hero:
See attached - "failedinstall.jpg"
Then I'll go to device manager to manually install the driver (it never allows me to manually select upon connection for some reason):
See attached "devicemgr.png"
And then this is the message I get when I point it to the "right" folder with the drivers:
See attached - "unabletoinstall.png"
So, on the Android SDK site I noticed this message:
"The USB driver for Windows provides support for the following Android-powered devices:
T-Mobile G1* / ADP1
T-Mobile myTouch 3G* / Google Ion
Verizon Droid*
Nexus One
* Or similar hardware on other carriers
Any additional devices will require Windows drivers provided by the hardware manufacturer.
^So is all of this HTC's fault? I've downloaded a couple of different .zip folders from different threads claiming that these drivers would work. But none of them have yet to do the trick for me.
I'm new at this so I have a few other questions as well:
Most guides I've read about how to do a Nandroid backup always recommend flashing a ROM b/f doing a backup. But I want to backup my current stock rom and settings before I flash. Wouldn't I want to create a recovery image before installing any other ROMs? Perhaps I'm misunderstanding some requirements?
Referring again to the thread on the CyanogenMod RC, can someone help me understand step #3? How do I know if it is necessary to update my radio? What implications does this have? I tried looking for info about this on the wiki and I couldn't find anything comprehensive enough to answer my question.
I'd appreciate any guidance!
Before you modify anything you will want to boot into recovery, assuming you flashed one, by holding down Home and turning the phone phone back on(power button). But since you don't have adb working then you probably haven't. You can still do this using terminal on your phone.
Download terminal emulator from market and then download a revoery image (AmonRa 1.6.2 or Darch's 1.7xx) and then mount your sdcard to the computer and transfer the recovery to the root of the sdcard. Open up terminal emulator and type in
Code:
su
cd /sdcard
flash_image recovery recovery-RA-heroc-v1.6.2.img(type the exact file name of the recovery you are using)
reboot recovery
If you had factory 2.1 on your phone then you have the latest radio. The radio can be flashed just like any ROM, but make sure that the radio is not for GSM phones as this will destroy your phone.
Instructions from Android Developers and ADB, Fastboot, and Nandroid for Noob
Download the latest Android SDK.
Unzip to C:\AndroidSDK
Right-click on (My) Computer, and select Properties
Go to Advanced settings
XP: Click the Advanced tab
Vista/7: Click Advanced system settings on the left
Click the Environment Variables button
double-click on Path (under System Variables)
Add the full path to the tools/ directory:
C:\AndroidSDK\tools\
(make sure a semicolon ( separates this new path from all the others)
Latest windows sdk version appears to need: "C:\AndroidSDK\android-sdk-windows\tools", install location may change with further updates..
Run C:\AndroidSDK\SDK Setup.exe
If you get an error about not having Java SDK installed but you do, add the path to 'bin' within your Java installation location to the Path environmental variable as described above before the sdk entry you just made. (eg add "C:\Program Files\Java\jdk1.6.0_20\bin;") This is likely to only be necessary where the 64 bit Java SDK is installed (obviously) on a 64 bit machine.
If it gives you an error about http go to settings and click on "Force http//....."
Unselect all options except for the USB driver
If you can't get the setup to work, download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows.
After it installs the drivers, goto the Start menu and type cmd into the search bar (Vista or higher) or click Run then type in cmd (XP) to open the command prompt.
Type the following into the command prompt window:
adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set. If you do NOT see a serial number, then we need to reinstall the drivers.
Download USBDeview
While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the HTC/Android drivers and uninstall them all. (Windows Vista requires program to be run as an administrator, otherwise files won't uninstall.)
Once all have been uninstalled, unplug the phone from the USB cable and plug it back in.
The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
To check, go to Devices in your Start menu then click on the “Android Phone”. Click on the Hardware tab, and check the list of drivers for ADB Interface under Type.
Done! Now you can use ADB to alter your phone from your computer.
If all else fails try installing HTC Sync software-- http://member.america.htc.com/download/Driver/HTC Hero (Sprint)/HTC_Sync_2.0.40.exe and then removing the drivers for it and then trying to install the android sdk drivers
Or you can dual boot with Linux and all you will need to do is download and unzip android sdk and edit 2 files and everything will work.
WOW>>>>>no that is way to confusing. the best thing to do is install vmware workstation. Then do a virtual WINDOWS XP MODE. from there you will be able to install the drivers and such in order to get the phone to be seen.
the version of htc sync i used for all my computers including win 7 was 2.0.33
if you want it then just pm me and I will get it to you
they don't offer it for a download anymore
this version corrected all my driver issues

[Q] DDMS cannot find ADB

I am trying to fix the WiFi on my Captivate. This thread here tells how to do it. Unfortunately when I run DDMS I get the error "Failed to get the adb version: Cannot run program "adb": CreateProcess error=2, The system cannot find the file specified." I have tried installing the SDK on both a Windows 7 64-bit and XP 32-bit machine. I get the same error on both machines. I have tried both the generic Galaxy S drivers and the Captivate drivers. Any suggestions? Here are the instructions I've followed in case you don't want to read the other thread:
1. Install the SDK -> Android SDK | Android Developers
(make sure the <SDK>/tools path is added to the windows path variable. My Computer -> Properties -> Advanced -> Environment Variables -> System variable -> add the SDK path at the end of Path variable )
2. On your phone, please enable (tick mark) "USB debugging" under "Settings" -> "Applications" -> "Development"
3. Connect your phone using USB to PC/Laptop. Close phone manager application if it comes up on the PC.
4. Run "ddms.bat" from <SDK>/tools directory. The DDMS application will come up and it should readily connect to your phone. (in the main screen, under Name, you should find the phone ID and SW ver. no.)
5. Go to menu Device -> File Explorer. New window will come up.
6. Here go to data -> wifi directory. You will see a file bcm_supp.conf.
7. Though it is not possible to read this file, you should be able to delete it. (at least I could delete it). You can delete the file by selecting it and then pressing red "-" on top left of the window.
Thanks!
Post in q and a.
sent from my craaazy fast cappy running di11igaf v2.5 at 1280mhz!!!
silverslotcar said:
Post in q and a.
sent from my craaazy fast cappy running di11igaf v2.5 at 1280mhz!!!
Click to expand...
Click to collapse
Yes, Q&A would be the proper location for this thread.
Sent from my GT-I9000 using XDA App
Ok, sorry, although I just figured out the problem. The Path should have the platform-tools directory instead of the tools directory because that's where adb is located. I corrected that and it loaded right up. Unfortunately, when I click on the + sign for the Data folder it doesn't show me anything Guess I'm going to have to do a factory reset after all.
automagrt said:
I am trying to fix the WiFi on my Captivate. This thread here tells how to do it. Unfortunately when I run DDMS I get the error "Failed to get the adb version: Cannot run program "adb": CreateProcess error=2, The system cannot find the file specified." I have tried installing the SDK on both a Windows 7 64-bit and XP 32-bit machine. I get the same error on both machines. I have tried both the generic Galaxy S drivers and the Captivate drivers. Any suggestions? Here are the instructions I've followed in case you don't want to read the other thread:
1. Install the SDK -> Android SDK | Android Developers
(make sure the <SDK>/tools path is added to the windows path variable. My Computer -> Properties -> Advanced -> Environment Variables -> System variable -> add the SDK path at the end of Path variable )
2. On your phone, please enable (tick mark) "USB debugging" under "Settings" -> "Applications" -> "Development"
3. Connect your phone using USB to PC/Laptop. Close phone manager application if it comes up on the PC.
4. Run "ddms.bat" from <SDK>/tools directory. The DDMS application will come up and it should readily connect to your phone. (in the main screen, under Name, you should find the phone ID and SW ver. no.)
5. Go to menu Device -> File Explorer. New window will come up.
6. Here go to data -> wifi directory. You will see a file bcm_supp.conf.
7. Though it is not possible to read this file, you should be able to delete it. (at least I could delete it). You can delete the file by selecting it and then pressing red "-" on top left of the window.
Thanks!
Click to expand...
Click to collapse
Hi,
I am going crazy with this crap, I am not impressed how google put this **** together.
I can see you managed to fix the issue of ddms not finding adb but I didnt. Can you please explain in more details? I searched everywhere over the internet but everybody just says "add the path". Fine. Then what....?
I added a new path in the environmental system variables called "SDK" and points to:"C:\program files\Android\android-sdk-windows\platform tools\. Still no joy. What am I doing wrong?
thanks
Did you reboot after adding the path?
And I didn't realize that Google had changed the SDK path to "platform-tools" with their latest release. Just plain dumb imo as folks have been so used to it being in just the "tools" location.

[SDK] Android SDK addon for Motorola Atrix4G

Anyone that is in need of it .. attached here is the Motorola Atrix4G addon for the Android SDK .. also the instructions for installation and execution.
http://www.mediafire.com/?73hkz09wr0l1kqe
Installing and Using Motorola SDK Add-ons
A Motorola SDK add-on, when added to the Android™ SDK, allows you to run and debug your applications on an emulated Motorola handset. Note that while the device image that the add-on presents does not necessarily reflect the look of the actual device, from a functional standpoint it should be a fairly faithful emulation of the actual handset.
Installing the add-on
To install the Motorola SDK add-on, unzip it, and copy the resulting directory to the directory named add-ons within the Android SDK that you are using (if you are using MOTODEV Studio for Android and are not sure where it placed the Android SDK, check the SDK Location field in the Android preferences dialog).
** NOTE: If MOTODEV Studio for Android or Eclipse™ were running when you copied the SDK add-on, you will need to restart it for the add-on to be recognized by your development environment.
Using the add-on
In order to run or debug your applications on an emulated Motorola handset, you must first create an AVD that has its AVD Target set to reference the SDK add-on. You can then deploy your applications to it. When creating your projects, you can either target the emulated Motorola device specifically (which you would do if your application runs only on that device), or you can select a more general, compatible target such as Android 1.5. The following sections detail the steps involved in each of these tasks.
Creating an AVD
To create an AVD named "Motorola" using the command line, do the following (you may need to be within the Android SDK's "tools" directory):
android list targets
The details for each possible target are listed, starting with a unique ID number that identifies that target. Make note of the ID number for the Motorola add-on you want to target.
android create avd -n Motorola -t target-ID
For target-ID supply the ID number for the target you obtained from the previous step.
To create it from within MOTODEV Studio for Android:
Select Android AVD Manager from the Window menu. The Android Virtual Devices Manager dialog appears.
Enter Motorola (or whatever name you want to give the new AVD) in the Name field.
From the Target list, select the target named for the Motorola device you are targeting.
From the Skin list, select the skin named for your target device.
If you want the emulated device to have an SD card, in the SDCard field either specify the path and filename to a file containing an existing SD card image, or specify a size (such as 64M) to create a new, empty SD card image. Leave this field blank if the device isn't to have an SD card.
Click Create AVD.
Click Finish to close the dialog.
When creating Run or Debug configurations, you can now select this new AVD when choosing a target device.
**NOTE: If your newly-created AVD does not appear in the Device Management view, click Refresh, which is located in the top right corner of that view.
Starting the AVD
If you start a Run or Debug configuration that specifies a Motorola SDK add-on AVD as the target device, the AVD will be automatically launched for you. If you want to start the AVD without deploying an application to it, you can do so either from the command line or from within MOTODEV Studio for Android. From the command line, the following command will start the AVD named "Motorola":
emulator -avd Motorola
To start it from within MOTODEV Studio for Android, select the AVD from within the Device Management view and click Start.
Targeting the Motorola device
If your application is designed specifically for a Motorola device, select the corresponding Motorola SDK add-on as the project target when creating the project.
To change an existing project so that it targets the SDK add-on from an Eclipse-based IDE such as MOTODEV Studio for Android:
Right-click the project in the Package Explorer and select Properties.
From the list of properties select Android.
The project build target is shown in the right side of the dialog; select the one named for your target device.
If you are not using an Eclipse-based IDE you can change your project's target with the android update project command; see Google's developer documentation on developing in other IDEs.
Awesome exactly what I was looking for!! Thanks for the Info looking foward to working with this more. XD
Djazin said:
Awesome exactly what I was looking for!! Thanks for the Info looking foward to working with this more. XD
Click to expand...
Click to collapse
You're welcome
What features does the addon add? I'm assuming nothing I can play with right now because the main app I'm working on now is in Necessitas/Qt, but when I get back to playing with Eclipse what could this do?
Hmm, that's weird. Maybe I'm missing something, but why set up a mediafire link for it when it's freely available from the Motorola development website?
Plus if you download it from there, you can get install directions, USB drivers, motodev studio, and even some sample apps...

[TUTORIAL]How to take a Logcat & use DDMS

{
"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"
}
HOW TO USE ADB , DDMS & TAKING AN LOGCAT ..etc​
WHAT IS ADB???​
EXPLANATION ​
Whenever you create an android app or when you develop an Rom , it is important that you must deliver GOOD QUALITY APP or ROM , that are rid of Bugs ..Eventually you might come across a situation when your APP or ROM isn't working or it is bricking the device or some things are not working .These situation can be tackled only with a proper debugging tools ..So ADB ( android debug bridge) is a powerful Debugging tool and a tool which allows us to step through each line of code and examine the value of each variable.It offers us some of the powerful tools ..Debugging is not a big deal for the people who come from a JAVA programming background .Dalvik VM in android supports java debug wire protocol to attach to the device over ADB
Click to expand...
Click to collapse
ADB​ADB or ANDROID DEBUG BRIDGE is a command-line utility that is often used to communicate over the debug channel with a connected phone or virtual device (emulator). ADB can control your device over USB from a computer, copy files back and forth, install and uninstall apps, run shell commands, and more...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
SETTING UP ADB :- ​
1) Install Java JDK :-​Before installing the Android SDK, you’ll have to install Oracle’s Java development kit. You can download it from here...(click me !!)
Even if you already have the Java runtime (JRE) installed, you’ll need to install the JDK as well.
After installing Java JDK , you can now download the Android SDK from Google .
NOTE:- If you see a any type of Java-related error during installation, then download and install the x86 version of the JDK, not the x64 one ..
Click to expand...
Click to collapse
2) Installing android SDK:-​Download Android SDK from here...(click me !!!)
After clicking on "DOWNLOAD FOR OTHER PLATFORMS" , you will get an extended menu ..
After downloading the .exe file , then Double click on the .exe file and install it in C:\ Drive or on whichever drive you wanna install .
Click to expand...
Click to collapse
Click to expand...
Click to collapse
3) Android SDK Setup
Click to expand...
Click to collapse
Once the Android SDK is downloaded and installed, launch the SDK Manager application from your Start menu.
Enable the Android SDK tools and SDK Platform-tools checkbox and click the Install button. This downloads and installs the platform-tools package, which contains ADB and other utilities.
After installing these packages , Go to the place where you installed ANDROID SDK . IN MY CASE , IT IS :-
Code:
C:\Program files(x86)l\Android\android-sdk\platform-tools
If you used a different install location, you’ll find ADB in the platform-tools directory,inside your ANDROID-SDK directory .
Browse to platform tools and hold Shift and right-click inside it, and select Open command window here...
Click to expand...
Click to collapse
​
NOW YOU WILL SEE THIS :-
Note :- To use ADB with your Android device
1) you must enable USB debugging on it. You’ll find this option under Developer Options on your device’s Settings screen
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
2)You must install your device drivers :- Individual OEM USB drivers for windows are available for each manufacturer and are listed in the official document ..
After you have downloaded you device drivers, then we have to install on our pc. for that :-
a) connect the device to the computer
b) right click on MY COMPUTER and click manage
c) go to devices > other devices and right click on device and select update driver software.
d) you should see an option to " BROWSE MY COMPUTER FOR DRIVER SOFTWARE" , which you nedd to click on and point to the location of your device driver installation file..​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
​
To test whether ADB is working properly, connect your Android device to your computer using a USB cable and run the following command:
Code:
adb devices
Now it will show the devices connected
Now you have sucessfully installed ADB and now we are good to go further..​
WHAT IS A LOGCAT :-​
Logcat is the command to view the internal logs of the Android system. Viewing logs is often the best way to diagnose a problem, and is required for many issues. This way you'll find out what apps are doing in the background without you noticing.
TAKING AN LOGCAT :-
Now type this in the terminal
Code:
adb logcat -v long > logcat.txt
or
Code:
Code:
adb logcat > logcat.txt
you shall have a log file called name of logcat.txt inside your ADB folder.
SOME OF THE USEFULL ADB COMMANDS :-
Code:
adb install C:\package.apk
– Installs the package located at C:\package.apk on your computer on your device.
EG -adb install G:\xda.apk
Click to expand...
Click to collapse
Code:
adb uninstall package.name
– Uninstalls the package with package.name from your device.
EG :- you’d use the name com.quoordy.xdadevelopers to uninstall the Xda developers app.
Click to expand...
Click to collapse
Code:
adb push C:\file /sdcard/file
– Pushes a file from your computer to your device. the command here pushes the file located at C:\file on your computer to /sdcard/file on your device .
EG :-adb push G:\system\framework\framework-res.apk /system/framework
Click to expand...
Click to collapse
Code:
adb pull /sdcard/file C:\file
– Pulls a file from your device to your computer – works like adb push, but in reverse. EG :-adb pull /system/app G:\rom\system\app\
Click to expand...
Click to collapse
Code:
adb logcat
– View your Android device’s log. Can be useful for debugging apps.
Click to expand...
Click to collapse
Code:
adb shell
– Gives you an interactive Linux command-line shell on your device.
Click to expand...
Click to collapse
Code:
adb shell command
– Runs the specified shell command on your device.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
The Dalvik Debug Monitor Service (DDMS) as it is known is one of the application debugging tools that must be a part of every ANDROID app developers's toolkit..This is very very useful to the app developers.Its is a very powerful debugging tool environment and offers various unparalleled debugging features like heap information , logcat monitoring , file manager.It is available by default in ECLIPSE IDE environment or even in the ANDROID SDK.It works on top of ADB for device communication..
DDMS can be stated as a standalone application as part of ANDROID DEVICE MONITOR.The Android Device Monitor is a standalone which can be used in case you do not use the eclipse development environment , though the integration with Eclipse is something that other IDE'S could be envious of.​
HOW TO USE DDMS ??
1)AS EXPLAINED IN THE ABOVE POST , INSTALL ANDROID SDK....AFTER YOU HAVE INSTALLED PLATFORM-TOOLS & SDK TOOLS..NOW GO TO ANDROID FOLDER AND OPEN TOOLS
2)NOW RUN MONITOR.bat AS ADMINISTRATOR
3)NOW ANDROID DEBUG MONITOR WILL APPEAR ..
Now let's learn about its components and it's use's
DDMS VIEW COMPONENT'S :-​
DDMS offers a set of view components , each of which show relevant information related to the connected Emulator.
DEVICES :-
The device panel shows the details of each process that are running in the connected device.There are various operations that can be performed from this panel.
Each of the icons present in this panel performs the functions as follow's :
Debug Process Icon :- It show's the state of connection of the debugger.
Update Heap :-Clicking on this enables Heap information for the process so that we do not have to do memory deallocation manually.
Dump HPROF :- Generates a Heap Dump , useful for tracing memory leaks in your app.
Cause GC :-Invokes the Garbage collector to collect heap data.
Update thread :-Show's the information about the running thread in the thread tad for selected process
Start Method Profiling :- Tracks the metric's related a method. It collects information like the amount of time taken to execute a method,number of calls.
Stop Process :-Stops the currently selected process.
Screen Capture :- Takes a screenshot of whatever is displayed on the screen.
Reset ADB :- Ast he name suggets,it resets ADB.
THREAD'S :-​The thread tab on the right of devices view shows informatiom related to the thread for each process selected in the devices view.The information shown can described as follows.
ID :- A unique ID assigned to each thread dby Dalvik V,, which are only odd numbers that start from 3 .
Tid :-The linux thread associated with each thread , ehich matches the process ID for each main thread in a process.
Status :- Status of the thread in VM , out of daemons are marked with an asterix.other values can be among running?sleeping/init/starting.
HEAP​ :-
the heap view show a information and statistics about memory heap .To view heap usage,follow these below steps
From the devices view,select the process for heap usage which has to be examined.
click on update heap
From heap Tab , select Cause GC to enable collecting heap data
Everytime you need to update your heap statistics.This will show you the amount of memory allocated to each
ALLOCATION TRACKER​The allocation Tracker show a real time information about allocation happening in the application over a certain period of time.To enable allocation Tracking.
[*]select the process to be tracked from device panel
[*]click on start tracking from allocation tracker tab.
[*]perform any actions on the devices or emulator that you want to be tracked.
[*]click on Get Allocations objects, since tracking was enabled .
NETWORK STATISTICS​ ;-
The network tab allows you to track and optimize the amount of network data your app is using.It even allows you to tag network sockets so that you can differentiate between types of data .It will indicate the speed and amount of data received /transmitted ..
EMULATOR CONTROL :-​One problem with testing Android devices using an emulator or developer device is the fact that it is unable to examine the performance of the app in the reak world conditions . like call or SMS is received/sent or when a particular location is reached.To be specific the emulator Tab allows you to to emulate the following real world conditions :
Telephony Status :- the following options are available to set the status of phones network.
Voice :- unregistered,home,roaming,searching,denied.
Data :- unregistered,home,roaming,searching,denied.
Speed :- Full,GSM,HSCSD,GPRS,EDGE,UMTS,HSDPA.
Latency :- GPRS,UMTS
Telephony Actions :- Telephony actions allow you to spoof the network.
Location Settings ;- Emulator control allows you to sppof the location
FILE EXPLORER :-​As the name says it lets you view the directory and file structure if the device and lso easily copy files to and from the emulator so as to enable easy data transfer in a manner similiar to ADB or ADB pull command.
SYSTEM INFORMATION :-​As the name says , it give's us the particular information about the GPU load , CPU load....
DDMS HAS ALSO AN INBUILT LOGCAT VIEWER :-​
​
​
CREDITS ;-
Google for everything
paxChristos for an command line
iamareebjamal for helping me :silly:
if i forgot you , just PM me .. i will be very glad to add it ..
great ,useful guide. many thanks

Teclast X98 Air 3G Tablet: 9.7" 2048x1536 px - Z3736F - 3G - Android/Windows 8.1

Teclast X98 Air 3G Tablet: 9.7" 2048x1536 px - Z3736F - 3G - Android/Windows 8.1
Hi to everyone,
I would like to apologize because my english is not so good.
This thread could be usefull for to get informations and modding istructions about the tablet Teclast X98 Air 3G.
I'm waiting for delivery via dhl and i guess some of the user here could think that the air 3G is an interesting tablet considering dimensions, cpu, display and the dual OS support .
I would like to point out that given the architecture and hardware of this tablet since the Teclast has released firmware for Android (standard) and Windows 8.1 (still in beta), even though I opened the thread in the Android tablet could be open also a thread in the Windows 8 section.
It was necessary to open a new thread because following the thread on the x98 Air teclast someone has mistakenly flashed a firmware dell'X98 air thinking it would go well on the X98 air 3G.
These are the hardware specifications:
Brand Name: Teclast
Teclast Model: X98 Air 3G
Processor Model: Intel Bay Trail-T Z3736F
Processor Main Frequency: Quad Core, 64-bit, 2.16GHz
GPU: Intel HD Graphics GEN7
Memory Capacity: 2Gb DDR3L
Tablet Data Capacity: 32GB
Screen Size: 9.7"
Display resolution: 2048X1536
Screen Technology : IPS Retina 10 Point touch Capacitive Screen
Dimensions : 240mmx169mmx7.4mm
Camera (Front): 2MP
Second Camera (Back): 5MP
Net Weight: 498g
Network Communiction: Built-in 3G,Bluetooth,Wifi
Extend Port: 3G External,Earphone Jack,OTG,TF card,Mini HDMI
Supporting Language: English,Russian,Spanish,Swedish,Portuguese,Turkish,Italian,German,Chinese,French,Japanese,Polish,Ukrainian,Greek,Hebrew
Other Feature: GPS, G Sensor,Phone Call
Operating System: Android 4.4
Cell Capacity: 8500mAh
OFFICIAL LINK
http://www.teclast.com/zhuanti/X98Air3GWin8/
SOME REVIEWS
http://mikecanex.wordpress.com/2014/09/18/teclast-x98-air-3g-gets-a-review/
http://translate.google.com/transla...s.imp3.net/thread-11183835-1-1.html&sandbox=1
http://bbs.teclast.com/thread-253051-1-1.html (you must be registered)
VIDEOS
Dual boot: www.youtube.com/watch?v=29dtAF39R9c
Dual boot conversion (with some usefull files): https://www.youtube.com/watch?v=qxpU_hFup64
Win 8.1: http://www.youtube.com/watch?v=Q3e_KTfbSK0
Win 8.1 - Multitasking and desktop mode: http://www.youtube.com/watch?feature=player_embedded&v=YHNki9ZBRgQ
Win 8.1 Gaming - Team Fortress 2:http://www.youtube.com/watch?feature=player_embedded&v=V8SpGjc3H4Y
Win 8.1 Gaming - Counter Strike Global Offensive: http://www.youtube.com/watch?v=rvwIxm2mCZw
Win 8.1 Gaming - Asphalt 8 (1366 x 768): http://www.youtube.com/watch?feature=player_embedded&v=qrJAGQ9iEYE
USEFUL TOOLS
VRoot : http://www.mgyun.com/vroot
VRoot chinese version (recommended) : http://d-h.st/lWu (Thanks to SUMMERBREEZE)
SRSroot: http://j.gs/4cyJ
Create ISO with driver : http://www.wincert.net/forum/files/file/5-win-toolkit/
Create bootable USB pen drive : http://rufus.akeo.ie/?locale=it_IT
REPOSITORIES WITH MANY THINGS (thanks to Frontiers and Hendrickson)
http://d-h.st/users/Frontier?fld_id=40727&s=file_size&d=DESC
http://techtablets.com/teclast-x98-air-3g/downloads/
BENCHMARKS
http://www.futuremark.com/hardware/mobile/Teclast+X98+Air+3G/review
OPEN A TECLAST TABLET (thanks to supercowz)
https://www.youtube.com/watch?v=841pMJC_QOk
ENGLISH REVIEW (thanks to Hendrickson)
techtablets.com review
ITALIANS REVIEW AND TUTORIALS (thanks to topdigamma.it)
Topdigamma.it Review
POSSIBILITIES FOR RECHARGE (thanks to cvfancypants)
Included Chinese Charger (TP-U25)- 5.0V/2.5A + Included USB cable
Belkin Boost Up (F8J040kr)- 5.0V/2.4A + Included USB cable
Samsung Charger (EP-TA11KWK)- 5.3V/2.0A (attached USB cable)
ANDROID DEVELOPMENT​
Disclaimer : these proceedings or files are provided "as are" and i'm not responsible for any lost (hardware / software )
I would also like to point out that these procedures have been tested for the model C6J6
ROOT INSTRUCTIONS WITH VROOT (thanks to zackman)
http://androidxda.com/download-vroot
VIDEOTUTORIAL VROOT USE
https://www.youtube.com/watch?v=cRgHZSnLmus
Note: someone has done the root through Vroot (english version) only after using Kingroot http://www.kingroot.net/
VIDEOTUTORIAL SRSROOT USE
https://www.youtube.com/watch?v=cRgHZSnLmus
FIRMWARE ANDROID
Teclast: http://dl.vmall.com/c0jpmqz7r5 (passw:C6J6)
Intel: https://01.org/android-ia/downloads
ADB DRIVER
https://mega.co.nz/#!3JshGCLB!6ldn4tPJZlZtDvlR17pmxhqxkrDs4OxxyCJhIHyhZ-4
http://www.koushikdutta.com/post/universal-adb-driver
FRONTIERS X98 TOOLBOX (for easy rooting)
https://www.oboom.com/MCY35B1Z
Just extract it and run "1_Toolbox.bat".
The rest is self explanatory.
If you have some difficulties you can follow these istructions: 25gee's tutorial
TOOLBOX WITH SU - updated to 2.43 - now root works without any problem if someone needs it
https://mega.co.nz/#!Mp50gIoD!ErMC5F...f9Qff_FQY0apcw
ALL THE APKS COMES IN /system/app STOCK ROM (thanks to migui88)
https://mega.co.nz/#!wYBixJaR!U6hO52KW0Wg_hy8OC8OBXP7ATmdpXmMWZNq9mHP2hMQ
ANDROID ROMS ​
CHINESE LITE 4.4.4 ROM (without bloatware and with lollipop keyboards)
https://mega.co.nz/#!KI8T0bBb!Pv25K1Rh0MJvXSCYQEC8P8l1mbsZQRgG6q5-XezP_aI
SUPERCOWZ X98 Air 3G (C8J7)-Android4.4.4-V2.00-1CF3.rar 556.1 Mb
https://mega.co.nz/#!zVdgWJyS!Vh7zGqX6NcYgXrCf-5v_qmEReZXuicvGzw6h1u5OnGo
jcespi2005 LIte ROM
v2.0 - C6J6 (Based on 2.01 Stock)
https://mega.co.nz/#!oQFU1CbR!NgwcEag4D1fuiVyS5qklyGq2wvMuPfwAwvHmFYzS4r4
v1.0 - C8J7 (Based on 2.02 Stock)
https://mega.co.nz/#!QY9kUQCI!hsPc8259qi0TmJhRmnc42inPEhFmpw-75fYxqrons6k
Description:
Fully rooted (Just launch SuperSU and update binary)
Deodexed
Zipaligned
Chinese Apps deleted (system should boot EN locale)
Nova Launcher as default Launcher (and the only one)
Google Play Fixed (integrated on System partition)
Audio fix by Frontier
Viper4Android
TeclastAutoUpdate (Just in case)
ES File Explorer
Three XML, one stock, one for 1Gb System, 128Mb Cache and 5Gb Data (for Dual Boot) and the other one to flash SYSTEM partition
mirek190 rom v3.1
v3.0 - C6J6
https://mega.co.nz/#!41IQHCDZ!g09l4U...A-30nY3DybSl2g
https://drive.google.com/file/d/0B8B...ew?usp=sharing
v3.1 - C8J7
https://mega.co.nz/#!8s4j0DZS!G6d9Ft...PI6fojDtwprLnM
https://drive.google.com/file/d/0B8B...ew?usp=sharing
v3.1 - C9J7
https://mega.co.nz/#!Yo4i0KJD!dnSXlt...jSH13iHvoHyc0o
https://drive.google.com/file/d/0B8B...ew?usp=sharing
Description:
ability to flash only system ( data and partitions are not touched ) or full flash.
system partition 1 GB instead of 1.5 GB -default but you can change it.
cache 100 MB instead of 1000 MB - is completely enough I tested but you can change it.
data partition 27 GB instead of 25 GB - I added other partition tables for data like 1 , 2, 3, 4, 5 ,6 ,7 ,8 ,9 , 10 GB , only android ( 27 GB ) , only windows 27 GB as well ) or default.
fully rooted
removed all Chinese programs
busy box
init.t
zip alignment
deodexed
changed navigation buttons to Android L looks
resided navigation bar
removed vol buttons and screenshot button from navigation bar - screenshot you can make pressing vol - and power at the same time.
battery with percent
bold fonts on system bar - fonts looks better
lower min brightens
microphone gain fix
clock on the middle of the status bar
4 way power menu - ability boot to droidboot, CWM, Hotboot
some changes in Buildprop for performance.
some optimizations in Framework but still very simple.
added. Google services, Google play, YouTube
google keyboard
adblock ( need root )
resolution changer ( need root )
ViPER4Android FX - need root now sound is really good and noisy
Apex launcher
and other things he don't remember
WINDOWS 8.1 => ANDROID PROCEDURE (thanks to Frontier)​
Required materials:
- A Teclast X98 Air 3G (obviously), battery sufficiently charged (recommended to be fully charged the battery before starting the process). The tablet will be running Windows 8.1 or in FastBoot mode
- The Android DnX BIOS (or Android BIOS) from here
- Tin last available (this season) Android ROM for the X98 Air 3G: X98_Air3G_(C6J6)-Android4.4.2-V1.10.7z
-The tools of the platform upgrade Intel (Intel Manufacturing Tools). These are available in two versions, the newer and older . Start with the newest and if do not work on your computer, install the older version. Only one version must be installed on your computer.
Upgrade Preparation tool (Intel Manufacturing Tools)
- Unzip the computer you use to convert (not tablet), the Android ROM given above.
- Unzip one of the two available sets of tools Intel Manufacturing Tools. Inside the folder, you will find some executables that run in the following order and always with administrator privileges:
iSocUSB-Driver-Setup-xxxexe: At some point during the installation, you will know that you have to connect the X98 with USB cable to the computer to install the NAND drivers. H connection is necessary otherwise you can install to see and shape the NAND memory of tablet.
IntelAndroidDrvSetupx.xxexe: We run this installer as an administrator with the tablet plugged in USB. This will install the ADB driver Intel, which appears in the Device Manager (Device Manager) for Windows. (See the picture Figure_1)
ManufacturingFlashTool_Setup_x.xxexe: This tool is used in the final planning "name" (branding) of the tablet and install the fastboot kernel. Install with administrator rights on the proposed application folder (hold down the name of the file for the next step).
- Upon completion of the installation of the Intel Manufacturing Tool, copy the file "CUSTOM_CONFIG.INI" into the folder that the tool was installed (the default is C: \ Program Files \ Intel \ Manufacturing Flash Tool).
The function is said to be installed and functional guest running on X98 Air 3G, host.
Once the installation of the guest operating, it becomes host to the tablet and just run it.
Not supported - for now - the simultaneous execution of Android & Windows.
Remove the microSD card that you probably have the tablet, before initiation.
From Windows host -> Android guest (conversion to Android tablet)
- Unzip the Android DnX BIOS directly into the Windows installation on X98 Air 3G.
- Run with administrative rights (from command line) flash.bat file inside the folder BIOS_X98_Air_3G_android. H process starts with the completion of the installation DnX BIOS displays the message "FPT Operation Passed".
- Turn off the tablet holding the POWER button for 10 seconds.
- Run Intel Manufacturing Tool as administrator.
- On the tablet, hold the VOL +, VOL- and POWER until you see the logo of the Teclast. The tablet will be "stuck" there, is perfectly normal. Connect the tablet to the USB port on your computer, so you will receive the following message: "Entering DnX mode. Waiting for fastboot command..."
- In the Device Manager of Windows (Device Manager), find the Android ADB Interface and right-click -> Properties (Properties). In the window that appears, go to the Details (Details) and there in the drop-down menu choose the Hardware ID (Hardware IDs). Our interest rates VID and PID, as shown in the picture Figure_2.
Transfer the VID and PID values ​​in the respective fields of Manufacturing Tool, section SoC Devices.
- Disables the tablet holding the POWER button for 10 seconds and disconnect the USB.
- We keep the tablet down the VOL- and POWER to enter the mode droidboot. Once this happens, connect the USB cable again, go to the Device Manager Windows (Device Manager) and - as before - we find the values ​​of the PID & VID Android ADB Interface (values ​​are different from the previous Figure_3
Transfer prices PID & VID Manufacturing Tool in their respective fields of unity "Android devices", so o Dialogue Manufacturing Tool will be something like shown in the picture. Press "Apply" and "OK" to save the parameters. Close the application.
- Disconnect the USB cable from the tablet and disable.
- Xanatrechoume the Intel Manufacturing Tool as managers and go to the menu File -> Open. There, choose the folder of ROM (X98_Air_3G_ (C6J6)), find the file "flash.xml" and open it.
- We keep the tablet down the VOL +, VOL- and POWER in order to display the logo of running Teclast DnX, connect the USB cable and Intel Manufacturing Tool begins the process of flashing Android ROM. Wait until the process is complete, disconnect the tablet from the USB and disable the X98 Air 3G.
The conversion process in Android tablet has been completed.
3D GAMES FREEZES FIX (thanks to Akitoyo and acc007)​You can download the patch from here: patch for 3D games freezes
Then follow these steps:
1. Copy the update.zip to the root path of internal storage
2. Click OTA icon, then choose local update
3. Choose update.zip file then apply it, system will reboot automatically
4. There will be a new icon "Fastmode" on the desktop, choose it before launching large 3D games.
You must click it again if you reboot the tablet then play 3D games
If you haven't Teclast OTA app you can download it from here: Teclast update tool
If you want can find the apk attached to this post (fastmode.apk).
If you don't want use apk, use adb shell and then su to become root.Then launch these commands:
Code:
echo 400 >/sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_min_freq_mhz
echo 400 >/sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_max_freq_mhz
If you want a persistent fix, also after reboot you can create new file install-recovery-2.sh file and put it in ./etc folder with these istructions:
Code:
#!/system/bin/sh
echo 400 >/sys/class/drm/card0/gt_min_freq_mhz
echo 400 >/sys/class/drm/card0/gt_max_freq_mhz
Remember remount /system as rw and chmod this neely created file to 755. You can then execute it or restart to have it automatically started.
For more detailed tutorial look here : jcespi2005's tutorial
GOOGLE PLAY STORE FIX (thanks to Frontier and Hendrickson)​Anyone having issues with Google Play Store - this applies to both Air 3G with the latest 2.0.1 update (will post more information later) and Air II - please apply this fix.
Your OS should be rooted in order for this to work.
- Download the files from here.
- Follow this Hendrickson's Videotutorial
TECLAST X98 AIR 3G ANDROID KITKAT 4.4.4 ROM(OFFICIAL) v2.0.0 (thanks to Frontier)​Download the upgrade from here.
You also need the Intel Manufacturing Tools (get them from here).
After installing this ROM upgrade, you need to apply the Google Play store fix (links and instructions just above).
The procedure to install this ROM is described above in this post. Just ignore the part that describes how to flash the Android BIOS to the tablet, as it is not needed in this case.
This upgrade will erase all data in the internal flash storage (32GB), so make sure you have a recent backup for your applications.
This ROM is OTA safe, after installation the Teclast Software Updater will notify you for an updated ROM; install the update (it's quite small) so the final ROM version would be v2.0.1_20141505 (see Teclast_X98_Air_3G_Android_4_4_4.png).
Visible changes:
- Intel Firmware Updater Tool inside the Android system; you can use it to flash .bin files directly to the tablet within Android (dual-boot system).
- Google Play Store enhancements; I can install applications now that I couldn't with 4.4.2 release (e.g Google+, Paypal and various e-Banking apps).
- A (little) faster boot.
MICROPHONE GAIN FIX FOR ANDROID 4.4.4 (thanks to Frontier)​Here is the final version of the microphone gain fix.
Tests done:
- Voice recognition using Google Now and Google voice typing (even in Greek) works as good as on my OnePlus One with CM11s 44R
- GSM/3G voice calls are clear (I am using Wind GSM network) both with the built-in microphone and via Bluetooth headset (Samsung WEP210).
- Skype voice/video calls are clear, both with internal microphone and the Bluetooth headset.
Connect the tablet with USB cable to a PC with android debug bridge installed.
The tablet needs to have USB debugging enabled.
Open shell and cd to the location of new audio configuration file.
On a PC shell write:
adb root
adb remount
adb push AudioConfigurableDomains.xml /system/etc/parameter-framework/Settings/Audio
adb shell
In the adb shell write:
cd /system/etc/parameter-framework/Settings/Audio
chmod 644 AudioConfigurableDomains.xml
reboot
Done !
XPOSED ON 4.4.4 (thanks to majkel_94)​Ok guys, thanks to @jcespi2005 for Xposed ASUS mod which steer me to the correct solution in xda topic for Xposed
So here it is:
Downolad Xposed Installer (2.6.1 has been tested, modules working ok), install it but don't launch the app or install framework.
Download Root Browser, install and open it.
In root browser:
go to the /data/data/de.robv.android.xposed.installer/ and create folder "conf" (permissions rwxrwxrwx)
in folder "conf" create the file "jit_reset_offset" (permissions rw-r--r--)
Download Terminal Emulator, install and open it. Then:
type "su"
type "echo 0x98 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset"
Reboot the tablet.
Open Xposed Installer, install framework, reboot.
Profit! You have working the latest Xposed and working KK Gravitybox!
Remember: You can disable xposed at boot by repeatedly pushing a hardware button as the tablet begins to boot. For example you can use Vol + button.
HOW TO UNPACK AND PACK framework-res.apk CORRECTLY (thanks to mirek190)​Follow these instructions. mirek190's tutorial
ITALIAN TUTORIAL FOR UPDATE TO STOCK ROM FROM CUSTOM SELLER ROM (thanks to topdigamma.it)​topdigamma.it Tutorial
DUAL BOOT FAQ + HARDWARE AND LOW LEVEL FIXING​
FAQ
1)Q: While in Intel Manufacturing Tools and trying to flash, the progress bar is stuck at X%
The flash tool does not like funny characters ,should clear up some confusion as to why things aren't working.So before to flash please try removing the chinese characters from the file name. It screwed you up on something else having chinese in the name.
At 0%: Well, reconnect your device again, check your VID and PID values in settings, check if your drivers are properly installed, replace a cable if it is faulty, check that you're in DNX mode, basically, the flashing didn't even start.
If you have the right pid/vid from the device manager,unplug the device, close the app and restart it, select the flash.xml (should say ready to flash) then plug the device in while in DnX mode and it should begin.
At 5%: Mostly due to the fact that "Custom_config.ini" was not copied to the IMT directory, or there are some other programs that is blocking the progress, try changing a computer and flash again.
At 10 or 11%: Mostly due to wrong settings or parameters, check Device Manager in Windows for any missing drivers, check that the downloaded ROM is not damaged, or that the tablet is not already bricked. Also, this software is very sensitive to the USB port that it was first installed on, so try plugging it back to the same USB port that you plugged it during the install process. (Yes, you have to plug the device in during the install process, if you missed this out, uninstall all the drivers and redo the installation properly).Sometime help to try a different ROM, just to clarify you have copied the "custom_config" file to the Intel Manufacturer Tool folder right. It should get to 10% for about 5-10 seconds then make a disconnection sound and suddenly jump to 15% and continue.
At 89 or 90%: The files written at this stage are larger, so it might take a while longer, but if it is really stuck here, probably the USB cable is faulty. Replacing a cable and flashing again should solve the problem, or just simply leave the tablet and cables still (do not move them around) and try again.
If the flash freezes at 90% a solution could to be increase the timeout values in the program facturing flash tool.
At any other points: Might be due to faulty cables, or simply just try again!
2) Q: I flashed android bios, now I can not get in to droidboot mode by pressing Vol + and POWER. The tablet always gets into EFI shell command interface. I can only get to DnX mode by pressing VOL+ , VOL- and POWER. Any solutions?
A: Follow this steps valid for C6J6 and C8J7 model :
Open Intel manufacturing tools,then open file menu and go to the settings.
Put this value to SoC Devices: VID: 8087 PID:0A65
Put this value to Androird Device: VID: 8087 PID: 09EF
Click on apply and then on ok.
Disconnect the USB cable from the tablet and turn off your tablet (important)
Download the Android 4.4.4 ROM for C6J6 and C8J7 by supercows (link above)
Then in Intel Manufacturing Tool and go to the menu File -> Open. There, choose the folder of X98 Air 3G (C8J7.C6J6) lite 4Gb or 8GB and choice "flash.xml" for your device 4Gb or 8GB and open it.
Keep pressed VOL +, VOL- and POWER button until the tablet go to the dnx mode
Connect the USB cable and Intel Manufacturing Tool begins the process of flashing Android ROM.
Wait until the process is complete.
Disconnect the tablet from the USB and and turn off your tablet .
Connect the usb keyboard to the tablet and turn on your tablet, you could get shell command error again
Just type exit and you see the tablet go to the android version
When go to the android you must change your bios with ifwiupdate and you can flash dualboot bios or new android bios from first post
3) Q: I have problems getting into Android from the dual boot menu! Windows is okay.
A: If there are any problems getting into Android from the dual boot menu, change this option in the BIOS. Change "Boot Architecture" to "OS Boot Menu Only".
View attachment 3048901
4) Q: After shutting down the table in Windows, it takes very long before I can power it on again.
A: Turn off "Fast Startup" option in Windows Power Options. Another way is to navigate to "C:\Windows\System32", find "SlidetoShutDown.exe" and use that to shut down.
5) Q: The time in Android and Windows is not synchronised!
A: Go to "Run", type in "regedit", then navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation
Add in a new REG_DWORD, "RealTimeIsUniversal" and set its value to 1
6) Q: I plugged the tablet into the charger and it shows as charging but after a while I noticed that the battery percentage dropped!
A: Check the cable, it should be of good quality and as short as possible. Original teclast cable is good, not too long and thick enough. Best to use short cable of 5cm. This is due to high current and low voltage of the tablet.
7) Q: I'm on Android 4.4.2 and this tutorial needs me to upgrade to 4.4.4. How
A: Go to post #2, download the 4.4.4 ROM from there, start by following the tutorial from the line "WINDOWS 8.1 => ANDROID PROCEDURE (thanks to Frontier)" onwards all the way until you reach GOOGLE PLAY STORE FIX (thanks to Frontier). If you see the line "From Windows host -> Android guest (conversion to Android tablet)" in the tutorial, do not worry, because this process is used for both purposes, from Android to Android or Windows to Android, both are applicable.
8) Q: I flashed my tablet to dual boot OS already, but now I want to reinstall only one OS! How can I do it without having to reinstall everything?
A: If you want to reinstall Android only (leaving Windows unharmed):
One way is to flash just "system.img" through the Intel Manufacturing Tools (try this way first).
Download from here the zip named "ONLY FLASH system.img": http://1drv.ms/1s8dci8
Replace the "flash.xml" in your ROM folder with the one in this version.
Then flash as per normal using IMT.
This "flash.xml" will instruct the IMT to flash only the "system.img" file which is Android OS.
If that doesn't work, we will try flashing all components of the ROM without re-partitioning the whole eMMC,
Download from here the zip named "ONLY FLASH ANDROID PARTITIONS": http://1drv.ms/1s8dci8
Replace the "flash.xml" in your ROM folder with the one in this version.
Then flash as per normal using IMT.
If you want to reinstall Windows only (leaving Android unharmed):
Prepare your USB Drive with the Windows image.
Boot into Windows first, then restart and plug in the OTG cable, USB HUB, keyboard, and USB Drive.
Enter BIOS by pressing "ESC" key during boot and under the "Save and Exit" menu, scroll down to the "Boot Override" option, find the USB drive and select it to boot from it. The BIOS restart the tablet and will boot into the USB Drive so Windows install should start.
Remember the USB bootable stick must be created with Fat32 file system and GPT table partitioning.
9) Q: Help! My touchscreen is inverted!
A: (Thanks to @krisbliz):
Download the files from @krisbliz post here, and copy the files into C:\Windows
now run gpedit.msc
computer configuration
scripts (startup/shutdown)
startup
add
browse for reset driver.bat
10) Q: How to reinstall windows without reinstall android ? I cannot change the language and even updates from winddows update,every time when I put usb prepared and trying to install windows it working installation and after 65% shows installation error 0xc1440137 0x2000c and going back to previous instal (chinese) to windows
A: (Thanks to @mohamad_skiller):
Connect usb keyboard and usb windows instalition to your hub then
Enter BIOS by pressing "ESC" key during boot and under the "Save and Exit" menu, scroll down to the "Boot Override" option, find the USB drive and select it to boot from it.
The BIOS will boot into the USB Drive and Windows install should start.
11) Q: I have installed dualboot bios with a success. When I plug in usb to install the IntelAndroidDrvSetup1.5.0.exe, in the boot menu I can see a Windows in the right center of screen and in the right top corner two small icons of android and windows which I can check. I dont see Android logo in the center of screen?
A: (Thanks to @jcespi2005):
Sounds you install windows on top of android partitions.So check what partitions do you have in windows partition manager...If you deleted the android ones, you'll need to start over starting installing android again.
In any case, make sure you've followed these steps correctly:
blackman818's tutorial
12) Q: Why Microsoft Store doesnt work?
A: (Thanks to @Hendrickson ):
Run the troubleshooter (Search and type trouble shooter) And run it for the Store, this should re-install the drivers
13) Q: Why camera doesnt shows anything (the screen turns black and i have to exit to desktop)?
A: (Thanks to @Hendrickson ):
Reinstall the camera.inf and OV and GS camera drivers from the Air 3G drivers
14) Q: I can't use touchsceen and also screen rotation is not working. During installation , Windows stopped at language selection ,i had to connect usb moude and keyboard to make selection, is this normal?
A: (Thanks to @25gee ):
Yes,continue the installation and use drivers zip on the first page.Install the driver under gyroscope and run the registry file.Go into device manager,find the unknown device,install drivers and point manually to the drivers folder (it will install but fail to enable,this is normal) from here simply right click on the display,disable it and reenable, you can do the same with the 2 I/O devices for the orientation and accelerometer to fix the inverted screen rotation
15) Q: I partitioned my 32 GB SD card and formatted the smaller partition EXT4. Link2SD recognized the partition but it "fails to create MOUNT SCRIPT.
A: (Thanks to @kinhvanhoa ):
Probably you forgot to format your EXT4 partition on the SD CARD as "PRIMARY PARTITION."
Please make sure the EXT4 Partition which should be smaller than FAT32 partition, must be set as "PRIMARY" (FAT 32 as well).
Then, use LINK2SD on the Rooted Android, it works fine and allows apps to be moved to the EXT4 partition on the SD card.
16) Q: How can i change the intel turbo mode on to off? How can i enter in the bios mode? Only few games works, others freeze!.
A: (Thanks to @SUMMERBREEZE ):
Find an USB keyboard first and plug OTG cable to the tablet and turn it off. Turn the tablet on and immediately press ESC button. And follow the images (bios_1 and bios_2) i attached and do the settings carefuly. f4 save & exit
17) Q: I have problem with the dual boot bios, now I don't arrive any more to the page where there are the icons of the Android and Window (that I never saw it). Please could anybody known what happens, I am stacked on the installation of windows?
A: (Thanks to @grigoris_a ):
From switched off press power button once to boot and keep holding vol up key pressed
18) Q: I have installed dualboot bios with a success. The icon of windows is not showed,why?
A: (Thanks to @grigoris_a):
If you don't see windows icon it means the USB is not bootable.Try getting into bios and see if the USB drive is detected and check the file system on your windows usb drive it should be FAT32. Often the problem is inside the bios, maybe is enabled the options the EFI format on the boot option, disabled it the icon of windows appears and then you can started the installation.
18) Q: I start from Windows 8.1 then I installed the Dual Boot Bios (No problem).
I restart to the bios, power down the tablet and power up again and use the Windows 8.1 again (without reinstall anything) with 60hz. Everything perfect but... right now I cant install android because my tablet is not recognize by the PC I power off by pressing 10 seconds the power button. Then while its connected I power it up and shows the battery meter but the PC dont do anything so I cant use any program to flash android, any idea? I tried different cables and nothing
A: (Thanks to @Petepe10):
This is the normal way, do not know about dualboot though: Power up (vol up down power press) until screen shows dnx mode, and then connect cable. Flash starts automatically (provided pc is ready to flash of course)
19) Q: How to switch from an OS to another?
A: (Thanks to @BPM):
Power off the device and then press and hold vol+ and power until you see the bootmenu
20) Q: On the lockscreen in Windows the text in the lower right corner is chinese.
Sometimes there pops up chinese messages in the infobar (lower right corner in windows - left to the clock).How can i remove this?
A: (Thanks to @smartchip):
On Control panel : Clock, Language and Region : Language : Change date, time or number formats. On Formats tab - Match Windows display language (should be default). On Location tab - change "Home location" to get your Start Menu tiles to load news, recipes, etc from your country (open the apps when you're done and refresh). On Administrative tab - "Welcome screen and new user accounts" click "Copy settings", apply to all.
21) Q: I have teclast x98 air 3g dualboot version but accidentaly i touch in corner to swich off choosing the system, now i have only android.How ca I return to dual boot menu?
A: (Thanks to @smartchip):
Hold power + volume up to power on. You'll get the menu back
22) Q: On Windows is there any way to hibernate the tablet? I try to hibernate but doesnt works well,the tablets power off but you have to press power button for 10s to power it up again, and you start windows normally?
A: (Thanks to @seba2000):
Make a shortcut on your desktop to C:\Windows\System32\rundll32.exe PowrProf.dll, SetSuspendState Hibernate
and save it as "Hibernate" for instance.You can pin it to start as well.When you will run this shurtcut tablet will hibernate. Remember that after you will run this command (shortcut) you need to wait a bit before you will be able to switch on again (10-15 sec) . Do not try to switch on immediately - Windows needs time to dump all data from RAM to hard disk (need time to hibernate). In this tablet there is missing any led which show disk activity so you just need be patient.
After 10-15 sec you will be able to switch on by single power button press.
If you want add hibernate and sleep option in Windows, follow the vpx tutorial
23) Q:Why there is one hour difference between android and windows ?
A: (Thanks to @G3n3R4L):
Hit Start and type regedit.exe in the search box. Hit Enter and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\TimeZoneInformation. Right click anywhere in the right pane and hit New > DWORD (32-bit) Value. Name it RealTimeIsUniversal, then double click on it and give it a value of 1.
and done, time in windows is exactly the same as android under the correct time zone.
If you want to do these steps automatically you can use this reg file: abanglek's X98DualClockFix.zip
25) Q:Windows only reporting 1 battery cell, battery gets stuck at 7% for a few hours as mentioned previously here. Did anyone manage to fix the issue in Windows?
A: (Thanks to @grigoris_a):
1.Fully charge the tablet
2 Run cmd as admin and paste this command
powercfg-setdcvalueindex SCHEME_CURRENT SUB_BATTERY BATACTIONCRIT 0
3 Use the tablet until it shuts down
4 Charge the tablet without pushing power button until it charges fully.(let it overnight)
24) Q:Why I can't enter in fastboot mode?
A: (Thanks to @jcespi2005):
Just power off (press power off for 10 seconds), wait some time, 5 minutes, and press VOL+ VOL- and then power on until fastmode shows on the tablet. When you connect the tablet on fastmode, the Manufacturing tool just boot a droidmode image like this:
01/14/15 00:14:29.870 INFO : Port 0/0/4 #0: Booting droidboot image - SN : Baytrail00005B06
01/14/15 00:14:32.914 INFO : Port 0/0/4 #0: Booting to droidboot.img success - SN : Baytrail00005B06
25) Q: The brightness auto dimming up and down by itself. But This tablet no light sensor and cannot enable/disabled auto brightness.
A: (Thanks to @melvincz):
Go to the Intel Graphics settings utility (find it in the tray), choose Power section and disable all energy savings functionality. That will fix the auto-dimming issue.
That's all! ENJOY! If there are any questions feel free to post in the forum. Thanks!
HARDWARE AND LOW LEVEL FIXING
FLASH BIOS WITH THE USB PROGRAMMER AND CLIP (thanks to Hendrickson)
You can follow the tutorial here:
Russian Tutorial
The clip took a few goes to connect and it finally do when you hear the windows beep beep that new hardware is detected. Flashed and verified and boots fine. Windows 8.1 installed the drivers itself. You don't need to install them.
Some tips, I did it with the battery connected and fully charged. I used the 25xx slot on the usb programmer and the clip #1 is the colored cable of the 8. #1 on the clip to the . connector on the winbond chip itself.
Flashing took around a minute its quick.
DISPLAY BRIGHTNESS THROTTLING (thanks to Petepe10)
I think I found a way to prevent that the display is heavily dimmed due to a thermal event. It is in thermal_throttle_config.xml in system/etc. My interpretation is that by the mod below the brightness reduction is not immediately to 40 percent but goes down in steps to 80 60 40. Wouldn't you agree? I have not found the trigger settings yet though. The xml is editable (I use total commander), reboot afterwards. I will test some more. Of course such thermal mods are not without risk, so be warned..
Code:
<!--Cooling Devices-->
<ContributingDeviceInfo>
<CDeviceName>Display</CDeviceName>
<CDeviceID>1</CDeviceID>
<CDeviceClassPath>com.android.server.thermal.Brigh tnessControl</CDeviceClassPath>
<CDeviceThrottlePath>none</CDeviceThrottlePath>
<ThrottleValues>
<!--ThrottleNormal>100</ThrottleNormal-->
<!--ThrottleWarning>40</ThrottleWarning-->
<!--ThrottleAlert>40</ThrottleAlert-->
<!--ThrottleCritical>40</ThrottleCritical-->
<ThrottleNormal>100</ThrottleNormal>
<ThrottleWarning>80</ThrottleWarning>
<ThrottleAlert>60</ThrottleAlert>
<ThrottleCritical>40</ThrottleCritical>
</ThrottleValues>
</ContributingDeviceInfo>
FIX EMMC (thanks to stachoo777)
You can follow the tutorial here:
stachoo777 Tutorial
Be aware of broken droidboot mode when updating to newest ifwi bios for c6j6. One hint for this is that efi shell is like dos so if you want to go to USB just type "fs1:"
FIX PROBLEMS OF HEAT DISSIPATION (thanks to acc007)
acc007 Tutorial
FIX HEADSET PROBLEM(thanks to Hendrickson )
If with music, it sounds like it's being played through a tunnel, or been compressed down to something like 8kbps. The main instrument tracks usually sound fine, but the vocal track is heavily muted and in some tracks practically inaudible; it's also tinny and a bit distorted.
It's not defective, it's a Iphone style jack, if you don't fully insert your 3.5 plug it will sound normal. Or use a headphone without a mic or a converter like this one: http://www.ebay.com/itm/301385140519?_trksid=p2060778.m1438.l2649&ssPageName=STRK%3AMEBIDX%3AIT
WINDOWS DEVELOPMENT​
Disclaimer : these proceedings or files are provided "as are" and i'm not responsible for any lost (hardware / software )
I would also like to point out that these procedures have been tested for the model C6J6
WINDOWS 8.1 PRO ISO
http://getintopc.com/softwares/operating-systems/windows-8-1-download/
WINDOWS 8.1 WITH BING (Teclast beta version - no driver nedeed)
https://drive.google.com/folderview...&usp=sharing&tid=0BzgIeN_XB6mlUmFieDdxa3JkUHc
WINDOWS 8.1 LANGUAGE PACK
https://social.technet.microsoft.co...uage-pack-for-windows-81?forum=w8itprogeneral
WINDOWS 8/8.1 TECLAST COMPONENTS DRIVER
https://mega.co.nz/#!tJdHCIAT!agSun8Wa1tOx_3tL8YMuS19j1i5wWG2WUJPprmTbTCs
ADB DRIVER
https://mega.co.nz/#!3JshGCLB!6ldn4tPJZlZtDvlR17pmxhqxkrDs4OxxyCJhIHyhZ-4
Note: The camera driver not work correctlly on Windows 8.1, after OS installation it's necessary to install ManyCam Pro to get a satisfactory use of the camera
ANDROID => WINDOWS 8.1 PROCEDURE (thanks to Frontier)​
Required materials:
- A USB stick of 256MB (generally small), FAT32 configuration with label (label) WINPE (uppercase).
- A USB stick capacity of at least 8GB, formatted system NTFS. This will pass the installation files Windows 8.1.
- A USB hub to connect these two sticks in OTG cable X98 Air 3G. The hub would be good to have its own power supply.
- A Teclast X98 Air 3G (obviously), battery sufficiently charged (recommended to be fully charged the battery before you start the process).
Preparing USB sticks:
- Unzip the file WinPE_User_20140814.7z and copy all files directly on the root directory of the USB stick WINPE. See the picture Figure_1.
- Unzip the installation files for Windows 8.1 DVD into a folder named "images", which should be on the root directory of the USB stick of 8GB (with NTFS configuration). The Windows 8.1 version with Bing for X98 Air 3G is here (5 files total): Part1 , Part2 , Part3 , Part4 , Part5 . Inside the folder images, you need to have the files install.txt, install.wim, UnattendAudit.xml, UnattendUser.xml, WIMPART.TXT, Winre.wim. If you want to use your own image and make the USB stick with a tool (Rufus, etc), drivers for the Windows X98 Air 3G is here . If you use Rufus remember to use MBR for UEFI, not GPT!.
See the picture Figure_2
Preparation of material:
- X98 Air 3G enabled USB debugging in the settings.
- On the PC, will be available the tool adb (part of the platform SDK) and have installed the ADB drivers (adbdriver.com). The PC should recognize the X98 Air 3G before starting the procedure.
- It is recommended to install Intel Manufacturing Tools before turning the tablet on Windows tablet, in order to be able to restore it to operating condition if the procedure fails. These are available in two versions, the newer and older . Start with the newest and if do not work on your computer, install the older version. Only one version must be installed on your computer.
Upgrade Preparation tool (Intel Manufacturing Tools)
- Unzip the computer you use to convert (not tablet), the Android ROM given above.
- Unzip one of the two available sets of tools Intel Manufacturing Tools. Inside the folder, you will find some executables that run in the following order and always with administrator privileges:
iSocUSB-Driver-Setup-xxxexe: At some point during the installation, you will know that you have to connect the X98 with USB cable to the computer to install the NAND drivers. H connection is necessary otherwise you can install to see and shape the NAND memory of tablet.
IntelAndroidDrvSetupx.xxexe: We run this installer as an administrator with the tablet plugged in USB. This will install the ADB driver Intel, which appears in the Device Manager (Device Manager) for Windows.
ManufacturingFlashTool_Setup_x.xxexe: This tool is used in the final planning "name" (branding) of the tablet and install the fastboot kernel. Install with administrator rights on the proposed application folder (hold down the name of the file for the next step).
- Upon completion of the installation of the Intel Manufacturing Tool, copy the file "CUSTOM_CONFIG.INI" into the folder that the tool was installed (the default is C: \ Program Files \ Intel \ Manufacturing Flash Tool).
The function is said to be installed and the guest OS you are running on X98 Air 3G, host.
Once the installation of the guest operating, it is now host to the tablet and just run it.
Not supported - for now - the simultaneous execution of Android & Windows.
Remove the microSD card that you probably have the tablet, before initiation.
From Android host -> Windows guest (conversion to Windows tablet)
- Uncompress file BIOS_X98_Air_3G_android_to_windows.7z folder without spaces in the name (eg C: \ Temp). We should be inside the unzipped folder, a subfolder 'fpt-tools-package'.
- Connect the tablet to the PC and wait (in Windows) to recognize.
- If you have rooted your device,from a command prompt (with administrator rights), we give the following commands:
adb push c:\temp\fpt-tools-package data/local/tmp/
adb shell
cd data/local/tmp
chmod 0777 FPT
su
./FPT -F X98Air3G.bin
- If you have not rooted your device,from a command prompt (with administrator rights), we give the following commands:
adb push c:\temp\fpt-tools-package data/local/tmp/
adb root
adb shell
cd data/local/tmp
chmod 0777 FPT
./FPT -F X98Air3G.bin
- Once the execution of the last command and display the message "FPT Operation Passed", disable the tablet holding and hold POWER. See the picture Figure_3.
- Connect the two USB sticks in USB hub and the hub of the OTG port X98 Air 3G. Activating the X98 Air 3G with the POWER button, and automatically starts the installation process of Windows 8.1. The whole process takes a long time - and for this reason it is recommended that you fully charged the battery - and requires no user intervention. See the picture Figure_4.
If you do not automatically start the process, connect a USB keyboard to the hub, then reset the tablet (CTRL-ALT-DEL or off) and after doing reset, enter the UEFI BIOS by pressing DEL. At the boot menu, go to the Boot Override option and press ENTER on the USB stick (small in size) to do boot from there. See the picture Figure_5.
- When the message "WIMboot image deployment COMPLETE. Type EXIT from command prompt to restart or turn off the device." You can disconnect the USB hub and terminate the tablet. See the picture Figure_6.
The process of converting the X98 Air 3G in Windows tablet, complete!
After the Android to Windows conversion is it recommended first install the Gsensor, run the kxaccel-win8-x86-dbg-intel.exe that comes in the folder GSENSOR in the attached zip in and then execute the reg file.
Finally copy the TouchSetting.gt to C:\Windows\inf folder and reboot.
Everything should go smoothly now.
For the Italian friends I have prepared a simplified guide in Italian pdf.
CHINESE TOOL FOR CLEAN WINDOWS FOLDER AND FREE MORE SPACE (thanks to BoORDeL and keepfishes)​
The zipped file is attached to this post (Windows_Cleaner.zip).
Execute the exe and click on button showed in Figure_7.
You will see a list of folder that can be cleaned (if this doesn't happen change permissions on your windows folder : http://tipsandtricksforum.com/thread-223.html )
Than select the checkbox near folders name and let the program clean them by pressing button as shown in the Figure_8
INVERTED CAMERA FIX (thanks to ro11er and Hendrickson)​
You can downlad the fix from this url:
Inverted Camera FIX
You need to uninstall these three devices and reboot:
Kionix KXCJ9 Accelerometer SPB
Goodix Touch HID
Intel Graphics
Then after reboot install in this order from the attachment download in above link.
Intel Graphics
Goodix Touch
kxaccel-win8-x86-dbg-intel.exe and registry
Once registry entry is done and reboot monitor will be reversed. You must change registry to this value: 01 00 00 01 01 00 02
Very important: Do not do video drivers update or u will loose all your configuration!
UPDATED WIRELESS AND BLUETOOTH DRIVERS (thanks to Hendrickson)​If you have problems with wireless when using bluetooth at the same time it was so damn slow, you can use updated bluetooth and Wireless drivers attached to this post ( Air_3G_Updated_WLAN_and_BT_drivers.zip).
These drivers were discovered November 4th from Dell site and seems to have fixed the issue.
TUTORIAL FOR DOWNLOAD WINDOWS METRO APP WITH IDM (thanks to mohamad_skiller)​For read tutorial click here: Mohamad_skiller's tutorial
BATTERY PROBLEM FIX (thanks to puzdar )​For read tutorial click here: puzdar's tutorial
HOW TO CHANGE LANGUAGE FROM CHINESE (thanks to Hendrickson )​For see the tutorial click here: Hendrickson's tutorial
DUAL BOOT DEVELOPMENT​
TUTORIAL VIDEOS
Hendrickson's complete Tutorial
This tutorial cover:
intel mfg tools installation
drivers
flashing
partitions
making a bootable usb drive
windows installation
windows drivers + fixes installation
DEMO VIDEOS
supercowz's Teclast X98 air 3G dual boot
UPGRADE FLOW PROCESS SCHEME(thanks to Petepe10)
upgrade flow process scheme
LAST BIOS
Be very carefull, you could brick your tablet if you use a version of bios not in conformity with your tablet model.I take absolutely no responsibility for damage caused by the flash of the following bios.
C9J8 ( Warning, the tablet could became instable with random rebooting and even if you turned it off you have to wait 2 min to power it again)
mirek190 modified C9J8 bios
AIR II DUAL (compatible with C6J6)
grigoris_a AIR II DUAL bios
Disclaimer : these proceedings or files are provided "as are" and i'm not responsible for any lost (hardware / software )
I would also like to point out that these procedures have been tested on C6J6 only. For C8J7, there are some additional pointers along the way, do look out. All files in this tutorial are by default for C6J6, unless otherwise stated. Is highly recommend reading through the whole post first before touching your tablet to prevent errors, or worse, bricking the whole thing
Install dual boot(C6J6) - KEEPFISHES TUTORIAL (thanks to supercowz, mohamad_skiller, ro11er and Frontier)​
Please before you begin to read this tutorial is better to watch the Hendrickson's complete Tutorial video that show and explain all the needed steps for dual boot implementation.
The original post of keepfishes is here. in case he make some updates and it is not shown in this post
I found that the tutorial on the first page lacked detail and some steps were not shown clearly, so I made a new one that I think is easier to follow for newcomers! Will add screenshots soon.
Dual boot BIOS benefits:
Fixes 60Hz refresh rate for Windows 32 bit system
Probably on old bios there are low voltage settings for GPU that makes some problems with 3D games,after updated to dual bios no problems at all for many users
Drawbacks:
BIOS settings very little
No boot menu (so no easy way to reinstall Windows with a USB drive)
Time in Windows will mess up when using dual OS
The flashing process is roughly as such:
Click image for larger version
View attachment 3050134
Many of us have different start points, some are coming from Android, some from Windows, but it does not matter. First thing is to flash with dual boot BIOS, which is most important.
WARNING: (Be very careful, this part may brick your device. After you get past here, you can practically do anything you want and there is almost no risk of bricking your device, so pay attention here!)
Get dual boot BIOS files here (both C6J6 and C8J7): http://pan.baidu.com/s/1sjK4Zbn
View attachment 3048864
Extract the BIOS "完美双系统BIOS.7z" and copy the contents to the tablet.
Note the filepath on the tablet, you will need it later.
1a) Flash BIOS from existing Android system
NOTE:
If your existing Android version is 4.4.4, you can use the "UpdateIFWI.apk" that was installed on the system to flash the BIOS.
If Android version is 4.4.2 on C6J6 and there is an "UpdateIFWI.apk" on it, there have been reports that it does not flash properly. (as reported by @ambrosio5)
Current advice is to update to 4.4.4 before proceeding. .For instructions on how to upgrade to 4.4.4 from other previous Android versions, see FAQ 7 below.
From the tablet itself, run “UpdateIFWI.apk”, select "Browser" and point it to the filepath of the BIOS named "X98Air3GDuala.bin''.
STOP: Make sure you have at least 50% battery and chose the correct file! If this fails, it might BRICK!
Now flash the BIOS.
1b) Flash BIOS from existing Windows system
From the tablet itself, RUN AS ADMIN the .bat file in the folder (the one with chinese words) provided.
View attachment 3048853
After you see the Green line “FPT Operation passed”, it’s good news.
Now reboot the system and you will be taken to the BIOS screen. Just igonore it and press power button for 10 seconds to turn it off.
2) Installing ANDROID first (must be done before Windows)
Now we need to FIRST install ANDROID. This step will wipe out your whole tablet (INCLUDING ALL PREVIOUS WINDOWS AND ANDROID PARTITIONS AND DATA)
ON ANOTHER PC (not tablet), download the Android 4.4.4 Lite ROM here: https://mega.co.nz/#!KI8T0bBb!Pv25K1Rh0MJvXSCYQEC8P8l1mbsZQRgG6q5-XezP_aI
OR
SUPERCOWZ ANDROID 4.4.4 C6J6 AND C7J8 ROM For Both: https://mega.co.nz/#!zVdgWJyS!Vh7zGqX6NcYgXrCf-5v_qmEReZXuicvGzw6h1u5OnGo
OR
USE ANY OTHER ROM YOU WISH
Download this modified "partition.tbl" file from the Chinese: http://pan.baidu.com/s/1qWnxc4G
Inside are two folders, the 5000 one is 5GB Android space, the 8000 one is 8GB Android space. I personally used 5GB, because I want to leave more space for Windows.
View attachment 3048857
Download and install Notepad++, we need to edit "partition.tbl" file below, the Notepad.exe and Wordpad.exe built in on Windows DOES NOT SAVE THE FILE CORRECTLY AND WILL NOT WORK!
Extract the contents of the ROM to a folder. You should see a "partition.tbl" file inside.
This file controls how the 32GB eMMC in the tablet will be partitioned in this step.
View attachment 3048867
Copy the "partition.tbl" file FROM the Chinese download (either 5000 or 8000) TO the Android ROM folder that you extracted. Replace the original "partition.tbl" file that came with the ROM.
Edit the "partition.tbl" file in the Android ROM folder, find the second last line, which is "add -b 5931048 -s 10240000 -t data -u 80868086-8086-8086-8086-000000000008 -l data -T 0 -P 0 /dev/block/mmcblk0"
and change the highlighted number to the value of user space you want in Android. The number is a multiple of 2048, so let's say if I want 500MB user space, I would have to multiply 500MB x 2048 = 1024000 and input "1024000".
View attachment 3048872
I tried 300MB but it was too small, I think 500MB would be good if you're planning to use more Windows. Save the file!
Credits to FRONTIER for Android ROM flashing instructions (I made a number of changes):
The tools of the platform upgrade Intel (Intel Manufacturing Tools). These are available in two versions, the newer and older . Start with the newest and if do not work on your computer, install the older version. Only one version must be installed on your computer.
- Unzip the downloaded Intel Manufacturing Tools. Inside the folder, you will find some executables. RUN THEM IN THE FOLLOWING ORDER WITH ADMIN RIGHTS:
iSocUSB-Driver-Setup-xxxexe: During the installation, DO NOT PLUG IN YOUR TABLET. Near the end of the install, there will be a text asking saying that you need to plug in tablet and power cycle to complete installation. ONLY PLUG IN YOUR TABLET THEN, and do as the instruction says. After you're done, click Finish. After install, you should see Intel SOC device in your device manager.
IntelAndroidDrvSetupx.xxexe: Plug in your tablet, and MAKE SURE that your computer RECOGNISES your tablet. You will see unknown ADB device if you plug in the tablet. Now run this program as ADMIN, this will install the ADB driver for the unknown device. In device manager, if it still shows unknown device after install, manually update the driver in device manager and browse to the install directory of the driver, it will then install the driver from there.
ManufacturingFlashTool_Setup_x.xxexe: Install with ADMIN rights, this will install the Flash tool with the Lightning icon, which is the GUI interface we use to flash our tablet.
Copy the file "CUSTOM_CONFIG.INI" from the downloaded folder into the install folder of IMT (the default is C: \ Program Files \ Intel \ Manufacturing Flash Tool).
Remove the microSD card from tablet.
Run Intel Manufacturing Tools (the one with Lightning icon), In the Settings menu, change the VID and PID values to this, then click apply and OK:
If you're using Windows XP, your VID and PID values may be different to the ones shown. Check the instructions on Post #2 on how to get the values.
View attachment 3051023
Close the IMT application and launch it again. Go to the menu File -> Open. There, choose the folder of ROM you want to flash, find the file "flash.xml" and open it. The "flash.xml" file which tells IMT how to flash the tablet's eMMC.
(IF YOU ARE USING SUPERCOWZ Android 4.4.4 C6J6 and C7J8 ROM, here are his instructions, :
flash with ManufacturingFlashTool
for C6J6 open in ManufacturingFlashTool :
flashC6J6-4GB.xml or flashC6J6-8GB.xml
for C8J7 open in ManufacturingFlashTool :
flashC8J7-4GB.xml or flashC8J7-8GB.xml
this last action dedicate 4 or 8 gb of rom space for Android and you can install windows in 18.5 or22.5 gb free rom space.
Then reinstall Android rom as before (open manufacture flash tools and select flash.xml)
After install android rom you can install windows as before (using bootable windows usb disk and select 18.5 or 22.5gb rom free))
-----------------------------------------------------------------------------------------------------------------
8) Turn off the tablet holding the POWER button for 10 seconds.
- Run Intel Manufacturing Tool as administrator.
- On the tablet, hold the VOL +, VOL- and POWER until you see the "Entering DnX mode. Waiting for fastboot command..."
Click image for larger version
View attachment 3048873
- Connect the USB cable to the computer and flashing will start.
- After progress bar is green and 100%, hold down power button for 10 seconds to turn off tablet.
If the progress bar turns red, take note of the percentage that it stopped at, and refer to FAQ 1 below.
Click image for larger version
View attachment 3048876
After finishing these steps, Android is now installed on the tablet, and if you power it up, you can see the dual boot menu with the Android logo.
Click image for larger version
View attachment 3048880
If you're happy with ANDROID only without Windows, you can stop here and just boot into Android! You can go on to do the Google play store fix and others...
3) Installing Windows
If you plug in your USB drive via the OTG cable and boot up, you will see the boot menu with an Android icon and a small Windows icon. (If you don't see the boot menu at all, shut down the tablet and press Vol + and Power button until the boot menu appears).
This small Windows icon is the only way to get the BIOS to boot into your USB drive to install Windows. This dual boot BIOS has no boot menu, and in the BIOS there is no option to select to boot from USB, so this is the only way to boot to a USB drive that I know of so far...
(If you already have a USB stick prepared, skip this section in BLUE)
Preparing your Windows USB Stick:
You can install Windows via the traditional method which involves the GUI (in which case you will need an OTG HUB to plug in the USB Drive and mouse together) OR you can use a downloaded wimboot image (no need for HUB and mouse, just a thumbdrive will do).
Whatever the case, make sure your USB Drive is formatted as FAT32! Very important!
I used this wimboot image that automatically uses WinPE to get through the whole install process automatically without needing a single mouse click, which also has all the drivers and everything installed and working properly:
Waiting for repost on mega...
Link: http://pan.baidu.com/s/1hqIfAle
password: zhec
Extract the downloaded files and then copy all the contents into the root of the USB Drive. NO NEED FOR RUFUS!
If you are not using the above images, and use other Windows ISO or images as found in Page 1 or if you want to make your own images, you will need this software RUFUS:https://rufus.akeo.ie/
Follow tutorial here on creating the USB Drive: http://www.techverse.net/how-to-create-bootable-usb-flash-drive-install-windows-8-1/
Remember to use MBR for UEFI, not GPT!
If your Windows doesn't come with drivers, you can download them from here and install them:
https://mega.co.nz/#!tJdHCIAT!agSun8Wa1tOx_3tL8YMuS19j1i5wWG2WUJPprmTbTCs
Here also a Windows 8.1 PRO version with drivers and English/French language pack (thanks to supercowz):
Win 8.1 PRO with driver and eng/fr language pack
Plug in the USB drive via OTG cable or HUB, and choose the small Windows icon until it turns blue, then hit the grey button below and Windows installation should start.
If it asks you for which partition to install to, you will see a great many partitions there (due to Android), don't worry, it is normal. Typically you will install Windows to the largest available partition. (Unless you set the Android user space partition in the "partition.tbl" file previously to be huge)
DO NOT TOUCH ANY OF THE ANDROID PARTITIONS, IT WILL DESTROY THE ANDROID SYSTEM!
Everything should go smoothly from here and you can remove your OTG cable and USB drive once Windows starts asking for your User Name.
4) Final Steps
One last step. Thanks to Android, we have to hide the Android partitions from Windows, because when we open "This PC", Windows will attempt to mount all the partitions and cause the whole thing to hang.
So, go to control panel, administrative tools, computer management, then Storage, then for each of the RAW partitions that belong to Android, right click and choose "change drive letters" and choose "remove", then OK. Repeat for the rest of the partitions, leaving the C: drive alone. DO NOT DELETE ANY PARTITIONS OR ANDROID WILL NOT WORK!
Note: For people who only want to install Windows and don't want Android but still want the dual boot BIOS (due to the 60Hz refresh rate), I have tried it and it works. What you need to do is to follow this tutorial exactly, but REPLACE STEP 2 WITH THE ONE BELOW:
STEP 2) This step will wipe out your whole tablet (INCLUDING ALL PREVIOUS WINDOWS AND ANDROID PARTITIONS AND DATA)
Yes, even though we are not installing Android, we need this step still:
ON ANOTHER PC (not tablet), download the Android 4.4.4 Lite ROM here: https://mega.co.nz/#!KI8T0bBb!Pv25K1Rh0MJvXSCYQEC8P8l1mbsZQRgG6q5-XezP_aI
OR
USE ANY OTHER DOWNLOADED ROM AS YOU WISH
Download this modified "partition.tbl" file from the Chinese: http://pan.baidu.com/s/1qWnxc4G
Download and install Notepad++, we need to edit "partition.tbl" file below, the Notepad.exe and Wordpad.exe built in on Windows DOES NOT SAVE THE FILE CORRECTLY AND WILL NOT WORK!
Extract the contents of the ROM to a folder. You should see a "partition.tbl" file inside.
This file controls how the 32GB eMMC in the tablet will be partitioned in this step.
Copy the "partition.tbl" file FROM the Chinese download from the 5000M folder TO the Android ROM folder that you extracted. Replace the original "partition.tbl" file that came with the ROM. Edit the "partition.tbl" file in the Android ROM folder, find the second last line, which is "add -b 5931048 -s 10240000 -t data -u 80868086-8086-8086-8086-000000000008 -l data -T 0 -P 0 /dev/block/mmcblk0"
and change the highlighted number to 2048. Save the file!
Open "flash.xml" with Notepad++.
DELETE this chunk:
<code_group name="system">
<file TYPE="system">
<name>system.img</name>
<version>eng.yankendi</version>
</file>
</code_group>
AND THIS CHUNK BELOW:
<command>
<string>fastboot flash system $system_file</string>
<timeout>420000</timeout>
<retry>2</retry>
<description>Flashing 'system' image.</description>
<mandatory>1</mandatory>
</command>
Then save the file.
Follow the post on the FIRST PAGE HERE, scroll down and start from this part onwards “WINDOWS 8.1 => ANDROID PROCEDURE (thanks to Frontier))” until the end (stop at "GOOGLE PLAY STORE FIX (thanks to Frontier)"). READ BELOW FIRST:
Because we have already done certain steps, we can ignore some parts:
PARTS TO IGNORE:
Under the "Required materials" section
IGNORE: “- The Android DnX BIOS (or Android BIOS) from here “
If you wish, you can use Android 4.4.4 lite ROM in place of the 4.4.2 ROM as proposed here.
Under the "From Windows host -> Android guest (conversion to Android tablet)" section
IGNORE all these: (because we have already flashed BIOS)
- Unzip the Android DnX BIOS directly into the Windows installation on X98 Air 3G.
- Run with administrative rights (from command line) flash.bat file inside the folder BIOS_X98_Air_3G_android. H process starts with the completion of the installation DnX BIOS displays the message "FPT Operation Passed".
After finishing the steps, you can power it up, you can see the dual boot menu option with the Android logo and a very small Windows icon. Continue and follow STEP 3 in the guide. You can partition your 32GB eMMC in the Windows setup to remove all previously created Android partitions and make it into one large Windows partition to install Windows.
For dual boot FAQ click here
INVERTED TOUCH FIX UNDER WINDOWS (thanks to krisbliz)​
You can use the DevManView to restart the "Goodix Touch HID" before the windows logon screen and everything working perfect again.
Here are the steps:
Download the file "disable enable touch driver.rar" attached to this post
So first copy the extracted files in Windows dir
Now run gpedit.msc
Computer configuration
Scripts (startup/shutdown)
Startup
Add
browse for reset driver.bat
Then reboot to test.
SPACE PROBLEMS IN WINDOWS 8.1 AFTER WINDOWS UPDATE (thanks to jcespi2005)​
Follow these istructions to clean WinSxS folder:
http://www.eightforums.com/tutorials/44351-winsxs-folder-component-store-clean-up-windows-8-1-a.html
SLEEP PROBLEM IN WINDOWS 8.1 (thanks to sasort)​
Follow these istructions:
First open cmd as admin and check status with this command:
powercfg /sleepstudy
It should give you this reply:
No connected standby traces available. Report not generated.
Now start regedit an go here:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Power
Change the value of the key CsEnabled from 1 to 0 and reboot.
(1 means connected standby enabled and 0 disabled.)
After reboot.
Now go to the control panel and select Energy, under Advanced there will be many new settings.
Don´t change anything, just select save settings.
Then with regedit change the CsEnabled key back to 1 and reboot again.
Open cmd as admin and again check status with the command:
powercfg /sleepstudy
It should now work and create a sleepstudy-report.html and the sleep function now works as expected.
MANAGE APP UNDER ANDROID (thanks to jcespi2005)​
You can use link2sd to move app, libs and data, and FolderMount to link and move OBB and SD data to microSD
BATTERY DRAIN FIX UNDER WINDOWS (thanks to vpx)​
The main problem is very old (year 2006) driver of "Intel SD Host Controller", they are 3 in Device manager. Only thing what you need is update driver.
start Computer Management (hold My Computer and select Manage)
select Device management
find SD Controllers, if you click on it, there are 3 "Intel SD Host Controller"s
hold on every one controller, select "Update Driver", select driver from computer, and there is another option "SDA Standard Compliant SD Host Controller", install driver, confirm restart of computer after last update install
reboot
WIFI FIX UNDER WINDOWS (thanks to Hendrickson)​
If you see that ping on windows is very strange,sometimes i have lost packets and ping time is not stable try this fix: techtablets repository
BATTERY CALIBRATION FIX UNDER ANDROID (thanks to Hendrickson)​
Try this, download and run advanced battery calibrator from Play and Battery Life repair:
Blackmart Studios - Battery riparator
Blackmart Studios - Advanced Battery Calibrator
This seems to have fixed the issue.
Maybe you should copy some post about Air 3G from X98 Air thread?
Nice english instructions for rooting, Win->Android, Android->Win, removal of bloatware etc. would be nice. Everyone can use google translate to navigate official chinese forums but you will get funny translations like "Brush Wizard software". If instructions are unclear and they leave space for interpretation mistakes can happen. Worst case scenario is bricked device.
After using windows and Android I still have the same gpu issues. I also looked in the log and at the end of every crashlog (in android) I see a dev_prive->gpu_error, which is a call from the kernel. (I saw some code on the internet about this) So, my intel Atom chip is bad. Going to return it and ask for a replacement.
The error seems to only happen when I use an app that uses opengl 3.0 (and a LOT of games use that!).
Also about the touchscreen, there seems to be a major problem with the driver in linux. Since I guess they cross-compiled the driver, I am guessing they made the same mistake in both android(linux) and windows.
How did I verify this? Well I used a goodix android application which had some demo app and I saw that the moments the touchscreen gets refreshed are not constant. Let me explain.
When I slide my finger over the touchscreen with a constant speed this happens to my tablets:
This is what my "old and smooth" tablet does(every dot is a touchscreen refresh): .---------.---------.---------.---------.---------.---------.---------.---------. (this is a constant refresh)
This is what my X98 Air 3G does: .--------.--.---------.-.-------.------.-------.-.-----.-----.-.-----.------.----.----.---------.-------.----. (not constant at all)
So the times the touchscreen gets refreshed is not constant. The result is that especially scrolling doesn't work that smooth.
And on top of that, the response time is extremely slow. I am guessing that the driver puts the touchscreen into sleep mode after every single touch, which is stupid. The response (as stated in the goodix GT9271 datasheet) is <200ms. Lets say it's about 100ms, do you know how slow that is??? If your mouse would only refresh every 10th of a second, it would be extremely slow!!!
If I didn't have gpu issues and the touchscreen issue would be corrected, this tablet would be superb, but that is not the case of course.
I am going to contact Teclast if they want my help in enhancing the touchscreen driver. (I am an embedded software engineer specialized in C/C++/C# code)
Also, I might be able to make simple C# app that does most of the work when you want to flash your tablet from android to windows. (this could also be done with a very simple windows batch script)
Jote said:
Everyone can use google translate to navigate official chinese forums but you will get funny translations like "Brush Wizard software". If instructions are unclear and they leave space for interpretation mistakes can happen. Worst case scenario is bricked device.
Click to expand...
Click to collapse
Hi Jote, sorry again for my bad english.
The biggest problem is that most of the information and instructions on how to root, how to change OS,etc.. come from the Chinese manufacturer's forum.
As written before your help in any way will be really appreciated! This is true also about the translation from chinese to the english language.
I ordered this tablet because I think it has enormous potential enclosed in a shell of very small dimensions, if we combine our knowledge to bridge the gap of the Chinese language I think we have great satisfaction with it.
I will try to add link to files for rooting, for change the OS and get other resources asap.
My tablet hasn't arrived yet but I tried to prepare everything.
I'm unable to browse the official forum. I've tried on several days but forums are just working extremely slow. When i try to browse directly through Google Translate I get "Proxy server to access restrictions ". I'll try again someday to find proper threads but right now i'm useless.
So the touch screen is going into sleep states very quickly? I noticed compared to the Onda v975w that it was much slower. I have the X98 3G air now and I have gotten use to it. But it would be nicer if it was how you pointed out.
I have disabled Allow the computer to turn off this device to save power, under power management on the Goodix Touch HID in device manager.
Jote said:
My tablet hasn't arrived yet but I tried to prepare everything.
I'm unable to browse the official forum. I've tried on several days but forums are just working extremely slow. When i try to browse directly through Google Translate I get "Proxy server to access restrictions ". I'll try again someday to find proper threads but right now i'm useless.
Click to expand...
Click to collapse
You have to use translator from bing/microsoft to translate threads from teclast forum at www .bing.com/translator/ (sorry, I'm not allowed to post links yet)
Hendrickson said:
So the touch screen is going into sleep states very quickly? I noticed compared to the Onda v975w that it was much slower. I have the X98 3G air now and I have gotten use to it. But it would be nicer if it was how you pointed out.
I have disabled Allow the computer to turn off this device to save power, under power management on the Goodix Touch HID in device manager.
Click to expand...
Click to collapse
Yes, that it what I am claiming right now based on the information I know and what I have experienced at this point.
I attached the zip containing the datasheet of the goodix GT9271 touchscreen controller. (it's the touchscreen controller inside our tablet if I can believe the log)
The zip also contains an android app from goodix. You can select demo in the menu and then test the touchscreen in various ways. Give it a try
Disabling the "Allow the computer to turn off this device to save power" isn't going to work I think. It can only be done in the driver and I am not sure if it's even supported. It's standard USB stuff, but the GT9271 is connected via I2C. This is a Inter-IC Connection to other chips (IC's) of smartphones/tablets like touchscreen controllers, temperature sensors, accelerometers, gyroscopes etc.
I use it a lot in embedded software engineering and I2C is a very common connection in embedded applications. USB is very heavy for small systems, but I2C does require "special code" to get it up and running.
This will give you a better idea of what an I2C connection is capable of(example of RK3288):
http://www.arctablet.com/blog/wp-content/uploads/2014/02/RK3288-2-nowrmk.jpg
Sorry for all the information
Edit: I contacted Teclast and said I'd like to offer them help for free. Let's hope they accept my free help. (if they are smart...)
Someone can check if is it true?
https://twitter.com/srsroot/status/522464839294550017
petruccig said:
Useful Tools
Root : http://www.mgyun.com/vroot
Click to expand...
Click to collapse
This link doesn't work ...
malojk said:
This link doesn't work ...
Click to expand...
Click to collapse
i uploaded the latest chinese version of vROOT for you and the others :good:
vRoot
http://d-h.st/lWu
With the help of a member of another forum, probably very soon we will have a detailed explanation of the steps for change the Operating System in a better english than mine .
Stay tuned.
petruccig said:
With the help of a member of another forum, probably very soon we will have a detailed explanation of the steps for change the Operating System in a better english than mine .
Stay tuned.
Click to expand...
Click to collapse
Which forum if I may ask?
LVL91 said:
Which forum if I may ask?
Click to expand...
Click to collapse
I've set-up an easy to follow guide (in Greek) for Android -> Windows flashing.
The link is here and the translated (in English) link is here.
The procedure of flashing from Windows -> Android is here (English translation is here).
Feel free to copy it and post it here in order to help others.
I have a question about the screen, namely, whether at you vertically (then best seen) is the difference between the left and right sides of the LCD to the distance from the frame (the black space)? In my left is approximately 2 mm and 1 mm from the right. Such a little thing but unobtrusive I hope you understand what I mean.
Next case. Has anyone tried to install on Android Xposed? For me, after the installation of almost every application resets the tablet .
How can I boost speaker volume in this tablet?

Categories

Resources