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 !
Related
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
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
HELP!! Im trying to replace my current german language orbit rom with B&B4...activesync was working and my screen went blank like it was supposed to...but I instantly lost activesync when it did...I can not go any farther. What do I do??
I have replied in the other forum, please don't post in more than one forum.
sorry.
I figured it out. Just procede through the USPL setup even though it says make sure activesync is connected. (activesync is dissconnected when screen goes blank but will still update correctly) thanks again guys
of course when your device resets itself activesync connection is lost. even usb connection is lost for a short time (you can hear the ding-dong and dong-ding sound). activesync needs a usb connection and software running both on pc and pocket pc. so when your device starts into bootloader you cant have an activesync connection. but to flash some stuff all you need is a working usb connection.
I can understand that but
I see what your saying...but when your flashing anything be it a PSP, P3300 or anything else where there is a possibility of bricking it, your going to try not to deviate from the instructions...so when the screen goes black and you have to check the box which says you've complied with the above steps and a connected activesync connection is one them...time to hit the forums and get a few things cleared up.
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
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.