Objective :
Create an Update Utility based on the Windows Update in Official ROMs
Description :
My idea is to create a ROM that can be updated without the need of RUU we use now. For example, you have Core2.0n version of my ROM and since you installed it, I created another version, for example Core3. In order to update you'd normally have to download the latest ROM to your PC and re-flash your HTC Wizard.
I want to allow you to go online directly from your Wizard and check for new version. If new version found, then automatically download and flash. All you'd need is an Internet connection.
Limits/Problems :
There are some problems about this. This is where I need help.
Usually the PPC turns OFF and then the RUU writes the ROM. With the way I want it, the ROM must be written while the device is ON...and then it would do a Hard Reset in order to complete the Update.
I don't know yet if this is possible, but I am willing to try.
What I need :
People with Assembler knowledge
People with good PPC knowledge and understanding
Huge amount of luck
I remember someone here already tried to restore the Windows Update components. Unfortunately I can't remember who and if he succeeded or not.
I'll search for his thread and post any update.
The ORIGINAL thread is located HERE. Please feel free to join the development crew.
The idea looks cool, it will allow us to redistribute updates and fixes to our roms more easy
But we have to figure out how the windows update feature is working, and how it manages to flash the downloaded update
I think that it downloads the updates to the storage card (in most cases there is not enough space in storage to store whole rom image) and then instructs the boot loader to flash the file from the card (this way it will be logical)
Also that way will be similar for all devices not just the wizard.
So the rom cookers can personalize windows update settings to update their roms trough it (of course separetely for every device)
xplode said:
The idea looks cool, it will allow us to redistribute updates and fixes to our roms more easy
But we have to figure out how the windows update feature is working, and how it manages to flash the downloaded update
I think that it downloads the updates to the storage card (in most cases there is not enough space in storage to store whole rom image) and then instructs the boot loader to flash the file from the card (this way it will be logical)
Click to expand...
Click to collapse
I think we'll try to do that. However I doubt that Microsoft intended to use a Storage Card for update. This makes me curious on what method they would have used.
Other problem would be error checking...We must know for certain the OS is not corrupted before attempting the update.
Maybe I didn't said it...but I will say it now. My intention is only to flash through the air an OS, that means no other components, like SPL, IPL , radio or SplashScreens will be altered by the Update so no chance of bricking the device plus making the whole process easier to accomplish.
Other idea is to study the way that security programs (anti theft) use they're software so that the data is included in the rom with a simple install.(they say the program will be there even after a hard reset...though i didn't tried any)
I am sad to notice so little enthusiasm from people around here.
This would affect chefs more than regular people but still.
Back to business...
Questions :
Is it possible to flash directly the ROM with the PDA turned on ?
If so, how can we access the ROM directly ?
How to use .pkg ? Can we make use of them ?
Considering the Update deals only with relative minor changes, this means we can leave the XIP out. We can think of new Builds as major upgrades and require the use of normal flash. The big problem..and unfortunately the thing I know less about it's managing to insert the new update in a very "raw" manner.
I am firmly convinced that few people here posses the knowledge to do this.
Please come in front and let's make this thing happen.
I could try to reverse engineer the default windows update but it would take a great deal of time and I would probably get stuck without some help.
P.S. I managed to find the thread I was talking about before. It's located here.
I think is a great idea my friend. However there are many things to think before trying to do it. First of all to flash the new files you shall need to make a pdoc write but i have now idea how can be made via the device itself.
Where are the "patches" being stored before they are updated?
May be the process of hard reset shold be manual. This are only some toughts.
i would help u as much as i can...
great idea !
the update can be on the storage card and one can put the device into
bootloader/update mode by running this little program in the windows dir
to switch it to the 3 color screen.
With this WM5torage program i can acces the romchip itself and write it.
not sure wether it messes up things.
not sure if this will delete contents of the storagecard itself...
another thought... why not make the updatepackage and let windowsupdate install it for you ?
I think the best way to procede is to find out how to make a pkg file (faria seems to know) and then to sniff what the windows update app does when connecting to the MS server and see if we can emulate that on a test server.
Midget_1990 said:
I think the best way to procede is to find out how to make a pkg file (faria seems to know) and then to sniff what the windows update app does when connecting to the MS server and see if we can emulate that on a test server.
Click to expand...
Click to collapse
All your ideas are great. But this was exactly what i had in mind. It seems the easiest way....only so little time right now. So...where`s Faria ?
P.S. Sorry for late reply...i thought ppl don`t care and i didn`t checked the thread
Does somebody of you have such a pkg file?
As I understand it right, this file will be delivered by windows update to the client?
I never got an Update via Windows Update... Everytime I try, there are no updates available ^^
Sniffing the Windows Update would be easy, I think. I could bet that all this stuff is done via a Webservice. That's the I would do it
Has anyone ever updated anything using that Windows Update? It's highly unlikely it will download a whole new ROM, maybe just some cabs which won't touch the ROM altogether, just mess around in registry.
And who needs to keep the device on while updating if you'd make a hard reset afterwards?
It can even be done now...
any back-up program
a cook who's willing to release ROMS on some stable host (NOT rapidshare where address changes)
a diff utility to download only the parts of the ROM that changed
A small app which writes XXXXIMG.BIN to storage card and enters bootloader.
Much harder task is to get rid of ROMs altogether and take control of the only advantage they give: XIP. I mean, why don't use a tool to convert the new apps to XIP format making them a part of the ROM?
@anichillus
I can provide u with the package but it will take some time..u see i have WM6 Emulator..but cant make it to use Internet Connection of my PC..so the Update manager starts but doesent download (no connectivity)..will see what i can do
i got the internet working..but when i click update..it doesent give any packages..what now
Related
I wanted to install one of the ROMs from www.yorch.net. But before doing so I have some questions:
1. If I choose to build ROM as an installer.exe, is installing it to my device as simple as running the .exe file? (of course with the device connected thru Activesync)
2. Is my present ROM (see specs below) supported?
3. If Murphy comes to visit and I screw up, will my phone be completely unusable or can I just reinstall old ROM, do hard reset and everything will be back to how it was?
My specs:
OS: Pocket PC ver 3.0.12039
ROM:3.20.06 ENG( 07/30/03) (O2 Asia I think since I bought it here in the Philippines)
Radio: 4.21.00.
Thanks
1 as far as i know yes havent don it to my own device yet though
2 a rom dont have to support a rom since it'll overwrite it
3 of cause merphy can also show his ugly face
but if all fails a sd flash reader writer can save many a tears
also if your phone is working ok then i would not mess with the
radio stack and beware because some roms include the radio stack
and if you try to update your radio stack to a US (900/1900) and you network is 900/1800 you could be in for a world of pain
ROM upgrade step by step
OK I'm really dying to give it a go but I'm just a overly cautious bloke. So I'm gonna outline what I interpreted (after reading lots of posts I think I'm getting it but not sure) to be the way do the upgrade. Please correct me if i'm wrong:
Equipment I have:
1. My notebook (Windows XP, Activesynch 3.7)
2. O2 XDAI
3. Cradle and USB connection.
Steps that I think I should take:
1. Place XDA on cradle and make sure it's connected with PC.
2. Backup?? (not so sure what to back up since contacts, calendar, notes are synched with outlook, docs are also synched, I have copies of cab and program files since I download them to PC before installing them to XDA.) If i'm missing something please slam a frying pan (this is a kitchen right?) on my head.
3. Go to www.yorch.net, check mark on all appropriate options, then (since I have to Unix box and dont know Unix at all) just go for the easy option of cooking the .exe install file.
4. Assuming, the .exe is downloaded to my PC. This time I just run it. I expect this to be just like installing PPC apps. If not, throw a tomato on my face
5. Assuming everything worked and Murphy's in the Arctic freezing his A**e off, then all I do now is hard reset.
6. I have a new ROM and I'm singing happy-happy-joy-joy.
To the wonderful people at xda-developers, am I in the right direction or am I as lost as Bill and Ted? If I'm lost, is there a step-by-step guide for non-unix programmers? (Sorry, there was a sticky but I thought it was for people with Unix boxes)
Once again, thanks for all your help and your patience.
2. Backup?? (not so sure what to back up since contacts, calendar, notes are synched with outlook, docs are also synched, I have copies of cab and program files since I download them to PC before installing them to XDA.) If i'm missing something please slam a frying pan (this is a kitchen right?) on my head.
Click to expand...
Click to collapse
well i can think of one thing to backup and thats your current rom
so if you dont like the new rom you are getting you have the option to go back
of cause if the rom you have now is downloadble from a place you know like your isp then maybe it dont matter
Thanks for the reply. That's a good point. Question: When you back up old ROM, is it just the ROM that gets backed up or is it the whole content of the device, like how you do in PCs?
Also, since no one, besides you, has made any comments regarding the steps that I outlined, is it safe to say that they are the correct steps?
Thanks
When you backup your ROM, no stuff that you customised will be in the backup - the backed up ROM will be the same as when you received it from your retail shop, or if you upgraded, it will be the upgraded ROM without any of your stuff. Do a backup and store it on your hard disk.
DON'T use the .exe cooked ROM, use a .nb1 or .nbf, and use XDA Tools from this site to do the upgrade. It's very easy that way, and less dangerous. Don't upgrade your radio stack unless you know exactly what you're doing, or your phone supplier has made an update available just for you.
If you use a T-Mobile ROM above version 4.00.05 it blocks the XDA-Tools from updating the ROM. At that point you need to use XDARIT (from this site) to low-level write the ROM image you have onto your SD card using an SD card reader which shows the card as another drive on your computer. Once you do that you need to boot into the boot-loader (press the reset button while holding the power button) and follow the prompts to restore from an SD card. If you're unlucky and are running bootloader 5.17 (or above I think) you need to write the bootloader diagnostics patch (wallaby patch from this site) onto your SD card first before doing the boot into the bootloader thing. You can then remove the SD card, write the O/S ROM onto it with XDRIT, and put it back into your phone while it's still sitting on in diagnostics mode. Then you can restore from the SD.
It sounds complicated, but it's easy, as long as you have an SD card reader, and as long as you don't mess with trying to update the bootloader or do an unknown radio update. There's lots of info in these forums if you get stuck.
I made a thread that summarised all the steps using the new tools and ROM's at this address : http://xda-developers.com/phpBB/viewtopic.php?t=3860. It's for Asian/European users, but if you are in the US the instructions are the same, except instead of using European 900/1800 radio you use 900/1900.
Further questions on ROM update
Thanks. It's becoming clearer and clearer. Have more clarifying questions:
1. How do you know whether or not you're including the radio stack with the ROM upgrade at yorch.net. I did not see any options there.
2. At www. yorch.net, nothing happens when I press the "Build ROM Now" command button. Is the download supposed to happen in the background or is there something wrong with my PC or the site?
3. I dont think I'm using the T-mobile ROM but how do I know if I'm runing bootloader 5.17? Is bootloader 5.17 only for T-Mobile users or all?
Once again, thanks for the help and bearing with a newbie.
2. At www. yorch.net, nothing happens when I press the "Build ROM Now" command button. Is the download supposed to happen in the background or is there something wrong with my PC or the site?
Click to expand...
Click to collapse
it should start to write some text about the progress of making the rom
and when it's finished then it should init a std download dialog
The meter down at the status bar does move, same as when you're loading a webpage, then it says Done. That's about it. Didnt see any other messages or dialogue boxes.
Can anyone confirm if it's up today or has it been down?
Thanks
PS. Tried to email using the email utility at the website but getting errors there as well.
OK, firstly to answer your question about Yorch's site... well it worked for me in getting all the ROM's I wanted, then when I went back again the download didn't work. I guess it's just on and off, so unless Yorch finishes getting married or someone else makes another kitchen it's a matter of pot luck. You can get away without using the kitchen if you can find another download source for ROM's, whether it be FTP or whatever. Just remember if you get an exe you can usually pull it apart with winzip to get the .nb1 or .nbf out of it.
Now, for Q1 :
An operating system ROM is generally just under 32MB, but when zipped from Yorch it's usually about 14 or 15MB - the operating system ROM will NEVER be smaller than that. I'm not sure about the exact radio stack size but I know it's a lot less than that. Also, doing some homework about the operating system ROM helps. eg. reading about the 4.01.00 ROM tells you that it's not a radio stack upgrade, it's an operating system upgrade - and the filename and the size of the file you receive reflects that.
Q2:
answered above...
Q3:
I think the bootloader is just pot-luck depending on when you phone was released. To check your bootloader it will reset your device completely, but I read somewhere that if you turn the radio (phone) off it doesn't hard reset. If you're worried, do a full backup first. But basically when you're ready to look, reset your phone while holding the power button and it will tell you the bootloader version. Don't be too turned off by that, I have read that SD card readers can be picked up very cheap if you look around, and that's all you need to get you out of trouble regardless of the bootloader version.
There's no real risk (but I won't guarantee anything), just make sure your phone is fully charged before mucking about with SD upgrades. Also make sure the radio (phone) is switched off before upgrading... using the bootloader/sd card method you shouldn't need to be concerned. I'm not sure what effect having your phone on and receiving a call while using XDA-Tools can have, but someone did mention it somewhere.
I'm a newbie too, but there's really not much you need to know, just a few caveats.
Yorch's Kitchen has been working OK for me the last couple of days. It takes maybe about 5 mins to "cook" before telling me that the ROM is ready. The 4.00.05 ROM gave me a lot of ActiveSync problems, so I went to the 4.00.16 ROM tonight and it looks like it's behaving better.
My SD reader is a Microtech Zio. It appears as a disk drive in windows, but the newer XDArit can't initialize a connection to write to the SD card. I used the "dangerous" older version of XDArit instead (available on Yorch's site), and it's worked OK for me (so far?).
One thing I wish I had realized before I started playing - going into the bootloader will reset your phone most (some?) (all?) of the time.
While I was flashing the ROM tonight I could see the GSM light flashing - I had the same "hope no one calls" feeling tht others must have had. Note that this was while I was flashing from an SD card in the bootloader - so apparently the process doesn't deactivate the phone while it's ongoing.
Muchas Gracias!
Ebswift, if ur a newbie then ur the god of the newbies. Thanks for all the help and for making me see the light. Much appreciated...
A quick Q:
Is the process for installing an .nbf file the same as that for installing an .nb1 file?
I have cooked a few ROMS to an .nb1 format and installed those OK, but now I have one in .nbf that I'd like to install.
So what I'd plan to do is put the nbf onto an SD card using XDArit, and then stick the card in the PPCPE and reboot to the loader. Is that it?
So what I'd plan to do is put the nbf onto an SD card using XDArit, and then stick the card in the PPCPE and reboot to the loader. Is that it?
Click to expand...
Click to collapse
You can do it that way (onto the SD card), or if you're not already using a T-Mobile ROM you can use XDA Tools which is easier. Basically the capabilities are spelled out for you with the available file types in the drop downs when you select a source.
Instaead of Hi I say you are great people
So the case is... I just need to have working Qtek 1010 with SOME additional soft on it inside a ROM...
I've read many pages in this forum and I'm able to find too many ways to change my ROM. I'm totaly confused.
I work for extremaly big worldwide company and they gave me q Qtek, told me to use it, gave me one simple application and web link... so I do.
But the Qtek is much powerfull than that so I need to flash my ROM.
Now comes a question: where can I find one document how to prepare for it, what tools do I need, how to do it... I know after some tries I will be confident enough to do such stuff easlily, my problem is I have only one try, they will make me w trouble if I screw my company recource.
I understand you had milion similar questions like that. Basicly I need help how to flash so I can be sure 100% not less that I can recover in case of trouble. I hope you understand I'm afraid to do it because lack of experience and you are able to tell me if I should try to flash...
or maybe it's better for me to ask my boss to by me a 512 MB SD and install all additional soft on it and stop worring about memory?
I'd appreciate any opinion... you are the best and I'm just new to this bussines...
Get an sd card, backup existing rom to sd card, very easy to do by bootloader method. Enter bootloader by holding down power while inserting stylus in the reset hole on the bottom left of pda then press top right function key, then choose ce to sd. Once you have done this you can check if it has in fact backed up your rom by putting sd card in the pda, enter bootloader, it will then give the option to program the rom, just remove the card and push the reset with stylus again, the other method to check a working backup is to put the sd card in the pda, the pda will ask to format it, say no and remove it. Once you have a backup you can either use xdatools to copy it to your pc or keep it in a safe place, no more files must be written to this card otherwise it will be rendered useless, if you wish to reuse the card sometime it will need formatting. Once you have your backup, go to www.yorch.net, cook yourself a rom and download it in the exe format, this will do a normal install from your pc while connected to pda via activesync, if it messes up you always have your backup. Once you become more proficient at using xdatools you might wish to try out lots of different roms until you are happy with the result, you can go on to sd card flashing which is a much better way of programming rom and much less prone to error because it doesnt rely on a pc connection. I would advise you to leave the radio stack alone, if you can make and receive call ok leave it alone. Have a thorough look around the forum before proceeding. Its good fun to program your pda and you can make it a much better tool, but make sure you always have a way out if things go wrong.
www.yorch.net not working... is there a place like that?
Hi!
I read the above post, one of the clearest here, and I almost got the confidence to finally do this ROM update...
But:
1) Can't find the www.yorch.net website where I could "cook myself a rom and dowload it in a .exe format"
2)It's still not very clear to me what exactly cooking a ROM means: it concerns the OS (the version 1.53, 1.72 type of stuff), the extended ROM (the default programs u get starting after and hard reset like the SW for the camera etc) or both?
Thanks!!!
Chris
Another ROM Kitchen
Try the following ROM Kitchen http://lumpistefan.dyndns.org/
I noticed that you have the XDAII. Now, someone please correct me if I'm wrong but the directions above and the ROM kitchens are all for the XDA I or Wallaby version.
Re: www.yorch.net not working... is there a place like that?
cchris said:
Hi!
I read the above post, one of the clearest here, and I almost got the confidence to finally do this ROM update...
But:
1) Can't find the www.yorch.net website where I could "cook myself a rom and dowload it in a .exe format"
2)It's still not very clear to me what exactly cooking a ROM means: it concerns the OS (the version 1.53, 1.72 type of stuff), the extended ROM (the default programs u get starting after and hard reset like the SW for the camera etc) or both?
Thanks!!!
Chris
Click to expand...
Click to collapse
Chris,
Those Roms are made for XDA1 beware it's not made for the device you have!!!!!!
What's the kitchen for XDA II
THANK YOU!
I was starting on the wrong foot... :-( :?
Anyway a couple of more question:
1) Is there a place like that for XDA II Kitchen? Is my undestanding of what a kitchen is correct?
2) The process for ROM backup outlined above, is still correct for XDA II?
Thanks!
Chris
I'm in the same boat as you CChris. I've been diligently a daily searching through the numerous topics on this site looking for similar information. I haven't found it yet - or at least nothing not-to-super-technical. I do know that you get to the bootloader by pressing the power button, reset button, and down on the toggle at the same time rather than the Wallaby way of the power and reset buttons only. It also seems that there are issues regarding 'country' and that it requires software to get around this. I haven't found the software yet - the links that I've seen all point to "itsme's" website which is currently down.
You can read the thread here: http://forum.xda-developers.com/viewtopic.php?t=9053&highlight=
Hopefully, someone with a lot more knowledge than me can go over updating the XDA II as clearly as cruisin-thru did for the XDA I.
The instructions on http://wiki.xda-developers.com/wiki/HimalayaRomFlashing are correct.
Unfortunately, there was an issue where the wiki removed the ~ from itsme's website's address. It's been replaced with %7e and now the link works.
If you download a ROM from the same vendor as your device (e.g. Qtek ROM on Qtek device, iMate ROM on iMate device, etc.) you don't need to use these instructions, you can just install the ROM upgrade from your vendor.
If you want to use the latest ROM (from iMate) and your device isn't an iMate, you need to decrypt, change the "country" code, encrypt, and then run the upgrade.
You can also edit the extended ROM when flashing, but it's easier to use itsme's extRom Tools. See http://forum.xda-developers.com/viewtopic.php?t=8422
You do NOT need to flash the ROM if you are not experiencing problems, or if you are experiencing problems which the new ROM also has (for example ugly cleartype fonts, which may be fixed without flashing). Flashing the ROM may void your warrantee. You will lose all your data when you upgrade, and you should not restore a backup, only your my documents folder.
If you are a newbie, it may be best not to flash your ROM. If you typed in itsme in google, you would have found his xs4all address as the third link, and would have quickly found out his site wasn't down at all, but the link was just wrong.
Just a warning: the things that could go wrong when flashing are potentially much worse than a wrong URL, and the answer to those problems won't be the third link in google.
NO MATTER WHAT YOU DO DON'T COME NEAR THE RADIO UPGRADE I QUOTE I FRIEND HERE THAT SAYS
DON'T MESS UP WITH A WORKING RADIO OR YOU'LL END UP WITH A SLIVER BRICK !!!!!!!!!
BEEN THEIR :x :x :x :x
Rabia said:
NO MATTER WHAT YOU DO DON'T COME NEAR THE RADIO UPGRADE I QUOTE I FRIEND HERE THAT SAYS
DON'T MESS UP WITH A WORKING RADIO OR YOU'LL END UP WITH A SLIVER BRICK !!!!!!!!!
BEEN THEIR :x :x :x :x
Click to expand...
Click to collapse
Rabia can you tell me how did you get out from there?
never got out of it
Please please reply it.
I want to make my application part of ROM my three PDAs. ( I have XDA2i, PDA2K and K-Jam), so machine will have application after hard reset. (i don’t want to write FLASH Memory \Storage\1257 etc i think any one can delete that)
Q1) is there any installer available which deploy to ROM and make desired application part of ROM.
Q2) to upgrade any ROM , is it must to have base ROM ?
I really thankful for your feedbacks
Khurram
Hi Khurram!
There are no installers that can put apps in to device ROM. If you want to add to the ROM you need to do the following:
1)Extract ROM image (or get one for your device from somewhere).
2)Decrypt the image (nbf file) and extract all files.
3)Add your app
4)Repackage and encrypt the image.
5)Reflash your device with the new image.
The tools to do it are on this site (check out ROM kitchen), but this is a complicated process, and there is a good chance you will wind up with a useless device which won't boot.
So you should read up on ROM cooking and be very careful when altering ROM images.
Good luck!
Hello levenum,
Great reply , thanks a lot . you are the only person who replied me now and in past as well.
in past, you suggested the "file store".
Problem: it is not a secure way , any person can remove it from the device.
does any one have idea about Extended ROM or any other secure and risk free way ?
Thanks
[/list]
Hi Khurram!
When you first posted you didn't specify your program was sensitive, and you didn't want people deleting it.
If it's really important Extended ROM is not good ether since it can be unlocked and manipulated just like the File store. There are unlocking tools in this forum.
If your program is some kind of anti-theft app. (in case your phone gets stolen) the only way to ensure no one messes with it is to put it in ROM.
Of course even then someone could re-flash the device with an original ROM,
so nothing is 100% secure.
Great , really impressed in way you picked my point.
i am working on such a application , actually 3 months ago I lost my newly purchased XDA2i , luckily i got that back with the help of mobile operator but I want to developed such a application which will lock the machine totally and will not allow re-flashing as well.
Q: stop to re-flash is possible?
Q: any existing tools for anti-theft ( i saw something at ROM Kitchen but it is for specific versions only)
any further help will be appreciated.
Thanks Again.
Yes, there are projects like this here:
http://forum.xda-developers.com/viewtopic.php?t=46174
Although, I don't remember anyone trying to put the app in ROM.
As for preventing device from re-flashing:
It is possible theoretically, but would require serious programming skills, and good knowledge of hardware.
There is a special program, called bootloader, which is responsible for loading the OS or writing a ROM update to the device. The only way to prevent re-flashing would be to write one of your own, and even then getting it on the device would be tricky.
Any way, that kind of knowledge is way beyond me.
But I do have one question you should consider:
Does your program need to save data, like SIM details for authorized SIMs or changing password?
Since this data cannot be written to ROM dynamiccaly, you would have to compile your program for each user\device specifically, and the password would have to be hard coded.
yes my application will be extention of existing security tools with more control of device something confidentional :twisted: .
the only problem is prevent from deletion so thats why i am worried about it
I didn't mean for you to tell me what your program saves.
I just wanted to point out that while preventing a program from being deleted is possible (I don't think many thieves would bother re-flashing a device, specially if your program would make it look as if the device is malfunctioning and not locked, only the user will know what to do)
its impossible to save settings so they will not be deleted.
If you are making this program only for your self, than fixed password, or SIM info is not a problem, but if you intend this for other people you will have to come up with some solution to store the settings securely.
At leas for this you may have to use the File store.
So I flashed Energy ROM not too long ago and I had to back up a number of applications on my phone to my SD card before I did it. Knowing that I might flash newer ROMs as they come along, I figured that I might as well keep everything on my SD card permanently. The only problem with this is that WM doesn't know it's installed. That is to say that whenever I update an application, the device treats it like a new installation and doesn't ask me if I want to uninstall the old version first. Secondly, certain applications (like most of Astraware's games) don't appear to be happy opening unless they're installed properly (I assume it's expecting certain registry keys to be there).
So what have most of the ROM flashers on this forum done to make sure all of their applications are working right immediately after a new flash?
SlyMaelstrom said:
So I flashed Energy ROM not too long ago and I had to back up a number of applications on my phone to my SD card before I did it. Knowing that I might flash newer ROMs as they come along, I figured that I might as well keep everything on my SD card permanently. The only problem with this is that WM doesn't know it's installed. That is to say that whenever I update an application, the device treats it like a new installation and doesn't ask me if I want to uninstall the old version first. Secondly, certain applications (like most of Astraware's games) don't appear to be happy opening unless they're installed properly (I assume it's expecting certain registry keys to be there).
So what have most of the ROM flashers on this forum done to make sure all of their applications are working right immediately after a new flash?
Click to expand...
Click to collapse
If you flash a ROM, you have to reinstall all the applications. Some of the ROMS will automatically install your cab files if you set it up. WM has to update the registry for each program, and the details may be different for each ROM, and for each time a particular ROM changes versions. So, yes, you ARE doing a new install.
stevedebi said:
If you flash a ROM, you have to reinstall all the applications. Some of the ROMS will automatically install your cab files if you set it up. WM has to update the registry for each program, and the details may be different for each ROM, and for each time a particular ROM changes versions. So, yes, you ARE doing a new install.
Click to expand...
Click to collapse
But really isn't it silly to do all of that work?
Surely there is something you can change in Windows Mobile that will tell it a specific application is installed on the device. For the registry keys, I can simply write a Mortscript that adds and updates the keys for all of the applications I typically want on the device. If I add an application, I just add its keys to the script. Ideally, I'd just like to run this script every time I flash a new ROM and have all of the dependencies set up automatically. I'm not sure, however, what I need to edit in order to make the operating system thing an application is installed (basically it appears on the "Remove Applications" list)
Yuu need something like this then [UC]XDA_UC Autoconfiguration User To User Thread[23-06-2009]
You should take note that I'm not sure if that's the latest version. But if you throw all your cabs in the XDA_UC folder and follow the instructions of the thread there you'll have it installing ALL your aps automatically when you flash a new rom
Aaron McCarthy said:
Yuu need something like this then [UC]XDA_UC Autoconfiguration User To User Thread[23-06-2009]
You should take note that I'm not sure if that's the latest version. But if you throw all your cabs in the XDA_UC folder and follow the instructions of the thread there you'll have it installing ALL your aps automatically when you flash a new rom
Click to expand...
Click to collapse
I believe that the ROM has to support this feature. So far as I know my ROM (NRG) does not, for example. But if it is supported it is great.
SlyMaelstrom said:
But really isn't it silly to do all of that work?
Surely there is something you can change in Windows Mobile that will tell it a specific application is installed on the device. For the registry keys, I can simply write a Mortscript that adds and updates the keys for all of the applications I typically want on the device. If I add an application, I just add its keys to the script. Ideally, I'd just like to run this script every time I flash a new ROM and have all of the dependencies set up automatically. I'm not sure, however, what I need to edit in order to make the operating system thing an application is installed (basically it appears on the "Remove Applications" list)
Click to expand...
Click to collapse
Well, I actually don't plan to be changing ROMs all that often. So far the latest NRG ROM is working well for me.
Yes, it is a lot of work, but I have all my .cab files in a single directory. So installing them is not that hard. My experience is that this method (or one of the auto install methods) provides the highest possibility of a stable WM environment.
I believe that you could probably create a script to put in the registry entries, but what if the ROM version has changed locations in the registry? Anyway, if you DO develop such a script, be sure and post the results on the forums!
the latest NRG roms do support this.
Aaron McCarthy said:
the latest NRG roms do support this.
Click to expand...
Click to collapse
Ah, good to know, maybe I'll give it a try. Although I actually prefer to watch each step...
Sashimihis?
Have you tried this? Sashimi
Youtube Demo
edit: Sorry for the wrong name in the title, but it won't let me edit that...(my keyboard went nuts..)
-Sblindheim
Hello,
Hoping someone could clear up a couple things for me. At my work we use the mc9090 RFID scanners which run windows mobile 6.1 currently. Currently we use motorola osupdate to push applications in a CAR file once the OS update util flashes the stock rom which are .sig files and .bin files. My question is do i have any chance of dumping the rom and if so would I be able to get it back on the device. Currently i was able to use imgfs tools to dump the os partition into a .raw files but that is as far as i got with dumping. So since they are signed files how would or is it possible for me to get them back on the device? I just didn't want to waste anymore time if i am not going to get anywhere on this. Also not saying that I would be able to use it but is package builder for wm what actually generates the .sig files?
Any ideas about how i could make this work would be awesome or any other ideas. The goal here is for us to have a base wm6.1 with all of our software on it and configured when we image a gun. I am sure motorola would hook us up with microsoft to do this but trying to figure out if anyway i could pull this off internally since we update so much..
thanks
jphilpot said:
Hello,
Hoping someone could clear up a couple things for me. At my work we use the mc9090 RFID scanners which run windows mobile 6.1 currently. Currently we use motorola osupdate to push applications in a CAR file once the OS update util flashes the stock rom which are .sig files and .bin files. My question is do i have any chance of dumping the rom and if so would I be able to get it back on the device. Currently i was able to use imgfs tools to dump the os partition into a .raw files but that is as far as i got with dumping. So since they are signed files how would or is it possible for me to get them back on the device? I just didn't want to waste anymore time if i am not going to get anywhere on this. Also not saying that I would be able to use it but is package builder for wm what actually generates the .sig files?
Any ideas about how i could make this work would be awesome or any other ideas. The goal here is for us to have a base wm6.1 with all of our software on it and configured when we image a gun. I am sure motorola would hook us up with microsoft to do this but trying to figure out if anyway i could pull this off internally since we update so much..
thanks
Click to expand...
Click to collapse
My suggestion is to set up one of your devices with all the setting and configurations exactly the way you want them, and then image that device using a program like Sprite Backup http://www.spritesoftware.com/ It's a tool I use to keep my device secure, since I do a lot of tweaking on it.This way, if any of my adjustments end up breaking it, I can always restore to a configuration that I know works. The same principal should work for what you need.
sprite
Unit ZER0 said:
My suggestion is to set up one of your devices with all the setting and configurations exactly the way you want them, and then image that device using a program like Sprite Backup http://www.spritesoftware.com/ It's a tool I use to keep my device secure, since I do a lot of tweaking on it.This way, if any of my adjustments end up breaking it, I can always restore to a configuration that I know works. The same principal should work for what you need.
Click to expand...
Click to collapse
We tried sprite clone in the beginning and didn't work out right. Some stuff didn't come across right, so not saying i havent learned
enough now to fix that stuff but as far as us implementing it i don't see that happening.
I will give it another look since we have 100 licenses :]