Xda II will not reflash - MDA II, XDA II, 2060 ROM Development

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:

Related

Dead Xda 2 On Serial v1.01

My xda 2 is stuck on the bootloader and wont do anything after trying to reset it ive tried i think everything that i can possible do and i read most of what was offered yet its still stuck on the bootloader. I tried to upgrade from v1.60.... to the latest at v1.72.187 uk o2 . Please help ><
Have you tried resetting your device, placing it back in the cradle and re-running the upgrade?
I have tried reseting but it fades then reappears disallowing me to run the upgrade 'Xda_II_172187_Final' but i have downloaded another which sizes around 512kb but this says that the rom image is not present. :/ can u link me to another upgrade if it may help
Shadow786 said:
I have tried reseting but it fades then reappears disallowing me to run the upgrade 'Xda_II_172187_Final' but i have downloaded another which sizes around 512kb but this says that the rom image is not present. :/ can u link me to another upgrade if it may help
Click to expand...
Click to collapse
Exactly which upgrades have you attempted? What happens when you run the XDA_II_172187_Final upgrade?
What is the 512kb upgrade you mention?
I used 'himaupgradeut_197.exe' after the 'Xda_II_172187_Final'.
'himaupgradeut_197.exe' was the 500kb file which gave me the error
that no rom image was found and the 'Xda_II_172187_Final' was the only 1 that i used to upgrade and that says it cannot connect to the device ...make sure its connected.
Shadow786 said:
I used 'himaupgradeut_197.exe' after the 'Xda_II_172187_Final'.
'himaupgradeut_197.exe' was the 500kb file which gave me the error
that no rom image was found and the 'Xda_II_172187_Final' was the only 1 that i used to upgrade and that says it cannot connect to the device ...make sure its connected.
Click to expand...
Click to collapse
The HimaUpgradeUt_197.exe file is not an upgrade it is a version of the upgrade program. It still needs to be used with all the other files that form part of the upgrade process.
As regards the connection error, make sure you are in bootloader mode (by pressing Jog button and Power button at the same time as pressing reset) before retrying the upgrade. Also make sure the USB cradle is plugged directly into a USB port on your PC and not through a hub and that the power supply is connected to the cradle. It may help to make sure that ActiveSync isn't running also, as it is not required for upgrading.
Isnt it already in bootload mode? if not i dont know where the jog button is Also i just realised i didnt have my cradle its own powersuplly which i have done just now but i dont want to carry on witht upgrade is there a way i can just make it back to normal ?
Shadow786 said:
Isnt it already in bootload mode? if not i dont know where the jog button is Also i just realised i didnt have my cradle its own powersuplly which i have done just now but i dont want to carry on witht upgrade is there a way i can just make it back to normal ?
Click to expand...
Click to collapse
It sounds like your device is already in bootloader mode - my suggestion is just a 'failsafe' The Jog button is the multi-directional button at the bottom centre of your device.
I don't think it is possible to 'go back' to normal as if you never did anything. With the power connected properly there is every chance an upgrade will now work. You can, of course upgrade using the original ROM version, if you know what that was.
hmm its still done a restart and yet it doesent seem to connect. When i restart the xda 2 its still in bootload mode when i place it in cradle still in bootload mode and i still get the same errors witht the upgrade ><
OK. This should work Can you try a different USB port? Failing that, is it possible to try another PC? I know about other users that had connection problems and tried a different PC and it worked OK.
Omg thank you i thought i lost it Thank you Very much i cnt thank you enough. ^^
For reference i switched the USB cable around and it worked ^^
That is great news

Help O2 Atmo

Dear All master,
I need help on my o2 Atom, when I upgrade it to latest version, it stop on stage 5: Burn in Radio Rom, 0%. Nothing happen even I had to wait for 1 hour.
I upgrade it with original atom rom from o2 site : 'Xda-Atom-ENG-20060426-MOT0822.exe'
The device stay in "O2" screen. this device can switch to diagnostic mode.
what should I do?
Note I repeated loading rom but Ietunai problem in Flash
Probably the Radio Hardware broken.... try to install without the Radio ROM.
sliders7 said:
Probably the Radio Hardware broken.... try to install without the Radio ROM.
Click to expand...
Click to collapse
from wher i can find that rom ?
or can u upload it ? for me plzzzz
http://pdaviet.net/showthread.php?t=17158
you can find how to flash rom without bootloader, extended rom , radio.
read my first post
medkid said:
http://pdaviet.net/showthread.php?t=17158
you can find how to flash rom without bootloader, extended rom , radio.
read my first post
Click to expand...
Click to collapse
but my phone is dead and it fail when i try to unpgrade it and it gave this eorr ===
!!!Please use DSUU in OS mode and syno with PC first !!!
usb transfer fail.
what shoud i do now plzz help me i dont know how to get it in DSUU mode its gose on boot loader but cant get it in to DUSS MODE
my Xda Atom Exec o2
waseemraj said:
but my phone is dead and it fail when i try to unpgrade it and it gave this eorr ===
!!!Please use DSUU in OS mode and syno with PC first !!!
usb transfer fail.
what shoud i do now plzz help me i dont know how to get it in DSUU mode its gose on boot loader but cant get it in to DUSS MODE
my Xda Atom Exec o2
Click to expand...
Click to collapse
u can't update using DSUU from activesync anymore. since u got broken ROM.
u must use Bootloader by pressing:
-power + camera + reset
-plug the USB
-start the update using DSUU.
sliders7 said:
u can't update using DSUU from activesync anymore. since u got broken ROM.
u must use Bootloader by pressing:
-power + camera + reset
-plug the USB
-start the update using DSUU.
Click to expand...
Click to collapse
i just do as u say but the but it fail gives the eorr as i told in my last post
and plzz tell me is i just have to get it in bootmode and conact it with usb and start updating
what is DSUU?? is this the file Xda-Atom-Exec-ENG-20060721-MOT0822 ? or what ?
Easy fix, check post #12 http://forum.xda-developers.com/showthread.php?t=319945&page=2&highlight=EBOOT
more than likely you will need a 256 or 512MB SD Card, the method discussed here (in most cases) will not work with higher capacity cards. Check the Atom Wiki too.
homer285 said:
Easy fix, check post #12 http://forum.xda-developers.com/showthread.php?t=319945&page=2&highlight=EBOOT
more than likely you will need a 256 or 512MB SD Card, the method discussed here (in most cases) will not work with higher capacity cards. Check the Atom Wiki too.
Click to expand...
Click to collapse
i tryied that too but still same postion.....
what shoud i do now plzzz help me i tell u again what it look like
====================================================
USB connected,waiting for download ..............
!!!Please use DSUU in OS mode and syc with PC first!!!
Usb Transfer fail
some one plzzzz help me ? for my atom exec
waseemraj said:
some one plzzzz help me ? for my atom exec
Click to expand...
Click to collapse
well...
after u see bootloader screen and waiting to download.
it should be ok to connect to USB and PC will recognize it for sure!
if doesn't... u should try different computer. not yours. just borrow somebody else computer... see the outcomes? just in case u got error/corrupted activesync.
if still not working... u must using SD card upgrade.
Use any ROM.. use WM5 Official ROM.
Extract the ROM.
put: diskimage_Ver.nb0 to the Blank SD card (use 512MB or 1GB)
and activate the bootloader again.
If your device are normal.. it should looking for SD card and start installing the ROM. If your device badly damage.. it will NOT run both method.
i don't know this is your hardware or Software are damage.
Maybe u should send it to the repair... hopefully u still got the warranty.
If Hardware is the problem, usually they replace the motherboard.
because no way to fix NAND memory module.
just keep trying... don't try one time only...
Good Luck & Pray!
sliders7 said:
well...
after u see bootloader screen and waiting to download.
it should be ok to connect to USB and PC will recognize it for sure!
if doesn't... u should try different computer. not yours. just borrow somebody else computer... see the outcomes? just in case u got error/corrupted activesync.
if still not working... u must using SD card upgrade.
Use any ROM.. use WM5 Official ROM.
Extract the ROM.
put: diskimage_Ver.nb0 to the Blank SD card (use 512MB or 1GB)
and activate the bootloader again.
If your device are normal.. it should looking for SD card and start installing the ROM. If your device badly damage.. it will NOT run both method.
i don't know this is your hardware or Software are damage.
Maybe u should send it to the repair... hopefully u still got the warranty.
If Hardware is the problem, usually they replace the motherboard.
because no way to fix NAND memory module.
just keep trying... don't try one time only...
Good Luck & Pray!
Click to expand...
Click to collapse
The above information will likely do more harm than good!
waseemraj said:
i tryied that too but still same postion.....
what shoud i do now plzzz help me i tell u again what it look like
====================================================
USB connected,waiting for download ..............
!!!Please use DSUU in OS mode and syc with PC first!!!
Usb Transfer fail
Click to expand...
Click to collapse
Bro I have recovered from this 20+ times, if its not working (and you can enter bootloader mode) then you're doing something incorrectly, either that or your memcard is incompatible, remember in most cases 256 or 512MB are the only working sizes! So place that EBOOT.nbo into and "empty" SDCard with your PC, enter the bootloader then stick the card in.... It wont take long, once you the screen goes black pull out the SDcard and then enter bootloader, plugin your USB and execute official O2 rom AKU2.2
The flash may not finish completely freezing in the Extended rom update, dont panic! unplug, softreset then flash in DSUU mode...easy as! works every time!
homer285 said:
Bro I have recovered from this 20+ times, if its not working (and you can enter bootloader mode) then you're doing something incorrectly, either that or your memcard is incompatible, remember in most cases 256 or 512MB are the only working sizes! So place that EBOOT.nbo into and "empty" SDCard with your PC, enter the bootloader then stick the card in.... It wont take long, once you the screen goes black pull out the SDcard and then enter bootloader, plugin your USB and execute official O2 rom AKU2.2
The flash may not finish completely freezing in the Extended rom update, dont panic! unplug, softreset then flash in DSUU mode...easy as! works every time!
Click to expand...
Click to collapse
Confirm!!!
I have done this also even using 1 GB memcard, my memcard is NCP mini SD.
I don't know it was lucky or it does work for 1 GB memcard. Even with non empty one.
But becareful, maybe I am just lucky, perhaps you should use 256 MB or 512 MB only.
homer285 said:
The above information will likely do more harm than good!
Click to expand...
Click to collapse
hei... he is desperately need help.
We all want to help him, thats all i can offer.
If you have different method.. thats a good news for him.
everybody here try to help him.. contribute something to help him.
so no more harm to his already broken device.
think the brighter side!
cheers

Sim Free Tytn Upgrade To Wm6 Help Please

Hi, Let me honestly admit that I am a newby and have read the threads over the last few weeks so much that I'm really confused now. I read one thing which then asks you to click and read another, but the answers I want are only partly found.
So I hope someone can please take pity on me and answer the following:
I have a TyTN SIM FREE phone which has a Orange sim card. In fact, Virgin & o2 cards have been used on it but Orange seems the best at the mo'.
Does that mean its unlocked?
I am trying to upgrade to WM6 (without even thinking about WM6.1), but "Error 260" comes up each and every time. I have tried 150+ and its still the same.
Please believe me that I have tried every way mentioned on these forums. I've tried on a xp (I have Vista) and its still the same.
My phone screen just goes black when trying to install, then the error comes up.
What exactly is "OPEN PORT" ? I cannot find a thread that actually EXPLAINS that. What do I have to do when it says:"Reset your computer"? Which one, the desktop or the TyTN? If the latter, I have reset so many times. If the desktop, what do I have to reset?
My TyTN tells me that its a HERM 200 IPL- 1.00 and HERM 200-2.03.
If someone can just list in a order what I have to do in order to get this upgrade I would be for ever grateful. HTC do not want to know & London HTC Support Hotline was a washout.
I do hope to hear soon, cos' its started to drive me mad now.
reset both, try unplugging usb cable and plugging into another usb port if prob persists...
1). download and install Hard SPL ver 7. Here http://forum.xda-developers.com/showthread.php?t=296722
This makes it easier or possible to unbrick your phone if something does(will) go wrong. THIS IS A MUST!!!!!!!
2). Once you have Hard SPL on your phone, you can either use the pc to flash OR the sd card method. I personally prefer the sd method as its harder to brick your phone. To do this, download the HERMES rom of your choice. Unzip(rar) the file and generally there are 2 files. RUU_Wrapper.exe & RUU_signed.nbh. Copy the RUU_signed.nbh onto a fat 32 formatted memory card and rename it to "HERMIMG.NBH". Put it back in the hermes and go to bootloader( hold power and OK button(above the flywheel) and then reset with the stylus. hold ALL the buttons down until it goes into tricolour screen. It should automatically detect the flash file and start the upgrade process, follow the prompts... Please remember to either delete or change the name of the .nbh file else it will upgrade next time you go into bootloader.
Hope this helps... Cheers...
Hi. Thank you for your reply and at the mo' I'm trying to get the Hard SPL7 file on my pocket pc. I've never come across something which sounds easy but being very difficult! The file is on my phone, but "will not unzip 'cos .net compact framework is not on my pocket pc" when I am staring at it in the face in my downloads.
What I've decided to do is to do a hard reset and start afresh. I'll let you know how I get on....
download it to your computer, not the phone
pls see the guides here: www.mrvanx.org
Sorry not been able to try anything yet due to illness. Going to try tomorrow & I hope it works. Not tried for a while and already dreading it.
I'll let you know how I get on. Thanks for your replies.
Hi everyone. Just letting you know a friend of mine upgraded my pocket pc. He said it was "hard work" but he did it!
The phone works great and is much faster, but now I have another problem. It will not sync with WMDC.
It is possible a new thread will be following soon. I am at present, following other people's advice.
Thanks for everyone's help.
beegeebopper said:
Hi everyone. Just letting you know a friend of mine upgraded my pocket pc. He said it was "hard work" but he did it!
The phone works great and is much faster, but now I have another problem. It will not sync with WMDC.
It is possible a new thread will be following soon. I am at present, following other people's advice.
Thanks for everyone's help.
Click to expand...
Click to collapse
Letting us know what ROM you had flashed with would help. As the different ROMs have different solutions in solving that WMDC problem.

Xda 11 (o2) In Boot Cannot Upgrade

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.

Rom Update - Connection Problem

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

Categories

Resources