Related
I need help desperately. When I turn my phone on - it shows a tri-colored (Red-green-blue)screen (with small white at the bottom)
My phone was working just fine - but when I turned it on yesterday - it showed this wierd screen. In the top right corner, it says: RUU
In the red section it reads: IPL 2.26 & below that it reads: SPL 2.26
When I try syncing it - the computer does not recognize it. What can I do? I've looked at the site and searched for a solution. I stayed up almost all night trying to fix it, using MTTY (but no response from the phone). The only thing it does is show USB, when I plug it into the computer.
Other than that - nothing happens. I'm very exasperated. Can someone help me out?
Thanks
Have you first of all tried hard resetting the device?
If you have to no avail then the fact that your PC can still establish a USB connection with your device (Hence USB displayed in the bottom left of your device's screen)means you should be able to download the latest MDA rom update from the T-Mobile site and re-flash your device to get it back on it's feet. There is plenty of advice on the boards on how to re-flash and it is quite straight forward with the original signed ROM's (no unlocking required)
I hope this helps you in some way and if anyone can provide a link to the download needed please chime in.
C.
Did you try flashing a new ROM recently? A failed flash can cause that to happen. If not, download T-Mobiles ROM and reflash it and it should go back to normal. Unfortunately that means you'll lose any info that you had on there so hopefully you have it backed up. Before you do that though, make sure it's not doing that because you're accidentally pushing the camera button in while your rebooting your phone. I can see where that would happen accidentally because I'm constantly looking down at my phone only to notice the cameras activated because I accidentally hit that button.
Thanks a lot. I'll give it a try and see what happens
I can't get activesync to connect w/my device! Everytime I try - no luck. I've tried the MTTY and still nothing. Can anyone suggest a way for me to use? When I connect the MDA to the computer - it registers in my device manager, but Active sync won't identify it??!???
You do not need to be connected to active sync (if you're in bootloader mode) to flash an original signed ROM. Just connect you device to the PC, If your device has the tri-colour bootloader screen with USB listed in the bottom left hand corner of the screen (like you said in your first post) you should be able to reflash. Just run the Installer that you have download from the T-mobile website and it should perform the reflash. Forget about active sync for the moment until you get your device up and running again. It really is quite a simple operation. If this does not work for you, you're device might have a genuine fault. I feel confident it should work though as i have been in this situation myself with the MDA-Vario.
P.S What type of device do you have and which country are you in? This may enable me to help you a little more in finding the correct ROM if you don't already have it.
Do let us know how you get on
Cheers
C.
I have the MDA and I live in the USA
thanks for all of your help. I'm still trying - but nothing seems to be working
Did you download the T-Mobile ROM from their site and try to reflash it? If you did, what happens when you run the update exe?
Don't worry about not connecting to activesync right now, if you're in bootloader mode it wont connect.
Here is a link to the T-mobile MDA (USA) Get Software page. you'll have to enter your phone number to get the software you need. Its a big download (Approx 50MB) so be patient. There are also instructions on how to perform the upgrade there.
Good Luck and let us know.
C.
http://www.t-mobile.com/wmupgrade/
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
Any help would be great....
I have a MDA Compact III issue when trying to upgrade to the ARTEMIS TOUCH 2.1 or 2.0 software
Unfortunatly, my pda was at 49% charge when i first tried, so stage one got to the end, then told me to charge my fone more and ended.
Thus i charge the fone to 75% and re-started. However, upon reconnecting the fone to commence the restart, the USB device was not recognised.
After removing the Active Sync and indeed the USB Driver from the PC and re-installing it, the conenction was re-established, however, it now often drops the connection. Plugging away, i tried the install Step 1 once more, and upon getting to 100% in the cmd part, and then progressing through the wizard, whereby the PDA displayed the progress bar reachinbg 100% (of the unlock stage) the PDA then reboots, and the connection is lost...and doesnt re-establish itself....and then the wizard reports Error [270] : Update Error The image file is corrupted. Please check your update Utility
Now, i have tried various sources for the software, and indeed tried both 2.0 and 2.1.....
Now i have a PDA that intermittantly drops its USB connection (and needs the USB removed and re-added on the PC) and is now slower than it was, plus never got to step 2 to get the software on iot.....
Can anyone help? Else i have a broken phone so to speak.....
Thanks alot in advance
Paul
paulcharles1 said:
Any help would be great....
I have a MDA Compact III issue when trying to upgrade to the ARTEMIS TOUCH 2.1 or 2.0 software
Unfortunatly, my pda was at 49% charge when i first tried, so stage one got to the end, then told me to charge my fone more and ended.
Thus i charge the fone to 75% and re-started. However, upon reconnecting the fone to commence the restart, the USB device was not recognised.
After removing the Active Sync and indeed the USB Driver from the PC and re-installing it, the conenction was re-established, however, it now often drops the connection. Plugging away, i tried the install Step 1 once more, and upon getting to 100% in the cmd part, and then progressing through the wizard, whereby the PDA displayed the progress bar reachinbg 100% (of the unlock stage) the PDA then reboots, and the connection is lost...and doesnt re-establish itself....and then the wizard reports Error [270] : Update Error The image file is corrupted. Please check your update Utility
Now, i have tried various sources for the software, and indeed tried both 2.0 and 2.1.....
Now i have a PDA that intermittantly drops its USB connection (and needs the USB removed and re-added on the PC) and is now slower than it was, plus never got to step 2 to get the software on iot.....
Can anyone help? Else i have a broken phone so to speak.....
Thanks alot in advance
Paul
Click to expand...
Click to collapse
well, I'll just try to give you some suggestions as I don't know much about MDA Compact III ,it does not fall in the category of wizard,it's a Magician device and I'm a wizard k-jam user. anyhow as a general of upgrading is to have your battery fully charged or atleast must have more than 70% charge.cuz during flashing in RUU upgrade mode,it does not charge,so if while during flash something goes wrong or it takes more time to flash,it shud have enough power to go through the whole process.if it does not have enough power to complete the process,it fails to flash properely and thus have a bad flash creating problems.so same has happened with u, you have a bad flash
well in wizards we have certain methods to revive the device or recharge the battery,i have no idea about your device,but can only suggest get the battery charge,secondly your usb connectivity problem is also due to the bad flash,cuz as there is no OS info on the device,it wont be able to establish the connection,which windows are you using,try to upgrade with winxp sp2 and active synchronize ver 4.5
as i have no idea about Magician upgrading method so wont comment further,but advise you to look in the below thread,it might be helpful,cuz its about Magician MDA Compact III
As your posting in the wring forum you might not get much help here,ok
http://forum.xda-developers.com/forumdisplay.php?f=276
good luck
thanks
thanks for the reply. Got it working - used 2.0 to unlock it, and 2.1 for the actual rom upgrade...
I've searched but can't find the answer to this one - sorry if I've missed it somewhere. I have an unmolested T-Mobile UK MDA Vario 2 and I'm trying to install the official TM UK WM6 upgrade ROM.
On my desktop PC (which is properly paired to the phone through ActiveSync to sync with Outlook etc) running the exe results in a grey box with red text saying "Checking files on your PC" forever unless I unplug the phone. Then it will eventually launch the wizard. If I plug the phone in again and wait until it's synced and "Connected", the wizard will go all the way through to checking the existing version and starting the upgrade. However, when the upgrade starts the progress bar stays at 0% and the phone turns off!! Eventually it times out with a 260 error, and no changes have been made to the phone. The PC is running XP, but the only fixes I've seen for the 260 error are if you're running Vista?
I've also tried on my XP laptop - this isn't paired, so the connection through Activesync is just as Guest. The update still does the strange thing with the "Checking files on your PC" box if the phone's plugged in, but unlike the desktop PC the RUU won't talk to the phone at all - connection error before it can even verify the existing ROM version.
Can anyone help? I've been waiting for months to get WM6!
Cheers,
Tim
Phone just turns off?
OK, so now I've done a hard reset on the phone, paired it up to my XP laptop and told it not to sync anything. Now I get to the same stage as I do on the desktop - i.e. the phone switches itself off when the upgrade begins (at 0%), then the RUU times out with an error 260!
One odd thing I noticed is that if I plug the phone in with "Advanced network functionality" enabled (which it is by default) the PC tries to connect it as a new 10mb network card!? However, the RUU does the same thing whether this is enabled or not.
Getting desparate for help now - I've tried 2 different machines and even cleared the phone completely, what more can I do?
Cheers,
Tim
Try flashing from an sdcard. There are quite a post on it here, if you do a quick search you should be able to find the information and hopefully get your device upgraded.
It might be worth installig spl V7 from here before hand just in case anything goes wrong.
http://forum.xda-developers.com/showthread.php?t=296722
Working!
Thanks for the reply. Finally got it flashed using the instructions from here:
http://forums.cingular.com/cng/boar...thread.id=42389&view=by_date_ascending&page=1
Basically, you have to:
- Connect using Activesync and let it finish syncing.
- Start RUU.
- Activesync will close - ignore it and carry on.
- Eventually the phone will go into debug mode.
- Continue through the wizard - it won't be able to identify the existing rom version but this seems to be normal.
- Let it finish!
I was fiddling when Activesync closed - strangely, by disconnecting, restarting AS and reconnecting the wizard carried on and even identified the existing rom properly! It seems that it needs AS to connect to the phone initially, then it closes AS but keeps the USB connection open for the update.
Hope that helps anyone else with the same problem.
Cheers,
Tim
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..