yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] marsrogers:
No, thanks however~the dropbox is also blocked here...:(

I dragged it down through vpn~

thank you anyway~~:o
[Nexus S Android Development] NexusCrazy:
Will my local mobile repair/unlock shop be able to write my original IMEI number back to my phone with one of there magic box/clip thingy?

I'm going to phone and see what he says, will post back soon.
[Nexus S Android Development] RisinT96:
dude, dont you read what people write? dont flash this, it will mess up your IMEI
[Nexus S Android Development] thegod2012:
fml really theres nothing out there that fixes this the easy way what has the dev said about this issue
[Nexus S Android Development] Erkan75:
Mine is an i9023 .... never flashed this rom and my imei is ok. but also in my file you can see i9000. so that can't be the issue:

my file:

GT-I9023 EUR EUR 2010-10-14 - I9020TEST 0000 0000 74700000809113 KB100D00WM(I9000)
[Nexus S Android Development] nitsuajd:
Yeah it's strange I have the issue and look mine...

GT-I9020T ¹Ì±¹/TMB TMB 2010-11-29 ±ÇÁØ¿À XXJK6 7CB0 CF0D 7520000 KB100D00WM(I9020T)S 0902-002582 xxx4-1011-24xx

Edit: I've the TMB version of i9020
[Nexus S Android Development] erikwervo:
i havent flash this ROM yet. but this imei things get into my curiousity. then i check my imei and find out that its different. how can it be? yes im a flash whore. this might be not the 1st case. perhaps with other custom ROM and we just dont realized it.

i dont know from how long my imei been changed but so far i got no problem with 3g signal.

hope this matter can be solved sooner or later.
[Nexus S Android Development] fixxxer2008:
for safety reasons the mods should lock this thread. no offense to the dev.
[Nexus S Android Development] Gonizahavy:
remove all the links- yes

lock the thread- no

we still need to find a solution.
[Nexus S Android Development] fixxxer2008:
theres a new thread opened for the issues at hand.
[Nexus S Android Development] thegod2012:
has anybody phone actually got block out or is this to prevent it and not get to that point
[Nexus S Android Development] erikwervo:
no we still need this thread for anything about solving this problem.

am not saying am looking forward for the next 0.4 update...

anyhow the download link is already removed and people should read the thread tittle 1st before they decide to flash the ROM :D
[Nexus S Android Development] bloodhawk:
Mine has , along with NexusCrazy's.

Its not long before other phones also start getting blocked, maybe this week , next week, maybe even after a month but it will happen for sure.

Because duplicate IMEI's are a huge risk for national security.
[Nexus S Android Development] erikwervo:
opps didnt realized it, havent out of this thread yet today :o
[Nexus S Android Development] fixxxer2008:
wheres the dev to respond to what happened here? im pretty sure people will not be testing out any future builds after this. shame as i would of loved to have sense on my ns4g.
[Nexus S Android Development] RisinT96:
hey! this is how they restore the imei on the captivate: http://xdaforums.com/showthread.php?t=881162 , i read it and a guy said that his imei became: 004999010640000 , same as us!

After i thought about it and about the nv log that says:

Thu May 26 13:20:25 2011: No NV backup found. Create one before MD5 on.
Thu May 26 13:20:25 2011: NV data back-up begin.
Thu May 26 13:20:25 2011: nv_data.bin does not exist.
Thu May 26 13:20:25 2011: NV data backup stopped due to NV data size.
Thu May 26 13:20:25 2011: MD5 is turned on.
Thu May 26 13:20:25 2011: nv_data.bin does not exist.
Thu May 26 13:20:25 2011: [B][U]default NV restored[/U][/B].

I think that the default IMEI for all the devices of the galaxy S series is : 004999010640000, Thats why we all got it!

I also opened a new thread where i hope we will find a solution: http://xdaforums.com/showthread.php?t=1098963
[Nexus S Android Development] erikwervo:
whatt??!! :eek: thats exactly my imei now.

and i dont flash this nexus sense 0.3 yet. how come?:confused::confused:
[Nexus S Android Development] l_sarra:
I have the same IMEI!!!!
[Nexus S Android Development] treUse:
It seems another ROM has caused this in the past...
[Nexus S Android Development] bigmizz79:
Maybe 0.2..but no one noticed..!!!
[Nexus S Android Development] treUse:
I dearly hope not.

I read in another thread you got in contact with an owner of the same version of the phone as you have, any progress?
[Nexus S Android Development] bloodhawk:
Yea have been trying to get it working. Tried changing a few values. Set the permissions and rebooted. BAM! the phone resets it to crap values :(
[Nexus S Android Development] RisinT96:
Maybe if you still have calls and all this stuff working not everything is lost!

Some of us whose cell phones are working may not be in such deep shi*....
[Nexus S Android Development] erikwervo:
exactly like i thought :cool:
[Nexus S Android Development] RisinT96:
Thats exactly what i said, that this IMEI is the default IMEI that why you get it if something is wrong
[Nexus S Android Development] Gonizahavy:
yes!

here is a part of the NexusSense02 updater-script:

# START: restore efs
show_progress(0.100000, 10);
ui_print("Restoring efs...");
mount("yaffs2", "MTD", "efs", "/efs");
assert(is_mounted("/efs"));
assert(is_mounted("/sdcard"));
package_extract_file("efsrestore.sh", "/tmp/efsrestore.sh");
set_perm(0, 0, 0777, "/tmp/efsrestore.sh");
run_program("/tmp/efsrestore.sh", "restore");
# END: restore efs
[Nexus S Android Development] erikwervo:
since we're on the same imei, if i can help with anything just holla. i will be glad to upload anything needed if its any means good.

mine got everything works like a charm HSDPA etc.. just this magical imei.. :confused::confused::confused:
[Nexus S Android Development] l_sarra:
I may have found a way to solve

Since we have galaxy's default imei and nav file, we can change imei like a galaxy :D

This is the video but I do not understand English well can someone translate the guide?
[Nexus S Android Development] treUse:
Maybe it was there even in 0.1...

Anyway, seems we're SOL unless someone works a miracle.
[Nexus S Android Development] bloodhawk:
The galaxy Method wont work unless we know what to replace and with what!
[Nexus S Android Development] erikwervo:
haha since 0.1 speechless...

c'mon apreichner, u know how to solve this.

the grow of this thread pages will kick cm7 nightly in no time if this still unsolved :o
[Nexus S Android Development] treUse:
Not in a positive way though...
[Nexus S Android Development] wuyanks:
FYI i flashed 0.2 in the past (NOT 0.3) and my IMEI is fine...
[Nexus S Android Development] RisinT96:
Thats right

I think that i had the same IMEI when i got my device from the shop, dono why.

but everything seems to be working for me
[Nexus S Android Development] treUse:
Strange, must be something else then.
[Nexus S Android Development] erikwervo:
how about the 0.1

if still no then lets start with other ROM :confused:
[Nexus S Android Development] paulpenny:
Yep. I flashed 0.2 and my IMEI is still correct.
[Nexus S Android Development] treUse:
What version of the Nexus S do you have?
[Nexus S Android Development] deeren:
yep. the 0.3 version has a script used to clear efs.
[Nexus S Android Development] fixxxer2008:
why would the dev put that in the rom?
[Nexus S Android Development] apreichner:
The lines in the updater script are there in 0.2but no restore sh file. The sh file is what did the job. The updater script just runs the file. I am researching. Another rom must have done this too.

I am contacting all devs I can.
[Nexus S Android Development] bigmizz79:
If its samsungs default O'Neil we should all b fine right..??
[Nexus S Android Development] apreichner:
It was a mistake because this was a port from a galaxy s rom. I apologize i didn't realize the script didn't back it up first.
[Nexus S Android Development] deeren:
mistakes happen i guess. . i even cooked a stock rom with a script removing the corrupted efs (thinking it might regenerate the good one on a stock nexus rom upon boot ) but nope.it failed.

installing windows now just to try the odin thing as i speak
[Nexus S Android Development] fixxxer2008:
it's ok, i was just curious, not bashing you.
[Nexus S Android Development] thegod2012:
Odin didn't help for me on windows
[Nexus S Android Development] barca-x:
hi my imei is change :S

but i'm restore my old backup .. and nothing is change :(

i have backup of old rom .. but nothing change
[Nexus S Android Development] deeren:
i think it's something even more than the imei or even product code. i removed my simcard and i see that i can still pick up signals (signal bar is active). lol. (dont know here i get this energy to smile though)
[Nexus S Android Development] erikwervo:
yeah it wont change.

lets sit down for a while and expect something good;)
[Nexus S Android Development] RisinT96:
Hey apreichner, I opened a thread where I hope to get a solution: http://xdaforums.com/showthread.php?t=1098963
[Nexus S Android Development] pulser_g2:
If you have a backup of your EFS partition (/efs), you should be able to restore it. If not, then I'm not aware of any way to restore the IMEI on the newer Nexus models, due to the fact that it's now lost...

To stop IMEI changing, it seems Samsung added more protection to the system, but that obviously makes it much harder to change it in this (legitimate) case.

I will take a look, but I don't have a Nexus S :(
[Nexus S Android Development] thegod2012:
Well I'm stumped I haven't slept yet due to this issue but I exhausted all sources but came up with nothing all is lost or all is not good luck everyone I have faith xda has never failed.
[Nexus S Android Development] treUse:
apreichner, do you think we have any hope of resolving this mess?
[Nexus S Android Development] bloodhawk:
I dont think so.

Lets hope im wrong.
[Nexus S Android Development] wuyanks:
Has anyone contacted TMobile or Samsung about this? This is truly a peculiar situation....
[Nexus S Android Development] erikwervo:
me too

but i put more hopes that phone provider in my country doesnt really care about duplicated imei.
[Nexus S Android Development] treUse:
True that...
[Nexus S Android Development] Zehlek:
I have the same imei
[Nexus S Android Development] bringonblink:
Just read through all the posts since the first issue cropped up...

Wow this is really unfortunate, hopfully koush will see this and backup the EFS partition in clockworkmod now.

Has anyone tried contacting samsung and asking for help?
[Nexus S Android Development] bloodhawk:
Nope i at least cant, because mine is a UK imported set :(
[Nexus S Android Development] treUse:
Yeah, mine's also imported...
[Nexus S Android Development] erikwervo:
welcome to the brotherhood :p

new world order. 1 imei for many devices.
[Nexus S Android Development] bringonblink:
sharing IS caring...
[Nexus S Android Development] treUse:
This sure is a major screwup...
[Nexus S Android Development] erikwervo:
thread of the months
[Nexus S Android Development] treUse:
Too bad it wasn't something to celebrate..
[Nexus S Android Development] marsrogers:
Yeah, I read these, but sadly I've already messed my IMEI before you guys posted the issue...

That reply is just to say thank you to the Windows7 for his willing to help~

As for the issue, I used Hex editor to open the nv_data.bin which caused the problem, but it was more likely a mess...

I'm trying to find if anyone is willing to upload a untouched efs folder in China's forum Gfan.com

Luckily I still can use my phone to make a call.
[Nexus S Android Development] chuckenfoot:
Member of the brotherhood here too...
[Nexus S Android Development] murdoch1:
Sadly........

apreichner's gone extremely quiet.......I feel for him. His sheer determination to release a Sense based rom was faultless. Sadly in the demand for v3 some dodgy scripting was left intact. Maybe we shouldnt harrass him for updates in future? Hopefully this wont put him off from future developing. At least he and us will know better in future.

I never realised the importance of backing up the efs folder.......hindsight...a wonderful thing.:o
[Nexus S Android Development] RisinT96:
I wanted sense so much and now no sense and fkd up imei .

Sad.......
[Nexus S Android Development] bloodhawk:
Im gonna throw my phone at the wall soon! :D
[Nexus S Android Development] treUse:
Try selling it instead ^_^

Nah, I feel you though, just waiting for mine to suddenly stop working...
[Nexus S Android Development] deeren:
now my aim is to brick the phone at the point it doesnt even light up. so that at the repairs, they can no longer check for imei through the phone.
[Nexus S Android Development] dario3040:
lol, flash some random HTC Desire Radio or something xP
[Nexus S Android Development] deeren:
was just kidding. ( i bought the phone from us- so no warranty whatsoever) i'll just wait and hope my imei does not get blacklisted or something and in the meantime hope that someone figure out a way to regenerate the bin file.
[Nexus S Android Development] Azure465:
Wow, now i'm really thankful I decided to wait a few days before trying this ROM :eek::eek:

I hope your phones can be fixed
[Nexus S Android Development] bloodhawk:
And im so sorry i did try it. Had purchased the phone off of a 3rd Party dealer a week back. :(
[Nexus S Android Development] deogunsurya:
well..can't do anything at the moment..

More than 10 people have bricked their phones with this and there will be more who don't even know that their IMEI is illegal or not the correct one and their connection can be terminated anytime...

sadness... :(
[Nexus S Android Development] bloodhawk:
@Op any response from your contacts?

Would love to hear some good news.
[Nexus S Android Development] treUse:
Yeah, some good news would be nice ...
[Nexus S Android Development] NexusCrazy:
+1 I'd be very interested in what your Developer you contacted has had to say.
[Nexus S Android Development] erikwervo:
How about the 0.1 or the 0.2? Did u flashed it? How about the other rom? If yes .. best for u to check your imei too. Hopefully you're good. Even though we still accepting more people in our brotherhood.:D

@apreichner

Please continue developing for this rom. Well my imei messed up already what can i say, but still having a working sense port is kinda cool fo me. Dont quit on us mate
[Nexus S Android Development] saryu:
actually the theory is quite simple, if sense ROM can change it, we can change it back the way the ROM change it..
[Nexus S Android Development] deogunsurya:
Go through all the pages from 75 to the current one.

I'm sure you'll take your words back.
[Nexus S Android Development] erikwervo:
Well he's talking about theory.. so he's right.. the thing is theory just not enough here right?

@saryu

Nice to see you here bro (well i know u're here all the time :p )
[Nexus S Android Development] derekwilkinson:
Surely there must be a way to inject the old IMEI number into the efs folder?
[Nexus S Android Development] deogunsurya:
^ Well there should be some.. Just need some good dev to check, what can be done at the moment... When SGS can be recovered, I believe this can be recovered as well..

@erikwervo - I mean to say that it isnt that easy as what he wrote.. and right now, it is looking impossible.
[Nexus S Android Development] Zehlek:
I'm sure there is a way but I have no idea
[Nexus S Android Development] Zehlek:
I don't think I have to worry about being cut off from Rogers. I have had my NS since December and they still think I am using an iPhone 4 :p
[Nexus S Android Development] Gonizahavy:
the script inside the 0.3 rom deleted the /efs folder (wrongly) assuming you have a backup in the /sdcard/backup/efs and then copy the backup to the /efs partition.

and in our case, there was no backup what so ever... which led to the system creating a default "failsafe" /efs content with this *40000 IMEI number
[Nexus S Android Development] erikwervo:
I heard about this device called JIG or something like that to manualy inject the imei for samsung devices. Some of my friend will check it out tomorrow to SCC if the same method can be done for nexus s. Hopefully some good result from there.
[Nexus S Android Development] mak213:
hopefully the dev will actually post something or comment...give us some type of reassurance ! :( thats hes actually trying?
[Nexus S Android Development] cgi101:
Have had all these efs problems with my Galaxy S before. The IMEI cannot be injected because nv_data.bin which contains your IMEI is encrypted, and then also MD5 hashed to make sure it isn't altered. It can only be restored if you had a backup of the original, or by sending it to samsung for service.

Some limited number of SGH-i897 captivate users claimed the phone restored their IMEI when they flashed to stock and did an ODIN master clear. I had no success with my Canadian captivate (SHG-i896).

The USB jig (which I have) only allows you to enter 'download mode' which lets you flash the phone including partitions like the /efs. However, without the original backup, there is nothing useful you can flash. The files in /efs are unique for each phone.
[Nexus S Android Development] saryu:
lol, page 75 is too long to read.. anyway, i haven't messed up my IMEI so i don't know the actual problem. I'm gonna go to SSC on monday for other phone, i will ask them about nexus s too if they can help it..
[Nexus S Android Development] TheDub:
I'm sure he's trying but the real world (work/family/kids/school/girlfriend/boyfriend/dog/cat/dentist appointment/you name it) can't just be pushed to the side so he/she might not be available 24/7....

Have some faith and remember that sometimes things go wrong when using your phone outside of what it was intended to do. (Read the Google warning when you unlock your phone ;))
[Nexus S Android Development] mak213:
yes yes i no just some good faith hes trying is all trust i obvouisly love his work i musta been like first one to flash lmao
[Nexus S Android Development] brmayhem:
And I have now been blacklisted (I think)

No calls or texts, only Wifi.

Time to dust off the ol' Razr. Fml.
[Nexus S Android Development] lavcoles:
actually that is correct grammar ^^ just saying.. lets just focus on the rom though guys
[Nexus S Android Development] Zehlek:
It is the best ROM out there thus far
[Nexus S Android Development] Trinitronik:
Any updates? Pleaassee :)))
[Nexus S Android Development] Zehlek:
Hopefully some good news soon
[Nexus S Android Development] dario3040:
Well, technicaly its not really the best rom, since many things are lacking (wifi, HW3d .etc).

But its still a step in the right direction
[Nexus S Android Development] Zehlek:
Touche. Sense is one of my favorites though lol
[Nexus S Android Development] apreichner:
I was thinking the same lol.

Hw3d is still giving me some troubles but I have an idea on how to fix it. I just need more time in a day lol. School is almost done so ill have more time soon.
[Nexus S Android Development] dario3040:
Huh, school was done 3 days ago here :S
[Nexus S Android Development] Zehlek:
It's a big step even getting it ported and booting up. I'd rather it take a little longer and working smooth then be rushed and very buggy
[Nexus S Android Development] xanos01:
I agree take your time on this future masterpiece. Iknow it will be big.
[Nexus S Android Development] Zehlek:
I am so anxious
[Nexus S Android Development] jroid:
Haven't really had a look (flashed) but you may want to have a read at init.herring.rc in the ramdisk. Make sure prvsrvinit looks good in /bin and load the hw libs in the respective dirs. I never achieved hw accel in the HC port but was right about there until me and steve encountered it had a bad driver in the kernel which was causing pvrsrvinit to fail and not load the hw libs.
[Nexus S Android Development] apreichner:
HW3D doesn't exist in the build I uploaded, it is using SoftGL because the drivers aren't there. The issue is in my current testing builds which don't boot because of the HW3D issue.

Here is a link to my logcat if anyone can give me some information:

http://dl.dropbox.com/u/1896480/logcatnotbooting.txt
[Nexus S Android Development] kingkurry:
Can you do a vibrant port too please?
[Nexus S Android Development] dario3040:
What are you doing here?
[Nexus S Android Development] Vandam500:
ROFL he hasn't even gotten everything to work on this version let alone even start thinking about doing another device.
[Nexus S Android Development] catchsomezz:
sorry for asking such a basic quesiton...but why? whats so good about sense UI?

i've did some googling but other than its found on HTC devices...i can't find anything on why people want it on the nexus s. but im sure there is! please educate!
[Nexus S Android Development] zephiK:
People have their preferences. Some people like the way it looks.besides, another rom doesn't hurt
[Nexus S Android Development] apreichner:
Im not a huge fan of it myself but i look at it like its a challenge. Actually right now im trying out miui as a daily driver while i work on this port.
[Nexus S Android Development] Zehlek:
Do you think a stable sense Rom will be possible?
[Nexus S Android Development] :
What service do you have?

-Remember, Android hell is a real place and you will be sent there at the first sign of defiance-
[Nexus S Android Development] pnnorth:
I had previously flashed 0.2 and my imei is fine so it must just be a problem with 0.3.

Hope you all manage to get this problem fixed.
[Nexus S Android Development] x4-FAo:
Hopefully this was not done intentionally
[Nexus S Android Development] brmayhem:
T-Mobile USA
[Nexus S Android Development] RisinT96:
All I can say is: ****, MY DEVICE IS ONLY ONE MONTH OLD AND I FKED IT UP!

I lost all my hope (although everything is STILL working, hope it won't stop)
[Nexus S Android Development] RisinT96:
What will happen if I delete my efs folder?
[Nexus S Android Development] jaker.the.skater:
I can confirm .2 did not change mine. hopefully this gets sorted out for you guys.
[Nexus S Android Development] :
Nothing, it'll still be the corrupted imei.

-Remember, Android hell is a real place and you will be sent there at the first sign of defiance-
[Nexus S Android Development] Blu3D:
Anyone know how the phone stores the failsafe imei?

Since, according to the logs, the efs is rebuilt from this default it could be possible to edit the default to your old imei and let it rebuild again.

It probably way down in the system and encrypted and everything though. Maybe even stored on hardware level.
[Nexus S Android Development] chiledog:
Man I really feel for you guys that have lost your IMEI.

There are always risks when flashing non-official Roms though and I hope the dev doesn't stop because of this.
[Nexus S Android Development] dario3040:
That's the most stupid thing I have ever heard :P

I don't think he would do that.
[Nexus S Android Development] treUse:
That's interesting...
[Nexus S Android Development] RisinT96:
I bought my device from a private shop in Israel called vmobile, because the shop added Hebrew support they rooted,unlocked and did all this stuff needed to change rom, then they changed the rom to a custom one, they gave me one year warranty which is still valid.

I have a backup of the rom I had out of the box, do you think that if I restore it and go to the shop and tell them I decided to check my IMEI and found out it doesn't match to the one on the box, will they agree to fix/change my phone? (They won't know I changed rom , and because I got it already rooted the warranty should be valid)
[Nexus S Android Development] RisinT96:
I think that this failsafe imei is stored down in the system and is the same for all android devices because some other phones also have the same imei we all got.
[Nexus S Android Development] Gonizahavy:
what should i say to best buy (where i bought the phone) if i want them to send it to samsung for repair? what do i need to do to get it fixed?