Hi,
My problem is Kies won't update my phone - GT-N7100 (a well known message that the device is not supported, with triple (xxx) in place of the CSC code at the end of this message). Also when I use Check Fus on my phone, in the Product Code field it says "Not active" like below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And this is what Kies says:
I think the lack of Product Code might be the reason why Kies doesn't update. I don't care about Kies so much but I just want to know what's wrong and try to resolve it.
What I did:
1. I bought the phone unbranded, unlocked, and it came with XEF CSC (FW: XXALJ1).
2. I changed the CSC to XEO with CSC Select (from Google Play) --> Phone wiped.
3. After this I upgraded to the newest XXALJ3 FW.
And then when trying to update with Kies it displays the message as above and Check Fus reports PC Not Active. As far as I know it should display full product code in the PC field so in this case: GT-N7100TADXEF (I don't know if the PC also changes when changing the CSC, in case it changes it should of course display GT-N7100TADXEO). I wiped the phone a few times, went back to the original FW (XXALJ1), changed the CSC back to XEF but no luck.
I've gone through many sites/forums but didn't find the answer. Also I didn't mess with EFS folder, I have my proper IMEI. Is there a possibility that CSC Select app did something wrong to the phone? I don't think so because if I'm right it only triggers Samsung's built-in Preconfig menu, so it should't do any harm. I regret not checking if Kies works properly before changing the CSC.
So the big question is: where the phone reads the PC from (where it's stored?) and how to make the Product Code appear as it should?
EDIT:
I figured out the problem lies within the nv_data.bin file in EFS folder. Inside of this file there's a string "Not active". The same string is present in the backup copy (.nv_data.bak). I tried to edit the file with hex editor and put the right product code in place of "Not Active" string but I can't generate proper md5 hash for it (it seems it's not a regular md5 hash that Samsung uses). And when you delete nv_data.bin.md5 it won't recreate one automatically as it was the case in earlier phones. It will just use the backup file. Even when I deleted .nv_data.bak, .nv_data.bak.md5 and nv_data.bin and nv_data.bin.md5 and uploaded only the modified nv_data.bin with proper product code - it somehow restored the files from somewhere else (I heard there is a hidden partition or something with another backup files) and again I have PC: Not active.
I think the solution would be to somehow create md5 hash of that modified nv_data.bin file that's accepted by the phone but I don't know how.
Great Work
Hi brother im also facing the same problem can you please help me.
tom369 said:
Hi,
My problem is Kies won't update my phone - GT-N7100 (a well known message that the device is not supported, with triple (xxx) in place of the CSC code at the end of this message). Also when I use Check Fus on my phone, in the Product Code field it says "Not active" like below:
And this is what Kies says:
I think the lack of Product Code might be the reason why Kies doesn't update. I don't care about Kies so much but I just want to know what's wrong and try to resolve it.
What I did:
1. I bought the phone unbranded, unlocked, and it came with XEF CSC (FW: XXALJ1).
2. I changed the CSC to XEO with CSC Select (from Google Play) --> Phone wiped.
3. After this I upgraded to the newest XXALJ3 FW.
And then when trying to update with Kies it displays the message as above and Check Fus reports PC Not Active. As far as I know it should display full product code in the PC field so in this case: GT-N7100TADXEF (I don't know if the PC also changes when changing the CSC, in case it changes it should of course display GT-N7100TADXEO). I wiped the phone a few times, went back to the original FW (XXALJ1), changed the CSC back to XEF but no luck.
I've gone through many sites/forums but didn't find the answer. Also I didn't mess with EFS folder, I have my proper IMEI. Is there a possibility that CSC Select app did something wrong to the phone? I don't think so because if I'm right it only triggers Samsung's built-in Preconfig menu, so it should't do any harm. I regret not checking if Kies works properly before changing the CSC.
So the big question is: where the phone reads the PC from (where it's stored?) and how to make the Product Code appear as it should?
EDIT:
I figured out the problem lies within the nv_data.bin file in EFS folder. Inside of this file there's a string "Not active". The same string is present in the backup copy (.nv_data.bak). I tried to edit the file with hex editor and put the right product code in place of "Not Active" string but I can't generate proper md5 hash for it (it seems it's not a regular md5 hash that Samsung uses). And when you delete nv_data.bin.md5 it won't recreate one automatically as it was the case in earlier phones. It will just use the backup file. Even when I deleted .nv_data.bak, .nv_data.bak.md5 and nv_data.bin and nv_data.bin.md5 and uploaded only the modified nv_data.bin with proper product code - it somehow restored the files from somewhere else (I heard there is a hidden partition or something with another backup files) and again I have PC: Not active.
I think the solution would be to somehow create md5 hash of that modified nv_data.bin file that's accepted by the phone but I don't know how.
Click to expand...
Click to collapse
bevybeast said:
Hi brother im also facing the same problem can you please help me.
Click to expand...
Click to collapse
I haven't find a solution yet so I can't help you but I'll post here in case I fix this. I'm rather counting on others' advice because I've already spent many hours trying to find the solution without success.
product code
tom369 said:
I haven't find a solution yet so I can't help you but I'll post here in case I fix this. I'm rather counting on others' advice because I've already spent many hours trying to find the solution without success.
Click to expand...
Click to collapse
You can try FREE SRS PRODUCT CODE CHANGER SAMSUNG FOR KİES UPDATE program.
ersan19 said:
You can try FREE SRS PRODUCT CODE CHANGER SAMSUNG FOR KİES UPDATE program.
Click to expand...
Click to collapse
you did try that program?
ersan19 said:
You can try FREE SRS PRODUCT CODE CHANGER SAMSUNG FOR KİES UPDATE program.
Click to expand...
Click to collapse
Thanks for the tip, unfortunately I can't check it because being helpless and with no clues how to resolve the issue I've sent the phone to the service center before I saw this message. But maybe bevybeast who's also facing this problem as written above can check it and report back if it works.
thanx for sharing this, OP
I had this exact same problem. I messed up with GalaxSim Unlock from Play to see if I'd be able to unlock my phone so my EFS files were changed. I decided I don't need it yet so I restored a backup (with the tool described in this thread: http://forum.xda-developers.com/showthread.php?t=1922473 ) and I was pretty sure I got it back to the original.
after I read your description I decided to take another look and found that my NV_DATA.BIN contained a "Not Active" code as it appeared to have been written a very long time ago. I tried again and again and wasn't able to restore the backup, after restart nv.log was showing:
Code:
Tue Dec 18 14:08:49 2012: cracking detected
Tue Dec 18 14:08:49 2012: NV backup has been rebuilt
Tue Dec 18 14:08:49 2012: NV restored
well, luckily I had a backup made with GalaxSim Unlock itself and when I tried restore from the application it worked.
I don't get what "Not Active" is doing there in the first place but it's quite dangerous in case anything goes wrong with the current nv_data.bin, the system will restore to some data that is fishy to say the least. So far I only noticed the "Product Code" was wrong inside but who knows what else is not that obvious
ersan19 said:
you did try that program?
Click to expand...
Click to collapse
Hi ersan19,
I did try it but unfortunately it seems to do nothing - I get the message that product code changed successfully but nothing more really happens. Even after restarting the phone. It won't even change the CSC, not to mention the complete product code. I even disconnected the phone and tried to change the code and it said product code changed OK
@primusmagestri: I'm happy this topic helped you.
i am having the same prob ... so did anyone have a solution to this prob .. or should i send my phone to service center ..... ?
but this happened to me after restoring animage of the efs .. which was taken when the phone was normal
can any one give me the product code of note 2 (n7100) uae ..
Hi,
If you really don't want to send the phone to the service centre the only way I see is to change the nv_data.bin file content (in EFS) folder and put the proper product code string for your phone. The problem is - you also have to calculate md5 hash for it, which is NOT a regular md5 and I don't personally know how to calculate it. In older firmwares you could just delete the .md5 file and the system would calculate the md5 but now it's not this way and you have to put the correct md5 checksum file. If you don't, the nv_data.bin will be recreated from nv_data.bak file. And in case you deleted both these files, the system will recreate them from nv_core.bak file.
There's still chance you have proper product code in either nv_data.bak or nv_core.bak file. If you find the right product code in nv_data.bak just delete nv_data.bin and you should be ok. If only nv_core.bak has good product code, you delete both nv_data.bin and nv_data.bak. You can check the contents of the files with hex editor. Remember to make EFS folder backup before doing anything, and remember that messing with those files can lead to serious trouble if you do something wrong. And of course you need root access for it.
Or maybe there's someone here who would like to share with us the md5 calculation method Samsung is using?
tom369 said:
Or maybe there's someone here who would like to share with us the md5 calculation method Samsung is using?
Click to expand...
Click to collapse
Big thanx for the info ..and waiting for some to tell us how to fix it
devil_slayer said:
can any one give me the product code of note 2 (n7100) uae ..
Click to expand...
Click to collapse
gt-n7100rwdxsg
I am also having the same issue. This happened to my phone after I used CSC Changer app from Play store(In root mode)..
Now I have to update my phone using ODIN only.. Hope somebody will come up with a solution.
AlanDS said:
I am also having the same issue. This happened to my phone after I used CSC Changer app from Play store(In root mode)..
Now I have to update my phone using ODIN only.. Hope somebody will come up with a solution.
Click to expand...
Click to collapse
You have to repair product code with any service box,ex- z3x ,and after that use CSC Galaxy S/s2/s3 from Google Play in ROOT MODE and choose your product code.
All data will be erased. Now flash your phone with odin again,star phone and wipe data again in recovery.
Bruno_rv said:
You have to repair product code with any service box,ex- z3x ,and after that use CSC Galaxy S/s2/s3 from Google Play in ROOT MODE and choose your product code.
All data will be erased. Now flash your phone with odin again,star phone and wipe data again in recovery.
Click to expand...
Click to collapse
can you please explain in detail?
I'm having the same problem with my note 3. Anyone found the solution yet?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Same problem. Any fix for this ?
Same issue.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Related
So I have an SGS and I screwed up when JPC came out and so I have the default IMEI number and product code of XXX. So out of curiosity, I'm wondering if I took the efs folder of another sgs and putting it in this 'paper weight' phone.
I'm obviously going to have to buy another SGS, but this is a thought that I had. I"m going to take a stab and think that this should work right since it's just like backing up/restoring the efs folder, just putting it on another phone.
I'm just looking for feedback on this idea, it's just going to be a costly solution for me. I'm primarily doing this until there's a solution to restoring the IMEI number for the SGS and then selling the other SGS.
I'm not a developer... but I would assume you would need to edit the new nv_data.bin files using a hex editor before you put them on the bricked device.
If you do a search on downloads.com you ought to find a freeware one.
Use that to search and replace the xxx imei number with that on the barcode on the side of the box.
Please be advised that this is pure speculation as my imei didn't default... but I found I could change my product code in a similar way.
Won't work. the /efs folder stores your IMEI number stuff, and the file's digitally signed. You can't just dump another file from another phone into it to fix the problem.
Well, my device not bricked as i can still use it, its just that i have a default imei and product code. Im aware that its digitally signed, but if im taking a file thats digitally signed by the same product then i would assume thats okay.
A digitally signed file from an one i9000m should be signed the same way as another i9000m would digitally sign a file no?
Sent from my GT-I9000M using XDA App
BakaSenpai said:
Well, my device not bricked as i can still use it, its just that i have a default imei and product code. Im aware that its digitally signed, but if im taking a file thats digitally signed by the same product then i would assume thats okay.
A digitally signed file from an one i9000m should be signed the same way as another i9000m would digitally sign a file no?
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Yes most likely but then it will have the IMEI of THE OTHER device and that's not what you want. If you change the file then the md5 checksum becomes invalid. However, I thought I read somewhere that the phone would re-create teh checksum file if it's missing. Whether this allows you to change the file I do not know......
ewok666 said:
Yes most likely but then it will have the IMEI of THE OTHER device and that's not what you want. If you change the file then the md5 checksum becomes invalid. However, I thought I read somewhere that the phone would re-create teh checksum file if it's missing. Whether this allows you to change the file I do not know......
Click to expand...
Click to collapse
It won't work, the files are device specific.
EDIT: Aha, found the posts i was looking for.
http://forum.xda-developers.com/showpost.php?p=7509851&postcount=24
http://forum.xda-developers.com/showthread.php?t=743183&highlight=IMEI
It works only for product code...
i restore my DBT product code in this way:
-first copy the nv_data.bin and md5 files with their bak files (4 files)
-reboot
then my sims didnt work right ... (wrong pin error)
-with root explorer i deleted the nv_data.bin and nv_data.bin.md5 files. DONT DELETE the .bak files....
reboot.
my product code is now ok and my sim works.
imei...wrong.
Rawat said:
It won't work, the files are device specific.
EDIT: Aha, found the posts i was looking for.
http://forum.xda-developers.com/showpost.php?p=7509851&postcount=24
http://forum.xda-developers.com/showthread.php?t=743183&highlight=IMEI
Click to expand...
Click to collapse
Bah! Had I only found this earlier, then I guess I wouldn't have posted this questions then. *sigh* I guess i just have to wait for some kind of solution. Thanks Rawat
check if this guy can restore your IMEI
http://forum.samdroid.net/f28/complete-imei-restore-how-1817/
(should be similar methodology)
I tried this and it dosen't work. The device somehow validates the imei..
Sent from my GT-I9000 using XDA App
I have a rooted Galaxy Nexus GSM (Maguro) running ClockworkMod and the stable version of CM9. I've been trying to find out how exactly the IMEI is stored --- whether it's baked into the radio component or whether it's controllable from firmware --- and how /factory/nv_data.bin relates to it.
I was able to "break" my IMEI, i.e., set it to the infamous 004999010640000, via the following procedure (derived from http://forum.xda-developers.com/showthread.php?t=1264021 ):
0. Get an adb root shell
1. Back up the contents of `/factory`, e.g., with `adb pull`
2. Remount the `/factory` filesystem read-only with `mount -oremount,rw /dev/block/mtdblock0 /factory`
3. Delete `/factory/nv_data.bin` and `/factory/nv_data.bin.md5`
4. Delete `/data/radio/nv_data.bin` and `/data/radio/nv_data.bin.md5`
5. Reboot
After this, the IMEI was reported as 004999010640000. Then I was able to restore my IMEI to its original value as follows:
0. Restore `/factory/nv_data.bin` (owned by root)
1. Restore `/data/radio/nv_data.bin` (owned by radio)
So it seems clear that the IMEI reported by the device depends on the contents of the firmware. But it's possible that the radio unit is hard-wired to only be in two possible states, 004999 and the true IMEI.
`/data/radio/nv.log` has log lines from code attempting to read `nv_data.bin`, in particular:
Fri Aug 24 01:10:53 2012: MD5 is turned on.
I searched all the repositories in the Google Android codebase for the string "MD5 is turned on" and couldn't find the code that generates this log line. Is it possible that it's generated by a proprietary binary blob?
So, the open questions:
1. Where is the code that knows how to interpret nv_data.bin?
2. Does nv_data.bin actually contain the IMEI?
Thanks for your time!
Have a look at this thread.
efrant said:
Have a look at this thread.
Click to expand...
Click to collapse
That's more or less what I did; I was able to break and unbreak my IMEI using the procedures outlined there. What I'm trying to find out is whether the IMEI is actually stored in that file (the first "theorem" in that post, although it is not proven), what code is able to read the IMEI, and whether the IMEI can be modified.
There's some more information here: http://forum.xda-developers.com/showthread.php?t=1626593&page=2
which points to the Samsung rild as the code which knows how to interpret nv_data.bin, and suggests that the md5 verification is performed with a secret seed. But I can't find the source code for the Samsung-specific rild to confirm this. Perhaps it is a binary blob somewhere on my phone's filesystem?
The two strings I have to recognize the code are the log message `MD5 is turned on.` and the function `__refresh_md5_file`.
Update: running `pmap` on `/system/bin/rild` showed that it links against `/system/vendor/lib/libsec-ril.so`. I think this is the relevant blob --- it looks like both of those strings are in there.
slingamn said:
Update: running `pmap` on `/system/bin/rild` showed that it links against `/system/vendor/lib/libsec-ril.so`. I think this is the relevant blob --- it looks like both of those strings are in there.
Click to expand...
Click to collapse
/system/vendor/lib/libsec-ril.so is just the "radio interface layer". It has nothing to do with the IMEI.
efrant said:
/system/vendor/lib/libsec-ril.so is just the "radio interface layer". It has nothing to do with the IMEI.
Click to expand...
Click to collapse
I think it does have to do with the IMEI, based on the strings that are in it. Here's the output of `nm -D` on it: gist.github.com/70f5222ce6d578a9655e
In particular, here are some suggestive strings: requestGetIMEI, requesetOemImei, requestOemEventStartIMEI, TxIMEI_EventStartImei, RxIMEI_UpdateItem.
I think it's likely that some of the functions here can be used to push a new IMEI value into the radio unit. But given that it also contains the log messages found in `nv_data.log`, it seems like it definitely has the role of reading and verifying `nv_data.bin`.
Does anyone have any guesses about the naming scheme of these functions, in particular the "Tx" and "Rx" strings?
slingamn said:
I think it does have to do with the IMEI, based on the strings that are in it. Here's the output of `nm -D` on it: gist.github.com/70f5222ce6d578a9655e
In particular, here are some suggestive strings: requestGetIMEI, requesetOemImei, requestOemEventStartIMEI, TxIMEI_EventStartImei, RxIMEI_UpdateItem.
I think it's likely that some of the functions here can be used to push a new IMEI value into the radio unit. But given that it also contains the log messages found in `nv_data.log`, it seems like it definitely has the role of reading and verifying `nv_data.bin`.
Does anyone have any guesses about the naming scheme of these functions, in particular the "Tx" and "Rx" strings?
Click to expand...
Click to collapse
so? no updates on this?
i'm stuck with the 0000049xxxxx generic IMEI and no back up... i'm trying everything i found on the internet with my poor knowledge and i'm stuck... no idea what to do
blasael said:
so? no updates on this?
i'm stuck with the 0000049xxxxx generic IMEI and no back up... i'm trying everything i found on the internet with my poor knowledge and i'm stuck... no idea what to do
Click to expand...
Click to collapse
I gave up on this project. If you're interested in working on it further, I would suggest contacting the Replicant developers (#replicant on freenode) for advice --- they're the people I would expect to know the most about hardware issues of this stripe.
slingamn said:
I gave up on this project. If you're interested in working on it further, I would suggest contacting the Replicant developers (#replicant on freenode) for advice --- they're the people I would expect to know the most about hardware issues of this stripe.
Click to expand...
Click to collapse
i am also haviong the same problem.I installed 4.3 factory image,build JWR66Y on my Galaxy Nexus .But after flashing my IMEI become generic (004999010640000).So I cant registered on network. Can give some suggestions to restore my genuine IMEI...
Hello, this is really weird. In fact, when I insert the SIM to my Note 2 N7100 and turn it on, it allows me to make emergency call, but I cannot use it to make any others and it doesn't show the carrier name (it shows Emergency call only). And when I try to use it to make normal phone calls, it says that I am not registered to a mobile network. I try to factory reset my phone, but the problem remains. I then try to remove the SIM card, and it says that I need to insert a SIM card (that means that it is not a hardware problem since it recognizes the card). I then try to go to the mobile network setting to try to connect to the network manually, it connects me but it shows me a warning which says that the mobile network service is not available (and the Emergency call only label remains). However, I am sure that this is not the problem of the card neither since when I insert the card to my Moto MB860, I can make calls as usual. So, what is the problem ??? It seems to me that the problem happens spontaneously since it works perfectly until yesterday. And all other wireless function works fine including wifi , Bluetooth and GPS and the only thing goes wrong is 3g and 2g.
Additional information:
ROM: Omega v.16
Carrier: Fido Canada (as you can see)
Thanks.
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore
jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
I tried a simple way which is format everything and flash another ROM but the problem remains.
TRS_80 said:
Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore
Click to expand...
Click to collapse
I don't know that we are in the same situation since at home I often got a good signal and this happened to me only since yesterday.
jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.
Dan Law 001 said:
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.
Click to expand...
Click to collapse
Results..??
Sent from my GT-I9001 using xda premium
jabrif said:
Results..??
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
I need to get the firmware first... since I already passed the download quota for today... need to wait until tomorrow...
Mmm... I heard that you mentioned clearing the EFS in your given procedure, but I do not think that I modified that folder... However, about few days ago, since I want to gain better control on the volume on my headphone remotes, I did modify the file called Generic.kl in system/usr/keylayout, but I restore it after since it didn't work. However, I don't think that this modification will trigger something in the efs folder since it has different directory. By the way, I did some research online and they say that the efs contains information about the carrier on the phone, so will there's a greater chance that the problem is caused by the possible modification on the efs than any other factor and will there also something else that possibly trigger the similar effects?
Sent from my GT-N7100 using xda premium
Still nothing
I need experts review and help to resolve my issue last night i am update my phone s20 ultra G988B/ds to its original software everything working fine except network i was using root phone it was fine on all networks but after updating my imei status goes to NG(not good) sim accepted phone but shows emergency calls both imei shoes but network not working plz give me suggestions and issue solution. I am again root my phone but still not working networks plz help
S20 ultra imei status NG
Why you experts not solving my issue no comments at all?
Bro i've posted same kind of post just now i hope someone replies soon otherwise i'll try z3x software or chimera and let you know about the results, i think if your imei is not corrupted then cert file will do the wonder.
well hey everyone same issue i have s20 plus phone was rooted and i flash the firmware and now imei is NG i trid the chimera tool but no luck if u find any fix please help me.
did you guys resolve it ?
i may have an idea
Any fix
do you guys even search before asking?
First, do a TWRP backup, all partitions including efs & modem.
Open the root explorer app, open the efs folder, delete the files named nv_data.bin
, nv_data.bin.md5 & the folder called imei. Then open twrp, wipe all partitions. Flash the latest firmware with Odin.
That solution work???
juda iskariotsky said:
do you guys even search before asking?
First, do a TWRP backup, all partitions including efs & modem.
Open the root explorer app, open the efs folder, delete the files named nv_data.bin
, nv_data.bin.md5 & the folder called imei. Then open twrp, wipe all partitions. Flash the latest firmware with Odin
Click to expand...
Click to collapse
Hi,
I have my 5T rooted with Magisk and TWRP recovery.
I've upgrated from OOS 9 to official OOS 10.0.1 flashing with TWRP as usual. I did a full nandroid backup before.
Everything went fine until I noticed that during the booting of the phone after the flashing, it didn't ask for the SIM code as it used to. And once the mobile had fully restarted, I could see 2 new icons on top of the screen picturing the 2 sim cards that can be contained in a OnePLus 5T. They were striken through, as if not present, when I had My SIM in Slot 1. And so, no mobile signal, no data network.
I tried switching Sim cards with another mpbile. My SIM worked fine in the other mobile and the other SIM was not recognized by my mobile.
I've read that I could be facing problems of damaged EFS. So I tried restoring through TWRP the EFS partition from the Nandroid I had done before. Nothing. Same thing with the modem partition. Nothing.
I tried then to restore the EFS from a safety backup that I had using Fastboot. Nothing.
I could still try to restore the full nandroid backup done at the beginning, but I forgot to take out pin protection code before taking the Nandroid, and I've read somewhere that it could be an issue after restoring the system. I might not be able to restart the phone and be obliged to factory reset, witch I would really like to avoid. And anyway, if restoring with Fastboot did not work, I wonder if the full restore would change anything.
Anyway, anybody has a magic idea about might be happening? A little help please??
Same problem!
I'm having the same problem. I have my 5T rooted with Magisk and TWRP recovery.
I've upgrated from OOS 9 to official OOS 10.0.1 flashing with TWRP as usual. I did a full TWRP backup before, including my EFS partition.
I'm seeing this too:
>"once the mobile had fully restarted, I could see 2 new icons on top of the screen picturing the 2 sim cards that can be contained in a OnePLus 5T. >They were striken through, as if not present, when I had My SIM in Slot 1. And so, no mobile signal, no data network."
I did the same thing and had the same no result.
>I've read that I could be facing problems of damaged EFS. So I tried restoring through TWRP the EFS partition from the Nandroid I had done >before. Nothing. Same thing with the modem partition. Nothing.
I'm looking for a solution too.
I came across this: https://forum.xda-developers.com/oneplus-5t/help/baseband-imei-lost-t3834334 and this: https://www.getdroidtips.com/how-to-repair-and-fix-imei-baseband-on-oneplus-5t-a5010/
I've been reluctant to try and rebuild the QCN file, but it might work.
Working on this
So I'm working on reprogramming the IMEI using the Qualcomm tools. I was able to use them to back up my phone and see the it still has the correct MEID.
However, the .gcn file linked to below isn't accepted, with a weird error: "The file model MSM8998 does not match the phone model MSM8998. Please select a file for the MSM8998."
I'm not sure what it isn't liking. In theory, I think I could just put the IMEI numbers into the QPST programming tool, but I'm not certain where they would go and the correct format for them (with the chksm at the end or not?).
This is as far as I've gotten. I'm looking for an alternate .qcn or .qcnx (which is the kind the tool generates when saving files).
rootlessabroad said:
I'm having the same problem. I have my 5T rooted with Magisk and TWRP recovery.
I've upgrated from OOS 9 to official OOS 10.0.1 flashing with TWRP as usual. I did a full TWRP backup before, including my EFS partition.
I'm seeing this too:
>"once the mobile had fully restarted, I could see 2 new icons on top of the screen picturing the 2 sim cards that can be contained in a OnePLus 5T. >They were striken through, as if not present, when I had My SIM in Slot 1. And so, no mobile signal, no data network."
I did the same thing and had the same no result.
>I've read that I could be facing problems of damaged EFS. So I tried restoring through TWRP the EFS partition from the Nandroid I had done >before. Nothing. Same thing with the modem partition. Nothing.
I'm looking for a solution too.
I came across this: https://forum.xda-developers.com/oneplus-5t/help/baseband-imei-lost-t3834334 and this: https://www.getdroidtips.com/how-to-repair-and-fix-imei-baseband-on-oneplus-5t-a5010/
I've been reluctant to try and rebuild the QCN file, but it might work.
Click to expand...
Click to collapse
Hi
I've found a code (*#06#) in a page that gives you the MEID. It worked for me. Hopefully, I have the correct MEID too. The code for the IMEI did not show anything. I'll check the lynks you posted later today.
Thanks for sharing!!
PS. I can not include the lynk to codes page as I'm too junior a member and XDA forums won't let me.
rootlessabroad said:
So I'm working on reprogramming the IMEI using the Qualcomm tools. I was able to use them to back up my phone and see the it still has the correct MEID.
However, the .gcn file linked to below isn't accepted, with a weird error: "The file model MSM8998 does not match the phone model MSM8998. Please select a file for the MSM8998."
I'm not sure what it isn't liking. In theory, I think I could just put the IMEI numbers into the QPST programming tool, but I'm not certain where they would go and the correct format for them (with the chksm at the end or not?).
This is as far as I've gotten. I'm looking for an alternate .qcn or .qcnx (which is the kind the tool generates when saving files).
Click to expand...
Click to collapse
So I've tried te rebuild the QCN file. But my issue is that I can't make the ADB comunicate with my mobile. It is as the mobile was not plugged in?? The usb debugging is activated. I can browse the mobile memory from the computer. But the ADB doesn't lynk with the mobile; when you type adb devices, it says List of devices attached and nothing after. Any idea what might be happening?
What about you rootlessabroad? could you fix it?
rootlessabroad said:
So I'm working on reprogramming the IMEI using the Qualcomm tools. I was able to use them to back up my phone and see the it still has the correct MEID.
However, the .gcn file linked to below isn't accepted, with a weird error: "The file model MSM8998 does not match the phone model MSM8998. Please select a file for the MSM8998."
I'm not sure what it isn't liking. In theory, I think I could just put the IMEI numbers into the QPST programming tool, but I'm not certain where they would go and the correct format for them (with the chksm at the end or not?).
This is as far as I've gotten. I'm looking for an alternate .qcn or .qcnx (which is the kind the tool generates when saving files).
Click to expand...
Click to collapse