Related
Any brave soul try using mkrom in conjucntion with the 2003 ROM? I think I might give it a shot here in a bit but wanted to know if anybody had tried it yet...
I've managed to build a 2003 ROM. It's extremely tricky though. I'm working on customizing a ROM similar to the XDA Developers SER - as soon as I get some free time
I'd like to acknowledge all the help given to me by Developer Itsme in this endeavor.
Let me know any suggestions you may have for the new ROM.
sheran_g,
i didn't know u could use mkrom with 2003 rom image. can u please post how u did it? i created a special version based on SE 1.1 rom but would like to put the same programs into the new rom. any help is appreciated.
thanks
alex
sheran_g said:
I've managed to build a 2003 ROM. It's extremely tricky though. I'm working on customizing a ROM similar to the XDA Developers SER - as soon as I get some free time
I'd like to acknowledge all the help given to me by Developer Itsme in this endeavor.
Let me know any suggestions you may have for the new ROM.
Click to expand...
Click to collapse
What's tricky about it...?
The modified registry file you make does not get picked up at the device startup. You need to manually inject the memory address of the modified registry file into the ROM in order for it to get picked up.
my latest romtools can be found at romtools
now it calls dumprom to find and fix the filedata offsets.
I think they should now build 2003 roms.
sheran_g,
can u post the steps that u take to buid it? i'm trying right now and its not working. i'm having little problems. can u post ur default.reg and initobj.txt? any other help is apreciated.
thanks
alex
Ok. Here they are in a nutshell:
Get the latest romtools.
Make the following dirs: romfiles, cfg, tmp, out, files, files1, files2
Split the ROM into Bootloader, bootimage, OS image, xipchain into the 'cfg' dir.
Dump the files in the OS image into a 'romfiles' dir.
Get the default registry file, initobj & initdb files into your 'cfg' dir.
Make changes to your default.reg and initobj.txt
Place any files you want loaded in the ROM into the 'files' dir.
Run 'mkrom.sh'
You should then have your new ROM. I'm sorry if it's extremely brief; you'll have to make do with this and the README file in the romtools archive file for now. You'll find my default.reg and initobj.txt files on my site: www.zensay.com/qtek/mkrom
sheran_g,
Have you created a decent working custom WM2003 ROM?
If so what Apps have you added?
How much ROM space does it use?
I've not added any apps to my ROM. I have only added a carrier logo file and made some changes to the registry. So I cannot comment on ROM space yet. The ROM works fine.
sheran_g,
what command did u use to extract rom files? did u do it under windows or unix?
I'm having problems trying to dump the rom image. I don't know if its too much to ask, but can u zip ur directory and post it somewhere so i can download it? or if u can post commands that u ran to dump the 2003 rom?
thanks
alex
Hi,
could you include "O2 home zune" to the 2003 image, like in the 2002 3.19 GER. Its for Germany interested only!
AR :?:
home zone depends on specific 3.19 rilgsm features. which are not in 4.*
okay, used dumprom -4 -d files -q nk.nbf and extracted all files. Got could not find pointer for ofs 00000000 ERROR but all the files seem to be there. Trying to figure this out. Saw the above abreviated directions but am fumbling around. Anyone have concise directions?
Val
Anyone? Just give me a good hint then please.
Hi all!
When i overwrite the rilgsm.dll file in the t-mobile 4.0.10 image with the rilgsm.dll from the O2 GER 3.19 image, i could use the "O2 home zone" option with the hz.exe in Starup directory? rilgsm.dll from german image hes 'at+creg=2' string in it. probably the RIL_GetCellTowerInfo call is now implemented. When it can work, how could i write the german rilgsm.dll to the image? I haven't linux, could somebody cook the image for me?
here is the germen rilgsm.dll and the hz.exe for the "home zone" funktion! http://www.nokiaprog.de/XDA/home_zone.zip
THX
PS: Sorry, my english! ;-)
AR
the homezone enabled rilgsm.dll depends on other dll's and exe's.
probably ril.dll, stk.exe, cell*.dll and maybe more, I have not tried
replacing all.
you don't need to build a new rom in order to experiment with this, you
can just copy the desired files to \windows, to override the rom versions.
And I don't think it works with the RIL_GetCellTowerInfo call,
but adds some notification events.
to change the CREG setting you need to call RIL_DevSpecific with parameter 25 ( to turn it on ) or 26 ( to turn it off )
even though that does not seem to be how hz.exe does it.
Hi,
I opened the image file in the Hex editor and renamed the file there rilgsm.dll. Then I flashed the image, which was phone probably deactivated, because rilgsm.dll was missing. Then I copied over ActiveSync the German rilgsm.dll into the Windows directory, XDA reset and he not accept the file. I assume because the file was not in the EPROM memory! Therefore I wanted to have rilgsm.dll first times in the image!
AR
XDA developer Itsme said:
my latest romtools can be found at romtools
now it calls dumprom to find and fix the filedata offsets.
I think they should now build 2003 roms.
Click to expand...
Click to collapse
Is there any other way i can access this site or I can download this files, the sites are block here in my country, Please Help
Ronnie
Hey Guys,
Do you know if anyone has defined what each of the files are in the Extended ROM for the T-Mo Vario? And if so could you point me in the direction.
Thanks,
Alex
You can extract cab files by yourself and look what each of them contains. For extracting cabinet you can use for exapmle Wince cab manager app.
I think the poster means not just file names but what they can do... I can access the ROM but only guess what each one does.
The read me just gives the file names and thats it.
Terran
PS I'm intrested too
i didn't mean to guess what cab does according to its name, but to extract files from each cabinet and look on them.
Most of them includes only some settings to the device's registries.
For example, CAB-Customization-TMCZ-Wizard-01-04-03Oct05 includes 4 files:
CeSettup.dll
CheckFiles.exe
Customize.lst
Platformxxx.reg
By looking into the Platformxxx.reg you can easily see this cab sets MMS and GPRS..
Thanks for the input. Although I believe there is probably some uneeded files in there, my device has been running smoothly, so I will probably just let it be until I hear otherwise.
Cheers
As we know, to upgrade ATOM ROM we have to lauch an exe file downloaded from seeo2.com. But we cannot extract any file from this exe file except Boot.nb0 and this file is useless. Does anyone know how to extract other files from it. As I know, there are at least following files inside this exe file:
eboot.nb0
dm.nb0
flash.img
agent.mot
mot.mot
CPLD.img
assetinf.img
extended.img
MDOC.img
Its strange that there is no .nbf file at all. Is there any method to dump the ROM from a working ATOM? Can the Grabit utility grap ATOM ROM to SD? Will it be usable ?
I have dumped it already and uploaded here, but i do not remember are the files you search there.
Tamagochi said:
As we know, to upgrade ATOM ROM we have to lauch an exe file downloaded from seeo2.com. But we cannot extract any file from this exe file except Boot.nb0 and this file is useless. Does anyone know how to extract other files from it. As I know, there are at least following files inside this exe file:
eboot.nb0
dm.nb0
flash.img
agent.mot
mot.mot
CPLD.img
assetinf.img
extended.img
MDOC.img
Its strange that there is no .nbf file at all. Is there any method to dump the ROM from a working ATOM? Can the Grabit utility grap ATOM ROM to SD? Will it be usable ?
Click to expand...
Click to collapse
When you double click the exe file, it will extract files to Windows\Temp foler, files are all hidden.
I'm not sure if this is correct, but I was provided with
Xda-Atom-ENG-20060123_Feb2006_.exe
Double click. This will extract to your root drive
c:\
Device Software Update Utility.exe
diskimage_Ver.nb0
Extendedrom.img
nova_pda_033105.mot
vl1d_pda_Ver.mot
Extendedrom.img can be opened with winimage.
diskimage_Ver.nb0 - can't remember how I dealt with it, but in the "usual" ways I guess! Mamaich's romtools I suppose. Thanks Mamaich!
If anyone can, I could still really do with a live rom dump, using this app:
http://www.vijay555.com/vj/!Tools/dump_167.exe
I'm not sure if it works on the Atom, but I'd be grateful if someone could try it and let me know. A couple of nice guys have tried and failed
V
Vijay dear friend..
like i told you before...
the DUMP didn't work..
but you have the lastest rom.
any way, in a week or so, a new rom is about to come out, may the new rom could be dumped...?!?
Nadavi..
Exactly assasins, and I'm really grateful for the info.
I've dumped the rom file above, but a dump from the rom isn't the most useful ways to get files out of it. Some files aren't usable from there, so a live dump is best. But not to worry, I'll live without for now.
Oh, but I could still do with an atom registry dump if someone can send me that... gracias!
V
vijay555 said:
I'm not sure if this is correct, but I was provided with
Xda-Atom-ENG-20060123_Feb2006_.exe
Double click. This will extract to your root drive
c:\
Device Software Update Utility.exe
diskimage_Ver.nb0
Extendedrom.img
nova_pda_033105.mot
vl1d_pda_Ver.mot
Click to expand...
Click to collapse
Anyone know how to edit the mot files?
vijay555 said:
If anyone can, I could still really do with a live rom dump, using this app:
http://www.vijay555.com/vj/!Tools/dump_167.exe
Click to expand...
Click to collapse
dear vijay555
is this suppose to wirk with ETEN M600
it runs ok but I don't no ware it extract files
thanx
I think it extracts them to a folder on your sd card, called Dump.
If you've got an eten dump, I could do with one of those as well.
I didn't write this app - I can't even remember where it came from. If anyone wants to volunteer as the author, I'd like to know more about the app!
V
Will I think it's not working hear
noyhing in my SD or TMP folder
thanks for your help
Regards
Guys, what's the storage card called on the Atom?
Is it still called \storage card\?
V
xda atom
its called memory card.
is there have such tool like HTC mtty for Atom?
Hi all.
I started using MSDevice emulator v1.0 to check some programs before I put them on my QTEK.
Atm,I'm trying to install the OS from Faria rom to the device emulator.
The emulator uses images *.nb0 and I'm having *.nbf rom
The tool on the FTP site (nb2nbf) does the exact opposite thing from what I want .
Can someone tell me how I can extract the nb file from eg Farias rom? {edit -found correct programs -check below}
Will farias hacks & customizations work ?
Is the device emulator a reliable program to test applications?
Also, I found somewhere in the internet some skins/localisations for the qtek for using in the dev emul but I can't remember where. I'd appreciate if someone could post a link.
Thanks
Note to moderators :I wouldn't like to add these kind of questions on the Windows mobile specific topic because I'm interested more in reliable wizard emulation. If you think I posted in the wrong place you can move it somewhere more appropriate . Thanks again
There are related links to this topic related links.
Beta: WM5 ROM editing tool
http://forum.xda-developers.com/showthread.php?t=249836&highlight=imgfs
extracting nk.nbf :
http://forum.xda-developers.com/viewtopic.php?t=33321
HI jtrash, did you find out the solution to run Wizard Rom in the device emulator?
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.