All Hurricane ROMS in one place!!!

---

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/10093450...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/arch.../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/13186028...y_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/42735227..._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

1. .bin that are used to identify the bare binary content of the various partitions (you mostly see those)
2. .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:

1. 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
2. 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
3. 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!