Hi!
I just like to share something I have discovered during the time I was already going nutts when I discovered that my phones IMEI was replaced by another set of numbers. It all started when I flashed a Firmware XXUBUBMG1 (Movistar) that I downloaded. It was for GT-I9500, the same model as my phone. Everything went well, then I noticed this problem when I decided to call the Customer Service Number of my SIM, the device is telling me that my phone is Not registered on network. Then I decided to check the IMEI and to my horror, it was replaced by this set of numbers, 004003150000, which is not my phones IMEI. Then I decided to look for answers over the internet. But before going further and going thru all the trouble of starting from scratch, an idea came to my mind. I decided to try it out before doing anything else. And whoalah! My phone's IMEA is restored! I can make calls again and connect to the net via Mobile Data again.
Anyway here is the solution that I came up with. If anyone else had tried this before then I give all the credits to him for fixing his phone. :laugh:
1. Download a firmware that is intended for your phone's model number and the region where you bought your S4. Mine was bought in Saudi Arabia, so the firmware I got was for KSA. It also applies for the GT-I9505.
2. Enter Download Mode and flash this firmware via Odin on your PC. I didn't do any Wipe or Factory Reset during this time.
3. Root and install any custom Kernel or CWM Recovery on your phone if you are on this setup. Otherwise leave it as it is.
Long story short, I have an AT&T S4 (SGH-I337). I have checked the IMEI online and found that it is not blacklisted.
Signed up for a MetroPCS account (as I have heard they partnered with T-Mobile)
Purchased unlock code from ebay, got it this morning, entered it and it worked
Tried flashing AWS band using QPST (made backup first), rebooted phone, got the message:
"Attention - Phone not allowed MM#6"
Restored QCN from before, rebooted, same message
Why can't my unlocked phone join the network?!
mikeDCMDVA said:
Long story short, I have an AT&T S4 (SGH-I337). I have checked the IMEI online and found that it is not blacklisted.
Signed up for a MetroPCS account (as I have heard they partnered with T-Mobile)
Purchased unlock code from ebay, got it this morning, entered it and it worked
Tried flashing AWS band using QPST (made backup first), rebooted phone, got the message:
"Attention - Phone not allowed MM#6"
Restored QCN from before, rebooted, same message
Why can't my unlocked phone join the network?!
Click to expand...
Click to collapse
Are you on the MF3 firmware on your S4? If you are then you have to read on alternative methods to unlocking on MF3. Also, from my understanding, any of the methods to unlock involving the native phone dialer will only work on the stock ROM for the device.
These may be one of your problems here.
Hi folks
This problem I have with this Australian L3 E400f is after I dial up 2945#*400# the unlock menu pops up as normal
selecting "network lock"
results in message "This phone is permanently locked and cannot be unlocked"
at no stage do I get a chance to input any unlock codes.
I gather there have been more than 10 failed attempts to input a NCK code, thou I am sure this is not the case it was straight out the box new.
the phone works just fine and dandy with all firmwares I have flashed as long as I have the telstra sim card in place.
I have used a Brazilian (V10D_00) stock firmware (using KDZ) hoping that the failed count lives in the firmware, it does not.
I have used CWM and flashed cynogen , this did nothing only the stock firmware allows 2945#*400#
gone back to my aussie V10D_00 telstra firmware and factory reset, then hardware reset..
I dont beleive this is a ROM issue. I am only guessing this is a EFS problem, anybody have any idea's if ADB or LGNSPT can get me out of this jam..
LGNSPT seems like a nightmare to get up and running and I have never used it before. I have once before on a samsung phone deleted the EFS folder (after backing up) and the phone generated a new EFS folder, I had my way with it then retsored the original EFS folder.
is their other methods of inputing the NCK code with ADB or else ?
thanks in advance this one has got me stumped...
all the best
ok here is my problem
i have Samsung s5 from rogers
i when to Ghana so i wanted to use my phone there but it was lock so
took it to some guy to unlock it and it worked ok
when i came back and inserted my old sim
i get not registered to network and my imei is different from the box
i have tried flashing it with stock rom but still getting the same message
any body had this problem and how it they get it working
thanks
Unless you have made a backup of your original cert files nothing can be done, the shop in Ghana most likely used an IMEI from another handset and wrote it yours during the process this also unlocks your handset afaik .
up
I was having the dreaded "Sim card not detected" message and decided to try replacing the mainboard of my Koodo/Telus S4 SGH-i337m with another from the exact same model but different company.
I rooted the phone (etc) and used the tool at http://forum.xda-developers.com/gal...ool-antaresone-s-imei-backup-restore-t2975136 to do a complete backup of the EFS and stuff
I was able to swap out the boards with no trouble and confirmed the newly repaired phone had an IMEI before doing a restore using the above tool as well, but after doing so, the IMEI says Unknown.
I put the phone into DM mode and enabled cp logging in recovery so the phone could be recognized by Windows (otherwise it was saying USB Device Not Recognized)
I tried Octoplus and it can get the software and firmware info from the phone, but does nothing else. NV Items reader writer gives an "Unknown Command" error for even just reading the full phone.
Not sure what I need to do to fix this. Thinking about contacting an unlocking guy here in Canada who says he can repair the IMEI remotely, but I don't want to do that if it's something simple I'm overlooking. Unfortunately most of the documents talking about IMEI repair refer to options that don't exist in my service menu (for example #6 Common and turning off FTM mode). Would appreciate any help.
The backup method is for the i9505 and I understand that, hardware-wise, the i337m has the same hardware but the major difference is support for LTE frequencies in Canada.
You tried to restore the imei from the original motherboard to the replacement motherboard? Do you have a back up of the replacement motherboard's imei information?
With the s4, I don't think all of the imei information is in the efs folder. Nvdata may be written in a hidden partition.
Yup I took a backup of both before doing anything
The tool I linked to says it supports the i337m and it detected it and did not complain at all.
audit13 said:
The backup method is for the i9505 and I understand that, hardware-wise, the i337m has the same hardware but the major difference is support for LTE frequencies in Canada.
You tried to restore the imei from the original motherboard to the replacement motherboard? Do you have a back up of the replacement motherboard's imei information?
With the s4, I don't think all of the imei information is in the efs folder. Nvdata may be written in a hidden partition.
Click to expand...
Click to collapse
The tool backed up several partitions it seems, not just the efs.
Just an FYI. Both motherboards are for Canadian models. My original was with Koodo and the new one is from Bell. Both are identical. It shouldn't have a problem with that.
You tried to restore your old imei to the replacement board? Any particular reason this was necessary? Both motherboards were running the same ROM although I'm not sure this makes a difference.
I wanted to keep it as close to the original as possible (guess I'm a bit OCD like that lol) and I'm pretty sure the seller I bought it from on eBay set the imei on it to a fake number, as I checked it online and nobody had any information on it (whereas my original Imei was recognized as coming from an s4).
Did you try flashing a stock rom on the replacement motherboard? If that doesn't restore the imei and you don't have the replacement's original imei, you may be out of luck.
You confirmed that the replacement is an i337m in download mode?
I am trying a stock Bell firmware using odin now and will then restore the imei backup I took of the new motherboard to see what happens.
Trying to restore the imei backup from the Koodo phone may make it worse.
After flashing a stock rom, check to see if wifi and Bluetooth works before trying to restore the imei.
audit13 said:
Trying to restore the imei backup from the Koodo phone may make it worse.
After flashing a stock rom, check to see if wifi and Bluetooth works before trying to restore the imei.
Click to expand...
Click to collapse
Still working on it, but previous attempts have had absolutely no other issues. Wifi, camera, et al have worked fine.
Okay so I flashed back the Bell stock firmware and my backup of the new motherboard, and the IMEI is back, but I am almost 100% sure it's a fake one. None of the sim unlock methods work and online tools cannot identify it. It's not the old 0049 or any other known fake/invalid one, which is quite weird.
Which method are you using to sim unlock?
I just purchased an unlock code for my original imei and am stuck at this point unless I can figure out why it doesn't work on the new motherboard.
Unlock codes are tied to the imei. Since you can't get your imei into the replacement board, you can't use the unlock code.
Also, some carriers can detect an altered imei and will not activate the phone on their network. Not sure if this is always the case.
We dont support nor allow discussion of imei changing, thread closed.