Are there any step for step instructions, either on a web site or in a downloadable PDF that detail how one can cook their own athena ROMs?
Such a thing would be a big help to all those that would like to try cooking their own ROMS..
I have found some instructions but they are old and are for other devices mostly running WM2003se or WM5. It would be goo to have an updated one for WM6 and the Athena.
Madhadder said:
Are there any step for step instructions, either on a web site or in a downloadable PDF that detail how one can cook their own athena ROMs?
Such a thing would be a big help to all those that would like to try cooking their own ROMS..
I have found some instructions but they are old and are for other devices mostly running WM2003se or WM5. It would be goo to have an updated one for WM6 and the Athena.
Click to expand...
Click to collapse
How about over in the Hermes forum? (Not trying to me a [email protected]$$..)
toyfreak said:
How about over in the Hermes forum? (Not trying to me a [email protected]$$..)
Click to expand...
Click to collapse
search for "rom donalds", its a guide for hermes written by myself and Bennec83 that aims to teach you the basics of cooking and give you and understanding of why and how you do things, not just do it
Nice explanation and good instructions. Is there a version that works for the Athena? I only got as far as dumping the os.nb. It must be a diifferent offset or addresses, or something with the imgfs.. it states
NBSplit 2.0 RC 2
Done.
ImgfsFromNb 2.0 RC 2
Searching for IMGFS start...
Found IMGFS at 00666668.
Dumping IMGFS at offset 00666668 (size 04666658)
Done!
ImgfsToDump 2.0 RC 2
guidBootSignature: F8 AC 2C 9D E3 D4 2B 4D BD 30 91 6E D8 4F 31 DC
dwFSVersion: 00000001
dwSectorsPerHeaderBlock: 00000001
dwRunsPerFileHeader: 00000001
dwBytesPerHeader: 00000034
dwChunksPerSector: 00000008
dwFirstHeaderBlockOffset: 00000200
dwDataBlockSize: 00001000
szCompressionType: XPR
dwFreeSectorCount: 00006494
dwHiddenSectorCount: 00000100
dwUpdateModeFlag: 00000000
Address: 00000200, dwBlockSignature: FFFFFEFE
dwNextHeaderBlock: 00000000 (size: FFFFFE00)
Header type: 00000270, Addr: 00000208
Unknown header type, FS_DATA_TABLE??
Header type: 004C006C, Addr: 0000023C
Unknown header type, FS_DATA_TABLE??
Header type: 000002A4, Addr: 00000270
Unknown header type, FS_DATA_TABLE??
Header type: 000002D8, Addr: 000002A4
Unknown header type, FS_DATA_TABLE??
Header type: 0000030C, Addr: 000002D8
Unknown header type, FS_DATA_TABLE??
Header type: 00000340, Addr: 0000030C
Unknown header type, FS_DATA_TABLE??
Header type: 00000000, Addr: 00000340
Unknown header type, FS_DATA_TABLE??
Header type: 00003608, Addr: 00000374
Unknown header type, FS_DATA_TABLE??
Header type: 00630061, Addr: 000003A8
Unknown header type, FS_DATA_TABLE??
it creates and Deletes the following files
OS.nb.payload
OS.nb.extra
imgfs.bin
it creates an empty dump_MemoryMap.txt and no dump folder.
Am i doing something wrong
ATHENA.. Not HERMES, guys.. while there maybe many simularities between the devices when cooking ROMS, some important steps are not correct for the Athena, thus the guides need to be updated.
basically the differences are:
dont use nbsplit at all and use the '-nosplit' option on all imgfs programs
Midget_1990 said:
basically the differences are:
dont use nbsplit at all and use the '-nosplit' option on all imgfs programs
Click to expand...
Click to collapse
thanks Midget_1990..That works great..
I knew you would know the answer!
guys the trinity tools dont work on athena. the tools we use for wizard and uni do. now to those that do wanna cook get ready for late nights and lots of anger. the athena's rom is partioned so the os.nb is a fixed size. if u dont overload it the rom will boot and everything will be ok. if u do then the rom wont work and ur device will not turn on. with the athena adding stuff is hit or miss. some stuff wont go in bc theres a real big file. it aint easy i can tell u that but if u want to try it go ahead.
Pawel062 said:
guys the trinity tools dont work on athena. the tools we use for wizard and uni do. now to those that do wanna cook get ready for late nights and lots of anger. the athena's rom is partioned so the os.nb is a fixed size. if u dont overload it the rom will boot and everything will be ok. if u do then the rom wont work and ur device will not turn on. with the athena adding stuff is hit or miss. some stuff wont go in bc theres a real big file. it aint easy i can tell u that but if u want to try it go ahead.
Click to expand...
Click to collapse
Yes be careful people and good luck. This one was a surprise to us...but then again, no one knows it all and it's fun to learn new things.
How abou just edit ext ROM.. can I do the same way as universal?? Or still unsolved?
Thanks
Related
Just curious as to how long it should take to flash the OS.nb file through mtty???
its been sitting on the 'start NB image download' for about 30 minutes now...
Code:
USB>
USB>task 32
Level = 0
USB>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 463
Storage Total block: 473
Total Bad Block in CE: 0
NeedToEraseBlockStart: 476
Storage format success
USB>lnb OS.nb
:F=OS.nb
:A=501A0000
:O=00000000
:L=FFFFFFFF
start NB image download
well it should take no where near 30 minutes (a full RUU upgrades takes only 25minutes)
when i upgraded to 2.05 via mtty it was done in under ten minutes (fast).
are you sure the filename is OS.nb because be default when you extract the .nb from the .nbh is will be 06_OS.nb
yes im sure it was named correctly else it wouldnt have picked up the
Code:
USB>lnb OS.nb
:F=OS.nb
:A=501A0000
:O=00000000
:L=FFFFFFFF
start NB image download
should i cancel it and start again??
when you extracted the .nb files from the .nbh did you rename any files?
If you didnt, then again I think OS.nb doesnt exist and that is why it is hanging there after more than 30 minutes.
also, make sure that mtty.exe is in the same directory as the .nb you are trying to flash.
yes i renamed the files from 06_OS.nb to OS.nb and the files are in the same directory... what version and connection speed are you using in mtty??? the version im using is 1.11a...
v1.11a and default settings for the USB connection.
I guess you can restart the process, because immediately after the messages you see on the terminal output should have sees the progress meter kick into full swing.
hahahahaha you were right... was using the mtty from a different folder ... time for some sleep....
there you go,
time for sleep? its only 3:22pm in Melbourne...... should you be at work?
EDIT: I cant talk, reading forums on company time, academia is so good.
yeah at work.. but been up all night playing with all these new tools!!!!
first i just want to say that i am not trying to out do pk's rom cause its great in a lot of ways that this rom isn't. with that being said i just wanted to offer up an alternative to those who r having problems with pk's v2 rom.
**** please use the unlocker first if you have not already done so, if your not sure if you have CID unlocked your phone then do it anyways *****
if your unsure how to CID unlock your device with this vid http://video.google.de/videoplay?docid=2234348915783114030
it is 18min.
ok now for the rom and unlocker **edit: i have updated this link to go directly to the pk3 rom
http://forum.xda-developers.com/showthread.php?t=338409
version 2.20
radio 1.45
for the extra programs **edit: link to PK3 rom
http://forum.xda-developers.com/showthread.php?t=338409
load this file onto the mini sd or microdrive, this is just a backup of everything
i left out the background cause i thought everyone would want there own
i am also attaching screen shot of the today.
***EDIT: i took down the links cause pk3 is a better rom and very stable, if you dont want all the stuff that comes with pk3 then u should download the offical htc wm6 rom ***
well i guess thats it. so have fun
features
so is this a standard rom with addons or is t cooked ie registry edits extra progs can we have the full details please
its really more of a standard rom with addons there are some registry hacks done but i want it to be as stable as possible. the only bug is in wm5storage when you deactive it the sd card is gone until you softreset then it back but 1.75 did not work at all for me which is why i loaded 1.73. Also you have the ability to uninstall any of the app that you don't want.
Yeah, details would be welcome.
It does not seem to be the latest available as you mention version 2.20 and
radio 1.45.
What is included, tweaked etc. and aren't the extras available as cab files?
ok, reg tweaks: time zone, date and time, hold comm manager for bright.exe, created .lnk for bluetooth, alarm, wifi, sounds that you have e-mail, text message, missed call and so on. as for as programs go i just loaded it and then backed them up so it would be easy to install. if i post cab then i can't give out serial keys for the programs that need it. it's not the latest but like i said i wanted to make sure that its stable for example pk's rom is ver 2.19 im sure part of the reason he choose that version is for stability.
irus said:
ok, reg tweaks: time zone, date and time, hold comm manager for bright.exe, created .lnk for bluetooth, alarm, wifi, sounds that you have e-mail, text message, missed call and so on. as for as programs go i just loaded it and then backed them up so it would be easy to install. if i post cab then i can't give out serial keys for the programs that need it. it's not the latest but like i said i wanted to make sure that its stable for example pk's rom is ver 2.19 im sure part of the reason he choose that version is for stability.
Click to expand...
Click to collapse
rom aint bad. i choose 2.19 because its the latest build at time for athena. build 17944. this build was awesome on my hermes and should also be for athena. only real problem in my rom is battery. the rest are realvga issues. good luck in ur rom cooking ventures.
Pawel062 said:
rom aint bad. i choose 2.19 because its the latest build at time for athena. build 17944. this build was awesome on my hermes and should also be for athena. only real problem in my rom is battery. the rest are realvga issues. good luck in ur rom cooking ventures.
Click to expand...
Click to collapse
thanks for the kind words
The more choices the better for EVERYONE! Sweet bro!
irus,
Which kitchen tool are you using to cook your rom? I would also like to cook my own, but not sure which tool is for Athena.
you'll find every thing you need.
http://forum.xda-developers.com/showthread.php?t=320338
And the roms just keep on coming.....
Nice option.....Good luck
Later.......
irus said:
you'll find every thing you need.
http://forum.xda-developers.com/showthread.php?t=320338
Click to expand...
Click to collapse
I'm aware of this thread, but I thought the tools there were for Trinity only. Am I wrong to have assumed that?
nice rom with nice aplications, thanks
eaglesteve said:
I'm aware of this thread, but I thought the tools there were for Trinity only. Am I wrong to have assumed that?
Click to expand...
Click to collapse
u can use it to extract rom from x7500
dump the os
I followed the manual and tried to dump the os.nb from the official "Advantage_HTC_NLD_2.21.404.1_1.50.00.00_Ship" rom. But I get the following errors. What am I doing wrong?
C:\ROMDonalds\02-Dump>dump os.nb
NBSplit 2.0 RC 2
Done.
ImgfsFromNb 2.0 RC 2
Searching for IMGFS start...
Found IMGFS at 00666668.
Dumping IMGFS at offset 00666668 (size 04666658)
Done!
ImgfsToDump 2.0 RC 2
guidBootSignature: F8 AC 2C 9D E3 D4 2B 4D BD 30 91 6E D8 4F 31 DC
dwFSVersion: 00000001
dwSectorsPerHeaderBlock: 00000001
dwRunsPerFileHeader: 00000001
dwBytesPerHeader: 00000034
dwChunksPerSector: 00000008
dwFirstHeaderBlockOffset: 00000200
dwDataBlockSize: 00001000
szCompressionType: XPR
dwFreeSectorCount: 00006A3C
dwHiddenSectorCount: 00000100
dwUpdateModeFlag: 00000000
Address: 00000200, dwBlockSignature: FFFFFEFE
dwNextHeaderBlock: 00000000 (size: FFFFFE00)
Header type: 00000270, Addr: 00000208
Unknown header type, FS_DATA_TABLE??
Header type: 004C006C, Addr: 0000023C
Unknown header type, FS_DATA_TABLE??
Header type: 000002A4, Addr: 00000270
Unknown header type, FS_DATA_TABLE??
Header type: 000002D8, Addr: 000002A4
Unknown header type, FS_DATA_TABLE??
Header type: 0000030C, Addr: 000002D8
Unknown header type, FS_DATA_TABLE??
Header type: 00000340, Addr: 0000030C
Unknown header type, FS_DATA_TABLE??
Header type: 00000000, Addr: 00000340
Unknown header type, FS_DATA_TABLE??
Header type: 00003608, Addr: 00000374
Unknown header type, FS_DATA_TABLE??
Header type: 00630061, Addr: 000003A8
Unknown header type, FS_DATA_TABLE??
Kan C:\ROMDonalds\02-Dump\imgfs.bin niet vinden
Done. The files are in "dump" folder
C:\ROMDonalds\02-Dump>
just redownload the rom and go from there
Thanks for this rom.
I know PK's rom is at the cutting edge of whats available, and whilst i like what it is capable of and am currently using it, its too unstable/buggy for me and i now realise that i prefer stability over the the extra's pk offers, so its time to reflash to your rom for now
Thanks
Mosser, if you have and questions or bugs please report both to this thread. thanks
I certainly will if i find any problems, have only been running it for about 6 hours so far, but it is ver fast, and is stable so far, the good thing is that everything seems to just work as it should, I miss the 96dpi though, but wouldnt give up battery life and stability for it
you can use real vga on this rom. there are a few bugs but it seems to work for the most part.
Cmd> lnbs SPL-1.01.nbs 50020000
:F=SPL-1.01.nbs
:A=50020000
:O=00000000
:L=FFFFFFFF
start NB image downloadS
Load ADDR: 50020000 Length: 402C4
H***
SPL flag is incorrect, please check your SPL is correct.
Write NAND error, addr=0x50020000
Error !! The image must be in ROM area.
BTW
I want to update my sys to WM6.1
What does this mean?
I wanna to change my spl to 1.01
my herm200
IPL-1.04
SPL*2.01.olipro
I am being online to wait your answers
thanks
i m trying to build Ervius Visual Kitchen to our gene i got information that Hermes Mobile is same rom structure as gene so i go to harmes forum and done necessary changes to Ervius Visual Kitchen but i m not able to flash
vaibhav,sumit,ramersonw,jyot,helgee,BesFen wakeup buddy
give some time to do different man, you all r doing same thing sine long time, i know we can do it
here is what i done till now
i got info that NBH file format used in gene is same as in the Hermes so why hermes kitchen is not working with gene (with gene XIP,hdr.etc )?
what is OS.nb.playload ?
what is ULDR ?
what is IMGSTART ?
hi guys i have tried this kitchen u need to modify xml file to get the gene settings
but after that it ask for some block size which it takes as defualt 4 and then when u cook the rom with this setting rom get build properly with a single warning erivius called it as time bomb.
but when u put the rom on the device it wont boot i tried many roms but non work with erivius visual kitchen v.9 latest verison might be working
i had put in the thread for this problem but erivius didnt respond...
will definately wake up ..lemme me bak frm vacation...
Pank789 said:
hi guys i have tried this kitchen u need to modify xml file to get the gene settings
but after that it ask for some block size which it takes as defualt 4 and then when u cook the rom with this setting rom get build properly with a single warning erivius called it as time bomb.
but when u put the rom on the device it wont boot i tried many roms but non work with erivius visual kitchen v.9 latest verison might be working
i had put in the thread for this problem but erivius didnt respond...
Click to expand...
Click to collapse
good start here my Solution + Question for this
you r talking about NBHUtil.xml
to all who don't know about NBHUtil.xml
its database file for NBHUtil, so u ask me what is NBHUtil.exe ?, NBHUtil is same like htcrt, htcrt use htcrt_devices.ini file as database and NBHUtil use NBHUtil.xml as database
new NBHUtil's database does not have gene device data base so you need add this entry
Code:
<device name="Gene" chunksize="1024">
<ModelID>GENE***</ModelID>
<CID>11111111</CID>
<Ver>1.00.000.0</Ver>
<Lang>WWE</Lang>
<Item value="0x100">IPL</Item>
<Item value="0x200">SPL</Item>
<Item value="0x600">Splash</Item>
<Item value="0x300">Radio</Item>
<Item value="0x400">OS</Item>
<Item value="0x700">ExtROM</Item>
</device>
i make this conflagration from htcrt_devices.ini
here is entry in htcrt_devices.ini
Code:
[Gene]
Experimental=0
ModelId=GENE10000
SignMaxChunkSize=1024
RomSections=6, "0x100,""IPL"",131072,TRUE", "0x200,SPL,524288,TRUE", "0x600,Splash,196608,FALSE", "0x300,Radio,2883584,FALSE", "0x900,""Ext. ROM"",10485760,FALSE", "0x400,OS,0,FALSE"
but this don't work
this is not big issue we can replace it with old htcrt but new stuff is always welcome
also if u see kitchen_build_rom.bat
there is entry for NBHUtil's
Code:
..\tools\nbhutil -model %deviceid% -ver %versionid% -lang %langid% -chunk %chunksize% -nogui -e -i %osidvalue% ..\temp\os-new.nb -b ruu_signed.nbh
but there no specification of ExtROM in this line
ankit360 said:
good start here my Solution + Question for this
you r talking about NBHUtil.xml
to all who don't know about NBHUtil.xml
its database file for NBHUtil, so u ask me what is NBHUtil.exe ?, NBHUtil is same like htcrt, htcrt use htcrt_devices.ini file as database and NBHUtil use NBHUtil.xml as database
new NBHUtil's database does not have gene device data base so you need add this entry
Code:
<device name="Gene" chunksize="1024">
<ModelID>GENE***</ModelID>
<CID>11111111</CID>
<Ver>1.00.000.0</Ver>
<Lang>WWE</Lang>
<Item value="0x100">IPL</Item>
<Item value="0x200">SPL</Item>
<Item value="0x600">Splash</Item>
<Item value="0x300">Radio</Item>
<Item value="0x400">OS</Item>
<Item value="0x700">ExtROM</Item>
</device>
i make this conflagration from htcrt_devices.ini
here is entry in htcrt_devices.ini
Code:
[Gene]
Experimental=0
ModelId=GENE10000
SignMaxChunkSize=1024
RomSections=6, "0x100,""IPL"",131072,TRUE", "0x200,SPL,524288,TRUE", "0x600,Splash,196608,FALSE", "0x300,Radio,2883584,FALSE", "0x900,""Ext. ROM"",10485760,FALSE", "0x400,OS,0,FALSE"
but this don't work
this is not big issue we can replace it with old htcrt but new stuff is always welcome
also if u see kitchen_build_rom.bat
there is entry for NBHUtil's
Code:
..\tools\nbhutil -model %deviceid% -ver %versionid% -lang %langid% -chunk %chunksize% -nogui -e -i %osidvalue% ..\temp\os-new.nb -b ruu_signed.nbh
but there no specification of ExtROM in this line
Click to expand...
Click to collapse
I already try to add os-new.nb and extrom manually using NBHutil, but still un booable. i guess the problem is in the xip.
BesFen said:
I already try to add os-new.nb and extrom manually using NBHutil, but still un booable. i guess the problem is in the xip.
Click to expand...
Click to collapse
did you flash gene successfuly ?, did u get msg on RUU that rom flash successfuly ? not bootable means what ? did u see htc splash screen ? or stuck at tri screen ?
ankit360 said:
did you flash gene successfuly ?, did u get msg on RUU that rom flash successfuly ? not bootable means what ? did u see htc splash screen ? or stuck at tri screen ?
Click to expand...
Click to collapse
flash success and RUU message said "congratulation........", but my deavice directly go to bootloader, no HTC slash. I release the battery and reinsert it again, and the device automatically on and go to bootloader again, and again.
BesFen said:
flash success and RUU message said "congratulation........", but my deavice directly go to bootloader, no HTC slash. I release the battery and reinsert it again, and the device automatically on and go to bootloader again, and again.
Click to expand...
Click to collapse
this not happen due to bad xip if u have bad xip u stuck at htc splash screen this happen because rom is no build property means wrong things goes wrong place
while building rom there is lot's factors like chunks size address of os.nb,xip,exrom if that get wrong device show u tri screen
gene partition info
this is new gene partition information
{
"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"
}
Hi Ankit,
Here is how i cook with visual kitchen, hope this could help ....
1)dump->Customize->Create Rom, after create rom i dont touch the released nbh file instead..
2)in kitchen/temp folder there is built xip.bin, os-ew.nb and imgfs-new.bin copy these three files and do nb work with imgfs.bin and xip and then htcert or directly htcert with os-new.nb and extrom ... it works try it.
and i also analysed os-new.nb its same with the original new gene os.nb the only difference is imgfsstart, you can if you do nbinfo oon on both you willl se imgfsstart address is different you can put the imgfs start value off new gene in the other biutton of kitchen and build .its someething 0060000
ps:writing from phone pardon my english
I will inspect it step by step tonight........., must by some coffee for it.
coolaj said:
Hi Ankit,
Here is how i cook with visual kitchen, hope this could help ....
1)dump->Customize->Create Rom, after create rom i dont touch the released nbh file instead..
2)in kitchen/temp folder there is built xip.bin, os-ew.nb and imgfs-new.bin copy these three files and do nb work with imgfs.bin and xip and then htcert or directly htcert with os-new.nb and extrom ... it works try it.
and i also analysed os-new.nb its same with the original new gene os.nb the only difference is imgfsstart, you can if you do nbinfo oon on both you willl se imgfsstart address is different you can put the imgfs start value off new gene in the other biutton of kitchen and build .its someething 0060000
ps:writing from phone pardon my english
Click to expand...
Click to collapse
it mean you use imgfs and xip to build the new os-new.nb, not use the result of os-new.nb from visual kitchen.
I ever read at ervius thread that they cut some address of xip and imgfstart, and it can save some phone storage and RAM, maybe that step make the result of RUU_Signed.nbh and os-new.nb from that kitchen not work in my GENE.
It's more interesting and exsiting, I will try it tonight and report it here.........see you tonight
coolaj said:
Hi Ankit,
Here is how i cook with visual kitchen, hope this could help ....
Click to expand...
Click to collapse
that means you create ROM for gene with visual kitchen successfully ?
here is result
my cooked ROM with old working kitchen
Code:
'os-new.nb' has valid boot sector
Partition table:
Partition 0
-----------
File System: 0x20 (boot)
Start Sector: 0x00000002
Total Sectors: 0x000000fa
Boot indicator: 0x00
First Head: 0x02
First Sector: 0x01
First Track: 0x00
Last Head: 0xfb
Last Sector: 0x01
Last Track: 0x00
Partition 1
-----------
File System: 0x23 (XIP RAM)
Start Sector: 0x000000fc
Total Sectors: 0x000017a0
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x01
Last Head: 0xfb
Last Sector: 0x01
Last Track: 0x18
Partition 2
-----------
File System: 0x25 (imgfs)
Start Sector: 0x0000189c
Total Sectors: 0x0001c0e0
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x19
Last Head: 0xfb
Last Sector: 0x01
Last Track: 0x1e0
Partition 3
-----------
File System: 0x00 (unknown)
Start Sector: 0x00000000
Total Sectors: 0x00000000
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x00
First Track: 0x00
Last Head: 0x00
Last Sector: 0x00
Last Track: 0x00
Geometry: flash has 252 virtual heads
MSFLSH50 header found at offset 0x200
(0 Reserved Entries, 2 Flash Region Entries)
Flash Region Entry 0:
---------------------
Region type: XIP
Start phys. block: 0x00000000
Size in phys. blocks: 0x00000000
Size in log. blocks: 0x00000019 -> Size in sectors: 0x0000189c
Sectors per block: 0x000000fc
Bytes per block: 0x0001f800
Compact blocks: 0x00000000
-> Bytes per sector: 0x00000200
Flash Region Entry 1:
---------------------
Region type: READONLY_FILESYS
Start phys. block: 0x00000000
Size in phys. blocks: 0x00000000
Size in log. blocks: 0x000001c8 -> Size in sectors: 0x0001c0e0
Sectors per block: 0x000000fc
Bytes per block: 0x0001f800
Compact blocks: 0x00000000
-> Bytes per sector: 0x00000200
Searching for IMGFS signature...
Found IMGFS at byte 0x00313800 (sector 0x0000189c).
dwFSVersion: 00000001
dwSectorsPerHeaderBlock: 00000001
dwRunsPerFileHeader: 00000001
dwBytesPerHeader: 00000034
dwChunksPerSector: 00000008
dwFirstHeaderBlockOffset: 00000200
dwDataBlockSize: 00001000
szCompressionType: XPR
dwFreeSectorCount: 0000490A
dwHiddenSectorCount: 00000100
dwUpdateModeFlag: 00000000
Original WM 6 Rom
Code:
'01_OS.nb' has valid boot sector
Partition table:
Partition 0
-----------
File System: 0x20 (boot)
Start Sector: 0x00000002
Total Sectors: 0x0000189a
Boot indicator: 0x00
First Head: 0x02
First Sector: 0x01
First Track: 0x00
Last Head: 0xfb
Last Sector: 0x01
Last Track: 0x18
Partition 1
-----------
File System: 0x23 (XIP RAM)
Start Sector: 0x0000189c
Total Sectors: 0x00001a94
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x19
Last Head: 0xfb
Last Sector: 0x01
Last Track: 0x33
Partition 2
-----------
File System: 0x25 (imgfs)
Start Sector: 0x00003330
Total Sectors: 0x0001e258
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x01
First Track: 0x34
Last Head: 0xfb
Last Sector: 0x01
Last Track: 0x21d
Partition 3
-----------
File System: 0x00 (unknown)
Start Sector: 0x00000000
Total Sectors: 0x00000000
Boot indicator: 0x00
First Head: 0x00
First Sector: 0x00
First Track: 0x00
Last Head: 0x00
Last Sector: 0x00
Last Track: 0x00
Geometry: flash has 252 virtual heads
MSFLSH50 header found at offset 0x200
(0 Reserved Entries, 2 Flash Region Entries)
Flash Region Entry 0:
---------------------
Region type: XIP
Start phys. block: 0x00000000
Size in phys. blocks: 0x00000000
Size in log. blocks: 0x00000034 -> Size in sectors: 0x00003330
Sectors per block: 0x000000fc
Bytes per block: 0x0001f800
Compact blocks: 0x00000000
-> Bytes per sector: 0x00000200
Flash Region Entry 1:
---------------------
Region type: READONLY_FILESYS
Start phys. block: 0x00000000
Size in phys. blocks: 0x00000000
Size in log. blocks: 0x000001ea -> Size in sectors: 0x0001e258
Sectors per block: 0x000000fc
Bytes per block: 0x0001f800
Compact blocks: 0x00000000
-> Bytes per sector: 0x00000200
Searching for IMGFS signature...
Found IMGFS at byte 0x00666000 (sector 0x00003330).
dwFSVersion: 00000001
dwSectorsPerHeaderBlock: 00000001
dwRunsPerFileHeader: 00000001
dwBytesPerHeader: 00000034
dwChunksPerSector: 00000008
dwFirstHeaderBlockOffset: 00000200
dwDataBlockSize: 00001000
szCompressionType: XPR
dwFreeSectorCount: 00003425
dwHiddenSectorCount: 00000100
dwUpdateModeFlag: 00000000
BesFen said:
it mean you use imgfs and xip to build the new os-new.nb, not use the result of os-new.nb from visual kitchen.
I ever read at ervius thread that they cut some address of xip and imgfstart, and it can save some phone storage and RAM, maybe that step make the result of RUU_Signed.nbh and os-new.nb from that kitchen not work in my GENE.
Click to expand...
Click to collapse
its called ULDR but don't know what is that ?
@Ankit, sorry replying late was testing rom built by ervius kitchen because icant test and be online at the same time b'cus i use internet from phone.
Okay yes i have created working roms from visual kitchen as said earlier used imgfs-new bin and xip and did nbwork and htcert. if you buil with os-new.nb and extrom gene will stuck at tricolour mode..have some more tricks will be posting..
All this done with Original 6.0 new gene rom
ULDR Info -http://forum.xda-developers.com/showpost.php?p=2916649&postcount=7 by ameet
coolaj said:
@Ankit, sorry replying late was testing rom built by ervius kitchen because icant test and be online at the same time b'cus i use internet from phone.
Okay yes i have created working roms from visual kitchen as said earlier used imgfs-new bin and xip and did nbwork and htcert. if you buil with os-new.nb and extrom gene will stuck at tricolour mode..have some more tricks will be posting..
All this done with Original 6.0 new gene rom
ULDR Info -http://forum.xda-developers.com/showpost.php?p=2916649&postcount=7 by ameet
Click to expand...
Click to collapse
can u give me you kitchen plz ? only tool folder
also tell me what changes u done in my temp folder i get only OS-new.nb romhdr.bin and xip.bin
if u have msn or yahoo mail id we can chat online
ankit360 said:
can u give me you kitchen plz ? only tool folder
also tell me what changes u done in my temp folder i get only OS-new.nb romhdr.bin and xip.bin
if u have msn or yahoo mail id we can chat online
Click to expand...
Click to collapse
In Tools/kitchen_build_rom.bat delete these lines
del imgfs-new.bin
del OS-new.nb.payload
and build you will see in temp folder.
and i think uldr part is causing the problem....
coolaj said:
In Tools/kitchen_build_rom.bat delete these lines
del imgfs-new.bin
del OS-new.nb.payload
and build you will see in temp folder.
and i think uldr part is causing the problem....
Click to expand...
Click to collapse
what is IMGSTART value ?
I would ask all active members to upload or share their collection of roms for Hurricane. I bricked my hurr 2 years from now and yesterday i got one so i would like to try as many roms as possible, and it will be great for all to share roms!!! I found several on this forum (lazaj's, saleng's, shadow's) but i think that there is more!!! So share your collection!!!
Here i found some on forum:
hurricane unlock, patch and upgrade wm 6.1(selang09) ***
Link: http://www.megaupload.com/?d=JLO5H1L7
Thread: http://forum.xda-developers.com/showthread.php?t=475286
Opinion: Good one, but chinese language everywhere! After u change main lang. still some apps name stay in chinese and options too!
wm6.1 for hurricane (with Bluetooth and INFRARED RAY problems solved)0415update!!!
Link: http://rapidshare.com/files/100934508/5x6_wm6.1_0319.rar
Thread: http://forum.xda-developers.com/showthread.php?t=378607
Opinion: Didn't tried!
WM 6 Graphite rom, how to get WMPlayer in English (now in Polish)
Link: http://rapidshare.com/files/108676266/wm6_2_2.zip
Thread: http://forum.xda-developers.com/archive/index.php/t-384972.html
Opinion: Using this one right now! Seems ok, works nice, nice look, except incoming calls didn't show up!!! Very bad bug!
Wm 6.1 Pl/eng
Link: http://rapidshare.com/files/131860280/wm_6_1_by_Lazaj007.zip
Thread: http://forum.xda-developers.com/showthread.php?t=410739
Opinion: Tried before Graphite eng edition, works great, looks great... Main lang polski, after lang change WMP stay in polski! But still ok!
WM6 for SPV C550
Link: http://rapidshare.com/files/56833250/566.zip
Thread: http://forum.xda-developers.com/showthread.php?t=330709
Opinion: Never tried!
And one pack with SPL 1.00.84 & soft spl (nb, nbf), IPL 1.00.15, GSM DATA (hex and dec), bootloader commands, splsplit... etc!
Link: http://rapidshare.com/files/427352270/data_hurricane.rar
Info: This last files can help u to unbrick your hurricane (BUT AVOID TO BRICK IT), i found it on pda2u.ru , and thanks them for that! Special thanks to member SAXON!
I found many links for ROMs but those which is here have alive links! Someone with good upload speed can reup them again in one pack and post a link here!
ENJOY!
I would like to have a non T-Mobile German version (can be a shipped ROM). Have not found any yet, only those that are available at www.shipped-roms.com Have to live with de-branding this as it seems.
Possibly someone with any of the following devices can do a "r2sd all" backup of the ROM?
imate SP4M
Orange C550
Qtek 8200 (the Russian/English is available as RUU)
Thanks for this link tobbbie !
Btw, in selang's rom SMS Send don't work! So, it is useless!!! :S
I have tested all ROM´s below for SDA II, but for me lazaj007 is the best of all
Thanks to lazaj007
Did anyone care to pick up some ROM cooking for that device? I did not succeed in getting the .BIN files manipulated correctly - and I think I have a collection of nearly all ROM tools now :-(
howto convert .bin to .nb0 and back
Foreword:
.BIN files are not all the same by their nature (of course not by content). There are
.bin that are used to identify the bare binary content of the various partitions (you mostly see those)
.bin that are used to flash a ROM to the device. This looks somehow historic though, the format is already described by itsme at: http://www.xs4all.nl/~itsme/projects/xda/wince-flashfile-formats.html. It seems to me that some non HTC devices are still using this format.
The osnbtool.exe (from Weisun at PDACLAN.COM) does not work for any purpose regarding .bin files
at least not for Hurricane.
- The -sp option cuts only the B000F\0a header but does not reconstruct the blocks of the .bin file.
Mind that small .bin files (smaller than 0x1c00000) are treated correctly as there is only one block.
- The -2bin option creates an incorrect .bin header (sets a weird total length) and sets totally confused
block-load addresses for the created blocks of 64k (0x10000) size. Check it with viewbin.exe if you like.
Reference for the filestructure by itsme:
http://www.xs4all.nl/~itsme/projects/xda/wince-flashfile-formats.html
The splitrom.pl (itsme romtools) seems not be able to read the content of any .bin file I have fed to it.
Neither for .BIN files created for Hurricane nor those for Typhoon, I always get:
cmd> splitrom.pl <binfile>
B000FF image: 82040000-84c40000, entrypoint: 00000000
!!! your rom is not known to me: md5: a520f0d1093b36f0a3cfd9323ea99155
this bootloader seems to be No bootloader present
no xipchain found
no bootloader found
no operator rom found
no bitmap found
I am rather sure it should handle everything correctly but I am too stupid to debug .pl :-(
So the only thing that works and will re-create a flash-able .BIN file from a .nb0 is listed below:
convert .bin to .nb0:
enter: viewbin -r <binfile>, you get something like:
Image Start = 0x82040000, length = 0x02C00000
Record [ 0] : Start = 0x82040000, Length = 0x01C00000, Chksum = 0x00000000
Record [ 1] : Start = 0x83C40000, Length = 0x01000000, Chksum = 0x00000000
Record [ 2] : Start = 0x00000000, Length = 0x00000000, Chksum = 0x00000000
Start address = 0x00000000
The above has two blocks of data and a termination block.
The checksum = 0 effectively disables upload checking (so potentially dangerous).
The size just fits the Hurricane's SPL "l" (load) command buffer, as you get when loading a ROM:
"clean up the image temp buffer at 0x8C080000 Length 0x01C40000 "
The blocks can be smaller than 0x1c40000 but not bigger obviously.
then convert to nb0, enter: cvrtbin.exe -r -a <imgstart> -l <length> -w 32 <binfile>
for above viewbin output: cvrtbin.exe -r -a 82040000 -l 2c00000 -w 32 <binfile>
mind to omit the 0x for the start and address, replace <binfile> with your filename, then you get a resulting file from <original-name.bin> to <original-name.nb0> which can further be decomposed and edited with standard ROM tools
convert .nb0 to .bin:
enter: xipbin.exe <input.nb0> <start-in-nb0> <output.bin> <loadaddress>
to get back something flashable like above: xipbin.exe <input.nb0> 0 <output.bin> 82040000
mind to omit the 0x for the loadaddress, replace <"file"> with your filenames
to recheck if the created BIN file is usable, startup the viewbin again
enter: viewbin -r <binfile> you now get something like:
Image Start = 0x82040000, length = 0x02C00000
Record [ 0] : Start = 0x82040000, Length = 0x00040000, Chksum = 0x0208CC79
...many entries deleted...
Record [175] : Start = 0x84C00000, Length = 0x00040000, Chksum = 0x0177FB3C
Record [176] : Start = 0x00000000, Length = 0x00000000, Chksum = 0x00000000
Start address = 0x00000000
Done.
Looks quite different - but this is ok! The loading process in MTTY indocates the loading of each above block with a sequence of |*, so with these many blocks the upload to the device is giving feedback and thus is not tempting people to interrupt it.
I have done my tests with the 566.zip linked in the first post of this thread, but this should work with any .BIN file from the other ROMs as well. So I will continue to see if I can recycle any of the WM6 Roms for inserting my imgfs created for Tornado. As before the imgfs still the XIP is loaded and I know too little about this yet (especially in connection to the imgfs and how close these two are linked) - I am prepared to see non booting device states quite a lot. Luckily there is nothing done to the early boot chain (IPL and SPL) so I can always get back to the bootloader and start over again.
I hope to get a first indication that imgfs is mounted correctly in the "old" XIP before I have to replace the OEMdriver parts in my Tornado ROM.
I just checked if I can still use this flash-method for the Tornado - and it works as well. So the created "os-new.nb" in the OUT directory can be converted to .BIN and then flashed inside MTTY with the "l" command. Not that I like this method - but it works as well.
Tobbbie, you have here a very good research! To bad this device is out of use!