Dunno if anyone actually uses 64 bit Vista around here, but if you do, I made a 64 bit version of the USB driver. It's unsigned, so before installing it you'll have to put Vista into test mode or it will refuse to load the driver:
1) Type "bcdedit /set testsigning on" at an admin command prompt
2) Reboot
3) Check to see if the desktop says "Test Mode" on the corners
(I'm not paying $300/yr for a kernel code signing certificate)
After that you should be able to install it like a normal driver. If adb seems to be freezing occassionally, try using adb_fixed.exe instead (don't forget to kill the adb server first).
Sweet! Thanks so much. I have XP 64 but it should work fine
dammit! a bit too late...i used vmware on my 64bit vista to create a virtual machine and 32 bit drivers..lol
but thank you for the drivers...will make my life easier
and welcome to xdadevs!
thank you, I like wise used a work around and dual booted xp and xp x64 so I could use the drivers but I will definilty thankfully switch back over to x64 now thanks much!
it works!
i'm working with original adb, no hangs at all.
aziwoqpd said:
Dunno if anyone actually uses 64 bit Vista around here, but if you do, I made a 64 bit version of the USB driver. It's unsigned, so before installing it you'll have to put Vista into test mode or it will refuse to load the driver:
1) Type "bcdedit /set testsigning on" at an admin command prompt
2) Reboot
3) Check to see if the desktop says "Test Mode" on the corners
(I'm not paying $300/yr for a kernel code signing certificate)
After that you should be able to install it like a normal driver. If adb seems to be freezing occassionally, try using adb_fixed.exe instead (don't forget to kill the adb server first).
Click to expand...
Click to collapse
Awesome! You should see if you can get the changes submitted to Google and then they might be inclined to release it with their signing cert.
Nice job aziwoqpd! I don't use vista myself, but lack of 64 bit vista drivers was a glaring problem.
Mods: this should probably be stickied
Thanks a lot, works like a charm
(Using Vista64 business edition)
Source ?
Hey, that's sounds really great ! Congratulations...
Can you provide the sources to your modifications ?
I'd like to be able to rebuild this myself. Yes, I'm a little anxious at the idea of installing a random driver from the Internet on my system ;-)
adb fixes?
aziwoqpd said:
If adb seems to be freezing occassionally, try using adb_fixed.exe instead (don't forget to kill the adb server first).
Click to expand...
Click to collapse
What's the issue with adb and what does your adb_fixed fixes? My adb seems to work fine, how do I know which one to use?
Could you give the source patch for adb, I like to see what I'm running too
adb_fixed just includes this patch: http://www.telesphoreo.org/pipermail/g1-hackers/2008-December/000191.html
I've attached a diff of the changes I made to the driver. Basically the only difference is that a pointer used for communication between the 32bit DLL and the 64bit driver needs to be explicitly defined as a 32bit pointer so that it's only 4 bytes wide. I also changed the version of Microsoft's WDF library to 1.7 since that's what I already had installed.
You'll also need the driver development kit (the WDK) from Microsoft to compile and link the thing. It's a (big!) free download, though. Just google for "WDK". It includes a command line utility called "build" that's not unlike make for userland code (you can try to use Google's Visual Studio files, but you'll have to hack them to work with x64 and they just end up calling build.exe anyway). For Vista you'll also have to test-sign the driver with a dummy certificate (the WDK help files have a walkthrough somewhere covering this). Or you could pay $300 a year to globalsign for a key! What a deal....
Hmm, it's not letting me attach the file. I'll just paste it:
Code:
diff -U4 -r ./common/android_usb_common_defines.h /mnt/sukiyaki/dev/andusb/common/android_usb_common_defines.h
--- ./common/android_usb_common_defines.h 2008-10-31 17:43:13.000000000 -0700
+++ /mnt/sukiyaki/dev/andusb/common/android_usb_common_defines.h 2008-11-14 14:18:51.439171200 -0800
@@ -132,8 +132,8 @@
ULONG transfer_size;
/// Pointer to the actual buffer for ADB_CTL_BULK_WRITE request. This field
/// is not used in ADB_CTL_BULK_READ request.
- void* write_buffer;
+ void* POINTER_32 write_buffer;
};
#endif // ANDROID_USB_COMMON_DEFINES_H__
diff -U4 -r ./driver/android_usb.inf /mnt/sukiyaki/dev/andusb/driver/android_usb.inf
--- ./driver/android_usb.inf 2008-10-31 17:43:13.000000000 -0700
+++ /mnt/sukiyaki/dev/andusb/driver/android_usb.inf 2008-11-14 15:54:04.556495700 -0800
@@ -10,9 +10,9 @@
Class=USB
ClassGuid={F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}
Provider=%GOOG%
DriverVer=date,1.0.0009.00000
-CatalogFile=androidusb.cat
+;CatalogFile=androidusb.cat
; ================= Class section =====================
[ClassInstall32]
@@ -27,9 +27,9 @@
; ================= Device section =====================
[Manufacturer]
-%MfgName%=Google,NTx86
+%MfgName%=Google,NTamd64
; For Win2K
[Google]
; For loopback testing
@@ -38,9 +38,9 @@
%USB\VID_0BB4&PID_0C01.DeviceDescRelease%=androidusb.Dev, USB\VID_0BB4&PID_0C01
%USB\VID_0BB4&PID_0C02&MI_01.DeviceDescRelease%=androidusb.Dev, USB\VID_0BB4&PID_0C02&MI_01
; For XP and later
-[Google.NTx86]
+[Google.NTamd64]
; For loopback testing
%USB\VID_18D1&PID_DDDD.DeviceDescTest%=androidusb.Dev, USB\VID_18D1&PID_DDDD
; HTC Dream
%USB\VID_0BB4&PID_0C01.DeviceDescRelease%=androidusb.Dev, USB\VID_0BB4&PID_0C01
@@ -85,21 +85,21 @@
AddReg=CoInstaller_AddReg
CopyFiles=CoInstaller_CopyFiles
[CoInstaller_CopyFiles]
-wdfcoinstaller01005.dll
+wdfcoinstaller01007.dll
[SourceDisksFiles]
-wdfcoinstaller01005.dll=1 ; make sure the number matches with SourceDisksNames
+wdfcoinstaller01007.dll=1 ; make sure the number matches with SourceDisksNames
[CoInstaller_AddReg]
-HKR,,CoInstallers32,0x00010000, "wdfcoinstaller01005.dll,WdfCoInstaller"
+HKR,,CoInstallers32,0x00010000, "wdfcoinstaller01007.dll,WdfCoInstaller"
[androidusb.Dev.NT.Wdf]
KmdfService = androidusb, androidusb_wdfsect
[androidusb_wdfsect]
-KmdfLibraryVersion = 1.5
+KmdfLibraryVersion = 1.7
;---------------------------------------------------------------;
[Strings]
THanks for the help....but how do I disable test mode after enabling it?
Thank you.
Thanks!
much appreciated.
remiks3 said:
THanks for the help....but how do I disable test mode after enabling it?
Click to expand...
Click to collapse
"bcdedit /set testsigning off" will turn testsigning back off, but you won't be able to use unsigned drivers any longer.
Thanks, I registered just so I could download that driver...
Just got my G1 flashed to the hacked RC and I wanted to play with some tethering on Vista X64...
This works perfectly on my XP 64 bit machine! Thank you!
I don't know if can help to sign the 64 bit driver , i try to post.
Test-signing the Micro Framework USB driver for installation on Vista 64-bit systems
The 64-bit version of Windows Vista requires all kernel mode drivers or services to pass a validation. In this follow-up of building USB driver in the Micro Framework, I’ll briefly outline the necessary steps to sign a driver that meets the requirement. These steps are intended for users working in a development environment. If you are planning to distribute drivers to third-parties, you should submit the driver for a WHQL signature or use a software publisher certificate. For more information about the bigger picture, review the kernel-mode signing guide on the WHQL website.
Let’s get on with the technical process. I’ve assumed you have a 64-bit Micro Framework USB driver built. If not, you’ll need to use the WDK and the WDK setup script, SETENV.BAT, to build the porting kit sample driver for an x64 (64-bit) Vista operating system. See the prior blog for detailed steps.
1. Open a command prompt with administrative privileges.
2. Run the command to enable test signed kernel mode drivers.
BCDEDIT /SET TESTSIGNING ON
3. Confirm the setting is correct by listing the Windows Boot Loader settings.
BCDEDIT /ENUM
4. Reboot to enable the new boot loader setting.
SHUTDOWN –t 60 –r
Notice the desktop background displays a new water mark after the reboot.
5. Open a command prompt and run the WDK SETENV.BAT command.
C:\apps\WDK\bin\SETENV.BAT C:\apps\WDK fre x64
6. Change directory to the porting kit root.
7. Set up the certificates folder.
MD Certificates
CD Certificates
8. Generate a self-signed certificate and private key.
Makecert –r –pe –ss MFCertificateStore –n “CN=MicroFrameworkOEM” OEMCertificate.cer
9. Open a MMC console and snap-in certificates for the current user. You will see the MFCertificateStore containing a private key and certificate. The certificate containing the public key is in a file called OEMCertificate.cer.
10. Add the certificate to the trusted publisher store.
Using the MMC certificate snap-in, right-click on the Trusted Publisher folder. Select import. Browse to the PK\Certificates\OEMCertificate.cer file.
11. Next, create a CAT file. First change directories to the Drivers\Vista64 folder. This folder contains the 64-bit USB driver under amd64 and the INF file.
CD BUILDOUTPUT\DRIVERS\VISTA64
12. Edit the INF file so that the version is 6.0.0.1 (or later as it matches the OS) and the driver date string is current.
13. Create a CAT file. The parameter to the “/driver” option must be the full path. Confirm the INF2CAT status output displays success with no warnings or errors.
INF2CAT /driver:C:\PK\Buildoutput\Drivers\Vista64\ /OS:Vista_x64
14. Sign the CAT file. The tool will use the the private key stored safely in the workstation certificate store.
SIGNTOOL sign /v /s MFCertificateStore /n MicroframeworkOEM /t http://timestamp.verisign.com/scripts.timestamp.dll MFUSB_PortingKitSample.cat
15. Verify the digital signature.
SIGNTOOL verify /kp /c MFUSB_PortingKitSample.cat amd64\MFUSB_PortingKitSample.sys
16. Plug in the Micro Framework device and install the newly signed driver. You’ll notice a pop-up that asks for permission to install the driver.
The steps above provide a process for signing 64-bit drivers that I use for Vista 64-bit testing. It is good to know the steps. But combined with the prior blog describing USB driver building, the labor to perform all these steps is too time-consuming. We’ll follow-up at a later time how to automate most if not all steps using the POWERSHELL toolset.
Jeff Simon
.Net Micro Framework
SDET - Porting Kit
Awesome, after 3 months finally got Windows to recognize. Thanks.
Vista 64 Development Mode Driver?
I'm runnin vista 64, and i can't get the "64 bit driver" that i found somewhere on here to work in Debug/Development Mode. anyone have one that they KNOW works?
Related
Updated on Aug-19-2012:
Download link: (4.0.4_r1.1)
http://www.vmlite.com/index.php?option=com_kunena&Itemid=158&func=view&catid=9&id=8838
we have built a virtual machine from the latest Android ICS 4.0.1 source code, Ice Cream Sandwich. You can download it free from our site.
It's created for virtualbox and vmlite, but can be converted to vmware format.
Unique features:
(1) mouse integration with host, no more mouse trapping
(2) shared folders
(3) auto mount sdcard
This is the full readme:
/////////// readme file ////////
VMLite Android 4.0.1 ICS virtual machine instructions
Copyright 2011 VMLite Corporation
1. Setup the virtual machine
(1) Using Winrar or 7zip to extract the zip file to a folder.
(2) Start VMLite Workstation 4.2 beta or VirtualBox v4, then go to menu Machine > Add, select Android-v4.vbox file to add the vm, you should be able to then
start the virtual machine.
(3) if (2) is not working for you, you can create a new virtual machine using Machine > New VM... menu, choose Linux 2.6 as guest os, add the two vdi files using
IDE controller to the vm. Android-4.vdi as Master, and sdcard.vdi as slave.
2. Using the virtual machine
(1) Drag the lock using the mouse to enter the Android screen.
(2) sdcard is now automatically mounted, if for some reason that it does not work well, you can do it manually as follows:
open a command prompt, and enter these commands: (adb.exe is included in the zip file)
adb connect localhost
adb shell
mount -t vfat /dev/block/sdb /mnt/sdcard
after the above, you should be able to use the sd card, which has 8G size.
If you can't connect using adb, and you are using NAT as network adapter, you need to run the following command:
VBoxManage modifyvm Android-v4 --natpf1 adb,tcp,*,5555,*,5555
If you are using bridged network adpater, you need to use the ip address of your vm to connect, e.g.
adb connect 192.168.1.10
If you have problems connecting to the vm, execute the following commands:
adb kill-server
adb shell
(3) Use shared folders to copy files between vm and host. This build includes shared folders additions, you can use the following commands to mount
the share.
adb kill-server
adb shell
mkdir /mnt/sdcard/c_drive
mount.vboxsf c_drive /mnt/sdcard/c_drive
ls /mnt/sdcard/c_drive
assume you have added a shared folder to the vm named as c_drive. You can ignore the error message from mount.vboxsf.
will continue to add more full screen, dynamic display resolution, emulations, such as GPS, Camera, remoting, etc.
We are determined to make it the best android vm and virtual phone you can even find.
We will also make it to boot a physical pc using the same virtual disk file via our unique VBoot technology, so same file can run as virtual as well as physical.
And what would be your website?
google "android v4 vm download", as I still can't post external links here.
refer to readme inside .7z for more instructions
100k download over last week after release.
I found the link:
http://www.vmlite.com/vmlite/Android-v4.7z
Some pics:
http://www.sevenforums.com/attachme...oid-v4-vm-available-download-android-v4-1.png
http://www.sevenforums.com/attachme...oid-v4-vm-available-download-android-v4-2.png
I will try it soon.
having issues with the mouse.... host mouse seems to be 2-3cm higher then ics, cant even reach the menu button
huisinro said:
google "android v4 vm download", as I still can't post external links here.
refer to readme inside .7z for more instructions
100k download over last week after release.
Click to expand...
Click to collapse
let me have a try!
yes, it's a bug we are fixing. the mouse moves inside 800x600 while display is 1024x768.
if you see this, try to reboot the vm.
if still like this, you can then disable mouse integration from menu.
elspanish88 said:
having issues with the mouse.... host mouse seems to be 2-3cm higher then ics, cant even reach the menu button
Click to expand...
Click to collapse
Android 4.0.1 ICS questions
Hi,
I do hope someone can assist me. I downloaded the .7z file, extracted and mounted the .vbox in VirtualBox v4.1.8. All good, it booted up perfectly but problems that arose are as follows:
1: no matter WHAT configuration I choose for networking I simply cannot get the VM to browse any webpages or even to see that there is a network connection. I do see briefly in the bootup that eth0 is loading though, so not sure where to look now as I cannot use ALT-F1 to get to a root shell to do a netcfg to diagnose. When booting the network indicator on the status bar of VBox shows activity, also once it is up and running but no internet access whatsoever.
2: I have noticed I cannot change the time, it defaults to whatever it was when it booted up, that is if the time says 13:20 when it booted up, I cannot change the hour to anything else. if I click set, it just reverts back to 13: or whichever hour digit was there before. Also, clock does not seem to run in this VM. Both the desktop clock and the digital clock on the status bar of Android stay at whatever time it was when it booted up, say 14:20. that is where it will stay, it never updates/moves/keeps time. In the settings page, it seems to be keeping time however.
If there is anyone who can assist me with these issues I would be most grateful.
Thanks in advance,
Mark.
i get an error at boot...
Code:
init: Timed out waiting for /dev/.cp;dboot_done
Kernel panic - not syncing : Attempted to kill init!
atkbd.c: Spurious ACK is isa 0060/serio0.Some programmight be trying to access hardware directly.
Is there any way to install more Apps?
Have send me one per mail but no way to install...
It works, but internet is only in the browser. And it still says that wifi isn't working.
By the way, I'm missing the market thats available in other android4.0 versions for X86:
http://code.google.com/p/android-x86/downloads/list
But these versions don't have internet at all, unless your doing some tricks that are explained here:
http://nil.uniza.sk/linux-howto/android-40-virtualbox-networking-issues
But keep on the good working
This is great! The only problem i am having is there is no Wifi avaiable. Also, if i may ask, how can i download apps to it? I have the apk files of the apps so i dont need a market either thanks!
sgtfoo said:
i get an error at boot...
Code:
init: Timed out waiting for /dev/.cp;dboot_done
Kernel panic - not syncing : Attempted to kill init!
atkbd.c: Spurious ACK is isa 0060/serio0.Some programmight be trying to access hardware directly.
Click to expand...
Click to collapse
Have you had any luck figuring out what was causing this? I'm having the same problem. I've tried different chipset, processor, and acceleration settings. None of which have worked.
Mouse Integration Fix!
elspanish88 said:
having issues with the mouse.... host mouse seems to be 2-3cm higher then ics, cant even reach the menu button
Click to expand...
Click to collapse
Hello, elspanish88! Two ways to fix this problem.
1. Double click on VirtualBOX and start your vm, then when you are logged on to Android, click on machine, at the top left corner, then click Disable Mouse Integration. Then you can move freely, around the screen.
2. The easy easy easy way! Type (Right Ctrl+I) .. there you have it!
Cheers,
ConnorTheHelpa!
This vm is updated to 4.0.4_r1 version, available here:
http://www.vmlite.com/index.php?option=com_kunena&Itemid=158&func=view&catid=9&id=8838
Our vmlite vm is very popular, more than 1 million downloads over last few months.
The latest Jelly Bean version, v4.1.1_r4 is being build, will release a vm when ready.
huisinro said:
This vm is updated to 4.0.4_r1 version, available here:
http://www.vmlite.com/index.php?option=com_kunena&Itemid=158&func=view&catid=9&id=8838
Our vmlite vm is very popular, more than 1 million downloads over last few months.
The latest Jelly Bean version, v4.1.1_r4 is being build, will release a vm when ready.
Click to expand...
Click to collapse
I have a noob dbt. Whts special in it than the original android avds??
send from Gods Own Country........
emulators are too slow, not for real work.
vm is 10x faster.
this is awesome, now i can have a real test environment rather than a test phone! kudos!
This is a guide to setting up Windows Kits on Windows 8.1 RT. While it itself is a set of debugging & testing tools that Microsoft publishes officially for Windows 8.1 RT, I haven't looked at them in detail and possibly there are tools in it that are useful for you.
Mandatory Warning
This is a set of development tools and should not be toyed around with if you don't know what you are doing.
Disclaimer
These tools were provided by Microsoft Corporation and this guide only points you out to the tools I've found.
There is no warranty, express or implied for these tools, either from me or from Microsoft.
Includes
ARM Kits Policy (Needed to run development binaries on Windows 8.1 RT) Info here (MSDN)]
ARM Debugging Tools (WinDbg, Gflags) Download here (Source)
ARM App Certification Kit Info and Download here
ARM Windows Performance Toolkit (included with above)
Guide
Make sure you are sane enough and you need to install these.
Download the ARM Windows App Certification Kit (third in the list above) and install.
Go to C:\Program Files\Windows Kits\8.1\bin\arm\SecureBoot. Open InstallKitsPolicy.cmd with an Admin CMD Prompt.
This will install the Kits Policy (other tools will not work without this). After rebooting, use Volume Down to select "Install" in the black screen that appears, and press the Windows button on your RT Device to proceed.
After it boots, try to run C:\Program Files\Windows Kits\8.1\bin\arm\dxcapsviewer.exe and see if it runs. If it does, your Kits Policy is now installed. Download the ARM Debugging Tools from above.
Install it. It'll also install to C:\Program Files\Windows Kits\8.1. The Debugger is located at \Debuggers, other useful binaries are around in \bin\arm. They also install Start Menu entries.
Notes
If the Kits Policy fails to install (black screen does not show up on next boot), try running the commands manually in an elevated command prompt. It failed to work for me in the first few tries, maybe due to a repeated command in the .bat file provided by MS. Running it manually should allow you to ignore that error.
jimmielin said:
ARM Debugging Tools (WinDbg, Gflags) Download here (Source)
Click to expand...
Click to collapse
Thanks for the info's. Any chance someone can mirror this, MEGA does not work for readers with certain browsers and security settings.
http://www.datafilehost.com/
** Version 4.7 Updated October 2016 - Supports Android 4.0-7.0 **
SUMMARY:
Allows WhatsApp users to extract their cipher key and databases on non-rooted Android devices.
UPDATE: This tool was last updated on October 12th 2016. and confirmed working on Android 4.0-7.0 using WhatsApp version v2.16.304 (latest available).
IMPORTANT: If you wish to extract media files or WhatsApp databases from Google Drive backups then you need: WhatsApp Google Drive Extractor instead.
TUTORIAL:
BRANCH UPDATES:
v4.0 - Fixed issues with Android API 14-17 (4.0-4.2 Jelly Bean).
v4.1 - Added support for Android API 23 (6.0-6.0.1 Marshmallow).
v4.2 - Added support for specifying adb backup passwords.
v4.3 - Added PowerShell version as optional alternative to bat version.
v4.4 - Changed primary mirror for legacy apk.
v4.5 - Fixed issue pushing cipher key to emulated storage.
v4.6 - Updated primary mirror for legacy apk (again).
v4.7 - Added new sanity checks and support for Android API 24 (7.0 Nougat).
PREREQUISITES:
O/S: Windows Vista, Windows 7, Windows 8, Windows 10, Mac OS X or Linux
Java - If not installed: Download Java
ADB (Android Debug Bridge) Drivers
USB Debugging* must be enabled on the target device. Settings -> Developer Options -> (Debugging) USB debugging
Android device with Android 4.0 or higher. I.E. Ice Cream Sandwich, Jelly Bean, KitKat, Lollipop, Marshmallow or Nougat.
*= If you cannot find Developer Options then please go to: Settings -> About phone/device and tap the Build number multiple times.
INSTRUCTIONS:
Extract WhatsApp-Key-DB-Extractor-master.zip maintaining the directory structure.
Click on WhatsAppKeyDBExtract.bat (Windows) or WhatsAppKeyDBExtract.sh (Mac OS X / Linux).
Connect your device via USB, unlock your screen and wait for Full backup to appear.
Enter your backup password or leave blank (if none set) and tap on Back up my data.
Confirm backup password in your command console and then check the "extracted" folder.
TROUBLESHOOTING:
If you have never used USB Debugging before, you may also need to verify the fingerprint.
If you have set a default backup password in your Android settings, then this MUST be the
backup password that you provide when prompted to backup your data. Else it WILL fail!
Linux and Mac OS X users may need to set the script permissions as executable. Depending on the
adb permissions, you may also need to sudo ./WhatsAppKeyDBExtract.sh from your command console.
If you're having issues with WhatsAppKeyDBExtract.bat then right click WhatsAppKeyDBExtract.ps1
and select Run with PowerShell. You may have to enter "y" at first run for script execution policy.
If you get an error saying "AES encryption not allowed" then you need to update your Oracle Java
Cryptography Extension (JCE) to Unlimited Strength Jurisdiction Policy Files.
DOWNLOAD: WhatsApp-Key-DB-Extractor-master.zip
AUTHOR: TripCode
THANKS: dragomerlin for Android Backup Extractor and Abinash Bishoyi for being cool.
alternatives
Yes, this is a normal backup method. There are automatic tools that do the same without using PC, just on device side.
Apart from normal ADB method, you could use ECLIPSE for that, using the memory module, you could transfer files from and in.
If you have physical access to the device, there are many solutions.
regards.
droopyar said:
Yes, this is a normal backup method. There are automatic tools that do the same without using PC, just on device side.
Apart from normal ADB method, you could use ECLIPSE for that, using the memory module, you could transfer files from and in.
If you have physical access to the device, there are many solutions.
regards.
Click to expand...
Click to collapse
The only way to access private application files (such as a WhatsApp's cipher key) without root is the ADB method. You can backup some files on the device without a PC (APK's etc...), but there is currently no way to access private files and folders. All the "My Big Fat Backup" style apps and tools will either require root or ADB. Eclipse also utilizes ADB. Basically, device side backups of application data require root. There are no other alternatives to this. If there was, then Android would be too infeasible and insecure as a viable operating system. Physical access translates into only two solutions. 1.) The ability to root and 2.) The ability to utilize ADB (Eclipse, Bats, Exe's doing nothing more than calling a simple command line). Of course if you are aware of a 3rd method (disregarding the user interface) and is not based on root or ADB then please feel free to share.
Thanks for this tool!
I've just tried to use it, but it installs the java constantly (while java is properly installed on computer as other applications uses it without any problem )
By any chance, do you have any idea how to pass that?
Thanks!!
Mia
PS I got JDK installed and still not working
MiaNet said:
I've just tried to use it, but it installs the java constantly (while java is properly installed on computer as other applications uses it without any problem )
By any chance, do you have any idea how to pass that?
Click to expand...
Click to collapse
The bat file automatically checks for the presence of java.exe on your system. If it's not found then it starts the install. It would appear that for some reason it's not finding Java and hence why you're stuck in this loop. Please find attached a bat file without the Java check. Just put it in the same folder as the original and run this one instead. Let me know how you get on. Java also needs to be callable from the command line. To check this is working you should click on Run... within Windows, type cmd, click OK and type "java -version" (without quotes) and press Enter. This will confirm java is in the command path and print out your JRE build number. I have also updated the release in the OP and removed the Java check, as I have had a couple of similar reports of the loop issue.
Thanks again.
still showing this message attached
TripCode said:
The bat file automatically checks for the presence of java.exe on your system. If it's not found then it starts the install. It would appear that for some reason it's not finding Java and hence why you're stuck in this loop. Please find attached a bat file without the Java check. Just put it in the same folder as the original and run this one instead. Let me know how you get on. Java also needs to be callable from the command line. To check this is working you should click on Run... within Windows, type cmd, click OK and type "java -version" (without quotes) and press Enter. This will confirm java is in the command path and print out your JRE build number. I have also updated the release in the OP and removed the Java check, as I have had a couple of similar reports of the loop issue.
Thanks again.
Click to expand...
Click to collapse
Still showing the attached message
mesho_alaa said:
Still showing the attached message
Click to expand...
Click to collapse
This sounds to me like you need to update your PATH Environment variable with the directory in which java is installed.
Open up a DOS window and type: "where java" (without quotes) to determine possible locations.
If it's located in: "C:\Windows\System32" then the following code should suffice:
Code:
set PATH=%PATH%;C:\Windows\System32
If it's located in: "C:\Program Files\Java\jre7\bin" then:
Code:
set PATH=%PATH%;C:\Program Files\Java\jre7\bin
The above needs to be added to the bat script BEFORE Java is called. You can edit the bat script by opening it with Notepad.
Alternatively, you could permanently update the PATH Environment (probably a better method).
To do this you would: Right click on "Computer" or "My Computer", within Windows Explorer, choose "Properties", click on the "Advanced system settings" and/or the "Advanced" tab, then click on the "Environment Variables" button. Select the "PATH" line, click the "Edit" button, and add the relevant directory to the end of any text that exists for PATH, prefixing the java path with a ";" (semicolon) if this line already contains other string paths. If PATH does not exist then you will need to add it. Sorry this paragraph is a little double-dutch (trying to cater for multiple versions of Windows).
Many thanks! I'll test when home and let you know.
Just to let know, the path command do not fix the prior version with Java check as I first thought this might be the problem.
Thanks!
Mia
Could even be use with ADB from phone to phone? without using the pc? Or I must install the app on the phone and do it offline?
I have find my way! Re-installed Java, manually clicked on java.exe stored in Java folder in Program files (or Program files (x86) ) I've clicked on Javacpl as well and enabled all options, not sure if this is necessary though.
I've then rerun the program without Java check (the Java check one is bugging now) and was able to do the back up.
Thanks!!
Best regards,
Melanie
Cannot tap button
Hi! i've done all the previous steps, but when i unlock the phone, to confirm the backup, i cant tap on "back up my data", it doesnt even grey at hover, just like the button wasn't there...
I can choose not to backup, that button works perfectly, and write the password too, i've tried all the screen, but nothing happends, so i can't backup the phone...
Does anyone think how to solve that? Thanks!
Permission denied
Hi, I followed all instructions and I generated this error.
I would appreciate your help.
Error
mesho_alaa said:
Still showing the attached message
Click to expand...
Click to collapse
I, too am showing the same error.
Curwens said:
Hi! i've done all the previous steps, but when i unlock the phone, to confirm the backup, i cant tap on "back up my data", it doesnt even grey at hover, just like the button wasn't there...
I can choose not to backup, that button works perfectly, and write the password too, i've tried all the screen, but nothing happends, so i can't backup the phone...
Does anyone think how to solve that? Thanks!
Click to expand...
Click to collapse
Try rebooting the device and trying again. If it is still greyed out, the backup feature maybe disabled on the device. Some manufacturers / service providers have specifically disabled usb backups.
kharloz_jc said:
Hi, I followed all instructions and I generated this error.
I would appreciate your help.
Click to expand...
Click to collapse
cardinalaa said:
I, too am showing the same error.
Click to expand...
Click to collapse
It would appear that the key was extracted, but the "copy" wasn't pushed to the sdcard. KitKat? You don't need a copy of the key on your sdcard unless you want to use a supported app. As the key was extracted successfully, you could attempt to copy it by other means.
TripCode said:
This sounds to me like you need to update your PATH Environment variable with the directory in which java is installed.
Open up a DOS window and type: "where java" (without quotes) to determine possible locations.
If it's located in: "C:\Windows\System32" then the following code should suffice:
Code:
set PATH=%PATH%;C:\Windows\System32
If it's located in: "C:\Program Files\Java\jre7\bin" then:
Code:
set PATH=%PATH%;C:\Program Files\Java\jre7\bin
The above needs to be added to the bat script BEFORE Java is called. You can edit the bat script by opening it with Notepad.
Alternatively, you could permanently update the PATH Environment (probably a better method).
To do this you would: Right click on "Computer" or "My Computer", within Windows Explorer, choose "Properties", click on the "Advanced system settings" and/or the "Advanced" tab, then click on the "Environment Variables" button. Select the "PATH" line, click the "Edit" button, and add the relevant directory to the end of any text that exists for PATH, prefixing the java path with a ";" (semicolon) if this line already contains other string paths. If PATH does not exist then you will need to add it. Sorry this paragraph is a little double-dutch (trying to cater for multiple versions of Windows).
Click to expand...
Click to collapse
Hi, I am receiving the "Cannot find the path specified" error. I have tried both changing the script and also the other method, in environment variables. I am curious if this has anything to do with the fact that its an ATT phone (since no one can even root it yet)? No other apps can access my phone, either. I have USB debugging enabled and all prerequisite programs installed. Tried on 2 computers, win7 and win 8.1
I wonder if i it is an error on my part..?
TripCode said:
Try rebooting the device and trying again. If it is still greyed out, the backup feature maybe disabled on the device. Some manufacturers / service providers have specifically disabled usb backups.
It would appear that the key was extracted, but the "copy" wasn't pushed to the sdcard. KitKat? You don't need a copy of the key on your sdcard unless you want to use a supported app. As the key was extracted successfully, you could attempt to copy it by other means.
Click to expand...
Click to collapse
I have reviewed the "Extract" folder and there was the key. I have managed to decrypt it.
Thanks for the help and the tool!
PD: sorry for my bad English, I use translator is haha.
Nothing happens
Hi, first, thanks for this iniciative. A lot of people would apreciate this
I think I did everything as u said, but when I open the WhatsAppKeyExtract,bat and then conect my phone in debuggin mode to PC, nothing happens. Ive waited for 10 minutes and.. nothing happens. Keep showing the initial message: "Please connect your Android device..." and in my phone nothing happens too. Just show a messagem at the upper tab saying: "USB debbugin conected".
Theres any kind of setting to do futher in the debbug options?
Thanks
Update: I had do install de universal adb driver for my phone, and now it starts the download, but now im having problem with java... the messagem says "'java' isnt a recognizable command". I tried all solutions in this post and nothing.. I need heeeelp!
Solution to path problem
Is working perfect. For someone else that can happen the same thing as me. I have to fix something (i am spanish) about:
java is not recognized as an internal or external command, operable program or batch file
Here is the solution:
java .com/en/download/help/path.xml
Or here:
1. Right-Click My Computer and select Properties
2. Then Click The Advanced Tab
3. Then Click Environment Variables
4. Select Path In The Bottom Box and Click Edit
5. Find Where You installed Java (E.g "C:\Program Files\Java\bin)
Its different on each computer
6. Make Sure to add a semicolon after the word bin in the path to seperate it from the other important paths
7. If this doesnt work then you may have to reinstall Java and Try Again
Setting Path on Windows
For Windows XP:
1. Start -> Control Panel -> System -> Advanced
2. Click on Environment Variables, under System Variables, find PATH, and click on it.
3. In the Edit windows, modify PATH by adding the location of the class to the value for PATH. If you do not have the item PATH, you may select to add a new variable and add PATH as the name and the location of the class as the value.
4. Close the window.
5. Reopen Command prompt window, and run your java code.
https://www.dropbox.com/s/nm1goi6m0oob15u/Screenshot 2014-06-15 22.25.27.png
I am getting this error.
using java run time 7 update 60
any ideas?
Thanks!
tzuyang said:
https://www.dropbox.com/s/nm1goi6m0oob15u/Screenshot 2014-06-15 22.25.27.png
I am getting this error.
using java run time 7 update 60
any ideas?
Thanks!
Click to expand...
Click to collapse
Have seen this error before (not related to bat file). You may need to revert to an earlier Java version.
The drivers that I downloaded from the Alcatel website didn't have the ids for the OneTouch Pixi 7 (9006w), so I modified the Google USB Drivers.
I edited "android_winusb.inf", removing all entries for Google devices and added our device.
Code:
[Google.NTx86]
;Alcatel 9006w
%SingleAdbInterface% = USB_Install, USB\VID_1BBB&PID_AF2B&REV_0225&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1BBB&PID_AF2B&MI_01
[Google.NTamd64]
;Alcatel 9006w
%SingleAdbInterface% = USB_Install, USB\VID_1BBB&PID_AF2B&REV_0225&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1BBB&PID_AF2B&MI_01
I also updated the string section at the end of the file.
Code:
[Strings]
ProviderName = "ALCATEL"
SingleAdbInterface = "Android ADB Interface (ALCATEL 9006w)"
CompositeAdbInterface = "Android Composite ADB Interface (ALCATEL 9006w)"
SingleBootLoaderInterface = "Android Bootloader Interface (ALCATEL 9006w)"
WinUSB_SvcDesc = "Android USB Driver"
DISK_NAME = "Android WinUsb installation disk"
ClassName = "Android Devices"
Download here.
Double-click "install.cmd" to start the driver installer.
I was able to get this to work in Windows 7 64-bit and Windows 10-64-bit. I have not tested 32-bit or Windows 8.
I had to disable driver signature verification for this to work in Windows 10, I would assume this would also work for Windows 8. Feel free to test and let me know.
I have also included adb and fastboot in the "platform-tools" folder in case anyone doesn't already have them installed.
Error message "Windows cannot find 'adb-interface-driver/dpinst-amd64.exe'. Make sure you typed the file name correctly, and then try again." when I double-click "install.cmd" to start the driver installer. I am running on Windows 10 and have disabled driver signature verification. Any help would be greatly appreciated.
Muxintorq said:
Error message "Windows cannot find 'adb-interface-driver/dpinst-amd64.exe'. Make sure you typed the file name correctly, and then try again." when I double-click "install.cmd" to start the driver installer. I am running on Windows 10 and have disabled driver signature verification. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Make sure you ARE NOT running it "As Administrator", and that you are, in fact running an AMD 64 bit CPU and Version of Windows.
Also, some folder locations are protected, and the location you view from the API (What you see/use while using the computer) is not, in fact, the location it says it is... it's in a temporary, protected location in case you change/delete/install something that damages windows. That way, it can prevent the change to the actual operating machine files themselves, and keep users & 3rd party software from damaging Windows or the computer itself. They started that in Vista.
OriginalHardwyre said:
Make sure you ARE NOT running it "As Administrator", and that you are, in fact running an AMD 64 bit CPU and Version of Windows.
Also, some folder locations are protected, and the location you view from the API (What you see/use while using the computer) is not, in fact, the location it says it is... it's in a temporary, protected location in case you change/delete/install something that damages windows. That way, it can prevent the change to the actual operating machine files themselves, and keep users & 3rd party software from damaging Windows or the computer itself. They started that in Vista.
Click to expand...
Click to collapse
Is it required that you have to have a AMD 64 bit CPU or a regular Intel 64 bit CPU will work on this also?
Thanks.
Amd64 basically just means 64-bit, for Intel or amd.
I have an rca tablet I can not get any drivers to work to get to replace/update the firmware and I was wanting to ask if anyone has found anything that works.
I have tried mediatek, rca and all other drivers I can find and nothing seems to work on windows 10 64.
Thank You
DL here:
Download Android USB drivers for RCA - HEXAMOB
Download Android USB drivers for RCA. Here you can find available USB Drivers for your Android phone and tablet. In this updated section, we try to help you find all types of downloads, links and help to connect your Android device to your PC.
hexamob.com
xXx yYy said:
DL here:
Download Android USB drivers for RCA - HEXAMOB
Download Android USB drivers for RCA. Here you can find available USB Drivers for your Android phone and tablet. In this updated section, we try to help you find all types of downloads, links and help to connect your Android device to your PC.
hexamob.com
Click to expand...
Click to collapse
Thank You will give a try
I have a Windows 7 64 bit system and I am trying to find drivers to access an rca rct6703w13
I have tried every driver I can find and nothing seems to work does anyone know something that will work?
I would be very grateful if anyone could help?
Thank You
Oh boy, I still remember this pain trying to find and use such drivers on Windoze:
- try another port
- try another cable
- try this driver or that one
- try doing a rain dance with 3 days old undies on your head, and turn only clock wise, unless it's full moon, then turn counter clockwise but stop briefly after ever two and a half turns
Maybe, as workaround, you could boot from a linux CD and try your approach from there.
Whenever I flash from my debian, it works: If "fastboot devices" still doesn't show anything then usually I have forgotten to plugin the cable
By using my "Yet Another Universal ADB Driver" Package (see the link in my signature) one can remove all the old adb drivers if that is the issue, but this case seems to be more interesting...
On win10 it seems that the adb is embedded to the winusb driver the same or similar way (registry wise) that my package is using. Now that I have tested, the behavior is similar with my devices. When using file transfer connection the adb is not recognized. With others, charging, photo, midi the abd works fine. To make adb work with file transfer one have to install the correct driver. In this case google's general driver could be okay, one match for vendor and product ids in it ...
https://dl.google.com/android/repository/usb_driver_r13-windows.zip
What I tested using virtual win7 64bit, it seems to behave the same way... which is a bit weird as I've tested it with my driver package. Worked okay then I think. The Android device used has changed since though.. It worked on win10 back then too.. the change has to have happened later.. or I didn't use file transfer..
@steadfasterX 's maid or salt or whatever it's called nowadays might be usable in this case. It's a Linux having SP flash tool etc. available..
edit: tested and it turned out that the updated phone is the problem... using another phone my driver package worked as expected..
@resxwni01
1. Don't confuse USB-driver and ADB-driver: the USB-driver since ever is by default part of any OS, so also of Windows OS. The ADB-driver is an extra protocol what allows you to communicate with a phone's Android ecosystem via an USB-connection.
2. Latest generic ADB-driver ( correct: ADB client ) got released August 2022 and is officially versioned 33.0.3.
3. AFAIK a 64-bit version of ADB-driver doesn't exist.
With regards to install this ADB-driver on a Windows 7,8.1,10,11 PC:
It's NO USB-driver installer - as introduced above by @CXZa - needed what unnecessarily bloats the Windows registry with crap.
You
1. simply create on any mounted drive of Windows PC a folder named "ADB",
2. extract there to the 3 files what are in the attached ZIP file,
3. add path of created folder "ADB" to Windows environment variable PATH, thus ADB-driver is systemwide accessible -
how to is described here
How to Set the Path and Environment Variables in Windows
Information on how to set the path and environment variables in Windows 2000, Windows XP, Windows Vista, and Windows 7.
www.computerhope.com
@jwoegerbauer , you're funny guy...