Help!
I can't extract them from any ROM.
I tried but have not succeeded.
Can some one please send me in PM/Post
TX in advance :wink:
1) Dump imgfs (all OS ROM files) from a device with italian rom:
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
2)Use rdmsflsh.pl to extract the contents from imgfs:
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoExtractImgfs
Hi Nicola!
You have to use Resco File Explorer (not the original File Explorer) to substitute all files I've uploaded
Remember to unhide all ROM's files from Options
....It works very well!!! :wink:
Tx Daniele
I am sure it will be useful for many Italians.
Ciao
:wink:
Here
http://htchermesitalia.forumup.it/viewtopic.php?t=10&mforum=htchermesitalia
istruction in italian lang...
i want to change my chinese rom nb file to LZX compression mode.
below is my test but none successed!
1,get imgfsbin
imgfsfromnb old.nb old.bin
imgfsfromnb korand.nb korand.bin
now open bins with ultraedit,i see old.bin is XPR and korand.bin is LZX.
2,imgfstodump old.bin
3,try to create new nb file with dump and LZX new.bin
imgfsfromdump korand.bin new.bin
4,imgfstonb new.bin korand.nb new.nb
now i can enter the today screen sucessfully but all provxml files are not executed when hard reset,so the security policy is strict and cannot install any cabs or sync.i don't know why bcoz the dump dir wokrs fine with old.nb
imgfstonb new.bin old.nb new.nb
i try to create new nb with dump and LZX new.bin based on old.nb
but after flash this the phone stuck in the 2nd boot screen and cannot get into windows mobile.
at last,how to change my old nb compression to LZX?
mrpotter said:
i want to change my chinese rom nb file to LZX compression mode.
below is my test but none successed!
1,get imgfsbin
imgfsfromnb old.nb old.bin
imgfsfromnb korand.nb korand.bin
now open bins with ultraedit,i see old.bin is XPR and korand.bin is LZX.
2,imgfstodump old.bin
3,try to create new nb file with dump and LZX new.bin
imgfsfromdump korand.bin new.bin
4,imgfstonb new.bin korand.nb new.nb
now i can enter the today screen sucessfully but all provxml files are not executed when hard reset,so the security policy is strict and cannot install any cabs or sync.i don't know why bcoz the dump dir wokrs fine with old.nb
imgfstonb new.bin old.nb new.nb
i try to create new nb with dump and LZX new.bin based on old.nb
but after flash this the phone stuck in the 2nd boot screen and cannot get into windows mobile.
at last,how to change my old nb compression to LZX?
Click to expand...
Click to collapse
The reason your phone can't boot is because the cecompr.dll in your XIP doesn't support LZX compressed. you have to use the same XIP (or make a proper port with the same cecompr.dll as Korand rom).
Hope it helped
if you Hexedit imgfs.bin and change the XPR to LZX your new imgfs will be LZX compressed.
thanks very much!
i don't know how to port xip,so i decide to use your crystal.nb as nb template.but why provxml files not executed when hard reset.the dump folder works fine with the old nb file.so i think it's something related to the xip of new nb.
i tried to process the provxml after cold init,retrieve error 0x80004005(unsepecified error)
Ay one have idea how we can open (tsw) file? I try to trasnform to (bin) file then open with a lot of diferent tool but all of them says it's not a orijinal bin file you can't open.
if you search a little bit, you'll see that it is a tool developed by cotulla, that transforms the .tsw file into .bin
ady_uaic said:
if you search a little bit, you'll see that it is a tool developed by cotulla, that transforms the .tsw file into .bin
Click to expand...
Click to collapse
And if you try this tool you go to see is not working.
You transform in bin who is not bin file. So that tool from cotula is the big XXX.
Who said that Toshiba's bin files are similar to htc ones ?
It's a bin file that contains whole system part drivers bootloader and other things with crc checks etc... Cotulla made a decrypter for TSW files now someone need to write tool that will be able to decompress all rom parts and then compress them back to bin file in TG01 format
who know the latest news about TG01 unlock?(japanese device T01A)
who know the latest news about TG01 unlock?(japanese device T01A)
I am confused and want the good news.
yes, i agree with you @nico101. the files are .bin, but the "composition" of those files is different than the ones from htc devices, for ex.
in this case, can you tell me (us) if, with this gps gate, you lose or not the signal, for 1-2 seconds when you drive, or when you walk?
Wait, guys, so all we need is a decompresser for the files?
I think yes.
TG01
bojan6 said:
I think yes.
Click to expand...
Click to collapse
I think we you might need to request a programmer who knows how to decompress files on your wmpoweruser home page wen, and sticky on homepage of xda developers to grab peoples attention!!
we need a hacker to figure layout of .bin file as i said before if some one figures out things i would probably be able to write the programs.
the .bin file is not encrypted or compressed but it contains more files, it is analogue to HTC .nbh file
00003808 , \Recovered File 01.mov
00112925 , \Recovered File 02.gz
00115498 , \Recovered File 03.png
00115530 , \Recovered File 04.png
00115533 , \Recovered File 05.png
00115563 , \Recovered File 06.png
00115791 , \Recovered File 07.cab
00115962 , \Recovered File 08.gz
00116325 , \Recovered File 09.png
00116351 , \Recovered File 10.cab
00116354 , \Recovered File 11.cab
00116385 , \Recovered File 12.cab
00116391 , \Recovered File 13.cab
00116417 , \Recovered File 14.png
00116420 , \Recovered File 15.png
00116421 , \Recovered File 16.gif
That is inside the bin file.
And here is reply from Cotulla:
"Seems you need decrypt TSW image to BIN and then encrypt it back to TSW.
BIN image have complex format with header and many parts.
Obviously we need exclude all stuffs except OS.
The main problem to test this - I am not sure if we put wrong image, it won't brick device...
-Cotulla"
bojan6 said:
00003808 , \Recovered File 01.mov
00112925 , \Recovered File 02.gz
00115498 , \Recovered File 03.png
00115530 , \Recovered File 04.png
00115533 , \Recovered File 05.png
00115563 , \Recovered File 06.png
00115791 , \Recovered File 07.cab
00115962 , \Recovered File 08.gz
00116325 , \Recovered File 09.png
00116351 , \Recovered File 10.cab
00116354 , \Recovered File 11.cab
00116385 , \Recovered File 12.cab
00116391 , \Recovered File 13.cab
00116417 , \Recovered File 14.png
00116420 , \Recovered File 15.png
00116421 , \Recovered File 16.gif
That is inside the bin file.
Click to expand...
Click to collapse
Got the same result with Isobuster.
I will now extract these files and look if there could be something done with them.
That is the result from Isobuster but no chance to extract them. Try if you can good. The furst one is the OS, there are some photo and I think other from provider to.
Well I get these files out of the .bin extracted.
But...I cannot extract for example the .cab files ...it tells me that they're damaged...all of them.
DunkDream said:
Well I get these files out of the .bin extracted.
But...I cannot extract for example the .cab files ...it tells me that they're damaged...all of them.
Click to expand...
Click to collapse
You try to open them?
I can open some of the archives.
For example I got a file named _setup.xml
That file contains:
- <wap-provisioningdoc>
- <characteristic type="CM_Networks">
<nocharacteristic type="Bouygtel GPRS" />
</characteristic>
- <characteristic type="CM_Networks">
<nocharacteristic type="MMS BOUYGUES" />
</characteristic>
- <characteristic type="CM_GPRSEntries">
<nocharacteristic type="Bouygtel GPRS" />
</characteristic>
- <characteristic type="CM_GPRSEntries">
<nocharacteristic type="Bouygtel GPRS2" />
</characteristic>
- <characteristic type="CM_GPRSEntries">
<nocharacteristic type="MMS BOUYGUES" />
</characteristic>
- <characteristic type="CM_ProxyEntries">
<nocharacteristic type="HTTP" />
</characteristic>
- <characteristic type="CM_ProxyEntries">
<nocharacteristic type="HTTP-{0DAEA92E-2917-4C6C-9E23-F2BCAA13DA07}" />
</characteristic>
- <characteristic type="CM_ProxyEntries">
<nocharacteristic type="null-corp" />
</characteristic>
- <characteristic type="Registry">
<nocharacteristic type="HKLM\SOFTWARE\ArcSoft\ArcSoft MMS UA\Config\mm1\MMSCSetting\SampleMMSC" />
</characteristic>
</wap-provisioningdoc>
I now tried to open the .bin file with an binary editor
You find the screenshot attached.
There is a text written:
Image file with header
C:\M8650\AMSS\products\8650\build\ms\bin\SDCAOPZ\FactoryImageTG01W.bin
msm=Q8650
flash_device = toshiba_tg_01
flash_id=0x9
And so on...Just look at the screenshot!
And that file is huge! I'll look if there are more information I can get.
I think we need just the furst two file.
00003808 , \Recovered File 01.mov
00112925 , \Recovered File 02.gz
The others are about providers..
This two files are the OS. we need to unpack(open, decompress or bla bla..)them.
If you extracted them tell me how you did it?
without much introduction, the fruit of my labor: tgtool.exe
it will dump parts of .tsw or unencrypted .bin files.
you need bepe's xidump to dump xip and imgfs
this is still alpha code
use example:
tgtool TG01WP_5005000167.tsw
xidump -b TG01WP_5005000167.09
xidump -b TG01WP_5005000167.10
Code:
[B][SIZE="3"]
Need these files from build 20130301
[B][U]etc folder[/U][/B]
firmware ( whole folder)
hw_config
media_profiles
sensors.
[B]lib folder[/B]
hw (whole folder)
modules (whole folder)
libandroid.so
libcald_cliente.so
libcald_debugger.so
libcald_hal.so
libcald_pal.so
libcald_server.so
libcamera_client.so
libcamera_clientsemc.so
libcameraextensionclient.so
libcameraextensionjni.so
libcameraextensionservice.so
libcameralight.so
liboemcamera.so
libsensorservice.so
usr (whole folder)
[/SIZE][/B]
can any plz provide me these files for LWW, MINI , ACTIVE ..
plz PM me links thanks
Why don't you download it yourself and extract?
BTW it's a wrong section.
Closed.
how to extract a xip.bin file?
I used xipport and it gived me necessary files: S000, S001 and S002
but these were in binary format. so I could modify these only via hexeditor. is there any way to extract or convert these files?
if we can do this, I will try porting rmnet protocol to clk bootloader