Develop Bugs

Upgrading your rom on Windows Vista And Windows 7

Follow these instructions and your vista and 7 problems is over...
I used this guide and it works on my phone..
Originally Posted by pvdhelm
To follow this guide please make sure you have a copy of WinRAR installed, I will refer to the Windows Mobile Device Centre as the WMDC for ease of reading. If you do not have the WMDC installed please go here to install it first - http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center-download.mspx
One problem with windows VISTA and 7 is that it uses the new "Windows Mobile Device Centre" and not activesync which we are used to, thus our standard RUU programs will not upgrade our Hermes devices as in windows XP. This guide will show you how to configure VISTA to work just the same as XP with our RUU programs.
For this guide firstly you need to download the new drivers:
Drivers for Windows Vista/7 x32 - http://forum.xda-developers.com/attachment.php?attachmentid=33662&d=1169888879
Drivers for Windows Vista/7 x64 - http://forum.xda-developers.com/attachment.php?attachmentid=33892&d=1170385335
Please note the x64 drivers are unsigned so to use them successfully you must disable driver signing.
Extract the contents to a folder on your desktop, call this folder "AS_DRIVERS". It contains the drivers from activesync which we will use instead of the native VISTA WMDC drivers when the device is in bootloader.
Now you must enter the bootloader on your device, to do this press and hold both the side ok button and the power button then put your stylus into the hole on the bottom of the device, your device will reset and show the red blue green bootloader screen. LEAVE THE DEVICE IN BOOTLOADER MODE and connect it using the USB cable to your VISTA/7 PC.
Now navigate into the WMDC (Start>All Programs>Windows Mobile Device Center) and click on the "connection settings" menu icon
In the connection settings menu untick "allow USB connections" then press OK.
Now exit the WMDC and return to the desktop, go into the start menu and type "Services", this will take you into the local services dialogue and show a list of all services either running or registered with your pc.
Scroll down the list and make sure these services are present:
Windows Mobile-based connectivity
Windows Mobile 2003-based connectivity
If these services are not started then double click each one and set them to Automatic start by clicking the "startup-type" drop-down menu and selecting automatic then click the start button in the same window, apply the setting by pressing OK. Now return back to the desktop again.
Go into the start menu and type "Device Manager" then run, this will take you into the device manager. Click the "+" symbol next to "Mobile Devices" and double click on "HTC USB Sync".
This will bring up the properties of the currently connected device (the hermes in bootloader).
Go to the "Driver" tab and click "Update Driver".
Click "Browse My Computer for Driver Software".
Select "Let me pick from a list...."
Click the "Have Disk" button.
Click "Browse" and navigate to the AS_DRIVERS folder we created earlier.
Vista x32 users select the file "wceusbsh.inf"
Vista x64 users select the file "wceusbshx64.inf"
Then click Open.
click next and the driver will be installed (wait a moment).
Press close and escape back to the desktop now.
Now we must stop the WMDC process, start the task manager by pressing Ctrl+Shift+Escape.
click the WMDC line and click "End Process". In the confirmation window, again press End Process.
Now re-enter the WMDC and re-enable USB connections (click connection settings and tick the box "enable USB connections").
Your RUU programs for HardSPL/Radios/WM6 ROMs should now run as desired once you are synced with WMDC. Since we have updated the driver which vista uses when the device is in bootloader mode.
Can this be made a Sticky please..??

Followed your Steps on Win7 x64 but WMDC doesnt connect do my device although I re-enabled USB connections. Digital Driver signing is disbaled.
No it did work, I just didnt get it
Write this into the wiki plx, really helpful.

All done till the driver installation.
But start from task manager and so on, it's failed to connect.
Am i doing wrong?

Just try to flash, at my side WMDC shows no connections either but flashing is possible.

DasEtwas said:
Just try to flash, at my side WMDC shows no connections either but flashing is possible.
Click to expand...
Click to collapse
After i installed the drivers then i started WMCD and re-enable USB connections and then took out my cable out of the phone then put it back in and it connected..

Method with no install
What I have been doing with Win7 without installing any drivers is
- Put phone in bootloader mode (press power and left OK button while pressing the reset button on bottom)
- Start the RUUWrapper
This of course assumes that you have hardSPLed the phone and select the right options, no autodetect
This is what I have been doing for a while now, I dont recall updating any drivers or activesync/mobile center

coolsva said:
What I have been doing with Win7 without installing any drivers is
- Put phone in bootloader mode (press power and left OK button while pressing the reset button on bottom)
- Start the RUUWrapper
This of course assumes that you have hardSPLed the phone and select the right options, no autodetect
This is what I have been doing for a while now, I dont recall updating any drivers or activesync/mobile center
Click to expand...
Click to collapse
Well this is another option you can do then...should i add this to my post..?

evo 4g windows 8 x64 diag driver

anyone found a diag driver for windows 8 x64 got the usb driver instaled but still cant find a diag driver that works.

djcodine said:
anyone found a diag driver for windows 8 x64 got the usb driver instaled but still cant find a diag driver that works.
Click to expand...
Click to collapse
Whats a diag driver?
Sent from my JB'd speedy

CNexus said:
Whats a diag driver?
Sent from my JB'd speedy
Click to expand...
Click to collapse
its a diagnostic driver. The regular usb driver allows for charging and access to memory on your micro usb, but you need another driver to access the phones internal settings once its put into diagnostic mode. Such as programing the phone for service or updating the prl.

Fix
Found a way to get it working on windows 8 x64 you need to Disable Device Driver Signing and install the HTC Diag drivers for windows 7
Code:
Guide:
1. Mouse over the lower-left corner, then select Settings.
2. Select Change PC Settings.
3. Choose General.
4. Scroll to the bottom and select Restart now under the Advanced startup area.
5. Select Troubleshoot.
6. Select Advanced Options.
7. Select Startup Options.
8. Select Restart.
after you install double click on htc usb modem go to modem tab and your port number should be there

Micromax canvas a1 drivers

Good day,
Can someone please tell me where can i download the drivers for micromax android one, my device is not detected in adb on windows 7?
Thanks,
marc

+100000
Really needed
I have searched for it but not found
Even looked on their official website but it doesn't shows a1 model number

Switch off phone. connect to pc. restart phone. it should install adb. also check if debugging is enabled.

Recognized Noob said:
Switch off phone. connect to pc. restart phone. it should install adb. also check if debugging is enabled.
Click to expand...
Click to collapse
Thanks for replying
But this method is not working with my windows 8.1
Still device is not detected

http://forum.xda-developers.com/can...ial-stock-rom-canvas-a1-t2887150/post55662339
see this thread which has link for drivers.

fyh said:
Thanks for replying
But this method is not working with my windows 8.1
Still device is not detected
Click to expand...
Click to collapse
The thing with windows 8.1 (atleast x64) is that they have changed the way adb drivers are recognized (or not recognized). You might have to:
1) In windows device manager find ADB Driver (or unrecognized hardware corresponding to the adb driver). Right click and select "update driver software".
2) Select "Browse my computer for driver software".
3) Select "Let me pick from a list of device drivers on my computer."
4) With "show compatible hardware" checkbox ticked, two drivers should be shown.
(a) Android ADB Interface. and (b) MTP User Device or Composite USB device.
5) Select (a) above and click Next.
6) Device should now appear.
Always good to use the default adb drivers from google for this. (https://developer.android.com/sdk/win-usb.html)

Hi marcusflint, Sorry to ask the obvious but was USB debugging enabled in developer options?
marcusflint said:
Good day,
Can someone please tell me where can i download the drivers for micromax android one, my device is not detected in adb on windows 7?
Thanks,
marc
Click to expand...
Click to collapse

Unistall the drivers from Device Manger and re-connect the device to PC ! Working gr8 and solves the MTP device recognition issue as well

avinash60 said:
The thing with windows 8.1 (atleast x64) is that they have changed the way adb drivers are recognized (or not recognized). You might have to:
....)
Click to expand...
Click to collapse
ADB driver is installed properly but the MTP isn't installed so I can't enable the mass storage device
I dunno MTP is even required for mass storage device, how come I enable it (I want my computer to detect my SD card which is in this Canvas A1 phone) ?
I am on Windows 8.1 x64
thanks

My problem is that my phone cannot detect the phone drive but it can detect SD card

LOleyer said:
My problem is that my phone cannot detect the phone drive but it can detect SD card
Click to expand...
Click to collapse
then install this.
http://www.micromaxinfo.com/mmx/CanvasA1/AQ4501.zip

OP3 stucks on "Waiting for Device"

Hi,
I try to flash my OP3.
I did first the UNLOCK, that worked with the CMD (Running Windows 10).
My device is Unlocked.
But when I wanna try fastboot flash recovery recovery.img
Or I type then it says waiting for device...
and when i typ: fastboot devices
then if gives nothing.
Yes, I did the OEM unlock in developers options en USB debugging is on.
HELP!

HELP!

Try manual boot into fastboot mode https://youtu.be/7ihDGm3EX_o and then reconnect.

peterk-1 said:
Try manual boot into fastboot mode https://youtu.be/7ihDGm3EX_o and then reconnect.
Click to expand...
Click to collapse
Yes, I did that.
But not working...
Over WiFi it's working, but not with USB.

Oke, ADB is working, but only when the device in ON.
When I does the device in Fastboot.
Than it doesn't work!

HELP!

Oke, I fix it.
Did it in an VM with Windows 7.
Bye.

YourTheBest said:
Oke, I fix it.
Did it in an VM with Windows 7.
Bye.
Click to expand...
Click to collapse
I'm also stuck with this, could briefly tell me how you set up a VM with window's 7 please? I tried with Ubuntu but no luck installing the adb and fastboot? Stuck with no recovery so please help

First Tick OEM unlock and enable usb debugging. And install latest driver

Ajshal said:
First Tick OEM unlock and enable usb debugging. And install latest driver
Click to expand...
Click to collapse
Way past that mate everything is installed, I need to get device to show in fastboot as it's currently not showing

How did you install the driver? do you have windows 8 or above?

daviss101 said:
Way past that mate everything is installed, I need to get device to show in fastboot as it's currently not showing
Click to expand...
Click to collapse
I have same pblm on my LG K10 dude

therightperson_630 said:
How did you install the driver? do you have windows 8 or above?
Click to expand...
Click to collapse
At first it it was called Marshall London bootloader interface but after clicking automatic driver update it then showed as "kedacom bootloader" it does show its in adb mode thou. Is there any Google/Samsung drivers you could link me?
Edit- windows 10

daviss101 said:
At first it it was called Marshall London bootloader interface but after clicking automatic driver update it then showed as "kedacom bootloader" it does show its in adb mode thou. Is there any Google/Samsung drivers you could link me?
Edit- windows 10
Click to expand...
Click to collapse
Ok, not sure if you know about this, but you'll have to install the drivers with signed driver enforcement turned off in windows 10:
Setting > update & security > recovery tab > Advanced start-up (restart now).
On boot up you'll use the function keys to turn off "signed driver enforcement" or something similar.
Then try and install adb/fastboot from this http://forum.xda-developers.com/showthread.php?t=2317790
It should come up with an extra security window during the installation - the driver will be properly installed and you'll be able to use fastboot on your OP3

therightperson_630 said:
Ok, not sure if you know about this, but you'll have to install the drivers with signed driver enforcement turned off in windows 10:
Setting > update & security > recovery tab > Advanced start-up (restart now).
On boot up you'll use the function keys to turn off "signed driver enforcement" or something similar.
Then try and install adb/fastboot from this http://forum.xda-developers.com/showthread.php?t=2317790
It should come up with an extra security window during the installation - the driver will be properly installed and you'll be able to use fastboot on your OP3
Click to expand...
Click to collapse
Okay thanks, I have tried that step but that's when it changed to kedacom via automatic update. I'm confused here I downloaded official oneplus drivers and installed and my phone is perfectly recognised as A300 when its file transfer but when you say install drivers which ones can I download to install manually to remove kedacom? Thanks your time to help but I'm completely stuck

daviss101 said:
Okay thanks, I have tried that step but that's when it changed to kedacom via automatic update. I'm confused here I downloaded official oneplus drivers and installed and my phone is perfectly recognised as A300 when its file transfer but when you say install drivers which ones can I download to install manually to remove kedacom? Thanks your time to help but I'm completely stuck
Click to expand...
Click to collapse
go to device manager and manually uninstall kedacom driver and install minimal adb/fastboot from the link I posted, they'll install the driver automatically

daviss101 said:
Way past that mate everything is installed, I need to get device to show in fastboot as it's currently not showing
Click to expand...
Click to collapse
Just install an FRESH Windows 7.
Install ADB Drivers
Install OP3 drivers
And than open CMD an enter the commands.

YourTheBest said:
Just install an FRESH Windows 7.
Install ADB Drivers
Install OP3 drivers
And than open CMD an enter the commands.
Click to expand...
Click to collapse
How do I get a free version of windows 7 without downloading a cracked ISO?

Huawei Watch 1 not recognized by PC

Hey guys,
I'm trying to root my Huawei watch 1 since a week but with no success. The problem is that I'm not even able to unlock the bootloader.
As stated in the title the watch is not recognized at all by the PC, when I plug it in nothing happens not even a sound. I tried with at least 5 different computers running Windows 10 and one computer running Linux (Ubuntu) and I also tried different cables. In Windows Device Manager there is no sign of the watch and in Ubuntu using "lsusb" all the usb ports are shown as empty.
The watch is working perfectly btw with the latest Wear Os update (2.23.0.238044309) and Android 7.1.1
Is there anything I can do to make the PC recognize the watch ? Or are there any workaround to root the watch / unlock the bootloader ?
Any help would be appreciated

Elixir_ said:
Hey guys,
I'm trying to root my Huawei watch 1 since a week but with no success. The problem is that I'm not even able to unlock the bootloader.
As stated in the title the watch is not recognized at all by the PC, when I plug it in nothing happens not even a sound. I tried with at least 5 different computers running Windows 10 and one computer running Linux (Ubuntu) and I also tried different cables. In Windows Device Manager there is no sign of the watch and in Ubuntu using "lsusb" all the usb ports are shown as empty.
The watch is working perfectly btw with the latest Wear Os update (2.23.0.238044309) and Android 7.1.1
Is there anything I can do to make the PC recognize the watch ? Or are there any workaround to root the watch / unlock the bootloader ?
Any help would be appreciated
Click to expand...
Click to collapse
Have you enabled Developer Options and ADB debugging on your watch? If not, here's how to do it:
Open the Settings menu on the watch.
Scroll to the bottom of the menu. If no Developer Options item is provided, tap About.
Tap the build number 7 times.
From the Settings menu, tap the Developer Options item.
Enable ADB debugging.

JimSmith94 said:
Have you enabled Developer Options and ADB debugging on your watch? If not, here's how to do it:
Open the Settings menu on the watch.
Scroll to the bottom of the menu. If no Developer Options item is provided, tap About.
Tap the build number 7 times.
From the Settings menu, tap the Developer Options item.
Enable ADB debugging.
Click to expand...
Click to collapse
Thank you for the suggestion ! I already did it before and unfortunately it didn't change anything to the fact that the watch isn't recognized by the pc.