hey.
i wanted to upgrade my o2 Xda Exec to WM6, i am not a stranger to flashing, and enjoy modifying consoles and such.
however i am running windows vista, and got the connection error (yes, i read through the stickies first) I was now stuck on the bootloader screen, no matter what i could do, and none of the utitlities, including mtty would work.
upon deeper research i learned that vista was a problem for flashing.
So i took my xda to a windows xp machine that i had freshly set up the day before:
installed active sync,
installed drivers,
disconected xda,
unchecked activesync usb connections,
restarted,
Installed "XDA_EXEC_WWE_21200_21207_11500.exe"
It then appeared to succesfully work.
upon hard rebooting though, i now have no screen, no bootloader, and no connectivity, hard rebooting brings up the white screen, upon hitting 0, nothing happens... i fear it is now bricked....
Will not charge, no orange light comes on when plugged either directly into power, or directly into computer.
its now an "Unknown Device" in vista and a "device thats malfunctioned" in xp, i cant connect anything too it.
mtty wont give me any options other than COM, on vista or xp.
can anybody offer any oppinions?
This is the device in question:
http://www.my-xda.com/xdaexec.html
Vista doesn't have any problems! I have flashed my XDA so many times under Vista that I count them! You only need the right driver that have been posted several times here in the forums! It is not Vista's fault the the stupid flash utility is as old as the earth itself!
i tried updating the drivers before flashing, with the ones i downloaded from here, but it said i couldnt as the drivers i had were better, even after uninstalling and re installing...
as a side note i found this if its of interest to anybody:
offical xda upgrade
http://www.my-xda.com/downloads/Xda_Exec_Upgrade_v1.30.162.exe
I have updated them manualy! And everything is fine! You only need to kill Sync center and Mobile device Center from task manager before flashing!
ok, well can anybody help me understand whats happened?
are there any steps i can take to diagnose any further, or will i write it off as a brick/
i tried updating the drivers manually, and it didnt work, mobile device center was disabled as well. yet something went wrong, it wouldnt connect, but it got far enough to wipe my rom. i had no version numbers of anything, and just a bootloader screen, after trying to upgrade with windows xp, i now have no response at all from my xda, it wont charge or anything.
can anybody help me diagnose any further? or help me understand what went wrong, if its not a case of windows vista and old programs.
Same for me ...
Xiviliai said:
ok, well can anybody help me understand whats happened?
are there any steps i can take to diagnose any further, or will i write it off as a brick/
i tried updating the drivers manually, and it didnt work, mobile device center was disabled as well. yet something went wrong, it wouldnt connect, but it got far enough to wipe my rom. i had no version numbers of anything, and just a bootloader screen, after trying to upgrade with windows xp, i now have no response at all from my xda, it wont charge or anything.
can anybody help me diagnose any further? or help me understand what went wrong, if its not a case of windows vista and old programs.
Click to expand...
Click to collapse
If you have noy figured it out yet then i would say i have exactly the same problem with my xda exec and i proved to be installation problem, what i did was, reflashed with original wm5 ROM first, after setting it up completelyi then flashed again with wm6, problem resolved automatically... so good news is your xda is still very much alive.i used windows XP though... give it a try mate!!
Manual bootloader mode and then reflash with an original rom of your choice.
That'll do the trick.
Psi
diffrences ??
hey can anyone enlighten me on wats the difference between o2 cda exec and imate jasjar ?? coz both seems to have the same specification and same functionality?
DEAD XDA brought back to life
I recently upgraded my XDA Exec to WM6 with no problems so offered to do same for my sisters XDA Exec but part way through activesync crashed. Needless to say after that her XDA was dead wouldn't do anything at all and appeared to have no usb connection no charging nothing. After a hard reset I did get the reset screen but pressing "0" or "x" did nothing.
After much reading of many forums I couldn't find the answer to this and so I had to give my sister mine Boo Hoo!!
Anyway not one to give up this is how I fixed it
I happen to have the XDA plugged into a different usb port to what I normally use and done a hard reset on it then pressed "0" then the PC popped up saying found new hardware and it was installed and working so I looked hard at the unlit and what appeared to be blank screen of the XDA I noticed then it said "usb" at the top and "2.0" at the bottom so I ran http://www.my-xda.com/downloads/Xda_..._v1.30.162.exe which doesn't need activesync even though it say it does on the start screen just carry on it found it ok and now its all back and working ok.
This may not work for you but the usb thing is easy to miss if you use the same port all the time and the instructions tell you you need activesync to run the flash program is misleading. Just to note I did have activesycn 4.5 installed and running when I run the xda up date exec but I'm certain it played no part in the process.
Of course I wish I had found this before I spent £150 on a replacement
anyone need an XDA Exec for Xmas????
wohooo free xda?me!me!
please help
p24hrsmith said:
I recently upgraded my XDA Exec to WM6 with no problems so offered to do same for my sisters XDA Exec but part way through activesync crashed. Needless to say after that her XDA was dead wouldn't do anything at all and appeared to have no usb connection no charging nothing. After a hard reset I did get the reset screen but pressing "0" or "x" did nothing.
After much reading of many forums I couldn't find the answer to this and so I had to give my sister mine Boo Hoo!!
Anyway not one to give up this is how I fixed it
I happen to have the XDA plugged into a different usb port to what I normally use and done a hard reset on it then pressed "0" then the PC popped up saying found new hardware and it was installed and working so I looked hard at the unlit and what appeared to be blank screen of the XDA I noticed then it said "usb" at the top and "2.0" at the bottom so I ran http://www.my-xda.com/downloads/Xda_..._v1.30.162.exe which doesn't need activesync even though it say it does on the start screen just carry on it found it ok and now its all back and working ok.
This may not work for you but the usb thing is easy to miss if you use the same port all the time and the instructions tell you you need activesync to run the flash program is misleading. Just to note I did have activesycn 4.5 installed and running when I run the xda up date exec but I'm certain it played no part in the process.
Of course I wish I had found this before I spent £150 on a replacement
anyone need an XDA Exec for Xmas????
Click to expand...
Click to collapse
can u please give the link again ??
your download link is invalid....can you post the file?
my jasjar is stuck and the pc wont accept it as a usb device....
02 XDA Exec Bricked
Hi - I have the same problem - the links dead can you post the file pls?
Fixed now:
This issue has now been resolved, not sure if you need to do all the steps but they worked for me:
1. Remove SIM card and SD card
2. Reinstall Active Sync and reboot
3. Reapply ROM
For me it doesn't work :-(
I am searchin since one month to find a way to get my Mda Pro to work... - On the Display says "Serial" when it is plugged...
Xiviliai said:
hey.
i wanted to upgrade my o2 Xda Exec to WM6, i am not a stranger to flashing, and enjoy modifying consoles and such.
however i am running windows vista, and got the connection error (yes, i read through the stickies first) I was now stuck on the bootloader screen, no matter what i could do, and none of the utitlities, including mtty would work.
upon deeper research i learned that vista was a problem for flashing.
So i took my xda to a windows xp machine that i had freshly set up the day before:
installed active sync,
installed drivers,
disconected xda,
unchecked activesync usb connections,
restarted,
Installed "XDA_EXEC_WWE_21200_21207_11500.exe"
It then appeared to succesfully work.
upon hard rebooting though, i now have no screen, no bootloader, and no connectivity, hard rebooting brings up the white screen, upon hitting 0, nothing happens... i fear it is now bricked....
Will not charge, no orange light comes on when plugged either directly into power, or directly into computer.
its now an "Unknown Device" in vista and a "device thats malfunctioned" in xp, i cant connect anything too it.
mtty wont give me any options other than COM, on vista or xp.
can anybody offer any oppinions?
This is the device in question:
http://www.my-xda.com/xdaexec.html
Click to expand...
Click to collapse
I rather think that you should first check whether your phone is really bricked, to read the instructions regarding this and to see how to recover from the brick
After you have recovered you phone, I recommend that you use Windows Mobile 6.5!
Thanks!
Always glad to help!
Have you seen the post date above you
Most likely he already solved or got another device
Besides that link does not include HTC Universal
Related
My DOPD - bought in China was running a chinese version of WM5.0 and I wanted to install a english version.
After upgrading my DOPOD 900 with the upgrade : Universal_Upgrade_v1.30.68_radio_1.09.0.zip I have problem.
It is really DEAD. soft reset does nothing and a hard reset only gives the option of "0" and "X" which do nothing.
the USB is no longer recognised and nothing seems to want to communicate with the Dopod. It seems the USB loader program is no longer running on the Dopod.
Has anybody any idea how I can attach to the device an install a new bootloader, or something.
I had the same issue and I have a solution. But, let me tell you my process that got me where you are.
I tried performing the update using the No_ID (or whatever) method and kept getting errors. I rebooted my PC and changed the Operator ID using the HTC64 Extended ROM Tool.
After this, I was able to use the typical installer. The flash went fine and I hard reset as instructed. From that point on, I had your exact problem.
A dead screen. I was able to redo the hard reset after pulling the battery but I would just end up with the dead (blank) screen again. ONCE, I did get it into boot loader mode where I could actually read the screen. But, of course I reset and again had a dead screen.
My solution was to revert back to a true O2 ROM. Even though I couldn't see the screen (still can't), the ROM update is proceeding as I type this. I'm at 44% of the radio ROM installed.
Hope this gives you hope!
Well, good news. I just finished the ROM update and I'm looking at the O2 boot image.
Is there any indication that the QTek ROM looks for the Carrier info to be QTek or it will fail once installed? Just wondering why I had this problem.
ARG! Reflashing with QTek ROM did the same thing. :evil:
Blank screen and all.
check 2 things
uncheck usb from active sync
hardreset after upgrade has been completed
just do the upgrade again and it should come alive again
Thanks and another question
Well thanks for the hope. but I have tried this already with no luck, however after this message I will try again. My biggest problem is that I cant regain communication over the usb.
I would like to know how your system behaved when you plugged in your apparantely dead device. My system just says device un recognised and I cant begin a download with or without active sync.
So I cant get another rom image to download.
regards
Nick
dolebole said:
check 2 things
uncheck usb from active sync
hardreset after upgrade has been completed
just do the upgrade again and it should come alive again
Click to expand...
Click to collapse
This was the first thing I did.
The problem is that I cannot get any communication over the USB.
The device is unrecognised on USB and after starting any ROM download it just timesout after "checking information from device" message .
Ever seen a dead USB interface like this ?
The USB PnP mgr sees the hardware but cannot establish the device type !!
Nick
@mobinick: You and I have the same situation.
I have 2 Universal dead like this. 1 Exec and 1 Jasjar.
Both dead, blank screen, can not enter bootloader, can not connect with PC. PC can not recognize the driver usb of the device.
I opened the phone and found that logically everything is so so. There is no clue about hardware.
So I think: the address of the bootloader with device ID maybe unlucky damaged.
Who can fix this problem pls share us some experience.
Thanksss
ta_mobile said:
@mobinick: You and I have the same situation.
I have 2 Universal dead like this. 1 Exec and 1 Jasjar.
Both dead, blank screen, can not enter bootloader, can not connect with PC. PC can not recognize the driver usb of the device.
I opened the phone and found that logically everything is so so. There is no clue about hardware.
So I think: the address of the bootloader with device ID maybe unlucky damaged.
Who can fix this problem pls share us some experience.
Thanksss
Click to expand...
Click to collapse
Why don't you guys take it to your respective service centres and get it fixed?
Even if you have to pay something, it will certainly be better than these bricks occupying table space.
Have you tried going back to an original O2 ROM? I went to 1.13.139 WWE and all is fine now.
Just to share my experience with you guys here:
I posted my problem way back during the Radio Upgrade from 1.04 to 1.06. My Dopod 900 got stuck on the splashscreen. I couldn't get my device to pass the splashscreen even after upgrading/downgrading the radio ROM back and forth two times.
Finally, I just forced my device into bootloader mode (Backlight+Reset+Power). Even after doing this, the dopod screen was completely blank (no indication of serial/usb letter on the screen). I downloaded the official O2 exec ROM and plug my device (in bootloader mode) back to the USB port. It said unrecognized port on my PC. Despite that, I reflashed my Dopod back with the NoID tool the complete O2 ROM (Radio, Main ROM & The extended). Once completed, my device regained its consciousness.
I managed to flashed back the 1.06 radio after that. And has since been upgraded 4 times (two i-mate, one Orange and the latest QTek ROM) with no problem whatsoever.
I had the exact same problem as you to guys, i tried to update it, and it wouldn't budge...
It constantly, without fail timed out... I tried everything...
As my hope started to wain, i gave it one last shot...
I took out everything, sim and sd and battery, then connect the battery back and from the bootloader menu, connected it to the pc, with usb cable...
Finally it worked!! Like normal, i was able to load any and all rom and radio updates...
Wouldn't work, from the normal working screen (which was working for a while, i later tested this out, and found out ) and also wouldn't work, from the bootloader (power+backlight+reset) with sim+flash in there....
Hope you guys have some luck.. I htink you should, because i was in the exact same boots as you guys...
It worked for me
My O2 Exec did exactly the same thing, and I spent (on and off) 24 hours trying to get the damn thing to go again - wouldnt charge either....
I too finally took out everything, SIM and sd and battery, then connect the battery back and from the bootloader menu (which I only found about from this site), connected it to the pc, with usb cable...
It worked as well - bloody brilliant. I now have the latest 02Exec Upgrade (Version 1.30.162 AKU2 Release) and all is great.
Cant believe that 2 days after logging email with O2 site, they have not responded...
Would almost kiss you guys.....
Solution for getting stuck in bootloader
http://wiki.xda-developers.com/index.php?pagename=Instructions for those stuck on Boot Screen
Hi all,
I've the following problem. A friend told me he found a new AKU 3.5 rom of Helmi and he sent it to me.
I unzipped it, checked the files who lookeed good and flashed my universal.
Once finished, tried reboot and got black screen.
After spending 2 hours to go back in bootloader mode (no success) and after looking in the files, seems he sent me a Blue Angel rom and no Universal.
Phone refuse to go in bootloader mode. Black screen. :s but when I put it in usb, windows says unrecognized USB device.
Any one can help please :$
Think Xanaxer needs his account deleted...sorry I can't help with the OP's problem
gloom said:
Hi all,
I've the following problem. A friend told me he found a new AKU 3.5 rom of Helmi and he sent it to me.
I unzipped it, checked the files who lookeed good and flashed my universal.
Once finished, tried reboot and got black screen.
After spending 2 hours to go back in bootloader mode (no success) and after looking in the files, seems he sent me a Blue Angel rom and no Universal.
Phone refuse to go in bootloader mode. Black screen. :s but when I put it in usb, windows says unrecognized USB device.
Any one can help please :$
Click to expand...
Click to collapse
I just tried several previous official and un-official upgrades but none detected the universal.
Tried mtty methode too but nothing detected on USB port. (Killed active sync modules with task manager)
Tried several times to enter in bootloader mode but nothing displays on screen like before. Screen stays black.
I hope it isn't broken cause seems windows detected something pluged on the usb
gloom said:
Hi all,
I've the following problem. A friend told me he found a new AKU 3.5 rom of Helmi and he sent it to me.
I unzipped it, checked the files who lookeed good and flashed my universal.
Once finished, tried reboot and got black screen.
After spending 2 hours to go back in bootloader mode (no success) and after looking in the files, seems he sent me a Blue Angel rom and no Universal.
Phone refuse to go in bootloader mode. Black screen. :s but when I put it in usb, windows says unrecognized USB device.
Any one can help please :$
Click to expand...
Click to collapse
your best bet with be take it back to your mobile phone vendor, because the motherboard is messed, and nothing can be done apart from replacing the motherboard
coolbeans252 said:
your best bet with be take it back to your mobile phone vendor, because the motherboard is messed, and nothing can be done apart from replacing the motherboard
Click to expand...
Click to collapse
No other way to get it back in bootloader mode ?
since the bootloader is also overwritten with something from the BA ROM, it is improbable.
Hi !
I had a similar problem, but I am in bootloader mode, but I can't reflash my board. Does anyone knows how should I do ?
Thanks
i got mine yesterday and i was playing around with it ,and i was about to upgrade it to windows mobile 6 ( and don't even now why ) and the device rebote and got stuck on boot loader page showing the serial , and version number, since last night i kept searching about this issues , i found so many article as well , so many of them talked about hard booting the device by pressing this and that , well i tried every single one but non worked.
and i need to mention that i dont have the usb driver for it so icant to anything from the computer.
Could you please help me , right now i feel so bad i wasn't even working with it for an hour.
Thanks
sepandar said:
i got mine yesterday and i was playing around with it ,and i was about to upgrade it to windows mobile 6 ( and don't even now why ) and the device rebote and got stuck on boot loader page showing the serial , and version number, since last night i kept searching about this issues , i found so many article as well , so many of them talked about hard booting the device by pressing this and that , well i tried every single one but non worked.
and i need to mention that i dont have the usb driver for it so icant to anything from the computer.
Could you please help me , right now i feel so bad i wasn't even working with it for an hour.
Thanks
Click to expand...
Click to collapse
A few things:
When the phone is at the screen and shows serial, does it change to USB if you plug the cable into a computer?
The needed 'drivers' for the phone are part of the activesync install. However, those only come into play when the phone is booted. The docs you found probably mention using mtty. A 'driver' for the phone is irrelevant at this point.
Oh,
Yes when i plug the usb cables change from serial to usb ?
Does that makes life easier or harder
sepandar said:
Oh,
Yes when i plug the usb cables change from serial to usb ?
Does that makes life easier or harder
Click to expand...
Click to collapse
Easier.
Your phone is stuck in bootloader mode. Try flashing it again.
If that doesn't work, try following the instructions here:
http://wiki.xda-developers.com/index.php?pagename=BA_FAQ_STUCK_AT_STARTUP
Thanks alot dude
Thanks so much man i honestly i was freaking out, i thought the device is not good any more and goes to recycle bin
so as an expert what do u think of upgrading the OS to wm6 ?
jdc said:
Easier.
Your phone is stuck in bootloader mode. Try flashing it again.
If that doesn't work, try following the instructions here:
http://wiki.xda-developers.com/index.php?pagename=BA_FAQ_STUCK_AT_STARTUP
Click to expand...
Click to collapse
I try many time with mtty 1.42 but my device still has 4 lines color when start up.
How can I do.
picheth
sepandar said:
Thanks so much man i honestly i was freaking out, i thought the device is not good any more and goes to recycle bin
so as an expert what do u think of upgrading the OS to wm6 ?
Click to expand...
Click to collapse
Well...
If you are fine with 2003, then don't change it.
Personally, I'm running WM6 on mine and I like it. It's a rather large improvement over WM5. However, anything beyond the original OS is a hack, and is not going to be perfect. WM5 and WM6 both have their issues, bugs, and limitations on the angel. But if you are aware of them and can deal with them, it's worth the effort.
Follow the wiki for upgrading, it covers going to WM6, with directions on how to go back to 2003 if you want. Check them both out and stick with what works for you.
ok man thank for your info i acttualy upgarded to wm6, i just wondering is there any way to get rid off the first screen that you see after restarting the device ( i mean the screen with four colours ) ?
sepandar said:
ok man thank for your info i acttualy upgarded to wm6, i just wondering is there any way to get rid off the first screen that you see after restarting the device ( i mean the screen with four colours ) ?
Click to expand...
Click to collapse
As far as I know, no. It's a side affect of the fact that WM5/6 is a hacked ROM, running on a device that was never intended to run what it is able to run now.
Hi, i have just bought a new imate jasjam and uploaded the windows mobile 6 as per your instructions. Everything was going ok, then active sync kept stuffing up, i reinstalled it 3 times and only sometimes works, i have limited to no connectivity in my LAN, and my imate takes 2hrs to do anything once i touch the screen. i have tried hard resetting etc nothing! i have searched and searched for everything and found nothing, i eally hope someone can help me, i am at my wits end!
PLEASE HELPPPPPPPPPPPPPPP
Try putting it into bootloader and flashing hard spl and flash a new rom after that.
thank you!
i just tried to do that and it said error please connect the usb to the phone etc..and it is..
if this helps anyone- ipl 1.04 and spl.2.10.0lipro?
ggrrrr
Can you tell us what ROM you are trying to flash, and what OS you are using to connect with?
ROM VERSION: 3.30.2.1
ROM DATE: 05/15/07
RADIO:1.38.30.10
PROTOCOL:32.71.7020.12H
I have a windows xp sp2
i am so grateful to everyones input. thanks
usb connectivityy
Goto to the usb settings under communication and remove the tick from advanced usb fuctionality. Maybe unplug from USB first before doing that.
Thanks, have just tried that but it didnt work, still got the red cross on the icon and limited to no connectivity thru the LAN. i am so lost, i should have just left the phone as is ;-(
have you tried loading into the bootloader and then connecting the jasjam to your pc?
How to get into the bootloader is described here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Resets
once connected just run the offical update from telstra (which is a damn good rom btw) and it should return your jasjam to normal. The latest Offical update can be found here - http://forum.xda-developers.com/showthread.php?t=348436&highlight=telstra
hope that helps
edit; should have read first post. hmmm. try uninstalling activesync and reinstalling it, or try on another computer. i had this problem awhile ago, can't remember exactly how i fixed it, but it was a combination of new activesync, bootloader and hardresetting
ok, i have reset it- is the bootloader screen the one with 3 colours with ipl etc on it?
i connected it and it then said usb on the screen, but activesync can't connect it?
When you get to the bootloader screen with the 3 colors you need to reflash with a new ROM
thanks to everyone, i am now back and running! god knows hoe but thanks!
Hello everyone!
I'm new at these forums, so excuse me if I'm being a "noob". I've searched all over the forums and found some instructions for my problem, but none of them helped.
My story is:
I have a T-Mobile MDA III device (I think it's also called HTC BlueAngel). It had the stock ROM, without any modifications. It was WM2003 I suppose.
I wanted to upgrade it to WM6, using this. In that thread it was recommended to use the updater given there, so I downloaded everything and tried to flash. After about 30 seconds of verifying information on the PDA, I got to a screen where it was supposed to say From and To version numbers, but everything was blank. I also have successfully flashed a HTC Trinity P3600 and those fields were blank there too, so I thought it's OK and pressed Continue. The program started to process, but after a while it said isn't designed for my device. I have tried numerous ROMs and RUUs to update it, but all of them gave some sort of error, some said "Congratulations, update complete" even if it didn't do anything.
The problem is, that my PDA is now stuck at the bootloader (?) screen. The backlight is off, the top of the screen says Serial (USB when cradled) and on the bottom I can see a version number (v2.05). I have read about key combinations (Camera, power, reset, record, etc) which are used to exit this state, but none of them worked. If I cradle my device, Windows (Windows 7, 64bit) recognizes the device as "Microsoft USB Sync", but WMDC doesn't see my device at all. On the forums I've read that in this state the device allows ROM updating, but I haven't found anything that could work, and the RUUs don't seem to recognize my device.
So if anyone has a ROM and updater that can work with this device, please link it to me, it's very important. I don't want to lose my PDA. If you haven't got a WM6 ROM, it can be even WM5, or even the stock ROM of this device, I just want to somehow revive it. Really, any ROM will do, just give me the proper updater and ROM. Or if you think the ROM wasn't erased from the device, please help me getting back to it.
JiGSaW_HTC said:
Hello everyone!
I'm new at these forums, so excuse me if I'm being a "noob". I've searched all over the forums and found some instructions for my problem, but none of them helped.
My story is:
I have a T-Mobile MDA III device (I think it's also called HTC BlueAngel). It had the stock ROM, without any modifications. It was WM2003 I suppose.
I wanted to upgrade it to WM6, using this. In that thread it was recommended to use the updater given there, so I downloaded everything and tried to flash. After about 30 seconds of verifying information on the PDA, I got to a screen where it was supposed to say From and To version numbers, but everything was blank. I also have successfully flashed a HTC Trinity P3600 and those fields were blank there too, so I thought it's OK and pressed Continue. The program started to process, but after a while it said isn't designed for my device. I have tried numerous ROMs and RUUs to update it, but all of them gave some sort of error, some said "Congratulations, update complete" even if it didn't do anything.
The problem is, that my PDA is now stuck at the bootloader (?) screen. The backlight is off, the top of the screen says Serial (USB when cradled) and on the bottom I can see a version number (v2.05). I have read about key combinations (Camera, power, reset, record, etc) which are used to exit this state, but none of them worked. If I cradle my device, Windows (Windows 7, 64bit) recognizes the device as "Microsoft USB Sync", but WMDC doesn't see my device at all. On the forums I've read that in this state the device allows ROM updating, but I haven't found anything that could work, and the RUUs don't seem to recognize my device.
So if anyone has a ROM and updater that can work with this device, please link it to me, it's very important. I don't want to lose my PDA. If you haven't got a WM6 ROM, it can be even WM5, or even the stock ROM of this device, I just want to somehow revive it. Really, any ROM will do, just give me the proper updater and ROM. Or if you think the ROM wasn't erased from the device, please help me getting back to it.
Click to expand...
Click to collapse
Remove the battery and look which model you have....
something like PH20B or the FCCID: xxxBLUEANGEL...
d-two said:
Remove the battery and look which model you have....
something like PH20B or the FCCID: xxxBLUEANGEL...
Click to expand...
Click to collapse
It says:
PH20B MDA III
FCCID: NM8BLUEANGEL
JiGSaW_HTC said:
It says:
PH20B MDA III
FCCID: NM8BLUEANGEL
Click to expand...
Click to collapse
Please look here for install the right driver for windows 7 64x
d-two said:
Please look here for install the right driver for windows 7 64x
Click to expand...
Click to collapse
Thanks, I've downloaded the PDFs and tried to follow the steps, but there were some problems.
The first strange thing I noticed was that the driver said it was already installed to my computer. I think that's not a problem, but still worthy to mention.
I have completed the driver installation, so I moved on to the ExtROM tutorial. Unfortunately this step failed completely, because it needs a working BA, and as I've said I'm stuck on the bootloader screen. Also I've tried to reflash the WM2003 that was in the tutorial, but it said that the Updater is not designed for my device. So I moved on to the final step, flashing - I downloaded the Updater and tried to flash the WM2003 you provided. I kept pressing Continue - but after getting to the last page, and pressing Continue for the last time, after about 10 seconds, the updater said Congratulations! The ROM have been updated successfully. But that was just a message, my BA acted like nothing happened. I'm still in the Bootloader and can't do anything. What am I doing wrong?
JiGSaW_HTC said:
Thanks, I've downloaded the PDFs and tried to follow the steps, but there were some problems.
The first strange thing I noticed was that the driver said it was already installed to my computer. I think that's not a problem, but still worthy to mention.
I have completed the driver installation, so I moved on to the ExtROM tutorial. Unfortunately this step failed completely, because it needs a working BA, and as I've said I'm stuck on the bootloader screen. Also I've tried to reflash the WM2003 that was in the tutorial, but it said that the Updater is not designed for my device. So I moved on to the final step, flashing - I downloaded the Updater and tried to flash the WM2003 you provided. I kept pressing Continue - but after getting to the last page, and pressing Continue for the last time, after about 10 seconds, the updater said Congratulations! The ROM have been updated successfully. But that was just a message, my BA acted like nothing happened. I'm still in the Bootloader and can't do anything. What am I doing wrong?
Click to expand...
Click to collapse
You have not read the tutorial right... you must install the driver manual!!!!
JiGSaW_HTC said:
Thanks, I've downloaded the PDFs and tried to follow the steps, but there were some problems.
The first strange thing I noticed was that the driver said it was already installed to my computer. I think that's not a problem, but still worthy to mention.
I have completed the driver installation, so I moved on to the ExtROM tutorial. Unfortunately this step failed completely, because it needs a working BA, and as I've said I'm stuck on the bootloader screen. Also I've tried to reflash the WM2003 that was in the tutorial, but it said that the Updater is not designed for my device. So I moved on to the final step, flashing - I downloaded the Updater and tried to flash the WM2003 you provided. I kept pressing Continue - but after getting to the last page, and pressing Continue for the last time, after about 10 seconds, the updater said Congratulations! The ROM have been updated successfully. But that was just a message, my BA acted like nothing happened. I'm still in the Bootloader and can't do anything. What am I doing wrong?
Click to expand...
Click to collapse
Can't you exit bootloader screen by simultaneously pressing power and reset?
Did you disable USB-Connection in activesync? Is important to do.
If update runs till "congratulations" in very short time (update usually takes about 10 minutes - estimated ), it seems like updater didn't see the nk.nbf file, which should be 32.769KB.
Please don't throw bricked phones at me, but- is the file unzipped? (note: i don't mean opened)
And: though d-two has given you the drivers for Win7 (and he's the one you can really trust he's got the right stuff) you may just try
another PC. Many people have trouble when trying to update with Win7. I still use XP.
B-44 said:
Can't you exit bootloader screen by simultaneously pressing power and reset?
Did you disable USB-Connection in activesync? Is important to do.
If update runs till "congratulations" in very short time (update usually takes about 10 minutes - estimated ), it seems like updater didn't see the nk.nbf file, which should be 32.769KB.
Please don't throw bricked phones at me, but- is the file unzipped? (note: i don't mean opened)
And: though d-two has given you the drivers for Win7 (and he's the one you can really trust he's got the right stuff) you may just try
another PC. Many people have trouble when trying to update with Win7. I still use XP.
Click to expand...
Click to collapse
If I press power and reset simultaneously, the screen goes dead for a second, then bootloader comes up again.
Tried disabling USB connection in WMDC (No activesync for Win 7), it changed nothing.
The nk.nbf is EXACTLY 32.769KB, so I don't know why it won't see it. With some versions it sees it but gives me an error 150 (RUU not designed for this device).
If by unzipped you mean extracted, yes, all the files (EnterBL.EXE, nk.nbf, MaUpgradeUt_noID.exe, etc.) are extracted to a folder, it looks the same as in D-Two's tutorial.
Unfortunately I don't have an XP PC. Will using a Vista laptop do any better, or should I use some kind of emulator of XP and update from there? If so, can you link me to one of those?
Sh*t.
Take out the battery for at least three days.
Then retry.
I lately had an VPA3 revived by this.
Always stuck in first step of bootscreen, already wanted to abandon it,
then after some days retried just out of some mood.
Worked.
XP emulator may be a good idea, but i'd have to google it the same way like you.
Because of my Siemens phones i haven't yet left original XP.
B-44 said:
Sh*t.
Take out the battery for at least three days.
Then retry.
I lately had an VPA3 revived by this.
Always stuck in first step of bootscreen, already wanted to abandon it,
then after some days retried just out of some mood.
Worked.
XP emulator may be a good idea, but i'd have to google it the same way like you.
Because of my Siemens phones i haven't yet left original XP.
Click to expand...
Click to collapse
he is not stuck at the 4 color screen he stuck in the bootloader mode..
If the bootloader mode active with software is he not wakeup after 3 days without battery or something else...
the BLENTER.EXE erase at adress 0x40000 the first 4 bytes and this will active the bootloader mode!!!
you must install the driver like in the PDF!!!
and than you can flash it with any rom!!
if you have install the driver correct it must like this...
sorry for my bad english
d-two said:
he is not stuck at the 4 color screen he stuck in the bootloader mode..
If the bootloader mode active with software is he not wakeup after 3 days without battery or something else...
the BLENTER.EXE erase at adress 0x40000 the first 4 bytes and this will active the bootloader mode!!!
you must install the driver like in the PDF!!!
and than you can flash it with any rom!!
if you have install the driver correct it must like this...
sorry for my bad english
Click to expand...
Click to collapse
No problem about your english, mine isn't perfect too
I realized what is the problem. When installing the driver manually, it says that the driver is not signed, and therefore I can't install it. I do everything the same as you did, but I fail at this step. I can't get it to install. Any solutions for this? :\ I'm starting to worry about this.
JiGSaW_HTC said:
No problem about your english, mine isn't perfect too
I realized what is the problem. When installing the driver manually, it says that the driver is not signed, and therefore I can't install it. I do everything the same as you did, but I fail at this step. I can't get it to install. Any solutions for this? :\ I'm starting to worry about this.
Click to expand...
Click to collapse
Reboot your PC and press before windows start "F8" and select the option "Start without driver signature" or something else...
I don't know what is the exactly word spelling in English i use my windows in German :laugh:
d-two said:
Reboot your PC and press before windows start "F8" and select the option "Start without driver signature" or something else...
I don't know what is the exactly word spelling in English i use my windows in German :laugh:
Click to expand...
Click to collapse
Found this option and I could install the driver You sent to me.
But the RUU still doesn't see my device. It acts the same as I was running it without my device.
JiGSaW_HTC said:
Found this option and I could install the driver You sent to me.
But the RUU still doesn't see my device. It acts the same as I was running it without my device.
Click to expand...
Click to collapse
have you use my updater?
d-two said:
have you use my updater?
Click to expand...
Click to collapse
Ignore my previous message. I just needed to reboot the computer. It updates now!! Thank you VERY VERY MUCH!! Finally I can use my PDA again Pressing Thanks button