Problems applying Bigstorage to 1.12.188.11210 - JAM, MDA Compact, S100 Software Upgrading

Ok, so I've done my research and am perplexed by two significant things. I applied the update 1.12.188.11210 since I'm on Rogers in Canada and need the 850 band support. No problems applying that and things looked good so far.
I've tried following two methods to do this and am running into 2 problems.
According to Ampda's walkthrough, I should see a ROM dump that looks similar to the BigStorage ROM that you open up with the hex editor. My first indication something might be wrong was that my dump did not have MAGICIAN in the first line of the ASCII translation of the HEX. Still I tried to follow the instructions and copied and pasted the 416 bytes into the new file and it did not apply.
Afterwards, I tried drchair's method of manually editing the hex values and reapplying that. Interestingly enough I only found 1 sequence of hex values that matched, and tried applying that and that also failed. I'm not certain why I only found one matching set of hex values and not the 2.
So I'm a little stumped and at a bit of a crossroads since it seems that my Jam's ROM dump for some reason or other doesn't look like what it should according to what other people have posted.
Has anyone else run into this problem, or possibly does anyone have some suggestions I can try?

Don't flash your magician with your dump, probably it will NOT work. Your story seems like my first attempt & that was no success.
I guess 1.12.188.11210 is a shipped-rom in .exe format, so try this:
get nbfdec.rar
http://forum.xda-developers.com/download.php?id=7603
get maupgradeut_noid
http://forum.xda-developers.com/download.php?id=7508
If the link is broken go to this thread & get both files: http://forum.xda-developers.com/viewtopic.php?t=32274
1. Unzip the shipped-rom to get all the .nbf & enterbl.exe etc.
2. Put NBFDEC in the same directory as the unzipped shipped rom files
3. Copy the getdevicedata.exe to your Magician and execute to write DeviceData.txt to \Windows and view with notepad
5. Decode nk.nbf -> nk.nb1:
nbfdec -d nk.nbf nk.nb1
6. Hexedit header in nk.nb1 to correct ID from DeviceData.txt
(probably only if using a rom from other provider, you can skip this step as you already installed the same rom as you're patching now)
7. Replace pattern for bigstorage in hexeditor (still in fike nk.nb1):
locate the 02 00 00 80 00 20 and change 80 00 to b8 01 in the nk.nb1
(use binary search for this!!)
7. Encode nk.nb1->nk.nbf
nbfdec -e nk.nb1 nk.nbf
8. connect your magician with usb
9. run maupgradeut_noid.exe to upgrade CE image
Also, this way you will save the contents of increased \Storage folder if previous rom was bigstorage one
Usage sample (must be run from the same folder as nbf files or specify full path):
nbfdec -d nk.nbf nk.nb1
nbfdec -e nk.nb1 nk.nbf
This method is the most simple I belief & works great.
Refards, M

Thanks, I will give your instructions a shot and let everyone know how it went!

Should be going fine, many took this road & succeeded. Including myself.
M

Actually, I feel a little sheepish...
After you had posted your instructions, I started to see you had posted this in a few other threads and realized I should have been reading a little more carefully and tried this as another method.
Sorry to everyone for being a bit of a newb and thank you for being patient oltp and reposting this information for me in a place where I could not miss it.

No harm done, after loosing my patience about posting this info over & over again & helping some Dutch guys in native Dutch I just have this info in a file. So I can copy/paste the required text & everybody's happy.
I know the board is growing fast & it's sometimes ally hard to find the required info, mostly finding the correct keywords helps but then again you're probably overwhelmed by hits.
& most of all I guess that's everybody has the right of his/her own noob time. Mine is still going on as I'm still finding handy small apps (like from VJ always patient too) & loads of other info on the board.
Cheers, M

I don't know if I'm the exception and most people just don't look, but I did find the wiki helpful. If I might make a suggestion for the board, I think perhaps adding your method to the wiki would be a very useful and alternative method to ampda's instructions that are already in there. Ideally, I would direct people to your method first as it seems more reliable since you're dealing with the original install files.
Also, if it's in the wiki, it might get more newbies to give it a shot without askiing.

Problem with the wiki is that I never tried changing it on a magician. I don't use the PC very often @ home, but I can always try. Thanks for the reminder.
& have you achieved BS?

Updating the wiki was dead-simple. Please do me favor & judge whether it's easy to find & correct.
Regards, M
Ps if you can't find it, it's in the howto section

Looks good to me. And yes, your method worked great and I now have BigStorage enabled on my Jam. Thanks for the help!
*Edit* Just noticed one thing that some might get confused about. When you copy over the GetDeviceData.exe file over, it will not provide any gui displays. Not to mention the fact that most newer users won't be expecting an exe to run anyways on a ppc. If you mentioned that, it might avoid some potential questions about it if a user is too lazy to look in the windows dir or look up in the forum about the file.

Thnx, I totally forgot about that fact of running GetDeviceData.exe. Probably I'm too curious I even executed enterbl.exe on my ppc. Works great it goes straight into bootloader.
I'll give the wiki another edit.
M

Related

The Most Direct Method to get BigStorage

So far, we know that BigStorage can be created for 1.11 or 1.12 ROMs by replacing 80 00 with b8 01 at the following two locations:
English version (i-mate JAM, T-mobile compact, etc.)
7e32 and 211e32e
French version (qtek, etc.)
7e32 and 212332e
German version (T-mobile compact, etc.)
7e32 and 213232e
Traditional Chinese version (Dopod 818, O2 Asia, etc.)
7e4a and 1fc232e
Simplified Chinese version (Dopod 818, etc.)
7e42 and 1fc232e
It seems that the two locations change with the language, rather than the brand. Older ROM versions have different locations.
Could anybody provide the locations of other language versions for the reference of those who need them?
Please note that some have reported success in creating the BigStorage by replacing the bytes at the first location only, leaving the second location unchanged.
For those who need a summary of the steps:
1. Dump your original ROM to SD card. (romupdate.exe and ntrw.exe)
2. Edit your own ROM. (hex editor)
i.e. search for the two locations in the ROM with "02 00 00 80 00 20" and replace 80 00 with b8 01.
3. Write the edited ROM back to the Magician and hard reset your machine. (ntrw.exe)
That's it!
- no more downloading of others' BigStorage ROMs
- no need to replace the first 416 bytes
- no more unsolicited splash screens
- a simple, safe, do-it-yourself method to create your own BigStorage based on whatever ROM version you already have or upgraded.
Thank you so much.
I have an Italian ROM. Can anybody give me some help?
Talents,
A good assurance for people....
Nice one
I put this together with bits taken from this forum
Does anyone know if this will work for older versions of the ROM (i.e. 1.03 or 1.06)? I still am having problems with the GPRS with the newer ROMs so I would like to apply the BigStorage to older ROMs.
Thank you,
F
I used this method on the 1.03 wwe version and it is working perfectly. I used the same method as described. Found the two locations made the changes etc. and all is well.
Thanks, I will try it out
NTRW PROBLEM
Everytime i try to run NTRW
i get the following message
USAGE: NTRW FILE DRIVE:
and it doesn't create a file
what am i doing wrong?
Re: NTRW PROBLEM
micha said:
Everytime i try to run NTRW
i get the following message
USAGE: NTRW FILE DRIVE:
and it doesn't create a file
what am i doing wrong?
Click to expand...
Click to collapse
You seem to have an old version of ntrw. Get the latest one (2.0) from this forum's FTP server.
Cheers
Daniel
Worked for me with French_11202_125_11210 8)
The first reboot took more than 5 min though.
glad to know that it works on your French ROM.
We should have warned everyone to be patient with the first boot up after upgrading. It takes 5-10 minutes to format the BigStorage, with the screen apparently "stuck" at the splash screen.
I've found a .nb1 file for BigStorage on the ftp server of this forum. I think it's the BigStorage version for ROM 1.12. Is it possible to use that file and enable BigStorage without a cardreader?
For example, when you execute the upgrade program an TEMP directory is created with a bunch of files in it. If I were to copy those files (which also include some .nb1 files) and replace one of those with the one I found on the ftp, would that give me BigStorage?
Welrogie,
I was actually thinking the same thing as you...
Although if it were possible, I'm sure someone would have posted somewhere on this site anyway (?)
BigStorager work great for 1.12 FR ROM
many thanks
your post is excellent, did it to a 1.12 and no probs, please just check the pdf instruction sheet as it mentions 2 different file names, 1 to download from SD card and another to upload, maybe I misread it but I just uploaded the modified version of the file I downloaded and it all went swimmingly. cheers
Just carrying out a few 'test' searches on rom files to locate the necessary information...
On the 3 that I have performed the search on, i seem to find the bytes ok but the locations never matches the one stated by Talents and others. Does it matter that they appear in different locations than the ones specified?
Thanks.

Storage Problems for a non developer

Hi
I know there are lots of people asking how to save space and mostly they get told to use 'search' and check the stickys.
I'm a keen gadget lover but have no technical background. I have a 64mb Tmobile MDA (with the horrible branding) and the following setup:
R 1.00.10
G 1337.36
D 1.01.00 WWE
I've heard/seen references to big storage etc but I don't really understand it.
Can someone either give me:
- a really simple way to update my rom etc, or
- suggest another way to delete stuff that I won't need (don't want to delete stuff only to find half the programs no longer work)
- explain the easiest way to get rid of all the Tmobile stuff
Many thanks in advance
To prevent the Branding stuff from loadibg you must hard-reset your magician (backup first!!) and after the initialization (calibration etc) you must soft-reset just before the customization starts. You got about 3 to 5 seconds to press the softreset, so when your screen reads 'tap screen to start using ....' you put the stylus in soft-reset hole & then tap the screen. As soon as the default blue WM background appears you press the stylus to soft-reset.
Now you got a plain WM2003 device. & you got the ext-rom visible, not editable, so you can explore it & choose what to install. Network settings for gprs is set by one of the ext-rom cabs.
To gain more storage you can move camera & album from \windows to storage folder. Remember to change shortcuts & registry as well. This saves ariund 1MB. More is possible: I've got < 8MB ram memory allocated to installed stuff with almost all ext-rom cabs installed. Yes I moved a lot.
To gain BIGstorage you can follow instructions below, but first you should get more familiar with the magician I guess. You can save your ext-rom cabs though & update to rom 1.13
url in instructions. To upgrade you just connect the magician to usb & start the downloaded shipped-rom & follow the instructions. Make a backup first & write down your gprs settings, caus you'll have dutch ext-rom cabs after the update. They're in English but contain dutch TMO settings.
Instruction for BS:
- Get nbfdec.exe from the thread 'Upg to 1.13 WWE ROM (with 1.13 Radio) in 10 easy steps!' @ http://forum.xda-developers.com/vie...&start=0&sid=75c5e40168a22052fb7c5554bddd68c2
- get maupgradeut_noid.exe from the ftp
- Download the shipped rom from:
http://www.t-mobile.nl/zakelijk/htdocs/page/service/mda_compact_upgrade.asp
- Download the Hexeditor from:
http://www.hhdsoftware.com/hexeditor.html
1. Unzip NL_11300_131_11200.exe (or any other shipped rom)
2. Put NBFDEC in the same directory as the unzipped shipped rom files
3. Copy the getdevicedata.exe to your Magician and execute to write DeviceData.txt
to \Windows and view with notepad
5. Decode nk.nbf -> nk.nb1:
nbfdec -d nk.nbf nk.nb1
6. Hexedit header to correct ID from DeviceData.txt
(probably only if using a rom from other provider)
7. Replace pattern for bigstorage in hexeditor:
locate the 02 00 00 80 00 20 and change 80 00 to b8 01 in the nk.nb1
(use binary search for this!!)
7. Encode nk.nb1->nk.nbf
nbfdec -e nk.nb1 nk.nbf
8. run maupgradeut_noid.exe to upgrade CE image
Also, this way you will save the contents of increased \Storage folder if previous rom was bigstorage one
Usage sample (must be run from the same folder as nbf files or specify full path):
nbfdec -d nk.nbf nk.nb1
nbfdec -e nk.nb1 nk.nbf
Regards, M
Many thanks OLTP for your reply....perhaps it's me but I still find that quite technical....when I have to rename stuff etc I'm not sure where it is to do it.
The tmobile branding piece is clear and I'll have a stab at that tonight though.
Perhaps I'm just destined to struggle with memory or buy a 128mb device.
Appreciate you taking the time though - anyone else want to have a pop at help a keen but useless gadget lover !
BS is unfortunately quite technical & this is the easiest way.
I suggest to remove the branding, that will save some storage. get more accustomed to your magician by exploring it without changing.
I can write you some steps for moving files to gain more ram.
maybe in the future you can think about BS again.
Cheers, M
pna: oltp's guide is about the best you'll ever get!
Basically, to debrand, do what he says in the first paragraph. This will remove all the additional TMobile gunk being installed. So, you need to hard reset (which will restore your system to "factory condition", and wipe everything), and then soft reset at the right time. Then you have a nice, fresh clean system. You can then read the board to see what files you might have skipped by achieving this, but frankly, you won't have missed much.
You can get your tmobile settings (for gprs etc) from here:
http://www.buymobilephones.net/sp3_setup.ihtml
FYI, before doing anything, get hold of a copy of GSFinder+ or a similar explorer. You will need it do any kind of installing/renaming etc.
Before venturing into the hardrest/soft reset business, consider if you want to do the big storage hack. Again, oltp's guide is perfect, but first the theory: the Extended Rom is like a small disk stuck inside your phone, carrying "backups" of the tmobile configuration stuff. If you do Bigstorage, it'll free that space for your use, giving you an extra 20mb or so to use for free. You can install stuff in there, and use it as a small, but bigger, disk to store stuff on. There's no reason not to do it, other than it's difficulty:
Difficulty? Yes, it takes some time, but instructions are provided, and clarified by oltp, so just follow the instructions carefully and you'll be fine.
It does require some knowledge, or confidence to learn.
So ideally, you want to:
1. Backup any files you want to keep.
2. Do Bigstorage.
3. Skip extended rom rubbish.
However, before you worry about bigstorage or anything technical, I suggest you just do this: clean up your system as it is now, and then just in future remember to install every program you want directly to your SD Card. If you do that, your system will generally have more than enough memory to run well. You can skip all the bigstorage and extended rom business. It's only necessary for those on a particularly tight memory budget. This should be fine for your needs I think.
FYI: to install onto your SD card, always choose NOT to use "main memory" when installing from your PC, or on the PDA, download and use a great program called cabinstl. That will allow you to install to your SD card.
V
oltp said:
Now you got a plain WM2003 device. & you got the ext-rom visible, not editable, so you can explore it & choose what to install. Network settings for gprs is set by one of the ext-rom cabs.
Click to expand...
Click to collapse
oltp, do you mean I cant rename, move, or delete any of the files in extended rom? So its safe even if they show?
Yes,
The magician ext-rom is write-protected. You can't delete the files. Nor format the space. Try it if you like with the delete of the file which mentions the loadvdisk. It's completely harmless, but if you want to be sure copy all cabs first to sd & execute them from there.
Btw the loadvdisk cab, present in a TMO ext-rom, will delete the loadvdisk.lnk from \windows\startup & that's why the ext-rom is hidden.
Cheers, M
oltp said:
Yes,
The magician ext-rom is write-protected. You can't delete the files. Nor format the space. Try it if you like with the delete of the file which mentions the loadvdisk. It's completely harmless, but if you want to be sure copy all cabs first to sd & execute them from there.
Btw the loadvdisk cab, present in a TMO ext-rom, will delete the loadvdisk.lnk from \windows\startup & that's why the ext-rom is hidden.
Cheers, M
Click to expand...
Click to collapse
ok.
the thing is, i want to edit my own extended rom, so next time i do a hard reset, it wont install unnecessary junk like skype and other customisation. i also want to add programs to it so they autoinstall when i do a hard reset.
any advice?
cheers
Sure,
You can use bal666's tool to convert the ext-rom part of a romdump to a diskimage which you can mount under Windows XP, with appropriate software ofcourse.
Then you can do whatever you want with your ext-rom. Requires flashing of your magician & a hard-reset.
For starters I recommend to skip executing of the ext-rom by applying a soft-reset just before the custmization starts after a hard-reset. This way you won't cripple your device.
M
Many thanks OLTP & vjay555,
The branding thing worked a dream and saved me 6mb.
Now want to do big storage. Have got all the downloads ready but just need a bit more help on the 1-8 settings.
I'm really sorry that I need such basic help - haven't really got a clue what I'm doing but prepared to give it a go - please help.
1. No problem with this...even I can do this.
2. Where is this...I assume I move them to the Magician using explore (through activesynch) - am I right...if so, is there an obvious place that the unzipped shipped rom files will be.
3. Can't find a copy of getdevicedata.exe, Where do i find it, and then how do I execute to write DeviceData.txt
5. Afraid I don't know how to do this
6. Happy to give this a go if I get this far
7. How do I do this
8. Happy to give this a go if I get this far
Also, a little confused in the section after no 8 - what do I do here?
Hope you haven't lost patience with me. Hope to hear back soon.
Cheers
Paul,
I recently updated the wiki (top right link on each forum page & go to the howto part of the magician section) with the BIG Storage from shipped-rom method. This contains some more info than this thread. Pls read it & mail me the remaining questions, you've got my email-address. I'll add some extra help then.
Cheers, M
Trying to download latest UK rom on WIKI site but the link to this ROM is not working: OS 1.12.00 / ExtROM 1.12.131 / Radio 1.12
Any ideas?
Ta
Yep a broken link, pls use this to go to the shipped rom section from the ftp: ftp://xda:[email protected]/Magician/Shipped_ROMS/
Maybe I take the time tomorrow to check some of the links
btw latest uk-rom should be 1.13WWE from TMO.
nm8 said:
oltp said:
Yes,
The magician ext-rom is write-protected. You can't delete the files. Nor format the space. Try it if you like with the delete of the file which mentions the loadvdisk. It's completely harmless, but if you want to be sure copy all cabs first to sd & execute them from there.
Btw the loadvdisk cab, present in a TMO ext-rom, will delete the loadvdisk.lnk from \windows\startup & that's why the ext-rom is hidden.
Cheers, M
Click to expand...
Click to collapse
ok.
the thing is, i want to edit my own extended rom, so next time i do a hard reset, it wont install unnecessary junk like skype and other customisation. i also want to add programs to it so they autoinstall when i do a hard reset.
any advice?
cheers
Click to expand...
Click to collapse
you may want to check this out at htt*://en.pdamobiz.com/en/forum/forum_posts.asp?TID=395&PN=1. it is based on bal666 info. go check it out.
That's about romcooking and can be found herevas well. It's no BS hack.
Yes, it's no BS. But just a little info for nm8 to do ext rom customizations from his last reply.

looking for an upgrade guide

hello, iv just recieved my exec and i am dying to upgrade it to jwrights rom, could someone please point me in the direction of a guide on how to do it? iv had an xda11i b4 but i cant remember how i upgraded that rom, and really dont wanna mess up my new phone!!
also if anyone can give me any tips for various other programs/upgrades that i might want/need please let me know
thankyou
and yes i have been reading the wiki, but it doesnt seem to mention jwrights rom anywhere, and im getting really confused cos in the file i downloaded there isnt any .nbf files??
Well done for reading the wiki. Nobody is likely to give you an upgrade guide because there is too much to know. I'm afraid you are just going to have to read the various threads on Universal Upgrading etc and WM6. In doing so, you will learn how to upgrade and also learn what do avoid and what to do if it all goes wrong.
The wiki isn't specific to a particular ROM - there are threads on his ROMs on Universal Mobile 6.
As for the nbf files, they are there but you're looking in the wrong place. Jwright kindly provided an installer for his ROMs. You have downloaded an exectuable. When you run that it will unpack to provide a large file in a subdirectory of whichever directory is set to be your Temp directory. Whilst the installer is running it tells you that it is unpacking - what it is doing is unpacking the installation files (including the nbf files) to another directory of your Temp directory.
Couldn't have put id better myself )
Mav
apd said:
Well done for reading the wiki. Nobody is likely to give you an upgrade guide because there is too much to know. I'm afraid you are just going to have to read the various threads on Universal Upgrading etc and WM6. In doing so, you will learn how to upgrade and also learn what do avoid and what to do if it all goes wrong.
The wiki isn't specific to a particular ROM - there are threads on his ROMs on Universal Mobile 6.
As for the nbf files, they are there but you're looking in the wrong place. Jwright kindly provided an installer for his ROMs. You have downloaded an exectuable. When you run that it will unpack to provide a large file in a subdirectory of whichever directory is set to be your Temp directory. Whilst the installer is running it tells you that it is unpacking - what it is doing is unpacking the installation files (including the nbf files) to another directory of your Temp directory.
Click to expand...
Click to collapse
Pugme said:
hello, iv just recieved my exec and i am dying to upgrade it to jwrights rom, could someone please point me in the direction of a guide on how to do it? iv had an xda11i b4 but i cant remember how i upgraded that rom, and really dont wanna mess up my new phone!!
also if anyone can give me any tips for various other programs/upgrades that i might want/need please let me know
thankyou
and yes i have been reading the wiki, but it doesnt seem to mention jwrights rom anywhere, and im getting really confused cos in the file i downloaded there isnt any .nbf files??
Click to expand...
Click to collapse
I have written this upgrade instructions the first month I joined. I made it so that computer and PDA newbies like myself would understand and follow it easily. Here it is: http://forum.xda-developers.com/showthread.php?t=269118

how can I cook a ROM by myself?

You never told anybody how to do it and then you complain of constant requests
I don't want to cook Wm6 I just want to change some files in my current WM5 Rom!
Could you please tell me how can I do it?
It does not need to be told how to do it, but told how to search ! A lot of people here know how to do it, just GOOGLE it !
sorry, I've already searched... Maybe I'm searching badly!
Could you please help me?
Basically you need to extract the ROM installer, you will find an nbf file in it, then get an NBF file converter, to convert it into some sort of editable format, then you start cooking the ROM, placing whatever you want, and in the end, convert it back into NBF
Hello,
You might find something useful here:
http://www.modaco.com/index.php?showtopic=255064
It would be more helpful if people genuinely try to help others instead of directing them to Google.
A
hey
if you can wait a day or two, i will write up a nice simple guide for everyone and have it stickied
i will also provide links to the tools required. it really isnt as difficult as some people thing! it just LOOKS difficult!
and we are a community here, so lets just help rather than-use the fricking search!lol. we were all n00bs once!
duke_stix said:
hey
if you can wait a day or two, i will write up a nice simple guide for everyone and have it stickied
i will also provide links to the tools required. it really isnt as difficult as some people thing! it just LOOKS difficult!
and we are a community here, so lets just help rather than-use the fricking search!lol. we were all n00bs once!
Click to expand...
Click to collapse
if all were like you ...
I know it isn't but in so much amount of infos it's not easy to find ones that apply to your device or even thing you wanna do!
Need help too
Yea, Please..my probs are the reconverting my data into a .nb->nbf file...after flashing My phone hangs in First Bootscreen...please help!Only Reflashing helps...i really want to cook a rom by myself.
Ive used THIS kitchen...but it is for Wizard-devices only....but i think,it can be used for Tornado,too.
as far as we tried we could not make a proper dump of the wm5 tornado...
but i did manage to build a rom kitchen with wm6 for the tornado...this was a whileago and the base rom is the same as the current available...if ther is enougth request i may be inclined to update the RK and release it.
to get you started here is some pointers.... you can use the same tools from the wizard, imgfs tools.
When I use nb2nbf_wizard.exe, is this created nk.nbf flashable for my Tornado (german XDA Phone aka HTC Douton)?
There is an nb2nbf_Tornado File out there,too, but my Phone stuck in first BootScreen.If i use the Wizard-Tools here and use the nb2nbf_Tornado,(by retyping the Start Adress from 8004000(for Wizard) to 8204000 (for Tornado)) it works well fine, Flashing works well,too,but stuck in first Screen every time.Ive only delete the Solitaire-Folder,but it dont work for me..maybe you have more luck!Or...faria may Post a RomKitchen exclusive for our lovely Tornado..
Have you removed the first two bytes of the initflashes.dat? When not, it can't be booting correctly! That was my mistake when I started to cook my own ROM's for my HTC Prophet (XDA Neo)!
What?
really?I may think,it is only needed after a Registryedit....thank you.!
edit:did not work...
arpy said:
There is an nb2nbf_Tornado File out there,too, but my Phone stuck in first BootScreen.If i use the Wizard-Tools here and use the nb2nbf_Tornado,(by retyping the Start Adress from 8004000(for Wizard) to 8204000 (for Tornado)) it works well fine, Flashing works well,too,but stuck in first Screen every time.Ive only delete the Solitaire-Folder,but it dont work for me..maybe you have more luck!Or...faria may Post a RomKitchen exclusive for our lovely Tornado..
Click to expand...
Click to collapse
i have the same problem like you.
I've made a nk.nbf from the *.nb files with nb2nbf_tornado.exe.
I've also extracted *.nb (OS, IPL, SPL, etc) from nk.nbf from windows mobile 6 alpha and then 'translated' those nb files with nb2nbf_tornado.exe. Same result: succesfull flash, stuck in first screen every time..
so not the "initflashes.dat" file is guilty..
...and nobody out there may help us?
arpy, it seems that if I include only OS without IPL & SPL in nb2nbf, all are OK..
But still with my modified OS does not get over the first splash screen.. maybe i've done smth wrong. In dump folder, I've added some files (some overwritten), i've removed some files, modified initflashfiles.dat (last line blank, + removed the two first bytes with winex), modified the hv files (saved in unicode standard, first line REGEDIT4, last line blank.. complied: no errors). replaced carrier_splash and shutdown
that's all what I've modified ...
edit:
arpy, try to translate only the OS module with nb2nbf_tornado. and tell me the result. also, tell me what changes you've made
edit2: found this: http://forum.xda-developers.com/showthread.php?t=298327 . improved tools
edit3: i've dumped my modified OS module with tadzio's ImgfsTools and discovered that initflashfiles.dat had the two bytes that i've removed with win hex.. what the?!
i've removed again, and run the whole build rom process again , but this time with tadzio's ImgfsTools.
Same result.. (stuck in first screen)
Maybe i've modified something wrong.
edit4: i've repeated the whole process and OS module flash and work ok . I haven't tried yet with all modules, only OS. I think I've made some mistakes when trying to replace drivers.
@DSF
Can you post a Step-By-Step Solution?I want to figure out my prob...which tools do you use?And how?May you Post your ROM?
well, i will post summary. i hope to release a "tornado romcook kitchen" and more detailed steps these days.
here is my OS module:
http://rapidshare.com/files/45915194/RUU.rar.html
right now i'm trying to figure out how to make the sd driver from iphone/other roms to work on my custom rom. every time i try other sd driver, i cannot view the card.
i'm using the tadzio's ImgfsTools (see link in my previous post).
steps:
- download typho5.exe, ImgfsTools, nb2nbf_tornado (you can get them by searching via gogole)
- copy all those files in the same folder, eg: ROMDEV
- copy nk.nbf in ROMDEV
Commands:
1) typho5.exe -x nk.nbf
2) imgfsfromnb.exe 82040000-OS.nb imgfs_raw_data.bin
3) imgfstodump.exe imgfs_raw_data.bin
Now the OS files are dumped in dump folder. Do the changes (delete, copy, modify, etc). When editing registry and initflashfiles.dat file, perform the important steps describeb at http://www.molski.biz/romcooking.html (turn off word wrap and use UNICODE in notepad, etc). If you're dune with those things do next:
4) imgfsfromdump imgfs_raw_data.bin imgfs_new.bin
5) imgfstonb imgfs_new.bin 82040000-OS.nb 82040000-OS_final.nb
if no error occured in the whole process, run 6) nb2nb_tornado.
There, chose the nb files, OS will be 82040000-OS_final.nb and not 82040000-OS.nb. Don't forget to use the correct image name. (eg: for 82040000-OS_final.nb chose OS)
The language, oem, operator version, cid can be left blank.
When you're done, press translate.
Copy the generated nk.nbf file in the rom update folder (RUU), execute ROMUpdateUtility.exe and follow the normal flash steps..
That's all.
Thanks to all those ppl that made this possible
PS: if you flash only the OS module (without IPL & SPL), even if the update proces crashes, you will not 'brick' your phone . Mine happen to crash on 2%.. i transpired instantly
kartam said:
You never told anybody how to do it and then you complain of constant requests
I don't want to cook Wm6 I just want to change some files in my current WM5 Rom!
Could you please tell me how can I do it?
Click to expand...
Click to collapse
Actually, I have some files about how to cook a rom, but they all Chinese, and may be useless for you.
DSF: the way you describe works with the tornado. thx. ive testest
an usefull app to edit initflashfiles.dat and the registry files is "notepad2".

1st try at the kitchen, and I can only fry some eggs....

Hi guys....
I've been a member of this comunity for 2 years now, but posted very litle, because I would be mostly spamming, re-interating what others have said, with" wow, this is fast...nice job"...and such..so i only post when I realy have to.
I downloaded the hypercore kitchen, and after some reading of the contained links and txt files, decided to have a go at it...
I would like to target Tomal's v8 but although very fast, it seems to have a significant number of com bugs...So maybe I'll go with v7.7...
I copied the nk.nbf file to the correct directory, and ran the decoder, but it errors on the next step saying that there is no OS.nb file...
Should this file be extrated from the nk.nbf?
Is this a problem with the nk.nbf file I'm using?
I would apreciate some help on this, as I'm looking for a full flavored cake, but to my taste...see I'm "diabetic" so I have to be extremly caution with what I cook...
When you decoding nk.nbf, decode it to OS.nb (change second line) instead nk.nba.
Something else to be aware of with Tomal's ROMs is that he ships all his RGUs in a single RGU.cab file.
You'll need to extract the contents of this file into the dump directory AFTER the imgfstodump and BEFORE the pkgtool step.
-PJC
Thanks for the quick answers, guys...
Something pop-up as a doubt...can I cook from an usb stick?(installing the kitchen, and workind directly trought the usb stick)???
I'm getting starved.....I can't even turn on the oven...
I have nstaledthekitchen over and ove again.
Changed the settings so it reads "Universal", copied the nk.nbf of my choice to the Extract/source folder, and whent to the Panel/extract and runned "DumpRom"...So far so good....
The DOS windows warns me that the file must be in the correct folder, so I double check....I press return...HTC Extender Rom Tool starts and prmpts me what I want to do and were is the extended rom...I thought it was embeeded in the nk file, but since Tomal provided with and empty extenden Rom, I downloade it and poited to it...Hit decode...
A big window opens with some file paths, so I check them to know were the files are going to...and using the above tip, change the name of the fat file to OS.nb, Hit decode...I'm happy, the window says "Decode sucessfull", so I hit "OK"...
I am agin at the Htc Extended Rom tool, so I hit exit(? done it right ?)...
The Dos window now tells me that it cannot find the ON.nb(? Didnt I just created it?)....
So I'm stuck....
The constructions workers haven't yet finished furnishing my kitchen, so I have no ingredients to work with....
Any chef willing to help me make a simple meal?????
psapg said:
I'm getting starved.....I can't even turn on the oven...
I have nstaledthekitchen over and ove again.
Changed the settings so it reads "Universal", copied the nk.nbf of my choice to the Extract/source folder, and whent to the Panel/extract and runned "DumpRom"...So far so good....
The DOS windows warns me that the file must be in the correct folder, so I double check....I press return...HTC Extender Rom Tool starts and prmpts me what I want to do and were is the extended rom...I thought it was embeeded in the nk file, but since Tomal provided with and empty extenden Rom, I downloade it and poited to it...Hit decode...
A big window opens with some file paths, so I check them to know were the files are going to...and using the above tip, change the name of the fat file to OS.nb, Hit decode...I'm happy, the window says "Decode sucessfull", so I hit "OK"...
I am agin at the Htc Extended Rom tool, so I hit exit(? done it right ?)...
The Dos window now tells me that it cannot find the ON.nb(? Didnt I just created it?)....
So I'm stuck....
The constructions workers haven't yet finished furnishing my kitchen, so I have no ingredients to work with....
Any chef willing to help me make a simple meal?????
Click to expand...
Click to collapse
With HTC Extender Rom Tool you must extract nk.nbf not ext_rom, and when extracting name it OS.nb (i thing it is 2nd line in tool)
Perhaps the would-be chef should read a cookery book?
There's a very, very good guide in this forum, which is what I started off with and had no problems whatsoever, but I can't for the life of me remember if it was beasty or thingonaspring who wrote it (apologies to the real author if I missed them out!). It also includes some fixes for the batch files.
Remember - the wiki and search are your best friends...
PJC
Hi Again...
The construction workers finaly had done some real work, so now my kitchen is properly furnished with all the CABinets i need...so now to try to cook me a simple meal, and try to learn from it....
Can't rebuild Ranju 7.7
Hi all.
I gave it a go and tried to rebuild Ranju 7.7.
I could decode it, dump it (yes, I extracted the contents of RGU.CAB to the dump directory), convert the dump to packages etc. So far, so good.
But when I tried to rebuild it, the ImgfsToNb tool gave this error message:
"Partition with file system 0x01 found after IMGFS partition. It's safer to abort here, sorry."
What should I do now?
jandevries12 said:
Hi all.
I gave it a go and tried to rebuild Ranju 7.7.
I could decode it, dump it (yes, I extracted the contents of RGU.CAB to the dump directory), convert the dump to packages etc. So far, so good.
But when I tried to rebuild it, the ImgfsToNb tool gave this error message:
"Partition with file system 0x01 found after IMGFS partition. It's safer to abort here, sorry."
What should I do now?
Click to expand...
Click to collapse
imgfstonb doesn't seem to support the FLASH disk that's in Tomal's ROMs. I don't know what he uses, but when I've based things on his work, I use a different 'donor' OS.nb for the imgfstonb stage. Obviously, I lose the FLASH disk, but as I don't use it anyway, that's not an issue for me.
^^ yup, exactly, it is due flash disk.
Ok, I understand.
But what is the "donor" os.nb used for?
I've extracted the OEM, SYS en XIP parts. Isn't that enough to compose a new ROM?
What parts are re-used from the original os.nb? And must an alternative donor os.nb be of the same version/build?
jandevries12 said:
Ok, I understand.
But what is the "donor" os.nb used for?
I've extracted the OEM, SYS en XIP parts. Isn't that enough to compose a new ROM?
What parts are re-used from the original os.nb? And must an alternative donor os.nb be of the same version/build?
Click to expand...
Click to collapse
As I understand it (and I'm sure someone can correct me if I'm wrong), the donor OS.nb is used as a 'template' for storing the IMGFS into an NB structure. As far as I've been able to tell, pretty much *any* OS.nb from *any* ROM can be used as the template.
Basically, imgfstonb takes 3 arguments - the imgfs file itself, a 'donor' OS.nb, and the 'target' OS.nb final output. This is all hidden by the scripting, but is what I've found by playing with the underlying utilities.
The only restriction I've found is that ROMs that contain Flash disk can't be used as the donor OS.nb.
PJC
Could one of the senior members of this forum please comment on pjc007's statements above?
Is it correct that the donor os.nb is only used to determine the right structure for the ROM?
(I'm asking because I got the impression from other posts on this excellent site that the donor os.nb is used as source for the XIP part, but I don't know for sure)
Well, I have the same matter now, I really want to cook sth to use the way I want a rom to be and share with others as I feel really bad just to download, I hope to upload my own rom and share but I read the instructions again and again , look for sth on the internet, download all the things to my PC that will be used to cook, still not certain what I'm going to do.
My question is if I cook a bad rom, then I up it to my EXEC, Is there any chances for it to die ? Or simply just install another well-known rom to rescue it if my rom jail to boot?

Categories

Resources