yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] murdoch1:
Cheers bloodhawk. Has there been any confirmation restoring efs backup actually resolves the inside problem?
[Nexus S Android Development] leejeans:
no,restoring the efs backup change nothing~good is still good ,wrong is still wrong~the same imei
[Nexus S Android Development] deeren:
What do you mean inside problem?

Yeah , if you have an efs backup done, restoring it would solve the problem.
[Nexus S Android Development] murdoch1:
Sorry I typed IMEI number on the phone but the word was replaced by inside....LOL... how i love my nexus s.....:D
[Nexus S Android Development] bloodhawk:
Yeap if you manage to mess it up...just restore using the original backup! :D
[Nexus S Android Development] deeren:
yes if you have a good back up you can always restore the good imei. there are many ways.

here is a proof. the 1st pic is a successful restore from a bin file(done some days ago) and the 2nd is a successful restore done using only the bak files.(yesterday)
[Nexus S Android Development] NexusCrazy:
Just had a bit of good luck too mate, see pic:

Buzzin, at least those who have a warranty should get there's repaired/replaced.

:D:D:D:D:D
[Nexus S Android Development] NexusCrazy:
Can clockwork recovery not be modified to have this feature built in.
[Nexus S Android Development] thegod2012:
.4

will there be a update to this bad boy
[Nexus S Android Development] NexusCrazy:
Not sure as to what u want updating on, or from who, but:

1] I'll b posting back when I get my Nexus S back in my hands. It just offers some hope to those who have waited patiently for a fix on here, in case a fix isn't possible. After all the Nexus S is nowhere near 12 months old, so unless you bought it second hand it will be covered by your warranty, I'm not sure about second hand phones but I would imagine you can send it of to Samsung anyway.

2] I personally think it would be a nice feature. To be able to back up your efs in Clockwork recovery or even in ROM Manager if possible but I'm no Dev so I can't help with that unfortunately.
[Nexus S Android Development] murdoch1:
Hi Nexus Crazy........good news re your Nexus too buddy. ;);). It took them about 5-7 days from repair completed for a phone to be back in my hands. I think we may be quite lucky as technically CPW state in their repair blurb that if the IMEI number is different they will not honour a repair. Luckily for me when I took the "damaged" phone into CPW they scanned the IMEI number from the battery compartment and not directly from the phone via the normal command, i.e *#06#.

I have backed up my EFS folder and have this on 3 storage methods, 2 x computers and 1 x flash pen (aint taking no chances LOL).

Also very tempted to try the fixed Sense 3 zip when I get chance to re-root.

Let me know how you get on buddy.
[Nexus S Android Development] dario3040:
Yes it can :P

But nobody have requested it yet. (I think)
[Nexus S Android Development] NexusCrazy:
Good to here youve got your's back, well a new one :)

I'll also be backing my efs up as soon as mines back in my hand, Can't wait to "fastboot oem unlock" and then get Root, it's an addiction and of course it makes the phone so much more fun and usable. I am missing my custom ROM's and will flash the fixed NexusSence 0.3 too.

I really do hope that apreichner keeps on building/updating NexusSense, it could/will end up being one of the nicest ROM's for the Nexus S if he does.
[Nexus S Android Development] NexusCrazy:
Where and who would I request it too?

Thanks
[Nexus S Android Development] bloodhawk:
Koush aka Koushik Dutta @Clockworkwod :P
[Nexus S Android Development] Amritttt:
y dont any of u cyanogenmod team or cyanogen for sure they must be knowing something about this issue?
[Nexus S Android Development] Zehlek:
Has anyone with a good imei tried the fixed version?
[Nexus S Android Development] chris6278:
Im running the fixed version as we speak. No issues at all an still have MY

imei
[Nexus S Android Development] brmayhem:
I'm glad that some of you guys have been getting your phones "fixed" lately. However I see you're sending it to CPW.

Has anyone who purchased it through Best Buy sent it back to them, or Samsung, or even T-Mobile? If so, what did you state exactly? I'm guessing you didn't say that after unlocking the bootloader and flashing a ROM your IMEI was demaged... TIA.
[Nexus S Android Development] Zehlek:
It's weird. I have a correct imei and yet with fixed sense, I can download apps. I select to download and it says starting download and then disappears
[Nexus S Android Development] marsrogers:
After my exam weeks, I will start digging this issue up from the very begging. From the dgs partition data for there is a "test" inside. There are certain countries like mine, China, don't have this phone sold, so the only way we can do is try fixing this on our own. A real fix. That's we say "宅男拯救世界～"(Try Google translate this, I don't know how to explain in English.)
[Nexus S Android Development] mr_recordman:
Cool!!! I hope you will dig up deep enough to find the solution!

I notice since mi IMEI is gone I have to try at least 4 or 5 times to download any aplication from the Market. Sometimes it works at the first attempt, sometimes even after 7 or 8 times. It does not matter what ROM I'm using.
[Nexus S Android Development] SoleOfJohn:
Fixed version?!

What fixed version? I would love to check it out.
[Nexus S Android Development] deeren:
according to recent changes, market should not be affected by the imei ( from what i understood). indifferent of the imei, you are given an android_id when logging into market.

try clearing market cache. this may be the cause.
[Nexus S Android Development] RisinT96:
I flashed the rom and I don't have any market problems, I don't know what's the problem with yours.
[Nexus S Android Development] Zehlek:
Thanks I'll try it
[Nexus S Android Development] dima_sk8er:
Here it is: http://dl.dropbox.com/u/10434059/NexusSense_0.3_fixed_unsigned.zip
[Nexus S Android Development] raymond4:
Will this work on the ns4g
[Nexus S Android Development] dima_sk8er:
At this version (0.3) - no. Maybe should work on next releases.
[Nexus S Android Development] Zehlek:
It worked, thanks.
[Nexus S Android Development] Zehlek:
Hopefully apreichner will release an update
[Nexus S Android Development] thekenny:
this rom is sooo cool please dont stop working on it :D
[Nexus S Android Development] Zehlek:
I love this Rom.
[Nexus S Android Development] NexusCrazy:
Just got my Nexus back from cpw, fixed not replaced and Samsung sent it back with the bootloader unlocked :D

And I've got my own IMEI back :D

Just need NexusSence v04 to be released now :D

Just going to back up my efs as well as doing a Nandroid, Just got to get Root first, but that wont take lonk
[Nexus S Android Development] Zehlek:
I'm glad you got it fixed. I do hope apreichner hasn't given up on this rom
[Nexus S Android Development] murdoch1:
Fantastic news buddy. :D:D:D:D Happy days again.....

I have installed SuperAOSP on mine, will defo try NexusSence 0.4 if it's released. Bring it on.
[Nexus S Android Development] NexusCrazy:
Rooted and My baby is back to how she was :D

Thanks Zehlek and I too hope apreichner keeps working on the ROM its amazing, I'm even going to flash the fixed version of NexusSense v03

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

Thanks mate, feels like Chritmas day did when I was a kid :D Just flashed Cyanogen 7, will mess about with different ROM's tonight.

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

@apreichner please keep up the excelent work mate, it really is a fantastic ROM.

NexusCrazy

aka Marc
[Nexus S Android Development] fabrizioo2007:
Just because you have solved your problem does not mean that now all of us with the

imei changed we no longer need to find a fix ...

Now apreichner is working to fix(I hope) imei problem before and only later he 'll can begin to think about continue development...

Would be very useful to know how did they (cpw) solved the the problem!!

Is there anyone who took it to a Samsung service center or that has solved the problem without cpw assistence??
[Nexus S Android Development] Byte_76:
I too would like to know how CPW fixed the phone because I had mine imported from the US in January and I don't have a service center nearby where I can send mine for repair so I have to rely on a fix from here.

Unfortunately my knowledge of linux, efs and specifically nv_data.bin files is very limited and I've had no luck with anything I've tried so far.

Is anybody still working on a solution?

I tried about 4 different roms last night and they are all so boring. I much prefer this sense ROM and still really hope that Apreichner continues developing it because its a great rom but still just a bit too incomplete to work as a permanent rom at this stage.
[Nexus S Android Development] Zehlek:
I agree they mostly are. I just use another because of data and camera
[Nexus S Android Development] dario3040:
Sounds like you demand a fix...
[Nexus S Android Development] marsrogers:
Still working...but even me myself don't have that much hope. I'm wondering why suddenly there seems nobody have this problem anymore or just because the victims were not that many at first as we thought? Maybe one day I can figure this out but I am not sure whether this is worthwhile for IMEI affects nothing actually here in China. Feels like being abandoned......
[Nexus S Android Development] Zehlek:
Sure the imei change was bad and I too was one that suffered from it, I was just lucky that someone still wanted to trade phones with me. I never did get upset with apreichner because as he posted, he isn't responsible and I made the choice to flash it. So it was myself at fault not him and I hope he still will be working on this awesome rom :-)
[Nexus S Android Development] dario3040:
It wasn't his fault anyway.

As far as I understand, some people on the GalaxySense team managed to **** something up.

And Apreichner used that code to build it.
[Nexus S Android Development] deeren:
well those from the galaxysense didnt do any mistake. its just the way they cook their roms and thats the way samsung makes them. Recoveries exist since months that back up efs folder, there were even applications on the market doing this.Their script was - backup the efs, install the rom and restore the efs. ( didnt work on ours as we do not have an sdcard )

What is regretful is that nobody coming from the vibrant,captivate or whatever.... didnt recommend us that. ( there should be many from what i have read since the beginning coming from the galaxy lines. Even devs like bionic, master , supercurio who had samsung devices never warned us in their threads abt this partition). just to give u guys an idea how things are going , till now i have not seen any dev mentioning or warning users abt it. i made a thread abt the backing of the folder and requested it to be sticky but pfffftttttt.

In 2-3 months' time, when things will get calmed down, you'll probably see other cases.
[Nexus S Android Development] Zehlek:
I agree it wasn't his fault. I just hope he will continue with NexusSense
[Nexus S Android Development] dario3040:
Yea, but I don't see any reason for them to warn you.

It's a completely different device.
[Nexus S Android Development] Borky_16:
the problem is that when you flash aosp/cm based roms that wouldn't happen to you! and ghe thing with backup & restore efs is only for NON touchwizz roms, so do not blame on OP he can't know that!
[Nexus S Android Development] deeren:
Calm down dude.lol. no rant here.nobody is blaming the op.we are just discussing that till now, there is nothing being done to warn future users.
[Nexus S Android Development] barca-x:
i think no new news about the IMEI :D

rly i hate that rom :D
[Nexus S Android Development] Zehlek:
Does anyone know of the best way to save battery on NexusSense
[Nexus S Android Development] bloodhawk:
SDo any updates on any developer sides?

Personally i dont think there is any other way out than to get the phone/motherboard replaced.
[Nexus S Android Development] itztuna:
will this port be available for sprints version of the nexus 4g?
[Nexus S Android Development] Zehlek:
0.4 might but the current version isn't.
[Nexus S Android Development] NexusCrazy:
As far as I'm aware there's 2 of us on here who returned are Nexus's back to CarPhoneWharehouse (cpw) the other member (sorry for forgetting your name mate) had his Nexus S replaced with a new one, on the other hand Mine was repaired.

As far as I'm aware we both flashed back to stock and locked the bootloader:

fastoot devices :D

fastboot oem lock​

I certainly did.

I got mine back repaired and the funny thing is they sent it back with the bootloader un-locked :confused:

So unless they replaced the board in mine there would apepr to be a software fix. Unfortunately this is in the hands of the cpw service center.

So its a case of knowing someone who works for either cpw or Samsung and who's prepaired to leak us a copy. Only thing is the software will probably be capable of doing a lot more than restoring the original IMEI numberand were likely to never see it

The good thing out of this is if there is software to repair this then hopefully they'll be a Dev on here who can replicate it.

I to want everyone's IMEI issues to be resolved.
[Nexus S Android Development] itztuna:
any word on release date.. i cant deal with gingerbread.. lol
[Nexus S Android Development] bloodhawk:
Well so all hope is lost for me. Nothing works in getting the IMEI fixed. Anybody wanna purchase my handset for a decent price? Obviously if the borked up IMEI still works in your country. Have the Box, Earphones and USB cable (Both brand New) , Charger used 3-4 times. :(
[Nexus S Android Development] Riyanweb:
Wow that's just wrong.
[Nexus S Android Development] brmayhem:
@NexusCrazy

Were you "blacklisted"? The reason I ask is because I see that you sent your phone in for "No signal/service"

My IMEI was corrupted as well but the phone still works. However, being able to fix the issue seems better than just living with it. I'd like to send it back to Samsung but with the phone still working they will probably just return it to me.
[Nexus S Android Development] bloodhawk:
Just out of curiosity, how many users are having non working phones because of the Generic IMEI issue?

As in in how many countries is the IMEI banned?

Because in most countries its still functional and doesn't look like it is going to be banned.

So far, the generic IMEI seems not to be working in - India and Spain.
[Nexus S Android Development] bigmizz79:
I'm in America and had no problems as of yet..crossing fingers..lol
[Nexus S Android Development] Zehlek:
I'm in Canada and I never had any issues when I had my NS with corrupt imei
[Nexus S Android Development] sweety1:
I'm from Austria with corrupted IMEI and had no probs.
[Nexus S Android Development] ilnanny:
Awesome work.i love it.
[Nexus S Android Development] bloodhawk:
wow amazing. Your respective carriers are amazing. In this **** country of mine. I cant even use my phone. Gotta sell it! :(
[Nexus S Android Development] mr_recordman:
Sorry for that mate.

In Czech Republic there is no problem at all with IMEI, i hope.
[Nexus S Android Development] RisinT96:
No prob in Israel.
[Nexus S Android Development] bloodhawk:
Yea, lets see if a fix ccomes out soon. Which i think is highly unlikely. IF it doesn't. Im dooomed as it is.
[Nexus S Android Development] deeren:
Why exactly does it display? Have you tried selecting the network manually? Could you try deleting everything from the eds folder except nvdata.bin and nvdata.bak files and wait 10 sec and remove battery. Power on and see.

I know that carriers can block imei but this is the oem Samsung factory imei...why would they do that.
[Nexus S Android Development] RisinT96:
its not the samsung factory imei, some people with iphone had same imei after jailbreaking it and doin something
[Nexus S Android Development] bloodhawk:
Well it depends on the carriers. In a place like India where forgery and using the phone for illegal purposes , raises serious security concerns. Specially when you can just grab a working prepaid SIM card off of the streets with out any hassles.

But in other, way advanced countries, these IMEI's , I assume, play a very minor role, since the security measures (National and otherwise) are pretty stringent.
[Nexus S Android Development] Gonizahavy:
hey there

Im trying to solve it from a different angle now.. since the nv_data.bin is encrypted and hard to crack Im trying to edit the framework.jar in order to get it to return pre-defined original imei number before it is getting it from the baseband interface

so far I managed to change this method:

TelephonyManager manager = (TelephonyManager)getSystemService(TELEPHONY_SERVICE);
String imei = manager.getDeviceId();

to return my pre-defined original imei string and it works for all the market applications that use this type of imei retrival, but it is not the only way to access the imei since the settings app still gives me the wrong imei..

while digging a bit more i found out that there is a "iphonesubinfo" service that get that info from another place.. so i'll try to find and change it too.

my only concern is the the network provider identify our phone directly through the baseband and any of these changes will not apply on their end, and only on the application level
[Nexus S Android Development] bloodhawk:
^ nice work man! :D

But unless the IMEI can be fixed from the Radio/Baseband side. The phone wont work for a few of us here :(

And the answer most probably lies with either Google or Samsung. And with getting the Original/Decrypted nv_data.bin files.
[Nexus S Android Development] marsrogers:
I think only the riff box can do this...I will try find one somewhere or buy one from the internet in summer holiday...Such things are easy to get in China...but that must be the last hit...
[Nexus S Android Development] bloodhawk:
Nope the RIFF box method is also not working. I already sent to someone with one and even after flashing each and every partition, it didn't help.
[Nexus S Android Development] NexusCrazy:
Good luck mate, I did the same with mine; reverted it back to stock, locked the bootloader and played ignorant as to how or what was wrong, only that I couldn't make or recieve calls/SMS or recieve any data. I dealt with cpw though (CarPhoneWarehouse a knid of middle man/shop) and I know of at least one more member on here that has done the same with cpw and we got our phones back either repleced or fixed, (they fixed mine and sent it back with the bootloader unlocked :confused:

Yours is more of a test case though than ours, as youv'e sent yours straight back to the manufacturers. Cutting out the middle man?shop. e.g CarPhoneWarehouse Best Buy Orange etc.. (I'm pretty sure they'll repair it for you), So please keep us all up to date has how you get on.

At least then it means everyone should be able to send there Nexus's off to Samsung under Warranty,

as the phone isn't 12 months old yet so by default is covered by Samsungs warranty

.

Out of curiosity what circamstances are there where you coudn't/wouldn't send your Nexus straight back to Samsung????
[Nexus S Android Development] NexusCrazy:
Yeah No Service, No data, no nothing, Ther's another member on here who sent his Nexus back to Samsung, I think he was the same as me though with No Service.

Ive just posted, Asking him to keep us updated, at least we'll know if Samsung will repair it under warranty. If they do I'd phone them. I'm not telling you to lie, but be a bit loose with the truth ;)
[Nexus S Android Development] dopeypopey123:
just thought i would let all you guys know i sent mine straight back to samsung and just recieved it back yesterday working all fixed and perfect and the way i went around it is i did a fast boot system delete and then locked the bootloader and played dumb and said i did the 2.3.4 update and then it wouldnt turn on ;) ahaaaaaa
[Nexus S Android Development] Zehlek:
I'm hoping for a data and camera fix soon :-)
[Nexus S Android Development] bloodhawk:
Whoa which country are you from? Can you please let us in on the minor details?

Also did you have to provide the invoice or proof of purchase or something?
[Nexus S Android Development] Zehlek:
Has anyone heard from apreichner of any updates?
[Nexus S Android Development] nicknowsky:
yeah i was gonna say this thread gets a lot of action for ROM thats not even available
[Nexus S Android Development] Byte_76:
Has anyone tried http://www.samfirmware.com/WEBPROTECT-i9020.htm

They have one firmware on their site for European version NS.

The flashing application is Odin 1.8 and there is a detailed document that describes how to download the firmware to your NS.

My NS was imported from the US so I don't know if I can flash the European version however we do use the same bands as Europe so maybe it will work.

The site says type *#1234# on your phone to get the firmware region code but when I type that my phone shows "Connection problem or invalid MMI code"

Where else can I get the region code from?

How would new firmware know what the correct IMEI and product codes are?
[Nexus S Android Development] bloodhawk:
^ The files being provided by them are not sufficient. They are enough to go back to stock. But not for fixing our issue.
[Nexus S Android Development] apreichner:
Update:

I have been watching this thread every day now and I have been keeping up with the leads. Unfortunately, I still have come up with nothing as the nv data bins appear to be encrypted. I have also followed up on some leads about tricking the framework into believing it is a different IMEI number, but I don't know if that will be sent back to the carrier. My phone (and many others) I believe are still operating normally and I do not know of any North American carriers that have yet blacklisted the IMEIs, and I do not expect them to if they haven't already.

For the ones who have been blacklisted, it appears there is still some hope in sending it back to Samsung or other warranty services. I have read of 3 reports so far that they were able to get the phone repaired.

Another thing I wanted to talk about is exactly what happened. I noticed some users blamed TeamGalaxySense for making a mistake and others mentioned that it wasn't backing up because the lack of SD card. These claims aren't accurate. The other Galaxy S phones were originally formatted with a slower RFS filesystem. Therefore when it came to install better and faster ROMS, such as Cyanogenmod, they needed to turn this ext4. Backing up and restoring the EFS was a necessary part of this transition. What I didn't know is that the EFS Restore script did not do this, Cyanogenmod on the SGS had a seperate script for this, while the restore script just restored it. Cyanogenmod on the NS didn't do this because the filesystem was already formatted correctly. I'm not aware of all of the hairy details of why it was necessary because I came from an HTC device before this one. I still recommend that EVERYONE backup their EFS anyways because there is so much that could potentially go wrong when you have sensitive information stored on a partition of the storage.

Will I continue work on this rom? That has been a question I have been hearing from many of you. The answer is, possibly. It really depends on you. I have read the posts and heard the support from many of you, even the ones whos IMEIs are now messed up, and I am thankful I belong to such a good community. I do keep an eye on the SGS thread to see if there is any update on data or camera, but it appears they are working on porting the ROM to some of the many other Galaxy S devices. I will very likely release a 0.4 update without the EFS script and probably some other minor changes. If anyone thinks they can help in getting the data connection or any other missing features working, shoot me a PM.

Thank you. If you have any further questions, I will try to answer them in a timely manner.
[Nexus S Android Development] Zehlek:
Awesome. Thanks for your update. I hope to see updates to your awesome Rom.