Database Develop

[DRIVER] 64BIT Android Drivers

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!

Windows 8 ADB Fix!

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

[Q] Stuck in boot loop, have fastboot cable?

I tried installing a second bootloader with Fireflash, and apparently I missed a step. This led to my Kindle being stuck in a bootloop. I bought a fastboot cable from ebay, which arrived today. When I connect with that cable, the logo changes to the fastboot logo, but anything I try with the KFHD System.img Restore Tool doesn't work, neither does Kindle FirstAide.
With KFHD System.img Restore Tool, I always get < waiting for device >.
I'm not sure what to do now, can anyone suggest anything?

You need to install the drivers for the device, open your task manager and hit update driver on the Tate device with a triangle next to it, and download the drivers in my signature, then after extracting them, poi t the update drivers wizard to the place you extracted the drivers to and let them install.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
You need to install the drivers for the device, open your task manager and hit update driver on the Tate device with a triangle next to it, and download the drivers in my signature, then after extracting them, poi t the update drivers wizard to the place you extracted the drivers to and let them install.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I just tried that, and the wizard tells me that the hash is not present in the catalog file?

Ah your on windows 8, you need to first disable driver signature enforcement, Google it and then try again.
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, copy these commands in the command prompt one at a time hitting enter after each one.
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/

Device not detected in adb or fastboot

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

Can't unlock the bootloader

Hey guys.
I got my Xiaomi Mi 8 SE yesterday and I decided to apply for a bootloader unlock right away and wait 25 days to unlock it.
I signed into my Xiaomi account, linked my phone and account in the developer options and enabled the bootloader unlock option in Developer Options.
I then went to the Xiaomi Unlock page but instead of being directed to the page where you have to type in your reason to unlock the bootloader, it instantly directed me to the Mi Unlock Tool. It was weird but I decided to go with it.
Even the tool itself didn't deny me at the beginning.
But when I chose Unlock in it, it would fail at 50% of the verification every time.
Does anyone know what's going on and how I can possibly fix it?
EDIT
The issue has been sorted, details as post Number 6
And shortly put, get your hands on a Windows 7 device.

I even tried using and linking another account as well as using a VPN.
If I log in to Xiaomi, I immediately get directed to the Mi Unlock Tool page.
If I try using the tool, it says that it's checking my account for permission and proceeds instead of telling me I don't have permission. And then it fails at the verification stage at 50%.

Hi,
the xiaomi permission is not required from 1-2 months.
For the 50% I have the same problem with windows 10 but whit windows 7(from different pc) is all OK.
I think is a pc driver / USB problem

onecryon said:
Hi,
the xiaomi permission is not required from 1-2 months.
For the 50% I have the same problem with windows 10 but whit windows 7(from different pc) is all OK.
I think is a pc driver / USB problem
Click to expand...
Click to collapse
So I don't need to ask Xiaomi for permission, it goes straight-forward to unlocking?
But I have no clue where to find a Windows 7 device, lol.
ai am using the universal fastboot drivers and the tool did recognize the device. Which drivers should I use?
EDIT
People using the Mi 8 had to wait as well back in June.

Now we can unlock the bootloader without ask permission.
For the tool I don't know if is a driver(so software) problem or "pc hardware" problem.. I read on other site that changing the OS it work and I tried it

onecryon said:
Now we can unlock the bootloader without ask permission.
For the tool I don't know if is a driver(so software) problem or "pc hardware" problem.. I read on other site that changing the OS it work and I tried it
Click to expand...
Click to collapse
I installed Windows 7 onto my laptop and the drivers from HERE.
I enabled ADB debugging, OEM Unlock and I linked my device and account.
Then I connected my phone in adb to let the pc install drivers. And then I did the same for fastboot.
However, fastboot drivers didn't want to initially install so, by using the Device Manager, I had to update the drivers with the fastboot drivers I downloaded and then the phone got recognized as a Bootloader device.
Then I downloaded the Mi Unlock tool, started it as admin, signed in with the same account on the phone ( you can use the QR scan to be sure you use the same account if you want).
And I started with the unlock procedure. Finally, it got past the verification but failed while unlocking, saying that I have 355 more hours to wait.
But this means I can actually unlock my bootloader, I wrote this in as much detail as I could so anyone facing the same issue as me could fix it as well.
Thank you for the help, I will edit the OP.

Windows 10 issues
If using windows 10 you have to Disable Driver Signature Enforcement do the following:
use Command prompt admin
To "Disable Driver Signature Enforcement" enter the following code:-
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
Copy the Code
bcdedit.exe -set TESTSIGNING ON
Copy the Code
To "Enable Driver Signature Enforcement" enter the following code:-
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
Copy the Code
bcdedit.exe -set TESTSIGNING OFF
Copy the Code
Reboot after each action
Hope that helps

boysie37 said:
If using windows 10 you have to Disable Driver Signature Enforcement do the following:
use Command prompt admin
To "Disable Driver Signature Enforcement" enter the following code:-
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
Copy the Code
bcdedit.exe -set TESTSIGNING ON
Copy the Code
To "Enable Driver Signature Enforcement" enter the following code:-
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
Copy the Code
bcdedit.exe -set TESTSIGNING OFF
Copy the Code
Reboot after each action
Hope that helps
Click to expand...
Click to collapse
Yeah, it didn't.
I have a win 7 laptop so I will unlock it when those 360 hours expire.