Database Users

Help please! - Is this a bootloader problem?

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

USB Host - working?

First I would like to say hello, since it's my first post here, on xda.
While wandering throughout the internets, i've made an interesting discovery! On some other PPC-related forum i've found piece of software, that's supposed to enable USB-Host function.
Unfortunetly I don't know how to test it (how to connect cable and so on) and (to be honest) am afraid of bricking my diamond. So... here's the description by the author (Zeno):
USB Host Drivers Package version 2.0 (2009-02-07)
Requirements: PDA with WM5,WM6,WM6.1, propper USB cable for your device.
Overview: USB Host Drivers Package for PDA running WM5, WM6, WM6.1. Based on RATOC Systems drivers.
Made by Zeno Sloim 2009-02-07
The package contains:
USB Host Mouse Driver
HID Driver for US-101 keyboard
HostDriver for external USB-based CD-DVD
MassStorage Driver for external USB-based HDD or Flash or any other USB-based card-reader.
All features tested on Fujitsu Siemens Loox 560N running WM6.1 with 16 GB SDHC.
Used with OEM USB keyboard, OEM external HDD, Kingston 8 GB memmory-flash, OEM card-reader and various SD, SDHC cards, Microsoft various USB Mouses.
Download and run PCinstaller.exe on your pc or PPCautorun.exe on your pda.
What is new:
Version 1: 2009-02-06 (first version)
Version 2: 2009-02-07 added USB Host Mouse support for generic USB mouse. Only left-click and right-click support included, scroll-mouses are reduced to simple left and right click mouses.)
I hold no copyrights and so on. Just wondered, that it might be useful. If I broke any rules... delete this thread.

it works only on sd expansion card to usb or devices that support USB host feature (like my n560). anyway it's only usb 1.1 support so it won't do you
much good.

Doesn't work on HTC Diamond

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.

[Q] Win 8 hates my intel drivers?

So I can't even get win 8 to install. It always asks for drivers for my sata device. I tried using the newest intel drivers from intel for the DX58SO mainboard(sorry can't post direct link) and extracted the drivers from the package to my usb drive. Now I've tried 8 different sata drivers in that package but have been unable to get it to accept the drivers. My sata mode is currently set to IDE
Am I just going to have to wait for the build to progress so that it'll accept the intel storage drivers?

try to update bios

It's been updated as well. Updating it actually shaved 15 or 20 seconds off the complete boot time to desktop but still not working for me. I have a feeling I'll have to wait a while before I can install this onto my spare drive.

from the product page of your board:
Six Serial ATA 3.0 Gb/s ports, including 2 eSATA port with RAID support supplied by a Marvell* controller
maybe you should try the marvell drivers, idk with sata ports are used by your hd / drives

Unable to find any marvel drivers. Only thing I can find on their site is for Ethernet. Ill just wait for a later build
Sent from my SAMSUNG-SGH-I997 using XDA App

marvell dot com -> support -> driver downloads (dropdown from support) -> 2nd entry ( 5/26/11 Windows Setup Installer (32- and 64-bit) for Yukon Controllers )
or direct link: www dot marvell dot com/support/downloads/driverDownload.do?driverId=175&action=1

Ack sorry. Used to associating Yukon with network drivers

Unable to unlock bootloader

I've read the threads about unlocking bootloader in the redmi note 7, but none of them helped.
So the main problem is whenever I connect redmi into PC, it's recognized, but when I enter Mi Unlock app (miflash_unlock-en-3.5.1128.45), the phone is showing in left-up corner "..key to shutdown" (I can't see anything before key) and it's unmounting from PC.
I tried connecting it in many moments, but the result is the same. I tried also installing drivers from xiaomi, that you can install through the app itself, but it didn't change the results.
I've installed ADB app and drivers (as shown here: https://forum.xda-developers.com/showthread.php?t=2588979) and connected my device to mi account.
As in the thread on https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751 I tried to check via ABS if my device is listed and there is the output:
C:\adb>fastboot devices
afd9005 fastboot
C:\adb>fastboot oem device-info
...
FAILED (command write failed (Unknown error))
finished. total time: 0.005s
Click to expand...
Click to collapse
And the device goes into that mode like from mi unlock app
I'm posting below the link to the screenshots of my phone's settings, os version and things that I've read could help (I don't know how to insert photos in the post other way).https://we.tl/t-O3Z7H6AABu
I've been fighting with it for too long... Maybe someone encountered this problem and/or is able to provide the fix.

You can see help here https://forum.xda-developers.com/redmi-note-7/help/fastboot-issues-t3964100
Should to try another PC or use a 2.0 USB HUB. I also have same problem with my laptop (core i3 with USB 3.0 port) but it's OK on an older PC (without USB 3.0)
Update: Hi, I found a better way to fix this problem. I did with my Dell 14 5447 (with Intel chipset and Windows 7). I uninstalled Intel(R) USB 3.0 eXtensible Host controler in Program and Features. And then download and install a newer driver from Intel (https://downloadcenter.intel.com/do...100-Series-and-Intel-C220-C610-Chipset-Family).

gazavn said:
You can see help here https://forum.xda-developers.com/redmi-note-7/help/fastboot-issues-t3964100
Should to try another PC or use a 2.0 USB HUB. I also have same problem with my laptop (core i3 with USB 3.0 port) but it's OK on an older PC (without USB 3.0)
Click to expand...
Click to collapse
Oh I didn't try with USB 2.0. I have one in Mobo, so on few hours I'm going to tell if it fixed the issue

gazavn said:
You can see help here https://forum.xda-developers.com/redmi-note-7/help/fastboot-issues-t3964100
Should to try another PC or use a 2.0 USB HUB. I also have same problem with my laptop (core i3 with USB 3.0 port) but it's OK on an older PC (without USB 3.0)
Click to expand...
Click to collapse
On my main PC plugging into a USB 2.0 on back panel didn't work, neither on my dad's PC, that have in the front panel USB 2.0.
So I opened the whole thing now on the laptop without USB 3.0 drivers installed. I installed win7 and I didn't have option in driver selection "Android", so I installed xiaomi drivers and just plugged the phone. AND IT WORKED! Now I just have to wait 102 hours XD
I have 2 modules inside my laptop that are connected to motherboard (1st include 2.0 usb, and 2nd 3.0, both on different sides of laptop), so they're in some way separated. I don't know how it would behave if I installed the drivers, but for now I'm not checking it.
Thanks you for help, I would never come up with that fix!
Just leaving the specs if it's caused by hardware and for someone who has the same:
i5-8400
B360M pro-vdh
Probably not improtant in this case, but just in case:
GTX 1060 3GB
16GB ram ballistix sport lt

=Terys;81704493]On my main PC plugging into a USB 2.0 on back panel didn't work, neither on my dad's PC, that have in the front panel USB 2.0.
So I opened the whole thing now on the laptop without USB 3.0 drivers installed. I installed win7 and I didn't have option in driver selection "Android", so I installed xiaomi drivers and just plugged the phone. AND IT WORKED! Now I just have to wait 102 hours XD
I have 2 modules inside my laptop that are connected to motherboard (1st include 2.0 usb, and 2nd 3.0, both on different sides of laptop), so they're in some way separated. I don't know how it would behave if I installed the drivers, but for now I'm not checking it.
Thanks you for help, I would never come up with that fix!
Just leaving the specs if it's caused by hardware and for someone who has the same:
i5-8400
B360M pro-vdh
Probably not improtant in this case, but just in case:
GTX 1060 3GB
16GB ram ballistix sport lt
My pleasure.