Hi please help me , i'm stuck in boot loader mode trying to update my rom to windows 6.1 , i have vista on my computer .
I searched the forum but cant find any useful help.
I know lot many had this problem and have got sorted out , so please help me with clear instructions.
Thanks in advance,
shank
since you are using vista, it is very unlikely, that your device is actually stuck in bootloader mode, it was your pc, causing that error. because the device changes its identity, while upgrading, vista (and windows 7) seem to think, it is necessary to look for new drivers. maybe you saw the driver search in the bottom right corner of the task bar.
so, basicly you have 2 options to get your device back, either you get to a pc with xp and perform the upgrade properly, or you try the vista method.
for the xp way, have a look here:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade1_WM2003SE0
that is the first step in the tutorial on how to upgrade and i bet you didn't do that in your first attempt
for the vista way, refer to this page:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade4_Vista
or if you want it in pictures, this:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel_WM6_WizzardUpgrade4_Vista_Pic
i personally never got the vista way to work, not in vista home premium 32, nor in ultimate 64, and in windows 7 ultimate 64 it does not work for me neither.
the very best you can do in your situation is, try the vista method, and either it works, than proceed with the wizard i gave you as the xp link, or get to an xp computer and start with the wizard right away.
if your device really is stuck in bootloader (still unlikely), post back, and we try mtty
got the same problem but am working under windows 7 x64 so it willl be a serious issue
neverdmind fixed worked on my laptop with xp
I am still stuck
Can do nothing. Have this message on the screen and even then I try to connect it to my Vista there is no connection.
Is it that ****ty or something can be done
welcome to the forum!
your problem starts with v and ends with a (like so many evil things do): vista. ok, that was off, sorry, let's get to the facts now:
this is probably what you have experienced during the unlucky attempt to upgrade your device:
you start upgrading, everything looks fine, your pc's RUU (the rom upgrade utility, what you used to start the upgrade) is working fine, your device's screen said usb and v2.0X and then "upgrading" but then at some point, your pc said, "wait a minute, this is not the device i am used to, i cannot charge or sync it, and it also does not respond with the usual name!" so, vista is as 'smart' as trying to get a new driver for the device, making the sounds of a usb device unplugging, and a new one plugging in, that's when your connection is lost, and that is bad, because the wizzard told you before, to "never unplug the device, unless the upgrade process is over". you see, what happened there?
vista's ability, to make driver installation easier for the user has become bad for you in this situation, as you were relying on, say, windows xp's stubbornness.
ok, you say, why would he tell me all that? i saw that happening!
yes, but now you know what caused the problem. now we get on to solving it.
there is a nice tutorial in the wiki, where you can find a driver for vista x86 and x64, that will behave like the xp driver used to, it will charge the device, sync it, and still be able to upgrade, you find the wiki entry -=here=-, and -=here=- again with screenshots.
when you arrived at successfully having installed the driver, so making the screen on connection change from serial to usb, without vista searching for new drivers, you arrived at the point, from where on you can continue, or better restart, flashing the rom you originally intended to.
but let me say, after breaking rule 1, when it comes to flashing, may i advice you to read a little more about the general topic in the link -=here=-, because i can guarantee you, that that was not the last mistake you made with the upgrading process, and since you probably don't want to start from scratch again in a few days, you should ask yourself these questions:
have i formatted the extrom?
have i resized the partitions to gain storage space?
do i have a proper RUU?
did i pick the right rom?
what about sim unlock?
what about radio rom update?
do i know how to reset a device with a higher os than wm2003?
if to either of these questions, your answer was not a clear "yes!!", but a "no" or even "what is he talking about?" you should definetely make a little research before starting over, because you are breaking hardware limitations here, doing things, htc originally intended trained service professionals to do, not home users, this is something that could break your device or at least cost you a lot of time to repair, when done wrong, so please read the links i gave you, it will save a lot of your nerves. here you are again, -=the most important link=-
and -=another link with a common misunderstanding cleared up=-
have fun reading, you won't regret it.
Related
I've stuggled on with the unreliable ROM that my PDA2K came with because I have been unsuccessful at upgrading using my Mac and Virtual PC 7 (Windows XP).
I don't have access to a PC, and wondered whether anyone could give me any guidance.
Is it possible to upgrade the rom directly from the device itself, or are there ROM installers for other Blue Angel phones that would work via Virtual PC?
Any help very welcome - but please give as much detail as possible if telling me to install or change things manually. I've read posts about 'extended roms' and taking bits from here and there and I've no idea what this is about.
hello fellow mac user
What exactly is the problem?
ANy error messages? are you trying via BT or USB ?
HI,
When I tried to upgrade previously the PDA2K's screen showed USB but I got an error (sorry I cant remember the number code; radio upgrade error or something).
Recently, and I don't know what's changed, I just get Error 101: Connection Failure. When I try to run the upgrade the device does a soft reset at the beginning, then there is a long pause then I get the error. It seemed to manage more previously (may be that was an earlier from upgrade, but it never worked anyway!).
Have you been successful from your Mac?
Just looked back at my old posts on the howard forums, and discovered it was Error 114 I was getting previously (with the first ROM upgrade). I presume I'm getting the 101 connection error now that I'm trying to use the latest ROM upgrade.
One thing I'm about to try myself is to switch off both the windows and Mac OS X firewalls just in case they are interfering with the process.
Just to be more specific:
It comes up with the info from the phone and the upgrade, then I click next to start the upgrade; the device does a soft reset then repeatedly the device says it's connecting to host, the PC says reading info from device; then after a while I get error 101. As soon as the ROM upgrade installer quits, then Activesync reconnects the device (as guest).
Are the ERK files supposed to be run from the device? Will this help me? I've just downloaded one, and downloaded a thing called WinRAR but the resulting files say they aren't Win32 applications; and most of the contents of the folder are .rar files even after I extracted it. Wierd. Please can someone help!
Oh well, it's getting late here in the UK, I will just have to try again another time. Going to have to reinstall everything again now (as I have after every failed attempted at a ROM upgrade over the past few months). This is the last time I buy anything with a Microsoft operating system!!!!
Can anyone help?
Anyone?
Hi
Sorry but I don't think I am going to be much help.
I too am a Mac user with VPC and happily ActiveSync every day using VPC 7.01.
HOWEVER I would never try and use VPC to do something as basic as a ROM upgrade.
I managed to borrow a PC from someone at work and used that for the upgrade. I went on the basis that a ROM upgrade is so basic to the device and would likely need real PC hardware that I would not risk it.
Is there no colleagure, friend or workmate that can help you out?
Regards.
Robin
Hi,
Thanks for replying. I had bought Virtual PC because I just couldn't find any other way of getting a lot of the software onto the iMate. Having made this investment I hoped it would work with the ROM upgrade too.
I did manage to get use of a PC yesterday, but unfortunately it didn't work either. The PDA2K reset itself at the start, then after a delay the updater gave error 101 connection error, exactly the same as with Virtual PC.
Later, I managed to get someone really helpful at i-mate on the live support (and for once it didn't time out) and I went through a few things, including pressing power-reset-record (so that USB is displpayed) and trying from there. It still didn't work, I got Error 114 after the updater sat at 0% for several minutes.
This leads me to the exact reason I didn't want to have to rely on someone elses PC: having access to it for a limited time I tried repeatedly the ROM upgrade yesterday with no success. Later, at home, I got help from iMate and some ideas that will be trying again with a PC, but now I've got to wait for another opportunity to use a PC. What concerns me, is if I ever get a major problem the phone may be unusable until I next get access to a PC. Worse still - if the phone locks up when I'm using the PC and I don't have the time/knowledge to resolve it, I could end up with a non-functioning phone. It's much easier to tinker with these things in the comfort of my own home when time is less of an issue.
I just received my K700i yesterday. I decided enough was enough. I'm going to sell the PDA2K as soon as I've got the ROM sorted out. I really did try to get on with this device but it's caused me more grief than I have ever had with an electronic device before. I learned a lot, setting up GPRS, wifi, bluetooth, found all sorts of useful software, used VNC to control my Mac remotely etc etc, but at the end of the day I just couldn't rely on it. Some days I could get email, some days I couldn't. Some days people would receive the SMS I sent, some days they didn't. Sometimes the people I was calling could hear me, sometimes they couldn't. Sometimes the phone would stay switched off, sometimes it turned itself on and drained the battery. The list of problems I had with this phone were endless. Hence why I was trying to get the ROM upgraded.
I understand your concenr and problem.
I actually have the latest ROM installed on mine and I STILL get someof the problems you describe.
Only Microsoft could get away with writing such a crap operating system to run a phone.
And i-mates issues just compund the Windows issues.
Good luck.
Robin
ive never bothered even trying to run activesync thru vpc. It was a bit hit and miss on my XDA1 so as soon as my xda2i arrived i just bought missing sync from mark space. Hassle free syncing and installing, plus the ppc gets mounted like a mass storage device too.
Trouble is I use Outlook at work and need to sync it to my PDA.
I cannot even use Entourage as we are a) running to old a version of Outlook server and b) Missing Sync will not sync with Entourage.
I am stuffed both ways.
Robin
Me again!
Just thought I'd let everyone know that I did indeed succeed first time on a PC today (having pressed power-reset-record to go into bootloader mode first).
So, as everyone told me, it was necessary to use a PC, and Virtual PC on a Mac just wont work.
I'm getting on ok with my K700i, although the email seems a bit limiting (doesn't seem to have message titles displayed, and a short limit to the length of the email).
My plan: use the K700i for a few weeks and see how I get on, then perhaps I might try the newly upgraded PDA2K for a few weeks, and see which I prefer.
The other complicating factor is that the SIM free Treo 650 has just become available, but I'm going to hold fire on that for now. Perhaps if I'm not happy with either the K700i or the upgraded PDA2K then I might consider it...
Hi, I have an HTC 8125, and I desperetely want to flash it with a WM 6 ROM, But I only have Vista, and I am having so much trouble following the threads on doing this with Vista, that I am going to have to give up if I don't get some advice. I have downloaded the Wizard Tool, but it won't ever recognize that my phone is connected, even though Mobile Device Center says "connected". I tried using the program HARD SPL G4, but when it makes the screen go white on my wizard, mobile device center automatically says not connected, and at that point even though I get the screens to proceed with the new Rom, they dont work because my phone is no longer connected and nothing that I do lets it connect to mobile device center while the screen is white. I have to reset the phone and then the rom update doesnt work anymore.
Please help, even if it is pointing me to a topic or post that I don't know about. I have spent 12 hours reading and failing over and over with this.
Simple answer to all of your problems is Vista,Do it on a WinXP machine there won't be any problems.
Although,its possible to unlock and flash through Vista,but its still not compatible,WinXP is highly recommended.
Hello,
I have searched thoroughly on this site and I cannot find any help. I used to have vista ultimate and I down loaded the usb modem drivers and it worked like a charm. I had to re image my pc and now I have vista business. However now when I try to load the drivers they do now show up on the device list and it does not successfully install the modem. Am I missing something? is there an updated driver? Can anyone please help or point me to where I can get some help. I really need to get back on line. Thanks XDA
I have a suggestion which might work.
Look at your device manager and see if there is anything on there thats coming up as unidentified... if there is, and with the phone connected to activesync so the PC knows the phone is there (assuming activesync is working), delete those entries one by one and when you delete one you need to click *scan for hardware changes under the *actions menu.
If you didnt start from scratch with the PC - IE format the hard drive and rebuild the system - that may mean there is a corrupt version of the driver still floating about and causing problems. This is why in the places I have worked we always backed machines up - did a full format - and then either imaged or rebuilt the box manually.
Another option is to go online to the manufacturers support site for updated drivers and install them from a location you have saved them too to your hard drive..
From my experience dealing with recalcitrant USB devices I would think that the first issue is more likely.
However there is another possibility that may be the root of the problem. I know that different versions of Vista support different connectivity options and setups - aka Vista Basic doesnt do Active Directory or Domains (im dredging this up from memory so its a little hazy). There is the remote possibility that the Business version doesnt support phones as USB modems, although I would be very surprised if that was the case.
It does strike me as a little odd that you have gone from one version of the same OS to a different version of the same OS and have had this sort of problem... but then Microsoft are known for compatibility gremlins - two words - Windows ME
Hope that helped.
I know, it is very surprising to me that now it does not work on Vista Business. You would think that it is basically the same OS but with less features. It is the 32 bit version. Its driving me crazy because I depend on it to do my work from my laptop and it just does not populate the device name when browsing and selecting the drivers. It sees the device it just does not pupulate. When I try to do the right click and install it does install it but it still does not show up under modems. If any one else has more suggestions I will greatly appreciate it.
No need to panic fello xda members and friends. It is all good now...i am typing thins theteering from my laptop through my tilt. Thanks xda you are the best. The speed trough my tilt is faster than my 2wire at home....ftw.:d
Hi guys..
I'm using O2 XDA IIs, and I'm trying to upgrade to WM 6.5.
I've downloaded the ROM and other misc applications to upgrade, and also read the walkthrough in the XDAdevelopers Wiki page. But I find my device have no four colored boot screen but instead an O2 image with some color information as such :
Code:
R : 1.02.00
G : 1337.32
B : 1.31.00 WWE
in the bottom right of my screen. I also can't see the four colored screen with options to format storage which is one of the point mentioned in the upgrade section.
That's why I've been hesitating to upgrade it since I have this phone, because I can't follow the upgrade walkthrough completely which might caused my phone to brick.
Anyone can help?
Thanks
the four colour boot screen is a bug/feature of any cooked rom, meaning any wm5 and higher rom, you can download here. since you are still using the stock rom it is normal to have a carrier's boot screen. it will go away once you upgraded your device.
since the wiki is quite outdated, you should follow the tutorial link in my signature. it will provide you with the newest step by step instructions, that i wrote with a lot of user feedback, to make sure, people would understand it correctly, at some points, the wiki instructions are mistakable.
also, while i really appreciate being cautious (since it is always easier to guide in before, than to repair afterwards), you shouldn't worry about bricking the device. if you follow the tutorial word by word, there should be no risk of failing to upgrade. and even if an upgrade fails, you can always start over again.
Just read all the tutorial firstto have some sense of it, and the follow it while doingthe upgrade. Make sure that your battery is at least 50% charged and you'll be good to go.
Good luck and if you have questions, please post them in the q&a thread...
Good luck
Chef_Tony said:
the four colour boot screen is a bug/feature of any cooked rom, meaning any wm5 and higher rom, you can download here. since you are still using the stock rom it is normal to have a carrier's boot screen. it will go away once you upgraded your device.
since the wiki is quite outdated, you should follow the tutorial link in my signature. it will provide you with the newest step by step instructions, that i wrote with a lot of user feedback, to make sure, people would understand it correctly, at some points, the wiki instructions are mistakable.
also, while i really appreciate being cautious (since it is always easier to guide in before, than to repair afterwards), you shouldn't worry about bricking the device. if you follow the tutorial word by word, there should be no risk of failing to upgrade. and even if an upgrade fails, you can always start over again.
Click to expand...
Click to collapse
thanks for the help chef..
I've visited the link on your signature, and it really helps. unfortunately, I'm using Vista in my notebook. since there's no guide for that in your thread, should I just try the steps for Vista user mentioned in the wiki? or should I just find another computer with windows XP on it? I already have the Windows Mobile Device Center installed on my notebook by the way.
also, there are some other things I'd like to know. I've tried putting my device into bootloader mode by pressing power + record button and then reset. but there's nothing changed, just looks like a normal soft reset. is it really supposed to looks like that? or there's something wrong with me or my device?
and when I do the hard reset, just like I've mentioned above, there's no menu appears. is the menu also part of bug in the cooked ROM and not supposed to appear in the carrier's boot screen?
thanks for the answer.
egzthunder1 said:
Just read all the tutorial firstto have some sense of it, and the follow it while doingthe upgrade. Make sure that your battery is at least 50% charged and you'll be good to go.
Good luck and if you have questions, please post them in the q&a thread...
Good luck
Click to expand...
Click to collapse
yes, I've always searched for more and more informations before doing something this risky. I'll visit the Q&A thread after posting this reply. thanks for the support.
---
btw, sorry if my English is mixed up. it's not my primary language, so please endure with my bad English.
for the bootloader mode, you might have to press and hold the power+record button a little longer while resetting and only release them, when the display is grey and shows SERIAL on top and v2.0x (where x is between 5 and 7) at the bottom.
the mentioned hard reset method is also only suitable for windows mobile 5 and higher. for windows mobile 2003 a hard reset is done by simply pressing power+reset (also maybe holding the power button for a second). there is no hard reset necessary before the upgrade, but afterwards, and then, using a higher rom, you will have the 4 coloured screen with the menu. there is really no way to make a dry run on this.
as a first time upgrader it would be much easier for you to use a windows xp machine. it simply works because activesync provides all the necessary drivers, for syncing (of course), and also for flashing, while on vista/7 you have to replace the driver with a custom one depending on your version (x86 or x64). those drivers are not digitally signed, which, especially on x64 machines means more trouble to go through. in d-two's thread, you will find a how-to for vista/7 flashing if you find no other way. i think that is just an option for experienced windows and blueangel users, that are already running a cooked rom and want to change to another one. with a first time upgrade you have so much stuff to read through, so many more steps to actually prepare the device for the first time upgrade... xp would be your better choice.
alphadeeto said:
thanks for the help chef..
I've visited the link on your signature, and it really helps. unfortunately, I'm using Vista in my notebook. since there's no guide for that in your thread, should I just try the steps for Vista user mentioned in the wiki? or should I just find another computer with windows XP on it? I already have the Windows Mobile Device Center installed on my notebook by the way.
also, there are some other things I'd like to know. I've tried putting my device into bootloader mode by pressing power + record button and then reset. but there's nothing changed, just looks like a normal soft reset. is it really supposed to looks like that? or there's something wrong with me or my device?
and when I do the hard reset, just like I've mentioned above, there's no menu appears. is the menu also part of bug in the cooked ROM and not supposed to appear in the carrier's boot screen?
Click to expand...
Click to collapse
There is a set of instructions for Vista in the wiki (the ones you are referring to). They seem to work well afaik, but I agree with Chef... do it from a XP computer to avoid any issues.
Bootloader (the easiest way) is to hold power +record and then put the stylus in the hole. Doing the three of them at the same time might not get you anywhere. For the hard reset (WM5 and up), you can simply use the stylus and as soon as you get the stylus out, hold the two side buttons (camera/WMP and record) and you'll be able to see the options mentioned by Chef.
Good luck!
thanks for all the help, both of you..
I finally upgraded my BA to WM 6.5, and it turns to be a success. I'm using the steps from wiki to upgrade in vista since it's hard to find someone who's using XP in my neighborhood.
Nothing's wrong until I tried to send SMS messages. I can't either send or receive any SMS's. The messages are delivered to me but it doesn't appear in inbox, only in today screen notification. Fortunately, the other function works really well, the phone, GPRS, bluetooth, ad even the wi-fi.
I'll upload the screenshots later when I'm using my notebook since the internet fee using GPRS in my country is really expensive.
Can I reflash using another ROM? or is there something I can do to fix the problem?
oh, and another thing : my USB active sync can't work. Should I reinstall the WMDC or what?
thanks for the support guys.
alphadeeto said:
thanks for all the help, both of you..
I finally upgraded my BA to WM 6.5, and it turns to be a success. I'm using the steps from wiki to upgrade in vista since it's hard to find someone who's using XP in my neighborhood.
Nothing's wrong until I tried to send SMS messages. I can't either send or receive any SMS's. The messages are delivered to me but it doesn't appear in inbox, only in today screen notification. Fortunately, the other function works really well, the phone, GPRS, bluetooth, ad even the wi-fi.
I'll upload the screenshots later when I'm using my notebook since the internet fee using GPRS in my country is really expensive.
Can I reflash using another ROM? or is there something I can do to fix the problem?
oh, and another thing : my USB active sync can't work. Should I reinstall the WMDC or what?
thanks for the support guys.
Click to expand...
Click to collapse
Most of those issues sound like issues present in my rom. Is that the one you flashed? If so, it would be wise to flash to something else... I never really got that rom working the way I wanted... Go with 28232 or one of d-two's releases.
egzthunder1 said:
Most of those issues sound like issues present in my rom. Is that the one you flashed? If so, it would be wise to flash to something else... I never really got that rom working the way I wanted... Go with 28232 or one of d-two's releases.
Click to expand...
Click to collapse
excellent!
I've flashed with the latest ROM from Sun Dream. and it works superb!
there are lots of changes from my previous ROM. the today's screen, start menu, and the buttons position (the start button is on the top of the screen previously, and now it's in the bottom. )
well, the only problem I encounter is that I can't sync with WMDC on my Vista.
alphadeeto said:
excellent!
I've flashed with the latest ROM from Sun Dream. and it works superb!
there are lots of changes from my previous ROM. the today's screen, start menu, and the buttons position (the start button is on the top of the screen previously, and now it's in the bottom. )
well, the only problem I encounter is that I can't sync with WMDC on my Vista.
Click to expand...
Click to collapse
You have to use a newer driver which if I am not mistaken comes with WMDC 6.1
Ok, this may be slightly off-topic but is something that's been bothering me since I started flashing ROMs with a purpose.
Each and every time I reflash, I have to reboot my Vista-based computer --and it takes more than 5 minutes for me to shut down Outlook and reboot and wait for everything to come back up.
If I don't reboot, then WMDC (Windows Mobile Device Center -- and yes, it's the latest version, which isn't that new) refuses to recognize my phone after it reboots and reconfigures. Windows will see the phone with its new ROM, but treats it as a USB device.
I've tried to kill the previous partnership, but that doesn't do anything. I've also tried to kill the WMDC process and restart it before hooking my phone back up, but that doesn't do anything either. The phone will try to start Activesync but of course Windows justs laughs at that.
Wasted over an hour perusing old articles on ActiveSync and WMDC (mostly outdated MS "tech" articles) and just can't find anything. Since I haven't seen any griping on the ROM threads alluding to this problem I'm thinking it must not be common.
Does anyone have any ideas?
Two things your could try, what I can think of. Not sure if it is the answer your looking fore, but in my opinion it's worth a shot. (especcially number 2.)
1. Flash true your SD card.
2. Enterbootloader, plugin your usb, flash true your pc. (this way you don't need WMDC, but it works just the same).