dear all,
.tsd file is a japanese rom file format,usually eng rom is a .tsw file format.
I use cedesmith tgtool to -chk and -dec .tsd,and recieved the messege "invalid header file" error.
who can help me to check how to solve this problem.h
T01A Rom may be have a little bit difference from TG01 Rom ,so we need cedesmith release a tgtool version for japanese rom or need cedesmith release source code of tgtool and some one can modify it ,after that we can use it for japanese rom.
The japanese rom file has a tsd (toshiba docomo) extension not tsw(toshiba worldwide) extension. http://update.toshibamobile.com/update/t01a/wm65/T01A_to_SP50_wm65.exe
@bird:have you tried to change extension file name from tsd to tsw and use the tgtool?
Now should try to contact cotulla for the encrypt key
http://forum.xda-developers.com/showthread.php?t=651060
Related
hi!!
i downloaded llbasha-WM5-AKU35pp16c3 rom
i want extract os.nb file from nk.nbf with typho5 utility (typhoonbftool_v5),i got this error:
unknow header format, and it abort work.
other way:
i want extract os.nb file from nk.nba with prepare_imgfs, and i got this error:
searching for IMGFS start.......Not found!!!
anybody know if it can extract some file from a rom already cooked ???
thank in advance
hi!!
i downloaded llbasha-WM5-AKU35pp16c3 rom
i want extract os.nb file from nk.nbf with typho5 utility (typhoonbftool_v5),i got this error:
unknow header format, and it abort work.
other way:
i want extract os.nb file from nk.nba with prepare_imgfs, and i got this error:
searching for IMGFS start.......Not found!!!
anybody know if it can extract some file from a rom already cooked ???
thank in advance
Chinese Edition: http://www.coolcode.cn/andot/bin2nb-nb2bin-released/277
Hello, everyone. I find there is no tools can convert bin file to nb file or convert nb file to bin file. so I made these tools: bin2nb & nb2bin. They only can convert os.bin to os.nb, and os.nb os.bin, they can't convert gsm, spl or ipl nb file to bin file.
They are all command line tools, and easy to use.
if you want to convert os.bin to os.nb, you can type:
Code:
bin2nb os.bin os.nb
and then, you will get os.nb file.
when you want to convert os.nb to os.bin, you can type:
Code:
nb2bin os.nb os.bin
you will get the new os.bin file.
The default setting is Typhoon(Feeler/Amadeus), if you want to convert other device nb file to bin file, you can add two parameters:
Code:
nb2bin <file.nb> <file.bin> [offset] [partbytes]
offset is a hex number without prefix, for example, the offset of Typhoon is 80240000.
partbytes is the size of the partition, it is also a hex number without prefix, for example, the partbytes of Typhoon is 1b00000.
Excuse me,
I've a Toshiba G900, I've used the Grab_it tool to create a DUMP of the ROM.
I obtained a "dump.bin" file.
Now I've to create a .nb file from this .bin file.
Do you thing your tool could works?
I've to imput a different code becouse my device is not a Typhoon?
I hope you can help me.
Thanks.
davideuck,
Have you solve your problème? Because i have the same and bin2nb doesn't work for me (My device is a Samsung Player Addict)
Thank,
McCoy.
it doesn't support diamond NB files.... anyway, thanks
Hello developers,
maybe some people know, that there is a new TG01 section in this forum.
I personally own this phone and like it very much. Only the Rom that Toshiba provided us isn't very good and stable. It has many problems, that need to be solved
The friendly guys of WMPowseruser told us, that they want to try to cook a Rom for the Toshiba TG01.
But until now nothing happens, because nobody knows 100% sure what is needed to be done, to get a working Rom for the TG01 cooked...
So I decided to gain more information about the Rom Development process for WM-Phones.
I want to ask you what is needed to get a working cooked Rom for our Phone.
Do we need a Hard-SPL? Or do we need to extract the Rom out of our TG01, decrypt it so that we then can cook a new Rom?
You may notice, that I'm not an expert on this topic, so I rely on your help.
There is already a tool made by the member Cotulla to encode/decode TSW-files. http://cotulla.pp.ru/Misc.html
And it is also possible to flash every Rom that Toshiba provided us with this method:
http://forum.xda-developers.com/showpost.php?p=5405267&postcount=325
So it's possible to flash for example a german O2 Rom on an english TG01 that has the Orange UK Rom originally on it.
But I don't know if that helps us for our development.
We already gained 250$ for the development and I think that we're also able to gain even more money if it's needed!
We need serious help
I thank you in advance for your answers to this thread!
Every answer is welcome.
I also wish you a nice remaining Sunday!
Best regards,
Manuel
agree
TG01 have come to market for almost 1 year, hopping the cooked rom can be made early!
TG01
TGO1 MAIN bin file needs decrypted then it's full speed ahead
we need an experienced hacker
TG01
can the mods sticky this post we need it's full attention!!
Ok here is the acutal development status:
Progress of the Project WM6.5.3:
- With SDDL+ made by stepw we can flash any Rom on the TG01
- With Cotullas Tool we can decode/encode .tsw files
(The .tsw file is the file, that Toshiba offers to download from their homepage to update to WM6.5.3...so these .tsw files need to contain the whole OS and all system files that are needed to run the TG01)
Cotullas Tool can make a .bin file out of the .tsw file that we got from Toshiba.
But there are two problems with that:
1. We cannot be sure, that the Decoder works 100% right.
2. The .bin file we get when we use Cotullas tool seems to be not normal. We cannot extract it.
If I open it with Isobuster than I first see only the one track is included in the .bin file.
But then I let Isobuster search for more files after their signatures in the .bin file, Isobuster finds the following files:
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
But for example the .cab files can't be extracted...it tells my, that the archive is damaged.
Well and we cannot be sure, that the above written files are the only content of the .bin file. Maybe Isobuster didn't find the others that are included in it...
So what we need:
- A person that understands the format of the .bin file (unencrypted .tsw file) so that we can extract the .bin file properly and get all of the system files and the OS out of it.
After that we can modify the files and create a new .bin file with the modified files included. Than we only need to encode it again, so that we have an flashable .tsw file again.
We could flash the new .tsw file with the SDDL+ made by the user stepw.
It would be very nice if someone would answer me and get in contact with me, that can help us to get a working WM6.5.3 Rom onto the TG01.
Thanks in advance!
I wish all of you a nice remaining Sunday evening!
Best regards,
DunkDream
hello,
to extract the rom, i used the raw-files.
i used "itsutilsbin"-tools. after dumping i get an extractet oem/sys-folder with known (typical) foldercontent and -structure.
here is a list of extractet raw-files
View attachment luste.zip
any lately news?
waiting...h
bird_9527 said:
waiting...h
Click to expand...
Click to collapse
The problem is in the nb0 file generated after using the cotulla tool.There are some extra bytes with checksum..i think only cotulla can make it possible.I tried manually with hexeditor..it fails..in short, we need another tool/program which can remove extea bytes, give us the normal nb0 file, which can be dumed recompiled and repacked with those removed extra bytes with the sme or modified checksum.Then we can have the custom ROM.
hi everyone
i try to use osKitchen but i had one prob. i can not understand MK folder how to create define.text ? pleas help coz i want to cook rom
i did MK forder but kernel not select
see sum screenshot from attachmens
Don't use oskitchen cooking roms for Opal.
There are some issues that haven't fixed yet.
If you cooking a nbh successfully,there is a flash write error at the end of the flashing.
define.txt.txt-->define.txt
My phone is: OPAL, but the use of OSKITCHEN decomposition, packing the official ROM is normal, but after the computer prompt Brush "226" error code, the phone automatically restart, direct access to three color screen and an error ~! Is this software does not support this type of phone models OPAL?, I use software version is 1.25, my phone model is: OPAL (HTC VIVA), still issue I found our handset, XIP using a OS.NB, not OS.NB.PAYLOAD . there any way let OSKITCHEN use OS.NB to customize ROM?