Database Info

Help Kaiser's XIP

Could anyone help me plz?
this is what i did:
Code:
nbsplit -kaiser os.nb
RomMaster -x -w 5 OS.nb.payload -s 0x320000 -o xip.bin
dumprom xip.bin -5 -d XIP
nbsplit is from imgfs tools 2.1rc2 vesion.
but i can not get xip folder and dump folder.
i think there's no problem of this
Code:
nbsplit -kaiser os.nb
and
dumprom xip.bin -5 -d XIP
and i think the problem is in this:
Code:
RomMaster -x -w 5 OS.nb.payload -s 0x320000 -o xip.bin
many many thanks in advance.
see attchment with which tool i used if it is helpful.

qooqoo said:
Could anyone help me plz?
Click to expand...
Click to collapse
What are the output for every command? do you see any error on the screen?
Cheers.

jcespi2005 said:
What are the output for every command? do you see any error on the screen?
Cheers.
Click to expand...
Click to collapse
thank you~
this is what i see
Code:
dumprom xip.bin -5 -d XIP
unable to determine loading offset for xip.bin
i think xip.bin isn't correct.

qooqoo said:
thank you~
this is what i see
Code:
dumprom xip.bin -5 -d XIP
unable to determine loading offset for xip.bin
i think xip.bin isn't correct.
Click to expand...
Click to collapse
What happen if you try this one...
RomMaster.exe -x -w 5 OS_03.nb.payload -o xip.bin

jcespi2005 said:
What happen if you try this one...
RomMaster.exe -x -w 5 OS_03.nb.payload -o xip.bin
Click to expand...
Click to collapse
with this:
RomMaster.exe -x -w 5 OS_03.nb.payload -o xip.bin
i got same result:
dumprom xip.bin -5 -d XIP
unable to determine loading offset for xip.bin

qooqoo said:
with this:
RomMaster.exe -x -w 5 OS_03.nb.payload -o xip.bin
i got same result:
dumprom xip.bin -5 -d XIP
unable to determine loading offset for xip.bin
Click to expand...
Click to collapse
And one stupid question i forgot to do before, do you have an XIP folder created inside this one you are? If not, make one writing "md XIP" and try again the dumprom command...

jcespi2005 said:
And one stupid question i forgot to do before, do you have an XIP folder created inside this one you are? If not, make one writing "md XIP" and try again the dumprom command...
Click to expand...
Click to collapse
yes i did that, i use code like this:
Code:
mkdir XIP
dumprom xip.bin -5 -d XIP
there is nothing in xip folder.

qooqoo said:
yes i did that, i use code like this:
Code:
mkdir XIP
dumprom xip.bin -5 -d XIP
there is nothing in xip folder.
Click to expand...
Click to collapse
Where did you get the OS.NB file?

jcespi2005 said:
Where did you get the OS.NB file?
Click to expand...
Click to collapse
i tried several roms,
Dutty_s_hybrid_Rom_Build_18533_beta_2_fixed
Helmi_Kaiser_1.57.00.02_AKU.0.7.0.Cooked
HTC_TyTNII_FRA_1.56.406.5_22.45.88.07_1.27.12.17_Ship
Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship
kaiser_dopodasia_wwe_1.81.707.0_radio_sign_22.45.88.07_1.27.12.11_ship
they all like this

qooqoo said:
i tried several roms,
Dutty_s_hybrid_Rom_Build_18533_beta_2_fixed
Helmi_Kaiser_1.57.00.02_AKU.0.7.0.Cooked
HTC_TyTNII_FRA_1.56.406.5_22.45.88.07_1.27.12.17_Ship
Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship
kaiser_dopodasia_wwe_1.81.707.0_radio_sign_22.45.88.07_1.27.12.11_ship
they all like this
Click to expand...
Click to collapse
Let me try with one of this OS files and see what happen.

jcespi2005 said:
Let me try with one of this OS files and see what happen.
Click to expand...
Click to collapse
many many thanks for your answers, and wait for your result

qooqoo said:
many many thanks for your answers, and wait for your result
Click to expand...
Click to collapse
There are some problem with the extracted xip.bin file, and don't know why fail.
The size for dumped XIP from live Kaiser have different size with this xip.bin file from NB file. I can extract the XIP folder from dumped XIP (3.584Kb) but the same tool fail with the extracted from NB file XIP (3.038Kb). So seems the RomMaster.exe is not doing the work fine, but don't know why.
The good news is you can use a part01.raw from any device to get the XIP and extract the content. If you look for dumped ROMs on the forum, you couldfind many.
Cheers.

jcespi2005 said:
There are some problem with the extracted xip.bin file, and don't know why fail.
The size for dumped XIP from live Kaiser have different size with this xip.bin file from NB file. I can extract the XIP folder from dumped XIP (3.584Kb) but the same tool fail with the extracted from NB file XIP (3.038Kb). So seems the RomMaster.exe is not doing the work fine, but don't know why.
The good news is you can use a part01.raw from any device to get the XIP and extract the content. If you look for dumped ROMs on the forum, you couldfind many.
Cheers.
Click to expand...
Click to collapse
thank you very much, i got it, it was caused by the vesion of rommaster, a friend give me the right rommaster, and it works fine.
i upload the new tool here, hope it can help other guys

qooqoo said:
thank you very much, i got it, it was caused by the vesion of rommaster, a friend give me the right rommaster, and it works fine.
i upload the new tool here, hope it can help other guys
Click to expand...
Click to collapse
Great finding, man. Sure this helps more ppl...
Many thanks for sharing this version of rommaster (and thanks to your frined too, of course...)
I'll give a try later...
EDIT: Yes, works fine... One strange thing is dumped XIP is bigger than extracted from NB ship... just strange... who knows.

The mistake...
I beleave i found the mistake...
I your first post you have this line...
RomMaster -x -w 5 OS.nb.payload -s 0x320000 -o xip.bin
And in your last post the line was
RomMaster.exe -x -w 5 -b 0x320000 OS.nb.payload -o xip.bin
Can you see the difference? Yes, the -s instead -b....
I compare the version of RomMaster you posted, and my version, and are the same, so the big deal is the -b instead -s
Cheers.

jcespi2005 said:
I beleave i found the mistake...
I your first post you have this line...
RomMaster -x -w 5 OS.nb.payload -s 0x320000 -o xip.bin
And in your last post the line was
RomMaster.exe -x -w 5 -b 0x320000 OS.nb.payload -o xip.bin
Can you see the difference? Yes, the -s instead -b....
I compare the version of RomMaster you posted, and my version, and are the same, so the big deal is the -b instead -s
Cheers.
Click to expand...
Click to collapse
i found that but with old rommaster, -d don't work, there are some differences between these two, i think.
for cooking magician's rom, there is also a rommaster, but these three is also different.
the old rommaster i post in the first page, with that one, there is no problem during dumping hermes's xip.

qooqoo said:
i found that but with old rommaster, -d don't work, there are some differences between these two, i think.
for cooking magician's rom, there is also a rommaster, but these three is also different.
the old rommaster i post in the first page, with that one, there is no problem during dumping hermes's xip.
Click to expand...
Click to collapse
I thought that I already told you the correct command for dumping kaiser xip is:
Code:
RomMaster -w 5 OS.nb.payload -x -b 0x320000 -o xip.bin
thats all.. -b is the key (ROM begin at)..

helmi_c said:
I thought that I already told you the correct command for dumping kaiser xip is:
Code:
RomMaster -w 5 OS.nb.payload -x -b 0x320000 -o xip.bin
thats all.. -b is the key (ROM begin at)..
Click to expand...
Click to collapse
thank you very much helmi_c, the problem is the vesion of rommaster i have is different from yours, i used -b, it said that the parametre is incorrect.
now it works fine, thanks for your help

@qooqoo: My RomMaster version is 2.3. What is the old one you used? I was looking in my computer for all RomMaster.exe files, and all are the same version...anyway, thanks to helmi_c for helping here
I think was a good idea to put this ussefull info about extracting the XIP from NB file in the Wiki... any volunteer?
Cheers.

Cooked images in Device Emulator?

Hi,
is there a way to test cooked images with MS device emulator?
I'm trying to do that but I get the following error message:
Error: cannot open file name.bin
Any suggestion?
Bye
Giosemmo

Nope, device emulator is not really emulator - it runs x86 version of WM, not ARM version, so binaries are different and not compatible. It is for testing developed software (which is compiled for different targets, either emulator, or real device)

Device emulator is ARM!
No, the device emulator isn't x86 - hasn't been for a long time. Check out the download page for the v2 release. The first comment on what's new with this version is:
Greatly improved performance at executing ARM instruction - reduces cold-boot time and improves application execution speed.
But I don't have the answer - it would be sweet to be able to run cooked roms on the emulator!

I searched a lot yesterday and it seems there is no way to use coocked rom on the emulator.
Thank you guys.

kingbing said:
No, the device emulator isn't x86 - hasn't been for a long time. Check out the download page for the v2 release. The first comment on what's new with this version is:
Greatly improved performance at executing ARM instruction - reduces cold-boot time and improves application execution speed.
But I don't have the answer - it would be sweet to be able to run cooked roms on the emulator!
Click to expand...
Click to collapse
Mea culpa then - thank you for the info!

I used to read this: (http://forum.xda-developers.com/showthread.php?t=298327&page=20 post:#194)
05-10-2007, 08:03 PM
Hi friends,
I try to modify a WM6 ROM from the MS device emulator (standalone) before I use on my X51v (coward scared ? me ? hum !)
I download a US Professional Image from : http://www.microsoft.com/downloads/...A8-1DD7-426F-A913-4F370A65A582&displaylang=en
I rename "PPC_USA_GSM_VGA_VR.BIN" to "OS.nb"
>NBSplit -emu OS.nb
create "OS.nb.extra" (6144 Kb) and "OS.nb.payload" (92160 Kb)
>ImgfsFromNb OS.nb.payload imgfs.bin
ImgfsFromNb 2.0 RC 2
Searching for IMGFS start...
Found IMGFS at 00285000.
Dumping IMGFS at offset 00285000 (size 0577aff0)
Done!
create "imgfs.bin" (89580 Kb)
ImgfsToDump imgfs.bin
create "dump" (Directory : 99,1 Mb=103.925.370 bytes)
and "dump_MemoryMap.txt"
I don't change anything (in dump directory or file dump_MemoryMap.txt)
ImgfsFromDump imgfs.bin imgfs-new.bin
create "imgfs-new.bin" very (too?) quickly (36864 Kb !!! Want more Storage? hey this is !!! )
ImgfsToNb imgfs-new.bin os.nb.payload os-new.nb.payload
ImgfsToNb 2.0 RC 2
No IMGFS partition found in partition table in os.nb.payload. Exiting.
I don't understand my mistake but I think a problem at the ImgfsFromDump command
If I use the Mamaich's Tools after NBSplit -emu OS.nb
prepare_imgfs.exe OS.nb.payload -nosplit
create imgfs_raw_data.bin (89344 Kb) and imgfs_removed_data.bin (0 Kb)
viewimgfs.exe imgfs_raw_data.bin
create "dump" (Directory : 99,1 Mb=103.925.370 bytes)
and "dump_MemoryMap.txt
BuildImgfs.exe
imgfs_raw_data.bin (89344 Kb) and imgfs_removed_data.bin (0 Kb)
make_imgfs.exe OS.nb.payload -nosplit
OS.nb.payload (92160 Kb)
NBMerge -emu OS.NB
OS.nb (98304 Kb)
rename OS.NB to PPC_USA_GSM_VGA_VR.BIN
and exécute with emulator it's OK (image modified if I modify the dump directory)
That's happen ?
Thank you (and sorry for my bad english)

try to build Korean Rom, Please help!!!

First, thanks for all the thread regarding building roms.
I was trying to translate and build WM6 korean for my tilt.
There are couple threads for how to make it from WM6 images.
I was following. However, whenever I am trying I get following error message.
Can any body tell me what is wrong?
------------------------------------------------------------------
Microsoft Windows [Version 6.0.6000]
(C) Copyright 1985-2005 Microsoft Corp.
E:\Download\Pocket PC\Kaiser\Tem>nbsplit -kaiser a.bin
NBSplit 2.1rc2
Using data chunk size = 0x800 and extra chunk size = 0x8
on file a.bin
Done.
E:\Download\Pocket PC\Kaiser\Tem>imgfsfromnb a.bin.payload imgfs.bin
ImgfsFromNb 2.1rc2
Input file 'a.bin.payload' has no valid boot sector! Aborting.
-------------------------------------------------------------------
I tried to change a.bin to os.nb and tried next, but same result.
---------------------------------------------------------------------
E:\Download\Pocket PC\Kaiser\Tem>nbsplit -kaiser os.nb
NBSplit 2.1rc2
Using data chunk size = 0x800 and extra chunk size = 0x8
on file os.nb
Done.
E:\Download\Pocket PC\Kaiser\Tem>imgfsfromnb os.nb.payload imgfs.bin
ImgfsFromNb 2.1rc2
Input file 'os.nb.payload' has no valid boot sector! Aborting.
-------------------------------------------------------------

Find where ROM begins (rommaster)

Hi,
I'm trying to extract XIP part of an orange rose rom here :
http://forum.xda-developers.com/showthread.php?t=450221
I know how to obtain OS.nb with nbhextract, but i don't know how to find "rom begin".
If i use nbsplit to obtain os.nb.payload, i don't know what option i must use.
And after, if i use "kaiser" option with nbsplit, i don't know how to extract xip with rommaster, and what "begin" option i can give.
How i can find it ?
Thanks.

No idea please ?
I always have this problem.
Thanks.

try this:
Code:
RomMaster.exe -x -w 5 -b 0x320000 OS.nb.payload -o xip.bin
good luck

Hi,
I was able to :
nbsplit.exe -kaiser OS.nb
and :
RomMaster.exe -x -w 5 -b 0x320000 OS.nb.payload -o xip.bin
and :
dump xip.bin with XIPPort
I obtained :
OUT and files usually found in xip.bin
BUT, how i can find this start adress 0x320000 ?
This value is for kaiser, but i don't konw if it's ok with others devices.
And how i can know if "kaiser" value is good with nbsplit ?
Thanks.

moved to Q&A section. please post your questions in the Q&A section next time.

fireburned said:
Hi,
I was able to :
nbsplit.exe -kaiser OS.nb
and :
RomMaster.exe -x -w 5 -b 0x320000 OS.nb.payload -o xip.bin
and :
dump xip.bin with XIPPort
I obtained :
OUT and files usually found in xip.bin
BUT, how i can find this start adress 0x320000 ?
This value is for kaiser, but i don't konw if it's ok with others devices.
And how i can know if "kaiser" value is good with nbsplit ?
Thanks.
Click to expand...
Click to collapse
Read the last few sentences of my post. It may be the long way to go about it, but it works for me.
http://forum.xda-developers.com/showpost.php?p=2846121&postcount=58

KMFM$ said:
Read the last few sentences of my post. It may be the long way to go about it, but it works for me.
http://forum.xda-developers.com/showpost.php?p=2846121&postcount=58
Click to expand...
Click to collapse
I always have a problem.
I want to extract XIP from this rom :
http://forum.xda-developers.com/showthread.php?t=450221
I tried this :
Code:
nbhextract.exe *.nbh
I obtain :
03_OS.nb => renamed to OS.nb
I tried :
Code:
ImgfsFromNb.exe OS.nb imgfs.bin
ImgfsFromNb 2.1rc2
ImgFs partition starts at 0x00000000 and ends at 0x00000000
Dumping IMGFS at offset 0x006c6c00 (size 0xff939400)
Done!
How i can use nbsplit ?
How i can extract XIP ?
I don't know how i can use nbsplit to obtain OS.nb.payload and OS.nb.extra
I tried rommaster to extract XIP (but it doesn't works because i don't use OS.nb.payload i think) :
Code:
RomMaster.exe -x -w 5 -b 0x006c6c00 OS.nb -o xip.bin
[Info] It is a common ROM.
[Error] File is damaged, end address small than start address.
[Error] File is damaged, end address small than start address.
Could you help me please ?
Bye.

No idea, please ?

How to dump TP2 ROM from Phone

I have successfully dumped the ROM from my Brand New VZW Touch Pro 2 ... Here is how I did it. You will need itsutils to dump the ROM, and imgfstools to extract it.
Dump:
1) List partitions - Should show Part00 to Part03 - pdocread -l
2) Get Part00 address - pdocread -w -d FLASHDR -p Part00 -t -b 0x800 - Find the partition address (displayed as 0x######)
3) Dump Part00 - Use address from step 2 - pdocread -w -d FLASHDR -p Part00 -b 0x800 0 0x###### Part00.raw
4) Repeat steps 2 & 3 for Part01, Part02 and Part03 ... MAKE SURE YOU USE THE CORRECT ADDRESSES
Partitions:
Part00 - Core XIP? (May have something to do with AutoUpdate)
Part01 - XIP
Part02 - OS IMGFS
Part03 - User Storage (TFAT)
Extract XIP (Part00 and Part01 ... You will need bepe's dumpxip.exe from ervius visual kitchen):
1) Make sure there is not an XIP folder (if so, rename it) and run dumpxip Part00.raw
2) Rename XIP folder to XIP_00 (ren XIP XIP_00)
3) Make sure there is not an XIP folder (if so, rename it) and run dumpxip Part01.raw
4) Rename XIP folder to XIP_01 (ren XIP XIP_01)
Extract IMGFS (Part02):
1) imgfstodump Part02.raw - This will create a folder called dump, and extract the contents to it.
View User Storage (Part03):
1) Mount Image using DaemonTools Lite
To rebuild flashable ROM from DUMP (Currently OS Only, No radio or SPL):
1) You need a base_os.nb.payload for your device ... See below for details
2) Convert OS IMGFS (Part02.raw) to nb.payload (new-os.nb.payload) imgfstonb Part02.raw base_os.nb.payload new-os.nb.payload
3) Insert XIP (Part01.raw) into new-os.nb.payload implantxip Part01.raw new-os.nb.payload
4) Merge os-new.nb.payload into os-new.nb nbmerge -kaiser new-os.nb
5) Create os-new.nbh nbhutil, Select "Touch_Pro2" under "Target Device", change RHOD*** to RHOD500, click the ... box next to OS, and select new-os.nb, click Build NBH and select where to save NBH file.
How to get a base os.nb.payload:
1) Download a stock ROM and extract RUU_Signed.nbh
2) Extract RUU_Signed.nbh nbhextract RUU_Signed.nbh - This will list the files extracted ... The one you need is ##_OS.nb ... Copy as os.nb copy ##_OS.nb OS.nb
3) Split OS.nb to OS.nb.payload nbsplit -kaiser OS.nb
4) Create OS.imgfs.bin imgfsfromnb OS.nb.payload OS.imgfs.bin
5) Create empty directory called 'DUMP' (If a DUMP folder exists, rename it) mkdir DUMP
6) Create a blank IMGFS file imgfsfromdump OS.imgfs.bin blank_imgfs.bin
7) Create base_os.nb.payload imgfstonb blank_imgfs.bin OS.nb.payload base_os.nb.payload

Dump SPL and Radio
Does anyone know how to do this?

Oh my god I found the answer on "how to dump a rom from the TP2"!
Could someone rename the topic in something like "official guide" or stick it?
I think it could be useful for a lot of people..

dj13241 said:
How to get a base os.nb.payload:
1) Download a stock ROM and extract RUU_Signed.nbh
2) Extract RUU_Signed.nbh nbhextract RUU_Signed.nbh - This will list the files extracted ... The one you need is ##_OS.nb ... Copy as os.nb copy ##_OS.nb OS.nb
3) Split OS.nb to OS.nb.payload nbsplit -kaiser OS.nb
4) Create OS.imgfs.bin imgfsfromnb OS.nb.payload OS.imgfs.bin
5) Create empty directory called 'DUMP' (If a DUMP folder exists, rename it) mkdir DUMP
6) Create a blank IMGFS file imgfsfromdump OS.imgfs.bin blank_imgfs.bin
7) Create base_os.nb.payload imgfstonb blank_imgfs.bin ##_OS.nb.payload base_os.nb.payload
Click to expand...
Click to collapse
Aloha Man,
- i'm trying to use your tutorial to Dump and Rebuild an HTC ROSE (S740) ROM
- i'm at the point where i've downloaded the RUU_Signed, and folowed the above procedure until step 7
- in step 2, i've replaced ## in ##_OS.nb with 03, witch is the number of the file after nbhextract
- i can't find 03_OS.nb.payload and at step 7, the command spits out and error :
" ImgfsTools 2.1rc2>imgfstonb blank_imgfs.bin 03_OS.nb.payload base_os.nb.payload
ImgfsToNb 2.1rc2
Using bigstorage mode
Input file 03_OS.nb.payload cannot be opened. Exiting "
Should i rename
OS.nb.payload to 03_OS.nb.payload or change the syntax on the command input file accordingly ?
tks again alot for your help !

UrbanWarrior said:
Aloha Man,
- i'm trying to use your tutorial to Dump and Rebuild an HTC ROSE (S740) ROM
- i'm at the point where i've downloaded the RUU_Signed, and folowed the above procedure until step 7
- in step 2, i've replaced ## in ##_OS.nb with 03, witch is the number of the file after nbhextract
- i can't find 03_OS.nb.payload and at step 7, the command spits out and error :
" ImgfsTools 2.1rc2>imgfstonb blank_imgfs.bin 03_OS.nb.payload base_os.nb.payload
ImgfsToNb 2.1rc2
Using bigstorage mode
Input file 03_OS.nb.payload cannot be opened. Exiting "
Should i rename
OS.nb.payload to 03_OS.nb.payload or change the syntax on the command input file accordingly ?
tks again alot for your help !
Click to expand...
Click to collapse
You are correct ... Step 7 should should not have the ##_ ... I have corrected the instructions above in my previous post. The command should be:
Code:
imgfstonb blank_imgfs.bin OS.nb.payload base_os.nb.payload

dj13241 said:
To rebuild flashable ROM from DUMP (Currently OS Only, No radio or SPL):
1) You need a base os.nb.payload for your device ... See below for details
2) Convert OS IMGFS (Part02.raw) to nb.payload (new-os.nb.payload) imgfstonb Part02.raw os.nb.payload new-os.nb.payload
3) Insert XIP (Part01.raw) into new-os.nb.payload implantxip Part01.raw new-os.nb.payload
4) Merge os-new.nb.payload into os-new.nb nbmerge -kaiser os-new.nb
5) Create os-new.nbh nbhutil, Select "Touch_Pro2" under "Target Device", change RHOD*** to RHOD500, click the ... box next to OS, and select new-os.nb, click Build NBH and select where to save NBH file.
How to get a base os.nb.payload:
1) Download a stock ROM and extract RUU_Signed.nbh
2) Extract RUU_Signed.nbh nbhextract RUU_Signed.nbh - This will list the files extracted ... The one you need is ##_OS.nb ... Copy as os.nb copy ##_OS.nb OS.nb
3) Split OS.nb to OS.nb.payload nbsplit -kaiser OS.nb
4) Create OS.imgfs.bin imgfsfromnb OS.nb.payload OS.imgfs.bin
5) Create empty directory called 'DUMP' (If a DUMP folder exists, rename it) mkdir DUMP
6) Create a blank IMGFS file imgfsfromdump OS.imgfs.bin blank_imgfs.bin
7) Create base_os.nb.payload imgfstonb blank_imgfs.bin OS.nb.payload base_os.nb.payload
Click to expand...
Click to collapse
Aloha again,
i need some further clarifications if u are so kind :
- i've properly finished the "How to get a base os.nb.payload" section, so now i have a "base_os.nb.payload" file
- going back to point 2 of the section "To rebuild flashable ROM from DUMP (Currently OS Only, No radio or SPL)", i've succesfully executed points 2 and 3 , but when i go to try point 4 nbmerge spits out the following error :
"NBMerge 2.1rc2
Could not open input file os-new.nb.payload"
My Questions :
- where do u use the "base_os.nb.payload" file that's created at the "How to get a base os.nb.payload" step ? since the file is called "base_os.nb.payload" and in the command syntax description u call it : "base os.nb.payload"
- until point 4 of the "To rebuild flashable ROM from DUMP (Currently OS Only, No radio or SPL)" section in the syntax u use the name "new-os.nb.payload" for the file,
- from point 4 on u use the term "Merge os-new.nb.payload into os-new.nb" -> so os-new.nb.payload , and NBmerge is expecting "Could not open input file os-new.nb.payload" but until point for we've created a file called "new-os.nb.payload"
- shouldn't the syntax for the commands from point 2 thru 4 be what NBMerge is expecting ? meaning "os-new.nb.payload"
thanks again for your help!

When I get home from work today, I will run through the steps and eliminate any errors I find.

UrbanWarrior, I have updated the 'Build a Flashable ROM' section step 2 ... I changed the reference to 'os.nb.payload' to 'base_os.nb.payload' ... Let me know if you run into any other issues.

I was trying the steps for my HTCJade to dump my stock ROM. Things were going smoothly however, the step
"Insert XIP (Part01.raw) into new-os.nb.payload implantxip Part01.raw new-os.nb.payload"
fails with an error "XIP File not Specified!"
I noticed that the mentioned step is not following tha syntax of the command:
Usage: implantxip -XIP <xip.bin> -PAYLOAD <.nb.payload> [-ImgStart <hexvalue>] [
-uldr [tryremove] ] [-PP <MbValue>] [-NoCert]
The command expects "xip.bin" but i am giving the argument as Part01.raw as per the step.
What to do? Can anybody help.

svaym said:
I was trying the steps for my HTCJade to dump my stock ROM. Things were going smoothly however, the step
"Insert XIP (Part01.raw) into new-os.nb.payload implantxip Part01.raw new-os.nb.payload"
fails with an error "XIP File not Specified!"
I noticed that the mentioned step is not following tha syntax of the command:
Usage: implantxip -XIP <xip.bin> -PAYLOAD <.nb.payload> [-ImgStart <hexvalue>] [
-uldr [tryremove] ] [-PP <MbValue>] [-NoCert]
The command expects "xip.bin" but i am giving the argument as Part01.raw as per the step.
What to do? Can anybody help.
Click to expand...
Click to collapse
i had the same problem. i just did "implantxip -XIP Part01.raw -PAYLOAD new-os.nb.payload"