Related
Welcome to the Wizard Rom-Packer Kitchen V2.0, with "Squeezer" technology!
Please read all the way through before starting, even if you've used a previous version.
USE AT YOUR OWN RISK!
This kitchen is easy to use, but is really meant for those with some previous work with other kitchens,like faria's or 004's or Molski's. (If I've left someone out, I'm sorry about that.) This kitchen is based on Bepe's Hermes kitchen, which has incorporated tadzio's reworking of maimach's imgfs tools. This allows the rom to be packed more efficiently, and thus more packages and files to be burned into the rom. The savings is not trivial, a few megabytes at least.
In addition, I have added a new Squeezer module, based on open-source UPX technology, which actually compresses Office .exe files, freeing even more room in the rom (a few more meg), and actually decreasing load times!
Although the Wizard Rom is not quite as malleable as the Hermes in that the extra space is not translated into additional user storage memory, at least the additional freeware, shareware, themes, etc. which can be burned to the rom do not have to reduce the user storage space.
I hope over time to enhance this further, as new innovations become available, (maybe someone will figure out a way to repartition the Wizard Rom?). Also, perhaps adding some way of automatically generating the xip directory. If you have suggestions feel free to let me know about them.
Error checking is not extensive, so be sure to keep your old rom available to fall back to! Check the size of the generated .nbf file. If its around 59 mb you are close to the limit. Be ready to re-flash in bootloader mode (after paring some packages or files) if the program exits before the 100% mark.
How to use:
Download your favorite base rom, at this point one from another kitchen, which has already been broken down to SYS, OEM, and ROM directories. Delete the SYS, OEM, and ROM directories from my kitchen, and copy the ones from the other kitchen in there instead.
Make a copy of the SYS\OFFICE directory in case of later problems (not likely).
An additional caution/strong recommendation is to delete the /autoupdate package from your roms. This currently does nothing anyway, so you won't miss it, and in any case would likely only create havoc with a custom rom. But additionally the repacking method used in this kitchen removes the extra space in the rom which was to be used for that anyway, and so autoupdate will definitely be useless in a rom built with this method.
Run the SqueezeOffice.bat program. (This compresses your main Office .exe's)
Make sure there is an 80040000-os.nb file in the ROM directory. (It may be called something else and have to be renamed. It'll be around 50mb in size.)
Now click on Start.bat, and away you go...
(Optional) If you want to later go back to using another kitchen, run the PrepareNewNB.bat file. After it completes, there will be a new, compacted 80040000-OS.nb file created in the ROM directory which you can move back to your original kitchen. (Also copy the Office directory back) You will loose some packing efficiency by building in another kitchen, but you will still gain lots of space from having visited here!
Depending on the kitchen you were using, either you will see selectable packages or not during the running of BuildOS. Use whatever method you were using previously to add new packages or to remove the ones you don't want. In general, everything should work about the same way it did before, except you will be able to fit more packages in than previously! (Those who are importing faria's kitchen will have to rename his BuildOS.exe to BOS.exe and bring it into this kitchen. Also, rename his Flash file in the ROM directory to 80040000-OS.nb.)
You will be given the opportunity to go all the way to flashing the rom, similar to the way faria's kitchen is set up. Hold down the Control and "C" keys during one of the pauses provided if you do not want to go to the next step for some reason. (You have a G4, unlocked G3, want postpone flashing for later, etc.) Then press the "Y" key to abort when prompted.
If you'd like, check out the ZSqueezer directory, and the readme there. There you can compress your other programs for even more space (and speed!).
Thanks to all those who have helped me in the past, and especially those who created the tools and roms we all use and enjoy.
Version History:
Initial Unlabeled: Worked fine
V1.1: Added "pre-packing", had a bug in Start.bat
V1.2: Worked fine
V1.3: Deletion of .rgu files from the dump.
V2.0: Removed .rgu deletion (instability), and introduced "squeezer" compression.
Download Link: V2.0
http://rapidshare.com/files/33616241/Wizard_ROM-Packer_Kitchen_V2.0.rar
Standalone Squeezer Module
For those interested in having the "squeezer" technology for their own programs, but aren't comfortable cooking their own roms, I have created a standalone module for that. (Already included in the latest Rom-Packer Kitchen V2.0). I've also started a separate thread for that as well in the Upgrading section. Of course, feel free to leave comments and suggestions in either thread.
Here's the link: http://forum.xda-developers.com/showthread.php?p=1283338#post1283338
Have fun!
More space for later use.
thanks. i'll give it a go later tonight
I just tried these tools and didn't have much sucess....
I used the latest mUn base ROM, added some OEM stuff that I have been using without issues when creating ROM's with mUn's previous ROM. All this went OK. It got to the point of installing the ROM on the device but the ROMUpdateUtility just exited at 98% and left the Wizard in limbo. I have had put it in bootloader and re-intall a previous ROM
There was no message, it just got to 98% on the PC and the Wizard and then the ROMUpdateUtility just exited. I tried manually using the nb2nbf application and copying the resulting nk.nbf to another RUU folder and the same thing happened.
Any idea's?
Andy
ADB100 said:
I just tried these tools and didn't have much sucess....
I used the latest mUn base ROM, added some OEM stuff that I have been using without issues when creating ROM's with mUn's previous ROM. All this went OK. It got to the point of installing the ROM on the device but the ROMUpdateUtility just exited at 98% and left the Wizard in limbo. I have had put it in bootloader and re-intall a previous ROM
There was no message, it just got to 98% on the PC and the Wizard and then the ROMUpdateUtility just exited. I tried manually using the nb2nbf application and copying the resulting nk.nbf to another RUU folder and the same thing happened.
Any idea's?
Andy
Click to expand...
Click to collapse
Can't really say. I've also flashed mUn's latest, and it seemed to go ok. Did you create your own xip directory? If not, use the version in 004's kitchen as a base.
edhaas said:
Can't really say. I've also flashed mUn's latest, and it seemed to go ok. Did you create your own xip directory? If not, use the version in 004's kitchen as a base.
Click to expand...
Click to collapse
I had the XIP directory from the original ROM kitchen (in dOUbleOfour_Wiz_Dev_5.2.1413WWE.rar). I think I might try without any OEM stuff and build it up and see where it fails. In your original post you mentioned the error checking is not extensive, does it log any errors anywhere? (apart ffrom the log.txt file that looks OK).
Andy
ADB100 said:
I had the XIP directory from the original ROM kitchen (in dOUbleOfour_Wiz_Dev_5.2.1413WWE.rar). I think I might try without any OEM stuff and build it up and see where it fails. In your original post you mentioned the error checking is not extensive, does it log any errors anywhere? (apart ffrom the log.txt file that looks OK).
Andy
Click to expand...
Click to collapse
You put too many files, that's why it existed. I presume that because it exited at 98% , meaning that almoust fit, but it didn't . Try leaving out a package ...something about 1MB or so..mabe less
anichillus said:
You put too many files, that's why it existed. I presume that because it exited at 98% , meaning that almoust fit, but it didn't . Try leaving out a package ...something about 1MB or so..mabe less
Click to expand...
Click to collapse
Yep, I think that's what the issue is
When I tried cooking with this as the Base ROM previously I ran into size limitations so I was hoping that these new kitchen tools would solve this -
This allows the rom to be packed more efficiently, and thus more packages and files to be burned into the rom. The savings is not trivial, several megabytes at least.
Click to expand...
Click to collapse
Obviously not enough
I'll play around a bit more and see where I get....
Andy
I'm very sorry, but I left out a very important preparation step in my original posting. Please redownload the package to get the corrected version. (V1.1) I think you will find the results to be much more satisfying! Keep the bug reports coming..
the new start batch file doesn't have the correct paths in it. its trying to work in the root folder not temp.
the original one works good though. too late to flash tonight, but i'll give it a go tomorrow and let you know how it works
I tried to correct the start batch file to use temp but now get errors about not finding initflashfiles.dat in the temp\dump area. I don't have time to debug this right now.
I also noticed that the nb2nbf.exe is a Typhoon Smartphone version (so not sure that is correct for the Wizard).
I will say that the pre processor that does the packing is cool. The Faria Vanilla 80040000.nb (in Faria's kitchen its actually called FLASH.nb0, so I just renamed it) was 58.3MB in size. After running the PrepareNewNB.bat it was then 57.1MB, so a full meg smaller. I'll see about moving this over to the Faria kitchen and using it to rebuild my rom later and see how that changes things when its actually flashed to the phone.
i'll post the working one in a little bit.
edit... here's the one that works for me
notyourdaddy said:
i'll post the working one in a little bit.
edit... here's the one that works for me
Click to expand...
Click to collapse
Thanks, I was bleary eyed last night with trying to figure out what was going on that it wasn't working for you guys, and I ended up "fixing" some things that weren't broken I guess.
Just be sure to delete the old dump file in the temp directory after you run the preparenewnb.bat file.
Has the compression been working for you?
I appreciate your help. I'm juggling lots of things with "real life" and am sorry for the slip-ups.
I am updating the first postings.
notyourdaddy said:
i'll post the working one in a little bit.
edit... here's the one that works for me
Click to expand...
Click to collapse
Maybe its an issue with the Faria RK base rom and compatibility with this kitchen, but even with this updated file (thanks for that) I still get the following error when running the build os step:
Code:
Could not find file "temp\dump\initflashfiles.dat".
The other question is, is it ok to use the Typhoon Smartphone nb2nbf.exe that comes with this?
mfrazzz said:
Maybe its an issue with the Faria RK base rom and compatibility with this kitchen, but even with this updated file (thanks for that) I still get the following error when running the build os step:
Code:
Could not find file "temp\dump\initflashfiles.dat".
The other question is, is it ok to use the Typhoon Smartphone nb2nbf.exe that comes with this?
Click to expand...
Click to collapse
Yeah, I was just running through the faria kitchen and had the same issue. The workaround is to copy the initflashes.dat file in the OS folder and then paste it into the dump directory after buildos has deleted the previous dump and before it is processing the sys\os directory. (Watch the process messages at the bottom of the buildos screen.) This worked for me.
Yes the typhoon version works fine. I think they are mostly all relabeled versions of the same original tools. (Except the imgf tools which are recently updated by tadzio.)
Hope this helps.
weird. intiflashfiles.dat copied over for me using 004's kitchen
I just finished doing a build with faria's kitchen as a base, and was somewhat disappointed that I was unable to flash the entire kitchen at once. I had to leave out enterprise and voip (which is fine for me, but some may want them). I'd be interested in hearing how much extra space people are finding. I felt like I was able to cram a lot more into double_ofour's mUn release, but perhaps that's because it was more stripped down to start? Maybe "the kitchen sink" was a bit optimistic.
Re Faria kitchen
mfrazzz, The easy fix for the faria kitchen is to use faria's buildos.exe instead of the generic one I included. That one runs fine with his kitchen. Just rename it to bos.exe. (or edit the start.bat appropriately.) I don't think this will affect the packing of the files.
Update
OK, Things seem stable now. I've updated the first posting with additional information gleaned from everyone's input, and updated the version. The old start.bat that notyourdaddy posted should not be necessary.
FYI, I got feedback from one user that they got about 2.5 meg additional space from these tools vs the old tools. Not as earth shattering as I'd hoped, but helpful. Roms with more small files, as opposed to those with larger files will likely benefit more, as the savings are in the "padding" between them.
Feel free to incorporate this into your own kitchens.
Regards,
Here is the brand new rom version for T-mobile Wing. It has been modified based on the OS of Wing (thanks to Mr PhamQuang from PDAViet) and included TouchFlo.
This rom is the same as the version TOUCHFLO v4.17.07.12 PDAVIET (based on HTCs' OS), but for Wings' users only because of the keyboard. I am sure that from now on there is no more complain about the keyboard problem.
How to flash it? Just extract the nbh file by nbhtool. Then you can flash the extracted OS with Aserg's method.
It has a quite big storage compared with the original Shipped rom and TouchFlo runs well!
Link: http://tom-love.net/ROM/Herald/HERA_Wing_v4.10.07.14_PDAVIET_NBH.rar
i Might try this later so my keyboard gets fixed. If this version the keyboard is indeed fixed 100%, I hope it's my final version! TouchFLO + Keyboard fixed = masterpiece!
nugift said:
Here is the brand new rom version for T-mobile Wing. It has been modified based on the OS of Wing (thanks to Mr PhamQuang from PDAViet) and included TouchFlo.
This rom is the same as the version TOUCHFLO v4.17.07.12 PDAVIET (based on HTCs' OS), but for Wings' users only because of the keyboard. I am sure that from now on there is no more complain about the keyboard problem.
How to flash it? Just extract the nbh file by nbhtool. Then you can flash the extracted OS with Aserg's method.
It has a quite big storage that the original and TouchFlo runs well!
Link: http://tom-love.net/ROM/Herald/HERA_Wing_v4.10.07.14_PDAVIET_NBH.rar
Click to expand...
Click to collapse
I tried this version on my wing, but it never worked. I've being using PDAVIET since version .07 - .15 but .14 did not complete the flash for some reason.
Same here. Doesn't finish and when I try to extract the SYS and OEM files from it I get errors.
mikenaustin said:
Same here. Doesn't finish and when I try to extract the SYS and OEM files from it I get errors.
Click to expand...
Click to collapse
The same thing happened to me twice (did not know the reason). But the 3th time the flashing ran smoothly and now my device works perfectly.
You can try again, but remember to softreset after installing Aserg.Policy.cab. Then you need to turn you PPC to Flightmode.
New Download Option!!!!!!!
Here's the way to get the original package from PDAVIET:
Goto: http://www.pdaviet.net/showthread.php?t=13288
and get part 1
Then download part 2 from here and extract the rar file below:
EDIT: It's still hanging during the upgrade at copyFileToTFFS
nugift said:
The same thing happened to me twice (did not know the reason). But the 3th time the flashing ran smoothly and now my device works perfectly.
You can try again, but remember to softreset after installing Aserg.Policy.cab. Then you need to turn you PPC to Flightmode.
Click to expand...
Click to collapse
Thanks! You've given me new hope.
Did you upgrade from the original TMO USA Ship version?
Thanks,
M
mikenaustin said:
Thanks! You've given me new hope.
Did you upgrade from the original TMO USA Ship version?
Thanks,
M
Click to expand...
Click to collapse
From what I know there is only one rom for Wing at the moment. This is the original TMO USA Ship version. The cooked rom v14.PDAViet is based on this rom. Mr PhamQuang removed some APP from T-mobile and added some new things as follows:
- ArcSoft MMS v4.2.8.1
- BT FTP v1.2 Build-30234
- StreamingMedia v2.20h Build-615718
- HTC Audio Manager v1.02 Build-725711
- Esmertec Jbed Java v2.1 20070802
- CommManager 1.72 với 10B
- HTC Touch UI HOME v2.0 Build-814722 (Kaiser)
- NetWizard v1.0 Build-29982
- Voice Speed Dialer v1.2 Build-070612
- X-Button v1.51 Build-30744
- SIM Manager v6.25
Is there a thread that shows what has been changed/added/deleted to this rom?
I would like to know what was taken off, and what was changed from the original tmobile ship before I switch to it.
nugift said:
The same thing happened to me twice (did not know the reason). But the 3th time the flashing ran smoothly and now my device works perfectly.
You can try again, but remember to softreset after installing Aserg.Policy.cab. Then you need to turn you PPC to Flightmode.
Click to expand...
Click to collapse
Hi,
I've tried to flash this rom a lot of times without success. I'm just wondering how you were able to, since I think their is some thing wrong with the OS.nb file.
I'm able to reflash back to version .12 or even .15 but not .14.
Any help would be great.
ttran001 said:
Hi,
I've tried to flash this rom a lot of times without success. I'm just wondering how you were able to, since I think their is some thing wrong with the OS.nb file.
I'm able to reflash back to version .12 or even .15 but not .14.
Any help would be great.
Click to expand...
Click to collapse
Why did I introduce only the nbh file here? There is a reason! At first I started many times flashing with the OS.nb but no success like you. So I requested the rom-cooker to provide the nbh file.
I got the OS.nb from the nbh file by using nbhtool. With the new OS.nb I also failt twice. By the 3th time the falshing was succesful. I think you should turn your phone to Flightmode.
Has anybody been succesful with the flashing this version?
I ve got message
CopyFileToTFFS(OS.nb:0, 0, 04100000)
ERROR: ITWriteDisk - An existing connection was forcibly closed by the remote host.
ulrakhma said:
I ve got message
CopyFileToTFFS(OS.nb:0, 0, 04100000)
ERROR: ITWriteDisk - An existing connection was forcibly closed by the remote host.
Click to expand...
Click to collapse
I received the same error message.
Well, I've wasted enough time on this, going back to version .12 until they fix the OS.nb file for this version.
nugift said:
Why did I introduce only the nbh file here? There is a reason! At first I started many times flashing with the OS.nb but no success like you. So I requested the rom-cooker to provide the nbh file.
I got the OS.nb from the nbh file by using nbhtool. With the new OS.nb I also failt twice. By the 3th time the falshing was succesful. I think you should turn your phone to Flightmode.
Has anybody been succesful with the flashing this version?
Click to expand...
Click to collapse
I have but to no avail. Same problem. It just hangs while copying.
Hi nugift,
Have you made any mods to the radio or anything else prior to flashing this?
1st link dead cant wait for this to work looks promisin
Getting same error
CopyFileToTFFS(OS.nb:0, 0, 04100000)
ERROR: ITWriteDisk - An existing connection was forcibly closed by the remote host.
I've tried 5 times to no avail. I have no issues with the other PDAVIET releases for the P4350.
i renamed the nbh file to os.nb and overwrote the one in pdaviet it installs all the way but after hard reset wont pass tmobile boot screen ima have to retry
Smilez_c said:
i renamed the nbh file to os.nb and overwrote the one in pdaviet it installs all the way but after hard reset wont pass tmobile boot screen ima have to retry
Click to expand...
Click to collapse
your not sposed to rename it. you have to use nbhtool to get os.nb out of the .nbh file.
also
i've learned through experience that in order to flash the rom successfully without error you should
1.backup up any data you want to keep
2.install Tmob RUU factory shipped wm6 version
3.install the Asearg Policies cab file
4.soft reset
5.begin the upgrade rom flash batch file
applecarriage said:
your not sposed to rename it. you have to use nbhtool to get os.nb out of the .nbh file.
also
i've learned through experience that in order to flash the rom successfully without error you should
1.backup up any data you want to keep
2.install Tmob RUU factory shipped wm6 version
3.install the Asearg Policies cab file
4.soft reset
5.begin the upgrade rom flash batch file
Click to expand...
Click to collapse
well it gave me a windows.nb file so i renamed that and copied it to the touch folder i already had
Guys,
we love what you do, and we couldn't do it ourselves, *but* most of us could (and would like to) remove/add the odd OEM pkg or so. And be honest, that's probably how you all got started, too.
However, these days, it isn't possible to easily do. Hypercore Kitchen (which is wonderful) doesn't work for either Ranju or PDAViet ROMs, and I've had limited success with other recent ROMs.
I for one (and I know I'm not alone) would love to make my own custom ROM based on some of those out there, but because of problems, can't.
So - PLEASE - as well as your ROM, please post your kitchen somewhere.
Thank you!!
-Paul.
I second this request. I am currently using a custom builtRom I built using hypercore from an earlier Ranju WM6 ROM and although it works well I always want the latest ROMs and the WM6.1 roms I have tried are so much faster.
Any help would be much appretiated.
Would love to see this too.
I Think Ranju's ROMs are great but I would love to be able to remove total commander and a couple of other bits and pieces.
uMP2k said:
Would love to see this too.
I Think Ranju's ROMs are great but I would love to be able to remove total commander and a couple of other bits and pieces.
Click to expand...
Click to collapse
The Ranju 7.7 ROM have the rgu.cab file. Unzip this file in dump directory and use pkgtool for create oem and sys folder. Use a cooker tutorial for changes.
anmendes said:
The Ranju 7.7 ROM have the rgu.cab file. Unzip this file in dump directory and use pkgtool for create oem and sys folder. Use a cooker tutorial for changes.
Click to expand...
Click to collapse
Thanks for the tip, I have taken the rgu.cab file and now have them incorperated into the OEM folder after running pkgtool. However I still get an error that comes up when i use any uild rom tools. It runs through all the files fine but after i have "pressed any button to continue" it comes up with an error about the partition and then says it is safer to abort.
Could you let me know if you have successfully rebuilt a personal rom and exactly what tools you used.
Thanks
Dan
Hi All im a noob to cooking. So... I dumpbed the new official rom and used the cooking tutorial to cook my very first rom YAY. BUT when my titl boots it is WM6 not WM6.1 and a few other small issues like the boot screen not showing the verion number i changed it to. I used itsutils to dump and kaiserkitchen to cook. I have searched the forum but can't find anything. Pls help
WHy are you using itsutils to dump the ROM. Just extract the .exe rename it to RUU_signed.nbh and dump it using the kitchen....
Much easier and more fool proof this way.
joerf1115 said:
Hi All im a noob to cooking. So... I dumpbed the new official rom and used the cooking tutorial to cook my very first rom YAY. BUT when my titl boots it is WM6 not WM6.1 and a few other small issues like the boot screen not showing the verion number i changed it to. I used itsutils to dump and kaiserkitchen to cook. I have searched the forum but can't find anything. Pls help
Click to expand...
Click to collapse
Sounds like youve done more work than nessessary! Do like ryncppr said above, use the lastest pagepool patcher to change version number on boot. Don't know why you would want to though!
thank you ryncppr and yardie.spike.. That was just a small issue i wanted to change but the main issue is that the rom created from the kaiser kitchen is WM6 and not the new OS. What am I doing wrong?
[Cooking] Need Help Clearing out the bloatware
ok I solved the issue with the rom being WM6 and not 6.1. I just deleted the ROM, OEM and SYS folders and the os-NEW.nb file. Then I extracted the rom I dumped from the phone and I can now cook a 6.1 rom. BUT the issue I have now is all the bloatware is on there still with the software I selected during the cooking process. How can I remove all the software that came with the ATT rom?
[EDIT] Okay I have been messing around in the OEM, SYS and ROM folders...Is this the right place to remove the oem software and if so how do I go about doing it. I found, in the OEM folder, the EXEs for the shop stuff...can i just remove those or are there othere files I need to edit as well...pls help I just want to learn
OK for those wanting to cook their own rom from the ground up, below is a link to help with cleaning up the BaseROM.
http://wiki.xda-developers.com/index.php?pagename=OEM Package Tutorial
Say I downloaded "frauhottelmann"'s GUI kitchen and I grabbed the original, unmodified S740 SYS and OEM folders from a thread here.
What would I need to replace in order to build a ROM that will bootup on an Excalibur ? I have the "dump" of the original 6.1 ROM from the Excalibur. Some drivers maybe ? Any help ? Thanks
Oh, so you got it already. You should start with the OEM folder of the Excalibur. Then you might have to add some of the *.cpl.xml from OEMMISC to get all settings to work. The new packages are a bit trickier to use. You need more files from the new OEM. And don't use the new Connection Setup, it doesn't work. You should be able to use the whole SYS folder though.
This is going to be difficult then. The only kitchen that exists for the Excalibur, dumps the contents of the ROM in one folder and doesn't seperate the foldes out to OEM, SYS, etc...
So is the SYS folder where all the drivers are then ?
No. There are two main folder. SYS is for the general Windows Mobile OS part. OEM is what the manufacturer or you add. The folder for drivers is on OEM and is called OEMDrivers. If you have a dump, you can make "packages" with PKGTools. There is no official 6.1 ROM right? So I guess this will be a problem, because then it doesn't sort the packages right. You'll have to try. Maybe send me a screen shot of the files or the result!
Well the original 6.1 ROM for the Excalibur (the ONLY one) was made by this guy Kavana. I'm pretty sure it was based on the files from the MS emulator and drivers from the OEM WM6. IS PkgTools included in your kitchen ? Should I try to dissassemble the ROM with your kitchen ?
yes pkgtools included.
give it a try and post if it worked!
good luck mate... i saw your prog for the weather! really nice!!
htc sliding plugin also rocks! anyway keep it up!
Well I managed to make an excalibur ROM that works (partially) with the VOX GUI kitchen, and replacing the OEMDrivers with the drivers from my official WM6 ROM. Problem is, the center button on the keypad doesn't work. Everything else is fine... although WI-FI and BT don't turn on. Any ideas what I'm doing wrong ? Oh and the startup screen is all skewed and in 4 pieces, right after the splash screen, bu before the usual winmo 6.1 splash screen.
Well I'm over that road bump now, and I'm trying to port the S740 XIP and SYS over to take advantage of the new CHOME
So far, so good...
Thanks guys for the support. I was able to make a new ROM based on the 20279 core from the S740 ALL by myself. Reading these forums for a few days is what did the trick... heh. THe ROM runs great and I have to say that BuildOS+package tools is my best ROM cooking friend right now...
NRGZ28 said:
Well the original 6.1 ROM for the Excalibur (the ONLY one) was made by this guy Kavana. I'm pretty sure it was based on the files from the MS emulator and drivers from the OEM WM6. IS PkgTools included in your kitchen ? Should I try to dissassemble the ROM with your kitchen ?
Click to expand...
Click to collapse
There is no rgu file in the rom you dumped.
and the one is not official 6.1.
You can dump the
moto q8 WM6.1 rom
s740 official rom
C810 official rom for your resource.
I know.. that was my original problem. No worries though, as I used the SYS folder from the S740 and all is well now