Database Develop

2 NEW ROMs WM5 (Microsoft BT stack) based on namaich ROM

I have cooked two completely new WM5 ROMs based on namaich ROM.
One in WWE:
ftp://xda:[email protected]_Extracted_Updates/WM5_ArtZ/WM5_ArtZ_WWE.rar
and the second one customized for France:
ftp://xda:[email protected]_Extracted_Updates/WM5_ArtZ/WM5_ArtZ_FRA.rar
I hope you will like them ;-)
EDIT MDAIIIUser (links corrected)
Notes about these releases
__________________________________________________________
This version is based on "BA_5.1.1700_build_14343_Upgrade_V3_by_mamaich" ROM. I have used the original package and rebuild completely this version from that point. It's really a clean version and all modifications have been already tested successfully in TuMa's and Ivan's versions.
In fact, I've been using Ivan's 4 R1 version with Widcomm BT stack, but I find this version "dirty", because many Microsoft BT stack parameters are still in the registry and I found some keys were missing (intentionally?).
Personally, I don't see the interest of using Widcomm BT stack over a version built on Microsoft's... so I decided to go back to the original BT stack. Well, I don't use a headset but I use BT to connect my BA to the audio system in my car and TomTom Navigator 5.21 at the same time. I don't have any problem with this issue.
I find WM5 runs not as fast as WM2k3 on BAs, but I cannot see really an overall difference between Ivan's release and this one.
Do not hesitate to make your comments.
Briefly, I've done the following of changes:
-New Camera 2.3 version,
-New Pocket MSN version,
-SPCS is now disable by default,
-Extended_ROM is on your SD Card and supports AutoStart,
-GPRS disconection settings, WiFi fix, Buttons Fix, Headset Today, CarKit camera patch, Speed Settings (cache and flag values),
-Registry have been cleaned (ordered and double entries deleted) and version numbers have been added
HowTo install this new version
__________________________________________________________
1.- Copy the folders "\Extended_ROM" and "\Tools" in the root of your SD Card
2.- Launch "\Tools\DOC_Tool_1.0.exe" from your SD Card to to get extra storage space under WM2005 (31Mb). This change IS reversible with "DOC_Restore_1.0.exe"
3.- Launch WM5 upgrade
You're done!
When our BA will start, it will automatically install all the CABs located in "\Storage Card\Extended_ROM", though you must validate each CAB.
Some CABS will propose you to "Restart". Click on "Cancel" to continue the Setup. Your BA will automatically restart at the end of the process.
Notes about Extended_ROM
__________________________________________________________
I recommend you to install at least these CABs in the \Extended_ROM directory:
"\Storage Card\Extended_ROM\Album_BA_AKU26_RC23_Midi.cab"
"\Storage Card\Extended_ROM\ArcsoftMMS_3.0.7.6.cab"
"\Storage Card\Extended_ROM\BA_OEM_PA_WModem.sa.cab"
"\Storage Card\Extended_ROM\BA_WW5_ScreenRotate_1.1.cab"
"\Storage Card\Extended_ROM\BA_WW5_SMS_Alert_fix.cab"
"\Storage Card\Extended_ROM\BA_WW5_Wizard2_Tweaks.cab"
"\Storage Card\Extended_ROM\CAB-Cyberon_Voice_Dialer_2.cab"
"\Storage Card\Extended_ROM\CAB-TrueFax-2.09.1-WWE-04Mar05.cab"
"\Storage Card\Extended_ROM\Caller_ID_BA26_Generic_WWE_RC21.cab"
"\Storage Card\Extended_ROM\ClearVue_2.4.386_withoutBP_OzUp.sa.cab"
"\Storage Card\Extended_ROM\Java_10.1.2.76_BA_WWE_unremovable.cab"
"\Storage Card\Extended_ROM\PVPlayer_WWE_AAC.2577.cab"
"\Storage Card\Extended_ROM\Signed_HTC_CameraPatch_2.3.sa.cab"
"\Storage Card\Extended_ROM\ZIP_BlueAngelAKU26_Generic_WWE_RC20.cab"
Description
__________________________________________________________
"Album_BA_AKU26_RC23_Midi.cab" is used by the HTC Camera
"ArcsoftMMS_3.0.7.6.cab", you need this cab for sending MMS
"BA_OEM_PA_WModem.sa.cab" You can use your BA as a modem
"BA_WW5_ScreenRotate_1.1.cab" An icon to rotate your screen will display in "Today"
"BA_WW5_SMS_Alert_fix.cab" will fix a problem receiving SMS alerts.
"BA_WW5_Wizard2_Tweaks.cab" will install a small tool call "Set Security" that will allow you to set ON and OFF SPCS security.
"CAB-Cyberon_Voice_Dialer_2.cab" Voice Speed dialer. Works also with "Bluetooth"
"CAB-TrueFax-2.09.1-WWE-04Mar05.cab" You can use your BA as a Fax
"Caller_ID_BA26_Generic_WWE_RC21.cab" Will show the names in your phonebook instead of the phone numbers
"ClearVue_2.4.386_withoutBP_OzUp.sa.cab" will install clearVue fonts
"Java_10.1.2.76_BA_WWE_unremovable.cab" will install java
"PVPlayer_WWE_AAC.2577.cab" a multimedia player useful to play your MMS files.
"Signed_HTC_CameraPatch_2.3.sa.cab" contains important updates for the camera and camera
CarKit.
"ZIP_BlueAngelAKU26_Generic_WWE_RC20.cab" Zip utility for BA

Downloading... Will try it as soon as downloaded

[deleted]

Was not able to doenload with IE. Used WSFTP. Slow but it worked.
The Upgrade is running ...

YAY! The MP4 recording in Camera works!
The Keyboard lag is still there
Attempting test procedures...

[deleted]

willpower102 said:
i really don't understand what i am doing wrong. I do this stuff all the time so i'm not noob scrambling to learn ftp.
am i connecting to the wrong port?
Click to expand...
Click to collapse
NO : port 21 it's right.
Maybe your personal firewall? If you have installed one, try to disable it before connecting.

Hi,
BT problems are sthe same as in Tuma and Ivan's ROM, still disconnect's when pressing power onn and off.

Hi,
BT problems are still same as in Tuma and Ivan's ROM, still disconnect's when pressing power onn and off.

Hi guys,
According to a few post on xda-developers ( there's a very interesting post at http://forum.xda-developers.com/viewtopic.php?t=45846&highlight=cachesize by TuMa) and wiki.xda-developers, I have used the following parameters to speed up (cache settings) our BA in my ROM:
Registry entry: 0x00001000 (=dword:1000)
Number of sectors: 4096
Cache in kilobytes (KB): 2048
as follows
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS]
"EnableCache"=dword:1
"CacheSize"=dword:1000
"Flags"=dword:10046
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\fsreplxfilt]
"ReplStoreCacheSize"=dword:1000
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\FATFS]
"Flags"=dword:28
"DataCacheSize"=dword:1000
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC\FATFS]
"Flags"=dword:10056
"DataCacheSize"=dword:1000
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS]
"Flags"=dword:14
"DataCacheSize"=dword:1000
but after doing further tests, I have the impression that reducing
CacheSize to 1024KB my BA runs faster and smoothly.
Registry entry: 0x00000800 (=dword:800)
Number of sectors: 2048
Cache in kilobytes (KB): 1024
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS]
"EnableCache"=dword:1
"CacheSize"=dword:800
"Flags"=dword:10046
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\fsreplxfilt]
"ReplStoreCacheSize"=dword:800
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\FATFS]
"Flags"=dword:28
"DataCacheSize"=dword:800
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC\FATFS]
"Flags"=dword:10056
"DataCacheSize"=dword:800
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS]
"Flags"=dword:14
"DataCacheSize"=dword:800
I have also modified some of the default "Flags" values, but I don't recommend you to do that if you don't know exactly what are you doing.
For further information, please check:
http://msdn.microsoft.com/library/d...tml/wce50confatfilesystemregistrysettings.asp
Please, let me know your own experiences.
Regards,

it's very slow the telephone!

FANTASTIC ROM!!
Love the new ROM & extended rom on the SD card. By the way do we have to install all cabs in extended to the device or card?
Simon

You can install the cabs where you want. I installed all the 'system' cabs (such as camera upgrade, MMS tool, etc) to the internal storage, while all the others - to the card.
Is there any method to change the boot logo? Those stripes aren't nice...

Hi guys,
I keep on testing CacheSize and DataCacheSize values and I'm very impressed with the results I get. I show some articles in MSDN which point out that increasing cache size will decrease performance especially using flash memory.
In fact, reducing values (I'm testing =dword:100 (256 in DEC) and =dword:80 (128 in DEC)) my BA works really fast... as fast as WM2k3
I do believe now the fact of increasing values up to =dword:1000 (4096 in DEC), as we were doing, it DOES decrease overall preformance.
There're also other registry key I have modified to add the following values:
[HKEY_LOCAL_MACHINE\System\StorageManager\IMGFS]
"PathCacheEntries"=dword:80
"Flags"=dword:10046
"EnableWriteBack"=dword:1
"EnableDataCacheWarm"=dword:1
"EnableCacheWarm"=dword:1
"EnableCache"=dword:1
"DataCacheSize"=dword:100
"CompactionPrio256"=dword:ff
"CompactionCritPrio256"=dword:ff
"CacheSize"=dword:100
"CacheDll"="diskcache.dll"
"BufferSize"=dword:100
Please, if you can add these values and modify CacheSize and DataCacheSize in this key and all the keys I gave you previously in this thread, I would really appreciate your help.
I will post a new version on Sunday night or monday morning with the optimal values.
Concerning BT disconection at power off, I don't have a solution yet. For me it's not a big deal as I don't have a headset and when I use BT in my car with TomTom, the BA is always turned on but I keep researching.
ArtZ

@simonsalo
Well, install all cabs in the extended rom is not mandatory. But you need the following cabs if you want to use all possibilities of your BA:
Album_BA_AKU26_RC23_Midi.cab (this cab works with your camera)
ArcsoftMMS_3.0.7.6.cab (if you send and receive MMS)
BA_WW5_SMS_Alert_fix.cab (if you want to see the name of the person who is calling you)
Java_10.1.2.76_BA_WWE_unremovable.cab (needed for IE)
PVPlayer_WWE_AAC.2577.cab (used together with ArcsoftMMS)
Signed_HTC_CameraPatch_2.3.sa.cab (camera patch)
@_TB_TB_
This is how I add files (ie: boot splash image) into a nk.nbf file. If you feel confortable with it, you can try.
I use "IMGF tools" and "rgucomp.exe" to modify the ROM.
The process is as follows:
-With xda3nbftool.exe, I convert the original nk.nbf file into nk.nba
-With IMGF tools, I prepare the nk.nba file to antoher format so I can extract, delete, add files (You cannot replace an extinsting file for a new one if you don't delete first the old one) or make a dump of the whole ROM (all directories and files) into a directory (I use the this option). The registry is in two files: default.hv and user.hv
-Then I use "rgucomp.exe" to convert the registry (default.hv and user.hv) into a text (ASCII) file to modify the values.
-Once this is done, I convert the new ASCII files into UNICODE files and I use again "rgucomp.exe" to convert the UNICODE files into default.hv and user.hv
-I copy the new files to the dump directory to replace the old files. I also can add some new files (programs, dll, etc) to the dump directory (This is how I have updated the Camera and Pocket MSN)
-When all this is done, I compile the dump directory to build a nk.nba file.
-Finally, with xda3nbftool.exe I rebuild nk.nbf file

two thumbs up
Promptly, Thanks to Artz Efforts for new cooked WM2K5 ROM, I'm downloading... I do hope your ROM improved and solved some bugs & problems on Others ROM.

I have deleted Cache settings patch from ftp server. This patch is not need anymore with the versions actually on the server. The patch has been already included!

Hi ArtZ
Can i use your cab to setting my device using Ivan v4R1 now??

can you link to IMGF tools please
ArtZ said:
@simonsalo
Well, install all cabs in the extended rom is not mandatory. But you need the following cabs if you want to use all possibilities of your BA:
Album_BA_AKU26_RC23_Midi.cab (this cab works with your camera)
ArcsoftMMS_3.0.7.6.cab (if you send and receive MMS)
BA_WW5_SMS_Alert_fix.cab (if you want to see the name of the person who is calling you)
Java_10.1.2.76_BA_WWE_unremovable.cab (needed for IE)
PVPlayer_WWE_AAC.2577.cab (used together with ArcsoftMMS)
Signed_HTC_CameraPatch_2.3.sa.cab (camera patch)
@_TB_TB_
This is how I add files (ie: boot splash image) into a nk.nbf file. If you feel confortable with it, you can try.
I use "IMGF tools" and "rgucomp.exe" to modify the ROM.
The process is as follows:
-With xda3nbftool.exe, I convert the original nk.nbf file into nk.nba
-With IMGF tools, I prepare the nk.nba file to antoher format so I can extract, delete, add files (You cannot replace an extinsting file for a new one if you don't delete first the old one) or make a dump of the whole ROM (all directories and files) into a directory (I use the this option). The registry is in two files: default.hv and user.hv
-Then I use "rgucomp.exe" to convert the registry (default.hv and user.hv) into a text (ASCII) file to modify the values.
-Once this is done, I convert the new ASCII files into UNICODE files and I use again "rgucomp.exe" to convert the UNICODE files into default.hv and user.hv
-I copy the new files to the dump directory to replace the old files. I also can add some new files (programs, dll, etc) to the dump directory (This is how I have updated the Camera and Pocket MSN)
-When all this is done, I compile the dump directory to build a nk.nba file.
-Finally, with xda3nbftool.exe I rebuild nk.nbf file
Click to expand...
Click to collapse

Artz,
Thanks for this ROM. Seems very stable to me. Is there any way to get the UNLOCK feature as available on TuMA 1.3 and 1.4 on this ROM?
Just tried your cache patch and will report back after some experience.

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

querries about initflashfiles.dat ather90 dark rom

hi
i have been using dark rom for a while, so far great, except that i couldn't figure out how to do mms.
anyway i was going through initflashfiles.dat for which i have few querries
1..
Directory("\My Documents\My Pictures"):-File("Waterfall.jpg","\Windows\Waterfall.jpg")
Directory("\My Documents\My Pictures"):-File("Flower.jpg","\Windows\Flower.jpg")
i couldn't find these jpg in my picture folder or anywhere
2.
Directory("\Windows\Help"):-File("cecmd.htm","\Windows\cecmd.htm")
Directory("\Windows\Start Menu\Programs\Accessories"):-File("Total Commander.lnk","\Windows\Total Commander.lnk")
is there total commander in this rom
3.
Directory("\Windows\Start Menu\Programs\Accessories"):-File("WM5torage.lnk","\Windows\WM5torage.lnk")
i couldn' find wmstorage in this rom also
4.
Directory("\Windows\Start Menu\Programs\Accessories"):-File("PIM Backup.lnk","\Windows\PIMBackup.lnk")
pimbackup is not in accessories
May be i am missing something, please help
thanks

Hehe..actually i felt a lil lazy..so i just removed the stuff from the dump folder and left the initflashfiles like that
its my lazyness

This you shall find in most of the roms. hahaha

ather90 said:
Hehe..actually i felt a lil lazy..so i just removed the stuff from the dump folder and left the initflashfiles like that
its my lazyness
Click to expand...
Click to collapse
so it means:
1: i can remove these codes form the file
or:
2: i can add the programs ( but still not understanding how to put new programs in dump folder)

well yes you can remove them..becareful though
to add the files..i explained you earlier
place all the files in the dump folder except the option.xml and in the initflashfiles.txt
discard the option.xml and open the initflashfiles with a text file and copy its contents..then paste it in the MAIN (which u get before compiling ) initflashfile and ur done
again, BE SURE TO REMOVE THE 2 EXTRA BYTES ADDED BY NOTEPAD, which are FF and FE
Regards, Ather

ah-ha
i wish it was that simple for me
but i am trying hard..
i have the cab files... dump folder has exe.....bit lost here
can only wish for a detailed example...

jirrah said:
ah-ha
i wish it was that simple for me
but i am trying hard..
i have the cab files... dump folder has exe.....bit lost here
can only wish for a detailed example...
Click to expand...
Click to collapse
Hi jirrah, for cooking the rom, you have to use OEM packages, you have a very useful list made by Ather at http://forum.xda-developers.com/showthread.php?t=333359
Just remember to:
ather90 said:
ONE MORE IMPORTANT THING. Whatever you do make sure the ROM has at least 0001 bytes of free space or it will never work​
Click to expand...
Click to collapse
ather90 said:
place all the files in the dump folder except the option.xml and in the initflashfiles.txt
discard the option.xml and open the initflashfiles with a text file and copy its contents..then paste it in the MAIN (which u get before compiling ) initflashfile and ur done
again, BE SURE TO REMOVE THE 2 EXTRA BYTES ADDED BY NOTEPAD, which are FF and FE
Regards, Ather
Click to expand...
Click to collapse

Nicely done
if u need any more clarification..im here..all of us are here

thanks i think i am on right track,
WHAT SHOULD BE THE ADEQUATE SIZE OF ROM, i.e HOW many programs we can add??
i am onto the IBE in hima kitchen 4, trying to figure it out

fmvl said:
Hi jirrah, for cooking the rom, you have to use OEM packages, you have a very useful list made by Ather at http://forum.xda-developers.com/showthread.php?t=333359
Just remember to:
Click to expand...
Click to collapse
ONE MORE IMPORTANT THING. Whatever you do make sure the ROM has at least 0001 bytes of free space or it will never work
can you please explain this, how we can find about this thing.

At the end of the option "Re-assemble my new ROM" you will get that info.
{
"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"
}

well unfortunately there has been no soulution for that..if u get a weird Build OS error at the Last step..it means that the ROM is filled..

thanks fmvl you are a good teacher....
and thanks to ather for his wonderul rom, which i am trying to understand and not to mention his kitchen.. great stuff...
i am still trying to figure out to edit initflashfiles.dat by IBE (what does it means),,,
is there any way to manually edit the initflashfiles.dat and delete the last 2 bites mentioned...
thanks

jirrah, maybe ather can explain how to use the IBE, I use the tools provided at the "C:\ather\Himalaya Kitchen\Hex Edit" folder to edit my initflashfiles.dat.txt.
I've copied a initflashfiles.dat.txt file to "C:\ather\Himalaya Kitchen\Hex Edit" folder. I always make my changes in this file, and at the end (save and close) I run a new batch file (in the same folder) with this code:
Code:
CLS
@Echo This Will Remove the FF and FE from your InitflashFile
@Echo Place the File here
@Echo njoy Automation
@pause
@explorer.exe C:\ather\Himalaya Kitchen\Hex Edit
@CLS
@Echo " Press any key to Remove the Bytes "
@pause
XVI32.exe initflashfiles.dat.txt /S=del.xsc
@pause
At the builing process, when we are prompted to edit the initflash.dat.txt file I just copy the file from the "C:\ather\Himalaya Kitchen\Hex Edit" folder to "C:\ather\Himalaya Kitchen\Tools" folder.

some oem packages contain dll files, rgu, dsm without an initflashfiles.
as far i understand i hve to copy all dll, rgu,dsm in dump folder .. even the dsm or rgu are of 0 bytes...
rgu contain the registry keys setup for that dll..
then we have to process the HKCU and HKLM in the kitchen...
But when i open the HKCU and HKLM those rgu enteries are not added up.... or the add up later,, i even checked after reassembling...
am i doing something wrong.
thanks

yes..you have to import it by Registery Workshop after you get the prompt to Edit HKLM and HKCU

Oh i see
as i remember inanother thread you advised to:
"
as far the OEM pacages are concerned..its a lil bit hard..first download the required OEM then extract it in a seperate folder...then delete the option.xml from it..then copy the files,shortcuts,RGU's,DSM's and paste them into the dump folder..dnt touch the initflashfiles.txt file yet !
"
and that i was doing, thanks for clearing
Now do we have to mention any thing in the initflashfiles about these dll or rgu files which are dumped

im sorry for that..i must have been sleepy that time
nono..no refrence needed in initflashfiles file for this..the initflashfile file only holds the shortcuts

alright....
what about dsm files, do i need to put them in dump even they are of 0 bytes...(in dump of your rom, i dont see dsm files)
and in RGU where should i import when i am processing HKCU or in HKLM, as many RGU have HKLM enteries while others have HKCU enteries...

the DSM are useless for this kitchen..but are useful for others (if they want to extract the packages using PKGTool by Bepe)
as for the RGU's its better export in both, HKCU and HKLM..but i think one would be enough ...you can always try and tell us

TotalFire's ROM Cooking Guide [Unfinished]

TotalFire's ROM Cooking Guide
I have been requested to write a simplified guide on how to cook ROMs For Xperia, as I have just started please be patient and ignore any empty posts for now.
This guide is for anyone who wants to learn how to cook ROMs for Xperia, you dont need any knowledge other than being able to flash a ROM on your Xperia
If any of the information stated is incorrect please tell me and i'll change it.​
Tutorial Layout:
1: Tutorial Layout
2: Setting Up The Kitchen
3: Cooking Your First ROM
4: Customizing Your ROM
5: Customizing Using Autorun
6: Fixing BuildOS Error's
Credits:
Bepe & Gtrab for the kitchen
Anyone else I forgot to mention

Setting Up The Kitchen​
The Kitchen is where all the files in the ROM are kept and where there put together into a ROM which is flashed. There are mainly two types of kitchens, an automated kitchen and a visual kitchen, in this tutorial I will be using a automated kitchen which was made by bepe and modified by gtrab. The only modification I did to the kitchen was to make it rename the ROM to RUU_signed.nbh so that it could be flashed from the PC. in this tutorial I will explain the filesystem used in the kitchen.
In the root of the kitchen you will find 4 folders, they are OEM, SYS, ROM and Tools, below I will explain whats in each folder and what it does.​
OEM
The OEM folder contains all the customizations made by the OEM or in this case chef. In the folder you will find lots of folders which begin with PACKAGE, these are most often applications, registry changes or both. The name can indicate which phone they come from for example a package which is called "PACKAGE_Kovsky_Camera" comes from the Kovsky (Xperia) and a package called "PACKAGE_Rhodium_PhoneCanvas" comes from the Rhodium (Touch Pro 2). Inside a Package you could find many different filetypes, every package has at least a dsm file inside, this is a identifier file. The dsm files name will have loads of random numbers and letters in such as "d9dd6d62-02d6-48d7-9764-18ac81aff3ad.dsm", this is it's unique identity no other package will have the same ID. Most Packages will also have a rgu file, an rgu file contains registry changes for the device, a package can contain only one rgu file and it must have the same name as the dsm file. Make sure when writing a rgu file to have the first line say "REGEDIT 4" and the last line must be empty, if this is not done the rgu will be ignored. One more filetype to look out for is a provxml file this contains registry changes just like the rgu but can be called anything and you can have as many provxml's as you want in a package, the registry edits are written in xml. The last file to look for is an "option.xml" file, these are used only by the kitchen to tell it if the package should be used, these are not needed but without one the kitchen uses the package without giving you a choice. The "option.xml" files can be made manually or generated with Ervius Package Creator but its easy enough to make it manually so I usually do. OEM Packages can be extracted from official ROMs and unprotected ROMs, you can also convert cab's into oem packages using Ervius Package Creator or doing it manually, later on in the tutorial I will add a guide on how to using Ervius Package Creator (manually doing it is too complicated). CABs can be installed without converting them to OEMs but the more CABs you have the longer it takes for the customization to finish when you first install the ROM, I will also show you how to install CABs without converting them to an OEM in a later tutorial, the use of this is if a CAB doesnt convert properly with Ervius Package Creator and you dont want to convert it manually.
ROM
In the ROM folder you will find the folder XIP and the file "OS.nb.payload", the "OS.nb.payload" file contains things such as the splashscreen, usually this file is not edited and the splashscreen is overwritten by a package in OEM. The "OS.nb.payload" is usually changed when upgrading the SYS folder because "XIP.bin" contains the kernel files which is inbuilt in the "OS.nb.payload" file. In the XIP folder there is boot.rgu file which contains registry entries used by windows mobile and isnt used by the OEM or chef, it is used exactly as an rgu file would in a package in the OEM folder. When upgrading to a new build of windows mobile this folder will be upgraded, it will need to be ported properly to xperia for it to work but i'll add a guide for that in a later tutorial.
SYS
The SYS folder contains all the files used by windows such as themes and applications like office mobile. Inside the SYS folder there are many other folders such as MediaOS (Windows Media Player) and WindowsLiveIM(Windows Live Messenger) These are basically packages made by windows similar to the OEM packages. I dont need to go into as much detail as I did with the OEM because the only time you use this folder is when you either swapping images to change skins or upgrading the windows mobile build. I will show you how to upgrade the SYS folder in a later tutorial because some of the files in SYS are device specific and resolution specific so you cant just take a SYS folder and overwrite your old one.
Tools
The Tools folder contains all of the applications the kitchen uses to build a ROM. I dont need to go into any detail because you never need to touch any of the files in the Tools folder but if you intrested, you can open the cook.bat file in the root of the kitchen which should tell you more about which applications do what.
Other than the 4 folders in the root of the kitchen is 4 files, they are Cook.bat, CustomRUU.exe, SYSVersion.exe and XVI32.exe Shortcut, below I will explain what each file does.​
Cook.bat
This files runs all of the tools in the kitchen to build to ROM.
CustomRUU.exe
You should have seen this file before, it is used to flash a ROM
SYSVersion.exe
This application checks the version of each individual SYS folder, useful to check the SYS build
XVI32.exe Shortcut
This application is used to HEX edit files, this can be used to HEX edit the ROM to change the default date, i'll show you how to do this at a later date.
Download the Kitchen Here​

Cooking Your First ROM​
I feel the best way to learn to cook ROMs is to get familar with the cooking process. In this tutorial you will cook a ROM using Gtrabs/Bepes kitchen and end up with RUU_signed.nbh will can be flashed on your xperia, hopefully this will give you an sense of what cooking is like.
Step 1
Extract the kitchen you downloaded in post 2 to any place on you computer, I have my kitchen on the desktop. Please make sure you have framework 3.5 installed onto your pc as its required.
Step 2
Run the file Cook.bat, a command prompt will open up shortly followed by a application called BuildOS. BuildOS lets you chose which packages to cook in your ROM without having to delete them every time. Only packages with an option.xml file will be shown meaning if its not there it, you will have to make one or else it will be cooked in without giving you a choice. As this is an early tutorial i recommend you like all packages in for now incase you remove required packages accidently. Now press the play button and wait until it says at the bottom left corner "done", once "done" appears close BuildOS.
{
"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"
}
​
Step 3
After closing BuildOS, two Command Prompts will open, wait for one to close. Once one has closed you'll have one command prompt asking for you to chose a compression method, like in the picture below. What you do is press enter and an application called XVI32 will open, this is an HEX editor. Now you need to choose which compression method you want LZX or XPR, LZX compresses the ROM much better than XPR but takes longer to cook the ROM, most often I compress with XPR when testing but use LZX when releasing a ROM. All you do to change compression is look at the HEX editor it says either LZX or XPR, if it says LZX and you want XPR, change it to XPR, save and close and vice versa. After closing XVI32 There will be loads of white scrolling text wait for it to stop moving.
​
Step 4
You will now have a comand prompt, like below just press enter and wait for it to close. Congratulations!, you have just cooked your first ROM, if you would like to test it plug in your xperia and run CustomRUU.exe and just flash the ROM like you normally would.
Now that you've cooked a ROM you can try cooking another while removing some packages and following any customization suggestions in post 4​Click Here​

Customizing Your ROM​This Tutorial Contains Various Mini Tutorials On How To Customize Your ROM​
How to change your ROMs Name
In the kitchens tools folder there is a file called nbhgen.txt, edit the third line (which says "SEX1.R3" by default) to the new name of your ROM
In the kitchens OEM\OEMVersion there is a rgu file, edit the line in the file "ROMVersion"="SEX1-r3.61-XprT" changing "SEX1-r3.61-XprT" to the new name of your ROM
Note: Your ROM name can have a maximum of 16 characters and no more, change both of the above to chnage your ROMs name
How to change your ROMs Boot Screen
In the kitchens SYS\Redist_dpi_192_resh_480_resv_800 folder there is a file welcomehead.192.png which is the phones boot screen
Only the first 480 x 800 pixels are used from the image taking from the left side of the image
Adding Extra OEM Packages
Simply take the package and place it in the OEM folder of the kitchen
Some packages have a language package with must be cooked also for example "PACKAGE_Kovsky_Camera" & "PACKAGE_Kovsky_Camera_0409"
OEMs can be extracted from Stock ROMs and some custom ROMs (if there unprotected), I will show you how to extract ROMs in a later tutorial
Upgrading Windows CE Build (SYS)
Replace packages from your old SYS folder with ones from the new SYS folder
Dont replace the folders ".VM" or "WinCENLS_WWE" because they are unique to that device
Dont replace files with resolution packages with newer resolution packages of a different size, for example "Redist_dpi_192_resh_480_resv_800", this is for a phone with resolution 480 x 800, so dont replace it with something like this "Redist_dpi_192_resh_480_resv_640"
The same goes for DPI, make sure the new package is the same DPI as your old one, for example "Base_DPI_192" this package has a DPI of 192, dont change it to something like this "Base_DPI_96"
Finally packages that contain language files must be replace with files of the same language or else the OS will be in another language, for example "Browsing_Lang_0409" this package is and english package (0409 is english) so dont replace it with something like this "Browsing_Lang_0407"
Changing The ROMs Default Date
After cooking a ROM, open XVI32 in the root of your kitchen
Click File > Open and select the "RUU_signed.nbh" file from the root of your kitchen
Press Ctrl and F, and search for "Jan"
Below the line its selected there should be something like "Apr 23 2009", Change it to something like "Aug 18 2009"
"Apr" stands for April change it to the first 3 letters of the month you want to change it to

Customizing Using Autorun​This Tutorial Is Not Finished, Please Ignore It​
In most ROMs, there is a customizing screen which is shown just after the ROM is cold booted (ran first time or ran after hard reset). This is where all the CABs are installed, theme is set and the last registry entries are added. In this tutorial I will show you how to use autorun to customize your ROM.
First in the kitchen go into the OEM\OperatorPkg folder.
Installing CABs With Autorun
First place the CAB you want to install into the OEM\OperatorPkg folder
Open either config.txt or config_operator.txt, I would use config.txt
Add line in between "LOCK:Enabled" and "LOCKisabled", "CAB: \WINDOWS\your_cab_file.cab" replacing "your_cab_file" with the exact name of the CAB.
Remeber the more CABs you have, the longer it will take to customize, so only use it if converting it to a package doesnt work.
Installing TSKs (Theme's) With Autorun
First place the Theme you want to install into the OEM\OperatorPkg folder
Open either config.txt or config_operator.txt, I would use config.txt
Add line in between "LOCK:Enabled" and "LOCKisabled", "TSK: \WINDOWS\your_tsk_file.cab" replacing "your_tsk_file" with the exact name of the TSK, this changes your default theme
Put as many themes as you want in the OperatorPkg folder, they will all be added into the list in today settings

following every word!!

Very nj!
It's all clear and easy to follow: the perfect tutorial!
I was waiting for this for long time, thank you!

well done TotalFire, keep the high spirt

great work...i can finally understand how this works! When will you release another tutorial? I would love to know how to put programs in your rom (or the packages, for that matter) install skins or a connectio nsetup which runs automatically....
love this!

I'll try and release a few tommorow.
Does anyone know if its possible to disable smilies in a post?

yes when u reply click go advanced .then u click disable smilies in text!

rotastrain said:
yes when u reply click go advanced .then u click disable smilies in text!
Click to expand...
Click to collapse
Thank You
--------------

Totalfire , i believe after you finish this tutorial any beginner can cook his own rom with his own recipe
so please continue the same SIMPLE wording
thanks M8

I will, just need a bit more time

Please request tutorials, and i'll make then. Dont know which one to make next.

Nice tutorial I'm using Visual kitchen myself but nice tutorial for old style

killer8nl said:
Nice tutorial I'm using Visual kitchen myself but nice tutorial for old style
Click to expand...
Click to collapse
Ive just started using the visual kitchen, didnt give it much of a try last time. Seems good so far.

Fixing BuildOS Error's
While cooking ROMs you are very likely to come across error's, this post will show how to fix some of them.​
Default.hv And User.hv:
Open the file temp\log.txt, and scroll to the bottom of it
Look at the second last line, there should be an error message with the name of a rgu file
Higlight the rgu file and copy the name to clipboard
Search the root of the kitchen with the text you just copied from the last step
Look at the folder it says and open the rgu, there is a problem in there you need to fix

As i have switched to visual kitchen, it would be easier for me to make guides for that, would anyone prefer me to continue making a guide for the old style kitchen. BTW visual kitchen, is easier especially for thing like porting SYS and ROM.

if i need to remove anything from the OEM before cooking (like a panel), just delete the item? or is there another task i must perform as well?
BTW thanks for this tutorial, this is soo damn simple, nuff respect to you dude

Free SIM Unlock via nv_data.bin for SGS3 XXBLG1

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.