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
Related
If you have a 2.73+ rom with the latest hboot you will need to follow This Post to boot the recovery image
1) restart into bootloader (switch on holding the back button)
2) Extract the latest GSM Hero recovery IMG into your android SDK/tools folder
(For SDK & CMD help reffer to Post 3 "The Basics" )
3) Download Superuser.zip and extract the contents to your SDK/tools folder.
4) Plug in USB
5) open a CMD prompt from the tools directory and type the following command> fastboot boot recovery-RA-hero-v1.5.2.img
(you should now enter a recovery console on the handset)
NOW PERFORM A NANDROID BACKUP from the recovery menu, once completre, continue..
6)then type the following commands in CMD exactly as they are here, hitting enter for a new line.
adb shell mount /system
adb push su /system/bin/
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app/
adb shell reboot
Congratulations you now have root access..
Download "Root Boot" from the app store (this will only work if you have root!)
Step 6 modified thanks to ENLIGHTENER, cheers, su whitelist working nicely now..
Recovery image updated to recovery-RA-hero-v1.5.2.img , thanks to Amon_RA
Please be carefull! I accept no liability!
FYI, To unroot you will have to either restore an earlier backup or flash a stock rom..... (reccomend the new official HTC Update via RUU to do a full reset)
OK i have a stupid question as i'm new to all that android thing. Where is the sdk folder? How do i open CMD? Maby u could do a tutorial for totaly new guys on *how to root your HERO* ??
Thanks
The Basics
gaabrysz said:
OK i have a stupid question as i'm new to all that android thing. Where is the sdk folder? How do i open CMD? Maby u could do a tutorial for totaly new guys on *how to root your HERO* ??
Thanks
Click to expand...
Click to collapse
1) you need to download the android software development kit from Here and extract it to yourhard drive.
2) (check) fastboot and adb should be located in the tools folder.
3) in tools right click>new>shortcut when asked enter CMD.exe
4) right click on cmd.exe shortcut, go to properties and clear the "start in" box.
job done, follow as above.
*Edit*
FYI
Verify you have root, go to app store> download Root Booter and test its functions if this works, you have root!
The G2 is the HTC Hero on T-Mobile.
The SDK includes all the drivers needed.
once you have booted the img via fastboot you should enter a recovery console, at this point you need to follow the instructions exactly as typed for adb,
I am running windows 7 Ultimate, should be the same for all windows platforms,
Cheers
__________________
Thank you
Oh and one more question. Do i loose any data doing this??
gaabrysz said:
Thank you
Oh and one more question. Do i loose any data doing this??
Click to expand...
Click to collapse
No, you will not loose anything but be sure to do a Nandroid incase you need to go back to "Stock"
I've followed the process and I never ran into any problems, but I'm new to Android having previously owned Win Mobile phones and now an iPhone.
I got my G2 today on a contract upgrade just so that I could play around with it and try some development work.
Now that I have followed the process, how do I verify that I now have root?
Is there anything I can do to test?
MrHorus said:
I've followed the process and I never ran into any problems, but I'm new to Android having previously owned Win Mobile phones and now an iPhone.
I got my G2 today on a contract upgrade just so that I could play around with it and try some development work.
Now that I have followed the process, how do I verify that I now have root?
Is there anything I can do to test?
Click to expand...
Click to collapse
Use a program that requires root access.
MrHorus said:
I've followed the process and I never ran into any problems, but I'm new to Android having previously owned Win Mobile phones and now an iPhone.
I got my G2 today on a contract upgrade just so that I could play around with it and try some development work.
Now that I have followed the process, how do I verify that I now have root?
Is there anything I can do to test?
Click to expand...
Click to collapse
If by G2 you mean HTC Magic/Sapphire rather than HTC Hero you're in the wrong place...
OK i have a problem when i do this:
4) open CMD prompt use> fastboot boot cm-hero-recovery.img
the phone reboots and then you have to do "adb shell" but when i do that it says "error: device not found", what now??
Just tried it and it works sweet... Took all of 5 minutes... Awesome work thank you
I now have root access on my Hero
gaabrysz said:
OK i have a problem when i do this:
4) open CMD prompt use> fastboot boot cm-hero-recovery.img
the phone reboots and then you have to do "adb shell" but when i do that it says "error: device not found", what now??
Click to expand...
Click to collapse
Have you installed the correct drivers? They are located in the SDK folders you downloaded.
If so try entering "adb devices" in the commmand prompt, Just incase the daemon didnt start.
I think i did. i'm on win 7 x64 btw. ok i'll switch to vista 32bit and try there.
Ok i have checked and in the device manager there is a ADB device>HTC bootloader so i think drivers are correct.
gaabrysz said:
OK i have a problem when i do this:
4) open CMD prompt use> fastboot boot cm-hero-recovery.img
the phone reboots and then you have to do "adb shell" but when i do that it says "error: device not found", what now??
Click to expand...
Click to collapse
Having the exact same problem here.
gaabrysz said:
I think i did. i'm on win 7 x64 btw. ok i'll switch to vista 32bit and try there.
Ok i have checked and in the device manager there is a ADB device>HTC bootloader so i think drivers are correct.
Click to expand...
Click to collapse
try entering adb devices see if that makes any differences
btw, when i done mine the phone was in the recovery console..
Never mind I got it, I'm on Win7 x64, had to switch the driver from:
HTC Dream Composite ADB Interface Version: 1.0.10.1 [25/06/09]
To:
HTC Dream Composite ADB Interface Version: 1.0.9.0
Ok so lets clear something. after i type in cmd: fastboot boot cm-hero-recovery.img my phone reboots and goes to recovery console where i have some otions.... so now i have to type in cmd: adb shell, yes??
still nothing and the adb devices didn't help.
Mienaikage said:
Never mind I got it, I'm on Win7 x64, had to switch the driver from:
HTC Dream Composite ADB Interface Version: 1.0.10.1 [25/06/09]
To:
HTC Dream Composite ADB Interface Version: 1.0.9.0
Click to expand...
Click to collapse
Can u share a link to the drivers?? Please
it sounds like a driver issue. Using the lastest SDK?
android-sdk-windows-1.5_r3
OK got it working. It is a driver issue. using latest sdk but i had to use older drivers just like Mienaikage sad.
gaabrysz said:
Can u share a link to the drivers?? Please
Click to expand...
Click to collapse
They came with the SDK I believe, in the android-sdk-windows-1.5_r3\usb_driver\amd64 folder.
If that's not it then it was this one: http://forum.xda-developers.com/showthread.php?t=446274
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
Attached are Modified ADB USB Drivers for, when available via uRamdisk, ADB shell access through USB/Command Prompt.
Run adbfix.bat and follow the instructions. Currently, for me at least, it will only install the "SingleAdbInterface" connection not the "CompositeAdbInterface" since ADB only currently works wireless.
Again, don't flame because this doesn't work yet...it will once an updated uRamdisk is released with Command Prompt.
Enjoy
Totally not DOS man. It is just Command Prompt.
Nburnes said:
Totally not DOS man. It is just Command Prompt.
Click to expand...
Click to collapse
you know what I mean I'm just that old.
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...
im having this problem i installed platform tools and when i shift right click in folder i dont get cmd i get powershell command is this right
ron31 said:
im having this problem i installed platform tools and when i shift right click in folder i dont get cmd i get powershell command is this right
Click to expand...
Click to collapse
PowerShell is now the default in Windows 10. You can change it back permanently in Settings->Personalization->Taskbar and turn off "Replace Command Prompt with Windows PowerShell...".
You can also access cmd temporarily by typing 'cmd' in a Windows Explorer title bar.
Thanks for the reply I was thinking power shell is why I can't install twrp on my pixel XL