Welcome to CyanogenMod
|Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
Sim Network Unlock
Posted 23 February 2013 - 03:33 PM
I updated to cm-10.1-20130221-NIGHTLY-i9100.zip last night and now my Sll is asking for the sim network unlock code, every code I've tried like the default 0000's, 1234 and even my carriers PUK code doesnt work. I've re-flashed to stock samsung rom and rooted it again and it is still asking for my network unlock code. I cant make phone calls or use 3g internet. Can anyone shed any light on the probelm?
Posted 23 February 2013 - 04:24 PM
Posted 23 February 2013 - 07:33 PM
I managed to get my nv_data.bin fixed with Galaxy S unlock tool only for that (or) the contents of the /efs folder to change upon a reboot.
So, after much head scratching I've also had to flash back to stock with odin (which oddly required me to boot into the stock recovery afterwards and to then factory reset it to stop it soft boot looping), and using a combination of CF's ExynosAbuse/SuperSU to install Busybox, then using the above app to get - and this time keep, my correct nv_data.bin/efs folder after a reboot.
Trying to install the latest CM nightly in CWM then reproduces the above SIM network lock all over again. I'm just at the stage of downloading a nightly previous to the 20130219-NIGHTLY to see if there's still a problem. I'll be back.
edit: Woo! Flashed GT-I9100_ClockworkMod-Recovery_188.8.131.52 in odin, then installed cm-10.1-20130216-NIGHTLY-i9100.zip and I have an unlocked phone again.
Edited by ladfrombrad, 23 February 2013 - 08:17 PM.
Posted 23 February 2013 - 09:18 PM
Edited by ladfrombrad, 23 February 2013 - 09:47 PM.
Posted 24 February 2013 - 09:30 AM
Posted 24 February 2013 - 09:33 AM
But I had to pay 3 euros for it, which isn't a lot to unlock a phone if that's what you needed - but it sucks that I actually HAD an unlocked phone and the update put me in this position.
So I'll stay on cm9 until I think I can give up another few hours of life to attempt an upgrade to 10. Phooey.
Edit: damn after a reboot it is locked again, on cm9. This may not just be a 'phooey' problem anymore.
Edit2: okay so I found the app GalaxSimUnlock and it seems to have done the trick across reboots - I've done two reboots and I'm still working.
Edited by thewozza, 24 February 2013 - 09:46 AM.
Posted 26 February 2013 - 07:22 PM
luckily i've made a backup of /efs and stored it among my encrypted keys when my phone was new and i first read the advice... thanks for whomever advised it!
i've flashed cm-10.1-20130217-NIGHTLY-i9100.zip and then restored my /efs and now the mobile network works again.
start the recovery, connect with adb.
then set up a ramdisk (my CWM can't mount my /sdcard) to store files:
mount -t tmpfs none /sdcard/
then quit adb shell, adb push your backup, and reconnect with adb shell. then:
dd if=Samsung-I9100-efs-dev-block-mmcblk0p1.img of=/dev/block/mmcblk0p1
Edited by attila.lendvai, 26 February 2013 - 07:26 PM.
Posted 07 March 2013 - 02:04 PM
anybody knows any news?
Posted 16 March 2013 - 06:16 AM
so this wiki warning may be misleading:
"If you used a non-official method to remove a provider lock, your /efs partition may become corrupt!"
Posted 18 March 2013 - 02:44 PM
Tue Feb 26 23:23:58 2013: cracking detected
Tue Feb 26 23:23:59 2013: NV backup has been rebuilt
Tue Feb 26 23:23:59 2013: NV restored
Tue Feb 26 23:30:01 2013: OFFSET_FOR_PRESET2 writing input
Tue Feb 26 23:30:01 2013: 2nd NV built
Tue Feb 26 23:30:02 2013: NV data back-uped
Wed Feb 27 00:11:38 2013: OFFSET_FOR_PRESET2 writing input
Wed Feb 27 00:11:39 2013: 2nd NV built
Wed Feb 27 00:11:40 2013: NV data back-uped
but what is very strange is that when i restored the /efs and cm-10.1-20130217-NIGHTLY-i9100.zip, then it has been working for weeks, and at one point it also broke and produced the above log. why more recent android versions brake immediately, and this one only after weeks is baffling.
has anyone found anything else to fix this than the previously mentioned market app?
Posted 20 March 2013 - 04:55 PM
Posted 23 April 2013 - 04:22 PM