Customer:
I have a problem with writing RPL to Phone:
1.After write RPL IMEI again is 1234....
2.When i write RPL i see in log:
Simlock send - FAILED!
SuperDongle send - FAILED!
3.After write PM part and FULL i have a contact retailer
Answer:
If phone is with RAP3G MCU use
THIS erse file to erase phone totaly.
If the phone is with RAPIDO MCU use
THIS erse file to erse phone totaly.
ALL NEXT STEPS IS IDENTICAL FOR 2 TYPES OF MCU
1.After you erase full phone need to flash it with latest available Firmware Version!!!!!!
When phone is flashed on a latest FW version he need to work fine but with IMEI 1234....(this is sure for good woking hardware)
2.Connect phone to cable, he need to be in a local mode.
3.For your certainty you can click on a 6th button "OK" to see cable is good or not. If you see BOOT OK then all with cable is ok.
4.Click on a button write RPL
After this operation if all is ok then you need to have a phone with good IMEI and SIMLOCK state.
5. Restart phone (will be good to diconnect and connect cable again) and load good PM into section for writing PM, check only 1,135 fields and click on a sx4 authorization button.
Need to see this :
Login...
IMEI: 35760300XXXXXXX
busy, waiting...
Connect...
Login...
busy, waiting...
PMM Authorize SUCCESSFULL
Only after see
PMM Authorize SUCCESSFULL click on a write selected button.
POSSIBLE REASON FOR :
Connect...
Login...
IMEI: 35760300XXXXXXXX
busy, waiting...
SuperDongle Authorization Procedure failed!
Failed to locate SX4 on PC. Connecting server
Connect...
Login...
IMEI: 35760300XXXXXX
busy, waiting...
e/640/command execution error;
is bad simlock data!!!!!
6. Power on the phone and if he is on a contact reatiler need to repeat procedure 5 but need to check all Fields WITHOUT 134.
Power on the phone again and he is again is in Contact reatailer we dont have a solution for this .
WARNING!!!! FOR ALL THIS OPERATION USE MINIMUM 1.38B.exe LAST IS 1.40B!!! AFTER all this
If you see:
Simlock send - FAILED!
SuperDongle send - FAILED!
or IMEI again is 1234...
SORRY WE DONT HAVE A SOLUTION FOR THIS AT THIS TIME