So.... Can anyone confirm if the steps are the same like s3?
Shouldn't be in this section, you should know that...
Sent from my SPH-L900 using Tapatalk 2
Thread moved to Q&A.
can you do this without rooting?
No need for root to repair.
As long as the default samsung password works, it should be the same.
But I don't have my phone in hand yet. So I cannot confirm if default password work
So yes, I'm now on boost mobile with the note2.
For some reason this phone wouldn't do the ota activation or sprint zone activation trick.
I had to manually insert everything in qpst.
Working good now
Now need to work on mns
trim81 said:
So yes, I'm now on boost mobile with the note2.
For some reason this phone wouldn't do the ota activation or sprint zone activation trick.
I had to manually insert everything in qpst.
Working good now
Now need to work on mns
Click to expand...
Click to collapse
Trim, how were you able to get in and repair MEID? I used *#7284# to set the UART and USB to modem, but once I do that, Windows won't recognize the device. I do see a notification about "Qualcomm CDMA Technologies MSM" but no driver can be found.
If I set UART/USB back to PDA I can get Windows to recognize the device using mskip's device drivers.
trim81 said:
I had to manually insert everything in qpst.
Click to expand...
Click to collapse
by that you are referring to the data profiles, right? but how did you get your ESN allowed on boost, were you able to have customer service do it for you or did you actually spoof the ESN?
##3424# use that ibstead
After youre in everything is straifht foward
trim81 said:
##3424# use that ibstead
After youre in everything is straifht foward
Click to expand...
Click to collapse
What version of QPST are you using? I have build 378 and it's only good enough to establish the com port for QXDM. If you have a more recent version could you share it with us?
I'm not at home now... But look into the s3 forum, the repair method is the same, I used alpineman method.
But this phone is easier, in that no dfs is needed... Everything is repairable with qpst.
Like mentioned tho. I'm not sure if the towers or down or not.. But it will never take an ota activation both via profile 0 or wifi.
I ended having to input the settings manually via qpst
I won't go into spoon feeding, and step by step, it's already published - - look into the galaxy s3 forum
I used the same program versions as that thread
Edit
I used qpst 2.7 build 378
Can someone with knowledge please help create a voicemail. Apk hack for boost?
Still having problems
trim81 said:
Edit
I used qpst 2.7 build 378
Click to expand...
Click to collapse
Still cannot get into my phone.. hopefully you or someone else has more knowledge about this..
I installed the Toolkit drivers, then I put ##3424# into the phone. I pressed "Qualcomm USB Setting" and switched it to DM+MODEM+ADB and clicked OK, then switched UART to "CDMA MODEM", then plugged in the phone. At this point Windows correctly installs the drivers and I have a "SAMSUNG Mobile USB Serial Port (COM7)" under the device manager, and no abnormal status icon, so the driver installed correctly. But when I go to QPST I always see "No Phone" and the phone is never detected. I also get the same results if I put UART on "PDA" instead.. doesn't make a difference. Because QPST is in "No Phone" I can't get into to program it.
I also tried another way, *#7284*, then putting UART on MODEM and USB on MODEM, this time, Windows detects the device as a "Qualcomm CDMA Technologies MSM", not as a Samsung device. I installed the generic Qualcomm driver manually and QPST does detect the phone properly and I can get in, but I CANNOT read any of the crucial NVItems such as ds_mip_ss_user_prof (NVItem 466), QXDM always returns CFS_ERROR BAD PARAM, and I can't read these settings using DFS either. I tried writing it in DFS "blind" (since I cannot read to see
if it wrote correctly) but I still have no 3G, only 1xRTT and voice.
I have also tried many different USB cables and different Windows computers, always the same result. This is a brand new phone from Sprint, never been activated, is that the reason?
This is really frustrating, anyone out there seen this type of thing before? Spent days on this already.
Chanman said:
Still cannot get into my phone.. hopefully you or someone else has more knowledge about this..
I installed the Toolkit drivers, then I put ##3424# into the phone. I pressed "Qualcomm USB Setting" and switched it to DM+MODEM+ADB and clicked OK, then switched UART to "CDMA MODEM", then plugged in the phone. At this point Windows correctly installs the drivers and I have a "SAMSUNG Mobile USB Serial Port (COM7)" under the device manager, and no abnormal status icon, so the driver installed correctly. But when I go to QPST I always see "No Phone" and the phone is never detected. I also get the same results if I put UART on "PDA" instead.. doesn't make a difference. Because QPST is in "No Phone" I can't get into to program it.
I also tried another way, *#7284*, then putting UART on MODEM and USB on MODEM, this time, Windows detects the device as a "Qualcomm CDMA Technologies MSM", not as a Samsung device. I installed the generic Qualcomm driver manually and QPST does detect the phone properly and I can get in, but I CANNOT read any of the crucial NVItems such as ds_mip_ss_user_prof (NVItem 466), QXDM always returns CFS_ERROR BAD PARAM, and I can't read these settings using DFS either. I tried writing it in DFS "blind" (since I cannot read to see
if it wrote correctly) but I still have no 3G, only 1xRTT and voice.
I have also tried many different USB cables and different Windows computers, always the same result. This is a brand new phone from Sprint, never been activated, is that the reason?
This is really frustrating, anyone out there seen this type of thing before? Spent days on this already.
Click to expand...
Click to collapse
Yes!!! I did it. I thought I would share what worked for me in hopes that this will help others.
I ended up using *#7284* and then putting UART and USB both on MODEM. As I mentioned in my previous post, this causes the device to be detected as "Qualcomm CDMA Technologies MSM". I had to install a specific generic Qualcomm driver, which I have included in this post. After that, since I was only able to use QXDM/QPST/DFS to write the voice specific settings and HA profile (not passwords), the thing that ended up working for me was CDMA Workshop's free NVItem writer. Using this tool I was not able to read the crucial NVItems (466 and 1192), but I was able to write them. I did a byte-for-byte identical write, cloning the NVItems from the original phone (which I was able to read from). After the tool indicated the items were successfully written I rebooted the phone and everything worked!
guys I'm stuck, I'm not able to connect to my galaxy note 2 no matter what I try.I followed Chanman's post and was still unable to connect to my note 2 using the driver he provided. Are there any special steps I need to take because it's just not working for me.
I used all drivers and programs in the galaxy s3 post.
Follow that guide
iwin2000 said:
guys I'm stuck, I'm not able to connect to my galaxy note 2 no matter what I try.I followed Chanman's post and was still unable to connect to my note 2 using the driver he provided. Are there any special steps I need to take because it's just not working for me.
Click to expand...
Click to collapse
The driver I included in my post is a Win32 driver only. If you have Windows 7 64-bit it won't work. I had to use this particular driver on a 32-bit Windows XP machine. Sorry for not including that information in my post. You might be able to make a virtual machine to get the driver to load. I wasn't able to find a 64-bit Qualcomm CDMA MSM driver.
Ok I finally got this freaking phone connected and readable after messing it with with 1.5 days and I figured I would let you guys know.
What I had to do what go in to *#7284# mode, set both UART and USB as PDA (NOT MODEM), then go into Qualcomm USB Settings at the bottom and select either of the two options at the bottom (RNDIS+DM+MODEM or DM+MODEM+ADB, as long as it has DM in it it will connect).
As a result of this you will get a series of new devices connecting to your PC (visible on Device Manager), including one called SAMSUNG Mobile USB Serial Port (COM #), not Qualcomm CDMA MSM driver (if you get Qualcomm then you did it wrong, I wasn't able to connect to the phone using Qualcomm drivers posted above, although I'm not refuting Chanman's claim that it worked for him, I just couldn't get it working myself)
Now the drivers for the Galaxy Note 2 that you need installed are available here: http://org.downloadcenter.samsung.c..._L900_Note_II_Samsung_USB_Driver_v1_4_6_0.exe
I believe if you get the Galaxy Note 2 toolkit, those are the same drivers, but I prefer to get them directly from the source to avoid any issues.
Now I will continue by following the directions in the galaxy s3 thread as trim81 suggested, and I will report back (hopefully in a few hours).
Thanks for everyone's support.
iwin2000 said:
Ok I finally got this freaking phone connected and readable after messing it with with 1.5 days and I figured I would let you guys know.
What I had to do what go in to *#7284# mode, set both UART and USB as PDA (NOT MODEM), then go into Qualcomm USB Settings at the bottom and select either of the two options at the bottom (RNDIS+DM+MODEM or DM+MODEM+ADB, as long as it has DM in it it will connect).
As a result of this you will get a series of new devices connecting to your PC (visible on Device Manager), including one called SAMSUNG Mobile USB Serial Port (COM #), not Qualcomm CDMA MSM driver (if you get Qualcomm then you did it wrong, I wasn't able to connect to the phone using Qualcomm drivers posted above, although I'm not refuting Chanman's claim that it worked for him, I just couldn't get it working myself)
Now the drivers for the Galaxy Note 2 that you need installed are available here: http://org.downloadcenter.samsung.c..._L900_Note_II_Samsung_USB_Driver_v1_4_6_0.exe
I believe if you get the Galaxy Note 2 toolkit, those are the same drivers, but I prefer to get them directly from the source to avoid any issues.
Now I will continue by following the directions in the galaxy s3 thread as trim81 suggested, and I will report back (hopefully in a few hours).
Thanks for everyone's support.
Click to expand...
Click to collapse
Happy this worked for you. I believe this is the standard way to get into the phone (these instructions are all over Youtube and the S3 forum). The reason why I had to do things differently is that when I tried that approach, even though the devices show up as "Samsung" without any errors in Device Manager, QPST and DFS show "no phone" or can't connect to the port, even though it's there. Maybe I just got unlucky, or you got lucky, or both
Hi all,
heres my first post on xda and I just wanna to explain my problem.
I am in possession of a GT-N7105, just bought the USB connection worked perfectly but when I tried to install the CF-ROOT and CWM RECOVERY me no more, the PC recognized the phone.
I state that I had installed windows 8.
First of all I installed Samsung KIES and did not recognize him. I uninstalled Kies and installed the drivers using the NOTE 2 TOOLKIT. Even so, nothing to do. The computer can not find the driver for QUALCOMM CDMA TECHNOLOGIES MSM.
I thought it was an error of Windows 8, maybe a bug, so I formatted the system by installing Windows 7 Professional, downloaded NOTE 2 TOOLKIT and installed the drivers without having the phone connected to the PC. When the TOOLKIT required me to connect to the pc NOTE2, I did. But even here, unfortunately, can not find drivers for QUALCOMM CDMA TECHNOLOGIES MSM.
P.S. The phone in DOWNLOAD MODE is recognized by ODIN and I got it back to the SERVICE FIRMWARE but even so the problem is not resolved.
I also tried to change the usb port but nothing.
I tried to install other versions of firmware via odin but nothing. I do not know what to do. Google can not give me a solution and not XDA.
So I decided to write here publicly to expose my problem. I hope someone of you can help me solve this problem that prevents me from installing the CM10.1!
In advance thank you all.
Delete this.
Sent from my GT-N7100 using xda premium
UtkarshGupta said:
Delete this.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Thanks man! Very helpful!
nerdcorner69 said:
Thanks man! Very helpful!
Click to expand...
Click to collapse
Welcome.
But I can't figure out how that helped you...
Sent from my GT-N7100 using xda premium
Xda community is very helpful! Thanks all!
Found it!
My friend had a similar problem, he could not connect his note to the PC.
The following fixed the issue.
1. install new samsung kies.
2. follow these steps:
From -
http://www.danrichard.com/2013/06/1...nect-to-pc-via-usb-with-unknown-device-error/
"Method 3 – Ensure you have the right settings
By default my phone was already set to the right settings for USB file transfers so I’ll assume most of these ship with the same configuration, hence why I have this as method 2. I found this on a forum and while it did not work for me, it seems a few other folks declared it a success.
Launch the phone key pad on your note and press *#7284# (don’t forget to start with that * symbol!)
When you press the last pound sign (#) this will bring up an option that will allow you to change your USB connection settings (modem or PDA) – change it to PDA.
At the bottom there is a button that says Qualcomm USB. Click on it.
In that menu click on MTP + ADB option.
Save and reset.
Wait for your phone to restart.
Plug the micro USB cable to the Note 2 and the the other end to your PC or Mac
Let your computer down load and install drivers.
Once installing is done, unplug then replug phone.
There should be a USB symbol on your phone in the status bar - click on it. It should ask if you wsnd to use mtp or ptp. Click MTP
At this point your PC should open the phone’s folders in explorer similar to the screenshot above. "
Hope it helps you. keep the faith!
:highfive:
Really thanks man! Finally my usb is working like the first time Thx!
droritos said:
"Method 3 – Ensure you have the right settings
By default my phone was already set to the right settings for USB file transfers so I’ll assume most of these ship with the same configuration, hence why I have this as method 2. I found this on a forum and while it did not work for me, it seems a few other folks declared it a success.
Launch the phone key pad on your note and press *#7284# (don’t forget to start with that * symbol!)
When you press the last pound sign (#) this will bring up an option that will allow you to change your USB connection settings (modem or PDA) – change it to PDA.
At the bottom there is a button that says Qualcomm USB. Click on it.
In that menu click on MTP + ADB option.
Save and reset.
Wait for your phone to restart.
Plug the micro USB cable to the Note 2 and the the other end to your PC or Mac
Let your computer down load and install drivers.
Once installing is done, unplug then replug phone.
There should be a USB symbol on your phone in the status bar - click on it. It should ask if you wsnd to use mtp or ptp. Click MTP
At this point your PC should open the phone’s folders in explorer similar to the screenshot above. "
Hope it helps you. keep the faith!
:highfive:
Click to expand...
Click to collapse
Downloaded the Samsung Mobile Drivers and used Method 3- WORKED FINALLY!
Holy Toledo, you are confused my friend, if your OP is any indication. Understand that XDA is not a noobs forum. Yes, everyone had to start at the beginning, but if a forum wishes to aim for a clientele with a bit higher level of knowledge/experience, there's nothing wrong with that and they have a right to do so, especially with there being a gazillion other Android forums that do handle noob questions. I suspect you don't realize how many things are wrong with your OP, "wrong" in the sense that they reveal a massive level of confusion on several quite basic concepts. To wit: reinstalling the PC's entire operating system as part of a solution toward hooking up your mobile to it is such ludicrous overkill that it is not a wonder people will read it and run in the other direction. Fast . And that's one example of many I could make. None of this makes you a bad person by the way, just a very inexperienced one. The best advice I can give you is to pay your dues a little longer and post to other forums if you must, and use XDA in the meantime as the best reference you can find anywhere on the net. I don't know if you'll ever get this, but down the road others in your shoes will. And I won't be revisiting this thread, so good luck :good:.
This is weird my note one always pops up with a windows folder and I just drop my new rom in there but my new I317 when I connect it to the computer is doesnt show up. It will charge the device but does let me get into it so I can drop my rom in there and install any ideas? I did a factory reset and I have all the drivers installed.
blazin6969 said:
This is weird my note one always pops up with a windows folder and I just drop my new rom in there but my new I317 when I connect it to the computer is doesnt show up. It will charge the device but does let me get into it so I can drop my rom in there and install any ideas? I did a factory reset and I have all the drivers installed.
Click to expand...
Click to collapse
type this in your dial pad
*#7284#
go to USBSettingsMenu and tell me what your option is on.
You want it to be MTP+ADB
chousayz said:
type this in your dial pad
*#7284#
go to USBSettingsMenu and tell me what your option is on.
You want it to be MTP+ADB
Click to expand...
Click to collapse
Yep changed it to that shoud on the first page be uart pda and usb be modem?
blazin6969 said:
Yep changed it to that shoud on the first page be uart pda and usb be modem?
Click to expand...
Click to collapse
nope! both should be on MODEM
did it work?
Its did work when I changed them both to pda....I also stopped windows from searching for update for driver....You can then go to device manager see the error on usb com ports and direct which drivers to install from there...When I swtich to modem tho I have to do the drivers thing again.
I remember seeing a post to stop windows from installing thier own drivers just cannot seem where to find it
I installed Busybox Free on my phone (using the simple installer) and it allows my phone to connect to the PC just fine. I also have downloaded Samsung's drivers to my PC.
Hi
Question
Why wouldn't an Epic Touch get assign a COM port ?
I have all the drivers and I can see it in My Computer and in Device Manager / Portable Devices / as SPH-D710
btw I have another epic touch which does display as "SAMSUNG Mobile Modem Diagnostic Serial Port (WDM)"
is there something that needs to be enabled for the phone to be recognized as ^^^above^^
Thanks
Killtac said:
Hi
Question
Why wouldn't an Epic Touch get assign a COM port ?
I have all the drivers and I can see it in My Computer and in Device Manager / Portable Devices / as SPH-D710
btw I have another epic touch which does display as "SAMSUNG Mobile Modem Diagnostic Serial Port (WDM)"
is there something that needs to be enabled for the phone to be recognized as ^^^above^^
Thanks
Click to expand...
Click to collapse
In what application are you trying to get it to show up on? or is it just windows?
If you are running a 'one-click' or any Odin, make sure you 'run as administrator'.
Also if using adb or some other cli tool check that you have USB Debugging enabled under Developers options
leaderbuilder said:
In what application are you trying to get it to show up on? or is it just windows?
If you are running a 'one-click' or any Odin, make sure you 'run as administrator'.
Also if using adb or some other cli tool check that you have USB Debugging enabled under Developers options
Click to expand...
Click to collapse
Just windoes, Windows Vista Enterprise x64 to be exact
Phone is stock...factory reset it just before I made my post. Just to try I also enabled USB debugging but it still didn't get a COM port assigned
Killtac said:
Just windoes, Windows Vista Enterprise x64 to be exact
Phone is stock...factory reset it just before I made my post. Just to try I also enabled USB debugging but it still didn't get a COM port assigned
Click to expand...
Click to collapse
If you haven't already try another USB cable and different ports on the PC. I can't tell you how many times I've had a cable that had previously been good NOT work. I've spent hours trying to get phones, printers and other devices installed when all I had to do was grab a brand new high quality cable.
Also, I'd recommend un-installing ANY and all Samsung drivers - make sure you 'show hidden devices' in device manager! then reboot.
And then re-install them. They're here.
Then Power down phone
Wait for capacitative button lights to turn off
Simultaneously Press and Hold [Power] [VolDn] until confirmation screen appears
Press [VolUp] to enter Download mode.
Then plug it into the PC.
Good luck
Thanks for the help it deff helped me rule out a couple of things, but i noticed that on the modem section of device manager one phone was listed and the other one was not...looking at that helped me resolve the issue
here is the fix if anyone else is having the same issue
dial ##8778#
You should get a menu titled USB containing 3 options AP CP ALL
ALL has to be checked
http://forum.xda-developers.com/showthread.php?t=1626638
btw is there a repository containing all the ##XXXX# codes, and what are these called?
Here's one There are others just have to search for 'em. I can't find my other bookmarks.
Thanks for the info.
I have been experimenting with my nexus 7 2013 and the diagnostic mode. I have had issues finding appropriate drivers for the tablet's diagnostic mode. Whenever I switch to the diagnostic mode the windows driver manager shows up the devices as in the image.
Can someone please provide me with diagnostic drivers for the nexus 7 2013.
jared.leto said:
I have been experimenting with my nexus 7 2013 and the diagnostic mode. I have had issues finding appropriate drivers for the tablet's diagnostic mode. Whenever I switch to the diagnostic mode the windows driver manager shows up the devices as in the image.
Can someone please provide me with diagnostic drivers for the nexus 7 2013.
Click to expand...
Click to collapse
Here is QPST Diagnostics driver and all other USB drivers from Google.
k23m said:
Here is QPST Diagnostics driver and all other USB drivers from Google.
Click to expand...
Click to collapse
Hey thanks... I have tried these... they work too but still the QPST functions won't happen.... they just show errors relating to connectivity.
jared.leto said:
Hey thanks... I have tried these... they work too but still the QPST functions won't happen.... they just show errors relating to connectivity.
Click to expand...
Click to collapse
To enter Qualcomm Diagnostics mode please try:
turn N7 off
press and hold both vol buttons
plug in PC USB
Windows device manager should display a new item with hardware ID: VID_05C6&PID_9008
If not, please quote the VID/PID you get.
k23m said:
To enter Qualcomm Diagnostics mode please try:
turn N7 off
press and hold both vol buttons
plug in PC USB
Windows device manager should display a new item with hardware ID: VID_05C6&PID_9008
If not, please quote the VID/PID you get.
Click to expand...
Click to collapse
I get that in my device manager. Any idea how to use it with QPST programs? I need it to work so that I can fix my IMEI number.
jared.leto said:
I get that in my device manager. Any idea how to use it with QPST programs? I need it to work so that I can fix my IMEI number.
Click to expand...
Click to collapse
In 9008 mode the driver from QPST Diag package should register without an error and a new COM port will be available. Then QPST apps will work. I don't have a deb model but IMEI number must be in fsg - mmcblk0p8 partition I guess.