My Device is: I-teq X-bond equal to (Gigabyte gsmart-i64)
Its original OS is WM5 2.3 with original NB0 extention and Here is the official ROM link:
http://www.gigabytecm.com/eng/Downlo...=17&tabIndex=3
I can extract OS.NB from original file but the problem is that I do not know how to Repack and convert new OS.NB to a proper .NB0 file.
So I need your help
My Thread seems to be dead but still I did not find the answer
I google searched about the problem and I found a tool in Modaco, o2util.exe but I do not know that is a proper tool for my goal or not
Nobody here can help me?!!!
At least try to post a working link, as I can't find gsmart-i64 on gigabytecm.com or it's just gsmart-i?
Spiaatie said:
At least try to post a working link, as I can't find gsmart-i64 on gigabytecm.com or it's just gsmart-i?
Click to expand...
Click to collapse
OK Thank you very much for your reply, you are right gsmart-i is equal to gsmart-i64, so you can go ahead with it.
I already did that, but to download a ROM file I must to sign-up and IMEI is required, so I can't download ROM.
Can you upload it somewhere, like 4shared.com or Megaupload.com?
Spiaatie said:
I already did that, but to download a ROM file I must to sign-up and IMEI is required, so I can't download ROM.
Can you upload it somewhere, like 4shared.com or Megaupload.com?
Click to expand...
Click to collapse
I've sent my IMEI no. to you by private message. if u need it to upload let me know.
mechhadi said:
I've sent my IMEI no. to you by private message. if u need it to upload let me know.
Click to expand...
Click to collapse
Received your PM, downloding file now.
So step by step:
Take shippend ROM and prepare it for kitchen:
Code:
osnbtool -sp ROM.nb0
you will get two files ROM.nb0.PRE and ROM.nb0.OS.NB
ROM.nb0.OS.NB is OS.nb file you need to use on your kitchen.
After you have done ROM building with kitchen you should get OS.nb file.
Now use osnbtool to insert extra data:
Code:
osnbtool -extra OS.nb
You will get file OS.nb.EXA and now you need to make ROM.nb0 file:
Code:
copy /B ROM.nb0.PRE+OS.nb.EXA NEW_ROM.nb0
I hope this works
Thank you very much for your complete info, These days I'm on vacation.
As soon as possible I'll check the process, but I should say that the very first step for me is to convert back generated OS.nb by osnbtool to newrom.nb0 and check the file with original ROM. however I will let u know my progress and thank u again for your time and help.
Spiaatie said:
So step by step:
Take shippend ROM and prepare it for kitchen:
Code:
osnbtool -sp ROM.nb0
you will get two files ROM.nb0.PRE and ROM.nb0.OS.NB
ROM.nb0.OS.NB is OS.nb file you need to use on your kitchen.
After you have done ROM building with kitchen you should get OS.nb file.
Now use osnbtool to insert extra data:
Code:
osnbtool -extra OS.nb
You will get file OS.nb.EXA and now you need to make ROM.nb0 file:
Code:
copy /B ROM.nb0.PRE+OS.nb.EXA NEW_ROM.nb0
I hope this works
Click to expand...
Click to collapse
Thank u for your detail described process. I followed instruction and generated NEW_ROM.nb0 with generated OS.NB from the first step, but the volume of NEW_ROM.nb0 is different from original ROM.nb0, would u please tell me this is normal or I did something wrong or the generated NEW_ROM.nb0 is usable.
My problem is still persist and I can not reconvert extracted OS.nb to original ROM with nb0 extention
The most famous forum for WM is here, but still my problem has not solved.
Please somebody help!!!!!!!!!!!!
I used osnbtool to extract os.nb from original rom with nb0 extention. but the problem is I can not use osnbtool to use os.nb and generate rom with nb0 extention.
My request here is that is there any other tools that I can figure out my problem or because creator of osnbtool.exe is a chinese guy-WEISUN-, need someone chinese to ask my problem from Weisun.
thank u for your consideration and help
Still no progress?????!!!!!!!!!!!!!!!!!!!!!!!!!
Here are many chefs but no one can help.
As I know XDA forum is the best forum for WM but it seems that they do not consider any other devices except HTCs.
Related
Hello my friends !
I search how cooking rom from a bin file of 32M !
I know how do it from a nbh file or nb file, but i don't knwo how to do from a bin file !
Which tool using ?
Great Thanks !!!!
you need imgfstools2 to extract the bin / recreate a nbh
Thanks for you fast answer !
So i will re-tets with imgfs2rc2, but i think that i don't function
I re-test !!!
from the readme
ReadMe said:
On a high level, this is the chain of actions needed to unpack OS.nb:
RUU-signed.nbh ---(*NBHExtract)---> OS.nb ---(NBSplit)---> OS.nb.payload -->
--(ImgfsFromNb)---> imgfs.bin ---(ImgfsToDump)---> 'dump' directory
Here you'll edit the 'dump' directory. I recommend using bepe's excellent *Package Tool for this.
The reverse process is:
'dump' directory ---(ImgfsFromDump)---> imgfs-new.bin ---(ImgfsToNb)--->
OS-new.nb.payload ---(NBMerge)---> OS-new.nb ---(*NBHGen)--->
RUU-signed-new.nbh
(The tools marked with '*' are not part of the ImgfsTools, but are also available for free from xda-developers.com. There is also one additional tool, NBInfo, in this package.)
Click to expand...
Click to collapse
With imgfs 2.1 RC, I use :
imgfstodump winceimg.bin
And i result :
"Cannot map file winceimg"
Nixeus said:
With imgfs 2.1 RC, I use :
imgfstodump winceimg.bin
And i result :
"Cannot map file winceimg"
Click to expand...
Click to collapse
sorry i just knew what tools to use - im sure someone else can help you further though.
I will continue to investigate !!!
thanks'' !!
I used all the keywords imaginable, i read all the treads that was talking about something that use the words i'm looking for even if the subject wasnt in link. There is absolutely 0 treat talking about dumping a shiped rom. Hypercore need that you place your rom in the Hypercore/extract/source forler but when i run DumpRom.exe it says i need OS.nb file and when i hit enter it says there is no OS.nb file in the file. So what am i gonna do with my shiped.exe rom? Its a wm6 french and i fermly want to keep it and work on this one instead of taking anything that people already worked on and have no idea what as been made to it. Please, someone, is there any way to get the OS.nb from HTC_P4350_FRA_4.17.406.2_4.1.13.44_02.94.90_Ship.exe ????????
Hi there,
i would like to try to make a hybrid rom with an omnia rom.
Can anyone explain how to extract the exe file.
I downloaded the rom from kaiser rom dev section.
Its the normal update file from Samsung
Thanks in advance
C'mon guys, no one around here knows how to get the rom out of that file?
JeckyllHavok said:
C'mon guys, no one around here knows how to get the rom out of that file?
Click to expand...
Click to collapse
Get winrar or something, right click on the exe and click extract here?
veyka said:
Get winrar or something, right click on the exe and click extract here?
Click to expand...
Click to collapse
thats not the way for Omnia's ROM
the procedure is as follows:
1. check out this post.
2. after step 5, download this and use viewbin.exe to find out the start offset and length of imgfs.
3. use cvrtbin -r -a (start offset, don't use '0x' prefix) -l (length of imgfs, don't use '0x' prefix) -w 32 xxx.bin
4. after this u will get an nb0 file. use nbsplit with -kaiser switch on the nb0 to get xx.nb0.payload
5. use prepare_imgfs.exe xxx.nb0.payload -nosplit
6. use view_imgfs.exe or imgfstodump.exe to get the 'dump' folder.
thats not the way for Omnia's ROM
Click to expand...
Click to collapse
Yes, you can't open the file with winrar or zip.
Its not just a self extractin file.
It doesn't create temp files, too.
JeckyllHavok said:
Yes, you can't open the file with winrar or zip.
Its not just a self extractin file.
It doesn't create temp files, too.
Click to expand...
Click to collapse
check out my post above for the procedure
PS: i didn't learn this procedure myself, so i don't take the credit.
Hey man,
thanks for your answer, but i can't find B000F in the file.
I use WinHex
JeckyllHavok said:
Hey man,
thanks for your answer, but i can't find B000F in the file.
I use WinHex
Click to expand...
Click to collapse
B000FF is in ASCII (text). search again, it must be there 3 times
OK now i found it but i don't understand part 3 of the manual.
The string 0x060000EA3B is in Hex 30 78 30 36 30 30 30 30 45 41 33 42, right?
But i can't find it.
htctouchp said:
thats not the way for Omnia's ROM
the procedure is as follows:
1. check out this post.
2. after step 5, download this and use viewbin.exe to find out the start offset and length of imgfs.
3. use cvrtbin -r -a (start offset, don't use '0x' prefix) -l (length of imgfs, don't use '0x' prefix) -w 32 xxx.bin
4. after this u will get an nb0 file. use nbsplit with -kaiser switch on the nb0 to get xx.nb0.payload
5. use prepare_imgfs.exe xxx.nb0.payload -nosplit
6. use view_imgfs.exe or imgfstodump.exe to get the 'dump' folder.
Click to expand...
Click to collapse
Great! it works for me. In my case I had an img file (I presume that some one extracted from exe). If you run GrandPrix flahs utility and load this .img file you get a _xip0.nb0 that can be used as xxx.bin as stated above.
btw, how can we extract xip? Failed to extract with dumprom/rommaster the payload file generated in step 5...
hey guys,
no luck with the above procedure.
i Made a bin file starting at B000FF and finish after the 12 "00" before
060000EA3B .
But cvrtbin gives the error "Could not allocate memory for raw data"
Please Help
g77 said:
Great! it works for me. In my case I had an img file (I presume that some one extracted from exe). If you run GrandPrix flahs utility and load this .img file you get a _xip0.nb0 that can be used as xxx.bin as stated above.
btw, how can we extract xip? Failed to extract with dumprom/rommaster the payload file generated in step 5...
Click to expand...
Click to collapse
sorry, i didn't work on extrating xip.bin from the 'exe', didn't get time to.
JeckyllHavok said:
hey guys,
no luck with the above procedure.
i Made a bin file starting at B000FF and finish after the 12 "00" before
060000EA3B .
But cvrtbin gives the error "Could not allocate memory for raw data"
Please Help
Click to expand...
Click to collapse
thats the only procedure which should work for u. just follow/read everything carefully and also make sure u downloaded the cvrtbin.exe from the link that i gave (msvcr80.dll should also be there).
Thanks for your answer, i made the mistake that i just cut the unneeded lines and save it as an other filename. When i copy the lines in a new file it workes
JeckyllHavok said:
Thanks for your answer, i made the mistake that i just cut the unneeded lines and save it as an other filename. When i copy the lines in a new file it workes
Click to expand...
Click to collapse
could you zip that .bin up and upload it please?
i'm having a ton of trouble with this
anybody?
sorry to be a nag
There's a thread in modaco.com where they are extracting the ROM with a P535 kitchen. You can join in the funs there
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.
Hello all,
Is it possible to dump a .BIN rom ?
I've search before asking, but i did not find the answer. Thank you in advance.
Talonette said:
Hello all,
Is it possible to dump a .BIN rom ?
I've search before asking, but i did not find the answer. Thank you in advance.
Click to expand...
Click to collapse
To dump a .BIN ROM you need:
- OSNBTool
- XIDUMP
Run "OSNBTool -sp" on the .bin file once and you'll obtain a NB0, run it again and you'll obtain a NB. Run XiDump -B on the NB file and you will obtain the xip and imgfs dump .
Thank you very much
Perfcect answer, thread solved but opened if requires to ask more
Error while dumping the .bin ROM image using osKitchen Zero
i am getting an error while dumping the .bin ROM image using
osKitchen Zero v1.30.
osKitchen Zero uses OSNBTool; XIDUMP to dump a .BIN ROM.
The error description is attached as image.
Also the log file of the process.
It successfully extracts the original .bin ROM to folder
BIN to NB Conversion\
Rom.bin.BIN.NB0.OS.NB
Rom.bin.Footer
OS Sections\
imgfs.bin
uldr.bin
xip.bin
OS Sections Dump\
IMGFS\
OEM\
SYS\
While extracting the IMGFS.BIN it ends giving the error.
i am using the following ROM. Both the ROMs in the following post ends to the same error, couldn't complete the import process.
forum.xda-developers.com/showthread.php?t=579639
[sorry i cant write it as a link, its disabled for new user]
kindly suggest whats going wrong.
how can it be fully extracted w/o error.