I have flashed my i607 with the i600 new ROM and now I can't flash the phone back.
The phone works because I haven't flashed this part, however had flashed the PDA and have no camera anymore, no vibrator, but at least a working O/S.
I have tried the following:
a ) Purchased the D820 cable. I can see the phone connected using Tera Term in COM1, however is not seen by the WCE downloader as this is looking at USB ports.
b ) I have tried installing the modem drivers time and again, and tried to connect ActiveSync in COM1 according to these instructions:
(1) Use a Samsung D820 cable with Serial Port and plug into your i60x
(2) Connect the cable to your PC's serial port (probably COM1)
(3) Install the Samsung Blackjack Modem Driver
(4) Uncheck the "Allow USB connections" in Active Sync option and select COM1 in "Allow connections in one of the followings"
(5) Let Active Sync to search for the i60x and wait for "Connected"
(6) Run the i600 firmware update program as usual.
NO results. ActiveSync does not connect.
c ) Tried Corona Downloader ver 3.2 for Samsung SGH-D500, it connects to the phone, but vendor ID sent is 0x44 and the phone responds 0x52, aborting further exchanges. I also tried OneNAND downloaders ver 1.4, 1.7 and 1.8 with similar results. I know these flashers may not work on my phone, however gave me an idea some exchange was taking place...
d ) I tried to load the bootloader eboot.nbo in root of the SD card, however i don't know if there should be a key combination to boot from SD card or if there is one other trick nor what name the file should have. Any ideas here?
e ) I have made dumps prior this mishap of all 4 raw partitions in the phone. Is it there a way to write a partition using a utility that I can place in the SD card? Is it there available a SD flasher that may run from the phone?
f ) Is it there a way to modify the WCE downloader to work on COM1 instead of USB?
g ) Is it there a way to modify the device driver to accept the phone as it is now? Apparently the phone device driver messages windows with a device malfunction and Device not recognized. Is it there any way to bypass this?
h ) I even tried to use a Serial-USB bridge and WCE downloader. No results either.
If you have any ideas, please respond to this thread. Any input will be deeply appreciated. Thank-you in advance.
Hi,
Is your Samsung device a derivative of a HTC product or have you posted in the wrong place?
WB
I don't think so
I don't think the Samsung is a derivative of the HTC, nor I want to enter a discussion of territorialism, now with all due respect I though this forum was a place to openly exchange knowledge on xda devices, and yes, as this topic has to do with hacking, and yes, because I have seen postings on Samsung i60x and i71x devices, is why I have posted here. Do you have any insight about the subject matter?
Thank-you
Related
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
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.
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.
Hi, please help me with this. I need to activate the Diagnostics COM port in the SGH-i637.
Some info about this phone:
- This phone has a 32 bit Qualcomm MSM7201A CPU and Windows Mobile 6.1 OS.
- When connecting this phone as Modem, only modem driver is installed in Windows.
- During Flashing procedure (Turn off phone, press J, connect USB cable to PC, do not turn on phone) a Qualcomm device is detected and installs a COM port.
- Entering *#197328640#, then Option 9 (Common), then Option 4 (Diag_HFK_Configuration) only UART3 and UART 2DM are available (no USB Diag)
- Entering *#7284# nothing happens. Running Emchanger.exe or dataconnection.exe, you can choose between PDA or USB mode, but nothing happens.
- This phone is very similar to Samsung GT-B7320 and GT-B7330, on those both phones, changing from PDA to USB works (entering *#7284#) and installs the Diag COM Port.
So, any clue if there is a way to activate the Diagnostics port on this i637 smartphone?
Thanks!
Samsung GT-B7330 QXDM
I'm also working with QXDM and Samsung phones. I'm trying to used the USB modem mode(*#7284#) on my GT-B7330 but I can't find the right windows driver for it. Could someone provide me with the Samsung USB modem for the GT-B7330
I've search on the web and although I found many versions I could not get one which worked with the GT-B7330
Thanks
Running Emchanger not happening
as i wrongly updated my gt-b7320 to AT&T sgh i637 windows 6.5 now some of the keys are not working and led is always on
when i connect the phone to pc no COM port is showing it doesnt enter in boot mode as when i do it manually by *#7284# it shows cant find emchanger.exe
so is it possible to get my orginial version back by flashing it with original file.....
can anybody help me.......
Thnks in Advance
I'm a programmer but have no experience in Windows Mobile/CE programming before.
can anyone send me windows folder from healthy b7320 so that i can study and get u guys a solution.
Ok so here's the thing. This morning when I woke up I dropped my phone on the floor and the battery flew out.Initially I thought it was nothing but later it started rebooting without any good reason. I tried restarting, it would stay on for a bit then it would go down again. I am(was) running CyanogenMod 7 on a Samsung Galaxy SI. I want to reflash it with Odin as it won't start anymore.At first it would just boot loop but now it won't even get past the first logo. The tricky part is that my PC won't recognize it , all I get is Unknown Device code 43 yada yada BS! I tried alot of drivers, I tried the have disk method with the usb driver from SDK Tools , nothing worked ! Please, give me some suggestions about what I should try more because honestly this is beyond my expertise in this domain.
androis said:
The tricky part is that my PC won't recognize it , all I get is Unknown Device code 43 yada yada BS!
Click to expand...
Click to collapse
unknown USB solutions http://forum.xda-developers.com/showpost.php?p=27205737&postcount=4571
Tried those options, still Unknown Device. More suggestions ?
androis said:
Tried those options, still Unknown Device. More suggestions ?
Click to expand...
Click to collapse
code 43, has more to do with Hardware, its about your cable and PC ...so check cable, try switch to another USB port
Microsoft engineers answer
I suggest that you connect the Controller to a different USB port and check if you have the same issue.
If this does not work, you can try to uninstall and reinstall the USB controller.
To remove and reinstall all USB controllers, follow these steps:
1. Click Start, type Device manager and open device manager.
2. Right-click every device under the Universal Serial Bus controllers node, and then click Uninstall to remove them one at a time.
3. Restart the computer, and then reinstall the USB controllers.
Disable and enable the USB device:
1. Click on start and type devmgmt.msc.
2. Right click on the caution sign on the USB.
3. Select disable and reboot the computer.
4. Enable the device after reboot.
Also make sure that you download and install the latest version of Software for this. Here is a link you can follow to download the Software:
http://www.microsoft.com/hardware/download/download.aspx?category=Gaming
Thanks,
Irfan H, Microsoft Answers Support Engineer. Visit our Microsoft Answers Feedback Forum and let us know what you think.
Click to expand...
Click to collapse
Nothing worked. I even tried going to another PC but still I get unknown device... Is it still worth the struggle or should I just save up for a new phone ?
androis said:
Nothing worked. I even tried going to another PC but still I get unknown device... Is it still worth the struggle or should I just save up for a new phone ?
Click to expand...
Click to collapse
try and borrow another original samsung USB cable to test first, this is a major culprit, as numerous people including myself have experienced
what happens is one of the pins on the micro usb plug of rolls in and gets broken , also check your USB slot a good cleaning with a brush and alcohol would be good fro the connection ( do it when you have removed battery)
Got another USB cable still nothing... It's very weird, it's like nothing I heard off or read on the forums... Is there any method of connecting to the mobile using SDK manager ? I'm not really familiar to working with the SDK manager.
androis said:
Got another USB cable still nothing... It's very weird, it's like nothing I heard off or read on the forums... Is there any method of connecting to the mobile using SDK manager ? I'm not really familiar to working with the SDK manager.
Click to expand...
Click to collapse
was your cable an original samsung cable, IF not, many common cable do not work, due to pin configurations
For ADB, you still need connection with USB cable
Here's another thing I could try. If I go to Device Manager - Right Click on Unknown Device - Update Driver Software - Browse I can choose from a list of Samsung Drivers... The question is , which one do I have to choose for my Galaxy S ? Maybe it will work like this
androis said:
Here's another thing I could try. If I go to Device Manager - Right Click on Unknown Device - Update Driver Software - Browse I can choose from a list of Samsung Drivers... The question is , which one do I have to choose for my Galaxy S ? Maybe it will work like this
Click to expand...
Click to collapse
that was the solution given in my first post, have you not tried them all yet? samsung drivers were also attached on it and what PC software do you use XP or ?
In that link it requires your phone to be working and able to go in USB mass storage mode or debugging mode ... My phone can only stay in download mode . I use windows 7 x64 version .
androis said:
In that link it requires your phone to be working and able to go in USB mass storage mode or debugging mode ... My phone can only stay in download mode . I use windows 7 x64 version .
Click to expand...
Click to collapse
I think you have misunderstood it, there are many solutions mentioned there in, cause I am the one who wrote it ..your option was to try them all to see which one solved it
for win 7 . download this driver http://www.4shared.com/zip/0LQRmsMm/usb_driver.html and give it a go, if the other failed
Tried everything from your guide...even from the microsoft sites...Still can't get my device to be recognized...If I use the Usb driver you sent it won't let me use them even if I manually choose it for my device. Don't really know what to do more honestly other than throw it away and get another phone
http://cagnazzo.name/drupal/vista_corrupted_driverstore
Try the above, then install the Samsung drivers and then connect your device.
androis said:
Tried everything from your guide...even from the microsoft sites...Still can't get my device to be recognized...If I use the Usb driver you sent it won't let me use them even if I manually choose it for my device. Don't really know what to do more honestly other than throw it away and get another phone
Click to expand...
Click to collapse
problem is, its not the phone but its either, the micro USB slot or cable or your PC, if you have another USB cable and a lap top or a friends PC might be able to resolve your problem