Related
Can someone point me to the info to manually create ms_.nbf. I know there are no sw tools at this time to do this on the BA.
TIA[/b]
You don't need to create an ms_.nbf file. There is no way of doing this easily on a BA, but what everyone does is unlock their extended Rom using the tool on the wiki then modifying all the files manually. The wiki has a really great section on custmising extended ROMs on BAs.
HTH
Fin
Thanks, but I have been cooking Ext Rom's for quite some time now. My problem is I have to upgrade 140 units in the field. I used to use the SD card method, but it would be much easier if I could create my oun cooked ms_.nbf file that I could post for download to the field. There has to be a way to do it, I beleive it take a Unix workstation to compile it. Anyone know how?
Hi Cruzzer,
it is possible (I reckon anyway). There's now a similar tool that I've written for Magicians, Alpines and Universal devices - but it doesn't currently work with BlueAngels - seems it has a different parameter in the header for one of the fields I currently hard code
I'm not sure when I would get time to fix the problem though - might be a couple of weeks at least .....
But if you fancy a challenge http://forum.xda-developers.com/viewtopic.php?t=31106&sid=35aa5e7aeb5b4899d82e5391af4cd4b7 will give you the algorithm and hints on how to write one yourself if you're really desperate.
Bal
I am not a C programer, so I can only hope you have time to make it work for BA.
TIA for all your hard work!
Hi Cruzzer,
I finally got round to sorting this out.
Send me a pm if you still need to create nbf files for BA and I'll send you the app and instructions.
Bal
Cant you post the instructions and soft here ?
Bal, please post here for all.
Thanks
Hi Guys,
I'll post here as suggested. Give me a day, as I've another issue to deal with first :roll:
Bal
Cruzzer said:
Can someone point me to the info to manually create ms_.nbf. I know there are no sw tools at this time to do this on the BA.
TIA[/b]
Click to expand...
Click to collapse
The simpliest method.
1. Take MS_.NBA (a decrypted version of MS_.NBF). Open it in any hex editor, and search for bytes "EB FE 90 4D 53 57 49 4E 34 2E 31 00" ("ыРMSWIN4.1", there would be "FAT16" string a bit lower). The string should be found near offset 0x70000. Extract everything starting from the place you've found and up to the end of file to a file named "extrom.img"
2. Open "extrom.img" in WinImage, edit it as you like, save the file
3. Open the hex aditor and place modified "extrom.img" to the same place in MS.NBA file where it was before extraction.
that's all. Convert NBF to NBA and flash your ROM.
The same method cannot be used on Universal. It has TFAT16 instead of FAT16, WinImage knows nothing about TFAT and destroys FAT table. But there is a simple workaround.
Hi Guys,
here's the application.
It's a windows GUI which will also extract both splash screens embedded in the rom.
It's all pretty self-explanatory - but as a word of advice ... don't change any of the ROM parameters, unless you fancy having a play. You'll know what I mean when you try it out.
As usual - use this at your own risk ... plus I don't have a BA, so the only test I've been able to perform is to decode, re-encode and compare nbf files. I suggest you also carry this basic test out on your shipped extended roms.
Any problems just let me know and I'll offer what help I can.
Have fun.
Bal
The attachment has been removed as it is superseded by the one further down.
Works like a charm!!!!!!!!!!!!
Thank You!
Hi Cruzzer,
Just to let you know ... there may be a problem with altering and saving the ROM header information. Avoid that for now while I track the problem down and fix it!
Otherwise, if you don't change the ROM header info all works well.
Hey ho
Bal
OK - all fixed.
New version (1.1) is attached - please use this instead of the one above.
Bal
The attachment has moved to this thread http://forum.xda-developers.com/viewtopic.php?p=191164#191164
This is so that I only have to update one thread when the application goes up a version.
I can't seem to find any attachment for download in the message. Am I missing something?
Never mind, forgot to log into the forum before opening mouth <G>
I recently Upgrade to the Latest Ivan (with ramdisk) WM05 ROM.
I wanted to change the BOOTLOGO.
I tried the link where it asks to put BOOTLOGO.EXE and BOOTLOGO.BMP into the windows Directory then it asks to add registeries ... but doesn't explain how to add registries.
if anyone could help me with this... as how would u add Registry on the phone...
http://forum.xda-developers.com/viewtopic.php?t=47898&postdays=0&postorder=asc&start=150
hey
i matrix thanks for helping me..
the link u provided i have already read through it..
Posted: Sat May 20, 2006 22:51
--------------------------------------------------------------------------------
Quote:
Boot screen is a 'special feature' addition for TuMa v1.4. It was to try and comfort people with a nice boot screen since everyone panics with the colour bars. TuMa v1.4 was also designed to be a 'feature rich' out of the box solution ... but the feedback I've had has been to go the other direction.
Anyways ... if you want to have the bootscreen in ANY other ROM, all you need to do is the following:
You'll find the application and TuMa v1.4 Bootlogo attached in the ZIP.
To make it run at startup, just include the following registry entries, and place the files from the ZIP in /Windows directory.
Code:
[HKEY_LOCAL_MACHINE\init]
"Depend32"=hex:14,00,1E,00
"Launch32"="BootLogo.exe"
Once you've done that - any of the other CABs I created can then be used, or just replace the BootLogo.bmp file. You will need to ensure that the BMP file is in the SAME format as the example. 8 bpp, and same file size & resolution if you want to change it. That's all that is required.
so short explaination:
1. Make a BootLogo.bmp or use default WM5
2. Copy BootLogo.exe and BootLogo.bmp to \Windows
3. Crete these registry entryes into registry
4. Reboot
how do i do step 3 ... how do i create registry into registry as there r no steps mentioned.. pls advice
Download `total commander` for ppc (google it)
in total commander (TC), go to the top (the root) directory `\` and you should see a `\\`. Double click it and go to `registry`
You should see something like
HKCR
HKCU
HKLM
where HKLM is HKEY_LOCAL_MACHINE
do your guess work from there
hanmin said:
Download `total commander` for ppc (google it)
in total commander (TC), go to the top (the root) directory `\` and you should see a `\\`. Double click it and go to `registry`
You should see something like
HKCR
HKCU
HKLM
where HKLM is HKEY_LOCAL_MACHINE
do your guess work from there
Click to expand...
Click to collapse
I have resco registry explorer
but when i get to the folder.. i don't know how to add... specially the demand32 hex:14,00,1e,00
is it binary or string or multi string or dword... don't know what to do pls help.
Re: hey
[HKEY_LOCAL_MACHINE\init]
"Depend32"=hex:14,00,1E,00
"Launch32"="BootLogo.exe"
1. Launch your resco registry explorer whatever regedit utility u use
2. Browse to HKEY_LOCAL_MACHINE\init
3. Create a new Binary Value with
Value name: Depend32
Value Data: 14 00 1E 00
4. Create a NEW String Value
Value name: Launch32
Value data: BootLogo.exe
5. Save if u need to. exit
6. Reboot
have fun.
anyway i also attached the regedit program i use.
imatrix
Re: hey
imatrix said:
[HKEY_LOCAL_MACHINE\init]
"Depend32"=hex:14,00,1E,00
"Launch32"="BootLogo.exe"
1. Launch your resco registry explorer whatever regedit utility u use
2. Browse to HKEY_LOCAL_MACHINE\init
3. Create a new Binary Value with
Value name: Depend32
Value Data: 14 00 1E 00
4. Create a NEW String Value
Value name: Launch32
Value data: BootLogo.exe
5. Save if u need to. exit
6. Reboot
have fun.
anyway i also attached the regedit program i use.
imatrix
Click to expand...
Click to collapse
I copied the BOOTLOGO.exe and BOOTLOGO.bmp to the Windows Directory.
I added the String value LAUNCH32 VALUE BOOTLOOGO.exe
that way easy
with the Binary when i add DEPEND32 on the VALUE there's already 0000 and i can only input after that... anyway after doing that...
resco doesnt ask for saving anything.. so i close the folder and when i reopen it the new value r there... i restart but no bootlogo.
don't know what am i doing wrong.
ANYONE
OK I added the registries copied the bootlogo.bmp and bootlogo.exe to the windows folder...
Restarted nothing happens... Same old 4 colors.. can someone confirm this method works... pls
you said: with the Binary when i add DEPEND32 on the VALUE there's already 0000 and i can only input after that... anyway after doing that...
that where u went wrong.
download regedit utility i posted, and try that again.
imatrix
imatrix said:
you said: with the Binary when i add DEPEND32 on the VALUE there's already 0000 and i can only input after that... anyway after doing that...
that where u went wrong.
download regedit utility i posted, and try that again.
imatrix
Click to expand...
Click to collapse
yeh when i tried adding binary value under Depend32...
000 are already on the screen.. but when i input the data... and click ok..
the screen shows 14 00 1e 00 it doesn't show 0000 anymore. but when i reboot it doesn't work.. .so
anyway i will try your regedit.. and then post.. i hope it solves the issue.. don't know why but those 4 colors are annoying make the phone look fake or somethin.. haha
hey
Hey Imatrix.
thanks for ur tool.. that worked ... but i mean i still can't completely get rid of 4 colors.. the phone still reboots to 4 colors and then switches to the bootlogo.bmp.... its better then before.. but how do i change the intial 4 colors to O2 wall paper or somethin.. pls advice. thanks
Hi, i've just dialled *#06# to get my IMEI and my imei number has changed from 352*********** to 00004**********.
Does anyone currently know of a way to change the imei number back? Thanks in advance.
Your Friend
Phil
I noticed on JM6 and JMA that it made my IMEI number incorrect as well, so when I entered it, it didn't recognise it to change the CSC.
Not sure if there is a way, hopefully so!
I'm sticking with JJ7 now on my replacement tab until we get a proper recovery mode in place.
I had this on my galaxy S. Solved it by backing up the efs directory to be safe. you need root. then delete everything in the efs dir except nv_data.bak then rename it to nv_data.bin and reboot. It should rebuild the efs dir correctly and put the imei back.
But this only works if the nv_data.bak file has not been modified in anyway otherwise it will rebuild with the 0044 imei.
Lordao
Is a corrupted IMEI, can create you problems
I had it too before, but because I deleted also all the .bak files in the EFS folder...
You can recovery in 2 ways:
1st:
I suggest you to delete the nv_data.bin and the nv_data.md5 in EFS folder using rootexplorer then rename the .nv_data.bak to nv_data.bin and the .nv_data.md5.bak in nv_data.bin.md5 (same suggested by lordao); You can also delete the md5 files because it will rebuild it by itselfs.
2nd:
In the bad case the 1st solution will not work, means that your backup files are corrupted and your IMEI is not recoverable.....BUT if you are lucky like I was I recognize that I had a copy in my sdk folder (the one you used when you rooted the Tab!!!) I think the one click root did a backup copy of the nv_data.bin by itself. Grab that file and copy it in the EFS folder (deleting all the other nv_data.bin and nv_data.md5 and relatives .bak that you have in the folder) restart the tab. It will self rebuild the md5. You can make the new .bak files copying the nv_data.bin and rename the copy ad .nv_data.bak
Hope it will help you
Thanks zerocool76 worked perfect!! I now have my imei back. Your a star. Think I will keep a backup of that file. Just in case of future flashing.
diigibio said:
Thanks zerocool76 worked perfect!! I now have my imei back. Your a star. Think I will keep a backup of that file. Just in case of future flashing.
Click to expand...
Click to collapse
Just to know. Where you found the file? In the sdk? Because it would means that your .bak was corrupted too and I'm wondering why..???!!! Anyway glad it was working.I suggest you to backup all the EFS folder
zerocool76 said:
Just to know. Where you found the file? In the sdk? Because it would means that your .bak was corrupted too and I'm wondering why..???!!! Anyway glad it was working.I suggest you to backup all the EFS folder
Click to expand...
Click to collapse
I noticed and fixed this a few days ago.
When I look at my EFS folder backup, done right after rooting the Tab, I can see that nv_data.bak; size 1732608, is a different size, with an earlier creation date than the original nv_data.bin; size 2097152. According to nv.log, my nv_data.bin was corrupted during the time-frame where I was flashing different modems to the Tab while testing the screen timeout bug on JMA, it reports that when nv_data.bak was restored as nv_data.bin the file size was invalid, then says that it restored nv_data.bin, created from scratch I guess, which resulted in the improper IEMI and a serial# of all 0's.
Bell Tab
Roto-JMA firmware
Bell I9000UGJK4 radio
rgbc said:
I noticed and fixed this a few days ago.
When I look at my EFS folder backup, done right after rooting the Tab, I can see that nv_data.bak; size 1732608, is a different size, with an earlier creation date than the original nv_data.bin; size 2097152. According to nv.log, my nv_data.bin was corrupted during the time-frame where I was flashing different modems to the Tab while testing the screen timeout bug on JMA, it reports that when nv_data.bak was restored as nv_data.bin the file size was invalid, then says that it restored nv_data.bin, created from scratch I guess, which resulted in the improper IEMI and a serial# of all 0's.
Bell Tab
Roto-JMA firmware
Bell I9000UGJK4 radio
Click to expand...
Click to collapse
I destroyed my original nv_data.bin editing with a txt editor instead hex editor, plus I deleted baks files for mistake with root manager (no booze when playing with this **** anymore ), I didn't know that the IMEI is encrypted in that file. When I found a copy in my sdk (that I didn't make!?) I restore everything, and after that time I flashed a lots of Firmwares and Modems, but my imei is still ok.I know that a Galaxy S firmware made this issue because it was changing the nv_data and it didn't match anymore with the phone, so corrupted IMEI.I'm wondering if there is a firmware that is doing the same with the Tab
Mine has done the same but with JK5. First noticed when I did the Samsung UK offer thing. Completely different IMEI to whats on the back of my Tab.
Sent from my GT-P1000 using XDA App
Sorry to dig up and old thread, but is this still an issue, can say flashing back and forward from Overcome for example corrupt IMEI etc?
Interesting - are other Samsung devices able to have their IMEI changed?
What this means is that to a technically capable enough thief (or one who knows someone technical enough that will work on credit), Samsung devices are much more valuable: Normally if your mobile got stolen and you had the IMEI, you would report it to your network and they would have it blocked on all networks. Furthermore the police would use the IMEI to prove that the device is yours if it were recovered. If the IMEI can be changed, the device can't be identified and can't be blocked from networks. It only needs slight tweaking to make it appear valid. Don't know about the implications for post-registration call routing, but the thief wouldn't care about that.
In the US, gsm carriers won't block the number - they seem to view stolen phones as a potential new subscriber.
hello,
i have the same trouble ( imei change)on galaxy tab , but the phone work normally (for now ...).
Can i let it so , or could have trouble in future?
because i don't save nv data folder, and i'm not very good to restore rom.The mod was made from my friend.
excuse for my english ,bye
zerocool76 said:
Is a corrupted IMEI, can create you problems
I had it too before, but because I deleted also all the .bak files in the EFS folder...
You can recovery in 2 ways:
1st:
I suggest you to delete the nv_data.bin and the nv_data.md5 in EFS folder using rootexplorer then rename the .nv_data.bak to nv_data.bin and the .nv_data.md5.bak in nv_data.bin.md5 (same suggested by lordao); You can also delete the md5 files because it will rebuild it by itselfs.
2nd:
In the bad case the 1st solution will not work, means that your backup files are corrupted and your IMEI is not recoverable.....BUT if you are lucky like I was I recognize that I had a copy in my sdk folder (the one you used when you rooted the Tab!!!) I think the one click root did a backup copy of the nv_data.bin by itself. Grab that file and copy it in the EFS folder (deleting all the other nv_data.bin and nv_data.md5 and relatives .bak that you have in the folder) restart the tab. It will self rebuild the md5. You can make the new .bak files copying the nv_data.bin and rename the copy ad .nv_data.bak
Hope it will help you
Click to expand...
Click to collapse
i can recovery ANY imei number on ANY android device im currently making a program to do this automaticly
paul.robo said:
i can recovery ANY imei number on ANY android device im currently making a program to do this automaticly
Click to expand...
Click to collapse
Hows that program coming along? I might be in need of it on account of
losing my IMEI on my Galaxy tab.
ktmman said:
Hows that program coming along? I might be in need of it on account of
losing my IMEI on my Galaxy tab.
Click to expand...
Click to collapse
So i got my IMEI no.back but i still don't have a data connection. The strange thing is if i swap sim cards
with my phone it works so im not sure whats wrong with it.
hi all,
I think I am starting to understand how things work with nv_data.bin.
I've been taking snapshopts of it from my device and it looks like nv_data.bin is modified at every reboot. On the other hand, .nv_data.bak doesn't seem to EVER change. It seems to be the initial backup. I don't know if kies or something else would edit it but at least flashing Darky's ROMs does not modify this file.
Now, I know for sure that nv_data.bin contains imei, product code, sales code (not sure which is which product/sales), unlock codes. But there's plenty of other information that changes at every reboot!
So, my first question is:
1) does anyone know what this file contains?
Then, I've read some people suggesting that the code can be changed by editing this file. However, the product code is also contained in a file in /system/csc/sales_code.dat
2) I am not sure, but I suspect that changes in this file might be reflected on nv_data.bin at the next reboot. Do you have any idea if this is true?
thanks
I am about to receive a new phone from Bell with JL2 pre-loaded and I need to unlock it for use on Rogers. I did some reading and it seems that you cannot extract the codes from the nv_data.bin on JL2, you either have to downgrade, or change 1 bit and write the file back. Also, there are some unusual claims being made, such as that even if you change the 1 bit then write the file back, later firmware updates will not re-lock your phone.
If this file was just part of the filesystem then Samsung should be able to write firmware updates that will replace it and would then re-lock your phone.
Am I correct in understanding that this "file" is not so much an actual file, but a filesystem representation of part of the cell chipset? That perhaps when we copy to/from this file we are working directly in the memory of the modem itself, and that the reason the different firmwares can or cannot retrieve the unlock codes is because of the different ways that the firmwares interact with the chipset itself?
Well this is the method I used to unlock my S3 movistar.
requirement:
1 - Have the S3 root
2 - Make a copy of the EFS folder
3 - Hex Editor (I used Notepad + + with the plunging HEX)
4 - Have installed root explorer
We begin:
1 - We copy our EFS folder to your PC and perform a second copy to work with.
2 - Open the file nv_data.bin with Hex editor
3 - We go to the address 00181460 and modify 01 to 00
4 - Save the file
http://forum.xda-developers.com/attachment.php?attachmentid=1135934&stc=1&thumb=1&d=1339936756
5 - copy the file to your S3.
6 - With the Root explorer, activate R / W in the EFS folder and file replace nv_data.bin.
7 - With the root file explorer to give the following permissions:
a. Owner: Read, Write, Execute
b. Changes owner and group: 1001-Radio
8 - Restart the phone.
9 - After restarting check by dialing * # 7465625 # to the continuous network lock ON
10 - Now we copy the file nv.log of your S3 (located in EFS folder)
11 - Open this file and we will eventually see something like this:
Fri June 15 16:39:51 2012: MD5 fail. md5 orignal fd4425f64f7f498230f16cd2234638a '2 '
computed md5' faf1572f4a4dd15f1f9061840cc4b42f '(Rild)
Fri June 15 16:39:51 2012: restored backup NV.
12 - Now we're working copy of our EFS folder
13 - Edit the file nv_data.bin.md5 and see at the dump that matches the first line: 2fd4425f64f7f498230f16cd2234638a
14 - Modify from the dump placing the data in the second line: faf1572f4a4dd15f1f9061840cc4b42f
15 - Save the file.
16 - repeat the 5-6-7-8 but with both files (nv_data.bin and nv_data.bin.md5)
To XXBLG1 add this step:
17 - We copy and rename nv_data.bin and nv_data.bin.md5 to nv_data.bak and nv_data.bak.md5 respectively.
18 - After rebooting check by dialing * # 7465625 # to the continuous network lock OFF
I hope you find it helpful, as always, you are solely responsible, I just indicated to you those steps I've done on my terminal.
This method is based on dagentooboy work http://forum.xda-developers.com/showthread.php?t=761045 so I must thank you for your work and the people he thanked.
LEGAL NOTES (because information should be free for all):
YOU MAY NOT, BY ANY MEANS, USE THIS SOLUTION/CODE OR PART OF IT FOR COMMERCIAL PURPOSES.
DO NOT USE THIS EXTRACTION METHOD COMMERCIALLY
Thanks
Nice work dude, but change the title of the thread ahah .
THX Perfect Telenor Hungary.
Thanks, works for me !
txlibre said:
Well this is the method I used to unlock my S3 movistar.
requirement:
1 - Have the S3 root
2 - Make a copy of the EFS folder
3 - Hex Editor (I used Notepad + + with the plunging HEX)
4 - Have installed root explorer
We begin:
1 - We copy our EFS folder to your PC and perform a second copy to work with.
2 - Open the file nv_data.bin with Hex editor
3 - We go to the address 00181460 and modify 01 to 00
4 - Save the file
http://forum.xda-developers.com/attachment.php?attachmentid=1135934&stc=1&thumb=1&d=1339936756
5 - copy the file to your S3.
6 - With the Root explorer, activate R / W in the EFS folder and file replace nv_data.bin.
7 - With the root file explorer to give the following permissions:
a. Owner: Read, Write, Execute
b. Changes owner and group: 1001-Radio
8 - Restart the phone.
9 - After restarting check by dialing * # 7465625 # to the continuous network lock ON
10 - Now we copy the file nv.log of your S3 (located in EFS folder)
11 - Open this file and we will eventually see something like this:
Fri June 15 16:39:51 2012: MD5 fail. md5 orignal fd4425f64f7f498230f16cd2234638a '2 '
computed md5' faf1572f4a4dd15f1f9061840cc4b42f '(Rild)
Fri June 15 16:39:51 2012: restored backup NV.
12 - Now we're working copy of our EFS folder
13 - Edit the file nv_data.bin.md5 and see at the dump that matches the first line: 2fd4425f64f7f498230f16cd2234638a
14 - Modify from the dump placing the data in the second line: faf1572f4a4dd15f1f9061840cc4b42f
15 - Save the file.
16 - repeat the 5-6-7-8 but with both files (nv_data.bin and nv_data.bin.md5)
17 - After rebooting check by dialing * # 7465625 # to the continuous network lock OFF
I hope you find it helpful, as always you I am solely responsible for your terminal, I just indicated to you those steps I've done on my terminal.
Click to expand...
Click to collapse
good pointer --
I never used the lock bit flip method, so its not by me and I would appreciate it if you would remove my name from the title.
Odia said:
I never used the lock bit flip method, so its not by me and I would appreciate it if you would remove my name from the title.
Click to expand...
Click to collapse
Haha you're so honest!
Yeah you're honest buddy!
Odia said:
I never used the lock bit flip method, so its not by me and I would appreciate it if you would remove my name from the title.
Click to expand...
Click to collapse
OK no problem, I put your nickname in the title because I based on your work and respect for your work.
It is removed, I feel the mistake
can someone make a video for noobs like me ? just don't want anything wrong to happen.
faddys123 said:
can someone make a video for noobs like me ? just don't want anything wrong to happen.
Click to expand...
Click to collapse
James Cameron, Steven Spielberg ?
txlibre said:
OK no problem, I put your nickname in the title because I based on your work and respect for your work.
It is removed, I feel the mistake
Click to expand...
Click to collapse
I understand and appreciate your respect, but lock bit flipping method was not my work
luminouche said:
James Cameron, Steven Spielberg ?
Click to expand...
Click to collapse
What about them?
Hi, I need to get my phone unlocked quick
I have used mskip's TooKit to backup my EFS folder.
It has given me two files: efs.img (20,480 KB) and efs.tar(2 KB)
How do I get the 'nv_data.bin' from 'efs.img'
I am searching the net as well, but for quickness I have asked the question
EDIT:
OK, I found nv_data.bin in the /efs folder
---------- Post added at 11:20 PM ---------- Previous post was at 10:54 PM ----------
Ok, im stuck at step 11:
11 - Open this file and we will eventually see something like this:
Fri June 15 16:39:51 2012: MD5 fail. md5 orignal fd4425f64f7f498230f16cd2234638a '2 '
computed md5' faf1572f4a4dd15f1f9061840cc4b42f '(Rild)
Fri June 15 16:39:51 2012: restored backup NV.
I cannot find this text in my nv.log file
EDIT:
OK, so for some reason I didnt copy the modified nv_data.bin back to my phone... oops!
vinokirk said:
Hi, I need to get my phone unlocked quick
I have used mskip's TooKit to backup my EFS folder.
It has given me two files: efs.img (20,480 KB) and efs.tar(2 KB)
How do I get the 'nv_data.bin' from 'efs.img'
I am searching the net as well, but for quickness I have asked the question
EDIT:
OK, I found nv_data.bin in the /efs folder
Click to expand...
Click to collapse
Those programs make a bit by bit back up of the entire partition, which includes the EFS folder I believe, which is the way to go. I messed up my vibrant once somehow because that partition got corrupted, which disallows writing to the partition, meaning you can't copy over the /EFS stuff. Before doing this, make sure you have a backup! When you punch in *#06# after doing it, and it should still show your IMEI number and not the generic Samsung number. I think it caused some issues w/ the market as well.
In any case, I knew a sim unlock would be out soon. I think ALL Samsung phones have been unlocked similarly since the galaxy series. I'll make sure to try this once I get my phone this Thursday. Maybe someone will make an APK soon.
Yep, worked here in the UK with a SG3 locked to Orange
There is an app on the market galaxy s unlock by helroz and in the what's new it says galaxy s 3 works but there is only one command block can someone check it out haven't got my GS3 yet
Help needed pls.
to All helpers and friends. Huuuuge thanks in advance
Rooted phone. Super Su, Busy Box pro, CWM 3.60, OMEGA ROM.
with ES file explorer or Root explorer.
Follow instructions : yes.
With Root explorer
System EFS Folder : system root (R/W)
nv_data.bin Change owner
owner 1001-radio
Group 1001 - radio or what ever else, IN GROUP i have 0-root, 1000 system
1001 radio....... 1015 sdcard_rw (I Do not HAVE 755) I even dont know where to find (755) and what does it mean.
nv_data.bin change rights to rxw rw- rw- on system and in sd card didnt give me any permission. EVEN ROOTS (R/W).
BACKUP DONE.
I Open (nv-data.bin) directly from system or a copy from sd card with (Hex Editor.apk) on android system
I DONT HAVE (00181460)
I HAVE 00181455 ff ff ff ff ff ff ff ff ff
I HAVE 0014145e ff ff ff ff ff ff ff ff ff
I HAVE 00181467 ff ff 01 00 00 00 00 51 a8
What to do guys. I just feel going in desrt without Water and shoes.
I can pm or upload my original nv_data.bin and nv_data.bin.md5
Android Version 4.0.4
AP : I9300XXALF2
CP : I9300XXLF2
CSC : I9300EURALE1 (is it possible to change this one???)
Kernel 3.0.15-Siyah-s3-v1.0.1
Build number
omega 5.1 - XXALF2
am on SFR france network.
beautyangel said:
to All helpers and friends. Huuuuge thanks in advance
Rooted phone. Super Su, Busy Box pro, CWM 3.60, OMEGA ROM.
with ES file explorer or Root explorer.
Follow instructions : yes.
With Root explorer
System EFS Folder : system root (R/W)
nv_data.bin Change owner
owner 1001-radio
Group 1001 - radio or what ever else, IN GROUP i have 0-root, 1000 system
1001 radio....... 1015 sdcard_rw (I Do not HAVE 755) I even dont know where to find (755) and what does it mean.
nv_data.bin change rights to rxw rw- rw- on system and in sd card didnt give me any permission. EVEN ROOTS (R/W).
BACKUP DONE.
I Open (nv-data.bin) directly from system or a copy from sd card with (Hex Editor.apk) on android system
I DONT HAVE (00181460)
I HAVE 00181455 ff ff ff ff ff ff ff ff ff
I HAVE 0014145e ff ff ff ff ff ff ff ff ff
I HAVE 00181467 ff ff 01 00 00 00 00 51 a8
What to do guys. I just feel going in desrt without Water and shoes.
I can pm or upload my original nv_data.bin and nv_data.bin.md5
Android Version 4.0.4
AP : I9300XXALF2
CP : I9300XXLF2
CSC : I9300EURALE1 (is it possible to change this one???)
Kernel 3.0.15-Siyah-s3-v1.0.1
Build number
omega 5.1 - XXALF2
am on SFR france network.
Click to expand...
Click to collapse
Your problem is the app you used. In the line 00181467 , you must change the 01 to 00.