yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] stevm:
obviously you don't get it.To fix this takes more than friend of a friend cuz we are missing some vital encriptions informations that only samsungs got.I learned from winmo6 times to back up everything so luckily i could restore my imei in no time.fyi you should read disclaimer and decide the risk for yourself flushing any rom.there's nobody to blame.please leave apreichner out of it,he tried what we all wanted,and i hope he will continue working on sense port despite all flame(blame)etc.my 2 cents
[Nexus S Android Development] mak213:
LMAO sry dude but dammm you should have read...but welcome hope u have more leniant tmobile and they dont notice u have new imei #
[Nexus S Android Development] bloodhawk:
Anybody in the UK willing to help me out?

I can send the phone over and can paypal you the rest of the costs (Shipping + services)

:)
[Nexus S Android Development] mythamp:
apreichner, please do continue your work, like many have said before me, **** happens! and early adapters sometimes get it before the rest. This does not mean you have dissapointed us! Dont beat yourself about this!!!
[Nexus S Android Development] mak213:
ya i guess you cant do anything but cut the loss and continue to work without the "death script" **** my imei is alrdy changed cant do anything now but flash it again and use the dam rom ahahaha so i can gladly say awaiting 0.4
[Nexus S Android Development] unforgiven512:
I want to do some research on this.

I need a copy of the ROM, and as many EFS dumps as possible, both broken and working.

I want to see if I can create a fix.
[Nexus S Android Development] 651stp:
sorry to hear everyone who is stuck with a different IMEI number. It just sucks because no matter where you bought the phone from, (best buy or wherever) the first thing they check when you want to return/exchange/fix the phone is the IMEI number to ensure its the correct phone, so i think getting it done through where you bought it from is a no go.
[Nexus S Android Development] x4-FAo:
Thanks for helping!
[Nexus S Android Development] murdoch1:
I have no choice but try. The phone is clearly marked with my original IMEI number. I am going to argue that it occured when an update failed and plead ignorance. Fingers crossed. CPW scanned the barcode on the back of the phone which provided my original IMEI number. Now lets see what the repair centre has to say for themselves. In the mean time I have the crappiest NOKIA loan set imaginable. LOL. :rolleyes:
[Nexus S Android Development] mak213:
ya they dont *#06# they just check back of battery, also we are not all on different IMEI # unfortunately....we are all on SAME IMEI # lol...wat like 200 persay nexus s users atleast with all same 00499 imei start?
[Nexus S Android Development] bloodhawk:
PM'd you the EFS dumps.
[Nexus S Android Development] tehshouter:
I think we need to wait for a OTA update for the device.
[Nexus S Android Development] mr_recordman:
I have a Nexus S i9023 and it is fully working (Not sure about data, I dont use it)

Of course I have the generic IMEI. I hope my phone wont be blacklisted.

In case someone needs my EFS I can send it.

Thanks for all the support. ;)
[Nexus S Android Development] bloodhawk:
If possible please PM it to me. And unforgiven512
[Nexus S Android Development] RisinT96:
First: that's why I said that the friend of the friend is from Google or Samsung.

second: I don't blame anyone, I said that because apreichner is a dev and all (most) the devs have some contacts who are also devs.
[Nexus S Android Development] deeren:
Back on topic:

Has anyone succeeded in restoring a modified NV_data.bin. it seems that any slight modification to the file renders it undetectable or corrupt at boot.
[Nexus S Android Development] treUse:
Seems I started some kind of flame war earlier, although it seems it's over now.

Just to clarify my standing though:

I don't blame anyone, I merely lost hope that a fix would be found without sending it to Samsung.

Sure, it was apreichner who left the script there, but anyone could have done that. And I think we all can agree when I say we appreciate his efforts, both in creating the ROM in the first place, and helping us research a fix.

Now, back onto topic!
[Nexus S Android Development] marsrogers:
I asked some Chinese Devs and searched some of their post.

So we now can change the IMEI on I5800 and 5700, of course use the HEX editor. I think his method is the same one with Mr. Qdanin from Samdroid Forum.

The Samsung has a table of the IMEI code to encrypt a part of the nv_data.bin, the IMEI part. I have the one for I5800 but found it is not adaptable for nexus s.

And the dev who I got the method from and gave me the table said he couldn't done a research cuz he doesn't have one.

I have a folder of efs untouched from my friend, yeah he is a good boy just rooted his phone and never touches custom roms~~

But I think I need another efs folder to compare the two nv_data.bin files for difference, and the different part may be the IMEI part. But I can't do this now cuz I'll be on my test weeks from the next.

Just push an idea out and hope anyone can do this for a try.

P.S I think this issue united the whole world's nexus s users together XD

like our dear Chairman Mao said:"世界人民大团结万岁"（I know you can't read these ;)）
[Nexus S Android Development] RisinT96:
But google translate can!

Now back to TOPIC!
[Nexus S Android Development] chiledog:
Not at all dude.

I did say it was not directed at you. You did not say anything to make me respond that way.

I was just saying something I hope the majority agree with.
[Nexus S Android Development] barca-x:
if we get a OTA update .. the imei back to original ????

:$
[Nexus S Android Development] marsrogers:
Come on man, it is just in the P.S part...:rolleyes:

The main part is the larger one~~
[Nexus S Android Development] RisinT96:
hehe, who is mao?
[Nexus S Android Development] marsrogers:
Our first president~;)
[Nexus S Android Development] RisinT96:
Ohhhhh, ok.

now back to topic:

Any progress in trying to fix our big problem?
[Nexus S Android Development] marsrogers:
Not yet, and must prepare for my 10 tests next three weeks~~kind of preview I say hehe...
[Nexus S Android Development] RisinT96:
yea i also have a thousand test .... waiting for the 20th of june: my last test!
[Nexus S Android Development] mythamp:
If you have ever registered at android market/use google sync, the IMEI number should be saved with your email account. That technically means, google can verify that you are actually the real owner of the phone which might give you guys a slight chance that someone at google can send a fix remotely.

Would i be correct in this assumption?
[Nexus S Android Development] RisinT96:
Hmmm, I don't know but that's interesting!
[Nexus S Android Development] treUse:
That would indeed be awesome.
[Nexus S Android Development] Zehlek:
Are you sure? I have used the same market/Google account with 3 different android phones.
[Nexus S Android Development] deejaylobo:
They must be tied to the IMEI or something because, I have done the same. And all three phones are listed in my Market Account Settings. And one of them(one which was stolen) is still listed, despite changing my Google account passwords but, has the carrier changed. My current phone's carrier changes depending on what SIM I'm emulating.
[Nexus S Android Development] nicknowsky:
Whats going on with 0.3b??? Was it really F'd up
[Nexus S Android Development] raymond4:
Yes it is messed up right now
[Nexus S Android Development] Zehlek:
Since our IMEI's are now screwed up, is it safe to use 0.3 or could it do further damage?
[Nexus S Android Development] l_sarra:
News about the problem??
[Nexus S Android Development] lvnatic:
My sold Desire is also listed on my google account in market. It even displays the guy's new carrier.

You can eventually mail google about this, you guys have the correct google account and you can provide any information they may ask, to prove that you are the real owner of that IMEI.
[Nexus S Android Development] matt2053:
I've been hearing around various places that many carriers not NOT ban default/generic/failsafe/manufacturer IMEIs in the USA but many do in Europe. Might be good news for some of you guys.....
[Nexus S Android Development] bloodhawk:
Actually a great idea. But we need the actual no. on how many people are facing the changed IMEI issue. Then we need to find someone from Google who is willing to help.
[Nexus S Android Development] deeren:
the problem is not proving that ur r the real owner of this imei.... this can be easily proven with the invoice/receipt when u bought the phone. it is written there.

the real problem is that the phone diaplays one imei and the behind the battery another one. at repairs usually they never trust what is written behind cause this is just a sticker which can be removed and replaced.
[Nexus S Android Development] apreichner:
Except that the imei is a Samsung failsafe imei and not a fake one. Google and certainly Samsung should know this. I don't know how much luck it will be. I'm sure the answer is out there though. I'm contacting mods to get warnings and information posted. Remember some people who did not flash my rom reported the same imei so there is a chance another dev could have used the scripts from sgs builds as well.
[Nexus S Android Development] barca-x:
i think this can help

if i do " phone efs clear " from odin pro .. can it help ?

see the option from this pic

:D
[Nexus S Android Development] NexusCrazy:
@apreichner

In one of my earlier post I was pissed of and said a few things I should't have.

I in know way blame you, we flash ROM's at our own risk.

I think the work you've done porting this ROM is amazing, **** happens mate and I'm sure we'll get it sorted between us all one way or another.

And don't stop with NexusSence ROM it's by far one of the nicest ROM's out there, and as soon as we get this sorted I'll be back checking this Thread twice a day again waiting for an update with 3G working e.t.c. and of course no IMEI re-writing jkin ;)))

And thanks for trying to sort this.
[Nexus S Android Development] apreichner:
To anyone who wants to fix the release so it doesn't clear the efs just delete the .sh script from inside the zip and remove the lines for it in the updater script. Then zip and resign the zip package.
[Nexus S Android Development] deeren:
no. efs clear when flashing odin is the same thing what happened to us by flashing the nexussense. it just deletes the efs folder prior to flashing.

somehow re-partitioning might help but we would need a PIT file for that.

anyway, i wonder how HTC goes around this allowing us to delete everything from stratch, repartition everything (like the n1 and desire) and still get it correct after flashing
[Nexus S Android Development] NexusCrazy:
I've read somewhere that this works, it pulled someone else out with similar issues on a different phone.

Just don't no Odin at all and havnt had the balls to try it. What I read was about the 512.pit file and re-partition, apparently it rebuilds the partitions and I presume the IMEI as well.

I've searched for .pit file for Nexus S but can't find anything anywhare and I'm not even sure if the.pit file is phone specific.

In the article I read, it didn't mention clear efs, - although I can obviously see the relevance.

But this might be the answer
[Nexus S Android Development] deeren:
just a foolish and stupid thought,

has anybody tried going stock and performing fastboot oem lock and fastboot oem unlock and see ?
[Nexus S Android Development] treUse:
Yes, that has been tried, without success though.
[Nexus S Android Development] apreichner:
I might be wrong but I don't think HTC uses an efs partition to store important data such as the imei. If I were designing a phone it would be a separate chip altogether. Less chance of someone tampering with it and less chance of someone screwing it up. And Samsung should have designed the efs to self restore itself in the event of tampering so it becomes harder for someone with malclicious intent to steal the phone. Instead they decided that if you tamper with efs you should be gifted with a new imei that works on a lot of carriers. Just my two cents.
[Nexus S Android Development] bloodhawk:
Yeap, i think the last shot at the PIT files should work.

It has helped people with the Galaxy S.

Though this failsafe IMEI does create a lot of security concerns for a country . If someone with malicious intent wanted to exploit this, they could just purchase a Nexus S and delete the EFS partion, then go ahead and do whatever they wished to do with it. Now since the IMEI is failsafe, it is just not traceable anymore.
[Nexus S Android Development] NexusCrazy:
So where can we get the .pit file from for the Nexus S
[Nexus S Android Development] Zehlek:
Do you know where I can get this ODIN? Also what files will I need in my PC and where?
[Nexus S Android Development] NexusCrazy:
We need the correct .pit file first, then one of us needs to test it. But to be honest I've searched everywhere for the .pit file and not found one

I've seen 512.pit 513.pit and 803 (I think) .pit file but I think the files are different for all devices, correct me if I'm wrong.

I'm all set up with odin3, European GRH78 l just need the .pit to test
[Nexus S Android Development] Zehlek:
I wish I knew more about this stuff lol
[Nexus S Android Development] j_r0dd:
go to http://www.samfirmware.com/
[Nexus S Android Development] RisinT96:
I read somewhere (http://xdaforums.com/showthread.php?t=771426) that the pit determines the size of the partition, so maybe we can use the 512.pit (maybe its not unique for every device)
[Nexus S Android Development] dima_sk8er:
Fixed ZIP

To all who want to try NexusSense 0.3 without bricking device, I've fixed update-script in ZIP and put it to my dropbox.

Here is link for download: http://dl.dropbox.com/u/10434059/NexusSense_0.3_fixed_unsigned.zip
[Nexus S Android Development] brashmadcap:
Um, probably should tell us what you did and demonstrate before you post something like this
[Nexus S Android Development] dima_sk8er:
I've delete efsrestore.sh from ZIP and these lines from update-script:

package_extract_dir("recovery", "/system");

# 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

unmount("/sdcard");
unmount("/efs");

It works fine - IMEI doesn't corrupt.

Do I need to post a screenshot with IMEI? :D

Download link: http://dl.dropbox.com/u/10434059/NexusSense_0.3_fixed_unsigned.zip
[Nexus S Android Development] deeren:
Yes. That's the problem. We know nothing abt it. The galaxy s using rfs, I dont think it is a good idea to use it
[Nexus S Android Development] deeren:
Double post.sorry
[Nexus S Android Development] deeren:
We believe you.don't worry.
[Nexus S Android Development] chris6278:
I wanna try this so bad but im scared! Lol dont wanna f up my imei
[Nexus S Android Development] SilverEagle:
well if the zip doesnt contain the script no more...
[Nexus S Android Development] dima_sk8er:
If you no messed up imei, you can flash zip with fixed update-script ;) It works and imei does not corrupted. I've tested this.
[Nexus S Android Development] chris6278:
Im gonna download it but wait for a few more ppl to try it an say its ok before i do it. Not that i dont believe u but i just wanna be sure
[Nexus S Android Development] Trinitronik:
**** you damn *******! Just copy /efs folder with all your IMEI and MAC info, and you're free 2 go!

http://xdaforums.com/showthread.php?t=1098191
[Nexus S Android Development] dario3040:
THIS

...................................................
[Nexus S Android Development] dario3040:
And you do something awesome again :)

Thanks =)
[Nexus S Android Development] pnnorth:
Flashed ok without any change to my imei number. I'm using the I9020 gsm NS.
[Nexus S Android Development] NexusCrazy:
Does anyone know if a .pit exists for the Nexus S and if you do can you please point me in the right direction to a download link.

Thanks
[Nexus S Android Development] dario3040:
Just remember to do a backup if you haven't already.

the path is /sdcard/efs
[Nexus S Android Development] pnnorth:
Such is the paranoia about knackering my phone, I've got a backup on my phone, pc and dropbox now.
[Nexus S Android Development] dario3040:
Btw, does anyone know which kernels work on this ROM?

All of them freeze at boot -_-
[Nexus S Android Development] chris6278:
This is gonna sound stupid but how do u backup efs?
[Nexus S Android Development] matt2053:
1. Plug phone into computer

2. Find efs folder

3. Right click it and choose copy

4. Go to c:\ drive on computer

5. Find folder where you want to store backup

6. Paste
[Nexus S Android Development] dima_sk8er:
On 0.2 I using Netarchy Nexus 1.3.1& It works fine. But remember doing "wipe cache" & "wipe dalvik-cache" before flashing kernel ;)

With "Root Explorer" (or something like that). Just copy /efs partition to your sdcard or PC.
[Nexus S Android Development] dario3040:
Thanks :3

I'll try that.
[Nexus S Android Development] Zehlek:
My IMEI is already messed, so no harm in flashing :p
[Nexus S Android Development] NexusCrazy:
It doesn't matter to you if you flash the bad version or the fixed one. You already f'ed your IMEI no up when you flashed the bad version.

**************************************************

@apreichner

We (us who got messed up IMEI numbers) need a dedicated Thread now that someone kindly fixed the ROM cos we now got 2 topics going on in 1 thread.

Those looking for a fix to un-brick there phones

Those who are chuffed that they've got NexusSense v03 up and running (without messing up there IMEI numbers) and there obviously going to wan't to talk about how nice the ROM is e.t.c. .
[Nexus S Android Development] nitsuajd:
For those who do not want to wait a fix... (that's probably don't arrive...)

has anyone talked to Samsung for repair even out of warranty?
[Nexus S Android Development] Graham19:
Are /eds and a nandroid backup all I need to make sure I can recover?

Roor explorer shows other directories and files not backed up by nandroid, should I back them up as well?
[Nexus S Android Development] dima_sk8er:
Yes.

You don't need to backup other derectories.
[Nexus S Android Development] deeren:
does anyone have a link to the pre-released gingerbread leaks. i mean the unreleased ( very first ) buillds. GRH 35 in particular. i found it once but i do not know where.
[Nexus S Android Development] Zehlek:
Is this it?

http://www.mediafire.com/?kwk5oi05uyh0a8l
[Nexus S Android Development] deeren:
no. that's only the radio.
[Nexus S Android Development] Zehlek:
Sorry
[Nexus S Android Development] emc1990:
I've lost my IMEI...

How can I restore it please ?
[Nexus S Android Development] deeren:
no problem. i found it but nothing boots with the leak. i guess we are back to square one.
[Nexus S Android Development] Zehlek:
Presently the only way is to send into Samsung. Devs are looking into it
[Nexus S Android Development] treUse:
Please taken 5 minutes of your life and read a couple of pages in this thread; There is no current way to restore your IMEI without sending it to Samsung.
[Nexus S Android Development] slimjimwoods:
Its a shame 3g doesn't work on 0.3, its brilliant otherwise...
[Nexus S Android Development] Valantin:
If you reset the terminal and took it to a samsung service center can use the warranty? obviously saying that updating (officially) the terminal I was damaged the imei software?

is possible in this way a free repair?

I have the nexus of a few days :(

Sorry for my bad eng
[Nexus S Android Development] marsrogers:
Trust me, the day is approaching. I can edit the nv_data.bin on I5700 and 5800 now. One day when I9000 is a victim, nexus s is close then.
[Nexus S Android Development] deeren:
no actually the updates do not touch the efs folder at all. i talked to a samsung representative today, and i tried this thing about updates.... he said that they actually know about the efs folder and its consequences. apparently lots of users from i9000 have been messing their nv_data.bin trying to unlock their device. i don't think they will actually buy this update thing.
[Nexus S Android Development] Valantin:
Afford a recovery of imei for free to anyone? or as a member of samfirmware in payment?

If Free you are my hero
[Nexus S Android Development] bloodhawk:
Im even ready to pay for it! :D
[Nexus S Android Development] nitsuajd:
Maybe this tool can help restoring efs

http://www.youtube.com/watch?v=Ecp8jKmm48k

But yes, it's hard to use and do lose your warranty, but for people like me that have not warranty, could work
[Nexus S Android Development] apreichner:
Absolutely.
[Nexus S Android Development] Zehlek:
Sweet. I can't wait
[Nexus S Android Development] dario3040:
Well, HTC made a nice UI and some nice apps that people obviously want.

That and variety
[Nexus S Android Development] rubino90:
It's existing possibilty for next release work signal radio and wifi?

Sent from my Zeroxv3 Nexus S XDA Premium App
[Nexus S Android Development] dario3040:
Yes, of course.

But HW3D has a higher priority i guess
[Nexus S Android Development] owlmatt:
Can't wait for this. Thanks for your hard work. Obviously it's not for everyone but many people love sense and would love to see it on the great Nexus S. I am one of them.

I'm sure somewhere in the world some people even love motoblur ( I am not one of them) and we should never discourage people from having options of various roms even if we don't personally care for them.
[Nexus S Android Development] xanos01:
True I'm with you.
[Nexus S Android Development] Zehlek:
I agree totally. I myself love sense and thank you @apreichner for all the hard work and to everyone helping
[Nexus S Android Development] BraydenJames:
Watch this other thread...

http:// xdaforums.com /showthread.php?t= 1033571&page=5

(remove spaces..)
[Nexus S Android Development] apreichner:
The way the filesystem is on the Nexus S is different than the Galaxy S ports. If it was the same, I could probably just quickly get a rom going, but unfortunately some of the drivers are in different folders inside a Vendor folder. Wifi and HW3D drivers are two examples. In my first port, that folder does not exist, which is why everything is broken, but when I added the folder I ran into troubles booting the rom.
[Nexus S Android Development] dario3040:
Mmm, doesn't sound too good.

Hope it works out though
[Nexus S Android Development] apreichner:
UPDATE

Pretty certain I fixed HW3D. Live wallpapers work great and the home screen is smooth and fast. Already faster than my girlfriend's incredible. Moving right along!
[Nexus S Android Development] Zehlek:
Awesome wtg!!! Thanks for the update I can't wait :-D
[Nexus S Android Development] Amritttt:
amaziing new bro :D
[Nexus S Android Development] bigmizz79:
Hands up jumping for joy..lol ..can't wait..!!!
[Nexus S Android Development] apreichner:
Update 2

It now connects to the T-Mobile network, looks like its voice and SMS only atm. When I try to go into network settings, it drops the network and throws a repeating force close, reboot doesn't seem to fix. But I thought I would post this because it is an update.
[Nexus S Android Development] Amritttt:
nice nice i waiting ill keep eye on this forum i hope from now onwards:D
[Nexus S Android Development] Jrbourque:
Awesome ...can't wait for this ...which sense are you porting?
[Nexus S Android Development] bigmizz79:
When do u think we will get another rom to test

.??
[Nexus S Android Development] ytt3r:
This sounds like a really easy port (back) to SGS. This just uses the stock kernel or any other kernel in here, I'm assuming because I haven't read otherwise.
[Nexus S Android Development] dario3040:
Nope.

IMPOSSIBLE
[Nexus S Android Development] Valantin:
yes but 20$ is a bit much for a few minutes of work per person

sorry for my bad eng