Related
This is a copy paste from another forum, i take no credit/responsibility
Thought it might be of use for somebody
Android codes
FYI These codes have been obtained by decoding various .apk files present in the phone firmware.
*#*#4636#*#*
This code can be used to get some interesting information about your phone and battery. It shows following 4 menus on screen:
Phone information
Battery information
Battery history
Usage statistics
*#*#7780#*#*
This code can be used for a factory data reset. It'll remove following things:
Google account settings stored in your phone
System and application data and settings
Downloaded applications
It'll NOT remove:
Current system software and bundled applications
SD card files e.g. photos, music files, etc.
PS: Once you give this code, you get a prompt screen asking you to click on "Reset phone" button. So you get a chance to cancel your operation.
*2767*3855#
Think before you give this code. This code is used for factory format. It'll remove all files and settings including the internal memory storage. It'll also reinstall the phone firmware.
PS: Once you give this code, there is no way to cancel the operation unless you remove the battery from the phone. So think twice before giving this code.
*#*#34971539#*#*
This code is used to get information about phone camera. It shows following 4 menus:
Update camera firmware in image (Don't try this option)
Update camera firmware in SD card
Get camera firmware version
Get firmware update count
WARNING: Never use the first option otherwise your phone camera will stop working and you'll need to take your phone to service center to reinstall camera firmware.
*#*#7594#*#*
This one is my favorite one. This code can be used to change the "End Call / Power" button action in your phone. Be default, if you long press the button, it shows a screen asking you to select any option from Silent mode, Airplane mode and Power off.
You can change this action using this code. You can enable direct power off on this button so you don't need to waste your time in selecting the option.
*#*#273283*255*663282*#*#*
This code opens a File copy screen where you can backup your media files e.g. Images, Sound, Video and Voice memo.
*#*#197328640#*#*
This code can be used to enter into Service mode. You can run various tests and change settings in the service mode.
WLAN, GPS and Bluetooth Test Codes:
*#*#232339#*#* OR *#*#526#*#* OR *#*#528#*#* - WLAN test (Use "Menu" button to start various tests)
*#*#232338#*#* - Shows WiFi MAC address
*#*#1472365#*#* - GPS test
*#*#1575#*#* - Another GPS test
*#*#232331#*#* - Bluetooth test
*#*#232337#*# - Shows Bluetooth device address
*#*#8255#*#*
This code can be used to launch GTalk Service Monitor.
Codes to get Firmware version information:
*#*#4986*2650468#*#* - PDA, Phone, H/W, RFCallDate
*#*#1234#*#* - PDA and Phone
*#*#1111#*#* - FTA SW Version
*#*#2222#*#* - FTA HW Version
*#*#44336#*#* - PDA, Phone, CSC, Build Time, Changelist number
Codes to launch various Factory Tests:
*#*#0283#*#* - Packet Loopback
*#*#0*#*#* - LCD test
*#*#0673#*#* OR *#*#0289#*#* - Melody test
*#*#0842#*#* - Device test (Vibration test and BackLight test)
*#*#2663#*#* - Touch screen version
*#*#2664#*#* - Touch screen test
*#*#0588#*#* - Proximity sensor test
*#*#3264#*#* - RAM version
NOTE: All above codes have been checked on Google Android phone Samsung Galaxy I7500 only but they should also work in other Google Android phones
The only one I can get to is
*#*#INFO#*#* (*#*#4636#*#*)
hello guys, starting this trhead for a list of diagnostic codes. Samsung Omnia for 7 .. come forward and help all.
Enter always in diagnosis mode with: ##634# and hit the call button.
And now Try this code:
1) *#0*# for the LCD test
2) *#2*# for Debug Mode
3) *#3*# for TestBrigthnes
4) *#1234#* for Version
5) *#32489# for Test Mode - CIPHERING CONTROL
6) *#2263# for Test Mode - BAND PREFERENCE
7) *#0782# for RTC Time
8) *#0673# for MP3 Test
9) *#9090# for Test Mode - DIAG CONFIG
10) *#0842# for Vibrator Test
11) *#2580# for INTEGRITY CONTROL
12) *#0011# for Test Mode - WCDMA
13) *#7465625# for Personalize - Lock Status - Network Lock - Subset - SP Lock - Cp Lock
14) *#232337# for BT Mac Address
15) *#0002*28346# for INCREASE VOLUME !!!!!! - Sound Tuning: But i dont know use it - help me please
16) *#7284# for Micro USB Test (Zune Sync, Modem Tethered Call, Modem USB Diag)
17) *#1472365# for Location Service
18) *#05# for Simple Test
19) *#2470# for CameraFWUpdate
You can add :
Micro USB Test *#7284# (Zune Sync, Modem Tethered Call, Modem USB Diag)
Location Service *#1472365#
Simple Test *#05#
CameraFWUpdate *#2470#
PDAphoneAddict.com
Erwan960 said:
You can add :
Micro USB Test *#7284# (Zune Sync, Modem Tethered Call, Modem USB Diag)
Location Service *#1472365#
Simple Test *#05#
CameraFWUpdate *#2470#
PDAphoneAddict.com
Click to expand...
Click to collapse
Ok Many Tanks!!!
thank's but Not for Mozart maybe later ...
How do I input the codes once at the diagosntic screen?
What's with the beeping on the RTC Time screen?
The location service is actually pretty useful! It shows altitude and speed, as well as GPS co-ordinates.
more than 60 diagnosis codes
I've written 2 posts on my blog listing more than 60 diagnosis codes (tested on my Samsung Omnia 7), and how to use them:
post 1 : martani[dot]net/2010/12/windows-7-hacks-all-diagnosis-codes-you.html
post 2 : martani[dot]/2010/12/windows-7-hacks-all-diagnosis-codes-you_26.html (sorry can't post links yet!)
Enjoy
Hi. I'm a fun of yours work on Samsung Wave. I come here to ask if is possibile to create a program that automatically delete the gps+ data.
I have the JL2 unofficial fw on my Wave and I checked that, without a manual delete data + gps, they are not downloaded. It 's always necessary, any time, enter the secret menu (*#4097*4097#) and manually delete the data.
It would be possible to build a tool able to do this procedure automatically and, perhaps, start Route66 in the same time. In short, do everything with one click. With this settings the fix of our Wave will be always in the order of time of 20-30 seconds. It's possible in yours opinion?
Why do you need to delete any data? I've installed Sygic and i get a lock after about 10-20 sec ....
pockobg said:
Why do you need to delete any data? I've installed Sygic and i get a lock after about 10-20 sec ....
Click to expand...
Click to collapse
Is difficult to explain the situation. I use Ruote66 and fw JL2. I haven't a flat plan on phone and I use wap configuration. I think isn't a problem of Ruote66 but of the internal settings of gps. In my case, if I don't used the gps from a week, the fix is slow (12 min). I have active gps+ but the download doesn't run automaticaly if I delete gps data.
Nezmanpro said:
Is difficult to explain the situation. I use Ruote66 and fw JL2. I haven't a flat plan on phone and I use wap configuration. I think isn't a problem of Ruote66 but of the internal settings of gps. In my case, if I don't used the gps from a week, the fix is slow (12 min). I have active gps+ but the download doesn't run automaticaly if I delete gps data.
Click to expand...
Click to collapse
So this is a problem for Route66? Why dont you try Sygic?
pockobg said:
So this is a problem for Route66? Why dont you try Sygic?
Click to expand...
Click to collapse
Becouse I buyed Route66. I want use it and not another software.
Question: Can you give me the fw in your Wave and the setting in secret menù of gps (*#4097*4097#)? My interest is for "gps type" and the value of "time - out" in the "application settings". Thanks
Time out - 60000
GPS Device-Type - HYBRID
I found that setting a timeout to 1000 worked a little better but effectively deleting the data gets it going more quickly. That is after setting up the system correctly in the first place.
Sent from my Hero using Tapatalk
duxxyuk said:
I found that setting a timeout to 1000 worked a little better but effectively deleting the data gets it going more quickly. That is after setting up the system correctly in the first place.
Sent from my Hero using Tapatalk
Click to expand...
Click to collapse
I use this settings:
gps mode: standalone;
gps option: location+ velocity + altitude;
session type: tracking mode;
gps device - type; build - in;
data receive..: All;
time out: 60000 (change to 1000);
Horizzontal Accuracy: 1000;
Vertical Accuracy: 500;
I tryed to use the hybrid type of gps, but my apn doesn't support traffic of data. So I set built - in and it's ok if I delete gps data. Now, the most rational solution is waiting a new fw that, perhaps, will solve this problem but my idea is easy and can give to all those who use route66 an immediately solution.
So, there is anyone that can realise this application? Is possible?
Here's how I got mine working correctly. (effectively I finish with Nezmanpro's settings as well)
1. Dial *#4097*4097#
2. Choose 3-User setting
3. Choose 1-Assist Method Type then select AGPS. System will reboot.
4. When the phone boots and returns to idle mode (after entering pin and checking the SD Card) dial *#4097*4097#.
2. Choose 3-User setting
3. Choose 2-SUPL Setting and set the options as below
Use AGPS or NOT = On
MT-Auto Configuration = Off
SUPL MT-Response Type = Accept
Server Address Type = IP_ADDRESS
Server FQDN Type = Custom Config (this was originally BMC LIVE TEST )
SUPL Secure Socket = Off
Server IP Address = 74.125.77.192
Server Port = 7276
I then go back up to "Server Address Type" and set that to "HOST_NAME". I can then set Server Custom FQDN = supl.google.com
I think there's a bug here as the port should also be available when using a host name - when choosing host_name the port field is locked, that's the reason behind going back up and changing the "Server Address type".
Save this. then go into 4-Network Profile
4. Set the network to the one you use for your internet access, not the mms.
5. Check that in the PDR Setting all is checked.
6. Go back to the main menu of LBS Application then select 2. Application Setting
7. Set the following options:
GPS Mode = A-GPS CP Based
(See the following post for further info http://forum.xda-developers.com/showthread.php?t=729118)
GPS Option = Location+Velocity + Altitude
Session Type = Tracking Mode
GPS Device-Type = HYBRID
Date Recieve Type = All
Time Out = 1000 (like Nezmanpro)
Horizontal Accuracy = 100
Vertical Accuracy = 500
8. I then go back into User Setting
9. Back into Assist Method
10. Set Assist Method Type = GPS+
System will restart
11.When the phone boots and returns to idle mode (after entering pin and checking the SD Card) dial *#4097*4097# to get back to the LBS Application.
12. Go back into 3-User Setting
You'll see that SUPL settings are no longer present.
13. Go into GPS+ Setting and check that Auto Download = Enabled
14. Go back to the LBS Application menu then 6- DELETE GPS DATA
16. Happy navigation. Phew
duxxyuk said:
Here's how I got mine working correctly. (effectively I finish with Nezmanpro's settings as well)
1. Dial *#4097*4097#
2. Choose 3-User setting
3. Choose 1-Assist Method Type then select AGPS. System will reboot.
4. When the phone boots and returns to idle mode (after entering pin and checking the SD Card) dial *#4097*4097#.
2. Choose 3-User setting
3. Choose 2-SUPL Setting and set the options as below
Use AGPS or NOT = On
MT-Auto Configuration = Off
SUPL MT-Response Type = Accept
Server Address Type = IP_ADDRESS
Server FQDN Type = Custom Config (this was originally BMC LIVE TEST )
SUPL Secure Socket = Off
Server IP Address = 74.125.77.192
Server Port = 7276
I then go back up to "Server Address Type" and set that to "HOST_NAME". I can then set Server Custom FQDN = supl.google.com
I think there's a bug here as the port should also be available when using a host name - when choosing host_name the port field is locked, that's the reason behind going back up and changing the "Server Address type".
Save this. then go into 4-Network Profile
4. Set the network to the one you use for your internet access, not the mms.
5. Check that in the PDR Setting all is checked.
6. Go back to the main menu of LBS Application then select 2. Application Setting
7. Set the following options:
GPS Mode = A-GPS CP Based
(See the following post for further info http://forum.xda-developers.com/showthread.php?t=729118)
GPS Option = Location+Velocity + Altitude
Session Type = Tracking Mode
GPS Device-Type = HYBRID
Date Recieve Type = All
Time Out = 1000 (like Nezmanpro)
Horizontal Accuracy = 100
Vertical Accuracy = 500
8. I then go back into User Setting
9. Back into Assist Method
10. Set Assist Method Type = GPS+
System will restart
11.When the phone boots and returns to idle mode (after entering pin and checking the SD Card) dial *#4097*4097# to get back to the LBS Application.
12. Go back into 3-User Setting
You'll see that SUPL settings are no longer present.
13. Go into GPS+ Setting and check that Auto Download = Enabled
14. Go back to the LBS Application menu then 6- DELETE GPS DATA
16. Happy navigation. Phew
Click to expand...
Click to collapse
Ok. But you must always manually delete gps data after this operation? I Knew that this operation was for functionally to have more speed to data download but my problem doesn't solve, becouse you must always delete gps data. Or not?
In order to get a fix quickly - ahem - in less than 3 minutes I need to delete the gps data.
Compared to a HTC hero I have the impression that the phone has no A in GPS.
the HTC hero locks in under 30 seconds the wave in under 3 minutes.
duxxyuk said:
In order to get a fix quickly - ahem - in less than 3 minutes I need to delete the gps data.
Compared to a HTC hero I have the impression that the phone has no A in GPS.
the HTC hero locks in under 30 seconds the wave in under 3 minutes.
Click to expand...
Click to collapse
An application that auto deletes the gps data would fix this problem.
So the Wave does not use network assisted GPS? Then those Application settings in the GPS menu do not make sense other than the Standalone mode?
bsbharath1987 said:
So the Wave does not use network assisted GPS? Then those Application settings in the GPS menu do not make sense other than the Standalone mode?
Click to expand...
Click to collapse
Having deleted the gps data this morning. I put the phone in 3G mode... gps lock in under a minute... I think YES the phone is capable of being assisted it's just that Samsung appear to have completely misconfigured and have forgotten to implement the gps data timeout :-(
definitely not something that would get past Steve Jobs....
i think we have nothing to do untill now except waiting a new firmware fixing this
Good afternoon, this is a question of users of the wave (S8500) in Latin America for developers hope we can provide a solution to your great knowledge!.
My question is if you can adapt a AMSS.BIN bada bada 1.2 for use in 2.0?. Spend it here in latin america we do not support bada 2.0 and therefore when we installed our wave bada 2.0 do not have signs or fewer 3G signal and therefore we can not call or send messages ... You could adapt a 1.2 as I said AMSS? at least to give us a good reception signal and to call, we try to do that but we had good results from lack of knowledge, so you resorted to see if we could help with that .. I just hope that some developer is encouraged to this project since it will be helping many Latin American countries and thousands of users without enjoying bada 2.0.
I tell them I'll put my phone to test, if you accept to do the project I will go testing your Avanze if it works on my phone.
Of course many thanks to you all. please help us!
yes we need your help
elkpojlb said:
good afternoon, this is a question of users of the wave (s8500) in latin america for developers hope we can provide a solution to your great knowledge!.
My question is if you can adapt a amss.bin bada bada 1.2 for use in 2.0?. Spend it here in latin america we do not support bada 2.0 and therefore when we installed our wave bada 2.0 do not have signs or fewer 3g signal and therefore we can not call or send messages ... You could adapt a 1.2 as i said amss? At least to give us a good reception signal and to call, we try to do that but we had good results from lack of knowledge, so you resorted to see if we could help with that .. I just hope that some developer is encouraged to this project since it will be helping many latin american countries and thousands of users without enjoying bada 2.0.
I tell them i'll put my phone to test, if you accept to do the project i will go testing your avanze if it works on my phone.
Of course many thanks to you all. Please help us!
Click to expand...
Click to collapse
s.o.s.
S.o.s.
S.o.s.
S.o.s.
S.o.s.
S.o.s.
S.o.s.
S.o.s.
S.o.s.
S.o.s.
Very good, I think for what you asked must change the UMTS bands amms.bin modifying the firmware. It is long and you have to use complicated tools but each values what does And what he wants.
AMMS = Advanced Mobile Subscriber Software (Qualcomm by)
Qualcomm is a U.S. company founded in 1985 to produce chipsets for wireless technology CDMA and W-CDMA. Also responsible for the Eudora email client.
Among its main products, there Brew platform for creating applications for mobile devices.
It is one of the leading suppliers of processors for smartphones.
As we all know, our phone has AMSS, which is a driver software provided by Qualcomm, and telecommunications technology company.
As I researched, the AMSS functions as driver for this phone can connect to GSM, UMTS, among other things ...
There are tools, developed by Qualcomm, to enter the phone memory and calibrate the chipset, and my first thought when I heard this was in Latin Bada 1.2/2.0 + 3G.
I was hanging around in A and Developers Samsung universe and more or less able to operate the phone, and from what I saw, it is likely that the cell can be calibrated to use the bands that we need, but require a more advanced.
Below I leave a mini instructions on how to configure the phone and install the software if they want to investigate yourself. I believe that here comes the hand so that we can edit the file AMSS.bin and to use any firmware!
Clarified that are complicated and use tools that can write data on the phone, so, chances are corrupt memory to leave the cell unusable, everyone assumes their own responsibility to manipulate this program.
You need the following software is easy googling of last I can send PM's
- Qualcomm CDMA Technologies MSM driver
- Qualcomm QPST 2.7 Tools
- PSAS 1.5
Does not work on 64bit versions.
You must first change the USB connection mode of the Wave, for that we must enter the code * # 197328640 #
Then choose the following options
[8] Common> [7] SERVICE Configuration> [2] DIAG SERVICE Config> [2] USB DM / CP
Remember that the default connection mode is "[3] UART / AP" just want the connection back to normal.
Now that the cell is ready, connects to the PC and proceed to the installation of drivers, which by default is going to install one called "Samsung HS-9002 USB Diagnostics" which should be replaced by another driver.
-Open the Device Manager
-Where it says Ports Com & LPT search "Samsung HS-USB Diagnostics 9002" and the properties ponele "update driver" and select "Have Disk" to select it manually.
-In the package of "Qualcomm drivers" who have downloaded the driver select "msmdm.inf" (You have to remove the option "Show compatible hardware"), and the device list select "Qualcomm Diagnostics Interface 3197".
The end must be as follows:
Well, it already has configured the cellular to enter the internal configuration to do is to install elQPST Tools 2.7 and configure the COM port.
Start from the Start menu the "QPST Configuration", go to the tab "Ports" to add port go to "Add new port ..." and select the port "COMxx - USB / QC Diagnostic", then press ОК, should appear in the list, but the important thing, in the "Phone" must appear "QSC6270/QSC6240 (DEAD00D)", this means that the phone was recognized correctly and is ready for manipulation. If not, then you did something wrong ...
The tool I used to see some of the parameters was the "RF NV Item Manager". This program can read the phone's configuration parameters, you can also delete, edit and add new parameters ... but as I said before, is risky and if they know they are doing, I recommend not meddle.
When you open the "RF NV Item Manager" press the first button "Read from phone RF NV Items" and will start charging a nice list (as pictured below)
Pulling error, look at the top menu "Settings> ComPort" and select the port cell. (To know what, go to Device Manager under "Ports Com & LPT" and read from that port is "Qualcomm Diagnostics Interface 3197 (COMXX))
This list shows the NV Items, each one is configured with hexadecimal values, which can modify, delete, add, etc. .. as I said before.
You can also export to a. QCN which when opened can also be exported to TXT.
I warn you that among all these items, is the information of IMEI, so I recommend that no protection of their SETTINGS throughout the internet. The IMEI is in the NV Item 550 [NV_UE_IMEI_I].
My research was based on export a list of items in. QCN
First exported from my cellular with a 3G Firmware 1.0.2 with Latin America.
After the cell flashie a European Firm with Bada 1.2 (not 3g obviously) and went back to export another list. QCN
Comparing both configurations found 40 differences between the two configurations
The Latin American firm contains items that the European NO, such as:
said:
NV item: 3974 [NV_WCDMA_800_TX_PDM_LIN_1_I]
NV item: 3975 [NV_WCDMA_800_TX_PDM_LIN_2_I]
NV item: 3976 [NV_WCDMA_800_TX_PDM_LIN_3_I]
NV item: 3978 [NV_WCDMA_1900_TX_PDM_LIN_1_I]
NV item: 3979 [NV_WCDMA_1900_TX_PDM_LIN_2_I]
NV item: 3980 [NV_WCDMA_1900_TX_PDM_LIN_3_I]
Yes sir! UMTS bands are for Latin America as expected ... (UMTS or 3G WCDMA means)
And in the European Firm are other items that are not in Latin, as:
said:
NV item: 3984 [NV_WCDMA_900_TX_PDM_LIN_3_I], index 0
NV item: 5055 [NV_WCDMA_900_TX_LIN_MASTER_0_ENH_I], index 0
NV item: 5059 [NV_WCDMA_2100_TX_LIN_MASTER_0_ENH_I], index 0
NV item: 5061 [NV_WCDMA_900_TX_PDM_LIN_0_ENH_I], index 0
As expected, in this case refers to the European bands ...
With eggs in my throat ADD encourage the items found in firmware settings AMERICAN in my cell, which currently has no 3G bada 1.2, and thus prove that happens.
This can be done by generating a customized list of "NV items". To do this they must enter the "RV NV item manager" and press the button "Read form QCN file" and select the file (I had an export in. Qcn bada 1.0). Then in the menu "Option" select "Customized NV item list" and removed items that were already in the European firmware and let those of Latin America. Then press the button "Write listed items to the phone. (Override the Existing ones)"
This phone only write in the items I selected, but if any item that was already on the phone, it replaces the list.
After adding these parameters and restart the phone, still no 3G, no change I noticed in the cell may have to enable SETTING some more, so that bada 1.2 hablitado already understand that to use the local UMTS bands, but good is a matter of investigate ..
Then I installed the program PSAS 1.5, this tool also can read and edit the phone NV items, you can even see other items not marked with the "RF NV Manager items," such as item 2757 which is the product code, which can be changed also.
What I did was:
PSAS Open and go to "Hardware Forensics" -> "Use Mobile Ports" -> choose "Serial Com Port COMXX - Qualcomm Diagnostics Interface 3197 (COMXX)" In the same window go to "DIAG" and in " Diag Functions "drop down list and choose" Display NVitems ". Where it says start I wrote the item number that you "add" to the European firmware, such as 3980 and then you click on "Let's Go"
And below, the outcome QUAD going to say "Inactive item" ... mmmmm
P.D. I just do not probe the results conexsiones
Greetings to all!
Hello thank you for your interest ferrloz for this, but I want you to know that we have no knowledge about such things and that's why I brought my order to XDA developers because they know much about this.
I just hope that theirs will serve as a help to them and we can help .. Thank you very much!
I too would really like to see an easy way to do this. Here in Canada, we are still stuck on 1.0 because our phone providers don't give a flip about their customers and refuse to cooperate with Samsung to provide updates. I highly doubt we will ever see an official 2.0. If someone could please figure this out, you would be a hero.
ferrloz said:
Very good, I think for what you asked must change the UMTS bands amms.bin modifying the firmware. It is long and you have to use complicated tools but each values what does And what he wants.
AMMS = Advanced Mobile Subscriber Software (Qualcomm by)
Qualcomm is a U.S. company founded in 1985 to produce chipsets for wireless technology CDMA and W-CDMA. Also responsible for the Eudora email client.
Among its main products, there Brew platform for creating applications for mobile devices.
It is one of the leading suppliers of processors for smartphones.
As we all know, our phone has AMSS, which is a driver software provided by Qualcomm, and telecommunications technology company.
As I researched, the AMSS functions as driver for this phone can connect to GSM, UMTS, among other things ...
There are tools, developed by Qualcomm, to enter the phone memory and calibrate the chipset, and my first thought when I heard this was in Latin Bada 1.2/2.0 + 3G.
I was hanging around in A and Developers Samsung universe and more or less able to operate the phone, and from what I saw, it is likely that the cell can be calibrated to use the bands that we need, but require a more advanced.
Below I leave a mini instructions on how to configure the phone and install the software if they want to investigate yourself. I believe that here comes the hand so that we can edit the file AMSS.bin and to use any firmware!
Clarified that are complicated and use tools that can write data on the phone, so, chances are corrupt memory to leave the cell unusable, everyone assumes their own responsibility to manipulate this program.
You need the following software is easy googling of last I can send PM's
- Qualcomm CDMA Technologies MSM driver
- Qualcomm QPST 2.7 Tools
- PSAS 1.5
Does not work on 64bit versions.
You must first change the USB connection mode of the Wave, for that we must enter the code * # 197328640 #
Then choose the following options
[8] Common> [7] SERVICE Configuration> [2] DIAG SERVICE Config> [2] USB DM / CP
Remember that the default connection mode is "[3] UART / AP" just want the connection back to normal.
Now that the cell is ready, connects to the PC and proceed to the installation of drivers, which by default is going to install one called "Samsung HS-9002 USB Diagnostics" which should be replaced by another driver.
-Open the Device Manager
-Where it says Ports Com & LPT search "Samsung HS-USB Diagnostics 9002" and the properties ponele "update driver" and select "Have Disk" to select it manually.
-In the package of "Qualcomm drivers" who have downloaded the driver select "msmdm.inf" (You have to remove the option "Show compatible hardware"), and the device list select "Qualcomm Diagnostics Interface 3197".
The end must be as follows:
Well, it already has configured the cellular to enter the internal configuration to do is to install elQPST Tools 2.7 and configure the COM port.
Start from the Start menu the "QPST Configuration", go to the tab "Ports" to add port go to "Add new port ..." and select the port "COMxx - USB / QC Diagnostic", then press ОК, should appear in the list, but the important thing, in the "Phone" must appear "QSC6270/QSC6240 (DEAD00D)", this means that the phone was recognized correctly and is ready for manipulation. If not, then you did something wrong ...
The tool I used to see some of the parameters was the "RF NV Item Manager". This program can read the phone's configuration parameters, you can also delete, edit and add new parameters ... but as I said before, is risky and if they know they are doing, I recommend not meddle.
When you open the "RF NV Item Manager" press the first button "Read from phone RF NV Items" and will start charging a nice list (as pictured below)
Pulling error, look at the top menu "Settings> ComPort" and select the port cell. (To know what, go to Device Manager under "Ports Com & LPT" and read from that port is "Qualcomm Diagnostics Interface 3197 (COMXX))
This list shows the NV Items, each one is configured with hexadecimal values, which can modify, delete, add, etc. .. as I said before.
You can also export to a. QCN which when opened can also be exported to TXT.
I warn you that among all these items, is the information of IMEI, so I recommend that no protection of their SETTINGS throughout the internet. The IMEI is in the NV Item 550 [NV_UE_IMEI_I].
My research was based on export a list of items in. QCN
First exported from my cellular with a 3G Firmware 1.0.2 with Latin America.
After the cell flashie a European Firm with Bada 1.2 (not 3g obviously) and went back to export another list. QCN
Comparing both configurations found 40 differences between the two configurations
The Latin American firm contains items that the European NO, such as:
said:
NV item: 3974 [NV_WCDMA_800_TX_PDM_LIN_1_I]
NV item: 3975 [NV_WCDMA_800_TX_PDM_LIN_2_I]
NV item: 3976 [NV_WCDMA_800_TX_PDM_LIN_3_I]
NV item: 3978 [NV_WCDMA_1900_TX_PDM_LIN_1_I]
NV item: 3979 [NV_WCDMA_1900_TX_PDM_LIN_2_I]
NV item: 3980 [NV_WCDMA_1900_TX_PDM_LIN_3_I]
Yes sir! UMTS bands are for Latin America as expected ... (UMTS or 3G WCDMA means)
And in the European Firm are other items that are not in Latin, as:
said:
NV item: 3984 [NV_WCDMA_900_TX_PDM_LIN_3_I], index 0
NV item: 5055 [NV_WCDMA_900_TX_LIN_MASTER_0_ENH_I], index 0
NV item: 5059 [NV_WCDMA_2100_TX_LIN_MASTER_0_ENH_I], index 0
NV item: 5061 [NV_WCDMA_900_TX_PDM_LIN_0_ENH_I], index 0
As expected, in this case refers to the European bands ...
With eggs in my throat ADD encourage the items found in firmware settings AMERICAN in my cell, which currently has no 3G bada 1.2, and thus prove that happens.
This can be done by generating a customized list of "NV items". To do this they must enter the "RV NV item manager" and press the button "Read form QCN file" and select the file (I had an export in. Qcn bada 1.0). Then in the menu "Option" select "Customized NV item list" and removed items that were already in the European firmware and let those of Latin America. Then press the button "Write listed items to the phone. (Override the Existing ones)"
This phone only write in the items I selected, but if any item that was already on the phone, it replaces the list.
After adding these parameters and restart the phone, still no 3G, no change I noticed in the cell may have to enable SETTING some more, so that bada 1.2 hablitado already understand that to use the local UMTS bands, but good is a matter of investigate ..
Then I installed the program PSAS 1.5, this tool also can read and edit the phone NV items, you can even see other items not marked with the "RF NV Manager items," such as item 2757 which is the product code, which can be changed also.
What I did was:
PSAS Open and go to "Hardware Forensics" -> "Use Mobile Ports" -> choose "Serial Com Port COMXX - Qualcomm Diagnostics Interface 3197 (COMXX)" In the same window go to "DIAG" and in " Diag Functions "drop down list and choose" Display NVitems ". Where it says start I wrote the item number that you "add" to the European firmware, such as 3980 and then you click on "Let's Go"
And below, the outcome QUAD going to say "Inactive item" ... mmmmm
P.D. I just do not probe the results conexsiones
Greetings to all!
Click to expand...
Click to collapse
That's something I wrote Taringa.net forum, the wording is of my authorship, simplifying everything I learned in xda developers (thanks to adfree). Here is the original post.
Advanced skills are needed to "calibrate" the S8500's modem wherever possible with Qualcomm tools...
Instead of only modifying the settings (NV, etc) a you did, why not generate a new amss.bin file with the new settings, and then reflashing the phone only with that new file?
Maybe this way the phone can acept the modifications... In case of freezing... just reflashing the european file back and the phone would be back again....
Just guessing...
Confirmed working on the SPH-D700 Epic 4g, SPH-D710 Epic 4G Touch, SPH-L700/SCH-I515 Galaxy Nexus and SPH-L710 Galaxy S III
I have a DIAG script for the LG Optimus G LS970 here.
No more flashing back to Touchwiz! The following scripts enable USB Modem/Diag mode in AOSP roms(CM9/CM10/AOKP/etc). For those new to this, USB Modem mode is used to interface with Windows CDMA tools such as QPST, QXDM, DFS and CDMA Workshop. Modem mode has always been possible in stock Touchwiz roms using dialer codes. The issue has been AOSP roms not working with the modem mode dialer codes... requiring flashing back to stock TW to use it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
<--------- Doesn't work in AOSP
Few examples of what modem mode could be used for:
[HOW-TO][FIX] Repair your IMEI with QPST - updated w/ info
[How To] Upload a custom PRL to your Epic Touch 4G
[CDMA] 威盛 VIA Repair and Reprogramming
You can use a script manager to run the script. Open script manager, browse to script files on SD card, select script, set to run as SU and hit save. Do this with both scripts. Now you can use the script manager in the Widgets section to create shortcuts on the desktop for easy access. Hopefully these scripts get built into CM10 so this method is no longer needed.
You may or may not have to unplug/plugin the usb cable after new mode is set.
Samsung Epic 4G SPH-D700
Use in terminal emulator/adb or add to script.
**As of Oct 1, 2012... all SPH-D700 CM10 builds have working diag mode via *#*#8778#*#* menu thanks to bbelos. Script is not longer needed on those roms.**
**The SPH-D700 script below is confirmed working on the official TeamEpic CM9 builds**
Modem
Code:
echo MODEM USB > /sys/class/sec/switch/usb_sel
PDA
Code:
echo PDA USB > /sys/class/sec/switch/usb_sel
Samsung Epic 4G Touch SPH-D710
E4GT is working but being picky. If not detected in QPST correctly... connect phone to USB cable. While phone is in normal USB PDA mode open up QPST Service Programming > Server > Stop QPST Server. Now run the CP script(or run the commands in terminal emulator as SU) then pull out the USB cable then put it back in. Wait a second.. you should see a serial port being detected in Windows Device Manager. After port has been added and drivers installed.. go back to QPST Service Programming and enable the QPST Server. Your device should now be detected properly. If you disconnect your phone while QPST Server is running you will have to toggle it off/on again for the phone to show back up.
CP
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo CP > /sys/class/sec/switch/set_usb_path
echo 1 > /sys/class/android_usb/android0/enable
CP v2
thx2squash
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo disable_wimax > /sys/devices/platform/i2c-gpio.17/i2c-17/17-0008/port
echo enable_cp > /sys/devices/platform/i2c-gpio.17/i2c-17/17-0008/port
echo disable_ap > /sys/devices/platform/i2c-gpio.17/i2c-17/17-0008/port
echo CP > /sys/class/sec/switch/set_usb_path
echo 1 > /sys/class/android_usb/android0/enable
ALL (AP+CP)
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo ALL > /sys/class/sec/switch/set_usb_path
echo 1 > /sys/class/android_usb/android0/enable
AP
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo AP > /sys/class/sec/switch/set_usb_path
echo 1 > /sys/class/android_usb/android0/enable
AP v2
thx2squash
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo disable_wimax > /sys/devices/platform/i2c-gpio.17/i2c-17/17-0008/port
echo enable_ap > /sys/devices/platform/i2c-gpio.17/i2c-17/17-0008/port
echo disable_cp > /sys/devices/platform/i2c-gpio.17/i2c-17/17-0008/port
echo AP > /sys/class/sec/switch/set_usb_path
echo 1 > /sys/class/android_usb/android0/enable
Samsung Galaxy Nexus (Sprint/Verizon)
Script works great for me on my Sprint Gnex. Varied reports about script working on Verizons. If script fails use terminal emulator instead.
MODEM
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo MODEM > /sys/devices/tuna_otg/usb_sel
echo 1 > /sys/class/android_usb/android0/enable
PDA
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo PDA > /sys/devices/tuna_otg/usb_sel
echo 1 > /sys/class/android_usb/android0/enable
Samsung Galaxy S III (Sprint/Verizon/US Cellular/AT&T/T-Mobile)
Use the script!
DIAG+ADB
Code:
#/system/bin/sh
# sets DIAG mode
echo 0 > /sys/class/android_usb/android0/enable
echo 04E8 > /sys/class/android_usb/android0/idVendor
echo 6860 > /sys/class/android_usb/android0/idProduct
echo diag > /sys/class/android_usb/android0/f_diag/clients
echo 1 > /sys/class/android_usb/android0/f_acm/instances
echo diag,acm,adb > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
start adbd
MTP+ADB
Code:
#/system/bin/sh
# sets default USB mode
echo 0 > /sys/class/android_usb/android0/enable
echo 04E8 > /sys/class/android_usb/android0/idVendor
echo 6860 > /sys/class/android_usb/android0/idProduct
echo 1 > /sys/class/android_usb/android0/f_acm/instances
echo mtp,acm,adb > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
start adbd
Samsung Galaxy S IV (Should work on ATT, Tmo, Sprint, Verizon, Cricket etc...)
DIAG+ADB
Code:
#/system/bin/sh
#reboot phone to disable
#enables diag mode
echo "0" /sys/class/android_usb/android0/enable
echo "04E8" /sys/class/android_usb/android0/idVendor
echo "685D" /sys/class/android_usb/android0/idProduct
echo "diag,diag_mdm" /sys/class/android_usb/android0/f_diag/clients
echo "hsic" /sys/class/android_usb/android0/f_acm/acm_transports
echo "diag,acm,adb" /sys/class/android_usb/android0/functions
echo "1" /sys/module/ci13xxx_msm/parameters/streaming
echo "1" /sys/class/android_usb/android0/enable
Original post has been removed since this has been solved. For reference it has been moved to post 5.
Subscribed. Would love to have this feature on CM9 for the epic 4g touch.
Hi, I will try to help you as much as time allows.. But I'm easily confused as I'm trying to understand several different platforms, chipsets, models, AOS versions etc etc. So let's try to be very precise, to make sure that other people (not having an SPH-D710 or NS4G) also can benefit from this discussion. Please consider using:
(a) specific model numbers, in addition to generic names such as "SGS2".
(b) XDA-thread names/titles with posted links so that we don't have to waste time clicking on every link just to find out we have already read it. E.g. like this: "Kernel serial console on I9100".
(c) What exact steps you use to obtain a certain type of output.
Sorry for being anal about this, but it quickly gets really confusing and annoying otherwise, once you start following 30+ threads... Having said all this we can move On-Topic.
--------------------------- updated --------------------------------
[Partial re-post of PM]
Your phone is using the Qualcomm QSC6085 baseband processor, which means that your SPH-D710 is basically completely different from the GT-I9100. Thus it is most likely that the chips used (MUX) to interface with mUSB are also different, and if they are not, they must surely be wired differently to accommodate the modem chipset. The resistor values mentioned is valid for most Samsung phones using the FSA9280A mux, for other devices I have no idea, but given the laziness of Samsung they may still be implemented in various other ways..
Many issues with AOS, is with file-permissions. Another is that you may need to reboot, before certain settings take effect. Third is that there are internal mux's used/controlled by baseband with the +CMUX AT-command (and others). But one thing is for sure, Samsung doesn't want their service people to waste time with all this hacking. So yes, USB service mode (to talk to and tune the modem) via USB cable must be available somehow...
autoprime said:
While in AOSP we have no modem access. via computer or through the phone itself.
Click to expand...
Click to collapse
THAT is exactly what I find strange. You see on both my I9000 and I9100 when you connect your phone without using "modem" (as you put it), it still enables the (virtual-serial-usb) modem interface as an additional device. If I use the PhoneUtil menu to change USB to MODEM, I loose normal connection since windows ask to install proper drivers (referring to 7-CDC.) I don't know what that driver is or where to get it. (In fact it may already be present on my computer as part of the multiple driver CDC that was installed with first time use of Kies.) But perhaps need to be pointed to again, for activation...
For example, on a Vista machine the drivers are located under:
../Program Files/Samsung/USB Drivers/25_escape
There's a bunch of files located there, but the most relevant ones (for me) seem to be:
Code:
ssuddmgr.inf --> Install USB Device Management Serial Port Driver SSUD.DeviceDesc = "SAMSUNG Mobile USB At Command Port "
ssudmdm.inf --> Install CDMA USB Modem device driver SSUD.DeviceDesc = "SAMSUNG Mobile USB Modem"
ssudmdm.cat* -->
Do you also have these or are the ones you use different?
looking at my drivers.. they were indeed pulled from a Kies install and it is using those same drivers. Unfortunately it is not the drivers at fault here.. there is no detection taking place at all. The phone is not making the switch from USB PDA ---> Modem. Viewing Logcat while performing the *#*#8778#*#* PhoneUtil toggle shows no action being performed. And manually setting the mode to Modem via "echo MODEM> /sys/class/sec/switch/usb_sel" only kills the USB detection entirely.
... just the appropriate drivers for Diag mode itself. My computer can see all other phones in diag mode...
Click to expand...
Click to collapse
Which are these?
The very same ones you've mentioned establish a successful "Modem" connection to PC when using Stock Touchwiz on the SPH-D710.
Click to expand...
Click to collapse
Please post the output of:
Code:
# cat /sys/kernel/debug/usb/devices
# ls -l /sys/bus/usb/drivers/cdc_svnet
"No such file or directory" for both. The folder structures seem to be different.
Click to expand...
Click to collapse
Also, it is very important to understand that the ServiceMode application is actually running just as a wrapper for the real code, which is usually running in the baseband. This where all the hardware (MUXes, USB, i2c interfaces etc) are specified, that is used to communicate with modem. However, this may be working differently on your BP, and may be instead done in the RIL libraries, etc.
------------ Final PM Response --------------
Unfortunately it is not the drivers at fault here.. there is no detection taking place at all. The phone is not making the switch from USB PDA ---> Modem.
Click to expand...
Click to collapse
Ok, I know I am not coming across very clear, because we apparently have such different devices! Let me try to explain again.
1) I don't know why you insist you need to "make the switch" at all? On the I9100 there is no need to make this "switch" to get modem serial communication port. Why do you think you need it on yours?
2) In fact, unless you know for sure that your phone contain some (or the same) type of USB/UART switch IC (aka MUX) as in the I9100, there is no reason to expect you to have this "switch" functionality.
3) The USB drivers can do much of this virtual switching magic in software (by themselves). But really I have no clue how those things work in detail! Like I mentioned there are 7 "drivers" doing various ****, that is installed with Kies... How, and under what circumstances these are activated and used, is beyond me. (Or better, you can read how USB ports are activated on Wikipedia and about USB composite devices (CDCs) here.)
4) If you're still convinced that you need to do this switch, there is one more trick. You can try to use this tool (thanks to KickerTom in this post) to list the contents of your /mnt/.lfs/param.blk file, in readable format, or in hex-format with:
Code:
# hexdump -C /mnt/.lfs/param.blk
(You'll need busybox to do this.)
You can use that tool to write and change stuff as well, BUT: Make sure you have a full backup!! The .lfs partion is not writable in the same manner as other types of partitions. It can only "grow", and never get smaller... AFAIK.
KickerTom further states:
From my experiments it looks like the SWITCH_SEL parameter is ignored by the HW, at least I haven't observed any real effect. But you can change the UART switch by modifying a file next to the param.blk, /mnt/.lfs/sw_sel. It contains an ASCII number, by default 1. That is modem uart. Change it to 3 to get PDA uart connected, by e.g. "echo -n 3 > /mnt/.lfs/sw_sel". 5) You may need to reinstall the "Qualcomm USB Host Driver"...
Autoprime, you don't get the mass appreciation, but for those of us who know what you are trying to accomplish, we appreciate it.
-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Everything between the lines was originally in the OP as part of the unsolved, [Q] Enabling USB Modem(Diag) Mode on Samsung CDMA Devices w/ AOSP thread.
Currently on the Epic 4G Touch SPH-D710 we are not able to put the phone into USB Modem/Diag mode while using an AOSP rom. This is normally toggled through the PhoneUtil apk with *#*#8778#*#*. To this date, the fix has been to restore back to a stock Touchwiz rom or to boot a Touchwiz rom off the SD card. To my knowledge, outside of the Nexus S 4G(SPH-D720), no CDMA Samsung AOSP roms have USB Modem mode working. This thread is being created to help solve this issue.. for ALL SAMSUNG CDMA DEVICES. Modem/Diag Mode works on HTC, Motorola, LG.. it should work for Samsung devices too
USB Modem/Diag Mode establishes a serial-over-usb connection which allows us to use special Qualcomm tools like QPST and QXDM to talk to our phones. We can access the hidden EFS partition including the non-volatile memory to edit all sorts of values.. we also use this for updating PRL's.. etc etc. It has it's value.. although Samsung and the carriers don't want us in there
I see USB Modem mode in AOSP being possible in two ways.
1. Since the Nexus S 4G(SPH-D720) on Sprint is on AOSP and has working USB Modem/Diag mode.. figure out how the NS4G achieves this mode.
2. Use a hardware jig of some sort to boot into USB Modem/Diag mode.
1. For the software side of things here's some highlights I've come across..
a. Logcat of Nexus S 4G(SPH-D720) while toggling USB Modem/USB modes - http://pastebin.com/TfcSHzYB
b. In terminal emulator/ADB we have "radiooptions" command with some interesting output. QXDM Enable/Disable is what interests me in there. QXDM enable would seem to allow the phone to interface with QXDM.. QXDM requires a USB Modem(Diag) Connection to talk to the phone. Attempting the "radiooptions 3" command does nothing(even on the NS4G). Only command that does seem to work is Radiff which requires a reboot to get working again.
Code:
0 - RADIO_RESET
1 - RADIO_OFF
2 - UNSOL_NETWORK_STATE_CHANGE
[B] 3 - QXDM_ENABLE
4 - QXDM_DISABLE[/B]
5 - RADIO_ON
6 - SETUP_PDP apn
7 - DEACTIVE_PDP
8 - DIAL_CALL number
9 - ANSWER_CALL
10 - END_CALL
c. Use manual commands to enable/disable the USB Modem/Diag mode as TheBeano has shown us here in his Fun with resistors (home/car dock mode + more) thread.
You can see what the current state is with this command:
Code:
cat /sys/class/sec/switch/usb_sel
You can change the state with:
Code:
echo PDA> /sys/class/sec/switch/usb_sel
or
echo MODEM> /sys/class/sec/switch/usb_sel
Currently on the E4GT SPH-D710 enabling MODEM and then connecting the device to Windows results in no connection/USB detection at all. Phone is detected in PDA mode only. In addition, using the PhoneUtil menu(*#*#8778#*#*) and setting the USB mode to "Modem" has no effect at all.
2. As for the hardware side of things, I've been reading through XDA and came across some interesting threads in the SGS2 I9100 forums. A post by E:V:A specifically that mentions putting the phone into different modes by using resistors.. which I suppose would be the same thing as the jig's people have been using to reset their ODIN flash counts.. only using different resistors: Kernel serial console on I9100.
301K looks to be what we use for the standard jigs. that is documented here: [GUIDE] How to Make a USB Jig and Get Rid of Yellow Triangle+ODIN Counter reset. I wonder if there is a mode we can force which establishes USB Modem mode ON and then use serial-over-usb.. like how it works when we set Diag mode in touchwiz roms. AdamOutler has thread dealing with the E4GT pinouts etc.. not sure if this would help at all: Processor datasheets required(E4GT SPH-D710)
Code:
xOM_0=pin E3
xOM_1=pin D2
xOM_2=pin C3
xOM_3=pin E4
xOM_4=pin F2
xOM_5=pin A3
xOM_6=pin F3
I have no idea if anything I've said helps... just putting some ideas out there and hopefully get some people who DO actually know this more advanced stuff to join in I have HTC phones, LG phones, multiple Samsung devices.. Epic(SPH-D700), NS4G(SPH-D720), E4GT(SPH-D710). I can provide any logs needed for those devices.
Random references to Diag mode and AOSP on CDMA devices:
Cannot enter Sprint ## CDMA codes on dialer, need DIAG mode! (HTC AOSP DIAG)
Updating PRL on CM7 (Samsung CDMA AOSP)
Epic Dialer Codes working on CM7
DIAG ##3424# using an AOSP ROM CM7 (Various CDMA HTC methods mentioned)
QPST DIAG Mode CM7 Aka ##3424 (HTC Droid Incredible ADR6300)
Fun with resistors [home/car dock mode + more] (Manually enable/disable UART)
-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
E:V:A said:
Ok, I know I am not coming across very clear, because we apparently have such different devices! Let me try to explain again.
1) I don't know why you insist you need to "make the switch" at all? On the I9100 there is no need to make this "switch" to get modem serial communication port. Why do you think you need it on yours?....
Click to expand...
Click to collapse
It seems the more we compare notes.. the more we see how different the I9100 and SPH-D710 really are. Without getting into technical specifics I can give you a reason why some things are so different... which is how CDMA and GSM differs really. Looking at "security" alone.. GSM uses a SIM card to authenticate on the network.. outside of the IMEI(which seems to be rather accessible on your devices) the SIM card contains most of info the network is looking for. On our devices CDMA devices, ALL of the authentication info is stored on the device itself. Carriers/Manufacturers do NOT want use touching the hidden EFS partition.. where all of our authentication values reside.. ESN/MEID, EVDO username/passwords, PRL.. etc etc. So now, the main key to accessing this hidden partition... USB Modem(Diag) Mode!
I have taken some screenshots of Windows Device Manager. Far left is my Device Manager with no phone plugged in. Middle is phone plugged in but USB Mode is set to "PDA". Right side is phone plugged in and USB Mode set to "MODEM".
You can see the difference in the device manager... USB Modem mode giving us a serial diagnostic COM port. This COM port is ONLY available when the phone is set in this specific mode. ONLY when the diagnostic COM port is available can we use Qualcomm software to view the hidden EFS partition of our devices and start to tweak things. For the above image I used a Nexus S 4 G(SPH-D720) which naturally runs on AOSP and has this USB Modem mode working. This mode also work on Touchwiz roms. It does NOT work on AOSP in any other Samsung CDMA phone(the purpose of this thread).
I hope this sort of explains why our phone may be "locked down" a bit more due to how CDMA works... and also explains how I am sure that we need this USB Modem mode toggled.. and that I am positive Windows is set up properly etc etc. The issue is that we can not force the phone, while using an AOSP rom, into this diagnostic serial mode.
^^ Very good. I understand. Now, can you reproduce the middle picture for your E4GT?
autoprime said:
You can see the difference in the device manager... USB Modem mode giving us a serial diagnostic COM port. This COM port is ONLY available when the phone is set in this specific mode. ONLY when the diagnostic COM port is available can we use Qualcomm software to view the hidden EFS partition of our devices and start to tweak things. For the above image I used a Nexus S 4 G(SPH-D720) which naturally runs on AOSP and has this USB Modem mode working. This mode also work on Touchwiz roms. It does NOT work on AOSP in any other Samsung CDMA phone(the purpose of this thread).
Click to expand...
Click to collapse
Not sure if it helps you figure out how to get it enabled, but the USB port on E4GT is able to support both PDA and MODEM mode simultaneously. They aren't mutually exclusive.
E:V:A said:
Now, can you reproduce the middle picture for your E4GT?
Click to expand...
Click to collapse
Yes, the exact middle picture is produced on the E4GT. USB Composite and USB Mass Storage Device both show up. When toggling the PhoneUtil from PDA to Modem.. no changes in Device Manager happen. Tried toggling the UART selection in PhoneUtil as well just to see what would happen... no change as well.
sfhub said:
Not sure if it helps you figure out how to get it enabled, but the USB port on E4GT is able to support both PDA and MODEM mode simultaneously. They aren't mutually exclusive.
Click to expand...
Click to collapse
You're saying the E4GT can be seen on a computer as a mass storage device as well as enabling the diagnostic serial port.. at the same time? could you go into this more? have an example?
sfhub said:
Not sure if it helps you figure out how to get it enabled, but the USB port on E4GT is able to support both PDA and MODEM mode simultaneously. They aren't mutually exclusive.
Click to expand...
Click to collapse
That's what I've been trying to tell you guys all along, and I understand my message have not been very clear. This is because I don't quite understand how this works, but that is kind of the whole point with using a USB "Composite Device". The mere fact that you are using adb and can use Kies, is good enough for you to have several virtual (including serial) connections. I already posted a link above, about this. Did you read it?
Also in the middle picture there is an additional icon that is not present in the other two, "Portable Devices". You should run a USB sniffer (eg. USBlyzer ) to find out what happens when you connect, both with the Nexus S and your E4GT.
In addition, what you have marked as "not what we want" in the RHS picture, may in fact be exactly what you want. Because I'm getting more convinced that your Qualcomm tools (from 2006) are seriously outdated. It may just be a matter of updating some drivers, but who knows...
autoprime said:
You're saying the E4GT can be seen on a computer as a mass storage device as well as enabling the diagnostic serial port.. at the same time? could you go into this more? have an example?
Click to expand...
Click to collapse
Yes, on any stock GB ROM, ##8778#, select All to have both modes enabled (AP and CP will result in just one of the modes being enabled). Haven't tested on ICS.
Any progress??
I'm sure getting the touchwiz ics source code once we get an official ota will greatly help this project.
Sent from my SPH-D710 using XDA
E:V:A said:
Any progress??
Click to expand...
Click to collapse
there are /mnt/.lfs files in touchwiz only.. they are missing in AOSP. AOSP file structure seems to be much different. I believe the issue is a lack of "Diag" code in the AOSP code itself. We need to figure out the code in the Creso4G source(Nexus S 4G SPH-D720) which allows diag mode to be enabled and port it to our own device.
I was having this same problem on my Epic 4G (non-Touch), running a custom ROM. I wanted to change my PRL manually and the phone COM port would never appear in Device Manager in phone Modem mode - nothing happened.
I was able to fix it, after considerable trial and error, but I'm not sure the fix will translate to the Touch.
It was a driver issue - the computer finally installed the correct driver that allowed the phone modem to communicate with it and appear in Device Manager.
How I found it was a fluke deal - I had pretty much given up and decided to temporarily revert back to stock Gingerbread, figuring that would allow me to change the PRL and then I could re-flash the custom ROM.
I started the stock GB conversion process and ran into a roadblock right away - the COM port wasn't showing up in Odin. The conversion instructions emphasized installing a specific driver (older) for my phone, and I knew I had the latest Windows Update drivers for the Epic 4G installed - these were installed automatically in USB debugging mode. So I went back into debug mode and uninstalled the phone in Device Manager. I then disconnected the phone from the laptop, and installed the driver (64-bit) specified in the instructions. When I plugged the phone back in, I got a successful driver install confirmation.
Then, per the instructions, I unplugged the phone and put it into "download" mode (press 1 on the slideout keyboard along with the power button). Then I launched the required version of Odin and set it up with the stock GB file I had downloaded. The next step was to plug the phone back into the PC, and when I did that, I had Device Manager open and I noticed it installed a modem I had not seen before and COM3 showed up in yellow in Odin, indicating a good connection.
At that point, I shut down Odin, unplugged the phone and restarted both phone and PC. After the restarts, I switched the phone to Modem mode via ##8778# in the PhoneUtil, then connected again via USB and voila, there was the phone modem in Device Manager, using COM5. I went on to manually change the PRL using a procedure for the Epic 4G outlined elsewhere here on XDA.
Don't know if that will shed any light with resolving this issue with the Touch, but doing something similar might be worth a try.
^^ That is very good news! But I wish you could have been more specific in what drivers you found and/or installed, and what instructions you followed? (Also, what is the model number of that phone?)
gondo77 said:
I was having this same problem on my Epic 4G (non-Touch), running a custom ROM. I wanted to change my PRL manually and the phone COM port would never appear in Device Manager in phone Modem mode - nothing happened.
I was able to fix it, after considerable trial and error, but I'm not sure the fix will translate to the Touch.
It was a driver issue - the computer finally installed the correct driver that allowed the phone modem to communicate with it and appear in Device Manager.
How I found it was a fluke deal - I had pretty much given up and decided to temporarily revert back to stock Gingerbread, figuring that would allow me to change the PRL and then I could re-flash the custom ROM.
I started the stock GB conversion process and ran into a roadblock right away - the COM port wasn't showing up in Odin. The conversion instructions emphasized installing a specific driver (older) for my phone, and I knew I had the latest Windows Update drivers for the Epic 4G installed - these were installed automatically in USB debugging mode. So I went back into debug mode and uninstalled the phone in Device Manager. I then disconnected the phone from the laptop, and installed the driver (64-bit) specified in the instructions. When I plugged the phone back in, I got a successful driver install confirmation.
Then, per the instructions, I unplugged the phone and put it into "download" mode (press 1 on the slideout keyboard along with the power button). Then I launched the required version of Odin and set it up with the stock GB file I had downloaded. The next step was to plug the phone back into the PC, and when I did that, I had Device Manager open and I noticed it installed a modem I had not seen before and COM3 showed up in yellow in Odin, indicating a good connection.
At that point, I shut down Odin, unplugged the phone and restarted both phone and PC. After the restarts, I switched the phone to Modem mode via ##8778# in the PhoneUtil, then connected again via USB and voila, there was the phone modem in Device Manager, using COM5. I went on to manually change the PRL using a procedure for the Epic 4G outlined elsewhere here on XDA.
Don't know if that will shed any light with resolving this issue with the Touch, but doing something similar might be worth a try.
Click to expand...
Click to collapse
was this a touchwiz based rom.. or a aosp based rom?
Running the commands below as root will allow you to put your phone into modem mode from *#*#8778#*#*
chown radio /sys/bus/i2c/drivers/fsa9480/7-0025/switch
chmod 660 /sys/bus/i2c/drivers/fsa9480/7-0025/switch
AFAIK this only works for the Crespo4G I haven't been able to test on anything else.
NiteSnow said:
Running the commands below as root will allow you to put your phone into modem mode from *#*#8778#*#*
chown radio /sys/bus/i2c/drivers/fsa9480/7-0025/switch
chmod 660 /sys/bus/i2c/drivers/fsa9480/7-0025/switch
AFAIK this only works for the Crespo4G I haven't been able to test on anything else.
Click to expand...
Click to collapse
Prompts for msl, then gives a modem exception error on CM9 for e4gt.
Sent from my CM9 Epic 4g Touch using Forum Runner
SU PM enable com.samsung
I executed command disable com.samsung ot to get OTA FF18 updates since I am rooted. Then without thinking when to the google store and it told me that the background data was and it gave me an option to ok to turn it on.
Ever since them I can not get to play store it tells me I am not connected but I am . Try to do a able com.samsung command but returns disable.
any suggestions?
thnaks
I am running FF18 rooted stock
COM port not detected
EPIC 4G on stock EC05
All drivers installed
the phone goes into diagnostic mode but does not get detected.
is there any other way to get the phone to connect in CDMA ws ?
Phone was detecting on COM port earlier until i mistakenly uploaded
the Galaxy S3 SPH-L710 NV Item file which i had save from my Galaxy S3.
Instantly i lost my carrier signal and lost connection from CDMA ws.
i rebooted to check. did ##8778# goes to phon utils but even if i select MODEM under USB the modem is not
detected in COM port. just to check if my Drivers were correct or not, i connected my Galaxy S3 in Diagnostic mode..
the phone is detected under COM port but not my EPIC
I Odin back to Stock EC05 and tried without & with root. the phone is not detected on diagnostic/service mode. its detected
on PDA.
Need help to reset the phone so that i can get the phone to work on CDMA ws.