Some interesting things on the T-Mobile 1.60 update software

[killercheung]

I tried the T-Mobile 1.60 rom on my O2 xda2.
It works perfectly with my xda2.

However, I found some interest thing on the new rom upgrade process
1. It seems XDA2 (or HTC Himalaya) use one single program for RAIDO / Extended Rom / OS Rom update. It seems Radio upgrade failure may no longer case device failure, because the RADIO upgrade process is same as OS upgrade process, and not required to copy the whole software into the RAM to upgrade.


2. Sinces some of us (and my XDA2) report that the exteneded rom is READ ONLY, but the upgrade program can update the extended rom. That means the Exteneded rom is not REALLY read only, but somewhere locked it. More funny is , it is seems the Main OS rom is not controlling the exteneded rom is locked or not, because after I updated the extended rom, it is still locked.

3. If O2 XDA2 can use T-Mobile MDA2 update, it seems the upgrade software no longer check the header of the device (At lease this version won't). I think we can use it to change device's language. However I don't know how to dump the rom in .nbf format, is that possible to convert the nb1 format to nbf format?

Thanks.

[DenisJ]

Hi killercheung...
where are you find the 1.60 rom ?
and the radio what version is ?

Can you put it in my ftp pls ?
it's always on
ftp://dgmatic.com
user: xda
pass: xda
port: 21

...like this we can have it all

Thanks in advance
Denis

[arebelspy]

I asked here for you, hopefully it will be available for everyone soon:

http://www.ppcsg.com/forums/viewtopic.php?p=173744#173744

:)

-arebelspy

[keithop]

killercheung, thanks for that... I'm still deciding whether to apply the new rom to my UK XDA II.... is the language of the rom netherlands? or can I have it all in english as it is with the normal O2 rom?

Do we lose anything from the o2 rom/extended rom ?

I'm wondering if O2 do bring an upgrade out if we'll be able to still use it if we've tried this t-mobile 1.60 rom.... hmmmmm

hmmm decisions decisions... do you think its much better than the current o2 rom?

[Wiz]

Now that I have moved to the 1.60 rom, I must say there's ONE thing I DO miss .... :cry:

My O2 BUBBLES ARE GONE :cry: FROM MY ASIAN O2.

(I obviously knew this could happen, but thought I'd made a backup of my extended ROM (I DID, but I accidentally tossed it a few days ago) . Who would be so kind as to send me a copy of the O2.cab file from the extended rom, so that I can put the bubbles back into my dialer ...)

[satria]

Now that I have moved to the 1.60 rom, I must say there's ONE thing I DO miss .... :cry:

My O2 BUBBLES ARE GONE :cry: FROM MY ASIAN O2.

(I obviously knew this could happen, but thought I'd made a backup of my extended ROM (I DID, but I accidentally tossed it a few days ago) . Who would be so kind as to send me a copy of the O2.cab file from the extended rom, so that I can put the bubbles back into my dialer ...)

No need to be sad. Check ur e-mail. Inform me if it doesn't arrive. :)

[ming]

Now that I have moved to the 1.60 rom, I must say there's ONE thing I DO miss .... :cry:

My O2 BUBBLES ARE GONE :cry: FROM MY ASIAN O2.

(I obviously knew this could happen, but thought I'd made a backup of my extended ROM (I DID, but I accidentally tossed it a few days ago) . Who would be so kind as to send me a copy of the O2.cab file from the extended rom, so that I can put the bubbles back into my dialer ...)

No need to be sad. Check ur e-mail. Inform me if it doesn't arrive. :)

mind sending me a copy too ?
thanks in advance

ming14@magix.com.sg

[somesex]

Hi Killercheung,

You've missed out something ... the EXE file can be unzipped (using Winrar) ... you will then see the same upgrade.exe files, nbf files (3 of them) ... you can then deleted the ms_.nbf so that only the CORE ROM and RADIO is updated, and keep all O2 EXTENDED_ROM content untouch.

You can also use the same method to upgrade to Chinese ...

somesex





I tried the T-Mobile 1.60 rom on my O2 xda2.
It works perfectly with my xda2.

However, I found some interest thing on the new rom upgrade process
1. It seems XDA2 (or HTC Himalaya) use one single program for RAIDO / Extended Rom / OS Rom update. It seems Radio upgrade failure may no longer case device failure, because the RADIO upgrade process is same as OS upgrade process, and not required to copy the whole software into the RAM to upgrade.


2. Sinces some of us (and my XDA2) report that the exteneded rom is READ ONLY, but the upgrade program can update the extended rom. That means the Exteneded rom is not REALLY read only, but somewhere locked it. More funny is , it is seems the Main OS rom is not controlling the exteneded rom is locked or not, because after I updated the extended rom, it is still locked.

3. If O2 XDA2 can use T-Mobile MDA2 update, it seems the upgrade software no longer check the header of the device (At lease this version won't). I think we can use it to change device's language. However I don't know how to dump the rom in .nbf format, is that possible to convert the nb1 format to nbf format?

Thanks.

[Wiz]

Good news about the T-Mobile ROM. I don't know what they have fixed/patched, but my O2 XDA II ROM never bothered to disconnect the GPRS connection after having spent some time online, not after surfing, not after checking e-mail. Mind you the T-moblile ROM doesn't either, except ....... when checking e-mail, which in my eyes is quite important.

So now I can go back to have my XDA check my e-mail once per hour, knowing that it will disconnect automatically.

(And Satria, thanks for sending me my bubbles :)

[satria]

@ ming:

check ur email. Also I've seen ur review at PPCSG forum. Great.

Regards,
satria

[JoseF]

Hi,
Just one question. Did any of you that make the update testet with the bluetooth GPS?
If yes, It works? or you still have to install TOWA´s patch?
Regards

JoseF

[killercheung]

Hi Killercheung,

You've missed out something ... the EXE file can be unzipped (using Winrar) ... you will then see the same upgrade.exe files, nbf files (3 of them) ... you can then deleted the ms_.nbf so that only the CORE ROM and RADIO is updated, and keep all O2 EXTENDED_ROM content untouch.

You can also use the same method to upgrade to Chinese ...

somesex


I know that, and I did unzip them beforce upgrade.
The problem is I don't know how to get a CHINESE ROM in NBF format...

[Gilbert]

Hi guys,

I did the update to rom 1.60 and it is great. I have an Imate Pocet PC. the new rom is excellent but with one sad thing and that is if the device goes in standby mode the GPRS connection if you are connected to the internet goes off as well :twisted: :twisted: :twisted: :twisted: :twisted: :( :( :( i there a fix to this.

Thanks,

Gilbert
gilbert_halaby@yahoo.com

[somesex]

Hi Killercheung,

You've missed out something ... the EXE file can be unzipped (using Winrar) ... you will then see the same upgrade.exe files, nbf files (3 of them) ... you can then deleted the ms_.nbf so that only the CORE ROM and RADIO is updated, and keep all O2 EXTENDED_ROM content untouch.

You can also use the same method to upgrade to Chinese ...

somesex


I know that, and I did unzip them beforce upgrade.
The problem is I don't know how to get a CHINESE ROM in NBF format...

For NBF, you can use XDAtools to capture the Chinese ROM, I did once with the English ROM and the file size is exactly the same as the one in 1.60 update. So there should have no missing bytes in the saved file.

For the EXTENDED_ROM, no idea how to save in NBF format ..

[axbl]

I have installed the update but TomTom doesnt see the serial ports 4/5.

[JoseF]

@axbl
Hi, What do you think about the update? It´s mutch better than before?
You say "TomTom doesnt see the serial ports 4/5."
Have you installd Towa solution?
Regards
JoseF

[keithop]

one sad thing and that is if the device goes in standby mode the GPRS connection if you are connected to the internet goes off as well

yikes...... did that happen on the old rom as well or did gprs stay connected on the original rom?

I hate the way gprs disconnects on devices.. it's supposed to be always on, and I'd really prefer if it stayed on during suspend etc so that MSN could stay connected, notifying me when I got a message....

Email checking likewise, I'd prefer gprs remained always connected and it'd check email in the background whether off or on, notifying me when it got a new mail.

I can't check the behaviour of my xda II since Im on "roaming" at the moment in another country so no gprs :(

but can anyone say for sure which way the old vs new rom work in this regard?

[itsme]

I did some research on the upgrade process, and fileformats:

http://www.xs4all.nl/~itsme/projects/xda/xdaii-update-format.html

[arebelspy]

I did some research on the upgrade process, and fileformats:

http://www.xs4all.nl/~itsme/projects/xda/xdaii-update-format.html

I get an error 403 forbidden when I try this link.. odd thing is it was working for me earlier..

-arebelspy

[itsme]

oeps. fixed now.

[killercheung]

For NBF, you can use XDAtools to capture the Chinese ROM, I did once with the English ROM and the file size is exactly the same as the one in 1.60 update. So there should have no missing bytes in the saved file.

For the EXTENDED_ROM, no idea how to save in NBF format ..

Since my device already upgraded to 1.60, I only can try to dump the 1.60 in nbf format.

However it seems the dumped size is not correct.
It is only 31.0 m (vs 31.5m), would you mind to tell me how to dump it by osimagetool? I use version 1.05.

And as expected, it is not usable with the Himaupgradeut.exe (It said it is not a vaild rom files or something like that).

[somesex]

For NBF, you can use XDAtools to capture the Chinese ROM, I did once with the English ROM and the file size is exactly the same as the one in 1.60 update. So there should have no missing bytes in the saved file.

For the EXTENDED_ROM, no idea how to save in NBF format ..

Since my device already upgraded to 1.60, I only can try to dump the 1.60 in nbf format.

However it seems the dumped size is not correct.
It is only 31.0 m (vs 31.5m), would you mind to tell me how to dump it by osimagetool? I use version 1.05.

And as expected, it is not usable with the Himaupgradeut.exe (It said it is not a vaild rom files or something like that).

Hi,

I'd used XDAtools (still from this website) rather than osimagetools to capture the image file. The file size is supposingly the same as in the update tools. You might want to try.

[killercheung]

Hi Somesex,

Do you mean this one?
http://xda-developers.com/XDAtools/

If you are talking this one, the dump rom utility should be os image tool.

Thanks.

[itsme]

xdatools and osimagetool are one and the same. ( maybe you have different versions )

hmm, yes now you mention it, the size is a bit strange,

it contains a 64 byte header
then a 256k bootloader
followed by 31.25 M of rom.

the old xda-i format was as follows:
a 32 byte header
a 256k bootloader
30.75 M of rom

updated my page, now a tool is included that can both encrypt and decrypt.

[itsme]

I forgot to mention, that the extra 512k in the xda-ii nbf's is just empty space. you can fill it with zeroes.

[killercheung]

hi Itsme..

is that any problem with me ...
the new encrypt tools page seems not accessable for me..

"You don't have permission to access /~itsme/projects/xda/xda2nbftool.cpp on this server."

By the right, is that possible to
1. write a tools to edit the ms_.nbf
2. I already got an dumped chinese XDA2 rom with pmemdump in nb1 format.
However it seems not writable directly with bootabler. I am thinking how to write it by himaupgrade, and the rom dumped by pmemdump miss 412bytes in the head.

What I have to do to convert this file to a himaupgrade usable format?
May be the above question is a little bit stupid, but I am not a programmer...

Thanks.

[jpiek]

Can anyone inform me about the changes in the ROM update for bluetooth ?

As i understand the new ROM allows Bluetooth GPS, but does it support audio over Headset or even better, a handsfreeprofile ?

[itsme]

damn file permissions, keep chasing me. fixed again.

ms_.nbf can be editted under linux, if you mount it via the loopback device, with offset 0x70040mount -o loop,offset=0x70040 -t vfat ms_.nbf /mnt/loop0
and then just modify the filesystem mounted under /mnt/loop0

412 bytes is a strange number to miss. more likely 64 bytes,
I would have to change splitrom to also support xda-ii files I think.

[akira]

anyone found this problem?

after flashing
I cant copy files from any place to anyplace
the device copies it, but then keeps on thinking and thinking

i solved it by not installen the t-mobile TMDNLcustomize.sa.CAB file from extended rom
this error is not present anymore

dunno if anyone else had this

[killercheung]

The file explorer seems not quite stable in the 1.60 rom.
So I use Resco Explorer ...

[dnathan]

Can anyone inform me about the changes in the ROM update for bluetooth ?

As i understand the new ROM allows Bluetooth GPS, but does it support audio over Headset or even better, a handsfreeprofile ?

Hi there,

have you had any luck with answers with the above Qs? I've tried other threads like PPCSG and such but no luck. Do let us know if you've had any success with these questions.

Cheers,

[sider]

Now that I have moved to the 1.60 rom, I must say there's ONE thing I DO miss .... :cry:

My O2 BUBBLES ARE GONE :cry: FROM MY ASIAN O2.

(I obviously knew this could happen, but thought I'd made a backup of my extended ROM (I DID, but I accidentally tossed it a few days ago) . Who would be so kind as to send me a copy of the O2.cab file from the extended rom, so that I can put the bubbles back into my dialer ...)

No need to be sad. Check ur e-mail. Inform me if it doesn't arrive. :)

Can I also get a copy of that please?
You seem to be our only source
Thanks for the bother :)

sider@gawab.com

[van]

My MDA II

ROM version: 1.60.00WWE
ROM date: 12/03/03
Radio version: 1.06.01
Protocol version: 1337.16
ExtROM version: 1.60.06

I have been using new rom for 3 days, It seems alot of things better than Original ROM and more stable :P :lol: :D :D

http://www.myxda.com/XdaII/personal/template/XdaIIKnownLimitations.vm

I think that at least 7-10 bugs already fixed from XdaII Known Limitations

Thanks :D

[pjcltd]

Help HELP

I have put the 1.6 rom on my xda II

I have big problems i need to put my UK rom back on my XDA
Help please

I made a back of my ROM using the XDA tools prog

Now what do i do ?

[jpiek]

Can anyone inform me about the changes in the ROM update for bluetooth ?

As i understand the new ROM allows Bluetooth GPS, but does it support audio over Headset or even better, a handsfreeprofile ?

Hi there,

have you had any luck with answers with the above Qs? I've tried other threads like PPCSG and such but no luck. Do let us know if you've had any success with these questions.


Sad to say i haven't had any replies on these questions :(

[somesex]

The file explorer seems not quite stable in the 1.60 rom.
So I use Resco Explorer ...

Hi, can you try to remove the SD card (if you have) during restart, insert it back after WM2003 loaded, and see if your errors are still there or not.

Because I just got a Chinese XDA2 and found the same problem ... its rom is 1.50 ...

[Panabax]

If it supports bluetooth handsfree, I can't figure out how to enable it. I think the answer is no; however, it does fix the bluetooth serial port issue which was preventing the use of BT GPS units.

Panabax

[jpiek]

If it supports bluetooth handsfree, I can't figure out how to enable it.


pair with a carkit and say yes if it offers your MDA a handfree :)


I think the answer is no; however, it does fix the bluetooth serial port issue which was preventing the use of BT GPS units.

thats a fux to a problem i don't have ;)' comming froma XDA i miss the audio out, i hoped to use handsfree BT for it.. headset only supports audio by phone....

[palmop]

If it supports bluetooth handsfree, I can't figure out how to enable it. I think the answer is no; however, it does fix the bluetooth serial port issue which was preventing the use of BT GPS units.

Panabax

I am trying to connect to my EMTAC GPS, but it fails. Which COM port are you using?

Edit:
Scratch that, I forgot to enable outgoing serial/COM5 :)

[Panabax]

I am trying to connect to my EMTAC GPS, but it fails. Which COM port are you using?



OK, connecting to the bluetooth com port with the 1.60 ROM is similar to setting up bluetooth activesync. First, unpair your gps device if it is paired. Then go to Settings/Bluetooth Settings and check Outbound COM Port: COM5. Then it will tell you to bond with the serial device. At this point, pair with the gps device and then set your GPS software to use COM 5.

It worked for me without any problems in Pocket CoPilot.

Panabax

[palmop]

Interestingly several things no longer exist in startup, which is good, including bpinsert, ussd, sms receiver and bluetooth icon. I guess they are now built into the system.

PalMop

[GuardianZX9]

The Handsfree, BT Icon, and others seem to all be dll's now, does that mean they are no longer taking up valuable program slots?

[palmop]

Correct, they no longer use our 32 app space :)

[King]

anyone found this problem?

after flashing
I cant copy files from any place to anyplace
the device copies it, but then keeps on thinking and thinking

i solved it by not installen the t-mobile TMDNLcustomize.sa.CAB file from extended rom
this error is not present anymore

dunno if anyone else had this

Sounds peculiar...

no problems after? So what did you do, remove the cab file from startup then soft reset? Then it was fine?

Because if that's the case, there are a lot of CAB files we could remove from the T-mobile update.

[akira]

yes i removed it from the list config.txt
and deleted the cab

well extracted the cab
so i could get the phone skin and wav ringtone out :)

[killercheung]

Thanks all.

Finally I can edit the extended rom in my XDA2.
1.install Linux :(
2. as XDA developer Itsme, mount the ms_.nbf , and edit the contain.
3. move the edited ms_.nbf back to windows, and flash your device. You can simply extract the original upgrade EXE , delete nk.nbf and radio.nbf (?) , just leave the ms_.nbf.
4. Then run the upgrade program, it will just update the extended rom and will not hardreset your machine. Of course, since you may installed some unwanted T-Mobile setting and there is no option to uninstall, I recommand you hard-reset it.

More details will post tonight.

[King]

yes i removed it from the list config.txt
and deleted the cab

well extracted the cab
so i could get the phone skin and wav ringtone out :)

Whoa...hold on...elaborate please...I'm going to flash it, and I need you to explain to me what you did. I'm already guessing that you DL'ed the software from scarybear and ppcw.net, so I've got those ready.

I'm guessing that if you could remove the T-mobile CAB, then the other CAB files can also be removed, and the new extended_ROM could still imitate the old one in the i-mate, but with most of the bugs fixed already.

[mr.smile1]

damn file permissions, keep chasing me. fixed again.

ms_.nbf can be editted under linux, if you mount it via the loopback device, with offset 0x70040mount -o loop,offset=0x70040 -t vfat ms_.nbf /mnt/loop0
and then just modify the filesystem mounted under /mnt/loop0


Got it ! :P :P :P
Now, can I totally edit the NBF ? Can I exchange the cabs, can I simply delete some and make changes to Config.txt and then update the PDA with the modified NBF ?
Do I have to check for keeping the same filesize and how can I do that?

Thanks for further insight !!!

[akira]

i installed the rom update like it should normally go
and then installed a reg editor, for opening extended_rom
then edited config.txt and removed the line (sorry cant remember wich one it was)
and hard reseted

now no tmobile stuff was on my system

and the copy past in explorer with files was solved for me

[King]

i installed the rom update like it should normally go
and then installed a reg editor, for opening extended_rom
then edited config.txt and removed the line (sorry cant remember wich one it was)
and hard reseted

now no tmobile stuff was on my system

and the copy past in explorer with files was solved for me

Alright. I'll go do that as well. I'm sure the reg editor from scary bears will work anyway. But just in case, which one did you use, and where did you get it?

[palmop]

You can use the extended rom viewer cab from ppcw.net, it is easier ;)

I wrote this on a thread in ppcsg, the steps I took (backup part is not a must, but for those who want to play safe :) ):

1. Connect the XDA II via serial cable (gomadic.com sells XDA serial cables, which is perfect for this job).
2. Put XDA II into bootloader mode (Power+Direction+Reset)
3. Run Hyperterminal on your pc, connect to com port directly, 8n1, 115200
4. You'll see the command prompt. Enter d2s, this will dump the ROM to SD. It will wipe off everything from SD, so you need an empty SD card, 64Mb.
5. Keep the SD in a safe place.
6. Reset the device.
7. Follow the instructions of upgrade, if it fails, insert SD, put the device in bootloader mode and hit camera button and you can flash from SD back.
8. Once update is completed, calibrate, let the customizations run.
9. Install the extended rom viewer cab from ppcw.net
10. Reset
11. Edit config.txt, remove unnecessary items. Mine shows:

EXEC:\Extended_ROM\TPDisable.exe
CAB: \Extended_ROM\CameraRC131_WWE_1.5.sa.CAB
CAB: \Extended_ROM\MIDI56.sa.CAB
CAB: \Extended_ROM\CallerIDRC11_WWE_1.5.sa.CAB
CAB: \Extended_ROM\MMS1507_WWE.sa.CAB
CAB: \Extended_ROM\ClearVue_WWE.sa.CAB
CAB: \Extended_ROM\TMCOMREG.sa.CAB
CAB: \Extended_ROM\Version_AKU1.sa.CAB
CAB: \Extended_ROM\OEM_AKU1_WWE_4AP.sa.CAB
CAB: \Extended_ROM\OEM_WWE_03120301.sa.CAB
CAB: \Extended_ROM\VideoMMS.sa.CAB
CAB: \Extended_ROM\Broadcast_WWE.sa.CAB
CAB: \Extended_ROM\TM_phone_class10.CAB
CAB: \Extended_ROM\Extended_ROM_viewer.CAB
EXEC:\Extended_ROM\TPEnable.exe
RST: Reset

I added Extended_ROM_Viewer.cab to the Extended_ROM folder.

12. Once all is set, save the file, hard reset (Power + reset). It will run only the customizations/apps you setup in config.txt

13. You are good to go.

[mr.smile1]

Nice instructions.

Keep in mind - it only works your way if the Ext. ROM is not write-protected. Most new MDA/XDAs, it is nowadays.

[King]

Nice instructions.

Keep in mind - it only works your way if the Ext. ROM is not write-protected. Most new MDA/XDAs, it is nowadays.

It looks like mine is...what do I do then?

[palmop]

All the MDA IIs I have seen so far (we have 5 from different sources) are not write protected for Ext ROM.

Also I have couple of friends who have I-Mate and O2 XDA II (UK), they are not write protected either. Wonder which providers lock it up.

For those of you who see it as locked, have you tried to write onto it via Total Commander 6.0, it has a Windows CE plugin you can download and you'll see the CE device like a drive. Maybe that'll help.

[kalex]

palmop,

tried total commander, same result. read only can't delete. looks like its locked on ExtROM 1.03.20



alex

[King]

Well, mine's locked as well, and I'm using 1.60 :(

What now then? What happens when the update comes out? can I flash it again?

[palmop]

Did you try to change the File Attributes, they are read only by default and you cannot overwrite them, but Total Commander can change the attributes.

[kalex]

yep. tried it. its doesn't do anything. it has a file attribute of ROM
killerchung's method should work and i'll try it later today or tommrow

[mgolanlan]

anybody else notice these?

1. "running programs" program is no longer in "programs"
2. the GPRS duration is now displayed in the phone popup
3. the programs on the "start menu" don't show up in "programs"
4. changing the "start menu" require soft-reset before it is updated
5. the Games have a link to a non-existing game ...
6. actually need soft-resets more often than before (for me)
7. the Bluetooth icon on the bottom is gone!


All in all, this is yet another version that didn't have enough QA.
State of the art hardware, state of piss software.

Welcome to the Micro$oft experience.
What would you like to reinstall today?

[ming]

anybody else notice these?

1. "running programs" program is no longer in "programs"
2. the GPRS duration is now displayed in the phone popup
3. the programs on the "start menu" don't show up in "programs"
4. changing the "start menu" require soft-reset before it is updated
5. the Games have a link to a non-existing game ...
6. actually need soft-resets more often than before (for me)
7. the Bluetooth icon on the bottom is gone!


All in all, this is yet another version that didn't have enough QA.
State of the art hardware, state of piss software.

Welcome to the Micro$oft experience.
What would you like to reinstall today?

that's werid
did not encounter this in my case .
did anyone else face this problems

[palmop]

1. Some apps have been removed, including running programs, ussd, bpinsert, etc. Most of the functionality is still there, they are mostly converted into dlls.
2. Haven't seen that
3. What do you mean by that?
4. Not for me.
5. Not for me, maybe you didn't do a hard reset after upgrade?
6. So far much less resets.
7. I have the icon.

It sounds like your device might have the issue. I am using MDA II from Germany.

On a side note, it seems like the device turns itself on more ofter for no reason these days, I pick up the device from my belt, open the cover to find out it has been turned on. Weird, the button lock is in place. I thought it was the Piel Frama case, but it happens with the original case as well.

[akira]

what do you think about this one, :idea:

my home made carkit has 1 connector
wich charged the pda, has a USB cable ready, has the serial connection to my GPS and audio is going into my car stereo, and a externa mic ampliefier, pin 19 has been grounded so audio would only come out through the connector

all functions worked :lol:

now i updated the mda2 with the rom, and audio isnt going trough the connector anymore, it now just goes through its own speaker :evil:

gonna test the lines to see if they are broken, but that would be rather impossible..

been working on that car kit for 3 weeks and now it would just give another problem ! aaaargh

[jpiek]

what do you think about this one, :idea:

my home made carkit has 1 connector
wich charged the pda, has a USB cable ready, has the serial connection to my GPS and audio is going into my car stereo, and a externa mic ampliefier, pin 19 has been grounded so audio would only come out through the connector



Nice, i want that for my MDA II too :)
Did you connect a external Mic too ? How did you do that ?
Because the internal mic. no longer works if you ground Pin_19 afaik, you don't have a mic. for useing the phone....

[LanceM]

I upgraded to 4.01.00 a week ago and have only noticed a couple of issues..

The volume is lower even on speakerphone than it was before.

Call log now pulls up the dial menu, but you can click on call history from there to access the old call log.

Im struggling with memory to get some games running.. Most need like 10 megs free and Im lucky to have that without having to reboot the device first...

With those problems listed, I still LOVE the upgrade and would never consider going back...

[akira]

jpiek,
i bought a simple mono sound aplifier build it yourself kit
like 10 dolars i think
then power it up
connect the proper wires
and i use a nokia carkit mic as a mic

[jpiek]

jpiek,
i bought a simple mono sound aplifier build it yourself kit
like 10 dolars i think
then power it up
connect the proper wires
and i use a nokia carkit mic as a mic

No additions to the mic, like amplification ? Just one-on-one ?

[mgolanlan]

a follow up to my own post:

1. didn't anyone else notice the GPRS TIMEING is now displayed
if you click on the phone-level (popup to turn phone off etc)
this is nice!

2. I've no idea why the games error showed up,
program->games has "Icon" - click it ->
error mesg: "ceshell.dll,-52 cannot find"
this isnt a real issue

3. my BT is working fine, but the BT ICON (bottom right disappeared!
can someone tell me how to get it back?
did i delete something from the windows\startup ?

[jpiek]

You could but BTicon.lmk back in the \windows\startup but why should you ? It takes another process from the max. of 32...

btw, i still use the org. ROm, and removed BTicon. After a fresh reboot i have only 23 processes now :D

[smartphone4u]

You can use the extended rom viewer cab from ppcw.net, it is easier ;). ...Extended ROM Switch (http://www.smartphone4u.de/xda2/grundlagen/extended_rom.html) is more comfortable ;)

[palmop]

With the new rom, i still have bt icon,but it is not in startup

[King]

You can use the extended rom viewer cab from ppcw.net, it is easier ;). ...Extended ROM Switch (http://www.smartphone4u.de/xda2/grundlagen/extended_rom.html) is more comfortable ;)

It's in German. What the hell does it do?

[smartphone4u]

Extended ROM Switch (http://www.smartphone4u.de/xda2/grundlagen/extended_rom.html) is more comfortable ;)

It's in German. What the hell does it do?If those looks at shreenshots, then you can recognize it easily - the program is in English. The program recognizes whether the Extended ROM it is visible or not and switches if necessary into the other mode.

[alkandery75]

Well, mine's locked as well, and I'm using 1.60 :(

What now then? What happens when the update comes out? can I flash it again?

Any clue yet ? ! :cry:

[mgolanlan]

but how the ?#%^#%&*?%^ do you know the number of
processes running on the system?

I've been looking for a 3rd party "task manager"
that really shows all proceses, memory usage, etc ... but found none.

I've NO bticon.* in my system ... where do you have it located (in 1.60)?

The reason I want it is to quickly turn bt on/off ...
I hate menu->setting->connection->bluetooth...

[jpiek]

but how the ?#%^#%&*?%^ do you know the number of
processes running on the system?


PHM Taskmanager (windows alike)


I've NO bticon.* in my system ... where do you have it located (in 1.60)?

The reason I want it is to quickly turn bt on/off ...
I hate menu->setting->connection->bluetooth...

I still use ROM 1.03 :roll: I see no need for a onofficial update...

[rpc]

Can anyone Please send me the link where I can download the T-mobile 1.6 Update, thanks in advance


but how the ?#%^#%&*?%^ do you know the number of
processes running on the system?


PHM Taskmanager (windows alike)


I've NO bticon.* in my system ... where do you have it located (in 1.60)?

The reason I want it is to quickly turn bt on/off ...
I hate menu->setting->connection->bluetooth...

I still use ROM 1.03 :roll: I see no need for a onofficial update...

[apatrick]

has anyone noticed if the calculator app is now the proper 2002/2003 version or if it is still the clunky old one?

[joparp]

has anyone noticed if the calculator app is now the proper 2002/2003 version or if it is still the clunky old one?

With this Rom 1.60, the calculator is still the old one.

[Tuningszocske]

Hi all!

I have a question here. The bluetooth option in the new 1.60ROM is now avaliable for COM4 and COM5.
But my problem is the TomTomGPS utility doesn't know the port COM5 just COM1,2,6,9 + infrared + serial on USB.

So, any idea how can I use my BluetoothGPS with TomTom?
(It works with other GPS-prog with COM5)

thx

[boldi]

I tried the T-Mobile 1.60 rom on my O2 xda2.
It works perfectly with my xda2.

However, I found some interest thing on the new rom upgrade process
1. It seems XDA2 (or HTC Himalaya) use one single program for RAIDO / Extended Rom / OS Rom update. It seems Radio upgrade failure may no longer case device failure, because the RADIO upgrade process is same as OS upgrade process, and not required to copy the whole software into the RAM to upgrade.


2. Sinces some of us (and my XDA2) report that the exteneded rom is READ ONLY, but the upgrade program can update the extended rom. That means the Exteneded rom is not REALLY read only, but somewhere locked it. More funny is , it is seems the Main OS rom is not controlling the exteneded rom is locked or not, because after I updated the extended rom, it is still locked.

3. If O2 XDA2 can use T-Mobile MDA2 update, it seems the upgrade software no longer check the header of the device (At lease this version won't). I think we can use it to change device's language. However I don't know how to dump the rom in .nbf format, is that possible to convert the nb1 format to nbf format?

Thanks.

i lost my rom by put the xda 1 rom in the new xda2 that i have. can you mail to my the link to get the new rom and to run it on my fhone .is daed


thanks.s.o.s
roni@dagil.co.il

[goodman]

:lol:
there is an OFFICIAL UPGRADE ready and existing, but not yet PUBLIC,
it is one nice 40 MB RUU file which will uprgade your unit to english language:

Microsoft Pocket PC version 4.20.0 (Build 13252)
ROM version: 1.60.00WWE
ROM date: 12/03/03
Radio version: 1.06.01
Protocol version: 1337.16
ExtROM version: 1.60.06
Indirizzo http://xda-developers.com/incoming/rom160wwe/RUU16006WWE_T-mobile_NL.exe

IT'S FANTASTIC AND EASY BY THE USB CRADLE

[palmop]

And fyi, T-Mobile DE has already released official 1.60 upgrade...

[Rajaik]

Can i update to the new NL Rom using just my O2 supplied USB craddle? do i need sd card and stuff ?

[sonadt]

Can i update to the new NL Rom using just my O2 supplied USB craddle?
Absolutely you can. Do not install extended ROM automatically, try to install some needed applications only.

[thariman]

Just to be aware that by upgrading your XDA II/MDA II/Imate/Qtek you may not be able to upgrade to other none T-Mobile Rom. You will get contry ID error.

But if you already stuck like me, and have a read only Extended_ROM here is a modified version of ms_.nbf that don't have the T-Mobile customization but restore the O2 Asian customization.

This is the config.txt
EXEC:\Extended_ROM\TPDisable.exe
CAB: \Extended_ROM\CameraRC131_WWE_1.5.sa.CAB
CAB: \Extended_ROM\MIDI56.sa.CAB
CAB: \Extended_ROM\CallerIDRC11_WWE_1.5.sa.CAB
CAB: \Extended_ROM\MMS1507_WWE.sa.CAB
CAB: \Extended_ROM\GPRSMonitor_WWE.sa.CAB
CAB: \Extended_ROM\ClearVue_WWE.sa.CAB
CAB: \Extended_ROM\TMCOMREG.sa.CAB
CAB: \Extended_ROM\Version_AKU1.sa.CAB
CAB: \Extended_ROM\OEM_AKU1_WWE_4AP.sa.CAB
CAB: \Extended_ROM\OEM_WWE_03120301.sa.CAB
CAB: \Extended_ROM\VideoMMS.sa.CAB
CAB: \Extended_ROM\Broadcast_WWE.sa.CAB
CAB: \Extended_ROM\TM_phone_class10.CAB
CAB: \Extended_ROM\O2.CAB
CAB: \Extended_ROM\Extended_ROM_viewer.CAB
EXEC:\Extended_ROM\TPEnable.exe
RST: Reset

I added all the O2 Asian version autoconfig (for GPRS/MMS)
and the Extended_ROM_viewer to unhide the extended_ROM directory

To install you need to download this file:
http://xda-developers.com/incoming/rom160wwe/RUU16006WWE_T-mobile_NL.exe
extract the file to a directory using winzip or similar tools

You will find
HimaClearJumpCode.exe
HimaGetDeviceData.exe
HimaUpgradeUt.exe
ms_.nbf
NK.nbf
Radio_.nbf

Replace the ms_.nbf with my ms_.nbf

If you only want to replace the Extended_ROM (already upgrade to 1.60 NL) delete NK.nbf and Radio_.nbf

Run HimaUpgradeUt.exe

I test it on my own O2 XDA II several times and it work great. Make sure you backup your data before the upgrade. For more info on how to update the ms_.nbf http://www.xs4all.nl/~itsme/projects/xda/xdaii-update-format.html

[cshields1]

I will be receiving a new iMate XDA II soon & selling my XDA I. I've been following the XDA II ROM upgrade topics for sometime now.

Is the iMate ROM/RS upgrade the same as the T-Mobile 1.60 WWE upgrade? for USA iMate XDA II users?

I'm in Texas, USA using TMO with my XDA I and want to make sure what correctly to do when I receive my iMate XDA II.

[kruel]

Thariman,

Thanks for the file and the installation instructions. I upgraded my Extended ROM with your 'cooked' ROM and it works great! No more T-Mobile stuff on my XDA II...

Cheers,

Kruel

[rpc]

Just to be aware that by upgrading your XDA II/MDA II/Imate/Qtek you may not be able to upgrade to other none T-Mobile Rom. You will get contry ID error.

But if you already stuck like me, and have a read only Extended_ROM here is a modified version of ms_.nbf that don't have the T-Mobile customization but restore the O2 Asian customization.

This is the config.txt
EXEC:\Extended_ROM\TPDisable.exe
CAB: \Extended_ROM\CameraRC131_WWE_1.5.sa.CAB
CAB: \Extended_ROM\MIDI56.sa.CAB
CAB: \Extended_ROM\CallerIDRC11_WWE_1.5.sa.CAB
CAB: \Extended_ROM\MMS1507_WWE.sa.CAB
CAB: \Extended_ROM\GPRSMonitor_WWE.sa.CAB
CAB: \Extended_ROM\ClearVue_WWE.sa.CAB
CAB: \Extended_ROM\TMCOMREG.sa.CAB
CAB: \Extended_ROM\Version_AKU1.sa.CAB
CAB: \Extended_ROM\OEM_AKU1_WWE_4AP.sa.CAB
CAB: \Extended_ROM\OEM_WWE_03120301.sa.CAB
CAB: \Extended_ROM\VideoMMS.sa.CAB
CAB: \Extended_ROM\Broadcast_WWE.sa.CAB
CAB: \Extended_ROM\TM_phone_class10.CAB
CAB: \Extended_ROM\O2.CAB
CAB: \Extended_ROM\Extended_ROM_viewer.CAB
EXEC:\Extended_ROM\TPEnable.exe
RST: Reset

I added all the O2 Asian version autoconfig (for GPRS/MMS)
and the Extended_ROM_viewer to unhide the extended_ROM directory

To install you need to download this file:
http://xda-developers.com/incoming/rom160wwe/RUU16006WWE_T-mobile_NL.exe
extract the file to a directory using winzip or similar tools

You will find
HimaClearJumpCode.exe
HimaGetDeviceData.exe
HimaUpgradeUt.exe
ms_.nbf
NK.nbf
Radio_.nbf

Replace the ms_.nbf with my ms_.nbf

If you only want to replace the Extended_ROM (already upgrade to 1.60 NL) delete NK.nbf and Radio_.nbf

Run HimaUpgradeUt.exe

I test it on my own O2 XDA II several times and it work great. Make sure you backup your data before the upgrade. For more info on how to update the ms_.nbf http://www.xs4all.nl/~itsme/projects/xda/xdaii-update-format.html

What kind of tools you use to create ms_.nbf, I edited the ms_nbf, so it will be compatible to any update http://forum.xda-developers.com/viewtopic.php?t=4785
:roll:

[firecat168]

Hi Thariman,

Thanks for the MS_ file. I am from Hong Kong, and I want to know if your Asian ROM has profile for GSM provider "Sunday".

In my XDA2, I can see the name of your GSM provider, so I assume your MS_.NBF is good for me too.

Many Thanks!

[thariman]

Hi Thariman,

Thanks for the MS_ file. I am from Hong Kong, and I want to know if your Asian ROM has profile for GSM provider "Sunday".

In my XDA2, I can see the name of your GSM provider, so I assume your MS_.NBF is good for me too.

Many Thanks!
Here are all the provider that is included in the O2 Asia autoconfig
1O1O AIS Celcom
DiGi DTAC IM3
M1 Maxis One2Free
Orange Hong Kong
Satelindo SingTel
SmarTone StarHub
Sunday Telkomsel

[thariman]

For more info on how to update the ms_.nbf http://www.xs4all.nl/~itsme/projects/xda/xdaii-update-format.html

What kind of tools you use to create ms_.nbf, I edited the ms_nbf, so it will be compatible to any update http://forum.xda-developers.com/viewtopic.php?t=4785
:roll:

You need to put the ms_.nbf under a linux os via network or put it on a share partition if you dual boot your machine.

Then you need to create a mount point

mkdir /mnt/loop0

and mount the file with this command

mount -o loop,offset=0x70040 -t vfat ms_.nbf /mnt/loop0

Then you can edit the content of ms_.nbf under the /mnt/loop0 directory

After you finish with the edit just unmount it

umount /mnt/loop0

then you can copy back the ms_.nbf file back to your windows os.

@Home I don't have a linux box handy, the easiest way is
to boot your machine with knoppix live linux which you can get from http://www.knoppix.net/

[Chan]

Wow! it's really work, I can see them all with linux box.

Thank you so much, I've been looking for them.:D

[Terence]

I have follow the instruction and work scussed and one one problem is the ringintone go difrent, the sounds is not as the original, why? any solution?

[thariman]

I have follow the instruction and work scussed and one one problem is the ringintone go difrent, the sounds is not as the original, why? any solution?

Can you describe in more detail by ringtone go different ?
For sure the TMobile ringtone is not there only the O2 is.

[Terence]

The rigington sound is too high, and sound like clicki, not as the original sound is very smooth, I have try to use the Midi.cab it look very good, but when hard reset the auto cong will installback the Midi156.cab is that any possible you can put the midi.cab rather the midi156.cab. if you test you will feel the diffrent. the sound very smooth and nice.

[Chan]

The rigington sound is too high, and sound like clicki, not as the original sound is very smooth, I have try to use the Midi.cab it look very good, but when hard reset the auto cong will installback the Midi156.cab is that any possible you can put the midi.cab rather the midi156.cab. if you test you will feel the diffrent. the sound very smooth and nice.

Do you mean replace MIDI56.sa.CAB with MIDI.sa.CAB and change in config.txt also? If so, please check PM. I've modified them for you already, but I did not upgrade my Xda II yet.

see in them side:

http://www.cethai.com/neko/wm2003romeditor.jpg

You can use WM2003 Rom Editor from http://forum.xda-developers.com/viewtopic.php?t=5514 to see the contents. or modified by on your own.

But that extended rom I use my linux to modify them. :D

[Terence]

Thank, I also use the rom editor to modify as the same you send, but the tone still the same, but I have modify all the ext rom with the original ship only the tone go well and great. Anyhow thank you.