Database Info

Few question about upgrading W2K3 to W2K5

i've heard that WM2003 in himalaya gadget can be uprade to WM2005, it's very interesting and i going to try the uprade, but i have some question about the upgrade, my question is:
1. what's the risk during upgrading? could my device occuring some permanent error?
2. what's the consequence of this? will my device working slower? or working faster?
3. if i don't satisfy with the WM2005 can i downgrade back to the WM2003 OS?
please help me by answering my question

Response:
1. the device may fail, but you can restart the whole process entering the device in bootloader mode and upgrading (happen to me once)
2.Your device will work Faster but sometimes (at boot sequence) will be slower.
that's the price you have to pay. Other thing is there is no MMS in WM5 (dont work for me) and some camera issues, that can be fixed. But is more eye-candy than the WM2003 or 2003SE.
3. If you aint satisfied you can go back to 2003SE just putting the device in bootloader mode and then making the upgrade using a WM2003 ROM (the nbf file)
One thing: Tofclock and Buzz (thanks guys!) are working hard to bring us one stable, better and faster WM5 ROM, so be quiet and wait like me :wink:

Hi guys,
I ve also heard that after you upgrade to Wm 5.0 the phone vibratin wont work, is that true?
what else then?
:roll:
Thanks

Hi dickyw,
my vibration on my Himalaya works perfect...

Hi Guys,
Can anyone help another dumb newbie?
I upgraded my Himalaya to W2k5 OK from the O2 exe file, but I now want to downgrade to 2003 SE.
The folder I am trying to use to downgrade is WindowsMobile2003SE_XDA2_2.20.00CHS-translated.zip
Himaupgradeut.exe gives:- Error 120 Country ID error 1-1-8-n-1
HimaupgradeUt_noid.exe gives:- Error 103 ROM image file not found
XDA image tool gives me:-Unsupported file format error for NK.nbf
I have:-
Boot loader 1.06
CE image 1.72.00
Extended image 1.72.181
Radio image 1.17.00
Am I using the wrong tools, the wrong ROM or an incorrect procedure? I'm doing this for a friend so it's getting very embarassing. Any advice would be gratefully appreciated.
Thanks, Mike

Another issue to aware of when upgrading to WM5 is that you need to also upgrade to Activesync 4.1 as 3.8 won't work any more. Given that AS can be very tempremental it may take some time to get the sync link back up and working to your satisfaction so if your data is cruitial to your work then backup, backup, backup and upgrade when you have a few days free to dedicate to ironing out any wrinkles.
Then also xbackup doesn't work in WM5 so you are left with options like buying the latest Sprint backup soiftware (now WM5 compatible) or relying upon your PC Outlook to be your "backup data" (NB I use the Outlook free "backup" util to back up my pst files on exiting Outlook as double insurance).
Regards - Mallow1
PS I upgraded and v glad I did. Had a few AS issues but eventuall got there (took a lot of reading of forums and As battles, but worth it in the end)

cnimike,
One assumes that you have unzipped the zip file first before trying to reflash? If not try that (say use winzip). Also try reading the wiki as a guide to what to do (seee link attop left of page).
You are also best o use the HimaupgradeUt_noid.exe as at least it avoids the first error (esle you'll have to edit the flash files first and recompile them which is straight forward but if you are a noobie it's a step that can be avoided by using the "...noid.exe") and if you haven't unzipped the said file doing that may well sort out your second error.
Get back to me if you need more help.
Regards - Mallow1

cnimike said:
The folder I am trying to use to downgrade is WindowsMobile2003SE_XDA2_2.20.00CHS-translated.zip
Am I using the wrong tools, the wrong ROM or an incorrect procedure? I'm doing this for a friend so it's getting very embarassing. Any advice would be gratefully appreciated.
Thanks, Mike
Click to expand...
Click to collapse
I would suggest getting a hold of Sin's merged version (details in signature) or XDA2JoJo's version. Simply flash the ROM and you are there. Elsewhere, SIN has set out the steps in the most detailed fashion you are going to see outside a software manufacturer's manual. :wink:

I can not find enithing in this Search

Hi everybody!
I’ve surfed this forum many times, trying to find topics, where I could get info, such.
What are Radio Rom, Extended Rom, and Extracted Rom?
What they include inside?
To whom belongs files nk.nbf and ms.nbf?
What gives new version, when you do update?
What is Bluetooth version 1.0 ----2.0, is it version of chipset, or is it version of software?
Can you change this version of bluetooth, and a lot of questions, where I can’t find any answers over Word!!!
I have seen many times, instead answers just redirect to old topics.
Where do I know, may be from that time this question about WM5.0 is WORK?
I am myself seen QTEC2020i(XDAIIi) complete with mobile 5.0.
Please, answer how to Search(make sentence) and where(index), or answer to one of the many questions above?

Hi YARMen!
I know the search can be problematic if you do not enter the right keywords and even then it doesn't cover the WiKi which is where you should look for most of the answers.
Here are some quick answers for you:
Radio ROM - The drivers and stuff that control the phone WiFi and BT (all the radio) this is separate from the OS and can be updated by it self.
Extended ROM is a part of the devices FLASH that is hidden (can be unhidden with reg hacks and used to store files so they won't be deleted during hard reset). It is used to store provider customization cabs that install automatically after you hard reset the device.
Extracted ROM is a ROM image extracted from a device. Basically you take all the OS, drivers and stuff and save them to a file on the PC for later use.
To whom belongs files nk.nbf and ms.nbf?
What gives new version, when you do update?
Click to expand...
Click to collapse
Not exactly sure what you mean here. the mbf files are ROM images, and updates are produced by the OEMs. (Original Equipment Manufacturers)
Not sure about BT, but I think it's hardware.
That's it.

radio rom also called radio stack
have the software which also control the gsm/umts phone software

Thank you very much for answers!
Not exactly sure what you mean here. the mbf files are ROM images, and updates are produced by the OEMs. (Original Equipment Manufacturers)
Click to expand...
Click to collapse
When I updated my PDA I used ROM which consisted files ms_.nbf, nk.nbf, and radio_.nbf. I think it get 1, 2, 3 steps to install the softwere.
You can upgrade all of them or just one, moving files from folder, where installer starts.
So I know now what is radio_.nbf, it is radio ROM about that you have told me. Question is what the rest?
And please, if you know, what about version Bluetooth below?

Ok, well nk.nbf is 'main' ROM. It's the OS and hardware drivers for touch screen, LCD etc.
I am not sure but that leaves ms_.nbf to be the extended ROM. I could be wrong though.

Thank you, Levenum.
Good job!

There is a solution of search.
If you want to find exact words or sentences into this forum, or another wiki sites go to Google.com or another search server, put your words in extended search and choose domen(write down) 'forum.xda-developers.com' and etc.

OS image, new bee question

Hello developers!
I have some tasks that I need to implement:
1. Save Windows Mobile OS from the mobile device (to make backup copy of it).
2 Add some cab file (or other files) to OS image and write it to device ROM.
3. On device hard reset to install some files which are currently on the ROM.
For this purpose I ‘m asking you who are more experienced in the field to describe me road map of the way to achieve this.
I think in first turn I need links to comprehensible material concerning how OS storing on devices, file formats and so on. For sure you know better at the moment the right end to start with.
Thanks a lot.

Hi and welcome to the forums.
In order to better help you (so that we can direct you into the right place), we need to know which device you are talking about and what OS it has installed. Also, if it is locked or unlocked.

'unflash' Android NAND back to WM?

Forgive me if this is already solved...search function cannot find proper answer to resolve problem.
I used NAND method to install Android, work good with KaiserDroid, and I can get Bluetooth to work at minimum level, but too dangerous to release as it cause random shutdown while transfer files via transfer apk I make.
I need access to WM again to study related functions, I can't find solution how to reverse flash, since RUU need activesync, and I don't have flashing box with me right now.
Can someone please tell me if I can flash from Android NAND back to WM using only USB cable/RUU? I have HTC Polaris.
Pardon my English, I from Japan, still learning many things.
I may be able to provide help as soon as camera can capture and store image, but need time, as work is in schedule.

read this:
http://forum.xda-developers.com/showthread.php?t=384084

Thank you for your help, did work, thank you very much.
I will do my best to contribute to the project in any form I can.

Had anyone notice some apks cannot resize properly and result in bottom screen croped by 10-30px?
I try to adjust in many way but fail, is this screen hardware related or more like software script problem?
Please enlighten.

change default.txt - if using haret - to 320x428
or flash 320x428 nbh if nand
it also affects what u can see in market

hi
this isn't working for me
I used the mywarmdonut android image
i need to quit android and get back to WM but the bootloader just doesn't come out and it is pissing me off!!!
why is it?
i'm pressing the button, as always, but it won't ****in work
does it have anything to do with android deleting hardspl or somethingl ike that?
if so how can I reinstall hardSPL without Windows.??

Fixed by quitting the battery and then replacing the battery again

To aoao4040 - how did you switch back to wm
aoao4040 said:
Thank you for your help, did work, thank you very much.
I will do my best to contribute to the project in any form I can.
Click to expand...
Click to collapse
Dear aoao
i have HTC polaris and i am also trying to switch back from android to WM. please tell me what steps did you take to do the switch and which files did you put into the SD card for this.
Thanks
o2-lover

o2-lover said:
Dear aoao
i have HTC polaris and i am also trying to switch back from android to WM. please tell me what steps did you take to do the switch and which files did you put into the SD card for this.
Thanks
o2-lover
Click to expand...
Click to collapse
look into the link from post 2

i also notices that taking the battery out for a few seconds
lets u enter tricolor the old camera way - just once after every battery detachment

[Q] Porting From Xoom

Hi all,
I'm hoping some of you guys in the know would lend me a hand here. I recently became the proud owner of a Fusion Garage Grid 10. It's a really great slate that's based on the Tegra 2 platform, just like the Xoom. Unfortunately, unlike the Xoom, it was neither successful nor did it ever run a "true" version of Android. It is also no longer supported by the manufacturer, as the company itself no longer exists (they went bankrupt, big time).
Right now, through the efforts of some other Grid 10-owning community members, there is a stable build of Android 2.2 for the device, which I am currently running. However, I would really like the device to have a working version of the latest Android 4.0.3, not only because the chipset is powerful enough to justify it, but also because the device has no hardware buttons, making navigation in Froyo a bit of a hassle.
To this end, I have starting looking around and trying to learn as much as I can about Android, the nVidia Tegra chipset, and embedded computing in general. Although I have some significant experience with both Linux (I'm a Linux SysAdmin by trade) and Windows (MCSA, MCSE, MCDST, MCTS for Win7), I'm finding that the world of embedded computing is very different from that of the PC.
I was hoping that some of you more learned guys here could tell me if my current understanding of the situation is well-founded, and maybe give me some pointers on where to go from here:
As far as I understand, the easiest (ha!) way for me to go about getting a version of Android 4.0.3 running on the device is to port a build meant for another device to the Grid 10. To do this, I need the boot.img and system.img from another device. After I get those, I need to extract their contents, replace the kernel in the boot.img with the original kernel for my device, and replace the hardware and kernel specific files in the system.img with the corresponding original ones. After this I need to flash the updated images to the device and then debug through adb for a long, long time.
Obviously, that's a bit of an "in a nutshell" overview, but hopefully it is basically correct. Assuming it is, I have started taking steps towards completing this goal. So far I have:
1. Made a 1:1 backup of the internal NAND of the device using nvflash (a partition at a time)
2. Acquired the bootloader.bin, system.img, boot.img, and recovery.img used in the build of Froyo that was created by the community for the device (nvflash is used pretty much exclusively at this point, no update.zip's here!)
3. Downloaded the latest master branch of Android 4.0.3 from the AOSP and compiled it for the Xoom - this generated a boot.img, system.img, and recovery.img of Android 4.0.3 (albeit for another device)
Right now, I am in the middle of trying to transfer the data from the old images into the new one, and am running into some problems. However, I think I've already typed enough, and I don't want to overwhelm you guys with questions, so I'll stop there
Is the road I'm heading down right now the way I should be headed if I would like to have Android 4.0.3 running on the device (eventually)? If not, could you please point me in the direction I should be heading?
Thank you in advance, your patience and assistance is very much appreciated
~ Kent
MODS - Please feel free to move this to a more appropriate forum if applicable. I posted here because a lot of the issues I am running into revolve around my build of the AOSP for the Xoom, so I figured this would be the best place to ask.