Develop Bugs

AtomLife ROMs extract! Help pls

Hi all,
I am trying to port the mediaplus from AtomLife ROMs which has the second version of mediaplus with icons in circle.
I was successfull in extracting the imgfs.bin but there is onemore file ExROM.img which is not giving up.
I Tried
1. winimage
2. extended drive creator
3. scooter kitchen tools
but i am not able to look into the contents, it has the required _QHiddenPartition directory which has all the theme and image files for FMRadio/Mediaplus and Equaliser.
can anybody help me .
regards
Shreedhara

Mediaplus is very tricky..the images are in Ext ROM..but the links to executables are somewhere from the XIP section..any way keep working

Well
I don't think u understand my problem.
I was able to run the Mediaplus(v1.0) app on my Eten M700 earlier when I had WM5 on my eten.
But after I changed it to WM6, I want something new and hence I am trying to get the Atom Life Mediaplus (v2.0), which is better looking than the earlier one.
But SInce the latest ROM's from O2 have differenct format
It contains
lot of asm.mbss files (Motherboard assembly ) and FLASH.DIO and ExROM.img
with XLDR.nb and EBoot.nb0 files also.
But that Extended rom is hardnut to crack, it does not open at all for any tools we have here.
That'swhy I asked for help, so that I can extract it.

Asus P525 NB0 Kitchen by Anper

russian version can be found on:
http://asusmobile.ru/board/viewtopic.php?t=7816
version 080302_1843
This is english translated version of tool for editing of P525 ROM made by Anper.
Sorry for not so quite good english.
Additionally attached utilities for preparing of GIF "AsusP525GIFConverterByMrToto.zip"
About util KitchenNB0.exe:
Warranty: not any, only can say, that not especially include any harmful code to that utility. And before new version posting was firmware changes in mine PPC that made by that util.
don't known if that util works on other models (don't have it), it's tested only on my own ASUS P525. Flashing was made only thru USBloader.exe (don't knew how - read asusmobile.ru or anywhere in other places).
On mine device installed unchanged bootloader from WM6 official.
On WM5 was tested process completion on pc, but without real tests on pocket.
That Utility allow process images ROMGalaxy.NB0 and Galaxy.NB0
(Advised to use ROMGalaxy.NB0 (withiut bootloader), as more safe variant for Your device).
That images can be got by decoding of Galaxy.cap (decode can be done from that util).
First part of tool allow split to parts, and correcterrors in CHS, cut off bootloader, unpack galaxy.cap to ROMGalaxy.nb0 (used data from tool made by Ingvarr).
Second part allow you process IMGFS partition (partition that contain main
software). In that part partition IMGFS can be extracted to file. Get from that DUMP (in future You can do anything you want with that). After that combine DUMP to IMGFS and at the end combine and recalculate checksum of NB0.
splitting and combining functions of IMGFS to DUMP and back executed by Tadzio made utilities. But so they is made for HTC devices, so I'm correct that accordely to ASUS specific. That functions is called from mine tool (execute bat files is not necessary). Correction may be done by pressing button CORRECTION. ROM size is REALLY CHANGED WITH DECREASING OF nb0 image and accordely to size User storage INCREASED - checked (by recompressing of misar firmwares and by other firmwares corrections).
Checksum calculating made is done by tool, but algorhitm is taken from Ingvarr tools (slightly modified to this tool, that does not create all of file image in memory, but recalculate by chunks).
Process ROMs can in different directories, for no all in one place files garbage.
To flash ready file I'm advise thru bootloader and exactly ROMGalaxy.NB0 (without bootloader). Existence of bootloader you can check in first part of tool.
In that complect persist other tools, needed for coocing your rom.
But accordely to them - you must teach it yourself. I'm don't made that.
Also added in third part possibility to change any of parameters in XIP part of ROM (for correct processing parameters must be changed in order: firstly unpacking, changing, packing, and combining NB0).
Work examples:
1. Open NB0, if that not persist - make it from galaxy.nb0 (by cutting off of bootloader) or from galaxy.cap.
2. If that is homemade firmware, possible will be CHS error in MBR. Correct that by pressing button CORRECT MBR. (Why error persist? - Possible our firmware makers ignore that, or firmware was combined by utilities from Tadzio or other that was not adopted for ASUS (also possible CHS not so sensitive)).
Also may appear message about file size differences with sum of sizes of all partitions - it's not harmful - in most cases simple ignore that.
3. Next is Operations with IMGFS tab. In that part can simple do next processes in shown order. Get IMGFS, Create DUMP, edit DUMP as you wish, from DUMP create IMGFS, combine NB0 new and it's all, can flash. For checking you may open newly created NB0 in first part of tool.
4. Flashing may be done by USBLoader.exe.
Another example - correction and optimization of firmware size:
Shortly about compression:
I'm has provided an opportunity to combine IMGFS.new from DUMP with LZX compression (greatest, but slower starting) and XPR.
Choose by pressing needed button. At once want to warn you about not all firmwares have library with compression LZX, accordely to that after flashing, it will not run further to blue screen.
If you have not broke bootloader, this all is reperable (Many peoples through it passed).
Well, like everything, write at a forum.
And a long life for yoursdevices.
P.S. if you found translation errors - please PM to me.
20080303
Translation fixes, exe packed in own archieve as mainly only it changed
1. unpack kitchen ASUS_P525_NB0_Kitchen.zip
2. place ASUS_P525_NB0_Kitchen.exe from exe.zip to directory from 1.

Thanks DaLiV.
Thanks anper.
Great tools.
Wait for Eng version for a long time.
vivi

thanks anper & Daliv
great tools, Great work!

updated translation.

thanks!
Thanks DaLiV, anper!!
Have been looking for the English version!!
gabz

nice. looks interesting.
will give it a try.
but will it work using wm6/wm6.1 as base ROMs?
cheers!

ericjm said:
nice. looks interesting.
will give it a try.
but will it work using wm6/wm6.1 as base ROMs?
cheers!
Click to expand...
Click to collapse
tool work with WM5, WM6, WM6.1 only for ASUS P525.

anper said:
tool work with WM5, WM6, WM6.1 only for ASUS P525.
Click to expand...
Click to collapse
sweeeeet!
thanks for this one anper (and DaLiV for the english translation!)
can't wait!

How
How can we add additional OEM packages into our rom using this kitchen?

as in all other roms ... split by packages by other tools, if you want, but to that tool return ready dump directory

sorry
DaLiV said:
as in all other roms ... split by packages by other tools, if you want, but to that tool return ready dump directory
Click to expand...
Click to collapse
Sorry, But I cannot understand what you mean. Could you please elaborate?

search forum for tool like "buildos+packagetools" or "dmp2pkg" - then edit packages and after that make conversion back packages to dump

Sweet kitchen
Just letting everyone know that this kitchen can also be used for Dell Axim X51's - I have
For X51 users, make sure you don't click "Repair CHS" - it's for ASUS PDAs only and will result in a bricked ROM
btw You can also use recookstruct as well to sort the dump into packages, you may have to get rid of some entries in "HKEY_LOCAL_MACHINE\System\Inbox\Settings\WelcomeEmail\Templates\ServiceTemplates" because recookstruct can't parse the "®" symbol sometimes found in the key
(Only works with IMGFS, not XIP)

ubiquio (mwg) 501 XIP ported, need help for SYS+OEM

All,
I own an MwG (formerly ubiquio) 501 and eventually started looking for software updates for it. The device is mostly ditto to the imate JAQ3, so I proceeded as follows:
1- get a WM6.1 ROM for JAQ3 (as linked in a thread of this very forum)
2- try to flash it (fail)
3- disassemble the ROM with tools from chinese website (osnbtool.exe)
4- port XIP merging with the ROM of my own device (thanks to the wonderful manual full xip porting thread!)
5- insert my original IMGFS of SYS and OEM
6- success!
the current situation is (settings -> about)
CE OS 5.2.20269 (Build 17936.0.3.0)
The performance boost obtained by upgrading the XIP is significant (keyboard is usable and video playback is ~ 15fps @ full screen), but I would like to perform more optimizations (e.g. switch to .NET CF 3.5) but as soon as I start to work with the dumped SYS and OEM I have troubles, it seems that every kitchen is expecting to work on the XIP (or on .nb and .nb.payload) but such files are not compatible with the one I get from osbntool.exe (but the dump folder is).
Do someone have advice on how to proceed? I would like to either
1-find a kitchen that works with my device
2-go for manual cooking
For 2 I achieved to split the dumped folder to packages and removed some of them, then - as far as I understood - I would need Greloc (got it) and bepe's buildos.exe (nowere to be found )
Is someone willing to help me? Thanks a lot.
Rest assured I am going to share the obtained ROM (I am already willing to share the current one, of course, just drop me a line!)
Best,
DAniele

HP iPAQ 21x Custom ROMs-Help Needed!

Hello, I'm new here, and I have been attempting to make two custom ROMs for the HP iPAQ 21x series, and I ran into a huge problem. I have two dump folders, and I can't figure out how to turn either of them into an NBH(or NBF) file. Any help would be highly appreciated.
Edit:Oh, and also, in case anyone was wondering, I'm trying to make them a Windows Mobile 6.1 ROM and a Windiows Mobile 6.5 ROM, and they are both(as far as I know) clean, except for the HP stuff.

nbh or nbf... ? for what ? it is inpossible to flash it back, you need bldiag.nb0 and hpimage.bin (foxconn format) but fortunatly pdocwrite works fine, so you need to: dump or download dump of imgfs (part02, os) unpack it via imgfstodump, cook to wm 6,1 or 6.5, then convert back to imgfs via imgfsfrom dump, and write via pdocwrite, xip can be also writed by this way, xip is part01, it works but i'm not a rom cooker so I cant cook it myself...
edit: it is also possible to edit marvell obm's and bootloader, but only via linux
edit2: here is my post about ipaq 214 and pdocwrite http://forum.brighthand.com/showpost.php?p=1762892&postcount=4
edit3: it will also works on any 21x and 11x and as I think on other hp devices manufactured by foxconn

I'm sorry elektrownik, but I don't really get what you're saying, I'm not very experienced with this ROM stuff, this is the first time I've ever tried to make one. But in response to what you're asking(I think), I was going to make them NBH files, make a backup ROM image of the device, and then use the HP RUU, which I have made to look for a file called 'RUU_signed.nbh'(what I will name them), to update the device via Activesync connection.

Update:OK, I've managed to get a little further, and now I have two BIN files, and two NB.PAYLOAD files, and I'm pretty close to turning them into NB Files.

But how do you want to sign it for hpruu it need hp cert and key, or did you cracked it. Anyway here is default rom. http://rapidshare.com/files/2236847...n_marked_internally_with_custom_extra_data.7z

Oh, well I didn't know it had to be signed, but in the ROM files which I was basing mine off of(which I thought you made) was an HP digital signature file(.cer) that said it went an HP 21x Image Update, I clicked on it, Windows said it installed the certificate, and then the file dissapeared. I'm not sure if that will help use the HP RUU or not, but I found it kind of odd. Also, if you'd like to take a look at it I can put it up for download somewhere(there was another one).

Fdo35 said:
Oh, well I didn't know it had to be signed, but in the ROM files which I was basing mine off of(which I thought you made) was an HP digital signature file(.cer) that said it went an HP 21x Image Update, I clicked on it, Windows said it installed the certificate, and then the file dissapeared. I'm not sure if that will help use the HP RUU or not, but I found it kind of odd. Also, if you'd like to take a look at it I can put it up for download somewhere(there was another one).
Click to expand...
Click to collapse
just do what I wrote - cook wm 6.1 or 6.5 to romdump convert it back to imgfs and it will be posible to write it to device by pdocwrite application

Fdo35 said:
Update:OK, I've managed to get a little further, and now I have two BIN files, and two NB.PAYLOAD files, and I'm pretty close to turning them into NB Files.
Click to expand...
Click to collapse
What parameters did you use for Tadzio's imgfs tools on NBSplit?

Fdo35 do you know how to flash ipaq 21x?
Maybe you can work together with some people already trying to make wm6.5 rom....
Kind regards,
W.

Steven855 said:
What parameters did you use for Tadzio's imgfs tools on NBSplit?
Click to expand...
Click to collapse
What's "parameters", I don't know what you mean. Also I don't remember using NBSplit, I started out with a IMG file which I then dumped.
Edit:Oh wait, I see what you mean. I didn't use NBSplit, I was following the attached directions to reconstruct ROM, except it wasn't for the device the file specified, and instead of 'imgfs.bin', I used a file called 'ipaq214.img', and instead of 'Windows.nb' I used a file called 'flash.nb'. And, I'm pretty sure that elektrownik made both files.

lol why you all dont read what i wrote, i have rom, which was reconstructed from dump, but it impossible to flash it from sd like on htc by flash.bin, ipaq 214 need bldiag.nb0 and hpimage.bin to be flashed from sd, but those files never was released so it is impossible to study format in which they coming, 214 can be also flashed from pc, but it need foxconn application and like before hpimage.bin, and there is official metchod - hpruu, but files which it use need to be signed first, we dont have cert and key to sign them, it wold be possible to patch hpruu to delate sign validation but i dont see anyone who working on this, as i wrote only one working metchod is pdocwrite application, i check it and it works, but i'm not room cooker so i cant cook wm 6.1 or 6.5 imgfs...

I think there are quite few topics about it.
It would be maybe better to have EVERYTHING relevant in one so everyone who posesses knowledge can help.
Now it looks that we (you) are inventing hot water... no offence - i appreciate all the hard work you put into this. But we (you) need better cooperation and clean topic.
I am grateful to everyone who share and try to make something. Respect to you all!
Kind regards,
WODP

The HP iPAQ 110 has a ROM update on HP's website, is it possible to get any of those files from that?
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=215348&prodSeriesId=3644061&prodNameId=3644062&swEnvOID=4014&swLang=13&mode=2&taskId=135&swItem=hh-59617-3

HP iPAQ 210 Flashing

Hey, sorry to start another thread, but I noticed that on HP's web site there was a ROM Update for the iPAQ 110 series, and I remembered that the reason why the iPAQ 210 couldn't be flashed was because we didn't have certain files needed to flash to it. And, I was wondering if it was possible to get any of those files from it, or maybe even replace the IMGFS partition to make it compatible with the iPAQ 210(and change the OS version too), and use hpruu.exe to flash it to the iPAQ 210, if that's possible that is.
Edit:I have Windows Mobile 6.1 and 6.5 IMGFS(in BIN format), so I don't need anyone to do that.

Well I suppose if that's not possible, is there any way I could use a program like pdocwrite to write the files to the IMGFS partition, and if so, how?

Well, I guess I'll just try to get an HTC Touch HD and flash a Windows Mobile 6.5 ROM to it instead of trying to develop one for the iPAQ 210. Oh, well, at least I tried. Here are the 6.1 and 6.5 IMGFS partition files for it in case anyone wants them.
Note:The File Hoster will only allow 10 downloads, so only download if your actually going to do something with it.
http://rapidshare.com/files/257934918/CEimage_6.1_.bin.html
http://rapidshare.com/files/257934921/CEimage_6.5_.bin.html