When i try to use the command on the hasoon2000 rooting tool i get a error message "mobile is not recognized as an internal or external operable program or batch file" I have windows 7 pro 64 bit. can someone tell me the Fix for this? all of the drivers are installed USB debug is on and can be seen on my phone when USB cable is connected.Okay i found out that i had to place the tool in my C core directory.
Willibda1 said:
When i try to use the command on the hasoon2000 rooting tool i get a error message "mobile is not recognized as an internal or external operable program or batch file" I have windows 7 pro 64 bit. can someone tell me the Fix for this? all of the drivers are installed USB debug is on and can be seen on my phone when USB cable is connected.
Click to expand...
Click to collapse
Can you check one thing - if platform-tools folder is in PATH?
when i try a command
Addicted2xda said:
Can you check one thing - if platform-tools folder is in PATH?
Click to expand...
Click to collapse
This is what i'm seeing when i try a command, see the jpeg, everything worked great till i changed Laptops
The only problem is the space in your Windows username "WILL RAINES" - in the toolkit thread, haason2000 mentioned it won't work if a space is in the directory path.
Willibda1 said:
This is what i'm seeing when i try a command, see the jpeg, everything worked great till i changed Laptops
Click to expand...
Click to collapse
Copy the rooting folder to C:\....
It appears you did not read the hasoons first 1 or two posts....
I updated the original
On my old laptop I was able to run this tool from my desktop, but I did update original post saying that I fixed the issue
Willibda1 said:
On my old laptop I was able to run this tool from my desktop, but I did update original post saying that I fixed the issue
Click to expand...
Click to collapse
What is the full name of the folder where hasoon's tools are located?
Go to the ADB tools folder and run the command:
ADB DEVICES
does it show your device (it should be an alphaneumeric word)..
I am running on Win8 x64 without issues
Related
/edit - I'm a complete idiot
You are using an out of date version of adb...
Download the android sdk and use the new version
I always keep my sdk up to date
Also, USB debugging is selected (forgot to include that )
have you tried to change the drivers manually using device manager on your pc?
the dellsync may have messed them up..
Turns out i'm a complete fool!
I had adb set up so i could run it from anywhere, but it turns out that was pointing to an old adb.exe i forgot i had.
Everything's working fine now, sorry for wasting your time guys (but thanks for your help!)
I can't get adb to work with Streak neither.
and I only have one and updated adb.exe. what version do you have (the version that suppose to work...)?
thanks
oriharel said:
I can't get adb to work with Streak neither.
and I only have one and updated adb.exe. what version do you have (the version that suppose to work...)?
thanks
Click to expand...
Click to collapse
2 quick checks
make sure java 6 is installed
debug mode on ur device
for test go in tools folder---ddms and try if your device is connected
cheers
I have "Java version is Version 6 Update 20"
DDMS shows blank.
and device is USB debug enabled
when u click ddms a dos cmd open and it dissappear? am i right
when I click DDMS (from cmd window - in windows XP), the DDMS UI is launched. the cmd window remains.
in the DDMS, I see no device attached. all empty lists and windows.
Have you installed the Dell PC Suite that's on the sdcard? That contains some usb drivers or something. Not sure if it's necessary, but it's worth a try
oriharel said:
when I click DDMS (from cmd window - in windows XP), the DDMS UI is launched. the cmd window remains.
in the DDMS, I see no device attached. all empty lists and windows.
Click to expand...
Click to collapse
have you got dell pc suit installed?
if not first install from dell website then run from ur phone sd card folder called" pc suit"
and then try first if u device is connected with pc suit
Hi, I am looking for usb driver for viewpad 7 for using adb. Can anybody provide and link or pointers from where can I get the same.
Thanks,
Dang
There's no "real" driver...
Just connect your Viewpad 7 to your PC.
A window pops up where you can select "setup.exe" - select it.
Then a few drivers get installed (perhaps a restart is necessary)
Seems like the Viewpad 7 has a virtual drive which gets mounted when connecting it to a PC - it's shown up as virtual CD-drive for me under Windows XP and Windows 7.
PS: The drivers are also located on the virtual CD-drive in a directory.
Make sure you run the file from the virtual optical drive if you have autorun disabled.
Sent from my HTC Sensation Z710e using XDA App
plug youre viewpad in now youre pc see een cdrom right click and open use that adb.exe that one works
How to remove the virtual drive
I have already installed the drivers from this drive, but whenever I connect the device, the virtual CD-ROM drive still appears. Anyone know how to get rid of it?
LEGEND383 said:
I have already installed the drivers from this drive, but whenever I connect the device, the virtual CD-ROM drive still appears. Anyone know how to get rid of it?
Click to expand...
Click to collapse
I always open the Sync tool then (do nothing, no sync or so).
That's the only way my Windows 7 PC recognizes the tablet via ADB.
I have been doing that as well, but it's just annoying to have this extra drive that is of no use and just sits there taking up a drive letter.
Stupid question, ive never used adb, but does this mean i dont have to download it because already cames on that virtual drive, and so i only need to install it ?
Now i manage to install the drivers.
I go to the command line in windows and write :
adb usb
adb devices, and get this:
List of devices attached
FM6120420141
Then i do,
adb shell, and nothing happens.
Ive tried several commands and nothing works, what m i doing wrong here ?
Hi guys, i tried another pc with windows xp and everything worked perfect at first try. Thans for the help VPAD7, nice chating.
Bye all the other losers.
Hi VPAD7
Can you share the solution for "adb devices" not working on windows7? I am facing he same problem with my Viewpad7.
Thanks for your contribution to the forum.
---------- Post added at 12:45 AM ---------- Previous post was at 12:39 AM ----------
VPAD7 said:
Now i manage to install the drivers.
Could you share how did you manage to get drivers installed on windows7? I am also seeing same issue with viewpad7. I am trying to root it.
Click to expand...
Click to collapse
Solved driver issue on windows7
Hi,
I was facing issue in connecting viewpad7 to windows7 machine. Even synchronization steps were failing. Manuall attempt to run "adb.exe devices" were unable to detect the device. Here is my steps that I did for rooting the device with SuperOnceClick(SOC)1.7-
1. Initially driver were not detected/installed on windows7. Only CDROM displaying setup was displayed and clicking "Setup.exe" is not installing drivers. Copy the All files on computer and say folder name is "v7Setup".
2. To Install drivers, Connect Tablet/Phone to windows7, select "USB Tethering in tablet" (This is needed to detect devices by Windows7), in windows7:check the "Device Manager", it can show "Others" two devices: HSUSB & RNDIS. Update the driver for both devices from "v7setup/RUT/*" folders.
3. Now start SOC1.7 and select "rageagainstthecage" and click root. It may wait at "Running rageagainstthecage..." message in SOC log window. Then disconnect the Tablet after waiting for 1-2 minute and connect again after beep sound from windows7. Here, again I needed to install the drivers as mentioned in step2. SOC1.7 will proceed and finally in poup message, it will ask to "push su" files. And Done.
I managed to accidentally flash the BLADE boot.img for CM10.1 to my phone before I transferred the ROM across to my SD card.
Didn't think this was a problem.. went into recovery to Mount USB Storage. Didn't work, so I flashed TWRP to see if it worked on there. No luck.
Tried performing a restore of the full working stock sense and wiped caches so I could try to transfer it over the OS. again no luck.
I've even tried pushing the .zip file to the sdcard using adb (run cmd as admin and use 'adb push ROM.zip /sdcard/ROM/') with no luck. It just tells me the device isn't connected. The drivers are definitely installed (fastboot is working).
I'm all out of ideas. If anyone could point me in the right direction, I'd be grateful. Thank you!
Mounting usb storage does not work with MTP devices.
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
Mounting usb storage does not work with MTP devices.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Is there another way of accessing the SD Card through recovery?
No except adb, but that only works with twrp. Why not flash a stock rom, and copy the rom to the SD Card while booted into android.
Sent from my HTC One X+ using Tapatalk 2
You might not be able to directly access your sd card, but you can most likely use adb sideload to load the CM10.1 ROM onto your device and regain functionality. Check this out for more information: http://teamw.in/ADBSideload
NasaGeek said:
You might not be able to directly access your sd card, but you can most likely use adb sideload to load the CM10.1 ROM onto your device and regain functionality. Check this out for more information: http://teamw.in/ADBSideload
Click to expand...
Click to collapse
Yeah while I was waiting for replies. I did a lot of research into adb sideloading and I pretty much get it now.. Only problem is that I'm running Windows 8 which has a whole bunch load of problems with adb... can't get it to recognise my device even with the correct drivers installed. Followed a few guides on the internet, but to no avail.
Does anyone know of anything that works? Or do I have to install it all on a W7 PC?
petedavison93 said:
Yeah while I was waiting for replies. I did a lot of research into adb sideloading and I pretty much get it now.. Only problem is that I'm running Windows 8 which has a whole bunch load of problems with adb... can't get it to recognise my device even with the correct drivers installed. Followed a few guides on the internet, but to no avail.
Does anyone know of anything that works? Or do I have to install it all on a W7 PC?
Click to expand...
Click to collapse
Do you have the latest SDK downloaded from google? I can confirm on windows 8 sideload through command prompt works fine in the platform tools folder. This is through CWM in my experience. i have not messed with TWRP
Kraizk said:
Do you have the latest SDK downloaded from google? I can confirm on windows 8 sideload through command prompt works fine in the platform tools folder. This is through CWM in my experience. i have not messed with TWRP
Click to expand...
Click to collapse
I downloaded and installed it today.
I'll go through exactly what I've done..
- Installed Java SDK
- Installed Android SDK
- Installed platform tools and usb driver
- Installed HTC Sync
- Opened hasoon's toolkit for the One X+
- Booted into TWRP and selected Advanced > Side Load
- Used the side load button on the toolkit.
I've also tried pushing files using the command line directly and cd-ing to the platform tools folder. This is what brings up the error connecting to device message. I've also started getting messages about starting daemon? No clue what that means.
petedavison93 said:
I downloaded and installed it today.
I'll go through exactly what I've done..
- Installed Java SDK
- Installed Android SDK
- Installed platform tools and usb driver
- Installed HTC Sync
- Opened hasoon's toolkit for the One X+
- Booted into TWRP and selected Advanced > Side Load
- Used the side load button on the toolkit.
I've also tried pushing files using the command line directly and cd-ing to the platform tools folder. This is what brings up the error connecting to device message. I've also started getting messages about starting daemon? No clue what that means.
Click to expand...
Click to collapse
Ignore the toolkit. That thing is less than stellar. Open the platform tools folder in the android SDK directory (default should be C: Android) Place the ZIP file of the rom you wish to flash in this directory. Hold shift and right click in blank space in the android sdk folder. Select "open command window here" (or something along those lines, not at my desk). type "adb kill-server" and then type the command "adb sideload romname.zip"
I recommend using CWM as I know this works on that. I do not use TWRP. You are welcome to try it with TWRP though.
Kraizk said:
Ignore the toolkit. That thing is less than stellar. Open the platform tools folder in the android SDK directory (default should be C: Android) Place the ZIP file of the rom you wish to flash in this directory. Hold shift and right click in blank space in the android sdk folder. Select "open command window here" (or something along those lines, not at my desk). type the command "adb sideload romname.zip"
I recommend using CWM as I know this works on that. I do not use TWRP. You are welcome to try it with TWRP though.
Click to expand...
Click to collapse
I have tried this method before too. It brought up the error message. I'll try it again in a minute and let you know. I'll also try it on CWM, but I read somewhere that CWM didn't support it? TWRP 100% does. It has an option for it in GUI.
EDIT: my android sdk in burried in Users/x/AppData/Local/Android/ .. Should I re-install in C:\Android ?
petedavison93 said:
I have tried this method before too. It brought up the error message. I'll try it again in a minute and let you know. I'll also try it on CWM, but I read somewhere that CWM didn't support it? TWRP 100% does. It has an option for it in GUI.
EDIT: my android sdk in burried in Users/x/AppData/Local/Android/ .. Should I re-install in C:\Android ?
Click to expand...
Click to collapse
That sounds like it is in the wrong place. That is usually a temporary folder. Check your c drive, it may also be labeled adt bundle and may be in program files. Sideload is an option in CWM by lloir by default which can be found in the original development section.
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
Alternatively after rereading your OP. If you have not wiped anything you could just flash your old boot.img
Kraizk said:
That sounds like it is in the wrong place. That is usually a temporary folder. Check your c drive, it may also be labeled adt bundle and may be in program files. Sideload is an option in CWM by lloir by default which can be found in the original development section.
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
Alternatively after rereading your OP. If you have not wiped anything you could just flash your old boot.img
Click to expand...
Click to collapse
About to reinstall the Android SDK (uninstalled and rebooted PC). I should install it to C:\Android ? (This folder doesn't exist currently)
I've also never set the environment variables as the Android SDK installed fine. Should I set these?
Also tried that.. it just hangs
petedavison93 said:
About to reinstall the Android SDK (uninstalled and rebooted PC). I should install it to C:\Android ? (This folder doesn't exist currently)
I've also never set the environment variables as the Android SDK installed fine. Should I set these?
Also tried that.. it just hangs
Click to expand...
Click to collapse
Download the android SDK bundle from google and install to C: Android, if it does not exist let it create it (i would still bet it is somewhere in your C drive but ok). I do not know what comes stock but i typically launch the SDK (NOT ECLIPSE) and allow it download all of the files associated with android (probably not needed). There should be an sdk folder inside the c android folder. in that is the platform tools folder. This is where you will open your command window and run the previously mentioned commands.
Kraizk said:
Download the android SDK bundle from google and install to C: Android, if it does not exist let it create it (i would still bet it is somewhere in your C drive but ok). I do not know what comes stock but i typically launch the SDK (NOT ECLIPSE) and allow it download all of the files associated with android (probably not needed). There should be an sdk folder inside the c android folder. in that is the platform tools folder. This is where you will open your command window and run the previously mentioned commands.
Click to expand...
Click to collapse
Trying the sideload now
petedavison93 said:
Trying the sideload now
Click to expand...
Click to collapse
If it is CWM give it a few minutes (literally like 5). Never used TWRP but it could take some time as well.
Kraizk said:
If it is CWM give it a few minutes (literally like 5). Never used TWRP but it could take some time as well.
Click to expand...
Click to collapse
Nothing came up for the kill-server command but it did pause.. so I'm guessing it did something.
The rest ran pretty quick but the phone hasn't received anything and is just sitting there (using CWM to keep my battery charged)
petedavison93 said:
Nothing came up for the kill-server command but it did pause.. so I'm guessing it did something.
The rest ran pretty quick but the phone hasn't received anything and is just sitting there (using CWM to keep my battery charged)
Click to expand...
Click to collapse
You could flash the stock recovery and run the RUU
Kraizk said:
You could flash the stock recovery and run the RUU
Click to expand...
Click to collapse
Very quick guide? I knew this was a possibility, but I've never had to do it until now. Thank you so much for the help btw
Although this still doesn't solve my problems with adb
petedavison93 said:
Very quick guide? I knew this was a possibility, but I've never had to do it until now. Thank you so much for the help btw
Click to expand...
Click to collapse
Flash the stock recovery (I do not have this as you appear to be on the international variant). Download your RUU (search the forums, I know it is here somehwere but the usual htcruu.com is now down....) boot into your boot loader and run the command "fastboot oem lock" Hit the power button to select hboot from the list and then just run the executable.
Kraizk said:
Flash the stock recovery (I do not have this as you appear to be on the international variant). Download your RUU (search the forums, I know it is here somehwere but the usual htcruu.com is now down....) boot into your boot loader and run the command "fastboot oem lock" Hit the power button to select hboot from the list and then just run the executable.
Click to expand...
Click to collapse
Can't relock the bootloader without working drivers.. this is beyond annoying now ¬.¬
EDIT: Relocked but not enough battery to flash RUU. Do I just run the RUU from the computer while the phone is at the home menu in the bootloader?
I'm using a batch file to charge the device over night. Will try again tomorrow.
So I have issues with connecting my phone when I'm in bootloader, since I have Windows 8.1. I have hTC Sync Manager installed, though. Everytime when I connect my phone via usb its says on the windows that USB is not recognized
For Windows 8.1, adb / fastboot is known to be broken... Just use Linux instead or try to find an updated driver, maybe there is a fix somewhere now.
mrpeev said:
So I have issues with connecting my phone when I'm in bootloader, since I have Windows 8.1. I have hTC Sync Manager installed, though. Everytime when I connect my phone via usb its says on the windows that USB is not recognized
Click to expand...
Click to collapse
Check this for a workaround : http://forum.xda-developers.com/showthread.php?p=49131915
When you first run the script it will rename the files to *.bak
If the new file is not copied, just manually copy them to the directory
(make a backup of the original files first)
ckpv5 said:
Check this for a workaround : http://forum.xda-developers.com/showthread.php?p=49131915
When you first run the script it will rename the files to *.bak
If the new file is not copied, just manually copy them to the directory
(make a backup of the original files first)
Click to expand...
Click to collapse
Great, works like a charm for me on Win 8.1 64-bit. However, I had to copy the files manually because the script couldn't find them (although they were right there in the folder!).
Despite many tutorials I am still not able to connect to my HTC Desire X (unlocked, S-ON, HBoot 1.25.002) for executing the fastboot-cmd.
I am not on USB3, tried different USB-ports, tried to install the Google USB driver (v11) manually - but still no luck. In bootloader the message 'FASTBOOT USB' is visible and highlighted. In Windows the device has a yellow exclamationmark (unknown device), category 'USB serial bus controllers'. It used to work fine, on the same computer. Updating to Windows 8.1 could be a cause. If my phone is in normal mode and connected to the PC I am able to drag files to and from the phone. ADB is working also, 'ADB devices' shows my phone.
What can I do more to recognize the phone for executing fastboot? Or is something else needed to do? Thx!
I can't give you link right now but use the search there was a way to use fastboot under windows 8.
Ps:
Try this https://cloud.mail.ru/public/e0429e9c057f/usb_driver_r08-windows.zip
Thx for your reply, still no luck :crying: I have searched more and more and problem solved :highfive:
This thread (click on link to view) helped me the most and has the files which are needed. The suggested KB-solution didn't work so use the old-dirty trick (and USB.zip) which is inside the thread mentioned. After executing the batch-file you probably still need to copy the files manually.
"As you all may now, Microsoft pushed the new driver stack in Windows 8.1 so ALL (not only USB 3.0) devices must provide a BOS descriptor. Sony ADB and Fastboot doesn't, so Windows fails to enumerate the device which is reported in Device Manager as error code 43. This also may help if you have a USB drive or mouse and it stopped working after you upgraded from Windows 8 to Windows 8.1."
"It's not any kind of magic - it just replaces Windows 8.1's usbhub.sys and usbport.sys with Windows 8's ones. Old files don't check for BOS descriptor so Fastboot can work."
Also just having the very same issue, haha its extremely frustrating. got adb to work when phones on but not when off
Might have just killed my usb ports
thank god for backups
Inside the mentioned thread are some solutions, i.e. #44
Just use the command: "sfc /scannow" from an elevated command prompt... the original usb drivers will be restored.
Or rename the .bak files of the two copied files to the original ones?
RuudM said:
Inside the mentioned thread are some solutions, i.e. #44
Just use the command: "sfc /scannow" from an elevated command prompt... the original usb drivers will be restored.
Or rename the .bak files of the two copied files to the original ones?
Click to expand...
Click to collapse
Luckily I had a backup, hmm still no drivers work might have to downgrade windows8.0
Going to leave this in case someone is still having this problem:
http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337
And if you don't have the drivers AND don't want to install HTC Sync Manager:
http://forum.xda-developers.com/showthread.php?t=2222501