Develop Bugs

ROM Upgrade problems - Device dead? HELP please.

I am a rookie at upgrading this stuff. I have a QTEK 9000. I got UNI_QTEK_13077_176_10900_WWE_Ship.exe from the ftp site.
1) Did a device reset.
2) Connected via active sync.
3) ran the program.
After a short period, The device shut off and active sync disconnected.
The screen is black. On button does not work.
I tried a hard boot and I get the boot menu and 0 or x does not seem to do anything.
Did I do something wrong? What now.

GaryK2 said:
I am a rookie at upgrading this stuff. I have a QTEK 9000. I got UNI_QTEK_13077_176_10900_WWE_Ship.exe from the ftp site.
1) Did a device reset.
2) Connected via active sync.
3) ran the program.
After a short period, The device shut off and active sync disconnected.
The screen is black. On button does not work.
I tried a hard boot and I get the boot menu and 0 or x does not seem to do anything.
Did I do something wrong? What now.
Click to expand...
Click to collapse
I think that program is supposed to be run after you've removed USB from the connection methods in activesync - i.e. you're not connecting via activesync, even though the device is physically connected.

OK, I tried the process again without activesync.
That seems to be the answer. ROM Is now installed. I just have to finish up.
Thanks alot,
That scared the hell out of me.

GaryK2 said:
OK, I tried the process again without activesync.
That seems to be the answer. ROM Is now installed. I just have to finish up.
Thanks alot,
That scared the hell out of me.
Click to expand...
Click to collapse
Hehee... when you get the new rom on, you'll love it...

GaryK2 said:
OK, I tried the process again without activesync.
That seems to be the answer. ROM Is now installed. I just have to finish up.
Thanks alot,
That scared the hell out of me.
Click to expand...
Click to collapse
Sorry for my silly question but how can you process it without activesync, mean you have removed activesync form your conputer?, because my activesync is automatic running when the computer start up
Thanks,
Orangevn

orangevn said:
Sorry for my silly question but how can you process it without activesync, mean you have removed activesync form your conputer?, because my activesync is automatic running when the computer start up
Click to expand...
Click to collapse
You're just telling AS to ignore the Exec when it's connected. The PC itself still sees it and adds a driver on connection. So you're not removing AS from the PC as such.

i have same problem but it doesn't work
please help me....this phone is dead now:-(

Re: i have same problem but it doesn't work
bmlsbr said:
please help me....this phone is dead now:-(
Click to expand...
Click to collapse
Did you try the AS thing above?

First off what do you on the screen of your device when you turn it on? Is it in boot loader screen, a black screen with text that says boot loader mode and serial?
If it is in boot loader screen and it says serial on the bottom, when you plug in the USB do you see the "serial" text change to "USB"?
I had this problem with mine. I upgraded my Qtek9000 with the new orange ROM and when the process finished I was still in the boot loader screen and could not get out of it. I had to re-flash it back to the Original Qtek ROM which revived the devices. I then started the ROM upgrade process all over again which resulted in a successful flash.
If you can answers some of the questions above I can try to help.

BTW, the upgrade process takes about 20-25 minutes. if it was any less then that you unplugged the device to early.
Plug device in.
• Start ROM upgrade process.
• The device will turn off and go into boot loader mode (the computer will lose connection to the device and unrecognized USB devices error will appear in your task bar).
• Wait until the device reconnects to the computer and the ROM upgrade starts.
• This process will take 20-25 minutes.
• Reset the device with option 0 (erase all data)
• The device will boot normally and go through the extended ROM application installs. It will ask you to reset again.
• After the second reset you are done.

xda exec upgrade (dead phone)
tHIS ALSO HAPPENED TO ME (IT WAS PRETTY SCARY) . i DISCOVERED THAT I COULD GET IT LIVE BY PRESSING THE LIGHT BUTTON THE POWER BUTTON AND THEN SOFT RESET (THIS IS THAT BOOT MODE) .
THEN I RE-CONNECTED TO MY PC AND RE COMMENCED THE UPGRADE...WORKED FINE. I HAD ACTIVESYNC RUNNING WHEN I DID THE INTIAL UPGARDE, PROPBABLY THE PROBLEM!! :wink:

none of this worked....may be I am not doing it right
when I try to add hard-reset all I get this is this:
"press 0 to restore factory default"
"press X to exit"
When I run the rom update, I get device connection problem error message and sometimes the country id error message.

none of this worked....may be I am not doing it right
when I try to add hard-reset all I get this is this:
"press 0 to restore factory default"
"press X to exit"
When I run the rom update, I get device connection problem error message and sometimes the country id error message.
my yahoo and msn id is bmlsbr...please someone chat with me and provide some help. I feel helpless after spending all the money and the phone dead after i day of use.
please...........

here is what I am getting
I can not turn my device on at all.

I'm unclear to what you are saying. First you tell us that the device does not turn on. Then you say you are getting the 0 X option. Which one is it? If you are getting the O/X option what do you see on the screen when you press 0. Do you see the device in boot loader mode? You might have to remove the battery and try the reset button after. my experience has been when the device is in boot loader mode I cannot turn it off. It always stayed on. So you might want to charge it just to make sure you have full power. I would also use the ROM loader without the country and device ID restrictions you can download it from the FTP site.

QTEK 9000 DEAD
I was always able to get the hardware reset menu..but nothing happened beyond that.
Now the phone is working after multiple tries to put the rom. But active sync won't work. Any clues????

What do you mean by works? Did you load the ROM?

Have you tried to follow these instructions:
http://forum.xda-developers.com/viewtopic.php?t=43592
Seems to work for a few people.

i'm gonna kill myself..3 my friends Jasjar plus 1 qtek dead

Please guys..could anybody help me??error 150 rom upgrade utility error
this rom upgrade utility does not design for your device...
I tried everything but i can't make it works...the window is always the same ... :shock: error 150 rom upgrade utility error
this rom upgrade utility does not design for your device...
MaUpgradeUt_noID doesn't work...
PLEASE PLEASE PLEASE...thanks
mik111

Did you tried hard reset it?

First, don't get panic! Well.When I tried to unlock my device and make it Super CID that message appeared in my screen too.I tried anything I was told in this fantastic forum and nothing worked.Finally I was told to reinstalled windows on my PC and...it worked!! I think it's a problem of drivers. If you are desperated try it.
Good luck and be the force with you...

may the force be with you! :lol:
but like alberbrando said, don't panic. panic would only make things worse. try re-installing your windows. Hopefully, that should resolve your problem.

???
gtm55 said:
Did you tried hard reset it?
Click to expand...
Click to collapse
hi guys..i tried to hard reset it but nothing happend..i'm very depressed...how can it be possible??i've already done this operation with this pc..and it worked..is that possible ?drivers?reinstall windows??****..is one of the of the worst boring operations i've ever done..
any other ideas?

http://forum.xda-developers.com/viewtopic.php?t=61002

frz said:
http://forum.xda-developers.com/viewtopic.php?t=61002
Click to expand...
Click to collapse
thanks frz..i've hard resetted...nothing happend...

So do the other thing they told you and reset windows.
Which is worse? a few hours boredom of backups and reinstalls, or spending what. . . 1300. . £2600 on new PDA's for you and your friends?
I know which one I'D pick.

Try
Try with this upgrade Tools
-put nk.nbf file on this folder
-put your device to bootloader mode
-deactive active sync on your computer
-connect to USB
-Run upgrade tools
cheers
indra9110

Right, don't panic, not being able to flash isn't such a big deal.
First, get an official update package for your QTek, and for your friends an I-Mate update package.
Next, hold the power button and the light-button (next to the volume slider), and stick the stylus in the little reset hole in the back. Hold the keys for a little longer, untill you vaguely see "Serial" or "USB" on the bottom part of the screen (put a little light on the screen, as the backlight will not be lit).
At this point make sure it's connected to your PC through the USB cable.
Right-click the MS ActiveSync icon (on your PC) and choose connection settings, make sure "Allow USB Connections" is unticked.
Next run the update utility, and everything should be fine again
If this doesn't help, ask again and state clearly that you've tried this already.

TheBlasphemer said:
Right, don't panic, not being able to flash isn't such a big deal.
First, get an official update package for your QTek, and for your friends an I-Mate update package.
Next, hold the power button and the light-button (next to the volume slider), and stick the stylus in the little reset hole in the back. Hold the keys for a little longer, untill you vaguely see "Serial" or "USB" on the bottom part of the screen (put a little light on the screen, as the backlight will not be lit).
At this point make sure it's connected to your PC through the USB cable.
Right-click the MS ActiveSync icon (on your PC) and choose connection settings, make sure "Allow USB Connections" is unticked.
Next run the update utility, and everything should be fine again
If this doesn't help, ask again and state clearly that you've tried this already.
Click to expand...
Click to collapse
Thanks Blasphemer but i've done that 2000 times with no success at all...i think that entirely rebuild the pc is my last chance... I don't wanna think at what will happen when the same old window will came out...I' m preparing my gun... :shock:

b4 attempting to flash
b4 attempting to flash,
chk if the 3 steps with mtty work,
if u don't get any error,
plz get ur battrey charged fully from a friend.
then attempt a flash by downloading a different rom from the one u r presently using
disable ur pc firewall
also disable ur anti virus [dont know if this is really required...but i read it in quite a few forums & it worked for me...]
flash only the rom
no extended rom or radio
use the MaUpgradeUt_noID
hopefully this should sort out ur problem....
i know coz i had the same problem....
frz

Another suggestion....
before making any other test, if it's possible, try on another PC, using a fresh rom (not the same used...) .... can be a PC problem, so test the procedure on another host ....

... sorry, again...
have you checked the bootloader version on the devices ? ... verify it before any other tentative ....

htc s620 stuck at startup

Hi,
My S620 is stuck at the startup screen showing just the htc logo and won't go any further. Anyone know how I can fix this?

Try to remove the battery, the SIM card and the memory card. Just insert the battery and try again. This worked for me.

It does not work:-( Anyone know how to put directly into bootloader mode?

Or anyone has any other tip?

bump anyone have an idea why mine stopps at the htc screen at start up?

Hard reset?
Did you tried hard-reset? You need at least one previous sync sesion, or you will loose everything stored on the device.

I tried that. Not working;-(

It does not react at keyboard pressure at all;-(

surfer said:
Hi,
My S620 is stuck at the startup screen showing just the htc logo and won't go any further. Anyone know how I can fix this?
Click to expand...
Click to collapse
which rom did you use and have you unlocked it with Imeicheck ?

jhwo99 said:
which rom did you use and have you unlocked it with Imeicheck ?
Click to expand...
Click to collapse
The WM6 rom and it was unlocked through imeicheck. Any ideas?

surfer said:
The WM6 rom and it was unlocked through imeicheck. Any ideas?
Click to expand...
Click to collapse
I had a similar problem and Imeicheck helped me out.
"Plan B" worked for me.
I hope this will help you.
A) flashing ANY new ROM as CROSS-MODEL-ID update
B) Fix the "Data crashes"
In case you have problems please indicate the step letter/number which is not clear / not working for you.
Just do EVERYTHING EXCAT STEP BY STEP and everything will work.
---------
A)
Please do it EXACT step by step like described now and it will work (it is ESSENTIAL that you do it EXACT STEP BY STEP)
0) turn off antivirus/firewall/everything else running in background
1) start phone in windows, connect active sync (green circle in system tray of your pc)
2) start the unlocker (phone screen will turn white, active sync will disconnect, THIS IS NORMAL)
3) when asked for KEY-FILE or COMM ERROR#1 comes up WAIT 2 MINUTES (DON'T TOUCH ANYTHING)
4) DO NOT TOUCH PHONE AT ALL for ALL the next steps!!!
5) remove USB cable
6) close the unlocker on PC
7) reconnect USB cable
8) unpack the "RUU_Excalibur_TMO_US_1.20.531.1_4.1.13.34_02.79.90_Test.exe"
(right click on the .exe and select "Winzip->Unzip to folder..."
9) in the extracted folder you will find a file called like "RUU_signed.nbh" (.NBH), open it with HEX EDITOR (e.g. HexWorkshop) and locate the string like "EXCA20000" near the beginning of the file. Change it to "EXCA****" (all without the quotes, overwrite the DIGITS with STARS)
10) in the extracted folder you will find a file called like "RUU_Update.exe", open it with HEX EDITOR and SEARCH the string "BsaD5SeoA" and OVERWRITE it with "IMEICHECK" (all without the quotes)
11) start the just edited RUU_Update.exe now and make the ROM update (screen of phone will stay white ALL THE TIME, THIS IS NORMAL)
12) wait till update is complete and phone will start with the new ROM
13) To fix the "Data Crashes" problem just make a COMPLETE run of the unlocker (see B) ) and you are done.
---------
B) To fix the "Data crashes" you only have to make a COMPLETE run of the unlocker.
Please do it EXACT step by step like described now and it will work (it is ESSENTIAL that you do it EXACT STEP BY STEP)
0) turn off antivirus/firewall/everything else running in background
1) start phone in windows, connect active sync (green circle in system tray of your pc)
2) start the unlocker (phone screen will turn white, active sync will disconnect, THIS IS NORMAL)
3) when you get COMM ERROR #1 WAIT 2 MINUTES (DON'T TOUCH ANYTHING)
4) DO NOT TOUCH PHONE AT ALL for ALL the next steps!!!
5) remove USB cable
6) close the unlocker on PC
7) reconnect USB cable
8) start unlocker again and now it will complete the unlock
9) at next start the "Data Crashes" will be away.

surfer said:
The WM6 rom and it was unlocked through imeicheck. Any ideas?
Click to expand...
Click to collapse
Is your problem solved ?

jhwo99 said:
Is your problem solved ?
Click to expand...
Click to collapse
I can acess the bootloader now. So all i've to do is to find an official WM5 rom to try and flash back again. Any ideas?

surfer said:
I can acess the bootloader now. So all i've to do is to find an official WM5 rom to try and flash back again. Any ideas?
Click to expand...
Click to collapse
You van find the WM5 rom in this forum, but i suggest to install the Russian HTC rom. This works great (for me).
I work with all the options in the telephone, the whole day. Without any problems !

s 621 stuck on wm6
hello
Need Help pls! my new htc dash has stucked on the wm6 logo, active sync does not recognize the phone . it happened after ive installed on phone language extender
could any1 help pls...?
thnks

Ok this is what you do, hold down the camera button located to the right of the space bar for like 10 seconds, then while still holding it own plug the USB in and you should see the menu come up with three colors. This is where you load your original ROM and if its T Mobile you can get the rom from the website.

s 621 stuck on wm6
thank you very much for ur reply. i got the 3 color on screen. pls advise meaning of "flash..." pls note im not a t mobile member
thank u so much for helping

Oh ok I can get that rom for you, well flash means to install. Let me ask you one quick thing is your phone tmobile branded. Like does it have the tmobile logo on it or not.

s 621 stuck on wm6
nop
the phone aint branded
i actually got wm6 and when i try to install it the black window says there s no device connected..

Um... Well use this file to reflash it okay. Make sure that the tri-colored screen is on when you try to install the rom (reflash means install ok)
http://rapidshare.com/files/7886560...S_1.33.422.1_4.1.13.51_03.07.90_Ship.exe.html

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

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..