Hi,
I've read through the WiKi on the extended ROM on the blue angel, and i think i have a basic understanding of how it works now.
I have several CAB files (Microsoft .NET framework CAB files, and some of my own). Would i be right in saying that to put these into my Extened ROM all i have to do is...
- Unlock The Extended ROM folder on my blue angel
- Paste in the CAB files
- Edit the config file to add my CAB files to the execute list.
- ReLock Extended ROM
Would that work? If i were to create this extended ROM arranngement would it be possible to install it on several XDA IIs so that they would always automatically reinstall my program upon a hard reset? I was also wondering if it would be possible to customise things like the splash screen, menus, and hardware button settings within the Extended ROM?
I hope that wasnt to much of a long question!! Any ideas or thoughts would be great!
Many Thanks
James.
but also remember there is a limitation on the rom max of file size is 16MB.
happy cooking
Hi All,
There are many posts about updating ROMs (OS & Extended) to the latest version (Eg 2.8.7.102), but there isn't much information on how to revert back to an earlier version of Extended ROM which, generally has the customisation files from the service provider.
What I would like to know is how to replace the files in the extended ROM with ones from a backup source (ie I used aWizard to copy the extended ROM and there is a RAR file of these files on the Xda-developers FTP site).
Also, I wonder what file needs to be altered (config?) so that you can cherry pick which CAB files etc to load on reset.
Finally, there are posts which seem to be saying that with the latest ROM's 1.6.x.x and above that you can no longer write files to the extended ROM.? - although you can use Total Commander to delete these files so that they don't reload on a soft reset (But probably reload after a hard reset?)
Sorry is this is going over old ground !!
Many Thanks in advance
John
With 1.6.x and above version your ExtROM is read-only.
To customize your ExtROM:
1. Backup cab files you like from ExtROM (ie the Operator ROM)
2. Flash your device using RUU
3. Test functionality of the backed-up cab files by manually installing them one at a time
4. Backup OS, Radio and Ext rom using aWizard
5. Flash your device with a 1.5.x version using RUU
6. Replace the files in ExtROM with the ones you like on the new rom (from step 3 as well as the backed up ones from step 4!)
7. Restore OS and Radio using aWizard
You now have the same rom as from step 2, but with customised ExtROM
Download the rom121 from hp and use uniExtract to get
hpruu.exe / ceos.nbf / extrom.nbf / radioos.nbf .... and some more files.
When I try to use ER2003Edit to open the nbf, it ask me a password to open the rom image.
Did anyone have this problem before?
Thanks in advance.
I used dumprom.exe to dump the ROM, and mounted the EXTROM using WinImage. I did not tried to modify the ROM, but you cannot create EXTROM using WinImage (or tell me how ).
I have met the same issue, who knows the password for iPAQ 6515 ROM? thanks!
There Is No Password
The ROMs are not encrypted! No password!
You just have to use dumprom (ROM) or winImage (EXTROM)
Modifications shall be done using mkrom for ROM, for EXTROM I don't know.
help me i need this password to edit rom.
Before i get flammed like crazy. I have searched for guides to cooking roms and used all different kinds of kitchens but none seem to work at all. Unless there is something written between the lines that i can't see i just don't think i'm doing anything wrong.
Anyway. When I try an build a rom and create the os-new.nb file imgfsfromdump just crashes and i can't create the file. Sometimes it works but once it fails it doesn't start working for a long time. I'm not sure what i'm doing. I try and dumb a stock rom and rebuild exactly the same but the same thing happens.
If anyone with some xip|sys porting could give me a hand to get past this step i'd appreciate it.
Thanks..
I'm starting to believe it might be a conflict with SP3. Can anyone confirm that they have these kitchens working with SP3?
replace your ImgfsFromDump with the attached version
itje said:
replace your ImgfsFromDump with the attached version
Click to expand...
Click to collapse
Thanks itje. I tried this but it still crashes everytime i try and compile the files. I'm not sure why. Is there something i could be doing wrong? Have you seen this before?
Did ImgfsFromDump ever work for you? (That is, did you try just extract and create the image without modify any content)
For me, I am not following the script in the kitchen completely to create the image. Here is what I execute on the temp directory (w/ dump as sub-directory) and work fine so far. (just make sure you did not remove the imgfs.bin and the payload in extracting the image)
..\TOOLS\ImgfsFromDump imgfs.bin imgfs-new.bin
..\TOOLS\ImgfsToNb imgfs-new.bin os.nb.payload os-new.nb.payload
..\TOOLS\NBMerge -kaiser os-new.nb
Strangly enough it did work a couple of times then i just started getting that error that says "imgfsfromdump needs to close" that basic windows error. I thought it might have been DEP but i made a exception for that program. I'm going to try this and see if i have the same problems.
I'M SUCH AND IDIOT!!! The reason it was crashing is cause i kept building the dump into packages. So i assume it was looking for files in the wrong place which just causes the process to fail. Thanks guys!!!
Can someone help me find this 21109 build to where i can actuallyt port it? I've tried to extract it from various roms and all it does is fail everytime and my phone is stuck at the sony screen.
*******EDIT******
I finally figured out how to get XIP ported but now i'm having a problem with the SYS folder. No matter what SYS folder i use and no matter how many different tutorials i go through i still get the same point. I flash and it sits at the sony ericisson symbol and does nothing. Is there some folders i shouldn't change in the SYS?
run g'reloc on the stock sys folder from x1, note all the values..
then run g'reloc on your new UNTOUCHED sys, where you change NOTHING...no swapping of files (unless you port from vga or qvga, or change locale, but thats another story) then change the values on the new sys with the values from the stock x1 sys, apply changes, and you have ported the sys.
cheers
itje said:
run g'reloc on the stock sys folder from x1, note all the values..
then run g'reloc on your new UNTOUCHED sys, where you change NOTHING...no swapping of files (unless you port from vga or qvga, or change locale, but thats another story) then change the values on the new sys with the values from the stock x1 sys, apply changes, and you have ported the sys.
cheers
Click to expand...
Click to collapse
When i run g reloc i get the same values as i did with the original build. Let me see if i understand the file hierarchy correctly.
1. I run G'reloc where i have my stock ROM's SYS folde. (note those values)
2. then i run G'reloc where my Donor SYS folder with the rest of the crap from the Donor ROM.
3.Then i copy the Donor SYS folder into the location i have my stock ROM SYS folder and overwrite. I run G'reloc again if the information is different from the first time i ran g'reloc i change it and hit do it.
Is this what i should be doing? I do this and i get the same result no matter which ROM i try and port from. I am porting from a touch pro ROM so is there anything i would need to change due to the vga to wvga switch?
swap from the modules marked with red to blue
base_dpi_192_resh_480_resv_640
to
base_dpi_192_resh_480_resv_800
since our device is WVGA you need to have the value set to 800 instead og 640.
So swap the folders with 640 from donor rom to the ones from either blackstone or x1
I can't get anything to work... If i extract the xip from this 21109 build that i have and try an use xipporterex to create the new xip and write it into the os.nb.payload and then merge the files. If i take that os.nb that is created i can build that and it will boot but if i try use the rom build procedure where it makes the os-new.nb file it will never boot. Even if i do nothing but just extract and rebuild the rom will not boot. From this i assume that i'm doing something wrong, 21109 build is corrupted or both. I'm not this inept. This shouldn't be giving me this much trouble with all these tutorials. Can someone please help me out with the exact procedure they use when building an X1 rom with porting over a new build?
Hi, exist any "how to" cook ROM for our Treo750? I'd like to try make my own ROM.
?
any ideas? somebody?
Customize ??
I only know how to customize rom by use exists rom maybe Ruu_signed.nbh or Cheeimg.nbh .
By reading from wiki XDA http://wiki.xda-developers.com/index.php?pagename=Hermes_ROM_kitchen because of Treo750 base on Hermes.
if you want to know how to do , what to do read it from ROM Donalds topic but you can choose any tool for me prefer and (almost) use Want more Storage? Here you go! it has batch file to do all process and 'der hermes rom koch' is good for edit all hv file (hv file contain all registry setting for me I prefer to do after flash by mortscript so I only use batchfile).
Please notify once we use exists rom it mean (for me) we only use to add file or remove file with normaly we can't remove it from rom by easy way such as delete by file explorer because of system will said you can't not delete system file in rom example for me I never use Powerpoint,OneNote so I decide to customize WWE 19199 by remove 2 file and some file and rebuild back to Cheeimg.nbh and after flash and boot I got 67MB free ram for storage and 29MB for Program.
IF you need to make new one from zero I still not information I try to search from google but just know a little due to Treo has square 240x240 and very few people use that seem to be hard to find an information and sure if I got it I will let you or anyone know.
k101d