saving dmu secret keys

[shadowmite]

If you get the HA key from the mip profile 1 you will be able to read it as plaintext. The profile 0 16 byte key however is binary and will require qxdm to extract it. I should note, profile 0 is used for OTA provisioning of the mip profile 1. profile 1 is used for actual data.

[superdupe]

thx for the info...

can you explain how to use qxdm to save that info? also will i be able to use it again without a dmu reset if i flash and then put that info back in?

last q, you said the info shows up in plain text... can i re-enter the plain text into the default MIP profile?

[Ultima]

Originally Posted by superdupe

thx for the info...

can you explain how to use qxdm to save that info? also will i be able to use it again without a dmu reset if i flash and then put that info back in?

last q, you said the info shows up in plain text... can i re-enter the plain text into the default MIP profile?

Good question, I'm having the same issue, though my method for fixing is a little different. Do an ESN change to another device. Make a test call with it to make sure its authenticated (#832 works) and then try the data connection to make sure its fully functional. Then put your Touch Pro back on your account and it should regenerate the keys needed for your EVDO.

NOTE: It is wise to make sure the device you are NOT in the process of activating is turned off (or in flight mode) as sometimes it can cause data auth issues.

[JBHorner]

Originally Posted by shadowmite

If you get the HA key from the mip profile 1 you will be able to read it as plaintext. The profile 0 16 byte key however is binary and will require qxdm to extract it. I should note, profile 0 is used for OTA provisioning of the mip profile 1. profile 1 is used for actual data.

My Profile 1 doesn't populate. In fact, it says disabled.

Joel

[Ultima]

Originally Posted by JBHorner

My Profile 1 doesn't populate. In fact, it says disabled.

Joel

Same. I'm guessing QXDM will be the final solution to this problem.