Database Develop

PLS HELP ME I HAVE READ THROUGH THIS FORUM

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

Ather's Himalaya Kitchen 0.4 { 07/07/2008 } *Multi-Language*

Hello Guyz...this is my 4th Release....This Version of the Kitchen is coded in C# VS 2008 Professional..
ALL THE PATHS ARE HARD-CODED TO "C:\ather\Himalaya Kitchen"
I have included a help file also which explains all the instructions in detail..but even if u dont understand any thing or are facing a problem..just post it here or email me at
[email protected] (replace "x" with "c")
Requirments :
1. .NET Framework 3.5 (many computer now has this)
2. Windows XP / Windows Vista
3. A Himalaya Device
4. Brain POWER
Instructions :
Welcome and thank you for choosing Himalaya Kitchen V4
This Help file will guide you through all the steps required to Cook your own ROM
The Kitchen Is Available in the Following Languages
English, Arabic, German and Italian
ALL THE PATHS ARE HARD-CODED TO "C:\ather\Himalaya Kitchen"
Once you start the Kitchen you will see that you have a bunch of buttons and Few Tabs....let's discuss each of them
Language Selection:
The Kitchen is Multi-Language Supported From Version 4...Once you Fire up the Kitchen you will see the Available Languages. Choose your suitable language and Continue towards the next Step
Embedded Help :
The Second Tab is the Help tab. from this version the help file is set to display from the "C:\ather\Himalaya Kitchen "...So it does not require any Internet Connection
Dump My Chosen ROM for Me:
Once you press this button a Dialog will open and start dissembling your ROM...BUT before you that make sure you have placed the rom file you want to edit in the directory named "Tools" ...after the dissembling is complete you will get a folder called dump in C:\ather\Himalaya Kitchen\ folder…analyze it and select which files & modules to delete or to add and then press "Process My ROM's HKCU"
ONE MORE IMPORTANT THING. Whatever you do make sure the ROM has at least 0001 bytes of free space or it will never work
Process My ROM's HKCU:
After you press this button. A file by the name "HKCU.reg" will be created in the folder "Tools". Open it with Registry Workshop (a software from Torch Soft)...Once the registry is opened edit it and then save it.....even if you don't want to change any thing in the registry Open it and then save it
Now proceed to next step
Process My ROM's HKLM:
After you press this button. A file by the name "HKLM.reg" will be created in the folder "Tools". Open it with Registry Workshop (a software from Torch Soft) ...Once the registry is opened edit it and then save it ....even if you don't want to change any thing in the registry Open it and then save it
Now proceed to the next step
Re-assemble My New ROM:
When you press this button a file will be created by the name "initflashfiles.dat.txt" in the tools folder and you will be asked to edit it...Now this is the MOST tricky and sensitive part of the kitchen...if you edit this file incorrectly the ROM wont work correctly...some times when you haven't added any thing in the ROM just removed then there is no use of editing it. Leave it as it is and continue. After this step completes a file by the name NK.NBA is created...
BUT IF YOU EDIT IT MAKE SURE YOU RENAME IT FIRST TO "initflashfiles.txt" AND THEN GOTO "Misc Tools" Tab and SELECT IBE 2…AFTER THAT SELECT "Edit" AND PLACE THE RENAMED "initflashfiles.txt" IN THE OPENED FOLDER AND PRESS SPACE TO CONTINUE also do read the Help file of the IBE 2
PS. IF YOU CREATE YOUR "initflashfiles.txt" WITH MY BUILDER...IT WON'T ADD THE 2 EXTRA BYTES...SO NO NEED TO EDIT
Edit new NK.NBA:
If you have changed the ram disk size in the registry, you would need to make the following changes as well in nk.nba:
Once you press this button the NK.NBA will be automatically opened in the Hex Editor
For changing RAM Disk sizes find the following byte sequence, or Go to Address
· 0x004032e8 for WM 5
· 0x0040c2e8 for WM6,
· 0x00456250 for WM6.1
And modify as follows:
FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 08 --> 128MB Program, Memory: RAM Disk= 0MB
FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 06 --> 96 MB program, memory: RAM disk= 32MB
FF FF FF FF FF FF FF FF FF FF FF FF 00 00 80 05 --> 88 MB program, memory: RAM disk= 40MB
FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 05 --> 80MB program, memory: RAM disk= 48MB
FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 04 --> 64 MB program, memory: RAM disk= 64MB
· If you want to change the ROM Date (shown in Start - Settings - Device Information), Open nk.nba in hex editor and go to Address 001c4ab4 and edit it…it looks like "Nov 11 2006" ( In Some ROM's these Values are stored in the HKLM registry )
· To change the ROM name shown in Start - settings - device info , Open nk.nba with a Hex editor and go to address 1C1C18 , line 36
· If you want to change the image/rom version (show on first splash screen bottom right corner), Go to address: 82CDF
search for old version and replace it with exact number of digits.
· If you want to change the rom version shown in the upgrade utility go to address 19 and replace it
Save your file and press build nk.nbf
Building nk.nbf from nk.nba:
After you have edited the nk.nba run this step and a file will be created in the "C:\ather\Himalaya Kitchen\Upgrade" folder * and the upgrade utility will be started automatically
Enjoy cooking and Flash away...
* In case you want to distribute your ROM
Cleanup:
Once you run this step. All the un-necessary files will be deleted from the Tools Directory and once again you will have a clean kitchen J…
Miscellaneous Tools:
Once you select this tab...You will see two options…
1. IBE 2
2. Splash Changer
IBE2 was previously known as "initflashfiles editor + builder"...it lets you build your "initflashfiles.txt" for your OEM packages and also edit previously created "initflashfiles.txt" file to remove the two Extra Bytes
Splash Changer lets you change your "welcomehead.96.png" file...Read the Help of Splash Changer for More Info
MAKE SURE THE IMAGE SIZE IS 240X320....THE TYPE OF THE IMAGE DOES NOT MATTERS
Click to expand...
Click to collapse
Here is a screeny :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credits and Thanks :
Phex for alot of help in Bug-testing, German translation and for being a great Friend
Google, MSDN Libraries and Christian mass for the XVI Hex Editor
and all xda-dev's members
Download Himalaya Kitchen 0.4
Click Here To Download
________________________________________________________________________________________________________
Download Himalaya Kitchen 0.3
Click Here To Download
_______________________________________________________________________________________________________
Download Himalaya Kitchen 0.2
Click Here To Download
______________________________________________________________________________________________________
Download Himalaya Kitchen 0.1
Click Here To Download It​

SYed Ather,
When and where can we download it??

i have finished testing it and will upload it maybe later today

0.1a version of the Kitchen Released

guyz i have seen about 10 downloads but not a single feedback...

ROM Dumper cannot start.

Thanks a lot, the screen shot looks promising. Unfortunately I'm not able to test right now.

atomxdaii said:
ROM Dumper cannot start.
Click to expand...
Click to collapse
what error are you getting..make sure u have >netcf 3.5 and C++ Redistribuatble package installed

Thanks ather90. Is cooking ROM now so easy with this utility.

ather90 said:
what error are you getting..make sure u have >netcf 3.5 and C++ Redistribuatble package installed
Click to expand...
Click to collapse
Thanks ather90. It's working now.

you are welcome....Do let me know the results

ather90,
Can i suggest that the last stage, cleaning stage, deletes all files that are generated inclusive of the nk.nbf file and leave behind the created rom on your next upgrade.

i think you havent read the readme..the ROM image is moved automatically to Upgrade folder for the upgrade utility to find it..you can copy it from there

i was successful in using your rom kitchen Ather90 using C_ShekharWM6.1.1cR16.P32_public image as the base nk.nbf on my
Qtek 2020 WM6.1 AKU 1.0 (32MB pagepool+ 16MB RAMDisk)
I am a newbie to this and have only had my device for a few weeks.I was wondering if you could point me in the right direction regarding adding/removing files from the image.For example say i wanted to add some program that was in cab format like Poorlyduck's Vista Dialer from his Vista suite,using a cab extractor to extract the files and the reg settings of the cabnet,this leaves me with a windows folder with the needed files and a reg file to import,mabey into both the hkcu and/or hklm, or link me to a good tutorial to read over mabey regarding adding the OEM files posted here http://forum.xda-developers.com/showpost.php?p=1549211&postcount=1
Mabey you could also add ms_.nbf editing for ExtROM within the kitchen
On i different note i have an idea i hope could be implamented regarding the nk.nba/nk.nbf in step 4-5 , would it be possible to use a checkbox or slider to input changing RAMDisk size and coresponding reg entry into your kitchen?

hello hagis..im glad you were sucessfull..the addition and deletion of files is a complicated method...you ll have to manually search for files that you want to remove and add..for example
lets say you want to remove pShut XP
delete these icons
pShut xp.exe
pshutxp.lnk
Shutxp.lnk
if its an old version there will be also skin files of it
now if you want to add S2p for example :
copy all the files from the OEM package in to the dump folder (if they are in a folder take them out of it)
then if they have registery settings open the specific registery area and import the RGU file..now comes the HARD path...you will want windows to create shortcuts for you...when you get the option to edit the "initflashfiles" look at a line and copy it..now paste it in the second line and change the shortcuts to the name of the software ( in this case S2P.lnk)..but make sure that a .LNK file exists there..
if your ROM doesent starts up or when u press start you only get threee things this means that you have corrupted the initflashsiles file..you will have to re-cook again
regarding your second query..its not possible because you also have to HEX edit the file at the second last step..and regarding the extended rom..there is a utily called ER2003Edit..but as far as i remember they were last seen with WM 2003..this is WM 6.1
PM me or email me at [email protected] ( replace X with O ) for furthur details

Thanks for clearing things up for me,is there a very basic rom image you guys work from ?

I use my own Clean ROMS as Base rom..try to create your own or you can use the rom provided with Avis 6.1 kitchen...to create your own Base rom..just dnt add any files when cooking ..just delete files like speeddialer.pshutxp and etc....save the rom and try to flash it..if it works then enjoy...

New version Released guyz

ather90 thanx. http://cid-c6dcd1007b3043af.skydrive.live.com/self.aspx/Ortak/msvcr71.zip msvcr71.dll absent

sorry didnt get you..
i have tested this Kitchen on a fresh installition of XP with .Net framework only

Help! Restore BML3 / STL3

Hi all mates!
I have a problem with my i9000... I explain my problem fast:
I have extracted the BML3 and STL3 of my phone to 2 files .img... I have duplicated this files to a backup and I modified it. Now, I can´t load the original bml3.img and stl3.img because the /dev/block/stl3 doesn´t exists... not are mounted... also when I restart my phone, the /efs/ directory is empty, and the phone dont ask me for the pin... (obviously, I don´t have call service) but, If I copy the nv_data.bin to /EFS directory, the phone ask me for the pin and I can make and receive calls...
Do you have some idea to load the original stl3 & bml3 files in the phone????
-------------------
well, now I have put the bml3 and I reboot, all is ok, but when I try to put the stl3 and I obtain this message:
dd if=/sdcard/stl3.img of=/dev/block/stl3
/dev/block/stl3: cannot open for write: Invalid argument
but the stl3 partition exist! and I rooted the phone
ls /dev/block/stl*
/dev/block/stl1
/dev/block/stl10
/dev/block/stl11
/dev/block/stl12
/dev/block/stl2
/dev/block/stl3
/dev/block/stl4
/dev/block/stl5
/dev/block/stl6
/dev/block/stl7
/dev/block/stl8
/dev/block/stl9

all is done!!!
I had to reflash the phone after recover the bml3... Now all is OK but my IMEI... it has the famous 004999010640000 number but that is other history

awia said:
all is done!!!
I had to reflash the phone after recover the bml3... Now all is OK but my IMEI... it has the famous 004999010640000 number but that is other history
Click to expand...
Click to collapse
Simply make a Call from your Phone: +49 9901 0640000 xD

Aery said:
Simply make a Call from your Phone: +49 9901 0640000 xD
Click to expand...
Click to collapse
xDDDDDDDDD

Why in the Gods name you messed around EFS in that way?
If your IMEI is messed up, I recon so is your WIFI MAC and BT address too.

Richthofen said:
Why in the Gods name you messed around EFS in that way?
Click to expand...
Click to collapse
because I looking for restore my original IMEI number
the WIFI MAC and BT also are changed?? I don´t have any problem with the wifi... but I don´t tested the BT...

I don´t have the MAC of wifi and BT ............
but wifi works good....... at the moment!

surprise!
when I recovered the product code and I restarted the phone, it shows me the WIFI MAC !!!!
but the KIES reg continues showing me the XXXXXXXXXXXXXX product code...

awia said:
surprise!
when I recovered the product code and I restarted the phone, it shows me the WIFI MAC !!!!
but the KIES reg continues showing me the XXXXXXXXXXXXXX product code...
Click to expand...
Click to collapse
Do you try to copy the files nv_data.bin and nv_data.bin.md5 into /efs and then remove the battery without turning off the phone?

quiron said:
Do you try to copy the files nv_data.bin and nv_data.bin.md5 into /efs and then remove the battery without turning off the phone?
Click to expand...
Click to collapse
no........ I try it now

awia said:
no........ I try it now
Click to expand...
Click to collapse
any news about that?

quiron said:
any news about that?
Click to expand...
Click to collapse
The same result

i had a similar issue with my nv_data files. i backed them up to my computer, then copied a set of nv_data files over from my gf's phone, and it gave the same issue. when i copied my original ones back, it still wouldn't work. seems the signature of the file is changed, and the phone doesn't accept it. your phone has a set of backup nv_data files on the phone in the efs partition. delete your bad nv_data files, shut off your phone, and turn it back on. the phone should recognize the files are gone, and use the backup files......worked for me
edit: just to clarify, only delete the .bin and .md5 files, not the .bak files.
leave: nv_data.bak & nv_data.bak.md5

Hello,
I'm having the same problem but only have the bml3.bak and the nv_data.bak and nv_data.bak.md5.
I updated the firmware to JPH and make the changes to restore the product code to KOR from XEC the original for my country and operator.
The bml3 was corrupted and in the next reboot the phone didn't ask for the pin code of my SIM card.
I try to restore the original files, but the efs is empty or write protected, with root explorer a mount to r/w and only if I connected by usb the phone ask for the pin, and I can access to phone network and can make calls a recive it but the IMEI is the tipical 004999010640000.
The stl3 is imposible to read or write from it. The nv_data.bin can not be reinstalled because pin is not recognise and in a reboot the files are restore to previous state.
I think the nv_data are store somewhere and when the file system is mounted as r/w the efs directory is recovery from there.
Efs directory only has and .android directory, and nv_data.bin, nv_data.bin.md5, .nv_state. No imei directory, etc
awia you has some good news, i'm from spain to, it's possible to speak somewhere in spanish.
Do you recomend to take the phone to SAT?
I bought it in the Telefonica FlagShip Shop in Madrid.

Hello,
An update over my previous comments.
If I used rootexplorer to paste .nv_data.bak and .nv_data.bak.md5 that I backup before and then go to efs directory and mount r/w and immediately copy the previous pasted files, then the process start and ask for my pin, and then the imei is restored. The problem is that this is temporal and only works in the current session, if you reboot the phone then you must to make the same steps. I don't know if I can make a sh to do this step more automatically, because I don't know how and what rootexplorer remount in r/w permissions, may be someone can help me in this tasks.
In my previous comment I said that the pin prompt only has shown if the phone is usb plug in but this is not true, works in all conditions.
About the process, I suppose the bml3 contains all the information and in the bootload process this bml3 set the stl3 and mount over efs directory but for some reason this is not working with my phone because the changes over the bml3, I don't know how can I reestablished it. I use the redbend_ua for that and the bml3 are now like my backed-up one, but still doesn't work.

:( EFS folder empty = 12mb of 12 used! How to restore unzipped backup?

Hi all..
So Im pretty new at flashing androids, been using ubuntu for years and am quite familiar with the terminal as well as computers in general. I made the silly mistake of not doing a complete backup of my phone with CWM before flashing with CyanogenMod 9 and now my EFS folder is "empty" but still with Zero free space... giving the "usual" errors":
1) Corrupt or incorrect ( FAKE) IMEI number. (International Mobile Equipment Identity)
2) No Network and Signal ( calls, sms and mobile Internet not working)
3) No base Band or Unknown Baseband
4) Sim card lock missing
as described in the [A.I.O. Helpline] My Android Solutions.
CWM seems to have created a copy/paste backup of my EFS folder (not .zip and not .img, just a folder) on sdcard/efs/backup but the EFS folder is read only and root manager cant paste into it. I've read that deleting the EFS folder should recreate it, I tried in terminal with
Code:
rm -r /efs/*
and got the reply:
Code:
rm failed for /efs/lost+found, Directory not empty
How do I go about restoring the EFS folder?

Finally figured out how to copy/paste into the read only EFS folder! I have searched probably about a million threads, all say to "just copy paste" into the efs folder... but never how to do it when its locked because of read only permissions.
I think im one step closer.. but still not quite there yet.
The way to get write permissions is simply to open terminal and get root access and unmount the efs directory using:
Code:
umount /efs
After that, I could open the efs directory in Root explorer and mount it as R/W. Automatically, I get some default files there created by the system which I can delete and then I could copy/paste my backup into the efs directory. Bang, mobile network running, but baseband version is still unknown. Also, my IMEI number is the generic one, not my unique one
The problem now, is that on reboot my EFS directory goes blank again... anyone know how to continue from here?

Snarlster said:
The problem now, is that on reboot my EFS directory goes blank again... anyone know how to continue from here?
Click to expand...
Click to collapse
Solution:- Reason is you had Jumped from GB to JB (should be on ICS before JB), so now you need to
1) Download Root Explorer from Play Store and use it to
2) Search you internal SD card for sdcard/backup/efs
3) Copy nv_data.bin, nv_data.bin.md5 and nv.log paste them into /efs in your Phone memory
4) Reboot to get back your original IMEI
If it gets lost after reboot
Remedies for those who have a efs backup
If you Have a Backup and you want to restore it, this is one method Here or you can use the restore function in the app that you used to back it up
If restoring the efs folder or you have a nv_data.bin backup but if you write nv_data.bin or .nv_data.bak it's being deleted on every boot, than follow this [GUIDE] how to get IMEI to stick across reboots to make it stick.
BUT try this method first
Copy Paste EFS folder with root explorer, after paste , power down phone and reboot into recovery and wipe cache before rebooting....this worked for some

xsenman said:
Solution:- Reason is you had Jumped from GB to JB (should be on ICS before JB), so now you need to
1) Download Root Explorer from Play Store and use it to
2) Search you internal SD card for sdcard/backup/efs
3) Copy nv_data.bin, nv_data.bin.md5 and nv.log paste them into /efs in your Phone memory
4) Reboot to get back your original IMEI
If it gets lost after reboot
Remedies for those who have a efs backup
If you Have a Backup and you want to restore it, this is one method Here or you can use the restore function in the app that you used to back it up
If restoring the efs folder or you have a nv_data.bin backup but if you write nv_data.bin or .nv_data.bak it's being deleted on every boot, than follow this [GUIDE] how to get IMEI to stick across reboots to make it stick.
BUT try this method first
Copy Paste EFS folder with root explorer, after paste , power down phone and reboot into recovery and wipe cache before rebooting....this worked for some
Click to expand...
Click to collapse
Thank you, I had read each thread linking from those threads but it was good for me to do it again!
Flashing the EFS folder with Heimdall gave me the same results as copy/paste, setting the ownership/permissions made no difference in both cases, always empty on reboot.
FINALLY, these are the steps I took to get my phone "working".
1: Odin re-installed the stock I9000JVJV9_OJVJV9_JXJV6.tar file found on sammobile.com as well as the Pit file found on 4shared
2: This gave me an error on bootup... something about "failed to mount dbdata", this was solved with Odin as well by selecting only PDA and using the dbdata.rfs.tar found on hotfile.com.
After this, my phone booted up with the generic imei, a very welcomed change to the previous no imei thats been bothering me! Also, my baseband is showing, the EFS directory is full of files and google play is working... and fortunately, my carrier doesnt seem to care about the generic imei
I'm still going to get my imei back, but first things first! Its time to do some backing up!
Current plan is:
1: Install ClockworkMod
2: BACKUP
3: replace nv_data.bin with the backed up one.
4: reboot / see if my IMEI number is back.
5: BACKUP
6: install CyanogenMod
I hope this helpes someone down the road.. dont be shy on letting me know if my hours of pain helped you!
And... one more thing, my phone is Samsung Galaxy S GT-I9000
Thanks again for pointing me to the right direction

did you only used the PDA included on the I9000JVJV9_OJVJV9_JXJV6.tar file? and how did you use teh dbdata.rfs.tar? thanks.

efs Folder Contents
Hi Guys,
I am hoping you can help me with a problem.
I have a brand new GalaxyS2 i9100, which is on ICS 4.0.4 IMM76XWLPW - XXLQ6 Baseband version, Kernel 3.0.15-1056084 [email protected]#3(SMP PREEMPT Wed Aug 22 2:55:24 KST 2012). The phone is not rooted, but what I did was make a copy of my efs folder to my PC, obviously incorrectly, using My Phone Explorer.
I thought it was just a matter of uploading the folder to my PC and it could be used in an emergency, I thought it would just copy the folder.
What I have discovered, is that all the contents of the efs folder are now on my PC and the efs folder in my phone is empty!!!!
I am now unable to get the files, back into my phones storage.
When I enter *#06# into my phone, the IMEI number shows up and is correct.
I also have a copy of the original efs folder, on my External SD Card.
I have not changed anything else on the phone, other than removing the efs folder contents to my PC. Is there a way, to get all the contents back into my phones efs folder without having to "Root," using say....Emulator or something?
Would a "Hard Reset" on this unrooted stock phone, restore the efs folder to factory settings??
Thank You.

dixielee said:
Hi Guys,
I am hoping you can help me with a problem.
I have a brand new GalaxyS2 i9100, which is on ICS 4.0.4 IMM76XWLPW - XXLQ6 Baseband version, Kernel 3.0.15-1056084 [email protected]#3(SMP PREEMPT Wed Aug 22 2:55:24 KST 2012). The phone is not rooted, but what I did was make a copy of my efs folder to my PC, obviously incorrectly, using My Phone Explorer.
I thought it was just a matter of uploading the folder to my PC and it could be used in an emergency, I thought it would just copy the folder.
What I have discovered, is that all the contents of the efs folder are now on my PC and the efs folder in my phone is empty!!!!
I am now unable to get the files, back into my phones storage.
When I enter *#06# into my phone, the IMEI number shows up and is correct.
I also have a copy of the original efs folder, on my External SD Card.
I have not changed anything else on the phone, other than removing the efs folder contents to my PC. Is there a way, to get all the contents back into my phones efs folder without having to "Root," using say....Emulator or something?
Would a "Hard Reset" on this unrooted stock phone, restore the efs folder to factory settings??
Thank You.
Click to expand...
Click to collapse
I would be careful with that, if you have your efs folder on your sd card, I think it would be better to copy/paste them with root explorer back before reboot... though this is just a guess. In any case, since you have the folder on your PC, then at least you have the backup you need if you get into serious trouble.
If it did reset, please tell us about it in case someone else needs this info later

efs file restore
Thank you so much. After days of not having calling and texting functions available from a corrupted efs folder, who would have thought that a simple copy and paste of the backed up efs to the system would help greatly?

Hey, this worked for me, but I still can't connect to some carriers.

Sim unlock 6.0.1

Ok, So i have been messing around with the NV_data.bin file on my S6. I have backed up the Original EFS folder. Used T-Mobiles app to Temp unlock the phone then backed up the unlocked EFS folder. I then used VBinDiff to see what T-Mobile changed in the NV data. Turns out the main thing that changed is just a few things. I imagian that if someone just changed the data on this and not the "end date" hex data that it would result in a perm unlock can someone confirm this? I have to wait another 30 days before I can test this theory.
0x3930A changed from 01 to 00
0x3960C changed from 30 to 62
0x3960D changed from 54 to 2F
0x3960E changed from 03 to 54
0x3960K changed from 20 to 0E
0x3960L changed from 30 to D8
0x3960M changed from 03 to 36
Attached is a picture of it.

Really? 64 views and no takers? Please someone help me verify this. The other 2 gs6's i have are for sprint and verzion and they operate quite diffrent when it comes to nv_data.
To do this back up your efs folder. Copy the backup to your computer. Install notepad++ and the hex editor plugin. Open nv_data.bin with notepad++ and then go to plugins. Next click hex then view hex. Next all you have to do is go down to the lines i specified in the first post and change the values. Then just replace the one on your phone with the edited one.
Make sure you have an unmodified untouched backup of your efs folder and store it in a safe place. If the mod does not work then you can always just restore the original one.

I am getting a G920T in a approximately 2 weeks. As soon as I get it I'll test it and post the results. Btw, do you have any proof that this method works?