Hi there,
I don't know what went wrong, but this is what happened:
1. I had a Crossbow ROM running, one with the ExtROM unhidden and unlocked by default, calling it "Storage".
2. I was testing things out and reflashed Windows Mobile 5.0 (original shipped AKU2 WWE Qtek)
3. Testing was done and I reflashed the Crossbow ROM (Midget's 0.1 Vanilla).
The ExtROM (called "Storage") is still there, but it somehow seems locked.
I have access to the ExtROM, can delete, place, rename, files etc., but after a soft reset the original state has returned and all of my files/modifications are gone.
How can this be while the Crossbow ROM had it unlocked by default before? Can the ExtROM unlocking operate by itself, independent from the CE ROM?
If this all is the matter, how can I unlock the ExtROM again?
I tried a few "ExtROM Unlock" cabs already, but these only create another entrance called "Storage 2" and it stays locked somehow....
Thanks a ton!!
Related
I use this tool without an expected goal, I use another one (PPCW.net Extended_ROM_viewer) with same effect andfinally I did changes in registry manually, but still without effect. Where should be the problem?
ROM 1.72.00WWE
Radio: 1.17.00
Protocol:1337.28
ExtROM: 1.72.901
What do you expect and what do you get?
Can you be more specific about what isn't working?
Mark
to: markutah
Described applications has clear functionality: to show Extended_ROM directory (lock, unlock too, of course). I want copy .cab files to pc and cook my own ms_.nbf.
So after aplying these tools nothing happens, no directory shows in root of my XDAII. Why? Can you help me with this mess?
Did you soft reset your device after applying the unlock tool?
If not then do a soft reset. If yes then do the following to read the content of your extended rom:
Go in the registry to
HKLM\system\StorageManager\Profiles\TRUEFFS_DOC
Change the key MountFlags to 0 (= zero)
Soft reset your XDA II/QTEK2020 etc
In the file explorer a directory Extended_ROM will show up. Now you will be able to copy the content of your extended rom.
Note that your extended rom is not unlocked so you will not be able to write something to the extended rom. As you've stated you're going to flash your rom then this will not be problem I assume.
Mark
to markutah
you didn´t read ny first post carefully - i did it already hudret times manually or with tools, but nothing happens. No directory shows. I´m not rookie user, but now i´m on the end with my power and nerves.
I used copyying rom through bootloader and usb terminal to sd card, but format of data is not readable for Windows PC....see http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=62&PN=1
Sorry that my attempt to help you works on your nervers and sorry that I was trying to help you.
mark
to: markutah
today seems my mood better, (because i found somthing about that problem) so sorry about my reaction, for a little apology i´m writting what i find out:
so i had ROM version 1.60WWE as original one with Radio 1.12, devide with CDL oerator. I was upgrading ROM many times (ROM, ExtROM, Radio together and separatelly too), but new ROMs was still from CDL operator. Last time I upgraded ROM to 1.72WWE, Radio 1.17 from TMobile, and I couldn´t do any change in registry with sucsess. My registry data stand changed, but nothing happens. (for example: i tryied to show Orange logo in Phone to substitute title ORANGE (in right up corner) withouth sucsess, and that ist far easier operation that this we are talked before (see http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=80&PN=1 - you are orangeman too, so change yours logo , when you don´t have it yet.)
finally i have no idea how to fix it (without downgrading ROM) and i´m not 100% sure if this is the point of problem, but i gues. bye
today i tried to switch my xda2 from t-mobile's 1.72.170GER final rom back to o2's 1.72.184GER final which has been provided recently. i run into that damn country code error 120 because my xda2 has got a t-mobile device id. please find my steps for solving that problem:
1. unpacked the 1.72.184GER package into a folder and replaced the original HimaupgradeUt.exe by the hacked one (which is supposed to ignore country codes).
-> result: same problem - country code error 120 : 1-3-1-1-1
2. then i deleted the HimaGetDeviceData.exe in the folder containing the rom-files. and i deleted any existing DeviceData.txt in the windows folder of my xda2. time to start again the hacked HimaupgradeUt.exe.
-> result: first screen with no errors. it tells me that my device is going to get an update, from rom 1.72.01, radio 1.17.00, extrom 1.72.170 to rom 1.72.01, radio 1.17.00, extrom 1.72.184. i am happy so far but the next screen is again that damn county code error 120 message :-( meanwhile my device is stuck in bootloader 1.06 mode.
3. at this time i deleted the HimaClearJumpCode.exe (which is no longer needed for setting the xda2 in bootloader mode, it is already there) and started again the hacked HimaUpgradeUt.exe (the third time).
-> result: first screen with no errors. it tells me that my device is going to get an update, from rom "blank", radio "blank", extrom "blank" to rom 1.72.01, radio 1.17.00, extrom 1.72.184. next screen tells me that the devices rom is getting erased now and the progress bar shows the current status. everything went through the update process fine.
and my device has been successfully transformed from a t-mobile mda2 which looks like an xda2 to a real o2 xda2 with current xda2-software
summary: i guess you can shorten the whole procedure by setting the xda2 into bootloader mode connecting to your pc by usb unpack only the three rom file images into a folder, copy the hacked HimaUpgradeUt.exe into that folder and start it. but i have no time and motivation for doing that since my device works now.
best regards
peter
where to download hacked HimaUpgradeUt.exe
Dear
where to download hacked HimaUpgradeUt.exe
beast regards
:lol: :lol: :lol:
Thank you very much
Thank you very much its work now
beast regards
o2 ruu
i have tryed upgrading my i-mate to the o2 finaleng ruu with the help of dcs i got it to work with the acked file but now i have megga probs, no camera no extrom and no caller id file so i can't open pictures or video as they are looking for 'albam' to view them, can you suggest a way to get them back???
i have tried the upgrade a fair few times and am getting to the end of a short fuze..... if i run the upgrade direct from o2 i get a model id error, in the device data file i noticed that it has::
usb30 cdl uk5
cdl 1.70.00wwe ph10
or something like that..... it's the uk5 bit that is new..
any ideas :?:
I did not get the upgrade out of the PDA first, it is in bootloader mode.
By mistake, I picked up a XDA II upgrade instead of PDA III and clicked the sucker, only to get bummed completely. I guess it "deleted" the orig OS, or parts of it.
The BA is from o2, but private buy, no support expected from them.
The BA was in German, there is no "ID" for o2 given in the ID table.
I even tried T-kom's blackberry upgrade (German) gives same error as the 3 WWE SHIPS I tried, 120 "Country ID error"
Anyway to get the needed ROM info with the bootloader only ?
I would not mind the BA_5.1.1700_build_14343_Upgrade Engrish...
Somebody please help bring my new thang into life again
Hi Man,
Do not worry...Just upgrade the ext rom part of any ROM u have and it will be live again...then u can re-upgrade it completely
One problem I recognize I have: how to get DevData...
Thanks for the assuring words. But I have no idea what you mean with :"upgrade the ext rom part of any ROM u have and it will be live again."
I Assume the ext rom is a nbf file ?
I tried several of the ROM linked from this site (without modifiying them) no succes.
The nice guide made, explains how to get devdata on the PDA when working, but how to get that when bootloader mode is only option ? Or is that necessary? Are there ROM's that works anyway ??
The guide says:
"Device data reads:
PH20B 0 B GER R T-MOB101 1.12.00 0 0 1.12.100 1.02.00 02.00"
I do not have any of this info on my PDA Can it be retreived from the PC ?? (with a program)
I might also explain why I wanted to upgrade the ROM and didnt realize how "complicated" it can be. When trying to install a new appl. (Copilot) with a SD-card, the BA gave:
"setup-Fehler
Die datei "\storagecard\\2577\tts.cab ist keine gultige datei fur windows CE setup"
So, I thought the ROM version was ****ty not even knowing CAB files!
Any hints & help much appreciated
Rgds
Okeh..
Learned alot during the day on this site, it RAWKS!
I found the BA_TMUK_14200_112_11300_Ship (ENG)
& the MDAIII_TMDE_14201_116_11300_Ship (GER)
Using the "MaUpgradeUt_noID" I managed to get the GER running
Dropped the RADIO ROM of the GER to the ENG version and tried runnin the MaUpgradeUt_noID from that ROM. It worked!
The "standard" windows theme is NOT in the ENG pack, but in the GER one.
I then try run these Copilot cab files, still no luck ?!?
Tried some other CAB files snagged from the FTP, they worked...
I both tried the SD card install (autorun the cab) and from the install CD (to PC & device) both gives same error ? A little suspicious that none of the 2 install options work. Perhaps copilot is NOT compatible...
I reallly got a problem.
I installed Wm2005, but i dont want this.
now i tried to downgrade, but it says "wrong country id"
im a norwegian guy..
can anyone helps me ?
Checkout BA_Downgrade_WM5 thread
hi there are two kinds of upgrade programs one is
HimaUpgradeUt which needs country id to be correct or there is another
HimaUpgradeUt_noID which will do any even if country id is incorrect
contact me if you need further assistance or file thanks
Cannot Downgrade to 2003SE - SX66
I own a SX66 Cingulair (USA) and I recently upgraded the ROM to WM5 but now having a lot of problems with it. I need to downgrade it back to 2003. I followed all the instructions in the link given in one of the posts above but the program MaUpgradeUt_noID.exe does not recognize my existing ROM or the new one and no update happens.
Can anyone help me please.
DEK
Re: Cannot Downgrade to 2003SE - SX66
DEK said:
I own a SX66 Cingulair (USA) and I recently upgraded the ROM to WM5 but now having a lot of problems with it. I need to downgrade it back to 2003. I followed all the instructions in the link given in one of the posts above but the program MaUpgradeUt_noID.exe does not recognize my existing ROM or the new one and no update happens.
Can anyone help me please.
DEK
Click to expand...
Click to collapse
exactly the same here with SX66, but where did you get your ROM?
I also tried to apply SX66Upgrade.exe program which seems like WM2003SE installer, but this program says it cannot connect to device. I also was able to get nk.nbf from the temp folder and tried to run MaUpgradeUt_noID.exe with this one, but it goes to the final screen without actually reflashing PDA. PDA still has WM5 installed.
I made a backup copy of my previous Win2003SE ROM to a SD card and restored it now from file back to SD card, but cannot find the way how to initiate ROM restore from SD card. I've read instructions saying: Insert SD card, put PDA into bootloader mode, select to restore from SD card, but in my case I just see "Serial 2.07" after going into bootloader mode and nothing else.
Found a way to Downgrade
Hi all:
After so much testing in frustration I moved the new ROM file to PH20B folder in the WM5_pack_V3 folder and ran the program BaUpgradeUt.exe. Now I know for SX66 which is a PH20B1 device we are supposed to use MaUpgradeUt_noID.exe in PH20B1 folder according the the downgrade link (http://wiki.xda-developers.com/index.php?pagename=BA_Downgrade_WM5)
I got the ROM from (http://sx66-blueangel.home.comcast.net/) which is version 1.40 and I am very happy with it. Before upgrading to WM5 I have unlocked this device using the unlocker program some where on this forum and I am not sure whether it has anything to do with MaUpgradeUt_noID.exe not working.
DEK.
[/url]
Downgrade to WM2003 from 2005?
Hi,
I loked at this forum and want to do the same thing as described within the thread, but on a IPAQ RX1955 from WM2005 to 2003.
Not sure of the ROM I downloaded form the links on the page will work.
Thoughts?
Thanks!
Mike
Hi there,
I don't know what went wrong, but this is what happened:
1. I had a Crossbow ROM running, one with the ExtROM unhidden and unlocked by default, calling it "Storage".
2. I was testing things out and reflashed Windows Mobile 5.0 (original shipped AKU2 WWE Qtek)
3. Testing was done and I reflashed the Crossbow ROM (Midget's 0.1 Vanilla).
The ExtROM (called "Storage") is still there, but it somehow seems locked.
I have access to the ExtROM, can delete, place, rename, files etc., but after a soft reset the original state has returned and all of my files/modifications are gone.
How can this be while the Crossbow ROM had it unlocked by default before? Can the ExtROM unlocking operate by itself, independent from the CE ROM?
If this all is the matter, how can I unlock the ExtROM again?
I tried a few "ExtROM Unlock" cabs already, but these only create another entrance called "Storage 2" and it stays locked somehow....
Thanks a ton!!
Check Jwright's WM6 thread, there's a solution in there