[Q] KFU doesn't recognize device - Kindle Fire Q&A, Help & Troubleshooting

I try to root my kindle fire but it says waiting on device
Does anyone know how to fix it?

justin111 said:
I downloaded KFU but it won't installed driver and I have tried older versions and it sayes
(Waiting on device)
Can Someone help me? Please
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2179748

soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2179748
Click to expand...
Click to collapse
That help with the drivers but still doesn't recognize device ( waiting on device )

justin111 said:
That help with the drivers but still doesn't recognize device ( waiting on device )
Click to expand...
Click to collapse
Just for the hell of it...try an ADB command. If you don't get a response turn the device off, and close KFU.
Shift + Right-click on the KFU tools folder and select Open command window here.
Enter the following and turn the device on:
Code:
fastboot -i 0x1949 getvar product

justin111 said:
I try to root my kindle fire but it says waiting on device
Does anyone know how to fix it?
Click to expand...
Click to collapse
Are you sure it is a KF1? KF2 is not recognized.
Sent from a bird... No, a plane... Wait, It's a Kindle Fire!

Vlasp said:
Are you sure it is a KF1? KF2 is not recognized.
Sent from a bird... No, a plane... Wait, It's a Kindle Fire!
Click to expand...
Click to collapse
Yes it is a KF1

soupmagnet said:
Just for the hell of it...try an ADB command. If you don't get a response turn the device off, and close KFU.
Shift + Right-click on the KFU tools folder and select Open command window here.
Enter the following and turn the device on:
Code:
fastboot -i 0x1949 getvar product
Click to expand...
Click to collapse
I am not familiar with ADB

soupmagnet said:
Just for the hell of it...try an ADB command. If you don't get a response turn the device off, and close KFU.
Shift + Right-click on the KFU tools folder and select Open command window here.
Enter the following and turn the device on:
Code:
fastboot -i 0x1949 getvar product
Click to expand...
Click to collapse
I tried the shift+ right click but all it says is open in onenote or scan it not open command window

justin111 said:
I tried the shift+ right click but all it says is open in onenote or scan it not open command window
Click to expand...
Click to collapse
okay, then type: cd<space> and drag that folder to the terminal window.
The point is to run the adb commands from the directory the executable is in.

soupmagnet said:
okay, then type: cd<space> and drag that folder to the terminal window.
The point is to run the adb commands from the directory the executable is in.
Click to expand...
Click to collapse
Where do I type that and what is the terminal window.

justin111 said:
Where do I type that and what is the terminal window. I sorry I'm a noob.
Click to expand...
Click to collapse
Command prompt.

justin111 said:
Where do I type that and what is the terminal window. I sorry I'm a noob.
Click to expand...
Click to collapse
Open the start menu and type in cmd, then hit enter. That is the command line, aka the terminal window.
Sent from my Amazon Kindle Fire using Tapatalk HD

jma9454 said:
Open the start menu and type in cmd, then hit enter. That is the command line, aka the terminal window.
Sent from my Amazon Kindle Fire using Tapatalk HD
Click to expand...
Click to collapse
Does this work on windows xp or not

justin111 said:
Does this work on windows xp or not
Click to expand...
Click to collapse
Command prompt does, I don't know if you can access it like I said above.
Sent from my Amazon Kindle Fire using Tapatalk HD

What do I type in cmd?

justin111 said:
What do I type in cmd?
Click to expand...
Click to collapse
Code:
adb devices
or
Code:
fastboot -i 0x1949 getvar product
Make sure your Kindle doesn't show up in the device manager with an exclamation point. If it does, manually reinstall the 'android_winusb.inf'.
If neither of the commands work, and your device doesn't show up in the device manager with an exclamation point next to it, pull the hardware ID of the device as it's shown in the device manager and post it here.

What is cmd supposed to look like?

Am supposed to have my kindle fire pluged in during this process?

justin111 said:
What is cmd supposed to look like?
Click to expand...
Click to collapse
justin111 said:
Am supposed to have my kindle fire pluged in during this process?
Click to expand...
Click to collapse
yes, have your kindle plugged in.
here's a pic of the Command Prompt.

justin111 said:
Where do I type that and what is the terminal window.
Click to expand...
Click to collapse
If you don't know this information, I'd read/research a lot more before attempting to hack your kindle fire.
The terminal window is also known as the dos command prompt and can be accessed from the start menu in the following way:
windows menu->all programs->accessories->command prompt (on windows 7)
Since you do not want a paper weight instead of a useful device please read more and get familiar with windows development. If you get stuck we probably can help, but we do need you to be willing to learn and do some work on your own...
The primary problem people run into with KFU is a device driver issue, you will want to understand windows device drivers and then start learning how to get ADB working with your device first. Once you can do this KFU is a great tool at automating several simple tasks.
Good Luck!
EDIT:
Wow, I must not have noticed a second page was on this thread... I apologize for repeating information that you guys already posted...

Related

Unlocking Xoom on a Mac (edit - solved!)

Hey guys, while I'm not exactly new to rooting, it has been quite some time since I rooted my N1 (and that was the only time I've ever rooted anything. I'm now a little lost with the unlock/rooting process. At this point,:
*I have the latest SDK, and I've updated the Platform Tools and added the contents to the Tools folder
*I've connected via USB and I've done the volume-down-power-up combination and have the "Starting Fastboot protocol support" screen.
However, that's all I've been able to do, and I honestly don't know what I'm missing. I can't get the the commands in Terminal to communicate with the tablet. Any assistance that anyone could provide would be greatly appreciated.
THANKS!
You have the Motorola v4.9 USB charging drivers installed?
When you do "adb devices" in terminal, can you confirm the Xoom is recognized?
If it is, following the guide here on XDA should go swimmingly. If it isn't, something is wrong with your SDK installation.
Elysian893 said:
You have the Motorola v4.9 USB charging drivers installed?
Click to expand...
Click to collapse
Well I was looking for drivers initially, but then I read in the "how to unlock" thread that someone said drivers werent needed on a Mac. Plus I looked for Mac drivers and couldn't find any, just Windows.
bcgaynor82 said:
When you do "adb devices" in terminal, can you confirm the Xoom is recognized?
If it is, following the guide here on XDA should go swimmingly. If it isn't, something is wrong with your SDK installation.
Click to expand...
Click to collapse
Well I'm not sure I'm opening Terminal in the right location. Entering "adb devices" gives me "command not found.
Ah, Mac, I'm of no use to you then.
Well should anybody see this, I'm still trying to get this to work. I can now confirm that the xoom does not show up after entering "adb devices". Otherwise I think the SDK is set up properly...at least I think it is.
take the file you want to use (adb or fastboot) and drag/drop in to the terminal window. Then just finish typing the command.
tanman21 said:
take the file you want to use (adb or fastboot) and drag/drop in to the terminal window. Then just finish typing the command.
Click to expand...
Click to collapse
AH, FINALLY! See, I knew whatever the solution would be, it would be a simple one. Xoom unlocked! Now to move on to root! Thanks a LOT!
joeski27 said:
AH, FINALLY! See, I knew whatever the solution would be, it would be a simple one. Xoom unlocked! Now to move on to root! Thanks a LOT!
Click to expand...
Click to collapse
Set your path. Edit your .bash_profile and you can run commands from anywhere in the terminal. Example:
Code:
export PATH=$HOME/bin/android-sdk-mac_x86/tools:$HOME/bin/android-sdk-mac_x86/platform-tools:$PATH
tanman21 said:
take the file you want to use (adb or fastboot) and drag/drop in to the terminal window. Then just finish typing the command.
Click to expand...
Click to collapse
That makes me a little sad. People should know how to use a command line
Sent from my PC36100 using XDA Premium App

KF Failed Root

Hi guys! I'm new to the forum but not new to the IT world and not new to Linux or Android devices.
I'm stuck at the Kindle Fire screen after a failed attempt to root the device. Here's what I did. I'm hoping somebody can please help me. I did lots of Google searches to try to solve my issue and I can't seem to find the right solution.
So here's the background. I tried to root my KF by using this process http://www.pcworld.com/article/244303/how_to_root_your_kindle_fire.html on an Windows 7 VM. Then I found that SuperOneClick didn't work for KF6.3. So then I tried to KF Utility v.0.9.5 http://forum.xda-developers.com/showthread.php?t=1399889
I selected the option to root the KF. After it went through the process and I got the Kindle Fire screen (which is sounds like the KF is in the fastboot process) I couldn't get anything to work at that point. I couldn't get the VM to even see the KF nor Ubuntu (which is the main OS of that laptop). So then I figured I bricked the device. So I followed these instructions http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/ but that won't work ecause the KF isn't being recognized by the OS. SO at that point, I couldn't get anything to work. So I rebooted the laptop (which is running Ubuntu 12) and the KF booted back up and it fired back up.
If I power off the KF and turn it back on, it gets stuck at the KF bootup screen.
So at that point I decided to throw Windows 7 on a different laptop that I have and see if I can get it to work. So I installed java & Android ADK for my OS (Windows 7). I installed the USB driver and updated the packages. So I go through these instructions first http://forum.xda-developers.com/showthread.php?t=1568340 and I can't get the KF to be recognized as a device through adb. So I go back to the PC World instructions (linked above) and I follow steps through step 8. And I still can't get the KF to be displayed through adb. When I try to kill the adb server and then enter adb devices, I still can't get the KF to be recognized.
Oh and btw, Windows 7 does recognize the device as a "Kindle".
Any help would be greatly appreciated.
Sparty On!
Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works:
Sent from my Amazon Kindle Fire using Tapatalk 2
Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.
I'm having the same problem I think since windows doesn't recognize my kindle I can't install the drivers.
AndroidSparty said:
Thanks for the reply.
Unfortunately, I tried it and I get an invalid usage error. -i isn't a valid option. I can use -w, -s, -p, or -c.
I also obtained fastboot from the CyanogenMod Wiki for Fastboot and copied the exe to the /android-sdk/platform-tools folder and tried it. I also followed the wiki and copied it and found that placing it in the /tools/ directory wouldn't work because the missing .dll file isin the platform-tools directory and not in the tools directory.
Click to expand...
Click to collapse
Us the same commands without -i 0x1949
fastboot oem idme bootmode 4000
fastboot reboot
Sent from my Amazon Kindle Fire using Tapatalk 2
ammubarak said:
Use the following fastboot commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb this should be the way it works
Click to expand...
Click to collapse
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567
From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA
I received mine with 6.3 and KFU wouldn't recognize it even after using the driver installation. BUT I found way around it. You need to install the drivers manually, and then KFU will work. Download the drivers, then extract the .android folder (create it if you don't have one) to
C:\Documents and Settings\YOURUSERNAME\.android open up your device manager, click on the Kindle and follow the UI to select the .android folder. Restart and use KFU. Enjoy!
soupmagnet said:
None of these commands will work without first being able to communicate with the device. In order to communicate with the device you need working drivers. And even though Windows says the drivers are installed, it doesn't mean they are working.
For some reason, the Kindle Fire Utility, along with Windows is a bad combination. You could try to uninstall and delete the current drivers then reinstall OR set up your Linux to run adb and fastboot commands from the terminal.
From they way it sounds, your device is already rooted. All you need to do at this point is change the bootmode. This can easily be done in Linux as long as you are in root. For more info on bootmodes and drivers, read this thread:
http://forum.xda-developers.com/showthread.php?p=23747567
Click to expand...
Click to collapse
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
backspacepc said:
From a command prompt in windows CD over the the folder containing fast boot. One your command prompt is in that folder type fast boot devices. If it says that no devices found then you have a driver issue. What needs to be done next is open the folder containing kfu and run drivers.bat. this should install the appropriate drivers. Once this is done open kfu, select option one, then option 2. This should cause your fire to reboot in normal mode. IF that doesn't work you can push a boot.img to your fire in fast boot if for some reason you fouled up the system directory. Let me know if that does the trick first, if not I'll explain how to fastboot it back to a working condition.
Edit: in kfu select the option that says normal boot mode. Not sure if its option 2 or not. I'm not in front of my PC
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!
AndroidSparty said:
Thanks for the info. I'm on my Windows box now, but i'll try the Linux directions in that URL tomorrow and will get back to you. Thanks!
Good news, I ran fast boot devices without an error. Bad news, it didn't list any devices. Just sent me to another blank command line.
When I initially ran install drivers.bat through FK Utility, it installed the drivers successfully, from what it said. I just ran it again and it said the drivers were installed successfully and the driver name is Google, Inc (WinUSB).
When I ran KF Utility (run.bat), it says that the ADB Status is offline. At this point, I would think that since ADB is offline, the Utility won't work? Stupid Windows!!!
Click to expand...
Click to collapse
Actually it will, status will still be off line, just select the boot mode option, and then on the next screen select normal bootmode
Sent from my MB860 using XDA
For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.
soupmagnet said:
For future reference if you want to use Linux to issue fastboot and adb commands, here's the tutorial:
http://forum.xda-developers.com/showthread.php?p=22067293
I'd suggest using Linux as it is WAY more stable and WAY more reliable.
Click to expand...
Click to collapse
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA
backspacepc said:
I completely agree, I use and am familiar with both and it sounded like he was trying to do it from a windows machine.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Actually...I'm a she.
Since I have both available to me...it sounds like I should scrap the Windows (which is an understatement anyway) and use Linux/Ubuntu. That I can do!
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
AndroidSparty said:
I'll try the Linux directions later today and will let you know how I come out. Thanks again for the help!
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
You may also want to try to rerun your root script, oddly enough I've had that work before too.
Sent from my MB860 using XDA
AndroidSparty said:
Edit: Okay just tried it & I still can't get adb & fastboot to recognize the device. I followed the "Enable ADB under Ubuntu/Linux" directions and still nodda.
Click to expand...
Click to collapse
Did you notice the second post in the Linux tutorial?
kinfauns said:
Thanks for the guide on setting this up for linux. I just wanted to point out a small error in the instructions. The echo command above is incorrect and will not do what you intended. It should be corrected to
Code:
echo 0x1949 >> ~/.android/adb_usb.ini
Click to expand...
Click to collapse
backspacepc said:
Sorry ma'am! did you also try the directions I posted for windows as far as kfu? Its starting to sound like you may not have fully flashed fff
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I just ran kfu and I I was able to get it to do a normal boot. YAY!
Then I ran the .bat file in the KFU and I selected the permanent root. During the activating fastboot, it said that "Oops something went wrong...." it couldn't find the kindle. Then it installed twrp.img is missing and it downloaded successfully. So then I got the Notice, and it's installing TWRP and it's waiting for the device. I turned the Kindle off & on a few times to get the KFU to recognize the Kindle, and no luck. At least I was able to boot into the KF while it's still still waiting for the device. BUT....at this point during the TWRP install process, it's waiting for the device and not recognizing it.
soupmagnet said:
Did you notice the second post in the Linux tutorial?
Click to expand...
Click to collapse
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.
AndroidSparty said:
I did, but I used vi instead of gedit. And i verified that 0x149 was in the file on a new line.
Click to expand...
Click to collapse
I can't imagine why using vi would make any difference but you could try gedit to see if it works.
As for TWRP, you could install it manually (Windows). Make sure you have a connection with adb/fastboot and use KFU to set your device to fastboot mode. Keep in mind when you do this that you may have to go through the whole process of fixing your drivers again (blame Windows/KFU).
When you're in fastboot mode, hold the power button until the device shuts down.
Shift + right click the KFU folder that contains fastboot (tools) and open as a command
In the prompt that comes up, enter:
Code:
fastboot -i 0x1949 flash recovery /path/to/twrp2.1.img
When your prompt says "waiting for device", turn the device back on.
Make sure it's twrp 2.1 Version 2.0 is installed in a different manner and will most likely cause problems if installed with the "flash recovery" command.

Kindle bricked - Can't find the solution anywhere

Hey guys,
so I'm pretty new to the whole android scene and thought it would be a good idea to root my kindle fire. So, i went and downloaded the kindle fire utility and hit install permanent root with superuser.... but didnt put on twrp. oops. I was one of the few unfortunate ones whos rooting didnt work so smoothly. Now i have a kindle that is stuck on the stock start up screen indefinitely. When i plug it in it says windows does not recognize the device - just install the drivers, no big deal right? wrong. i installed the android sdk and all that jazz, and i installed the drivers packed with the kindle fire utility, and still my computer recognizes it as a universal serial bus controller.
every guide for unbricking either assumes you have twrp, or that the re installation of drivers will fix it. im at a complete and utter loss
Josepho1997 said:
Then, in cd to fastboot in cmd and type:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
So, i installed the drivers, and opened up the cmd window, but i have no idea how to navigate to the correct directory through cmd now. sorry about my ignorance, really, but could you break t down a tad more?
cellophanemask said:
So, i installed the drivers, and opened up the cmd window, but i have no idea how to navigate to the correct directory through cmd now. sorry about my ignorance, really, but could you break t down a tad more?
Click to expand...
Click to collapse
Navigating to a directory is very easy.
Type cd and then put the file path after it.
Example:
cd c:\Program Files\ Adobe
Shift+ right click on the tools folder in kindle fire utility select open command window here.

[Q] Code?

My KF is bricked. It has TWRP on it but it has been wiped clean and my pc will not recognize it. It does in ADB, I keep seeing write the CODE: then stuff. I was told I could to where I needed to write this code by right clicking on the KFU Tools folder. I then get C:\android\Kindle Fire Utility>
Now that being said.. where do I begin to type the fastboot -i Ox1949 and so on. Sure do need some much appreciated help assistance.
Boot into TWRP and then do what Josepho1997 said. Then you can just flash the rom.
The "Rom.zip" would be the file path to wherever the rom is saved on your computer.
Where can I write the tag
Josepho1997 said:
So you just have no OS?
Boot into TWRP. Then Download and transfer the ROM via adb
Code:
adb push Rom.zip /sdcard
Then flash the ROM.
Sent from my Kindle Fire
Click to expand...
Click to collapse
But where do I code?
adb in cmd not recognized as a command
Josepho1997 said:
In cmd. Open up cmd, run adb, and then type that code. And remember what veeman said. When I say Rom.zip, you must put both the correct name and directory applicable to you. (Ex. C:\AlienDroid.zip)
Sent from my Kindle Fire
Click to expand...
Click to collapse
in cmd, adb is not recognized as a internal or external command, operable program or batch file.
Know how long it's been since I used cmd. Help me out please.
You need to open the cmd window when you are in the directory that contains the adb.exe file. Usually this is in C:/kfu/tools directory. The easiest way to do that is to use windows explorer and navigate to that directory then press shift and right click your mouse then select the option "open command window here". You should now be able to issue adb commands.
Sent from my Amazon Kindle Fire using Tapatalk 2
nacraracer said:
in cmd, adb is not recognized as a internal or external command, operable program or batch file.
Know how long it's been since I used cmd. Help me out please.
Click to expand...
Click to collapse
Easiest way is to download the Kindle Fire Utility and then navigate to the tools directory in the command line. Then you can run adb and fastboot commands.
Still won't communicate
veeman said:
Easiest way is to download the Kindle Fire Utility and then navigate to the tools directory in the command line. Then you can run adb and fastboot commands.
Click to expand...
Click to collapse
I have tried everything to get the computer to see the kindle. adb commands are not working. Just says waiting on device, tried to adb push a rom and it just said device not found.
I was able to bring up a fastboot menu one time but once there it wouldn't respond.
Any ideas please.
I am looking at the TWRP v2.2.0 screen. It will not mount either
nacraracer said:
I have tried everything to get the computer to see the kindle. adb commands are not working. Just says waiting on device, tried to adb push a rom and it just said device not found.
I was able to bring up a fastboot menu one time but once there it wouldn't respond.
Any ideas please.
I am looking at the TWRP v2.2.0 screen. It will not mount either
Click to expand...
Click to collapse
Have you installed the drivers?
veeman said:
Have you installed the drivers?
Click to expand...
Click to collapse
I did install the google drivers at the fire tool kit

ADB commands for Win10 Pro PowerShell

Hi,
My PC running Win10 Pro was updated and now i when i try to use an adb command for flash a recovery it pops up a PowerShell window and the fastboot command doesn't work. Which adb drivers i have to use to make it run the fastboot command?
Thx
HC4Life said:
Hi,
My PC running Win10 Pro was updated and now i when i try to use an adb command for flash a recovery it pops up a PowerShell window and the fastboot command doesn't work. Which adb drivers i have to use to make it run the fastboot command?
Thx
Click to expand...
Click to collapse
Google adb anywhere and you'll find a 15 second installer, i use that with 10 Pro and powershell and it works a treat.
If you still have problems you should look in the device manager and see if Windows is using the adb driver at all
Skinpipe said:
Google adb anywhere and you'll find a 15 second installer, i use that with 10 Pro and powershell and it works a treat.
If you still have problems you should look in the device manager and see if Windows is using the adb driver at all
Click to expand...
Click to collapse
Yes, i found the solution but anyway i hate PowerShell, i prefer the old Command Prompt.
Thx!
HC4Life said:
Yes, i found the solution but anyway i hate PowerShell, i prefer the old Command Prompt.
Thx!
Click to expand...
Click to collapse
No probs, you can change powershell back to command prompt on shift+right click with a regedit if you want to, i haven't done this but i will now I've mentioned it

Categories

Resources