Database Info

Upgrading to Radio 1.13

I'm trying to upgrade my spv m500 to 1,13 radio that I danloaded from ftp and there is model ID error.
How can I upgrade and avoid Model ID error????
Thanks

Are you sure the 1.13 radio is for Magician? I thought it was for BlueAngel

findus said:
Are you sure the 1.13 radio is for Magician? I thought it was for BlueAngel
Click to expand...
Click to collapse
Yes, it's for Magician. I installed my version months ago, works perfect! I got no errors at all, just installed.
Sure you got the right version? I used a WWE version.

Yes, I danloaded from Magician ftp only radio 1.13 and one with maupgrade as well and still model ID error

I have the same problem

Is there anyone to help and explain step by step how to upgrade with 1.13 radio in Magician.
Thanks

Does this v1.13 solve the known 'GPRS cannot re-connect' issue?

I need 2.

?? help neone?

does it work for O2 XDA Mini????
If it does, i would like to give it a try...been going after this thread for months to get the solution but no go....

Anyone can help how to update the radio without 'Model ID Error'?
I have upgraded mine to NL_11300_131_11200, but I cannot upgrade the radio as rilazi encountered.

If you have a problem with the ID error, use the attached file instead of MaUpgradeUt. The one you need to use is MaUpgradeUt_NoId, not the one included in the original zip file.

I'm afraid that the MaUpgradeUt_NoId only works for the OS-upgrade, not for the Radio-upgrade (or is it just me?)...
I get this message: MaUpgradeUt_NoId.exe: This application has failed to start because RUU.dll was not found. Re-installing the application may fix this problem.
I also tried adding
[CHECKCEID_TYPE]=1
to the HTCRUU.conf file (like we do in the RUU.conf file during a OS-upgrade) but with no success.
Any suggestions?

It worked for me after I upgraded to T-Mob 1.13 ROM. Don't know why it's not working on yours. Did you download the Radio from ftp?

Kirky9 said:
I'm afraid that the MaUpgradeUt_NoId only works for the OS-upgrade, not for the Radio-upgrade (or is it just me?)...
I get this message: MaUpgradeUt_NoId.exe: This application has failed to start because RUU.dll was not found. Re-installing the application may fix this problem.
I also tried adding
[CHECKCEID_TYPE]=1
to the HTCRUU.conf file (like we do in the RUU.conf file during a OS-upgrade) but with no success.
Any suggestions?
Click to expand...
Click to collapse
I have same problems.

Here is the way step by step:
1. Dawnload previous MaUpgradeUt_noID in this page
2. Dawnload MagicianRadio_1.13.00_maupgrade from ftp
3. Unzip MagicianRadio_1.13.00_maupgrade and paste there MaUpgradeUt_noID
4. When you unzip MagicianRadio_1.13.00_maupgrade you will get several files including HTCRUU.dll and rename this file to only RUU.dll
5. Run MaUpgradeUt_noID first and you will get Model ID error
6. Run for the second time you will Update Radio
Cheers,

This is what I used ...

rilazi said:
Here is the way step by step:
1. Dawnload previous MaUpgradeUt_noID in this page
2. Dawnload MagicianRadio_1.13.00_maupgrade from ftp
3. Unzip MagicianRadio_1.13.00_maupgrade and paste there MaUpgradeUt_noID
4. When you unzip MagicianRadio_1.13.00_maupgrade you will get several files including HTCRUU.dll and rename this file to only RUU.dll
5. Run MaUpgradeUt_noID first and you will get Model ID error
6. Run for the second time you will Update Radio
Cheers,
Click to expand...
Click to collapse
Thnks.
It's works.
Kind regards

And...... Is it worth it?

rilazi said:
Here is the way step by step:
1. Dawnload previous MaUpgradeUt_noID in this page
2. Dawnload MagicianRadio_1.13.00_maupgrade from ftp
3. Unzip MagicianRadio_1.13.00_maupgrade and paste there MaUpgradeUt_noID
4. When you unzip MagicianRadio_1.13.00_maupgrade you will get several files including HTCRUU.dll and rename this file to only RUU.dll
5. Run MaUpgradeUt_noID first and you will get Model ID error
6. Run for the second time you will Update Radio
Cheers,
Click to expand...
Click to collapse
It didn't work for me... The second time I run MaUpgradeUt_noID, I get the screen saying the update will take +/- 20 minutes with the progress bar, but ... no progress. The Magician indicates that the radio ugrade is in progress, but after a while I get a message on my PC saying that an error has occured, and I should try again...

Upg to 1.13 WWE ROM (with 1.13 Radio) in 10 easy steps!

I just finished upgrading from Qtek 1.11 WWE Big Storage ROM to T-Mob 1.13 WWE Big Storage (with 1.13 Radio). Since the information available on the forum is spread over many threads, I thought I would amalgamate everything here ...
NB: ampda_How_To_PPC_Upgrades_V1.pdf (attached) tells you how to use ALL the tools I mention ... thanks to ampda for this useful write-up!
Before you start:
a) Take full backup of your PPC on SD using Sprite Backup or any other 3rd party app.
b) Take copy of SD on PC
Now for the ROM upgrade ...
1. Take backup of existing ROM (mine was BigStorage 1.11) on SD using romupdate.exe (attached) - Sec. 4 in PDF
2. Convert ROM (now on SD after step 1) to PC using ntrw ver2.0 (attached) - Sec. 5in PDF
3. Install 1.13 T-Mob NL WWE ROM (from ftp ... ftp://xda:[email protected]/Magician/Shipped_ROMS/NL_11300_131_11200.exe) using MaUpgradeUt_noID (attached)
4. Follow on-screen instructions and reset device just before installing customisations (to make extended ROM accessible)
5. Copy Extended ROM to PC (for later use) using Windows Explorer
6. Install 1.13 Radio using MagicianRadio_1.13.00.zip from FTP (attached).
This will hard rerset again so make sure you press the reset before T-Mob customisation starts.
7. Repeat steps 3 and 4 to create an nb1 file of your new 1.13 ROM on PC
8. Open your new nb1 file with a Hex editor (download the latest FREE version from http://www.hhdsoftware.com/hexeditor.html), locate the 02 00 00 80 00 20 and change 80 00 to b8 01 (at 3 locations in this version of ROM - not just 2)
9. Transfer your new ROM to SD card using ntrw ver 2.0 - Step 7 in PDF
10. Dump your new Big Storage ROM onto your Magician - Step 8 in PDF
You will note that after step 10 your Magician will take a VEEEERY LONG time to boot the first time. This is normal.
Install any required Extended ROM programs from the folder created in step 5 above. To install these CAB files just copy them anywhere on your PPC and click once to install.
Enjoy!

tnx I'm going too try this!

It has been several months since I last visited this forum. I am wondering, why do we need to install the 1.13 Radio using MagicianRadio_1.13.00.zip in step 6?
I thought the 1.13 T-Mob NL WWE ROM should already have the 1.13 Radio... or is it unstable?
Thanks.

programatix said:
It has been several months since I last visited this forum. I am wondering, why do we need to install the 1.13 Radio using MagicianRadio_1.13.00.zip in step 6?
I thought the 1.13 T-Mob NL WWE ROM should already have the 1.13 Radio... or is it unstable?
Thanks.
Click to expand...
Click to collapse
Nope, it has radio 1.12 (don't know why, radio version 1.13 is out for many months now...)

KoBolD said:
tnx I'm going too try this!
Click to expand...
Click to collapse
Tell us how it goes :wink:

pietrucci said:
Nope, it has radio 1.12 (don't know why, radio version 1.13 is out for many months now...)
Click to expand...
Click to collapse
Ok, thanks for the answer. Actually I'm already using radio 1.13 for months already. Now I'm wondering about the changes from rom 1.12 to 1.13... any idea? Does the Pocket IE (with SBP Plus installed) works correctly when mutiple windows are opened?
Thanks again.

i cannot convert ROM to PC using ntrw.exe
i hav follow the instruction by ampda_how_to_PPC_Upgrades_V1.pdf,
and i hav in section 5. i cannot convert the ROM to PC.
its appear:
c:\>ntrw read myrom.nb1 l:
usage: ntrw file drive:
can anyone helps me???
urgenttttt.....

it seems easier just to decode nbf, make bigstorage patch,
change header to what's in DeviceData.txt
and then encode and flash using ROMUpgradeUt
All steps:
1. run NL_11300_131_11200.exe - this will
2. unpack files to temp - copy them ! and
3. write DeviceData.txt to \Windows - copy this one too and view with notepad
4. decode nk.nbf -> nk.nb1
5. hexedit header to correct ID from DeviceData.txt and
6. replace pattern for bigstorage in hexeditor
7. encode nk.nb1->nk.nbf
8. run ROMUpgradeUt.exe to upgrade CE image
also, this way you will save the contents of increased \Storage folder if previous rom was bigstorage one
Attach: src+bin of enc/dec utility for nbf format used in ROMUpgradeUt.exe ver. 3.0.1.0
bin is in the Release folder
Usage sample (must be run from the same folder as nbf files or specify full path):
nbfdec -d nk.nbf nk.nb1
nbfdec -e nk.nb1 nk.nbf

kta said:
NB: ampda_How_To_PPC_Upgrades_V1.pdf (attached) tells you how to use ALL the tools I mention ... thanks to ampda for this useful write-up!
Click to expand...
Click to collapse
Thanks for the thanks much appreciated

Re: it seems easier just to decode nbf, make bigstorage patc
hlt said:
it seems easier just to decode nbf, make bigstorage patch
Click to expand...
Click to collapse
Hi hlt,
I tried your description and all I can say is: IT WORKS! And in my humble opinion this is the easiest method for BigStorage. I've some extra info in your steps, the parts where I had questions, for others to profit.
All steps:
1. unzip NL_11300_131_11200.exe (or any other shipped rom)
2. copy the getdevicedata.exe to your magician and execute to write DeviceData.txt to \Windows and view with notepad
4. decode nk.nbf -> nk.nb1
5. hexedit header to correct ID from DeviceData.txt (probably only if using a rom from other provider)
6. replace pattern for bigstorage in hexeditor
7. encode nk.nb1->nk.nbf
8. run ROMUpgradeUt.exe to upgrade CE image
also, this way you will save the contents of increased \Storage folder if previous rom was bigstorage one
Usage sample (must be run from the same folder as nbf files or specify full path):
nbfdec -d nk.nbf nk.nb1
nbfdec -e nk.nb1 nk.nbf
Thanks a lott for this wonderful piece of code,
M

Thanks Alot, your guide has allowed me to upgrade from a very early rom to this new one which makes my mdac so much faster! i recommend this upgrade route to everyone!
thanks again
R

thanxxxxxxxxxxxxx

Hi I have a question. Its been months also since I visited thise site and I didnt know there is already a new ROM for the XDA-Mini. My Rom version is 1.11.00 WWE and I did the Big Storage trick before so I dont have the ExtRom now.
If I upgrade to this new ROM versions, will I get a ExtROM back again or I still have the Big Storage?
thanks so much...

You will get the EXTROM back. The removal of EXTROM has to be done for every ROM you install, hence steps 8 to 10 above

I guess there will always be a chance of things going wrong, but as you don't forget to locate the 02 00 00 80 00 20 and change 80 00 to b8 01 in your decoded nk.nb1 and use the re-encoded nk.nbf in the upgrade you'll have BigStorage. I did it with a crippled magician, I lost all my storage with a BigStorage attempt, and it gave me back a 26.72MB storage. Now I'm moving a lot of files over to storage, so far all my 'program files' are there and large ones like album and camera. After moving some registry and shortcut changes are needed, but it works. Now got 8Mb in main memory stored and this is with a complete ext-rom installed (manually), MMS, Blackberry and Caller Id are quite large and will be gone this week after a planned hard-reset. First I need to figure out some more files to move. Keep in mind that programs from storage are starting slower than from main memory, especially when you move over the 'program files' and dll's as well.
Good luck, M

kta said:
You will get the EXTROM back. The removal of EXTROM has to be done for every ROM you install, hence steps 8 to 10 above
Click to expand...
Click to collapse
thanks, kta for the info.
I'm itching to give it a try now. But wait....is the ROm upgrade v1.13 that you guys are talking about here, applicable to all kinds of XDA-Mini? I mean I am using the O2 XDA-Mini purchased here in the Philippines. Its asian version but its "english".
Because I remember the last upgrade I did which procedure I got from here also...I got the upgrade procedure from a thread specified for XDA Asian version. This time, I couldnt see a thread for Asian XDA specifically....instead I see there's a common thread for all. But its a T-mobile rom, isnt it? Am I in the right thread?
thanks....

Hello dinoalbert,
This is a WWE rom, haven't found an asian 1.13 on the ftp. There's only one asian rom there: o2asia_11100_922_11100_ship.exe, don't know which rom you have currently so maybe you can use it. I guess the trick with exchanging radio's and the BS trick will work, won't know why not.
Gr. M

dinoalbert said:
thanks, kta for the info.
I'm itching to give it a try now. But wait....is the ROm upgrade v1.13 that you guys are talking about here, applicable to all kinds of XDA-Mini? thanks....
Click to expand...
Click to collapse
Yes, this ROM is good for all variants of the HTC Magician, except the 850MHz radio version. You would need a different RADIO for that.

KTA,
Do you know the difference between the 1.12 radio and the 1.13 version? Also the 1.12 in the shipped rom has a newer file-date than the 1.13 one, or is t-mob on a different number scheme?
Thanks,
M

@oltp
yup thats the one that I have now...ma_o2asia_11100_922_11100_ship......thats the last ROM upgrade I did which I also got it from here last May or June I think. But that seem to be along time ago already....so I was wondering if there is a new ROM upgrade now.
@kta
so you mean I can go ahead and upgrade my rom to the latest 1.13 rom? My current radio version I think came with that rom i mentioned above...ite version 1.11.00
so what will happen if I upgrade to the latest rom? Why do I need a different radio version?
thanks again...

Need original ROM-Image for MDA Compact 2

I've tried another rom image for my mda compact 2 and now my mdac2 does'nt start any more.
I have tried several rom-images (for compact, atom, ewtc..), but I can install no one .
On the T-Mobile Homepage there is no Image for the MDAc 2.
Can anyone help me ?

I only come to the bootloder screen (red - green - blue).
I need a rom-image, that i can start from the bootloader.
thx

Try this link from TMO UK http://t-mobile.iris-global.com/download_manager_mda_com2.html
Success, M

I've already tried this, and it starts updating but then comes the message :
ERROR [294] : INVALID VENDER ID
THis Update Utility cannot be used for your PDA Phone.....
Maybe I have to unlock the CID first ?
But can I unlock the CID with the aWizard, when the Comp.2 is in the Bootloader mode (red-gree-blue) ?

Ouch,
Yes the cid-unlock will be needed :-( Can't you fix the RUU.conf or something simular with a first line like checkid=1 ? I've read about it on the board & seems to work for magician. & there's some tool like MaUpgradeUT_noid for the wizard too, but I don't remember whether that is awizard :-(
You're almost of to the shop isn't it.
BTW when you unzip the shipped-rom, do you get all kinds of nbf files. & Do they all start with the same word when you open them in hexeditor? I use nbfdec to decode them to a 'normal' file which can be edited, then you could be able to fix the header of the nb1 encode it again & try to update your device.
& have you tried some of these tools ftp://xda:[email protected]/Wizard/DumpROM/

Ouch,
Yes the cid-unlock will be needed :-( Can't you fix the RUU.conf or something simular with a first line like checkid=1 ? I've read about it on the board & seems to work for magician. & there's some tool like MaUpgradeUT_noid for the wizard too, but I don't remember whether that is awizard :-(
You're almost of to the shop isn't it.
BTW when you unzip the shipped-rom, do you get all kinds of nbf files. & Do they all start with the same word when you open them in hexeditor? I use nbfdec to decode them to a 'normal' file which can be edited, then you could be able to fix the header of the nb1 encode it again & try to update your device.
& have you tried some of these tools ftp://xda:[email protected]/Wizard/DumpROM/

In the unzipped folder is no file like RUU.conf.
Only RUU.dll and RUUREsource.dll
There are following files in the folder
EnterBootloader.exe
nk.nbf
README.doc
ROMUpdateUtility.xex
RUUGetInfoi.exe
RUUResource.dll
RUU.dll
And I've downloaded " nbfdec " , but I can not start this program.
I think i have to reboot my computer.

un zip all the files from the t-mobile package
ftp://xda:[email protected]/Wizard/Roms/Wizard_RomUpgradeUtility_noID.rar
download this and unrar and overwrite in the same folder.
connect up the phone in bootloader to pc and run the ..._NoID.exe
as theres no activesync connection it will pause for a bit on the checking existing rom but still let you carry on
ignore the picture of the wizard, just make sure your installing the right nk.nbf for the compact 2

I've exactly done what you said, the update ended with 100 % and now the device starts until the bootloader-screen (red-green-blue).
Have I done something wrong ?
What has happened ?

dave106 said:
ftp://xda:[email protected]/Wizard/Roms/Wizard_RomUpgradeUtility_noID.rar
Click to expand...
Click to collapse
That's the one I was referring to, thanks.
Bundy did you reset afterwards?
M

Yes, I did a Hardreset, a Softreset , but I only get to the picture with the 3 colors.
IPL 1.12
SPL 2.15

I'm terribly sorry, but we've ran out of my knowlegde of the MDA Compact II. So besides the usual question: have you ran the update a second time, for me this would be warranty issue.
Hope Dave is worth more.
Good luck, M

Yes , I have done the update a second time, but with the same effect - the device only starts in the three-color-screen.
So I think I can do nothing more ....

:-(

how to upgrade g4

I will get o2 xda neo from germany.
I would like somehow upgrade it to English version.
I already know it is G4 model so 0001. and it is probably locked because it is new.
I read much of forum and I found only one way to upgrade it.
http://en.pdamobiz.com/en/forum/foru...p?TID=440&PN=1
is that the only way and the only rom I can use if my pda is locked?
Sorry because of my stupid questions. I'm new.

so anybody? I need help

dtusek said:
I will get o2 xda neo from germany.
I would like somehow upgrade it to English version.
I already know it is G4 model so 0001. and it is probably locked because it is new.
I read much of forum and I found only one way to upgrade it.
http://en.pdamobiz.com/en/forum/foru...p?TID=440&PN=1
is that the only way and the only rom I can use if my pda is locked?
Sorry because of my stupid questions. I'm new.
Click to expand...
Click to collapse
use awizard tool.
fisrt ,you need make a nba format rom file . use typho5.exe cmd break an offical nbf format rom, you will get the 80040000-OS.nb file, modify it as 80040000-OS.nba. then use awizard tool updata your neo. it updata you os rom only,so it's safe.

ypsys said:
use awizard tool.
fisrt ,you need make a nba format rom file . use typho5.exe cmd break an offical nbf format rom, you will get the 80040000-OS.nb file, modify it as 80040000-OS.nba. then use awizard tool updata your neo. it updata you os rom only,so it's safe.
Click to expand...
Click to collapse
Could you write something more about it?
Step by step instuction or something.
I'd love to change rom in my o2 xda neo G4 to english version.

rydzo said:
Could you write something more about it?
Step by step instuction or something.
I'd love to change rom in my o2 xda neo G4 to english version.
Click to expand...
Click to collapse
SORRY ,My English very poor. follow me,i hope you can understand.
1. download the files.
awizard & typho5.exe
2. download an eng offical (prophet)ROM file from xda ftp , and extract it ,then you will get the NK.NBF file.
3. copy typho5.exe and nk.nbf files to c:\
4. start > run> input "cmd"
5. this folder "c:\" on dos, input typho5 –v –x nk.nbf
wait..... you will get the 80040000-OS.nb file from c:\
6.Modify " 80040000-OS.nb" to "80040000-OS.nba" (add " a " word )
7.put the 80040000-OS.nba file into awizard\ROM\
double clik awizard.bat file, see about awizard tool writer's "readme" file.
Q1 : How to flash ROM file to device:
1.run option 'e'
2.run option 'u'
(after program perform finished, you must confirm your phone restart itself )
4.run option 'w' (choose 80040000-OS.nba) and enter
wait..... until pc display show over,then you reset your phone.(hard reset)
work finished , your phone is eng platform now. but the extended_rom need modify ,next time tell u.
do you undertand my above means?

No, there is no need to use any thirdpartytools.
It was no problem for me to upgrade my Xda Neo with the 2.15-O2-Rom directly to the 2.20-Qtek-Rom (could be found on FTP-server).

crazyd said:
No, there is no need to use any thirdpartytools.
It was no problem for me to upgrade my Xda Neo with the 2.15-O2-Rom directly to the 2.20-Qtek-Rom (could be found on FTP-server).
Click to expand...
Click to collapse
yes ,if your ipl_spl version lower than the updata rom version,use the romupdatauitlity "next--next--next-flash....." could be successfull . if u downgrade contain ipl_spl 's rom,your phone will not be reboot (g4 phone).
awizard tool updata your rom only , any os roms can be used. it's useful tool for g4 machine

crazyd said:
No, there is no need to use any thirdpartytools.
It was no problem for me to upgrade my Xda Neo with the 2.15-O2-Rom directly to the 2.20-Qtek-Rom (could be found on FTP-server).
Click to expand...
Click to collapse
I couldn't do it your way.
I did it ypsys way.
THANKS!!!
Now it's time for extended rom.
Any tips???

rydzo said:
I couldn't do it your way.
I did it ypsys way.
THANKS!!!
Now it's time for extended rom.
Any tips???
Click to expand...
Click to collapse
here you go.
I have "Qtek_wwe_ExtROM_v2.20.7.114" EXT_ROM only, cooperate the same OS version is the best. if you want to get your currently EXT_ROM version ,maybe need other same version users use awizard tool backup it for you.
This is the EXT_ROM replacement method :
1.download "ext_rom unlocker ,extended rom,Total Commander", then copy these files into your phone.
2.on your phone, run "ext_rom unlocker.exe" first;
3.install "Total Commander.cab",then run this 'Total Commander' program.
4.In 'TC' interface，click "show">"Singe window mode">choose "Two window mode", then input "\extended_rom" in the top of the blank row 。it will show the hiding files, click one file, then click "show">"select/unselect files", input " * ", click "select", click one file and hold on press,then delete all files. in the row below ,open the Extended ROM folder ,copy all files .click "Copy to Clipboard". then paste these files in above window. select this new files, hold on press , select "Properties" , in front of the "Read Only", click twice,click "OK", do the 'hard reset'.
over.

don't work
5. this folder "c:\" on dos, input typho5 –v –x nk.nbf
this doesn't work

Rydzo, could you give exact link to ROM (ftp) you used?
Thanks
Slawek

slawje said:
Rydzo, could you give exact link to ROM (ftp) you used?
Thanks
Slawek
Click to expand...
Click to collapse
i don't remember wher I found it, but here is excacly the name of the file:
RUU_Prophet_220734_2207114_024721_QTEK_WWE_Ship.rar

I am surprised that ypsys's method actually works on G4 Prophet. Can someone please double confirm it? rydzo anyone?
The reason that I am in doubt because ypsys's method of using awizard includes step to CID unlock from the 'u' command, which does not work on G4 Prophet. I download the latest awizard tool and the readme clearly says that the tool will try to force unlock CID in every write option. Won't that cause any harm to G4 Prophet?

kjliew said:
I am surprised that ypsys's method actually works on G4 Prophet. Can someone please double confirm it? rydzo anyone?
The reason that I am in doubt because ypsys's method of using awizard includes step to CID unlock from the 'u' command, which does not work on G4 Prophet. I download the latest awizard tool and the readme clearly says that the tool will try to force unlock CID in every write option. Won't that cause any harm to G4 Prophet?
Click to expand...
Click to collapse
yes, I was suprissed to
but it worked perfectly.
I've changed rom in 5 G4 prophets whithout any problems using this method.

Hi,
I'm a totaly newbie to HTC and CID so I do have 2 Questions.
1) Is there a ROM which does support wpa2-aes and eap-ttls ? I did not find a detailed description of the many diffrent roms.
2) if 1 == true how do I find out if my phone is CID locked without trying a rom update. Some said that every HTC Prophet G4 is CID locked and others only newer G4 are locked. My phone :
ipl 2.15.0001
spl 2.15.0001
GSM 02.19.21
ROM 2.15.4.47
thx
steiftier

if 1 == true how do I find out if my phone is CID locked without trying a rom update. Some said that every HTC Prophet G4 is CID locked and others only newer G4 are locked.
Click to expand...
Click to collapse
hi,
i too have similar confusion. I bought new Neo, with dopod rom already installed having following :
ipl/spl 2.15.0001
radio 2.19.21 (dont remember, may be 2.17.21 or some like that)
OS 2.15.13.27 WWE
Rom dt 3/09/06
Protocol 4.1.13.16
Ext rom 2.15.13.121
i only upgraded radio to 2.47.21, but then downgraded to 2.20.21 bcos it was eating battery so fast. still this radio is consuming more battery than my original radio which i had no backup. Is there any available source of only radio 2.19.21 ?
well main confusion remains intact--- whether my G4 Neo is CID unlock or not? I guess it is unlock as it already comes with dopod rom. I dont know right answer, may some senior help.
Due to this uncertainity im not flashing my Neo with
RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_Ship.exe
to get back the radio 2.19.21
should i do the flash with this?
please answer gurus.
thanx
nandlal

Ok guys,
i flashed my Neo with
RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_S hip-NoVendorID.exe successfully and now it got radio 2.19.21.
device is runing good as before and battery drain is as standard.

WM6.1 Running BBConnect 4.0.0.90 GOOD

Ok,
So I got the Universal yesterday and spent all day trying to get BBConnect to run on it and after searching for days and days I was able to piece things together to get it to work. So here are the links to the tools I used and as far as I can recall the steps I took.
ROM: DFT WM6.1 19174
http://www.darkforcesteam.com/showthread.php?t=133
HTC64 Tools (to convert the nbf to a fat file)
http://forum.xda-developers.com/attachment.php?attachmentid=25416&d=1133971744
HEX Editor
http://www.rs.e-technik.tu-darmstadt.de/applets/frhed-v1.1.zip
BBConnect software
http://rapidshare.com/files/45075798/BBConnect_WM6_Professional_BB_4.0.0.90.exe.html
HTC NetworkWizard cab file
http://forum.xda-developers.com/attachment.php?attachmentid=80495&d=1207858578
Ok so here is what I did
Right click the ROM file "DFT.U.V1.WWE.rar" and extract this will put the files in a folder "Outputfile" containing the following files:
EnterBL.exe
GetDeviceData.exe
ROMUpgradeUt.exe
RUU.dll
UI.dll
nk.nbf
Next extract the HTC64 Tools folder this will allow you to launch:
HTC64 Extended ROM Tool.exe
Double click it and choose decode
point to the nbf file and choose extract
This will creat the following files in the "OutputFile" folder:
nk.fat
nk.prj
Now install the hex editor and launch it, then click Open to open the "fat" file
along the top of the address bar is a set of binoculars click on that type "HTC" and check the Unicode box change the letters Univer to Hermes the remaining letters sal change to ...
save the file
Use HTC64 tools and encode the file, then update your universal
Run the network wizard cab file, reboot, configure for your provider
Install the registry editor and go to the following location
HKLM/System/Version/AKU change it to .0.3.1 (yes that is a . at the begining)
Reboot
Ok now your ready to install BBConnect
I was able to connect and have been connected for about 5 hours now.

i was actually trying this out a couple days back with Tomal (Ranju) latest rom.
i got the client to startup but couldn't connect.
figured it's a problem with my account, which i gotta check with the network provider.
but can you explain why you had to edit the ROM to change the Universal to Hermes.. and the AKU version to 0.3.1?
does the BBConnect software check for these and refuse to work if they're not matching?

I read on a post that it had to do with the model of device that was sent to authenticate with the BB servers, the ROM edit from the information I gathered sends the device type as a HTC-Hermes which is an authorized BBConnect device.......

What's the chance of getting the BB connect software running on Tomal's 7.6 ROM by performing the same search-and-replace as you did? Or does it have to be the ROM you used?