Jump to content

Stuff Missing


Recommended Posts

Guest Orangatang
Posted

TECHNICAL BODS, READ THIS CAREFULLY, WITH THE NEW UPGRADE YOUR UNLOCKING PROCEDURE IS NOW OUT OF DATE.

(Background story)

I got a new phone from CPWH after the headphone bit

got buggered (After 2 weeks)

I thought it was about time to unlock it

I backed up the whole phone to my spanking new mem card

I buggered up the phone royally trying to unlock it

I fixed the phone with the card backup - all ok.

Then.....(phone back to it's factory state)

(The Juicy Bits you should read)

I installed the update, formatted the card, went to unlock it only to find that the files are now different: mxipcold_oem10.provxml no longer contains the security bit, the mxip_oem10.provxml does but the whole file is much shorter, and there's another instance of the security characteristic in a file called mxip_smartphon_1.provxml.

I've got these files and pasted in the change where this characteristic occurs, but now i find i can no longer back up my phone to the card!!!!

So, i'm too chicken-s*** to attempt to apply these changes without backup, what should i do?

The only function in CanaryDiag 0.79 is EraseIPSM, what actually does this do and if I do it will it badword my phone or is it an ok thing to do?

I think the reason i screwed up the first time is that i booted the phone from the card half way through the process, it got half way through remaking WinCe and i pulled the back off (i know, risky).

So, will EraseIPSM do my machine in or what?

Tell me it's safe and i'll attempt to unlock my phone for the benefit of all SPV users in the future.

Cheers, Dan.

Guest ajb3000
Posted

EraseIPSM just reverts the phone back to its out of the box state.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.