Related
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..
I'm the newbiest of them all, I think I bricked my brand new Excalibur!!!
Sorry if I'm posting in the wrong place, but I need heeeelp!
O.K., here it is:
I just downloaded kavana's 080314 WM6.1 installer for the HTC Excalibur, I ran the exe and followed instructions, afterwards, the ROM app opened and started upgrading the phone but it got stuck at 1%, it made be go thru the recovery process several times (unplug, turn off, disconnect battery, turn on) but it always started on tricolor mode and always got stuck on 1%, after a third recovery process the ROM app just quit and left me hanging on tricolor mode!!!
Activesync won't connect now, I try to run kavana's exe again but it doesn't recognize the phone either, the phone is on, conected (windows makes the usb sound for connection) but it is not recongized, it's as if it's not plugged.
It is stuck on tricolor mode and I don't know what to do!
Please help me!!!
Try the dicussion thread "Bricked my T Mobile phone" there are plenty of answers there.
Will this work?
I saw this on said thread, but I presume it applies for a Herald phone, will it work?
The tricolor mode is "bootloader mode"?
Isn't there some sort of restart that can fix it?
Can someone elaborate on this? I'm really a super-noob!!!
"Try a SD card flash to unbrick your device
This is how:
MAKE SURE THE HERALD IS FULLY CHARGED BEFORE STARTING THE PROCES
#01 Download your original RUU
#02 Download (if not yet installed) WinRar and install
#03 Copy your full sd micro card to your harddisk and format your card with FAT 32
#04 Rightclick the downloaded exe file with your original RUU, click Unpack here
#05 In the map the will be created you will find a file (or similar) called RUU_signed.nbh. Copy this file to your formated sd microcard.
#06 Rename the file to Heraimg.nbh
#07 Get your Herald into bootloader modus by pressing the comm manager button and the camera button and pressing the reset button at the same time. Do not release both buttons until your in bootloader.
#08 Once in bootloader pop in your sd micro card.
#09 As soon as your card is popped in the screen will say something like "Reading SD card". Wait it out till it says "Push button to start" and slide the indicated volume slider down.
#10 The Herald will start the flashing proces. Wait it out till it says "Press any button" and hit the send button.
#11 Perform a hard reset
#12 Voila! Your back in business"
velascoperroni said:
I'm the newbiest of them all, I think I bricked my brand new Excalibur!!!
Sorry if I'm posting in the wrong place, but I need heeeelp!
O.K., here it is:
I just downloaded kavana's 080314 WM6.1 installer for the HTC Excalibur, I ran the exe and followed instructions, afterwards, the ROM app opened and started upgrading the phone but it got stuck at 1%, it made be go thru the recovery process several times (unplug, turn off, disconnect battery, turn on) but it always started on tricolor mode and always got stuck on 1%, after a third recovery process the ROM app just quit and left me hanging on tricolor mode!!!
Activesync won't connect now, I try to run kavana's exe again but it doesn't recognize the phone either, the phone is on, conected (windows makes the usb sound for connection) but it is not recongized, it's as if it's not plugged.
It is stuck on tricolor mode and I don't know what to do!
Please help me!!!
Click to expand...
Click to collapse
I believe you didn't application unlock it first. I had same issues. I finally got it to load. I don't think you bricked it. Remove battery wait a few seconds and restart phone
timothyjok said:
I believe you didn't application unlock it first. I had same issues. I finally got it to load. I don't think you bricked it. Remove battery wait a few seconds and restart phone
Click to expand...
Click to collapse
Already did that... still on "brick" mode...
Question: is my warranty still valid? I bought it 3 days ago.
you can solve simply to launch original upgrade to wm6 rom
glenbo said:
Try the dicussion thread "Bricked my T Mobile phone" there are plenty of answers there.
Click to expand...
Click to collapse
Do try these procedures first. I'm just throwing it out there but if you try again it is probably a better choice to flash to WM6 first. Then try flashing to the 6.1.
I'm sure you can return it but come up with a believable excuse.
Yes, You Are Correct!
pfunkside said:
Do try these procedures first. I'm just throwing it out there but if you try again it is probably a better choice to flash to WM6 first. Then try flashing to the 6.1.
I'm sure you can return it but come up with a believable excuse.
Click to expand...
Click to collapse
Yes, that is the correct path for him to take, install a 6.0 ROM first, before installing a 6.1 ROM. I suggest he install the T-Mo official wm6, just to get things started in the right direction again.
(1) If the device is still in the tri color mode (bootloader mode), that's a very good sign, it's not bricked. Connect the device to your PC via active sync in the tri color mode, you may think that the device is not connected to Your PC but it is, it may not look like it's connected, run the official T-Mo wm6 ROM RUU WWE, it will install on your device as long as your device is in the tri color mode.
(2)Once you get the wm6 ROM installed on your device, you must first SDA_ApplicationUnlock your device, next you want to Certificate AppUnlock and SurrealApplication Unlock your phone. Now, the reason you are doing all these unlocks are because you coming off the T-Mo wm6 ROM.
(3)After all this have been done, it now ok to try to install the 6.1 ROM on your device.......!
Great support!!! But now comes the obvious question from the n00b of the n00bs!!!
Got it, now the big question is: how to flash to WM6?
Is it done by the steps I posted early? (formatting SD, etc.)
Also, where do I get the T-mobile RUU?
Finally, there are a few things you should know, my phone was bought in Mexico, under the cellphone company Movistar (Spain's Telefonica and I've heard U.S. AT&T), it had WM5 before I "bricked" it (hehehe).
When I turn it now, a few miliseconds before the tricolor screen I can read in the phone a "waiting for SD card" message when the tricolor screen comes on, I get this version of RUU 1.15.000.
I appreciate all your help, as a contribution to this amazing community, when I get thru this, I hereby commit myself to write a fully understandable guide for noobs with the same problem (not too long).
T-Mo Wm6
velascoperroni said:
Got it, now the big question is: how to flash to WM6?
Is it done by the steps I posted early? (formatting SD, etc.)
Also, where do I get the T-mobile RUU?
Finally, there are a few things you should know, my phone was bought in Mexico, under the cellphone company Movistar (Spain's Telefonica and I've heard U.S. AT&T), it had WM5 before I "bricked" it (hehehe).
When I turn it now, a few miliseconds before the tricolor screen I can read in the phone a "waiting for SD card" message when the tricolor screen comes on, I get this version of RUU 1.15.000.
I appreciate all your help, as a contribution to this amazing community, when I get thru this, I hereby commit myself to write a fully understandable guide for noobs with the same problem (not too long).
Click to expand...
Click to collapse
Is your mobile device still in the tri color mode, if so just connect it back to your PC via active sync, It will accept the download! OK you can get the T-Mo wm6 at T-Mo's website, if not I will send you a link with the T-Mo wm6 RUU. Don't panic, you are still in the game.......!
Update!! Phone unbricked but still on WM5!
Ok... I used this ROM: HTC_S620_WWE_1.27.405.1_4.1.13.44_02.94.90_Ship.exe
It went thru the upgrading process but got stuck at 3%, anyway, it finished with a message like "this ROM cannot be used for your phone" or something and restored WM5.
Now I will follow instructions on the thread: "The Full Guide To Upgrading From Windows Mobile 5 to 6" and I'll be posting my acomplishments on this thread.
Question: The reasons for me not being still able to upgrade may be:
1. I haven't unlocked phone,
2. My phone is for Mexico and cellphone co. "Movistar", or
3. I'm running Windows XP as a virtual machine (via parallels) on an intel Macintosh and somehow there's a problem with the USB drivers.
I'm rooting for option 1 (but kavana's upgrade was supposed to already unlocked it). Option 3 maybe but then, why do I get Activesync to run? Option 2 would be a bummer!
T-Mobile WM6 RUU WWE ROM
Get the T-Mobile official Wm6 RUU WWE Rom here http://www.mediafire.com/?0vtw32zmuz3 ......!Oh! I throught you had a Excalibur.....!
Just can't seem to upgrade WM5 to WM6!
Iv'e tried the T-Mobile ROM and the HTC ROM and I get an: "invalid vendor id"
I tried every step on the aforementioned thread, even de CIS unlock, and still no luck... again, my vendor is movistar/telefonica/cingular.
Any thoughts?
Your Answer Is In jockyw2001 Thread
velascoperroni said:
Iv'e tried the T-Mobile ROM and the HTC ROM and I get an: "invalid vendor id"
I tried every step on the aforementioned thread, even de CIS unlock, and still no luck... again, my vendor is movistar/telefonica/cingular.
Any thoughts?
Click to expand...
Click to collapse
A easy frix, but read the instructions very carefully, jockyw2001 thread is located in the sticky section. What you are looking for will be in post #1.........!
New Instructions
Run the Excalibur Uspl-CID ByPass.zip, extraxt on your PC and open it there, you will see several file folders. Open the one that say (uspl) MS-Dos batch File, follow on screen instructions by pressing any key. This time when you see the white screen on your device do not panic! Run the HTC WM 6 ROM, this is done while the screen is still white on your device. Just follow the on screen instructions on your PC.............!
Now I definitively bricked it!
I ran the CID unbloker, screen went blank, ran the ROM, it got to 16% and made me do a recovery, after the recovery it gave me the same "invalid vendor id" message and it automatically restarted the phone, but...
The restart stopped at the HTC intro screen!! I've restarted it several times and it just stops on the first HTC logo screen... even a hard reset won't fix it!!!
HEEEEEEEEEEEEEEEEEELP!!!
Here is a visual aid.
You are not reading into detail. Use the Tmobile rom instead of the HTC Rom.
http://forum.xda-developers.com/showthread.php?t=368998&highlight=Jamerican
Still Bricked!!!
Yeah!!! superb visual aid!!!
I just wish I had seen it before I bricked it!!!!
This is the current state of my phone: I press power, I see a white screen with the HTC logo in the middle, the phone vibrates, still the same HTC logo... and it is stuck that way! I can't turn it off, I have to take out the battery!!
I've tried a hard reset, same thing happens! It stays stuck on the HTC logo screen and I'm forced to pull the battery out for the phone to shut down.
It is obviously not recognized in any way when I plug it to the PC's USB.
What made this happen? HTC Generic ROM got stuck on 16% before telling me "invalid vendor id", restarted the phone and voila: brick!!
Boy, I wish I was back in the tricolor mode!!!
IS THERE NOTHING I CAN DO?
I'm seriously thinking about going back to the vendor on monday and saying: It was like this when I woke up (I just bought it three days ago!!!)
If it gets that far, it doesnt seem totally bricked, ima PC man, so this may be off, but it seems like some kinda bootloader error on the phone itself....IE, the HTC screen is all that the bootloader tells the phone to load. Have you tried forcing the phone into bootloader mode?
I Looooooove Google!!!
OK... I found a turnaround for the problem... got it to go to bootloader mode!!!
Whenever something like these happens to you this is the hard way to put your excalibur/dash in bootloader mode:
1. Take out battery and sd card;
2. Plug your USB cable to your PC (not yet to the phone)
3. Press and keep holding the SIMB. key (the one with the camera next to the space bar)
4. Plug your USB cable to your phone (while still pressing the SIMB. key)
5. Voila: You are in bootloader mode!!
This was gotten for a 15 min. search in google!!
Now... I'll keep going with my WM5 to WM6 upgrade...
Hi there!
I am in serious need of help with my iPAQ hx2490. Yesterday, I tried to do the
official HP ROM Update. Everything went well, up to about a point when the RUU told me that there is a connection problem with my device.
The update went to just about half way through, and I didn't touch anything, I just left the device in it's cradle.
Anyway, my problem now is, that the device won't start the OS, I can't get past the HP welcome screen. The loading bar fires up, and completes it's way to the right, but after that: NOTHING!
I have tried soft, hard and clean reset, without any help. When I do a clean reset, the display shows "Formattin PS", and the loading bar reaches the right. But after that: NOTHING again!
I tried flashing everything again, from WM 2005 first and second edition, even WM 2003. The result is always the same.
I can get it into Pre-Bootloader, normal E-Bootloader. I do get a "USB Connected" message, and I do get the following "USB" message on the screen.
Now here's the odd thing (and I do hope that all you experts are dying to solve this mystery!): when I do the update again, at either 84,1% or sometimes 85,1%, the iPAQ shuts down, and starts again. But this doesn't stop the RUU from continuing!!
I've tried everything I can, I read all the infos in the forums concerning iPAQ problems, but they're mostly concerning entering bootloader, which is NOT my problem.
Money ahead: I'll donate 10€ to the person who is able to solve this riddle!!
The money can go to either this website or the person's own PayPal account.
oh I forgot: I did try ChrisMRulz bootloader method, but I wouldn't work for me. I managed as far as the MTTY program firing up, and I do get a WCEUSB prompt, but can't enter any commands, and the nbf file doesn't get uploaded!
PROBLEM SOLVED!! Sorry.....
Can you tell us how?
Maybe it will be helpful for others that have similar problems in future.
Sure, I can do that:
I managed to flash the official International English ROM Update to my german hx2490 iPAQ. I just used the trick that you have to start the correct HPRUU.exe for your country-specific device, but just before you hit the last "Update" button, you change the .nbf file with the one you want to flash.
But you have to rename it to according filename the HPRUU.exe originally loaded,
if you don't rename it, the update utility will crash.
By doing so, I was able to flash the above mentioned ROM to my device, and after that I just flashed my country-specific ROM.
Now I'm back and running WM5.
If further explanation is needed, I'll gladly help out someone with the same problem.
Hi
My device has a German ROM.
I tried to Rom Upgrade to my O2 XDA III PDA but it doesn't work!
when i flashing the device it's freeze on process at%41 and give a error message. i unplugged the device craddle and flash same ROM again and process completed succesfuly. After all when i turn on my device ,there is only 3 Color on screen (Blue - Green - Red) and at the bottom of device is white. it writes R.1.10.00 at the right bottom of the screen.
Sorry about my english ! i searced it on web but i found a information and it tells find same type device and update ROM with FAT 32 Formatted SD Card.
Can anybody help me for Solve This Problem.
Thanks.
1. do you use vista/7 ?
2. did you forget to take out the sim and sd card during flashing?
that would be 2 possible reasons why you had the error in the first place.
now for the solution: if the flash was really complete and successful, which at this point you cannot tell by the success message, have you performed a proper hard reset?
the instructions on how to do that are to be found here: http://wiki.xda-developers.com/index.php?pagename=BlueAngel_WM5_For_Beginners
power+reset, record+camera, then set the menu options to No, Yes, Yes confirm with the mail button.
rom upgrade through the sd card is generally not such a good idea, since it has never been fully confirmed, that and how it works.
if the hard reset does not solve your problem, you should read -=this=- really carefully and think whether you really did ALL the steps, they are all equally important.
Problem is getting worst !
Thanz chieff for your Help.
Problem is getting worst and confusing. i updated Radio version to 1.10.00 to 1.15.00. Device is turn on but it doesn't boot. My Device has no camera. When i plug it to creaddle it's orange led is ligthting and randon times it boots and 3 Colored screen shown. R.1.15.00 D.****** G******
HTC Blue Angel Windows Mobile 6.1 WWE only. But now it's do nothing. This morning i made hard reset to device and shown SERİAM V.2.07 and put ,t to creedle and tried to Urgrade room but it gives error random positions etc. %54 or %89. ERROR 112
is my device dead???
Thanx you very much for helping me.
(Sorry About My English )
About my OS
i tried to upgrade XP Pro (SP2). Vista and Windows / is Not permission to upgrade...
if you're giving up, mail it to me. i should be able to tinker with it.