Related
Hi everybody!
Yesterday I installaed the new build JPC and before this I taken a backup of nv_data.bin and nv_data.bin.md5 but this morning I've deleted my MD5 file.......
I've try to calculate another MD5 checksum but this is different. I made md5 from JPC's nv_data.bin and this is different than hash inside of nv_data.bin.md5
Do anyone know generate a correct hash?
I used MD5sum.exe in Windows and md5sum of busybox.
Thanks
dont u have a backup file .nv_data.bak.md5 in /efs?
Mikulec said:
dont u have a backup file .nv_data.bak.md5 in /efs?
Click to expand...
Click to collapse
No. Because I already run two flash
Sent from my GT-I9000 using XDA App
anyone have idea?
Nothing?
It's impossible that no one know to made this md5...
Sent from my GT-I9000 using XDA App
I've tried many many times but without good result..........probably there is a "salt" in .md5, not only generated on the file.
tokinux said:
I've tried many many times but without good result..........probably there is a "salt" in .md5, not only generated on the file.
Click to expand...
Click to collapse
I tried much way but nothing...
My problem isn't the IMEI code or Product Code but the code to unlock, infact with Windows application I can see the two code (network and unlock) but with SGS with "SGS Unlock" I can't see these two code...
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
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
My tail of woe. From what I have read there is nothing that can be done but I thought I would ask anyhow.
I was overseas with an SGH-T999L, and took it to a man in a market to be unlocked. 2 hours later it was useless. The man said it would be OK once it was back in the US, but it wasn't. Obviously he didn't keep backups.
Dialing *#06# gives me "null/null".
I cannot turn on wifi (I slie the switch and it slides right back) but can turn on bluetooth, gps and nfc.
Baseband version is "Unknown"
Build number is JSS15J.T999LUVUBNC1
It appears that he used vRoot to get root.
According to the "odin screen"
CUSTOM BINARY DOWNLOAD: No
CURENT BINARY: Samsung Official
SYSTEM: STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER AP SWREV: 1
I used this article from techglobal101.wordpress.com 2013/05/02/how-to-solve-no-service-on-samsung-galaxy-s3/ following the imei already corrupt steps to generate
the text file with the imei in it. However the NV Reader/writer has problems. Firstly *#7284# only gives me a choice of "Modem" or "PDA". However *#0808# does give me more options including "RMNET + DM + MODEM". The bigger problem is that the SPC code of 000000 is not accepted, so NV reader/writer can not access anything.
Looking in the /efs filesystem (using "adb shell" and "su" and "busybox find /efs -size +1000k" ) does not find any files larger than 1MB (I believe the nv_data.bin should be at least 2MB) so no original ".nv_data" file, no "nv_data.bin" nor "nv_data.bak". There are smaller files, for example there is a file /efs/imei/mps_code.dat, 3 bytes long containing TMB. The /efs partition is 13716 blocks in size and is only 33% full (4556 blocks in use).
I can use adb to install and uninstall packages, and copy files.
Things which look interesting to me in the output of "getprop" are (with a valid sim card installed)
[DEVICE_PROVISIONED]: [1]
[gsm.operator.alpha]: []
[gsm.sim,state]: [NOT_READY]
[gsm.sim.unknownready]: [1]
So far I have not done anything else. In particular I have not tried using ODIN to download a stock image, nor have I tried removing the files which are in /efs.
I also have not tried creating a 2MB file of NUL characters called /efs/nv_data.bin in the hope that that would at least advance the solution.
I would be pleased to get any good advice on what to do next. Please assume I know my way around a unix command prompt, but this is my first venture into the world of Android.
First thing, don't mess with the efs. It's not relevant to the issue at hand and sounds to be just fine. Most of the NV Data is stored on different partitions. Don't assume its the same as on other devices like many others seem to advise.
Second, download your stock firmware (NC1)(root66 firmware is ok), flash via Odin on your computer, and factory reset (will wipe internal sd). This often fixes these problems without having to touch the NV data.
Something tells me that whoever you took it to may have tried to flash the 4.1.1 modem to use our free unlock method. If so, that will cause the exact same thing you are experiencing now.
If after that it is still not fixed, PM me and I will try to help get your imei restored. We are not allowed to post information, tools, links or further discuss that here, so if it comes to that, I can only help you via PM.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
How does one change the IMEI?
I've tried this without success:
1. Root your device
2. Download and install QSPT and UltraEdit (HxD would also do).
3. Download an IMEI converter.
4. Get hold of a working qcn (I used my own which I know works in my other P2). Open the file by using Ultraedit/HxD and try to locate the IMEI. In my case it often starts with "08 8A...".
5. Use the IMEI converter and input your true IMEI. Memorize the output.
6. Return to the qcn file. Write it over with the IMEI output you got in step 5.
7. Save the file.
8. In a terminal enter:
su
setprop sys.usb.config rndis,diag,adb
9. Restore the qcn file from step 7 by using QSPT. You click on QPST configuration and go to "ports". If your port isn't already visible go to the device manager, look up the Qualcomm Diag port and add it. For me I believe it's COM9. Now you click on "start clients", then "software download". Tick the "Allow phone/file ESN mismatch", locate your saved qcn file and start restoring it.
10. All done. Reboot!
Apparently some XDA members managed to get their signal back once the modem was deleted so I guess somebody should know.
Other methods I've tried include flashing stock MM and installing OTA until you're on S251 as well as restoring an older full TWRP backup from when your signal used to work. Needless to say, they didn't work.
This procedure worked for me. Lenovo K6 Power with Qualcomm proc.
Successfully I found other users qcn file and wrote my IMEI in it.
Signal is back but diag port disappeared and I can't turn it on again.
WhatsApp me or call me 8436243173
WHERE CAN I GET THIS QNCN ? I'm confused
I had same problem, here are my steps with qcn backup file from working P2. My IMEIs stays right. Sorry for my english and here is my link and read next threads from that forum.
https://forum.xda-developers.com/showpost.php?p=73444145&postcount=70
mL-7 said:
This procedure worked for me. Lenovo K6 Power with Qualcomm proc.
Successfully I found other users qcn file and wrote my IMEI in it.
Signal is back but diag port disappeared and I can't turn it on again.
Click to expand...
Click to collapse
Have K6 power with IMEI turned 0 after fastboot erase modemst1 and 2. Could you please detail the steps to restore IMEI?