Related
I've been reading the forum, and based on the information and the tools there I have been able to modify my extended ROM, which is great. Now of course I'd like to modify the main ROM as well, but despite the many hours I've spent searching the forum, I can't find the necessary information to do it. There's always something essential missing, something which probably is obvious to a programmer, but not to a normal user. As I've been able to modify the extended ROM, I guess I should be able to modify the main ROM too. Who can point me in the right direction?
from what i understand it's not even 100% possible with xda1 since people cant seem to make the extracted files back to a nbf file
and there are no tools that i know of that even extract the main rom from a xda2
As I understand it, when you upgrade the operating system, you're actually modifying the ROM. Some people here like to call it to "flash", I think, and there are a lot of messages about it in here. I just haven't found the information necessary to do it. I want to modify the ROM on my XDAII.
no the operating system is the rom which is in a eeprom in the device
when you flash the rom you replace the operating system with the new one
when you say modifying it mean more in the way of exchanging different files inside the rom
but if you just mean flashing the rom with a newer then here is a guide
http://wiki.xda-developers.com/wiki/HimalayaRomFlashing
What does EEP stand for? How many ROMs are there?
I've seen a ROM created here for the XDAI, containing more programs than what the devices normally come with. I would like to have a ROM on my XDAII containing the programs I use, so that I don't need to reinstall them every time the device is hard reset. Isn't this possible?
What does EEP stand for?
Click to expand...
Click to collapse
huh what does EEP have to do with this ?
suppose it could stand for
Executive Excellence Publishing
or
European Environmental Press
how many roms there are i think there are 1.5 1.6 1.66 and 1.72
about extra programs then they are not! in the rom they are in the extended rom any CAB file you copy to the extented will install after automatic after a hardreset
you should take a look at the romkitchens ( specifically for xda1, but can be made for xda2 as well ).
and mkrom, and the other romtools
EEPROM stands for "electrically erasable programmable read only memory".
this is sort of the predecessor of flash memory.
"electrically erasable programmable read only memory" sounds like a contradiction, but thanks for that, it makes more sense than EEPROM.
What about all of us users who don't have a Unix machine? I suppose we're stuck with the original ROM then, and have to install our programs over and over again for every hard reset. Of course you can put a few of them in the extended ROM, but it becomes full too quickly and you're left with installing the rest of them manually.
well you can upgrade to a newer rom as they come out
like i have 1.66 but if i wanted 1.72 i could upgrade
about contradiction heh yeah suppose so but then if it was 100% always READ ONLY then it would be random was what in it as how the transistors randomly set when it was produced
A newer ROM wouldn't contain the programs I want.
no :/ but it could contain bug fixes for ms and radiostack and such
i suspect that extented rom was made so it would be easier for the phonecompanys' and other 3th party resellers to get programs preinstalled fast without having to mess around too much in the rom
this is at the cost of memory though
but then some programs dident like to be in the rom i believe here i mean if setting files were places in the rom aswell and the program could not write to the setting file
mkrom also works on cygwin under windows.
( now I also wrote this in the wiki page )
Isn't that just for XDA I?
it works for windows ce in general.
that doesn't mean that there is no work involved in getting it to work, but it is possible to make it work for the xda2. I use it to build custom roms for the devices we sell, that is why I wrote it in the first place.
What's cygwin?
How much space is there in the ROM to add extra programs? In the ROM that this forum developed for XDA I they added quite many programs from what I could see.
http://www.google.dk/search?hl=da&ie=UTF-8&q=cygwin&btnG=Google-søgning
Thanks for that, Rudegar.
To Itsme: I don't mind the work, but it looks like its written for programmers and that if you're not a fairly skilled programmer, you wouldn't be able to do it.
i don’t see why we shouldn’t open a section for the 4100 here. A lot of the developments that goes on here also work on the 4100.
I have done some research on it and so far I found out that the ppc4100 use 2 file to flash the rom one is the boot and the other is the WM image just like the others do. Now both of those files are nb0 format and can be extracted with dumprom.exe which is available here. It can flashed back on the ppc4100 using a flash card to hold the image and triggering it by booting with the bootstrap.
Wish list
to edit the image file ( to change certain files)
to compile the extracted files from the rom ( to customize the rom with new programs or to custom update to a newer operating system )
what does anyone think?
u can change the press icon on the 4100 its located in a file called bobo.exe in the windows folder.
see? its almost the same there is very little change i think we need to sit down for a little while and think about how good this will do.
it will bring in more readers that would like to read about the 4100 thus u will generate more traffic that also will generate more donations
so pls i dont know how to get the athoraty's attentions here at least concider it
or comment
thanks
I am very intersted in the 4100 development as well.. I was hoping someone in here or maybe a few would be interested in sharing some knowledge and possible experience. I have done a lot of research and played around quite a bit with this over the last week using various XDA tools as well as hex editor, ect. If anyone would be interested in helping please post us here.
hey jr97ai. might as well start posting here maybe we will catch someone's attention and they will declare the ppc4100 a worthy of this site
---------------
the original rom files for the 4100 are the currunt morst recent update from at& however, both files are *.bn0 extention. as follows.
SP_E0402_230A.nb0
SP_K1112_230A.nb0
i recieved those files from audiovox a little while ago. jr97ai and myself have been working on this and have extracted the files out of the romfiles with the use of dumprom.exe. (great app by the way). i think jr97ai knows alot more about this than i do and can explain a little better.
i will attach the bootstrap rom file along with a letter that came with the cd that was sent from audiovox. i can attach the rom file as soon as i free up my bandwith
I have been playing around with mkrom and have been experiencing some problems. as it says on mkrom its not the most user friendly program. no its not, not at all, not even close. but i still try anyways lost but still trying.
if anyone can somehow point us to a direction it coul dbe verry helpful.
there might be a possibility tto use the exsisting xda WMse existing rom to use on the 4100. they seem to be similar. they do use the same operating windows after all.
well i tryed to post the rom file many times it didnt work. its uploaded in the ftp if someone can post it.
every time i try to post it shows this err.
Upload Error: Could not upload Attachment to ./files/sp_k1112_230a.rar
question to anyone who can answer.
to change the operating system from win2003 to 2003se wouldi need to change the bootstrap as well?
i am thinking i could use a nb1 and rename it to nb0 it should be the same.
if you would like to see a new section appear for the audiovox 4100 please post saying so. maybe that will gets omeone's attention.
we got 60 views and only 2 ppl have posted.
ok .. so the rom for the 4100 is in the xda ftp sire. the file is called SP_K1112_230A.rar under ppc 4100
ftp info
ady: xda-developers.com
username: xdaupload
pass: xda
im working with audiovox ppc4100 , and if u wanna dump with rom for make permenent rill file and dont losse it when u make a hard reset ,,i think the best solution its when u replace rill u can make a completat backup in a sd card then when u have to make a hard reset u can restore your backup and all will work ok...by the way i have working well mms, photo contacts , npencil , ms money , etc.
not jsut the rilgsm
now that we are able to flash the rom to the ppc4100 i am thinking we could change the operationg system. i am running towards the wm2003 se . i am trying to look for a basic rom nb1 format so i can try to flash it.
i am thinkiing it will work but i am worried about the phone part of the ppc.
do u have any thoughts on this?
No ppc4100 folder, any help please!!!
faramisimo said:
ok .. so the rom for the 4100 is in the xda ftp sire. the file is called SP_K1112_230A.rar under ppc 4100
ftp info
ady: xda-developers.com
username: xdaupload
pass: xda
Click to expand...
Click to collapse
Report about wrong user name and password
I need to reflash my PPC4100. Looking for rom and can`t find it. May be somebody have a original ROM from AT&T, or custom ROM, or WM5 ROM?
Hello,
Today if I'm wish to replace a file (stored as a module) in WM5/WM6, I end up deleting the module and replacing it by a file (stored as a file).
How do you create a module from a file?
How do you relocate a module (for instance if you import a module from another ROM and you don't want to turn it into a file)?
Regards,
--eluth.
So what? Does nobody know how to do that?
Is there no one capable of pointing me in the right direction?
--eluth.
eluth said:
Today if I'm wish to replace a file (stored as a module) in WM5/WM6, I end up deleting the module and replacing it by a file (stored as a file).
How do you create a module from a file?
How do you relocate a module (for instance if you import a module from another ROM and you don't want to turn it into a file)?
Click to expand...
Click to collapse
The "simple" answer is that you can not relocate a module - i.e. into a different memory map location. It was compiled for a specific space in memory, and there it must stay. There are no tools available for this. While something could potentially be written to do this task, the complexity involved would be quite high, and probably not worth the risk/reward/time.
Deleting the module - thereby freeing up the space, and having that space 'reclaimed' by a relocatable file is the only way you can modify/merge the ROMs. Use mamaich's tool to convert the module to a file. There is "no" other way.
Now, having said that, I have (previously) relocated a number of modules in the ROMs I made (TuMa series), however these relocations were MANUALLY done with a HEX EDITOR, and only on very small modules. i.e. I analysed the module, and changed everything necessary (byte-by-byte) to relocate the module. This is a very time-consuming manual process, and not recommended unless ... well ... ok, it's just not recommended period. Let's just say I won't be doing that again unless I really need to.
Tuatara. Many, many thanks for that answer.
This question was here several times, but always without any answer.
Thanks
You're very welcome ...
I forgot to mention that what I meant by "unless I really need to", was during the time BEFORE mamaich made his recmod tool. That tool actually came about because there were so many problems trying to relocate modules and/or find file-based versions of the required DLL's in order to build up a complete ROM. In TuMa v1.1 onwards there were always a number of modules which "previously didn't exist" in any ROM that came before. The things we do!
Anyways ... some day ... when I have some time again (real life has just been very consuming!), I'll be looking into the last few issues with the BA and see what I can resolve. The ROMs which have been made now are fantastic ... kudos to you all!
Tua! Your back How's things going?
Midget_1990 said:
Tua! Your back How's things going?
Click to expand...
Click to collapse
Well ... I actually never left ... I've just been 'lurking'.
Things have been good and things have been busy and things have been very trying. Kind of the 'same old - same old' story of everyone else who has real life take over, and doesn't have any time left to do the things they would like to do. Otherwise though, everything (and everyone) has been great!
I have watched with great interest all of Bepe's ROM Kitchen work, and the ROMs released from Helmi, xplode, baniaczek, yourself and others. With only a few things now causing problems, I think a solid WM5 ROM for the BA is quite possible to achieve ... but some of the last bugs do "bug" me ... so they'll NEED to be fixed. I want to keep using my BA ... nothing else beats it ... yet. (Well, ok VGA screen rocks, but ...)
I'm probably going to look into WM6 for BA at some point myself - just to see if there is anything which can be done. I don't hold much hope, but I'm not sure until I try ... it could just end up being a 'Frankenstein monster' of a ROM instead.
Anywho ... I might be a bit less 'lurker' and a bit more 'around' in the next while. Gotta have some hobbies ... right?
Thanks Tuatara,
This helps and explain why I couldn't find more details.
Best regards,
--eluth.
can you make a special System for D9000/cht9000.
My friend is trying to change this phone's ram.
every body kown this phone's ram is 64 M.
And my friend is trying to change it become 128M.
so I need a special System for D9000/cht9000.
can you edit it ?
waiting!
It will be made when you come back with an successful upgrade.
Delete this from here or point this guy toa technician maybe he can tell him that there isnt NAND ememories 128 for hermes... I know there are for universal but not for hermes... althout is non related to this forum...
Mods...
With some help from me, manelscout4life dumped his LG Expo.
Links here:
Part00 and Part01: http://rapidshare.com/files/330408837/part0.zip.html
Part02: http://rapidshare.com/files/330404062/Part02.zip.html
Enjoy!
(don't forget to vote against XDA's stance of only doing HTC! )
MIRRORS:
Part00 and Part01: http://rapidshare.com/files/334116367/part00and01.zip
Part02: http://rapidshare.com/files/334116370/part02.zip
awesome work guys! if i hadnt been at a funeral id have been on there helpin out. nonethe less... fantastic work!
i just hope to see some custom roms soon!
we'll i think we might need to focus on getting the phone's SSPL or Hard SPL so continuous flashing is possible eh?
Chainfire said:
(don't forget to vote against XDA's stance of only doing HTC! )
Click to expand...
Click to collapse
Where is the vote? Not to hijack the thread, but it's known that we're going to go 6 months without anything better than the HD2 from HTC meanwhile LG, Samsung and Acer are pumping out WM phones yet there's no XDA support so they will inevitably lack the same base support as we continue to salivate over HTC and it continues to pump out Android phones...We'd all be better off if XDA moved with the industry.
bugsykoosh said:
Where is the vote? Not to hijack the thread, but it's known that we're going to go 6 months without anything better than the HD2 from HTC meanwhile LG, Samsung and Acer are pumping out WM phones yet there's no XDA support so they will inevitably lack the same base support as we continue to salivate over HTC and it continues to pump out Android phones...We'd all be better off if XDA moved with the industry.
Click to expand...
Click to collapse
wouldn't we all be better off if we just got along?
Awesome that you were able to dump the eXpo rom, but we can't do anything with just a dump. We had this problem with the Incite. We had to wait for an official rom because the way LG makes their roms. The format is a .dz file and there are parts of this file that is needed to cook a rom which is not found with a dump.
We would need the actual dz file in order to deconstruct it, dump the contents, cook, and then reconstruct the dz file. Without the dz file we can't flash.
Dark9781 said:
Awesome that you were able to dump the eXpo rom, but we can't do anything with just a dump. We had this problem with the Incite. We had to wait for an official rom because the way LG makes their roms. The format is a .dz file and there are parts of this file that is needed to cook a rom which is not found with a dump.
We would need the actual dz file in order to deconstruct it, dump the contents, cook, and then reconstruct the dz file. Without the dz file we can't flash.
Click to expand...
Click to collapse
Right the dz file will be helpful but this is nice for just hacking up the phone we have now or porting the apps as well. With the dump there can be driver hacks made and all kinds of other fun goodies its a start...
killerskincanoe said:
we'll i think we might need to focus on getting the phone's SSPL or Hard SPL so continuous flashing is possible eh?
Click to expand...
Click to collapse
But we dont even know yet if we will need one we need an spl dump so we can check to see if it needs a signed image or not
This is def. very exciting and I very much look forward to seeing things getting ported from this phone to all of our other WM phones!! So we can have pieces of this phones apps/programs running in our phones to play with!!
GREAT JOB NOW LET THE FUN BEGIN
meh
that was faster than I expected. Great work!
Dark9781 said:
Awesome that you were able to dump the eXpo rom, but we can't do anything with just a dump. We had this problem with the Incite. We had to wait for an official rom because the way LG makes their roms. The format is a .dz file and there are parts of this file that is needed to cook a rom which is not found with a dump.
We would need the actual dz file in order to deconstruct it, dump the contents, cook, and then reconstruct the dz file. Without the dz file we can't flash.
Click to expand...
Click to collapse
Just because you can't do anything with a dump because it doesn't give you all the stuff you need, doesn't mean it isn't useful for other purposes.
Apps porting, driver research, etc. I am personally not interested in flashing the LG Expo (mainly because I don't have one) but I was in need of the dumps.
So... shortsighted much?
Wonderful News
This is great!!!
I tried to dump my LG IQ which is the Canadian version of this phone, but didnt work too long at it, and I fail because the phone said device not ready in the dumping process.
If you want to PM me with how you did it, and give me a bit of advice, I would be willing to try again.
The Telus and AT&T versions are slightly different, one difference being that the Telus phone has a slightly newer version of windows ce on it.
Telus 5.2.21868.5.0.69
AT&T 5.2.21749..don't know the rest
Awesome job......
Installing this CAB on your phone and rebooting should get rid of that pesky error:
http://www.jongma.org/tmp/MultASync_Security_Policies.cab
(Taken from MultASync project)
Aside from that, it's just pdocread / raw dump as usual ...
For an example of the commands, see:
http://forum.xda-developers.com/showthread.php?t=501871
As a fellow user of the LG Expo, would be more than happy to help out as I can.
Chainfire said:
Installing this CAB on your phone and rebooting should get rid of that pesky error:
http://www.jongma.org/tmp/MultASync_Security_Policies.cab
(Taken from MultASync project)
Click to expand...
Click to collapse
Sorry to say, it didn't work for me
tried installing the cab, and tried editing the reg manually to the values in the cab....
any other ideas?
Not really... all we did is hook up the device correctly, install that cab, excute the commands and we had a dump ...
Thank you Chainfire! Telus IQ ROM dump
OK I am now feeling like an idiot.
Yes, the disk on the IQ is called DSK1: not FLASHDR
Yes, this cost me being at least two weeks later than I needed to be.
Yes, I goter dun tonight....
rofl
Easy mistake to make: but rest assured, everyone only makes this mistake but once, and probably every dumper once made it
Sorry, I should of been a bit clearer, but when I said we can't do anything with just a dump I was referring to cooking. Someone had mentioned seeing custom roms soon so I was just pointing out that that wouldn't be possible until we get a base rom to work with. If I confused anyone it was not my intention.