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!!!!
when I insert the sim
leave this message
FATAL ERROR
Data crashes. Please contact your service center
the phone cingular 3125 that the purchase was blocked and the sim cid not say who because I live here and nobody in bolivia unlock a cingular 3125 windows movile!
OMG it's you again. I already tried to explain you a couple of times that your "simlock data area" is corrupted. Ah well ...
Doesn't Solution Exist Then?
diego1x0 said:
Doesn't Solution Exist Then?
Click to expand...
Click to collapse
Try this:
Code:
"pdocread -n 1 0x000000 0x20000 -b 0x4000 simunlock.nb"
Attach the file in this thread.
I have the same problem (Cingular 3100)
jockyw2001 said:
Try this:
Code:
"pdocread -n 1 0x000000 0x20000 -b 0x4000 simunlock.nb"
Attach the file in this thread.
Click to expand...
Click to collapse
I'm having the same problem with my Cingular, can you help me please?
ASPcoder said:
I'm having the same problem with my Cingular, can you help me please?
Click to expand...
Click to collapse
Seems to me you didn't produce the file with this line:
pdocread -n 1 0x000000 0x20000 -b 0x4000 simunlock.nb
Your filesize is 64 KByte, it should have been 128 Kbyte
jockyw2001 said:
Seems to me you didn't produce the file with this line:
pdocread -n 1 0x000000 0x20000 -b 0x4000 simunlock.nb
Your filesize is 64 KByte, it should have been 128 Kbyte
Click to expand...
Click to collapse
sorry for the mistake, is attached better?
code error thc data crashes.please contact service provider
how to do you apply the zip file to solve the problem
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 ?
Gentlemen, with these settings below I can not succeed in installing android on my HTC topaz where I'm wrong because the settings of the Haret defaul.txt enters the boot to put it on display with this information
Haret boot
Shutting down hardware
Turning off MMU ...
PSR = 600000
AND LATCH.
I'LL SHOW THEM HOW THIS SET THE SD CARD AND THE FILES THEREIN.
THE ROOT OF THE FOLLOWING FILES ARE SDCARD:
/ CONF
/ MEDIA
CALIBRATION.TXT
DEFAULT.TXT
EncFiltLog.menc
HARET.EXE
Initrd.gz
modules-2.6.27-00706-g4da65fd-dirty.tar.gz
ROOTFS.IMG
system.sqsh
zImage
REMEMBERING THAT THIS CARD SD formatted in FAT32.
SETUP FILE IS THIS DEFAULT.TXT.
MTYPE September 2293
September KERNEL zImage
# Set FBDURINGBOOT 0
September initrd initrd.gz
September ramsize 0x10000000
September ramaddr 0x10000000
PWF # dm.txt 0x8e0000 0x20000
PWF # smem.txt 0x01f00000 0x100000
# = Msmts_calib 0x376.0x3c1.0x6a.0x8a
September cmdline "= msmts_calib 0x395.0x3d5.0x79.0xa0 msmvkeyb_toggle = off lcd.density mddi.width = 240 = 320 = 480 mddi.height no_console_suspend pmem.extra gsensor_axis = 1 =- 1, -2.3 sensor topaz force_cdma = = htc_battery_smem.fake 0 = 1 "
# Mddi.width mddi.height = 320 = 480
boot
WHAT IS WRONG OR BETTER WHERE I'M wrong?
GRATEFUL FOR THE HELP
pauloedusp said:
Gentlemen, with these settings below I can not succeed in installing android on my HTC topaz where I'm wrong because the settings of the Haret defaul.txt enters the boot to put it on display with this information
Haret boot
Shutting down hardware
Turning off MMU ...
PSR = 600000
AND LATCH.
I'LL SHOW THEM HOW THIS SET THE SD CARD AND THE FILES THEREIN.
THE ROOT OF THE FOLLOWING FILES ARE SDCARD:
/ CONF
/ MEDIA
CALIBRATION.TXT
DEFAULT.TXT
EncFiltLog.menc
HARET.EXE
Initrd.gz
modules-2.6.27-00706-g4da65fd-dirty.tar.gz
ROOTFS.IMG
system.sqsh
zImage
REMEMBERING THAT THIS CARD SD formatted in FAT32.
SETUP FILE IS THIS DEFAULT.TXT.
MTYPE September 2293
September KERNEL zImage
# Set FBDURINGBOOT 0
September initrd initrd.gz
September ramsize 0x10000000
September ramaddr 0x10000000
PWF # dm.txt 0x8e0000 0x20000
PWF # smem.txt 0x01f00000 0x100000
# = Msmts_calib 0x376.0x3c1.0x6a.0x8a
September cmdline "= msmts_calib 0x395.0x3d5.0x79.0xa0 msmvkeyb_toggle = off lcd.density mddi.width = 240 = 320 = 480 mddi.height no_console_suspend pmem.extra gsensor_axis = 1 =- 1, -2.3 sensor topaz force_cdma = = htc_battery_smem.fake 0 = 1 "
# Mddi.width mddi.height = 320 = 480
boot
WHAT IS WRONG OR BETTER WHERE I'M wrong?
GRATEFUL FOR THE HELP
Click to expand...
Click to collapse
1st off.. post in the correct forum: http://forum.xda-developers.com/forumdisplay.php?f=623
2nd try change the name of the startup file from "default" to "startup.txt"
3rd: you should have this layout in your sd card:
/AndroidApps/
/conf/
/media/
/STARTUP CONFIG/
/STARTUP.TXT
/haret.exe
/initrd.gz
/rootfs.img
/system.ex2
/zImage
4th: try using latest bundle package (XDAndroid is working for me). find some more info here: http://forum.xda-developers.com/showthread.php?t=509493
hope this helps, good luck!
I'm sorry for this post I will put it in the forum thanks for the warning stated.
I did just download the knack that you told me.
only one question should be how startup.ext settings?
AND A QUESTION FILE modules-2.6.27.46-01165-gfc1639f.tar.gz Unzip WHERE DO I HAVE?
the system that I downloaded was XDANDROID.2.2.AOSP.FRX01.17.09.10.UPDATE_PACKAGE
grateful
pauloedusp said:
I'm sorry for this post I will put it in the forum thanks for the warning stated.
I did just download the knack that you told me.
only one question should be how startup.ext settings?
AND A QUESTION FILE modules-2.6.27.46-01165-gfc1639f.tar.gz Unzip WHERE DO I HAVE?
the system that I downloaded was XDANDROID.2.2.AOSP.FRX01.17.09.10.UPDATE_PACKAGE
grateful
Click to expand...
Click to collapse
if you just extract the package and copy the whole 'Andboot' folder to the root of your SD, then go into the STARTUP CONFIG\TOPAZ and copy the startup.txt file to into the Andboot folder and launch haret it should work.
keep in mind that you should have at least 250mb-300mb free in your storage card.
the modules can stay gzipped, no problem.
I'm afraid that for advanced setting i cannot be of any help. If you have question, try posting them in the XDAndroid thread...
good luck
thanks for the help but I have not had success ...
I tried all forms with multiple files at last unable to exit the screen when having to boot the Haret.
Haret boot
Shutting down hardware
Turning off MMU ...
In preloader
PSR = 600000df
I'm forgetting to do something so I do not know what it is yet but thanks for the help.
nobody answered me in the post.
good keep searching and counting on your help
I'm already almost one month trying and nothing ...
but thanks
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!