yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] NeuronNetwork:
thank you :o

yes it will be the same size because osnbtool able to search/look for that specific IMGFS type image inside ciphone rom file. osnbtool should be use with the FLASH file, not rom file. when you use with rom file, it will ignore all the other partitions and it also didnt care about the header inside the rom file which is wrong.

it is smaller because you didnt merge with other partitions inside rom image. that's why i said you have to extract all other partitions inside your rom image and merge it with your new unmodified FLASH file. your new generated rom image is only contained flash partition without the header and other partitions, this is wrong already.
[Upgrading, Modifying and Unlocking] NeuronNetwork:
yes

i named the partition based on the type. yes it's so important and you must merge these other partitions too in order to cook your own rom ;)

no. the windows mobile OS is together inside the FLASH file. the FLASH file contain OEM specific drivers, languages, screen resolution, XIP image and OS image.

yes. it's not in the proper order, but i do have to mind you that i've seen the rom file still working even improperly ordered. it seems the offset, size and info of the partition plays important part here. :rolleyes:
[Upgrading, Modifying and Unlocking] NeuronNetwork:
let me look through ETENtool for awhile. i'll see what i can do with it. :rolleyes:

it seems you're having a locked IMGFS image file.

i'll try even it makes me confuse :p
[Upgrading, Modifying and Unlocking] NeuronNetwork:
the process you're saying is correct.
[Upgrading, Modifying and Unlocking] Hellmuth:
It seems to me confusion :confused: disappears slowly :) :):):)

Why? You don't? I just used the CiPhone.bxx from the Update of the Firmware (see Picture)

It seems to me you don't have Problems with the IMGFS.bin

Witch way did you went? How did you get your data?
[Upgrading, Modifying and Unlocking] Hellmuth:
You are right. In the installation folder of the Ciphon Firmware Update is a File called Ciphone.bin or CiphoneImage.

This file has to be placed into the Source-folder of my kitchen. You have to rename it to Ciphone.bin anyway Because I wrote the batchfiles to use this name.

But sad the Chinese 6.5 Rom is Read-protected you can't dump the IMGFS.bin.

Grüße Hellmuth
[Upgrading, Modifying and Unlocking] rolfey:
ok, I think I'm making some headway here, first of all I've used your batch file to extract the partitions from the Rom, then I used XIPPort.exe to crack open the Xip.bin, this creates an out folder, within that there are 2 more folders created called Files and Modules. I'll keep you posted on my next move.

@NeuronNetwork, yes I understand that the partitions in my diag may be in the wrong order, when then flash file is modified I take it the partition order would be important, the flash file has to know what the flash partition number is?

Mike
[Upgrading, Modifying and Unlocking] NeuronNetwork:
there are several methods to protect a rom.. search the forum you'll find several ways to unlock.. you may have more interest on the kitchen, look for "T5355 C02 kitchen".. it's from the same manufacturer who create C6 :) the kitchen able to process FLASH file ;) it's not meant for C6, but the process of extracting and combining about the same (although not exactly).. the rom file has very similar structure as C6 though :rolleyes:.. several files are in chinese, but i dont understand chinese so dont ask me the meaning of any words.. use translator if you do stumble into problems..
[Upgrading, Modifying and Unlocking] NeuronNetwork:
it's a number, but merely more to a type.. type 0x05 to be specific ;)
[Upgrading, Modifying and Unlocking] rolfey:
hey Hellmouth, I've been going through your batch file and after redirecting everything to a log, for me anyway the script seems to be broken, I've inserted loads of pauses so I can see what you've done and what's working and what's not. now it may just be my set up but this is what I have .

1 step.

the directory is changed to the source directory and osbtool is run against Ciphone.bin

from Ciphone.bin 5 files are generated.

DosPartition

imgfs

xip

Ciphone.bin.OS.NB

Ciphone.bin.PRE

Ciphone.bin.OS.NB and Ciphone.bin.PRE seem to be generated as a by product of (DosPartition,imgfs,xip)

What are Ciphone.bin.OS.NB and Ciphone.bin.PRE? Also an XIP folder seems to have been created in Root, I take it this is a product of osnbtool.

2 step

We move back to the root directory and then copy xip.bin to the current and root directory and rename it to xip_old.bin

If xip.bin has only just been extracted, then why is it being named _old and moved to the root?

3 step xipdump is run against the XIP_old.bin from root, it knows how to reach tools to run because a path was defined.

4 step Rom folder is created in Root.

5 step the XIP folder is moved into the Rom folder.

6 step romhdr is also moved to the Rom folder

7 step changing directory to the Rom folder and and clearing all attributs against the xip folder.

8 Step boot.hv,boot_ms.rgu,boot.rgu files are all moved oemxipkernal to the xip directory.

9 step ImgfsToDump.exe is run againt imgfs_old and the output I think is the dump folder?

10 step from the tools folder, packetbuilder.exe is run against the dump folder in root, but fails!!! should this be run against the folder? or it's contents?

11 step attributes are applied to the dump folder

12 step attributes would be addes to the metadata folder if it existed

13 step stuff from the metadata folder would be moved into the dump folder if it existed.

14 finally the dump\oem folder is moved to the oem folder but this does not exist as far as I can see so fails.

Mike
[Upgrading, Modifying and Unlocking] rolfey:
by the way I'm downloading that kitchen you suggested to see how easy it may be to use with the Ciphone rom, I'll update you.

Mike
[Upgrading, Modifying and Unlocking] rolfey:
wow, well spotted Neuron, this really looks like it could be worth a shot, and not far away at all from what we have been using, but I would have to change the language in the bat file to see what would need to be changed, that would be most helpful.

Mike
[Upgrading, Modifying and Unlocking] NeuronNetwork:
there are 2 more partition types identified :D ModemNV(for CDMA device, not exist for GSM) and Customer :) another new news is that the very first boot screen :rolleyes: and windows mobile boot screen are stored in the same FLASH file ;)
[Upgrading, Modifying and Unlocking] rolfey:
I was looking at this kitchen for this other phone, but I don't understand what's happening because it's all in Chinese :( this is making it difficult to see what's going on.

How did you found out about the other partitions Neuron?

Mike
[Upgrading, Modifying and Unlocking] MobileXT:
Is this possible to delete this file so that will boot into the OEM splash screen.
[Upgrading, Modifying and Unlocking] NeuronNetwork:
It's more on programming aspect, those venture in this arena knows how to do it ;)
[Upgrading, Modifying and Unlocking] NeuronNetwork:
what do you mean by OEM? if it's from manufacturer then the original one should be the apple logo(but i dont think there's originality, everything is cloned) :D you have to change, i have never tried to delete it. but it's possible that only FLASH partition exist in a single rom file, since the flashing tool able to write to specific location based on the type and there is one rom file exhibit this characteristic and it works :)
[Upgrading, Modifying and Unlocking] MobileXT:
So, the only thing can change this boot screen is the flashing tools then. Do you think that the Kaiser_SPLASH_BIOS_080818r_Genetic will do the job.
[Upgrading, Modifying and Unlocking] rolfey:
@Neuron

I would like to ask a few questions, but in a slightly different way,

osbntool will unpack partitions in a Rom:

osnbtool -sp CiPhone.bin

osnbtool -d CiPhone.bin.OS.NB 0 boot.bin

osnbtool -d CiPhone.bin.OS.NB 1 xip.bin

osnbtool -d CiPhone.bin.OS.NB 2 imgfs.bin

osnbtool -d CiPhone.bin.OS.NB 3 DosPartition.bin

CiPhone.bin.OS.NB

CiPhone.bin.PRE

What partition is the flash partition?

xidump is used against the xip.bin to unpack.

what are the files contained in this dump folder?

imgfstodump is used to unpack the imgfs.bin to the dump directory, these looks like Operating system files?

At this point are there any other things that need to be unpacked or is that it?

what files where, are commonly modified?

at this point I just want to fully unpack the Rom, and then then glue it back together again to see if it's flashable.

Mike
[Upgrading, Modifying and Unlocking] NeuronNetwork:
these two are just

parts

of FLASH partition. osnbtool only able to process *.OS.NB file, it

cannot

process *.PRE file. since it's part of it(not all) that's the reason why it's always reduced in size in the end and totally wrong. this is why i have to create my own tool. the startup screens are stored inside *.PRE file :rolleyes:.

these are parts of it, not the whole:)

search the forum if you want to know what xip is all about. contained very important drivers, boot information, languages, and others to make sure your os can be boot.

yes it is:)

the os are commonly modified. if you want to overclock you have to modify xip too.:rolleyes:

you have not fully unpack the rom, not even the flash partition. even if you manage to fully unpack the whole rom you cant simply glue it using copy /b, it wont work. flash partition is in the middle of the rom, all subsequent partitions will be improperly addressed if you just copy like that. in addition to that, there are 3 level of checks in place. ;) osnbtool cannot handle all these, so you can't really see as it's not flashable at all.
[Upgrading, Modifying and Unlocking] rolfey:
Ahhhhh, thankyou Neuron!

the story is becoming a little clearer at last :) no wonder the Roms so far are not flashable with a vital bit missing.

by the way I didn't think you could just copy bit and pieces back together to make up the Rom, I'm guessing that they have to be merged back together in the correct order and format?

Mike
[Upgrading, Modifying and Unlocking] NeuronNetwork:
yes the order and format are stored in the header, osnbtool also cannot handle this. that's why we need a new tool ;)
[Upgrading, Modifying and Unlocking] rolfey:
I am about to pull out the ruu file using Duttys nbhtool, but I'm not sure what to do with that file, does this have to be broken down again, this is the rom update file yeah? am I correct it saying that this file contains the boot screen stuff, images and so forth?

Mike
[Upgrading, Modifying and Unlocking] NeuronNetwork:
yes it does contain all that stuff, it's out of the scope of this thread, so you have to search it in the forum there are several ways to extract all images of ruu file.
[Upgrading, Modifying and Unlocking] rolfey:
if this is something that just isn't needed to be altered in order to create a wm6.5 Rom for the Ciphone then fiddling with that will be way down the line for me, hey we need to just be able to break the rom apart and put back together again first lol.

I just needed know if I had gone far enough down the extraction path with that file! but we still need to be able to open the *.pre file?

What's in the Pre file is it that we need to modify before recompiling the whole rom?

Mike
[Upgrading, Modifying and Unlocking] NeuronNetwork:
done on extracting and combining it back. it's flash-able and working. but im still analyzing several unknown areas of the rom file.

no need. osnbtool ignore *.pre file. manufacturer use this area/section(not file) to store pictures :rolleyes: boot screen and etc.. if you dont want to change the boot screen and other pictures, then no need to modify this area/section(not file again since osnbtool treat this area/section wrongly that's why it's ending with *.pre because it didnt know what it is exactly).
[Upgrading, Modifying and Unlocking] rolfey:
Ok, so I'm with you then Neuron, I've just put together my own really really simple kitchen for now, I'll improve it after I know it works.

What tool are you using down your end to merge the Rom back together?

and what about this size problem with the new Rom coming up short, or was that just the way it was unpacked that wasn't quite right?

Mike
[Upgrading, Modifying and Unlocking] NeuronNetwork:
i create my own since osnbtool cannot be used. you can see screen shot in one of attachment in a post inside this thread.

it's running fine with reduced in size. the problem back then was because i use imgfstodump to extract the os but it has several problems so it extract improperly and resulting in lost of several files on the new unmodified rom so i created my own tool to handle all these.
[Upgrading, Modifying and Unlocking] rolfey:
ahh that's very interesting, because I too have been extracting using imgfstodump.exe, but when running packagebuilder against the dump folder there were always errors and missing stuff, that's one of the reasons that I've not even tried to rebuild the Rom yet, that and the fact that I was not sure what to expect to see in a successful extraction. I've not had any dealing AT ALL with cooking until now, so I have nothing to compare the extractions to, that's why you've had all the questions :)

Mike
[Upgrading, Modifying and Unlocking] rolfey:
I think if you've made it that far Neuron, than we are in your hands!

When will you be releasing flpkg? and will you releasing a kitchen to go with this, or just the exe?

Mike
[Upgrading, Modifying and Unlocking] NeuronNetwork:
i'll be releasing it after i've done analyzing on several unknown portion. i've other things to attend to. i dont think i have plenty of time to do a kitchen.
[Upgrading, Modifying and Unlocking] MobileXT:
That's sound good NeuronNetwork keep up the good work and your the best.
[Upgrading, Modifying and Unlocking] rolfey:
Yes thanks Neuron,

I'll keep fiddling around with the simple kitchen that I have, and just use your tool to unpack the Rom fully when you when you are willing to allow me to use it.

Thanks again Neuron!:)

Mike
[Upgrading, Modifying and Unlocking] rolfey:
Hi Neuron, I just though you would like to know, someone at Cifans has manged to open the rom and change the boot logo, my guess is, if he's managed to do that with the other tools that we've been using it's going to be fully possible to create a flashable 6.5 Rom, I know you have a working tool - but I'm waiting to see what he's used to do this.

Mike
[Upgrading, Modifying and Unlocking] NeuronNetwork:
yes you can change everything including the two boot logo inside the rom. and yes 6.5 also running in ciphone. the person is not using osnbtool and that's for sure :)
[Upgrading, Modifying and Unlocking] rolfey:
I have to tool to do the job Neuron, what it does it extract the partitions as .nb0 format.

Flash.nb0

xldr.nb0

ipl.nb0

usbload.nb0

Raminit.nb0

now, as the tables have turned again, today's questions is ...

is the OS contained in the Flash.nbo > I think it probably is.

and do you know of a tool to use to extract the OS from this.

and Lastly, this will only unpack a 6.1 Rom, so I would have to change the whole OS to 6.5 and then repack, I seem to think that the folders that would need changing are VM, Rom, and SYS, but I'm not sure at this stage how to do this , and how to maintain the driver base used in 6.1

are you able to offer yet even more guidance?

Mike
[Upgrading, Modifying and Unlocking] NeuronNetwork:
:)

yes

now you may use osnbtool against the flash file. it's compatible but dont say i suggest it.

changing the whole os to 6.5 requires you to modify XIP. the driver is not inside any of these folders, it's inside XIP. wm6.5 is using new memory model, and that's why you have to modify the XIP in order to cater for new 6.5. if you are unsure better not. even though you've completely erase the flash file(no os at all), you will still be able to reflash it even without os ;) and that's the function of USBLoad file. so dont touch other than FLASH file :rolleyes:
[Upgrading, Modifying and Unlocking] rolfey:
Hi Neuron, this seems to defeat the whole purpose of the exercise? maybe i've misunderstood you, but you seem to be saying that you're advising me not to change the Rom to 6.5? but this is what I've set out to do! this has been my whole aim from the start?

Mike
[Upgrading, Modifying and Unlocking] NeuronNetwork:
you have to understand the new memory model for wm6.5. there's info about this here in this forum. im not discourage you, but i dont have the time to explain all these in great details.

by the way, have you test extract and combine back the rom file using the tool that you have from that person? are you sure it's working fine on your ciphone?
[Upgrading, Modifying and Unlocking] rolfey:
yes, I can extract and put it back together to make a flashable Rom!

but I can't unpack it past the file structure that you showed you in my previous post. osntool does not seem to recognise the file, and complains that the partition table is wrong.

Mike
[Upgrading, Modifying and Unlocking] NeuronNetwork:
which file structure do you mention about? how do you extract it with osnbtool? what are the output?
[Upgrading, Modifying and Unlocking] NeuronNetwork:
can you attach the tool here so all other people able to use it?
[Upgrading, Modifying and Unlocking] asger-shah:
c6 rom

hi all ciphone devolopers i am the person who has successfully unpacked the rom and repacked it and then successfully flashed with no problem and i wanted to ask if you can upload the tools that you are using to make the rom and inreturn i will provide you with how to unpack the bin to get all the partition and then reback so pls responce asap

Thanks
[Upgrading, Modifying and Unlocking] Hellmuth:
Hi Asger-Shah

Her comes the Link :)

http://rapidshare.com/files/338409355/Hellmuths_K__che_7_letzter_versuch.rar

I hope it will help you

Grüße Hellmuth
[Upgrading, Modifying and Unlocking] Hellmuth:
Hi MobileXT,

may be this is the solution to your splash-screen problem

http://www.cifans.com/forum/index.php?f=31&t=1899&rb_v=viewtopic##p

Grüße Hellmuth
[Upgrading, Modifying and Unlocking] asger-shah:
i mean i need the other tool that can extrack .nbo files and then reback back in to .nbo and if you can supply this to me then i am pretty sure creating the rom with be no problem and i have the whole weekend to do this so pls can you post the toold to megaupload.com as rapidshare.com sucks.

Thanks
[Upgrading, Modifying and Unlocking] Hellmuth:
Do you mean IMGFSfromnb and IMGFStoNB

They are in my toolset

I changeged the download from normal to privileged please try again I think it should work better now
[Upgrading, Modifying and Unlocking] igor192:
Hi Hellmuth,

your link don't work :-(

If this posible, pls place new link

Thank you
[Upgrading, Modifying and Unlocking] Hellmuth:
Download should work

Try again please
[Upgrading, Modifying and Unlocking] Hellmuth:
Sorry I'm not quiet sure what you need. But I think this will help more.

http://xdaforums.com/showthread.php?t=572673

Grüße Hellmuth
[Upgrading, Modifying and Unlocking] MobileXT:
Yes Hellmuth,

asger-shah he succesfuly replace the boot screen to the original apple logo with no problem. We need to help him out in order to give us the tools to unpack the bin file and repack again and hopefuly we will have a WM6.5 ROM soon and this will help the english community.
[Upgrading, Modifying and Unlocking] Hellmuth:
... and the German community aswell :) :D :cool:
[Upgrading, Modifying and Unlocking] rolfey:
Hi everyone, just got back from work, good to see all you good people mucking in!!

I don't think osbtool will unpack the .nb partition, futher more I don't think this partition is a real .nb format, nothing I have done so far has unpacked it.

there has to be a way to do it though!!!

Mike
[Upgrading, Modifying and Unlocking] Hellmuth:
What do you mean we can't extract *.nb from from the Romfile or do you mean we can't extract data from the extracted .nb file?

Grüße Hellmuth
[Upgrading, Modifying and Unlocking] rolfey:
yes exactly, you can use the utility to break down the Rom into it's respective partitions,

Flash.nb0

xldr.nb0

ipl.nb0

usbload.nb0

Raminit.nb0

but to make changes to the OS, you would have to open up flash.nbo.

you may have more luck than me, but osnbtool will not open that .nb0

o, it see's the format as unrecognisable - this is why I think it's not really an nb0 file.

Mike
[Upgrading, Modifying and Unlocking] MobileXT:
Sorry Hellmuth, definitely yes! the German Community aswell..
[Upgrading, Modifying and Unlocking] needle2k:
Hi m8´s,

Why not sharing the knowledge of how to unpack the c6 rom step wise?

We should collect steps each made already to come to the point instead of saving secret´s & tools ;)

Hellmuth shared his too

thx

needle
[Upgrading, Modifying and Unlocking] rolfey:
oh I'm not trying to hide anything, but I didn't think that I had more to offer than anyone else at this point!!

I agree together we may be able to come up with a solution faster, but I thought that was what we were doing? I've attached the tool that I used to break down the Rom, it take it down enough so you can change the boot logo, but not further so far, if we could do that then we could get to the OS

edit: damn, it won't let me attach this file, but if you want it PM me with your email address and i'll send it to you.

Mike
[Upgrading, Modifying and Unlocking] rolfey:
hey everyone I've been doing some testing, what I've found that works as far as opening up the flash file is this

first copy your Cipone.bin image into the idt folder, you have to have this tool in the first place, then this is what I've got to so far....

1 - run the makelogo.bat file within the idt folder, if you haven't used this tool yet either I'll give you instructions or else ask asger.

Once you've used this tool to extract the partitions, you should have something like this ...

RAMInit.nb0 size=1kb

USBLoad.nb0 size=45kb

XLDR.nb0 size=128kb

IPL.nb0 size=117kb

logo.bmp size=255kb

flash.nb0 size=113,209

now this is the extra bit that I've done,

now i've run osbntools -sp flash.nb0 this will give you ..

OS ROM Partition Tool V1.59 By Weisun :> PDAclan.com

Sector size : 0x00000800

Extra data bytes : 0x00000008

OS IMAGE found.

Partitions infomation:

**************************************

Part-0 type: BOOT SECTION image

Part-1 type: XIP RAM Image

Part-2 type: IMGFS file system

Part-3 type: legit DOS partition

**************************************

flash.nb0.PRE written.

-------------------------------------------------

Sector counters (extra-data) found in source file.

Partition 0 true offset:00000002 true size:0000027E Len:0000027E

Partition 1 true offset:00000280 true size:00000740 Len:000006C0

Partition 2 true offset:000009C0 true size:0000CD80 Len:0000CD00

Partition 3 true offset:0000D740 true size:00000140 Len:00011DC0

flash.nb0.OS.NB written.

and now you will have 2 extra files in your folder called flash.nb0.OS.nb and flash.nb.pre.

As far as I know .pre is not needed to modified, so I have gone on with using

xidump.exe -build flash.nb0.os.nb

this will then, or should give you now a good dump of the xip folder and also even better an imgfs folder with the OEM stuff in it.

it's over to you lot now - this is as far as I've managed to get this evening, but it feels like some progression to me, I don't know if it is :confused:

Mike
[Upgrading, Modifying and Unlocking] NeuronNetwork:
Thank You needle2k, you really understand our intention ;)

Thank You Hellmuth, and because of you we are all here sharing and unite :)

i have never analyze kaiser