Related
yes this is real.
The KJAM rom, which can be found in the FTP of this site, is working on the Qtek9100 !!!
does anyone have any thoughts about that? is this ROM a better one than the 9100? I think it is!
From what I understand, The KJAM is slower with its rom then the QTEK. Because KJAM is full of apps which might not be needed. Once those apps are removed it should be exactly the same ( are the rom version numbers not the same )
ANyone have any views on this ?
I believe the ROM dates are different, with the K-JAM being 9/16/2005 and the Qtek at 9/22/2005. I don't know the difference between the two, but I'd be interested to find out. Also, I'm still trying to find out how to change the splash screens (HTC, then i-mate) when it boots, but it's different than previous HTC models so far (not splash?.nb).
As for the apps, the difference does lie in the Extended ROM, so once you've custom-tailored that area, they should be identical.
HOWEVER, people on HowardForums are complaining about the Bluetooth in the 9100, where K-JAM users don't seem to be having an issue. I didn't check up further on this, can anyone confirm?
Would yo umind sharing information about details? How to avoid device ID error? IS there hacked exe file? I need to flash my QTEK with IMATE ROM since I think BT performance in IMATE is way better.
TIA
bt on the qtek smells
Grill! Wake up and give us a clue,please!
I did the soft reset after the WM5 setup so that the crap wouldn't install and it works great
so what did you do?
imate rom on a qtek???
i got a vender error when try to install the k-mate rom on my qtek 9100. what´s the trick, that it work without the error? please help!
nice we have to get around that.
Anyone try to place the Wizard in bootloader mode first before running the upgrade utility?
If someone can point me out to the Magician upgrade utility with the NoID hack and give me the original file as well, I might be able to do a byte-compare and apply it to the Wizard's upgrade utility.
BeyondtheTech said:
If someone can point me out to the Magician upgrade utility with the NoID hack and give me the original file as well, I might be able to do a byte-compare and apply it to the Wizard's upgrade utility.
Click to expand...
Click to collapse
This one? ftp://xda:[email protected]/BlueAngel/Tools/MaUpgradeUt_noID.zip
from here: http://wiki.xda-developers.com/index.php?pagename=BA_1.42.00_Upgrade
pimbo said:
BeyondtheTech said:
If someone can point me out to the Magician upgrade utility with the NoID hack and give me the original file as well, I might be able to do a byte-compare and apply it to the Wizard's upgrade utility.
Click to expand...
Click to collapse
This one? ftp://xda:[email protected]/BlueAngel/Tools/MaUpgradeUt_noID.zip
from here: http://wiki.xda-developers.com/index.php?pagename=BA_1.42.00_Upgrade
Click to expand...
Click to collapse
Hi,
I don't think this is the good way because I unpacked the "KJAM_WWE_ROM_1010903_104_10110_cdl_wwe_ship.exe" (rename to rar)
and I've foud the following files:
EnterBootLoader.exe
nk.nbf (74 MB)
README.doc
ROMUpdateUtility.exe
RUUGetInfo.exe
RUUResource.dll
I don't know which file have to change to "MaUpgradeUt_noID.exe".
Any idea?
THX
TB
Again, if I can find out how the NoID utility bypasses the check by comparing it with the original (does anyone have the exact file before it was hacked?), and we can compare, it'll be a start to look for similar code or text in the EXEs or DLLs of K-JAM's upgrade utility.
Find me the unmodified version of the NoID utility. Look on the FTP, and check all the other Blue Angel ROM update utility's EXE files...
thebiker said:
"KJAM_WWE_ROM_1010903_104_10110_cdl_wwe_ship.exe" (rename to rar)
and I've foud the following files:
Well
EnterBootLoader.exe
nk.nbf (74 MB)
README.doc
ROMUpdateUtility.exe
RUUGetInfo.exe
RUUResource.dll
Click to expand...
Click to collapse
Looks to me that somebody who knows howto and has this phone for testing could to edit the The ROMUpdateUtility.exe to bypass the country id errors,
And use as refference maybe the hacked no id loader for the BA.
P.s. the original MA upgrade utility should be found in the original roms from the providers of the Magician devices, we got it from them if i'm right.
Hope it helpes a bit,
I'm no developer, but this file sticks out in my mind..."RUUGetInfo.exe" If that is part of the upgrade installer then it looks to me that it is looking for the actual device ID, and it probably has to fall within a certain range to allow the upgrade to proceed. Something to the effect that each country, language or brand has a range. If your device isn't in that range, you are SOL.
With each generation they do something different, and more difficult.
Dave
i think it has to be in the ROM if not then all we have to wait for is a update from qtek and switch the nkf file
vbguru613 said:
i think it has to be in the ROM if not then all we have to wait for is a update from qtek and switch the nkf file
Click to expand...
Click to collapse
Nah, it's Much more involved than that. Just look at the process taken to develop the method to do it on the JAM, PDA2K, and so on. With each generation they make it more difficult.
Dopod 838 > K-Jam rom upgrade.. need some work
I had under my hands the Dopod 838 which is infact the cH version of the WIZARD.
I would like to load the imate K-Jam rom to the Dopod
Playing a bit with the machine, it seems that the Boot loader is actually looks like the Typhoon, the TyphoonNBFTools utility will decode the NK.NBF file but I am not sure what is the Vendor ID of the Dopod.
On top of it after altering the Languge from English to WWE and made the vendor DOPOD, the romupgrade utility reports the new version going to Prodigy and the Lang is English. it seems that although the TyphoonNBFTools was able to decode the NK.NBF, the upgrade application did not take the header information.
I did run also the Boot loader command under the MTTY (on the usb port) and command that did work for the typhoon "R2ds all" responded that I do not have the authority to dump the rom image.
Tried the command password WIZARD and although it did take it, still was not authorized to dump the rom image.
If somebody could help find a method to bypass the protection of rom , upgrade (bypass vendor , Country code...) it would be very helpfull to exchange roms.
:shock:
I've been playing with the ROMUpdateUtility.exe
Well, i've also noticed that the rom is like a typhoon rom.
Ive removed some strings to RUUGetInfo.exe(since this one seems to do the thing), but i cannot test it,
I got error 222, device not responding, (DUH, its a BA :lol
Maybe somebody can replace this file for the original in the folder and try running it. (if it passes the country id and the model no)
But it is a test, use at your own risk.
Do not blame me for anything.
I have a Siemens SX66 Cingular branded PPC. I downloaded the latest Official ROM Update but get the Wrong Country ID error. I found out that this was due my phone being an AT&T varient even though the phone says Cingular. So I wanted to know is anyone has the original ROM update that came out before the Siemens-1.33.10-Full_Update and if so could provide it to me thank you in advance. I need to put an offical rom back on my phone so I can send it back to cingular so they can send me a replacement phone.
Go to the SX66 Standardization Project to get the most recent ROMs for the SX66; they have both Cingular & ATT versions.
I went there but it's not an official version number which cingular will check for.
hakushox said:
I went there but it's not an official version number which cingular will check for.
Click to expand...
Click to collapse
Try following the instructions here:
http://wiki.xda-developers.com/index.php?pagename=BA_FAQ_Upgrade_Errors
You will need to run the upgrade a second time for it to install, the first time clears the previous contents, the second time the upgrade should run.
That wont work already tried that. Thankz for the resond though. BTW how do you like that new wizard OS on your sx66?
hakushox said:
That wont work already tried that. Thankz for the resond though. BTW how do you like that new wizard OS on your sx66?
Click to expand...
Click to collapse
Did you edit the .conf file as outlined in step 4? This worked for me. You may also try the MaUpgradeUt_noID route as well.
I prefer WM 2005 over 2003 I'm willing to work with the warts and try to advance the ball
Ya it gets rid of that error but then i get a error in the checksum
hakushox said:
Ya it gets rid of that error but then i get a error in the checksum
Click to expand...
Click to collapse
go back and make sure you have edited the editfix.bat file correctly, there is a set of three lines to recalculate the checksum and update it for each of the nba files (xda3nbftool -c -u ?????.nba).
hakushox,
The only way to get back to an officially supported ROM on the AT&T variant of the SX66 is with the MaUpgradeUt_noID. Now, I have not tried this, but here is what you'd need to do. Download the official Siemens update for the 1.33.10 System, and launch it. Once the first screen screen appears, open the Windows File Explorer, and search for nk.nbf. The one you are looking for will exist in a temp directory, and will exist with ms_.nbf, and radio_.nbf. Copy these files to a easy to find directory as these are the files you'll need to do the downgrade with. Cancel the offcial upgrade tool. Now, download the MaUpgradeUt_noID tools from this site, and extract it to a directory on your computer. Copy the .nbf files into that directory. Now, place your phone into boot loader mode, and place it in the cradle. Wait a few minutes for the OS to detect the "new" sync device. Finally launch the MaUpgradeUt_noID tool, and step through the screens. Once completed, it will place System 1.33.10, Radio 1.06.02, and Extended 1.33.110 ROMs on your device.
This works because the MaUpgradeUt_noID tool does check the ROM ids, and will let you flash any IDed rom onto your phone. As you can imagine, it is a rather dangerous tool if you don't have a good idea what you are doing, which is why I have tried to get it away from the Standardization project.
-Chris
Worked like a charm much thanks
Excellent!
-Chris
I tried uploading the original SX66 Cingular rom to the FTP but for some reason its not responding, if some one wants it email me and I will send it.
SysCrasher13 -
I am interested in downloading the factory Siemens SX66 firmware, after upgrading the firmware my SD slot no longer recognizes SD Memory... very strange.
Please let me know where to download the factory firmware.
Note: I have (2) SD PNY cards that work fine in my PPC4100, however, my SX66 doesn't recognize either card and wondering if this maybe a compatibility issue. I'm going to swap the 512MB with a SANdisk tomorrow to see if this rectifies the problem. Can anyone confirm SD compatibility issues with the SX66 --- is there a SD Memory quick reference chart available for the SX66?
Mike
Let me know if anybody has any ideas before I send it in for repairs...
Thanks - Mike
ok...i got the error from upgrading from 2.17 hacked rom to the 2.26 official rom. tried to read whatever i can but looks like solutions were given for cingular ipl etc...
can someone help me out? when i run the official rom, it updates to 1% and then i get the nbf error. i tried to run loki but mda not recognized by my usb connection.
stuck now...please help!!!
actually, tried to run machinagod's RAPI unlocker..but MDA not recognized as connected...this was part of xelencin's 2.24 rom updater.
please help!!!
Hi,
you must provide more information if you want someone to help you.
First and most important: what does it mean your phone is stuck? Stuck where? Does the screen come on? Can you get the bootloader screen? (for the bootloader screen: hold the two keys on the right side of the device and press shortly the reset hole; if you see the three colors screen then you have the bootloader!)
bye
i get the screen with the 3 colors, and usb at bottom left. when i run the official t-mobile 2.26 update, the screen goes gray and there is a bar with % done. when that kicks in, i get 1% done then it stops. on my computer screen, i get the nbk error, saying the nbk file that i have is not for my phone.
i looked for fixes but all the fixes require activesync connections which i am unable to connect with. just fyi, when i plug in the usb cable to my laptop, i hear the *ding* for usb noting it is connected but the activesync connection is not available.
thanks in advance for your help.
-mike
m3m3 said:
i get the screen with the 3 colors, and usb at bottom left. when i run the official t-mobile 2.26 update, the screen goes gray and there is a bar with % done. when that kicks in, i get 1% done then it stops. on my computer screen, i get the nbk error, saying the nbk file that i have is not for my phone.
i looked for fixes but all the fixes require activesync connections which i am unable to connect with. just fyi, when i plug in the usb cable to my laptop, i hear the *ding* for usb noting it is connected but the activesync connection is not available.
thanks in advance for your help.
-mike
Click to expand...
Click to collapse
Before your battery goes flat i suggest you to re-install your old rom. Don't know why 2.26 is not working, maybe you downloaded a corrupted archive. To install your old rom it is not required that activesync sees your phone. Go in bootloader mode and flash your old rom back.
i dont think i downloaded a corrupted rom file because i downloaded it from 2 different places, one from Tmobile site directly from my tmobile account.
what bootloader program should i use? please advise and location to download...
thanks,
mike
m3m3 said:
i dont think i downloaded a corrupted rom file because i downloaded it from 2 different places, one from Tmobile site directly from my tmobile account.
what bootloader program should i use? please advise and location to download...
thanks,
mike
Click to expand...
Click to collapse
bootloader program??? There's no bootloader program!
What i'm trying to tell you is:
- Your phone is stuck for unknown reasons. In this state you cannot recharge your battery!
- Before the remaining battery charge becomes too few, reinstall your old rom (the one you had before trying 2.26)
- When your phone -with the old rom- will be working again, then you'll have all the time to investigate on the causes of this failure.
- Now hurry up and install the old rom before it's too late (unless you have a second wizard that you can use to recharge the batteries)
To install the old rom you must go to the three-colors screen (the bootloader), connect to USB (but activesync won't start!) and start the rom installer.
bye
risi,
sorry...how do i get to bootloader screen? is it the tricolor screen? has anyone had the same problem that i'm having, going from 2.17 hack to 2.26 official?
what program can i use to load my original rom with?
sorry for the semi-newbie questions...desperate to revive my MDA...
again, thanks.
-mike
m3m3 said:
risi,
sorry...how do i get to bootloader screen? is it the tricolor screen? has anyone had the same problem that i'm having, going from 2.17 hack to 2.26 official?
what program can i use to load my original rom with?
sorry for the semi-newbie questions...desperate to revive my MDA...
again, thanks.
-mike
Click to expand...
Click to collapse
to go to the bootloader screen you must keep pressed the two keys on the right side of the device and, while keeping them pressed, shortly press the reset button. the bootloader screen IS the three colors screen. when you get the bootloader screen, reinstall your previous rom (2.17).
i plugged the phone in the wall charger and the battery charged up all last night so i am not worried about the battery...
i just cannot figure out how to load the old rom i had.
i didnt bring the phone with me to work...i will try to reflash with old rom...for now...i am using my old hp 6315 (yikes! - remember the probs with this phone?? lol
m3m3 said:
i plugged the phone in the wall charger and the battery charged up all last night so i am not worried about the battery...
i just cannot figure out how to load the old rom i had.
Click to expand...
Click to collapse
to load the old rom you must:
- get to the bootloader screen (the three colors one)
- download the 2.17 rom's ,exe archive (download it from the same place you took it last time)
- connect the phone to USB (don't worry if activesync doesn't see it)
- start the rom .exe file
thanks risi...
hope i can get it back man...
m3m3 said:
thanks risi...
hope i can get it back man...
Click to expand...
Click to collapse
I hope so! About the problem you had with 2.26, i don't know why it happened. Is your phone a T-mob USA MDA? If it is not then you must CID unlock it before flashing a different operator's rom.
Bye
yes, it is a tmo usa mda...or i would think so since i bought it from a factory store (not an authorized dealer). anyway man...i will keep you posted...for now, using my trusty hp 6315. lol
Hello,
I have a similar problem. I updated my QTEK 9100
with a T- Mobile 2.24 ROM. Now I need to go back to the original QTEK Rom, namely RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe, but after starting the upgrade process the program refuses to downgrade the device and says get a newer nbf file.
Is there a way to force a downgrade?
Many thanks in advance
Anais said:
Hello,
I have a similar problem. I updated my QTEK 9100
with a T- Mobile 2.24 ROM. Now I need to go back to the original QTEK Rom, namely RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe, but after starting the upgrade process the program refuses to downgrade the device and says get a newer nbf file.
Is there a way to force a downgrade?
Many thanks in advance
Click to expand...
Click to collapse
Is your phone CID unlocked? If so, then you must download the wizard_upgrade_noid tool from the ftp server and use it to install the 'down'grade.
In details:
- be sure your phone has been CID unlocked (and is not a G4)
- download the wizard_upgrade_noid (i don't remember the name exactly) tool
- use winrar to extract the original qtek rom .exe archive
- copy the noid tool to the folder where you extracted the qtek rom
- run it
bye
Hello Risidoro,
At first thanks for your fast answer. Since I have a QTEK I don't beleve it's CID locked. How can I verify if the phone is CID locked? Is there a tool to check this?
I proceeded exactly as you advised. I used Winrar to extract the files and used the Wizard_RomUpgradeUtility_noid I downloaded from the ftp site.
Then I copied the nk.nbf file to the respective folder but the utility after having completed the initial 2 screens says:
ERROR [238] : FILE READ
The update utility cannot open the requested file. Please check your update utility.....
any ideas
Greetings
Hello,
Just some small updates: My phone has currently the Mr Clean 2.3 firmware loaded : IPL 2.24 SPL 2.24 GSM 02.25.11 and OS 2.24.10.1.
Previously I was using RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe and had no problems. After upgrading to xelencin t-mobile based US rom I had trouble when making data transfers over GPRS. Then I decided to test Mr clean. Altough I data transmission has improved a bit it's still not so good as with my original RUU 2.17 release.
Unfortunately I am unable to revert to this version. Also having tried to downgrade using Faria's Custom downngrade file only the IPL was downgraded to 1.05 and the SPL file stayed to 2.24.
I tried then to reapply RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe but I recieved the error message UPGRADE only.
Since apparently this is unstable I decided to reapply Mr Clean and now I have again IPL 2.24 SPL 2.24 GSM 02.25.11 and OS 2.24.10.1.
I suspect that the data problems are due to the fact that these new radio versions are not compatible with our provider. I live in Luxembourg so we use LUXGSM.
Is there a way how I can revert to my old 2.17 software.
Any coments are highly appreciated.
Greetings
Anais said:
Hello Risidoro,
At first thanks for your fast answer. Since I have a QTEK I don't beleve it's CID locked. How can I verify if the phone is CID locked? Is there a tool to check this?
I proceeded exactly as you advised. I used Winrar to extract the files and used the Wizard_RomUpgradeUtility_noid I downloaded from the ftp site.
Then I copied the nk.nbf file to the respective folder but the utility after having completed the initial 2 screens says:
ERROR [238] : FILE READ
The update utility cannot open the requested file. Please check your update utility.....
any ideas
Greetings
Click to expand...
Click to collapse
Hi Anais,
try flashing with the RUU (Rom Upgrade Utility) tools that you find in this thread: http://forum.xda-developers.com/viewtopic.php?t=56088
Download the archive RUU.rar and extract its content somewhere in your PC. Copy in the same location the nk.nbf from the rom and run the .exe.
bye
Ok guys - since my Molski.biz 2.26.10.2 rom has a few bugs (like the volume-control slider not working), I decided to reinstall a new rom. Ive seen already tons of threads including thousands of posts so it`s difficult to find out which rom is the best.
I heard of Faria released a cooked WM6-Rom but I m not sure if it`s working fine with the wizard and if there are still some bugs. In addition to that i don`t know if there are any incompatabilites with WM5 applications.
I`ve also seen a WM5 Rom tons auf WM5 Roms - but which one is working realy fine?
Oh forgot that: I`ve a G4 Device but it`s already CID unlocked.
What ever suites for YOU.
For me WM5 was a disaster, crashed every day. Now with WM6 X-plore 1, not a single crash during 4 months! Next thing I'm going to try is Titanium 2 I guess.
Well, I don`t want a Rom with tons of Tools, but it should have a nice look (like WM6),a good performance and most important not too much bugs .
Then I would try X-plore 2.0n or wait for Titanium release
Try T-Mobile USA 2.26 ROM(you can flash extROM blank if you don't like soft in extROM).It's WM5 ROM but so stable,fast.None WM6 ROM have no bug.
Saiyajin said:
Well, I don`t want a Rom with tons of Tools, but it should have a nice look (like WM6),a good performance and most important not too much bugs .
Click to expand...
Click to collapse
try the ingenetics rom, as ms built it with nothing added
I found the nk.nbf file in your RapidShare, and it says to insert it into any ROM to install the vanilla WM6. I have a CID Locked Wizard. Would it be possible to insert that file into Cingulars default ROM and flash it to my phone without CID unlocking, or would I brick my phone?
drumguy211 said:
I found the nk.nbf file in your RapidShare, and it says to insert it into any ROM to install the vanilla WM6. I have a CID Locked Wizard. Would it be possible to insert that file into Cingulars default ROM and flash it to my phone without CID unlocking, or would I brick my phone?
Click to expand...
Click to collapse
NO, and yes,
you can't do the former and you may end up doing the latter.
afaik the ruu is just a small prog to tell the phone to flash the nk file in the same folder that the ruu is in. if the nk file is wrong, it won't flash.
anyway, in the time it's taken for me to reply you've probably unlocked anyway?
Hi, I have HTC Blue Angel running WM6.5 and find that it struggles to run at this level, i am looking to downgrade to the original wm2003 that it came with, I am on Orange UK
Current Seetings :-
Rom Version : 6.5.23004EN
Rom Date : 06/12/09
Radio Version : 1.15.00
Protocol Version : 1337.45
Extrom version : 23004-xplode
could anyone help and tell me excactly what files i need to download to restore to original shipped state and exactly how to carry out the downgrade.
Regards,
John.
welcome to the forum!
ok, what you need is:
- a pc, preferably with windows xp
- a wm2003 rom in your preferred language, e.g. from -=xplode's shipped rom archive=-
-a RUU (Rom upgrade utility), you can try mine there (attached)
and then you go to the -=wiki wizard for downgrading=- and follow the instructions there or follow these shortened instructions:
1. hard reset your device: power+reset, then camera and record, change the values in the menu from No, No, Yes to YES, YES, NO using the camera and record buttons, confirm with the mail button.
2. put your device in bootloader mode
3. connect it to the pc using the cradle or a usb cable
4. extract the shipped rom in any folder
5. put the maupgradeut_noid in there and start it
6. have a look, whether the 2nd page shows device and rom information, if not, exit, start task manager and kill activesync (wcesmgr and wcescomm) and go back to step 2
7. start the "upgrade"
8. when it's done, perform a wm2003 hard reset by pressing power+reset, and wait for the versions to show up in the bottom right corner, if all the values changed from your previous wm6.5 versions, you're probably fine and done by now.
in very rare cases, something goes wrong, some combinations of pcs and devices wouldn't work with my ruu, but you would realise that at step6 or 7, try and download another ruu then and try again, i think there also is one linked in the wiki.
at the end, your device should read something like:
R:1.12.00
G:1337.42
D:1.06.02
with best regards
Chef_Tony
Decided to go for windows pocket 2005
Thanks Chef_Tony im afraid im running vista and have tried using mtty but with no success, I have now decided to downgrade to pocket 2005, is this possible and how would i do it with windows vista as i am unable to downgrade to XP. Please help if possible.
Thanks John
Bootloader
Hi i dont know if this makes any difference my Bootloader is showing Version 2.05 Reagrds.
no, it does not make any difference, since the bootloader's version is not the problem. before you go on doing anything, you should have a good look at this site:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade4_Vista_Pic
and unless you are sure, the installation of the driver was successful, you should not attempt to flash the device, because then you will end up with a half-flashed device, that cannot be switched on and maybe also not flashed anymore.
http://firmware.atspace.com/ can't be accessed. is there any other site for wm2003se rom ?
I have the same problem, as i m downgrading to WM 2003, i followed all the instructions as u mentioned here, but when i run "maupgradeut_noid" it always said that this ROM is not for your device, i have Orange SPV M2000 (Blue Angel), please help i cant able to downgrade to WM 2003.
One more thing is there any way to Merge ExtROM with Storage in Windows MObile 6.5?
byudi23 said:
http://firmware.atspace.com/ can't be accessed. is there any other site for wm2003se rom ?
Click to expand...
Click to collapse
http://firmware.atspace.com/Blueangel.html
working flawlessly for me. check now
subratamm said:
http://firmware.atspace.com/Blueangel.html
working flawlessly for me. check now
Click to expand...
Click to collapse
still can't open http://firmware.atspace.com/Blueangel.html too
ok, we are dealing with several different things here:
1. the storage resize:
no, it can only be done in wm2003, no way to do it in wm5 or above, you have to downgrade
2. while attempting to downgrade, don't forget to put your device into bootloader mode, before connecting and starting maupgrade, then there will be no device error anymore.
3. of course for downgrading you need the original rom, at best from xplode's shipped rom archive, if you can't access it, just tell me your favoured language and country, and i will look it up and send you the direct download link. btw. xplode's site works fine!
favoured languange : English
Country : Indonesia
please send me the direct link. thx a lot. chef_tony
since he doesn't have indonesian roms and you are fine with english, here are the links of 2 different UK roms, you should be fine with.
T-Mobile UK WWE 1.42.00 1.42.112 1.13.00 Download (Ziddu) / Mirror 1 (Rapidshare) / Mirror 2 (Megaupload)
O2 UK WWE 1.40.00 1.40.242 1.12.00 Download (Ziddu) / Mirror 1 (Rapidshare) / Mirror 2 (Megaupload).
i hope these links work for you.
thx a lot chef_tony. I almost forgot. I want to ask whether the different rom can drain the battery fastly ? because my battery drain faster using WM6.5.
the power consumption of the device mainly consists of 2 things:
- wireless communications (gsm, gprs, bluetooth, irda, wi-fi)
- hardware usage (cpu & ram)
the wireless does not really vary from rom to rom but much like on the pc, graphically more intense applications use more power and since wm6.5 has a much nicer shell, it uses more ram and cpu to run. that uses more power.
if you want to save battery, reduce the backlight intensity, let the device switch off faster and end all applications that you don't need and de-activate wireless communications that you don't use. still then the battery life is limited but that is something you will have to learn to put up with.
thx chef_tony. I want to ask about the memory used ? is it better with storage 42mb and program 90 mb or repart it into default which is storage 60mb and program 60 mb ? is this RAM configuration also affect the battery consumption ?
no, that has nothing to do with that, because you don't resize the ram, you resize the extrom and the storage. that doesn't have any influence, kind of like the size of the sd card does not have influence.
Chef_Tony said:
welcome to the forum!
ok, what you need is:
- a pc, preferably with windows xp
- a wm2003 rom in your preferred language, e.g. from -=xplode's shipped rom archive=-
-a RUU (Rom upgrade utility), you can try mine there (attached)
and then you go to the -=wiki wizard for downgrading=- and follow the instructions there or follow these shortened instructions:
1. hard reset your device: power+reset, then camera and record, change the values in the menu from No, No, Yes to YES, YES, NO using the camera and record buttons, confirm with the mail button.
2. put your device in bootloader mode
3. connect it to the pc using the cradle or a usb cable
4. extract the shipped rom in any folder
5. put the maupgradeut_noid in there and start it
6. have a look, whether the 2nd page shows device and rom information, if not, exit, start task manager and kill activesync (wcesmgr and wcescomm) and go back to step 2
7. start the "upgrade"
8. when it's done, perform a wm2003 hard reset by pressing power+reset, and wait for the versions to show up in the bottom right corner, if all the values changed from your previous wm6.5 versions, you're probably fine and done by now.
in very rare cases, something goes wrong, some combinations of pcs and devices wouldn't work with my ruu, but you would realise that at step6 or 7, try and download another ruu then and try again, i think there also is one linked in the wiki.
at the end, your device should read something like:
R:1.12.00
G:1337.42
D:1.06.02
with best regards
Chef_Tony
Click to expand...
Click to collapse
THANK YOU VERY MUCH! It was very helpfull!
Showing white screen after hard reset
Dear Tony,
Since I wanted to get more space for my Xda iis tonight, so I install a unlock softwares to unlock the Extrom according to some indication on web, also I format it after scusseful to get a extrom, but I got a freezable white screen after using hard reset, the programe showing rom upgard scussefully but it cannot get into window: Could you teach me how to fix this problem? Can I save my xda IIS?
Thank you so much for your help.
Simon
please do not double post! i answered this exact question in the thread you opened for that.
thanks chef tony!