Firmware recover update via KIES & IMEI problem

[Vitor Costa2]

Question:
A Firmware recover update via KIES cand modify IMEI??

What happened:
I had a corrupted OS showing messages like failed to mount data ... efs, invalid argument and stuff.
So I used KIES to recover it and now my IMEI has changed to a generic 004999010640000 / 04
How can I solve this situation?

 

[GSDer]

The /efs partition contains your IMEI. If it was corrupted then it's possible that there was nothing Kies could do but write a generic IMEI (although it prompts you for the model number and IMEI during a firmware reload - you'd think it could figure it out).

Now that the corruption is fixed, try reloading the firmware again using the second item in the Tools menu (Firmware upgrade and initialisation).

If that doesn't work you'll have to see if you can get an answer over on XDA.

Sent from my rooted, debloated, deodexed Sinclair ZX-80 running CM -0.001 using Tapatalk Pro

 

[Vitor Costa2]

The /efs partition contains your IMEI. If it was corrupted then it's possible that there was nothing Kies could do but write a generic IMEI (although it prompts you for the model number and IMEI during a firmware reload - you'd think it could figure it out).

Now that the corruption is fixed, try reloading the firmware again using the second item in the Tools menu (Firmware upgrade and initialisation).

If that doesn't work you'll have to see if you can get an answer over on XDA.

Sent from my rooted, debloated, deodexed Sinclair ZX-80 running CM -0.001 using Tapatalk Pro

I did that but no sucess.
It can be fixed somehow?

 

[GSDer]

It can be fixed somehow?

Not with anything I know - I only know enough to be dangerous. As I mentioned earlier, the folks over on XDA may be able to help you. Or you could try http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-imei-efs-repair/

Sent from my rooted, debloated, deodexed Sinclair ZX-80 running CM -0.001 using Tapatalk Pro