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
Hi there,
I made visible the extended ROM of M600 with registry tweaks seen in this forum. I dont use any of the programs on the extended ROM, coz I dont like my phone to be customised for my service provider. (I soft reseted while it was trying to customize after the hard reset).
Now I have a 10MB of Ext ROM on "My Device". My qustions are;
1) Is this Ext ROM just like another 10MB SD Card?
2) WOuld this space make the my handheld run faster? or can this be made available fot programme memory?
3) Is there any advantage of installing programmes on it compared to on th SD Card?
Currently I have about 3MB of Orange CAB files on it. None of them I use.
How can I use this space efficiently?
Thanks in advance for any comments
ps: Another thing I just remembered is that, after I made this Ext ROM visible, I cant save the camera pics to SD card. The options on the camera settings are to save it on Main Memory or Ext ROM! it doesnt recognise SD card! funny! Any way around?
Anyone please..?
I order:
1) Yes it is exactly like a 10MB SD card, you just can't remove it from the device. If you need to hard reset it will become hidden again but the data will not be lost.
2) No. Program memory is RAM and this is FLASH. You can only use it for storage.
3) It is mounted before the SD, so if you have an app that needs to run on start up, you can put it on the ext ROM but not the SD.
4) I suggest you move the Orange cabs to your PC. Having the i-mate variant I had 9MB filled with stuff out of which all I needed were Skype and Voice speed dial. Then use this space for the basic and most needed apps. Also some apps like TCPMP can be used with content from different SD cards so ext ROM would be a good place for them. I try to keep main memory free for outlook stuff.
5) Yea, the camera app only seems to recognize the first storage card it sees. Don't know about a fix for that.
levenum said:
[...]
5) Yea, the camera app only seems to recognize the first storage card it sees. Don't know about a fix for that.
Click to expand...
Click to collapse
Thank you very much, Levenum!
I finally understood a bunch of things about the ExtROM.
About this 5th point, I would add something.
The same identical problem raises when the \Network path created by Resco Explorer is shown on the main memory root.
The internal camera seems able to access only to the first two objects in the mountpoint list (you can see this list when installing some apps, as the dest options radio button)
So, question comes out: what about hiding ExtROM again after installing startup apps on it ?
I mean: are those apps still runnable, when staying on a hidden mountpoint ?
Thanks for any answer
..._
Sorry to butt in on this topic, but I have also been thinking of doing this.
I would just like to know though once the Extended Rom has been unlocked as described in many past posts, can you lock it again?
I am just asking this because, what happens if I have to return the phone? Surely messing with it would void any warranty?
I would need to restore the CABS back to Extended Rom, and then lock it before returning it.
Thanks
Val3r10 said:
So, question comes out: what about hiding ExtROM again after installing startup apps on it ?
I mean: are those apps still runnable, when staying on a hidden mountpoint ?
Click to expand...
Click to collapse
Interesting, I never tried it. Perhaps if you don't change the MountHidden flag, but only the MountOrder.
NewSPV said:
I would just like to know though once the Extended Rom has been unlocked as described in many past posts, can you lock it again?
Click to expand...
Click to collapse
I don't know about other devices, but in case of the Prophet it's just a matter of changing back the registry values and soft resetting.
Thanks for that.
I have already backed up my Extended Rom, as Total Commander let me copy the CABS without unlocking the Extended Rom.
Orange has only added 1.95 MB which seems such a waste of vital memory.
I have heard that approx 10 MB is set aside for this. Is this set physically in manufacture by HTC? Can the extended Rom be merged into main memory like partitions can be merged on a PC?
Thanks
I read somwhere that removing things from the extended rom gives the device more storage available and shown int he memory part of settings. This however is not true, the extended rom is a seperate partition, full or empty the device will work the same.
I use mine to store the cabs of installs I use when I hard reset. Saves me copying them over each time.
Thanks very much Levenum and others who contributed. That was very informative and I am glad many others have benefited with this thread.
Cheers
One note:
I made a little experiment this Friday, which require a me to restore my Jamin to it's original state. (Hard reset + restore ext ROM).
I didn't check the CAB attributes when I copied them so even though the ext ROM was in it's original state all cabs that were used after first hard rest were deleted and didn't install after second hard reset.
So when restoring your ext ROM make sure you mark all CABs 'read only'.
I unlock ExtRom and put mein cab, edit config.txt.
But after HardReset mein cab didn't installiert.
I think, dieses cab need to signen.
Help me please signen mein cab or any cab theoretically.
you also need the modified autorun.exe, the config file isnt read by the default one.
dannyoneill said:
you also need the modified autorun.exe, the config file isnt read by the default one.
Click to expand...
Click to collapse
dannyoneill, wie kann man das machen? :shock:
..Sorry, how kan das make?
See this thread for more info
http://forum.xda-developers.com/viewtopic.php?t=38957&highlight=autorun
dannyoneill said:
See this thread for more info
http://forum.xda-developers.com/viewtopic.php?t=38957&highlight=autorun
Click to expand...
Click to collapse
I have renamed the file so:
my_file.cab -> Default_my_file.cab
All the same it is not installed!
There it is spoken about Wizard, i have O2 Xda Neo.
Where it is possible to take patched file Autorun.exe?
Can somebody to lay out it if it´s have?
Please, help me.
as the thread says, you cant just rename the file as it needs to be signed and designed for wm5 for it to isntall. To do your own cabs you need to have a special autorun.exe that reads a config file.
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?
Hello ppl, after so much cooking in 6.5 i decide to play a lil into 6.1... well i never cook for 6.1
Ok here is teh question as the title says... i jump into 21057 build 6.1 and I have a weird thing that is annoying... A mouse pointer (a lil arrow) does any body knows how to get rid of that arrow in my screen?
thanks a lot
Im usin HTC Hermes 6.1 build 21057 QVGA 0409 EVK 1.8.2
So 71 views and none idea? OMG i need to start over with an old build... maybe is a feature in the gwes shell or other core file
mmmm interesting experience... if I reply myself in this thread, i gain 18 views... and none answer... well... i talked last night with Da_G, he told me that some driver of my old OEM is causing troubles.. maybe the ddi.dll:
1.- made a search... then i see i had it twice... and i see a file inside a module.... is aid!!! OMG that is stupid!!!
2.- went running to my OEMdrivers and check that module "ace_ddi.dll" and yes it has a file ace_ddi.ddl inside so i said FK!!!! checkk all my modules and fK!!! all has the same issue... but the kitchen ddint told me about it.... i erase them all... and now the platform rebuilder crash...
The new question is... In WM6.1 the file inside the modules are needed?
+ Que PPC said:
mmmm interesting experience... if I reply myself in this thread, i gain 18 views... and none answer... well... i talked last night with Da_G, he told me that some driver of my old OEM is causing troubles.. maybe the ddi.dll:
1.- made a search... then i see i had it twice... and i see a file inside a module.... is aid!!! OMG that is stupid!!!
2.- went running to my OEMdrivers and check that module "ace_ddi.dll" and yes it has a file ace_ddi.ddl inside so i said FK!!!! checkk all my modules and fK!!! all has the same issue... but the kitchen ddint told me about it.... i erase them all... and now the platform rebuilder crash...
The new question is... In WM6.1 the file inside the modules are needed?
Click to expand...
Click to collapse
to my experience - NO
i did always delete all of them..
did you track your crash down to OEM/SYS?
+ Que PPC said:
mmmm interesting experience... if I reply myself in this thread, i gain 18 views... and none answer... well... i talked last night with Da_G, he told me that some driver of my old OEM is causing troubles.. maybe the ddi.dll:
1.- made a search... then i see i had it twice... and i see a file inside a module.... is aid!!! OMG that is stupid!!!
2.- went running to my OEMdrivers and check that module "ace_ddi.dll" and yes it has a file ace_ddi.ddl inside so i said FK!!!! checkk all my modules and fK!!! all has the same issue... but the kitchen ddint told me about it.... i erase them all... and now the platform rebuilder crash...
The new question is... In WM6.1 the file inside the modules are needed?
Click to expand...
Click to collapse
What kitchen did you use to dump the rom? I ask because I've played around some with cooking 6.1 roms and using EVK to dump shipped roms (20771 and 20779) for the raphael, and every time I do it, I get the files inside of modules phenomenon. And let me say, the roms I cooked SUCKED! They had all sorts of issues (even after deleting all the files). I recently dumped the 20779 rom with OSKitchen (first time I'd ever used it) to get a few drivers out, and it dumped everything properly. I'm not sure if I was doing something wrong or not with EVK-is there a setting for dumping 6.1 roms? I don't have much experience dumping roms, since there hasn't been a new one for the Raph in over a year and Da_G basically did all the hard work setting up 6.5 kitchens. I removed recmod.exe from the tools folder (thinking maybe it was kicking in somehow and recmodding the modules), but that didn't make a difference.
Anyway, you may want to try a different kitchen if you're using EVK. I also didn't get any file/module errors, and it was just blind luck that I found out the every IMGFS module had a file inside of it (but not in the dump, so I guess that's a good thing, although the rom I was working on was a turd).
Nope not necassary.
You need GReloc to reloc sys, some changes to your kitchen batch and a 6.1 nk.exe if you ask me.
+ Que PPC said:
mmmm interesting experience... if I reply myself in this thread, i gain 18 views... and none answer... well... i talked last night with Da_G, he told me that some driver of my old OEM is causing troubles.. maybe the ddi.dll:
1.- made a search... then i see i had it twice... and i see a file inside a module.... is aid!!! OMG that is stupid!!!
2.- went running to my OEMdrivers and check that module "ace_ddi.dll" and yes it has a file ace_ddi.ddl inside so i said FK!!!! checkk all my modules and fK!!! all has the same issue... but the kitchen ddint told me about it.... i erase them all... and now the platform rebuilder crash...
The new question is... In WM6.1 the file inside the modules are needed?
Click to expand...
Click to collapse
Farmer Ted said:
What kitchen did you use to dump the rom? I ask because I've played around some with cooking 6.1 roms and using EVK to dump shipped roms (20771 and 20779) for the raphael, and every time I do it, I get the files inside of modules phenomenon. And let me say, the roms I cooked SUCKED! They had all sorts of issues (even after deleting all the files). I recently dumped the 20779 rom with OSKitchen (first time I'd ever used it) to get a few drivers out, and it dumped everything properly. I'm not sure if I was doing something wrong or not with EVK-is there a setting for dumping 6.1 roms? I don't have much experience dumping roms, since there hasn't been a new one for the Raph in over a year and Da_G basically did all the hard work setting up 6.5 kitchens. I removed recmod.exe from the tools folder (thinking maybe it was kicking in somehow and recmodding the modules), but that didn't make a difference.
Anyway, you may want to try a different kitchen if you're using EVK. I also didn't get any file/module errors, and it was just blind luck that I found out the every IMGFS module had a file inside of it (but not in the dump, so I guess that's a good thing, although the rom I was working on was a turd).
Click to expand...
Click to collapse
Thats true, my 6.1 rom is a mess i will try that thanks
Laurentius26 said:
Nope not necassary.
You need GReloc to reloc sys, some changes to your kitchen batch and a 6.1 nk.exe if you ask me.
Click to expand...
Click to collapse
mmm interesting where can I learn more about that Changes you talk about?
to be homest i have the same thing
when i look at modules i have a dll in it called the same as folder
i have this since the beginning i started cooking and thought it whas meant this way but here im reading its not:-o
will the rom become faster if i delete all the dll's from the modules?
definetly gonna give it a go tomorrow:-o
yes... we are wrong, as the kitchen warns us when in SYS and EXT is a module with a file inside... but it dont happends when we got them in OEM.
The idea to have modules instead of files is cause the file is already recmoded when the cooking process starts at IMGFS merging (maybe im wrong) doing the recmod into slots by the reloc tool... so... in 6.1 the Greloc did it in the oem and goes wrong, and the same happends for WMreloc for 6.5 cooking.
and yes having modules allows us to have correctly recmoded files at the end to have faster roms so... the files inside modules is a wrong way to cook
i will try to dump again the stock... in OSkitchen zero... then i will add it into my 6.1 kitchen... but something is weird in my case... cause my device dont has stock rom for 6.1 ( we have wm6 shipped roms) but i will try it anyways
It never affected me (I think, lol) but you can use PreKitchen tool to delete all files with the same name as the folders that they are in. Its a lot quicker then manually deleting each duplicate
seeM_ZA said:
It never affected me (I think, lol) but you can use PreKitchen tool to delete all files with the same name as the folders that they are in. Its a lot quicker then manually deleting each duplicate
Click to expand...
Click to collapse
muchias gracias for this s my entire ext folder is full of files inside modules:S
:verry nice program and verry quick
edit2: gonna flash my new rom without the files inside modules and see what happens
i deleted them from the oemdrivers folder and all the ext packages(im hoping for some nice extra speed)
edit3: just looked at the kitchens i made for tp2 and leo and they have the exact same thing files in modules in ext packages and oemdrivers:s
and the strange thing none of the kitchens told me this and all gave nice working roms where evrything works like it should:S
edit4: hmmm looks like weather animation is slower after deleting all the files in modules:s
Im pretty sure it shouldnt affect the speed at all :? Because if you look in the dump folder it doesn't happen there. Maybe its just in your head? Lol, I could be wrong though, so please correct me if I am.
seeM_ZA said:
Im pretty sure it shouldnt affect the speed at all :? Because if you look in the dump folder it doesn't happen there. Maybe its just in your head? Lol, I could be wrong though, so please correct me if I am.
Click to expand...
Click to collapse
for the weather animation im quite sure as yesterday i let it run the weather animation for rain ten times after eachother and it whas ten times smooth
now i did it 5 times and 5 times with stuttering in it:s
Strange :? You sure you didnt change anything else?
seeM_ZA said:
Strange :? You sure you didnt change anything else?
Click to expand...
Click to collapse
100% sure
i downloaded the program you mentioned and let it run over the entire ktichen so all files in flders with the same name got deleted then i cooked the rom and flashed it
gonna reflash the rom i used before i deleted all those files to doucble check if im right about the weather animation but im 99% sure about the outcome
Try task29 before you reflash also. Otherwise I have no idea glad you backed up though hehe
seeM_ZA said:
Try task29 before you reflash also. Otherwise I have no idea glad you backed up though hehe
Click to expand...
Click to collapse
lol it went from rain to clouded
gonna flash back to the rom without the dll in the modules and do a task 29 before flashing and use it a day then i know for sure if its faster or slower
miniterror said:
lol it went from rain to clouded
gonna flash back to the rom without the dll in the modules and do a task 29 before flashing and use it a day then i know for sure if its faster or slower
Click to expand...
Click to collapse
Haha, I hope it works out for you bro
I tested out my weather animations and they're perfectly fine, without the dlls in modules. Im running 21909 and sense 2016 CFC'ed (from Leo 3.04) on TP2.
So... laurentius, how can I use Greloc instead of WMreloc in EVK to cook 6.1 ROMs???
i have this using WMReloc in a vanilla ROM 6.1
Memory Map...
SLOT 0: 0x02000000 - 0x01660000 (END: 0x00060000, 64 MODULES)
0x02000000 - 0x01fe0000 - ROM 0
0x01fa0000 - 0x01e20000 - ROM 1
SLOT 1: 0x04000000 - 0x02020000 (END: 0x02020000, 253 MODULES)
RAM IMAGE: 0x80000000 - 0x8029cc34
RAM: 0x8029d000 - 0x802cc000 - Used for kernel modules
0x802cc000 - 0x83a00000 - 55 MB free
... done!
I guess this 64 Modules in slot 0 are causing troubles
I'm not too familiar with 6.1 but what I do know is you want as little modules as possible in slot 0, so ideally you want no modules there.
EDIT: Wrong info here, my bad.
All the best
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