Thanks to Dave Amenta, i got around to the Registry Editor in the Dell Venue Pro. I am able to read values, but not able to set them..May be i am doing something wrong. I am giving it to the community to crack it open.
Here is what you need to do to get to the registry editor:
1. Go to the EM App in the DVP.
2. Choose RD Test. It will prompt for a textbox to enter something (its basically asking for password). Enter *#6336# . Now voila, you are in MFC Test.
3. Scroll to the bottom of the list and choose About EM.
4. Now it will say sorry..bla,.bla.. It will also have a textbox for another password. Enter *#734#
5. Voila you are in Registry Editor.
6.To read a value, go to the 'Path' prompt. While in, choose L M/C R/C U, etc..they are nothing but HKEY_LOCAL_MACHINE\HKEY_CURRENT_USER,etc.. Then enter the remaining path name. In the Key field, enter the key you want to query. In the Type, press the down arrow and choose the type. Now hit the 'Get' button on top, you will see the result (If you enter all right). If you want to set data, i think you enter the value in Data field and hit set. But, so far no luck. Iam still researching.
IMPORTANT: DO not do this as this is super advanced user mode. You might end up brick'ng ur DVP if you do not know what your are doing.
This sounds awfully similar to the LG registry editor on the phone. I do not have a DVP in my possession, but I know a friend who does. I shall try this and let you know how it goes. (BTW, Dell Venue Pro works on Wind and Mobilicity in Canada)
I am trying to do a AT Hyperterminal command to unlock the phone.,Will see how it goes.
notebookgrail said:
Thanks to Dave Amenta, i got around to the Registry Editor in the Dell Venue Pro. I am able to read values, but not able to set them..May be i am doing something wrong. I am giving it to the community to crack it open.
Here is what you need to do to get to the registry editor:
1. Go to the EM App in the DVP.
2. Choose RD Test. It will prompt for a textbox to enter something (its basically asking for password). Enter *#6336# . Now voila, you are in MFC Test.
3. Scroll to the bottom of the list and choose About EM.
4. Now it will say sorry..bla,.bla.. It will also have a textbox for another password. Enter *#734#
5. Voila you are in Registry Editor.
6.To read a value, go to the 'Path' prompt. While in, choose L M/C R/C U, etc..they are nothing but HKEY_LOCAL_MACHINE\HKEY_CURRENT_USER,etc.. Then enter the remaining path name. In the Key field, enter the key you want to query. In the Type, press the down arrow and choose the type. Now hit the 'Get' button on top, you will see the result (If you enter all right). If you want to set data, i think you enter the value in Data field and hit set. But, so far no luck. Iam still researching.
IMPORTANT: DO not do this as this is super advanced user mode. You might end up brick'ng ur DVP if you do not know what your are doing.
Click to expand...
Click to collapse
It looks like the button isn't wired up to perform the SET command - the event handler is there, the button is there, but clicking it even without entering any data should return "1", but it's not doing anything...
What do you mean by AT unlock? What commands are you going to send to the modem? Do you have the modem drivers? If not, take a look here: http://forum.xda-developers.com/showthread.php?t=929468
kltye said:
It looks like the button isn't wired up to perform the SET command - the event handler is there, the button is there, but clicking it even without entering any data should return "1", but it's not doing anything...
What do you mean by AT unlock? What commands are you going to send to the modem? Do you have the modem drivers? If not, take a look here: http://forum.xda-developers.com/showthread.php?t=929468
Click to expand...
Click to collapse
When i get home, i will post the Registry Set Command CS code.
AT command - Yes, the command to the modem. And yes, i used the HTC Modem driver you linked for the DVP. I am able to query the modem from the modem properties - but i can't enter any commands in that properties window. So i am going to do a hyperterminal to send AT commands for SIM Locking and try to unlock it.
I also came across a test called 'SIM Lock' in Protocol, which returns what is its locked to.
notebookgrail said:
When i get home, i will post the Registry Set Command CS code.
AT command - Yes, the command to the modem. And yes, i used the HTC Modem driver you linked for the DVP. I am able to query the modem from the modem properties - but i can't enter any commands in that properties window. So i am going to do a hyperterminal to send AT commands for SIM Locking and try to unlock it.
I also came across a test called 'SIM Lock' in Protocol, which returns what is its locked to.
Click to expand...
Click to collapse
The registry set command is:
IEmToCom.sync("EM:REGISTRY_SET:" + <path> + "," + <key> + "," + <data type, e.g. DWORD> + "," + <data> + "," + <path_type expressed as int> + ";", 1, false);
I was working with Dave over the weekend, but it looks like whatever value we insert is not being accepted - quite possibly because Dell hasn't implemented the interface yet.
this should surprise me and yet...
THIS IS DELL!
kltye said:
What do you mean by AT unlock? What commands are you going to send to the modem? Do you have the modem drivers? If not, take a look here: http://forum.xda-developers.com/showthread.php?t=929468
Click to expand...
Click to collapse
For the AT unlock, go to protocol, then TMO, then AT Command - Here you can pass various AT Commands. Unfortunately, we need the Password to reset any setting here. The password is 8 char long. And the DVP is 'ph-net pin' locked.
damn.....i think it probably means that we need to get the modem rom somehow in order to figure out how to generate the unlock PIN
I'm probably missing something really obvious here, but what does SIM unlocking have to do with registry write access?
kltye said:
I'm probably missing something really obvious here, but what does SIM unlocking have to do with registry write access?
Click to expand...
Click to collapse
It was a off topic discussion. I should have started a new thread for it. My mistake.
Is there anyone volunteering to reset their phone (cold boot)? I think i might have found the way to edit the registry. There are 2 modes for the EM App. One is Driver and another is socket. Not sure which one is by default. But i know how to change them. It requires a reset of the phone (cold boot) to take effect. I have too much of data on my phone to try it and reload everything. I can PM them the details and see if they are able to edit the registry.
notebookgrail said:
Is there anyone volunteering to reset their phone (cold boot)? I think i might have found the way to edit the registry. There are 2 modes for the EM App. One is Driver and another is socket. Not sure which one is by default. But i know how to change them. It requires a reset of the phone (cold boot) to take effect. I have too much of data on my phone to try it and reload everything. I can PM them the details and see if they are able to edit the registry.
Click to expand...
Click to collapse
You could try calling new EMToCom() rather than EMToComByDriver() when you initialize the connection, and see if that works. I've tried it and it seems that it fails to execute the command, with the debug window printing:
A first chance exception of type 'System.Runtime.InteropServices.COMException' occurred in EM.dll
calling COM receive error(socket) : 0xffffffff
I tried calling the turn on LED command via my flashlight app that works fine with the driver connection, but I'm getting the same exception when I connect via socket. Do you know if there's a special way to send commands if you connect via socket?
notebookgrail said:
Is there anyone volunteering to reset their phone (cold boot)? I think i might have found the way to edit the registry. There are 2 modes for the EM App. One is Driver and another is socket. Not sure which one is by default. But i know how to change them. It requires a reset of the phone (cold boot) to take effect. I have too much of data on my phone to try it and reload everything. I can PM them the details and see if they are able to edit the registry.
Click to expand...
Click to collapse
I'll be a guinea pig
domineus said:
I'll be a guinea pig
Click to expand...
Click to collapse
Sent you a PM.
Shoot me the details and I may be able to help out sometime this week.
it didn't work for me...doubt it will work for anyone else =/
domineus said:
it didn't work for me...doubt it will work for anyone else =/
Click to expand...
Click to collapse
Was it doing the same blank result box? Any difference did you notice with either the Driver or Socket option? - i mean not just registry editor, but overall.
blank result no changes =/
I hope we all find some progress on this because I believe that this is what is holding us back from a lot of customization on this phone....
Long road almost there, error 67 :( calls & text ) but no data :( [evo on boost]
THE GOOD AND BAD NEWS... THE GOOD NEWS FIRST! i got my evo4g over to boost mobile with my boost account i already had open i can outgoing text and recieve text (no mms right now) i can call out and get calls in, works great shows my boost cell phone number on my evo and everything..
NOW THE PROBLEM...
my DATA doesn't work at all... i get the error 67
I TRIED THESE INSTRUCTIONS AFTER SEEING MY DATA DIDNT WORK..
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If data is not working move on to the next steps...
(Note: These are steps not verified by me as I still dont have neither 1x nor Evdo working but some people say 1 or 2 or all of these following steps combined worked for them, so i guess it depends on the network you are trying to get on)
1. First attempt to update your profile if it can or update PRL
Menu>Settings>About Phone>System Updates>Update Profile
Reboot and see if data works....
2. If still no Data, plug in your Hero to the computer, dial ##3424#, go to QPST folder and open QPST Configuration app.
Under the Ports Tab if the active COM port your phone is on is not in that list Click Add Port and add it.
Then go to Active Phones Tab, select the phone and then go to Start Clients>Service Programming
A new window opens, hit ok, then click Read From Phone on the bottom left, its gonna ask you for your MSL type it in
Then go to the M.IP Tab and under user profiles click on profile 0, click edit, and then deselect Profile Enabled, hit ok, then click Write to Phone.
Close the program unplug your hero, reboot it, and try your data again.
3. If still no data, plug in your old phone to the computer, open up QXDM
check Connections and make sure your COM port is being read.
Go to View>New>Common>NV Browser , in the Category Filter drop down menu, filter only Data
Then scroll down to ID numbers 1192 and 1194
Click read and copy down all the values in there until u reach 0x00
Then unplug your old phone and plug in your hero, dial in ##3424# and go to NV Browser
navigate to the same ID numbers 1192 and 1194, (just to be safe copy all the values here so you can revert back to the originals)
Then double click each value under the input column and it becomes changeable and change all the values to the ones from your old phone and hit write
Close QXDM unplug and reboot your hero, test Data again
4. If still no data, plug in your old phone to the computer, open up QXDM
check Connections and make sure your COM port is being read.
Go to View>New>Common>NV Browser , in the Category Filter drop down menu, filter only Data
Then scroll down to ID numbers 465 and 466
Click read and copy down all the values in there until u reach 0x00
Then unplug your old phone and plug in your hero, dial in ##3424# and go to NV Browser
navigate to the same ID numbers 465 and 466, (just to be safe copy all the values here so you can revert back to the originals)
Then double click each value under the input column and it becomes changeable and change all the values to the ones from your old phone and hit write
Close QXDM unplug and reboot your hero, test Data again
NONE OF IT WORKED.... SO I WENT TO THE SECOND SET OF INSTRUCTIONS.
Run the QPST config and plug in your phone, make sure your phone is detected in the COM port list. If not click Add New Port and add the one that it has detected your phone on. What it says may vary but USB will often be in the description.
Run QXDM click Options -> Communications and set the Target Port for the same one QPST config listed for your phone.
In the command box at the top type "spc 000000"
Note: If your SPC is not 000000 then you need to use the correct number instead!
If successful you will see a window titled "Command Output" that will output some text with the final line reading "SPC Result = Correct"
Next in the command box type "requestnvitemread ds_mip_ss_user_prof"
This will get you a lot of stuff in the Command Output window. It will start with the "DIAG TX item" section, ignore this one, we are interested in the "DIAG RX item" part.
The actual keys are 16 lines and marked in the output as 0-15. You will notice that quite handily both HA and AAA are both there. Take the part after the "0x" and that is actual key data. Just write down (or use word, notepad, whatever) to record this for safe keeping.
If you are doing this right then you have a long string of 30 characters all strung together for each key. DOUBLE CHECK YOUR COPYING! A single mistake will cause this to fail.
Putting the keys back into the phone:
Load QPST service programming, go to the M.IP tab. Double click profile 0 (in the white box) and use "Enter hex value" to enter your backups of your HA and AAA keys.
Write to phone.
Soft reset. (may not be required but I do it for good measure)
do "requestnvitemread ds_mip_ss_user_prof" for the sprint info and "requestnvitemread ds_mip_ss_user_prof 1" for the boost info
I'm telling you.. If you're getting the error 67, the following these steps above will fix it.. I'm on the Sprint network and the problem i was having was, in "Profile 0" The username which began with A000000 (this is actually your ESN #) Was from the original phone, not the donar phone... So i took the battery out the donor phone and looked at the ESN (not DEC) and began to type A00000 etc.
Then i used the steps above to get AAA Shared Secret from the Donor phone.. My AAA Shared Secret was 32 Alpha numeric characters...
i did that and still no dice.... i got the AAA key and the HA key .. both were 32 characters...
i even went as far as to get the profile info from the incognito phone, for profile 0 and 1, and made it exactly the same on my evo and addresses for the HA and alternate HA ADDRESS... still no dice.. i went into debug mode on my evo and even hit the restore to start fresh , and let it download the data via the servers... still didnt work...
i even re-entered the profile info and etc, for profile 0 and 1, and still not working
i know im close i just need to finish the puzzle please help.
oh yea, and when i go into debug mode it shows the authentication as failed.. i dont know how thats even possible I've triple checked the HA AND AAA keys via QXDM and they are the correct keys from the incognito boost phone.
Any truth to this?
"Here is a easy way to unlock your LG Optimus 7 by using the LG MFG application. If you have no idea about this app, Google it, you will get what you want. LG Phone Problem and Solution
1.Open the MFG app and use the password to open it. If you don’t know it’s (appmfg#*#)
2.Go to Engineer Menu -> Other Settings -> Edit Registry
3.Set your ROOT PATH to "HKEY_LOCAL_MACHINE"
4.Set your input path to "\Comm\Security\LVMod"
5.Set your input key to "DeveloperUnlockState" and set to DWORD
6.Hit Query. Output result should return a "0". If it does continue.
7.Set your input data box to "1" and hit SET. Output result should be 1
Now your LG Optimus 7 is unlocked. Good luck!"
Is true, men. )
Working fine.
And from there just sideload away?
So I got an unlocked version of the sprint's LG G8 variant. Everything works perfectly excepet the wifi hotspot.
I can connect to it but I get the "No access to Internet" message. Any ideas why?
Thanks!
mariomtes said:
So I got an unlocked version of the sprint's LG G8 variant. Everything works perfectly excepet the wifi hotspot.
I can connect to it but I get the "No access to Internet" message. Any ideas why?
Thanks!
Click to expand...
Click to collapse
Download "Setttings database editor" by 4a. Open it up and click on Global properties, scroll down until you see "tether_dun_required". Change the value to zero. You now have internet via hotspot. It's best to buy the add on because it keeps the setting locked even if you restart phone. Enjoy?
Toni_RM said:
Download "Setttings database editor" by 4a. Open it up and click on Global properties, scroll down until you see "tether_dun_required". Change the value to zero. You now have internet via hotspot. It's best to buy the add on because it keeps the setting locked even if you restart phone. Enjoy?
Click to expand...
Click to collapse
Tried that. I get an error that says I can't edit that table
mariomtes said:
Tried that. I get an error that says I can't edit that table
Click to expand...
Click to collapse
Oh my bad i left out the most important part.
1. Install adb on your laptop (search it up)
2.On your phone go to settings, general, about phone, software info, find build number section and keep tapping until you are a developer
3. Go back to general and you'll now see developer options, turn developer options on and go down to usb debugging and turn it on.
4. Connect your phone to your laptop via USB (you will get a promt on your phone along the lines of "allow USB debugging?", click ok) and open up command terminal
5. Type "adb" and press enter
6. Type the command (without quotes) "adb devices". Your device should show up.
7. Type "adb shell" and press enter
8. Open up the settings database editor and go to global and scroll down to tether_dun_required. Click "edit value" and the shell command should pop up.
Type the shell command into adb shell and press enter
9. Go to the settings data base editor and go back to the tether_dun_required and click on change value. You'll notice that you are now able to change the value, change it to 0.
10. Enjoy your hotspot!
It seems like a lot of steps but it's not. The most "difficult" task will be installing adb.
Awesome. Got it to work now. Do you have to set it to 1 for the Ota updates or after each reset? Thanks again!
No, theres no need to set it back to "1". After you shut off your phone the setting value will turn back to a "1" and you hotspot wont work until you switch it back to "0". To save time you can buy the feature pack and you'll get access to settings guardian which will keep it at "0" at all times.