Related
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!
I had a Galaxy i5700 a few years ago but it has been sitting gathering dust. I changed to an iPhone 3GS and now onto a Galaxy S3 which I love.
I want to get my old i5700 back in use as a prepaid phone on a different network but I have a few issues.
1 - it needs to be unlocked. I flashed the firmware along time ago to get rid of network branding but I'm now trying to use it on the 3 Ireland network and I think it is still locked on 3 UK. When I turn on with the sim in it says "sim network unlock code".
2 - I don't have the Play Store, only the old Market app and I can't seem to update to the play store. I tried to download what I think is the APK for it but when I try to install is says "there was an error parsing the package".
I kow this is an old phone but can someone point me in the right direction? Thanks!
How To
Hello! With regard to Play Store, you must update the device to version 2.2 or higher! If you can not install it because you, Presumably, the 2.1 is the latest version available officially for the Galaxy Spica.
As regards the release to use other sim driving is this:
UPDATED# 24/4/2011
Hello another time.
I dicovered a new method to unlock the Spica for all carriers.
This method can be public, is no related with imei generation, I do it public for all Spica users.
You need be root, root explorer and one hex editor, I use UltraEdit, you can use the trial version.
First step, backup efs folder.
With root explorer, copy the efs folder from your Spica to your sd memory, save two copies in your pc, one is a backup, no modify it, and the other copy is for modify nv_data.bin to unlock the Spica.
Second step, edit nv_data bin and paste in efs folder.
Open nv_data.bin with your hex-editor, I use Ultraedit.
Go to line 433a0h, you only need do changes in this line.
Look at this first image, is your locked sim nv_data.bin:
You need do this changes, is a unlocked sim nv_data.bin:
Edit line 433a0h, do changes in hexadecimal area, not the encrypted area, only two values, change 01 to 00, see the pictures, and save the nv_data.bin modify.
Now the nv_data.bin is sim unlocked.
Put the new nv_data.bin in your sd card.
Copy with root explorer from your sd card, and paste in to efs folder, overwrite the original nv_data.bin.
Reboot and enjoy
PD: Other values, and changes in near lines too are valid, this disable the check sim.
If you like my work, buy me a english dictionary, is very bad Donate
Click to expand...
Click to collapse
Via Samdr*id
Seraser thanks for the guide, Samdr*id*com Forum user. I would put the link but I have 10 posts and then the forum does not allow that to prevent spam.
Hi,
So i have the generic IMEI (004999010640000/01) on my device and I have no backup of the EFS. Can I get it Back? Thanks!
Edit: Actually, while installing a Custom ROM I ended up formatting all the partitions except ExtSD Card. I wanted a clean install and did not know that IMEI in android is on EFS. Dumb.. I know.
Solved
amit.talukdar said:
Hi,
So i have the generic IMEI (004999010640000/01) on my device and I have no backup of the EFS. Can I get it Back? Thanks!
Edit: Actually, while installing a Custom ROM I ended up formatting all the partitions except ExtSD Card. I wanted a clean install and did not know that IMEI in android is on EFS. Dumb.. I know.
Click to expand...
Click to collapse
Try to find the full stock ROM with the PIT file, and flash it with repartition.
Best case scenario: you will have efs restored
Worst case scenario: you will end with the stock ROM, without efs, ready to be sent out for WARRANTY repair
EFS Floder deleted with no Backup
spamtrash said:
Try to find the full stock ROM with the PIT file, and flash it with repartition.
Best case scenario: you will have efs restored
Worst case scenario: you will end with the stock ROM, without efs, ready to be sent out for WARRANTY repair
Click to expand...
Click to collapse
HI, Thanks for your reply. I already tried that.
I used adonis.pit & I9500XXUEMK9_I9500ODDEMK9_I9500DDUEMK9_HOME.tar. But no change in IMEI status. It is still the generic one.
But I was wondering... If it is a fact that there is no "Hardware" IMEI in this device and the IMEI is in the EFS folder. Then is there any way I can replace the generic imei with the original one?
amit.talukdar said:
HI, Thanks for your reply. I already tried that.
I used adonis.pit & I9500XXUEMK9_I9500ODDEMK9_I9500DDUEMK9_HOME.tar. But no change in IMEI status. It is still the generic one.
But I was wondering... If it is a fact that there is no "Hardware" IMEI in this device and the IMEI is in the EFS folder. Then is there any way I can replace the generic imei with the original one?
Click to expand...
Click to collapse
You stated that you do not have backup => I assumed that no backup is available.
In SGS 4 there is nothing like hardware IMEI, bcs all info is stored at efs partition.
any try to force the "custom" efs upload would lead you to legal issues, so if you have successfully restored "stock" condition of your phone, I'd recommend you to go to service center claiming that it was the result of OTA update.
amit.talukdar said:
HI, Thanks for your reply. I already tried that.
I used adonis.pit & I9500XXUEMK9_I9500ODDEMK9_I9500DDUEMK9_HOME.tar. But no change in IMEI status. It is still the generic one.
But I was wondering... If it is a fact that there is no "Hardware" IMEI in this device and the IMEI is in the EFS folder. Then is there any way I can replace the generic imei with the original one?
Click to expand...
Click to collapse
Here is an EFS backup/restore app from Play. :good: Root needed.
Please click Thanks, if it was useful for you! :good:
tripod74 said:
Here is an EFS backup/restore app from Play. :good: Root needed.
Please click Thanks, if it was useful for you! :good:
Click to expand...
Click to collapse
Have you ever imagined that the RESTORE option may exist only if the BACKUP was made before?
no? so, young Einstein, tell me please from what source the efs restore would originate?
your Pampers?
spamtrash said:
Have you ever imagined that the RESTORE option may exist only if the BACKUP was made before?
no? so, young Einstein, tell me please from what source the efs restore would originate?
your Pampers?
Click to expand...
Click to collapse
Did I said that is will restore without backup? It is ment for the others reading this thread to backup quickly and safely, nothing else. Naturally, it can not create backup from the "fresh air". Hope you can solve your problem, I wish you a nice day.
spamtrash said:
Have you ever imagined that the RESTORE option may exist only if the BACKUP was made before?
no? so, young Einstein, tell me please from what source the efs restore would originate?
your Pampers?
Click to expand...
Click to collapse
OK, was there really the need to be such a ****?
And for the OP if you use the search button there is a thread pages pages long with detailed info and step by step terminal commands that might help you
Sent from my GT-I9505 using XDA Premium HD app
He wasn't being a ****. People post some really stupid **** to threads without even reading OP's or putting their brain into gear first.
Spamtrash's point stands.
spamtrash said:
You stated that you do not have backup => I assumed that no backup is available.
In SGS 4 there is nothing like hardware IMEI, bcs all info is stored at efs partition.
any try to force the "custom" efs upload would lead you to legal issues, so if you have successfully restored "stock" condition of your phone, I'd recommend you to go to service center claiming that it was the result of OTA update.
Click to expand...
Click to collapse
thanks a lot.
Obagleyfreer said:
OK, was there really the need to be such a ****?
....
Click to expand...
Click to collapse
Sorry, did not understood your wording (can be an effect that I grown in different environment what resulted with other than yours standards and wording, apologies for that).
Did you mean, if it was really a reason to be sarcastic, while seeing the totally rubbish post, asking the @op to perform nonsense, useless and irrelevant in his situation actions because its author was not able to read the problem with understanding?
If so, the answer is: yes, indeed, it was a need to be sarcastic. Maybe the author would stop himself from posting nonsenses in the future.
Solved:Hex Editor Route
1- Flashed Stock android- adonis.pit & I9500XXUEMK9_I9500ODDEMK9_I9500DDUEMK9_HOME.tar
2- Rooted using CF-Auto-Root-ja3g-ja3gxx-gti9500.tar
3- Installed TWRP Recovery using goo
4- Downloaded Hxd (Windows Hex editor- Freeware)
5- Using ES Explorer (Root Mode) copied EFS folder to Windows and started opening all files-
Made following changes-
Change 1: In nv_data.bin change the addresses to this-
00188000: FF FF FF FF 4D 50 20 30 2E 38 30 30 00 00 00 49
00188010: 4E 55 00 00 00 00 47 54 2D 49 39 35 30 30 5A 4B
00188020: 41 49 4E 55 00 00 00 00 00 00 FF FF FF FF FF FF
This reads as - MP 0.800...INU....GT-I9500ZKAINU......
Change 2: efs\FactoryApp\ serial_no
Put the serial no in hex and changed permission to system and removed write access from system. After reboot it reverted to zero so made it read only for system (changed permissions from with in ES file manager)
Rebooted and it worked
I know.. I am lucky to get it back working.. have made 4 backups from dropbox to google drive now
I got one board replacement ... but it comes with generic IMEI - how do i write a new one ( i have the one that was corrupted board ) i want to write that imei to the new board ? how to do ?! hexedit will work ?!
You have the IMEI at under battery spot, so get the number than change the IMEi with IMEi Changer.
Take a look on google for a app for this.
Or with Notepad + ADB
Cya!
amit.talukdar said:
1- Flashed Stock android- adonis.pit & I9500XXUEMK9_I9500ODDEMK9_I9500DDUEMK9_HOME.tar
2- Rooted using CF-Auto-Root-ja3g-ja3gxx-gti9500.tar
3- Installed TWRP Recovery using goo
4- Downloaded Hxd (Windows Hex editor- Freeware)
5- Using ES Explorer (Root Mode) copied EFS folder to Windows and started opening all files-
Made following changes-
Change 1: In nv_data.bin change the addresses to this-
00188000: FF FF FF FF 4D 50 20 30 2E 38 30 30 00 00 00 49
00188010: 4E 55 00 00 00 00 47 54 2D 49 39 35 30 30 5A 4B
00188020: 41 49 4E 55 00 00 00 00 00 00 FF FF FF FF FF FF
This reads as - MP 0.800...INU....GT-I9500ZKAINU......
Change 2: efs\FactoryApp\ serial_no
Put the serial no in hex and changed permission to system and removed write access from system. After reboot it reverted to zero so made it read only for system (changed permissions from with in ES file manager)
Rebooted and it worked
I know.. I am lucky to get it back working.. have made 4 backups from dropbox to google drive now
Click to expand...
Click to collapse
Amit, your instructions were spot on !
Fixed everything for me.
I've been narrowing it down and figured it was something to do with EFS but i've been researching this all day and stumbled upon your post GJ I dont think i would have edited the .bin file with a hex editor to read it ..
Just to point this out for the rest of the folks watching, but in order for this to work the phone has to have the nv_data.bin file. Some devices, e.g. mine, don't have the file at all.
amit.talukdar said:
This reads as - MP 0.800...INU....GT-I9500ZKAINU......
Change 2: efs\FactoryApp\ serial_no
Put the serial no in hex and changed permission to system and removed write access from system. After reboot it reverted to zero so made it read only for system (changed permissions from with in ES file manager)
Click to expand...
Click to collapse
Sorry but, what you mean here is that I replace the serial number inside the serial_no file with I9500ZKAINU?
amit.talukdar said:
1- Flashed Stock android- adonis.pit & I9500XXUEMK9_I9500ODDEMK9_I9500DDUEMK9_HOME.tar
2- Rooted using CF-Auto-Root-ja3g-ja3gxx-gti9500.tar
3- Installed TWRP Recovery using goo
4- Downloaded Hxd (Windows Hex editor- Freeware)
5- Using ES Explorer (Root Mode) copied EFS folder to Windows and started opening all files-
Made following changes-
Change 1: In nv_data.bin change the addresses to this-
00188000: FF FF FF FF 4D 50 20 30 2E 38 30 30 00 00 00 49
00188010: 4E 55 00 00 00 00 47 54 2D 49 39 35 30 30 5A 4B
00188020: 41 49 4E 55 00 00 00 00 00 00 FF FF FF FF FF FF
This reads as - MP 0.800...INU....GT-I9500ZKAINU......
Change 2: efs\FactoryApp\ serial_no
Put the serial no in hex and changed permission to system and removed write access from system. After reboot it reverted to zero so made it read only for system (changed permissions from with in ES file manager)
Rebooted and it worked
I know.. I am lucky to get it back working.. have made 4 backups from dropbox to google drive now
Click to expand...
Click to collapse
Bro. I will try this tomorrow morning. If I need any help can I PM you. Please please...
---------- Post added at 06:09 PM ---------- Previous post was at 06:02 PM ----------
Strephon Alkhalikoi said:
Just to point this out for the rest of the folks watching, but in order for this to work the phone has to have the nv_data.bin file. Some devices, e.g. mine, don't have the file at all.
Click to expand...
Click to collapse
So what do we have to do in this case...
Scary Samsung...
Send it in to Samsung and have them fix it. It's likely the only legal way to get your IMEI back if you didn't make a backup.
please,.help me for I9500 imei
please,.help me for I9500 imei
So atlast I permanent interop unlocked my lumia 525 and still able to install windows 10 update
Thanks to
@vcfan for the tip that we can add interop unlock files in any .reg files in windows\packages\registryfiles folder and also for his live interop unlcker..... (BTW after modifying my software.reg and interop unlocking my phone I am still able to install windows 10)
@WojtasXda for the additional_entries.reg file whick I used to unlock my phone
.And others....
BTW @vcfan I've attached my software.reg file which I used to interop unlock my phone can you add the additional capabilities unlock that you unlocked by your app other than those unlocked by WojtasXda
OTHERS DON'T USE THIS BECAUSE THIS NOT A TUTORIAL OF PURMANENT INTEROP UNLOCKING LUMIA 525 OR ANY OTHER PHONES
IF YOU USE THIS THEN I'M NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE
Hi there, great discovery, I am also a user that has one of the phones that have the OEMSettings.reg file read-only and I have been trying to add the lines to lots of reg files and always got a on herd reset so would like to ask if you did a hard reset after editing the software.reg file (you probably did) and if it worked right, and if you are sure you kept your interop unlock after the reset?
Ranomez said:
Hi there, great discovery, I am also a user that has one of the phones that have the OEMSettings.reg file read-only and I have been trying to add the lines to lots of reg files and always got a on herd reset so would like to ask if you did a hard reset after editing the software.reg file (you probably did) and if it worked right, and if you are sure you kept your interop unlock after the reset?
Click to expand...
Click to collapse
Thnx dude and ya same thing happened to me 5 days ago when I tried to modify the language.reg files and failed but today when I used the software.reg file it worked
@souma_rox , im happy you got it working. sorry, I've been busy with another project so I didn't have enough time to try all the different files and see which one is the optimal one to use, but im glad you've found it.
im attaching a text file with all the reg entries to unlock all the capabilities that are programmed in a stock wp 8.1 rom. also included are some other tweaks such as full fs access.
vcfan said:
@souma_rox , im happy you got it working. sorry, I've been busy with another project so I didn't have enough time to try all the different files and see which one is the optimal one to use, but im glad you've found it.
im attaching a text file with all the reg entries to unlock all the capabilities that are programmed in a stock wp 8.1 rom. also included are some other tweaks such as full fs access.
Click to expand...
Click to collapse
so if i just paste all of these lines at the end of software.reg file like the additional_entries.reg file of wojtas it will work right?????
souma_rox said:
so if i just paste all of these lines at the end of software.reg file like the additional_entries.reg file of wojtas it will work right?????
Click to expand...
Click to collapse
it should as these are the exact entries my app appends to the end of OEMSettings.reg for the permanent unlock, and that works.
will this work on a 520 from at&t?
@vcfan it seems the lines you provided prevent the phone from getting updated to windows 10 mobile, the phone always getting stuck in the update and requiring a re-flash of the ROM,, on the other hand the lines @WojtasXda provides for his ROM Rebuilder seem to work just fine, do you happen to know what lines might cause that?
Also sorry for posting so late but I didn't want to post before testing everything (slow and fast ring) and also trying to remove the full mtp access lines from your file, it seems to not be related to that.
I updated to wm10 after vcfan permanent interopunlock.... 3 times I used vcREG templates.
augustinionut said:
I updated to wp10 after vcfan permanent interopunlock.... 3 times I used vcREG templates.
Click to expand...
Click to collapse
So the file "C:\Windows\Packages\RegistryFiles\OEMSettings.reg" is kept as is when updating the phone? From 8.0 to 8.1, too?
I think so...
The files run in LUmia 520
??
thanks..
i just replace the reg file of my stock rom with this reg file..but nothing happened..
Riyad_ said:
i just replace the reg file of my stock rom with this reg file..but nothing happened..
Click to expand...
Click to collapse
I think that only works with live unlock.
Rivo17 said:
I think that only works with live unlock.
Click to expand...
Click to collapse
No bro...i just interop unlocked my phone again..though i tried so many times..finally i got this..all i have to do is just unlock bootloader of my phone with sbl3 partition.then in mass storage mode i get software.reg file from that then i modified the file with capabilities.then put the file again in my mass storage then resetted my phone and it works ... i will write a tutorial on this. soon..
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