Hey guys. I need your help. I think that with our combined know how, we can achieve this.
The Herald formats its storage memory using the size of the os.nb within the nbh file. It completely ignores the actual partition table within the os.nb. The problem is that the flasher for the Herald and Atlas has a size requirement of 51.2mb. If the file is smaller than this, the ruu says the image is corrupt. I can pad the image with FF's but it will still use the physical size of the file. (This is an observation, I haven't had time to "test" out my assumption.)
Can someone help me figure out a way to hack the RUU to allow flashes of smaller size?
ANY help will be GREATLY appreciated.
Bump. Anyone willing to help? I've been trying to decompile the RomUpdateUtil to no avail. I don't have the tools and the knowhow.
At the very least does anyone know what tools I can use? All my decompiling tools only work on Win32 files.
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.
I am working on a WM5 version of the popular VGA hack OzVGA. I have all the registry settings I need but am missing some files from a QVGA installation of WM5. A member of the Himalaya forum provided me with his 96dpi DLLs but they appear to be incomplete and/or buggy.
Would it be possible for someone to rip and e-mail me the following files form your Wizard?
browsres.96.dll
coreres.96.dll
exappres.96.dll
instmsgrresources.96.dll
miscres.96.dll
msim.96.dll
officeres.96.dll
outres.96.dll
pegcards.96.dll
pmsnresources.96.dll
pptres.96.dll
riresdll.96.dll
shellres.96.dll
shellresapps.96.dll
syncres.96.dll
tapres.96.dll
trares0409.96.dll
tshres.96.dll
Thanks in advance.
i will rip them for you if you tell me how i can do it?, as it will not let me just copy the files to my pc?
SURE
YES
I'LL DO THE SAME, JUST TELL ME HOW TO DO IT,,,
Not having a Wizard I don't know how you would do it. I'm guessing you would need to download the rom from your device and then rip the files using the correct offsets.
Need someone more knowledgeable than me to advise on how to do it.
hi
this might help.....
awhile back i was messing with my jasjar and wanted to copy some files from windows directory ...after trying i found renaming them and then copying them worked for most files
like browsres.96.dll could be renamed to browsre2.96.dll orbrowsres.96.dll2 ...
try and let us know
TIA
Anyone know how I can extract .nbf files? I need to see what is in this nbf file. Refer to this thread if you are curious
http://forum.xda-developers.com/viewtopic.php?p=250201#250201
Use the tools made by Buzz on this page:
http://buzzdev.net/index.php?option=com_content&task=view&id=65&Itemid=1
To see the contents of the nbf (converted to nba using the above method) file, you need to use these tools:
http://wiki.xda-developers.com/index.php?pagename=WM5EditROM
Its rather simple and hardly takes about 5 minutes for the whole thing
Cheers!
Thanx for the fast response. I gave it a go and it dosent seam to work. I get the .nba from the .nbf then when trying to
"prepare_imgfs.exe nk.nba"
I get this
"Searching for IMGFS start... Not found!"
I think that the .nbf is password protected. If anyone more gifted than me can help out with this one I know we will find a way to change the splash screen on all the newer (2.17 an so forth) ROMS.
Thanx again; Lew
then how do you extract NBF file from 8125 instead of NBA file ? Is there a way to do this ?
I would like input on this as well. I think we are missing a password here or something.
universaldoc said:
Use the tools made by Buzz on this page:
http://buzzdev.net/index.php?option=com_content&task=view&id=65&Itemid=1
Click to expand...
Click to collapse
I don't believe this works with (newer?) wizard nbf's.
Is there anyone here that could crack this would be "encryption" on the .nbf in question? I tried encoding my splash backup from aWizard using the project file from the "decoded" nk.nbf from "ruu_forcedalias_splash_245_425.exe" and it was a no go. It said that my storage was the wrong size for this ROM update (or something to the effect of NO). So it looks as if this nk.nbf from "ruu_forcedalias_splash_245_425.exe" is the key to unlocking the ability to change splash screens to custom images.
Later; Lew
u can try the tools in the attachment to extract files from image file.
the typho2 can extract parts from a SD card image, and the typhoonnbftool_04 can extract parts from a NBF file. they work well while do with the 1.x ROM, but I've never experienced it in extracting a 2.x ROM.
any exciting info, pls let me know,
Ok, good news, thanx to BrightMoonHeart I have been able to extract the BMP from the NBF using "typhoonnbftool_04.exe". The bad news is so far I can't seem to add an image (bmp) to the nbf or remove the current image. So this was a great step forward, just need a little help to get r done. I tried "typho2.exe" but I couldn't get it to do anything except give me the same info "typhoonnbftool_04.exe", It says it can extract the ".NBF" to an ".SPL" and that may allow us to edit it but I was not able to get it to convert. Any ideas guys? Always appreciated
Thanx; Lew
Ok I'm even closer now. I am using "typhoonnbfdecode.pl" and I can extract the ".nb" from the ".nbf". I can create custom splash using "nb_image_converter_859_418_826.exe" and make a ".nb" but when trying to put it back to ".nbf" i get this error
Code:
read 00030000 for splash from 92000000-Splash.nb
no sm signature at 0 in Splash
If anyone can help me out with any of this I would really appreciate it. I keep getting held up with all these conversions. I think some out there must know how to do this already, and I'm close but I keep hitting road blocks.
my head hurts; Lew
I have an iPAQ hx2790 (JPN) with WM5 and I was wondering if someone can point me in the right direction of extracting files from the ROM area. I did some searching and also looked at the WM5 ROM Tools thread, but I tried all these tools in vain. I tried dumping a ROM image from my ppc (using the tool that auto-dumps ROM into storage card) and extracting that but it didn't work (I believe it locked up). I tried dumping the original .nbf ROM upgrade file provided by HP but that didn't work as well. I just need to extract 3 .dll files so if someone can point me in the right direction, I'd greatly appreciate it!
You should decrypt NBF file, then the tools would work.
Currently there is no decryption tool available, you should make it yourself.
I don't remember the encryption used in HP NBF format, but it should be simple, maybe XOR with a constant string, and maybe some garbage added after each block.
Thanks for your reply mamaich, I didn't know HP's NBF was encrypted. Is there source code for a decryption tool someone made for another NBF format already?
I have a diagnostic .nbh image for Hermes devices. When copied to the storage card and started in bootloader mode, the device will boot the image and enter a diagnostics sort of mode. The utility ends after a bit when some "security checks" fail. I'd like to analyse the file but I'm having some trouble. I am somewhat experienced in disassembling ARM code, but I'd like to start at a higher level than that. I can convert the file to a .nb using the tools available on the forums, but I can't seem to break it down any further from there. Is anyone here familiar with the .nb file format? When I attempt to use the tools that convert a .nb to a ROM dump it fails saying "Not an img file" or something like that. It reads as a straight binary file in IDA so I'd have to manually identify an entry point in order to analyse it further.
The interface of the diagnostic mode looks similar to what is displayed when a ROM is being updated - a gray screen with a blue system font.
I can tell from looking at the .nb that there is significant functionality that I would like to check out further.
Any help?
fluxist