Develop Bugs

Complete idiots guide needed, please!

It might be very simple to all you educated guys, but I am sure there are a few more like me that are a bit baffled by some of the threads on here.
What would be REALLY nice would be a 'simple' step-by-step guide to installing wm6 on our devices, and what we need to download to achieve it, eg "you need this for MDACIII, and this for O2 Orbit"
Obviously anyone trying it runs the risk of buggering up their phone, but that's their own fault.
Any volunteers?

stunno said:
It might be very simple to all you educated guys, but I am sure there are a few more like me that are a bit baffled by some of the threads on here.
What would be REALLY nice would be a 'simple' step-by-step guide to installing wm6 on our devices, and what we need to download to achieve it, eg "you need this for MDACIII, and this for O2 Orbit"
Obviously anyone trying it runs the risk of buggering up their phone, but that's their own fault.
Any volunteers?
Click to expand...
Click to collapse
having asked the same question myself here goes.
Download USPL and follow the instructions. they are very clear.
Download
extract
connect phone with minimum 50% battery
soft reset and once started up fully run the app by clicking on Rom Update utility
follow the process through once finished your device will restart.
once restarted you then can flash the rom of your choice
I used Black and Blue again ran the update utility and bingo.
dont forget that all data on your device will be lost so make sure you have back up of contacts etc in outlook on pc.
Finaly make sure you have Activesync 4.5
enjoy
AS STATED ALTHOUGH THIS WORKS YOU ALL DO IT AT YOUR OWN RISK

Id just like to know really is that how many people have done it without unlocking the device for o2 orbit uk. i have one and am not really willing to try it unless i know there are people out there that have tried it and it worked.
as there is no rom install file from o2 for this, there is no way bacj and bricked phone is the only way forward. id like not to brick my phone as i need it daily.
so, has anyone with a locked o2 device upgraded to WM6 successfully and which rom did you use if it worked.?

joey jojo said:
Id just like to know really is that how many people have done it without unlocking the device for o2 orbit uk. i have one and am not really willing to try it unless i know there are people out there that have tried it and it worked.
as there is no rom install file from o2 for this, there is no way bacj and bricked phone is the only way forward. id like not to brick my phone as i need it daily.
so, has anyone with a locked o2 device upgraded to WM6 successfully and which rom did you use if it worked.?
Click to expand...
Click to collapse
i have o2 uk orbit and all is well

pof said:
I created update package for this ROM in NBH format, so no risk of bricking when flashing it, just unzip & run RomUpgradeUtility.exe
Download here:
ARTE_WWE_WM6.zip​
NOTE: Before flashing you need to have Artemis USPL on your device.
Click to expand...
Click to collapse
Taken from Bepe's thread about the modified o2 German update. Basically you need to use the Artemis USPL program and then use the first link to install which I did successfully on a CID locked phone.

Thanks guys, but, unfortunately, the uspl thing does not work on my pc
Along with a few others I get the 'black screen' on my mdac3 then activesync disconnects and the rom loader throws up an error
Luckily my mdac3 survives through a soft reset
I think the idiots guide is not quite there yet

hi..
i have O2 uk orbit.. which is still locked, i fully charged the battery, completed a hard reset of the phone used the pof Artemis Update SPL (USPL) v.01 upgrade (wow what a brain box he is!) just in case it failed, so i could you use any NBH file to get you orbit to work again if i failed. Then used Bepe's WM6 os.nb file renamed it to windows.nb downloaded ATRE.zip unzipped the ARTE.zip file placed the windows.nb into the same directory, don't forget to edit UpgradeRom.bat file 0x3900000 to 0x3500000 with in the ATRE directory and copied and installed EnableRapi.cab to the phone. Reset it the phone and then started the UpgradeRom.bat! 12 mins later upgrade complete. Hard restart the phone.. Chewing nails by now... all went well did a soft reset of the phone before the O2 ExtROM autorun starts..
sorted, and did half way though a night shift at 3 am.. not bad at all!

crushuk said:
hi..
i have O2 uk orbit.. which is still locked, i fully charged the battery, completed a hard reset of the phone used the pof Artemis Update SPL (USPL) v.01 upgrade (wow what a brain box he is!) just in case it failed, so i could you use any NBH file to get you orbit to work again if i failed. Then used Bepe's WM6 os.nb file renamed it to windows.nb downloaded ATRE.zip unzipped the ARTE.zip file placed the windows.nb into the same directory, don't forget to edit UpgradeRom.bat file 0x3900000 to 0x3500000 with in the ATRE directory and copied and installed EnableRapi.cab to the phone. Reset it the phone and then started the UpgradeRom.bat! 12 mins later upgrade complete. Hard restart the phone.. Chewing nails by now... all went well did a soft reset of the phone before the O2 ExtROM autorun starts..
sorted, and did half way though a night shift at 3 am.. not bad at all!
Click to expand...
Click to collapse
Confused... is it really necessary to take all these steps? I thought that the only thing required is to run Pof's tool USPL, and after that run Romupdateutility.exe from the package in .nbh format (the link is just a few messages above yours). Please correct me when I'm wrong.

step by step guide
stunno said:
Any volunteers?
Click to expand...
Click to collapse
OK, I volunteered... This is a detailed list of steps how I installed a new ROM on my MDA Compact III (CID locked, at least I think so). It worked without any errors or problems. I used PDAVIET Black&Blue v2.0. It was my first flash on my Artemis, so I more than understand your need for step-by-step guide
1. download the file Artemis_USPL.zip
2. unpack into the folder c:\USPL
3. download the file ARTEMIS_Black_Blue_v2.zip
4. unpack into the folder c:\ROM
5. soft reset your phone and have it charged over 50% (I have it fully charged)
6. wait until the system starts on your Artemis
7. turn on flight mode (probably not necessary, but I wanted to minimize any risks)
8. connect your Artemis to PC with a USB cable
9. wait until ActiveSync icon in your tray (lower right corner of your windows desktop) turns from gray to green. If you connect your Artemis for the first time to PC, you do not need to set up synchronization, just click "cancel" on the first screen of "Synchronization Setup Wizard"
10. while ActiveSync icon is green, run c:\USPL\start_uspl.exe
11. a DOS screen will pop up with the text "Initializing: 0.." in the bottom indicating probably seconds from the start (it stopped around 70 in my case after about 1.5 min)
12. DOS screen disappears and PDA Phone ROM update utility pops up
13. at the same time, your Artemis turns blank (orange/green LED turns off as well)
14. tick the check box next to " I understand..." and then click Next
15. tick the check box next to " I completed..." and then click Next
16. a box saying "Verifying information on your PDA..." pops up
17. on the next screen click Update button
18. next screen says "Upgrade to ... image version 9.99" - click Next
19. Next screen says "You are now ready to update..." - click Next, a window with a blue progress bar appears with a text "Updating ROM image..", it quickly runs to 100%
20. next screen says "Congratulations! ..." - click Finish
21. your phone turns on and boots into your old system, however it should be CID unlocked now
22. your Active Sync should reestablish and icon turns green again
23. do not touch anything (phone or USB cable) and run C:\ROM\ROMUpdateUtility.exe (make sure activesync icon is green)
24. PDA Phone ROM Update utility window appears, tick the check box next to " I understand..." and then click Next
25. tick the check box next to " I completed..." and then click Next
26. a box saying "Verifying information on your PDA..." pops up
27. on next screen click Update button (says "Current information...")
28. next screen says "Upgrade to ... image version BnB2.0" - click Next
29. Next screen says "You are now ready to update..." - click Next
30. a window with a blue progress bar appears with a text "Updating ROM image..", your Artemis will have light gray screen with blue progress bar showing the progress of flashing - do not touch anything and wait (it took 2-3 minutes on my 3 years old PC)
31. next screen says "Congratulations! ..." - click Finish
32. your Artemis turns on and starts booting, you can disconnect it from PC now
33. the boot screen remains the same (T-Mobile in my case), so do not panic!! it is normal
34. wait until calibrate the screen appears, calibrate, choose time zone and you are ready to use your new OS
35. let me know if this manual was clear enough, whether it helped you and please suggest potential changes for improvement
Take care,
Dzim

i've just succesfully flashed my dutch CID-LOCKED MDA Compact 3 with this method, so i'd say it's reasonably fool-proof

A couple of questions before i take the plunge - if my t-mobile cmda iii is already CID unlocked, can i just go straight to the update rom part.
Also, is there any way of dumping my standard t-mobile rom first off? I'm having trouble trying to use itsutils due to the app lock.

Cheers Dzim!
Your instructions worked perfectly.
One very happy complete idiot here!

Furbious said:
A couple of questions before i take the plunge - if my t-mobile cmda iii is already CID unlocked, can i just go straight to the update rom part.
Also, is there any way of dumping my standard t-mobile rom first off? I'm having trouble trying to use itsutils due to the app lock.
Click to expand...
Click to collapse
There is a TMobile rom on here somewhere already, I just cant find it at the moment

My Compact 3 it’s death now. After pres voice commander button MDA start only to the boot loader. Can’t run complete system.
Pleas tell me. How can I write the new rom with WM5 or WM6 ?

OOPS! Working well apart from the "cant save word documents" bug!!

Just an update - to use the v1 or v2 black and blue, even though it is unlocked, you still need to use the supercid util.
Otherwise you get the rom update getting to 3% before crashing out to say the rom is corrupted.
I've now converted 2 other tmobile compact mda IIIs successfully, wm6 is much quicker

Yes, with my Compact was exactly as You say. Now is death. What I can do now to repair it.

big thanks to Dzim, used the idiots guide and now on wm6 =D
cheers!
PS: first post

Hi! Nemesis, try to connect your HTC to your pc in bootloader mode.
Lauch start_uspl.exe in USPL folder. Follow instruction on post N°9 by DZIM.
After USPL your HTC should reboot (maybe in bootloader mode only).
Launch the ROMUpdateUtility.exe in Black&Blue ROM v2 and follow instruction.

Thanks gguyaz
Pleas tell me.
Could I doing this upgrade with Windows Vista on my PC?

error [260] message every time

Firstly I would like to say thanks to this site and the trinityguides.info site for the great work people have being doing and making available to everybody, it is great being able to use my trinity with wm6, keep the good work going!
Now the issue I seem to be hitting the same "error [260] connection" every time I attempt to update anything on my Trinity. I have followed the advice on the trinityguides site regarding being stuck in bootloader mode to no avail, and I can't seem to find anything in the posts on the xda site which will rectify the issue.
Previously I have been able to update to AX3L v2.8.01 version without any problems, but I decided to update to sammy's ultra light, it initially kicks into des' crashproof sspl, but then it can't connect to the pc. even when I manually enter olipro's hard-spl it does the same. I have tried to re-install hard-spl, but can't. Disconnecting the usb option in the activesync settings doesn't do anything either. Does anybody have any suggestions for me please?
I am not even too sure if my trinity should have both Des' crashproof and hard-spl on it at the same time? Could someone advise me on whether this is alright please?
the tech details:
Trinity
AX3L_OS_v2.0.8.2
radio - 1.46.30 (even though it doesn't say this in the device info, or boot screen after soft reset)
Home PC - XP (just in case)

Did you also try flashing it again, the ROM I mean. I have this error also but as soon as I execute the ROM flash again it finds the device and starts flashing:
http://forum.xda-developers.com/showpost.php?p=1449597&postcount=2

I am assuming you mean flash with the new ROM, sammy's in my case?

yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)

No, I am in the same situation. The first attempt puts the device in 'ipl-sspl by des' bootloader mode then after about 10 seconds or so the error[260] is displayed on the pc. If I exit the ruu app and attempt again, nothing new happens on the trinity (i.e. it is still in Des bootloader) and the message is displayed again.

the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.

What operating system en activesync are you using?

On the PC I am using XP and Activesync 4.5

Check your connection settings to accept USB connections. Also, try using Hard-SPL 1.30 before flashing the ROM again.

deejacker said:
the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.
Click to expand...
Click to collapse
In your PC, try another USB connection.

BLOODY HELL!!! It is the simplest things which we often forget to try. Thanks Jotam for pointing out an obvious point, it must have needed a re-plug of the usb cable into another port for the pc to pick up the device again. I will remember that for future updates so I don't make a dumb ass of myself again. Thanks guys/gals.

Vista
Using Vista? if so which version?

Hi I asked this question yesterday, I am a noob :-[ but the only difference is I'm using Vista Ultimate.
Just for others who have the problem.
When you replug into another USB port (Luckly I've got two on my laptop..)
I used the Vista drivers from TrintyGuides and bingo !
now I try and flash a WM6.....English or Italian...maybe French.
Thanks for the help I keep you posted.
Richard

It works
Now to discover the joys of WM6 after only having WM5 for two weeks....

/i am getting the same only rom update 3.14.4.1 now sees the phone..
has the device name changed???
evene exploit no longer sees the phone

sorry, can you be a little more clear.. what ROM are you flashing, and what exactly is happening?
by the way... i thought error 246 was the connection error... am i mixed up? which is 260?

This seems to be on any rom bar the Dopod roms
and it says 260 connection error

Error 260 connection error - the phone is not going in to bootloader mode - and the RUU cannot seem to initiate communication with the phone.
I'm getting this a lot recently trying to flash.
However, Hold the power and camera buttons while resetting with the stylus (keep them buttons held down).
When you get to the bootloader - plug the phone in - wait till you see the USB at the bottom of the bootloader screen - then run the RUU again - it WILL work - every time.

I used to get this error message alot. sometimes the programs you install don't allow you to update even if you force the phone into bootloader mode so you have to hardreset the device and then upgrade.....hope this helps

htc diamond stuck
T-Rob said:
yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)
Click to expand...
Click to collapse
hi ,
my htc diamond stack, no respond on the screen i try to do hard reset with tree buttons but its not working, nothing happaned, screen stay home screen with the time and not responding touching the screen at all
please emergensy help

Newbie but I hope not !!! help btw !!!

I own a new blue angel...called by O2 II's
So, after i read ,again,and again...I have successed enter boot loader.
With white screen it's shown the version 2.07 and the line at the top "Serial"
(uhm, i use WM2003SE as the original pda when i purchase)
Ok, the problem now is, i can't flash anyrom (in Wiki and any rom i found)
After the line appear "Don't plug cable or craddle of ...." it's seem to verifie it's self... and then the line appear again "this tool is not support for this device".....and some error like that.
I was totally confused, how i made the thing go wrong? or just i missed something???
i make a soft reset, then hard reset and then 3 button together to get the white screen with no light, still see words such as: serial, version 2.0.7...
When i plug the usb cable , then the serial change into USB as usual.
As my experience,( Dopod810 and Qtek S200) everything is normal...
One problem too, i can't connect to PC with activsync (i tried any versions as possible)but itself avaiable on Boot loader...
All you understand what happen with me???
Please help me out of this. I want my Blue Angel is not the worst i got ...(i think it's possible go up to wm6???)
Finally, thanks you all for listening( reading this topic)

Yep, Happened to me too. Heres the fix.
The regular WM6 exe will give you an error everytime with the O2 IIs. Finally I printed out the WM6 directions, and also the Blue Angel for beginners and some other threads and found the answer.
You are in the right place (stuck in bootloader that is). Now you should be ready to load the OS. In the Upgrade folder you will find:
"MaUpgradeUt_noID.exe"
Run it and you will see the progress bars on the Windows screen and the dark XDA screen. Don't bother it - allow it to complete.
After it completed, I was unable to restart, soft reset, hard reboot. I think I actually had to take the battery off. When I powered it again I saw the Color Bars and knew it was good.
Good luck, Be careful. Try to be calm. I know when I was stuck in between Roms I was close to being a nervous wreck.

erh, one more message when i fkash rom...
This MaUpgradeUT novid erh something like this but this
" This tool is not support for my device" or somehow ...
I think i really stuck...
when itself verifie version of rom , i can't see both version appear on windows.
ie : version rom which is in PDA and version of rom which is in the OS i next to flash(want to flash).
So Confused . Anyway, thank for helping !!!

You are close!
Yea,
I Kept getting that too. Couldn't see both versions. Got a couple of different error messages. you are right where I was. you've got to find the upgrade exe. in one of the folders. My IIs was stuck in bootloader and I started that upgrade and it skips checking the IIs first and just begins to xfer the data.

crashed/frozen. wont boot (FInixNOver) - cant reflash!

Hi guys.
I was using the installed the FInixNOver 3.0.1 ROM onto my SPV M700 and it was great. I've had it for about 2 weeks without any problems.
Last night I looked at my phone, only to realise that it was completley dead. This didnt shock me to much because the battery was running low, and i decided to let it die completley before recharging it again.
I charged my phone overnight and switched it on this morning, but the phone would freeze at the 'FInixNOver' splash screen (the numbers at the bottom of the screen would appear overlaying the splash, but the phone wouldnt go pass this point).
The only way to turn off the phone from this state is to eject the battery. I have tried removing the sim card, turning it back on in as many ways as possible but to no avail. I am able to get to the TriColor test screen (im running IPL-0.50 / SPL-1.30.Olipro) but with all the custom roms available, they all use the ROMUpdateUtility which requires the phone to have established an activesync connection initially (but this would mean my phone would have to be 'on completley' - so this is catch 22.)
For the record, my phone/battery died while my wired handsfree was attached (dunno if thats of any interest to anyone or the rom baker).
But it looks like the only way i'll be able to flash my phone is by finding a way to install the .nbh file without using the RUU method. Because I can put my phone into test mode manually.... any help or guidence would be very much appriciated.
Thanks.

Ok can you get it into bootloader? power/camera buttons and reset?
sorry didnt read fully.
right get your device into bootloader first,
then open active sync (are you using xp)
then open connection settings and disable usb connection,
put your device into bootloader mode, then run any rom upgrade, i prefer the WM6.1 pdaviets from HERE (Username: PDAVIET / Password: pdaviet)

Your pda does not need active sync with ruu's, so no catch 22. if you turn off usb connection in active sync, you can still run ruu and it will be recognised, unless you are using vista, where you need to change your HTC SYNC drivers.

Thanks for your quick response...
Yes I can get into boot loader using the power and camera buttons (or holding the power and camera buttons when resetting the phone)...
When the phone is in boot loader mode, active sync doesnt even detect the phone anyway, but nevertheless, I have followed your instructions and disabled the USB Connection. (BTW, yes i am using XP)
The phone is still in boot loader mode, so now i try and execute the ROMUpdateUtility.exe and go through the steps, at the 1st step i tick the tickbox and click next, and the 2nd step i tick the tickbox and click next. (this step says DO NOT enter the bootloader manually? - but i have havent i?) anyway, when i click next, it says... "Verifying the information on your Trinity... Please Wait..." for about 10 seconds, and then i get a message "ERROR [260] : CONNECTION"
What am i doing wrong?

Huumm.. why dont you flash your phone throw the sd card??
Read this link:
http://wiki.xda-developers.com/index.php?pagename=Trinity_SDCardFlashing

try to flash your phone with some official rom and after that flash it with any other you want!

manos_23 said:
try to flash your phone with some official rom and after that flash it with any other you want!
Click to expand...
Click to collapse
I would recommend this option above, to be safe, i usually get them error messages when the battery is below 50% or sometimes i try it again and it works. it does state do not manually enter bootloader but i always do it this way.

also make sure active sync is not still running in taskmanager under the alais: wcescomm.exe and WCESMGR.exe, end them both.

I've just tried using an official ROM, but the problem still occurs with the 'connecting'. It doesnt seem that the computer picks up a connection to the phone whatsoever.
Should i be concerned that at the bottom of the bootloader screen it says "serial", is this correct?
Im starting to get annoyed now.

Bye,
the bottom of the sreen mast say "usb" not serial.

it seems there is a problem, if it states serial. as it should say usb. try THIS

Seems like the problem was that my USB lead was loose and made a bad connection, hence why the bootloader showed 'serial' and not 'usb'... as soon as i wiggled it and heard the 'connection noise' in windows, i knew i was good to go, and so using the RUU worked fine to reupdate my phones ROM.
Thanks for your help.
My only question is that why did it happen in the first plave?

WIZZKID - I just saw your post here now. I have to tell you that I also saw "SERIAL" at the bottom of the bootloader screen and not "USB". As I said I returned it to get another phone but maybe I will try something else for now instead of a P3600i. I will monitor your thread to see how it turns out for your phone, because it seems that we have the same problem.

if you see "serial" instead "usb" your problem is in the usb cable, usb port from your computer or in the usb connector from your trinity!!!!!
I was having the same problem that you have!! my problem was from my usb from mine trinity!! see if the conector is at good conditions !!!

Well as some of you may know, I got my Trinity replaced for sticking at the WM splash screen after a few days. This second one - I have had it ONE night - and the same thing has happened with incomplete booting. This time I have been trying all night to flash the phone to an official ROM, but I cannot do it (apparently) because I can't establish a connection via ActiveSync. When I stick the data cable in while in bootloader I see SERIAL replaced by USB and when I try the flash I get a "270" error (cannot connect to phone) and the phone re-boots to the sticking plash screen. What should I do now?

ladies and gentlemen...
we've got a lot of mixed messages in this thread.. please make sure you're posting the right thing. no need to disable USB when manually going in to bootloader to flash (at least in xp).. Also, you can ignore the part of the RUU that says 'do not manually enter bootloader' (you should really read the guide on my site)
foxuniform- can you please give some details..
1) are you running xp or vista
2) have you flashed hard-spl? if so what version?
in the mean time, try a couple of things.. first, flash hard-spl (even if you already have it, but from the sound of it i think you don't have it on your device).. if that works, try to flash an official ROM. Can also try to use splxploit, then flash hard-spl, and then flash official ROM (there's a guide on my site if you're unsure)
please post your results
*edit*
here are the steps for SD card upgrade, but i HIGHLY recommend flashing Hard-spl first..
try to do it from SD card. how?
Extract the .NBH file from your prefered ROM upgrade: In windows use winrar (right click) to extract the contents of the exe file. In Linux / MacOS use cabextract (http://www.cabextract.org.uk/) .
Rename the .NBH file to TRINIMG.nbh and copy it to the root folder of your miniSD card.
With miniSD card inserted on the phone, start the bootloader (hold Power button on right side and Camera button at same time and stick with stylus in RESET on bottom).
You should see the screen pictured on the left, confirm flashing on screen by pressing the power button.
Flashing might hang after some time but this is normal. Just wait. Complete flash takes about 30 minutes, so check your battery or connect to charger before the flashing process starts.
When flashing completes soft-reset your device.
Make sure your SD has FAT32 and has no label. There have been reports that if SD has a label the bootloader can not access the TRINIMG.nbh

racerx_ I have carefully read your response and suggestions, and thanks for your expertise input on the matter. I am fairly new to this stuff so read below carefully as you may find errors in the way I tried to go about doing what I was hoping to accomplish.
First let me answer your questions. I am running Windows XP. The phone is in it's completely natural state in that I have not flashed it in any way. The ROM I was TRYING to flash to the phone while it was not starting properly (this is where I manually entered bootloader) is an official ROM from the HTC website (please note everyone that when I registered my P3600i on the HTC website it came up as the Dopod 810). Anyway, that never worked. ActiveSync never detected the phone (and I guess that's the reason I could not do anything as far as flashing goes). I HARD-RESET my P3600i and it booted normally. I re-installed all the stuff I had on it, from memory card to various .cab files, and the phone is working beautifully thus far. I will report if anything funny happens again.
I have to ask you racerx_, if I CAN flash hard-SPL on the P3600i according to the lovely guide on www.trinityguides.info. I have been of the opinion that things don't work for the P3600i as they did for the P3600, and that has been echoed by many P3600i users on this forum who are ready and waiting to try out some cooked ROMs (myself included).
For the sake of record, my phone is running rom version 3.00.707.17 and radio version 1.46.00.11. I patiently await your response.

woaaahhh..
i didn't notice the 'i' in your previous post... yeah, as far as i know, these ROMs are not flashable on your p3600i.. sorry..
**correct me if i'm wrong somebody**

Yeah I kinda thought that would be your response. By the way - do you think that this phenomenon of sticking at the Windows Mobile splash screen (both the P3600 and P3600i models apparently) has anything to do with something users do with the devices, or you figure it's an inherent software glitch of some sort? I am wondering if I should try a different model or hold on to my P3600i? Hope it's not something that'll happen again - I fly for a living and it's not gonna be good to have the thing screw up on me away from base - I really count on it for everything from casual keeping in touch on Messenger to viewing my work schedule. I love the Trinity though - it's one of my all-time favourite HTC phones.

hmm... i don't think its inherent in the Trinity.. (not a hardware issue.. in my opinion)
its been a while since i followed the posts on it, but always seems to be software related.. sometimes ROM-specific problem. Personally, i've probably flashed as many ROMs as anyone and the only time i ever encountered problems was with the official HTC WM6 ha.. go figure.. I think ppl did find that hard resets before and after flashing are helpful as well..
i love my trinity, and there's not much else on the market to make me want to trade it in (is it just me, or have pda's kind of stopped getting cooler).. i'd stick with it..

Need desperate help with possibly bricked Diamond

Hi all,
Just received my Vodafone-branded Diamond, and I'm afraid I already managed to brick it!
It was equipped with version "1.37.172.3 NLD" so I decided to upgrade it to the latest version.
The installation of OliNex Hard-SPL 1.93 went flawless, but the installation of ROM "RUU_Diamond_HTC_WWE-ME_1.93.456.2_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe" stopped at about 25% with error code 302. The recovery method that came with the package didn't help, every time the upgrade stopped at the same moment.
Since the device is stuck in the bootloader, and I'm left with a non-chargeable battery, I tried the official Vodafone-branded "RUU_Diamond_Vodafone_NL_1.97.172.4_Radio_Signed_Diamond_52.44.25.24_1.08.25.08_Ship.exe" ROM. Unfortunately, this upgrade stops at 48% and throws the same 302 error.
Anyone who can tell me what I'm doing wrong, and what I can do to solve all this?
I hope I don't have a brand new, but bricked device on Christmas!
TIA and have a nice day.

Try a hard reset first. If this doesn't help google or search at XDA for MTTY.
This tool can fix your device

http://wiki.xda-developers.com/index.php?pagename=Kaiser_Stuck_at_bootloader
Try this, maybe will work

Try a Vodafone branded stock rom before mtty.
Regards,
Carty..

He already tried a stock rom....

Potential Solution
Have you looked at the thread titled,
[UPG][TRBL]How-to fix: Update/Flash doesnt work, stops at 0% or 5% (invalid model ID)
It may just be a model ID glitch that can me fixed.
Take a look. It's in this forum in a sticky by cptsunshine.

Thanks all for the help, I'll have a look at your suggestions.
The problem isn't that it stops at 0% or 5%, it stops at random percentages (depending on the ROM I use).
I also see the bootloader (red / green / blue), so it's not dead. I guess it's just that it doesn't pick up a ROM.
Besides, the bootloaders says upgrade ROM code error please try again.
Edit:
A hard reset doesn't seem to work. In the bootloader, when I press "volume down" and "enter" together, and press the "reset button" the screen goes black, but then goes back to the bootloader screen after a sec or 2.
Edit 2:
MTTY doesn't do much either, after executing "boot" the phone is showing me the Vodafone logo and that's it.
For the rest, MTTY shows me the following:
Cmd>boot
InitDisplay: Display_Chip=1
dwDirectNum: 0, dwMatrixNum: 0, dwMicroPNum: 0
Fixed new dwPSImageSize = 0x53E0000

Install Rom via Internal Memory Method
Steps from Suiller:
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
Let me know how it goes.
Make sure you have Net framework 3.5 installed on devices.

Nakkie27 said:
Thanks all for the help, I'll have a look at your suggestions.
The problem isn't that it stops at 0% or 5%, it stops at random percentages (depending on the ROM I use).
I also see the bootloader (red / green / blue), so it's not dead. I guess it's just that it doesn't pick up a ROM.
Edit:
A hard reset doesn't seem to work. In the bootloader, when I press "volume down" and "enter" together, and press the "reset button" the screen goes black, but then goes back to the bootloader screen after a sec or 2.
Edit 2:
MTTY doesn't do much either, after executing "boot" the phone is showing me the Vodafone logo and that's it.
For the rest, MTTY shows me the following:
Cmd>boot
InitDisplay: Display_Chip=1
dwDirectNum: 0, dwMatrixNum: 0, dwMicroPNum: 0
Fixed new dwPSImageSize = 0x53E0000
Click to expand...
Click to collapse
u can do one thing then press woluem down and reset bottom at the same time then u go to rescue mode then u wait and put in the usb stick and there stand seriel when u put in the cable it will change to usb thenu can load the firmware again

band27 said:
Steps from Suiller:
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!
Click to expand...
Click to collapse
I wish I could mate, but I cannot put files on it anymore, since ActiveSync doesn't recognize my device when it's in the bootloader.
janielsen said:
u can do one thing then press woluem down and reset bottom at the same time then u go to rescue mode then u wait and put in the usb stick and there stand seriel when u put in the cable it will change to usb thenu can load the firmware again
Click to expand...
Click to collapse
Can you please be more specific? Are you telling me how to do a hard reset? I tried as to do a hard reset, but it goes back to the bootloader instead of resetting. USB stick?
Thanks all, much appreciated. A pain this can happen, looking at the fact that I did everything exactly as described in all these flashing manuals.

Nakkie27 said:
I wish I could mate, but I cannot put files on it anymore, since ActiveSync doesn't recognize my device when it's in the bootloader.
Can you please be more specific? Are you telling me how to do a hard reset? I tried as to do a hard reset, but it goes back to the bootloader instead of resetting. USB stick?
Thanks all, much appreciated. A pain this can happen, looking at the fact that I did everything exactly as described in all these flashing manuals.
Click to expand...
Click to collapse
first push the volum down buttom at the same time press the reset buttom then the 3 color display will appear and in the buttom will stand seriel then u putt in the usb cable to ur phone whit u have attact to ur pc then it will say usb now u can load new firmware

janielsen said:
first push the volum down buttom at the same time press the reset buttom then the 3 color display will appear and in the buttom will stand seriel then u putt in the usb cable to ur phone whit u have attact to ur pc then it will say usb now u can load new firmware
Click to expand...
Click to collapse
No mate, I never had problems getting into the 3 color screen. The problem was updating afterwards, which never completed without error code 302.
Anyway, I guess I just fully bricked my device after putting SPL-1.40.OliNex (according to the guide at http://forum.xda-developers.com/showthread.php?t=416211) on it. The SPL install was succesful, but when booting I'm now not even getting to see the 3 color bootloader. All I see is the Vodafone logo with some version numbers at the bottom, but that's it. It doesn't boot further on, and I can't get a USB-connection.
Edit:
Volume down + reset brought me in the bootloader again, although it's saying SPL-1.93.OliNex.

Nakkie27 said:
No mate, I never had problems getting into the 3 color screen. The problem was updating afterwards, which never completed without error code 302.
Anyway, I guess I just fully bricked my device after putting SPL-1.40.OliNex (according to the guide at http://forum.xda-developers.com/showthread.php?t=416211) on it. The SPL install was succesful, but when booting I'm now not even getting to see the 3 color bootloader. All I see is the Vodafone logo with some version numbers at the bottom, but that's it. It doesn't boot further on.
Click to expand...
Click to collapse
that i know but as i say in the post that when u do it that way i say u can load new firmware whitout it needs to boot try my friend i have done it 3 times because wrong loading of firmware

u have to only push thoose 2 buttom then it will work because u go to rescue mode

But what will that give me extra? I can access the Hard-SPL 1.93 bootloader (3 color screen), and I can get into USB mode. It's just that the upgrade of both firmwares stop at a certain percentage.
I'm constantly trying to hard reset the device, but after pushing the reset button (with both volumn down + enter pressed down), the device just reboots back into the bootloader and doesn't give me the hard reset warning.

Nakkie27 said:
But what will that give me extra? I can access the Hard-SPL 1.93 bootloader (3 color screen), and I can get into USB mode. It's just that the upgrade of both firmwares stop at a certain percentage.
I'm constantly trying to hard reset the device, but after pushing the reset button (with both volumn down + enter pressed down), the device just reboots back into the bootloader and doesn't give me the hard reset warning.
Click to expand...
Click to collapse
u need to hold them down until it leave the 3 color display an turns into grey

Ok, finally managed to do a hard reset. Afterwards I tried upgrading to the official Vodafone NL 1.97 ROM once more, but it failed at 48% again.
Any ideas what to do? I know have Diamond with Hard-SPL 1.93 (which says upgrade ROM code error) with no working OS.

Ok all, got it finally working again!
Don't ask me why, but flashing the newest Dutty ROM (and the included radio) did work.
Thanks for all your help, and a wonderful evening!

Hi all,
I have a quit similar problem. I've read a lot, but couldn't find an answer to my problem - may bye someone can help me.
I updated my Dimond (OliNex Hard-SPL 1.93, radio 1.09.25.23 and rom dutty V4). When I start my phone most of the time (95% plus) I end up in the color screen - however some time it's starts perfect (without changing anything).
When I get stock in the color screen, I can start the phone with mtty and the command "boot".
What can I do to make my phone always start in the normal way?
Thanks!

Nakkie27 said:
Ok all, got it finally working again!
Don't ask me why, but flashing the newest Dutty ROM (and the included radio) did work.
Thanks for all your help, and a wonderful evening!
Click to expand...
Click to collapse
i smell a radio issue - last time i was trying to upgrade my radio - ended up with something similar, managed it out like you did - but now you're up - so that's good!!
try some other rom (this time without radio) - i don't think you should have any issues going forward... good luck and have fun!