Here's how:
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
This is for windows vista/7 probably works with xp.
Install the drivers attached once in Test Mode.
Hope this helps!
Related
From personal experience, I found out that in windows vista and 7, you can't flash HardSPL and dead device. So I put this together from the dead trinityguides.info and other post in this forum. So follow this to the letter.
1a. If your p3600i is stuck in the HTC screen, put it in boot loader and plug it in.
1b. If its stuck in boot loader, just plug it in.
2. You need to download and extract the Windows Xp drivers to a memorable location (e.g. the desktop). You can download them here:
* Vista x32 drivers
* Vista x64 drivers
the 64-bit drivers are unsigned, so if you are using Vista x64 go to the bottom of this post to disable driver signing and then follow the rest of this guide
Run 'Windows Mobile Device Center', and click 'Connection Settings'.
Uncheck the 'Allow USB Connections' box, and select 'OK'.
Run 'Services' by opening the start menu and typing 'Services'
ensure the 'Windows Mobile-based connectivity' and Windows Mobile 2003-based connectivity' services are started. If they are not, click the service name and press the 'start' button on the top bar.
Image
Load 'Device Manager' by opening the Start menu and typing 'Device Manager'.
Expand the 'Mobile devices' section and right click the 'HTC USB Sync'
Select 'Update Driver Software'.
Click 'Browse my computer for driver software'.
Click 'Let me pick from a list of device drivers on my computer'.
Click 'Have Disk' or "Browse".
Click 'Browse', and browse to the location where you extracted the ZIP file in the first step.
Vista x32 users double click 'wceusbsh.inf', Vista x64 users double click 'wceusbshx64.inf'
Select 'HTC USB Sync' from the list, and click 'Next'.
Wait while your driver is installed.
Run 'Task Manager' by clicking the Start Orb and typing 'taskmgr'. Then find the 'WMDC.EXE' item in the processes section, and click 'End Process'.
In 'Windows Mobile Device Center, re-enable the 'Allow USB connections' .
3a.If your device is bricked, download stock rom from htc.com NOT FROM A MIRROR IN RAPIDSHARE/MEDIAFIRE/4SHARED/MEGAUPLOAD etc... and flash it with no compatibility mode.
3b.To HardSPL: Run RUU and flash normally, but when you get to the JumpSPL bootloader, it will erroe 260. LOOK AT THE SCREEN ON YOUR PHONE, YOU MIGHT HAVE SECURITY PERMISSIONS AND NEED TO MANUALLY ALLOW THE PROGRAMS TO RUN.
KEEP YOUR PHONE ON THE BOOTLOADER SCREEN[/B][/B][/B], and unplug it from your computer. Exit the HardSPL program, RUN IT AGAIN, PLUG THE PHONE BACK IN, wait for HTC USB Sync to install and FLASH THE PHONE AGAIN WITH HARDSPL.
To install driver in vista/7 x64
1. Start -> type gpedit.msc right click in the result gpedit.msc and select run as administrator. Select yes in the UAC prompt if you keep it enabled.
2. Navigate to User Configuration -> Administrative Templates -> System -> Driver Installation.
3. Enable the "Code signing for drivers" and then choose "Ignore".
4. Close gpedit.msc.
Hope this guide help you out there.
Hello all, you might've seen my thread down below, about having painstaking errors with getting ADB to work with my Windows 8.
PLEASE READ!!!
First and foremost, IF you have plugged in your Fire HD into your Win8 pc already, please go to device management, and see what it recognizes the Kindle as. If it recognizes as "Android ADB", please right click on it, and remove the drivers (With the Kindle unplugged). It MUST be recognized as a "portable media player" or something along those lines. If it's recognized as the "Android ADB", then it will have driver conflicts with my steps below, and nothing will happen. Took me 4 hours to figure out the issue.
IF you haven't plugged in the Kindle before, then PLEASE install the ADB and Android SDK first. Then once you plug the Kindle in, it should be recognized as "Android Composite ADB". IF not, it prolly will set at "Daemon started".
First of all, you gotta do the below method, to remove the darn security, since the ADB is unsigned drivers.
Click on Command Prompt (Admin)
At the blinking cursor type: bcdedit -set TESTSIGNING OFF
Then once done, reboot, you should see "Test Mode" watermark on the lower-left side of the screen. Install Android SDK, all you gotta install is the Google USB Driver, and then install the Amazon ADB drivers NOT Google, or any other drivers. Download those here. Once downloaded, right-click, and "run as admin". They should install without ANY error.
Once done, reboot, and go into your Fire HD, in Settings>Security>Enable ADB, and then root with your program of choice. I used "Root with restore by Bin4ry", it worked PERFECT for my latest version Fire HD 7". Make sure to click "restore" on the Fire HD, when it pops up, then it'll reboot, and be done in approx 2 mins.
Now go back into Command Prompt (Admin), and enter the below data to re-enable the security for unsigned drivers.
Once at CMD, enter bcdedit -set TESTSIGNING ON
Now reboot, and your PC should be back like normal, with the exception of a rooted Kindle. :laugh:
Basically I found out that Windows 8 likes to install it's own version of ADB, which messes things up terribly. Because my ADB drivers from Amazon wouldn't do crap, and once I deleted the drivers that Win8 installed, then it worked PERFECT with the Amazon ADB drivers.
Please "thank me" if I've helped. If you need further help, please ask. Sorry I'm no programmer, only a PC addict.
A few things:
1: Nice guide
2: Forgot something
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
and to disable
bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF
3: Search the forums for other guides first
http://forum.xda-developers.com/showthread.php?t=2093296
Hi, my device (tate) cannot connect to any of my computers in adb or fastboot modes, rendering me unable to transfer any files onto my device. However, I am able to perfectly boot into TWRP recovery. The ROM I previously flashed didn't work, and I had already factory reset the device without making a backup. How can I now transfer a working ROM given my problems in adb?
OS: Windows 8 x64 (failed to install the KFHD adb drivers)
Upon command 'adb devices' or 'adb usb': 'no device found'
Upon command 'fastboot -i 0x1949 getvar product': nothing happens
You need to install the drivers while in twrp/fastboot. I would recommend just using adb to push the ROM onto the sdcard from twrp. You will need to fix your drivers first though, to do that you need to disable windows driver signature enforcement, look it up on Google. Then download the drivers in my signature and update the drivers for the device with a triangle in the device manager and point then to where you extracted the drivers. Then try adb again while in twrp.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Disable device driver signature enforcement.
Both must be done from the administrator profile to work right.
Both of these are for Windows 7 X64 users.
Windows 7 X32 and earlier version users do not have this issue.
A.
1. Reboot and on start up press F8 a couple times.
2. Scroll down to "Disable Driver Signature Enforcement."
Note: This must be done on every bootup you want to install something not MS signed.
B. For a more permanent solution.
1. First go and uninstall the driver (delete driver) you want to replace and then restart your computer.
2. Now go to the start menu and type cmd.
3. Right click on "cmd" and open a command prompt with elevated privileges (run as administrator.)
4. Now copy these in the command prompt one at a time hitting enter after each one.
bcdedit /set testsigning on
bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS
4. Now install the driver you want.
5. Restart the computer.
6. Profit.
Note: If you do this right, you will see "Test Mode Windows 7 Build 7601" (or something comparable) in the lower right corner of your screen. This means that drivers not signed by MS can be installed without getting the Windows has installed the best driver already bit.
If you opt to take your computer out of test mode, the drivers will more than likely be replaced by MS drivers next time. Following steps 1, 2 and 3 in part B of tutorial enter these commands
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF
Since I don't have Windows 8 to do a personal tutorial, I'll just link to a good tutorial for that http://www.fotoclubinc.com/blog/how...on-of-windows-7-printer-drivers-on-windows-8/
---------- Post added at 10:18 PM ---------- Previous post was at 09:55 PM ----------
chemicalrubber said:
Hi, my device (tate) cannot connect to any of my computers in adb or fastboot modes, rendering me unable to transfer any files onto my device. However, I am able to perfectly boot into TWRP recovery. The ROM I previously flashed didn't work, and I had already factory reset the device without making a backup. How can I now transfer a working ROM given my problems in adb?
OS: Windows 8 x64 (failed to install the KFHD adb drivers)
Upon command 'adb devices' or 'adb usb': 'no device found'
Upon command 'fastboot -i 0x1949 getvar product': nothing happens
Click to expand...
Click to collapse
You need to push a ROM onto TWRP using this tutorial http://forum.xda-developers.com/showthread.php?t=2459498 Also disable drivers via my post above this post. Lastly, make sure to use Hashcodes crackflasher mirro as TWRP is still messed up making goo.img zip file downloads a mere shell that fail to flash. Make sure to have the most up to date TWRP as well http://forum.xda-developers.com/showthread.php?t=2128848
Thanks stunts and Linearequation! Disabling driver signature enforcement was the crucial step. Adb now works perfectly in recovery!
chemicalrubber said:
Thanks stunts and Linearequation! Disabling driver signature enforcement was the crucial step. Adb now works perfectly in recovery!
Click to expand...
Click to collapse
You're welcome. To clarify my post, TWRP works fine, goo,.img is causing some corrupted downloads yet.
Sent from my Amazon Kindle Fire HD running CM 11 KitKat 4.4 using xda app-developers
My OnePlus 3T, in recovery is installing as " LeMobile Android Devices, Android ADB Recovery Interface"
i am not able to install in sideload mode, can anyone help?
For Windows:
A few steps to get rid of the LeMobile pesky driver (or another driver for PnP devices).
1. Have the device manager opened "devmgmt.msc". Make sure the LeMobile is visible in the device tree by connecting your phone or tablet.
2. Open the Command Prompt with Admin privilege. type "pnputil /enum-drivers" This should generate a list, lookup the "Published Name" value of the LeMobile driver, should be something like "oem??.inf" Remember this name.
3. Use the following command in the Command Prompt with Admin rights: "pnputil /delete-driver oem??.inf /force" Of course oem??.inf should be the name you found in step 2.
4. Go to the device manager. Do not refresh of rescan! Right-click on the LeMobile device still shown in the device manager and select "Update Driver Software". Now you can browse to your preferred driver
5. And You're done!
nAFutro said:
For Windows:
A few steps to get rid of the LeMobile pesky driver (or another driver for PnP devices).
1. Have the device manager opened "devmgmt.msc". Make sure the LeMobile is visible in the device tree by connecting your phone or tablet.
2. Open the Command Prompt with Admin privilege. type "pnputil /enum-drivers" This should generate a list, lookup the "Published Name" value of the LeMobile driver, should be something like "oem??.inf" Remember this name.
3. Use the following command in the Command Prompt with Admin rights: "pnputil /delete-driver oem??.inf /force" Of course oem??.inf should be the name you found in step 2.
4. Go to the device manager. Do not refresh of rescan! Right-click on the LeMobile device still shown in the device manager and select "Update Driver Software". Now you can browse to your preferred driver
5. And You're done!
Click to expand...
Click to collapse
trying to install driver from oneplus driver folder, it is giving me that the driver is not for windows 10 64bit
tekken1972 said:
trying to install driver from oneplus driver folder, it is giving me that the driver is not for windows 10 64bit
Click to expand...
Click to collapse
Have a look at https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
The toolkit has the drivers. OnePlus is being weird with drivers. I've read from another user that OnePlus is using the driver download internally but it is not yet published.
nAFutro said:
Have a look at https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
The toolkit has the drivers. OnePlus is being weird with drivers. I've read from another user that OnePlus is using the driver download internally but it is not yet published.
Click to expand...
Click to collapse
Did all the above still could not install the drivers.
Problem solved by latest windows 10 64bit update
Google, Inc. - Other hardware - Android Bootloader Interface
Hello, I've searched everywhere but can't find a solution to my problem. every bricked honor 3c that I read can be flashed, but when I connect mine to the pc to flash it sp fails and the computer makes a disconnected device sound.
does anyone have any idea how to flash the stock ROM on this phone in this state? I'd really hate to throw it away because of a software problem.
thanks and have a great day!
with windows 10 or 7?
if you use win 8 or 10 :
1- Open a Command Prompt with admin privileges. In Windows 10 or 8, just press the Windows key + X and then select “Command Prompt (Admin)”.
2- Type in the following command and press Enter.
bcdedit /set testsigning on
You should receive “The operation completed successfully” message. If you see a message saying the value is protected by Secure Boot policy, then you have to turn off Secure Boot in the UEFI/BIOS, before disabling Driver Signature Enforcement.
3- Close the Command Prompt and restart your computer. From now on, you will be able to install or run any unsigned driver without problems.
If you need to enable the Driver Signature Enforcement again, run this command instead:
bcdedit /set testsigning off
source
for win 7 reinstall Handset WinDriver.
mt_nik said:
with windows 10 or 7?
if you use win 8 or 10 :
1- Open a Command Prompt with admin privileges. In Windows 10 or 8, just press the Windows key + X and then select “Command Prompt (Admin)”.
2- Type in the following command and press Enter.
bcdedit /set testsigning on
You should receive “The operation completed successfully” message. If you see a message saying the value is protected by Secure Boot policy, then you have to turn off Secure Boot in the UEFI/BIOS, before disabling Driver Signature Enforcement.
3- Close the Command Prompt and restart your computer. From now on, you will be able to install or run any unsigned driver without problems.
If you need to enable the Driver Signature Enforcement again, run this command instead:
bcdedit /set testsigning off
source
for win 7 reinstall Handset WinDriver.
Click to expand...
Click to collapse
I don't know how you got faulty drivers from my problem. my problem isn't drivers, they're installed correctly, my problem is the phone not staying on enough for the software to flash before it reboots.