The device is Pharos137 with 512M ROM.
I am trying to cook a ROM for this device and it fails to boot if add any file larger than 5Mb to OEM folder.
When Google Map cab(which is less than 4Mb) is added to OEM with out any changes to XIP and SYS every thing goes well. Device boots up and installs the cab.
But when I try just adding Skype cab or Copilot or any other cab larger than 6Mb, device fails to boot and struck at spalsh screen!
Is there a setting for IMGFS size? Where is it stored and how do I change it?
Having ROM size of 512M and unable to cook IMGFS larger than 90M is stupid I think. But such is my problem!
Can any one please point me to a solution?
BTW I have gathered various tools and put together into a kitchen. So I might not be having all the tools! I have also ported XIP and SYS and successfully created a ROM that boots. But when I try adding larger files to OEM it fails to boot.
Thanks.
Not even a single reply!
Question:
Am I really stupid asking this question or no one knows the answer to my problem. So which one is it folks?
Now that we are officially started hosting discussions on non-HTC phones, may I ask you to at least post your thoughts on this issue please?
BTW I've read in some place that IMGFS size information some times coded into NK.EXE module. Is this true?
Many thanks.
I have the same Q..
device rom 128M,cooked rom limit 48.9M .when cooked rom more than 48.9M,device halt on the first splash screen.
You have to take in to account things like the radio ROM, XIP, etc when looking at the size of the OS.
What kitchen are you using to build the OS? Many of the tools can resize the IMGFS partition. You may be using up space that's reserved for ImageUpdate, which will be hard coded, but can be resized (tadzios bigstoreagemode resizes the reserved space).
hahahh said:
I have the same Q..
device rom 128M,cooked rom limit 48.9M .when cooked rom more than 48.9M,device halt on the first splash screen.
Click to expand...
Click to collapse
l3v5y said:
You have to take in to account things like the radio ROM, XIP, etc when looking at the size of the OS.
What kitchen are you using to build the OS? Many of the tools can resize the IMGFS partition. You may be using up space that's reserved for ImageUpdate, which will be hard coded, but can be resized (tadzios bigstoreagemode resizes the reserved space).
Click to expand...
Click to collapse
I am not using any kitchen per say since it does not exist for Pahros137. I have put together one my own by using OSNBTOOL, and other IMGFS and XIP port etc.
My device has 512M rom size and when I cook any thing larger than 98M device fails to go beyond flash screen!!!
This is more of a quick fix, but just split the bigger cabs like skype into smaller packages. Or, don't use cabs and see which apps you can run straight out of windows. It will save storage memory.
Yes I can split the cabs and/or install them once windows loads. But my main aim is to cook new TouchFlo into the rom.
So what are my choices now?
Why do you need to put it into a cab? Can't you just cook the manila files (you're talking about manila, right?) straight into the rom?
yes that is exactly what I want to do but ran into size limit. So i was experimenting with various cab sizes to figure out the limit.
I do not think new Manila can be made into a cab!! I have heard many people saying there are many dependencies in creating a cab and has be cooked into ROM unfortunately. Did you try making a cab of manila?
Related
I finally found a method for backing up and modifying the Extended ROM on an XDA2i device.
http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=373&PN=1
Unfortunately, although this method is able to do most of what I want, some of the cab files do not self-extract successfully during the reset process.
Graham. -- Issue resolved. No spaces allowed in Cab file name --
Before you ask, yes the cab files do self-extract successfully if tried manually (i.e. outside of the reset process).
If anyone has any ideas why some cab files work and others do not, please let me know.
I played with the information in the article yesterday.. Some information in the article is incorrect. They state the ext. rom is 24 MB but when following the steps on the website this is incorrect !
Sure, extra drive reports a 24 MB drive but the what's backuped to the SD card doesn't include the whole 24 MB the ext. rom supposedly has !
What I'm typing below is more guess work than knowledge.
"d2s 80000000 3BF0000" probably means "dump to SD card" for a total length of 80000000 hex starting at 3BF0000 hex.
80000000 hex is 2147483648 in decimal. These aren't the amount in bytes that are copied.. I to honest it I have no real idea in what it are but when dividing it by 1024^2/100 you get 20,48. The / 100 is something I made up since that gives me about the amount in MBs I can put in the ext. ROM without having corrupted files. I don't want to experiment with larger values since I haven't studied the tools that are used in the article enough yet.
In short, be sure not to put more than say 20 MB in the ext. ROM and most likely your problems are solved. I personally put an executable sprite backup file in the ext ROM, packaged it in a way it will be copied to storage and run from there. It's the most effective way I could think of to fill an extended ROM. Simply with a fully installed but clean backup of the pocket pc.
Anyhow, that's it for now.
I considered it being a problem with size and reduced the amount of data in the Extended ROM by a huge amount (deleted several of the cab files that I did not need).
This reduced it down to around 13Mb for what it's worth.
All of the files installed to the ROM ok, but when the process which reads the Config.txt file reached the parts regarding two of the cabs I wanted to install, the files failed to self-extract without giving any feedback.
Several other cab files I wanted to install worked fine.
What all this means is that the problem (probably) lies somewhere other than the size of the Extended ROM.
Thanks for the post sparcle and if you find out anything more please let me know.
If anyone else can help here, please feel free to contribute.
Graham.
As above guide:
CE Rom size is 2700000 (hex)
Total backup size is 3BF0000 (hex)
So extended rom size is 3BF0000-2700000 = 14F0000 (hex) or 21,954,560 (dec)
So extended rom size shall not be over than 21,954,560 in total space.
-----------------------
But itsme's document
http://wiki.xda-developers.com/index.php?pagename=AlpineRomStructure
82700000-83f00000 extended rom
So backup range shall be 3F00000. (size = 66060288 (dec) which you can not use 64mb card, you have to use 128mb card to backup)
So sorry, I'll ask my friend ruchonburi to recheck again.
Just a quick note on the sizes you gave above:
83,f00,000 - 82,700,000 = 1,800,000 (hex)
= 25,165,824 (dec) (24Mb) for the extended rom.
83,f00,000 - 80,000,000
= 3,f00,000 (hex) = 63Mb for the whole rom
The document given at the site uses:
80,000,000 to 83,bf0,000 which may miss some of the extended ROM, which may explain my problem.
I will try using the numbers from wiki and see if it works.
Cheers,
Graham.
I tried using d2s 80000000 3f00000 to create the SD Card backup initially and I still had the same problem with some CAB files extracting successfully and some not.
Graham.
Looks like the issue may lie with spaces in the CAB filenames.
If it is I will kick myself for not realising it sooner and then post here to let you know.
Graham.
Ouch, ouch, ouch....
I've finished kicking myself.
The problem was indeed the space in the cab filename.
On the plus side it means that the process works fine.
Graham.
i just want to ask......by cooking Ext Rom....how much free space that can be use after that???? does it effect any upgrade in the future????
The Extended ROM is an area that you cannot normally write to and is not considered part of the memory (as far as I am aware) under Settings/Memory.
By cooking the ROM you can alter what applications get installed when the device is hard reset. The installed applications will take up their normal memory allocation so in that respect it will reduce the amount of memory available to further applications.
It is possible to increase the amount of memory available by cooking the ROM as there may be elements of the Extended ROM that came with the device that you do not actually want installed. This is done either by removing the relevant cab file completely or by removing the relevant entry from the Config.txt file (both should be done, but one or the other will have the same effect).
Hope this helps,
Graham.
gbird, thanks very much for that information. im sorry because asking question just about benefit, not about how and why. thanks again!
Hi fellow alpine owners
I'm keen to follow your tips and do some work in the kitchen.
I have downloaded all the relevant articles from the link provided so thankyou for that.
However i'm reluctant to take the first step with the thought of a unrecoverable disaster on my hands. MY NEW XDA2i!! So before i get started i thought i would consult the experts for any tips and traps for young players.
I've bought myself a large enough quality SD card to dump to.
I guess the aim of the exercise is to a remove unwanted programs and install some of the cool features of Special Edition ROM 1.2 including that really excellent anti theft tool.
Any assistance would be greatly appreciated, with what to remove/ install and how thanks in advance.
Miket
ROM version 1.11.00
ROM date 01/27/05
Radio version 1.03.00
Protocol Version 1337.42
ExtROM version 1.11.162 WWE
First tip, use the process to back up the ROM of the device and keep it very safe.
Since all you will be playing with is the Extended ROM (and not messing with the OS Rom or Radio Rom) the good news is that if you removed all of the files from the Extended Rom you would still be able to boot the device. This gives you an opportunity to remove files to see what they install. If it goes really wrong, you can restore the Extended Rom from the SD card backup.
The XDA2i device does have a lot of room on it for additional items so you can add in extra Cab files or Exe files if you wish. You need to modify the Config.txt file to make the Extended Rom run these extras.
As for which files do what, there is a lot of info available around this site and others and I am afraid I do not have time to go into it at the moment.
I will see if I get some time over the next few days, but work is a little hectic at the moment.
Hope you have fun,
Graham.
Thanks for the speedy reply Graham
Will endevour to make backup this evening and start chopping up extended ROM.
Any thoughts on the instructions provided by this web site.
http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=373&PN=1
Obviously a highly regarded PDA hacker.
I will be working through these. It's a bumber that XDA2i is so arkward.
Thanks for now
Miket
The page is pretty good (that's why I pointed at it)
RomUpdate
The only bit that is a bit short on description is the stuff regarding using the romupdate tool at the top.
If you need a more complete description of this tool then I would take a look at:
http://en.pdamobiz.com/en/forum/PDAforum_posts.asp?TID=62&PN=1&TPN=2
Be aware that the addresses for the d2s command are different for the XDA2 and XDA2i
Rom Structure
The memory address information for the Alpine (XDA2i) is available at this site:
http://wiki.xda-developers.com/index.php?pagename=AlpineRomStructure
RomUpdate Commands
There is also a page describing some of the commands available in the romupdate tool:
http://wiki.xda-developers.com/index.php?pagename=HimalayaBootloaderCommands
XDA2 Cab Files
This site has a description of some of the XDA2 cab files which may interest you (though the XDA2i uses different cab files, some of which have similar names):
http://forum.xda-developers.com/viewtopic.php?t=6470
Soft Reset in the Config.txt File
The last bit I'm going to mention here is that the last item in the Config.txt file soft resets the device. If you remove this item for some reason then adding the line "RST: Reset" on the end of the Config.txt file will soft reset the device automatically for you.
Hope these are of use to you, I know they were all of use to me,
Graham.
Absolutely excellent thanks Graham
Have got as far as using the split tool.
Xp is throwing a 16bit error my way, so i will have to resolve that before i can go any further.
Are you suggesting that when i re-build extended ROM to include "RST:Reset" on the last line in config.txt?
Anyway it's time for bed.
Thanks for the great links, will read through these tomorrow.
Miket
With regards to the RST: Reset command, it is sometimes useful to soft reset the device at the end of the configuration.
This is because some of the Cab files will probably modify the registry and most of these changes will not be picked up until the device is soft reset (the device is still usable, just not using the changes).
Most of the builds that you may come across already do this as a last step in one of their Executables so they do not always include the reset line in the config file. Adding this line to the end will ensure that a soft reset always happens so that registry changes will be used.
Be warned, soft resetting the device will halt the configuration build at that point, so anything after the reset command will never happen.
I hope this makes some sense
Graham.
Hi again Graham
Finally sorted 16 bit issues with the PC. Have loaded SPLIT ROM and created the 3 components. Particularly ext.img
I have also created the virtual drive "X" with "ext.img"
File\properties tells me this is a 24MB file. All good until i wish to open. PC asks if i wish to format disk, i'm not able to read contents any ideas.
TA
Mike
I thought i would try downloading the cooked rom off en.pdamobiz.com as a test. The extended rom opened up perfectly in virtual drive creator. Mine however is an exact match size wise but wont open.
HMMM
I guess the next step is work out what i need and dont need in extended ROM. Assuming i can get past this stage.
Any guidance here would be appreciated.
Miket
Hello guys!
I'd like to modify my german extROM too but I have a little problem: when I'm starting the ntrw.exe (it lay in the basement of my HDD, in C:\) it closes itself!
So I mean, I can't use the ntrw.exe from the PDA-Miz guide to write the ROM-image to my HDD!
What can I do?
Thanks in advance
animelover from germany
As many of you will be glad to hear, I've begun working on typhoon wm5 build 5.1.29.14847.2.0.0
now i've added almost all necessary files. some drivers are left yet, though - camera, sim toolkit and htc obex driver.
Now I need help of real gurus like mamaic and buzz. Here is the point: drivers are added, but still only keyboard works. drivers are added correctly, like modules. I Guess there's something to do with the security. maybe, regenerate packages.sof? but how? also, how to create dsm and how to change offsets in modules? actually, i only need to know how to create dsm and how to add them to registry, and how to create packages.sof. Strange that i boot the os and all the files and registry entries are present, but i see phone of on today screen and only keypad and display work.
Hi, Do you have any working (even bugy) WM5 ready to install? I need it to fix my phone and revert back to W2003.
Thanks
Inquiry
Hey Sp3Dev, just wanted to know whats going on with the new build you have been working on. Did you manage to get the help that you were looking for. I just got this device yesterday to use until my Artemis arrives, but I think I will end up keeping it to replace my d600 just because I love customizing my devices. Hope you are still working on a little somthing for my SP3i.
sp3dev said:
As many of you will be glad to hear, I've begun working on typhoon wm5 build 5.1.29.14847.2.0.0
now i've added almost all necessary files. some drivers are left yet, though - camera, sim toolkit and htc obex driver.
Now I need help of real gurus like mamaic and buzz. Here is the point: drivers are added, but still only keyboard works. drivers are added correctly, like modules. I Guess there's something to do with the security. maybe, regenerate packages.sof? but how? also, how to create dsm and how to change offsets in modules? actually, i only need to know how to create dsm and how to add them to registry, and how to create packages.sof. Strange that i boot the os and all the files and registry entries are present, but i see phone of on today screen and only keypad and display work.
Click to expand...
Click to collapse
I can help a little. I only use the files already listed in the packages.sof. I don't know how to read the file though. I use Bepe's kitchen. When you seperate the files into OS and LOC, you may find some folders only contain a .dsm file. These are extra folders and can be either deleted, or used for holding additional files. these files should already be listed in the packages.sof. You may have to test them one at a time by using the createOS.exe. Now to rebuild a .dsm file, put the your folder in the OEM folder, and createOS. This will automatically rebuild the .dsm files in the OEM folder. I'm sure there is a more elegant method, perhaps by using the kitchen tools directly, but i don't know how. I recently had to translate a chinese AKU 3.2 set into english, and thats basically the method i used. This post was written w/ the assumtion that you are familiar w/ Bepe's kitchen.
Regards,
Jason
Hello.
How are you trying to create this build? Have you started off with the original Typhoon WM5 Beta, or do you use a "true" WM5 build and try to incorporate Typhoon drivers? I suppose you are doing the latter, which I really hope you'll accomplish!
If you need any help betatesting and stuff, please say so
xxxx://www.zxxxu.com/download/3320666/6.5Beta1.rar.html
Based on Sundreams and Xplode´s work, ringtones and kitchen from Swampy and other bits credit to their respective authors
Finally thanks to mikrosoft for providing an open source mobile platform, errr ok scrap that last bit...
FeatureS:
No Ram disk
UC Capable *
A few customized logos and ringtones (Simpsons, StarWars)
fully integrated psshutxp (REBOOT) and akwifitoogle (WIFI_ON_OFF) in Start menu
Screenlock in Start menu (once active press mail + calendar to unlock the screen)
Space invaders in Games
Autorun for ExtROM is working
*SDAutorun runs but .cabs have to be hardcoded to install on SD Card or else will be installed in Storage
Tips:
Do not install CHome and manila2d together as they don´t like each other.
Use the WIFI_ON_OFF program if having trouble with wlan, it can be very handy
Known issues:
Given that CHome is still buggy I recommend to stick to manila2D (and it is part of the ExtROM file included)
GSPlayer complains on first run about being unsigned and hence unable to run, but second time works
I tried to load newer versions of Manila and HTC Album but both .cabs wouldn´t load
ExtROM:
http://www.zxxxu.com/download/3323355/ExtROM_6.5.rar.html
ExtRom contains:
1-AudioManager_2.0.1819.3326.cab
03_HTC_Album_2.0_1818.3829.4.cab
14_BnG_M2D_0.11.allDevKnobiSkin.cab
01_HTC_Enchasements.CAB
08_M2D_PIE_FIX.cab
thnx so fast
hi,the PDA2k is the number 1 that WM 6.5 pro work on the pocket pc`s,and this goes to the good developers in this website,all of you the best,can u add Advanced Config V3.3 in the extended rom?is this useful for manila 2d?can manila 3d works?and ntfs 3.5 may helps?thnx again.
Is Start Menu something like this
?
I mean is any changes vs. sun_dream ROM ?
EDIT : Any screenshoot's ?
problem
hi,i installed your rom in my blue angel but it did not works,after 100% finished and pressing(record+camera+reset)(no,yes,yes) then white screen then back to color screen and stops but the led light works only without light of screen,then i tried again and restart but nothing changed,there is aproblem,i returnd to explode modified sun_dream`s rom no ram disk,work directly,thnx
THNX gloomyboy for that rom
I haven't try it yet,
downloading now..
Regards
For screenshots see my previous ROM
rayatz said:
Is Start Menu something like this
?
I mean is any changes vs. sun_dream ROM ?
EDIT : Any screenshoot's ?
Click to expand...
Click to collapse
not works
hi, this rom is not works, i try it.
this may be off topic - but i am new to the world of PDA's and cooked ROMS - so far i have used sundreams WM6.1 and now have WM6.5
Could someone please explain to me what the RAMDISK is all about? - and why so many people refer not to have it?
it is a virtual disk eating your ram
It is good for other PDAs where for technical reasons if you don´t have the ramdisk you simply waste that space.
In the Blue angel there is no such problem, so no ramdisk equals more ram
Download site not working
Hi Gloomy,
Is there any site where I can download your latest ROM?
Regards,
George
I Don't download this files beacause...
dear sir,
thank you for your rom , bu when I try to download this file from rapidshare , this message shows for me :
"This file is neither allocated to a Premium Account, or a Collector's Account, and can therefore only be downloaded 10 times.
This limit is reached.
To download this file, the uploader either needs to transfer this file into his/her Collector's Account, or upload the file again. The file can later be moved to a Collector's Account. The uploader just needs to click the delete link of the file to get further information."
if it possible, please reupload this file.
very very thank you for your attention.
This weekend I will cook another 6.5 hopefully this time UC capable.
I am afraid in rapidshare it can only be downloaded 10 times.
If somebody knows of a better upload site that does not require registration, please let me know
gloomyboy said:
This weekend I will cook another 6.5 hopefully this time UC capable.
I am afraid in rapidshare it can only be downloaded 10 times.
If somebody knows of a better upload site that does not require registration, please let me know
Click to expand...
Click to collapse
try sharecow.com, no registration needed
Register on megaupload.com it can be downloaded maaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaany times =)
try www.sendspace.com NO REG NEED
Mediafire is better than them all, because it doesn't require anything and it doesn't have any limits, or time counters!
See first post for updated files and download links
Ok I have opted for ziddu, see first post
Feel free to re-upload it to your favourite site and post the links for the community´s benefit
good job bloomy, it's very stable rom.
Any guidance on installation procedure - explicit and simple instructions?
QUOTE=superflyboy;3239489]Any guidance on installation procedure - explicit and simple instructions?[/QUOTE]
create folder ExtROM in your SDCard
unpack the content of the ExtROM.rar file on this folder (should be containing .cab and a few other files=
put BA in serial mode
run BaUpgradeUt.exe to flash the rom
hard reset once it finishes
Then let the instalation continue, should be 5 more minutes.
Your phone will soft-reboot automatically
and you will be presented with the manila2d interface
Hi
When reading about XIP tweaks and increasing free memory, I usually end up seeing this mentioned. What exactly does it mean and how exactly do I do it?
Also, what other cooking tweaks are there for memory and performance that arent really mentioned a lot?
Thanks
I suggest you avoiding this. if you want a bit of speed up delete from xip hd.dll osaxst0 and osaxst1 (or something similar) and increase pagepool a bit
and try keeping wincenls in xip instead of imgfs
ps. doing what you requested is just cut things from xip and past somewhere in oem or sys
Interesting....can you explain what these modules needs to?
Its safe to delete them and this operation its the same for every device?
michyprima said:
I suggest you avoiding this. if you want a bit of speed up delete from xip hd.dll osaxst0 and osaxst1 (or something similar) and increase pagepool a bit
and try keeping wincenls in xip instead of imgfs
ps. doing what you requested is just cut things from xip and past somewhere in oem or sys
Click to expand...
Click to collapse
I delete them from my ROMs every time. It doesn't have any negative effects but I can't see major differences.
Here Hd.dll and Aosaxst0.dll are used for M$ debug. Like some times on pc the apps close itself, and windows asks you to send the details to M$ (example. error number : 893647). We ( users) don’t know what it means, only the developer in M$ know. But I never saw these files report anything to us. SO!!! We don’t need them! they are trash!!
Now Mencfilt.dll is for storage card encrypt. If you don’t use it, you can delete it as well. Have you had this experience where after flashing a new Rom every thing in storage card can’t show any more!!!! but its still use the space in the card. Yes it's because of this file only.
Click to expand...
Click to collapse
More: http://www.techparaiso.com/windows-...and-speed-up-your-windows-mobile-phone-device
Thanks TAEL,
well i do like the idea to not have useless things in Rom even if they doesnt improve the speed......i will cook a new rom soon with these tweaks soon.
Thanks for clarifing me.
So its just moving them to EXT or OEM? Maaan I thought it was way more complicated
Thanks
Hello everyone!I had started a project for our devices (and yes this mean a holl new ROM) I started this days to make something and I managed to do something but need a lot of help from other users of this section of the forum who have knowledge of ROM cooking,so for those of you that want to help improving this project I want a PM from you.
Use my kitchen, with it you can extract ROMs and cook ROMs without problems... I don't exactly know why you are being so overly excited in the General Hacking Forum, since all that you need is already there, use it!
no the prb. is that i need more support for ex how to extract a .nb image?or how to extract from a ROM the programs that it haves?Because with yours i didn`t manage to do something to different and now i`m preparing the build a new ROM 6.5.3 with new XIP and new SYS
In my kitchen go to TOOLS -> bats -> extract.bat and open it in an editor, it should tell you everything you need to know about extracting roms (the nbimagetool extracts pretty much every *.nbh and *.nb you throw at it). Once the dump is put into packages by the pkgtool, the programs are sorted into those packages (if the cook didn't prevent this for example by deleting the dsm files during the cooking process, in this case all you get is a veeeeery long list of files )...
EDIT: I forgot to mention, I had a lot of problems with the 6.5.3 emulator image, the home screen wouldn't rotate (CHome that is). And I figured that 6.5.3 isn't worth the hassle on non-touch screen WM phones (I am moving to Android soon anyway )
I also had some problems with the SYS when i was trying to make G`reloc and gived me a Skybox language error and stoped,but after I deleted Skybox it worked like a charm .Did you had this to?
That's normal. G'Reloc doesn't support the new modules of WM 6.5 that are allocated to memory slots that don't exist in previous WM versions. So you either remove or recmod the modules or you use wmreloc instead of G'Reloc...
yes i found out that if I remove it everything is ok i removed it with unlocker but now i want to try wmreloc hope it will go without errors
I always used the recmod mehtod, but removing skybox makes sense anyway, because it's available in the market...
Something for you to read on the topic: http://www.techparaiso.com/windows-...memory-and-native-kernels-in-windows-phone-os
So it`s better to remove it because eats lot of memory anyway I don`t use it but I wanted to be included exactly like in the original ROM but in the last days I was thinking to do it different and I will do probably a light version and one customize by my own needs but I would love also to know what the users would want to include,so waiting for some proposals