Database Develop

[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

Cant get windows 10 to recognize Fire

Has anyone been able to connect there Fire to windows 10 and get windows 10 to recognize it in order to run ADB commands.
In device manager i have a yellow exclamation showing on the my Fire. Ive tried installing the drivers for it that have been posted by RootJunky and the ones in the zip file from the root zip...they all error out

Don't know which ones those are but maybe the ones here if they are different?
https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing

Pond-life said:
Don't know which ones those are but maybe the ones here if they are different?
https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Click to expand...
Click to collapse
thanks dude, i think those are the ones that finally worked. funny some of the ones posted here werent working

el7145 said:
thanks dude, i think those are the ones that finally worked. funny some of the ones posted here werent working
Click to expand...
Click to collapse
I'm sure they must have worked for those that mentioned them though, probably depends what other drivers they already have installed. And maybe which windows.

I succeeded with Windows 10 x64 using the drivers in the zip file for installing Google Play found in this thread: http://forum.xda-developers.com/showthread.php?t=3216122
I had to disable driver signature enforcement before it would accept the drivers. Pop an admin command prompt (try the new Windows+X key combo and click admin command prompt there!), then run the following two bcdedit commands:
bcdedit -set loadoptions DISABLE_INTEGRITY _CHECKS
bcdedit -set TESTSIGNING ON
Reboot and proceed to install the drivers. I did it manually from Device Manager, clicking "Let me specify a location" (or whatever that one says) and such. Once I did that, all was well.

Been searching for this! Same problem, the fix worked! Amazon's fix was so useless.

How to Solve 'Unauthorize Device' in ADB

Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot

Install the Android SDK or install the OnePlus 3 drivers
Sent from my ONEPLUS A3003 using XDA-Developers mobile app

speedyjay said:
Install the Android SDK or install the OnePlus 3 drivers
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
What does the Android SDK do mate?
I never used it before, so would be great if u can give me some hints
Thanks

toughkid said:
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Click to expand...
Click to collapse
Make sure debugging is clicked on under developer options in the main menu. Then disconnect the phone from the pc and reboot the pc. Reconnect the phone after it reboots and hope that you get the adb prompt on the phone again.

android sdk have the latest tools including latest ADB. There is ADB standalone install, that means that if you tell us that you have the latest ADB, that only mean that someone extracted the ADB and lastest fastboot and did a repack and in the end it's not an official repack.
but "disable the debug permission" reset all the recorded device for debug so you should have another prompt.
If in the end you don't have another prompt, verify you adb version by installing the lastest android SDK, uninstall and reinstall the oneplus drivers.
Then if no prompt there is 2 choices :
- wipe the phone, it will reset the prompt for sure, 100%
- use another computer (well you have to have another computer).

I have a computer at home where this happened and I have never been able to straighten it out...tried everything.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app

tdamocles said:
Make sure debugging is clicked on under developer options in the main menu. Then disconnect the phone from the pc and reboot the pc. Reconnect the phone after it reboots and hope that you get the adb prompt on the phone again.
Click to expand...
Click to collapse
Le_Zouave said:
android sdk have the latest tools including latest ADB. There is ADB standalone install, that means that if you tell us that you have the latest ADB, that only mean that someone extracted the ADB and lastest fastboot and did a repack and in the end it's not an official repack.
but "disable the debug permission" reset all the recorded device for debug so you should have another prompt.
If in the end you don't have another prompt, verify you adb version by installing the lastest android SDK, uninstall and reinstall the oneplus drivers.
Then if no prompt there is 2 choices :
- wipe the phone, it will reset the prompt for sure, 100%
- use another computer (well you have to have another computer).
Click to expand...
Click to collapse
Hello sir, i've been trying all of this method, include the wipe the phone (except using another computer) but still no prompt re-appear. Another advice would be greatly appreciated.
Thanks

joho5 said:
I have a computer at home where this happened and I have never been able to straighten it out...tried everything.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Then how's in the end it goes mate? Do you root your phone? I just wanna root it, if u got any other way except the adb that would be great tho

toughkid said:
Then how's in the end it goes mate? Do you root your phone? I just wanna root it, if u got any other way except the adb that would be great tho
Click to expand...
Click to collapse
Have you checked all of your USB ports? I know in the past (with other phones), problems arise if you're not using a direct USB port (one soldered into your MoBo).

toughkid said:
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Click to expand...
Click to collapse
Go to Control Panel > Hardware and Sound > Device Manager > expand Universal Serial Bus controllers. Now connect your phone. You'll now see USB Mass Storage Device. Right click on it. Select Properties, then go to Details. In the Details section, under Property, select Hardware ids. You'll then see the device id. It will be shown something like this: USB\VID_2A70&PID_9011&MI_01. From this you have to take the 2A70 code ~ the code between the first _ and &. Now go to desktop and create a new text document and copy paste this using your device id as shown:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2A70
Now open the Save As menu. In Save As type select All Files. Save the file as adb_usb.ini
Copy this .ini file from desktop and paste it in C:\Users\YourPCName\.android
Disconnect your phone, reboot your pc. Now with USB Debugging turned on, connect your phone to your pc, you'll surely get the permission thingy popup in your phone.

For completion:
If you DO NOT have access to your phone for any reason but still want to use ADB you can simply boot your phone into TWRP and follow these steps.
Windows:
1. Open %userprofile%\.android
2. Copy "adbkey.pub" to your phone (adb push %userprofile%\.android\adbkey.pub /sdcard/adb_keys)
3. Switch to your phone.
4. Go to Advanced > Open Terminal
5. Type in "stop adbd"
6. Move "adb_keys" from /sdcard to /data/misc/adb (mv /sdcard/adb_keys /data/misc/adb/adb_keys)
7. Type in "start adbd"
8. Switch to computer
9. Type "adb shell setprop persist.service.adb.enable 1"
10. Type "adb shell setprop persist.sys.usb.config mtp,adb"
11. Reboot your phone - DONE
Linux / Maybe Mac:
Same steps, but use "~/" instead of "%userprofile%"
Please note:
You may have to repeat the steps 1-7 after boot when still not having permissions so it makes sense to use cp (copy) instead of mv (move) and only repeat steps 5-7.
Edit: Please also check if your drivers are all installed and enabled.
Sent from my OnePlus 2 using XDA Labs

?k

Honor 3C Vibrate only when connected to pc for flash

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.