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.
Related
Hello to all. I'm trying to fix my friend's s4 i9505 because it shows that it's Baseband is Unknown and IMEI is null/null.
He told me the baseband and imei changed when he upgraded to 4.3 using wifi.
I have tried to flash stock rom but unfortunately the phone is in 4.3 so no downgrade.
I have tried flashing different modem.bin but still no avail.
He did not back up his EFS folder before upgrading to 4.3 but I still looked at the folder anyway.
I noticed that inside the EFS folder, there is no nv_data.bin and md5 file which is I think needed for the IMEI.
Is there a free way of recovering these files?
Is this a hardware failure?
I tried the different methods on recovering IMEI in the forums but all of them involves those 2 files so I can't continue.
I have another friend who has a i9500, can I copy and use his nv_data files? (He is willing to do it BTW to help my friend)
FYI: WIFI, Bluetooth and other functions are OK. It's just the call an text function which do not work.
Currently in JB 4.3 XXUEMJ5
No more warranty on the phone.
Any help would be greatly appreciated.
Thank you for taking the time to read our problem.
thetruth34 said:
Hello to all. I'm trying to fix my friend's s4 i9505 because it shows that it's Baseband is Unknown and IMEI is null/null.
He told me the baseband and imei changed when he upgraded to 4.3 using wifi.
I have tried to flash stock rom but unfortunately the phone is in 4.3 so no downgrade.
I have tried flashing different modem.bin but still no avail.
He did not back up his EFS folder before upgrading to 4.3 but I still looked at the folder anyway.
I noticed that inside the EFS folder, there is no nv_data.bin and md5 file which is I think needed for the IMEI.
Is there a free way of recovering these files?
Is this a hardware failure?
I tried the different methods on recovering IMEI in the forums but all of them involves those 2 files so I can't continue.
I have another friend who has a i9500, can I copy and use his nv_data files? (He is willing to do it BTW to help my friend)
FYI: WIFI, Bluetooth and other functions are OK. It's just the call an text function which do not work.
Currently in JB 4.3 XXUEMJ5
No more warranty on the phone.
Any help would be greatly appreciated.
Thank you for taking the time to read our problem.
Click to expand...
Click to collapse
This phone isn't that old! I have only today contacted Samsung as there is nothing in my EFS folder, they are sending out a jiffy bag for me to send the phone to them to repair under warranty!
Be careful talking about swapping efs partitions from phone to phone as the mods in here get funny about it, I would try contacting Samsung to return it if you can? When did you get it?
I would suggest you do the same. I can't fix mine either.
thetruth34 said:
Hello to all. I'm trying to fix my friend's s4 i9505 because it shows that it's Baseband is Unknown and IMEI is null/null.
He told me the baseband and imei changed when he upgraded to 4.3 using wifi.
I have tried to flash stock rom but unfortunately the phone is in 4.3 so no downgrade.
I have tried flashing different modem.bin but still no avail.
He did not back up his EFS folder before upgrading to 4.3 but I still looked at the folder anyway.
I noticed that inside the EFS folder, there is no nv_data.bin and md5 file which is I think needed for the IMEI.
Is there a free way of recovering these files?
Is this a hardware failure?
I tried the different methods on recovering IMEI in the forums but all of them involves those 2 files so I can't continue.
I have another friend who has a i9500, can I copy and use his nv_data files? (He is willing to do it BTW to help my friend)
FYI: WIFI, Bluetooth and other functions are OK. It's just the call an text function which do not work.
Currently in JB 4.3 XXUEMJ5
No more warranty on the phone.
Any help would be greatly appreciated.
Thank you for taking the time to read our problem.
Click to expand...
Click to collapse
try to flash latest modem twice (MKF or MKE) twice. first flash un-tick "auto-reboot".
benbird7 said:
This phone isn't that old! I have only today contacted Samsung as there is nothing in my EFS folder, they are sending out a jiffy bag for me to send the phone to them to repair under warranty!
Be careful talking about swapping efs partitions from phone to phone as the mods in here get funny about it, I would try contacting Samsung to return it if you can? When did you get it?
I would suggest you do the same. I can't fix mine either.
Click to expand...
Click to collapse
Should I try this too? I've just seen on Samsung website that mobile phones are covered for 24 months. I've only had this 8 months.
It's weird I have imei number when I type *#06# but nothing in efs folder!
Sent from my GT-I9505 using xda app-developers app
Thanks for all the replies. I tried to check it with my local technicians and all of them told me that my main board needs to be replaced.
I didn't know that a software mishap can result to a hardware failure to the extent of changing the main board.
I have tried flashing the recommended modems above but unfortunately still does not work.
I have noticed that when I type *#1234# in the Phone app, It shows me the AP and CSC and that is all written in the screen. No word modem and no modem version.
When I try to flash a firmware or a modem it says it flashed successfully but when I check the phone, still no service.
Again, wifi, bluetooth and other phone functions are working.
Technicians told me it is a "no service" unit and "cannot be fixed by software" because I have a "broken baseband/modem".
Is there really no hope for this unit?
Again any help or info is welcome.
Thank you for reading friends.
Bump
What do you want anyone here to say if you've been told by someone qualified that it needs a motherboard replacement ? In some (many ?) countries, this would be fixable by 're-writing' the IMEI to the device (either by a Samsung service centre or other repairer), but if that's not possible for whatever reason in your country & the way they fix it is a motherboard replacement, you don't really have any other option, do you ?
Edit - Attempting to move EFS files between devices normally ends up in both being blacklisted. Not recommended.
Hello,
I have exactly the same problem, with the i9505 phone version, do i have to change the motherboard or it can be fixed the "soft way"?
Hi all,
Sorry for the noob question but I have tried most of the repair suggestions in this forum all still could not get back the IMEI, Baseband, and serial number of the handset. Is there a way to program the original IMEI and serial number back into my Galaxy S4 I9505?
The handset had Hong Kong firmware 4.4.2 but with null IMEI, null baseband and wierd serial number. The handset is not IMEI blocked in Australia which I am trying to get it to work.
Would Chimera or Z3x software do this? Kies could not detect the handset for firmware update.
Thanks.
Wildwind101 said:
Hi all,
Sorry for the noob question but I have tried most of the repair suggestions in this forum all still could not get back the IMEI, Baseband, and serial number of the handset. Is there a way to program the original IMEI and serial number back into my Galaxy S4 I9505?
The handset had Hong Kong firmware 4.4.2 but with null IMEI, null baseband and wierd serial number. The handset is not IMEI blocked in Australia which I am trying to get it to work.
Would Chimera or Z3x software do this? Kies could not detect the handset for firmware update.
Thanks.
Click to expand...
Click to collapse
You may have a defective modem, try installing new modem software and see if that works. good luck
roscored1000 said:
You may have a defective modem, try installing new modem software and see if that works. good luck
Click to expand...
Click to collapse
Already tried that. Flashed with stock Hong Kong firmware, modem only, etc and did not fix it.
Is there a way to find out the which is the original firmware for the phone as the previous owner might have flashed it with the wrong firmware?
:crying:
Go here and enter your IMEI. The result should pop up with a great deal of information about your device. Post the result, not including the IMEI itself, and we can figure this out for you.
If your IMEI just disappeared without you doing anything, then chances are you got a hardware failure and the your EMMC chip needs to be replaced.
Lennyz1988 said:
If your IMEI just disappeared without you doing anything, then chances are you got a hardware failure and the your EMMC chip needs to be replaced.
Click to expand...
Click to collapse
Thank, I'm beginning to think this is the case.
Wildwind101 said:
Thank, I'm beginning to think this is the case.
Click to expand...
Click to collapse
Hi all,
I have re-flowed the MMC chip successfully. Is there a way to restore the IMEI and baseband without the nv-backup file?
Thanks :crying::crying:
Only if you used Wanam's EFS Backup tool to make a backup. It backs up not just the EFS partition, but the modem partitions and a few other hidden partitions as well. Otherwise you need to use methods we can't discuss on XDA to fix it.
Strephon Alkhalikoi said:
Only if you used Wanam's EFS Backup tool to make a backup. It backs up not just the EFS partition, but the modem partitions and a few other hidden partitions as well. Otherwise you need to use methods we can't discuss on XDA to fix it.
Click to expand...
Click to collapse
How do I find out the if the modem and IMEI info were still there and not completely erased or gone by the previous owner. I received it with null/null IMEI baseband fault.
You already replaced the modem as it was suggested by someone upthread. That would take care of the modem. There's no way to know whether the IMEI is present or not. It probably isn't present, in which case it needs to be rewritten.
Strephon Alkhalikoi said:
You already replaced the modem as it was suggested by someone upthread. That would take care of the modem. There's no way to know whether the IMEI is present or not. It probably isn't present, in which case it needs to be rewritten.
Click to expand...
Click to collapse
I think the IMEI info is lost so I would need to rewritten as I don't an NV_backup copy
The NV backup isn't present in the /efs folder on Android 4.4.2, at least from what I've witnessed on my own device. That's why I've switched to using Wanam's EFS Backup tool from Samsung Tool as it backs up the hidden modem and EFS partitions where the IMEI actually is stored.
If the IMEI is completely lost, you'll have to take the phone to Samsung for service. As mentioned upthread, there are other methods to fix this, but they can't be discussed here.
Strephon Alkhalikoi said:
The NV backup isn't present in the /efs folder on Android 4.4.2, at least from what I've witnessed on my own device. That's why I've switched to using Wanam's EFS Backup tool from Samsung Tool as it backs up the hidden modem and EFS partitions where the IMEI actually is stored.
If the IMEI is completely lost, you'll have to take the phone to Samsung for service. As mentioned upthread, there are other methods to fix this, but they can't be discussed here.
Click to expand...
Click to collapse
Thanks, in my case the modem and IMEI are already corrupted without an EFS backup so how can they be restored except for re-writting the IMEI ? I will look into Wanam's EFS Backup tool to see if I can salvage this mainboard.
okay so i tried to install xposed framework via recovery since it gave me an error during normal install, the device rebooted the got stuck in a bootloop, i flashed the latest rom for the shv-e300k from sammobile, everything worked great and the device booted into touchwiz, but there was 'No service' and the phone didnt connect to mobile network, when i dial *#06# i get IMEI 0000000000000.
i tried flashing different stock and custom roms, but nothing worked.. i tried a method to restore imei by copying EFS folder and using the .nvdata file, problem is there is not .nvdata in my EFS folder, I even tried installing cyanogenmod 13 and installing xposed framework on it together with the IMEI changer module, I typed my IMEI there but still no service..
PLEASE HELP!!!!!
The NV Data no longer lives in the EFS folder but is located in a hidden partition you cannot access. Wanam Partition Backup could have backed up and restored that partition for you if you had used it, but since you didn't, you'll have to take the phone to a service center and have the service center restore the IMEI.
Strephon Alkhalikoi said:
The NV Data no longer lives in the EFS folder but is located in a hidden partition you cannot access. Wanam Partition Backup could have backed up and restored that partition for you if you had used it, but since you didn't, you'll have to take the phone to a service center and have the service center restore the IMEI.
Click to expand...
Click to collapse
can you please tell me how to get to that partition using wanam partition backup ? and what is the partiton called ?
All the app does is back up and restore that partition. It doesn't let you access that partition, and besides, it's too late anyway. Your IMEI is gone, and using the app now would only back up what you currently have.
This device needs to be taken to the service center.
same problem here
Strephon Alkhalikoi said:
The NV Data no longer lives in the EFS folder but is located in a hidden partition you cannot access. Wanam Partition Backup could have backed up and restored that partition for you if you had used it, but since you didn't, you'll have to take the phone to a service center and have the service center restore the IMEI.
Click to expand...
Click to collapse
respected dev. i have the same problem. i flash a different firmware and now my phone baseband is unknown and imei is null. after a few days of checking its still not working. i have recovered its last working condition details as you can see in the photo attached
If restoring stock firmware does not restore the imei, you will probably have to have it fixed by jtag service or repaired using a programming box like an octopus box: http://octopusbox.com
Or have the phone serviced by Samsung, as discussing tools to rewrite IMEI I don't think is permitted on XDA.
I think discussions about restoring the original imei to the original motherboard/phone is okay but discussion about changing imei or serial number to something other than the original is not permitted.
Could you please check this.
audit13 said:
I think discussions about restoring the original imei to the original motherboard/phone is okay but discussion about changing imei or serial number to something other than the original is not permitted.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.vivek.imeichanger
check this but before this i want to ask that can i flash other firmware so that i can get baseband back. if i get baseband then i will use the above software to install the New Imei on the Phone. Tomorrow i will try every possible method to get back the phone to life and then if i fail, i will take it to the service center but if there is any possible way that you can help us so please assist and we will appreciate your assistance. thanks Regard Muhammad Ismail
That Xposed module won't work as what it does is spoof the IMEI for apps that have reading or sending the IMEI in their permissions. It does not change the existing IMEI and cannot be used to restore a lost IMEI. It requires the Xposed framework to function in the first place, which should give you a really big clue that this won't work.
If you want to waste the time and try it I'm not going to stop you, but the resolution to the problem requires tools only Samsung has. Android can't rewrite the IMEI as the IMEI is part of the phone's low-level firmware that Android cannot touch.
check your phone box if you have lost the imei
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?
Hello.
I'll first describe the secuence of events and then tell which solutions I've tried. Bear with me. I'll be brief.
I've bought a second hand Samsung Galaxy S4 (i9500) sold through a local carrier. By law the carrier can only give the unlock code to the original buyer of the phone, and the person from who I bought it from wasn't him/her.
I tried to unlock it by my means (basically this, trying lots of variants until "186" code dead-end), which resulted in rooting, flashing diferent modems and trying a CM based custom ROM (GearCM). Before going on any of this, I made an EFS, cdma-radio, radio, m9kefs1/2/3 backup.
As I couldn't do it, I took the phone to a repair shop, where they unlocked it with a box. Then they told me that the SIM tray was broken, and after trying a different one, they concluded that it was a software problem (I suggested it) and flashed a stock ROM from the carrier, which still didn't recognized any SIM.
This is when I took back the phone.
I've restored the EFS and flashed the correct modem (In fact I've found two which work: I9500UBUHPB2-CP and I9500UBUHOI1), but even if the SIM card is recognized, I can't connect to the network, I think, because the IMEI which displays the phone is different from the factory IMEI. In fact, is the infamous generic IMEI 0049... with IMEISV 01.
I've since tried this methods:
- Changing permissions of the EFS folder
- Flashing the stock ROM after completly wiping out the phone
- Manually deleting the EFS contents and restoring
And combinations of the above with RegionLockAway and with both working modem drivers.
I still have to try rooting an older stock ROM, maybe 4.4.2, but I wanted to ask more wise people if there is a logical, correct order to any of the above steps, or if you think I'm missing something here.
The only other answer that comes to me is that it's something done by the repair shop with the box, but still I've no conclusive proofs of that. I wanted to exhaust options.
Thanks in advance. Any answer will do good.
Restoring the EFS does nothing, as the IMEI is no longer stored in it. Thus none of the things you tried will help. You'll have to take the device back to the place who fixed it for you.
Strephon Alkhalikoi said:
Restoring the EFS does nothing, as the IMEI is no longer stored in it. Thus none of the things you tried will help. You'll have to take the device back to the place who fixed it for you.
Click to expand...
Click to collapse
I would have thought that it was stored on it. Do you infer that from my failed attemps? Where should it be "stored"?
I don't "infer" anything. It's a fact. IMEI was stored in a file named nv_data.bin in EFS, but for some time now it's no longer been located there. It's been moved to three hidden partitions that a nandroid backup does not touch. You'd have to use Wanam Partition Backup and Restore to see the partitions in order to be able to back them up as well as restore them. Thus, your IMEI is gone, and the repair shop is going to have to fix it.
Strephon Alkhalikoi said:
I don't "infer" anything. It's a fact. IMEI was stored in a file named nv_data.bin in EFS, but for some time now it's no longer been located there. It's been moved to three hidden partitions that a nandroid backup does not touch, m9kefs1, m9kefs2, and m9kefs3. You'd have to use Wanam Partition Backup and Restore to see the partitions in order to be able to back them up as well as restore them. Thus, your IMEI is gone, and the repair shop is going to have to fix it.
Click to expand...
Click to collapse
But I have a backup of those partitions, made with Wanam Partition Backup. I've restored them in this order: cdma-radio, EFS, radio, m9kefs1, m9kefs2, m9kefs3. Somehow, its not working.
That's why I think maybe it has to do with the order of the steps I'm taking, maybe even before restoring the partitions.
I edited my post while you were making yours.
My backup consists of much more than those three partitions. I have in addition to those efs.img, fsg.img, modemst1.img, and modemst2.img. The IMEI is in one of those partitions, NOT EFS.
Well then... I hope they can repair the IMEI then. It would be a damn shame if not... Thanks for your time.