Database Users

and what if someone (me) can not afford to break anything?

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

WM6 image

Where to get a WM6 CEOS.nbf file ?
since the Updater has 4.nbf files :
CEBL.nbf
CEOS.nbf
RadioFS.nbf
RadioOS.nbf
i guess the CEOS.nbf is the OS, if replacing it with WM6 nbf and trying if it works would harm the pda ?

which flash utility will you be using. If the rom is for the ipaq 6900 and formatted properly then it will not harm the pda. (but this rom does not exist) at lease we dont have it. So if you do this you can damage your pda. Which rom and utility are you planning on using?

*should* be doable
unless you replace nbf BL file (for bootloader) you should
always be able to enter BL mode even after catastrophic
flash failure. NOTE THOUGH: This is just pure speculation.

Yea but if i change the CEOS file with a standard, not modified for any phone WM6 image, should this work ??
afbcamaro : have a friend at HP who can make me and update with any CEOS file...
P

If you replace any stock WM6 ROM file with the hp one, you should theoretically not harm the pda as long as the BL.nbf and radio nbf files are not used. but when using another rom and you find out it fails it wont do any good that the device is not harmed since it cant be brought back to stock because we have no stock rom CEOS.nbf and EXTRom.NBFs...... So until we have the stock firmware then yes it will make your device useless, but if we did; no it should not hurt it....

Please continue this thread at
http://forum.xda-developers.com/showthread.php?t=315359
Thank you!

prepare_imgfs for ipaq HW69xx

Hi, after some research (German and Spanish ROM from HP, and dumped ROM from spgi), I present you a modest modification of prepare_imgfs which works with the ROMs is it supposed to.
Of course, the dumped ROM from spgi doesn't need it to be correctly extracted since it's a dump (and dumps are not encoded!)
to use it:
prepare_imgfs.exe CEOS.nbf -i (or -ipaqHW69xx)
and then to extract the content (a dump directory will be created):
viewimgfs.exe imgfs_raw_data.bin
Modifications "should" work but I cannot test it (I just did it for pleasure).
Of course: thanks itsme, mamaich and all gurus who share source code.
Modifications: rate=0x10089; step=0x10000; skip=0x89;

and now make_imgfs
USE IT AT YOUR OWN RISK...
make_imgfs.exe YOURROMFILE.nba -i (or -ipaqHW69xx)
Should work (tested by comparing a ROM with a decrypted and re-encrypted ROM => no change).
As addfile/delfile/buildimgfs works only in nosplit mode, the imgfs_removed_data.bin file could be invalid, so keep a safe backup of these data (just in case) and restore it before using make_imgfs. That way, the imgfs_removed_data.bin file will remain as valid as possible (if it's a CRC or sth like that... it could not work).
Try to make a very small modification (like a background image) to see if it works before cooking.
Good luck!

Need more info
Try to explain with more details.
Drahtman

I don't know!
drahtman said:
Try to explain with more details.
Drahtman
Click to expand...
Click to collapse
I don't even have a 6915!
All I know is:
-nobody made it for 6915
-based on a correct imgfs_raw_data.bin + correct imgfs_removed_data.bin + correct ROM (for bootloader and headers), you obtain a valid ROM
now you have to find how to create a correct imgfs_raw_data.bin and a correct imgfs_removed_data.bin. More informations are available on ROM kitchen making guides (all along the threads) and one of the already found methods may work (with small modifications)
I tried to make a buildimgfs, it should work but some things in the source code are obscure to me, and doesn't permit me to validate the tool...
But you can find it by yourself... I made those tools without having the device... you have the device, you could try WITH MASSIVE PRECAUTIONS! read all ROM problem threads to be sure you cleared every possible problems! Reading is the only thing important in such operations... Then try to create a ROM, see if this ROM can be dumped as an official one...
You need to try to use USB Monitor during an upgrade to see if more informations are needed (if we could be sure imgfs_removed_data.bin is useless, it would make the thing easier)
Read, Read, Read!
Many others problems (CID Unlock) seem to have be done, but nobody shares the how to, same for ROM Dump from device...
It's just sad the 6915 community doesn't try to solve their problems by themselves... I mean the community as an ensemble...

bumpity bump

Will Try Soon, And Post Results
I have did this about a 8 months ago, and got some error, my data cable is broke, so once my new one gets in I will post the results

This doesnt extract the ROM right? This lets us play with it after? We still need to find a way to extract the ROM without errors.

Backup Everything
Please man, If you want me to port a rom, I still need this with the errors,
mdelleman said:
This doesnt extract the ROM right? This lets us play with it after? We still need to find a way to extract the ROM without errors.
Click to expand...
Click to collapse

I have backed up everything I can with awizard. It is posted in your WM6 port thread pg 3. Awizard won't let me backup the radio but I have a copy of the OS. I'm not sure how we can get all of it, no one has had any luck getting a complete backup.

mdelleman said:
I have backed up everything I can with awizard. It is posted in your WM6 port thread pg 3. Awizard won't let me backup the radio but I have a copy of the OS. I'm not sure how we can get all of it, no one has had any luck getting a complete backup.
Click to expand...
Click to collapse
Try this one also, post that, in the meantime I will work with your awizard os backup.

[Help Request] Live ROM Update

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

Hello Wm61 question

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 :]