Help please! - Is this a bootloader problem? - MDA, XDA, 1010 Software Upgrading

Hi,
I keep getting error (Code 43) when trying to upgrade my O2 2002 ROM to WM2003SE.
I've tried everything to get around the error, the only thing i haven't changed yet is the bootloader version. (Currently on v 5.22)
If anyone can provide some advice this would be great.
Thanks
W

Bootloader 5.22 is alright. Have it also and do not have any Problems with it.....
Have you tried another PC to do the upgrade?
Stefan

Hi Stefan,
Yeah - I have tried other machines to do the upgrade - 2 laptops and a desktop.
All report the same error.
The wierd thing for me is that it seems to be Windows XP that reports the error - I get a Code 43 error in device manager - I've attached an image of the error i get.
I've also upgraded all my laptops USB drivers, chipset, BIOS - basically everything to see if it was a problem with a version of the driver or firmware i was running but the error remains unchanged.
Everything runs just fine until Programme A wants to upload the new image - the screen where you should see the progress bar as the new ROM is uploaded - I see that screen for a split second before the Qtek reboots back into the old ROM!
Thanks for the reply
W

Code 43
Windows has stopped this device because it has reported problems. (Code 43)
You could try a different usb port and also make sure it is connected direct and not through a hub.

Yup!
Tried both my USB ports, also tried disabling the "USB Root Hub" in Device manager - I don't have a USB hub plugged into my laptop, but there is one reported in Device Manager - I guess it's internal to the PC?
I figured that if there was a hub built into the laptop that would cause the communication problems experienced by USB hubs.
I couldn't disable all the USB Root Hub instances without switching off the USB port, so i closed all the ones i could and still have the port alive.
Still got the problem - The USB Root Hub in Device Manager - you think this is the "Hub" that the upgrade documentation says will create the error?

I give up...
Thats it! Back to the Good ol T-Mobile v4 ROM.
I've done everything including downgrade my laptop to Win 98 to try USB 1 drivers for this WM 2003 SE upgrade.
I've read every research article, installed every patch, been through TechNet and MSDN libraries.
This thing will just not work!
The universe is trying to tell me something!!

usb and 98 is not the best match
some chipset require special drivers for usb to behave like via
with xp having the latest service pack is prob a good idear

Related

Stuck in bootloader mode - USB device has malfunctioned

Sorry if I'm missing something really obvious but I've looked through the forums and the wiki for possible solutions to this.
I tried to upgrade the ROM to tomal - V8.0 (6.1 Pro). After syncing and going through the initial screens, Windows came up with a message that the attached USB device had malfunctioned on going into the bootloader. I've tried using the mtty utility in a few different computers but each time there is no USB option listed in the port. As it is, I'm stuck in the bootloader screen (showing "Serial" rather than "USB", v1.00) and softresetting just brings me back to the same bootloader screen again.
Does anyone have any ideas?
Hello bro,
Faced this problem few times...and got it to work .
What i did was removed SIM Card / MMC Card and disable Usb connection in active Sync and try not to use any HUB for usb and try all the Usb ports available on your computer. keep trying thats all i can say and i did.
Hope it works out for you good luck .
~ZODI.
Thanks for the reply. There's no SIM card or SD card inserted and I've tried all the USB ports on three different computers - one running XP, one running Vista Home and one running Vista x64. I've also tried running lsusb on a linux boot and nothing comes up on that (though in all honesty I don't know what it should be detected as).
progress?
Hi Steven,
any progress, I am having the same problem on my (new) universal. serial doens't change to usb whatever I do (tried mtty and everything)
Oh one other thing, When I retract my usb-cable halfway form my phone "usb" DOES appear, you think we could do sth with that?
Thanks and thanks to all on these great forums at xda!
Curehead
nope, sorry. i've never got any further forward.

ROM Upgrade fails when ActiveSync disconnects

Boo Hoo ... I love my HTC-HD2, (despite all the grief HTC should have avoided inflicting on us), ... and so I was really looking forward to the 1.66 ROM Upgrade. BUT it won't load for me...
I downloaded the ROM ("GCC & Egypt" version out of Middle-East & Africa site - I'm an expat living in Dubai), connected my phone to my PC by USB & ActiveSync, ran the ROM.exe on my PC, carefully ticked and clicked my way through all the dialogue boxes and when I hit the last "next" button to launch the ROM upgrade, ActiveSync decides to disconnect leaving the phone hanging in the tri-clour bootloader mode and 10 seconds later, (with the connection dropped), I get Error [266] UPDATE ERROR (see attached screen shot).
Happily a quick restart after removing the battery restored the phone to its un-upgraded state. Thinking I may have tweaked something I shouldn't have on my phone (with loaded software, reg-edits and xda-tweaks), I hard reset it back to the original factory 1.43 ROM condition and retried the 1.66 Upgrade; but no go - same ActiveSync disconnection/bootloader hang. Tried again with firewall and virus protection turned off; and again on a different PC; and again and again holding my tongue in every conceivable different position - but no joy and now I have a bald patch from all the hair I pulled out.
I might just be thick and missed something, (though - as a last resort - I did read the instructions seven times), ... so I'm desperately seeking assistance. Any help would be greatly appreciated ... as I'm finding it difficult to suppress the rising anger and loathing I developing for Team HTC - who have now predisposed me to blame them for everything that goes wrong including global warming; - this is turning out to be pretty much like my relationship with all the old Landrovers I've owned - but I digress - can anyone suggest a solution or point out my error ... before I send the less than complimentary email I'm drafting to HTC, who will then have to blacklist me from buying the HD3 and then I won't have anything to complain about, (because my current Landrover Discovery 3 is uncharacteristically perfect !!).
That's because Windows needs an extra driver for the phone in bootloader mode. It is then no longer connected via Activesync.
Put your phone into bootloader mode, connect it to your PC, wait for the driver to install, then flash again (while the phone is in bootloader mode).
ROM Upgrade Utility / Phone connection problem persists
Thanks for the advice; but still have a problem.
PC connects and recognises the phone via USB connection in bootloader mode(so I assume driver has loaded properly) but ROM upgrade utility still stalls with error message saying "Update Utility cannot get response from your PDA Phone".
Several attempts to run Upgrade Utility while phone is in bootloader mode all fail; sometimes with no detection at but once or twice it manages to detect the phone but doesn't obtain any status info and ultimately fails to communicate properly, always ending up with the Error message noted.
Starting think I have a hardware problem ... oh no ... will have to deal with HTC Middle-East (which will mean numerous miscommunications, 3-4 week waits, phone being lost/misplaced, after 2-months being told there is actually no problem - must all be in my head ... think I'll just slash my wrists now and save the aggravation.)
eViking said:
Thanks for the advice; but still have a problem.
PC connects and recognises the phone via USB connection in bootloader mode(so I assume driver has loaded properly) but ROM upgrade utility still stalls with error message saying "Update Utility cannot get response from your PDA Phone".
Several attempts to run Upgrade Utility while phone is in bootloader mode all fail; sometimes with no detection at but once or twice it manages to detect the phone but doesn't obtain any status info and ultimately fails to communicate properly, always ending up with the Error message noted.
Starting think I have a hardware problem ... oh no ... will have to deal with HTC Middle-East (which will mean numerous miscommunications, 3-4 week waits, phone being lost/misplaced, after 2-months being told there is actually no problem - must all be in my head ... think I'll just slash my wrists now and save the aggravation.)
Click to expand...
Click to collapse
What version of Windows are you using? If you are using Windows Vista or Windows 7 64 bit you may need to install the required drivers by yourself, rather than automatically updating drivers.
Have tried on two systems:
1. Win XP (32bit version with Service pack 3) running as virtual machine in Parallels 5.0 on an iMac OS 10.6 (snow leopard) - yes I've ventured out of the shadows into the light.
and
2. Win XP (32bit version with Service pack 3) running on a standard PC
Both seem to connect, bootloader on phone shows "USB" and under Control Panel/System/Device Manager the HTC Device shows as a USB Root Hub device "working properly" ???
eViking said:
Have tried on two systems:
1. Win XP (32bit version with Service pack 3) running as virtual machine in Parallels 5.0 on an iMac OS 10.6 (snow leopard) - yes I've ventured out of the shadows into the light.
and
2. Win XP (32bit version with Service pack 3) running on a standard PC
Both seem to connect, bootloader on phone shows "USB" and under Control Panel/System/Device Manager the HTC Device shows as a USB Root Hub device "working properly" ???
Click to expand...
Click to collapse
Strange. I guess you have tried using different USB ports, and not using a USB hub port. Are you using the stock USB cable that came with your HD2?
You might also try flashing a ROM with your storage card. That should bypass your USB problem. You can find instructions here.
Flashing Via MicroSD Card
1. Make sure your microSD is Formatted to fat32 (you dont have to delete all files but it is safer if you do)
2. Download your prefered Rom from the LEO Rom Develpoment Page and unzip/unrar it to your PC
3. Goto the Roms Folder and rename the .nbh file to LEOIMG.nbh
4. Copy the LEOIMG.nbh file to the root of your MicroSD Card
5. Plug the MicroSD Card into the phone
6. Reset the device while pressing the volume down button to enter the BootLoader screen, you will first see a tri-color screen with the phone and SPL Information at the top
7. Follow the On Screen instructions to start the update
8. After flash has completed, press the reset button with the stylus to reset the device.
Yes; the first thing I tend to suspect is the USB Hub or ports on peripherals, but I also tried virtually every direct connect USB port on both machines.
and
Yes, I'm using the standard HTC micro-USB cable ... BUT whilst waiting for my second HTC cable to arrive I have also been using a micro-USB from a Jabra SP700 (car speaker) which "looks" identical but only charges my HD2 and doesn't work with ActiveSync ... so now I'm wondering if it is slightly different, maybe it has damaged the terminals on the phone - though would've thought that all micro-USBs plug in the same even if terminal configs differ resulting in connectivity differences ???
eViking said:
Yes; the first thing I tend to suspect is the USB Hub or ports on peripherals, but I also tried virtually every direct connect USB port on both machines.
and
Yes, I'm using the standard HTC micro-USB cable ... BUT whilst waiting for my second HTC cable to arrive I have also been using a micro-USB from a Jabra SP700 (car speaker) which "looks" identical but only charges my HD2 and doesn't work with ActiveSync ... so now I'm wondering if it is slightly different, maybe it has damaged the terminals on the phone - though would've thought that all micro-USBs plug in the same even if terminal configs differ resulting in connectivity differences ???
Click to expand...
Click to collapse
I do not understand all the mechanics of it, but no, not all micro-USB cables are the same, apparently some do not carry enough current, or some such thing. I am searching for more information for you now. If I find it, I will post it here.
For the life of me, I cannot find the information I was looking for. I read somewhere that others solved the problem by just disconnecting and reconnecting the phone during the flash process when the error occurs.
Well try another HTC cable as that sure seems to be suspect now. If all else fails, I would try flashing through the memory card method.
Keep us update. Hopefully soon you will get what you want.
Success!!! Flashing from a 3rd (more powerful) PC, went without a hitch and I'm now up and running.
My observations for what they're worth:
1. As noted by "FreyBerry", when running the Upgrade Utility from a PC using an ActiveSync connection to the phone, the connection gets dropped when the phone goes into bootloader mode and the PC is supposed to detect the phone as a USB device and reconnect - loading the appropriate driver. If driver and/or connection fails to load quickly enough the Utility times-out and you get the error message.
2. Though my USB cable may have been my problem, it seemed to work flawlessly on the 3rd PC. So other possibilites could be:
3. On the 1st attempt, running WinXP as a virtual machine inside an iMac, the USB-device re-connection doesn't happen fast enough as the Mac and PC inside the Mac arm-wrestle over which OS will pickup the connection.
4. On the 2nd attempt, using my office PC, our network/virus protocols/firewall or simply the aging PC may have been too slow or obstructed in reconnecting.
If the problem re-occurs I'll be opting for the SD-Card Flash method you suggested.
Many thanks for all the help ... I can already feel my pulled-out hair re-growing. Cheers.
Windows 7 seems to be the problem. I have the same problem if I want to upgrade the ROM on Windows 7, not on Windows XP.
3. On the 1st attempt, running WinXP as a virtual machine inside an iMac, the USB-device re-connection doesn't happen fast enough as the Mac and PC inside the Mac arm-wrestle over which OS will pickup the connection.
Click to expand...
Click to collapse
I never succeeded in flashing from a virtual machine on OS X.
@wereldbol No, it should work fine with Windows 7, both 32bit and 64bit.
Just last week I flashed a rom on a Vista x86 no problem. Now I've got Windows 7 x64 on a brand new computer and I'm now getting error 266. I don't have the option of using the old computer so I'm lost on what to do. I was already even able to flash HSPL3 to my wife's phone on the Win7 pc and didn't have this kind of trouble. But now I can't install a rom.
The device drivers installed. If anyone has any help. It would be much appreciated.

Problems connecting Hero to PC

I've been trying to get anything to recognize my Hero on my PC for the past few days.
What I've tried:
Installing HTC Sync
Installing Android SDK
Installing the HTC HERO DIAG drivers
Doing ##DIAG# and not doing it.
...And all different combinations of those. The problem is I can't get QPST, CDMA Workshop, UniCDMA, or QXDM, etc to recognize it. The Hero synced to the HTC Sync a couple times, but nothing else. It won't even assign a COM port on the computer.
The phone is also rooted, which, I wouldn't think would make much difference, but I'm running out of ideas here.
Any help is really appreciated.
Did you install the regular HTC drivers ? Go to your device manager and see if it says android phone when its plugged in if its there tell it to update driver and point it to the folder called HTC drivers located in the HTC sync program directory.
I tried to do that but the driver wizard said that it could not find any drivers that were better than the ones already installed. (or something to that effect)
EDIT: Ah! I don't know what happened but it appeared on COM5 as "HTC Diagnostic Interface". That may be what I needed. We'll see.
I get the same thing, says "Windows has determined the driver software for your device is up to date."
"HTC Dream Composite ADB Interface" <--???
Exactly the same for me.
Device not recognized, Remove and reinstall HTC Sync and manually selecting drivers, Device wiping and trying again, using a different USB port, using a different cable, reinstalling windows!!!!!, using a different computer, Pulling out my hair!!!!!
Nothing works!!!
However, It did used to ask for mounting and unmounting the SD when plugged in but it has NEVER found HTC sync on my PC.
Now, all I get is Charging battery on the Hero and device not recognized on the PC.
Device manager politely tells me "Windows has stopped this device because it has reported problems. (Code 43)"
My system is Windows 7 X64 and my Hero Has run both the shipped ROM and now a cooked 2.1.
Please help me!
I have never been able to sync my Hero on any of my Win7 machines. I have been able to sync sporadically with my work XP Pro SP3 machine though. However, since flashing the AOSP 1.6 rom, HTC sync isn't recognizing my phone anymore. I can however mount the SD card.
Problems connecting Evo to PC
Same problem, but on EVO... Anyone ever figure it out??
I should elaborate I suppose lol... Everything *worked* fine, and then suddenly, appearantly for no reason, it just stopped... Device manager now calls the HTC diag driver an unknown usb device and gives the same warning message as above. And when I try to update the driver, gives the same message about it being up to date...
I have not been able to get ADB to work on my phone since the first time I flashed 2.2, when plugged in it will do the "do you want to turn on usb storage" message and it works fine.
You all might want to try installing the android adb drivers. Its a well know issue with the htc drivers. If you click on my avatar and go to my post you can find my thread on how to install adb on windows 7 32/64 and xp. Adb works fine for me and sync as well. The adb drivers might help out. Well good luck.
Edit: Running Aosp's 3/26 gb build RA1.7 Jason m's 806 kernel kifno build prop tweak -mp
Yea it's Me Again With The
Modified Hero
Tramline said:
Exactly the same for me.
Device not recognized, Remove and reinstall HTC Sync and manually selecting drivers, Device wiping and trying again, using a different USB port, using a different cable, reinstalling windows!!!!!, using a different computer, Pulling out my hair!!!!!
Nothing works!!!
However, It did used to ask for mounting and unmounting the SD when plugged in but it has NEVER found HTC sync on my PC.
Now, all I get is Charging battery on the Hero and device not recognized on the PC.
Device manager politely tells me "Windows has stopped this device because it has reported problems. (Code 43)"
My system is Windows 7 X64 and my Hero Has run both the shipped ROM and now a cooked 2.1.
Please help me!
Click to expand...
Click to collapse
more than likely it is your usb cable has been damaged.
i had the same problem, i went to my provider and got a new usb cable for it. (they gave it to me for free, no questions) no more problems at all, works like a charm.
i still have the old cable too, it will not recognize the hero on the computer. in fact if i plug the cable in without the phone, the cable itself actually comes up and says unrecognized device. but it works great for charging.

HTC HD2 Drivers won't install Win 7 x64

Anyway to manually get the drivers for it? I can't find them and I can't sync my device to my computer. Windows Mobile Device Center won't work at all, it doesn't recognize my HD2 and it says the driver installation fails.
Can someone help me out please? Thanks
Windows Mobile Device Centre was all I never needed on my win7 x64. I installed the program before inserting the HD2 though. Obviously make sure you have the program up and running before plugging in the HD2 and selecting activesync on it; It should load up. You could uninstall the driver (from device manager) and start again if all else fails.
What if it does not?
Started doing that "cant recognize" issue while installing NAND (at the radio installation process -r: 2.15., compatible)
Figured to go to stock WinMo with SDCard, but it still cant..
Faster data sync disabled, after that it tried to install the drivers again, but says it fails...
Gotta go to ms and install the updated win mob dev c. The one that ships needs updating.
Also, once you are into the android side of things you should open wmdc, connection settings, and turn off allow usb connections, and install the android usb drivers.
Thanks mate, but done everything, I mean everything. Now I'm totally stock, original SPL and original WWE ROM, everythings working like a charm, besides connecting to a PC. Also tried with another computer (XP) and another cable. I can say I've done everything I found on the net, but nothing helps. Uninstalling driver, uninstalling HTC Sync etc etc etc... It just cant recognize the USB..
thekillingroad said:
Thanks mate, but done everything, I mean everything. Now I'm totally stock, original SPL and original WWE ROM, everythings working like a charm, besides connecting to a PC. Also tried with another computer (XP) and another cable. I can say I've done everything I found on the net, but nothing helps. Uninstalling driver, uninstalling HTC Sync etc etc etc... It just cant recognize the USB..
Click to expand...
Click to collapse
Replace your USB Cable and Thats ALL !
i had the same problem....i am for now using windowx xp
aks777 said:
i had the same problem....i am for now using windowx xp
Click to expand...
Click to collapse
I have been using it win 7 64 bit since the beginning. and I never have a problem with the driver.
Try redownload and reinstall Windows Mobile Device Center from Microsoft website.
Only connect your device after the driver has been properly installed.
in device manager delete usb controller after software installation.
Thanks to ALL, but changing the USB cable, so sure that's ALL? =)
I'm not gonna mention that I've written that I've tried it with many computers and many cables. =)
The phone is sent to HTC and they told me that they ordered a new mainboard.
Hope doesn't take too much time. My Service Provider gave me a Galaxy 7500.. Cupcake, no market.. arrrgh!
Thinking of buying an iPhone and selling it after two weeks but that's gonna cost me $200 loss in two weeks. too much =)
As doing some thinking.. the device cannot "introduce" itself to the computer. I couldn't find a more sense making answer.
If you've tried hard-resetting, cable and PC changing, if it's still not working, then there should be a problem about the phone, mostly about the mainboard.
I suggest anyone having that problem go make your phone check at a service, of course if you have warranty. =)

[Q] USB connection problem - Donation & eternal gratitude for the solution!

Hi everybody,
I hope you can help me because I really can't find the solution:
When I connect my HD2 WP7-device to my computer it charges, but isn't recognized.
- Zune won't start automatically and won't find any device.
- Device Manager doesn't show any unknown device or something that could be my phone.
What I have tried so far:
- Used a XP3 and W7 x64 machine (also ones without any history with a WP7-phone)
- Used a lot of different cables
- Used a lot of different USB-ports
- reinstalled WP7
- reinstalled zune
- (de)installed activesync
- I'm not sure, but first I had a dual-boot solution with Android and I recall USB also didn't work there.
I started to think the USB-connection of my phone might be broken, but when I use MAGDLR, the USB works as mass storage and I can also use the USB flasher. The Bootloader also works, so I tried the following:
- (using bootloader) restored the HD2 in its original state with a official stock ROM and original (locked) HSPL
- Installed a Android ROM: the USB also does NOT work with WM6.5 or Android.
Does anyone know anything I can try now? And Yes, I have read all of the threads of other people with USB-issues and the MS-solutions, but none of them had the solution for me...
Coffee-donation for whoever has the golden tip
Hello guys, I don't mean to hijack the thread, but I am facing a similar issue.
I installed the LEO70 ROM on my HD2 when it first came out, and forgot all about it. I now want to install the NoDo (7932) update to test it out (and maybe move permanently to an Android ROM eventually when I decide I don't like it). I am facing an issue; I want to upgrade my MagLDR to 1.13 (from 1.12) and ROMUpdateUtility doesn't recognize my phone, giving me the 'Error 260 - Connection' error.
I did remove Windows Mobile Device Center a month or two ago... could this be the problem? I have the latest Zune software installed on my Windows Server 2008 R2 SP1 (x86-64) machine, and when I plug in the phone, Zune automatically starts and recognizes my phone, telling me there's a phone update available (from February that I need to install to enable future updates). I know it will kill my phone, so I won't install it. Also, USBMassStorage mode works nicely.
Any ideas?
Hi sclip,
I don't mind if you try to find an answer to your problem too, but it seems like a different one, because mine does work in bootloader/magdlr-mode.
BTW. I just installed the stock WM6.5 Rom of HTC, and USB still doesn't work! Can it be the radio of hardSPL or is it just broken?
****, after installing the stock WM6.5, it won't install another Radio/MAGDLR using bootloader, it stucks at the 0%.
I think I might haved destroyed my HD2
Daanmannetje said:
****, after installing the stock WM6.5, it won't install another Radio/MAGDLR using bootloader, it stucks at the 0%.
I think I might haved destroyed my HD2
Click to expand...
Click to collapse
remember to HSPL it once you have installed your original Stock rom
dazza9075 said:
remember to HSPL it once you have installed your original Stock rom
Click to expand...
Click to collapse
That did the trick, thanks. To bad it didn't help my USB problem...
since youve tried just about everything else try this
try using USBDVIEW and delete all the USB drivers
also install it on a different PC that hasnt had WP7 connected to it before
to continue with fault testing will requirer us to rule out the PC or the phone, at the mo it could be anything.
since you have Windows 7 install the XP virtual machine and use that, i believe the VM now supports pass through on USB so it should work, i have an old IrDA adaptor that wont install on my w7 PC but it will on the XP VM
dazza9075 said:
since youve tried just about everything else try this
try using USBDVIEW and delete all the USB drivers
also install it on a different PC that hasnt had WP7 connected to it before
to continue with fault testing will requirer us to rule out the PC or the phone, at the mo it could be anything.
since you have Windows 7 install the XP virtual machine and use that, i believe the VM now supports pass through on USB so it should work, i have an old IrDA adaptor that wont install on my w7 PC but it will on the XP VM
Click to expand...
Click to collapse
Thanks for the USBDVIEW-tip, quite a nice piece of software! However it didn't help me with my problem. Using a computer which never had WP7 connected before didn't help either...

Categories

Resources