I downloaded the so-called "Launch ROM" for the XDA IIs from the SourceO2 web site, this has now stuck my XDA IIs in boot loader, I suspect because it copied over HimaClearJumpCode.exe. So right now I'm a bit stuffed..and yes I know I should have done a backup
so does anyone have the O2 UK operator name/ID so I can try and get the iMate PDA2K ROM on there OR does anyone have he XDA IIs ROM backed up, that they can let me have??
Any help appreciated, as I am potentially the owner of a very expensive door stop...
hi i am in exactly the same position please help ....
Found the O2 UK Operator ID
Well, whilst fiddling around with the batch file, I got onto trying different operator IDs, and I found one that worked:
O2___001
I now have the iMate ROM on my XDAIIs, just hope I haven't broken too much :wink:
excellent !!! xda2s is also now up and running more info 4u
it is fair to say 2 years on i am still a novice
first impressions of imate rom = a stable quick o/s. vast improvment on the O2 effort. ( what r o2 playing at it seems they are continually wounding these great little devices with crippling software)
to resovle issues as above you will need -
xda3nbftool.exe ( found here as an attachment)
a rom of your choice i am running this one -
pda2k_wwe_12200_162_10600_SHIP.exe ( found here-http://forum.xda-developers.com/viewtopic.php?t=14854&postdays=0&postorder=asc&start=25#77518 )
you will need this text to create a batch file to modify the extracted rom files on your pc before runing the upgrade ( simply run the upgrade package it will open itself and will then promt you to selcet next, at this point you navigate to the temp directory somthing like this-C:\Documents and Settings\yourname\Local Settings\Temp\pft34.tmp once you have found the folder which contains among others these files - radio_.nbf nk.nbf ms_.nbf you need to copy and past "xda3nbftool.exe" into this folder along with the text file created from the strings below. ( your almost there) when you get to this position you need to copy the "HimaGetDeviceData.exe" via activsync onto your device then using file explorer on your device navigate to the windows folder here you will see a new file called "device data" copy this and then paste it to your desktop and then print it out ! - on here you will see your device data and on some occasions the operators code. the operators code is important because you need to remove all instances of "O2ASI001" in the strings below and insert in their place your actual operators name. once you have inserted the correct name that applies to your device save the text file and then change its extension from ".txt" to ".bat" you will get a message mentioning stability just continue. one you have accomplished this simply double cllck your " .bat " file . after a little number crunching the whole thing stops thats it your now ready to resume with the upgrade that you extracted earlier..... ( as was pointed out to me above some o2 supplied xda2s dont show operator code using described method as for us two the following did work fine ( O2___001 )
good luck and please realise that what i have presented above is not my work it is a presentation of the facts i have harvested at length from this forum and it is with thanks to you all that my own xda2s is now a worthy companion.::
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -so O2ASI001 ms_.nba
xda3nbftool -so O2ASI001 nk.nba
xda3nbftool -so O2ASI001 radio_.nba
xda3nbftool -c -u NK.nba
xda3nbftool -c -u ms_.nba
xda3nbftool -c -u Radio_.nba
xda3nbftool -x ms_.nba ms_.nbf 0x20040522
xda3nbftool -x nk.nba nk.nbf 0x20040521
xda3nbftool -x radio_.nba radio_.nbf 0x20040523
del *.nba
ROMs supply!
I have an mDA 3 (TMOBILE Germany), and I messed up things. Can anyone send me nbf files with their passwords (Extended ROM, OS and RADIO). I don't know if it'll help. I'm trying to write them to the PDA using er2003edit provided my softworkz.
Cheers
Re: excellent !!! xda2s is also now up and running more info
Hello,
I am running my O2 XDAIIs with the original O2 ROM on it. Is this NEW iMATE ROM any better? What advantages are there?
Cheers,
Dom
is the rom any better ?
hi - if you are happy with the usability of your individual device then i would suggest you stay with it. some of the reasons i was not happy with my original o2 rom are as follows,
1) - very slow to populate screens
2) - having loaded my software device became unstable and kept freezing. ( tomtom3 and other main stream renown applications)
3) - unable to answer the phone. ( would ring but couldnt be connected either by accepting via screen or buttons)
4) - system continually needed soft reset etc etc etc........
the list goes on and on if the only rom available to me was the o2 rom i simply would have had to return the device to my supplier as not fit for the purpose intended..... and failing a full refund sadly my xda 2s would have gone in the bin .
if yours works for you dont alter it as complications can be encountered if you not familier with the process of upgrade as i found to my horror - and subsequently had to read pages and pages of info from this site in order that i could repair my device a concise method of which is outlined above... i would appreciate anyone using the above method to leave feed back on the methods clarity and suggest any improvment they think would help others.
to everyone HAPPY 2005 !
Ok, thanks for the info.
I am experiencing many of the same problems you had so I will try the upgrade as experienced above and see if it makes a difference.
I will let you know how I get on.
Regards,
Dom
Ok, good news and bad news...
Good news:
Upgraded to the new i-mate ROM, looks quite nice. With any luck it will be better than that pile of rubbish that O2 are pumping out on these devices.
Bad news:
I tried to restore the O2 ROM (launch ROM from the SOURCEO2 website). I ran the HimaGetDeviceData.exe and there was no operator name/ID in the DeviceData.txt file. I ran the batch file as before (using the old data :S) but it seemed to corrupt the installation files. Dare-Devil as I am I ran the O2 install and it failed due to corrupt files so I then had to re-run the i-mate install to get the device working. (20 mins of my life I'll never get back)
This isn't a tragic scenario as the i-mate ROM is nice but it would be great to have the option of going back to the old O2 ROM incase they bring out a better version. Can anyone shed any light on this? Where am I going wrong?
Cheers,
Dom
SourceO2 ROM comes with the wrong tools
I think the ROM from the SourceO2 site comes with the wrong tools, I believe they are for the Himalaya not the Blue Angel. The iMate ROM comes with tools starting "BA" whereas the O2 ones start "Hima".
To be honest, I am not even sure the ROM file is correct. I am in exactly the same position as you : tried the SourceO2 ROM, got the stuck in the bootloader, and then had to use the iMate ROM, which is good, but again like you I would like to be able to go back to the O2 ROM if I wanted.
so, really, we need the original O2 XDA IIs ROM to restore our devices? I will get onto finding this and will get back to you if I gather any info.
Cheers,
Dom
Re: SourceO2 ROM comes with the wrong tools
kulster said:
To be honest, I am not even sure the ROM file is correct.
Click to expand...
Click to collapse
http://forum.xda-developers.com/viewtopic.php?t=14996
tomlow1 just received email from O2 that the correct files should now be available under the link
Thanks for the info - I'll download that now!
Cheers,
Dom
Will this work on a T-Mobile UK branded MDA III?
My MDA III is stuck in Bootloader mode after I screwed up the firmware update.
Will this rescue process for the O2 XDA work on my T-Mobile UK branded MDA III?
If so, is there anything I need to change, such as the Operator code?
Many thanks!
PS - Just to confuse things, I'm on Orange UK (but the phone is unlocked)
It should do...
You will have to change the operator code as described in the workthrough above. You will have to find out what operator code to use - ask someone with EXACTLY the same device to run the GetDeviceData part for the workthrough. This should give you the data you need.
I would recommend upgrading to the i-mate ROM then installing the T-Mobile custom files from someone elses extended ROM. If you need any help, just let me know, and I'll see what I can do!
Good Luck!
Dom
PS: I think it's T-MOB101 but check this out first.
Thanks Dom, much appreciated.
XDAs are still all a bit new to me, as I've come from the world of Nokia! I'll give this all a go tonight.
Just one question - how crucial is this operator code? Does it matter which network you're going to use the phone on? For example, the phone was originally T-Mobile. If I reflash it with O2 data and then use it on the Orange network is this still OK? Or should I just enter the equivalent code for Orange when I'm asked for the operator code?
To be honest, I'm not that bothered about losing the T-Mobile branding. If I can make the phone "Orange" flavoured (as this is the network it will be used with) then that would be even better.
However, if the phone is taken back to a state where it's not branded then that's great too.
Thanks again. I'll let you know how I get on.
The operator code is crucial! As far as I'm aware this code refers to the device, not the sim card you are using. The installer checks that your device has the same code as the files. As my device is UK coded I had to hack the setup files and tell it to be UK coded.
For example, I have the O2 branded XDA IIs. To upgrade to the i-mate rom I had to run GetDeviceData to find out my operator code. Then use the batch file to change the install files from Asian coded to UK. The setup will then run correctly and install the new rom.
If you want the orange customised stuff, you'll need to find an Orange Extended rom from a device by Orange and run the cab setup files from that.
Good luck,
Dom
I, too, got my O2 XDA IIs dead on the boot loader after applying the wrong IIs ROM posted earlier. Because my device was bought from a dealer who got it from Hong Kong, it had the (unlocked) HK/Asian ROM.
Now that I can't load GetDeviceData into the device, can someone with a HK XDA IIs confirm the code is O2ASI001 (as in the text above)?
The reason is that when I upload the ROM image, it quits on nk.nbf saying the ROM is not for this device (first install), and quits on the second install with an error, even though both the radio and extended ROM uploaded fine.
Thanks,
Dave
Time taken to update?
HEEELLLPPPP!!!!!!!!!
I don't have the Operator code for the MDAIII, as this was (presumably) destroyed when I foolishly ran the i-mate update.
Is the T-Mobile German code still OK for the UK?
Also, how long should the process take after running MaUpgradeUt.exe (or BaUpgradeUt.exe) to update the MDA/XDA ?
Mine seems to be taking forever...
Thank you for your patience and understanding people!
A write off?!
After many fruitless hours last night, I'm beginning to wonder if my MDA III is a write off.
I must have tried every ROM image on this website and every version of FIX.BAT
I either get an Operator Error, but what happens all the time is that the software just sits there saying its updating, when it clearly isn't.
I don't know what to do now!
Related
Today, I've download a Dopod rom "ba_dopodcht_12406_110_10600_ship.exe"
Afterward, I've unzipped the exe file to several files.
Before ugrading my Eng OS to Traditional chinese, I try to fix the country ID error first.
However, while execute ,
"xda3nbftool -x ms_.nbf ms_.nba 0X2004030522"
The screen prompt out such error,
"Warning: this does not look like a nbf header, possbile you provided the wrong password"
I think it is the 0X2004030522 problem, would there anyone can told me how to solve it or the correct password for those 3 nbf file?
Many thanks.
Old tool wont work on type 2 encription found in that rom.
New tool is not out yet.
MDAIIIUser said:
Old tool wont work on type 2 encription found in that rom.
New tool is not out yet.
Click to expand...
Click to collapse
Thanks MDAIIIUser again.
Then, if nothing to do the files, country id error appear.
So, how can XDA 2s user bypass the country ID error ?
thanks
http://forum.xda-developers.com/viewtopic.php?p=98811#98811
MDAIIIUser said:
http://forum.xda-developers.com/viewtopic.php?p=98811#98811
Click to expand...
Click to collapse
oh.... thanks, I will try the CheckCEID_type =1 in this few day.
Hello MDAIIIuser, it is implied that no matter the upgrade.exe (shipped) is originally design for which country, using the special method can bypass the country id error ?
thanks
Well if you want to read it that way the answer is yes,
but if it does not work then the answer would be no.
I Never tried it!
The method is working allways when the device is still running.
However when the device is jumping into bootloadermode then it checks again.
With some upgrade files it works when it is in bootloader mode and with some other updates it wont work when your device is in bootloader mode.
It does work with o2 and with latest update from qtek.nu
I am scared to try i with chinese versions since i can't read chinese
I already try few times but not working,evem I try to used others tools in here still get error.
Thanks mwang reply and thanks all of the above.
However, it is quite confuse that someone (like mwang) can't work but someone work fine.
Could any experienced member try to explain it ?
Thanks for your kindly reply.
Dear All and MDAIIIUser,
Chris and me has been test this special method [CheckCEID_type]=1 on the dopod version.
Unfortunately, it fail and the country id error has been appear again.
1) The xda3nbftool can't work and prompt the password is incorrect
2) CheckCEID_type =1 still can't work.
Do any expert can help me , how can we upgrade our device to Dopod version ?
Thanks
I've spent hours going through the beginner's guide and have searched all over for this. I'm confused because I've seen different answers and explanations to this so would appreciate some advice.
I'm running an O2 Asia IIs on the latest ROM and I'm sick of the lack of stability and the need to reset it 2-3 times a day. So, I've decided to change ROMs, and have been recommended the iMate ROM (although if anyone else knows of other reliable ROMs then let me know)
My device from getdevicedata is:
PH20B 0 B WWE E O2ASI001 1.40.00 0 0 1.40.923 1.12.00 12.00
Where I'm stuck and scared of moving forwards is: I've tried running the xda3nbftool against PDA2k_WWE_14000_176_11200 but it keeps saying that the password is wrong. I've discovered that I need to run it with the -t option against the nbf files to get the passwords out so I tried that, but there's no password for the radio_.nbf file. And then after I've modified the editfix batch file with the updated passwords for the ms_.nbf file and the nk.nbf file, it still says that the password could be wrong the first time (subsequent runs don't say this however).
Then I saw the info about the "TYPE II" methodology, so I am confused and don't want to risk having a phone that is dead or unusable for a period of time because I chose to do it the wrong way - I want to do this the right way and have honestly checked everything I can think of to get this working - if someone could set me on the right path it would be great.
Thanks
simopimo
I'm using the O2 Asia ROM, on my PDA2k, before of the dodgy i-Mate Bluetooth Headset Problems
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.
http://t-mobile.iris-global.com/files/BA_TMUK_14200_112_11300_Ship.exe
Seems to have appeared as the FINAL offical release from t-mobile for uk users.
I've not tried it yet but the number does seem to suggest it is a slightly lower version than the Dutch one
EDIT MDAIIIUser
Added to wiki
no surprises
build of 2003se identical to Dutch rom previously released:
version 4.21.1088 (build 15159.2.6.4)
Extended rom just hasth changed regional settings (english UK default)
Added to wiki
Still a lot of echo.
Can't pair my Motorola HS820, BA sees the HS820, but error on connecting.
Anyone a fix for the echo and for the BT problem?
Use 1.40 before, was less a problem compaired to 1.42
Please help.
Regards,
Max
Report Back - T-Mobile Rom.. One week or so on..
Hi All,
Wanted to feedback my impressions of the new 1.42 T-Mobile UK Spec Rom..
Well, it's been interesting.. I now have (or have had) most of the faults that everyone else is experiencing.. I never used to get them at all with the i-mate 1.40 Rom or the NL 1.42 T-Mobile Rom.. I have listed the bugs below..
1 - One Hard-reset when inserted into GPS Car holder
2 - Several occasions where I've "lost" the Storage Card (when serching for it on the device AND through Active Sync)
3 - Interesting situation where I've started TomTom5 and I've suddenly had to go through the set-up process again only to be told that there's no maps (Can only attribute this to an occasion where the Storage Card is not seen by the PPC - See above).. Solved by remove Programs, soft-reset then re-install off SD Card.. (quite annoying as I was lost at the time!)
4 - Occasional failure for BT Headset being recognised on an in-coming call (I use the Logi-Tech Pro).. Solved by Soft-reset..
5 - Sometimes, after soft-reset, get a low performance from the Device.. ie, after soft-reset and switching to phone where it takes a few seconds to "build" the phone screen..
Strange but as I mentioned above, I don't recall getting these bugs on the 1.42 NL Rom or the i-mate 1.40 Rom.. I might try a hard re-set on Monday then re-install my tomTom, etc to see if it carries on.. If it does, I MIGHT switch back to the either :shock:
That's it really.. I have had the early T-Mobile 1.06, the i-mate 1.40, T-Mobile NL 1.42 and T-Mobile GB 1.42 and finally the WM5 Roms and from what I've seen, I place them in this order of preference..
1 - i-Mate 1.40
2 - T-Mobile NL 1.42
3 - T-Mobile GB 1.42
4 - WM5
5 - T-Mobile GB 1.06
Hi,
Updated to the dutch ROM, is better then this UK ROM.
Version number is also newer.
Regards,
Max
dazed and confused
sorry if I'm being simple but ....
I though this was the last offical rom
http://www.iris-global.com/t_mobile_download/download_manager_mda_com.html
MA_TMUK_11300_128_11200_SHIP.exe
Rather than
http://t-mobile.iris-global.com/files/BA_TMUK_14200_112_11300_Ship.exe
How did you maanage to find the link?
What is the diference between the builds - How can I find a change log?
What is the BA / MA?
:?:
See here:
http://forum.xda-developers.com/viewtopic.php?t=31360
No difference in UK and NL Rom..?
[email protected] said:
Hi,
Updated to the dutch ROM, is better then this UK ROM.
Version number is also newer.
Regards,
Max
Click to expand...
Click to collapse
Hi Max,
The Rom is exactly the same and the only difference is the changes in the extROM that makes it either UK or NL Spec (ie, MMS settings, etc)
Hi Starfish - Perhaps you need to look at this for the answers to your other questions:
http://wiki.xda-developers.com/index.php?pagename=BlueAngel_For_Beginners
Oh, and BA is "Blue Angel" and MA is the "Magician" HTC Names for the devices..
Sorry I did'nt read close enough Magican vs Blue angel
starfish_001 said:
Sorry I did'nt read close enough Magican vs Blue angel
Click to expand...
Click to collapse
That's ok.. We all have to start somewhere.. 8)
Now, I'm not too sure how far advanced you are in Upgrading, etc but before you do, please remember the following that I put on another post on here..
MrPhilly said:
General Tips to you (and others)..
If you do want to update or upgrade then make sure you read everything through first.. Make sure you're happy in doing it.. Perhaps use the search function to read through others comments.. I would also recommend reading others comments about trying to downgrade from WM5 to WM2003SE to see what others have encountered
You will not believe the amount of people who end up posting questions when they've not followed the instructions from Wiki that I've pasted for you here..
Finally, if you are stuck, use the search command and describe your problem in the Keywords section, select Blue Angel from the Category and read through the posts relating to it before posting questions..
Hope this helps..?
Cheers!
Click to expand...
Click to collapse
How can I upgrade to a stable rom
I have tried the TMobile NL and UK version both give the Country ID eror with the extra numbers 17-17-38-38-38
How can I safely upgrade to the 1.42 version (I have read the Getting Started With The Blue Angel) .
Is that the way to go?
"I get the password error on the xda3nbftool for the nbf segment"
I would like to get rid of all the phonesound failure and systemhangs with TomTom5.10
My Qtek9090
PH20B 0 B
WWE E
DANGA001
1.40.00 0 0
1.40.556
1.13.00 13.00
Upgraded to this from the last O2 update (my BA is an O2 Xda IIs), and while for the most part it works fine, now if the device turns the screen off for power-save while out and about, the GPRS connection drops. I know the hardware is capable of keeping the GPRS connection alive in such a situation because, well, it didn't drop it under the previous two O2 ROMs I ran.
Anyone else had this problem, or know a fix? Hopefully it's something simple that I've overlooked...
I'm getting better Bluetooth support with this (whether through actual improvements in the stack or through sheer dumb luck), so I'd prefer not to downgrade if I can avoid it.
Upgrade for NON OEM/Carrier Blue Angel
I have an unlocked OEM i-mate PDA2K. Because of this I am unable to install the T-Mobile upgrade to 1.42.
Is there a way to get around this?
I tried using the MaUpgradeUt_noID.exe, but I was unsuccessful.
Any ideas on how to upgrade a non-T-mobile branded blue angel?
Thanks
problems upgrading a non-t-mobile branded PD2K
BELOW IS THE SCREENSHOT OF THE ERROR
Did you make sure you had the MAUpdate file in the same directory as the actual upgrade had been uncompressed into? Since it's missing the RUU.DLL file that is part of that package.
Basically, get the files out of the real upgrade, then copy the MAUpdate into that directory, then run it instead.
I can not unzip or unpackaged the shipped OS
When I double click on the file, it runs the file, when you right-click and select extract, it gives you an error.
How do you unpackage the ship package?
Me, I used WinZip, I think it was.
Can not unrar or unzip setup files from exe package
the instructions states:
Unrar or unzip all files in exe or rar into a new folder. I get an error when I do that.
I also noticed that the instructions states:
First Method (Quick/Easy) (TYPE II), but there is another method Second Method (Slower/Harder) (TYPE I)
I am going to give that a try
O2 XDA IIs
Hi from Greece,
A friend bring me to Greece from Singapore one O2 XDA IIs but it has a old versions:
rom 1.31.00 wwe
rom date: 12/13/04
radio v:1.02.00
protocol version: 1337.32
ExtROM version: 1.31.920 wwe
sorry but I'm newbie here, can you tell me what (and where can i find) I must download in order to update to the latest versions.
I allready download the latest version from O2.UK for O2-XDA IIS but I do not want to lock my device to any network and that's the reason who asked you and I do not install this I allready download.
I allready see http://wiki.xda-developers.com/index.php?pagename=BA_Upgrades but I don t now what I must download.
thk u
For those who wanna just unlock but still want to use orange ROM
with GPS-enable
1. Using HTC_Trinity_SIM_CID_Unlock_v1.zip, run it unlock Orange
2. download new dopod d810 rom
http://forum.xda-developers.com/showthread.php?t=293809
3. extract RUU_Trinity_DOPODASIA_WWE_1.23.707.6_6275_1.35.00.11_108_Ship.exe
by using winrar , you will see a lot of file, find out RUU_signed.nbh
4. download dutty's good NBHTool v1.0
http://forum.xda-developers.com/showthread.php?t=296314
5. using it NBH to NB, to extract RUU_signed.nbh , find out Radio.nb
6. using NB to NBH, just put radio.nb in to radio, then change version to 1.23.61.5, device choose trin100, then generate NBH file
7. download Custom RUU Updater
http://forum.xda-developers.com/showthread.php?t=295113
extract it
8. copy the NBH file ( RUU_signed.nbh) should be around 13.5MB to
ModifiedRUUUpdater-V2-TRIN folder
9. run ROMUpdateUtility.exe
at the end, you will still using orange rom but only update the radio rom to 1.35.00.11
there maybe a easy way to do it, that's just what i have done for unlock sim and using gps-enable Orange rom~~
great guide! was holding off unlocking my m700 cos i'd loose the gps until orange released a wwe rom so now all unlocked and sorted!
help!
hi guys, i have just read some of these threads and as a non developer and simply a new SPV M700 user i am bewildered!
i don't suppose anyone would take a few minutes just to tell me in simple terms what the advantages of unlocking the SIM are and then let me have a step by step guide as to exactly how i download the phone pad software?
I read about the latest dopod ROM and obviously didn't understand a thing.
If this is not really worth your time, i totally understand but thanks for considering it anyway.
If anyone wants to email me and then give me a basic lesson via telephone then i would be extremely grateful.
In return any legal questions answered - fair trade?!
Thank you,
Raj
help
PS - my email address is [email protected]
actually what are you looking for?
advantages of unlocking the SIM only allow you to use any sim card you want, e.g. O2, vodafone..etc...
well, if it is easy to do, any basic guidance would be most welcome!
Hi !
Can I unlock SIM M700 using HTC_Trinity_SIM_CID_Unlock_v1.zip , without any other files ?
And from where I can download this ?
http://forum.xda-developers.com/showthread.php?t=293957
Hi guys!
Please excuse my ignorance.. I'm a total newbie... Can anybody please tell me how to get back the original orange uk rom on the spv m700? i just like the orange logo and settings back...I'm sorry if similar question has been asked already, i couldn't find the thread if there's any... Any suggestion is much appreciated.. thanks alot!
this is the thread, just follow the step i wrote in here, then you will keep using orange rom with sim unlock and gps enable..
Thanks very much, followed the steps - no problems, Works with my O2 sim Cheers. Wireless seems slower now though anyone else have the same problem?
Just checked the Wireless LAN settings - power mode setting has to be best performance now, it used to work fine set to best battery, hope this doesn't use all the power too fast now
Good job first!
I got one question. I got an orange M700 Dutch version and just only unlock the network with AUTO_Unlock_v1.bat. At point six (6. using NB to NBH, just put radio.nb in to radio, then change version to 1.23.61.5, device choose trin100, then generate NBH file)
1 Do I have to leave CID Type: SuperCID Or do I have to SiperCID my device?
2 Do I have to leave the language WWE or should it be Dutch???
Orange SPV ROM upgrade issue
Hi,
Has anyone else had a problem after upgrading their Orange SPV M700?
The upgrade went smoothly and the phone works fine when I put an O2 SIM (from my work mobile) in but when I put my Orange one back in it comes up as an invalid SIM
When I went to the Orange shop, the guy said that Orange lock the SIMs if they find the ROM has been tampered with - but I can't find any other references to that.
Anyone have any thoughts?
siupiu said:
For those who wanna just unlock but still want to use orange ROM
with GPS-enable
1. Using HTC_Trinity_SIM_CID_Unlock_v1.zip, run it unlock Orange
2. download new dopod d810 rom
http://forum.xda-developers.com/showthread.php?t=293809
3. extract RUU_Trinity_DOPODASIA_WWE_1.23.707.6_6275_1.35.00.11_108_Ship.exe
by using winrar , you will see a lot of file, find out RUU_signed.nbh
4. download dutty's good NBHTool v1.0
http://forum.xda-developers.com/showthread.php?t=296314
5. using it NBH to NB, to extract RUU_signed.nbh , find out Radio.nb
6. using NB to NBH, just put radio.nb in to radio, then change version to 1.23.61.5, device choose trin100, then generate NBH file
7. download Custom RUU Updater
http://forum.xda-developers.com/showthread.php?t=295113
extract it
8. copy the NBH file ( RUU_signed.nbh) should be around 13.5MB to
ModifiedRUUUpdater-V2-TRIN folder
9. run ROMUpdateUtility.exe
at the end, you will still using orange rom but only update the radio rom to 1.35.00.11
there maybe a easy way to do it, that's just what i have done for unlock sim and using gps-enable Orange rom~~
Click to expand...
Click to collapse
Can you post the final exe(ROMUpdateUtility.exe)? Because i have orange and little experience about that type of procedure...
I have the M700 White form orange and i didnt have to unlock the CID to upgrade to WM6 its just did it. Now im rying to do a mates old T-mobile MDA Vario (Wizard) now thats areal pain in the Arrrrrrrrse. Managed it though after a lot of searching and reading on this forum.
but back to the Trinity i just downloaded the rom i fancie na d ran the install and it did it no bother.
nealcass said:
Hi,
Has anyone else had a problem after upgrading their Orange SPV M700?
The upgrade went smoothly and the phone works fine when I put an O2 SIM (from my work mobile) in but when I put my Orange one back in it comes up as an invalid SIM
When I went to the Orange shop, the guy said that Orange lock the SIMs if they find the ROM has been tampered with - but I can't find any other references to that.
Anyone have any thoughts?
Click to expand...
Click to collapse
Dont you need to unlock the Sim and not the CIS ist two different things
thanks a lot
Just for reference: I did this - got to last step and got a connection error from my device. It flashed up the connection error on my pc, but the pda went to tri-colour screen.
I then ran ROMupdate utility again, with the tri-colout screen still showing on pda and it worked
great guide very help ful
thank you