Details:
OS: Windows 7 (32 bit)
Kindle Fire Version: 6.3.1 (stock, unrooted, only 2 days old)
What have I done so far:
1. Installed Android SDK with platform tools and USB driver
2. Modified usb_driver info file to include kindle hardware ID
3. Installed kindle driver after connecting with factory cable (can see 'Android ADB Interface' in the device manager)
4. ## Couldn't find the adb usb ini file in C:\Users\(User_name)\.android\
This is when I decided to try the KFU
5. Unplugged factory cable. Installed drivers using add_drivers batch file in KFU
6. Checked for adb usb ini file in C:\Users\(User_name)\.android\ - it was present with the new ID added
7. Plug cable -> Wait for device to be detected - > Start > Run > cmd
8. Navigate to the KFU tools folder with adb.
9. Tried all the various ways to see if the device is detected.
Code:
adb shell
adb kill-server
adb devices
Did not detect device at all (device not found error)
10. Unplug factory cable -> restart kindle -> repeat from step 5 till 9. Still nothing
11. Unplug factory cable -> restart computer -> restart kindle -> repeat from step 5 till 9
None of this has worked. I still can't get adb to detect my device. Am I missing something?
Thanks in advance for any help. Appreciate it.
x3_voodoo_3x said:
Details:
OS: Windows 7 (32 bit)
Kindle Fire Version: 6.3.1 (stock, unrooted, only 2 days old)
What have I done so far:
1. Installed Android SDK with platform tools and USB driver
2. Modified usb_driver info file to include kindle hardware ID
3. Installed kindle driver after connecting with factory cable (can see 'Android ADB Interface' in the device manager)
4. ## Couldn't find the adb usb ini file in C:\Users\(User_name)\.android\
This is when I decided to try the KFU
5. Unplugged factory cable. Installed drivers using add_drivers batch file in KFU
6. Checked for adb usb ini file in C:\Users\(User_name)\.android\ - it was present with the new ID added
7. Plug cable -> Wait for device to be detected - > Start > Run > cmd
8. Navigate to the KFU tools folder with adb.
9. Tried all the various ways to see if the device is detected.
Code:
adb shell
adb kill-server
adb devices
Did not detect device at all (device not found error)
10. Unplug factory cable -> restart kindle -> repeat from step 5 till 9. Still nothing
11. Unplug factory cable -> restart computer -> restart kindle -> repeat from step 5 till 9
None of this has worked. I still can't get adb to detect my device. Am I missing something?
Thanks in advance for any help. Appreciate it.
Click to expand...
Click to collapse
When you say factory cable do you mean the modified USB cable that makes the kindle boot into fastboot mode if that is the case adb will not see the device
Sent from my Galaxy Nexus using xda premium
ztkryan said:
When you say factory cable do you mean the modified USB cable that makes the kindle boot into fastboot mode if that is the case adb will not see the device
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You mean I should try it with a normal micro usb cable?
Sigh. I did not see this in any of the threads. Let me go try it first thing.
Thank you very much.
x3_voodoo_3x said:
You mean I should try it with a normal micro usb cable?
Sigh. I did not see this in any of the threads. Let me go try it first thing.
Thank you very much.
Click to expand...
Click to collapse
Factory cable enables fastboot mode... fastboot and adb are mutually exclusive.
Similar to "adb devices", you can try "fastboot getvar product" to see if the KF is found.
Do keep in mind fastboot mode changes the hardware ID and thus needs to have drivers installed for it as well, if you haven't already.
Dasanko said:
Factory cable enables fastboot mode... fastboot and adb are mutually exclusive.
Similar to "adb devices", you can try "fastboot getvar product" to see if the KF is found.
Do keep in mind fastboot mode changes the hardware ID and thus needs to have drivers installed for it as well, if you haven't already.
Click to expand...
Click to collapse
That didn't help either.
Tried with a normal cable. Neither fastboot nor adb nor the KFU would work although I have the drivers installed and have done everything else to root, as described in my first post.
My plan of action now is to try it on another computer. Fresh start with KFU alone.
Will update about how that goes. Have a bad feeling though.
x3_voodoo_3x said:
My plan of action now is to try it on another computer. Fresh start with KFU alone.
Click to expand...
Click to collapse
Run install_drivers.bat before you plug in the KF for the first time, should help.
Dasanko said:
Run install_drivers.bat before you plug in the KF for the first time, should help.
Click to expand...
Click to collapse
It worked in a new computer when I ran the install_drivers.bat file first.
Thanks all for helping. Appreciate it.
After struggling for two days to get adb up and running, I finally got the cmd window up and able to get to adb shell. After running daemon it returns-
error: device not found
sh-3.2$
So are my drivers missing or not in the right place? any help greatly appreciated.
xD lol get the universal naked drivers from efrants thread . Then with the phone plugged in go to device manager and uninstall the drivers... then unplug the phone, install the drivers put the phone in fastboot mode (volume up + volume down + power) and plug it in again... enjoy
Sent from my GT-P7500 using xda premium
When installing the drivers, with the GNex connected, go to the Device Manager in windows. Right click the unknown device that appears on your list and right click to update the driver. Select browse (as opposed to automatic driver lookup) and navigate to the folder where you have the modified driver extracted to:
http://github.com/gu1dry/android_winusb/zipball/master (this modified driver comes directly from the CyanogenMod wiki)
this should solve your problem.
type on the cmd: adb devices
and if any device actually shows up, then you have installed drivers successively.
IonAphis said:
When installing the drivers, with the GNex connected, go to the Device Manager in windows. Right click the unknown device that appears on your list and right click to update the driver. Select browse (as opposed to automatic driver lookup) and navigate to the folder where you have the modified driver extracted to:
http://github.com/gu1dry/android_winusb/zipball/master (this modified driver comes directly from the CyanogenMod wiki)
this should solve your problem.
type on the cmd: adb devices
and if any device actually shows up, then you have installed drivers successively.
Click to expand...
Click to collapse
I followed the steps in your post to the letter and drivers seem to display properly in Device Manager but I still get the sme message displayed in cmd window.
diver47591 said:
After struggling for two days to get adb up and running, I finally got the cmd window up and able to get to adb shell. After running daemon it returns-
error: device not found
sh-3.2$
So are my drivers missing or not in the right place? any help greatly appreciated.
Click to expand...
Click to collapse
You cannot use adb commands within a shell..
Sent from my Galaxy Nexus using Tapatalk 2
looks like this
i opened debugging mode and turn on bluetooth debugging
but in the Android Wear
it shows disconnected
not any windows let me confirm RSA keys
and i remove moto connect ,tired reset moto360 and restart my phone
tired connnect Wear again
never change
Device: windows 7 , Nexus 4 with 4.4.4 ,moto 360 4.4W1
is any steps i miss?
Thanks a million~~
Maybe its too late, but these instructions worked for me.
Source (Cédric Champeau's blog): melix.github.io/blog/2014/10/android-moto360.html
1. Open applications settings > Android wear, force stop
2. Clear its data and cache
3. Open applications settings > Google Play Services
4. Manage space > delete all data
5. Reboot the phone and the Moto 360
you need the ADB tools;
open a cmd prompt in the folder with adb.exe and type in adb forward tcp:4444 localabstract:/adb-hub without the quotes and on the next line, type adb connect localhost:4444
I have had this watch for about an hour now... ANNNND the bootloader is unlocked...
easy steps below
Note For Clarification: you CANNOT do this over Bluetooth.
Enable ADB and connect to computer.
reboot into fastboot using: adb reboot-bootloader
then issue command: Fastboot Oem Unlock
accept the prompt on the watch.
then reboot the watch...
Piece of cake.
Now... about that boot logo...
Yeah its like a nexus in that regard. And no I don't have the watch yet but have ordered it today.
I would unlock mine but there's no reason to yet. I always unlock my Nexus devices first thing yet with the watch I would like to keep it stock for now.
No reason to unlock, until someone creates twrp, and root.
suzook said:
No reason to unlock, until someone creates twrp, and root.
Click to expand...
Click to collapse
I agree, a factory reset on it only takes 2-3 minutes so its not like a phone where it takes forever to set up again.
ApoKyla said:
I have had this watch for about an hour now... ANNNND the bootloader is unlocked...
easy steps below
Enable ADB and connect to computer.
reboot into fastboot using: adb reboot-bootloader
then issue command: Fastboot Oem Unlock
accept the prompt on the watch.
then reboot the watch...
Piece of cake.
Now... about that boot logo...
Click to expand...
Click to collapse
Hello, may iam to stupid, but i cant force a reboot.
i connect phone via USB to PC, then Bluetooth to the watch, enabled ADB,...and i can see the watch but when i want reboot, only the phone reboots not the watch.
i see this...
C:\ADB>adb devices
List of devices attached
FA2CJW201138 device (PHONE)
localhost:4444 device (WATCH)
regards
UPDATE:
Whit this i can reboot the Watch into FASTBOOT MENU.
C:\ADB>adb -s localhost:4444 reboot-bootloader
but how can i unlock it now?? (after rebooting, there is no connection to the Phone)
Carlossianz0815 said:
Hello, may iam to stupid, but i cant force a reboot.
i connect phone via USB to PC, then Bluetooth to the watch, enabled ADB,...and i can see the watch but when i want reboot, only the phone reboots not the watch.
i see this...
C:\ADB>adb devices
List of devices attached
FA2CJW201138 device (PHONE)
localhost:4444 device (WATCH)
regards
UPDATE:
Whit this i can reboot the Watch into FASTBOOT MENU.
C:\ADB>adb -s localhost:4444 reboot-bootloader
but how can i unlock it now?? (after rebooting, there is no connection to the Phone)
Click to expand...
Click to collapse
Have not done it, but fastboot takes the -s parameter as well. So I would try:
fastboot -s localhost:4444 oem unlock
brizey said:
Have not done it, but fastboot takes the -s parameter as well. So I would try:
fastboot -s localhost:4444 oem unlock
Click to expand...
Click to collapse
Hi,
no, the fastboot command does not work,it stops with the message < waiting for device >
Cannont get USB drivers to work
I tried bith google USB drivers and ClockWorkMod universal ADB drivers and cannot get my Huawei to properly connect. I tried two separate computers with the same result. Each time the USB drivers seem to install but the watch shows up under other with exclamation point. My objective is to side load watch face apks to see what I can accomplish with running this watch under iOS.
ADB debugging is on and I also tried also turning on Bluetooth debugging. Intersetingly Bluetooth debugging does kick in.
I'm a novice at BT debugging and any attempt to communicate with the watch following on-line guidance did not work.
Any suggestions/help would be appreciated.
---------- Post added at 05:19 PM ---------- Previous post was at 05:18 PM ----------
I tried both google USB drivers and ClockWorkMod universal ADB drivers and cannot get my Huawei to properly connect. I tried two separate computers with the same result. Each time the USB drivers seem to install but the watch shows up under other with exclamation point. My objective is to side load watch face apks to see what I can accomplish with running this watch under iOS.
ADB debugging is on and I also tried also turning on Bluetooth debugging. Intersetingly Bluetooth debugging does kick in.
I'm a novice at BT debugging and any attempt to communicate with the watch following on-line guidance did not work.
Any suggestions/help would be appreciated.
I still use the old pdanet drivers...they seem to work with everything.
Hi Guys,
still can not work whit the watch after rebooting, may i missunderstand somthing.
Thats the way i do:
From PC to Phone via USB DEBUGING, from PHONE to WATCH via BLUETOOTH DEBUING!
but after reboot into bootloader, i can not talk to the watch anymore, so how can i put the files on the watch???
thanks for help!!!
Carlossianz0815 said:
Hi Guys,
still can not work whit the watch after rebooting, may i missunderstand somthing.
Thats the way i do:
From PC to Phone via USB DEBUGING, from PHONE to WATCH via BLUETOOTH DEBUING!
but after reboot into bootloader, i can not talk to the watch anymore, so how can i put the files on the watch???
thanks for help!!!
Click to expand...
Click to collapse
Enable ADB on the watch (settings/about/tap build# 10 times then developer options, ADB enable)
Download PDANet ADB Drivers: http://www.topnotchtablets.com/installADBdriver
connect to computer. (Using the magnetic USB charging cable)
reboot into fastboot using: adb reboot-bootloader
then issue command: fastboot oem unlock
accept the prompt on the watch. (Hold the watch button)
then reboot the watch...
You should be good
Sent from my SM-N920T using XDA mobile app
Thanks for replay,
last night i got it, via Bluetooth.
Thanks all, now i have the new kernel and recovery.
I think the new kernel works faster and need less power then the orig one.
best Regards
Thank you !
az93civic said:
Enable ADB on the watch (settings/about/tap build# 10 times then developer options, ADB enable)
Download PDANet ADB Drivers: http://www.topnotchtablets.com/installADBdriver
connect to computer. (Using the magnetic USB charging cable)
reboot into fastboot using: adb reboot-bootloader
then issue command: fastboot oem unlock
accept the prompt on the watch. (Hold the watch button)
then reboot the watch...
You should be good
Sent from my SM-N920T using XDA mobile app
Click to expand...
Click to collapse
I have the same problem. Once it boots into bootloader on the watch, cmd prompt on the pc becomes unresponsive and i cannot type anything else in. Were you able to fix yours
---------- Post added at 03:27 AM ---------- Previous post was at 03:04 AM ----------
wookie_666 said:
I have the same problem. Once it boots into bootloader on the watch, cmd prompt on the pc becomes unresponsive and i cannot type anything else in. Were you able to fix yours
Click to expand...
Click to collapse
just realised i should probably be using the magnetic charger, because when i reboots it looses bluetooth connection
ill try when i get home
az93civic said:
...
then issue command: fastboot oem unlock
accept the prompt on the watch. (Hold the watch button)
then reboot the watch...
You should be good
Click to expand...
Click to collapse
What does "issue command: fastboot oem unlock" mean exactly? There is a little red action name which I can cycle between "Reboot", "Shutdown", "Reboot-bootloader" and "Reboot-recovery", none of which seem remotely correct. I went into "Reboot-recovery" to see whether there was further stuff in there, but nothing seems relevant.
Trejkaz said:
What does "issue command: fastboot oem unlock" mean exactly? There is a little red action name which I can cycle between "Reboot", "Shutdown", "Reboot-bootloader" and "Reboot-recovery", none of which seem remotely correct. I went into "Reboot-recovery" to see whether there was further stuff in there, but nothing seems relevant.
Click to expand...
Click to collapse
So what this means is you need to have ADB and fastboot setup on your computer. From there, you will need to go into developer settings on the watch and enable ADB debugging. Then once you have that enabled, go to where you set up ADB on your computer and type in those commands provided.
P.S. If you're sitting there not sure what ADB means and how to set it up, you NEED to do more research before trying anything like this.
dbroer91884 said:
So what this means is you need to have ADB and fastboot setup on your computer. From there, you will need to go into developer settings on the watch and enable ADB debugging. Then once you have that enabled, go to where you set up ADB on your computer and type in those commands provided.
P.S. If you're sitting there not sure what ADB means and how to set it up, you NEED to do more research before trying anything like this.
Click to expand...
Click to collapse
Actually, it has been a bit of a ride.
I knew of adb already from my watch face development so I had initially wondered whether fastboot was a subcommand of that. I didn't expect it to be another command in the SDK at all for some reason. But yep, it's in the same place as adb, and it works, and now everything flashed fine. I don't know why I didn't search my computer for a file with that name, since that would have located it.
Un-hiding the development options is mentioned on the wear developer site so that was fairly easy to set up. The only hard part was that they gave a text-only explanation, but this watch came set to Chinese, so it was a bit fun to figure out which button to press to "confirm" a dialog. I recognised the first option as the "no" and the second option turns out to have been the "yes", but there are more options below that I still don't know what they are, lol.
suzook said:
No reason to unlock, until someone creates twrp, and root.
Click to expand...
Click to collapse
Custom recovery already available by skin 1980. Take a look here. Custom kernel with custom twrp.
http://forum.xda-developers.com/showthread.php?t=3219596
I was thinking to upload a custom rom for Huawei watch “slim system.img, deodexed, root and more " But I need someone to try it first. I am still waiting for my watch. I will upload if anyone is interested.
Sent from my Nexus 6P using Tapatalk 2
janjan said:
Custom recovery already available by skin 1980. Take a look here. Custom kernel with custom twrp.
http://forum.xda-developers.com/showthread.php?t=3219596
I was thinking to upload a custom rom for Huawei watch “slim system.img, deodexed, root and more " But I need someone to try it first. I am still waiting for my watch. I will upload if anyone is interested.
Sent from my Nexus 6P using Tapatalk 2
Click to expand...
Click to collapse
You are quoting me from 4 mos ago? LMFAO!
Has any one got the red underline spell check working on their note 4 at&t varient ?
I have been doing some research and I think I have nerrowed down the issue just need some one who has spell check currently working on their device.
If you have then please do reply, it would be best if you have 6.0.1 update but I think android veraion wont matter at all.
:good:
Managed to fix it via ADB
- turn on developer options
- turn on usb debugging
- on your PC downlolad and install minimal adb and fastboot ( http://forum.xda-developers.com/show....php?t=2317790 )
- connect your device via usb to your PC, wait 2 minutes until adb drivers have been installed
- run the installed adb link in your start menu, a cmd window opens op
- enter: adb shell
- enter: settings put secure spell_checker_enabled 1
- close cmd, disconnect phone, spell checking is enabled