XDA 2 (no sim in phone at present) downloaded latest rom from O2 site. Coonected phone via cradle directly to PC and ran the utility, it finds the phone and the says your phone will be updated to version and has three new versions listed (current versions are all shown as blank) click continue and then machine sits and hangs and it the says error 112 and suggests resetting phone and trying again but the same continues to circle around.
Phone still shows usb v1.03 and cannot do anything to get out of it.
Please can any response be in plain english as i am not too much of a techy.
Any help greatly appreciated though and your knowledge is accepted but mine is less.
Matt
Can you get any of the WM5/6/6,1 ROMs to install? You may just have a faulty original ROM
MATT9711 said:
Phone still shows usb v1.03 and cannot do anything to get out of it.
Please can any response be in plain english as i am not too much of a techy.
Any help greatly appreciated though and your knowledge is accepted but mine is less.
Matt
Click to expand...
Click to collapse
Bootloader 1.03? Can you do me a favour, can you take the battery out of the back of your device, and look at the sticker under where the battery goes (on the device).
What does it say? PH10A, PH10B etc
VERSION
Ph10b Is The Number Under The Battery
*bump*
I'm having exactly the same problem, and would desperately like to try and find a solution.
I'm suspecting it's a device communication problem, as the screen showing what CD iimage version is currently on the device is listed as blank.
Once it gets to the screen where it says that the device is about to be erased before installing the update, nothing happens on the XDA 2 at all - so I imagine that it's not talking back to the computer to say "erase me".
Edit:
Problem fixed. The cause of the problem was Windows Vista. I connected the cradle to a laptop running a fresh install of XP, and was able to successfully install the upgrade ROM.
Related
Hi,
My XDA II was up and running until I wanted to flash it with Wm2003se.
I not sure if the battery is fading out or what but the flash didn't conplete and I am left with the "serial 1.06 boot screen" I have tried numerous times of taking out the battery, letting everthing drain out and trying again. but it still goes back to the serial screen. Also activesync won't recognize the device and Windows XP picks it up as "Unknown Device". When I try and reflash it, I get the "communication error". Could someone dump thier Rom and/or instruct me on how to flash my device using my SD card?? Or if there is another way to revive my XDA II, I am open to anything. Thanks!!
Shane
Hi
Am also facing same problem on my O2 xdaII..it always shows serial v1.02
can any one help us pls..
tks isse
Hi
same problem whit MDA ll t-mobile de.please help
shane said:
Hi,
My XDA II was up and running until I wanted to flash it with Wm2003se.
I not sure if the battery is fading out or what but the flash didn't conplete and I am left with the "serial 1.06 boot screen" I have tried numerous times of taking out the battery, letting everthing drain out and trying again. but it still goes back to the serial screen. Also activesync won't recognize the device and Windows XP picks it up as "Unknown Device". When I try and reflash it, I get the "communication error". Could someone dump thier Rom and/or instruct me on how to flash my device using my SD card?? Or if there is another way to revive my XDA II, I am open to anything. Thanks!!
Shane
Click to expand...
Click to collapse
Come on....Somebody help us, we have a crisis club going on here!!!
did u guys follow all the intructions in upgrading the rom?
try this
disable activesync by ctrl+alt+del and kill wcescomm.exe by end process
make ur phone in bot screen
put ur phone in the cradle(with the power supply, so that ur bat will not drain).
usb should be in the display and not serial
make sure the 3 files(ms_ , radio_ , and nk) are in the same folder with himaupgrade.exe
run himaupgrade.exe
Wait about 5 processes i think. after the pc will let u know if it is done... get ur xda from the cradle and hard reset it (power button+reset button)...
if it doesnt work still im sory, im just a newbie, i just did mine.... maybe u should read more...
shane said:
shane said:
Hi,
My XDA II was up and running until I wanted to flash it with Wm2003se.
I not sure if the battery is fading out or what but the flash didn't conplete and I am left with the "serial 1.06 boot screen" I have tried numerous times of taking out the battery, letting everthing drain out and trying again. but it still goes back to the serial screen. Also activesync won't recognize the device and Windows XP picks it up as "Unknown Device". When I try and reflash it, I get the "communication error". Could someone dump thier Rom and/or instruct me on how to flash my device using my SD card?? Or if there is another way to revive my XDA II, I am open to anything. Thanks!!
Shane
Click to expand...
Click to collapse
Come on....Somebody help us, we have a crisis club going on here!!!
Click to expand...
Click to collapse
I assume you did a hard reset?? In the past three days I have gone from Windows Mobile 2003 >>> Windows Mobile 5 >>> back to Windows Mobile 2003 SE (SIN's magic version available here on XDA-Developers) which I like best of all (for many reasons, mainly speed and reliability). As someone else stated, you need to put it in the cradle AFTER deleting the old profile in ActiveSynch on the PC. Oh, and make sure you are using ActiveSynch 4 or higher. This is now available from Microsoft's site. :idea:
I think my Mogul is bricked after trying the ROM update; after about 7% update Vista kicked off the USB connection and I'm left with a tri-color screen. When I try to reinstall the ROM I get an Error 328 message - Invalid Command. Any help? Thanks!
Definitely not bricked if you can get to the tricolor screen.. which rom exactly were you flashing and what have you flashed so far (unlocker, etc)?
Have you tried updating from the microsd card? That solved a similar problem for me.
AFH said:
I think my Mogul is bricked after trying the ROM update; after about 7% update Vista kicked off the USB connection and I'm left with a tri-color screen. When I try to reinstall the ROM I get an Error 328 message - Invalid Command. Any help? Thanks!
Click to expand...
Click to collapse
What steps have you taken so far? That might help others figure out your problem(I would help but I'm leaving my computer right now)
Just tried to re-cradle and reinstall the update - ROM 3.35.651.2 from HTC's website, and I get the message Invalid Command and it stops the update. Can I run this from the MicroSD card as suggested? Any help very much appreciated!
I have no access to anything on the phone BTW - just the screen and nothing else. The screen has four horizontal stripes - Red, Green, Blue and White. In the red stripe it says TITA100 MFG, SPL-2.03.1000, CPLD-9, and at the top of the screen RUUNBH....
Run Olipros 2.40 bootloader. Than, go back and flash the 3.35. I'm pretty sure you need the 2.40 to load the new ROMs. Yes, just run Olipro's 2.40 while you are in the tri-color screen. Also, make sure you have more than 50% battery life left.
Where do I get the bootloader and how do I run it? Sorry to sound dense, but this is new to me. I have the concept of running the bootload mode - Camera, Power, Reset, so I assume some software needs to be loaded on the MicroSD card? Thanks!
You know, it's fine if you're new to this....everyone starts somewhere...and it's good to see new faces in the community...
But what I don't get is why people insist on just flashing right away without reading and researching. Then they make posts about thinking their phone is bricked, not even knowing what a bootloader is.
My advice before you do anything else is to take an hour and read. Read about how to flash, read about bootloaders, read everything you can find about updating your phone. Then, try and fix your bootloader.
Your phone isn't bricked. A brick is just that, a brick. NOTHING works, not the bootloader, not the buttons, nothing.
gcincotta said:
You know, it's fine if you're new to this....everyone starts somewhere...and it's good to see new faces in the community...
But what I don't get is why people insist on just flashing right away without reading and researching. Then they make posts about thinking their phone is bricked, not even knowing what a bootloader is.
My advice before you do anything else is to take an hour and read. Read about how to flash, read about bootloaders, read everything you can find about updating your phone. Then, try and fix your bootloader.
Your phone isn't bricked. A brick is just that, a brick. NOTHING works, not the bootloader, not the buttons, nothing.
Click to expand...
Click to collapse
i second this emotion
Actually, although I'm new to this forum I'm not new to computers. I'm not as familiar with the inner workings of a handheld. I assume a bootloader is the software necessary to run the ROM flash from the SD card; when I run in bootloader mode, I do get a very brief "image not found", so I assume it's looking for the ROM image on the card. And I'm tracking down Olipros stuff right now through the forums, as well as the recommended reading. With a little written direction I think I can "unbrick" this phone. I did successfully flash another Mogul from a different computer, so assumed it would be as smooth; guess not. For those with the expertise, I certainly appreciate the advice and patience to teach a novice...
Once you find the required bootloader program, just run it as if you are flashing a ROM. Once you get "Olipro 2.40" on your tri-color screen, you'll know that your getting somewhere. But yes search and search and read. I also downloaded everything I think I would need also, just in case.
OK - so far 've tried running the Olipro Bootloader 2.40, but I get "device not connected." Perhaps I should mention I'm running Vista Home Premium, so no ActiveSynch; my PC has Mobile Device Center. I hear the little chime when I connect the Mogul, but the Olipro software doesn't recognize a connection....
I have done all of my flashes on my Vista Home Premium laptop. Make sure you uncheck "allow USB connection" on WMDC. Also, after every failed attempt, take the battery out of your phone for 3 seconds and then reinstall.
Did you mean check "allow USB connections"? WMDC is attempting to connect, but always fails. I was assuming because it doesn't recognize the PDA...
no he meant uncheck....READ!!
start here http://forum.ppcgeeks.com/showthread.php?t=9927
Thanks; I have an XP machine I'll try; jacking with the WMDC drivers in Vista would take more time than its worth...
Actually Vista should automatically find and install the required drivers for you. It shouldn't take long. It's well worth the time considering what you are getting yourself into.
First, thanks for the assistance all. Status to date: I have connected to my XP machine and still can't connect the Mogul to ActiveSynch. ActiveSynch won't recognize the device in its current state. I've tried running the bootloader program both with the "USB Connection" option in ActiveSynch on and off; when I run the bootloader I get a popup window that says "No device connected", and a query "Would you like to try copying again?" with button options "Yes", "No" or "Cancel." Clicking "Yes" gives me the same popup. Clicking "No" lets the loader proceed, but has no effect on the Mogul except ultimately it brings up a screen showing the percentage complete which remains at 0, and on the PC it brings up the Recovery screens for the ROM update, which have no effect on the Mogul because I assume no connection has been made. I'm obviously misinterpreting some of the steps?
Any way to run the loader from the MicroSD card? I think someone mentioned it before?
Sounds like you still didnt get Olipro 2.40 into your machine, right?
When you boot it (press camera+power+soft reset) which bootloader do you get showing?
If its 1.06 or something like that you need to flash a (manufacturer) stock rom.
If its 1.20 Olipro then you need to flash a customized pre-3.16 rom. (if you need one pm me and I will give you a link to a clean one for your carrier)
Either way you need to get the rom file called xxxx.nbh. Rename it to TITAIMG.nbh. Place that file into the root of a FAT32 formatted sd card. Inster it into your sd card slot and power down and power up the titan. It will automagically read the rom from the card and flash it for you. Same goes for radio nbh files
I know, I know: First use the board-search and google...
I did that and I couldn't find anything useful for my issue.
I'm trying to update my HTC Prophet G4 to WM6.1...
I wanted to use SoftSPL and after executing the SPL.lnk the screen turns white as it should, but after that Windows XP doesn't recognize my phone anymore as connected.
I tried different USB-Ports, but the "ROMUpdateUtility_NV_G4.exe" keeps telling me "Error 260" which means it couldn't connect to my phone.
I'm really desperate cause I've already tried to upgrade for some days...
So if anyone knows how to fix that plz write =D English and German are okay with me
mickgrand said:
I know, I know: First use the board-search and google...
I did that and I couldn't find anything useful for my issue.
I'm trying to update my HTC Prophet G4 to WM6.1...
I wanted to use SoftSPL and after executing the SPL.lnk the screen turns white as it should, but after that Windows XP doesn't recognize my phone anymore as connected.
I tried different USB-Ports, but the "ROMUpdateUtility_NV_G4.exe" keeps telling me "Error 260" which means it couldn't connect to my phone.
I'm really desperate cause I've already tried to upgrade for some days...
So if anyone knows how to fix that plz write =D English and German are okay with me
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=353547
Thanks for posting, but as I already told you: I did my research...
So I already tried different FlashingTools, like ProphetTools etc.
When I SoftSPL, I get to the whitescreen but i cannot make my pc recognize the phone at my usb-port.
When I enter the 3-Colored-Screen manually it shows the usb-connectivity, but I cannot update the ROM...
There was a way (I cannot remember anymore which way I did it, cause I really tried very often) I entered the 3-Colored-Screen and there was "RUU" written in the right upper corner of the screen. But then again the connectivity doesn't work...
Also tried different usb-ports and cables...
I could say that I'm feeling like a weirdo, cause upgrading a rom seems easy and still makes my day miserable xD
//EDIT:
Didn't see the "Lazy_Tool" at the first glance, but now after trying I still get the same error...
//EDIT2:
Realized that the error-code could be useful^^ --> "Error[260]: Update Error" (Sth like that^^)
I had a similar issue. When your PC reports it cannot connect to the phone - does the phone restarts?
mickgrand said:
Thanks for posting, but as I already told you: I did my research...
So I already tried different FlashingTools, like ProphetTools etc.
When I SoftSPL, I get to the whitescreen but i cannot make my pc recognize the phone at my usb-port.
When I enter the 3-Colored-Screen manually it shows the usb-connectivity, but I cannot update the ROM...
There was a way (I cannot remember anymore which way I did it, cause I really tried very often) I entered the 3-Colored-Screen and there was "RUU" written in the right upper corner of the screen. But then again the connectivity doesn't work...
Also tried different usb-ports and cables...
I could say that I'm feeling like a weirdo, cause upgrading a rom seems easy and still makes my day miserable xD
//EDIT:
Didn't see the "Lazy_Tool" at the first glance, but now after trying I still get the same error...
//EDIT2:
Realized that the error-code could be useful^^ --> "Error[260]: Update Error" (Sth like that^^)
Click to expand...
Click to collapse
260 IS A KIND OF CONNECTION ERROR,
PLEASE SOFTRESET AND TRY AGAIN!!!
1. FLASH NVID FIRST,
2. LAZY TOOL TO HAVE THE JOB DONE.
dwizard said:
I had a similar issue. When your PC reports it cannot connect to the phone - does the phone restarts?
Click to expand...
Click to collapse
If u want to know if I bricked the phone then no =) I can restart it and everythings fine^^
If u meant sth else plz specify your question a bit
@ dioxda2:
Ok I'll experiment a bit^^ I'll get my new hardware soon, so maybe the error won't be a problem^^ We'll see =)
mickgrand said:
If u want to know if I bricked the phone then no =) I can restart it and everythings fine^^
If u meant sth else plz specify your question a bit
Click to expand...
Click to collapse
OK, rephrasing: the problem I had with my phone was that while a ROM update was running the phone would restart and I got the same error you did.
It turned out the battery was at fault, after replacing it with a new one - it works great.
If u do as dioxda2 says all should be fine. He is right in saying 260 is a connection error. That means unplugging all usb devices out of ur machine. It also means disabling all other connection software, like my raspberry program that display device screen when active sync'd. I always disable my anti virus and firewall (make sure ur not connected to internet at time).
i always ensure that the flashing tool is on the root drive, not in many folders (so place flash tool direct on ur main hard drive in its folder as uve unzipped) this itself can cuase connection errors. Ensure battery is 50% min too.
Good luck
Hi...
Can anybody help, my Display is dying at the moment, and i want to send it in for repair,
but i need to restore the original bootloader,
can anybody help, download link for the bootloader and manual,,instruction..
Many thanks
Markus
I think you can download the official firmware somewhere, when you flash it everything should be back to the way it was.
What version of firmware do you need? WWE? T-Mobile? Orange?
If it's the WWE 2.73 version - click here - This will restore the phone to factory settings including bootloader/ROM/Default Settings e.t.c
Hello,
I tried to flash the UCP cited for the same screen problem. I checked my windows drivers are correct (sync between the hero and the perfect pc). Every time I have the same error message, 170 which would normally be bad drivers, which should not be my case since retry several times. I mark the following 170: wrong version of bootloader. The same thing happens whether on a PC or XP win7.
Does anyone have a solution please??
Armrhero said:
Hello,
I tried to flash the UCP cited for the same screen problem. I checked my windows drivers are correct (sync between the hero and the perfect pc). Every time I have the same error message, 170 which would normally be bad drivers, which should not be my case since retry several times. I mark the following 170: wrong version of bootloader. The same thing happens whether on a PC or XP win7.
Does anyone have a solution please??
Click to expand...
Click to collapse
There is a thread called "usb and ruu issues solved" by BTDAG. That should sort you out.
Sent from my HTC Hero using XDA App
The phone notified me there is a system update so I went ahead. Unfortunately, towards the end, it gave me an error message. I remember seeing the big Android robot lying flat on its back.
Now, the phone is completely dead. When I connect it to my computer I can hear the "new hardware connected" sound then immediately the disconnecting sound. This goes on and on for ever.
I tried using the tools provided on Leagoo's site, but they're useless as the computer is not able to recognize the phone.
Is there a hard reset key combination?
Thanks.
Eddie
silentmonolith said:
The phone notified me there is a system update so I went ahead. Unfortunately, towards the end, it gave me an error message. I remember seeing the big Android robot lying flat on its back.
Now, the phone is completely dead. When I connect it to my computer I can hear the "new hardware connected" sound then immediately the disconnecting sound. This goes on and on for ever.
I tried using the tools provided on Leagoo's site, but they're useless as the computer is not able to recognize the phone.
Is there a hard reset key combination?
Thanks.
Eddie
Click to expand...
Click to collapse
I've here 4 brick-phone (friends have updated with the same result!).
leagoo support didn't answer to my polite email of support.
Anyone can give us a sugestion to recover it!?
j045 said:
I've here 4 brick-phone (friends have updated with the same result!).
leagoo support didn't answer to my polite email of support.
Anyone can give us a sugestion to recover it!?
Click to expand...
Click to collapse
In the end, I was able to finally recover it. I just kept trying and trying: while the phone was connected to the computer, I removed the battery, then I put it back in; as well I was disconnecting it from the computer, then plug it back - I did this several times until the software on the computer was able to recognize it.
Even so, when I managed to reflash it, around 60%-70%, I got a message that it failed; so I tried again - it failed around 80% then I tried one more time and it was successful. Now the phone is working fine.
So my advice to you is to keep trying - leave the software on and click on the "download firmware" or whatever it was called, meanwhile keep unplugging the phone (and play with the battery as well).
Good luck! (you will need it)
Same problem, but leagoo responded with driver, firmware, flash tool, instructions and a video.
But nothing changed, so i have to retry.
Thanks for your post.
Edit:
I was thinking that was a hardware problem with micro usb connector!
ItalianWolf said:
Same problem, but leagoo responded with driver, firmware, flash tool, instructions and a video.
But nothing changed, so i have to retry.
Thanks for your post.
Edit:
I was thinking that was a hardware problem with micro usb connector!
Click to expand...
Click to collapse
i did it! just tried a lot of times, but firmware from leagoo doesn't work, display shows only "stipes".
I found another firmware (don't remember where) and then all things went good.
Now the phone notified me there is a system update, i have to do it?