I recently bought a Note 3 SM-N9008W of Claro PR which is loaded with the TELCEL 4.4 KitKat firmware. The guy who sold me the cel told me that as a result of flashing that firmware, it didnt have baseband and imei. So after reading a lot, I decided to give EFS Pro a shot. EFS Pro has a option to restore NVRAM, so I did that and after rebooting, I got the TELCEL baseband and a imei
Problem is that the imei on the firmware is not the same as the one on the back label. I used the Phone Info app, and everything looks ok for Telcel except that the Mobile Provider ID is Claro and there is no RIL serial number.
Any help? I dont have a EFS backup and Knox is 0x1.
There is a guide here on how to restore serial and imei but read everything before performing the task as I read there is the potential to brick your phone if not followed correctly.
I managed to install Claro PR 4.3 , still shows wrong IMEI, not the same as the back label. I insert any sim , tmobile ,claro and it doesnt say invalid sim. I only have signal bars. Also, and Im afraid of this, if I dial #*0011 , it shows IMEI CERT: FAIL.
Any help?
After a second reflash with 4.3, the software imei now matches the back label imei!
but I already tried 2 unlock code sellers, and none have provided a working code.
Any help?
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.
Hi Guys,
This is my first post here and also I am fairly new to android, so I apologize in advance if I violate a forum rule or ask an obvious silly question. Anyway,I Recently, I received a Samsung A5 2016 Dual Sim from my friend which did not boot up. Apparently he had installed an app which caused this situation. Then he had tried to install multiple firmwares with Odin on it without success. Anyway, I received the phone and first strange thing that I found was that product name in download mode was SM-A5108 which was different from A510FD which was on the phones box. This probably was the main reason behind not being able to flash any A510FD firmware on phone. So I flashed a A5108 firmware on it booted up to android. But there was 4 issues there:
1- No baseband version was available.
2- No IMEI information for either of sim card slots and of course not detecting any of sim cards.
3- Very sensible lag and delay on loading apps and working with menus.
4- Also A5108 is apparently available for china region so menu was Chinese and other region specific apps was on it.
I found out the original firmware on it was A510FD so searched a little bit and found out it is possible to restore a backup from A510FD. I downloaded a backup file from internet and restored it using TWRP (Data, System, Boot). After restore, phone booted up with A510FD but once again with null IMEI and also lagging. Right now baseband version is available and device model on about section is A510FD. I know all radio related information is on EFS but I have no EFS backup right now and restoring EFS is not an option. Is there any way to fix IMEI issue now?
I can provide exact build number and any other information about phone and firmwares that I used in case it is required for better troubleshooting.
check you phone model by imei or serial from the box or from back of the phone, if someone messed up that phone is hard to be sure what model is
remosam said:
check you phone model by imei or serial from the box or from back of the phone, if someone messed up that phone is hard to be sure what model is
Click to expand...
Click to collapse
I forgot to mention there is no IMEI on phone's box or phone itself. But phone's model (A510FD)is printed on box. Also battery is non-removable so not able to check inside of phone for IMEI.
If there is no other option you could remove the back glass panel to see the IMEI number there is a sticker underneath it i replaced the screen of mine and i saw this sticker. You need to be carefull taking off the panel tho cuz you coul rip off the sticker if you're not careful.
Thank you for responding. Okay, Let's suppose I found out IMEI by opening phone's back panel. What is the next step? How could I use these information to recover IMEI to phone? Is there any chance that IMEI information is at EFS partition but due to wrong firmware upgrade it is not working?
After flashing a stock ROM using Odin, the phone no longer recognises the SIM. The SIM works in another phone. The phone I flashed appears to have forgotten its IMEI numbers.
I haven't forgotten the numbers - I still have the sticker that came on the back of the phone with the IMEIs and S/N printed on it.
Is there a way to input my IMEI numbers back into the phone?
Thank you.
Can someone give me an backup of the efs partiton with twrp of a520f please?
I have successfully rooted my phone using twrp and magisk, but managed to lose my phone's identity, I screwed up because I did not make a backup first. I lost imei and baseband version, now the phone can't have a sim, no CDS info, only Wi-Fi is working. Model is XT1761, single-sim, already searched in the whole forum, couldn't manage to find nothing. Tried various nvram files without success. Please help, I am a beginner, and would appreciate if someone could help me understand better if I can repair this phone. Not my main phone, but still, I would be happy to repair it.