Database Info

Found Answer To Windows XP 32 Bit Driver install Error

Hi Guys!!!
Recently I had A problem Installing Windows 32 bit Driver For Android So i searched On the web for this error & Found that there were many people with this error...
Here Is the info about that Error In My Last Post: http://forum.xda-developers.com/showthread.php?t=493604
WINDOWS XP x86 / 32-Bit Only
The error was so:
When we download the android_usb_windows.zip then extract it and then try to install it via device manager all goes right it detects the driver but at the last step where it asks for androidusb.sys file and when given the path it waits some time and says Fatal Error...
SO I tried To Go deep in the system32 folder There Go into Drivers Folder Now Here You begin some stuff:
1. Go in "C:\WINDOWS\system32\drivers" Folder there Find These files and cut them and paste in some folder where its safe:
androidusb.sys
usbccgp.sys
usbstor.sys
wdf01000.sys !!!! (Be Careful Deleting this File, I Say First try Without Deleting this file !)
2. Now Go to device manager "Right-click My Computer -> Manager -> Device Manager"
3. Click On ADB Interference Or something like that U ll Get a sub-category Right-click on it Click Uninstall -> OK
Do The Same For the Following :
USB Composite Device
USB Mass Storage Device
4. Get The Drivers From Here If U already Don't Have: http://dl.google.com/android/android-sdk-windows-1.0_r2.zip
OR
Get The Haykuro's Updated USB Drivers from here : http://sapphire-port-dream.googlecode.com/files/usb_driver_updated.zip
5. Now Try To Install The Driver Again By Going to "Right-click My Computer -> Manager -> Device Manager -> Action -> Scan for Hardware Changes" Then You will Get a pop-up saying Found New Hardware...
6. Install the drivers As Usual..... It Will install The Drivers Succesfully....
You Are Done.....

All I can say is THANK YOU.
THANK YOU THANK YOU THANK YOU.
This post deserves a sticky..
you are great

LOL
-- well after this I couldn't use FASTBOOT anymore hahahahaha
well, I worked around that, had to reinstall drivers for Haykuro's SPL too. So now both ADB and FASTBOOT work.

Thanks helped with my Win NT at work. lol

lol i have no idea if this was the cause... after this, I was no longer able to use my laptops keyboard, mice, video card drivers were corrupted along with network drivers, processor bus communications driver and a whole lot more. I had to perform a full system recovery so... yay.. lost everything, but im working on it.
---EDIT, I performed this on my fully recovered system again, and had the same results after it rebooted. I was able to conlude that it was caused by the system file with the wdf in it. Luckily, I hadn't deleted it and simply moved it into the recylcing bin and was able to recover from it. This may just be specific to my system, but I'm not sure. Just a warning to back everything up.

SolemnWishing said:
lol i have no idea if this was the cause... after this, I was no longer able to use my laptops keyboard, mice, video card drivers were corrupted along with network drivers, processor bus communications driver and a whole lot more. I had to perform a full system recovery so... yay.. lost everything, but im working on it.
---EDIT, I performed this on my fully recovered system again, and had the same results after it rebooted. I was able to conlude that it was caused by the system file with the wdf in it. Luckily, I hadn't deleted it and simply moved it into the recylcing bin and was able to recover from it. This may just be specific to my system, but I'm not sure. Just a warning to back everything up.
Click to expand...
Click to collapse
So Is that you are sayin is we do not need to remove the wdf file, did the drivers work without removing & again installing that wdf file?
or u did not put the new file again before rebooting ?

I am not really sure. It can possibly just be my computer. Once removing all the drivers you listed, the ADB then successfully worked, and continued to work as long as the computer was not rebooted. Once rebooted, I drivers for many pieces of hardware became corrupt and unreadable. By simply replacing the wdf driver and rebooting, it fixed the issue. So, I really am not sure. My computer... is strange. I believe it likely could just be my computer thats all.

next time if u get such problem just try solving without removing the wdf file & post what happens...
& plz post the consequences....thanks

The key points are:
To choose ADB interface\HTC Dream Composite ADB Interface to install
--DIYism

sangeet.003 said:
next time if u get such problem just try solving without removing the wdf file & post what happens...
& plz post the consequences....thanks
Click to expand...
Click to collapse
I will be performing another system recovery install soon, so I will post the results. My computer got screwed up again, so backing everything up now...

I still have a problem...
thanks for your tutorial.
I followed as you say, but I can't find my phone in cmd mode in my computer.
I succeed to install driver also it's shown in device manager as like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but something wrong in cmd mode as like this.
I'v tried whatever I can do..reinstall driver, adb, swipe my phone..
what shall I do now?

adb problem
Hi,
Same problem here, tried everything but CMD just is not showing any device...

I found the solution: make sure that debugging mode is checked in your G1 settings because if not ADB will not work.

pluplus said:
I found the solution: make sure that debugging mode is checked in your G1 settings because if not ADB will not work.
Click to expand...
Click to collapse
I followed this completely, I have the phone installed correctly now, not a mass storage device, device manager reads:
ADB Interface > HTC Dream Composite ADB Interface
However, I have usb debugging enabled, and still get the same *error: device not found*
Took a decent amount of time to get done right too, thanks to "trustedinstaller" being the only "user" that can delete drivers on my laptop..yay for changing ownerships! You'd think administrator would suffice, but nay.
Anywho..wtf am I missing here?
edit: win 7 x64, however the same rules for this how-to should still apply, as all the drivers and install options/processes are identical

ive found that trying to use the adb driver the driver gave me error code 10 (within the device manager)
ive got rc win7 64 bit
what i used to get rid of this problem is the program called USBdeview ( google for it)
and uninstalled everything related to htc/android
after connecting the phone the correct driver installed and i could use the adb device

I didn't want to make another topic on this, but I have a problem. Whenever I uninstall the drivers from device manager, then search for new devices, it installs the drivers automatically. I have mass storage and adb dream interface, but no devices are found when I execute the adb command. I cleaned out what I could from the system32 and /drivers folder. Any clues? Just to add, it did work about a week ago, didn't need to use it, now it doesn't work.
Edit: Oops, I forgot the check the uninstall driver box. I have the drivers, they install correctly, but I still can't use adb.
PS: vista x64, installing from the amd64 subfolder.

sangeet.003 said:
Hi Guys!!!
Recently I had A problem Installing Windows 32 bit Driver For Android So i searched On the web for this error & Found that there were many people with this error...
Here Is the info about that Error In My Last Post: http://forum.xda-developers.com/showthread.php?t=493604
The error was so:
When we download the android_usb_windows.zip then extract it and then try to install it via device manager all goes right it detects the driver but at the last step where it asks for androidusb.sys file and when given the path it waits some time and says Fatal Error...
SO I tried To Go deep in the system32 folder There Go into Drivers Folder Now Here You begin some stuff:
1. Go in "C:\WINDOWS\system32\drivers" Folder there Find These files and cut them and paste in some folder where its safe:
androidusb.sys
usbccgp.sys
usbstor.sys
wdf01000.sys
2. Now Go to device manager "Right-click My Computer -> Manager -> Device Manager"
3. Click On ADB Interference Or something like that U ll Get a sub-category Right-click on it Click Uninstall -> OK
Do The Same For the Following :
USB Composite Device
USB Mass Storage Device
4. Get The Drivers From Here If U already Don't Have: http://dl.google.com/android/android-sdk-windows-1.0_r2.zip
OR
Get The Haykuro's Updated USB Drivers from here : http://sapphire-port-dream.googlecode.com/files/usb_driver_updated.zip
5. Now Try To Install The Driver Again By Going to "Right-click My Computer -> Manager -> Device Manager -> Action -> Scan for Hardware Changes" Then You will Get a pop-up saying Found New Hardware...
6. Install the drivers As Usual..... It Will install The Drivers Succesfully....
You Are Done.....
Click to expand...
Click to collapse
nothing happeneds...
after doing that after reboot my laptop,i'm loosing harware keyboard and have some other problems too..
i just change the drivers again and reboot and all ok but there isn't any way to my laptop(toshiba xqosmio x300 with vista 32bit)read my hero in fastboot usb condition...
i tried it and in 2 pc's with xp (service pack 2) but the same again and there....
adb shell and adb devices aren't reade the phone in fastboot usb ....
in my cmd i'm taking allways the same error message when i try to load the cm-hero-recovery.img ""canot load cm-hero-recovery.img""
anybody who can help??

i have the windows usb drivers. and when i go into device manager on my 32bit vista machine, it shows "Android Phone" under portable devices. i click update drivers and select the usb drivers. problem is, it tries to install them, then i get a message saying like 'unable to install "da da what ever driver its called" then it just closes.
why wont this work help is appreciated

THANKS, i was keen to install linux

Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you, Thank you.
You save my life. I've been having this problem for MONTHS!!! and no way im gonna restore my windows xp again. Thanks so much.

[SOLVED] Need help: Can't get ADB to recognize device

I have a Windows 7 Professional 64 bit machine. I have tried every combination I can think of to get the TF300T to show up in adb devices, but to no avail. I have installed Asus Sync and then done Update Driver in the Device Manager, uninstalled Asus Sync and downloaded only the drivers from the thread in the development section, modified the android_winusb.inf in the Android SDK and tried using that driver, many restarts, etc. I have needed to modify every android_winusb.inf I have used, btw, since even the Asus ones didn't have my device in there (my hardware ID ends in 4C81, the one supplied only supported 4DAE, which I find odd).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I update the driver, the device does show up in the Device Manager as "ASUS Android ADB Interface" under "Android Phone," which is where my Galaxy Nexus also shows up, but adb devices only returns the nexus. And now, when I go into "My Computer," the Asus doesn't show up as a connected device (the GNex still does). Same in the Device Manager under Portable Devices.
Has anyone been able to get their TF300T to work with ADB on a Win7 64 bit machine? Is it possible that the version of Windows (Professional) could be causing the issue? I have heard that in the past. Any help would be greatly appreciated. Thanks!

I have windows 7 home edition (x64), I had installed Android SDK a long time ago. Before I connected my Pad for the first time, I updated Android SDK through the manager. I don't have ASUS sync nor Suite. The first time I connected the Pad it automatically installed some drivers, and it worked with adb from the get-go.

I'm on Win7 HP 64 and its working fine here
https://docs.google.com/open?id=0B_7VIwxjudWvVEt4N2JaeUJQUVk
Fixed sharing linkage
Here is the drivers I used.

Northern-Loop said:
I'm on Win7 HP 64 and its working fine here
https://docs.google.com/open?id=0B_7VIwxjudWvVEt4N2JaeUJQUVk
Fixed sharing linkage
Here is the drivers I used.
Click to expand...
Click to collapse
Is this the same drivers as here http://forum.xda-developers.com/showthread.php?t=1661653?
The zip has the same name, so I'm just wondering if you made any tweaks to get it to work or not.

Accord281 said:
Is this the same drivers as here http://forum.xda-developers.com/showthread.php?t=1661653?
The zip has the same name, so I'm just wondering if you made any tweaks to get it to work or not.
Click to expand...
Click to collapse
No not changed anything. Have you installed Google SDK with the USB drivers?
http://developer.android.com/sdk/index.html
Enabled USB Debugging on the tablet under Settings/Dev Options?
Here is mine: https://docs.google.com/open?id=0B_7VIwxjudWvUmJKNmtLYVJ4THM

Northern-Loop said:
No not changed anything. Have you installed Google SDK with the USB drivers?
http://developer.android.com/sdk/index.html
Enabled USB Debugging on the tablet under Settings/Dev Options?
Here is mine: https://docs.google.com/open?id=0B_7VIwxjudWvUmJKNmtLYVJ4THM
Click to expand...
Click to collapse
Yes I've done both those things. I even went so far as to try to copy the relevant information from the Asus drivers into the google usb drivers. It lets me install the driver and then shows up under the Android Phone in Device Manager. But still no luck with adb. I even uninstalled the GNex and then reinstalled it using the same drivers as the Asus (again, copying relevant info into the android_winusb.inf file) and that works just fine. Did it again with a Droid Incredible 2 and that also worked. I thought it might perhaps be related to the fact that the .inf file is no longer signed but these 2 cases make that theory go out the window.
I am banging my head against the wall on this one. I had the same problem with an Acer Iconia A500 and I never did get that one to work.

Accord281 said:
Yes I've done both those things. I even went so far as to try to copy the relevant information from the Asus drivers into the google usb drivers. It lets me install the driver and then shows up under the Android Phone in Device Manager. But still no luck with adb. I even uninstalled the GNex and then reinstalled it using the same drivers as the Asus (again, copying relevant info into the android_winusb.inf file) and that works just fine. Did it again with a Droid Incredible 2 and that also worked. I thought it might perhaps be related to the fact that the .inf file is no longer signed but these 2 cases make that theory go out the window.
I am banging my head against the wall on this one. I had the same problem with an Acer Iconia A500 and I never did get that one to work.
Click to expand...
Click to collapse
So when you type adb device it shows nothing?
Try removing all ASUS from device manager reboot then plug device back in and let windows sort it out.
You'll need to Google to remove hidden ASUS stuff from device manager though.

Northern-Loop said:
So when you type adb device it shows nothing?
Try removing all ASUS from device manager reboot then plug device back in and let windows sort it out.
You'll need to Google to remove hidden ASUS stuff from device manager though.
Click to expand...
Click to collapse
Correct. It will show my GNex or my Dinc 2 (depending on which one is plugged in), but the Asus isn't there. I will try those things and update. Thanks.
Edit: No go. I uninstalled the Asus Composite ADB Interface then turned off USB debugging then uninstalled the TF300T listing that popped up after that. After reboot, I connected it while not in debug mode, allowed it to install the driver itself, then turned on debug mode and had to manually point it to the driver. It still shows up in Dev Manager under Android Phone, but still nothing in ADB. I get the feeling there is nothing that can be done.

My win 7 professional installed the drivers by itself. It originally installed as a media device, and I had to switch the storage mode to "camera" on the tablet for it to come up as ADB device. I didn't test the adb devices in command prompt, but I ran the viper script and it worked just fine.

xAshxMoneyx said:
My win 7 professional installed the drivers by itself. It originally installed as a media device, and I had to switch the storage mode to "camera" on the tablet for it to come up as ADB device. I didn't test the adb devices in command prompt, but I ran the viper script and it worked just fine.
Click to expand...
Click to collapse
H.O.L.Y. S.H.I.T. that did it. I just switched it to camera (PTP) and it is now listed in adb. THANK YOU THANK YOU THANK YOU THANK YOU!!!!!!

Took me quite a while to figure that out (and I have no idea why it works TBH, just got lucky), glad I could help out.

xAshxMoneyx said:
Took me quite a while to figure that out (and I have no idea why it works TBH, just got lucky), glad I could help out.
Click to expand...
Click to collapse
The odd thing is, my GNex is set to Media device, and it works just fine. Thanks again.

Accord281 said:
The odd thing is, my GNex is set to Media device, and it works just fine. Thanks again.
Click to expand...
Click to collapse
No problem homie. My GS2 didn't have that problem either, went in just fine as ADB.

Accord281 said:
I have a Windows 7 Professional 64 bit machine. I have tried every combination I can think of to get the TF300T to show up in adb devices, but to no avail.5
Click to expand...
Click to collapse
OMG, this is what happened to me last night when I tried to do the downgrade so I could root the phone.
I am on an XP 32bit machine.
I have a feeling that the Samsung software, which I also had installed on this machine is conflicting.
I'm in the process of removing all the drives (Samsung and Asus) and starting from scratch.
I still need to read the rest of this thread to see if someone answered your question, if they did, they they help me as well.
Rob

HI,
I guess a picture is worth a thousand words.
I finally managed to get a screen shot of what I have been asking help on:
I've been trying to do a downgrade so I can root my 300.
Why is the Asus showing up underneath my Samsung and does it matter.
Thanks!
Rob

Looks like it's showing up as ADB so it should be fine. Mine comes under a generic "android phone" listing, but maybe if Samsung was your first ever adb device on the computer, they will all show up that way for you. Just a guess.

thank you so much! I've been trying to solve this for 2 days
:good:
xAshxMoneyx said:
My win 7 professional installed the drivers by itself. It originally installed as a media device, and I had to switch the storage mode to "camera" on the tablet for it to come up as ADB device. I didn't test the adb devices in command prompt, but I ran the viper script and it worked just fine.
Click to expand...
Click to collapse

switch storage mode to camera
"I had to switch the storage mode to "camera" on the tablet"
How is that done? I only have usb storage on or off options.. and still stuck

jbosari said:
"I had to switch the storage mode to "camera" on the tablet"
How is that done? I only have usb storage on or off options.. and still stuck
Click to expand...
Click to collapse
Sorry to bump an old thread, but I have the same problem, can't get ADB to recognize my device, and onlu have usb storage on/off in the options.
Anybody shed a light in this?
Thanks in advance

Mefna said:
Sorry to bump an old thread, but I have the same problem, can't get ADB to recognize my device, and onlu have usb storage on/off in the options.
Anybody shed a light in this?
Thanks in advance
Click to expand...
Click to collapse
What is your device and version of Android you're running? It might help to know. There are some tools that can help. I've used USBDeview to delete all drivers and start over to fix problems like this (scroll down to the "Feedback" heading for the download.) After deleting anything ADB related from the list of drivers and starting over with the driver for my device, it worked... Good luck! I'll see what I can find if you write back with your device info.

[DRIVERS] Latest HTC Drivers [4.2.0.001]

Latest HTC Drivers
Latest HTC Drivers extracted from HTC Sync v3.3.21 and HTC Sync Manager v2.0.61.0
Latest Driver Version (HTC Sync): 4.0.1.001
Latest Driver Version (HTC Sync Manager): 4.2.0.001
BMP Drivers are the same for both sets of drivers.
For those who don't want to have to download 120 some MB of bloatware called HTC Sync
Instructions:
Determine if your system is 32-bit or 64-bit
Download the BMP Driver for your OS type (x86 version if on 32-bit, x64 if on 64-bit)
Download the newest HTCDrivers file (choose either the "EXE" or "MSI" driver file, but not both)
Disable any antivirus program(s) present
Run both files downloaded above (the BMP.msi and the HTCDriver file)
Re-enable your antivirus program(s)
Click to expand...
Click to collapse
Links
ALL DRIVER FILES: www.mediafire.com/?o10b16j5b3r3o
OEM SETUP FILES: www.mediafire.com/?1rwmleoe17akd
Updated on 6.6.13
HTCDriver_4.2.0.001.exe
SyncManager_2.0.61.0.exe
Updated on 4.23.13
HTCDriver_4.1.0.001.msi
HTCDriver_4.1.0.001.exe
HTCPluginChecker.exe
HTCSync_3.3.21.exe
SyncManager_2.0.53.0.exe
SyncManager_2.0.53.0_STRIPPED.exe
Updated on 4.02.13
RemoveOldHTCDriver3.exe (packaged in HTC Sync Manager v2.0.41.0)
Removed duplicate x86 BMP Driver
Updated instructions with link to determine if on 32-bit or 64-bit
Updated on 3.31.13
HTCDriver_4.0.1.002.exe
HTCDriver_4.0.1.002.msi
IPTInstaller_4.0.8.msi
Updated on 3.6.13
HTC_BMP_USB_Driver_x86_1.0.5375.msi
HTC_BMP_USB_Driver_x64_1.0.5375.msi
HTCDriver_4.0.1.001.exe
HTCDriver_4.0.1.001.msi
Updated on 11.28.12
HTC BMP USB Driver_x86.msi DELETED: Turned out to be the same 1.0.5375 as above. Download from link above.
HTCDriver_3.0.0.023.msi
Click to expand...
Click to collapse
------------
MD5 CHECKSUMS
Sometimes downloading from the internet can yield a corrupt download. To prevent this, make sure you always check the md5 checksum (also known as "md5sum") of the file. This method verifies the digital integrity of the file by verifying its digital signature with the MD5 algorithm.
After you download each file, make sure to check that the md5sum matches what is given.
Code:
[LIST]
[*]25912deacc5d55528e223ec7b99705cc [B]*HTCDriver_3.0.0.023.msi[/B]
[*]220c41f3b03f42190899db8cb081b5c6 [B]*HTCDriver_4.0.1.001.exe[/B]
[*]a578d837343fe2542ecf405a630d46a0 [B]*HTCDriver_4.0.1.001.msi[/B]
[*]8223ec1c2aa71503b431a0daabb23154 [B]*HTCDriver_4.0.1.002.exe[/B]
[*]4dfbd4ae8662124d06e0a04db2065069 [B]*HTCDriver_4.0.1.002.msi[/B]
[*]bf24b0adc2f792ee4180ca545e4b60a0 [B]*HTC_BMP_USB_Driver_x32_1.0.5375.msi[/B]
[*]7b461095d56f9a6814d8f3e14cac0859 [B]*HTC_BMP_USB_Driver_x64_1.0.5375.msi[/B]
[*]96e6d181192a995214493a6828e4287d [B]*IPTInstaller_4.0.8.msi[/B]
[*]92bd34ec7787e631231c68aba392b6e7 [B]*RemoveOldHTCDriver3.exe[/B]
[*]f281d8994ab9f1315828ac2226a9bb75 [B]*HTCDriver_4.1.0.001.exe[/B]
[*]ed6d5fc5cc7dcca653f7a0beab01035d [B]*HTCDriver_4.1.0.001.msi[/B]
[*]96589c02be46fd7b85160d5b15f4c88a [B]*HTCPluginChecker.exe[/B]
[*]36ba2c8627ba18c6540bfa25be3b67fc [B]*HTCSync_3.3.21.exe[/B]
[*]a356e5c828c7cb3869dc67058e5bbc2c [B]*SyncManager_2.0.53.0.exe[/B]
[*]da1e40e478725d3e829243e84043d21f [B]*SyncManager_2.0.53.0_STRIPPED.exe[/B]
[/LIST]
Click to expand...
Click to collapse
How to check the md5sum of a file:
Windows:
For windows you need to download the md5sum binary. I recommend the one from my dev-host.
After that, copy the file you're trying to verify to the directory where where you downloaded the "md5sum.exe"
Once that is finished, do SHIFT+RIGHT CLICK (inside the folder window) and choose "Open command window here"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then type the following ("fileNameHere" must include the extension):
Code:
md5sum fileNameHere
That will output a hash, which you can compare to the ones above.
Linux: No need to download anything, md5sum binaries are included in all distros, as far as I know.
Open a terminal and type the following ("fileNameHere" must include the extension):
Code:
$ cd path/to/download/folder
$ md5sum fileNameHere
Two important notes:
This method can be used with any files you download, as long as the download site (or the dev themself) provides the correct md5sum.
If any of the digits do not match exactly, you need to download the file again.

Extracted x32 BMP Driver and added to OP
HTC_BMP_USB_Driver_x32_1.0.5375.msi​

Do I need to uninstall any old version first (from older Sync)?

Interesting, I found a HTC Driver Installer 4.0.1.002 in my machine.

Re: [DRIVERS] Latest HTC Drivers [v4.0.1.001]
RayYung said:
Interesting, I found a HTC Driver Installer 4.0.1.002 in my machine.
Click to expand...
Click to collapse
Are you sure? If you have the (htc sync) exe can you upload it somewhere and give me the link?
I heard that the drivers were updated as well, and I've literally redownloaded HTC Sync about 50 times to try and update this, with no luck.

CNexus said:
Are you sure? If you have the (htc sync) exe can you upload it somewhere and give me the link?
I heard that the drivers were updated as well, and I've literally redownloaded HTC Sync about 50 times to try and update this, with no luck.
Click to expand...
Click to collapse
This is what I have(see attached), I am still trying to figure out where it come from...
(I uninstalled and re-install three different versions of HTC Sync multiple time coz my HOX is "unknown" in device manager...)
I extract every exe I have but no luck, will let you know once I find it...

RayYung said:
This is what I have(see attached), I am still trying to figure out where it come from...
(I uninstalled and re-install three different versions of HTC Sync multiple time coz my HOX is "unknown" in device manager...)
I extract every exe I have but no luck, will let you know once I find it...
Click to expand...
Click to collapse
OK, I uninstall all version and install them one by one, HTC Driver Installer 4.0.1.002 come with HTC Sync Manager 2.0.41.0. But can't find it in the exe, will play with it more tomorrow...

Updated OP with IPTInstaller and Drivers version 4.0.1.002
Updated on 3.31.13
HTCDriver_4.0.1.002.exe
HTCDriver_4.0.1.002.msi
IPTInstaller_4.0.8.msi
Click to expand...
Click to collapse

Updated OP with another link; some cleaning up in OP as well.
Updated on 4.02.13
RemoveOldHTCDriver3.exe (packaged in HTC Sync Manager v2.0.41.0)
Removed duplicate x32 BMP Driver
Updated instructions with link to determine if on 32-bit or 64-bit
Click to expand...
Click to collapse

Updated OP with md5sum how-to and checksums.

Have updated all drivers per above but I get a constant error "There is a problem with MTP driver"
Device manager says "The installation failed because a function driver was not specified for this device instance"
Driver update always says it cannot find a driver automatically, when I try to install drivers manually it says the driver is already up to date and does not need to be changed
Any ideas?
WP7 64-bit OS

Go to Devices and Printers > Your phone > Right click the icon > Properties > Edit details / Change settings (or something similar) > uninstall driver (THEN UNPLUG PHONE)
Then go to Control Panel > All Programs > Uninstall everything that has HTC and try again.
These drivers have worked for me upon several reinstalls of Win7 x64 on my laptop, so there's just something interfering with it on your end. I've also gotten several reports of it working for other people on their Win7 x64

CNexus said:
Go to Devices and Printers > Your phone > Right click the icon > Properties > Edit details / Change settings (or something similar) > uninstall driver (THEN UNPLUG PHONE)
Then go to Control Panel > All Programs > Uninstall everything that has HTC and try again.
These drivers have worked for me upon several reinstalls of Win7 x64 on my laptop, so there's just something interfering with it on your end. I've also gotten several reports of it working for other people on their Win7 x64
Click to expand...
Click to collapse
i am on Windows 8 and no way i can make the computer recognize the phone, keep telling me USB device not recognized and on properties i have HTC with the question mark on it?

CNexus said:
Go to Devices and Printers > Your phone > Right click the icon > Properties > Edit details / Change settings (or something similar) > uninstall driver (THEN UNPLUG PHONE)
Then go to Control Panel > All Programs > Uninstall everything that has HTC and try again.
These drivers have worked for me upon several reinstalls of Win7 x64 on my laptop, so there's just something interfering with it on your end. I've also gotten several reports of it working for other people on their Win7 x64
Click to expand...
Click to collapse
Afraid I still definitely have a problem with the MTP driver on one PC (not all my PCs).
HTC support logged in remotely to my PC but were unable to fix it: they have escalated the problem to their technical team - I hope to have a response next week and will post when (if) resolved.

Anyone able to get the drivers working in fastboot mode on Windows 8 ?

appelflap said:
Anyone able to get the drivers working in fastboot mode on Windows 8 ?
Click to expand...
Click to collapse
i managed to do all the process using another laptop where there were no driver installed, is a window 8 and worked fine, no i try to personalize the phone and will let you know

melando said:
Afraid I still definitely have a problem with the MTP driver on one PC (not all my PCs).
HTC support logged in remotely to my PC but were unable to fix it: they have escalated the problem to their technical team - I hope to have a response next week and will post when (if) resolved.
Click to expand...
Click to collapse
Cool. Let me know, maybe some other drivers are interfering woth the HTC drivers

For those having issues with Windows 8 drivers, look here

KidCarter93 said:
For those having issues with Windows 8 drivers, look here
Click to expand...
Click to collapse
Thanks a million. Going tot try these drivers out.

Bump

[OFFLINE UPDATE] WP8.1 To W10 Mobile [ATT] [Verizon] [T-Mobile] (Build 10586.107)

Prerequisites:
Your PC must be at least Windows 7 Service Pack 1, although you must install every Visual C++ Redistributable Runtime and the Windows Device Recovery Tool.
Your Phone OS version must be at least 8.10.14219.341 or newer. If not, please update it using the windows insider app.
Have registered your device as a developer with the WP SDK.
Remove pin lock and turn off reset protection before the update procedure.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:fingers-crossedlease follow this guide at your own risk as I am not responsible for bricked devices, dead SD cards or thermonuclear war:crying:.
Instructions:
1. Backup Your device.
2. Download Iutool (WP_CPTT_NT-x86-fre.msi) from the attachments section and install it. The default install directory will be
Code:
C:\Program Files (x86)\Windows Kits\10\Tools\bin\i386
3. Download the M8.Rar that reflects your Carrier and extract the contents to C:\ on your PC.
M8ATT
M8Verizon
M8TMobile
Code:
C:\M8ATT
Code:
C:\M8Verizon
Code:
C:\M8TMobile
4. Open Command Prompt as administratior and change directory to where Iutool is installed.
Code:
cd C:\Program Files (x86)\Windows Kits\10\Tools\bin\i386
5. Plug your M8 into your PC and check to see if Iutool discovers your device by typing
Code:
iutool -l
If your device appears then you are ready to continue
If you met error 80070490 when executing iutool -l then disconnect your device and remove it from the Devices & Printers section of Control Panel
6. Assuming you extracted the correct zip into C:\ you are either going to type
Code:
iutool -V -p C:\M8ATT
Code:
iutool -V -p C:\M8Verizon
Code:
iutool -V -p C:\M8TMobile
That command will push the update to your device and it will prepare for the installation! Once the update is ready, take it! You'll want to find something to occupy your time as the process will take 40 minutes.
8. Once booted into W10 open Settings and navigate to the "For Developers" menu and enable Developer Mode.
9. Download and install Interop-Tools from it's respected thread and follow the For All other OEM Devices section to Interop/Cap Unlock your M8 if you had planned on doing so.
Interop-Tools https://forum.xda-developers.com/wi...app-interop-tools-versatile-registry-t3445271
10. Use any method that you know to modify your model(DeviceTargetingInfo) to a supported W10 Mobile Device
11. Now enable Windows insider preview builds and set to either slow or release ring.
12. Go into phone update and search for update. You should be brought to build 14393 or later. Updating to this build will fix critical issues/bugs you met earlier.
13. I also recommend a factory reset after all updates as that will reset Registry values to defaults and fix other things as well.
A HUGE thanks to @hikari_calyx for the Offline Update package V4.1 that he had put together over on the Windows 10 Mobile forums!
Another HUGE thanks to @gus33000 for Interop-Tools!​

RECOMMENDED TO ADD:
1. If you met 80070490 error when executing iutool -l, disconnect your phone, and delete your phone in Device & Printers (Run "control printers") and delete your phone listed on it, then reconnect your phone again.
2. You can also install Mobile Enterprise provisioned package in order to get 10586.753. This provisioned package will be available with my Offline Update Package V4.
3. I also recommended to modify PhoneHardwareVariant to RM-1045 if you are going to modify to L930. You should also modify PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB.
4. Turn off reset protection before update procedure.

hikari_calyx said:
RECOMMENDED TO ADD:
1. If you met 80070490 error when executing iutool -l, disconnect your phone, and delete your phone in Device & Printers (Run "control printers") and delete your phone listed on it, then reconnect your phone again.
2. You can also install Mobile Enterprise provisioned package in order to get 10586.753. This provisioned package will be available with my Offline Update Package V4.
3. I also recommended to modify PhoneHardwareVariant to RM-1045 if you are going to modify to L930. You should also modify PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB.
4. Turn off reset protection before update procedure.
Click to expand...
Click to collapse
PhoneHardwareVariant to RM-1045 if you are going to modify to L930? does this affect anything?
PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB? will this help service? i had not changed these values before updating myself.

AnierinB said:
PhoneHardwareVariant to RM-1045 if you are going to modify to L930? does this affect anything?
PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB? will this help service? i had not changed these values before updating myself.
Click to expand...
Click to collapse
In some case, without modifying them, you can't search any update.

I successfully installed WP 10.0.14393.953 in my HTC M8 and everything seems ok but the in-call volume that is very very low, quite inaudible. Any ideas? Thanks, ALe

I got the following error after pushing the contents of the M8ATT folder onto my device:
[1] Transferring files complete: 37 files
[1] Installation failed (HRESULT = 0x80004005)
[1] Failed (0x80004005)
ERROR: 0x80004005
Command failed. (HRESULT = 0x80004005)
Is this bad?
---------- Post added at 06:50 AM ---------- Previous post was at 06:30 AM ----------
Cashdog53 said:
I got the following error after pushing the contents of the M8ATT folder onto my device:
[1] Transferring files complete: 37 files
[1] Installation failed (HRESULT = 0x80004005)
[1] Failed (0x80004005)
ERROR: 0x80004005
Command failed. (HRESULT = 0x80004005)
Is this bad?
Click to expand...
Click to collapse
Never mind. Fixed the problem by removing my SD card, and restarting the phone I think...

zagreo said:
I successfully installed WP 10.0.14393.953 in my HTC M8 and everything seems ok but the in-call volume that is very very low, quite inaudible. Any ideas? Thanks, ALe
Click to expand...
Click to collapse
ThIs is normal as I've encountered the same issue.
Bugs I know of:
Front facing camera sometimes causes reboot (switching from back in most cases)
Sound will sometimes only go through one speaker (works itself out but happens every now and then)
Flashlight toggle in quick settings has a long delay and sometimes doesn't work at all
Dot view doesn't work (but I personally delete the "extras" apps as the update process somehow made that possible for me)
Other than all that I'm pretty amazed at the way this devices handles the OS... every time I've gone back to 8.1 I'd instantly regret it after the setup

Hi so I tried installing Interops on my WP 10 HTC but for whatever reason it doenst let me install stating i dont have 10.0.14393.953 or higher but if i recall i have 10.0.15xxx.xxx Im not home so i cannot check the actual numbers.

Cokefrevr said:
Hi so I tried installing Interops on my WP 10 HTC but for whatever reason it doenst let me install stating i dont have 10.0.14393.953 or higher but if i recall i have 10.0.15xxx.xxx Im not home so i cannot check the actual numbers.
Click to expand...
Click to collapse
Are you trying to install interop tools via the store? From what I can recall installing the pre release via device hub worked on all builds for me

Cashdog53 said:
I got the following error after pushing the contents of the M8ATT folder onto my device:
[1] Transferring files complete: 37 files
[1] Installation failed (HRESULT = 0x80004005)
[1] Failed (0x80004005)
ERROR: 0x80004005
Command failed. (HRESULT = 0x80004005)
Is this bad?
---------- Post added at 06:50 AM ---------- Previous post was at 06:30 AM ----------
Never mind. Fixed the problem by removing my SD card, and restarting the phone I think...
Click to expand...
Click to collapse
Everything work out?

AnierinB said:
Are you trying to install interop tools via the store? From what I can recall installing the pre release via device hub worked on all builds for me
Click to expand...
Click to collapse
Yea trying to install from the store, sorry for being stupid really tired but device hub?

Cokefrevr said:
Yea trying to install from the store, sorry for being stupid really tired but device hub?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=71000190&postcount=607
Download arm dependencies and arm interop tools. Extract and install dependencies one by one via file manager before installing interop tools appx.
Oh and it's called the device portal... here's a link to info on that https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile

AnierinB said:
https://forum.xda-developers.com/showpost.php?p=71000190&postcount=607
Download arm dependencies and arm interop tools. Extract and install dependencies one by one via file manager before installing interop tools appx.
Oh and it's called the device portal... here's a link to info on that https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile
Click to expand...
Click to collapse
Thanks, although it seems to be auto closing, then if i open it again it stays loading and auto closes again.

I've got the same problem installing interop tools i've install the dependencies and the appxbundle but when i try to open the program on the phone it only show a logo for a few seconds and go back to the main screen. Is interop tools the only way to modify the devicetargetinfo ? Please advice.

Cokefrevr said:
Thanks, although it seems to be auto closing, then if i open it again it stays loading and auto closes again.
Click to expand...
Click to collapse
rayxanber said:
I've got the same problem installing interop tools i've install the dependencies and the appxbundle but when i try to open the program on the phone it only show a logo for a few seconds and go back to the main screen. Is interop tools the only way to modify the devicetargetinfo ? Please advice.
Click to expand...
Click to collapse
https://forum.xda-developers.com/wi...app-interop-tools-versatile-registry-t3445271
Follow the for all other OEM Device section. Interop tools has changed a bit since I last used the device.
And yes that reminds me.. In worst case you can't get interop tools to work I'm afraid you'll have to change it before you do the offline update via The modified preview for developer's.. But no worries as the WDRT tool can bring you back to 8.1 NP.
Besides that.. How's the experience with w10 on the m8 for you guys?

AnierinB said:
[*]Your PC must be at least Windows 7 Service Pack 1, but you must install every Visual C++ Redistributable Runtime and Windows Device Recovery Tool. Windows 8/8.1/10 are also acceptable.
Click to expand...
Click to collapse
I found that only 2013 was necessary, and specifically the x86 (not x64, even if you have a 64bit computer and 64bit OS) as iutool is a 32bit binary. This link should also be handy for anyone wanting to install all the Visual C redistributables.
AnierinB said:
(If you met error 80070490 when executing iutool -l, disconnect your phone, and delete your phone from Device & Printers section of control panel. Then reconnect your phone again)
Click to expand...
Click to collapse
This didn't work for me on my main computer. Even after I removed ALL windows devices. I got out a burner laptop, installed Win10 fresh and set up the necessary tools and only then did iutool work for me.
AnierinB said:
Besides that.. How's the experience with w10 on the m8 for you guys?
Click to expand...
Click to collapse
Once I can figure how to get Win10 to update, I'll let you know.
[EDIT] WOW, I just found https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile, that I can upload the app using nothing but a browser. All this time I was thinking I'd have to use the USB cable and find yet another deployment tool.. but I still get the same problem as Cokefrevr and rayxanber in that it always auto-closes or crashes.
[EDIT2] Ok, finally found out that anything beyond the 1.9 beta crashes in this old windows build. At least the 1.9 beta runs... now I need to figure out what this cryptic statement means in terms of steps:
AnierinB said:
11. Use any method that you know to modify your model(DeviceTargetingInfo) to a supported W10 Mobile Device
Click to expand...
Click to collapse
[EDIT3] I found https://windowsinsiderbits.blogspot.com/2017/03/upgrading-unsupported-windows-phone-81.html which led me to the steps:
1. Edit registry HKLM/SYSTEM/Platform/DeviceTargetingInfo changing PhoneManufacturerModelName to RM-1105 and PhoneModelName to "Lumia 950" (taken from http://www.lumiafirmware.com/ )
2. Run the Windows Insider app, select the Insider Slow release (it should automatically reboot)
3. Check for updates in the Settings > Update & security > Phone update
Now I'm finally updated to Version 1607 OS Build 10.0.14393.448
[EDIT4] And now that it's on the current windows version, the Interop Tools from the store can run... but it needs some kind of extensions which I think are what is referenced in the 'Other Device' section, but needs Interop Tools to run before extensions can be side-loaded? That doesn't make much sense. I guess I'm fine with my device saying HTC Lumia 950 until Interop works or I find a better simple registry editor without so many complicated dependencies.
[EDIT5] Looks like the RC beta from the originally linked thread works on this version. I have to say, the self-web-host to install applications is by far the easiest way to side-load apps. I think the only thing I miss by going up to Win10 is the dotview. :crying: I hope some awesome developer makes a dot-view addition to Win10. Oh... looks like it's downloading the 1703 version now...

reukiodo said:
I found that only 2013 was necessary, and specifically the x86 (not x64, even if you have a 64bit computer and 64bit OS) as iutool is a 32bit binary. This link should also be handy for anyone wanting to install all the Visual C redistributables.
This didn't work for me on my main computer. Even after I removed ALL windows devices. I got out a burner laptop, installed Win10 fresh and set up the necessary tools and only then did iutool work for me.
Once I can figure how to get Win10 to update, I'll let you know.
[EDIT] WOW, I just found https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile, that I can upload the app using nothing but a browser. All this time I was thinking I'd have to use the USB cable and find yet another deployment tool.. but I still get the same problem as Cokefrevr and rayxanber in that it always auto-closes or crashes.
[EDIT2] Ok, finally found out that anything beyond the 1.9 beta crashes in this old windows build. At least the 1.9 beta runs... now I need to figure out what this cryptic statement means in terms of steps:
[EDIT3] I found https://windowsinsiderbits.blogspot.com/2017/03/upgrading-unsupported-windows-phone-81.html which led me to the steps:
1. Edit registry HKLM/SYSTEM/Platform/DeviceTargetingInfo changing PhoneManufacturerModelName to RM-1105 and PhoneModelName to "Lumia 950" (taken from http://www.lumiafirmware.com/ )
2. Run the Windows Insider app, select the Insider Slow release (it should automatically reboot)
3. Check for updates in the Settings > Update & security > Phone update
Now I'm finally updated to Version 1607 OS Build 10.0.14393.448
[EDIT4] And now that it's on the current windows version, the Interop Tools from the store can run... but it needs some kind of extensions which I think are what is referenced in the 'Other Device' section, but needs Interop Tools to run before extensions can be side-loaded? That doesn't make much sense. I guess I'm fine with my device saying HTC Lumia 950 until Interop works or I find a better simple registry editor without so many complicated dependencies.
[EDIT5] Looks like the RC beta from the originally linked thread works on this version. I have to say, the self-web-host to install applications is by far the easiest way to side-load apps. I think the only thing I miss by going up to Win10 is the dotview. :crying: I hope some awesome developer makes a dot-view addition to Win10. Oh... looks like it's downloading the 1703 version now...
Click to expand...
Click to collapse
Glad you got it working.. Haven't logged in to xda in a while because i'm using micro g on my Android device so sorry about the absence of help. How you liking it so far? HTC should have supported this huh? p.s lumia 735 works best for device spoofing.. 950 is unnecessary

I'm curious, which phone should I change it to in the registry, to receive updates? To make sure it doesn't break?
Also I'm using Interop Tools 1.9 since apparently, everything after that crashes, and I can't unlock Interop/cap it keep turning off. Do you have any pointers to what I should do?

nar001 said:
I'm curious, which phone should I change it to in the registry, to receive updates? To make sure it doesn't break?
Also I'm using Interop Tools 1.9 since apparently, everything after that crashes, and I can't unlock Interop/cap it keep turning off. Do you have any pointers to what I should do?
Click to expand...
Click to collapse
What carrier do you have? I used an ATT varient and before using the offline update I used the custom preview for developers method to change my device to a lumia 735 on wp 8.1 then did the offline update because interop tools kept failing for me at the time as well. if I remember correctly, you can also use interop tools to change the device targeting info but nothing else if you can't cap unlock/ interop unlock your device.
And about cap unlocking your device:
Download the NDTK packages and the WPAK utilities
Go to the Interop Unlock section of Interop Tools, and tap the button that says "Enable installing NDTK on any device"
Put the two NDTK cabs in one empty folder on your PC
Open a command prompt as administrator and make sure you're in the directory where the iutool executable is located from the WP(AK) zip
run "iutool -V -p "<fulllocationwherethetwondtkpackagesarestored >" with your phone connected into the PC
if iutool throws an error, please unplug your device, go to the control panel, devices and printer, select your phone, should be ghosted, click
on uninstall device, and then replug the device and wait for it to reinstall. If you still have issues, run GETDULOGS from the same CMD prompt, and post the cab you get along with a message in this thread
When the installation is finished, open Interop Tools, go to the Interop Unlock section, and tap restore the original manufacturer info button.

AnierinB said:
What carrier do you have? I used an ATT varient and before using the offline update I used the custom preview for developers method to change my device to a lumia 735 on wp 8.1 then did the offline update because interop tools kept failing for me at the time as well. if I remember correctly, you can also use interop tools to change the device targeting info but nothing else if you can't cap unlock/ interop unlock your device.
And about cap unlocking your device:
Download the NDTK packages and the WPAK utilities
Go to the Interop Unlock section of Interop Tools, and tap the button that says "Enable installing NDTK on any device"
Put the two NDTK cabs in one empty folder on your PC
Open a command prompt as administrator and make sure you're in the directory where the iutool executable is located from the WP(AK) zip
run "iutool -V -p "<fulllocationwherethetwondtkpackagesarestored >" with your phone connected into the PC
if iutool throws an error, please unplug your device, go to the control panel, devices and printer, select your phone, should be ghosted, click
on uninstall device, and then replug the device and wait for it to reinstall. If you still have issues, run GETDULOGS from the same CMD prompt, and post the cab you get along with a message in this thread
When the installation is finished, open Interop Tools, go to the Interop Unlock section, and tap restore the original manufacturer info button.
Click to expand...
Click to collapse
Am I supposed to do all this on my computer, or the phone? And I don't have the "NDTK" button on Interop 1.9 on my M8 (It's the AT&T version, if that helps)

[TOOL] MobyDroid (Android Device Manager for Linux, Windows and MacOS)

Hello every one,
MobyDroid is a simple and cross-platform Android Devices Manager.
It runs on any operating system with Java support (Mac OS X, Windows, Linux, BSD, Solaris...).
THIS IS JUST A BETA RELEASE !
I have been running linux from while now. And what I noticed is there is no GUI Android Devices Manager until now (QtADB didn't work for me).
Basicly I kept using ADB command line and kept waiting for someone to make something or some alternatives.
Some day a friend of mine kept complaining about the same problem. After that, I decided to make a simple Apk installer with a graphical user interface. And something lead to another.
And I wanted to share it for any one having the same problem.
So here it is !
Prerequisites
Java Runtime Environment (JRE) 1.8 or later
ADB
BETA
THIS IS JUST A BETA RELEASE !
So you should expect a ton of bugs or crash issues.
if you encounter an issue or have a great ideas please file an issue.
Download
You can download from here.
Authors
Bilux ([email protected])
Link
MobyDroid
https://github.com/ibilux/MobyDroid
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ibilux said:
Hello every one,
MobyDroid is a simple and cross-platform Android Devices Manager.
It runs on any operating system with Java support (Mac OS X, Windows, Linux, BSD, Solaris...).
THIS IS JUST A BETA RELEASE !
I have been running linux from while now. And what I noticed is there is no GUI Android Devices Manager until now (QtADB didn't work for me).
Basicly I kept using ADB command line and kept waiting for someone to make something or some alternatives.
Click to expand...
Click to collapse
this is kinda long term general issue, most of manufacturers had their own app, samsung, htc, lg, and there is no general solution android manager, so this could be a start of a big project. good luck
Sent from my ONE A2005 using Tapatalk

chxei said:
this is kinda long term general issue, most of manufacturers had their own app, samsung, htc, lg, and there is no general solution android manager, so this could be a start of a big project. good luck
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Thank you very much.
As a start, I'm just trying to give back to the XDA and open source community.

Nice work keep up ???

@ibilux
Hi, is this project discontinued?
Any plans for future development?
Thanks!

EuK_V said:
@ibilux
Hi, is this project discontinued?
Any plans for future development?
Thanks!
Click to expand...
Click to collapse
I just didn't have anything to add.
But, if you have an issue or feature, I'll look into it.

ibilux said:
I just didn't have anything to add.
But, if you have an issue or feature, I'll look into it.
Click to expand...
Click to collapse
Thank you, for your reply!
First of all I'd like to say that I am interested more in the "File manager" function of the app. And if you don't mind I have some suggestions:
I am faced with the following: when I start the app I don't have full root access, though "su root permissions" is checked in settings. I can browse the root directory, but cannot create or delete any file or folder. There is a workaround: if I start adb as root from my Ubuntu terminal executing:
adb root
after that I have full root access to my phone. It works this way, but I think since Mobydroid is a gui to adb, it should be able to start adb as root.
Also it would be great if the app could start adb via wifi (I don't know maybe add an option to choose how to connect via usb or network. Now if I start adb via network in terminal executing:
adb connect 192.168.0.101:5555
Mobydroid then works well. Again I need to make some actions outside the app before I start it. (BTW IP address of a device is just an example)
Another thing I'd like to say is that Mobydroid when viewing a device shows symlinks to folders as files and you cannot enter them. On the side of Ubuntu it works well, symlinks to folders work as folders and you can enter them. See my screenshot.
And it would be great to have sort options like "folders first" to sort folders before files and to sort dot folders (.folder) after regular folders and dot files after regular files. Like it works in most linux FMs.
Hope this wouldn't be too overwhelming...
Thanks!

EuK_V said:
Thank you, for your reply!
First of all I'd like to say that I am interested more in the "File manager" function of the app. And if you don't mind I have some suggestions:
I am faced with the following: when I start the app I don't have full root access, though "su root permissions" is checked in settings. I can browse the root directory, but cannot create or delete any file or folder. There is a workaround: if I start adb as root from my Ubuntu terminal executing:
adb root
after that I have full root access to my phone. It works this way, but I think since Mobydroid is a gui to adb, it should be able to start adb as root.
Also it would be great if the app could start adb via wifi (I don't know maybe add an option to choose how to connect via usb or network. Now if I start adb via network in terminal executing:
adb connect 192.168.0.101:5555
Mobydroid then works well. Again I need to make some actions outside the app before I start it. (BTW IP address of a device is just an example)
Another thing I'd like to say is that Mobydroid when viewing a device shows symlinks to folders as files and you cannot enter them. On the side of Ubuntu it works well, symlinks to folders work as folders and you can enter them. See my screenshot.
And it would be great to have sort options like "folders first" to sort folders before files and to sort dot folders (.folder) after regular folders and dot files after regular files. Like it works in most linux FMs.
Hope this wouldn't be too overwhelming...
Thanks!
Click to expand...
Click to collapse
Root and wireless connection features has been implemented in version v0.4.
I'll implement symbolic links and folders order in next release.

Thanks. Works good, but it can't sort dirs/files by name or date.

sorry but it doesn't work

@rifkican, enable adb in developer settings.

Is this still working? I tried to run it but i get this error:
[CheckBinaries] : I: couldn't create file: Read-only file system.

pabekam said:
Is this still working? I tried to run it but i get this error:
[CheckBinaries] : I: couldn't create file: Read-only file system.
Click to expand...
Click to collapse
What platform are u using ? and how did u install MobyDroid ?

ibilux said:
What platform are u using ? and how did u install MobyDroid ?
Click to expand...
Click to collapse
Windows. I downloaded the Standalone version, installed java and run the command over cmd. MobyDroid starts but in the cmd i get the error message. In MobyDroid when i go to the file manager, it doesnt show me any files/folders on my phone

pabekam said:
Windows. I downloaded the Standalone version, installed java and run the command over cmd. MobyDroid starts but in the cmd i get the error message. In MobyDroid when i go to the file manager, it doesnt show me any files/folders on my phone
Click to expand...
Click to collapse
can u provide full log errors.

ibilux said:
can u provide full log errors.
Click to expand...
Click to collapse
how do i do that?