How to restore a dump - Part*.raw - Please !!!! - HTC Vox

Hello,
I really need to restore a dump
I have the 3 files of pdocread : Part00.raw ; Part01.raw ; Part02.raw
How can I make a Rom with this file !!
Is there a post on xda to explain it?
many thanks !
at this time i have do this :
hat`s steps I take:
1. 'imgfstodump part02.raw` (result: ok)
2. imgfsfromdump part02.raw imgfs.new.bin (result: ok)
3. Use a donor .hbh to extract, Have a 04_os.nb
4. Nosplit -hermes 04_os.nb (result: ok) Have now: 04_os.nb.payload (rename to: 04_os.nb.old.payload)
5. Imgfstonb imgfs.new.bin 04_os.nb.old.payload 04_os.nb.payload (result: error. "MSFLSH50 header not found.")

Related

nbf, nba, n_d, n_e...now I am totally lost!

Hi,
At first I want to cook the pdamobiz customized AKU23 rom to make it clean, so I read this thread http://forum.xda-developers.com/viewtopic.php?t=34171 and decided that I need to convert the nbf file found in the rom package to nba first.
So I tried using xda3nbftool and got the following result:
Code:
E:\makerom>xda3nbftool
Usage: xda3nbftool [-u] { -c | -e | -d } inputfile outputfile password
-c : calculate crcsum of file
-u : updates the calculated checksum
-e : encrypt inputfile
-d : decrypt inputfile
-x : xor inputfile with password ( should be a number )
-t : automatically find the xor key, with -x auto decrypt
-sd : change devicetype
-so : change operatorname
-sl : change language
-sv : change version
-v : verbose
HimaUpgradeUt v0400, v0500 use password HTC
HimaUpgradeUt v0600 uses password 921211
HimaUpgradeUt v0910 uses xor with 0x89124137, 0x25863614 or 0x12345678
HimaUpgradeUt v1000 uses xor with 0x20040304, 0x20040305 or 0x20040306
E:\makerom>xda3nbftool -t -x nk.nbf nk.nba
NK.nbf: Permission denied
ms_.nbf: No such file or directory
Radio_.nbf: No such file or directory
E:\makerom>
Then I tried typhoon nbf tool v0.4, thinking maybe with it I can dump the OS part. But I only found options to dump rom into .n_d or .n_e format, still not the nba file I wanted.
And then I read a thread saying we can use typho5 to extract the nbf file into several nb files and then use winimage to edit it...
Now I am completely lost! Please tell me by which way I can remove those utilities I don't want from the OS rom, would you?

How For Extracting Files From Cooked Rom

hi!!
i downloaded llbasha-WM5-AKU35pp16c3 rom
i want extract os.nb file from nk.nbf with typho5 utility (typhoonbftool_v5),i got this error:
unknow header format, and it abort work.
other way:
i want extract os.nb file from nk.nba with prepare_imgfs, and i got this error:
searching for IMGFS start.......Not found!!!
anybody know if it can extract some file from a rom already cooked ???
thank in advance
use xda2nbftool
open command prompt -> xda2nbftool.exe -c nk.nbf nk.nba 0x20040304 press enter.

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"

Categories

Resources