Bricked my handset - I think

[ajf]

Trying some new ROMs on my phone last night and yep, didn't set a backup first, and probably due to the ROMs I was playing with too.

It is a Galaxy S3 on Three.

Went to Samsung 'btu' ROM for Android 4.3 and then a bit later reverted it back to the Samsung 'three' ROM for Android 4.1.2.

Anyway, now coming up with No Service.

Quick search suggested IMEI issues, so checked what it thought it was, and indeed, the IMEI number is wrong. Seems to be a default one.

Any way of sorting this, without a suitable backup?
I found a way if the IMEI is 'null' but that didn't work.

New handset time?

 

[Myshra]

Did you backup your EFS at all as part of a previous ROM upgrade maybe? Did you take a backup of the mnt/extsdcard at all - a few upgrade ROMs automatically put the EFS here sometimes.

 

[ajf]

I will double check. I thought I had but couldn't find it on my PC last night, although was in a state of at the time!

Any other ways do you know failing that?

 

[tom_e]

http://forum.xda-developers.com/showthread.php?t=1264021 That might help.

 

[Grrrrr]

Probably not this but won't hurt to suggest...

Have you checked your APN settings? Either reset them or manually add them http://ask3.three.co.uk/srvs/cgi-bi...e=obj(1376),varset_username=Mobile:mobileUser

 

[Myshra]

His IMEI is damaged so he will not be allowed to connect to the network at all, he can't even get onto the network which would allow the device to goto the APN. Your IMEI is sent to the network when you start your phone up (with a bit of math to protect it and the SIM number too) and if it isn't legit you are barred from joining.

 

[ajf]

http://forum.xda-developers.com/showthread.php?t=1264021 That might help.

Thanks.
I will go through this tonight and see what happens!

Yep, not just APN settings. No mobile network access at all and also confirmed IMEI is wrong.