Hi all. I've been reading for several weeks now. The group is very helpful and supportive. Good reason to join the community!
I have an SX-66 from Cingular that I have been attempting to go with the Wizard WM5 ROM. I get to the point of flashing the updated ROM but the BaUpdateUt.exe flash utility says its not a valid ROM for my device. I ran XDA3NbfTool after editing the EditFix.bat file with data from GetDeviceData.exe run on the BA. Does this appear correct? The line updated in EditFix.bat was:
Code:
xda3nbftool -sd PHB20B1 -sl WWE -so XGULA001 nk.nba
I am also curious to know what the current 'best' WM5 ROM to try. From what I have read, the Wizard has the advantages of no slow-downs and all the hardware is working. Any comments here would be appreciated too.
TIA,
Midas
Maybe this will help
I too have a cingular sx66, I've successfully gotten it patched up to the wizard wm5 rom and radio 1.15 and I have to say, I'm VERY pleased. It's running just about like it was meant to have this rom on it. Here's the info from my editfix.bat file that I used to alter my nk.nbf rom before flashing. Perhaps it will help you.
REM ~DeviceData.txt PH20B 0 B WWE E T-MOB101 1.12.22 2 2 1.12.169 1.02.00 02.00
REM Replace the question marks with the data from ~DeviceData.txt
REM 'sd' stands for device, e.g. PH20B.
REM 'sl' stands for language, e.g. WWE.
REM 'so' stands for operator (Country ID), e.g. T-M0B101.
REM ms_.nbf Password = 0x20040522
REM nk.nbf Password = 0x20040521
REM radio_.nbf PAssword = 0x20040523
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -sd PH20B1 -sl WWE -so XGULA001 ms_.nba
xda3nbftool -sd PH20B1 -sl WWE -so XGULA001 nk.nba
xda3nbftool -sd PH20B1 -sl WWE -so XGULA001 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
One thing that I notice when I do a hard reset though is that to get my GPRS settings to work I have to run a cab file called Cingular_Cust.cab which sets up my "Media Net" GPRS connections, after that I'm all set.
Hope this helps, Lord knows I've received my fair share of help from this group maybe I can give back a little.
Good luck!
Derek M.
Jackson, MS.
sx66 PH20B1
Wizard WM5 "Maimach'ed"
Radio 1.15
Perhaps tonight
Thanks dmelton75. If I can find the radio ROM on the forum, I'll try things tonight! Although I note you have the exact same settings as I did. I didn't do the ms and radio patches since the available WM5 Wizard pack didn't come with those ROM images. Is that true of the WM5 package you upgraded with? Where might I find the latest version?
TIA,
Midas
Files
Go here:
ftp://xda:[email protected]/Uploads/Blueangel/
Download the wizard2ba_v1test.rar under the wm5_test folder.
Use that editbatch info I gave you to modify the rom for a sx66/cingular and follow the other instructions here:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM5_WizardPort
After you do that, go back to the FTP and download this file:
File: ba_radio_1.15_in_v1_format.rar
I ran the edit fix stuff on this radio rom too, dunno if I needed to but it worked.
Hope this all works!
Thanks,
Derek
Success!
Just a follow up. I used the EditFix.bat data that demlton75 provided. It worked flawlessly. I was also able to update the radio ROM. Thanks!
I am now tracking down all of the little 'nuisances' that I've been reading about. One confusing one is what extra patches should one install? I believe I'm reading about older issues with the Himalaya or earlier WM5 build but I'm not sure.
So after installing the Wizard2BA ROM what patches are sugessted? I've followed the install guide, so tweaks, etc are already there.
Also, anyone know of a VB runtime for WM5? I miss my Warring States!
And finally, I seem to notice that my BA slows down over time. Anyone else run into this? What I mean is that the GUI does not respond as quickly.
-Midas
I know this post is going to make me look like the n00b I am with this subject, but I know how to use the phpBB though.
I have been reading the wiki... not that it makes a whole heck of a lot of sense to me at this point in time (giving me a headache to be honest). I'm sure it will later though.
I've been searching all over this board all day, and this thread is as close as I'm going to get to what I want to do.
Well.. what I think I want to do anyway.
I want to upgrade to WM5, but if Cingular doesn't offer it.. then how is this possible. I don't care about voiding my warranty as Cingular and Siemens have pretty much told me in my search for a screw for the case that I'm on my own. It's just a simple T-6 screw for crapsake. *sigh
I do need a better signal though. My wife's flip phone in the same room has better signal than my PPC :/ Sad really..pay more for a phone and get less service.
OK I dl'd the files aforementioned in this thread. I think I need a editor of some sort. Anybody got a link to one. I think I can edit on my own without any handholding if the editor is straight forward.
I also need to edit the vib/ring cycle as I'm hard of hearing and need this feature to be "adjusted". (Tired of my wife asking me why I don't answer the phone when I just plain can't hear it. :/
I'm not clear on this point. Do I have to "unlock" the phone before I start this upgrade?
TIA for any help. I searched this board all day looking for answers. I finally had to ask.
SUCCESS!!
Well... upgraded the radiostack to 1.15 at any rate.. maybe I'll do do Wm5 later..MAYBE
From what I understand, the wizard works on the cingular version however overall...i read that there are so many issues with the wizard rom such as MS voice command....because the wizard version comes with a voice dialer and so forth...there are various issues that prevents me from updateing to the wizard...i am staying with the himalaya until there is better news about hardware issues and voice dialing...
bluetooth is still a lost cause...
SX66 upgraded to WM05
I have a Cingular SX66 . My search started because I wanted to improve the bluetooth. 1. I have upgraded to Mamaich v3 too slow at start button and didn't improve my BT 2. Upgraded to Wizard v1 it's Faster , but can't use voice command which I love. I have downgraded to WM_2003 Async 3.8 but, am unable to create a partnership, guest only. I have removed firewall, Anti-Virus, installed & reinstalled Async several times; 2 versions, re-registered MSXML3.DLL & MSXML.DLL, tried to repair IE 6.1 following MS steps to the letter, it won't allow. The only thing I can do is go back to WM_05 & Async 4.1. I have spent 4 or 5 days over the last two weeks screwing with this! It would be Ok if I didn't have pressing work to do. I should have known to leave well enough alone, seeing that I am a computer tech, I'm the one with the card board sign that say's have high tech skills will work for food, if you see me standing out on the hwy honk I am running XP Pro SP2 SX66-PH20B1 No Camera. If anyone has any wisdom I would appreciate
I've migraded both ways without any problems. I think the problems lies with Active Sync. Make sure that the removal of your software program has taken out any references to your other devices before removing active sync.
also, active sync lets u modify alot of things...if you did...ur going to have problems if you go back.
overall, i recommend going with the himalaya version. from what im reading, there are ups and down to both but the himalaya on a cingular siemens sx66 has been my best experience. I have everything working as i want except bluetooth. voice command works like a champ as well as all my other applications and games. its a little slow but i mean for the overall performance and no losing all my data when i reset, its heaven.
i haven't had any crashes or anything like that. just keep in mind bluetooth does turn off when your phone is put into standby. For me its a good thing because it saves on battery. same thing goes for wifi. there is a patch you can use to make wifi reconnect but i haven't installed it again due to battery saving.
for all your cingular users, i also recommend the extended life battery to get the best bang out of your device. it helps test all the glitches in your phone so you can post here.
mamaich is a genius.
To WM5 and BACK
I wanted to give my experiences with the Wizard 2? ROM. I was able to get WM5 up and running. It took some time to get the keys, etc. ironed out but everything seemed to work very well. That is until I started using my BT.
I had noticed some overall system slow downs but as soon as I turned on my BT it became unbearable. BT worked better than ever when connected (no more pops and hisses w/headset) but the delay worsened to almost 5 seconds on button pushes, voice commands (MS Voice Command) would timeout, and I would miss calls (by the time I heard the ringer, I couldn't pick up before it hung up).
So, needless to say, I reverted back to 2003. Is the Himalaya ROM base still being updated to work better on SX66s? Reading the forum tends to suggest that the Wizard is the only way to really go. HMMPPH!! :x
Re: Maybe this will help
dmelton75 said:
One thing that I notice when I do a hard reset though is that to get my GPRS settings to work I have to run a cab file called Cingular_Cust.cab which sets up my "Media Net" GPRS connections, after that I'm all set.
Click to expand...
Click to collapse
Please provide the location of that file for Cingular GPRS Settings that works on WM5. I was looking for such a CAB
thanks
Related
I wrote this piece not to have to answer the same question over and over again:
http://wiki.xda-developers.com/wiki/HimalayaRomFlashing
If you find anything missing or wrong, please add, correct.
or if you like to add screenshots, please do.
also it would be helpful if someone could add a nice picture showing how to enter bootloader mode.
Thank you very very much!
I speak for a lot of people here
Gonna try it asap.
Cheers
Marcel
aka Panja
Me again
You made one mistake in my opinion...
now modify the devicetype, operator and language strings in the nbfs
using the values from the devicedata.txt file above
xda2nbftool -sd PH10 -so Qtek -sl WWE -v ms_.nbf
xda2nbftool -sd PH10 -so Qtek -sl WWE -v Radio_.nbf
xda2nbftool -sd PH10 -so Qtek -sl WWE -v nk.nba
Click to expand...
Click to collapse
That needs to be:
ms_nba
Radio_.nba
Gonna upgrade now
Worked like a charm (with the addition I mentioned here above)
I now got an Orange SPV m1000 (DK)
Cheers man, you made me happy!
105 views and only me replying.... :shock:
Come on people give the man some credit!
Cheers
Panja
p.s. I'm now on the English QTek rom
Changing xda2 rom to orange m1000
hi there guys im very new to all this is there an easy way to do this ?
Hi,
it is great, a very good explained information, I did not use it actually (are somthing afraid 'cose am new in this thing),
but soon I will try it ...
ciao from Spain
thank you itsme
short but still effective
regards ize|man
Hey itsme
Are you going to update your guide because there is already a 1.1.0.0 (HimaUpgradeUt.exe) version out now...
hope to hear from you soon.
Thanks
Panja
I added an extra option to xda2nbftool to automatically figure out the xor decryption keys, and decrypt the nbf files into nba files.
just '-t' will only print the commands needed to decrypt, with '-x' it will do the decryption too.
D:\tmp>xda2nbftool -t -x -v
xda2nbftool -x NK.nbf NK.nba 0x20040304
devicetype= PH10
operatorname= TMobile
language= WWE
version= 1.72.00
crc= e71c8c6f
xda2nbftool -x ms_.nbf ms_.nba 0x20040305
devicetype= PH10
operatorname= TMobile
language= WWE
version= 1.72.104
crc= e29d719e
xda2nbftool -x Radio_.nbf Radio_.nba 0x20040306
devicetype= PH10
operatorname= TMobile
language= WWE
version= 1.12.00
crc= 8d76be40
D:\tmp>
Thanks m8!
Good stuff
Itsme.... After i try downgrade from T-Mobile Test ROM (1.72.00), now i always get Model ID Error. I cannot get BOOT it out. My Bootloader is 1.03. Now My XDAII is DEAD! What should i do?
Please Help....
with 'I cannot get BOOT it out.' I suppose you mean that you only have a bootloader now?
read the last sentence in the guide referred to in the first post of this thread.
itsme said:
with 'I cannot get BOOT it out.' I suppose you mean that you only have a bootloader now?
read the last sentence in the guide referred to in the first post of this thread.
Click to expand...
Click to collapse
I'm sorry. I really dont understand. Let me get you my sad story from the beginning :
1. Before, i use ROM 1.66.176 Cooked
2. Then i Format it to get the new ROM installed
3. I cooked the new ROM first
4. Then everything went oke to the upgrade
5. But then, i want to format it again so i can get my new cooked installed
6. Format it
7. BAM!! Cannot do anything else!!
8. I only goes to BOOTLOADER mode
9. Always saying Device ID Error not Country ID Error!!
10. Then i get image from my friend ROM 1.03.11 dump it to SD Card
11. I put the SD Card to my device with that image, but SUDDENLY... Not Allowed Update!!
What should i do, itsme? Please Help...
I do know this is obviously an old post/thread but im new to rooting also new to the site...i'm rooted using a samsung moment with ultimate dream 5.0..i want to switch roms soo bad..but dont know how to go about it now that im rooted...i know i have to go back to stock somehow but dont know how..i need a step by step help...i did search the site and found this thread but the link is dead...help please..im trying to swith to froyo1.9.3
Thanks m8!
Good stuff
Hi following the instructions for the build 14343 i get a "Model Id Error".
here is the content of my DeviceData.txt ;
PH20B2 B 2 WWE VODAP102 1.40.00 0 0 1.13.00 13.00
is there any particular BaUpgradeUt.exe that i should use?
feel free to email me, Tx
S.
Try the NOID version it will skip the country check , you can get it on the ftp @ ftp://xda:[email protected]/BlueAngel/Tools/MaUpgradeUt_noID.zip
I believe that should help you, just unzip and put the *.exe in the folder with the upgrade.
I'd be interested to know if WM5 on your PH20B2 worked, as everything to date is concerning the PH20B/1. Also your opinion as to whether WM5 on the PH20B2 is ready for use, or still better to stay on the 1.40 ROM. Things like the backlight issue seems to suggest the latter.
br/Bosseye
Ignore my last email, already solved it. For the PH20B2, do as the WiKi says except be sure to use the PH20B directory. I found that "maupgrade" wouldn't run until I renamed the HTCRUU.conf and HTCRUU.dll files as RUU.conf and RUU.dll respectively. Then all worked as the Wiki suggests. More updates later...
br/Bosseye
Np .. however, In the end the upgrade it is possible but how SLOW is it? I found it unplayable, and I had to go back to WM2k3
Actually, I found it OK. There are a few problems:
- using the BA keyboard, sometimes keypresses are missed
- sometimes you get Wifi and GPRS at the same time (confused BA)
- it does run a little slower
However, overall, I have no intention of reverting back to WM2003SE. Despite the niggles above, it is a great credit to the star chaps in this forum that they have WM5 running, and so good.
Now Mr Gates, about that Messaging and Security Feature Pack - we're (still) waiting... tap... tap... tapitty-tap...
bosseye You can explain to me more in detail as you have made it?
bosseye You can explain to me more in detail as you have made it?
bosseye said:
Ignore my last email, already solved it. For the PH20B2, do as the WiKi says except be sure to use the PH20B directory. I found that "maupgrade" wouldn't run until I renamed the HTCRUU.conf and HTCRUU.dll files as RUU.conf and RUU.dll respectively. Then all worked as the Wiki suggests. More updates later...
br/Bosseye
Click to expand...
Click to collapse
Hi,
does this mean i can Update an PH20B2 (Vodafone VPA3) with WM5 for the PH20B ??
I have just update my VPA3 with the 1.42 Rom T-Mobile for the MDA3 and the MDA3 is a PH20B but all is working. Whats the different between PH20B2 and PH20B?
Totti
bosseye said:
Actually, I found it OK. There are a few problems:
- using the BA keyboard, sometimes keypresses are missed
- sometimes you get Wifi and GPRS at the same time (confused BA)
...
Now Mr Gates, about that Messaging and Security Feature Pack - we're (still) waiting... tap... tap... tapitty-tap...
Click to expand...
Click to collapse
I've flashed a few WM5 roms and never found any missing keypress on the BA keyboard! You can also try PocketMSN for messaging. If the speed is slower than WM2k5, take care of your device with the 'Startup Manager'
(I am not responsible for any damage you might do to your device using this guide)
I tried flashing with the NoID tool several times, yet it always failed, or my Universal would not boot after the flash.
The regular T-Mobile update utility did work like a charm, and never failed on my. Thus I created a little tutorial on how to convert wrong ROMs to ROMs it will accept.
In this Example I will explain how to use an O2 XDA Exec ROM (and a different radio ROM) on a T-Mobile MDA Pro device
It's easiest to start with a clean directory to do all this as else it can get quite messy.
First, get the HTC64 Extended ROM Tool by Bal666 here:
http://buzzdev.net/component/option,com_remository/Itemid,100/func,fileinfo/id,196/
Next get an original ROM for your device, in my case I used the T-Mobile UK ROM as my device was english anyway.
For example, on the T-Mobile MDA Pro UK (or dutch) version, use "UNI_TMUK_11242_126_10002_Ship.exe" (find it yoursef)
Use WinRAR (http://www.rarlabs.com/) to unpack this file to a new directory called "Original", and unpack it again to a directory named "Converted".
The Original directory will be used to check things, and the Converted directory will be used to store all the roms that we have converted
Next we must find the ROMs we want to flash. I got "Xda_Exec_LaunchROM_v113139.exe" and Unpacked it in a directory named "O2", and "UNI_radio_1.08.00.rar" (from buzzdev.net) and unpacked it into "Radio Update".
First we must find out some things about our original ROMs. For each original ROM in the "Original" directory, follow the next steps:
- Open the HTC64 Extended ROM Tool
- Click Decode
- Open the ROM (.nbf file)
- Write down the values after "Operator Name" and "Language"
- Hit Cancel
Now we must modify the ROMs from the other distributions.
From the O2 directory we will use nk.nbf (OS) and ms_.nbf (Extended ROM), and from the Radio Update directory we will use radio_.nbf (Updated Radio ROM).
For each ROM you want to convert, follow the following steps:
- Open HTC64 Extended ROM Tool
- hit Decode
- Open the ROM
- In "Operator Name" and "Language" fill in what you wrote down earlier
- Hit Decode
- (on the begin screen) Hit Encode
- Open the .prj file you just created (same name as ROM, but with extensio .prj)
- Hit Encode
- if asked "Overwrite existing ROM", choose "Yes"
- if asked "Fat16 file is too large", choose "OK"
- When done, copy the over-written .nbf file from the directory you created it in (like O2 or Radio ROM) to the Converted directory. Choose to overwrite the existing file.
When all is done, run the ROMUpgradeUT.exe in the Converted directory, and follow the instructions.
If all goes well, you should have upgraded your ROM without having to CID-Unlock or use NoID tools that were originally made for another device
If before the actual upgrade your PC says it has found an unrecognized USB Device, close the RomUpgradeUT.exe with task manager (ctrl+alt+del), and reset your device (push the stylus in the hole at the backside). Then re-run the ROMUpgradeUT.exe
Credits go to iruja because he helped me find these tool
Let me know if it also worked on your device
EDIT: Stupid me, HTC64 Extended ROM Tool is by bal666
EDIT2: Note on "Unrecognized USB Device"
EDIT3: Added credits
Nice Job! Good, Clear and informative instructions.
he, leuke guide, die ken ik ergens van
Nice people like my way, this is the same way I test different roms for the wizard, without having to cid unlock the phone and loose warranty
Thank you "TheBlasphemer"
wow, I searched this forum for a few hours trying to understand how to install roms from other developers onto my Universal. It was driving me insane cause i kept on recieving country id errors. I found your post and was delighted to find how easy it really is to upgrade roms. Thank you for helping people like me who have no clue. Thanks, Thanks and More thanks. I also give shout outs to all others in this forum who take time to help others. XDA Developers is awesome! I'm surprised that developer sites dont link to xda developers for their customers. It would save them alot of time and money. Peace
Great Instructions
Many thanks for the great instructions.
I tried to flash my T-Mobile MDA Pro to the latest i-Mate rom and it became stuck in the Bootloader mode (I used the No-ID tool, and tried every type of reset). Fortunately this approach works, and I'm now the proud over of an much faster PDA.
Rom: 1.30.68 WWE 02/08/06
Radio: 1.09.00
Protocol: 42.42.P8
ExtRom: 1.30.153 WWE
The original T-Mobile Rom sucks compared to these i-Mate Roms
http://forum.xda-developers.com/viewtopic.php?t=42743
Excellent
Crystal clear instructions. worked like a charm once I found the Orange operator code is ORANG007. The "Orange" ROM on ftp appears to be a hash of 3 other versions as the operator names are QTEK001 and CDC__ something or other....
Thanks again for the excellent, no hassle upgrade method!
This procedure will be working on MDA Vario (QTek9100) ?
I have a QTEK 9000 that is in Spanish OS. There is no available downloadable shipping ROM so how do i get the values of Operator Name and Language? Are they in the registry=?
Tried this on my MDA pro NL which is stuck in boot screen, but no dice
I used however the init UK rom from T-mobile, not the NL which was my official one. I don't have a NL so I maybe if I use that one, it'll work, but Im afraid not
Viper, I also have a NL version and would like to upgrade my MDA...did you have any luck doing so or did you find the original dutch ROM?
(A stupid question: when I upgrade my rom, i assume that all my data is lost, right?)
Just wondering did you all upgrade your devices with the exe that came with the new ROM, or the one that comes from the phone vendor? :roll:
Kinda wondering should I use the one that comes with the QTek ROM, or should I use the one that came with the Dopod ROM (mine's a Dopod)
wow, how easy was that
the orange updater from the net (M5000_email.exe M5000) creates a temp directory called
\Local Settings\Temp\pft3CA.tmp\
run the orange updater program so it extracts the files, DONT CLOSE IT, leave it at the point where you make it update (don't hit next)
now follow the steps of the OP
simply decode your chosen rom, encode them with the correct info, then overwrite the roms in the temp directory with your required ones
then let the orange app install 'em for you!
took me 10 min to make my radio only to 1.09
hi guys
my MDA Pro dead, only show boot mode. i can't turn on my phone. i'm using all rom files. but no result. please help me how repar my phone. i'm use then solution no result. i can't change my phone lang. detect phone show only empty info. help me pleaseeeeeeeeeeeeeeeeeeee
siemens man??
why that name, do you work for 'em?
hi guys
thank you for reply mail. all problem solved. now good working
thanks to Buzz
Thank you verry much i'm verry happy with the Qtek-ROM (radio of Dopod 900) instead of the T-mobile rom
And now I have MSN
Im going to upgrade my MDA PRO tonight using the instrutions in this thread, but which is the best ROM to update it to? i suppose i would like push mail and msn messenger/hotmail.
also is there a slightly more stable internet browser in the ROMS? my current IE is not very good, and opera has the habbit of coming up with a not enough storage memory in dll error!
XDA EXEC is dead
I received my xda exec two days ago. I've tried the ROM upgrade as described. ROMUpgradeUT went OK. When I cold boot my device I get two options - Press 0 to restore factory default Press X to exit. Neither have any effect and the exec seems to be dead. Can someone help out or suggest a fix please?
It's alive !!!
Managed to get the exec in boatloader mode, plugged in usb and reflashed it with an original O2 rom, which, thankfully revived it. I still would like to find out what went wrong with the original ROM upgrade and why it 'killed' the exec. I followed the instructions to the letter. My orignal pre-installed ROM was a 1.13.82 (11/30/05), Radio 1.04.02, XROM 1.13.188. I tried to upgrade to JASJAR ME 1.30.82 171 10900 WWE ship ROM, which effectively turned my exec into (I quote) 'a very expensive paperweight'. I now have got it working with an older O2 original ROM (ROM 1.13.48 (09/19/05), Radio 1.04.02, XROM 1.13.139). When I tried to flash I overwrote the 'original' (ROM 1.13.48 (09/19/05), Radio 1.04.02, XROM 1.13.139) with the modified ROM, RADIO and XROM files from the JASJAR version, I didn't replace any dll files. Could this be the problem or am I way off target? Can anyone spot were I messed up here. Tonight I will try with another JASJAR upgrade, now that I know I can safely reflash with an oringal O2 ROM.
anyone know where i can get ROMUpgradeUT.exe tool from?
Just thought i would post a download link for the latest WM6 official o2 rom, it has been out for a few months but now at least people who have other hermes devices can now download it
http://rapidshare.com/files/82987999/RUU_Hermes_O2_UK_3.62.206.2_6275_1.50.00.00_108_Ship.exe
what kind of O2?
I have O2 Atom.., can it ?
thanx for the info.
Man..this is hermes thread.. so obviously it's hermes o2 rom..
Thank you for the link.
I've been away from the site for a long time and I'm a bit nervous. I started out with a blue angle and did almost very thing to it years ago. So for with the Hermes I only done the official updates. But now my phone is unlocked incl SCID and Hard-SPL-V7, I need re-arrange things.
So after day's of reading I come to the conclusion thus. To use this upgrade I did to extract the *.nb's and re-compile them back to a RUU_signed.nbh. ( Herm_ExtendedRom.nb + PrimarySplash.nb + Radio.nb + SecondarySplash.nb + Windows.nb extracted and re-compiled using nbhtool-v101) With my newly created RUU_signed.nbh I can install using RUUWrapper.exe and a USB cable or re-name it to HERMIMG.nbh and install from SD card.
Could someone confirm that this would be my procedure.
(P.S. when re-compiling the *nb's using nbhtool-v101 I used the setting HERM100 instead of HERM200. My Hermes is a 100 according to the Device Information -> Model No:.
mithrin said:
Thank you for the link.
I've been away from the site for a long time and I'm a bit nervous. I started out with a blue angle and did almost very thing to it years ago. So for with the Hermes I only done the official updates. But now my phone is unlocked incl SCID and Hard-SPL-V7, I need re-arrange things.
So after day's of reading I come to the conclusion thus. To use this upgrade I did to extract the *.nb's and re-compile them back to a RUU_signed.nbh. ( Herm_ExtendedRom.nb + PrimarySplash.nb + Radio.nb + SecondarySplash.nb + Windows.nb extracted and re-compiled using nbhtool-v101) With my newly created RUU_signed.nbh I can install using RUUWrapper.exe and a USB cable or re-name it to HERMIMG.nbh and install from SD card.
Could someone confirm that this would be my procedure.
(P.S. when re-compiling the *nb's using nbhtool-v101 I used the setting HERM100 instead of HERM200. My Hermes is a 100 according to the Device Information -> Model No:.
Click to expand...
Click to collapse
Excellent post sir, i like to see people who have done thier homework
Best thing to do is only to flash a radio unless you REALLY need to. Leave out the radio nb file and just rebuild the ROM as you (correctly) described.
Flash the new nbh file using RUUWrapper over USB (sync with activesync first).
Take a look at the thread in my sig about the choices of radio ROM.
Good luck sir
Thank you mrvanx for the reply and confidence. My radio is 1.16.00.00, with radio roms going up to 1.54.? I think I need updating. So this being an official rom I'll use it as a base. I'm hoping to try Schap's WM6 4.31 if all gos well.
Hi all - sorry about this, but I'm new to this. Got an Orange M700 - still running the original Orange branded WM5 OS: yup, Orange have mangled it. I've been reading the (many...many...many) threads and the wiki and... well I think I'm more confused than ever.
So, just wondering if someone can advise me on the best route to upgrade, and bear in mind I'm a graphics guy....
So, briefly
from the Orange WM5, is there a straight one-step upgrade to WM6?
What .cabs/versions should I be looking for? -> I know there are many you guys have tuned. I guess I'm looking for a fairly standard one? Unless you think otherwise!
Are there any major caveats (other than warranty/support invalidation)?
Need a little hand-holding...
Thanks in advance.
Hi, welcome..
I have M700 too, took the plunge a while back and loaded one of Mun's ROM's.
All I did was install activsync onto my pc and hook up the phone for the first time, once that ran its course I unplugged the phone powered down and removed the sim & sd card and then powered back up again.
Once up n running I plugged it back into the pc and ran the rom I had chosen, yes I was worried it might go wrong but I have to say it was and is very simple n straight forward. There is a WM5 Orange backup rom on here so if you ever did need to send back then you can flash this back onto the phone so it "looks" normal, tbh I'd doubt it would come to that.
I was using XP-SP2 at the time, not sure of anything different for Vista but that's where others here will put you straight, since then I have altered rom many a time and finally settled for Tom's Black'n'Blue - nice and fast and room to add what I want to add rather than be given. Oh and also update the radio rom to the latest version too, pretty much the same method.
Have a look at the roms and decide what you want Happy modding...
Only "gotcha" try and flash from XP, it is rumored to be problematic on a vista PC.
Also be warned flashing ROMs can be addictive, think i have tried 8 or 9 on my Trinity to find one i like, have yet to try the MUN one suggested in the previous post, looks like it will be next.
Ah, twas an early Mun rom and was WM5 - like I said the very first rom I'd flashed so I wouldn't flash to that now
Also realised why i hadn't tried it, i have tried several 6.1 ROMs and none of the WM6 ones. Probably will now i think about it though.
spv m700
Just joined the forum, thought I'd say hi.
I've just bought an spv m700 (following 2 years of the great spv m600), mainly because I wanted inbuilt gps.
The previous owner flashed it with Windows Mobile 6.1, I've yet to really test it.
First of all, I'm going to re-install all my Spb software (spb time, spb backup, spb mobile shell, etc) and transfer contacts etc via active sync.
If anyone has any advice or tips n tricks that you feel may benefit me, I'm all ears.
Cheers,
Matt.
Mattster_spv said:
Just joined the forum, thought I'd say hi.
I've just bought an spv m700 (following 2 years of the great spv m600), mainly because I wanted inbuilt gps.
The previous owner flashed it with Windows Mobile 6.1, I've yet to really test it.
First of all, I'm going to re-install all my Spb software (spb time, spb backup, spb mobile shell, etc) and transfer contacts etc via active sync.
If anyone has any advice or tips n tricks that you feel may benefit me, I'm all ears.
Cheers,
Matt.
Click to expand...
Click to collapse
First of all, welcome!
You have to know that the key to knowledge is searching, reading, and if none of those work, asking through posting!
So, happy enlightment and enjoy your device!
OK Monkeybox - hold out your hand - here's mine.
First thing - choose a ROM (sorry, you'll need to make your own choices). Judging by what you have said a LITE ROM would suit your needs.
I have tried most trinity ROMS. I like ADW's ROMs, am currently on Akeo's ROM but have tried LVSW, mUn, black and blue, PDAVIET, FInixNOver, ervius etc etc etc (Sorry if I've tried and forgotten your ROM!). Once you have your ROM, you should unlock the phone
1. (Hard-SPL - Service Providor Lock). http://forum.xda-developers.com/showthread.php?t=299659 This will enable you to flash a ROM with different carrier ID to you SPV M700. OK - Once you have hard-spl'd your phone, find the RUU (Rom Update Utility) exe file within the ROm that you downloaded.
2. Connect your phone (windows XP is best) using activesync and when activesync is connected, run the RUU Updater. The phone will switch off and go into "bootloader" (coloured bars on screen). If you get a connection error here, just run the RUU updater again. this time things should get going. When finished - your new ROM is installed - no more Orange!
3. Next update the Radio - search xda-developers.com using google for Trinity Radio - and choose 1.46 or 1.5x.
4. Install missing software (generally you'll need a GPS navigation software at least).
5. Enjoy.
6. If you like a ROM - donate to the cooker
7. Get a flashing addiction
8. Read all of the Kitchen threads
9. Cook your own ROM
10. Share it with us
11. Be eternally happy
nealed said:
OK Monkeybox - hold out your hand - here's mine.
First thing - choose a ROM (sorry, you'll need to make your own choices). Judging by what you have said a LITE ROM would suit your needs.
I have tried most trinity ROMS. I like ADW's ROMs, am currently on Akeo's ROM but have tried LVSW, mUn, black and blue, PDAVIET, FInixNOver, ervius etc etc etc (Sorry if I've tried and forgotten your ROM!). Once you have your ROM, you should unlock the phone
1. (Hard-SPL - Service Providor Lock). http://forum.xda-developers.com/showthread.php?t=299659 This will enable you to flash a ROM with different carrier ID to you SPV M700. OK - Once you have hard-spl'd your phone, find the RUU (Rom Update Utility) exe file within the ROm that you downloaded.
2. Connect your phone (windows XP is best) using activesync and when activesync is connected, run the RUU Updater. The phone will switch off and go into "bootloader" (coloured bars on screen). If you get a connection error here, just run the RUU updater again. this time things should get going. When finished - your new ROM is installed - no more Orange!
3. Next update the Radio - search xda-developers.com using google for Trinity Radio - and choose 1.46 or 1.5x.
4. Install missing software (generally you'll need a GPS navigation software at least).
5. Enjoy.
6. If you like a ROM - donate to the cooker
7. Get a flashing addiction
8. Read all of the Kitchen threads
9. Cook your own ROM
10. Share it with us
11. Be eternally happy
Click to expand...
Click to collapse
Thank you, and all others who have responded, for your greatly appreciated advice! I've been trying to get my head around the process. Have backed up using PIM backup and settings saviour... and with your hand holding, am about to dive into the world of modding!
It's a little daunting for a newbie (and I really do mean a newbie!), but with everyones help, and this fantastic community as a resource, bah, watch me fly! (I'll probably be back tomorrow asking how I can de-brick the phone ;O) )
Thanks again all.
Cool. Upgraded to WM6.1 - Akeos latest black one.
Have to say the functionallity is 10 times better already. Upgraded to the latest radio too.
HOWEVER... and this is where the newbie kicks in, I can't seem to start any data sessions. IN COmm manager I don't have the option to turn the data connection on (this was also the same prior to the radio upgrade)
Don't suppose anyone knows how to resolve this do they?
As I say, taking my first steps on the modding ladder, and it appears I may have slipped...
mkOnKeY bOy said:
Cool. Upgraded to WM6.1 - Akeos latest black one.
Have to say the functionallity is 10 times better already. Upgraded to the latest radio too.
HOWEVER... and this is where the newbie kicks in, I can't seem to start any data sessions. IN COmm manager I don't have the option to turn the data connection on (this was also the same prior to the radio upgrade)
Don't suppose anyone knows how to resolve this do they?
As I say, taking my first steps on the modding ladder, and it appears I may have slipped...
Click to expand...
Click to collapse
You have to define your data connection from "Start, Settings, Connections, Connections, My ISP, Add new" according to your carrier (ie GPRS, 3G). Same goes to configuring MMS, just that you do it at "Start, Settings, Connections, Connections, My Work Connection" and you also have to define it in Arcsoft MMS.
You will not be able to start them from the CommManager as they connect on demand as needed, but you can STOP the in the CommManager when they are connected since they don't disconnect automatically.
tnyynt said:
You have to define your data connection from "Start, Settings, Connections, Connections, My ISP, Add new" according to your carrier (ie GPRS, 3G). Same goes to configuring MMS, just that you do it at "Start, Settings, Connections, Connections, My Work Connection" and you also have to define it in Arcsoft MMS.
You will not be able to start them from the CommManager as they connect on demand as needed, but you can STOP the in the CommManager when they are connected since they don't disconnect automatically.
Click to expand...
Click to collapse
Once more, thanks to all who've helped me over the threshold - the data connection must have been an issue with the signal, as this morning it was happy to connect to mms/internet via 3G/GPRS and HSDPA (which I didn't even know Orange supported).
Cheers all. Your help has been absolutely spot-on. It's refreshing to come to a community where you not only happy to help newbies, without the usual sarcasm or pomposity you find elsewhere, but you do so in a clear and concise way that really does help.
Thanks all. Look what you've gone and started now... !!!
One happy newbie stepping out into a brave new world...
---edit---
please delete this post
have fun with your spv
I have a problem, and the more I search the forums, the more I worry it may be due to an upgraded Rom.
The original owner of the spv m700 I just bought has by the looks of it debranded it and installed WM 6.1:
Device name: HTC_P3600i
Model NO: TRIN100
Windows Mobile 6.1 Professional
ROM version 3.03.751.5
ROM Date: 04/01/08
Radio Version: 1.16.00.00
Protocol Version: 32.53.7018.01H
With Tomtom 6 installed and seemingly working, the GPS receiver is not being detected. I have done what the forums say, i.e. selected "NMEA GPC receiver", get a screen with:
COM3: GPS in COM9
COM7: RIL on COM6:
S2410 IRDA
I have clicked on the first option (COM 9 is recommended), but still no GPS device found, indoors or out, after 10 minutes of trying
Like I say, much info says the above should solve it, but others say an upgrade can knock out the GPS and it needs to have a different ROM reinstalled. Never done this before, and there may be an easier solution?
Help anyone.... please.......?!
I'm not 100% sure but I think your radio rom needs upgrading to support GPS - I'm sure the one's that do have 11 at the end of them..
Really?? It would be great to finally reach a soultion!
Can someone verify if this is true and if so, what do I have to do??
Thanks.
Hi Monkey Boy and all.
I think I'm in a similar situation that you were...
The original owner of my new spv m700 debranded it, unlocked it (by flashing an old radio ROM) installed WM 6.1. I now fear that the reason tomtom detests no GPS device is because the radio may need updating too... (see below for the spec on my phone at the moment).
Have you discovered which is the best radio to update to?
Device name: HTC_P3600i
Model NO: TRIN100
Windows Mobile 6.1 Professional
ROM version 3.03.751.5
ROM Date: 04/01/08
Radio Version: 1.16.00.00
Protocol Version: 32.53.7018.01H
All advice and recommendations welcomed. I have never flashed anthing before so this is all new to me, but I like to think I learn fast...
Thanks,
Matt
http://forum.xda-developers.com/showthread.php?t=293957
Original owner would have done this to unlock it, so all you have to do is search for the latest radio rom and flash that to your phone - there are guides how to do this in here..
Radio ROM
http://forum.xda-developers.com/showthread.php?t=325197&highlight=radio+flashing
Guides
http://trinityguides.info/index.php?option=com_content&task=category§ionid=4&id=31&Itemid=66
Hey Trixter.
Thanks for the reply.
I managed to get in touch with the original owner and he sent me a link to an an .exe file which I downloaded, ran whilst activesynced to my phone, and voila! I now have radio ROM 1.50.08.11. Tomtom 6.03 now successfully works using settings "other NMEA GPS receiver" with "GPS baud rate 115200" and "GPS in Com9"!
I'm a novice and bought the phone as a "pimped up" spv m700. But I'm learning loads since joining thanks to people like your good self answering posts, so thanks.
Matt
Thanks to seeing your signature I'm sorted! If you read anyone else with the same problem, I hope my experience helps them.
Thanks again for your time,
Matt.