Hi!
I was wondering if the WM5 Rom editing tools still work with a WM6 Rom, I was trying to add some dll's to the WM6 rom to make it work on my Prophet (Sound dll is wrong). I first umpacked the rom with prepare_imgfs.exe then viewimgfs.exe I replaced the files in the dump directory and then tried to repacked with buildimgfs.exe but it displays one line of junk on the commandline and that's it. So the questions are:
1. Can the Rom editing tools be used on a WM6 Rom
2. What orther options are there to change files in a not flashed .nba file?
Thanks,
Ramon
ok how did you get that to work, cus i was trying it and the folder Dump was not getting made!!! i tried it so many time!
I don't have any problems at all... Everything works just the way it did with wm5...
extract OS.nb from nk.nbf using: typho5.exe -x nk.nbf
prepare_imgfs.exe OS.nb -nosplit
viewimgfs.exe imgfs_raw_data.bin
...modify "dump" directory as you need...
BuildImgfs.exe
make_imgfs.exe OS.nb -nosplit
-----------------------
replace OS.nb with the name of the OS part.
do not forget the -nosplit option in prepare_imgfs and in make_imgfs.
bye
Just to clarify, I'm using
Code:
typhoonnbfdecode to get 80040000-OS.nb
prepare_imgfs 80040000-OS.nb -nosplit
viewimgfs imgfs_raw_data.bin
make the changes without removing any of the files created in the dumping process then
Code:
buildimgfs
make_imgfs 80040000-OS.nb -nosplit
after that use nb2nbf_tornado to make a new nk.nbf
_Nomad_ said:
Just to clarify, I'm using
Code:
typhoonnbfdecode to get 80040000-OS.nb
prepare_imgfs 80040000-OS.nb -nosplit
viewimgfs imgfs_raw_data.bin
make the changes without removing any of the files created in the dumping process then
Code:
buildimgfs
make_imgfs 80040000-OS.nb -nosplit
after that use nb2nbf_tornado to make a new nk.nbf
Click to expand...
Click to collapse
I'm doing the exact same thing, but at this step:
make_imgfs 80040000-OS.nb -nosplit
It goes wrong it fails without an error message..
What exact file are you trying to integrate in the rom? is it a module?
btw. you never get an error message
_Nomad_ said:
What exact file are you trying to integrate in the rom? is it a module?
Click to expand...
Click to collapse
Well I don't think it matters, because I also tried a makeimgfs and changed nothing.. no files.. but the file I want to change is "wavedev.dll"
Solved it!
I though the last step:
make_imgfs.exe nk.nbf -nosplit
But it had to be make_imgfs.exe 80040000-OS.nb -nosplit
I thought it was just going to create a new file..
That's odd... before rebuilding you didn't remove any files did you? such as imgfs_raw_data.bin?
rvbcrs said:
Solved it!
I though the last step:
make_imgfs.exe nk.nbf -nosplit
But it had to be make_imgfs.exe 80040000-OS.nb -nosplit
I thought it was just going to create a new file..
Click to expand...
Click to collapse
Naa, no new file... the old one is used as a template...
Great to see you solved it
Good luck with the rest...
Just learning a bit of ROM-cooking atm. Got a little problem, hope someone can help me get further:
When I add files to the "dump" dir and try running "BuildImgfs.exe" it lists the files nicely, but "imgfs_raw_data.bin" doesn't change date or time, nor does it change size.
What am I doing wrong?
vippie said:
Just learning a bit of ROM-cooking atm. Got a little problem, hope someone can help me get further:
When I add files to the "dump" dir and try running "BuildImgfs.exe" it lists the files nicely, but "imgfs_raw_data.bin" doesn't change date or time, nor does it change size.
What am I doing wrong?
Click to expand...
Click to collapse
It's NORMAL, go on. I don't know why the date doesn't change, i was confused too the first time i cooked a rom, but i can say it's completely normal.
Thank you Risidoro for the fast response.
is it possible to cook wm6 rom for G4 locked devices? thanks
risidoro said:
extract OS.nb from nk.nbf using: typho5.exe -x nk.nbf
prepare_imgfs.exe OS.nb -nosplit
viewimgfs.exe imgfs_raw_data.bin
...modify "dump" directory as you need...
BuildImgfs.exe
make_imgfs.exe OS.nb -nosplit
-----------------------
replace OS.nb with the name of the OS part.
do not forget the -nosplit option in prepare_imgfs and in make_imgfs.
bye
Click to expand...
Click to collapse
Thank you you are a star, i have it working now!!! the auto thing that was made does not work!!!
funman said:
Thank you you are a star, i have it working now!!! the auto thing that was made does not work!!!
Click to expand...
Click to collapse
the autothing?!? Where is it? I've never heard of it!
BTW: i'm happy you succeeded in cooking your first(?) rom! Happy cooking!
bye
risidoro said:
the autothing?!? Where is it? I've never heard of it!
BTW: i'm happy you succeeded in cooking your first(?) rom! Happy cooking!
bye
Click to expand...
Click to collapse
I forgot to thank you too risidoro You really helped me out here! I suceded to cook my first rom hehehe.. nothing special some extra files.. but still hehe.. Now I like to know how I can change registry settings, do I have to change them from the extended_rom or is there a way to do it in the ROM?
Thanks again to all who helped out!
rvbcrs said:
I forgot to thank you too risidoro You really helped me out here! I suceded to cook my first rom hehehe.. nothing special some extra files.. but still hehe.. Now I like to know how I can change registry settings, do I have to change them from the extended_rom or is there a way to do it in the ROM?
Thanks again to all who helped out!
Click to expand...
Click to collapse
Now you need to learn how to create cabs and autorun them from ext_rom. That's what does all that AFAIK. Chefs -- is there any other way? Can you modify the seed hives directly?
I would like to know how to modify the hives too. I saw a tutorial somewhere, but I can't find it now.
Related
I am trying to modify a ROM for my BA with the use of imgfs tools I downloaded from buzzdev.. This is what I did... (hope someone here could comment if this is correct) I have not tried flashing any of my modified ROM coz i dont still have my BA with me, mabe this 3rd week of sept I will have it in my hands!!! LOL
Here's how:
1.) I tried helmi v1.3 (I converted nk.nbf to nk.nba with the use of nba converter)
2.) Prepare_imgfs nk.nba
3.) viewimgfs imgfs_raw_data.bin
4.) modified the dump directory (added the wm5torage, pocketrar, taskmanager v1.4.4)
5.) edit the initflasfiles.dat with the use Notepad (deleted the 2byte signature with the use of ULtraEdit)
6.) I also edit the default.hv with the use of rgucomp (I dont know if i made it correctly) to include the registry entries of WM5torage) (Well I succesfully convert it to rgu, edit it with the use of UltraEdit save it as unicode and I managed to convert it to .hv file successfully without any errors)
7.) Buildimgfs
8.) make_imgfs nk.nba
Is this a correct way of modifying the ROM? If not, how? I read alot of posts here (xda and buzzdev) on how to modify a ROM with use of imgfs tools and this is how I understood it... hehehe
Is the rom i made workable? Thanks hope soomeone here could help me!!! by the way here is the attached rgu and hv file i modified!!
I might suggest trying the Bepe ROM Kitchen.. quite a bit easier
Yeah its easier>>!!
I tried the method you said..But for me this is simplier... So based on your own understanding, is that correct? I know you have done modifying a lot of roms already....
Thanks
So anybody here could give some more opinions>>>Pls
Anyone?
Anyone???
It seems OK the way you did.
I did the same way as you when I used XdaII or Himalaya.
I edited BA ROM this way too.
One thing to tell you is that you will not know that it works or not until you flash it in your device.
The file you add may overload the space if you don't delete some files you don't use.
I delete transcriber because I don't use it and will have about 500 KB for adding some files I want.
Flash it and you will know the answer yourself.
8)
Thanks
Thank vivi.. Yeah I did, i deleted some of the files in the rom (which I donot use at all) to have some space for my additional files... btw, I read about boot.hv (like on the other method) do I need it also in this method? Or is it included in the default.hv?
I left boot.hv in dump folder and didn't touch it.
I edited only default.hv and initflashfiles.dat.
But it is a long time not doing.I nearly forget the steps to do.
I think Helmi ROM is OK and I use it as it is.
OOOH
I dont see any boot.hv in the dump directory? Did i mess somthing?
Yup It seems that Helmi ROMs are great..Thanks again
Hi all ,
i would really like to know what tools you are using to edit the Rom,
(a short explanation will be excellent)
I've tried some tools from the furom without luck.
Many Thanks
Jimmy
jimmymotek said:
Hi all ,
i would really like to know what tools you are using to edit the Rom,
(a short explanation will be excellent)
I've tried some tools from the furom without luck.
Many Thanks
Jimmy
Click to expand...
Click to collapse
look for imgfs tools,nb2nbf.exe, and typho5.exe.
it was quite easy creating a Ext. ROM (so i know how to use nb2nbf.exe, and typho5.exe it's imgfs tools that is not working for me.
i would really appriciate help with that.
Thanks again
Jimmy
jimmymotek said:
it was quite easy creating a Ext. ROM (so i know how to use nb2nbf.exe, and typho5.exe it's imgfs tools that is not working for me.
i would really appriciate help with that.
Thanks again
Jimmy
Click to expand...
Click to collapse
what part are you having trouble?
This is what I did :
after extracting the OS with typho5.exe
prepare_imgfs.exe 80040000-OS_0.nb -nosplit
viewimgfs.exe imgfs_raw_data.bin
than I wanted to edit the "dump" directory (I don't know how to put different files in diffrent directories) , any how i've replace few files. and than I run :
BuildImgfs.exe
make_imgfs.exe 80040000-OS_0.nb
than nb2nbf.exe and after all that I "burned" it into the device
(RUU) and than the device stucked.
So what I'm doing worng ?
again
many thanks
Jimmy
jimmymotek said:
This is what I did :
after extracting the OS with typho5.exe
prepare_imgfs.exe 80040000-OS_0.nb -nosplit
viewimgfs.exe imgfs_raw_data.bin
than I wanted to edit the "dump" directory (I don't know how to put different files in diffrent directories) , any how i've replace few files. and than I run :
BuildImgfs.exe
make_imgfs.exe 80040000-OS_0.nb
than nb2nbf.exe and after all that I "burned" it into the device
(RUU) and than the device stucked.
So what I'm doing worng ?
again
many thanks
Jimmy
Click to expand...
Click to collapse
your OS address is most problably wrong. it should be; 80040000
faria said:
your OS address is most problably wrong. it should be; 80040000
Click to expand...
Click to collapse
I know this is the OS address (that's what i was typing),
can you think of anything else ?
how do i know where the file is goona be (in which directory)
how can arrange the startmenu ?
sorry for the "tons" of questions
Jimmy
jimmymotek said:
I know this is the OS address (that's what i was typing),
can you think of anything else ?
how do i know where the file is goona be (in which directory)
how can arrange the startmenu ?
sorry for the "tons" of questions
Jimmy
Click to expand...
Click to collapse
look at the initflashes.dat in the dump.take a good look.,thats how.
faria said:
look at the initflashes.dat in the dump.take a good look.,thats how.
Click to expand...
Click to collapse
Found it...
Still not working , i have made a test on the T-Mobile ROm,
just took the os file , prepareifile -nospilt
than i used delfile t-mobile.tsk
afterward i used make_imgfs.exe
afterward i used nb2nbf , just the os (address 80040000) and than bured it.
and..... No luck still stuked on the Startup LOGO , what am i missing ?
(it's almost driving me nuts)
thanks again
Jimmy
faria said:
look at the initflashes.dat in the dump.take a good look.,thats how.
Click to expand...
Click to collapse
I'm not able to find it out the file "initflashes.dat" in dump folders. Where can I find the file?
It must be in the rom, if you cannot find it type in a command line console in the dump directory "attrib -h -s initflashes.dat", that surely would let you see it. But normally you will see it without doing this.
Molski
jimmymotek said:
Still not working , i have made a test on the T-Mobile ROm,
just took the os file , prepareifile -nospilt
than i used delfile t-mobile.tsk
afterward i used make_imgfs.exe
afterward i used nb2nbf , just the os (address 80040000) and than bured it.
and..... No luck still stuked on the Startup LOGO , what am i missing ?
(it's almost driving me nuts)
thanks again
Jimmy
Click to expand...
Click to collapse
Molski , Do you have any suggestion ?
jimmymotek said:
Molski , Do you have any suggestion ?
Click to expand...
Click to collapse
Extract one of my Roms, replace my OS.nb file with yours and cook it again.
Use ALL files including IPL/SPL so you will have to put 7 files in nb2nbf tool, if you need all the correct addresses, PM me.
Regards,
Molski
is it possible that my problem was that i just tried to "burn" OS and Ext. rom only ?
going to tray it again.
(BTW : is there a number of times i can burn my rom , i think i've done a hundred time)
thanks
still not working , stuck at the logo screen (it does write the spl,Ipl etc)
here are the address i used :
i think the problem is with something else ,
what version of imgfs you using (link ?)
can you write down the list of commands you writing
(i've been dealing with it quite few days with no luck)
I would really appriciate any help....
thanks again
Jimmy
molski said:
It must be in the rom, if you cannot find it type in a command line console in the dump directory "attrib -h -s initflashes.dat", that surely would let you see it. But normally you will see it without doing this.
Molski
Click to expand...
Click to collapse
Thanks molski I'm able to find it...
hey
I am using windows xp on my desktop so when i try to extract the nk.nbf files using dumprom a window opens like that of cmd prompt and closes immediately. can anyone tell me of a software that works on xp since i dont know linux,unix and other stuff expect windows.
I searched the forums but I could't find such programs.
can anybody help me plz since I am trying to cook rom on my own using the procedure given by faria .
I found that the batch files that are included in the ROM cooking tools don't work, but typing the commands that are in the batch files work fine. Try that, it worked for me.
Not got around to cooking my own ROM yet though
HTH
Andy
try looking here
THANKS it worked
Still need help
Ok I must be missing something.
I probably found it but just did not know it.
most things need a nk.nbf file to start with.
Where do I get one ?
Does it make a differance what it is ?
stainlesspc said:
Ok I must be missing something.
I probably found it but just did not know it.
most things need a nk.nbf file to start with.
Where do I get one ?
Does it make a differance what it is ?
Click to expand...
Click to collapse
It makes ALL the difference
The RUU files are compressed pakages with the various files used in the update process one of which is the nk.nbf (always with that name)
So no matter if the OS is WM5, WM6, cooked or official, a radio only, a splash image only, it is ALWAYS named nk.nbf since it will be looked by that name by the updater application.
hope it was clear enough
cheers
_Nomad_ said:
try looking here
Click to expand...
Click to collapse
I looked at this, but it extracts .nba files. I need to extract files out of .nbf
So i can start cooking my own ROMs
freeyayo50 said:
I looked at this, but it extracts .nba files. I need to extract files out of .nbf
So i can start cooking my own ROMs
Click to expand...
Click to collapse
use typho5.
peter petrelli said:
use typho5.
Click to expand...
Click to collapse
OK, so i just downloaded typho5 through the ftp, but i dont have the dll file for it. I get error: LoadLibrary p2x587.dll failed
Where can i find the file?
just get it from shelltool.
I found another typho5 and it works. After dumping the files with typho5 which one is the extended rom so i can extract the cab files??
freeyayo50 said:
I found another typho5 and it works. After dumping the files with typho5 which one is the extended rom so i can extract the cab files??
Click to expand...
Click to collapse
Use my tool (Wizard Service Tool) as it extracts all the files in a nk.nbf without command lines and without any hassle
cheers
Thanx. Worked great. Why doesn't WinImage want to open the .nb files??
Im tryin to extract cab files from faria's Crossbow Reloaded v1.5. After using Wizard Service Tool, I get the 3 .nb files.
freeyayo50 said:
Thanx. Worked great. Why doesn't WinImage want to open the .nb files??
Im tryin to extract cab files from faria's Crossbow Reloaded v1.5. After using Wizard Service Tool, I get the 3 .nb files.
Click to expand...
Click to collapse
Winimage only handles the extension_rom.nb since it is an image of a HDD formatted with FAT16; the other files are encrypted/packed and can only be handled with kitchen tools spread all throughout the forum
cheers
Ok thanx. I'm going to start my search
I had posted this to the mamaich's thread. posting here as well since it is wizard specific:
I've been trying to use the tools for building an HTC wizard ROM. Now, before starting out on any modifications, I simply tried to break apart and rebuild it. So, I extracted a ROM using typhoondecode_v5, then followed this:
1. prepare_imgfs.exe OS.nb -nosplit
2. viewimgfs.exe imgfs_raw_data.bin
3. BuildImgfs.exe
But then my imgfs_raw_data.bin is not rebuilt and stays at its original self. The buildimgfs tool does not give me an error, however the last 3 lines of its output reas something like :
total sectors: 0000
used: <some number>
free: <some number>
I searched the forums but couldn't find an answer. Saw a couple of posts having the same prob but no answer. Since I havent done any modifications to the ROM and have tried with both AKU2.3 and AKU 3.3 (and custom ROMs as well as official Qtek ROMs), the ROM that i am using is also not an issue.
Now, since there are so many custom wizard ROMs out there and ppl swear by mamaich's tools so there must be a solution. Please help me out or let me know if there is no way out and I ve to use some other way to make ROMs, i also found bepe's kitchen post but couldn't find how to use it for wizard..
Thanks in advance.
for the wizard, this line:
1. prepare_imgfs.exe OS.nb -nosplit
should be:
prepare_imgfs.exe 80040000-OS.nb –nosplit
see if that helps...
prepare_imgfs.exe 80040000-OS.nb –nosplit
Click to expand...
Click to collapse
I used that one only, and I have no probs with the "prepare" and "view" commands. I correctly get the bin files as well the modules/files are correctly extracted. I have problem with the "build" and "make" commands.
side question. should have thought of this earlier. how do you know its not updating? its been stated that this file will for some reason not change date/time and size.
hopefully that helps.
see this post:
http://forum.xda-developers.com/showpost.php?p=1110892&postcount=13
see this post:
http://forum.xda-developers.com/show...2&postcount=13
Click to expand...
Click to collapse
oopsie I am sure I read that post some time ago when I was collecting all the info for ROM cooking, but somehow forgot abt it when I started. Thnx for reminding
But There's another problem after this. When I run make_imgfs command it gives me some weird characters, however, a couple of posts above the one that you pointed at, there is a comment that I've to give the name of the old file only instead of new one. Will try that tonight when I go home and report back.
Thnx for the help dude
Anyways, another question:
This one is about the "universal id" part (dont remember the name of the app correctly, smthing like genuuid), for which all packages do we have to use this app? I mean if I wanted to add an executable (say a.exe) to the ROM, is it enough to simply add it to the "dump" directory and follow the build/make path or do I have to use the genuuid app path, or is this app used for some special kinda apps?
Thnx in advance. I'm not a newbie by any means in programming, GSM, and programming for GSM etc (I work in a Nokia GSM BTS project ) but am cooking a ROM for the first time.
yupz, worked...I was able to rebuild the rom. (Though the size/date-time stamp of the final 80040000-OS.nb also remains the same as the older one. I take that to be OK like the same thing happening with img_raw_data.bin. Haven't flashed the ROM onto my phone to see...)
Moreover, about the uuidgen program, I found out that it is bepe's way of doing it. We can do it the mamaich way that is simply add the programs that we want to the /dump folder and rebuilding. Correct me if I'm wrong.
Now that I've tested the waters, I'm on to making a custom ROM myself...
Thnx xda-dev...
shantzg001 said:
yupz, worked...I was able to rebuild the rom. (Though the size/date-time stamp of the final 80040000-OS.nb also remains the same as the older one. I take that to be OK like the same thing happening with img_raw_data.bin. Haven't flashed the ROM onto my phone to see...)
Moreover, about the uuidgen program, I found out that it is bepe's way of doing it. We can do it the mamaich way that is simply add the programs that we want to the /dump folder and rebuilding. Correct me if I'm wrong.
Now that I've tested the waters, I'm on to making a custom ROM myself...
Thnx xda-dev...
Click to expand...
Click to collapse
Hi shantzg001
i too am doing similar steps and all gone well ( i.e breaking/rebuilding).
but im surprized why dump dir size is extremaly different in compare to
imgfs_raw_data.bin . I tried some OS.nb and got the size of dumb approx
456kb or 368 kb or some MBs. Also dump dir contains only some modules and
some files.
Am i doing some mistake or u too r getting similar result
reply ASAP
thanx
nandlal
That seems strange, because in my case the dump folder is even bigger than the bin file (more than double the size)..
Can you list out the exact steps that you are following, and which ROM were you breaking apart?
wm6 can we change bootspash like wm5?... hopefully we will have sooner!
Yes the second bootsplash can always be changed..
c_shekhar said:
Yes the second bootsplash can always be changed..
Click to expand...
Click to collapse
same procedure and tools? in wm5?
coz i try, but did not work!
the most simpple method is to create any 320X310 picture in png format and rename it to welcomehead.96.the name should be as welcomehead.96.png and copy it to ur Windows folder and overright..make sure to copy the orignal one for ur later use.
thanks!
ather90 said:
the most simpple method is to create any 320X310 picture in png format and rename it to welcomehead.96.the name should be as welcomehead.96.png and copy it to ur Windows folder and overright..make sure to copy the orignal one for ur later use.
Click to expand...
Click to collapse
yea! thanks!
thanks!
i simply change my bootsplash! thanks!
and all boot splash can be changed.
2003 Rom editor + any extrom.
1 cleaning via romeditor all contents from extrom.
2 insert 1st and 2nd boot splash image you want.
3 flash extrom only
that`s all
c_shekhar - you don`t know it great ROM master ?
obaz said:
and all boot splash can be changed.
2003 Rom editor + any extrom.
1 cleaning via romeditor all contents from extrom.
2 insert 1st and 2nd boot splash image you want.
3 flash extrom only
that`s all
c_shekhar - you don`t know it great ROM master ?
Click to expand...
Click to collapse
@obaz
But there is no extROM in WM5 or WM6? Which extROM are you editind ?
ExtROM diminished in WM5 and WM6 instead of that we got extROM in SD Card. I wondering which extROM is meant by Obaz
amerikans....
you don`t need to wonder - if you whant to change bootsplash - just do it as I tell.
THERE IS EXT ROM IN WM6 AND WM6 (few kb) - it can`t be totaly remooved.
when you use BIG STORAGE tweek you just make it as small as it can be.
and remember - rom, extrom, radiorom are SEPARATED !!!
@selankahlagi
@peter01
What obaz says is correct. Wonderful obaz! Nobody thought the way you suggested for changing the bootsplash screens.
Let me elaborate what is required to be done in the lay man's language:--
From your old storehouse pickup any (immamterial whether for WM3/WM2003SE/WM5) it is found in the name of ms_.nbf .
search out for old ExtROM editing tool called ER2003Edit_1_4_26. You shall find it on this forum or search using google.
Install the ExtROM editor on your PC.
Now open the ms_.nbf using the tool and delete the entire content from it except the splash screens. replace the splash screen (both) as you like. and enjoy.
Flash it on your device using HimaUpgradeUt.exe or HimaUpgradeUt_NoID.exe
Sorry double post
Link to Editor: ftp://xda:[email protected]/Tools/ER2003Edit_1_4_26.zip
Does someone actually tested this ?
and as far as i know the extrom is resized to 128 kb which is not enough for the 2 boot screens
also (i am not sure about this but ...) the new boot loader in wm5 and wm6 does not handle boot images the same way as in wm2003
c_shekhar said:
@selankahlagi
@peter01
What obaz says is correct. Wonderful obaz! Nobody thought the way you suggested for changing the bootsplash screens.
Let me elaborate what is required to be done in the lay man's language:--
From your old storehouse pickup any (immamterial whether for WM3/WM2003SE/WM5) it is found in the name of ms_.nbf .
search out for old ExtROM editing tool called ER2003Edit_1_4_26. You shall find it on this forum or search using google.
Install the ExtROM editor on your PC.
Now open the ms_.nbf using the tool and delete the entire content from it except the splash screens. replace the splash screen (both) as you like. and enjoy.
Flash it on your device using HimaUpgradeUt.exe or HimaUpgradeUt_NoID.exe
Click to expand...
Click to collapse
Dear C_Shekhar
As I know you never include ms_.nbf to your package in WM5 and WM6. Thank for your tip
but it was included in WM2003 Windows..and plus i dnt think it will work just as Xplode said..
xplode said:
Does someone actually tested this ?
and as far as i know the extrom is resized to 128 kb which is not enough for the 2 boot screens
also (i am not sure about this but ...) the new boot loader in wm5 and wm6 does not handle boot images the same way as in wm2003
Click to expand...
Click to collapse
@explode
the procedure works very well. even on WM6. I have tested it many times. The extROm is shrunk to more than 128KB definitely..
selangkahlagi said:
Dear C_Shekhar
As I know you never include ms_.nbf to your package in WM5 and WM6. Thank for your tip
Click to expand...
Click to collapse
You are right that ms_.nbf was never included by me in the package. because, even if we delete the content of the ms_.nbf, the size of the ms_.nbf still remains abt 16MB. Flashing it along with the nk.nbf thakes proportionately larger time for no bigger material gains.
Moreover it is one time activity (in my opinion) whereas you flash nk.nbf may be 100 times for testing. I am already using replaced bootsplash screens on my device.
c_shekhar said:
You are right that ms_.nbf was never included by me in the package. because, even if we delete the content of the ms_.nbf, the size of the ms_.nbf still remains abt 16MB. Flashing it along with the nk.nbf thakes proportionately larger time for no bigger material gains.
Moreover it is one time activity (in my opinion) whereas you flash nk.nbf may be 100 times for testing. I am already using replaced bootsplash screens on my device.
Click to expand...
Click to collapse
You are righ again my dear C_Shekhar, I have delete all the files in ms_.nbf but I check the size remains 16 MB, how it could be. May be we delete only the list in ER_2003 editor And I agree we will not get magnificent gain from that
i don't have a copy of ms_.nbf file. where can i find one? i googled it and most download links were closed due to being old files.