I use my Lumia 920 as my main communications device with unlimited internet/tethering from my provider. The Wifi internet sharing feature works fine but is a HUGE drain on the battery. Plus I have concerns about the safety of wifi!
Ideally I wanted to tether to my computer using USB but there doesn't seem to be a lot of information about regarding this with WP8.
Has anyone found a way to do this? Have I been missing something obvious?
I would recommend against using your phone as a router, it will simply die a lot faster due to high hardware stress.
http://microsoftarena.net/usb-tethering-in-windows-phone-7/
WP8 should be similar.
mcosmin222 said:
I would recommend against using your phone as a router, it will simply die a lot faster due to high hardware stress.
http://microsoftarena.net/usb-tethering-in-windows-phone-7/
WP8 should be similar.
Click to expand...
Click to collapse
Thanks for the link, unfortunately, this doesn't work on either the Lumia 900 or 920. Nokia don't seem to have built the option the same as Samsung.
As for the hardware stress, thankfully in the UK we get a 2 year warranty! It'll be up to Nokia to repair/replace if my phone dies using one of the built in features
For the record, wired tethering does work on the Samsung Ativ S. The trick was finding the drivers for my 64-bit PC.
First, you need the Diagnosis app for Samsung phones. This is included, but hidden, on each phone. To access it, type ##634# (##MFG#) into the phone dialer. After it's run once, you can launch it from the Apps list like normal.
Next, to access the USB control, type *#7284# in the numpad that the app displays.
Select "QC RmNetComposite" from the USB Path Control radio button options. This will take the phone out of its default MTP (Media Transfer Protocol) mode, and make it act as a Qualcomm USB modem. The phone will need to reboot when you select this option; let it do so.
When the phone boots up again, it will not appear in Windows Explorer or the Windows Phone app. You'll get a "Found new hardware" notification, but the odds are that the drivers will fail to install automatically. We'll need to install them manually.
To do that, first download the attached ZIP file included with this post. Extract its contents somewhere handy.
Next, open Device Manager. This can be done from the Start menu/screen, or by opening Computer Management, or by typing "devmgr.msc" into Start search or the Run dialog and then hitting Enter. It will require Administrator permissions.
You should see four "Qualcomm composite device" entries that don't have drivers. We only need two, maybe even one, of them. It's possible to tell them apart, but for simplicity's sake I'm just going to tell you to do the next steps for each of them.
Double-click one of those entries, or right-click on it, and select Update Driver.
Choose the "Browse" option, and navigate to the folder you extracted from the ZIP file. You don't have to go any deeper, so long as the "Include Subfolders" option is checked.
Hit Next and, if a warning pops up about unsigned drivers, choose to install anyhow. There is actually a signature; the drivers will work on 64-bit Windows. I don't know what that complaint is about. If it just says that it couldn't find a driver, that's fine; that's one of the two devices we don't need, probably.
Once you have the Qualcomm USB Modem and (possibly) Qualcomm Diagnostics devices installed, you're ready to configure the modem in Windows. To do this, open Network and Sharing Center (or Network Connections in XP) and chose the Create new connection option.
Select a "Dial-up connection". Don't worry; it's neither as slow nor as noisy as a classic modem.
This next part is probably carrier-specific. For T-Mobile US, it was ridiculously easy: type a name for the connection (doesn't matter what), in the place for the number you dial, put "*99#" (without the quotes), and leave the password and username blank.
Try to connect! If it doesn't work, look up the WP7 settings for wired tethering to your carrier; they should be on this forum somewhere.
When you want to get back to normal (MTP) mode on the USB port, just repeat the first three steps but choose "MTP Mode" instead of "QC RmNetComposite" and let the phone reboot again.
Something which may help: I found that the PC would lose data connection while the phone used it. To make the PC's data connection more reliable, turn off data usage on the phone. The modem should still function. There are a ton of other tweaks to configure the modem driver which might also help, but for basic usage, the steps provided here work.
I recommend copying the driver bundle onto your phone (or its SD card) so that if you need to tether a PC that isn't already set up, you can get the drivers without needing Internet access. It's quite possible to copy Zip files to and from the phone via MTP mode.
GoodDayToDie said:
For the record, wired tethering does work on the Samsung Ativ S. The trick was finding the drivers for my 64-bit PC.
First, you need the Diagnosis app for Samsung phones. This is included, but hidden, on each phone. To access it, type ##634# (##MFG#) into the phone dialer. After it's run once, you can launch it from the Apps list like normal.
Next, to access the USB control, type *#7284# in the numpad that the app displays.
Select "QC RmNetComposite" from the USB Path Control radio button options. This will take the phone out of its default MTP (Media Transfer Protocol) mode, and make it act as a Qualcomm USB modem. The phone will need to reboot when you select this option; let it do so.
When the phone boots up again, it will not appear in Windows Explorer or the Windows Phone app. You'll get a "Found new hardware" notification, but the odds are that the drivers will fail to install automatically. We'll need to install them manually.
To do that, first download the attached ZIP file included with this post. Extract its contents somewhere handy.
[*[Next, open Device Manager. This can be done from the Start menu/screen, or by opening Computer Management, or by typing "devmgr.msc" into Start search or the Run dialog and then hitting Enter. It will require Administrator permissions.
You should see four "Qualcomm composite device" entries that don't have drivers. We only need two, maybe even one, of them. It's possible to tell them apart, but for simplicity's sake I'm just going to tell you to do the next steps for each of them.
Double-click one of those entries, or right-click on it, and select Update Driver.
Choose the "Browse" option, and navigate to the folder you extracted from the ZIP file. You don't have to go any deeper, so long as the "Include Subfolders" option is checked.
Hit Next and, if a warning pops up about unsigned drivers, choose to install anyhow. There is actually a signature; the drivers will work on 64-bit Windows. I don't know what that complaint is about. If it just says that it couldn't find a driver, that's fine; that's one of the two devices we don't need, probably.
Once you have the Qualcomm USB Modem and (possibly) Qualcomm Diagnostics devices installed, you're ready to configure the modem in Windows. To do this, open Network and Sharing Center (or Network Connections in XP) and chose the Create new connection option.
Select a "Dial-up connection". Don't worry; it's neither as slow nor as noisy as a classic modem.
This next part is probably carrier-specific. For T-Mobile US, it was ridiculously easy: type a name for the connection (doesn't matter what), in the place for the number you dial, put "*99#" (without the quotes), and leave the password and username blank.
Try to connect! If it doesn't work, look up the WP7 settings for wired tethering to your carrier; they should be on this forum somewhere.
When you want to get back to normal (MTP) mode on the USB port, just repeat the first three steps but choose "MTP Mode" instead of "QC RmNetComposite" and let the phone reboot again.
Something which may help: I found that the PC would lose data connection while the phone used it. To make the PC's data connection more reliable, turn off data usage on the phone. The modem should still function. There are a ton of other tweaks to configure the modem driver which might also help, but for basic usage, the steps provided here work.
I recommend copying the driver bundle onto your phone (or its SD card) so that if you need to tether a PC that isn't already set up, you can get the drivers without needing Internet access. It's quite possible to copy Zip files to and from the phone via MTP mode.
Click to expand...
Click to collapse
this way doesn't work on Windows phone 8 s by htc =(
allesand said:
this way doesn't work on Windows phone 8 s by htc =(
Click to expand...
Click to collapse
my htc 8x dosent work with these code ##634# work but *#7284# doesnt work
these drivers don't seem to work for windows 8.1. Any idea where to get them?
No, sorry. It took me hours of searching to find them for Win7. They should, in theory, be pretty standard drivers; you could maybe find ones that work for an Android phone with the same Qualcomm USB modem and tweak the INF file to get them to install for the Windows phone. I don't have an easy solution, though.
The USB tethering code (*#7284#) doesn't work on my Sprint Atic S Neo. Is this a known issue on the Sprint version of this phone?
For some reason Windows 8 x64 doesn't like these drivers. It complains there isn't a hash for the file. I guess back to test-signing mode....
Diag codes
GoodDayToDie said:
For the record, wired tethering does work on the Samsung Ativ S. The trick was finding the drivers for my 64-bit PC.
First, you need the Diagnosis app for Samsung phones. This is included, but hidden, on each phone. To access it, type ##634# (##MFG#) into the phone dialer. After it's run once, you can launch it from the Apps list like normal.
(deleted text)
I recommend copying the driver bundle onto your phone (or its SD card) so that if you need to tether a PC that isn't already set up, you can get the drivers without needing Internet access. It's quite possible to copy Zip files to and from the phone via MTP mode.
Click to expand...
Click to collapse
Thanks for the drivers
I found it interesting that additional features appeared in Ativ S T899M after diags turned on (##MFG# replies with Odyssey_121205 on diagnostics page) EXCEPT the ability to gain better control of APNs.
With my Ativ S (T899M again) the #7284# does nothing when entered into the diagnostic app.
I was wondering if there is a decent listing of all (or at least some) of the diagnostic codes.
whoops!
ramjetwiebe said:
Thanks for the drivers
I found it interesting that additional features appeared in Ativ S T899M after diags turned on (##MFG# replies with Odyssey_121205 on diagnostics page) EXCEPT the ability to gain better control of APNs.
With my Ativ S (T899M again) the #7284# does nothing when entered into the diagnostic app.
I was wondering if there is a decent listing of all (or at least some) of the diagnostic codes.
Click to expand...
Click to collapse
WHOOPS!
Missed the star in front of the hash when I entered the command. Should have been *#7284# which works just fine. Should have done more than copy and paste.
also found the complete listing by W_O_L_F ( http://forum.xda-developers.com/showthread.php?t=2311626 )
!SPOOHW
ramjetwiebe said:
WHOOPS!
Missed the star in front of the hash when I entered the command. Should have been *#7284# which works just fine. Should have done more than copy and paste.
also found the complete listing by W_O_L_F ( http://forum.xda-developers.com/showthread.php?t=2311626 )
!SPOOHW
Click to expand...
Click to collapse
There's even more things hidden in there that's available by using the native toast launcher in the hacking forum.
I have a Sprint ATIV S Neo and *#7284# does nothing.
However...
##3424# takes me to the proper screen (Micro USB Test).
Still haven't found drivers for 8.1 yet though...
You'll need to use the Native toast launcher to bring it up.
Sent from my Lumia 928 (RM-860) using Tapatalk
GoodDayToDie said:
For the record, wired tethering does work on the Samsung Ativ S. The trick was finding the drivers for my 64-bit PC.
First, you need the Diagnosis app for Samsung phones. This is included, but hidden, on each phone. To access it, type ##634# (##MFG#) into the phone dialer. After it's run once, you can launch it from the Apps list like normal.
Next, to access the USB control, type *#7284# in the numpad that the app displays.
Select "QC RmNetComposite" from the USB Path Control radio button options. This will take the phone out of its default MTP (Media Transfer Protocol) mode, and make it act as a Qualcomm USB modem. The phone will need to reboot when you select this option; let it do so.
When the phone boots up again, it will not appear in Windows Explorer or the Windows Phone app. You'll get a "Found new hardware" notification, but the odds are that the drivers will fail to install automatically. We'll need to install them manually.
To do that, first download the attached ZIP file included with this post. Extract its contents somewhere handy.
Next, open Device Manager. This can be done from the Start menu/screen, or by opening Computer Management, or by typing "devmgr.msc" into Start search or the Run dialog and then hitting Enter. It will require Administrator permissions.
You should see four "Qualcomm composite device" entries that don't have drivers. We only need two, maybe even one, of them. It's possible to tell them apart, but for simplicity's sake I'm just going to tell you to do the next steps for each of them.
Double-click one of those entries, or right-click on it, and select Update Driver.
Choose the "Browse" option, and navigate to the folder you extracted from the ZIP file. You don't have to go any deeper, so long as the "Include Subfolders" option is checked.
Hit Next and, if a warning pops up about unsigned drivers, choose to install anyhow. There is actually a signature; the drivers will work on 64-bit Windows. I don't know what that complaint is about. If it just says that it couldn't find a driver, that's fine; that's one of the two devices we don't need, probably.
Once you have the Qualcomm USB Modem and (possibly) Qualcomm Diagnostics devices installed, you're ready to configure the modem in Windows. To do this, open Network and Sharing Center (or Network Connections in XP) and chose the Create new connection option.
Select a "Dial-up connection". Don't worry; it's neither as slow nor as noisy as a classic modem.
This next part is probably carrier-specific. For T-Mobile US, it was ridiculously easy: type a name for the connection (doesn't matter what), in the place for the number you dial, put "*99#" (without the quotes), and leave the password and username blank.
Try to connect! If it doesn't work, look up the WP7 settings for wired tethering to your carrier; they should be on this forum somewhere.
When you want to get back to normal (MTP) mode on the USB port, just repeat the first three steps but choose "MTP Mode" instead of "QC RmNetComposite" and let the phone reboot again.
Something which may help: I found that the PC would lose data connection while the phone used it. To make the PC's data connection more reliable, turn off data usage on the phone. The modem should still function. There are a ton of other tweaks to configure the modem driver which might also help, but for basic usage, the steps provided here work.
I recommend copying the driver bundle onto your phone (or its SD card) so that if you need to tether a PC that isn't already set up, you can get the drivers without needing Internet access. It's quite possible to copy Zip files to and from the phone via MTP mode.
Click to expand...
Click to collapse
Hi everyone, especially the writer of the quoted post, i know this is a old post but i just want to tell how to install the driver on Windows 8.1 64 bit in case if someone ended up here.
Windows 8.1 64 bit won't allow users to install unsigned driver like the driver he attached (Actually, the driver is signed, but i forget the reason why windows recognize it as unsigned driver. Please refer to the previous post). So, to make windows allow that, use this instruction:
http*://www*.howtogeek.*com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
nb: remove the star. i'm new here, so i can't post a link.
After you follow the instruction, then install the driver as the guy described.
I've tried this method, and it's work!
Pearlian said:
Hi everyone, especially the writer of the quoted post, i know this is a old post but i just want to tell how to install the driver on Windows 8.1 64 bit in case if someone ended up here.
Windows 8.1 64 bit won't allow users to install unsigned driver like the driver he attached (Actually, the driver is signed, but i forget the reason why windows recognize it as unsigned driver. Please refer to the previous post). So, to make windows allow that, use this instruction:
http*://www*.howtogeek.*com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
nb: remove the star. i'm new here, so i can't post a link.
After you follow the instruction, then install the driver as the guy described.
I've tried this method, and it's work!
Click to expand...
Click to collapse
Pearlian,
How did you find this driver?
I am looking for an modem driver for HTC One (M8) and would appreciated if you can point me in the right direction for my Search.
Volosat1y said:
Pearlian,
How did you find this driver?
I am looking for an modem driver for HTC One (M8) and would appreciated if you can point me in the right direction for my Search.
Click to expand...
Click to collapse
Ok, i've figured it out. Here is a link to my post.
Related
i need some help
when i connect the usb with my tilt
it just charges the phone
You want to give a little bit more information?
Yes, that would help. What happens when you connect and what version of active sync do you have and what Windows OS are you running?
Step one: make sure you have activesync v. 4.5
step two: disable your norton or mcafee or whatever virus protection you have
step three: go to start, control panel, switch to classic view (on the left side) click on windows firewall and disable it.
it should connect at this point.
leave the device connected and disable one at a time when you hear that little activesync noise you've found the program that was causing the problem. Ta Da! let me know if that works. PM me if anything else.
gqstatus0685 said:
Step one: make sure you have activesync v. 4.5
step two: disable your norton or mcafee or whatever virus protection you have
step three: go to start, control panel, switch to classic view (on the left side) click on windows firewall and disable it.
it should connect at this point.
leave the device connected and disable one at a time when you hear that little activesync noise you've found the program that was causing the problem. Ta Da! let me know if that works. PM me if anything else.
Click to expand...
Click to collapse
i tired it
but it still doesnt work
i am using xp, and the activesync is 4.5
when i connect the phone to PC, it doesnt even show up new hardware detected and asked me to install a driver
it just keep charging the phone
Hmmmmm, hard reset or in device manager check for your device's driver and delete it, then try again.
~~Tito~~ said:
Hmmmmm, hard reset or in device manager check for your device's driver and delete it, then try again.
Click to expand...
Click to collapse
already did a hard reset
where is device manager located?
Right click on my computer, go to properties, then hardware, then click device manager.
~~Tito~~ said:
Right click on my computer, go to properties, then hardware, then click device manager.
Click to expand...
Click to collapse
r u asking me to removed all usb drivers?
coz it doesnt say which one is which
Sometimes this is a simple cable problem.
Try a different USB Port on your computer, or a different cable. Also check that you haven't damaged the USB connection on your phone (some people do this by poking it with their stylus when trying to soft reset).
I had a similar problem, no idea if it is the same or even similar, but with mine RAPImgr also locked up and spiked the CPU usage to 50% (ie maxed out one of the cores - have a look in task manager). This only started happening with my Kaiser, wasn't happening with the Hermes....
Anyway, the way I solved it was to go to Start -> Settings -> Connections -> USB to PC and disable the "advanced network functionality" (ie uncheck the box).
If I had already plugged the phone into the computer, rapimgr would already be locked up and the only solution was to reboot (killing the process spawns a new one and when you finally find its parent's parent to kill, it takes out something vital which causes the machine to force a reboot).
For it to connect to my Vista box, I have to have this setting enabled. For XP I have to have it disabled.
Hope this is of some help.
I too was having this problem - i uninstalled ActiveSync from my PC and reinstalled it from the MS site - works fine now.
Alot of people are having problems making the switch to vista, i created this thread to help out making the move easier and help solve some compatability issues, as currently they aren't very easy to find all in one place. This thread is a depository for vista how-to's and fixes. I will continue to updates it as i find problems and solutions.
-----MY KAISER ISN"T BEING READ BY WINDOWS VISTA!!!!!-----
If your kaiser isn't being read by windows vista there is a pretty simple solution, you just need to disable advanced networking on your kaiser. To do this go to:
START----SETTINGS---CONNECTIONS---USB TO PC---UNCHECK THE BOX
After you do this your computer should greet you like r2d2 and install drivers and then connect to WMDC.
If you have further problems try swapping usb cords or using a different usb port (you have to connect via usb for the first time.)
------Using your device as a modem--------
WARNING tethering your devise is usually in violation of your contract, you will be able to use your phone as a modem but if you start using "excessive" amounts of data you could get in some trouble.
This is also a simple fix and requires only that you use the program "internet share" on your kaiser. (if you don't have it you can get it here thanks to ericc191) download the file and unzip the two items in it and place them in the windows directory. You can then create a shortcut and place in Windows>Start Menu>Programs.
Run the program and then select the type of connection you would like to use, bluetooth or usb. if you use bluetooth you will need to set up a partnership before hand. Personally i recommend usb because it is more secure won't kill your battery because it is plugged in and charging. Choose the internet service you would like to connect to and then push "connect" (left soft button.) Vista should automatically install the modem driver connect to your phone AS A MODEM. You will not be able to transfer file at this point as vista is recognising your phone as a modem, not as a windows mobile devise. you will not be connected to windows mobile devise center(WMDC.)
----I can't read my files or set up my device!----
Is your device connecting to WMDC? if not read "my kaiser isn't being read by windows vista." If your device is connected make sure you have disabled programs such as "MY MOBILER" as they do not react the same way as they do with active sync.
----Flashing in vista is here!!!
I take no credit for this, A big thanks to MrVanx as he made this tutorial possible!
One problem with windows VISTA 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.
NOTE: PLease Download the latest version of WMDC before attempting this.
You will need winrar to extract the files
First of all you will need one of these drivers depending on your version of Vista:
Windows Vista x32 Usb Driver
Windows Vista x64 Usb Driver
NOTE TO x64 WINDOWS USERS, you will need to boot up with driver signing enforcement turned off. To accomplish this, you will need to press F8 during boot up. If you do not do this, the 64 bit drivers will not install properly and this tutorial will not be of any use to you.
And of course you will need the Vista RUU
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.
1.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 PC.
2.Now navigate into the WMDC (Start>All Programs>Windows Mobile Device Center) and click on the "connection settings" menu icon.
3.In the connection settings menu untick "allow USB connections" then press OK.
4.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.
5.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.
6.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 Kaiser in bootloader).
7.Go to the "Driver" tab and click "Update Driver".
8.Click "Browse My Computer for Driver Software".
9.Select "Let me pick from a list...."
10.Click the "Have Disk" button.
11.Click "Browse" and navigate to the AS_DRIVERS folder we created earlier.
12.
Vista x32 users select the file "wceusbsh.inf"
Vista x64 users select the file "wceusbshx64.inf"
Click open.
13.click next and the driver will be installed (wait a moment).
14.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.
NOTE:: This technique is still in testing! It has been proven to work though!
The Vista Version of MTTY can be downloaded from dave daveshaw's site (http://taeguk.co.uk/xda)
Thanks dave!
------reserved---------
Did installing vista 32bit drivers help anyone?
I had this problem before but not anymore as I am using a shorter usb cable that was used to power portable hard drive and now it connects every time and charges phone faster.
moddin said:
Did installing vista 32bit drivers help anyone?
I had this problem before but not anymore as I am using a shorter usb cable that was used to power portable hard drive and now it connects every time and charges phone faster.
Click to expand...
Click to collapse
vista 32 bit driver is actually the driver from active sync, they should allow flashing, they won't necessarilly "help" with anything beyond that... does that answer your question?
The Vista Version of MTTY can be downloaded from my site (http://taeguk.co.uk/xda) - it's not my work, I just keep a mirror.
Ta
Dave
Well... It's good BUT i never had any problems with Vista really! More with Xp than with Vista! At least with Original Rom and Mobile device manager, no problems, everything works perfectly!
DaveShaw said:
The Vista Version of MTTY can be downloaded from my site (http://taeguk.co.uk/xda) - it's not my work, I just keep a mirror.
Ta
Dave
Click to expand...
Click to collapse
Thanks dave i'll put it in the original post
bandit2xx said:
Well... It's good BUT i never had any problems with Vista really! More with Xp than with Vista! At least with Original Rom and Mobile device manager, no problems, everything works perfectly!
Click to expand...
Click to collapse
same here. Now an XP user but never had any problems with Vista. Flashed ROMs daily...
Hi
I'm posting for my brother, he has a Kaiser and is trying to connect to his windows vista 32 computer. Problem is that he can't get the drivers to load for nothing good! He has tried everything you wrote here and still it won't detect the Kaiser! Whatelse can he do?
Regards
maw said:
Problem is that he can't get the drivers to load for nothing good!
Click to expand...
Click to collapse
If Advanced Networking is disabled on the phone, the next thing to check is that the latest version of WMDC is downloaded and installed on the Vista PC (and reboot after that before plugging in the phone just to be on the safe side). Yes the last step is on the previous page but you may have missed it....
First, thank you to the developersfor all your hard work that made the Windows XP "downgrade" possible on the shift.
I now have a Shift running running XP tablet edition, and it does so beautifully!
However, Everything I've been finding online in regards to the WLAN driver is for Vista. I can't, for the life of me, seem to find a working XP WLAN driver.
If anyone out there is chuckling to themselves and thinking, "hehe, well I've got that driver right here!" Would you be so kind as to post it?
Thanks in advance.
I think you managed to start the wireless using the ioperm from cygwin and the wf-on.bat file. When you start the wireless go to device manager and you will se there something with "!", just right click and use update driver, point to the folder where you downloaded the wireless driver from the HTC support site and that will work great.
PS: the guys are using a mod'ed sdbus.sys to use the wireless but the SD card then stops working... a way for both to work that I discovered is like this...
you just started your device, ok? now go to sleep mode with it and wake, now you have both sd card and wireless working ! then what's the catch? everytime your OS restarts, it's needed to sleep and wake again to make that work, I think is an exploit in the sleep module, you can investigate more using some development software if you're interested
no dice
Dalvus, when I try that, it tells me that "The specified location does not contain information about your hardware."
Any suggestions?
Regardless, thanks for the info about the SD slot, that's going to be really helpful if and when I get my WLAN working
so I understand your problem...
so here is the scenario, tell me if I'm wrong. Your wireless device doesn't appear in the control panel and the green light from the low level menu is not blinking. You should have been activated the wireless before installed Windows XP, so you need cygwin, a program that allow a linux shell to be run in Windows environment and to add the ioperm application while installing it.
I also used Windows XP Tablet PC SP3 to which I slipstreamed a file so it could read a VL serial and make it 100% genuine with no hack.
The problem at your device is that you do NOT have wireless chipset activated.
SO this is exactly what you need to do:
1.)start your device, let windows load, and then check your leds, if the led below the wireless/bluetooth is blinking blue that means bluetooth is activated, if it's blinking green that means wireless is activated, if blue and green as well are blinking, both of them are activated, so SKIP to 3.), if not blinking carry on to 2.)
2.)none of two leds are blinking so you need to activate them AND make them been recognized by Windows XP so install cygwin in c:\, just google for cygwin is free, when the installation starts, make sure that you check the ioperm program from devel submenu. now run cygwin.bat from where you just installed and type there:
ioperm –i then hit enter
exit then hit enter
now that you've just installed the I/O permision, google for hsect2.exe and place that .exe file in \cygwin\bin\
download these here http://dl.fisier.ro/files/1gjld5kjleh3fij/controls.zip.html and place in \cygwin\ where you installed or everywhere you want, where is a folder named controls, let it that way, now use the WF on and BT on to make it start, but still unrecognized by Windows/
3.) so now the leds blue and green are blinking, that's good, now restart windows and let it fully load... go to sleep mode and wake it, your wireless is now been recognized and sd slot as well, FULL functional, install the driver from the device manager and you're set to go
so i've done all of that, and i had already installed and run cygwin, i have both green and blue LEDs blinking under the bluetooth/wifi illustration... i restarted the pc, i put it in sleep mode, brought it back up, tried installing the drivers, and i still get the same "The specified location does not contain any information about your hardware." message.
Am I using the right drivers? "sd8686"
I just don't understand the problem, and it's looking more and more like I might have to reinstall xp to correct the issue..
I don't think it's necessary to reinstall Windows. To check if ok do this...
you said the blue and green [BT and WiFi] are blinking, ok. But Windows DO NOT recognize the device in any way, it DOES NOT see it !
Now go to sleep mode, and then wake it. Now in device manager you should see the "!" sign assigned to Marvel SD8686, if you can't see it, you can't do anything about it
PS: I'm selling my Shift in 1 week if no bluetooth support is for WinMobile part, I need to use all features
okay, so for some reason, i've been able to get teh bluetooth to work. so hooray for that!
but i'm still having the same issue with the WLAN. I've attached a screenshot of my device manager.
as you can see, no matter what i've tried, (including all the help offered from this thread), the shift still does not see the wireless card.
any further help would be greatly appreciated
note: the WLAN LED on the front panel of the shift IS blinking both blue and green but apparently the shift still does not see the WLAN adapter
you weren't paying atention...
one thing is to activate WiFi and because XP... other thing is to recognize it.
blinking means activated... now sleep it ! and wake it... it would recognize the WLAN...
if you restart XP, you must do the sleep/wake again to make it recognize
I have been listening, I assure you.
As I stated, I've tried EVERYTHING mentioned in the comments provided, including making the Shift sleep and then reawakening it. I'm still left in the same situation as you see in the screenshot above.
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.
After going through a ton of hoops to get this thing rooted, then ****ing flashed, I (naturally) run into another infuriating issue that is USB drivers don't seem to work, I hear the USB connected sound on windows when I plug it in but nothing appears, connecting as a Camera (PTP) seems to "work" but I can only see some(?) of my files and nothing can be copied to the phone. I have no SD Card, only the internal memory, so mass storage is not an option either. It shows up in Device Manager as "Google Galaxy Nexus ADB Interface" under "Android Device"
Things I've tried:
-Rebooting the PC(Many times)
-Rebooting the phone(Many times)
-Powering off the phone, taking out the battery and leaving it for 5 mins then powering on again
-Reinstalling Samsung Kies and Samsung USB drivers(infinite times)
-Factory resetting the phone and skipping all account prompts at startup then connecting the phone(seems to work for some people)
-Connecting with USB debugging off
-Connecting with USB debugging on
-Changing the USB Port.
Please help, I'm just about sick of this phone and it's countless issues, can't believe how hard it is to customize.
So here's a development. I tried turning USB debugging on and it installed some drivers then restarted my PC, now MTP mode works but only when USB Debugging is on, so at least that's good.
Still if anyone knows a way to fix this(ability to connect via USB with debugging off) that would be great. I don't imagine it's safe to have debugging on all the time.
Edit: also I got an idea, if there is a way to run the Phoneutil thing on CM10 that would be wonderful, I probably need to change the qualcomm USB settings from there or set those options in the main menu to PDA/PDA. The *#7284# code doesn't work without touchwiz.
I believe this is what you need.
http://forum.xda-developers.com/showthread.php?t=2583271
Seen the post a while back, wasn't hard to conduct a quick search. You're not alone on the MTP hate boat.
kaynpayn said:
I believe this is what you need.
http://forum.xda-developers.com/showthread.php?t=2583271
Seen the post a while back, wasn't hard to conduct a quick search. You're not alone on the MTP hate boat.
Click to expand...
Click to collapse
Thanks man.
Would you mind explaining that permissions bit though? I don't quite understand it. I've found the folder and can't delete it because of the permissions but I can't understand his explanation of getting the permissions... lol.
EDIT: I can't find "upperfilter" either.
I had to change permissions on that object to do so, then inside permissions take ownership and tick child keys and subkeys
Uncheck inherit from parent
If it pops up a dialog pops up choose add from the options
You will have to do this for several tabs in this permissions of the registry.
Click to expand...
Click to collapse
naxol said:
Thanks man.
Would you mind explaining that permissions bit though? I don't quite understand it. I've found the folder and can't delete it because of the permissions but I can't understand his explanation of getting the permissions... lol.
EDIT: I can't find "upperfilter" either.
Click to expand...
Click to collapse
Well, windows sucks on that department. The process is a bit buggy and shows you WAY too many warning and unnecessary windows. So this is what you need to do. After locating said registry key, i'd advise you to export it (it's a backup).
Then try to delete it's contents. You've noticed you can't, it says permission denied. So you right click on the denied folder and chose permissions.
You'll notice it's all blank. Press Advanced on the bottom and you'll notice on the next windows, up there where it says Proprietary, it says you're not the proprietary. But there's a placeholder link that does allow you to change who is. Click it and type in (search if you need) your current windows username (assuming your username is an admin on that machine). Accept everything util you reach the first window you got when you chose "permissions". Instead of pressing "Advanced" you pick "Add" and add your username again, give yourself "Total control" on the tick boxes below and press OK. You'll be back at the registry keys. The process to pick up the new permissions is a bit buggy. You'll need to refresh them now and you won't be denied access to the contents of the key you've just altered but you'll find out another key where you need to repeat the whole deal again. Think this'll happen 3 or 4 times. When all's done you will have no trouble deleting everything.
Now, this is the part i managed to do. My control panel part, is no where like what was stated in the OP (maybe because i'm using win8.1). I'm still figuring that one out. Removing the reg key, seems to have had no effect whatsoever in connecting my device to the computer, everything still works albeit through MTP.
Oh yea, i never had an issue with MTP not working. I just want to remove it because it's a limitative uneeded piece of crap. Slow transfer speeds and blocked access to my stuff during an operation (copying stuff) is just retarded.
kaynpayn said:
Well, windows sucks on that department. The process is a bit buggy and shows you WAY too many warning and unnecessary windows. So this is what you need to do. After locating said registry key, i'd advise you to export it (it's a backup).
Then try to delete it's contents. You've noticed you can't, it says permission denied. So you right click on the denied folder and chose permissions.
You'll notice it's all blank. Press Advanced on the bottom and you'll notice on the next windows, up there where it says Proprietary, it says you're not the proprietary. But there's a placeholder link that does allow you to change who is. Click it and type in (search if you need) your current windows username (assuming your username is an admin on that machine). Accept everything util you reach the first window you got when you chose "permissions". Instead of pressing "Advanced" you pick "Add" and add your username again, give yourself "Total control" on the tick boxes below and press OK. You'll be back at the registry keys. The process to pick up the new permissions is a bit buggy. You'll need to refresh them now and you won't be denied access to the contents of the key you've just altered but you'll find out another key where you need to repeat the whole deal again. Think this'll happen 3 or 4 times. When all's done you will have no trouble deleting everything.
Now, this is the part i managed to do. My control panel part, is no where like what was stated in the OP (maybe because i'm using win8.1). I'm still figuring that one out. Removing the reg key, seems to have had no effect whatsoever in connecting my device to the computer, everything still works albeit through MTP.
Oh yea, i never had an issue with MTP not working. I just want to remove it because it's a limitative uneeded piece of crap. Slow transfer speeds and blocked access to my stuff during an operation (copying stuff) is just retarded.
Click to expand...
Click to collapse
Thanks. I just found a huge timesaver called run as system that opens any exe as the SYSTEM profile, so you have sufficient permissions to delete whatever you want.
I removed the whole folder and the issue persisted, then I don't know what I did and USB stopped working completely, with and without Debugging. Gahhhh...
I'm recovering the original firmware now and starting from scratch on this.
Will post any updates/progress.
I DID IT. 6 hours of pain, I finally fixed it. Guess what the big thing is? Outdated ****ing drivers... god.
The drivers in this thread are outdated and do not work for androids past 4.1:
[WARNING! + GUIDE] Backup and Restore IMEI / NV Data Procedure for GT-I9305
Do NOT use the USB drivers from this thread.
For anyone having this problem:
Uninstall Samsung Kies, at the end you'll be asked if you want to remove usb drivers as well, accept.
Uninstall USB drivers from to make sure they are completely gone
Reboot your computer
Reboot your phone (doesn't make sense, just do it)
Reinstall Samsung Kies
Install up-to-date version of the drivers, look up version 1.5.29.0, filename SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.29.0.exe (Not posting the link because I'm not sure it's clean, don't want to infect anyone)
Plug your phone in
Ta da! You can now transfer files from your computer to your phone and vice versa using the DREADED, ABYSMAL ****ING Media Transfer Protocol
If this does not work, redo the first 2 steps, plug your phone in while you have Device Manager opened (Right click on my computer then choose Manage) and look for any devices showing up after you plug it in and uninstall the **** out of them, removing their drivers as well, make sure you do this with both MTP and CTP(Camera mode).
After that proceed from step 3 and you should be good.