Guys,I am new here. I have a windows phone but nowadays, It is useless. So,I want to convert my windows phone to a android phone. But I cant turn on developer option and usb debugging. I saw a lot of videos and searched a lot of place but I cant find any solution because everywhere I got, They say that there is something called build number and if I press this a several times, It will turn on developer option and then I can turn on usb debugging. But I cant find any. So.guys please help me.
My device information are given below
Phone name>Windows Lumia 535
Operating system>Windows 8.1
Software release>Lumia Denim {I dont know what is it}
English is my second language.So,there is a lot of problem on my writing, Sorry for that.
Thanks in advance.
View attachment 5503205
Hi,
first of all you should update to Windows 10 mobile (there are several threads in here, a tool which allows an offline update without Microsoft sources). Windows 10 mobile gives you the possibilities to turn on developer mode and USB modes.
These standard methods Google or Bing offer you are for Android devices, a Lumia 535 is a Windows device and there are no Android ROMs for Lumia devices providing full functionality.
Don't hesitate to ask via PN, also in a different language. I can answer in DE, FR, IT or HU.
Best regards,
Joachim
Related
Hello everyone,
I am sure this is one of the most often asked questions around here. But I am going to ask anyway because I've not been able to use the solutions provided before and my research elsewhere has not yielded the results I expect.
So here goes. I have a T-Mobile MDA Vario III connected to a new-built Window 7 (Home Premium version) using a USB cable. On connection, Windows detects a new "Generic RNDIS" device and starts downloading the driver for it. From the message on the screen, it seems to have found the driver but fails when it tries to install.
So far I've tried the following:
The Microsoft Solution of Pausing the Windows Update Service, Clearing the %WINDIR%\SoftwareDistribution\Download and %WINDIR%\DataStore\ folders, resuming the service and then re-trying. This does not change the error.
On my mobile, go under Start > Settings > Connections > USB to PC > {Uncheck the only option} - This seems to partially work as Windows 7 now discovers a "Serial" device and promptly installs a "HTC USB Sync" driver for it. But this does not seem to be very useful because I cannot see a new drive or any other signs of a new device being attached (other than under the USB list). Turning ON the unchecked box takes me back to square one.
Uninstalled *everything* and then installed Windows Mobile Device Center v6.1 from Microsoft's site. However, that does not help with the RNDIS as it continues to find a driver, yet is unable to install it
I've tried hard AND soft resetting the device in various combinations with the above options - again, to no use.
Are there any other options that I can try? Any other suggestions are welcome.
thank you in advance..
tropicanapure said:
Hello everyone,
I am sure this is one of the most often asked questions around here. But I am going to ask anyway because I've not been able to use the solutions provided before and my research elsewhere has not yielded the results I expect.
So here goes. I have a T-Mobile MDA Vario III connected to a new-built Window 7 (Home Premium version) using a USB cable. On connection, Windows detects a new "Generic RNDIS" device and starts downloading the driver for it. From the message on the screen, it seems to have found the driver but fails when it tries to install.
So far I've tried the following:
The Microsoft Solution of Pausing the Windows Update Service, Clearing the %WINDIR%\SoftwareDistribution\Download and %WINDIR%\DataStore\ folders, resuming the service and then re-trying. This does not change the error.
On my mobile, go under Start > Settings > Connections > USB to PC > {Uncheck the only option} - This seems to partially work as Windows 7 now discovers a "Serial" device and promptly installs a "HTC USB Sync" driver for it. But this does not seem to be very useful because I cannot see a new drive or any other signs of a new device being attached (other than under the USB list). Turning ON the unchecked box takes me back to square one.
Uninstalled *everything* and then installed Windows Mobile Device Center v6.1 from Microsoft's site. However, that does not help with the RNDIS as it continues to find a driver, yet is unable to install it
I've tried hard AND soft resetting the device in various combinations with the above options - again, to no use.
Are there any other options that I can try? Any other suggestions are welcome.
thank you in advance..
Click to expand...
Click to collapse
use this Driver.... for more details about Use this method only if you have Windows Vista or Windows 7 go to --> http://forum.xda-developers.com/showpost.php?p=3932827&postcount=3
I have an HTC Touch Diamond DIAM100
I'd like to install Android or WM6.5. These forums contain too many information and I can't filter them. That starts with the many HTC models in this forum (MDA, CDMA, ???) I would be glad, if you could help me a little.
1. What Android version is best for my phone?
2a. Does everything work when changing O/S?
2b. Is it faster than WM6.1?
3. Where can I download Android?
4. Where do I find a How To?
5. Where would I find WM6.5?
6. Is it faster then WM6.1 on my phone?
7. Where do I find a How To?
Thanks a lot!
I just installed the Android rom found here: http://forum.xda-developers.com/showthread.php?t=907509
I don't think you'll be able to use it on a daily basis, as it's somewhat emulated (needs Win to run, it's not native...yet), eats the battery way too fast and there are several issues that don't work properly (yet). For example, in my case, the Wi-fi performance is horrible, the speed is somewhere between 5-10KB/s. The developer knows about this and it may be fixed on the next version. Also, connecting to my PC doesn't work, at least on Win 7, because it complains about missing drivers and stuff. I have to turn on USB storage mode to be able to copy files on the device. After turning it off, Android sees the internal storage as empty, and there's no way to fix it unless I reboot the phone.
If you want to install Windows Mobile 6.5, there are plenty of ROMs here and it's easy to do it if your device is security unlocked. Take your time and read the tutorials on the ROM development forum, you'll get it.
hi guys, ive got a quick question for you.
When you put the device in to flashing mode (the black screen with the wee USB cable plugging in to the PC)
what driver is installed? when in that mode you should see a different USB device im guessing something like HD7 or perhaps its code name.
anyhow, if someone tell me that i would be very aprechiative, also if you can tell me which driver set its installed from, for instance, OEM11.inf or perhaps a zune driver set.
use device manager, it could be under portable devices or USB devices or windows phone devices, right click on it and go to properties, then details , im looking for the matching device ID, inf name, inf section, included infs
thanks for your time folks!
I don't have all the driver info, but I know it lists the device as "HTC Shubert."
jelliottz said:
I don't have all the driver info, but I know it lists the device as "HTC Shubert."
Click to expand...
Click to collapse
well thats a start, cheers mate! amazing how 60 odd folk looked at this an didnt want to help, your an example to them all!
thanks again
Perhaps i can find the rest of the info trawling through google using that as a start, but if anyone can provide the INF details and device ID it would make my life that much easier!
was that definitely the name for the device as listed in device manager when the device was in update mode? Im finding info for that as the overall device name but not the friendly name, the friendly name is HD7 which is what would be listed in device manager and is listed when the device is connected to the computer in normal mode.
Basically what im looking in to is what exactly is happening when the HD2 is updated, it obviously doesnt work, im looking to find out exactly why that is.
when the HD2 is made to look like an HD7 it works fine and is listed as an HD7 in device manager, but the moment it goes in to update mode it changes back to a LEO device
Obviously this might not be the whole reason it doesnt work but if i can find out what driver is installed for the update mode with the HD7 i can fiddle with the device IDs in the driver inf file and force that to be used instead of the leo drivers. Now that wont work by its self i dont think but its one less thing that might be behind it not updating.
if that doesnt work than the next step is to compare the registery for both devices, but one thing at a time, and the driver issue is possibly the easiest to fix.
Bit weird here !
Hi
I've been having problems with the 801812c error.
After reading about updating the drivers using device manager, and doing so, (my device was listed as HD7) i found nothing changed and I still couldn't update, so I deleted the drivers, and then re downloaded them.
Suddenly I had loads more drivers, and my device is now listed as Windows Phone 7.
Still won't update though !
Sorry, just my tuppence worth.
Garrickus
sorry, say that again, your HD2 which is normally listed as HD7 or whatever you called it in zune, which in flashing mode is listed as a LEO?
so you updated the LEO driver and got it to use a HD7 driver?
so now in flashing mode its listed in device manager as a HD7 and it doesnt update still?
so putting all that aside you uninstalled the HD7 driver? then when you installed it again windows installed it as a windows phone?
again, this is all in the updating mode? in normal operations you will see a windows phone device and the HD7 device.
or are you using a native HD7? and i got that all wrong?
if you do have an HD7, put it in to flashing mode without the cable attached, turn off the device, then hold down the power button and the camera button, when the device turns on let go of the power button and keep holding the camera button, that should put it in to flash mode.
then in device manager check out what device is listed when you connect it to a USB cable, if you plug it in after you load device manager you iwll see which one pops up. then if you wouldnt mind going to properties and look for the info i asked above?
if you do have a HD7 and are having issues updating try this out
Windows phone support tool
and
ChevronWP7.Updater
install the first one which gives you a guide to updating and the second one does all the updating out of zune by its self.,
comes in two flavours, 32bit and 64,
My phone is updateing now, Here ya go!
i564.photobucket.com/albums/ss85/gloves085/Capture1.png
i564.photobucket.com/albums/ss85/gloves085/Capture2.png
i564.photobucket.com/albums/ss85/gloves085/Capture3.png
Apparently I'm a noob and can't post img links yet, so you can go look yourself, just add the http header to each of the above to make them into links.
cheers, so thats using the zune drive pack, now if anyone has the device ID from the details tab?
i think im running in to a rock on this, bloody LEO keeps getting installed no matter what i do, im starting to think that the update mode must have its own registery or at least a protected section thats identifying it, because no matter what i do i cant keep LEO away, which is intresting because its not apart of the zune driver, its a windows mobile driver.... so where it keeps coming from i dont know
When i put my device into bootloader mode and connect it to the pc, Qualcomm Technologies MSM Windows driver was the one that got downloaded. Also, what OS are you running? you need to download windows mobile device center if you're on vista.Windows 7 should install that driver by default. Anyways, my hardware id listed when connected to zune is :
USB\VID_045E&PID_04EC&REV_0000&MI_00
USB\VID_045E&PID_04EC&MI_00
Also, if you're on xp, get the driver from here http://forum.xda-developers.com/showthread.php?t=408105 , its in the 10th post..
cheers for that, i shall check that out tonight, i had a small amount of progress last night, i have been able to perminantely change the driver installed to a windows phone driver, although its still called LEO for some odd reason, but anyway, so instead of a invaid registry error i now get a timed out error.
So im assuming the driver ive chosen wasnt correct, with out a hardware ID of a HD7 in update mode it gets quite difficult, however ill have a look through that driver you poster a link too, im on win 7 but even if i can locate the ID from that file i may be able to find a working complete driver set i can use.
Hello again.
Windows Phone Developer Registration tool doesn't "see" my device. I've double checked all requisites (.net framework, IpOverUsbSvc, phone listed in file explorer, screen unlocked, correct time, internet connected, etc.) The only issue I can think of is the fact that I still haven't set up a Microsoft account in the phone; but... is this reason enough for the WPDR tool to not even see the phone?
Any hint appreciated. Thanks!
That's probably the cause, yeah. You could try setting up the account to see if it works, then...
Well, I've found something interesting: when I've plugged my device to a virtual machine running win8 and the full WP8 SDK, it recognized my phone instantly. So, now we know that a device that has not been set up with a Microsoft account can be dev-unlocked.
So, definitely there's something wrong with my installation of the hacked SDK-lite. Or maybe the drivers. I have a kind of mess in my laptop because of all the previous drivers and programs for Symbian and my Nokia C7. I still find it hard to get used to the idea that Nokia is not Nokia anymore, but Windows. I have to repeat to myself twice a day: "I don't own a Nokia Lumia, but a Microsoft Lumia".
Thanks for caring, GDTD.
zogoibi said:
Well, I've found something interesting: when I've plugged my device to a virtual machine running win8 and the full WP8 SDK, it recognized my phone instantly. So, now we know that a device that has not been set up with a Microsoft account can be dev-unlocked.
So, definitely there's something wrong with my installation of the hacked SDK-lite. Or maybe the drivers. I have a kind of mess in my laptop because of all the previous drivers and programs for Symbian and my Nokia C7. I still find it hard to get used to the idea that Nokia is not Nokia anymore, but Windows. I have to repeat to myself twice a day: "I don't own a Nokia Lumia, but a Microsoft Lumia".
Thanks for caring, GDTD.
Click to expand...
Click to collapse
Well maybe the virtual Win 8 OS with WP8 SDK recognized your phone because Win 8 has the winusb drivers build in. On Windows 7, you need to install these winusb driver (you normally have a unrecognized device called Windows Phone 8 in the Device Management).
Link to the drivers : http://catalog.update.microsoft.com/v7/site/Search.aspx?q=winusb http://catalog.update.microsoft.com...updateid=90462af8-f533-4522-9ad1-dcc969d94832
Hmm... Well, this is strange. My device seems to be perfectly recognized by the system. Actually, every time I plug the phone in I get a popup window listing it under "devices and printers" with the correct model (RM-892 | Nokia Lumia 925). In the device manager it appears as a Nokia USB device, with no exclamation marks nor any sign of "wrong driver". Yet, the hacked SDK insists in not finding it.
On the other hand, I've tried to install the "winusb" driver you mention, but the link you provide redirects me to somewhere where there is no such driver, and I haven't been able to find a download. In any case, there are at least five copies of winusb.sys in my system...
Don't know what am I doing wrong.
zogoibi said:
Hmm... Well, this is strange. My device seems to be perfectly recognized by the system. Actually, every time I plug the phone in I get a popup window listing it under "devices and printers" with the correct model (RM-892 | Nokia Lumia 925). In the device manager it appears as a Nokia USB device, with no exclamation marks nor any sign of "wrong driver". Yet, the hacked SDK insists in not finding it.
On the other hand, I've tried to install the "winusb" driver you mention, but the link you provide redirects me to somewhere where there is no such driver, and I haven't been able to find a download. In any case, there are at least five copies of winusb.sys in my system...
Don't know what am I doing wrong.
Click to expand...
Click to collapse
You need to visit the website with Internet Explorer. Go to google type "winusb windows phone microsoft update catalog" and go to the site with "catalog.update.microsoft.com" in the URL. If you don't see the download link of the driver type "winusb windows phone" in search. There should be an unrecognized device called "Windows Phone 8" in the device manager (start menu -> My Computer -> right mouse click -> Manage -> Device Manager in left context menu) for this driver to be installed, if not I can't help you further.
Thanks Bruce. I've done what you said and was able to download winusb. It's a .rar package containing two files, winusbcompat.cat and winusbcompat.inf. Now, if I'm not abusing your patience... what do I do with them?
[EDIT] Ok, don't bother. I figured out how. Actually this solved my problem. After properly installing the winusb driver, the WP8 SDK lite by Arnold Vink recognized my phone.
Thanks to everybody who helped me "out".
Now I wonder how could I mark this thread as "solved"...
Hi,
My Nokia Lumia 925 won't respond to anything (NSU, NSU->”My phone does not startup or respond”, Nokia Care Suite->recover phone, volume down + power button,…).
Already leave it charging for several hours. Can’t have any reply from the phone.
Now the phone is kind of dead. Can start it and the only thing I see Is a QHSUSB_DLOAD (Nokia Emergency Connectivity) in PC.
I have tried many things according to internet but i can't get any success windows device recovery tool is also not detecting my phone and it is not listed in it. i have tried thor command also not working it says invalid hex file.
Please help me to recover my phone from QHSUSB_DLOAD mode.
Hello everybody and thanks for accepting me in such a distinguished community!
I recently bought my mi 8 lite, which i must say, is much better than the reviews want it to be due to their own marketing reasons..........
However, as many people already did, I encountered issues when i tried to put it in fastboot mode and moved on, trying to unlock it.
My win 10 pc, only recognizes it as a Composite ADB Device and when i go into fast boot mode, the device manager goes crazy......it cycles and all of a sudden the device is gone in more or less 10 sec. The fast boot mode also dissappears from the device itself! Needless to say that even if the device is shown at the bottom of the PCs device list, it also vanishes in a few seconds!
I have gone through all possible ticks and workarounds but in vain....................!
For those who will ask, yes, i have activated debugging, yes, i have installed the correct (if existing for win 10) drivers and finally yes, I have tried to go in Test Mode, but again.......in vain! My PC denies everything.
So, i was directed by a friend to, and tried through win 7 and after doing everything i should, i got 274hrs from xiaomi untill it unlocks..........
Is there anybody to suggest anything else that i could possibly do, to make these two opponents, become friends???? (i mean win 10 and mi 8 lite)
Is any other co-forumist facing similar issues ?
Are we really able to overcome this or we should go back to 7?
The motherboard of my computer is only win 10 compatible (STUPID ME>>>>) and its is an ASROCK H310-HDV. I have also tried to find any hidden function, with -of course-dissapointing results.:crying::crying::crying:
Thanks in advance for any answer or effort made by anyone in here!
Respectfuly
ioannisthom
I have Windows 10 and driver get on Windows Update.