As I have posted on this thread I've dumped the ROM from my spanking new Palm Treo Pro (pt-BR).
After a (what seems) long while I found here some instructions on how to rebuild a ROM from the raw files.
Here's a complete step-by-step of what I have done in order to release this ROM:
Download the ITS Utils, although only the pdocread.exe is used.
Download the NightRaven's WM6.1 Stock ROM that will be used as a template in later steps.
Download the Rebuild ROM utilities that will be used to repack the files. The needed files are located in the ManualRebuild sub-folder.
Connect the USB cable between the computer and the Treo and get them to sync.
Run pdocread -l to list the contents of the ROM. in my case the results were:
Code:
189.50M (0xbd80000) FLASHDR
| 3.12M (0x31f000) Part00
| 3.75M (0x3c0000) Part01
| 73.38M (0x4960000) Part02
| 109.25M (0x6d40000) Part03
14.50M (0xe80000) EXT_FLA
| 14.50M (0xe80000) PART00
5.00M (0x500000) MS_FLAS
| 5.00M (0x500000) PART00
STRG handles:
handle#0 874c0ae6 5.00M (0x500000)
handle#1 66f6528a 14.50M (0xe80000)
handle#2 e7488592 109.25M (0x6d40000)
handle#3 c74aacde 73.38M (0x4960000)
handle#4 874aacba 3.75M (0x3c0000)
handle#5 e74aab0a 3.12M (0x31f000)
disk 874c0ae6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 66f6528a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk e7488592
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk c74aacde
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 874aacba
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk e74aab0a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Run pdocread -w -d FLASHDR -p Part00 -t -b 0x800 to get the exact size of the partition 00.
In my case it is:
Code:
real nr of sectors: 1598 - 3.12Mbyte, 0x31f000
Which means that the actual size of the partition 00 is 0x31f000.
Run pdocread -w -d FLASHDR -b 0x800 -p Part00 0 0x31f000 Part00.raw to dump the first partition to your hard drive.
Do the last two steps for partitions 01, 02 and 03.
From NightRaven's file, extract the RUU_Signed.nbh file.
Run NBHExtract RUU_Signed.nbh to extract the 00_OS.nb file.
Run NBSplit -data 2048 -extra 8 00_OS.nb to split the .nb file into .extra and .payload.
The Part01.raw file is (according to the tutorial I based this one) the XIP.bin that needs to be implanted on the payload.
Run ImplantXIP.exe -xip Part01.raw -payload 00_OS.nb.payload to implant the XIP into the payload.
Here's the result of mine:
Code:
Implantxip & Payload Resizer v. 1.1 by ervius!!!
BLOCKS SIZE IS: 00020000
ROM Block is : 00000800
NO ImgStart....
From IMG Value: 00340000 - NON ULDR Reducing...
....................................
Preparing payload to be resized.....
....................................
Before:
XIP.BIN Target Size: 003C0000 AdjSize: 003BFFFF
ULRD in Payload Start:00001000 Size:0001EFFF End:0001FFFF
XIP in Payload Start:00020000 Size:0031FFFF End:0033FFFF
IMG in Payload Start:00340000 Size:042FFFFF End:0463FFFF
FAT in Payload Start:04640000 Size:1877FFFF End:1CDBFFFF
After:
XIP.BIN Target Size: 003C0000 AdjSize: 003BFFFF
ULRD in Payload Start:00001000 Size:0001EFFF End:0001FFFF
XIP in Payload Start:00020000 Size:003BFFFF End:003DFFFF
IMG in Payload Start:003E0000 Size:042FFFFF End:046DFFFF
FAT in Payload Start:046E0000 Size:1877FFFF End:1CE5FFFF
Payload resized and XIP Inserted into: 00_OS.nb.payload
According to several sources the Part02.raw is the actual OS, as it can be verified by running ViewIMGFS Part02.raw, which will create a folder named Dump with all the files of the OS (IMHO I believe that IMGFS stands for IMaGe File System), along with a dump_Memorymap.txt that contains information regarding how the ViewIMGFS program read the Part02.raw file.
Run ImgfsToNb Part02.raw 00_OS.nb.payload 00_OS-new.nb.payload -bigstoragemove to implant the OS into the payload. Note that the new file has a -new suffix on the filename, it's necessary for the merge ahead.
That's the result of my run:
Code:
ImgfsToNb 2.1rc2
Using bigstorage mode
Sector size is 0x800 bytes
Writing imgfs to offset byte 0x3e0000, sector 0x7c0
Padding ImgFs from 0x4960000 bytes (0x92c0 sectors)
to 0x4960000 bytes (0x92c0 sectors)
Not conservative mode. Changing imgfsEnd from 0x46e0000 to 0x4d40000
Partition entry before:
File System: 0x25
Start Sector: 0x000007c0
Total Sectors: 0x00008600
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x1f
Last Head: 0x3f
Last Sector: 0x01
Last Track: 0x236
Partition entry after:
File System: 0x25
Start Sector: 0x000007c0
Total Sectors: 0x000092c0
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x1f
Last Head: 0x3f
Last Sector: 0x01
Last Track: 0x269
Partition entry before:
File System: 0x04
Start Sector: 0x00008dc0
Total Sectors: 0x00030f00
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x237
Last Head: 0x3f
Last Sector: 0x01
Last Track: 0x272
Partition entry after:
File System: 0x04
Start Sector: 0x00009a80
Total Sectors: 0x00030240
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x26a
Last Head: 0x3f
Last Sector: 0x01
Last Track: 0x272
ImgFs Flash Region log blocks was 0x218, now is 0x24b
Storage Flash Region log block was 0xffffffff, now is 0xffffffff,
Done!
Run NBMerge -data 2048 -extra 8 00_OS-new.nb to merge back the extra space into the .nb file.
That's the result of mine:
Code:
NBMerge 2.1rc2
Executing NBMerge.exe with data chunk size = 0x800 and extra chunk size = 0x8
on file 00_OS-new.nb
Partition 0: start sector: 0x00000002, total: 0x0000003e
first used: 0x00000002, used: 0x00000001
Partition 1: start sector: 0x00000040, total: 0x00000780
first used: 0x00000040, used: 0x0000064f
Partition 2: start sector: 0x000007c0, total: 0x000092c0
first used: 0x000007c0, used: 0x000092c0
Done.
Now come the trick part. First I've tried to use Olipro's NBHUtil to build the .nbh file and although it does have the PANT100 configuration it didn't create the .nbh file, but it did provide me with assurance -- by reading the NBHUtil.xml file -- that the Kaiser device has the same configuration of the PANT100. So I used Dark Simpson's HTC Rom Tool version 1.1.4 to build.
Run htcrt
Navigate to ROM Builder tab.
Select the Kaiser device.
Change the device name to PANT100**
Change the version to 1.65.28.25 because that's the version of this ROM.
Change the language to 0416 because that's the language of this ROM (pt-BR).
Click on the [...] button next to the OS: label, and select the 00_OS-new.nb file.
Click on the [Build!] button.
Read carefully the message boxes telling about the possible dangers of making a ROM, and click on [Yes] on the first one, [No] on the second one.
Give a meaningful name for the .nbh file like TreoPro.pt-BR.1.65.28.25.nbh
If everything went according to plan, you should have a flashable Unbranded Windows Mobile 6.1 pt-BR ready to be flashed.
I've put a small ZIP file with all the tools required to reproduce this steps, as well as the ROM file I've made.
I hope this is helpful to someone, and I plead to the cook gurus on this forum to check if I did everything right.
Now I need a brave enough person to see if the ROM is OK because I admit I'm too scared to try it myself and brick my phone.
-----
Palm Treo Pro Rebuild ROM Utilities (zipped)
Palm Treo Pro pt-BR 1.65.28.25 ROM File (zipped)
hi man i flash my pro with u rom and work perfet!! thks man ;D
waltercell said:
hi man i flash my pro with u rom and work perfet!! thks man ;D
Click to expand...
Click to collapse
Thanks... I really appreciate!
new rom
Hi I am downnloading now. Will let you know how I get on Cheers
what's the benefit of this process being done?
Thanks. I used the info to build the stock ROM in Spanish.
Man, i would like to thank you. Since the release of the HardSPL I was studying a way to make a pt-br ROM.
So, I´ve flashed my dad´s phone with your ROM some days ago and up to now, everything is going fine with his Treo Pro.
But i have to admit that i´m like that ==>
I just read this part of your post today: "Now I need a brave enough person to see if the ROM is OK because I admit I'm too scared to try it myself and brick my phone."
sentencedbr said:
Man, i would like to thank you. Since the release of the HardSPL I was studying a way to make a pt-br ROM.
So, I´ve flashed my dad´s phone with your ROM some days ago and up to now, everything is going fine with his Treo Pro.
But i have to admit that i´m like that ==>
I just read this part of your post today: "Now I need a brave enough person to see if the ROM is OK because I admit I'm too scared to try it myself and brick my phone."
Click to expand...
Click to collapse
Valeu!!
Eu fiz isso antes de qualquer alteração no meu Treo pra ter um backup caso alguma coisa desse errado. Eu queria uma ROM em inglês, já que todo meu sistema em casa é em inglês, porque eu trabalho com desenvolvimento de sistemas e as coisas tendem a sair primeiro em inglês.
Translation for the non Portuguese speakers:
Thanks!!
I did that before any updates in my Treo to have a backup in case something went wrong. I wanted an English ROM, once that my whole system at home is in English, because I work as a software developer and all the good stuff comes first in English.
Man, I'll try by myself to backup my rom here. Your dump is from a unbranded Treo?
Finally, with your explanation is possible to build a 6.5 rom?
Thanks a lot!
Build 28205 PLEASE!!
i have tried several times to build my own ROM for my Treo Pro with no success... I am currently running the BigE ROM 23511 but would LOVE to have the current (28205) build!
Is there any amount of pleading I can do to persuade you (or someone) to build it? I have collected a great deal of the HTC cabs for many things (new phone canvas, ArcSoft MMS 5.2.2, etc.) which would go great in the new ROM too. Please get back to me and let me know if you can help.
Thanks in advance!
PJonDevelopment, your rom is from the unlocked and unbranded brazilian's version? If yes, you can put this in a mirror please, i'm having troubles in the download.
PJonDevelopment,
First, thanks a LOT for the rom, great to use a native language on the phone.
Nevertheless, I'd like to ask, thinking about develoiping a 6.5 pt-BR ROM? I've been trying the 6.5 ROMs, and there are some nice improvements there I'd like to have, but keeping the portuguese basis...
I'm willing to try any ROMs you may want to test, if you give it a shot.
Best regards,
Roger.
rgkamei said:
PJonDevelopment,
Nevertheless, I'd like to ask, thinking about develoiping a 6.5 pt-BR ROM? I've been trying the 6.5 ROMs, and there are some nice improvements there I'd like to have, but keeping the portuguese basis...
I'm willing to try any ROMs you may want to test, if you give it a shot.
Best regards,
Roger.
Click to expand...
Click to collapse
Hey, it's a good idea! I'll find the way to put portuguese in a 6.5 rom. If someone wants to help I'll be grateful
i like your tutorial on how to dump and rebuild your rom but could you tell me where you found out your rom version and language number thanks
DeveuS said:
i have tried several times to build my own ROM for my Treo Pro with no success... I am currently running the BigE ROM 23511 but would LOVE to have the current (28205) build!
Is there any amount of pleading I can do to persuade you (or someone) to build it? I have collected a great deal of the HTC cabs for many things (new phone canvas, ArcSoft MMS 5.2.2, etc.) which would go great in the new ROM too. Please get back to me and let me know if you can help.
Thanks in advance!
Click to expand...
Click to collapse
Deveu.. i'm currently running Zevot's 23511-V1.2 on my sprint's treo pro, and it's working great. Could u plz tell me why u prefer the 28205 build, and since u r saying it's current.. why can't u have it? Am I missing something!
Thnx!!
Hi guys. Today I cooked a 21884 build and it's working fine on my treo. It's in english yet, next step is to port this to another language, like portuguese. Till now no have success in porting the building process generates a lot of errors that I don't know the origins, but still trying.
I have a doubt with step 7 and 8 in the above mentioned instructions...
7. Run pdocread -w -d FLASHDR -b 0x800 -p Part00 0 0x31f000 Part00.raw to dump the
first partition to your hard drive.
8. Do the last two steps for partitions 01, 02 and 03.
For Part00.raw we have set the Start as 0 and end as 0x31f000, should we use "0" for even Part 01,02 and 03 ?
PJonDevelopment said:
As I have posted on this thread I've dumped the ROM from my spanking new Palm Treo Pro (pt-BR).
Click to expand...
Click to collapse
I can't get htcrt.exe to load any devices in the "build tab"...looks like the configuration file is missing ?
am I missing anything ?
Some confusion....
jaypro said:
Deveu.. i'm currently running Zevot's 23511-V1.2 on my sprint's treo pro, and it's working great. Could u plz tell me why u prefer the 28205 build, and since u r saying it's current.. why can't u have it? Am I missing something!
Thnx!!
Click to expand...
Click to collapse
I think the was some confusion as to which build I am running... At the time of my post, I was running the BigE ROM 23511... since then I have flashed up to the BigE ROM 23518... The improvements are few, but ok. mostly, The BigE change was in the software which was included in the build (namely the upgrade of Office Mobile 2010, Screen Lock, addition of versions of telenav, sprint navigation and a few others.
To tell you the truth, I think the previous build I was running (23511) was more STABLE, but I DO like the newer software.
What I was referring to was the AVAILABILITY of the 28205 build package but that nobody seems to have done ANYTHING with it... The 28205 rollup package was posted by Da_G quite a while ago. As of yet I have still seen anyone even attempt anything close to the 28205 build... still waiting and searching!
is there a way to rebuild the rom with all four .raw files thanks for a great tutorial
Related
This is the procedure to convert the dumped ROM into NBH "flashable" file. I take no responsability in any damage on your device. If you're not sure what you're doing, take time to learn some basics from wiki.
Well, i manage to reconstruct the spanish dumped rom from my Kaiser. This thread is about how to reconstruct a dumped Kaiser ROM, to have the original ROM that cames with your Kaiser, so you can revert to origin.
1. First of all is to Dump the ROM from your device. For this you only need to go to Pof post here and follow the instructions. After dumping the ROM you'll have 4 RAW files. Take apart in one folder the Part01.raw that contains the XIP and Part02.RAW that contains the IMGFS, both needed for the reconstruction process.
2. Download the WWE BaseROM to use in the reconstruction process here http://rapidshare.com/files/5781641...dio_sign_22.45.88.07_1.27.12.11_Ship.rar.html or http://rapidshare.com/files/1205992....5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
3. Download the modified version by Alex of Kaiser Kitchen here, that allows to reconstruct the ROM from the dump. The Kaiser Kitchen allows to cook a ROM from a dumped one and from base NBH shipped one. You need to put the NBH file from the step before in the BaseROM folder, and put the RAW files too. Then execute the KAISERKITCHEN.CMD and choose the next options from the menu it this order:
e, b (for dumped ROM), c, b, choose BuildOS tab, Load ROM option, Choose the KaiserKitchen folder, Go > Option, Close BuildOS, in the HRT choose ROM Builder, Choose Kaiser in device list, in the System button choose the os-new.NB file from the Kaiser Kitchen folder, press the BuildROM button and save as RUU_signed.NBH
Thanks to JugglerLKR for help me and the knowledge to solve the issues into reconstructed ROMs, and Alex to make a better script...
Thanks to all the testers who make this work for me
Cheers.
List of Reconstructed ROMs (all BigStorage and only OS)
Spanish HTC 1.56.412.4
Polish HTC 1.56.118.4
Sweden HTC 1.56.413.2
Russian HTC 1.56.411.5
German TMobile 1.56.111.4
UK TMobile 1.56.110.4
Italian HTC 1.56.408.5 or Mirror thanks to udK
German HTC 1.56.407.3
Norwegian HTC 1.56.409.4
Chinesse HTC 1.56.708.3
German Vodafone1.56.162.5
German SwissCOM 1.56.166.2
Netherlands TMobile 1.56.114.4
French Orange 1.81.73.1
Italian Vodafone 1.56.165.5
UK Vodafone 1.56.161.4
UK Orange 1.81.61.2
Danish HTC 1.56.403.3
FIN HTC 1.56.414.2
PTG HTC 1.56.410.2
Croatian TMobile 1.82.119.1 (WWE)
Spanish Vodafone 1.56.164.3
Czech TMobile 1.56.113.4
Slovakia Orange WWE 1.81.68.3 (thanks to Leon.nr)
Czech O2 1.56.405.5 (other version thanks to Leon.nr)
Croatian VIPNet 1.56.405.5
Dutch Vodafone 1.56.172.3
CZech HTC 1.56.405.5
German T-Mobile Austrian Rom 1.62.112.4 with shipped radio 1.27.12.32 (Thanks to GSLEON3)
Portuguese Brazillian HTC 1.88.514.1 (thanks to Denis Costa)
Dutch HTC 1.56.404.6 (thanks to Imperium)
Spain Orange 1.85.75.1
Thanx
That was a wonderfull guide. Now I gonna dump and reconstruct my Swedish rom so I can test the new cooked roms and have my Swedish as backup
batch file for steps 4 to 7: mind the filenames!
Waiting for this explanation I kind of figured out this myself...
Great move to make a tutorial!!!
If it helps, I made two batch files (reconstruct conservative ROM from dump.bat) from step 4 to 7.
All you need is to have an 'original' OS.nb (named Windows.nb in your tutorial) and the Part02.raw in the same directory as this batch file, along with all the programs described in step 1 to 3.
usage:
bigstorage 03_OS.nb Part02.raw
or
conservative 03_OS.nb Part02.raw
It performs the described steps and deletes the files you don't need for the ROM reconstruction.
Note:
I don't take any responsibility for any outcome and consequenses. Make sure you know what you are doing!
All credits go to the makers of the programs needed...
EDIT:
REMOVED THE ATTACHMENT...
NO USE FOR IT WHEN WE CAN USE THE KITCHEN!
By the way...
This should definitely be a sticky!
rvdgeer said:
Waiting for this explanation I kind of figured out this myself...
Great move to make a tutorial!!!
If it helps, I made a batch file (reconstruct conservative ROM from dump.bat) from step 4 to 7.
All you need is to have the 'original' 03_OS.nb (named Windows.nb in your tutorial) and the Part02.raw in the same directory as this batch file, along with all the programs described in step 1 to 3.
Click to expand...
Click to collapse
Thanks for your contribution
I noticed something...
When I flash back my reconstructed ROM I'm missing some icons in settings, for example 'device information'...
Did you notice this too?
Anyone with the dutch T-mobile Dump?
hellejoep said:
Anyone with the dutch T-mobile Dump?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=1582642&postcount=29
Works Fine
Hello,
I am a newbie here. First I flashed my German TMobile vario III with original HTC rom and found that original HTC rom is somewhat sluggish in performance as comapred to the HTC rom.
I checked this step by step way of building the rom and it works just fine. Great learning experience. Thanks to Pof, Tadzio and yourself for the explanation.
Regards
vijavij said:
Hello,
I am a newbie here. First I flashed my German TMobile vario III with original HTC rom and found that original HTC rom is somewhat sluggish in performance as comapred to the HTC rom.
I checked this step by step way of building the rom and it works just fine. Great learning experience. Thanks to Pof, Tadzio and yourself for the explanation.
Regards
Click to expand...
Click to collapse
Glad to hear helps you...
I add a link to this thread in the Wiki for quick finding...
EDIT: If you guys want, you can upload your reconstructed ROMs to rapidshare or any other site, and i mantain a list of reconstructed ROMs in the first page. This can be ussefull for ppl looking differents languaje ROMs.
Send me a PM if you don't know how to upload or any other issue.
I have the follow error when work with CHT part02.raw (imgfs.bin here)
Any hint?
C:\wm6\ppc\test2>imgfstonb imgfs.bin 03_OS.org.nb.payload 03_OS.new.nb.payload -conservative
ImgfsToNb 2.1RC1
Using conservative mode
Sector size is 0x800 bytes
Writing imgfs to offset byte 0x6e0000, sector 0xdc0
Padding ImgFs from 0x4690000 bytes (0x8d20 sectors)
to 0x46a0000 bytes (0x8d40 sectors)
Conservative/move mode: imgfs partition overflow! Aborting!
available sectors: 0x8c00, needed sectors: 0x8d40
No problem in -bigstorage mode
C:\wm6\ppc\test2>imgfstonb imgfs.bin 03_OS.org.nb.payload 03_OS.new.nb.payload -bigstorage
ImgfsToNb 2.1RC1
Using bigstorage mode
Sector size is 0x800 bytes
Writing imgfs to offset byte 0x6e0000, sector 0xdc0
Padding ImgFs from 0x4690000 bytes (0x8d20 sectors)
to 0x46a0000 bytes (0x8d40 sectors)
Not conservative/move mode. Changing imgfsEnd from 0x4ce0000 to 0x4d80000
...
...
ImgFs Flash Region log blocks was 0x232, now is 0x237
Storage Flash Region log block was 0xffffffff, now is 0xffffffff,
Done!
kfluk said:
I have the follow error when work with CHT part02.raw (imgfs.bin here)
Any hint?
C:\wm6\ppc\test2>imgfstonb imgfs.bin 03_OS.org.nb.payload 03_OS.new.nb.payload -conservative
ImgfsToNb 2.1RC1
Using conservative mode
Sector size is 0x800 bytes
Writing imgfs to offset byte 0x6e0000, sector 0xdc0
Padding ImgFs from 0x4690000 bytes (0x8d20 sectors)
to 0x46a0000 bytes (0x8d40 sectors)
Conservative/move mode: imgfs partition overflow! Aborting!
available sectors: 0x8c00, needed sectors: 0x8d40
No problem in -bigstorage mode
C:\wm6\ppc\test2>imgfstonb imgfs.bin 03_OS.org.nb.payload 03_OS.new.nb.payload -bigstorage
ImgfsToNb 2.1RC1
Using bigstorage mode
Sector size is 0x800 bytes
Writing imgfs to offset byte 0x6e0000, sector 0xdc0
Padding ImgFs from 0x4690000 bytes (0x8d20 sectors)
to 0x46a0000 bytes (0x8d40 sectors)
Not conservative/move mode. Changing imgfsEnd from 0x4ce0000 to 0x4d80000
...
...
ImgFs Flash Region log blocks was 0x232, now is 0x237
Storage Flash Region log block was 0xffffffff, now is 0xffffffff,
Done!
Click to expand...
Click to collapse
For me sounds like a bad dumping making imgfstonb bad calculating the lenght of imgfs.... can you repeat the dump process and attach the output yo see how goes?
And don't try to flash the result of -bigstorage cause don't work. To work you need to use -bigstoragemove instead of -bigstorage to get the result working.
Thanks for advise. Try to dump the raw ROM now. Post result later.
btw, I don't find -bigstoragemove in imgfs 2 rc1 readme.txt.
Hidden parameter?
ROM re-construction still fail. I post what I did for the ROM re-construction here. btw, my ROM is CHT unlock from HTC.
=================================
C:\wm6\ppc\org_rom>pdocread.exe -l
210.63M (0xd2a0000) FLASHDR
| 3.12M (0x31f000) Part00
| 4.38M (0x460000) Part01
| 73.38M (0x4960000) Part02
| 129.75M (0x81c0000) Part03
3.80G (0xf2e80000) DSK1:
| 3.79G (0xf2a80000) Part00
STRG handles:
handle 85a97436 3.79G (0xf2a80000)
handle 47476c3e129.75M (0x81c0000)
handle 0748310a 73.38M (0x4960000)
handle 474830e6 4.38M (0x460000)
handle a74b1f0e 3.12M (0x31f000)
disk 85a97436
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 47476c3e
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 0748310a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 474830e6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk a74b1f0e
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=====================================================
pdocread -w -d FLASHDR -b 0x800 -p Part00 0 0x31f000 Part00.raw
pdocread -w -d FLASHDR -b 0x800 -p Part01 0 0x460000 Part01.raw
pdocread -w -d FLASHDR -b 0x800 -p Part02 0 0x4960000 Part02.raw
pdocread -w -d FLASHDR -b 0x800 -p Part03 0 0x81c0000 Part03.raw
=====================================================
copy part02.raw C:\wm6\ppc\org_rom_test1
=====================================================
C:\wm6\ppc\org_rom_test1>dir
Volume in drive C is OS
Volume Serial Number is 34EC-33D3
Directory of C:\wm6\ppc\org_rom_test1
17/10/2007 22:23 <DIR> .
17/10/2007 22:23 <DIR> ..
17/10/2007 22:14 76,939,264 Part02.raw
28/08/2007 21:11 99,219,775 RUU_signed.nbh
=====================================================
C:\wm6\ppc\org_rom_test1>nbhextract RUU_signed.nbh
=== NBHextract v1.0
=== Extract contents from HTC NBH files
=== (c)2007 xda-developers.com
=== by: pof & TheBlasphemer based on itsme perl scripts
Device: KAIS13000
CID: HTC__001
Version: 1.56.405.5
Language: USA
Extracting: 00_Unknown.nb
Extracting: 01_SPL.nb
Extracting: 02_MainSplash.nb
Encoding: 02_MainSplash.bmp
Extracting: 03_OS.nb
=====================================================
C:\wm6\ppc\org_rom_test1>nbsplit -kaiser 03_OS.nb
NBSplit 2.1RC1
Using data chunk size = 0x800 and extra chunk size = 0x8
on file 03_OS.nb
Done.
=====================================================
C:\wm6\ppc\org_rom_test1>ren Part02.raw imgfs.bin
=====================================================
C:\wm6\ppc\org_rom_test1>imgfstonb imgfs.bin 03_OS.nb.payload 03_OS-new.nb.payload -conservative
ImgfsToNb 2.1RC1
Using conservative mode
Sector size is 0x800 bytes
Writing imgfs to offset byte 0x6e0000, sector 0xdc0
Padding ImgFs from 0x4960000 bytes (0x92c0 sectors)
to 0x4960000 bytes (0x92c0 sectors)
Conservative/move mode: imgfs partition overflow! Aborting!
available sectors: 0x8c00, needed sectors: 0x92c0
=====================================================
kfluk said:
Thanks for advise. Try to dump the raw ROM now. Post result later.
btw, I don't find -bigstoragemove in imgfs 2 rc1 readme.txt.
Hidden parameter?
Click to expand...
Click to collapse
Glad to help...
Really tadzio tools are in Release Candidate, means not finished yet, so this parameters are part of the "testing" phase to get the tools working for Kaiser.
Tadzio makes a great effrot and work on the new version.
kfluk said:
ROM re-construction still fail. I post what I did for the ROM re-construction here. btw, my ROM is CHT unlock from HTC.
Sector size is 0x800 bytes
Writing imgfs to offset byte 0x6e0000, sector 0xdc0
Padding ImgFs from 0x4960000 bytes (0x92c0 sectors)
to 0x4960000 bytes (0x92c0 sectors)
Conservative/move mode: imgfs partition overflow! Aborting!
available sectors: 0x8c00, needed sectors: 0x92c0
=====================================================
Click to expand...
Click to collapse
Well, seems the part02.raw have a problem. Have you tried to dump the part02.raw? do executing imgfstodump imgfs.bin
Take a look at the output of the command and look for an error. If the dump process goes well, then try to dump back the dump folder with imgfsfromdump imgfs-in.bin imgfs-new.bin (the imgfs-in.bin is extracted from origin Windows.nb.payload with imgfsfromnb windows.nb.payload).
The result of this process is a new imgfs-new.bin to use with imgfstonb.exe command.
Say me if this helps you...
I dump again the Part02.raw from kaiser.
After rename Part02.raw to imgfs.bin
I run imgfstodump imgfs.bin
Dump goes well. At least the command complete without problem.
imgfsfromdump fail if do it immediately after dump.
C:\wm6\ppc\org_rom_test1>imgfsfromdump 03_OS.nb.payload imgfs-new.bin
ImgfsFromDump 2.1RC1
Compression DLL does not support compression type ''!
The only different is I extract OS.nb from "RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship".
i.e. full procedure.
1. Get part02.raw from device and rename to imgfs.bin
2. NBHextract RUU_signed.nbh
3. NBSplit -kaiser 03_OS.nb (result two file 03_OS.nb.payload and 03_OS.nb.extra)
4. imgfstodump imgfs.bin (no error)
5. imgfsfromdump 03_OS.nb.payload imgfs-new.bin (error)
kfluk said:
I dump again the Part02.raw from kaiser.
After rename Part02.raw to imgfs.bin
I run imgfstodump imgfs.bin
Dump goes well. At least the command complete without problem.
imgfsfromdump fail if do it immediately after dump.
C:\wm6\ppc\org_rom_test1>imgfsfromdump 03_OS.nb.payload imgfs-new.bin
ImgfsFromDump 2.1RC1
Compression DLL does not support compression type ''!
The only different is I extract OS.nb from "RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship".
i.e. full procedure.
1. Get part02.raw from device and rename to imgfs.bin
2. NBHextract RUU_signed.nbh
3. NBSplit -kaiser 03_OS.nb (result two file 03_OS.nb.payload and 03_OS.nb.extra)
4. imgfstodump imgfs.bin (no error)
5. imgfsfromdump 03_OS.nb.payload imgfs-new.bin (error)
Click to expand...
Click to collapse
This is not valid command "C:\wm6\ppc\org_rom_test1>imgfsfromdump 03_OS.nb.payload imgfs-new.bin"... cause you need to extract the imgfs.bin from the 03_OS.nb, and then use like imgfs-in.bin. Note that the imgfs.bin is inside the 03_os.nb.payload.
The imgfsfromdump commmand takes the dump folder and makes a new imgfs named imgfs-new.bin using imgfs-in.bin to take infor about headers...
Te correct command is imgfsfromdump imgfs-in.bin imgfs-new.bin.
If you want, upload the par02.raw and send me the link. I'll try to repack for you.
Cheers.
jcespi2005 said:
This is not valid command "C:\wm6\ppc\org_rom_test1>imgfsfromdump 03_OS.nb.payload imgfs-new.bin"... cause you need to extract the imgfs.bin from the 03_OS.nb, and then use like imgfs-in.bin. Note that the imgfs.bin is inside the 03_os.nb.payload.
The imgfsfromdump commmand takes the dump folder and makes a new imgfs named imgfs-new.bin using imgfs-in.bin to take infor about headers...
Te correct command is imgfsfromdump imgfs-in.bin imgfs-new.bin.
If you want, upload the par02.raw and send me the link. I'll try to repack for you.
Cheers.
Click to expand...
Click to collapse
Hi jcespi2005,
How could I extract the imgfs.bin from the 03_OS.nb?
I am uploading part02.raw to rapidshare, speed is very slow. Will post you the link.
thanks for your patient.
kfluk
Evening all,
I also have a brand new Orange(UK) branded TyTnII. I have dumped the ROM following the guide http://forum.xda-developers.com/showthread.php?t=334680, however the partition table looks a little different:
C:\Users\***\Desktop\ITS>pdocread -l
210.38M (0xd260000) FLASHDR
| 3.12M (0x31f000) Part00
| 3.50M (0x380000) Part01
| 69.63M (0x45a0000) Part02
| 134.13M (0x8620000) Part03
STRG handles:
handle e7489c1a134.13M (0x8620000)
handle 074970e6 69.63M (0x45a0000)
handle e74b0fda 3.50M (0x380000)
handle e74b0eee 3.12M (0x31f000)
disk e7489c1a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 074970e6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk e74b0fda
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk e74b0eee
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
which meant that the dump commands were:
pdocread -w -d FLASHDR -b 0x800 -p Part00 0 0x31f000 Part00.raw
pdocread -w -d FLASHDR -b 0x800 -p Part01 0 0x380000 Part01.raw
pdocread -w -d FLASHDR -b 0x800 -p Part02 0 0x45a0000 Part02.raw
pdocread -w -d FLASHDR -b 0x800 -p Part03 0 0x8620000 Part03.raw
The reconstruction was then as per http://forum.xda-developers.com/showthread.php?t=337066,
using the Windows.nb from http://rapidshare.com/files/65254405/WindowsFRA1.56.406.5.rar
The ROM has been rebuilt with Dark Simpson ROM tool, 7zip'ped and is availiable :
http://rapidshare.com/files/66123403/1.81.61.2.WWE.Orange.UK.7z.html
If anyone wants the RAW files, please let me know and I will zip and up those too. Usual disclaimers about me not being responsible for your bricks apply.
Nicely done......
In your original post about this ROM, I asked if you could post the OS and Build numbers, but you never did (and still haven't!)
Go to Start | Settings | System tab | About - make a note of the line that starts "CE OS......" and post it back here please
Click to expand...
Click to collapse
This is the missing piece of the puzzle so to speak....when this information is available, then the cooks will know if the core of the O/S has been updated etc. before they waste time cooking with it.
Thanks in advance,
Mark.
Mark Crouch said:
Nicely done......
In your original post about this ROM, I asked if you could post the OS and Build numbers, but you never did (and still haven't!)
This is the missing piece of the puzzle so to speak....when this information is available, then the cooks will know if the core of the O/S has been updated etc. before they waste time cooking with it.
Thanks in advance,
Mark.
Click to expand...
Click to collapse
its an old os and build CE OS 5.2.1620 (Build 18125.0.4.2)
^^ yep, what he said!
Thanks Dutty/Rik - glad we've got that cleared up
Mark.
so now what? it is a lie? it doesnt looks like a big update from 1.56 ?
rom
the rom that has been uploaded is that the raw files or a reconstructed rom
many thanks
steven
this was my reconstruction from the raw dump
orange
so if i put one of the other roms on my orange tytn ii could i flash your reconstruction for warranty purposes
do i need any tools to flash the rom
many thanks
steven
Hi Steven,
I hope so! It's the reason I dumped and reconstructed this ROM - I have subsequently flashed the HTC shipped ROM to my Kaiser, and its running so much faster.
Although I have tested re-flashing this ROM to take me back to an Orange branding, I give no guarantees that it will return your Kaiser back to how it was when you bought it, or that it won't turn your Kaiser into the most expensive paper weight you ever bought.
As with everything on XDA-devs, its entirely at your own risk (but i'm glad I gave it a go!)
sirsyco has posted a guide http://forum.xda-developers.com/showthread.php?t=335568 on reverting back to the original ROM, while using POF's Hard-SPL http://forum.xda-developers.com/showthread.php?t=334679 and CustomRRU http://forum.xda-developers.com/showthread.php?t=334890 should provide everything you need to flash to the first HTC shipped ROM, which you will find links to in various places in this forum.
Please note that I only flashed the HTC OS, not the radio stack or the splashscreen.
I am afraid I am not going to provide a step-by-step - all of the guides linked above provide the details to do what you want to do, and I am afraid I am of the opinion that if you don't get what is being described in those tut's, you really should not be dumping and flashing ROM's yourself.
No offence intended, but im not going to lead you out of your depth - I don't want anyone to fry their beloved Kaiser on my instructions!
orange rom
hi rik
no offence taken
can i just ask you when you went from orange to htc did you hard spl then just run the htc shipped rom
how did you just instal the os and not the spl or radio stack
did you notice a difference with the htc rom
many thanks
steven
Rik
Can you tell me...when you flashed the OS only, did you get the SIMLOCK problem?
I think that was the mistake I did... I flashed the whole thing rather than the OS alone... i wasnt aware of this complication in changing other bit besides the OS...
My phone (originally Orange ROM) is still locked (24hrs now) but its usable if you put it on flight mode.. it seems to be faster..menus, keyboard opening response, applcation launch etc.. not sure how much having the phone part switched off effects the performance...
bigchemist said:
I think that was the mistake I did... I flashed the whole thing rather than the OS alone... i wasnt aware of this complication in changing other bit besides the OS...
My phone (originally Orange ROM) is still locked (24hrs now) but its usable if you put it on flight mode.. it seems to be faster..menus, keyboard opening response, applcation launch etc.. not sure how much having the phone part switched off effects the performance...
Click to expand...
Click to collapse
Could possibly be
Could you share radio or raw from this ROM?
Thanks.
Need the newest build for flash, anyone here has got this one?
STILL WAITING
How do you know these builds exist?
optiquest said:
Need the newest build for flash, anyone here has got this one?
Click to expand...
Click to collapse
Thank you for the answer
keep cool my friend
you gave him only 18 minutes to reply...
this is no chat, so it is quite possible that it will need some time before he realizes that a reply is needed.
cheers
Haha... I was only teasing a little
But I'm very curious about these new builds
ninja.rogue said:
keep cool my friend
you gave him only 18 minutes to reply...
this is no chat, so it is quite possible that it will need some time before he realizes that a reply is needed.
cheers
Click to expand...
Click to collapse
How much minutes now?
pffff....
Yep,
I'm still waithing to...
Build date is 28/03/08?
It's out there... org wm6.1 from HTC but where to grab.....
Problem with dumping
This may not be the place to post this but The how to dump thread is unfrequently visited since I have posted this yesterday and no one has posted anything after. I think whoever reads this thread can help me.
Flame suit on but here goes
Please help me... Anyone... I'm getting Access is denied the bottom line.
-- Is it working correctly or what? IDK. Please help!! Thanks in advance
C:\>pdocread -l
210.25M (0xd240000) FLASHDR
| 3.12M (0x31f000) Part00
| 3.50M (0x380000) Part01
| 79.13M (0x4f20000) Part02
| 124.50M (0x7c80000) Part03
STRG handles:
handle c7481c1a124.50M (0x7c80000)
handle 2748f0e6 79.13M (0x4f20000)
handle 274b0fda 3.50M (0x380000)
handle 074b0eee 3.12M (0x31f000)
disk c7481c1a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 2748f0e6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 274b0fda
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 074b0eee
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C:\>pdocread -w -d FLASHDR -b 0x800 -p Part00 0 0x31f000 Part00.raw
CopyTFFSToFile(0x0, 0x31f000, Part00.raw)
ERROR: Unable to open host/destination file - Access is Denied
Laurentius26 said:
How do you know these builds exist?
Click to expand...
Click to collapse
what you think ? yes, there had 19400 build , where to find it , maybe you know that :cool
mwang said:
what you think ? yes, there had 19400 build , where to find it , maybe you know that :cool
Click to expand...
Click to collapse
I can't see that image
hi
here´s a link to 19400 kaiser rom in chs: http://rapidshare.com/files/109028458/Kaiser_DFT_V2_19400_CHS_Release.rar, but i can´t dump it to change the mui files, it´s from darkforces team.
cheers.
ark666 said:
hi
here´s a link to 19400 kaiser rom in chs: http://rapidshare.com/files/109028458/Kaiser_DFT_V2_19400_CHS_Release.rar, but i can´t dump it to change the mui files, it´s from darkforces team.
cheers.
Click to expand...
Click to collapse
Nice job my friend. Let's see if I can round up somebody who can dump this to change it up.
While i´m trying to dump it with kaiserkitchen, it gives me an error with RecMod.exe.
cheers
I just dumped the rom and it appears it is not an official ROM. I am assuming this as PCMKeyboard is in the SYS files already!!!!!
Is this a joke
Haven't really worked alot with other languages, but I'm seeing alot of errors while dumping the contents of the imgfs in the latter half of step 2a.
It's being really retarded and making modules out of all sorts of stuff, some of it being bitmaps. I'm gonna call it quits.
_Alex_ said:
Haven't really worked alot with other languages, but I'm seeing alot of errors while dumping the contents of the imgfs in the latter half of step 2a.
It's being really retarded and making modules out of all sorts of stuff, some of it being bitmaps. I'm gonna call it quits.
Click to expand...
Click to collapse
Well, thank you for trying anyways. Guess we will just have to wait for somebody to find a good source for this build.
ryncppr said:
I just dumped the rom and it appears it is not an official ROM. I am assuming this as PCMKeyboard is in the SYS files already!!!!!
Is this a joke
Click to expand...
Click to collapse
Can u share the method to dump the ROM?
Ok let me change the topic real quick where can i find the att tilt test rom 19209 dump.
correct me if i wrong.
Laurentius26 said:
How much minutes now?
pffff....
Click to expand...
Click to collapse
sorry for forgot to reply it!
Yes, 19400 released today, and the newest build i know is 1955x..
hope someday we can use it soon.
Very soon I will receive a new phone (TyTnII) and I would want a full backup of my phone. The new phone will be flashed with my current phone and thus containing all my current settings and software. I think the only way to do this, is by dumping (cooking) and restoring (flashing) a ROM of my current phone. -Maybe I could be wrong-
Is there a "dumping ROM" -thread for dummies? In each and every thread there are parts of the solution, but nowhere a step-by-step description is to be found. In most of the threads people mention the programming code they use to dump a ROM, is a user-friendly user interface (GUI?) for cooking and flashing already available? Btw, after reading and searching on this superb site for some 3 days, I found out all I needed to know about flashing. Currently using a Dutty ROM with separately flashed RADIO. LAS, for cooking no solution seems to be at hand.
Hoping to find a solution, if you are so kind to respons, please no "use the search-section" or "read W.I.K.I. please" - been there, done that - and make sure to use all related links. Maybe this thread might become a first try to build a real "Cooking and flashing for dummies".
With kind regards,
Gert Beckers
Belgium
GertBeckers said:
Very soon I will receive a new phone (TyTnII) and I would want a full backup of my phone. The new phone will be flashed with my current phone and thus containing all my current settings and software. I think the only way to do this, is by dumping (cooking) and restoring (flashing) a ROM of my current phone. -Maybe I could be wrong-
Is there a "dumping ROM" -thread for dummies? In each and every thread there are parts of the solution, but nowhere a step-by-step description is to be found. In most of the threads people mention the programming code they use to dump a ROM, is a user-friendly user interface (GUI?) for cooking and flashing already available? Btw, after reading and searching on this superb site for some 3 days, I found out all I needed to know about flashing. Currently using a Dutty ROM with separately flashed RADIO. LAS, for cooking no solution seems to be at hand.
Hoping to find a solution, if you are so kind to respons, please no "use the search-section" or "read W.I.K.I. please" - been there, done that - and make sure to use all related links. Maybe this thread might become a first try to build a real "Cooking and flashing for dummies".
With kind regards,
Gert Beckers
Belgium
Click to expand...
Click to collapse
Are you sure you've read all the Relevant wiki pages?
This has instructions for Dumping and Reconstructing a ROM.
If you want to read these and make you own tutorial, feel free, but don't ask others to do it for you.
Kyphur says it best: http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
Ta
Dave
"IF YOU DON'T CARE ABOUT UNDERSTANDING THE JOURNEY THEN YOU PROBABLY SHOULDN'T BE HERE IN THE FIRST PLACE." is exactly what I mean with "In each and every thread there are parts of the solution". Nowhere the -part- of the solution is in clear english. Can I give you an example from your link?
How to dump a ROM :
"$ ./pdocread.exe -l
210.38M (0xd260000) FLASHDR
| 3.12M (0x31f000) Part00
| 3.50M (0x380000) Part01
| 69.38M (0x4560000) Part02
| 134.38M (0x8660000) Part03
STRG handles:
handle e7489c1a134.38M (0x8660000)
handle 474960e6 69.38M (0x4560000)
handle c74b0fda 3.50M (0x380000)
handle 074b0eee 3.12M (0x31f000)
disk e7489c1a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 474960e6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk c74b0fda
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 074b0eee
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00"
?????????????????????????????????????????????????????????????????????
Maybe some people forget that not everybody is a programmer! Seems to me something is missing here? Anyone can explain to me what the h*ll this means?
Next line:
"DUMP THEM!
Code:
pdocread -w -d FLASHDR -b 0x800 -p Part00 0 0x31f000 Part00.raw
pdocread -w -d FLASHDR -b 0x800 -p Part01 0 0x380000 Part01.raw
pdocread -w -d FLASHDR -b 0x800 -p Part02 0 0x4560000 Part02.raw
pdocread -w -d FLASHDR -b 0x800 -p Part03 0 0x8660000 Part03.raw"
And again something seems to be missing here. Maybe some people forget that not everybody is a programmer!
Anyone can explain to me what the h*ll this means?
Thus my remark:
"Hoping to find a solution, if you are so kind to respons, please no "use the search-section" or "read W.I.K.I. please" - been there, done that -" Maybe -I admid- I should have added: "Are you sure you've read all the Relevant wiki pages?" and "If you want to read these and make you own tutorial, feel free, but don't ask others to do it for you."
Good teachers are just thais hard to find. Thanks for the response anyway, but I will just keep on looking for a clear and understandable explanation and/or guideline.
kind regards,
Gert Beckers
Belgium.
GertBeckers said:
Maybe some people forget that not everybody is a programmer!
Click to expand...
Click to collapse
This is XDA-Developers and your posting in the ROM Development forum. A certain level of understanding is expected.
May I suggest you look at backup software such as Sprite or SPB Backup instead or dumping and reconstructing your ROM.
Thanks
Dave
Sprite backup works great and btw Gert,
those are command line instructions-pretty straightforward actually.
Thank you for your reply , I used "SPB Backup". I just hope this nifty little tool will also make a backup of all installed software (but I doubt it).
Btw, my new 8GB Ultra II SD SDHC Memory Card just arrived!
Sir Thanks-a-lot,
Gert Beckers
GertBeckers said:
Thank you for your reply , I used "SPB Backup". I just hope this nifty little tool will also make a backup of all installed software (but I doubt it).
Btw, my new 8GB Ultra II SD SDHC Memory Card just arrived!
Sir Thanks-a-lot,
Gert Beckers
Click to expand...
Click to collapse
Sprite does-use it all the time, not sure about SPB, haven't used it.
GertBeckers said:
Thank you for your reply , I used "SPB Backup". I just hope this nifty little tool will also make a backup of all installed software (but I doubt it).
Btw, my new 8GB Ultra II SD SDHC Memory Card just arrived!
Sir Thanks-a-lot,
Gert Beckers
Click to expand...
Click to collapse
SPB Backup 2.0 will backup your entire ROM won't it?
Dave
This is becoming less and less of a developer site and more and more of a whinning, lazy a$$, "help me do what I can't do for myself". These users aren't even willing to read and then they retort back with indignation.
By the way, DaveShaw is kind of a big deal here. He doesn't have over 1200 posts because he is too lazy to read or do some research on his own. He has been helping and developing. Show some respect or be ready to be ignored.
kimtyson said:
This is becoming less and less of a developer site and more and more of a whinning, lazy a$$, "help me do what I can't do for myself". These users aren't even willing to read and then they retort back with indignation.
By the way, DaveShaw is kind of a big deal here. He doesn't have over 1200 posts because he is too lazy to read or do some research on his own. He has been helping and developing. Show some respect or be ready to be ignored.
Click to expand...
Click to collapse
... and hot water might have been invented on this "whining-site" over and over again. Thank you for you constructive info and positive feedback.
Since everything is going downhill, and most of you are having a bad day, it might be the moment to close this topic?
Sir Grins-a-lot,
Ger Beckers
This topic shouldn't be opened.
Gert,
I'm not having a bad day.
The ROM dumping instructions are in command line format and as Dave has pointed out, all that info is available in the ROM dumping thread. Read it and try it yourself, works great to dump ROM's.
kristoff_sz said:
This topic shouldn't be opened.
Click to expand...
Click to collapse
I agree. Can we drop this, please.
When a Moderator get's on this thread should be closed.
-Question asked, advice given. End of Discussion.
Dave
hey man,
Well, I haven't tried it, but here's some easy step-by-step instructions on how to dump a ROM:
1. I just put all the necessary files in this folder:
http://www.mediafire.com/download.php?jc1xtnpqnxj
Download it and extract it to your C: drive.
2. Plug in your device
3. Open a Command Prompt and type in the following:
Code:
cd C:\
Code:
pdocread -l
This should bring output something like this:
Code:
210.38M (0xd260000) FLASHDR
| 3.12M (0x31f000) Part00
| 3.50M ([COLOR="orange]0x380000[/COLOR]) Part01
| 69.38M ([COLOR="orange"]0x4560000[/COLOR]) Part02
| 134.38M (0x8660000) Part03
STRG handles:
handle e7489c1a134.38M (0x8660000)
handle 474960e6 69.38M (0x4560000)
handle c74b0fda 3.50M (0x380000)
handle 074b0eee 3.12M (0x31f000)
disk e7489c1a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 474960e6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk c74b0fda
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 074b0eee
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Look at the orange items at the top. I've made these orange to make note that when you do this, those numbers will probably be different. So, open Notepad and copy and paste the numbers you see there. Now do this:
Code:
pdocread -w -d FLASHDR -b 0x800 -p Part01 0 [COLOR="orange"]0x380000[/COLOR] Part01.raw
NOTE: Replace the orange numbers with the first set of numbers you took down.
Do the same with this, except replace the orange numbers with the second set of numbers you took down:
Code:
pdocread -w -d FLASHDR -b 0x800 -p Part02 0 [COLOR="orange"]0x4560000[/COLOR] Part02.raw
NOTE: this line might take a while, but don't close the window until it's done.
OK, if done correctly, you should have Part01.raw and Part02.raw in your C:\ drive.
Now, download this file:
http://www.megaupload.com/?d=5NA811QP
and extract it to your C: drive
Now go to your C drive, cut Part01.raw and Part02.raw and paste them in C:\kaiserkitchen\BaseROM.
Now download this file:
http://210.64.124.194/download/TyTN II_SEA_WM6.1_Upgrade_20080602.zip
and take the RUU_signed out of it and place it in C:\kaiserkitchen\BaseROM
then go into C:\kaiserkitchen, double-click on KaiserKitchen.cmd, press e, then press b.
4. Cook the ROM.
Now cook the ROM by following the steps here:
http://wiki.xda-developers.com/index.php?pagename=Kaiser ROM Kitchen Tutorial
although, make sure you do not add any packages
You're done, hope it helps
Eric Draven,
Finally some one who understands the true meaning of a forum!
Thanks a lot for the clear and understandable explanation. I'm sure that I will finally be able to cook my own ROM, I hope that this tread might be used by plenty other seekers At least finally the title of the thread correspond with its content!
Just one last question; at the end of your reply you wrote: "although, make sure you do not add any packages" What kind of packages do you mean? Is installed software considered "packages"?
Sir Thanks-a-lot,
Gert Beckers
Belgium
Eric Draven,
Finally some one who understands the true spirit of a forum: helping others! At last the title of the thread corresponds with its content! No *****ing or wining, just helping! Respect!
I hope this final and conclusif answer might help tons of others in cooking their own ROM!
What do you mean with: "although, make sure you do not add any packages". Is any installed software considered "packages"?
Sir Thanks-a-lot,
Gert Beckers
Belgium
GertBeckers said:
Eric Draven,
Finally some one who understands the true meaning of a forum!
Thanks a lot for the clear and understandable explanation. I'm sure that I will finally be able to cook my own ROM, I hope that this tread might be used by plenty other seekers At least finally the title of the thread correspond with its content!
Just one last question; at the end of your reply you wrote: "although, make sure you do not add any packages" What kind of packages do you mean? Is installed software considered "packages"?
Sir Thanks-a-lot,
Gert Beckers
Belgium
Click to expand...
Click to collapse
Packages are the Equivelant of CABs that you use when Cooking ROMs.
i.e. You would use a new Dialer Package and Cook that into your ROM, rather than install a CAB.
When using the Kitchen, you get to pick what packages you would like.
All of this is in the ROM Cooking Wiki.
Thanks
Dave
Dave- Finally someone who understands the true spirit of a forum: helping others to help themselves.
GertB- You remain thick as a brick! And you double posted.
Oh, and though you "are sure you will finally be able to cook your own ROM" I am not as confident. You don't even understand what packages are. I suggest you stop posting and begin reading a little. Then best of luck to you. I will wait with baited breath for your excellent ROM addition to the forums.
Here is a link to the ROM KITCHEN TUTORIAL, http://forum.xda-developers.com/showthread.php?t=349895&highlight=ROM+cooking+WIKI, posted before you decided to join the party. I'd say "title of the thread correspond with its content".
kimtyson said:
GertB- You remain thick as a brick! And you double posted.
Click to expand...
Click to collapse
I believe that was a mistake, and I'm pretty sure he did not mean to bump this thread
@GertBeckers: Yes, when I say "Do not add any packages" I am talking about the software you would usually add when cooking a ROM
I would really appreciate some help associated with the below quote from a thread relating to i780 ROMs.
I along with a bunch of other Aussies would love to upgrade our Australian versions of this device to WM6.1.
Please help us!!
Originally Posted by Kostiz
G'Day All,
Just to bring this question up once more of the ROM version in my Australian released PDA i780 is DTHD1.
This version is not listed or at this stage supported under the samsung support page.
http://www.samsungmobile.com/support...untry=sg&os=xp
So if I may throw out some question to some of the xda family.
[1] Can I back up the current boot+PDA+phone ROMS of the i780 before flashing?
[2] What is the difference in this ROM version DTHD1 and is this Australian Specific because of our 2G-3G GSM networks?
[3] Is it possible to upgrade WM6 via using i780PDXIB1_Upgrader_XP or similar downloadables from the samsung support page from above?
[4] Will I need to revert to a different ROM (backwards) like i780_PDXHL2 in order to use the upgrade (move forward) and then one of these cooked ROM versions?
[5] Can I use WM6.5 or do I need to jump to WM6.1 first?
I might add that the Samsung web site under choosing country - Australia doesn't have the i780 listed (well I couldn't find it), So I assume they don't even know we have it, LOL
If you haven't guessed already, I am from Sydney Australia, Gday mate!!
So I hope someone can take the time to point me in the right direction to make some changes as the ROM performace of my current version "DTHD1" is very poor when battery drops below 50%.
I am sorry for the long thread, and digging up an old one, but I did see a fellow commrade ask a similar question with no real answer that I saw so I'm asking again in a little more detail.
PEACE
Kostiz
Click to expand...
Click to collapse
1)I don t know how but is possible to backup the pda part
2)I don t know
3)Yes but you need to modify the updater or flash the pda part extracted from the updater and then do the completely update
4)If you want you can flash cooked roms without upgrading phone and boot
5)You can use wm6.5
Thanks for the reply mate.
So it's looking like a cooked 6.5 rom might be the best option at the moment...
What are the risks associated with flashing the ROM? Is there a chance that because the version is different more common Euro/Asian versions that a cooked ROM could brick the device??
I upgraded my Treo 750 from WM5 to WM6 (cooked) and then to an official WM6 ROM and there were no dramas. I am assuming this process will be similar?
LI0NMAN said:
Thanks for the reply mate.
So it's looking like a cooked 6.5 rom might be the best option at the moment...
What are the risks associated with flashing the ROM? Is there a chance that because the version is different more common Euro/Asian versions that a cooked ROM could brick the device??
I upgraded my Treo 750 from WM5 to WM6 (cooked) and then to an official WM6 ROM and there were no dramas. I am assuming this process will be similar?
Click to expand...
Click to collapse
All the wm6.5 roms for i780 have a mouse bug (when you move the cursor a little square appears on the screen) and (i think) they are slower than wm6.1.
Someone briked his i780 but i think it was because of hardware problems.
Yes, for example if you want to upgrade boot+phone+pda to HL2 you can flash a cooked HL2(only pda), upgrade using the officially upgrader and than reflash the pda part.
Thanks again, I'll have a good read of EFN's thread there to further understand what needs to be done...
Anyone here successfully upgraded their i780 DTHD1? If so what version have you upgraded it to?
Well I gave up waiting and dove right in and updated the PDA part with i780 Heroes WM6.1 Final ROM. (was the only one I could find quickly)
Basically I took the following steps;
run Mirage Updater:
- select PDA in Mirage updater
- Select .bin file in my case i780 Heroes WM6.1 Final ROM.
- Wait until Mirage Updater finishes checking the bin file
- Press Detect.....wait
now on the phone..
- Take OUT the battery (MUST!) and then put it back
- Switch on the phone while holding the ENTER and FUNCTION buttons (ALT BUTTON)
- Wait until you see the boot msg
- Then Plug in the USB cable
- It should begin downloading automatically and once done you can disconnect your i780
- Reset & DONE!
( I found a procedure in PDF that talk about loading the russian DXHE1 ROM E1 english version first, but I didn't bother and jumped straight to this ROM )
**Now the only I problem I encountered after it booted was the align screen loop issue began!!! I didn't have this issue prior so I can only assume it has something to do with the flashing.**
The temp solution for me was I added a empty txt file on my storage card (installed in phone) labeled "welcome.not" without quotes of course
I tried an alternate solution by editing the HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH:MaxCalError vale from 7 to 20, but this didn't work.
the file on the card bypassed the alignscreen so I could finally use the ROM.
The ROM and phone is behaving far better than the OEM firmware, but as the alignment is all messed up, this new ROM is not the best of options for me until I figure out the issue with the touchscreen section. (The phone is only weeks old, so I doubt hardware failure)
One thing I forgot to do was back up my original ROM, so if any Aussies out there are thinking of flashing, could you please backup the ROM prior to flashing as I want to revert back and see if the alignment recovers.
There is a process to do this here
http://forum.xda-developers.com/showpost.php?p=2307129&postcount=15
Finally a snapshot of my phone now looks like this..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can someone pls back up the DTHD1 OEM rom as I want to try and roll back.
This link should take you to where u can do the backup dump of the rom..
http://forum.xda-developers.com/show...9&postcount=15
Backed up ROM
Hi Kostiz.
I have just backed up my rom for you below is a copy of the CMD screen and the outcomes.
Which files do you want / need?
C:\itsutil>pdocread -l
254.25M (0xfe40000) DSK1:
| 1.25M (0x13f000) Part00
| 2.88M (0x2e0000) Part01
| 84.00M (0x5400000) Part02
| 164.75M (0xa4c0000) Part03
1.90G (0x79b00000) DSK2:
| 1.90G (0x79ae1200) Part00
STRG handles:
handle#0 07664e1a 1.90G (0x79ae1200)
handle#1 677f642e 164.75M (0xa4c0000)
handle#2 e78567be 84.00M (0x5400000)
handle#3 4785679a 2.88M (0x2e0000)
handle#4 a7856752 1.25M (0x13f000)
disk 07664e1a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 677f642e
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk e78567be
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 4785679a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk a7856752
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
C:\itsutil>pdocread -w -d DSK1: -b 0x800 -p Part00 0 0x13f000 Part00.raw
CopyTFFSToFile(0x0, 0x13f000, Part00.raw)
C:\itsutil>pdocread -w -d DSK1: -b 0x800 -p Part01 0 0x2e0000 Part01.raw
CopyTFFSToFile(0x0, 0x2e0000, Part01.raw)
C:\itsutil>pdocread -w -d DSK1: -b 0x800 -p Part02 0 0x5400000 Part02.raw
CopyTFFSToFile(0x0, 0x5400000, Part02.raw)
C:\itsutil>pdocread -w -d DSK1: -b 0x800 -p Part03 0 0xa4c0000 Part03.raw
CopyTFFSToFile(0x0, 0xa4c0000, Part03.raw)
BTW : - Below are the .raw file sizes as reported by the system as you can see all is successful.
C:\itsutil>dir *.raw
Volume in drive C has no label.
Volume Serial Number is 04BA-005C
Directory of C:\itsutil
03/06/2009 14:31 0 file.raw
03/06/2009 14:34 1,306,624 Part00.raw
03/06/2009 14:38 3,014,656 Part01.raw
03/06/2009 14:38 88,080,384 Part02.raw
03/06/2009 14:50 172,752,896 Part03.raw
5 File(s) 265,154,560 bytes
Just let me know which file(s) you need and I am more than happy to upload them somewhere.
Thanks
LI0NMAN said:
I would really appreciate some help associated with the below quote from a thread relating to i780 ROMs.
I along with a bunch of other Aussies would love to upgrade our Australian versions of this device to WM6.1.
Please help us!!
Click to expand...
Click to collapse
Hi there, the version you can use should be the same found on the Heroes WM6.1 thread page.
I am using i780 from Optus here and have upgraded using this file:
i780PDXHL2_Upgrader_Vista
and after that I upgraded using i780PDXIB1_Upgrader_VISTA
Please download the SamsungModem_VISTA.zip prior running the upgrader executables.
I am not sure what OS you are using but at least you know what versions worked for me.
I am not using any custom made ROMs but I am still waiting for the developments of 6.5 by Inertiax. So, I won't be able to help you with the roll back or tips on the custom 6.1 ROM, sorry.
Installing updates/roms
http://forum.xda-developers.com/showpost.php?p=3965684&postcount=162