Database Users

RESTORE IMEI and Product Code w/o ADB, PC (ALL DONE ON PHONE) nv_data.bin

**VIDEO GUIDE ADDED BELOW**
There is already a guide for restoring IMEI and Product code with a PC and ADB moving files between phone and computer......so i thought i would provide an alternative method that can be done without a PC or ADB.
(This should be done from stock 2.1 (JF6) but may not be required (got this to work while in phoenix 1.5 without reverting)- results may very in custom rom environments....
***IMPORTANT PRECURSOR - we will be working with an important system folder (/EFS) and its contents (nv_data files). It is important to back this folder up (we will be doing this in step 2 below). I first backed it up to my external sd card but i did also copy the backup folder to my PC just in case.
fyi this fix is intended specifically for persons with borked product codes and imei's due to custom rom flashes and will not address nv_data issues of carrier blocks/etc. for those who had unlocked their devices and may in fact undo your unlock.***
This method assumes you are starting with a rooted phone w/ superuser rights
You will need the following APPS that can all be downloaded from market and, with the exception of Root Explorer, are all free:
A. Root Explorer (i know its paid but its the most $ worthy app i have encountered. You can use the free Android Mate as an alternative but not as robust or convenient IMO)
B. Busbybox (once installed from market open the app to install it)
C. Android Terminal Emulator
D. Hex Editor
E. SGS Toolbox
_________________________________________________________________
Once all tools/apps listed above have been downloaded proceed as follows:
THERE ARE 3 Total Lines you will need to edit:
00188008
00188010
00188020
1. Install Busybox if you haven't done so already.
2. Use Root Explorer to create EFS Backup folder on an External SD (if you don't have one you can use the internal sd and give it a generic name that you will be able to identify). When ROOT EXPLORER opens you will be in the system file directory to get to your internal sd card open the SDCARD folder (from there you will see your external sd card as well if you have one installed)
3. Use root explorer to view the open the EFS folder from your system directory. The EFS folder contains the file you will will need to edit and replace. Open the efs folder and use the multi-select copy to copy the following files: nv_data.bin and nv_data.bin.md5 (you can also copy their respective backup files nv_data.bak and nv_data.bin.md5.bak).
4. Staying in root explorer go back to parent directory (option at top of file/folder list) and navigate to the backup folder you created and paste the files there. While still in this directory make a copy of just the nv_data.bin and the paste is either in the root directory or external sd or internal sd if you do not have ext. *Since i have good backups now on PC and external sd...i generally just edit the nv_data.bin file in place and save over the original in the efs folder.
5. Open Hex Editor Application and open the copy of nv_data.bin from your external or internal SD (click the capacitive menu button on phone and select OPEN FILE)
6. Once the file opens click the capacitive button to bring up the menu again and select jump to address:
7. Enter 0188008
This will take you to line 00188008
8. Edit the last or 8th Block (last column of green text). Click in the box and edit it so that it reads 41.
LINE 00188008
Block 8 = 41
9. use menu to jump to address again and Enter 0188010
10. This will take you to line 00188010. Edit the first two blocks of green text from this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read TT....SG)
11. Now look down to line 0018020 and look at the line. If you look at the line to the far right text you will see ATOR or ATMB (or something other than AATT) if your nv_is messed up.
12. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
13. Save the file and move it back to efs using root explorer copying over the original.
14. delete all nv_data files from efs folder EXCEPT FOR YOUR NEWLY CREATED NV_DATA.BIN. (Delete the following: .nv_data.bak, .nv_data.bak.md5 and the nv_data.bin.md5 files. This differs from video but i also delete any .nv_state or nv.log file present and they are recreated). FYI IF YOU ARE USING A GINGERBREAD ROM AND YOUR EFS CONTAINS .nv_core.bak and .nv_core.bak.md5 DO NOT DELETE THEM with the other .nv files.
15. (This step may not be necessary unless you lose your voice/data connection upon reboot)
Open Terminal Emulator and run the following commands:
su
busybox chown 1001:1001 efs/nv_data.bin
reboot
16. Once your phone has rebooted use SGS Toolbox APP to check your IMEI and Product Code to make sure the fix worked.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|TT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
PS - In terminal emulator after you enter your first Command Line
su
your keyboard may not pop back up. Don't worry if it doesn't just reopen it from your app drawer and proceed with line 2 and 3
**NEW: VIDEO GUIDE**
SPECIAL THANKS TO CONNEXION2005 for providing the video guide below:
http://www.youtube.com/watch?v=JqLK_2I-SBM&feature=player_embedded#!
-----------------------------------------------------------------------------
*DISCLAIMER*
have already had one person post a response that this thread was misleading and stating that:
This thread is misleading. There is no way to restore IMEI if you didn't back up your nv_data.bin before it got messed up.
Click to expand...
Click to collapse
I have seen other users make this claim as well, however, they are either mistaken or what i experienced was a complete anomoly.
I had never backed up my efs folder or nv_data files prior to them being messed up (i didn't know they were there and had never used root explorer to view them until i had to research a fix). The first thing i did was use a hex editor to look at my nv_data.bin and its bak(s) and in fact none of them were good. They all contained wrong product code.
So the process i described was conducted without any previously backed up original nv_data.bin or nv_data.bak files.
I started with:
wrong IMEI
wrong product code
totally botched nv_data files with no backup of original unmolested efs folder or nv_data files
I ended up with
Restored original IMEI
Correct Product Code
Healthy/Correct nv_data files that i immediately backed up in multiple locations.
So if you didn't back up your original untainted efs or nv_data files and this fix doesn't work to restore your original imei and product code then allow me to apologize in advance for "misleading" you and trying to assist with your problem by posting what did in fact work for me.
--------------------------------------------------------------------------------------------------------------
DONATIONS NOT REQUIRED OR EXPECTED. IF YOU FEEL THIS THREAD HAVE HELPED YOU WITH A SICKLY DEVICE OR SAVE YOU ANY HEADACHE OR TROUBLE FEEL FREE TO CONTRIBUTE:

bames said:
There is already a guide for restoring IMEI and Product code with a PC and ADB moving files between phone and computer......so i thought i would provide an alternative method that can be done without a PC or ADB.
***IMPORTANT PRECURSOR - we will be working with an important system folder (/EFS) and its contents (nv_data files). It is important to back this folder up (we will be doing this in step 2 below). I first backed it up to my external sd card but i did also copy the backup folder to my PC just in case.***
This method assumes you are starting with a rooted phone w/ superuser rights
You will need the following APPS that can all be downloaded from market and, with the exception of Root Explorer, are all free:
A. Root Explorer (i know its paid but its the most $ worthy app i have encountered. You can use the free Android Mate as an alternative but not as robust or convenient IMO)
B. Busbybox (once installed from market open the app to install it)
C. Terminal Emulator
D. Hex Editor
E. SGS Toolbox
_________________________________________________________________
Once all tools/apps listed above have been downloaded proceed as follows:
THERE ARE 3 Total Lines you will need to edit:
00188008
00188010
00188020
1. Install Busybox if you haven't done so already.
2. Use Root Explorer to create EFS Backup folder on an External SD (if you don't have one you can use the internal sd and give it a generic name that you will be able to identify). When ROOT EXPLORER opens you will be in the system file directory to get to your internal sd card open the SDCARD folder (from there you will see your external sd card as well if you have one installed)
3. Use root explorer to view the open the EFS folder from your system directory. The EFS folder contains the file you will will need to edit and replace. Open the efs folder and use the multi-select copy to copy the following files: nv_data.bin and nv_data.bin.md5 (you can also copy their respective backup files nv_data.bak and nv_data.bin.md5.bak).
4. Staying in root explorer go back to parent directory (option at top of file/folder list) and navigate to the backup folder you created and paste the files there. While still in this directory make a copy of just the nv_data.bin and the paste is either in the root directory or external sd or internal sd if you do not have ext.
5. Open Hex Editor Application and open the copy of nv_data.bin from your external or internal SD (click the capacitive menu button on phone and select OPEN FILE)
6. Once the file opens click the capacitive button to bring up the menu again and select jump to address:
7. Enter 0188008
This will take you to line 00188008
8. Edit the last or 8th Block (last column of green text). Click in the box and edit it so that it reads 41.
LINE 00188008
Block 8 = 41
9. use menu to jump to address again and Enter 0188010
10. This will take you to line 00188010. Edit the first two blocks of green text from this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read TT....SG)
11. Now look down to line 0018020 and look at the line. If you look at the line to the far right text you will see ATOR or ATMB (or something other than AATT) if your nv_is messed up.
12. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
13. Save the file and move it back to efs using root explorer copying over the original.
14. delete the nv_data.bak and the nv_data.bin.md5 files (leave the nv_data_bin.md5.bak in the folder..don't delete it).
15. Open Terminal Emulator and run the following commands:
su
busybox chown 1001:1001 efa/nv_data.bin
reboot
16. Once your phone has rebooted use SGS Toolbox APP to check your IMEI and Product Code to make sure the fix worked.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|TT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
PS - In terminal emulator after you enter your first Command Line
su
your keyboard may not pop back up. Don't worry if it doesn't just reopen it from your app drawer and proceed with line 2 and 3
Click to expand...
Click to collapse
Questions?
1) Do you need to be on stock jf6 or this can be done from the current custom rom?
2) Is this for restoring IMEI or Product code? (I guess imei doesn't change)
Thanks.

I think i deleted the file i wasnt supposed to... can someone post that file?

krips2003 said:
Questions?
1) Do you need to be on stock jf6 or this can be done from the current custom rom?
2) Is this for restoring IMEI or Product code? (I guess imei doesn't change)
Thanks.
Click to expand...
Click to collapse
you should revert to stock to run this.
your welcome to try it with any rom you are using but i have only used it in stock jf6 as that was when i discovered the problem. I tried odin one click jf6 when i noticed both my product code and imei were wrong thinking go full stock reinstall would fix. No luck....with alot of reading i discovered one method of fixing the problem then also worked out the 2nd method that doesn't require adb or pc in case it needed to be done on the fly away from computer.

Shouldn't step 15. have
busybox chown 1001:1001 efs/nv_data.bin
instead of efa?

CapnPez said:
Shouldn't step 15. have
busybox chown 1001:1001 efs/nv_data.bin
instead of efa?
Click to expand...
Click to collapse
yes..thanks...duly noted and corrected

So when i open my efs folder, it's empty. Or it says iy's empty anyway. I couldn't get hex editor to save my file on the pc, so I figured I might give this one a try.

rwj5279955 said:
So when i open my efs folder, it's empty. Or it says iy's empty anyway. I couldn't get hex editor to save my file on the pc, so I figured I might give this one a try.
Click to expand...
Click to collapse
what are you looking @ your efs folder with? It shouldn't be empty...even if you had completely deleted your nv_data files when trying the other method there should have been other folders in /efs. You didn't cut and paste or move all the folders/files from efs (rather than copy) somewhere did you?
PS - aside from the files starting nv_ you should have two folders /efs/imei and /efs/.android

bames said:
There is already a guide for restoring IMEI and Product code with a PC and ADB moving files between phone and computer......so i thought i would provide an alternative method that can be done without a PC or ADB.
***IMPORTANT PRECURSOR - we will be working with an important system folder (/EFS) and its contents (nv_data files). It is important to back this folder up (we will be doing this in step 2 below). I first backed it up to my external sd card but i did also copy the backup folder to my PC just in case.***
This method assumes you are starting with a rooted phone w/ superuser rights
You will need the following APPS that can all be downloaded from market and, with the exception of Root Explorer, are all free:
A. Root Explorer (i know its paid but its the most $ worthy app i have encountered. You can use the free Android Mate as an alternative but not as robust or convenient IMO)
B. Busbybox (once installed from market open the app to install it)
C. Terminal Emulator
D. Hex Editor
E. SGS Toolbox
_________________________________________________________________
Once all tools/apps listed above have been downloaded proceed as follows:
THERE ARE 3 Total Lines you will need to edit:
00188008
00188010
00188020
1. Install Busybox if you haven't done so already.
2. Use Root Explorer to create EFS Backup folder on an External SD (if you don't have one you can use the internal sd and give it a generic name that you will be able to identify). When ROOT EXPLORER opens you will be in the system file directory to get to your internal sd card open the SDCARD folder (from there you will see your external sd card as well if you have one installed)
3. Use root explorer to view the open the EFS folder from your system directory. The EFS folder contains the file you will will need to edit and replace. Open the efs folder and use the multi-select copy to copy the following files: nv_data.bin and nv_data.bin.md5 (you can also copy their respective backup files nv_data.bak and nv_data.bin.md5.bak).
4. Staying in root explorer go back to parent directory (option at top of file/folder list) and navigate to the backup folder you created and paste the files there. While still in this directory make a copy of just the nv_data.bin and the paste is either in the root directory or external sd or internal sd if you do not have ext.
5. Open Hex Editor Application and open the copy of nv_data.bin from your external or internal SD (click the capacitive menu button on phone and select OPEN FILE)
6. Once the file opens click the capacitive button to bring up the menu again and select jump to address:
7. Enter 0188008
This will take you to line 00188008
8. Edit the last or 8th Block (last column of green text). Click in the box and edit it so that it reads 41.
LINE 00188008
Block 8 = 41
9. use menu to jump to address again and Enter 0188010
10. This will take you to line 00188010. Edit the first two blocks of green text from this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read TT....SG)
11. Now look down to line 0018020 and look at the line. If you look at the line to the far right text you will see ATOR or ATMB (or something other than AATT) if your nv_is messed up.
12. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
13. Save the file and move it back to efs using root explorer copying over the original.
14. delete the nv_data.bak and the nv_data.bin.md5 files (leave the nv_data_bin.md5.bak in the folder..don't delete it).
15. Open Terminal Emulator and run the following commands:
su
busybox chown 1001:1001 efs/nv_data.bin
reboot
16. Once your phone has rebooted use SGS Toolbox APP to check your IMEI and Product Code to make sure the fix worked.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|TT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
PS - In terminal emulator after you enter your first Command Line
su
your keyboard may not pop back up. Don't worry if it doesn't just reopen it from your app drawer and proceed with line 2 and 3
Click to expand...
Click to collapse
Does not work for me on jpx. This changed my product code, but not changed my imei.
I think we have to live with a generic imei.
However, thanks.

KALI2000 said:
Does not work for me on jpx. This changed my product code, but not changed my imei.
I think we have to live with a generic imei.
However, thanks.
Click to expand...
Click to collapse
suspected would only work with stock. the generic id is less of an issue because i think as long as your product code isn't screwed in the nv_data files your original imei will restore upon reflash of stock.
One interesting thing and may be just luck. I had flashed all kinds of roms before and it usually changed the imei to the generic one but it was no big deal because it would restore when going back to stock (and the product code was never altered).
Since having them get messed up and doing this fix i have flashed multiple roms Axura, Assonance, Perception, Epsyl, and currently chronos and it has yet to alter my original imei in the process. Right now i am running chronos and it still has my original imei.

Also, you guys can also try using the 3 button fixed ODIN posted in the same thread instead of using DG's 1 click to stock jfs6 using ODIN. That might also fix the issues regarding product ID. Even if it doesnt resolve the product ID issue, you'll still be flashed to stock and then you can use the procedure mentioned in here to change your product ID. I'm using xda app to post so I cannot find a way to copy the link for that forum.
Sent from my SAMSUNG-SGH-I897 using XDA App

krips2003 said:
Also, you guys can also try using the 3 button fixed ODIN posted in the same thread instead of using DG's 1 click to stock jfs6 using ODIN. That might also fix the issues regarding product ID. Even if it doesnt resolve the product ID issue, you'll still be flashed to stock and then you can use the procedure mentioned in here to change your product ID. I'm using xda app to post so I cannot find a way to copy the link for that forum.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
here is the link odin files and 3 button fixed one click (scroll to 3rd post):
http://forum.xda-developers.com/showthread.php?t=786532

krips2003 said:
Also, you guys can also try using the 3 button fixed ODIN posted in the same thread instead of using DG's 1 click to stock jfs6 using ODIN. That might also fix the issues regarding product ID. Even if it doesnt resolve the product ID issue, you'll still be flashed to stock and then you can use the procedure mentioned in here to change your product ID. I'm using xda app to post so I cannot find a way to copy the link for that forum.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
here is the link odin files and 3 button fixed one click (scroll to 3rd post and it contains links to both versions):
http://forum.xda-developers.com/showthread.php?t=786532

Sorry, my files showed when i checked show hidden files.
Still, I'm gonna flash back to stock when I get home and try this again. Thanks for this.

rwj5279955 said:
Sorry, my files showed when i checked show hidden files.
Still, I'm gonna flash back to stock when I get home and try this again. Thanks for this.
Click to expand...
Click to collapse
hope it helps. let me know your results when you get a chance.

I did a similar method, but only changed the AATT part in a hex editor and moved the file back with super manager, gave owner full chmod access, rebooted, made sure kies mini detected my device and then reflashed stock/master clear.
Now everything is back to normal.

I don't have an EFS folder and a search in Root explorer finds no nv_data.bin.
Apparently I flashed too many ROMS...lol

So ... As I can get my imei?

This thread is misleading. There is no way to restore IMEI if you didn't back up your nv_data.bin before it got messed up.
Sent from my MB520 using XDA App
EDIT - apparently my statement is incorrect in regards to the captivate. I had been researching fixing my unlock that got relocked and many on the Vibrant forums have the generic IMEI with no way back. As of Jan-3-2011 - bames testing shows that changing the product code, does indeed fix the IMEI - I have to assume that the encrypted IMEI in the nv_data.bin is tied to the product code (maybe a pad or salt) and the phone can't read the IMEI if the product code changes.
Still, the best solution, before any modding, is to back up nv_data.bin.

alphadog00 said:
This thread is misleading. There is no way to restore IMEI if you didn't back up your nv_data.bin before it got messed up.
Sent from my MB520 using XDA App
Click to expand...
Click to collapse
from my own experience you are either mistaken or my result was an anomoly.
I had NEVER backed up my efs (had never used root explorer and didn't know the folder was even there prior to researching a fix) folder prior to having my imei, product code, and nv_data files messed up. (Once it was discovered and started researching a fix i used hex editors to view my nv_data files and both the original and BAK copies were messed up).
I ran the fixes and in fact my original IMEI and product codes were restored and in fact have remained in tact for each of the 4 or 5 times i have flashed new 2.2 roms after completing the fix. Right now i am running Chronos and still have my original IMEI (not a generic).
Once i saw the fix worked and i had healthy proper nv_data files the first thing i did was back up the entire efs folder in multiple places.

galaxy s unlock

anyone having trouble unlocking there galaxy should try these guys.mobileunlocked.co.uk .i tried everything to unlock my phone and nothing worked.but these guys soughted it.it cost me £15 but it was worth it.the only thing i managed to do right was root it.oh and dont worry if your phone froze up they send you the unfreeze codes first.i was very happy with them.

I used " Generate Unlock Windows" found here...
http://forum.xda-developers.com/showthread.php?t=761045
It worked great on my GT-I9000M.
Ian

didnt work for me.i tried every method on here.my galaxy was a pain in the arse.ive unlocked every phone ive had and ive got to say this one was the most difficult.

Unlocking
I used Dawen's method
dawen said:
in hex editor on phone jump to address look for 00181460 looked in the colums on the right of 00181460 and saw
ff ff ff ff ff ff ff ff 01 00 00 00 so i changed 01 to 00
that will make your phone sim free, u dont have to edit to lock just one network, i already try this tricked while leaving 610 as bell in the nv_data file, after i changed to 00 my rogers sim now work, so i assume it will work with other sims also
Click to expand...
Click to collapse
dawen said:
u can use root explorer or use the adb method in the forum to backup the whole efs folder u need to have root and superuser and busybox, i suggest backup more than 1 backup, back it up to sdcard, and ur pc if possible, u need to use ultraedit hex editor and edit the nv_data.bin file, and change that line from 01 to 00, delete the nv_data.bin and nv_data.bin.md5 file from ur phone efs folder then copy your new edited nv_data.bin file, works on a bell vibrant so im not sure about the rest which i think should be same, when i dial *#7265625# it saids network lock [off], so it does work for me
Click to expand...
Click to collapse
If you are still confused, have a look around this thread
http://forum.xda-developers.com/showthread.php?t=761045&page=127
Took me less than 10 minutes.

+1
Works great
Sent from my GT-I9000 using XDA App

[GUIDE] [VIDEO]How to SIM unlock your Galaxy SIII for free!!

I'm just taking what txlibre wrote in http://forum.xda-developers.com/showthread.php?t=1715149 and re-displaying it in a format that I think is easier to understand for n00bs
This really isn't that hard TBH IMO
This worked for me on a GS3 locked to Orange UK, and another locked to Three UK. Your Mileage May Vary!!
-----I cannot be held responsible for anything that happens to you or your phone, from carrying out anything I have said!-----
Credits: txlibre, mskip, the person whoever originally wrote these instructions
----------------------------------
VIDEO GUIDE:
Part 1 (A-E) - http://youtu.be/P1H2yUyQ4J8
Part 2 (1-25) - http://youtu.be/uAVbYx68WI4
----------------------------------
Things to do before starting:
A - Make sure your S3 is rooted (http://forum.xda-developers.com/showthread.php?t=1703488).
B - Make a backup copy of the /efs folder on your PC.
C - Also backup your EFS using mskips ToolKit (http://forum.xda-developers.com/showthread.php?t=1703488).
D - Get a Hex Editor (I used Notepad++ with this plugin: http://sourceforge.net/projects/npp...n v0.9.5/HexEditor_0_9_5_UNI_dll.zip/download (just put the dll in the plugins folder of Notepad++)).
E - Install Root Explorer on your phone.
Now for the actual process:
1 - Using Root Explorer, copy the file nv_data.bin file from your phones /efs folder to your PC and open it in Notepad++.
2 - Scroll down and find address 00181460, modify the 01 to 00.
3 - Save the file.
4 - Copy the modified nv_data.bin from your computer back to your phones /efs folder using Root Explorer.
.....(Make sure you keep a copy of this modified file for step 15.)
5 - Once copied to the phone, open Root Explorer and long press on the nv_data.bin file till the menu pops up and select 'Permissions'.
6 - Make sure ONLY the Read, Write and Execute boxes for Owner are ticked, and press OK.
7 - Then again, long press on the nv_data.bin file till the menu pops up, and select 'Change owner'.
8 - Change Owner and Group to 1001-Radio and press OK.
9 - Restart your phone.
10 - Once restarted dial *#7465625#, check Network Lock is ON and press OK.
11 - Using Root Explorer, copy the file nv.log from your phones /efs folder to your PC and open it.
12 - You should see something like:
... ..Mon Jun 18 23:34:32 2012: MD5 fail. orignal md5 'e1493854d4d62ff4e123040855f8b2a9' computed md5 'd29d791b193de8b6711445231fb7d427' (rild)
.. ...Mon Jun 18 23:34:32 2012: backup NV restored.
... ..(Your numbers may differ).
13 - Copy the file nv_data.bin.md5 from your phones /efs folder to your PC and open it.
... ..You should see the first number listed in step 12 (in my case e1493854d4d62ff4e123040855f8b2a9).
14 - Copy the second number in step 12 (in my case d29d791b193de8b6711445231fb7d427) and put in the nv_data.bin.md5 file, so it is the only number in there. Now save the file.
15 - Now copy the modified nv_data.bin file (from step 4) and the modified nv_data.bin.md5 (from step 14) back to your /efs folder on your phone.
16 - Once copied, long press on the nv_data.bin file till the menu pops up and select 'Permissions'.
17 - Make sure ONLY the Read, Write and Execute boxes for Owner are ticked and press OK.
18 - Then again long press on the nv_data.bin file till the menu pops up and select 'Change owner'.
19 - Change Owner and Group to 1001-Radio and press OK.
20 - Now, long press on the nv_data.bin.md5 file till the menu pops up and select 'Permissions'.
21 - Make sure ONLY the Read, Write and Execute boxes for Owner are ticked and press OK.
22 - Then again long press on the nv_data.bin.md5 file till the menu pops up and select 'Change owner'.
23 - Change Owner and Group to 1001-Radio and press OK.
24 - Restart your phone.
25 - Once restarted dial *#7465625# and check Network Lock is OFF and press OK.

anyone tried this

This is the exact same process I used to unlock my gs2. Unless the address where you modify the the byte is off, I see no reason why this wouldn't work on a gs3.
Sent from my SGH-I897 using Tapatalk 2

any pictures for step 14 or is it pretty self explanatory when you do do it. can you paste it anywhere ?

mox123 said:
anyone tried this
Click to expand...
Click to collapse
I have tried this, and on the original thread, 3 others have used is successfully.
I used this on my wife's phone last night and I'll use it on mine this morning when I get it. Ill do a video

galaxy.S3 said:
any pictures for step 14 or is it pretty self explanatory when you do do it. can you paste it anywhere ?
Click to expand...
Click to collapse
I'll hopefully get a video up later today or tomorrow

can this be undone for warranty if a repair is required.

I'll wait till you post a video.
Sent from my SGH-T769 using XDA Premium App

reaths17 said:
can this be undone for warranty if a repair is required.
Click to expand...
Click to collapse
I would say all you would have to do is repeat the process but in step 2, just overwrite the 00 with a 01.
I will try it out when I get my own GS3 later.

Video guide is up guys

the second vid has been taken down
also, i can't get notepad++ to read the file, it just looks like a load of symbols and no actual text. Any help would be appreciated.

dumb donkey said:
the second vid has been taken down
also, i can't get notepad++ to read the file, it just looks like a load of symbols and no actual text. Any help would be appreciated.
Click to expand...
Click to collapse
Ill sort the video when i get home.
make sure the hex plugin .dll is in the right folder
Open the file in NotePad ++
Go to the plugins tab at the top and select the hex plugin

vinokirk said:
Ill sort the video when i get home.
make sure the hex plugin .dll is in the right folder
Open the file in NotePad ++
Go to the plugins tab at the top and select the hex plugin
Click to expand...
Click to collapse
Great...! was able to unlock the phone without the video; just followed the instruction and voila I'm now sim unlock...

vinokirk said:
Ill sort the video when i get home.
make sure the hex plugin .dll is in the right folder
Open the file in NotePad ++
Go to the plugins tab at the top and select the hex plugin
Click to expand...
Click to collapse
i've got notepad++ showing the dll file and also reinstalled it though plugin manager in notepad++ but still the same?

dumb donkey said:
i've got notepad++ showing the dll file and also reinstalled it though plugin manager in notepad++ but still the same?
Click to expand...
Click to collapse
You have to put the .DLL file you just download to this folder of your computer :
C:\Program Files (x86)\Notepad++\plugins...(If that is your installation folder of course)
And Go to:
1.Plugins
2.HEX editor
3.View in Plugin
In Notepad++ bar

armanderli said:
You have to put the .DLL file you just download to this folder of your computer :
C:\Program Files (x86)\Notepad++\plugins...(If that is your installation folder of course)
And Go to:
1.Plugins
2.HEX editor
3.View in Plugin
In Notepad++ bar
Click to expand...
Click to collapse
Thats done it! Thanks bud!
---------- Post added at 06:54 PM ---------- Previous post was at 06:14 PM ----------
Just putting my experience out there for anyone who comes across what i did.
Neither of my nv.log numbers matched the one from the nv_data.bin.md5, but i copied the second number anyway and put ONLY that one in the nv_data.bin.md5 file and follwed the rest of the instructions and it still worked!
I am now on a sim unlocked phone!
Thanx!
EDIT!! i'm currently having problems with 2 efs folders and tthe phone stuck in factory mode. i dont recoment changing if you come across what i did!
EDIT 2! Phone back to normal after i restored original efs folder.. but back to network lock on!

Thanks for taking the time to write this thread, as I have justed ordered a S3 which is locked to the 3 network. So will use your guide when I receive the phone, and save me £10 paying to get the code.
One quick question though, when you say download "root explorer" for a few pence, are you referring to the Root Explorer (File Manager) app at £3?
The other ones that come up are all free, so I assume these wont work with the below process?

dumb donkey said:
Neither of my nv.log numbers matched the one from the nv_data.bin.md5, but i copied the second number anyway and put ONLY that one in the nv_data.bin.md5 file and follwed the rest of the instructions and it still worked!
Click to expand...
Click to collapse
This is also what happened to me when I unlocked my phone. Once the video is up, you'll see

djglenn1337 said:
Thanks for taking the time to write this thread, as I have justed ordered a S3 which is locked to the 3 network. So will use your guide when I receive the phone, and save me £10 paying to get the code.
One quick question though, when you say download "root explorer" for a few pence, are you referring to the Root Explorer (File Manager) app at £3?
The other ones that come up are all free, so I assume these wont work with the below process?
Click to expand...
Click to collapse
I got it for 64p. It must've been a special offer.

dumb donkey said:
EDIT 2! Phone back to normal after i restored original efs folder.. but back to network lock on!
Click to expand...
Click to collapse
I'd try it from the top again.
Make sure you know which files you've modified already and which ones you haven't. The first time i did it, the phone didn't unlock. I found out it's because i copied across an unmodified bin file, doh!

[Q] HELP! Samsung Galaxy S5 Stuck In Factory Mode!

Hello Everyone.
So... I'll get right to the point here. My Galaxy S5 got stuck in factory mode. That day i was installing a bunch of ROMS. If you need a list of them, let me know.
I decided to go back to my old nandroid backup because I wanted to wait for a 4.4.4 version of the ROM i had found. However, I also got interested in installing a Custom Kernel, so I went ahead and installing Chronik Kernel cause I heard that it was really good. However, I forgot to wipe the cache and dalvik cache before installing the zip, so now I think it messed up my EFS partition, and am stuck in factory mode without WiFi and calling.
I have tried many methods involving the "FactoryApp" folder, but when I checked my phone to edit the text, the folder wasn't in the EFS folder. So I also knew that the Terminal Emulator option was out.
I even tried unrooting and re-installing the stock firmware and doing a factory reset, (I have a nandroid backup on computer) but even that didn't work. I can re-root if needed, but please someone help me, I really want to fix my phone soon. (Also I probably shouldn't have tried doing this on my vacation from home, oh well I am a really curious guy)

Help please!!
Someone please help me! I really don't know what to do! All that is in my EFS Folder is a bunch of APK files for apps i have installed and these files called: act_lock, react_lock and react.lock.bak. Someone please... I really want to get back on WiFi, also I am back from vacation, so I can use my Data plan to install things needed.

Is anyone going to help me?
OK. What is taking so long? I understand that lots of people have questions, but come on its been 1 week and no I be had helped me yet. Like I understand 3 to 4 days but a week? Please someone help me soon!

V1Command3r said:
OK. What is taking so long? I understand that lots of people have questions, but come on its been 1 week and no I be had helped me yet. Like I understand 3 to 4 days but a week? Please someone help me soon!
Click to expand...
Click to collapse
Typically it is in a file efs/FactoryApp/factorymode.
Can you show your efs folder structure?

EFS
vndnguyen said:
Typically it is in a file efs/FactoryApp/factorymode.
Can you show your efs folder structure?
Click to expand...
Click to collapse
Alright so inside that system folder is a bunch of apk files. The only thing that's in my efs folder is apks and a file called react_lock

V1Command3r said:
Alright so inside that system folder is a bunch of apk files. The only thing that's in my efs folder is apks and a file called react_lock
Click to expand...
Click to collapse
It looks like you have an invalid efs folder.
Did you make the imei backup? If so just restore it.
If you don't have imei backup, try reflashing full stock firmware.

vndnguyen said:
It looks like you have an invalid efs folder.
Did you make the imei backup? If so just restore it.
If you don't have imei backup, try reflashing full stock firmware.
Click to expand...
Click to collapse
No imei backup and I've tried installing stock firmware, still in factory mode

EFS
Weird thing is imei still the same. . I don't know why my phone being so
weird.

V1Command3r said:
Weird thing is imei still the same. . I don't know why my phone being so
weird.
Click to expand...
Click to collapse
Yes, it is not too weird as Samsung now does not store the IMEI in EFS partition. It does store in another 2-3 partitions (these partitions are vary from model to model).
EFS partition does not contain the IMEI. It contain the S/N, WiFi and Bluetooth MAC addresses, etc...
Please do the following things:
1- Install Phone INFO ★Samsung★ app and look for the IMEI and S/N (in the DEVICE ID section), and compare them with the IMEI and S/N on the sticker behind the battery. Are they the same?
2- Create a file with a name 'factorymode' on the sdcard, open it, input 'ON' and then save it. Navigate to the efs folder, create the folder with a name 'FactoryApp' (case sensitive). Finally move the file 'factorymode' you have created above to that folder. Reboot the phone to see if the problem still persists?

EFS
vndnguyen said:
Yes, it is not too weird as Samsung now does not store the IMEI in EFS partition. It does store in another 2-3 partitions (these partitions are vary from model to model).
EFS partition does not contain the IMEI. It contain the S/N, WiFi and Bluetooth MAC addresses, etc...
Please do the following things:
1- Install Phone INFO ★Samsung★ app and look for the IMEI and S/N (in the DEVICE ID section), and compare them with the IMEI and S/N on the sticker behind the battery. Are they the same?
2- Create a file with a name 'factorymode' on the sdcard, open it, input 'ON' and then save it. Navigate to the efs folder, create the folder with a name 'FactoryApp' (case sensitive). Finally move the file 'factorymode' you have created above to that folder. Reboot the phone to see if the problem still persists?
Click to expand...
Click to collapse
Alright so the imei is the same but serial number isnt, however when I try to create folder it will say in efs partition: Operation failed:No Space Left On Device

V1Command3r said:
Alright so the imei is the same but serial number isnt, however when I try to create folder it will say in efs partition: Operation failed:No Space Left On Device
Click to expand...
Click to collapse
Yes, as I have said, the efs folder does not contain the imei. However it does contain the S/N.
What did you mean by 'serial number isnt'? The S/N in Phone INFO app is still in valid format? Or it is zero or empty? Can you PM me that S/N (in Phone INFO app)?
Regarding creating folder, make sure your file explorer app has been grant root permission. And try to move/delete some APK files (in efs folder) to free space.

vndnguyen said:
Yes, it is not too weird as Samsung now does not store the IMEI in EFS partition. It does store in another 2-3 partitions (these partitions are vary from model to model).
EFS partition does not contain the IMEI. It contain the S/N, WiFi and Bluetooth MAC addresses, etc...
Please do the following things:
1- Install Phone INFO ★Samsung★ app and look for the IMEI and S/N (in the DEVICE ID section), and compare them with the IMEI and S/N on the sticker behind the battery. Are they the same?
2- Create a file with a name 'factorymode' on the sdcard, open it, input 'ON' and then save it. Navigate to the efs folder, create the folder with a name 'FactoryApp' (case sensitive). Finally move the file 'factorymode' you have created above to that folder. Reboot the phone to see if the problem still persists?
Click to expand...
Click to collapse
vndnguyen said:
Yes, as I have said, the efs folder does not contain the imei. However it does contain the S/N.
What did you mean by 'serial number isnt'? The S/N in Phone INFO app is still in valid format? Or it is zero or empty? Can you PM me that S/N (in Phone INFO app)?
Regarding creating folder, make sure your file explorer app has been grant root permission. And try to move/delete some APK files (in efs folder) to free space.
Click to expand...
Click to collapse
Hey I removed some apks, added the folder, rebooted and now my phone is working ?thank you so much!

V1Command3r said:
Hey I removed some apks, added the folder, rebooted and now my phone is working ?thank you so much!
Click to expand...
Click to collapse
Hey, glad that it worked and was helpful.
Please backup your IMEI asap (search for IMEI Backup app on the Play Store)

vndnguyen said:
Hey, glad that it worked and was helpful.
Please backup your IMEI asap (search for IMEI Backup app on the Play Store)
Click to expand...
Click to collapse
i still have the same problem did evry thing but didn't work for me :S

Successfully de-brand AT&T Lumia 1020!

Finally de-brand AT&T Lumia 1020 (RM-877) successfully, this method may also work on any other Lumia Windows Phone!
Warning: This method is not fully tested, may brick your phone! Back up all data, and do not use this method to flash any incompatible ROMs!
Method A
Update your AT&T Lumia 1020 to Windows 10 mobile and interop unlock it.
Change the registry value of “DataStore” to “C:\EFIESP\efi\Nokia” in “HKLM\SOFTWARE\Microsoft\MTP”.
Connect the phone to PC, open “Phone\PCONF”, copy “config.pcn” to your HDD and use a HEX editor to open it.
Change P5217_ATT (HEX: 50 35 32 31 37 5F 41 54 54) to P5217 (HEX: 50 35 32 31 37 00 00 00 00) at offset 0x10, then save it.
Copy modified “config.pcn” back to “Phone\PCONF” and overwrite it.
Restart your phone and use flashing tools like “thor2.exe” to flash unbranded RM-875 rom!
Method B
Download the update cab (Lumia 1020 ONLY)
Then copy the cab file to an empty folder, e.g. “c:\cab”.
Download and install the tools (Thanks WojtasXda!)
Connect the phone to PC, then run cmd and go to “iutool.exe” folder (default: Program Files (x86)\Windows Phone Kits\8.1\Tools\bin\i386), type
Code:
iutool.exe -p c:\cab -V
The phone should restart and install updates automatically (ignore ERROR: 0x8024a110)
Flash unbranded RM-875 rom!
My AT&T Lumia 1020 is carrier unlocked, the method does not relock my phone.
We knew AT&T changed the Platform ID (P5217_ATT) to avoid flashing RM-875 rom (P5217). The flashing tools check the platform info values of the phone and the DevicePlatformID string from the rom. Lumia 635/820 has SD card, and the device info in the registry can be changed. After the phone checking and installing updates, it is unbranded. Thus the updates can change the Platform ID info of the phone. (Thanks pankaj981 for this guide)
I find the update cabs of an unbranded RM-876 phone (flashed RM-875 rom). Then using the iutool.exe to update AT&T RM-877 manually. After that, I flashed RM-877 with RM-875 rom successfully (Method B). Finally, I find “config.pcn” contains Platform ID. Thus for an interop unlocked phone, Method A may be easier.
Post here if you have any questions!

Lumia 640 AT&T
I can't seem to find the config.pcn on Lumia 640 AT&T, but I got access to EFIESP by using "C:\EFIESP" or "\EFIESP" (both work) for the DataStore.
I see from another forum users can edit the xml files found in "Windows Phone\Phone\Windows\Packages\DsmFiles", so is there anything else I can edit to remove the _ATT for Lumia 640 AT&T?

qodexc said:
I can't seem to find the config.pcn on Lumia 640 AT&T, but I got access to EFIESP by using "C:\EFIESP" or "\EFIESP" (both work) for the DataStore.
I see from another forum users can edit the xml files found in "Windows Phone\Phone\Windows\Packages\DsmFiles", so is there anything else I can edit to remove the _ATT for Lumia 640 AT&T?
Click to expand...
Click to collapse
I've download the AT&T 940 rom (RM1073_059X0B8), and I find file "pconf.bin" in "PLAT" partition has the infomation about platform ID; but i'm not sure whether the modified file takes effect.
Code:
NAME=P6204_ATT
SWVERSION=02177.00000.15184.36000
To access "PLAT" partition ,the drive letter may need to be assigned. The information about mounted drive is in registry "HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices"
But the registry editors like vcREG have the limit:
binary: when you read, the app will return 20 bytes, regardless of how long the binary is.
Click to expand...
Click to collapse
The key is stored in binary and may be longer than 20 bytes.
The "PLAT" partition is FAT12, I don't know if W10M were able to read it.
If you have an international Lumia 940 and it have a lower ROM version, you could use Fiddler to find all the update cabs like this.
If there is one which has the Platform ID, you could use iutool to update your AT&T 640 with that cab. This may be a lot work to do.
If just using the way here then updating to W10M?
Lumia 640 has SD card, and the DeviceTargetInfo can be edited in WP8.1. If the edited AT&T 640 was updated to W10M, the Platform ID may be changed. I'm not sure, but this seems easy to try.

e-Pig said:
I've download the AT&T 940 rom (RM1073_059X0B8), and I find file "pconf.bin" in "PLAT" partition has the infomation about platform ID; but i'm not sure whether the modified file takes effect.
Code:
NAME=P6204_ATT
SWVERSION=02177.00000.15184.36000
To access "PLAT" partition ,the drive letter may need to be assigned. The information about mounted drive is in registry "HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices"
But the registry editors like vcREG have the limit:
The key is stored in binary and may be longer than 20 bytes.
The "PLAT" partition is FAT12, I don't know if W10M were able to read it.
If you have an international Lumia 940 and it have a lower ROM version, you could use Fiddler to find all the update cabs like this.
If there is one which has the Platform ID, you could use iutool to update your AT&T 640 with that cab. This may be a lot work to do.
If just using the way here then updating to W10M?
Lumia 640 has SD card, and the DeviceTargetInfo can be edited in WP8.1. If the edited AT&T 640 was updated to W10M, the Platform ID may be changed. I'm not sure, but this seems easy to try.
Click to expand...
Click to collapse
It's definitely that pconf.bin values that needs to be edited. That plat partition is preventing me from flashing other roms, I'm getting "image targeting check failed Device: Nokia.MSM8926.P6204_ATT.1.1, Image: Nokia.MSM8926.P6204". I tried updating to Windows 10 with modified DeviceTargetInfo, but I still get this error when I try to flash a CV rom.
I don't think I can edit the registry for "HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices", it showed something like "system.[]" for value. I think the only way is for someone to provide an international 640 platformid cab and use iutool.

qodexc said:
It's definitely that pconf.bin values that needs to be edited. That plat partition is preventing me from flashing other roms, I'm getting "image targeting check failed Device: Nokia.MSM8926.P6204_ATT.1.1, Image: Nokia.MSM8926.P6204". I tried updating to Windows 10 with modified DeviceTargetInfo, but I still get this error when I try to flash a CV rom.
I don't think I can edit the registry for "HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices", it showed something like "system.[]" for value. I think the only way is for someone to provide an international 640 platformid cab and use iutool.
Click to expand...
Click to collapse
It seems that this registry editor can read/write binary values. But I don't have W10M phone now to test it.
PS. I tested the ffu vhd on PC. The Plat partition is hidden, it is not work even if you write the information about assigning drive letter in HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices. The drive letter will not appear until the hidden attribute been clear. It is hard to edit partition attribute on a phone. Maybe the only way is getting a cab that updating the Platform ID.

Thanks for testing and confirming the registry method doesn't work. Well there is nothing to do but wait for a .cab file.

Don't **** with the PLAT partition unless you know what you are doing.
I know someone who applied an update to PLAT partition that wasn't for their device, and doing that hard bricked it.

One thing you could try is modifying the exact same registry keys for the RM-977 as mentioned in my thread here. Now the only reason the update will kick in is if the OS/firmware version is lower than what's on your device.

Hello! When using method # 2 I get the message:
[1] Started device **********************************
[1] Transferring files started
[1] Transferred file 1/4
[1] Transferred file 2/4
[1] Transferred file 3/4
[1] Transferred file 4/4
[1] Transferring files complete: 4 files
[1] Update started
[1] Installation failed (HRESULT = 0x801882c1)
[1] Failed (0x801882c1)
ERROR: 0x801882c1
Command failed. (HRESULT = 0x801882c1)
Using Windows 10 Pro. On Windows phone 8.1 update 1
Help in this issue please

Please, explain me this method with one Nokia Lumia 1520 AT&T ?
Thank you.

someone can upload the PCONF file from a lumia 1520 NON at&T?
regards

It works.
Just wanted to say thanks to e-Pig, and let people know that this works (at least on my machine). I have an AT&T Lumia 1020, 32gb version:
I used the cab method (Method B) as described.
For flashing, I used this tutorial http://forum.xda-developers.com/showthread.php?t=2515453. Disabling driver signing in Windows 10 is a pain, so for flashing I instead emulated Windows 7 in VirtualBox. This required using the USB passthrough feature when connecting the phone to the PC.
The ROM I used was RM875_3051.50009.1424.0003_RETAIL_eu_euro1_211_03_447991_prd_signed.ffu , which I obtained from the mr.crab site mentioned in the flashing tutorial http://www.mrcrab.net/nokia.html. So, no need for Naviform+.
Everything good so far.

Fantastic, thank you!
First try using the cab file method to unbrand my ATT RM-877.
The "tools" when I install them, I don't get an i386 folder where the iutool should be. I got a zip of the i386 folder and used that. Everything I tried to do generated ERROR: 0x80070490. It was a driver issue. I tried it on a different machine, successfully unbranded an ATT 1020 and flashed it with unbranded US CV 059W473. I tried a repair of the Lumia USB drivers from Programs and Features on the original machine, tools work there now.
Question: Do you happen to have the ATT-branded cab file, in case someone wanted to reverse the process?

nunzio1961 said:
Please, explain me this method with one Nokia Lumia 1520 AT&T ?
Thank you.
Click to expand...
Click to collapse
I don't have Lumia 1520. I downloaded the RM940 rom (059V5B2) and find the Platform ID is the same as Lumia 640. It's in pconf.bin located in "PLAT" partition.
Code:
NAME=P6081_ATT
PKEY=3
SWVERSION=02540.00019.14484.37000
I haven't found a way to modify this file manually. An update cab to modify this file is needed, just as Lumia 640.
Sorry for not helping.

tyler200298 said:
someone can upload the PCONF file from a lumia 1520 NON at&T?
regards
Click to expand...
Click to collapse
This is from RM938 (059V3K8).
Code:
NAME=P6081
PKEY=3
SWVERSION=1028.3534.9200.10517

e-Pig said:
This is from RM938 (059V3K8).
Code:
NAME=P6081
PKEY=3
SWVERSION=1028.3534.9200.10517
Click to expand...
Click to collapse
Hello, thanks
so this is config.pcn code from a no brand lumia 1520.
i'll try to modify one inside the phone
---------- Post added at 06:46 PM ---------- Previous post was at 06:38 PM ----------
e-Pig said:
This is from RM938 (059V3K8).
Code:
NAME=P6081
PKEY=3
SWVERSION=1028.3534.9200.10517
Click to expand...
Click to collapse
hello, can you zip this file and upload? so i can see complete hex

tyler200298 said:
Hello, thanks
so this is config.pcn code from a no brand lumia 1520.
i'll try to modify one inside the phone
---------- Post added at 06:46 PM ---------- Previous post was at 06:38 PM ----------
hello, can you zip this file and upload? so i can see complete hex
Click to expand...
Click to collapse
Of course.
From here I find the Platform ID update cab of ATT 1520. A non-ATT 1520 is still needed to find the cab to debrand.

e-Pig said:
Of course.
Click to expand...
Click to collapse
thanks my friend

ATT L925
Hello, will it be possible to de-brand a AT&T Lumia 925 RM-893 using method B? Where can i find the cab file?
Mine is sim unlocked.
Thank you in advance.

Lumia 625
Is this same for lumia 625