Related
Hi,
I am in the process of upgrading my rom using the rom upgrade from the o2 www site.
Its been stuck on the
'checking the information on your device....Please wait.....Please do not disconnect your device from the PC or power supply until the upgrade is complete'
window for some time now. I dont know if its hung / crashed or in the middle of upgrading.
I dont want to chance it by removing the unit from the sync cradle but at the same time i dont wanna just leave it there for hours if its not doing anything.
Can anyone help ?
Steve
ps - the window I am speaking about came after the big window stating what your current rom / radio stack was and what they would be updated to giving you the option to click 'update' or 'cancel' I chose 'update' and got the message which I described earlier
Try this on a different PC...I'm assuming the phone itself is still functioning.
I had this a while back with the XDA2 and found that by attempting the upgrade on a laptop I had, it worked great without the hang.
I would then remove ASync completely (including registry items) and then reinstall it.
Cheers
Ant
I had this happen, I just shut down and restarted the installer program
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
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..
Hello,
My HTC 3300 is blocked on Windows start screen.
I have hard reboot my device and un screen with 3 color appear.
When i plug my device with USB cable, my computer play a song to inform my device is well connected.
But when i launch Artemis USPL, a popup appear with the message : "No Device Connected : Would you like to try copying again ?" Yes, No, Cancel.
I'm blocked a this step.
Can you help me ?
Thx
PS: Sorry for my bad english. I'm french guy.
hi guys,
i have the same problem....
I was trying for the first time to upgrade my Artemis!!! I DIDN'T DO THAT!!!!
Please help me!
TNH
USPL only work if you are in WM. It doesn't work at the booloader.
Zecanilis said:
USPL only work if you are in WM. It doesn't work at the booloader.
Click to expand...
Click to collapse
yes... i know
i am reading.... i am looking for a solution.
I read on the POF USPL guide that probably (Unfortunately ) this problem should be caused by same PDAmobiz tool!!!!
i am being funny!!!
yet another bricked artemis owner
Hi…
Newbie as I am I’ll try to explain to you what you should do...I’ve bricked mine artemis()but I think it is more related to hardware issue. You should try this:
1. Download mtty
2. Disable usb in active sync
3. Bring your Artemis to boot loader(pres start record +start phone+ reset)
4. Start mtty, choose usb and you’ll get popup up screen with direct access to your device.
5. Type this in command line of mtty (NOTE-YOU MYST TYPE IT/NO COPY PASTE WORKS)
Password BsaD5SeoA
6. You’ll get %indicator bar on your phone and then you can switch off mtty(do not disconnect your phone!!!)
7. Just start your ROM upgrade (it has to be factory rom if your phone is locked) and you should be ok.
(You need to have downloaded your original factory rom...For me it was O2 UK...do not start until you have it all)
If it fails, or you get some error massages, repeat all from point 2. Or follow on screen instructions...recovery etc...
If it fails,repeat,repeat,repeat....
Hope it will help you and save you from reading s... load of threads!!
P.S.
I’m still trying to bring mine to life….
zikizile said:
Hi…
Newbie as I am I’ll try to explain to you what you should do...I’ve bricked mine artemis()but I think it is more related to hardware issue. You should try this:
1. Download mtty
2. Disable usb in active sync
3. Bring your Artemis to boot loader(pres start record +start phone+ reset)
4. Start mtty, choose usb and you’ll get popup up screen with direct access to your device.
5. Type this in command line of mtty (NOTE-YOU MYST TYPE IT/NO COPY PASTE WORKS)
Password BsaD5SeoA
6. You’ll get %indicator bar on your phone and then you can switch off mtty(do not disconnect your phone!!!)
7. Just start your ROM upgrade (it has to be factory rom if your phone is locked) and you should be ok.
(You need to have downloaded your original factory rom...For me it was O2 UK...do not start until you have it all)
If it fails, or you get some error massages, repeat all from point 2. Or follow on screen instructions...recovery etc...
If it fails,repeat,repeat,repeat....
Hope it will help you and save you from reading s... load of threads!!
P.S.
I’m still trying to bring mine to life….
Click to expand...
Click to collapse
It solved my problem: I've played around with some dll's on my Artemis and it won't boot anymore.
Just one thing: you must type password BsaD5SeoA, cause it's case sensitive.
THANK YOU VERY MUCH!!!
Hi guys,
i fixed my problem!!!!!
i flashed an official ROM (1.12.405) using a SD card (512mb)
now i'm going to work with ARTEMIS_USPL!!!! WOOOOWWWW
owner of a brick called artemis
glad it helped you solve problem...
when I was young I use to poke with programming...
but that was looooong time ago (remember zx spectrum?48 kb ram..haha)now you got it in your pocket(working if you're lucky guy, not like me)
Any way, point is:
never give up!!!!
Yes, I agree with you: NEVER GIVE UP!!!!
I'd like to help you, i'm not expert people on this work...
I just read a lot of good indications on this forum.
Good Luck
Thanks man,
I'm trying to find another motherboard,before I start playing with this one.
Maybe you know where to get one for artemis?(arte 200)Or someone with broken screen not willing to repair it?
cheers,
z
Hey I would like to have sense 2.5 on my tilt too, but i really have no clue where to download it or start, help plz
I've read all the howtos and I tried flashing a 2.5 rom i found(i think its the right kind) and I keep getting error 262
Did you flash hardspl? What rom are you trying to flash? I suggest trying energy rom leo.
If by flash you mean download and run it on my computer then yes and the energy leo is the one i tried
When I click on the leo customRUU I get "windows cannot acces the specified path device of file. you may not have the appropriate permission to access this file "
http://forum.xda-developers.com/showthread.php?t=550540
I alrdy read that a few times over
"Flashing via ActiveSync with USB Lead (thanks to OliNex)
1. Download HardSPL package from *HERE* and extract to an empty folder
2. Synch Phone with PC in Windows Mobile!!! It has to be connected to activesync or WMDC via USB cable and it must not be in Flight/Airplane mode (i.e. radio should be on)
3. NEW: Internet access is required as the program checks online for updates and license
4. Run Rhodium-HardSPL_V2_00R3.exe on PC, make sure it's launched from a local drive (not through network drive, etc.). XP requires Admin logon and Vista/Windows 7 will automatically prompt to allow it to run in Admin mode, allow it. If you get an AntiVirus warning please ignore it, it contains no harmful code (just used a packer to compress it)
5. Follow steps as prompted in the HardSPL program. If this is the first run of HardSPL on a device after Hard Reset, you must select Automatic Flash Mode (first button in Welcome Screen)
NOTE: You should usually go for Automatic Flash Mode. The Manual Flash option is only to be used as noted below and you must only attempt the Manual Mode option if Automatic Flash Mode or SSPL-Manual.exe already put device in black screen. Any other errors triggered while running in Autoflash Mode will have to be fixed as instructed in the error message.
6. It will ask you to wait while it prepares for the flashing, press OK
7. Now it should go through without any error messages, if one does pop up then follow the instructions included in the error text. If no specific instruction is shown then ask for help in the thread, but this should not ever occur (as this means a really fatal error occurred)
8. At this point the phone hopefully went to a black screen (reporting version as 1.01.C-SSPL only using "info 7" in mtty), this is the SSPL version, which is temporary. Then RUU will instantly launch
9. NOTE: When RUU says it will Hard Reset do not worry, it is not going to do that. Also when it says the flash will take 10 minutes ignore that, it will only take a minute or so
10. SPL flashes, device automatically reboots, job done"
So im here asking for help
did you download the package from "here" in the directions first and flash that before going onto a custom rom like nrg's?
yes i did.....
never ran into any problems myself so i dont know whats up but have you tried on another computer? flashed through sd card?
Dragonmaster0430 said:
Hey I would like to have sense 2.5 on my tilt too, but i really have no clue where to download it or start, help plz
Click to expand...
Click to collapse
Ok, which device are trying to flash? Does tilt too mean "Tilt 2" or "tilt also"? If you are talking about a Tilt, you are in the wrong forum. This is Tilt 2 (Touch Pro 2/Rhodium).
WillardZ said:
Ok, which device are trying to flash? Does tilt too mean "Tilt 2" or "tilt also"? If you are talking about a Tilt, you are in the wrong forum. This is Tilt 2 (Touch Pro 2/Rhodium).
Click to expand...
Click to collapse
Wow...i mean tilt 2 ... XD
Dragonmaster0430 said:
Hey I would like to have sense 2.5 on my tilt too, but i really have no clue where to download it or start, help plz
Click to expand...
Click to collapse
i had this pb a few time ago, and as I remember, I solved it just by changing the folder where RRU AND NBH files where. try installing from an other folder...don't know why it works for me