Hello,
Which is the purpose of the command
pdocread -w -d FLASHDR -b 0x800 -p Part02 0 0x4560000 Part02.raw
and
CopyTFFSToFile(0x0, 0x4560000, Part02.raw)
Thank you
I have manage to upload the .raw files for the vodafone uk ROM.
I don't know how to make it into a ROM so just gave you what I have.
link below:
Dump.rar
If some can make it into a ROM for me that would be great.
1: download a kitchen, for example http://forum.xda-developers.com/showthread.php?t=408951
2: if you have Part01.raw and Part02.raw, put it into the "source" folder
3: Place the RUU_signed.nbh from the prebuilt ROM into the "source" folder
4: Rebuild using the right hand side menu.
Thank you! Now I can have my voda rom backup
Thanks for the files.
Rebuilt but would like to know what information should go in the boxes in the htc rom tool.
Device Diamond*
Model ID DIAM***** Should this be changed?
Country ID 11111111 Should this be changed?
Version 1.93.456.3 WWE What is the original Vodafone ROM details
Language WWE
Does it matter what goes in these boxes as I trying to build a backup ROM just in case I need to return my phone under warranty.
Thanks
oops...delete this
What did you use to back up your ROM?
Garetht said:
I have manage to upload the .raw files for the vodafone uk ROM.
I don't know how to make it into a ROM so just gave you what I have.
link below:
Dump.rar
If some can make it into a ROM for me that would be great.
Click to expand...
Click to collapse
Glad lad...
You had the patience to learn and do this yourself nice one
Firstly you will need to download the file below:
http://nah6.com/~itsme/itsutilsbin-20080313.zip
Once you have downloaded the file you will need to extract it into a folder.
You will see lot's of icons and programs in the folder but that is normal.
Now go to "Start" and then "Run" on your PC and type 'CMD'.
This will open a command prompt window (DOS window).
You will need to get to the folder where to extracted the downloaded file from.
The folder that I use is in my C:\ drive, so in my DOS command window it will look like this: C:\>.
Helfire got this for me and you just need to follow this for the next part:
This is a copy from the post i mentioned think i know what your doing wronas i did the same.
Go to the folder with itsutils in command prompt window eg. c:\itsutils
Then type pdocread.exe -l
You then should see the following. ive cut of the bit at the bottom.
C:\bin>pdocread.exe -l
210.38M (0xd260000) DSK1:
| 3.12M (0x31f000) Part00
| 4.38M (0x460000) Part01
| 106.38M (0x6a60000) Part02
| 96.50M (0x6080000) Part03
3.75G (0xf0000000) DSK7:
| 3.75G (0xf0000000) PART00
STRG handles:
handle e6932666 3.75G (0xf0000000)
handle e7cae8da 96.50M (0x6080000) (Part03)
handle c7db27be106.38M (0x6a60000) (Part02)
handle a7db279a 4.38M (0x460000) (Part01)
handle 67db2752 3.12M (0x31f000) (Part00)
[...]
Ok take note of the values underlined as they will probs be different for some of the parts.
Next enter below changing the values to match the ones you got from above step underlined.
pdocread.exe -w -h 0x67db2752 -b 0x800 0 0x31f000 Part00.raw
When it finishes you should see below
CopyTFFSToFile(0x0, 0x31f000, Part00.raw)
Next enter below changing the values to match the ones you got from above step underlined.
pdocread.exe -w -h 0xa7db279a -b 0x800 0 0x460000 Part01.raw
When it finishes you should see below
CopyTFFSToFile(0x0, 0x460000, Part01.raw)
Next enter below changing the values to match the ones you got from above step underlined.
pdocread.exe -w -h 0xc7db27be -b 0x800 0 0x6a60000 Part02.raw
When it finishes you should see below
CopyTFFSToFile(0x0, 0x6a60000, Part02.raw)
Next enter below changing the values to match the ones you got from above step underlined.
pdocread.exe -w -h 0xe7cae8da -b 0x800 0 0x6080000 Part03.raw
When it finishes you should see below
CopyTFFSToFile(0x0, 0x6080000, Part03.raw)Dump the bootloader:
To dump the bootloader
Code:
pmemdump.exe 0xa8000000 524288 SPLdumped.nb
When it finishes you should see below
CopyProcessMemoryToFile(00000042, a8000000, 00080000, SPLdumped.nb)
I hope this helps you as its what i did.
By the looks of it you typed the whole pdocread.exe -w -h 0xa7db2752 -b 0x800 0 0x31f000 Part00.raw CopyTFFSToFile(0x0, 0x31f000, Part00.RAW)
when you only need to type pdocread.exe -w -h 0xa7db2752 -b 0x800 0 0x31f000 Part00.raw
as the CopyTFFSToFile(0x0, 0x31f000, Part00.RAW) is the output.
Let me know how you get on, it took me a while but when Helfire showed me this it all made sense.
Thanks
I'm stuck at the first hurdle with the -
Could not update itsutils.dll to the current version, maybe it is inuse?
try restarting your device, or restart ActiveSync
Click to expand...
Click to collapse
Do you get that message when you have downloaded the ITSUTILS and try to extract it ?
No, it seems it wants to put that on my phone, my phone displayed a message asking if I wanted to run the program. Seems I need to do a regdit somehow to allow it to run.
I think it might just be easier to get a copy of your ROM if that's ok. I've downloaded your dump already, have you made that back into a ROM yet?
you have to use first cert.cab then enablerapi.cab then softreset
after this you can make your dump
Trying to back up the rom...
adwinp said:
2: if you have Part01.raw and Part02.raw, put it into the "source" folder
3: Place the RUU_signed.nbh from the prebuilt ROM into the "source" folder
Click to expand...
Click to collapse
Sorry for my ignorance, but where do I get the RUU_signed.nbh ? and don't I need Part03 and 04 at all?
Gadgetgal-C said:
Sorry for my ignorance, but where do I get the RUU_signed.nbh ? and don't I need Part03 and 04 at all?
Click to expand...
Click to collapse
Nope. No need for part 3 & 4.
RUU_signed - take from any stock ROM (just extract).
Where could a noob learn the fine art of Rom flashing?
adwinp said:
Nope. No need for part 3 & 4.
RUU_signed - take from any stock ROM (just extract).
Click to expand...
Click to collapse
Thanks for the hint. Is there any thread that would explain in more detailed procedure how to do this (extracting the RUU_signed and the whole backing up the old and flashing a new roms)?
Sorry, my ex did this kind of things for me in the past, but now I am trying to learn myself how to manage all this... Apologise for those noobie questions, but I've gotta start somewhere.
Has anyone managed to assemble this back into a working ROM yet?
Help
Please can someone make the RAW files in the first post into a ROM for us, then I can get it uploaded for everyone else.
I'd like this too if somone would be so kind.
Thanks
Garetht - Did you see my post with the Vodafone Nav if you were interested.
I posted a simular question in another board and no one answered. I assume that anyone who read it did not know or it as the wrong forum. so after 2 days of reading the forum I am posting this question here.
Is there a generic tool for dumping Windows Mobile ROM?
I have a Hantel Q5 Phone that I would love to MOD.
I have tried the itsutilsbin package but it would not copy the dll. I then manually copied the dll, tried again... didn't work. soft reset... didn't work. I thought that maybe it needed to be in some sort of recovery mode and tried starting the phone holding different key combination's. I did find one that did a hard reset (by holding the End key while powering on the phone.) I did not find any other combination's that would do anything.
This is a inexpensive alternative to some higher priced phones and I am surprised that no one here has tried anything with it yet.
Thanks for reading.
Just noticed elf0100 above the Serial sticker
Does this mean this device a HTC Touch clone?
Ok so I have gotten a little farther
First I moved to an XP machine...
Then I used a regeditor and edited HKLM\security\Policies\Polices0001001 dword value to 1 (it was set to 2)
this allowed pdocread.exe to read some information. it was not complete but it gave me enough information to do a search.
I then tried pdocread.exe -w TrueFFS -p Part02 -t
this resulted in..
ERROR: ITTFFSGetInfo - The device is not ready for use.
WARNING: using default 512 bytes for sectorsize
real nr of sectors: 1 - 512.00byte, 0x200
well that did not look right so I searched for it and I then found a diamond ROM dumping thread with a similar problem.
This thread outlined a way to specify handles and sector sized ( at least that is what I think it is)
So I did the following
Code:
E:\WM6\itsutilsbin-20088313>pdocread.exe -l
122.13M (0x7a20000) DSK1:
| 1.25M (0x31f000) Part00
| 2.00M (0x200000) Part01
| 46.63M (0x2ea0000) Part02
| 72.25M (0x4840000) Part03
3.69G (0xec580000) DSK2:
| 3.69G (0xec180000) PART00
STRG handles:
handle 47e7be7a 3.69G (0xec180000)
handle 87f52bca 72.25M (0x4840000)
handle 67f777be 46.63M (0x2ea0000)
handle 67f7779a 2.00M (0x200000)
handle 47f77752 1.25M (0x13f000)
[...]
E:\WM6\itsutilsbin-20088313> pdocread.exe -w -h 0x47f77752 -b 0x800 0 0x13f000 Part00.raw
CopyTFFSToFile(0x0, 0x13f000, Part00.raw)
E:\WM6\itsutilsbin-20088313> pdocread.exe -w -h 0x67f7779a -b 0x800 0 0x200000 Part01.raw
CopyTFFSToFile(0x0, 0x200000, Part01.raw)
E:\WM6\itsutilsbin-20088313> pdocread.exe -w -h 0x67f777be -b 0x800 0 0x2ea0000 Part02.raw
CopyTFFSToFile(0x0, 0x2ea0000, Part02.raw)
E:\WM6\itsutilsbin-20088313> pdocread.exe -w -h 0x87f52bca -b 0x800 0 0x4840000 Part03.raw
CopyTFFSToFile(0x0, 0x4840000, Part03.raw)
This output 4 .raw files with what seemed to be the correct sizes. I opened one of them in a hex editor to ensure that it was not just an empty file. It wasn't so I continued my search.
Now I should be able to combine these files to make a ROM Image.
But what I have run across is I have to find a OS.nb file that is larger than my original Part02.raw file. This is where I am stuck. All the posts I have read say to extract this from an original ROM file. Well my device as far as I know is the first one of its kind to get dumped. so no larger original to extract from.
The way I think I understand it the OS.nb file is an operating system container. This leads me to believe that the container is generic and not specific to my Phone. But I am not taking any chances. e.g. this post. Is this the case? if so what do I do now? Can I extract the OS.nb from one of my .raw files and hope I do not exceed the size limitation?
If so how do I extract the OS.nb?
Furthermore all threads I have found have outlined a Kitchen (tools package) specific to there phones. would one of these work ok for my purposes? I have tried one of these and it asks you which model you are using and spits default values specific to that devices parameters. obviously my system will not fall into one of these categories but the underlying tools may be useful. I am hoping that one of these will work and I will just have to do it the manual way. If someone would point me in the right direction to which one to use and perhaps some instructions for doing so I would greatly appreciate it.
First things first however, to combine my .raw files. Any light on my OS.nb dilemma would be great.
Thanks again for reading
Hantel Q5 = Elf clone
I cannot resolve the OS.nb file dilemma but will keep reading around. What I read so far on xda-developers is that it has been proof positive verified the the Q5 has identical hardware with the HTC Touch (GSM version), also known as HTC Elf. Reading around about the Elf, there is an Elf upgrading thread, probably you are aware of it:
http://forum.xda-developers.com/forumdisplay.php?f=374
Maybe those folks know more. Trying to flash the Hantel Q5 using the "standard" method (using the HTC RUU = ROM Upgrade Utility) doesn't go anywhere: once the RUU starts updating, ActiveSynch shuts down and RUU throws a 260 error (cannot connect). Lots of good Elf ROMs out there but out of reach for Hantel, for now ...
What you did so far is *good* work - maybe it is only a matter of persistence ...
This was posted in another thread, but alas, nobody replied. Hopefully somebody here can help me.
i'm trying to dump the ROM from my Blackstone. I've got the 4 raw files, but i'm kinda confused now, since all the kitchen tutorials only mention the first two files. Seeing the sizes of the files, it makes me think - the first two files are only about 8 megs, and the other two are huge. What is taht about? Why did we make the last two files and when do we get to use them?
Also, another question, the ROM on my Blackstone comes with Sunnysoft Interwrite preinstallled - is it possible to extract it's cab from dumped rom?
Thanx!
EDIT: Whooops, possible problem here:
I was dumping ROM according to this
CMD outputs info that's similar to the one in the guide
Code:
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part00 -t
real nr of sectors: 1598 - 3.12Mbyte, 0x31f000
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part01 -t
real nr of sectors: 2176 - 4.25Mbyte, 0x440000
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part02 -t
real nr of sectors: 64768 - 126.50Mbyte, 0x7e80000
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part03 -t
real nr of sectors: 166016 - 324.25Mbyte, 0x14440000
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part00 0 0x31f000 Part00.raw
CopyTFFSToFile(0x0, 0x31f000, Part00.raw)
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part01 0 0x440000 Part01.raw
CopyTFFSToFile(0x0, 0x440000, Part01.raw)
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part02 0 0x7e80000 Part02.raw
CopyTFFSToFile(0x0, 0x7e80000, Part02.raw)
[C:\itsutils]pdocread -w -d FLASHDR -b 0x800 -p Part03 0 0x1440000 Part03.raw
CopyTFFSToFile(0x0, 0x1440000, Part03.raw)
But the generated files are of different sizes:
Part00.raw 3,12 MB (3.272.704 bytes)
Part01.raw 4,25 MB (4.456.448 bytes)
Part02.raw 126 MB (132.644.864 bytes)
Part03.raw 20,2 MB (21.233.664 bytes)
WTF? Is this ok?
I used RUU_signed.nbh from Duttys HD 2.6 Xtreme rom.
And kitchen gives me a "RecMode.exe has encountered an error and needs to close...." error after this:
Code:
Please wait for this script to finish after you see "Done!".
Don't close it, but press enter to continue!
------------------------------------------------------------
NBSplit 2.1rc2
Using data chunk size = 0x800 and extra chunk size = 0x8
on file OS.NB
Done.
ImgfsFromNb 2.1rc2
Sector size is 0x800 bytes
ImgFs partition starts at 0x00840000 and ends at 0x079a0000
Dumping IMGFS at offset 0x00840000 (size 0x07160000)
Done!
And the same thing happened even in a virtual xp machine - clean machine, .net 3.5, sp3 and all the updates, which leads me to believe that ROM dump wasn't succesful. Any ideas?
Honestly, not one answer? Just a hint if i'm doing it right or wrong?
How to pack tccutils.
Compiling applications needed:
based on debian linux: sudo apt-get install gcc libssl-dev git
Code:
[B][SIZE=4]Compiling the tools[/SIZE][/B]
$ mkdir rom
$ cd rom
$ git clone https://github.com/naobsd/tccutils.git
$ cd tccutils/
$ cc -o tccpack tccpack.c
$ cc -o tccunpack tccunpack.c
$ cd ../
$ git clone -b ics-telechips-naobsd https://github.com/naobsd/cm_system_core.git
$ cd cm_system_core/mkbootimg/
$ cc -o mkbootimg mkbootimg.c -lcrypto
$ cc -o unpackbootimg unpackbootimg.c
$ cd ../../
$ git clone -b ics-telechips-naobsd https://github.com/naobsd/cm_external_yaffs2.git
$ cd cm_external_yaffs2/yaffs2/utils/
$ make mkyaffs2image
$ cd ../../../
$ git clone https://github.com/ehlers/unyaffs.git
$ cd unyaffs/
$ make
$ cd ../
Copy compiled binaries to somewhere you like.
Code:
[B][SIZE=4]using tools[/SIZE][/B]
[B]MTD image[/B]
$ tccunpack MTD.img
(boot.img, system.img, and recovery.img will be extracted)
$ tccpack boot.img system.img recovery.img MTD_new.img
boot.img/recovery.img
$ unpackbootimg -i boot.img
$ mkdir ramdisk
$ cd ramdisk
$ gzip -cd ../boot.img-ramdisk.gz | cpio -i
(modify files)
$ find * | cpio -o -H newc | gzip -9 > ../boot.img-ramdisk_new.gz
$ cd ../
$ mkbootimg --kernel boot.img-zImage --ramdisk boot.img-ramdisk_new.gz --cmdline `boot.img-cmdline` --base 0x`boot.img-base` --pagesize `boot.img-pagesize` -o boot_new.img
system.img
$ unyaffs -d system.img
(check page(chunk) size and spare size)
$ sudo unyaffs system.img system
$ cd system
(modify files)
$ cd ../
$ cd system
$ sudo mkyaffs2image -c (PAGESIZE, e.g. 4096(not 4)) -s (SPARESIZE, e.g. 128) . ../system_new.img
[B]Example for 4gb: sudo mkyaffs2image -c 4096 -s 128 . ../system_new.img
Example for 8gb: sudo mkyaffs2image -c 8192 -s 256 . ../system_new.img[/B]
note: i have updated some of the steps from the original post.
source: http://androtab.info/arm/telechips/customize-firmware/
This scripts below are designed to unpack Cx-01 4gb adn 8gb roms. Thank you Hairybiker for the scripts. you can update them to unpack your tcc rom.
Unpack the rom and ramdisk
ex.sh
Code:
#!/bin/bash
PATH=~/bin:$PATH
tccunpack CX1*en.rom
unpackbootimg -i boot.img
mkdir ramdisk
cd ramdisk
gunzip -cd ../boot.img-ramdisk.gz | cpio -i
cd ..
mkdir system
unyaffs -d system.img
unyaffs system.img system
RepackRom with ramdisk
mkall.sh
Code:
#!/bin/bash
PATH=~/bin:$PATH
if ( "$1" == "8") then
page=8192
step=256
else
page=4096
step=128
fi
cd system
mkyaffs2image -c $page -s $step . ../system_new.img
cd ..
cd ramdisk
find . | cpio -o -H newc | gzip -9 > ../ramdisk_new.gz
cd ..
mkbootimg --kernel boot.img-zImage --ramdisk ramdisk_new.gz --cmdline "console=null" --base 0x80000000 --pagesize $page -o boot_new.img
tccpack boot_new.img system_new.img recovery.img CX-01.v0.0.rom
Pack Rom without recompiling ramdisk
mk.sh
Code:
#!/bin/bash
PATH=~/bin:$PATH
if [ "$1" = "8" ]; then
page=8192
step=256
else
page=4096
step=128
fi
echo Page=$page Step=$step
cd system
mkyaffs2image -c $page -s $step . ../system_new.img
cd ..
tccpack boot.img system_new.img recovery.img CX-01.$1v0.0.rom
Thx, I ad this link to my telechip compile thread.