yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] oluwaponmile:
Does flashing a stock rom replaces the efs folder?

---------- Post added at 12:47 PM ---------- Previous post was at 12:26 PM ----------

Here is what I have done:

1. Phone came originally with 3 network.

2. Used voodoo to originally unlocked the phone

3. Installed Omega v11 (phone became locked) Unlocked again with voodoo and Sam fix.

4. Upgrade to Omega to v13 - phone still unlocked.

5. Backed up efs folder to install your fix.

6. Copy files from your fix to /efs

7. Flashed Omega v14

8. Phone locked and does not request unlock code.

9. Flashed stock rom BLG8 - phone unlocked to Orange network without any fix.

10. root ur device + back up efs

11. app voodoo + mike's ril

12. copy my 2 files of into ur efs

13. flash jb rom

14. tell me the result

Why do I need to use the voodoo + mike's ril (in step 11) when phone is not locked to any network using the BLG8 stock rom (see step 9)?
[Galaxy S III Android Development] tux821:
Thanx for figuring out this unlock trick.

:thumbup:

I have been in some stress for a quite a few days (and nights) when, after using CM9 for some time flashed CM10, and instantly got network locked on a phone which was already unlocked and worked fine with CM9. :eek:

Then even more stressed finding a solution, saw the voodoo threat, learned about this efs folder/partition.

That's the positive side of messing something up, you start reading the posts you should have read like:

*** BACKUP YOUR EFS ***

BEFORE FLASHING CUSTOM ROMS AND/OR START MESSING WITH UNLOCK HACKS!!

Look in the apps store for the hc-ktool

Seems to to a decent job.

I got it fixed by ordering all unlock codes at an unlockers webshop. I could unlock by entering the network unlock code.

I hope this and the efs backup will help me in case of future lockups..

What I want to know from you developer elite on that efs part is some info what is happening here??

I do not need to know what your crack is doing. I only want to understand what happened to me and others having this network lock issues.

Is this some funky Samsung code in some initial firmware bootloader part and/or ril which checks if someone has flashed the phone a few times and then changes something in the efs?

What is it and how does this work globally?

Sent from my totally unlocked GT-I9300
[Galaxy S III Android Development] jamie2002uk:
Same as me got my phone sent to me unlocked on three in the uk flashed criskelo rom v5 no problems still unlocked went to upgrade to v6 and bam network lock on wtf... so reverted back to a backup of stock lf6 still there which was expected just used voodoo and unlocked at the moment i tried to flash v6 again but network lock returns.

I have a backup of my efs folder which i dont really want restore yet as everything is working but i know soon as i upgrade network lock will be back the only thing i didnt downgrade was my modem i was on lg8 gone back to lfb today so may try an upgrade see if it anything modem related

Which files should i restore from my efs backup the same as the OPs?

Thanks in advance
[Galaxy S III Android Development] recond9:
I cant find the efs folder..can someone say where he's located? Thanks:D

Sent from my GT-I9300
[Galaxy S III Android Development] jamie2002uk:
Use root explorer
[Galaxy S III Android Development] tux821:
I did not have restored my efs but used unlock codes.

The efs backup is only if all else fails for me or something totally bizar happens like a different or lost imei number.

I understand efs contains important id/security stuff so if I ever should try this I guess it's best to restore all of it like the hc-ktool seems to do.

Anyone did a full efs restore yet?

I am now on CM9 don't know what will happen if i flash CM10 again, due to this network lock experience I m holding off till I basically understand what's happening here.

So again, what is happening here?

What does this Samsung code basically do and why?
[Galaxy S III Android Development] jamie2002uk:
Why the unlock code? ive not tryed another sim apart from my 3 sim i just type *#7465625# but i do agree as everthing is working restoring the efs is my last option and im not flashing anything just yet
[Galaxy S III Android Development] tux821:
I am a bit new on also flashing my phones, altough i already did flash most of my hardware ;)

Paying for unlock codes looked a save option to try and it worked for me.

I now have all unlock codes for this phone (network, provider, subprovider, defreese).

I agree with you that I did not want to pay for an unlock solution because I did buy this phone unlocked in the first place.

But entering an unlock number before trying the other stuff looked more save to me.

Actually I first tried a tip posted pretty fast on XDA when I posted my problem.

I did try a Galaxy unlock app but did not work.. I now understand a bit why by looking into the /efs/nv.log

which had some lines with cracking detected ..
[Galaxy S III Android Development] recond9:
I used lots of explorers,but they all give 0 results for "esf"....

Sent from my GT-I9300
[Galaxy S III Android Development] jamie2002uk:
I didnt even think to check nv.log just have an yes same as u cracking detected i may just use efs pro and restore my efs folder
[Galaxy S III Android Development] tux821:
To see the efs folder/partition:

1)You must be rooted

2) Use Root Explorer app

---------- Post added at 11:50 PM ---------- Previous post was at 11:44 PM ----------

If your rom / ril / modem combi works I would not restore your efs, see my post before.

Just wait until some xda efs specialist at least can explain a bit what is happening here in stead of posting the next fix/workaround to unlock.

Why do already unbranded/unlocked SGS3 i9300 phones get this network lock, what is happening here?
[Galaxy S III Android Development] machu28:
before (since lbg6) when i typing the code *#7465625# (View Phone Lock Status) i got nothing but now after using this hack it works :D
[Galaxy S III Android Development] tux821:
Wow.. if I enter this *#7465625# i got:

'Connection problem or invalid mmi-code'

My phone works perfectly btw with CM9..
[Galaxy S III Android Development] machu28:
if u want more explication on efs process just google it.

---------- Post added at 11:11 PM ---------- Previous post was at 11:09 PM ----------

this code and other codes doens't work on cm9. it work only on samm pda
[Galaxy S III Android Development] muhamet:
*#7465625# locked phone see the picture whit flashed jelly bean
[Galaxy S III Android Development] zohawkish:
How did this happen ?

( you should say hi zohawkish):)
[Galaxy S III Android Development] zohawkish:
only voodoo is ok.

yes u have right

Efs is just an"encrypted file system" used to protect files and signatures. You got ur device locked because Cm10 is based on jb.
[Galaxy S III Android Development] rafaelfessel:
Im really lost here...

Im planning to buy the s3... now i have the galaxy nexus...

My problem is that phone is only sold locked to one operator here in ireland

If i buy this and buy the unlock code ... ill be able to install any rom or ill be back locked again ( in this case...if i flash the cm10) m

Tks ...and im sorry for the noob question
[Galaxy S III Android Development] tux821:
1) Ok so the JB image or some code in the JB setup maybe together with some Samsung boot code dit erase the unlock code from my efs or JB uses a modified efs which turned my unlocked phone in a locked phone?

2) Just wondering would a full efs restore after installing CM10 also give me back my unlocked phone?

3) Even a full CWM restore to go back to CM9 did not fix this the network lock stayed there.

Does CMW backup does not backup efs?
[Galaxy S III Android Development] jamie2002uk:
Well i have just restored my efs folder from a backup i made when i got the phone with efs pro fully unlocked nv.log has no mention of cracking detected no thankfully so just a case of what rom to try :)
[Galaxy S III Android Development] tux821:
Soo.. you just restored your efs..

Like the Duke would say: balls of steel !!

:cool:

Thanx for the feedback!
[Galaxy S III Android Development] Odia:
Well its nice to see you here and very good to read what you have written, hopefully it will stop the madness with people using this lame method.

Just to clear up your assumptions, they would not end up with the IMEI from the core file, since the core file, same like the nv_data files are encrypted using the unique ID and since the file cannot be decrypted using a different unique ID, the IMEI would become 0049...

So I just hope anyone who has used this crazy method has a backup of their EFS and can restore their own core file.
[Galaxy S III Android Development] tux821:
@Odia

I have read some threats from you about this subject so I assume you know a bit more what is going on.

Just want to ask you two questions:

1) What do you think basically happend to me and others with an unlocked phone flashing some JB custom rom (in my case CM10) and end up with a very consistent network lock ?

// even a full CWM restore to my working CM9 did keep this lock on.

2) What is your advice when someone ends up with this nework lock and want to fix this?

// Fixed mine by ordering network unlock code. I am back now on a fully working CM9 till I understand more what happened.
[Galaxy S III Android Development] daveg1980:
I am getting permission access denied for file - .nv_core.bak

Can anyone please advise me? I am tearing my hair out
[Galaxy S III Android Development] marrila:
I got this same error when I was using efs explorer.

Use root explorer instead worked for me!
[Galaxy S III Android Development] zohawkish:
could you explain how the imei would be become 0049..? could you explain me the reason why no one so fair have stated that its imei was changed by using this mod ? personnaly i ve tried voodoo app after this mod and the result no minor change (no corrupted file or anything else) in the whole efs files even i ve edited by myself nv_data to see if i get something corrupted but same result. btw i ve write in the op a clear message. btw i can declare that mod is safe so far and works for all sgs3 varriants including us version and it is free.

"if you have anythings that helps users here in this section of "DEVELOPMENT" you known what to do :) but your post here is very laming and ridiculous because i haven't made any change in nv-data. strange u talking about nv data and in your sgs2 mod is based on it ...are you crazy ;)
[Galaxy S III Android Development] rafaelfessel:
So... even if my phone was previous unlocked by a nac code... it will be blocked again when we upgrade to JB CM10?
[Galaxy S III Android Development] zohawkish:
you need root explorer and back up the whole efs file in safe place like upload it on dropbox
[Galaxy S III Android Development] zohawkish:
follow op steps you will get unlocked device on jb or cm10
[Galaxy S III Android Development] daveg1980:
Cheers, I am doing the Mike1986 fix to fix my sim lock issue since upgrading to Omega 4.1.1

I have now went from SIM Lock to no SIM Lock but No service

Now I am worried!
[Galaxy S III Android Development] zohawkish:
just follow up op :eek:
[Galaxy S III Android Development] cooldfuzion:
I am using the supernexus (JB) and did all the steps and still its locked, do i have to install another rom? what am i doing wrong??

Thanks
[Galaxy S III Android Development] Odia:
Since you have no idea what you are doing and you have no slight notion how the core file works and how nv_data files work, its impossible to put it into simple terms for you to understand, if you have no idea what you are talking about and no idea what I am talking about then just STFU, I was not talking to you, but the guy I did reply to will understand what I said.

if you want to understand then read what spocky12 wrote and what I replied to him.

and yes I am crazy from fools like you who are possibly fcuking up peoples expensive phones.
[Galaxy S III Android Development] zohawkish:
lol....now i m sure that you are very crazy. you cannot post an explication of what you have written "imei could change..." at least to people who can understand some notions. btw im not fool to play with this mod. the entire responsabilty is bound to users and they are free to use it. so use it or not dont belong to me.

"please respect the choice of users here don't use a vulgar term. shame on you considered as a recognized developer"
[Galaxy S III Android Development] zohawkish:
did you back to stock lbg8?
[Galaxy S III Android Development] cooldfuzion:
No, do i have to? and if i want to go back to Supernexus, and not loose the unlock, what do i have to do?

Thanks
[Galaxy S III Android Development] zohawkish:
yes read the op :mad:
[Galaxy S III Android Development] Toufik1967:
Zohawkish.......you have our full support...at least you're the only one lately who posted something usefull to unlock this phone, and for FREE.......those who had successfully unlocked their phones are happy without any issue so far with you continuous help.

Apparently, you're making some jealous people there.....keep up the good work........thumbs UP!!!!
[Galaxy S III Android Development] machu28:
just upgraded to the latest dlh6 jb with no problem the device stay unlocked :good:
[Galaxy S III Android Development] tux821:
That is what happened to me and others, see previous posts.

So far no response from te experts to explain in some more detail -what- happend here.. only fixes to work around this issue.

Altough I respect the experts working on this, some info about what happens in the first place would be nice.
[Galaxy S III Android Development] zohawkish:
thanks ;)
[Galaxy S III Android Development] Daelyn:
@Odia

Forget it. I tried too. People jump the gun on anything these days.
[Galaxy S III Android Development] Odia:
Who do you think you are that I have to explain anything to you? If you had any idea what this file function was you would not be copying it across devices, you was the one who started with words by saying I was crazy, since I am far from it, now I made a reply here to someone I think is expert enough and will understand what I am saying, so live with it and your own shame.
[Galaxy S III Android Development] transzo:
Well said ..but playing with kids could be harmful than playing with your mod :D
[Galaxy S III Android Development] cooldfuzion:
It worked :) many thanks and keep the good work!
[Galaxy S III Android Development] rafaelfessel:
but if i have the nac code...when i upgrade could i use again to unlock the device? bcause i believe the nac code is a unique code for each device...

right?
[Galaxy S III Android Development] Odia:
If you unlock the phone via code it will not relock, unless you played with your EFS first.
[Galaxy S III Android Development] tux821:
I have the same question because I unlocked on CM9 with a network unlock code too after the CM10 upgrade network locked my unbranded/unlocked phone.

I assume it will work as long as your imei stay's the same. But I have not tried this yet. I'll wait for the first stable CM10.

Be sure to backup your efs before you flash CM10.

* Edit *

Oops too slow :eek:

did not see previous post. Thanx.
[Galaxy S III Android Development] jadajada:
Can this be applied to an S3 running on stock firmware? I am on build XXLFB now.

I was unlocked using the 8 digit code provided by my carrier (Telenor Norway), but after an Odin flash of a more recent stock firmware + data wipe and factory reset, it is requesting this: Sim network unlock PIN.

The phone is supposed to be unlocked, but isn't anymore. The 8 digit code does not work either. I want to keep it stock in the case of me selling the phone, it has to be unloced for the same purpose.

If I have to root for this procedure I suspect the lock will come back when I flash back into stock?
[Galaxy S III Android Development] tux821:
No.. it should but it does not..

After the network locking drama I did instantly order another Samsung Galaxy S3 because I like this phone very much and was not sure how long it would take to get things working again :rolleyes:

This phone is also unlocked and stock Samsung. Today I did enter *#7465625# to try to get the lock status. It gives the same error message:

'Connection problem or invalid mmi-code'
[Galaxy S III Android Development] machu28:
hmm...if so it seems that your new device will face the same issue, this code should work on unbranded phone
[Galaxy S III Android Development] tux821:
Yep I guess so, ordered the phone from the same webshop.

I remember the setup which did start in Poland language and I live in the Netherlands using KPN provider sim.

I am now Googling find other hits on this but no answer.

Should this code directly be catched by the phone or is this also routed through my SIM/provider?

The phone works fine btw. altough my primary CM9 flashed phone also works again, lol.

Is there another trick to find out which locks are active (without root)?

* edit *

This seems a bit related, rofl:

http://code.google.com/p/android/issues/detail?id=2226
[Galaxy S III Android Development] Odia:
The core file in the OP contains the following info

IMEI Number: 353328056751546

Left the factory with I9300XXBLH1/I9300ITVBLH2/I9300XXLH1/I9300XXBLH1

Italy Unbranded
[Galaxy S III Android Development] tux821:
The '.nv_core.bak' ?

Erm how would I know the data in this file is crypted right :cool:
[Galaxy S III Android Development] Odia:
Yes the .nv_core.bak and you know now because I have just told you :cowboy:
[Galaxy S III Android Development] tux821:
Lol, thats pretty impressive.. and this workaround may, as I understand correctly end up with some phones running this id.. 8)
[Galaxy S III Android Development] Odia:
No they will not end up using this IMEI because the phones unique ID will not match the unique ID used to encrypt this file, so the IMEI will become the default IMEI of 0049... e.g. corrupted.

I was only able to recover the IMEI from the file, because I know the encryption algo and the format of the unique ID, so I was able to brute force the file and decrypt it.
[Galaxy S III Android Development] Joao Oliveira:
I think you people are playing with fire here! Maybe you stop attacking Odia for everything and nothing and hear what he has to say, and maybe you could get something from him. Bashing doesn't help a bit! :P

It's your phones, do whatever you want, just don't complain after! :P
[Galaxy S III Android Development] Odia:
Hey Joao,

How is your unlocked phone doing, has it re-locked yet (NOT!)

Don't worry what we see here is typical school boy behaviour, they think they have something good and they are god, but when someone try's to help and show that they actually have a ticking bomb they start with insults like a bully in the playground, now the OP has all the proof he needs and can re-title the thread to "DESTROY YOUR EFS FOREVER"
[Galaxy S III Android Development] Joao Oliveira:
Oh Yeah it's working fine! Done a few custom Roms updates no problems at all nothing corrupt, everything smooth. :) thanks!!

What. Can one do, apparently people love the risk of having a $ 700 mp3 player...

All the best to you
[Galaxy S III Android Development] machu28:
but if i got something wrong i can restore my original efs no ?
[Galaxy S III Android Development] Odia:
You can most of the time, but the EFS has a sync number which shadows to an area in flash and if it gets too far out of sync your baseband will become unknown and your IMEI blank and then even restoring your original backup will not fix it.
[Galaxy S III Android Development] tux821:
1) Thats the reason I want more info on the causes of this, not only fixes like Voodoo this and flash that and you might be lucky.

2) Must say learned some more about the mechanisms in the efs folder.

3) I think the OP was an honest attemp to help, don't be that hard on him.
[Galaxy S III Android Development] zohawkish:
please go play to another thread :angel:

thread will be closed ......
[Galaxy S III Android Development] jamie2002uk:
Ahhh thank you but upgraded via odin to stock lg8 unbranded now it locked so yet again itryed restoring efs while on lg8 restarted no joy lock still on :(
[Galaxy S III Android Development] veyka:
Closed per the OP's request.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snoopdaclown:
Looking to flash a rom and need a great rom to flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spiderjerusalem:
Wrong forum son. Does not belong here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KennyG123:
What the other Spider dude just said!

READ FORUM RULES AND STICKIES BEFORE POSTING ANYTHING!

Thread moved

NFNM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snoopdaclown:
Sorry still used to infuse 4g forums where they didn't care

Sent from my Rooted Stock S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tlo218:
Read through the ROMS posted and find one with features that fit your wants. Some are performance driven, and some are customization driven. Only you know what your looking for. Start reading threads in the development forums.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] The Archangel:
Well around here you'll find out, That what tolerated nothing. It's nothing personal against you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snoopdaclown:
O yeah I know just gotta get used to these forums. Yeah I found some stockish Tom's with features I want. Triune 2 and nastolgia are the 2 that caught my attention. I want a good kernel to use and found one that has oc which would be nice.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snoopdaclown:
Mainly want init.d support for future tweaks for ram and speeding things up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] timeToy:
Dude, stop it, we are not going to answer anything on this thread. After being chastised you still find ways to come back and now put forward requirements for your perfect ROM, for the community to hunt or build for you? Classy...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bravomail:
Three knives in the back of indian

My ROM is the greatest of all!!

No. Not really. :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neubauej:
The greatest ROM of all is the one you build yourself.

:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KennyG123:
All ROMs are great to each of the members using it.

You will need to make a backup and try each until one suits YOU

Everybody uses their phone differently so they cannot decide for you

This is why these threads get closed
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ryancnap:
Wanted to verify I undervolted correctly since this is my first time messing with system tuner, I wouldn't be posting but it seemed too simple.. which usually means I did something wrong. After flashing sky ics and applying updates, etc. I let the phone settle all day and charge up to full battery. Updated system tuner, went to voltage tab

Previous recommendations were to UV to -75 mV so I tapped the -12.5mV option six times. Then I exited system tuner. Not sure if I did it correctly, or if I have to reboot for changes to set in? Oh and just before I undervolted I wiped cache and dalvik and flashed the latest cymbaline kernel. My battery's already gone down 2% since I started typing this..but I'll assume everything just needs to settle.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Bruno2123:
Make sure to check system tuner after your restart and see if the voltage table are the same as you changed i cant remember if you have to change the boot settings for cpu settings to on boot complete. cymbaline drains battery faster then stock even with uv it will just mitigate it some. If the tables are the same you might want to do a stress test if it passes then your fine.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ryancnap:
Yep reboot resets the values. It already seems like battery's draining faster, but that could just be me. Gonna leave this setup go for a day or two though on minimal usage, UVed to -87.5 now, and see how it goes. Then I'll try seanz modded UCLF5 kernel (which I believe doesn't have support for UV) and post results here. Thanks for the help though.