yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] emcee15:
i'm currently using GNEX with 4.1 jelly bean os and it is permanently unlock via ****docomo V3 with correct imie..theres a 4.1.2 update available now. just want to ask if i update will i lost the unlocked?
[Samsung Galaxy Nexus] bel3atar:
Works for me
[Samsung Galaxy Nexus] modgadgets:
Did u try Mate flashing Stock ICS or Gingerbread ??
[Samsung Galaxy Nexus] Khizar:
i have gotten unknown baseband a couple of time and a reboot fixes it.. you might have corrupted your efs partition
[Samsung Galaxy Nexus] modgadgets:
That's right 786
[Samsung Galaxy Nexus] sanu.mathews:
thanks

May be a dump question, sorry for that.

If efs is corrupted, then will I be able to see my /factory directory ? I can cat all the md5 files from factory without issues. I'm able to copy nv_data.bin file, even though I didn't try checking the content as it is encrypted
[Samsung Galaxy Nexus] Khizar:
i am not sure.. but you cant try this guide and see if it fixes your issue, i know its for s2 but you can use it on gnex

http://xdaforums.com/showthread.php?t=1264021
[Samsung Galaxy Nexus] sanu.mathews:
thanks k786

---------- Post added at 04:33 PM ---------- Previous post was at 04:14 PM ----------

I'll give a try. Isn't QPST specific to Qualcomm. Samsung Galaxy S2 & S3 may be using Qualcomm baseband chip. Any idea about Gnex baseband part ?

http://www.ifixit.com/Teardown/Samsung+Galaxy+Nexus+Teardown/7182/2
[Samsung Galaxy Nexus] sanu.mathews:
I have an unlocked phone but ran into Baseband not working issues without any rooting/bricking. So I tried flashing, rooting etc without backing IMEI data. I would like to know if I'm trying copy to/from /factory to/from /data/radio to see if md5 mismatch issues get resolved.

Can I use this method to correct my Gnex IMEI issue ? I don't have a an original back up. If I copy nv_data.bin nv_data.bin.md5 from /factory to /data/radio, will it fix the issue in 4.0.4. I tried a few combinations, so far no success.

Thanks
[Samsung Galaxy Nexus] i-MAD:
Good tip but nothing i did resolved the issue becuase:

- FLIGHT MODE doesn't stick... no matter what you do, the phone will keep turning it on and off resulting in copying the nv_data files from factory to data folder

- the permissions can't be changed in factory (and it is not recommended) but they are corrupted

- so when nv_data files are copied over from factory to data folder they have the wrong permissions

- meaning that the system can't even see them

this was verified from the nv.log which keeps saying nv_data.bin file doesn't exist, but if you list (ls command), both files are there! and because it's not found by the system/radio, even if you correct permissions, it will be copied over and over again from factory folder with wrong permissions and fail again.

If only we can find a way to get the FLIGHT MODE to stick, it would make life easier. i have tried to switch radio off in eng menu (*#*#4636#*#*), but it doesn't stick.

Hope this helps

NOTE: my /data/radio/log/nv.log doesn't show any checksum md5 values, orignal (heheh) or computed, because the system can't see the files, though they are there. it says "nv_data_bin file doesn't exist" even if i change owner to radio and permissions to 700.
[Samsung Galaxy Nexus] badtzo:
Have you tried to do it without sim card? I think that works like setting airplane mode on.
[Samsung Galaxy Nexus] i-MAD:
Yes I'm doing all this without a sim card in the phone.

The phone doesn't even recognise a missing sim.
[Samsung Galaxy Nexus] i-MAD:
can I actually copy and change mode and owner of /factory/nv_data.bin from a recovery? this requires mounting system as read/write, right?
[Samsung Galaxy Nexus] badtzo:
Yes you can, I did it once and you can get RW using root explorer or another one for easy way.

For owner and permission use chmod and chown commands as jup007 posted.

Be sure to get correct backup before erasing anything.
[Samsung Galaxy Nexus] _codemaniac_:
F***Docomo Generic IMEI FIXED

I followed this theory to the dot and was able to fix my phone's IMEI. Thanks a ton !!!
[Samsung Galaxy Nexus] whoadood:
Hi, I'm about to get a GNex from vodafone ES, and I wonder whether this is still correct/up to date for this device.

Do I need to run the "theory test" before and then the "theory application", or just go straight to the application?
[Samsung Galaxy Nexus] darshan1983:
I am a newbie can and I tried mouting /factor as rw thru terminal emulator on my phone but it gives message the system is read - only. I also changed the permission on /factory as R/W using root explored and mounted the /factory as r/w still am getting the same read -only error on terminal emulator when executing the echo command. Any help?

My issue is that the phone was working perfectly on t-mobile till few days back when it cannot connect to the network. I inserted the sim in another phone and it worked fine that is when I started reading xda on phones purchased thru negri .

Any help is welcomed
[Samsung Galaxy Nexus] darshan1983:
only trying the steps mentioned in theory test. I am getting following .. ? is this good or bad?

root@android:/data/radio/log # cat nv.log

cat nv.log

Sat Feb 9 23:09:17 2013: nv data does not exist (GED)

Sat Feb 9 23:09:17 2013: checksum fail

Sat Feb 9 23:09:17 2013: checksum fail

Sat Feb 9 23:09:18 2013: default NV restored

Sun Feb 10 01:51:50 2013: checksum fail

Sun Feb 10 01:51:50 2013: checksum fail

Sun Feb 10 01:51:50 2013: checksum fail

Sun Feb 10 01:51:50 2013: default NV restored

--- Guys I figured out what was the problem. My EFS folder was not there and due to which my actual IMEI was lost, hence I had to flash 4.0.4 run the **Docomo app and follow the above steps that ensured my original IMEI was back.

THank you all for help.

Send me a message if anyone is facing similar issue.
[Samsung Galaxy Nexus] alexwinsberg:
I am trying to do the 1. Theory test (reasonably SAFE) method, and when I input cat nv.log, I am told Permission Denied. Have I missed a step somewhere that is preventing me from doing this?
[Samsung Galaxy Nexus] alok1663:
please tell me what to write in COMPUTED2 i am not ale to get it
[Samsung Galaxy Nexus] markizan:
Hi, I bought a Docomo Galaxy Nexus and did the permanent unlock with the F**k Docomo apk. Everything was fine until I transformed my yakju on takju and updated to 4.2.2 Jelly Bean, after 1 month I have lost my network, no calls, no sms, no nothing.

Can I do this procedure with 4.2.2 version or do I have to be on 4.0.4?

Ps: my phone is currently rooted and I can't find the EFS folder, it doesn't exist.

Edit: I tried to the step 1 and got this message:

nv data does not exist (GED)

checksum fail

checksum fail

deafult NV restored

.

.

.

.
[Samsung Galaxy Nexus] plutarcian:
im in the same boat. anyone ?
[Samsung Galaxy Nexus] Pseudonym:
I did this successfully when I downgraded to 4.0.4. After I unlocked I can now upgrade to 4.1 or 4.2.x without problems

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ar_156:
I am very confused about COMPUTED1 and COMPUTED 2...

In cat data/radio/nv_data.bin.md5 I got AABBCCDDxxxxxxxxxx

in cat /factory/nv_data.bin.md5 I got XXYYZZxxxxxxxxx

which is COMPUTED ? COMPUTED1? COMPUTED2? or COMPUTED is a mix of them???

I put XXYYZZxxxxx into /data/radio, checked the md5 and confirmed it was XXYYZZxxxxx but after reboot it changed into other numbers....

Help please
[Samsung Galaxy Nexus] .NetRolller 3D:
I'd like to direct people's attention to this paste: http://pastebin.com/NiM8DwSQ

Appears to be the solution for generating the correct MD5 values without relying on log messages. May also work on Jelly Bean.
[Samsung Galaxy Nexus] libanidibale:
I have the same case here.

Did you resolved the issue by flashing 4.0.4 ?

I am with JB 4.3
[Samsung Galaxy Nexus] puryk:
Welcome. I have a Fujitsu Arrows F-05D with ICS 4.0.3. Can sim unlock by this method? Thank you!
[Samsung Galaxy Nexus] yardiego:
Now i'm the same boat, i just bought a SH-02E locked to Docomo, can i unlock the phone with this method? Thanks!
[Samsung Galaxy Nexus] marti_ns:
Why ****Docomo change the IMEI Number on CM11??

on factory image the imei is not chaged
[Samsung Galaxy Nexus] afraaa:
can i return my IMEI ? some azzhole guy in the name of fix phone used this application and lost my IMEI . and didnt even back up it .

any chance to return it ?
[Samsung Galaxy Nexus] marti_ns:
Flash factory image and original imei should be returned

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] jason.jhake23:
please help

can you provide how to sim unlock my ntt docomo fujitsu f-02e..im just noob,can you provide step by step..please..thanks so much:(:(:(
[Samsung Galaxy Nexus] eyestrey:
what about my gnex it was lock in the philippines [SMART Lock] can anyone help me please... thanks..
[Samsung Galaxy Nexus] tinOFbeer:
Do u mean Smart Philippines simlock? If yes, you need back to Android 4.0.4 and use ****DoCoMo v3.1 app.

Everything Perfect, perm unlock &keep imei

Wysłane z mojego Galaxy Nexus przy użyciu Tapatalka
[Samsung Galaxy Nexus] iamdude:
This method is specific for a Google Galaxy Nexus devices? Or it could be used for an other docomo-locked phone?
[Samsung Galaxy Nexus] jup007:
No, you can just go straight to number 2. Just be sure to be in airplane mode and delete both files in /data/radio/. Otherwise, you'll fix your /factory, but until you wipe out /data/radio (or do factory reset) it will still get used and you'll see generic IMEI.

This post contains complete theory behind while it works, so admittedly, it's quite long. Since tests seem to indicate that this really works, I may create slimmed down executive summary at the beginning - or just create new [HOWTO] thread with only the commands that need to be executed and link to this thread for those who want to know what's going on.

I added Docomo to subject line. Thanks for suggestion.

Above all, thanks everybody who tested this and reported here! :)
[Samsung Galaxy Nexus] pewpewbangbang:
Sounds good, so go into airplane mode, open up root browser, and delete both files in /data/radio/ before moving on with theory 2.

got it

Edit: Crap, I deleted the two files in /data/radio/ before doing Theory 2.....lets see if I run into a problem

Edit: No problem lol, basically nothing happened because I deleted those two files too early? Will go through the process again lol.
[Samsung Galaxy Nexus] jup007:
Yes. Delete of /data/radio files is actually mentioned in theory 2, only airplane mode may be not emphasized enough. I now believe that in non-airplane mode, phone dumps its current status into /data/radio files on shutdown, so if current status is generic imei, that's what you get after reboot too.

Alternative would be battery pull, but I don't like the sound of it. ;)

Edit: and no, as I mentioned before, don't worry too much about /data/radio files. If they don't exist, they get regenerated from factory. It's factory /factory/nv_data.bin that you should not delete (well I did, but it was part of testing, you know. Just have backup.;))
[Samsung Galaxy Nexus] pewpewbangbang:
I did everything and my IMEI is still the generic one. Not sure if I did anything wrong, or if I needed to have my unique IMEI in the beginning or something?
[Samsung Galaxy Nexus] chlehqls:
Could it be possible to have a video tutorial of this soon? This is pretty awesome.

I haven't the time lately to do any sort of modding outside of flashing a kernel or two, but I'm definitely going to try this very soon.
[Samsung Galaxy Nexus] jup007:
What your /data/radio/log/nv.log says? I don't need the whole file, just bottm with recent timestamp is enough.

If there's no recent timestamp (basically time when you did this), /data/radio probably got in the way.
[Samsung Galaxy Nexus] pewpewbangbang:
Fri Apr 20 15:27:28 2012: default NV restored.

Seems like theres the problem already lol

Edit: a bunch of fails also

Fri Apr 20 15:27:28 2012: MD5 fail. orignal md5

'COMPUTED' computed md5

'buncha numbers' (rild)

Fri Apr 20 15:27:28 2012: MD5 fail. orignal md5

'COMPUTED2' computed md5

'buncha numbers' (rild)

Not sure why they spelled "original" "orignal" unless its some word idk about lol
[Samsung Galaxy Nexus] jup007:
Yes, that's generic IMEI nv. Correct message is:

Thu Apr 19 02:20:01 2012: NV restored.(GED)

Slight but important difference.

I assume above it would be some md5 hash fails. Correct?
[Samsung Galaxy Nexus] pewpewbangbang:
I think??

lemme just copy all of it and PM you it.

Edit: PM'd you what my NV Log said
[Samsung Galaxy Nexus] jup007:
Ok, I see. I knew somebody will be confused by this.:D

You're not really supposed to echo string COMPUTED and COMPUTED2 in there. You need to replace them with that bucha numbers, you know. This is different for everyone, so I can't post them.

Redo the whole process, but this time:

- put the first buncha numbers into /factory/nv_data.bin.md5 (it now contains COMPUTED)

- put the second buncha numbers into /factory/.nv_data.bak.md5 (it now contains COMPUTED2)

Don't put there COMPUTED.;)

Edit: This, however, just confirms the theory. MD5 hashes in /factory are broken after application of fdocomo perm unlock and it doesn't really matter what they contain. If you put there random string, it still doesn't work exactly same as before. ;) We only need these string to identify which line belongs o which file. I see how these could be used for an app...
[Samsung Galaxy Nexus] pewpewbangbang:
My IMEI is now unique.....on first reboot though, I couldn't connect back to AT&T. Lets see how it goes after a reboot.

Okay sweet, rebooted and it works. IMEI is my unique IMEI, thanks for the help.

This is awesome, great find and amazing job. When I eventually change ROMs and wipe or something, will find out if it stays true.

Great success people, definitely recommend doing this if you have a Docomo Galaxy Nexus etc....
[Samsung Galaxy Nexus] jup007:
Thanks.:)

I tested factory reset. There's no reason while it wouldn't stick even through ROM flash, once files in your /factory are correct. Almost nothing touches /factory, even ROM developers are generally tiptoeing around this partition and for good reasons.

In your average unlocked phone, /factory is created once in, ehm, factory and never changes since then.
[Samsung Galaxy Nexus] pewpewbangbang:
Sounds good.....perfect unlock basically. Can virtually put a regular back cover and it's exactly the same as i9250. But I like the Docomo branding and how they changed it actually. Looks better to me.

Want a black galaxy nexus though :rolleyes:
[Samsung Galaxy Nexus] jup007:
Yes, this script is equivalent to temp unlock from fdocomo. I just don't like that it chmods bunch of files to 777, they really need to be accessible just by radio.radio.

It probably comes from the same sources as fdocomo. It also modifies files in /factory files on assumption that in some way they're needed for temp unlock (they're not).

Two questions:

- did you try theory test or also theory application?

- what happened on 4.0.4? Did your phone just relock?
[Samsung Galaxy Nexus] pepe_binefar:
i tried the test, i will try the theory along this weekend

when i installed the stock version the phone was locked again, then running the script did not work, and so until today

thanks for the information, i was wondering where did that script come from!
[Samsung Galaxy Nexus] nenepyg:
so i did the test. succeed. i understood which is COMPUTED value but where do i get COMPUTED2 value? :confused:

edit: it is from .nv_data.bak.md5?
[Samsung Galaxy Nexus] jup007:
Thanks. This fits nicely. Since your script doesn't modify backup, /factor/.nv_data.bak, it has correct checksum and once you clean /data/radio (like in /data/wipe) that one gets used. It has correct IMEI but is SIM locked. Now, fdocomo perm unlock also modifies .nv_data.bak in the same way, thus invalidating checksum and forcing generic IMEI to be used.

So, one warning. If you go with theory application and don't modify .nv_data.bak beforehand, you don't need to fix its md5 sum (you won't even see second md5 sum in log files) which is correct. But it's still locked version, so I don't know exactly what happenes. I believe nv_data.bin (unlocked) and now having correct checksum will be the one used, but if it's not, then you'll still end up with locked phone after wipe. In that case you have to modify .nv_data.bak too.

Let me know how it goes.:)
[Samsung Galaxy Nexus] netarchy:
The log will have 2 lines about hashes failing, one is for .nv_data.bak.md5

To figure out which is which, compare the hashes of the md5's to the "found" value in the log, the fail lines tell you the hash it found, and the computed hash.
[Samsung Galaxy Nexus] nenepyg:
ive inserted the one from .nv_data.bak.md5, apllied all successfully, i have my imei, also did wipe/factory reset and i still have my phone unlocked. great job! thanks! :D
[Samsung Galaxy Nexus] chlehqls:
Okay, is Root explorer need or can I just use ES file explorer for the rest of it?

I'm sure it does not matter, but just making sure before I take this on.
[Samsung Galaxy Nexus] jup007:
You don't need root explorer, you just need a way to remount factory in r/w mode for permanent unlock method to work. I use explorer because it's one button in there, but you can just use shell and:

# mount -o rw,remount /dev/block/platform/omap/omap_hsmmc.0/by-name/efs /factory

or something similar.
[Samsung Galaxy Nexus] chlehqls:
So what exactly is COMPUTED2? The one that came after this?

I got the first method down. I have my unique IMEI after being unlocked. I'm trying to work my way toward the second method.

EDIT: Okay, I read a couple of posts back and I think I figured it out. I'm attempting method 2 now.
[Samsung Galaxy Nexus] pewpewbangbang:
Yea, my experience should've cleared up the COMPUTED error.

Definitely just go for Theory 2 so you can get permanent unlock with permanent unique IMEI. I'm happy with it.

Only thing is, I swear service/signal is different now that it's changed. That or the weather really is messing with it. My signal is weaker than before I did all of this and it even went into edge a few times after doing this. I'm hoping it's just the rainy weather though.

Edit: Also running into problems now when after disconnecting from Wi-fi. It doesn't get 3G data back and all I have is grey bars with no "H" icon or anything. Weird....i'll try taking my sim out and messing around with it, trying to continue to replicate this issue.
[Samsung Galaxy Nexus] chlehqls:
Okay, after all of Theory 2 and plus a reboot, my unique IMEI is still there. I'm guessing I did everything right?

As for signal issues, it's been widely reported that 4.0.4 broke data connectivity consistency. It drops out for me time to time when I switch from Wifi to 3G. It takes me a reboot or airplane mode to get back my 3G again. It's pretty lame.
[Samsung Galaxy Nexus] pewpewbangbang:
Yea, but I didn't have these problems with 4.0.4 before doing this.

Either way, I decided to flash a different modem. Changed from UGCL1 to UGLA4 and it seems to be better. I'm putting it down to the crappy weather thats making it weird.

Will see if 3G comes back or not after connecting and disconnecting wi-fi. I'll let it deep sleep a bit too just to make sure.
[Samsung Galaxy Nexus] chlehqls:
Yeah same here. I never had data issues until I either flashed a new kernel or a radio. I cannot remember.

Making a nand and going to fully wipe and flash AOKP b33 for test. I will report back. It should.
[Samsung Galaxy Nexus] pewpewbangbang:
Changing modems seems to have helped. Connects to "H" data almost immediately/quickly after turning wi-fi off.
[Samsung Galaxy Nexus] jup007:
Try to experiment with this if you have time. That's something I'd like to rule out before somebody implements an app. It's now obvious that method works, but there still may be some issues. I also mentioned seeing grey bars quite often, but I can't put my finger on it and if it's different after messing with nv_data. There's generally no reason for this, on he contrary, phone should be in better state now - unless nv_data.bin files were specifically tailored for Japan and generic IMEI one works actually better in the US...
[Samsung Galaxy Nexus] chlehqls:
I'm on XXLA2 since any other modems I have intermittent connectivity during 3G usage where it times out. Still, it's weird that you guys are experiencing that.
[Samsung Galaxy Nexus] pewpewbangbang:
That's what I was thinking. I was like hmmm....was I actually getting better connection with generic IMEI?

But I can't tell because we got bad weather right after I did the IMEI change. But so far, flashing to a different Modem has fixed the problem with not connecting back to "H"/"3G" after connecting/disconnecting to wi-fi.
[Samsung Galaxy Nexus] chlehqls:
Alright, it works on my end. After fully wiping and reflashing, my IMEI is intact and everything works fine.

Congratulations, you done an awesome job. I'm willing to donate a beer or two for this. :)
[Samsung Galaxy Nexus] netarchy:
The IMEI stuff has no bearing on data drops, any idea that you had a better connection is placebo tbh.
[Samsung Galaxy Nexus] pewpewbangbang:
Well I personally can say my connection and radio was different after going through the procedure multiple times. It only went back to normal after flashing a new modem. Wasn't able to get data back after disconnecting from wifi. Even after reboots it fixed it, then after I connected/disconnected from wifi it didn't work again no matter how long I waited for it. I just had grey bars for like 15 minutes with no data. flashing a new modem got rid of the issue. Maybe even re flashing the same modem might have fixed it
[Samsung Galaxy Nexus] netarchy:
http://xdaforums.com/showthread.php?t=1610403

OTA update that fixes the connection drop issue apparently.
[Samsung Galaxy Nexus] pewpewbangbang:
Yea I know, and as I said before. I never had issues with connection drop or anything on 4.0.4 before doing this perm IMEI. All is well now though after flashing UGLA4 after doing the procedures etc..
[Samsung Galaxy Nexus] netarchy:
I still think it's a coincidence, but then I can only base it on my personal experience, and I had the occasional drop on both the generic and unique IMEI.

No biggie, all things considered ;D
[Samsung Galaxy Nexus] pewpewbangbang:
haha yup.....i'm gonna test out running my Min CPU at 700mhz and 875mv undervolt. See if I can get a good blend of battery and performance/stability compared to 350mhz and 760mv undervolt.
[Samsung Galaxy Nexus] jup007:
Yeah, I also believe these shouldn't be related. But then, I don't really know what is contained in nv_data.bin files, the're 2MB long, which is quite a lot of data. What we know they contain:

encrypted IMEI

network lock status, network they've been used to

baseband (radio) version used when they were generated, this can be read clear text there, so your original nv_data.bin will contain SC04DOMKKA, newly regenerated something like i9250XXLA2. This is probably just signature.

few other readable strings

But in the end there's lot of data that I don't have any idea what they mean.

At the same time, my experiments here prove that you can regenerate nv_data.bin from .nv_core.bak, which is half the size and still obviously contains all the vital info, so lot of data is definitely redundant.

Yeah, I should get that donate button. Being czech in the US, I need all beer money I can get.;)
[Samsung Galaxy Nexus] italia0101:
Just a quick question ... Could any of this help me get my original imei number back... As I have a generic 0049..
[Samsung Galaxy Nexus] chlehqls:
Yes you can. If you are familiar with terminals plus having the ability to read/write through root explorer then you can do this. Matter of following the explicit details outlined in each theory.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] italia0101:
Thing is I have no backups of my efs folder... I.e. no.bak files

Iv been searching for a way to fix this for so long

Even if the imei is completely lost ?
[Samsung Galaxy Nexus] italia0101:
Also I probably should have specified I'm on a nexus s
[Samsung Galaxy Nexus] ygvuhb:
if the next version re check and update the md5 file

nv_data.bin.md5 & .nv_data.bak.md5 in /factory

the permanent unlock will break?