Note for Mods: If you feel that this thread belongs to some different forum, feel free to move it (coz i also have this feeling, but i am not clear
Hi Friends,
I have seen this discussion many times that the older GReloc cannot be used for relocating newer, WM 6.5 SYS. While this is partially true, there is a workaround for this that I have been using with last 2-3 WM 6.5 ROMs that i have cooked for myself. So i thought it will be good for all the fellow chefs and wannabes if i share this info with you.
Although the new tool WMReloc can be used in place of GReloc, i don't find it as user friendly as GReloc and since GReloc works for me, there is not enough reason for me to switch over. Also, once or twice i have seen reports of WMReloc doing overlapping of addresses while the relocation process which defy its sole purpose.
So here is the method I use :
1. Download Unlocker from Here. This will help you unlock files that are currently in use by other programs so that you can copy move and delete them. Install it and on every file and folder you'll get a new entry in context menu called "Unlocker".
2. Now start Greloc.exe and fill in proper values if needed. Click "Do It". When it gives Integer Overflow, click OK but dont close it. Press "Do It" again and this time it will show you the file that is givin error in the message box, mostly its a .tmp file.
3. Go to the file, right click on it and select "Unlocker". In the box that opens, on the right hand, choose delete in the dropdown box. Now click Unlock All. This will delete the file.
4. Click "Do It" in GReloc Window again, this time it will complete the process. If the error comes again, for a different file (never happened with me though), repeat this process.
5. To be sure, run GReloc once again and it will complete the process successfully in one go.
Explanation:
Although I don't claim to be an expert on this subject, As far as my understanding goes, the problem lies within the algorithm used in GReloc. It uses integer data typed variables for doing whatever it does during the relocation process and with Wm 6.5, somehow the value stored in one of these variables crosses the upper or lower limit of the allowed range for integer variables.
Now, In the process of relocation, GReloc creates a tmp file based on the contents of the modules it is relocating. When error occurs GReloc stops as it is and doesn't closes the handle to this tmp file. This causes the process of relocation to fail on successive attempts.
What we do is we unlock this file forcefully using unlocker and delete it. This way, GReloc restarts the relocation process from that module again and the problem is solved.
Happy Cooking!
Hi sumit,
Great tutorial. It'll be aplicable not only to wm6.5 but to wm6.1 as well. In some wm6.1 roms i have the same problems.
this is temporally solution if u want to know how to use wmreloc i will tell u
but if you r using ramersonw kitchen it will little bit trick becoz tool folder comes when you start kitchen
i have my own kitchen witch support wmreloc 1.4
@ ramersonw
if u want to add wmreloc support to your kitchen contact me , and what about your visual kitchen ? is it done ? tell me if you want any help .
@Ankit: Yes its a temporary solution, it was working for me for last few roms so i thought it may be of some use to others also. And Yes, Please post the tutorial for using WMReloc.exe either in this thread (I'll rename the title of thread in that case) or in a separate thread, as you find it appropriate. That will be really good. Try to post the necessary tools with it too, like the WMReloc.exe file itself and anyother thing needed to use it.
In Ramerson's kitchen, the tools folder is created at start of the process, and buildos runs for atleast a minute or two, so the files in tools folder can be replaced in that period.
@Ramerson: Ya, the problem can occur in WM 6.1 also. I think it has to do something with the number of files that GReloc is relocating. Actually at the start of the relocation process, GReloc seems to be calculating which files needs to be relocated, and if this number exceeds a certain limit, that i am not aware of yet, it crashes. But when the relocation process is resumed from the point of error, number of files to relocate comes within the range and then GReloc continues. Great thing is that GReloc is a .NET app and exception handling has been done quiet intuitively otherwise there was no chance to resume this process.
Anyways Buddy, These are just assumptions and are working for now but this may not last for long so i think its really the time to update your kitchen. I request you to either you do it, or please share the code with me and i will try to understand and port it to .NET for further development.
krazy_about_technology, hi, put that in the attache a folder tools in their kitchen. And replacement following -" GReloc-doit-dump" on - "start / w "" tools \ WMReloc.exe-g. \ Temp \ dump-lWMReloclog2.txt"
Good luck
@ankit
this is temporally solution if u want to know how to use wmreloc i will tell u
but if you r using ramersonw kitchen it will little bit trick becoz tool folder comes when you start kitchen
i have my own kitchen witch support wmreloc 1.4
Click to expand...
Click to collapse
can u upload ur kitchen for wm6 & 6.5 plz ............
ankit360 said:
this is temporally solution if u want to know how to use wmreloc i will tell u
Click to expand...
Click to collapse
Please can you write tutorial on this?
In my case g'reloc missing S001 file, iam forget which module, so i use wmreloc, it was working well.
Xumit said:
Please can you write tutorial on this?
Click to expand...
Click to collapse
change
G'Reloc -doit -dump
with
wmreloc -gtemp\dump
swapnil_0081 said:
@ankit
can u upload ur kitchen for wm6 & 6.5 plz ............
Click to expand...
Click to collapse
You can download ankit wm6.5 kitchen, edit file build.cmd in the tools folder,
find line
start /w "" Tools\G'Reloc -doit -dump
change it with
start /w "" tools\wmreloc -gtemp\dump
save the file.
copy wmrelox.exe to tools folder
The file missing is in either marketplace or my phone. I got that message too. I removed these two packages and thereafter the process went smoothly. WMReloc skippes these files. Did you checked whether these services are working in your wmreloced rom?
I can't found it in wmreloc log, but it work well in my gene
I will give you solution very soon
Related
Simple steps on howto
1. download the kitchen Download
2. download Prophet Touch X rom Get it here
3. extract Kitchen and Prophet Touch X to separate folder
4. Place the OS.nb from Prophet Touch X in the rom folder of the Kitchen
5. run Buildos.exe and choose what to include (the marked apps are the once that are in Prophet Touch X) press the green play button and wait for it to finish
6. run CreateROM.bat (if there is any error the you have included to much in the Buldos prosess)
7. if there were no error the new OS.nb is in the temp folder move it to the Prophet Touch X folder and overwrite the os.nb in it
8. flash any step 1 WM5
9. now Flash your new rom within Prophet Touch X folder
if everything is done right you should have your new coocked rom on your Prophet
I have put all the things that should not be removed into the SYS folder so do only make changes to the OEM folder till you know more about cooking .
replace the HTC Audio Manager with this one
View attachment OEMAudioManager.zip
New HTC Album with folder option
View attachment HTCAlbumFolderOption.zip
Extras and links
I'll upload some addons for the kitchen later on as I've made more OEM packs
You can also search for oempacks to include but be aware that some OEM packs are device depented
Some cool tools that I use but have not included in kitchen You'll need to understand what they do before using them
HyperCore Kitchen cool for dumping roms and building ( I use it for dumping)
this is great.. awesome.
Great job Gullum. Now guys, we all should start frying Hokienmee or Char Kueh Teow (both chinese cuisine)
geney said:
Great job Gullum. Now guys, we all should start frying Hokienmee or Char Kueh Teow (both chinese cuisine)
Click to expand...
Click to collapse
I like both of them..LOL..
Really love this kitchen...
Thanks man, you are great!!!
It'll be even better if have a list of what those things really for. I do not know which box to check and which one is not
Maybe I'm too new for 'cooking'
geney said:
It'll be even better if have a list of what those things really for. I do not know which box to check and which one is not
Maybe I'm too new for 'cooking'
Click to expand...
Click to collapse
hold the mouse over one of the options and there should show and explaination for most of the items
good news
i'll try it
for every change in X and flashing it, is it always necessary to do step 1 again (wm5 flashing) ?
When I do hard reset and at the "tap screen to go on" point, I could start flashing X too ?
What I mean, is the complete rom exchanged when I flash X, or do some parts from wm5 or old X (IX, VIII ....) remain ?
I've try to cook today.. BUt seems something is going wrong...
Better I flashed it back to the original touch X ROM...
I also had some bad luck with cooking.
I did everything gullum said, flashed 'new' TouchX, did hard reset and then when its time to see welcome screen and 'press any key.....' there is blank white screen! Nothing happens no matter which button i press! Any ideas?
mcupurdija said:
I also had some bad luck with cooking.
I did everything gullum said, flashed 'new' TouchX, did hard reset and then when its time to see welcome screen and 'press any key.....' there is blank white screen! Nothing happens no matter which button i press! Any ideas?
Click to expand...
Click to collapse
I did the same think.
At my case, i have enter today screen.. But I think, its programs don't install clearly.. (hard reset don't help either.)
The first screen is the same one as you.. The white one.. Maybe you should to try ask Gullum again..
I just flash back to Touch IX with another Ext ROM. QuickMenu in that ext.ROM
thanks gullum
I would like to translate this rom to Portuguese can you give some advices? our some tutorial to do that, please? can i do that with this soft?
best regards
thanks (for this perfect kitchen) gullum ,some 3 questions i have :
1.>how to get oem or make one ,and
2.>how to get .dsm , .rgu files of my favorite software . and
3.>how do i make registry changes prior to build os are they automatic
Note :ext_rom files attributes should be read only since its like that in original rom so i made them read only(i think its healthy for system files any virus won't be able to modify it unless the file needs to be appendable updateable it should be read only),plus i deleted alot of thumbs.db files lying in many folders (about >2mb) just to clean oem folder files off thumbs.db i know winxp might be making them all the way .
i corrected audio manger with this kitchen (its gr8),i can't seem to solve camera album (have solved solution given below )problem ,it seems to have come back you know i can't use gestures , what to do ,any reg setting solution.
Edit : **corrected** the setting in reg hklm\software\htc\htcalbum\cacheserial to 2130706432
and hklm\software\htc\htcalbum\default_viewer to 0
if it still don't get solved set first 11 enteries (h_enable to v_pos) value to 0 in
hklm\software\htc\htcalbum\touchscroll\htcalbumclass
i'll try to provide a cab but this forum has alot of intelligent members
BuildImgfs
whatever I include in the buildos I am facing the same error when I try to create rom; something about BuildImgfs
any help guys!!
ma3ayta said:
whatever I include in the buildos I am facing the same error when I try to create rom; something about BuildImgfs
any help guys!!
Click to expand...
Click to collapse
2 reasons 1.> i hope you are pressing play(top left in build OS)button after whatever you choose,with what ever you want in it.
2.>your file size has to be limited its almost full with this kitchen so you have to remove some item like voice dialing (which i seldom use) or some other item removed before you add some item since size dependency is very important here ,and later run create rom .remember you cannot select everything because of space limitation .
Hello Gullum
I'm trying to do very basic thing adding Windows Live package into the OS.nb but it fails during CreatROM.bat. At BuildImgfs.exe the application BuildImgfs.exe crashes and show the error message and whether to send a report to MS or not (I don't send...).
I just directly add Windows Live to your OS.nb. Is it already fully loaded? Should I remove something before?
question with task manager
something is wrong with task manager.
in control panel ,its setting doesn't work!
Same problem.
Whatever i select in buildOS, BuildImgfs crashes.
Last records is CreateROM.bat window is:
Processing "Painting.gif" as file
Processing "S5K3BAFX.dll" as file
Processing "3aca900a-0834-11dc-8314-0800200c9a66.dsm" as file
Processing "c7dbe475-1d17-4fbf-a63e-af6dc042569a.rgu" as file
Processing "c7dbe475-1d17-4fbf-a63e-af6dc042569a.dsm" as file
Processing "-жE+-A+?.txt" as file
I think reason in strange file name -жE+-A+?.txt.
BINGO!!!
I Found this file in Prophet Touch kitchen.
\\OEM\Quickmenu\-жE+-A+?.txt
Just delete it before kitching.
DCD if you dont like what im doing just tell me to delete this post and i will.
All credit goes to DCD one of the best kitchen and Rom maker's out there.
If it wasn't for him our 6800's would be almost useless.
This is for the people who are using the titan kitchen. I took DCD's latest build and repackaged it for the PPCKitchen.org Titan Kitchen located
here http://forum.ppcgeeks.com/showthread.php?t=23206
Place it in your BuildOS/Kitchens directory and then extract "Titan_DCD_3.01_Selections.txt" and place it in the BuildOS/Projects directory.
Now you can create your own custom DCD rom using the new kitchen and DCD's latest build.
I've been using this for about 20 hrs and the rom is very stable.
Thanks again DCD u Da MAN!!!!!!!!
Make Sure to remove---> _fixed <---from the end of the file before u place it in the kitchens folder.
Download
http://rapidshare.com/files/108106961/Titan_DCD_3.0.4_FIXED.rar REALLY FIXED this time LOL
thank i'm looking for this. I ran into error error nk.dat
AstronusX said:
thank i'm looking for this. I ran into error error nk.dat
Click to expand...
Click to collapse
Sorry i forgot to change it from os.paylod to nk.fat, im up loading a fix right now thanks.
Errors in PPCkitchen
King - Thanks for putting this together
Unfortunately, I'm getting an error message (a bunch).
I downloaded the main file and did the updater.
When I go into BuildOS and select DCD 3.0.4 5054 or 5060, I am bombarded with error messages "Internal Error - Option.xml GUID not found (PROGRAM - xxxxxxxxxxxxxxxxxxxxx) where the "Program" is the name of the program and the x's are registry keys.
After I click ok 100 times to get through to the Kitchen, it allows me to select programs and build the OS, but once I install it, nothing actually gets installed on the phone.
Do you know what is causing this? Any help would be appreciated.
Thanks,
mfrish said:
King - Thanks for putting this together
Unfortunately, I'm getting an error message (a bunch).
I downloaded the main file and did the updater.
When I go into BuildOS and select DCD 3.0.4 5054 or 5060, I am bombarded with error messages "Internal Error - Option.xml GUID not found (PROGRAM - xxxxxxxxxxxxxxxxxxxxx) where the "Program" is the name of the program and the x's are registry keys.
After I click ok 100 times to get through to the Kitchen, it allows me to select programs and build the OS, but once I install it, nothing actually gets installed on the phone.
Do you know what is causing this? Any help would be appreciated.
Thanks,
Click to expand...
Click to collapse
Is this your first time using the kitchen?
King_tee - I had to do alot of editing to get ALL the errors to go away. I had to remove the welcomehead96.png, also had to remove a few other items.... like remotedesktop..... I guess I should have taken a log of what I did....
Edit - However - VERY nice job getting it to where it is..... Thank you
Thanks will try. The BuildOS in the regular kitchen is crashing so I can now cook a kitchen.
Also will my OEMs made for the 3.0.1 rom work if I put them in the build os directory. I didn't use the OEMizer w/ BuildOS. It appears to be the same just w/ a different save directory.
azclown said:
King_tee - I had to do alot of editing to get ALL the errors to go away. I had to remove the welcomehead96.png, also had to remove a few other items.... like remotedesktop..... I guess I should have taken a log of what I did....
Edit - However - VERY nice job getting it to where it is..... Thank you
Click to expand...
Click to collapse
No prob az i forgot about getting rid of those files. I thought i got all of them. I will upload a new file with the fixes for those who haven't downloaded it yet.
NEW FILE UP LOADED
Let me know if its working for you guys
As of this morning, the version I downloaded still gives an error (can't find HTC Sliding Sound module) when trying to load the selections.txt file for the DCD kitchen.
drgreenberg said:
As of this morning, the version I downloaded still gives an error (can't find HTC Sliding Sound module) when trying to load the selections.txt file for the DCD kitchen.
Click to expand...
Click to collapse
The sliding sounds module is in the DCD OEM's folder......when u open it up in the kitchen it should come up as a selectable OEM. At then point all you have to do is select it.
Bell?
Does the kitchen work for Bell phones? It does not seem to be in the carrier list.
jondixon said:
Does the kitchen work for Bell phones? It does not seem to be in the carrier list.
Click to expand...
Click to collapse
I don't know if it does.Are you are referring to the ppckitchen or DCD's Kitchen?
What i have provided is just a modified version of DCD's work (all credit goes to him) that will work in the ppckitchen.
You can check over here http://forum.ppcgeeks.com/showthread.php?t=23206
if you are talking about the ppckitchen, and they should be able to answer your questions.
If you asking about the DCD kitchen you can ask over here http://forum.xda-developers.com/showthread.php?t=385336 and im sure he will help you out.
I guess the obvious question is, what's the difference between the two kitchens?
DCD's kitchen is built around his ROM. The PPCkitchen kitchen isn't designed for any specific ROM or device.
Advantages of DCD's kitchen:
It's what DCD is using, so you know it builds his ROM like he intended it.
Advantages of PPCkitchen's kitchen:
Easy to install.
Prettier front end.
More error checking.
More OEMs to pick from.
Self updating.
Device dependency/exclusions supported
Carrier dependency/exclusions supported
OEM dependency/exclusions supported
Easy to move same configuration from one kitchen to the next.
Effortless switching between ROM configurations and kitchens
Splash/animation support
gguruusa said:
DCD's kitchen is built around his ROM. The PPCkitchen kitchen isn't designed for any specific ROM or device.
Advantages of DCD's kitchen:
It's what DCD is using, so you know it builds his ROM like he intended it.
Advantages of PPCkitchen's kitchen:
Easy to install.
Prettier front end.
More error checking.
More OEMs to pick from.
Self updating.
Device dependency/exclusions supported
Carrier dependency/exclusions supported
OEM dependency/exclusions supported
Easy to move same configuration from one kitchen to the next.
Effortless switching between ROM configurations and kitchens
Splash/animation support
Click to expand...
Click to collapse
I honestly don't think you give DCD enough credit for his work.... Here are some more Advantages....
Easy to use
Builds a basic ROM with only 2 clicks of the mouse.
Can be used behind firewalls.
No IP logging when you use it. (I had been told this was logged with your login name)
In all fairness both systems work very well, while the PPC kitchen has a more elegant streamlined interface, I do believe the end result is the same, a working ROM the way "I" want it.
error
hey guy anybody else getting an error unable to make file
when it goes to unpack the ppcgeeksoem rar
azclown said:
I honestly don't think you give DCD enough credit for his work.... Here are some more Advantages....
Easy to use
Builds a basic ROM with only 2 clicks of the mouse.
Can be used behind firewalls.
No IP logging when you use it. (I had been told this was logged with your login name)
In all fairness both systems work very well, while the PPC kitchen has a more elegant streamlined interface, I do believe the end result is the same, a working ROM the way "I" want it.
Click to expand...
Click to collapse
Could be because DCD has only a little to do with what we're talking about (which I gave him credit for). That's Bepe's buildos you're looking at, and essentially what we're comparing is Bepe's buildos w/ DCD integrated against PPCKitchen's buildos w/ DCD integrated.
You can't seriously suggest that Bepe's buildos is easier to use - the interface is practically identical! Both are about the same difficulty to use in their most basic, unaltered configurations, and both can build a basic rom w/ 2 clicks. Installing, configuring, starting, and maintaining is a lot different however...the nod hands down goes to ppckitchen there. Once you get past a basic configuration, PPCkitchen's buildos is unchallenged.
The proxy/firewall thing is fixed (general release this weekend) and it doesn't log IPs (never has).
Bepe's buildos get's the nod for no internet connection required, and the previous version (I don't know about v2) get's the nod for Linux compatible. Bepe's buildos also get's the nod for being more interfaceable to other projects and having more projects using it, but none of that is related to the original question (except maybe linux compatibility). [EDIT: v2 isn't native linux compatible, so no nod there.]
All of this is not too suprising, as PPCkitchen's buildos is, at it's core, an evolution of Bepe's Buildos.
I give credit to all sources DCD's kitchen / PPC Geeks kitchen and more.
They both offer the tools to make a ROM to your likings, some better then other, but the fact of the matter is that it gets the job done.
What PPC Geeks version is doing is making a bit more user friendly ( in my opinion ), but I still used DCD's kitchens because I really don't add any extra OEM's to my ROM's unless it is a specifically Themed ROM and then again I can get it done with both kitchens with ease.
I guess users will just have to test them both out themselves to see if they prefer one or the other.
What would be great is if we can have a Modifier / virtual simulator / kitchen where we can find ways to modify our ROM's / PPC's to their best potential ( such as drivers, RAM Management that works / compatibility with different OS and maybe interface change support ).
A virtual simulator to test out all of our modifications by simulating our respective device just as if we were to cook the ROM ( this could save tons of time rather then just flashing all the time or preventing an accidental bricking of your phone)
And a Universal kitchen for practically any Device ( well TITAN at least for our use ) that works on XP, Vista, MAC, and even Linux.
Im sure with all the developers on this forum and on ppcgeeks we would be able to get this done some time in the future.
Just an Idea....
[email protected]$ said:
What would be great is if we can have a Modifier / virtual simulator / kitchen where we can find ways to modify our ROM's / PPC's to their best potential ( such as drivers, RAM Management that works / compatibility with different OS and maybe interface change support ).
A virtual simulator to test out all of our modifications by simulating our respective device just as if we were to cook the ROM ( this could save tons of time rather then just flashing all the time or preventing an accidental bricking of your phone)
And a Universal kitchen for practically any Device ( well TITAN at least for our use ) that works on XP, Vista, MAC, and even Linux.
Click to expand...
Click to collapse
PPCkitchen buildos is actually the closest you can come currently for easily swapping components around, and there's a universal kitchen here on xda that supports many devices (way more devices than PPCkitchen does).
Don't hold your breath on the hardware emulator
lightbiter said:
hey guy anybody else getting an error unable to make file
when it goes to unpack the ppcgeeksoem rar
Click to expand...
Click to collapse
You'll have to elaborate a little better. If I had to guess, however, I'd say that you might have an older version of winrar installed. As a workaround, you can manually extract and modify the selections to use the extracted dir instead of the .rar.
Since i'm not going to cook just yet for the Pro, nor am i helping out any specific crew Over At the Pro (SPC crew will come over to Pro someday anyway).
I have decided to make a OEMMORT Packages Repository.
For those that want to cook with the utmost optimized packages for their Pro.
OEM PACKS
To use these Optimized Packages to Cook (specifically with Touch Pro In Mind), you always need the the MortScript Base.
So if you use more or less packages the RFO.mscr & CLASC.mscr need to be adjusted appropriately to correspond with the correct File Operations.
Mort Script 4.112.b7
AdobePDF_2_5_103401_01
IA_ZIP_1_21_18171328_1
More coming eventually.
Explanations
If you do see the Logic and and improvements this adds to cooking control and performance enhancement, then don't forget to mention the SPC-MORT-COOKING Style, Wax in Wax Out
Any Comments, Opinions, Ideas or Questions welcome.
TNX to the rest of the bengalih for some pointers & SPC crew for testing and helping out.
And thanx of course to MORT.
Don't Know MortScript? Shame on you. (neither do i)
Donny Bahama's easy to carry Mortscript Manual in HTML:
http://forum.xda-developers.com/atta...9&d=1214102654
excellent stuff
Hi Noonski... Very interesting concept.. Great Works! Cheerz..
would it be possible to put the cab files from UC all into 1 zip file to save space ?
da_jojo said:
would it be possible to put the cab files from UC all into 1 zip file to save space ?
Click to expand...
Click to collapse
ExactMundo.
If you'd make the cab files into OEM packages first.
I have a WNDWS.zip
PRGF.ZIP
and a MYDOCS.zip
But even that would not be needed as one zip file should be able to do it.
As long as the Makedir command is used in a Mortscript before the Zip is extracted for folders that do not exist unless you have the complete folder structure in the zip files.
Unless you mean the Cabs from the UC on your SD card.
But even then you could also only extract just a cab at a time.
So i'm not sure you meant the ROM Autorun Cabs or the SD UC cabs?
Also unzipping the files instead of having them in Rom, or making the links with a script removes that darned ROM Read File Protection.
yes yes yes that is what i mean exactly my friend
i mean both ... it would save space on the storagecard as well as remove this freaking writeprotect on the dirs. dir structure in the zip file would be the best option i think as it copies 1 on 1 without setting userrights.
this writeprotect option is set on a hidden part of the systemflashdrive. in the mft i think. strange thing is that i got acces to my windows folder through activesync and it doesnt work on vista mobile device center.. frankly i have no idea what i did but it seems something in the pc as it works on my xp machine and not on vista. i didnt change anything yet on the phone itself relating to this.
pocketcommander www.totalcommander.com is able to ignore or overwrite the writeprotected files in windows dir so there must be a sollution to this.
i dont have the proper tools to do all this stuff but it would be the fastest way to extract all files from all cabs one need into one zip file and let mortscript handle the unpacking and settings of the registry. this way theres no need for autorun cabs merely the UC SD installer. maybe someone can make an nice logo for the custom uc installer.
da_jojo said:
yes yes yes that is what i mean exactly my friend
i mean both ... it would save space on the storagecard as well as remove this freaking writeprotect on the dirs. dir structure in the zip file would be the best option i think as it copies 1 on 1 without setting userrights.
this writeprotect option is set on a hidden part of the systemflashdrive. in the mft i think. strange thing is that i got acces to my windows folder through activesync and it doesnt work on vista mobile device center.. frankly i have no idea what i did but it seems something in the pc as it works on my xp machine and not on vista. i didnt change anything yet on the phone itself relating to this.
pocketcommander www.totalcommander.com is able to ignore or overwrite the writeprotected files in windows dir so there must be a sollution to this.
i dont have the proper tools to do all this stuff but it would be the fastest way to extract all files from all cabs one need into one zip file and let mortscript handle the unpacking and settings of the registry. this way theres no need for autorun cabs merely the UC SD installer. maybe someone can make an nice logo for the custom uc installer.
Click to expand...
Click to collapse
I think for that for the SD Autorun UC solutions there are already a few good solutions around some even supporting Mortscript.
And they all are pretty user friendly to.
Depending on what a user wants and knows, using mortscript being cooked in just gives them more freedom to play around customizing a cooked rom.
But it would need more hand work using your method, but it is possible of course.
It boils down to, do you like making Mortscripts to change registry settings or do you prefer making PROVXML files?
And not everyone is into decompiling cab files to make them fit their exact requirements.
But there's only one rule, Copy the Script to device memory and a folder name tat does not contain a space in it's path. And then run the script.
As the Exec: command from autorun doesn't like that.
But mostly the main way i use it is for the Cooked Autorun part.
I control when the Welcome wizard is run, Before Autorun or after the boot.
I can remove the extra parts of the Networkwizardauto.exe files and also run the networkwizard when i want during the process.
All i need to ad to my process is to open the Locale Preferences dialog during this process and then finish it of with Syncrotime. (or asking for the choice if you want threaded SMS on or not, the possibilities are plenty)
Put all the Setting up your device options after each other for those users that don't have the know how of how to use UC to setup their personal settings.
I even delete the back up files for the one App that i only get installed correctly through a cab file
DelTree( "\Windows\AppMgr\SRS Labs SRS WOW HD" )
So i hope that those that cook or customize and want even more control and detail into what happens can appreciate this.
I know i'll keep using this, and adjusting all my OEM packages to it. Because i have experienced the overall speed improvements in the Rom because of it.
I'm not a Pro in Mortscript and myself i only use the fairly simple commands.
i see.. thnx for explaning
it would be far simpeler using the xmlprov
unless one requires the extra functionality of mort script
the SRS wow HD is a driver enhancement so it needs the system to detach the driver which is only possible with the installer . hence cab files work good cause the're installed by the windowsinstaller which can temp disable the driver.
Instead of MortScript, there is a Yonsm's CeleCmd that perform roughly the same thing.
Check it out!
http://www.yonsm.net/read.php?329
V
vibranze said:
Instead of MortScript, there is a Yonsm's CeleCmd that perform roughly the same thing.
Check it out!
http://www.yonsm.net/read.php?329
V
Click to expand...
Click to collapse
Hey Vibranze, Long time no See.
Would you mind translating
Mort has a bigger fanbase here on XDA.
Yeah, long time no see How are you?
I really not used to your new avatar, without the cigarette it's not like you at all hehe
Actually you can try to download it and check out the sample, it's very easy to understand. I attached here for you
Anyway, here is the translated page by Google.
V
Noonski said:
Hey Vibranze, Long time no See.
Would you mind translating
Mort has a bigger fanbase here on XDA.
Click to expand...
Click to collapse
Explanations
What Does RFO.mscr do?
What Does CLASC.mscr do?
Which Packages Contain Modules and Why?
There's Files Missing from the Packages?
What Does RFO.mscr Do?
Well this script is copied to the regular Start up Folder in Windows.
I use short file names because as much as possible for anything that goes into Windows folder and have no other use being in the Windows folder then being copied by initflashfiles to another folder.
RFO.mscr basicly is the only file i use an initflasfiles.txt for (goes to \Windows\StartUp\ReplaceFileOperations.mscr)
Because after that it takes over the File Operations of the Default build in initflashfiles method.
Why?
Well You don't need actual shortcut files present in ROM to make them.
Code:
CreateShortcut("\Windows\StartUpDisabled\btdwake.lnk","\Windows\btdwake.exe")
in the RFO i don't put that much actual File Operations.
Only the ones that might be useful.
(Why start up WiFiInit.exe during autorun, if it's only useful after the Autorun reBoot?)
Code:
CreateShortcut("\Windows\StartUp\WiFiInit.lnk","\Windows\WiFiInit.exe")
I basicly set up the Second mortscript that will run after the Autorun reboot.
And i make sure the script is not to short. A script that is to short might actually copy the second script so fast into the autorun folder that it will actually be run immediately at during Autorun.
And i make sure the script deletes itself
Code:
RegDeleteKey( "HKLM" , "Services\SqmUpload" , TRUE , TRUE )
RegDelete( "HKLM" , "init" , "Launch99" )
SetFileAttribute("\Windows\StartUp\ReplaceFileOperations.mscr", "readonly", FALSE)
SetFileAttribute("\Windows\StartUp\ReplaceFileOperations.mscr", "system", FALSE)
CreateShortcut("\Windows\StartUp\WiFiInit.lnk","\Windows\WiFiInit.exe")
Copy( "\Windows\CLASC.mscr", "\Windows\StartUp\Clean AutoShortCutStartUp.mscr" )
Delete( "\Windows\StartUp\ReplaceFileOperations.mscr" )
So you can choose during which Boot you want to do what.
But it's better to do it after the first Reboot in case there is no Autorun installation and the phone reboots before finishing the RFO script.
So the Yummy goes to the CLASC.mscr.
What Does CLASC.mscr Do?
Well this does the actuall JuJu...
It takes over the Job of AutoAttribute.exe, so that can be kicked out of the Rom.
Code:
SetFileAttribute("\Windows\StartUp\Clean AutoShortCutStartUp.mscr", "readonly", FALSE)
SetFileAttribute("\Windows\StartUp\Clean AutoShortCutStartUp.mscr", "system", FALSE)
It Takes over the Job of AutoShortcut.exe and initflashfiles.
(less autoshortcut.provxml files in the final rom for the people to lazy to put these into a .rgu file for correct cleanliness)
Also Autoshortcut.exe is set up to run and check the regsitry at every Boot up, so out with this nonsense.
Code:
MkDir("\Windows\Start Menu\Programs\Office")
CreateShortcut("\Windows\Start Menu\Programs\Office\Adobe Reader.lnk","\Windows\AdobeReaderLE.exe")
And eventually it run some Post Stuff to make setting up the device easier at first boot.
Code:
Run("\Windows\ConnectionSetup.exe")
Delete( "\Windows\StartUp\Clean AutoShortCutStartUp.mscr" )
Message("Thank you for installing A SPC Optimized Rom. ","Installation Finished")
Also sometimes people encounter a registry setting that does not get applied directly because of .rgu or .provxml conflict.
So instead of making a new EXTRA .provxml file to fix this.
The registry setting can be added to a file that is already there.
Code:
RegWriteString ("HKLM", "Software\Microsoft\MediaPlayer\Skins", "DefaultPortraitSkin", "\Storage Card\My Documents\Windows Media Skins\Mono SPC\portrait-htc-touch.skn")
RegWriteString ("HKLM", "Software\Microsoft\MediaPlayer\Skins", "DefaultLandscapeSkin", "\Storage Card\My Documents\Windows Media Skins\Mono SPC\landscape-htc-touch.skn")
Or create a new start up script that runs at every start up when you have these annoying Registry settings that for some reason like to reset to a specific default value.
Code:
WriteFile("\Windows\StartUp\FixRightSFTKey.mscr", 'RegWriteString("HKCU", "Software\Microsoft\Today\Keys\113", "Open", "\Windows\Submenus\Contacts.mbi")^NL^RegWriteString("HKCU", "Software\Microsoft\Today\Keys\113", "Default", "Contacts")')
Less headaches going trough all the files finding the conflicts, as you now have a sure fire hit to get the registry right.
And we all know that eventually you will stumble upon the rgu or provxml file that is causing Havoc. But at least you don't have to stay awake pounding your head to find them.
Which Packages Contain Modules and Why?
Well the ones that do have Modules instead of regular files most propalby..
Work as a Module.
Show improved starting up of the application
Can be made into a module to start with (not all files like this)
Show improved handling speed or usage performance.
So when you do find Modulated files in the packages, these have been tested and found worth modulating.
These days most of the kitchen's have G'Reloc.exe build into the cooking process.
So the chance of Modules overlapping a specific memory allocation/space is fixed.
Some kitchens also offer this functionality to Make Modules of files.
But in some Junior Cheffs cases, that usually will result in (nice term coming) OverModulating.
If the kitchen you are using does not run G'Reloc.exe automatically please do so manually when cooking packages with modules.
Update 2009/04/12
Here is a working cab to enable "Rogers/Fido Call Display" by Captain_Throwback. This cab has been tested and proven to work with many ROMs. I've personally tested it on "Energy" and "RoMEOs" ROMs and it work like a miracle. A big bravo to you, Captain
----------------------------------------------------------------------------
The QUICK/EASY method on Post #14 only work for ELITE RC2 (cab file included)
----------ROMs that work for Raphael----------
NATF's v4
Lantis OS 21009 AKU 1.5.0 v3.00
RRE Canadian 4.1
PROven ROM 1.12
Elite RC3 will include this option
For Da_G ROM and Shipped ROM, you simply have to replace the dll file
----------This is how you do it, for chefs----------
After 33 hours straight non-sleep, and plenty of pm to Da_G and NATF, I can proudly say that we've found the perfect answer for this problem
and finally we can put an end to this question "how to make Rogers/Fido Call display to work?"
I've tested this and believe that this solutions may work for any ROM. So far I've tested with 2 of NATF's ROMs, but I need someone to test
this on Kaiser and other device as well. You don't need to used a Shipped ROM, but you can apply these step to any of your favorite ROM.
2 simple steps in summary:
First you need to cook rilphone.dll file into your ROM in the folder /OEM/OEMDrivers/
Second, you need to change the file that setup all the registry key to your device when you flash
For Fuze (may be different for Kaiser), this is the file: /OEM/OEMDrivers/de3f3189-9f71-4162-9f26-39393dcc8c94.rgu
(I attach the original file from Da_G's clean ROM)You can either just replace this file or simply go in the file and Make
sure that all lines related to these regs are the same as the one I've posted here (took from Da_G's ROM)
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
[HKEY_LOCAL_MACHINE\Software\Microsoft\RIL]
POST #12 includes all registry lines that I've modified
The Files are attached.
----------How to cook rilphone.dll into your favorite ROM, from Da_G's words----------
Code:
[B][COLOR="Indigo"]-=01=-[/COLOR][/B] Download a ROM Kitchen for your device, for Fuze is RaphaelKitchen
[B][COLOR="Indigo"]-=02=-[/COLOR][/B] Extract Kitchen
[B][COLOR="Indigo"]-=03=-[/COLOR][/B] Copy your favorite ROM *.nbh file into \BaseROM\ folder (from extracted Kitchen)
[B][COLOR="Indigo"]-=04=-[/COLOR][/B] Rename your *.nbh file to RUU_Signed.nbh
[B][COLOR="Indigo"]-=05=-[/COLOR][/B] Launch "RaphaelKitchen.CMD" from *Kitchen\ folder
[B][COLOR="Indigo"]-=06=-[/COLOR][/B] choose "e" for extract, then "a" for from BaseROM "RUU_Signed.nbh
(if everything work so far, your dos should be running on it own now)
[B][COLOR="Indigo"]-=07=-[/COLOR][/B] When it's done, check if you have these three main Folders
+/OEM
+/SYS
+/ROM
(make sure they are not empty or only have 1 sub folder. if this is the case,
then your favorite ROM is protected... ask the cook nicely to share with you
those 3 folders)
[B][COLOR="Indigo"]-=08=-[/COLOR][/B] replace these 3 files into /OEM/OEMDrivers/
[URL="http://forum.xda-developers.com/attachment.php?attachmentid=141542&d=1230689478"]+"rilphone.dll[/URL]",
[URL="http://forum.xda-developers.com/attachment.php?attachmentid=141541&d=1230689478"]+"de3f3189-9f71-4162-9f26-39393dcc8c94.rgu"
+"de3f3189-9f71-4162-9f26-39393dcc8c94.dsm"[/URL]
[COLOR="Red"][B][SIZE="2"]It's recommended that you modify the *.rgu file instead of replacing it for a moded ROM,
because of all the tweaks chefs have added.)
For list of registries that I've changed in the *.rgu file, [URL="http://forum.xda-developers.com/showpost.php?p=3106249&postcount=12"]READ POST #12[/URL][/SIZE][/B][/COLOR]
[B][COLOR="Indigo"]-=09=-[/COLOR][/B] Launch "RaphaelKitchen.CMD" from *Kitchen\ folder again
[B][COLOR="Indigo"]-=10=-[/COLOR][/B] chose "cf" for cook and flash a ROM, then "b" for "if you want to use the
new BuildOS+Package..."
[B][COLOR="Indigo"]-=11=-[/COLOR][/B] Ervius Package _tool+BuildOS windows will launch, choose "BuilOS" tab
[B][COLOR="Indigo"]-=12=-[/COLOR][/B] click on "Load ROM", now choose your Kitchen/ Folder where you have
OEM/ROM/SYS folder, then click ok
[B][COLOR="Indigo"]-=13=-[/COLOR][/B] Click on RUN, once it finished loading the ROM. When you see the
word "Done" Close Ervius by clicking on the "X" button
(your DOS will run again, and ask you to press any key to start... Press
the "any key" :p )
[B][COLOR="Indigo"]-=14=-[/COLOR][/B] While it's running, it will open a tables with a bunch of numbers that
you don't understand
(it's checking the memory)... just close it by clicking on the "x" button.
(your Dos will run again, till you get your favorite Flash Window come up...
from here, you're on your own)
Don't forget to HardSPL your device before FLashing your device.
Let us know if this method work for you.
I'm also inviting all the Chefs to join the fun and provide us a Canadian version.
----------Credits----------
This tweak isn't perfect, but took me a while to make Rogers/Fido Display work. However I wouldn't be able to get this far without the helps of Da_G, NATF, trueg and a bunch of other people that I've bugged.
At least give some credits to those who have spent so much time to make this finally happened. Like Da_G said, a donation isn't required, but always appreciated.
Donate
Also, thank nitroblu and y2whisper and other Canadian users who has tested and post their results
There were many bounty offering for this discovery, but none of them keep their words... so disappointed... anyway
----------Found issues----------
1- Does not work while MSVC phone notification is activate.
2- May have issues with QuickGPS (not yet confirmed)
3- It froze my device every-time I run it with spb Wireless (need confirmation)
Can any Mod Change the topic of this one to "[Tut]First step to Canadian ROM, Rogers/Fido Display on your Fuze"
Click edit on the first post, then click advanced edit, you can change the topic from there
Da_G said:
Click edit on the first post, then click advanced edit, you can change the topic from there
Click to expand...
Click to collapse
Thank you... Now, I'll leave the Rom Cooking to the real Chef... I'm going to bed
so happy now
Hi pandaboyy,
Thanks for doing all the hard work. I am in Toronto and use Rogers and ever since I got my Tilt2 earlier this year I have been missing the name display. I just got my Fuze from the states today and installed NATF v3.2 rom. I look forward to having name display working again.
Just one question: any way to put this in a cab or build it into NAFT roms?
Thanks again.
Rob.
talonrob said:
Hi pandaboyy,
Thanks for doing all the hard work. I am in Toronto and use Rogers and ever since I got my Tilt2 earlier this year I have been missing the name display. I just got my Fuze from the states today and installed NATF v3.2 rom. I look forward to having name display working again.
Just one question: any way to put this in a cab or build it into NAFT roms?
Thanks again.
Rob.
Click to expand...
Click to collapse
Hey Rob,
I was about going to TO today to celebrate New Year Eve, but since I didn't sleep I got lazy out and drop the plan (true story). I don't think a cab would do the job. Da_G did explain it, but trust me, I still don't understand why
Da_G said:
Yes, the reason my method does not work is because the rilphone.dll is not signed with a trusted certificate as I stated..
Click to expand...
Click to collapse
And since I'm far from a chef, I really don't know how to cook a cab sorry.
However, try the cooking process that I mentioned in the first post. It's as easy as 1-2-3 and it's fun to start understand a little bit how your device work. Once you open the "de3f3189-9f71-4162-9f26-39393dcc8c94.rgu" file, you'll see that's the whole reg setting of your device. This may helps in the future, because you can actually customize your ROM so that whenever you re-flash it, your reg is already added.
Just try the Kitchen_Raphael (it's small and very easy). It'll take you about 15min to do the whole thing... with NAFT's permission, I'll try to release v3.2 with Rogers display. However, here is a good news for you; NATF is trying to release the first Canadian ROM very soon
Help me to Help you
I was trying change the entry in de3f3189-9f71-4162-9f26-39393dcc8c94.rgu file instead of replacing it to keep all the Tweaks that NATF has done. However, I come up with this error when I tried to build the ROM
"Error building default.hv and user.hv! (see "BuildOS-log.TXT")
I take a look at the file again, and I don't see any important different except for the file properties (ignore the size). Look at the image. The working file is hidden and the hidden option is disable. The non-working file is hidden, but not disable
how do I change make the file hidden and disable the option? I know that DOS can do it, but I just don't know the command.
EDIT---------------------- Solved the problem, but still want to know how to disable Hidden option-----------------------
Ok, I've read several post around the forum, and quite honestly, it didn't help much.
so I did a trial and error... If you want to edit your the de3f3189-9f71-4162-9f26-39393dcc8c94.rgu instead of replacing it, Don't overwrite the file.
1- After you finish to edit save it with another name eg: de3f3189-9f71-4162-9f26-39393dcc8c94_test.rgu.
2- Delete the original file (or move it somewhere else to be sure)
3- Rename your test file to the original name: de3f3189-9f71-4162-9f26-39393dcc8c94.rgu
4- Right click on the file, Properties then make it Hidden
(You may find this funny, but this is my amateur way)
monx said:
that file has system attributes. run this from command prompt to remove all attributes & locked attributes.
attrib -s -h -r -a filename.ext
your rgu file must hv unicode encoding, REGEDIT4 in line 1 & blank space on last line to avoid rgucomp error.
Hope this helps.
Click to expand...
Click to collapse
You mean
attrib +s +h +a filename.ext
then leave 1 empty line on the last line... do I have to add 1 space as well?
Just has to end with a blank line, rather than ending with a registry entry
Da_G said:
Just has to end with a blank line, rather than ending with a registry entry
Click to expand...
Click to collapse
Cool, thanks
Ok, I have successfully change the rgu file. It's one of these Lines, but I don't know which yet and I have no energy today to test 1 by 1 again... so if you can test it for me it would be great
Here are the lines that I've changed to make Call display work
Code:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL] ; for HTCmaskW1
"HTCmaskW1"=dword:1871
"HTCmaskW1BitMask"=dword:FFFFFF
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL] ;for A5/2, A5/3
"En52"=dword:1 ; A5/2
"En53"=dword:1 ; A5/3
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL] ;for remove RX Diversity
"RMRXDiv"=dword:0 ; Enable
[HKEY_LOCAL_MACHINE\Software\OEM\RIL]
"DisH"=dword:2
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"DisableAutoPickupAtSilentMode"=dword:1 ;disable by default
add ---> [HKEY_LOCAL_MACHINE\Software\Microsoft\RIL\APIInfo\69]
"Timeout"=dword:7918 ; 31 sec.
[HKEY_LOCAL_MACHINE\Software\Microsoft\RIL\APIInfo\82]
"Timeout"=dword:1D4C0 ; 120 sec.
[HKEY_LOCAL_MACHINE\Software\Microsoft\RIL\APIInfo\81]
"Timeout"=dword:1D4C0 ; 120 sec.
[HKEY_LOCAL_MACHINE\Comm\Cellular\RIL\RemoteCalltype]
"CalltypeDLL"=" PTTCalltypeCallback.dll" ; DLL containing the callback routine
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000100c"=dword:800 ;Service Loading (SL) Message Policy
[HKEY_LOCAL_MACHINE\Software\OEM\RIL\OperatorContexts\20801] ;Orange FR
"GPRSContextNumber"=dword:2
"UMTSContextNumber"=dword:2
[HKEY_LOCAL_MACHINE\Software\OEM\RIL\OperatorContexts\20810] ;SFR (Voda FR)
"GPRSContextNumber"=dword:2
"UMTSContextNumber"=dword:2
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"BattSuspendTimeoutBackup"=dword:3C
"BatteryTimeoutBackup"=dword:1E
"BattSuspendTimeoutInCall"=dword:30
"BatteryTimeoutInCall"=dword:30
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"EnableIMSIAttachedIcon"=dword:1
Perhaps someone can pick this up for me since I'm not much of a registry guy.
Here is a weird thing that I found about this Tweak
When someone call, the ID will display and all... However, in Call history, it will only display the caller Name if it's a missed call. If you answer it, then it won't show the name ID in call history, but only the number... I'm testing it with FuzeBerry v6 theme. Can anyone confirm this?
and if you know how to fix this, it would be great
Ok, for this tutorial, I deserved a kiss
History:
you all know how I didn't sleep for 2 days just to find what needed to be done to make it work. Now after my 10hr sleep and a bunch of parties for new years, I finally found a way to do this without cooking anything. I need someone to test it for me thou. I've tested on NATF's and Elite's ROM and it works. If this work, a thank you would do.
The Basic:
The Main idea to make this work is to replace the rilphone.dll file and add some registry into it, like I was explained in the first post. Some people claimed that those files need to be cooked in, well, you don't however, you can't just replace rilphone.dll it just doesn't work that way. But I found a way
So How to do it?
1- Download rilphone+reg.zip file from this post
2- Extract the file and you'll find
+rilphone.dll
+rilphone2.dll
+rilphone.reg
3- Copy rilphone2.dll into your Device in \Windows\ folder
4- Copy rilphone.reg anywhere
5- Importe rilphone.reg to your registry (I used resco registry to do this)
6- Change this registry from your device
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"Dll"="rilphone2.dll"
7- reboot
8- copy rilphone.dll into your device \Windows\ folder
9- Change the registry back to
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"Dll"="rilphone.dll"
10- Soft Reset
11- Delete rilphone2.dll
12- Soft Reset
13- Give me a hug
***Please report which ROM have you tried this method with and if it works or not***
--------Edit---------
Ok, so it doesn't work for every ROM. It worked with Elite RC2, thou... I'll give it more tries tonight. Stay Tune
If you want to try this process, please make backup of rilphone.dll first
And please try to put step 5 at the end.
Instead of trying all this, try the cab on post #26... if it doesn't work, just uninstall it. Backup rilphone.dll first. Worst case, just do a hard reset.
---------------------
--------ROM tested with cab-------
- Elite RC2 -> Work
- Proven 1.08 -> did not work
- Romeo -> did not work
-------- I'm sick of flashing and hard reset, so I'll stop here. If you're already on other ROM. let me know.
Good to see you we're able to get this working.
I didn't modify any part of the RGU file in OEMDrivers, so I'm just gonna drop the new DLL and the RGU/DSM you provided here into my v4.0 kitchen.
NotATreoFan said:
Good to see you we're able to get this working.
I didn't modify any part of the RGU file in OEMDrivers, so I'm just gonna drop the new DLL and the RGU/DSM you provided here into my v4.0 kitchen.
Click to expand...
Click to collapse
Ya, it should work... however, can you check if the RGU/DSM file didn't affect QuickGPS? I didn't make any change there, but just check for sure.
Finally, I can sleep with ease now...
My next wish, somebody make a cab or 2 to make my previous post easier
Only problem with non-cook method will be, if target ROM is not cert patched, or doesn't have certificate loaded from rilphone.dll signature it will refuse to load rilphone.dll due to not being signed with a trusted cert..
hey pandaboy,
tried this on my fuze but didn't work, (using proven rom right now) my wireless radio stops working after. i even tried starting over by deleting your rilphone.dll file and softresetting to get my phone working and did the steps again. no go.
Same, my radio is not working now either. Is there anyway to get my radio back?
just delete the rilphone.dll file from your windows directory and perform a soft reset
y2whisper said:
just delete the rilphone.dll file from your windows directory and perform a soft reset
Click to expand...
Click to collapse
When i try to delete it it says cannot delete the file.
YES I have searched and read before I posted..
I am attempting to cook my own roms for my Exec, I have d/l and installed a number from here and enjoy the process, so I have downloaded the files as suggested and tried to cook.
I can dump the rom OK and sort and fiddle through the files with no issue, but when I then try to build the rom, BUILDOS.EXE comes up with an error
BUILDOS has encountered an error and needs to close...
I found you had to move the OEM and SYS folder back up one level, but then when you run the buildos it now fails with external component has thrown an exception
Windows XP SP3 up to date with patches
Any ideas most appreciated
no one?
Is the kitchen empty?
BuildOS.cmd
To build:
1. Execute BuildOS.cmd (requires .NET to work)
2. After the entire process, your new ROM will be found in \FLASH folder
Nongs said:
To build:
1. Execute BuildOS.cmd (requires .NET to work)
2. After the entire process, your new ROM will be found in \FLASH folder
Click to expand...
Click to collapse
Obviously you have no idea... Have you in fact done this and obtained a result?
The process is complicated and requires much ammendment to the source data to be even able to dump the rom, but to then edit, re-assemble and produce does NOT work using the kitchen indicated in the original posting.
If YOU have been able to do this, then please feel free to document the full an correct steps taken and the changes you made.
buildos
Yes I have.
I would like to recommend you to read
http://forum.xda-developers.com/showthread.php?t=345735&page=5
since post#47
I think same as your problems.
I have cooked by Atom 6.1 cooking set, never found those problems.