Related
Hi,
Just two questions.
1)I runned the Mkrom.sh and when building it it comes with the
error ' operator rom not found' but continues.
Then there's only a .nb1 file build which has a size of 32,243,712.
I don't know if this is correct !????
Is it a problem the operator roms are not found for a working rom???
2) Is it possible to delete, maybe even extract files from an image to
clean it so you get more space for your own programs?
hopefully any can answer these......
DCA said:
1)I ran the Mkrom.sh and when building it it comes with the error ' operator rom not found' but continues.
Then there's only a .nb1 file build which has a size of 32,243,712.
I don't know if this is correct !????
Click to expand...
Click to collapse
There should be both an nbf file of 32505888 bytes and an nb1 file of 32243712 bytes. So the size for the .nb1 seems correct.
Is it a problem the operator roms are not found for a working rom???
Click to expand...
Click to collapse
I'm not sure I understand the problem enough to be sure. Itsme, who made the tool, has left for a well-deserved two-week holiday, so I guess this will have to wait if you can't figure it out for yourself.
2) Is it possible to delete, maybe even extract files from an image to clean it so you get more space for your own programs?
Click to expand...
Click to collapse
Yes, extraction is possible using the dumprom tool described in another thread. Deletion of files to save space would take some hacking and slashing of your own. We do plan to make some more intricate ROM manipulations more easy once we clean up and publish more tools.
@XDA developer Peter Poelman
I'm glad the size is correct.
Just tried it again and only the .nb1 file is created, not the .nbf !!!
Is it possible to convert a .nb1 to a .nbf file??
Is the XDA ROM Tool able to write to USB SD-card reader/writers?
(could be an option to generate a valid .nbf)
thx
[ I split this topic away from the main Special Edition v1.1 thread, as it's not primarily about that. I will probably start doing this more as topics grow larger. ]
Yes, you can use XDArit to write an nb1 to SD, and then read SD to nbf. Easier tools for this exist, and we've even built the beginnings of one (which we haven't yet released).
If you have the SD, you could also just use the bootloader to burn the contents to flash.
How can I remove from the original ROM some files like T-Mobile, AIM ... etc. ?
I cooked up a 4.00.10 T-Mobile with GPRS monitor and batterypack but i want some more addons.
Can someone tell me what steps are required to remove from the ROM some files ?
Thanks,
Decebal
ROM = Read Only Memory.
But, i've we're able to add Programs to the ROM in the ROMkitchen, i think we're also able to remove programs.
Regards
Stefan
cruisin-thru said:
ROM = Read Only Memory.
Click to expand...
Click to collapse
obviously i do not deserve that
i was talking about the ROM image and since i've already succeded in putting into the ROM two apps i want to try something else.
so if anyone know how to remove at least T-mobile and AIM files from the image i'll be happy.
thanks,
Decebal
I believe they are in an area not able to be modified.
I was just quoting from that site, it does state that it cannot be erased, modified etc, no offence meant here. :roll:
The mkrom tools will allow you to 'unpack' a rom, i.e. extract all the files that are in it.
A rom, to the best of my understanding, has a 'native' or stock part to it, and then a series of XIP chains -- programs that are added into the free spaces of the rom.
I dont know what happens if you try to remove files from a rom that are part of the standard build...
Maybe the TMobile stuff is in a 'removeable' section of the ROM... there is also the 'operator' section... I am assuming that is a location that will give the 'operator' or creator of the rom space to put specialized programs, such as TMobiles phone apps, etc.
So, it seems that your best bet is to get the mkrom tools and read about how to extract/remove files/rebuild a rom.
Hey, it may even work!
J
You can rebuild a rom image from extracted files and leave some files out but Mkrom does not use compression and therefore the rom you end up with will probably be bigger than the rom you started with.
Richard
If I am correct, an eeprom is something else than a flash-rom.
so the article at least states it incorrectly.
if it is flash, you should be able to modify it.
XDA developer Itsme said:
If I am correct, an eeprom is something else than a flash-rom.
so the article at least states it incorrectly.
if it is flash, you should be able to modify it.
Click to expand...
Click to collapse
Now, I do think that the real question is "How do we unlock the 'ROM' so that it can be modified being that it is an eeprom?"
Misterdollymaker
you need backup the ROM to *.nb1 or *.nbf file, than using tools to add/delete file to *.nb1 , write the new file back to XDA ROM. it is fun to add/delete file to your personized ROM!
cgigate said:
you need backup the ROM to *.nb1 or *.nbf file, than using tools to add/delete file to *.nb1 , write the new file back to XDA ROM. it is fun to add/delete file to your personized ROM!
Click to expand...
Click to collapse
this is quite interesting...can you elaborate further?? I wish to learn more...
cgigate said:
you need backup the ROM to *.nb1 or *.nbf file, than using tools to add/delete file to *.nb1 , write the new file back to XDA ROM. it is fun to add/delete file to your personized ROM!
Click to expand...
Click to collapse
Yes, please! I wish to learn more too! I am looking to remove the standard sounds and replace them with my own (using same names) as well as the boot image and desktop.
yea, no kiddin, i'd like to know how too!
im sure its not impossible, 'they' did it the first time arround.
why not hacking it? and since its all at no charge (no profit) are we realy breaking any patents?
I wanted to know if there is an easy :wink: way around, to put our own programs in the rom. xda-developers certainly can't put ezwap2.5, and the total commander appears to be older version, while new version is much better. There are some more freeware application I'd love to put in there
xda-developers already posted some tools to do job, such as MKROM ...
cgigate said:
you need backup the ROM to *.nb1 or *.nbf file, than using tools to add/delete file to *.nb1 , write the new file back to XDA ROM. it is fun to add/delete file to your personized ROM!
Click to expand...
Click to collapse
I'm interested too
How can i add/delete file from nb1 file?
Thanks
Fabio
I've used mkrom suite to do this (even for Smartphone2002). This are great tools.
Unfortunately it's not as easy as you might think. It's nearly impossible to build a ZERO-KNOWLEDGE ROM file explorer which can add or delete files "on the fly".
You will still have to look for valid gap's in the original rom where you can add a new XIP block.
All .exe and .dll files are "fixed up" that means they MUST run at THE fixed ROM position where they have been initially placed (execute in place). If you dump an exe or dll file you can't use it for other than disassembly to see how things work.
Removing files is a very hard task (they are splitted over the whole rom). And the resulting gap's are mostly not more than 10-16 kB. All you can do is to "hide" files (simply patch the directory entry).
So you see compression is not the real problem (see programers corner for a .bib file which can be used with romimage.exe - a Microsoft Tool to build XIP blocks, this tool supports compression)
John Smith
only the kernel actually runs in the virtual memory area mapped to rom,
all the other XIP stuff runs from a virtual memory area mapped somewhere
in the top of each processes memory space.
( look at the 'real=' values in the output of dumprom )
so for all the other modules it should be possible to move them around
in rom a bit, I think you only need to keep the pagealignment the same.
Hi,
The virtual memory address is also fixed in the module. (That's why I've to rebuild all the stuff I want to copy from other roms).
Since all relocation info is gone the module can't run from another memory position. So the only thing you can do is to move it in it's own XIP section...
John
I have just installed the new Dopod 828 Chinese ROM on my i-mate JAM and created the 27M BigStorage on it.
The radio ROM is 1.13.
I have also extracted the Extended ROM for those interested.
ftp://xda:[email protected]/Uploads/Magician/Extended_ROM_Dopod_CHT_112_177/
There are quite a few interesting add-on softwares such as
- Skype For PocketPC
- Iconlab Intervision
- Polaris PWinner
- wLAN11b (for the Dopod "short" SD wifi card)
Talents,
Can you upload the CHT 1.12 Rom also? Thanks a lot
The full OS ROM was uploaded on 11 August by someone else.
ftp://xda:[email protected]/Magician/Dumped_ROMs/Dopod828V112OS.zip
opps. mislook it tim..
Talents said:
The full OS ROM was uploaded on 11 August by someone else.
ftp://xda:[email protected]/Magician/Dumped_ROMs/Dopod828V112OS.zip
Click to expand...
Click to collapse
Hi, Talents
Could you teach me how to install this rom file, after zip the rom is .bin format.
thanks you
thanks for info,it works fine with my 818!!
Please note that in Device Information, it will show Model to be PM10B instead of PM10A. This should cause no problem to installing almost all softwares, but Pocket Hack Master fails to recognise it.
My i-mate JAM has been upgraded to 128M RAM. So, the configuration is no different from Dopod 828.
Talents said:
Please note that in Device Information, it will show Model to be PM10B instead of PM10A. This should cause no problem to installing almost all softwares, but Pocket Hack Master fails to recognise it.
My i-mate JAM has been upgraded to 128M RAM. So, the configuration is no different from Dopod 828.
Click to expand...
Click to collapse
Hi Mate,
How to install this rom on the I-mate.
Thanks & Regards,
Use the standard SD method to install. You can find a lot of postings about the method in this forum.
As a short summary:
1. Use RomUpdate.exe to dump your orginal ROM to a 128M or 256M SD card.
2. Use ntrw.exe to read the ROM file on the SD card and save it to your hard disk.
3. Use HexEditor to replace the first 416 bytes of the downloaded ROM by the same of your original ROM.
4. (BigStorage option) Change the bytes 80 00 to b8 01 at locations 7e4a and 1fc232e.
5. Use ntrw.exe to write the modified ROM file to SD card.
6. Insert the SD card and set the ppc to bootloader mode.
The above may appear complicated if you are new to ROM upgrade procedures. Please search the forum for more detailed instructions before you attempt.
Compare with o2 mini ROM and 828 rom
have imporove quantity of carmera ?
thank You
Talents said:
Use the standard SD method to install. You can find a lot of postings about the method in this forum.
As a short summary:
1. Use RomUpdate.exe to dump your orginal ROM to a 128M or 256M SD card.
2. Use ntrw.exe to read the ROM file on the SD card and save it to your hard disk.
3. Use HexEditor to replace the first 416 bytes of the downloaded ROM by the same of your original ROM.
4. (BigStorage option) Change the bytes 80 00 to b8 01 at locations 7e4a and 1fc232e.
5. Use ntrw.exe to write the modified ROM file to SD card.
6. Insert the SD card and set the ppc to bootloader mode.
The above may appear complicated if you are new to ROM upgrade procedures. Please search the forum for more detailed instructions before you attempt.
Click to expand...
Click to collapse
Hello, Talents
Thanks a lot of for ur help, i had done the upgrade, thanks u very much.
Can this work on the Xda II mini?
Thank you!
adeliang said:
Can this work on the Xda II mini?
Thank you!
Click to expand...
Click to collapse
THX TOO
Talents said:
Use the standard SD method to install. You can find a lot of postings about the method in this forum.
As a short summary:
1. Use RomUpdate.exe to dump your orginal ROM to a 128M or 256M SD card.
2. Use ntrw.exe to read the ROM file on the SD card and save it to your hard disk.
3. Use HexEditor to replace the first 416 bytes of the downloaded ROM by the same of your original ROM.
4. (BigStorage option) Change the bytes 80 00 to b8 01 at locations 7e4a and 1fc232e.
5. Use ntrw.exe to write the modified ROM file to SD card.
6. Insert the SD card and set the ppc to bootloader mode.
The above may appear complicated if you are new to ROM upgrade procedures. Please search the forum for more detailed instructions before you attempt.
Click to expand...
Click to collapse
Why I got 11.03 MB of my Rom Storage when I Finished the rom upgrade?
And also my radio Version still in 1.11 ?
Thanks a lot! Although I haven't 828.
can I flash it to Eng O2Mini if no RAM upgrade (still 64MB) and how to do? Is there any improvement such as carmera and phone?
and how to use your .bin file? thank you.
Thanks, it's very useful
Still having trouble with BIN file
What do we do with the bin file? I downloaded the full OSDopod828 and have no idea what to do. I see nb1 files and then bin files. do we rename it or what? Can you guys help and clarify. Getting really frustrated.
What's the purpose of editting the 416bytes. If i just want the standard OS, did i have to back up anything at all? Why cant it be just as easy as the EXE which does everything for you...geeesh
C.
How to use BIN Files and SD upgrade?
Read a few posts which arent as clear for me at least. Maybe i'm just slow. I want to upgrade my dopod 828 back to CHT. Any easy way to do it next to the SD method which doesnt work with me. I didnt back up my CHT before i went for the WWE. What do i do with the bin file. Rename it or edit it what? Need desparate help here guys.
Sorry for multiple posts.
Hi, I am beginner here, can any one help me to create a nbf file from sd dumped rom? or you can also tell me how to do that. thanks in advance!!!
SD dumped rom is here:
ftp://xda:[email protected]/Magician/Dumped_ROMs/o2mini_1.12.07_CHS.zip
What do you want to do with this .nbf. For backup/restore purposes the .nb1 is sufficient.
You can try it with nbfdec, but I don't know what it does with a dumped rom. I use it to decode & encode the nk.nbf contained in a shipped-rom. For nbfdec get it here: http://forum.xda-developers.com/download.php?id=7603
Cheers, M
oltp, thanks for your respose, i have tried nbfdec and finally I got a nk.bf from the SD dumpped rom. but it seems this nk.bf is different with the one contained in shipped rom. my purpose for doing that is to custom the extended rom with that SD dumped rom. but I don't konw how to separate all nbfs (ms_.nbf, nk.nbf, etc)from the dumpped rom.
Take a look @ the ftp & see if your current rom is available as a shipped-rom. If so start with the shipped-rom & try it with that.
Or use bal666's tool HTC64_Extended_ROM_Tool_v1.1.zip from http://forum.xda-developers.com/download.php?id=8015. He made one to convert the ext-rom part of a rom-dump to a fat-image, which you can mount & change.
Succes, M
unfortunately, there is no shipped-rom for o2mini_1.12.07_CHS.zip...so my problem is to separate ms_.nbf and nk.nbf from dumpped-rom.
how could i do that with HTC64_Extended_ROM_Tool_v1.1.zip?
does any one know how to break dumped-rom into two nbfs(nk.nbf, ms_.nbf)? or is there any other way to create two nbfs?
FIRST OF ALL I'M NOT RESPONSABLE OF ANY KIND OF DAMAGE OCCURRED DURING THIS PROCEDURE.
DO IT AT YOUR OWN RISK!
Ok, go on now
This guide assumes that you have already dumped your original ROM.
For how to dump your ROM, follow [email protected]'s wiki until obtain imgfs_raw_data.bin
What we need:
Official Pharos WWE ROM
tadzio tool (by tadzio)
XIPPORT tool (by bepe)
bPatch (by suracha)
HTC rom tool (by Dark Simpson) with pharos settings added by me
ROM update utility
I suggest you to create a folder for each tool (eg. C:\tadzio C:\XIPPORT C:\HTCRomTool C:\RomUpdate)
and unzip the tools in the respective folders. bPatch.exe is inside tadzio tool.
Download the official rom, right clic on "RUU_Pharos_HTC_WWE-ME_1.11.456.1_4.1.13.59_03.15.90_BLUE_Ship.exe", select "Open with WinRar" and extract RUU_Signed.nbh in "C:\tadzio"
Open a command prompt, go in "C:\tadzio" and type this command:
Code:
C:\tadzio>nbhextract ruu_signed.nbh
this tool extract the content of the .nbh file, if its all ok you should have these files now:
Code:
00_GSM.nb
01_IPL.nb
02_SPL.nb
03_MainSplash.bmp
03_MainSplash.nb
04_OS.nb
Copy 02_SPL.nb and 03_MainSplash.nb to C:\HTCRomTool and 04_OS.nb to C:\XIPPORT
ok, now we have official SPL and MainSplash ready to use but we need the OS too
To obtain exactly the original OS we need to modify some registry keys inside "boot.hv" according to our language.
This file is located in the XIP section, so we should extract the xip files from 04_OS.nb, modify boot.hv and re-inject the xip in the os.
Don't worry, we have another solution because we already have the original xip obtained from dump process ([email protected]'s wiki)
The XIP section is Part01.raw
Copy Part01.raw to C:\XIPPORT and rename it to "xip_out.bin"
Run xipport.exe, change the offset to "00313800", the filename to "04_OS.nb" (see pic01 at the end of post for detail) and press "write xip_out.bin to:"
This tool write the xip section (xip_out.bin) in the OS (04_OS.nb) at the specified address (00313800).
Now we have 04_OS.nb with our original XIP
Rename 04_OS.nb to OS.nb and copy it to C:\tadzio
Copy imgfs_raw_data.bin obtained from dump process to C:\tadzio
Open a command prompt, go in C:\tadzio and type this command:
Code:
C:\tadzio>imgfstonb imgfs_raw_data.bin os.nb os-new.nb -bigstoragemove
This tool recostructs the OS (os-new.nb) from our dumped image (imgfs_raw_data.bin)
Now we need to patch the size of OS-new.nb, to do this type this command:
Code:
C:\tadzio>bPatch.exe -1 0xFF 0x632D000 OS-new.nb
The size of patched file must be 99.1 MB (103,993,344 bytes)
Ok, our OS is ready to use!
Copy OS-new.nb to C:\HTCRomTool and run "htcrt.exe"
This tool creates and signes a .nbh file from a .nb file. I suggest you to create 2 .nbh, one for OS and Spalsh (eg. OS.nbh)
and one for SPL (eg. SPL.nbh).
Select "ROM builder" tab and fill the fields like screenshots at the end of post:
OS.nbh (see pic02 for detail)
SPL.nbh (see pic03 for detail)
Press "Build!", type the filename without extension and press "Save"
Flash OS.nbh first so if something wrong in the image and the device don't boot you'll be able to flash any other ROM; while, if it boots ok, then flash the SPL.nbh.
Copy OS.nbh to C:\RomUpdate, rename it to ruu_signed.nbh, run "ROMUpdateUtility.exe" and follow the instructions
At this point we have flashed OS and Splash, if its all ok and the device boot right, then you can flash SPL
Delete ruu_signed.nbh, copy SPL.nbh to C:\RomUpdate, rename it to ruu_signed.nbh and run "ROMUpdateUtility.exe"
That's all!! Now you have completely restored your device to its original condition.
I've tested this procedure, worked fine for me and i hope for you too
.
.
.
bye all
.
.
.
isnt there some way to find out if we can enable wifi in the startup of the os? .. then we know if its in the Pharos or not. whadoyathinkhuh? seems in the Artemis wifi is enabled by the os....
avathar behemoth said:
isnt there some way to find out if we can enable wifi in the startup of the os? .. then we know if its in the Pharos or not. whadoyathinkhuh? seems in the Artemis wifi is enabled by the os....
Click to expand...
Click to collapse
i've tried to play around this few time ago with no succes
I've configured wifi interface card throw registry hack, it appears in the network adapter list, but when i turn on wifi nothing happens...
did you use the files i posted in the wifi thread? (posted the tnetw 1251 driver and a file from the extended rom of the artemis... wifinit.exe) but kudos to you for getting a device listed in the pharos (though i looked with task manager i think in a previous rom i flashed and i saw wifi.dll or something loaded at the list of pharos devices)
poldo964 said:
FIRST OF ALL I'M NOT RESPONSABLE OF ANY KIND OF DAMAGE OCCURRED DURING THIS PROCEDURE.
DO IT AT YOUR OWN RISK!
Ok, go on now
This guide assumes that you have already dumped your original ROM.
For how to dump your ROM, follow [email protected]'s wiki until obtain imgfs_raw_data.bin
What we need:
Official Pharos WWE ROM
tadzio tool (by tadzio)
XIPPORT tool (by bepe)
bPatch (by suracha)
HTC rom tool (by Dark Simpson) with pharos settings added by me
ROM update utility
I suggest you to create a folder for each tool (eg. C:\tadzio C:\XIPPORT C:\HTCRomTool C:\RomUpdate)
and unzip the tools in the respective folders. bPatch.exe is inside tadzio tool.
Download the official rom, right clic on "RUU_Pharos_HTC_WWE-ME_1.11.456.1_4.1.13.59_03.15.90_BLUE_Ship.exe", select "Open with WinRar" and extract RUU_Signed.nbh in "C:\tadzio"
Open a command prompt, go in "C:\tadzio" and type this command:
Code:
C:\tadzio>nbhextract ruu_signed.nbh
this tool extract the content of the .nbh file, if its all ok you should have these files now:
Click to expand...
Click to collapse
Failed to pass this step with this message " 'nbhextract' is not recognized as an internal or external command, operable program or batch file"
This command was not included in your attached tadzio tool.
wittanny said:
Failed to pass this step with this message " 'nbhextract' is not recognized as an internal or external command, operable program or batch file"
This command was not included in your attached tadzio tool.
Click to expand...
Click to collapse
oops! sorry
hi
i have not imgfs_raw_data.bin ????
when i run the romupdateutility i get error "invalid vendor id"
please help
lindows said:
when i run the romupdateutility i get error "invalid vendor id"
please help
Click to expand...
Click to collapse
you need HardSPL to flash a NON official ROM
well, actually I went from a Pharos running Poldo v13 (HardSPL Mobiz) to a completely original english Pharos by simply installing Pharos Official English ROM Version 1.11.707.1 (http://forum.xda-developers.com/showthread.php?t=394721).
Now when I boot, everything is original, even the SPL is the original and not the Mobiz anymore.....
Lucky?
fmulinacci said:
well, actually I went from a Pharos running Poldo v13 (HardSPL Mobiz) to a completely original english Pharos by simply installing Pharos Official English ROM Version 1.11.707.1 (http://forum.xda-developers.com/showthread.php?t=394721).
Now when I boot, everything is original, even the SPL is the original and not the Mobiz anymore.....
Lucky?
Click to expand...
Click to collapse
are you italian?
poldo964 said:
are you italian?
Click to expand...
Click to collapse
yes, why? do I write english so bad ?
by the way, I got a question for you: from your signature now you are using your latest rom and the new radio. I now a lot of people likes your new rom very much, but somebody complains about poor battery lasting. Does this new radio improves battery issue?
Cheers
fmulinacci said:
yes, why? do I write english so bad ?
Click to expand...
Click to collapse
no no... i mean that you have a WWE ROM now, not italian... When i've bought my pharos there was an ITA ROM inside and this thread explains "how to completely restore your device to its original condition (warranty coverage)" like the title says
by the way, I got a question for you: from your signature now you are using your latest rom and the new radio. I now a lot of people likes your new rom very much, but somebody complains about poor battery lasting. Does this new radio improves battery issue?
Cheers
Click to expand...
Click to collapse
cannot confirm this, i'm working with kaiser device now... but you can test by yourself, just flash the old radio and see what happens
cu
poldo964 said:
no no... i mean that you have a WWE ROM now, not italian... When i've bought my pharos there was an ITA ROM inside and this thread explains "how to completely restore your device to its original condition (warranty coverage)" like the title says
cannot confirm this, i'm working with kaiser device now... but you can test by yourself, just flash the old radio and see what happens
cu
Click to expand...
Click to collapse
ok, I got it....however my Pharos was French (a great deal, about 150€ at FNAC in Geneva...I could not let it on the shelf), and I did not back it up before upgrading....let us hope in 1 year nothing bad will happen ;-)
Hi all,
I'm looking for the official french version. Could anyone share it or tell me where i could DL it?
Thanks all.