Cooking ROM for Voq? - Non-Touchscreen Windows Mobile Other

I've got pretty good knowledge about WM phones in general, however..
Would there be any way to cook a rom for the Sierra Wireless Voq? I know for a fact that it would be a bit difficult since nothing is documented on it, but if there's a way to figure it out..
TIA!

It seems that the nk.bin file distributed with the last Voq upgrade uses the Wallaby bin file format described in this wiki entry.
Any tools for dealing with that format? I've looked but I can't find any.

Related

Cooking Help

Since all of you have made it so easy to understand the basics, I'm trying to cook!
I'm using the latest official Tilt ROM posted here, but I'd like to import the latest CE OS version from a different ROM. I don't even know if this is possible, but I figure someone would know how if it is.
If I extract the base ROM and the ROM with the target CE OS, how would I go about importing this OS into the Base ROM?
Someone at least tell me shut up Newb and read or point me in the direction I need to go. I've looked and the only thing I can find is some references to XIP being difficult to port.
Is this where the main operating system of the device is stored?
Anyone willing to help?
BulldogXTRM said:
Anyone willing to help?
Click to expand...
Click to collapse
I think you just asked the single hardest question about cooking. The answer is there's no "simple" easy way to do it. Most of the files you're looking for will reside in the SYS\OS* folders. The really good news is that as long as you keep the OEM\OEMDrivers folder alone you can port pretty much anything you want from a similar device (Hermes, Polaris, Wizard, etc) and it should work on the Kaiser.
But it is *truly* a VERY slow process to port enough to make things work without porting so much you break it again. And when you have a ROM that won't even boot its a ROYAL PAIN to track down which of dozens of changes you might have made between compiles/flashes is causing the problem. In my experience it's usually something really simple like extra characters in initflashfiles.dat (from editing in Notepad), or some registry setting gone awry.
Anyway, good luck to you!

Is it at all possible to merge multiple cab files to create a single cab?

What I am interested in doing is taking multiple cab files and then merging them into a single cab file so rather than having to install multiple theme tabs i could just install a single file which would make the whole process simpler after a hard reset to get all my things reinstalled.
I'm a bit of a noob and have searched through the forum but havent really found a noob's walkthrough although i have found usefull posts they arent exactly what i'm looking for, i'm sure other members would find this really usefull too if its at all possible.
It could also be helpful for installing multiple applications at a time.
I appreciate that people dont have the time to sit and talk me through the whole process but any information you could give would really be appreciated.
I've attached the files that i would be interested in merging. I'm not looking for anyone to do the work for me i'm just interested in any knowledge of the process that you may have to offer.
Thx
Alex
Doobee24 said:
What I am interested in doing is taking multiple cab files and then merging them into a single cab file so rather than having to install multiple theme tabs i could just install a single file which would make the whole process simpler after a hard reset to get all my things reinstalled.
I'm a bit of a noob and have searched through the forum but havent really found a noob's walkthrough although i have found usefull posts they arent exactly what i'm looking for, i'm sure other members would find this really usefull too if its at all possible.
It could also be helpful for installing multiple applications at a time.
I appreciate that people dont have the time to sit and talk me through the whole process but any information you could give would really be appreciated.
I've attached the files that i would be interested in merging. I'm not looking for anyone to do the work for me i'm just interested in any knowledge of the process that you may have to offer.
Thx
Alex
Click to expand...
Click to collapse
Simplest and easiest thing to do is to use UC to install all these cabs automated style when the ROM boots up. I am assuming you are using a ROM which is UC compliant (all the official ones arent.....the cooked ROMs are mostly UC compliant though).
The 'hard' way is analyzing the cab's -> extracting files/reg-entries -> rebuilding the cab-files to one cab.
Theoritically it's possible with a program like WinCE Cabmanager but it is a hell of job I think.
I would go for the UC-option mentioned by MrVanx. I use it myself and it works like a threat (you have to get familiar with wap-provisioning and stuff but it's worth the journey)
Ive tried using a few of the cooked roms over the past couple of weeks but to be honest they dont work all that well for me, none of them seem to work with msn (which is something i use all the time) i always get error messages saying that it cant find a data connection even through wifi which is always setup properly as i can search the net quite easily and have verified that the wifi is working and searched through the rom threads for fix's and all ive seen so far is that this seems to be a bit of a problem for a number of users, some fixes work for certain members but it doesnt for others, unfortunatly i'm one of the others.
Currently using Vodafone UK 1.90.161.5 stock rom.
I think the WinCE Cabmanager approach mite be the best option for me as i'm still a bit of a noob with regards to things and as most of the cabs i'm interested in merging are simple theme cabs so it shouldnt be that much of a task (gulps)
Are there any good tutorials that i could use for WinCE Cabmanager?
I'll have a search myself to see what i can come up with but in the past i've found it quite hard to find things in the forum and most of the time i stumble across certain "gems" by following links in peoples signatures.
Thanks for the info its much appreciated.
Alex
Over on the Kaiser section there was a user named bengalih, who made an automated installer called Sashimi. Although Bengalih has been banned, his work is still floating around. Check out this thread, or do a search for Sashimi. In theory, it should work for the Raphael, since it is still a Win Mobile device. Hope that helps. I might add, that right before Bengalih was banned, he stripped his Sashimi guides from his posts on xda, but they are available here.
This does look like the type of thing i am looking for unfortunately all his posts are just "..........................." but i regged on the other site and got the software so i'm going to go check it out and see how it works. Thanks for that
Alex
Just a quick question but does your mobile connection (Vodafone UK) allow you to use msn (or to that matter any IM program) or is it just http stuff only?
Tmobile wnw doesnt allow IM software over the data connection unless you use wnw+ so i wonder if this is the case with vodfone aswell?
Yeah it does, it also allows me to use skype too. Unfortunalty its the only ROM that does allow me to use msn although i havent tested skype as this is my secondary IM app.
In theory to make a theme (cab) i tried to extract files from a few cabs, files including:
1AA884~1.004
1BBFDC~1.001
1E29E8~1.005
4E6705~1.002
5A7AE8~1.015
5B86C9~1.016
5C27FF~1.017
etc
Then i used "QuickCab 1.0" to add all the extracted files from a couple of cab files, i directed QuickCab 1.0 to install the files to the Windows directory and the process made the new cab file with no problems however i tried to install the cab file that it had created but my TF3D didnt change at all even after a restart.
I'm trying to merge NoTopCurtain.cab-NoCurtains.cab-GlassClock_v1.cab-Pamas Transparant Slider.CAB & NeonIcon.cab
By looking at the xml file it looked like all the 90 files should be installed to the Windows directory.
Any idea of what i am doing wrong?
Thx
Alex
try cabmanager. You will see the actual files. And there is very logical registry structure.
I do not have a tutorial for the program but it's not that hard. You can export files (right mouse click) and reg-entries (under 'file'). Put those all together (import of reg-entries is also possible!) Adding files gives you a simple window with where to put the files on your ppc.
It is not that hard and you will be in control of the proces instead of working with the encrypted files you are doing now...
made dozens of (working) cab's this way myself and I'm no einstein!
Good luck
@merten3000 thanks for that for the next 30 days i can make working cabs, i initially seen your post and checked the program but noticed it was only a 30 day trial so i never bothered then with your last post when u mentioned "encrypted" files that sort of made sense when i originally seen the file names of the files i was extracting where as they are now extracting properly and i created a working cab, thanks very much.
Dont suppose you know of a free program that will do the same job? Money is tight and cant justify buying this app.
Alex
The simplest thing to do, for me, would be to take the stock rom that you like, extract and recook it making only the changes needed to make it UC compliant.
That way you get your rom just as it was, and can run all your cabs. Shouldn't be much work either. (well, it wouldnt be on the Kaiser - not used Raphael kitchens etc, but assume it is relatively easy)

Advice on RAMdisk and/or Extended_Rom

Hi There
I have spent a few days researching and searching the net but I still haven't been able to find a solid answer to how you can create a hard reset resilient piece of software that is user installable rather than having to manually tweak extended roms etc.
I have a piece of inhouse software that is hard reset resilient on CE 4.2/5.0 devices but I need to port the application to some new WM5 & 6 devices and I am currently testing a few different models. I have looked at the excellent work in the Extended_Rom discussions on this forum and tweaking the config.txt and unlocking and adding my cab would be perfect for me apart from I need to do something that will do all of this on a simple user install. The user will install the cabs, the device will need to burn the app into the Extended Rom so that if the device is subsequently hard reset the software is still running.
I understand that I will have to write a different cab for different handsets (For slightly different reg settings), thats not a problem and using c# I am able to do most of this in a cab, but the questions I have are below:
1. Is extended_Rom a WM5 thing only or is it a device dependant thing? What do I do when there is no Extended_Rom, like with the Kaiser/TytnII? and is it a reliable method of doing this!?
2. Are the last 2 lines in the config.txt always the same (LOCKisabled
RST: Reset), so that I could reliably insert some extra CAB: lines ahead of them?
2. Is creating a RAMDisk a better option and is this something that would offer a more generic solution to me across all devices?
3. Is there a proper industry standard/MSDN way of doing this!?
There are pieces of software out there that are doing this like B2M mProdigy's device management client so it must be able to be done.
Any help or advice would be very much appreciated.
Regards
DaveK17
Any ideas....anyone?
I'm begining to think that this is not possible in the Consumer world of WM. I guess i'm too used to the rugged market where the manufacturers provide this kind of resilience themselves.
Would this be the right line of thinking?
Any help is appreciated
DaveK17
The extended rom is for some of the older phones made before the HTC Touch series and the TYTN II. It is uses across all Windows Mobile versions since the phones need it.
I think I can help you with the config.txt part as well. The last two lines are always there and yes you can put in the relevant lines above them which would be:
Code:
CAB: \Windows\path\to\your\cab
So provided you can make the cab file apart of the ROM then you should be good to go.
As for the RamDisk, I would recommend against it unless you'll be including the relevant software into you cab file. Window Mobile doesn't come with one by default.
I haven't looked into the msdn for this aside from Windows CE 6 so I can't help you there. But I hope my answer help you...
Regards,
Soul_Est

OsKitchen support for Herald

Hi friends !
I'm usually trying to cook for my Kaiser, using OsKitchen. I could obtain 3 or 4 flashable ROMs -lots of disaster ROMs too- and now I'm trying to obtain a "decent" ROM with everything well located.
Then, I tried (I like Thahny25's ROMs made in Ivan's kitchen but I'ld like to create my own ROM and share it) to use Ivan's SuperJustKitchen, but it seems too difficult for me; also, thus I must spend more space in my Hard Disk as I can't have no shared folders with OsKitchen to cook for Herald/Wing and Kaiser.
So, I wondered to include Herald's files into Oskitchen structure. But as you maybe read on other places, I'm not an expert in this, but on building, landscape and environment (and this is too far from coding, programming, etc.).
Maybe some of you could use OsKitchen to cook for Herald/Wing. Or maybe some of you know "where to place" every file from Ivan's kitchen into OndraSter's one. This is what I'm asking to any charitative aim who can explain this.
Yes, I know I could ask OndraSter but I think he's busy on other things and also he does not know Herald's world but Kaiser's one.
TYhank you and forgive me the inconvenience, if such considered.
I was working on helping the developer port OsKitchen to the Wing earlier, but he got too busy.
It's an incredible kitchen, and I'm sure he'd help you port it to the Wing for us. It's the best kitchen I've ever seen!
http://forum.xda-developers.com/showthread.php?p=4854633
Well, Ivan/Ervius/Bepe kitchen is amazing, but for my degree of expertise, OndraSter's one is better for me.
@ace....
Yes, I remember you wrote something there. Now we must "only" put the files in the correct folders, but I'm trying to take the files from Ivan's structure into OndraSter's new one and I'm missing. Then, it's supposed the kitchen works for any device we want.
afn691 said:
Well, Ivan/Ervius/Bepe kitchen is amazing, but for my degree of expertise, OndraSter's one is better for me.
@ace....
Yes, I remember you wrote something there. Now we must "only" put the files in the correct folders, but I'm trying to take the files from Ivan's structure into OndraSter's new one and I'm missing. Then, it's supposed the kitchen works for any device we want.
Click to expand...
Click to collapse
I guess I might be able to look into it again tonight. I'll see.

Bog standard Rom

Hi, is there such a thing as a bog standard vanilla rom, as XP is to the PC?
or does this not exist, do you have to have all the correct drivers for your device in the same way you would have to with XP for instance?
If so, I wonder could anyone tell me where I would lift the driver files from within windows mobile 6.1?
Alternatively, is there any way to just upgrade to 6.5 from 6.1, and keeping your driver base?
thanks,
Mike
Oh, were it that simple.....
Your XP CD has the most popular world languages and the vast majority or drivers already on it. The installation asks you for your main preferences and sorts the rest of it out as best it can.
PPC ROMS are built to one or a handful of languages, and are targetted at a particular phone with a particular hardware config. They are built by HTC and/or various Telco's using Microsoft's CE Platform Builder. The drivers are added here and the ROM image built.
The chefs use various tools to unravel the ROMS, mix and match, add extra bits and pieces, then rebuild them, but they still have to target a particular phone/hardware combo or you may find parts or your phone fail to function properly.
The only thing that can be considered 'Bog standard' is the original ROM that your phone came with or any updates on HTC or your Telco's site. Once they stop supporting that model, you would have to rely on the ROMs that the chefs produce here.
Ohhhh dear, well for a start I don't have a HTC phone, I have a Ciphone C6, this means I'm waiting for the support forum for my phone to release the proper ROM.
it doesn't looks like it will be that long, but I was just wondering if I speed things up, how easy is it to pull a rom apart and take out the driver base?
Would the driver base used for 6.1 actually work with 6.5?
Mike
As regards the last question, I'll stick my neck out and say they probably would. There is not much difference between 6.1 and 6.5 and the drivers were probably written in Win32 C++ anyway.
As regards how to get at this stuff, then it is over to the chefs. My expertise is in this area is on the application development side, not ROM extraction or cooking.
There my be some pointers in the WIKI. Anyone want to shed any more light?.........
this guy seemed to get some of the way there, but the thread seems to have just died, maybe someone can pick up the story here
http://forum.xda-developers.com/showthread.php?t=596076
Mike

Categories

Resources