Impossible error in TMobile 1.60.36 upgrade

[nargalzius]

I found ALMOST everything i needed to know in this single thread:
http://forum.xda-developers.com/viewtopic.php?t=6694

As far as prepping the files are concerned, there's no problem . . . but flashing it is where my problem started (or wouldnt start rather).

I followed the forum, and got the announced T-Mobile ROM upgrade in the above thread, and extracted the files.

I then decrypted them using xda2nbftool. I actually used the batch scripts (which were all over the thread), that's where I found out about the decryption / modification / reencryption etc. etc. of the nbfs.

Everything was going smoothly, until I got that blasted COUNTRY ERROR thingie. And what's worse is no matter what "countryID" I put, it still gets the error. I viewed the different threads posted about the country error thing, but I dont think I have the same problem. For example, they say you can fix the country error by matching it to the CountryID of your unit (or proabably current flashed ROM) using xda2nbftool. So the syntax looks something like this:

xda2nbftool -so <ID> -v ms.nba
xda2nbftool -so <ID> -v Radio.nba
xda2nbftool -so <ID> -v nk.nba

for an O2 is probably

xda2nbftool -so O2 -v ms.nba
xda2nbftool -so O2 -v Radio.nba
xda2nbftool -so O2 -v nk.nba

Usually it just rotates between, TMOBILE, QTEK, O2, O2ASIA, etc. etc. as mentioned in the other thread (the nbfs of the official upgrade obviously start as TMOBILEs)

I've tried redoing the whole process with all these different codes (by modifying the bat files and trying out the bat files posted, but the damn error is still there.

Finally was able to spot a post about DeviceData.txt. And upon opening it, this is what I saw:

U S B 3 2 1 . 5 2 . 0 0 W W E P H 1 0 O 2 A S I A W W E 1 . 5 2 . 8 2 1 . 0 5 . 1 4


Obviously, the ID should be O2ASIA right? But i've already tried O2ASIA and I still get the country error. I wonder why it wont work. last thing I suspect would be the PH10, cuz i checked my unit via device information and it was listed as "PH10B" (but the DeviceData.txt says PH10 only)

Basically that's my dilemma. . . as far as modifying the extrom etc. etc. I seem to be getting it already, only thing to do is figure out how to make the flashing WORK.

That's it for now i guess. Hope someone can help me out

[Jos]

For an O2ASIA, you should use O2 and not O2ASIA.

Grtz,

Jos

[nargalzius]

OH ic, i could've sworn it didnt work with O2

it seems to accept it no :)

so last question i guess would be as of today, is this the newest rom upgrade available? (aside from SE) or should i wait for that

and lastly i should have no problems with a Himalaya regarding the radio right since it's a triband phone (so it should still work with my carrier)

[pochreyes]

nargalzuis, I recently upgraded to the latest t-mobile rom and it works fine...

[Jos]

so last question i guess would be as of today, is this the newest rom upgrade available? (aside from SE) or should i wait for that

and lastly i should have no problems with a Himalaya regarding the radio right since it's a triband phone (so it should still work with my carrier)

It's the last update, should work with any provider.

Grtz,

Jos

[nargalzius]

Ey guys,

Thx for all your help. I've successfully upgraded the ROM (even with a modified ExtROM) :D

A few problems I just ran into that i should share with you to hear your comments about them.

When I first flashed, everything went well and I noticed that I cooked the ExtROM not quite the way I wanted (some orphan cabs i had no intention of using ever), so I wanted to reflash a corrected version.

What I did was like was said in the forums (to just leave ms_.nbf, so it'll flash only that) and ran himaupgrade . . . the dialog was fine, it confirmed the ID, etc. etc. (which was strange since the nbf was set to O2 (but after flashing I believe it would be a TMOBILE now (as i confirmed when checking the DeviceData.txt)

Question there is: is the whole changing of operators merely a spoof trick? or does it really change the countryID?

I ask this since the upgrade started, but when it resetted to bootloader to flash, it got the id error again . . . which rendered my device dead.

I was thrashing for a bout an hour, when I tried to use an old o2asia rom, which failed at 10% . . . BUT allowed me to reflash the TMOBILE upgrade (but the works, meaning the OS, ExtROM and Radio)

took a pretty long time . . . but at least now everythig is fine now . . . and I corrected the ExtROM before I tried flashing everything.

Next question is the splash screen . . . I WASNT able to change it to the O2 screen i wanted, BUT i included a cab there in the ExtROM which had the splash screens . . . my question is, whenever the cab puts the new splash1 and 2 .nb files in the unit, will that erase the previous splash screens forever more EVEN after a hard reset?

Cuz if it does then I probably dont have to reflash the ExtROM since i have an O2 splash screen now (and based on the problem I had earlier, I think I dont want to try it again), but that is only confirmed for soft resets. I want to confirm that if i HARD RESET will it still be O2?

Lastly, cam you use folders in the ExtROM? Just to be organized, I was wondering that my "custom" CABS which I didnt set to install automatically be grouped in an orderly fashion.

that's about it for now :wink:

Cheers,
Carlo

[ahiemstra]

When I first flashed, everything went well and I noticed that I cooked the ExtROM not quite the way I wanted (some orphan cabs i had no intention of using ever), so I wanted to reflash a corrected version.

What I did was like was said in the forums (to just leave ms_.nbf, so it'll flash only that) and ran himaupgrade . . . the dialog was fine, it confirmed the ID, etc. etc. (which was strange since the nbf was set to O2 (but after flashing I believe it would be a TMOBILE now (as i confirmed when checking the DeviceData.txt)

...
Cheers,
Carlo

I had the same thing. I used xda2nbftool.exe -so O2 but the second time I flashed I could not use the same nbfs anymore. I had to change to -so TMOBILE, which was also reported by DeviceData.txt (although I used O2!).

Problem I have now is that my radio is dead. I will not log into EPLUS who is my provider. I get endless searching with "..." running to the right of my antenna sign.

HELP: What is needed to get the radio connected again? :cry:

ROM 1.60.00WWE
Radio 1.10.00
DeviceData.txt has "T M O B I L E" in it
My provider is EPLUS.

[ahiemstra]

Just figured out that the trick with the provider is just to make the update work. So for the first time you have to make the flasher believe it is actually a O2 patch, because you have O2 on your system at that point in time.

After the first flash you should be fine with TMobile all along.

Still tracing down the Radio error. It is a file in the O2 extended ROM which causes this. And I figure it sits in "OEM_WWE.sa.CAB"...

[ahiemstra]

What I did was applying the original O2 extended ROM files on top of the TMobile 2003 update. That was a bad idea.

Next thing I did was take the entire TMobile update and left out some CABs that do the customizations (like the ugly pink phone). This is a list with CABs I used for the extended ROM:

AutoRun.exe
Broadcast_WWE.sa.CAB
CallerIDRC11_WWE_1.5.sa.CAB
CameraRC131_WWE_1.5.sa.CAB
ClearVue_WWE.sa.CAB
Config.txt
Extended_ROM_viewer.CAB
GPRSMonitor_WWE.sa.CAB
MIDI56.sa.CAB
MMS1507_WWE.sa.CAB
OEM_AKU1_WWE_4AP.sa.CAB
OEM_WWE_03120301.sa.CAB
TPDisable.exe
TPEnable.exe
Version_AKU1.sa.CAB
VideoMMS.sa.CAB

Radio worked fine after that.