XDA IIs Failed ROM Update - I HAVE READ THE WIKI - Upgrading, Modifying and Unlocking

A plea to the wonderful XDA Community out there - Please help!
I posted a few days ago under "Blue Angel" that my device was no longer recognising the presence of its SD Card. [ http://forum.xda-developers.com/showthread.php?t=312147 ] Nothing had helped with that situtation so I tried a ROM update as a last resort (knowing I would have to reinstall everything, etc)
The ROM updates I have tried have all failed. I have found several different ROM downloads from various sources, including this website. I have done ROM updates before with no problem and as the post title says, I have read the WIKI so I am not posting this in complete noob ignorance!
Every time, it fails when updating Radio Stack (I have tried V1.12.0, 1.14.0 and 1.15.0) Sometimes the ROM update program says it has encountered an error when updating radio stack. Sometimes it just disappears from the screen on my PC. Sometimes I get a Win32 error.
My device is stuck on "Serial V2.07" bootsplash grey screen.
All this just because it stopped detecting SD card
PLEASE please help, any and all advice v much appreciated.
If someone knows a link to a good, reliable ROM update I would be glad to receive it
P.S. If you think my device is FUBAR then please let me know but I hope not!

I'd try another computer.
Since you can still get into the bootloader mode, there's hope for your device.
Also if your cradle is USB, then it should change from Serial to USB in the bootloader screen when you plug the device into the cradle.

Reply to Wuzy
Wuzy - thanks for the tip, I'll try another computer. Will post further update on here when I've tried that.
For the record, it certainly DOES change to "USB" on the bootloader screen when I dock it into the cradle.
I'm glad to know there is still hope *crosses fingers*

Cradle yr device and flash a suitable ROM.See more in Blue Angel Upgrading section

Related

My grey screen says USB v2.07 I think I killed it!

My grey screen says USB v2.07. I tryed to update the radio to 1.13... I copied the EnterBl.exe over to the Siemens SX66 and executed it. It blinked and then turned off. Then it came back on and displays USB when on the cradel and Serial when removed. I cannot get it to do anything now. Does anyone have any advice?
Thanks,
Bobby
Cingular
Siemens SX 66 ( I have no idea how that translates into blue angel)
same here
if some one has a sulotion please send me instruction or a mail [email protected]
thnx
you are stuck in bootloader mode. just run the setup for rom upgrade/restore for your device and it should work. I think a hard reset will also allow it to reboot into normal mode, but not sure.
Defiant XDA
I cannot seem to get it to reset nor be recognized by the computer when it is placed in the cradle. It will chime as it is placed in the cradle, yet the charging light no longer ignites and the hot-sync program on my WinXP pc does not indicate that they are connected any more.
Thank you for your time!
Bobby
restore the original ROM. I had this issue after I run a defrag on my "Storage" folder using Storage Tools. I could not reset it. Also, upgrade with higher ROM did not work.
You have to restore / setup using original ROM version. Good luck!
Follow this link, download the update and follow through the instructions.
http://t-mobile.iris-global.com/download_manager_mda_3.html
original rom
Does any one has the original rom for the ph20b my son messed it up
\if any one can send it via email or a link will be helpfull
thnx
Another Possible Solution...
This has happened to me numerous times when upgrading to various ROM versions and through experimentation I finally realized that it was related to my storage card. I also remember reading another post like this where this problem can occur if the storage card is on the large side (>= 1GB ).
Just take out the card and reconnect to the cradle and you should be able to flash again.
Hope this helps

error [260] message every time

Firstly I would like to say thanks to this site and the trinityguides.info site for the great work people have being doing and making available to everybody, it is great being able to use my trinity with wm6, keep the good work going!
Now the issue I seem to be hitting the same "error [260] connection" every time I attempt to update anything on my Trinity. I have followed the advice on the trinityguides site regarding being stuck in bootloader mode to no avail, and I can't seem to find anything in the posts on the xda site which will rectify the issue.
Previously I have been able to update to AX3L v2.8.01 version without any problems, but I decided to update to sammy's ultra light, it initially kicks into des' crashproof sspl, but then it can't connect to the pc. even when I manually enter olipro's hard-spl it does the same. I have tried to re-install hard-spl, but can't. Disconnecting the usb option in the activesync settings doesn't do anything either. Does anybody have any suggestions for me please?
I am not even too sure if my trinity should have both Des' crashproof and hard-spl on it at the same time? Could someone advise me on whether this is alright please?
the tech details:
Trinity
AX3L_OS_v2.0.8.2
radio - 1.46.30 (even though it doesn't say this in the device info, or boot screen after soft reset)
Home PC - XP (just in case)
Did you also try flashing it again, the ROM I mean. I have this error also but as soon as I execute the ROM flash again it finds the device and starts flashing:
http://forum.xda-developers.com/showpost.php?p=1449597&postcount=2
I am assuming you mean flash with the new ROM, sammy's in my case?
yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)
No, I am in the same situation. The first attempt puts the device in 'ipl-sspl by des' bootloader mode then after about 10 seconds or so the error[260] is displayed on the pc. If I exit the ruu app and attempt again, nothing new happens on the trinity (i.e. it is still in Des bootloader) and the message is displayed again.
the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.
What operating system en activesync are you using?
On the PC I am using XP and Activesync 4.5
Check your connection settings to accept USB connections. Also, try using Hard-SPL 1.30 before flashing the ROM again.
deejacker said:
the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.
Click to expand...
Click to collapse
In your PC, try another USB connection.
BLOODY HELL!!! It is the simplest things which we often forget to try. Thanks Jotam for pointing out an obvious point, it must have needed a re-plug of the usb cable into another port for the pc to pick up the device again. I will remember that for future updates so I don't make a dumb ass of myself again. Thanks guys/gals.
Vista
Using Vista? if so which version?
Hi I asked this question yesterday, I am a noob :-[ but the only difference is I'm using Vista Ultimate.
Just for others who have the problem.
When you replug into another USB port (Luckly I've got two on my laptop..)
I used the Vista drivers from TrintyGuides and bingo !
now I try and flash a WM6.....English or Italian...maybe French.
Thanks for the help I keep you posted.
Richard
It works
Now to discover the joys of WM6 after only having WM5 for two weeks....
/i am getting the same only rom update 3.14.4.1 now sees the phone..
has the device name changed???
evene exploit no longer sees the phone
sorry, can you be a little more clear.. what ROM are you flashing, and what exactly is happening?
by the way... i thought error 246 was the connection error... am i mixed up? which is 260?
This seems to be on any rom bar the Dopod roms
and it says 260 connection error
Error 260 connection error - the phone is not going in to bootloader mode - and the RUU cannot seem to initiate communication with the phone.
I'm getting this a lot recently trying to flash.
However, Hold the power and camera buttons while resetting with the stylus (keep them buttons held down).
When you get to the bootloader - plug the phone in - wait till you see the USB at the bottom of the bootloader screen - then run the RUU again - it WILL work - every time.
I used to get this error message alot. sometimes the programs you install don't allow you to update even if you force the phone into bootloader mode so you have to hardreset the device and then upgrade.....hope this helps
htc diamond stuck
T-Rob said:
yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)
Click to expand...
Click to collapse
hi ,
my htc diamond stack, no respond on the screen i try to do hard reset with tree buttons but its not working, nothing happaned, screen stay home screen with the time and not responding touching the screen at all
please emergensy help

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

I own a new blue angel...called by O2 II's
So, after i read ,again,and again...I have successed enter boot loader.
With white screen it's shown the version 2.07 and the line at the top "Serial"
(uhm, i use WM2003SE as the original pda when i purchase)
Ok, the problem now is, i can't flash anyrom (in Wiki and any rom i found)
After the line appear "Don't plug cable or craddle of ...." it's seem to verifie it's self... and then the line appear again "this tool is not support for this device".....and some error like that.
I was totally confused, how i made the thing go wrong? or just i missed something???
i make a soft reset, then hard reset and then 3 button together to get the white screen with no light, still see words such as: serial, version 2.0.7...
When i plug the usb cable , then the serial change into USB as usual.
As my experience,( Dopod810 and Qtek S200) everything is normal...
One problem too, i can't connect to PC with activsync (i tried any versions as possible)but itself avaiable on Boot loader...
All you understand what happen with me???
Please help me out of this. I want my Blue Angel is not the worst i got ...(i think it's possible go up to wm6???)
Finally, thanks you all for listening( reading this topic)
Yep, Happened to me too. Heres the fix.
The regular WM6 exe will give you an error everytime with the O2 IIs. Finally I printed out the WM6 directions, and also the Blue Angel for beginners and some other threads and found the answer.
You are in the right place (stuck in bootloader that is). Now you should be ready to load the OS. In the Upgrade folder you will find:
"MaUpgradeUt_noID.exe"
Run it and you will see the progress bars on the Windows screen and the dark XDA screen. Don't bother it - allow it to complete.
After it completed, I was unable to restart, soft reset, hard reboot. I think I actually had to take the battery off. When I powered it again I saw the Color Bars and knew it was good.
Good luck, Be careful. Try to be calm. I know when I was stuck in between Roms I was close to being a nervous wreck.
erh, one more message when i fkash rom...
This MaUpgradeUT novid erh something like this but this
" This tool is not support for my device" or somehow ...
I think i really stuck...
when itself verifie version of rom , i can't see both version appear on windows.
ie : version rom which is in PDA and version of rom which is in the OS i next to flash(want to flash).
So Confused . Anyway, thank for helping !!!
You are close!
Yea,
I Kept getting that too. Couldn't see both versions. Got a couple of different error messages. you are right where I was. you've got to find the upgrade exe. in one of the folders. My IIs was stuck in bootloader and I started that upgrade and it skips checking the IIs first and just begins to xfer the data.

Phone can't power on.

I have a o2 xdaIIs, when I connect the battery, the phone goes to boot model, show me the serial and version v2.07, when connect to usb, connect to the computer, try to reflash the rom, no success. Please help me.
what's the error in the computer screen?
it may help if you searched the forum
using the string that is said in the flashing program.
like Error <number>
I too am suffering from the sam problem.
I was attempting to upgrade the ROM and it failed. Now all I see on the XDA IIs screen is USB at the top and v2.7 at the bottom. This is whilst in the sync cradle.
When out, the USB changes to SERIAL.
Please help as I don't really want to use this as a paper weight
Thank you....
"the USB changes to SERIAL."
when it does that it's ready to recieve a new rom and starting the flash will give it that if it finish successfull that is
thanx for that. I also went scouring the forum and came across a faq about this very problem...
thank you though for taking the time to respond.
I appreciate it !
have a good new year !

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

Categories

Resources