Related
Good Morning!
Well, I upgraded the ROM on my (previously) Cingular 8525, two days ago, and continue to fail at getting it recognized by both my Dell M170 laptop and my Alienware Area51 Desktop via USB.
Activesync 4.5
Tried it with both Advanced Network Functionality and without.
All firewalls off.
No errors during ROM update.
Tried two different USB cables.
Reinstalled XPpro SP2, fully patched.
Tried removing and rediscovering all USB drivers for both machines.
I've tried everything I could think of, and in every order I could think of.
The OS discovers the device, and ultimately gives me a popup message that the USB device is installed correctly and ready for use, but then 10sec later I get "USB Device Not Recognized" pop up error....
Should I roll back to a previous version of Activesync? Can I roll the ROM back to a previous version?
I admit to surveying the forums here before posting, but it seems a bit confusing to me and I certainly don't want to destroy my phone.
Thanks in advance for your help!
jdtarch said:
Good Morning!
Well, I upgraded the ROM on my (previously) Cingular 8525, two days ago, and continue to fail at getting it recognized by both my Dell M170 laptop and my Alienware Area51 Desktop via USB.
Activesync 4.5
Tried it with both Advanced Network Functionality and without.
All firewalls off.
No errors during ROM update.
Tried two different USB cables.
Reinstalled XPpro SP2, fully patched.
Tried removing and rediscovering all USB drivers for both machines.
I've tried everything I could think of, and in every order I could think of.
The OS discovers the device, and ultimately gives me a popup message that the USB device is installed correctly and ready for use, but then 10sec later I get "USB Device Not Recognized" pop up error....
Should I roll back to a previous version of Activesync? Can I roll the ROM back to a previous version?
I admit to surveying the forums here before posting, but it seems a bit confusing to me and I certainly don't want to destroy my phone.
Thanks in advance for your help!
Click to expand...
Click to collapse
what os is running on your computer?
XPpro SP2 fully patched
jdtarch said:
XPpro SP2 fully patched
Click to expand...
Click to collapse
do you have .NET framework 2.0 installed?
edit removed questions that were answered in first post (guess I should read closer)
Did you flash a WM5 or WM6 rom?
I have issues with AS not being able to connect to my device sporadically when I am running WM5 roms but don't have issues at all with WM6 roms. I have no idea why this is but this problem goes away for me while running WM6.
Can you boot into bootloader and get a constant USB connection that way? if so you may be able to flash to another custom rom or shipped carrier rom.
And I know you said you already did this but uninstall and re-install activesync 4.5 to make sure its drivers are not corrupted. Select yest to overwrite when prompted (if prompted).
First off, I have read every thread mentioning error 260, every wiki about upgrading, and have not been able to fix my problem.
I am trying to upgrade to Schap's newest 6.0 ROM, not the 6.1. I currently have the OEM 5.0 ROM that came on the device from AT&T. I can connect via activesync perfectly. No issues there at all. When I run the upgrade program, it gets all the way to the status bar showing 0% or 1%, then the phone and computer disconnect the activesync connection, the phone goes back to the today screen, and my computer shows error 260.
I have seen posts saying I need to install HardSPL. I tried that and get error 260 there also.
I have seen posts about installing JumpSPL, I tried that and it only locks the phone up. I must do a soft reset to bring it back to life.
I found the instructions on upgrading the ROM via the SD card. I followed those and renamed the .nbh file and copied it to the fat32 formatted sd card in the phone. Where do the rest of the files go??? The .nbh file cannot possibly contain the entire rom, right? The instructions leave that part out from what I can see.
Help!
Device is a AT&T 8525. Thanks!
okeven said:
First off, I have read every thread mentioning error 260, every wiki about upgrading, and have not been able to fix my problem.
I am trying to upgrade to Schap's newest 6.0 ROM, not the 6.1. I currently have the OEM 5.0 ROM that came on the device from AT&T. I can connect via activesync perfectly. No issues there at all. When I run the upgrade program, it gets all the way to the status bar showing 0% or 1%, then the phone and computer disconnect the activesync connection, the phone goes back to the today screen, and my computer shows error 260.
I have seen posts saying I need to install HardSPL. I tried that and get error 260 there also.
I have seen posts about installing JumpSPL, I tried that and it only locks the phone up. I must do a soft reset to bring it back to life.
I found the instructions on upgrading the ROM via the SD card. I followed those and renamed the .nbh file and copied it to the fat32 formatted sd card in the phone. Where do the rest of the files go??? The .nbh file cannot possibly contain the entire rom, right? The instructions leave that part out from what I can see.
Help!
Device is a AT&T 8525. Thanks!
Click to expand...
Click to collapse
Try a different USB port first, fire the device into bootloader mode manually and see if the device is detected by windows as "HTC USB SYNC"........use a hardwired port NOT a USB Hub aswell.
I tried a different USB port. It is not being plugged in to an external USB hub. I went into the bootloader screen and my computer makes the sound that a USB device was plugged in and it does show in the device manager as "HTC USB SYNC". What now?
Now try to do an update, Sounds like a problem associated with the connection of the device to your machine...usually caused by messed up USB drivers or a conflicting program.
Just tried. Same error again. Tried restarting the computer and tried it again. No dice.
this is the answer
hey man, how u doing. I was getting those errors too, I actually have a Tilt, I got error 200, and 260 trying to change my rom, I was about to give up. then I tried something I didn't think of, I updated my device center software from Microsoft and then miraculously everything worked after that. If you have XP update your Active sync software to the latest one and everything should work after that. Hope this helps.
and one more thing, make sure you install HardSPL v1 (or later when its released) first before trying to install the ROM.
I don't think anything is wrong with your usb drivers
I had actually checked to make sure I had the most recent version already and I do. I cannot install HardSPL either, since it gives me error 260 there also.
Error 260 is an open port error... I believe you have already tried resetting your device, but have you rebooted your pc prior to this procedure... I am grasping at straws for you, since you said you have tried soft resetting to no avail... I believe MrVanx stated to put the phone in bootloader mode and try to run the update utility that way... It works for me...
Can you try this on a different pc? If so, does it work? I have a post on another forum that you might find interesting... I did not compile it on my own, but cannot recall where I got it from... anyway, the link is HERE...
Hope this helps you out...
I have restarted the computer multiple times. I just tried it on my laptop and that did not work. I can boot the phone to the bootloader, but how do I install it from there?
That should be the easiest part... once you have it in bootloader mode, connect it via usb and then launch the update utility...
I get error 260 doing that also. argh!!!
i know how u feel
i had your problem several times. you want to know how i fixed it?
i didn't...
first i tried everything you and the guys mentioned and... nothing. then it worked the next day by itself.
the second time i couldn't connect i was really mad because the errors came sporadically. i tried installing AS, uninstalling, hard resetting the device, changing usb ports, anything logical and illogical and it worked on changing usb ports (but not on the first change).
now i'm at my girlfriends, had no problems until i saw farias new rom and wanted to flash it. guess what connection error
p.s. i've read trough and trough, but i've found no solution
what version and OS?
okeven said:
I get error 260 doing that also. argh!!!
Click to expand...
Click to collapse
yeah, I thought u would dget that again. i don't believe the error is originating from your phone, its more from the computer. what operating system are you using and whats the version number for activeSync or MS Device Center you are using?
I had that error on my home pc and on my girlfriend's laptop prior to updating my device center software. My pc is running Vista ultimate x64 and my girlfriend's laptop is running Vista Home Premium x32. I'm on her laptop right now, the version of device center is 6.1.6965. when I get home I will see which version is on my computer, I remember seeing "beta" on the one I got at home, lol, I didn't know Microsoft sent out beta software through its msupdate.
okeven, someone replied with good suggestions to the thread that u accidentally started over in the kaiser forum. you might want to check that out
I have version 6.1.6965 also. It does not say anything about it being a beta version, but with Microsoft, isn't everything in beta stage?
I did try the "official wm6 AT&T" version. Upgraded just fine. Tried upgrading to another one. Failed with error 260. What is different with the official upgrade program compared to the unofficial ones. THAT is the problem.
help
hi guys,
i have the same problem always the code 260, and also, my tytn's screen become within light, and without any boot number, ni radio, anything appears, please help me,,
thanks,
Finnaly
Hi guys
I also have the 260 problem but i resolved it:
1º- connect pda and make a active sync connection
2º run RUU
3º the 3-color screen will appear and update will stop with the 260 message error. be sure you can install the "qualcomm cdma technologies msm driver" at this moment, by an internet connection.
4º after the driver is installed, the word "USB" will appear in the white strip of the 3 color screen;
5º run RUU again and that´s all!
I´ve tried it in windows 7 ultimate 32-bit
hi,
I had the same issue on my second flash... I resolved it by ignoring all .exe's (which I like in general).
So I copied the .nbh onto the card, renamed to Kovsimg.nbh, bootlader mode, done
cheers
lxlx said:
hi,
I had the same issue on my second flash... I resolved it by ignoring all .exe's (which I like in general).
So I copied the .nbh onto the card, renamed to Kovsimg.nbh, bootlader mode, done
cheers
Click to expand...
Click to collapse
Hermes use HERMIMG.nbh ... kovsimg.nbh is for Xperia X1 ..
Hi gys, I think that this is my first post, but I want to share some solution for with you. The most important think with "connection" errors is to have HSPL installed correctly. I was trying to install on my HD2 universal ones, like Hard spl v7 and 9, but problems occured. So after trying everything, I found HSPL (on this forum) just for HD2. After that, everything wass like a charm
Hi,
I have had my 8125 for about 2 1/2 years now, love it!. Just the other day, it started locking up and giving me the white screen of death.
I tried to flash it with a rom, and it got to 99% and then lost connection. Tried to do the recovery, but that failed too.
I have found alot of good information from the smart and wonderful people on this forum and tried a bunch of stuff.. but I am now stuck.
Now, I can always boot into the bootloader, and it says USB over the left softkey, but no apps can connect to the phone.
I tried to use other RUU roms, HardSPL, SoftSPL, etc...I tried to unlock my CID using the thread in this forum, but SoftSPL couldnt connect to the phone via USB.
All apps error with "error unable to connect to device."
I have read the forum about having a bad mimi-USB port, but I dont think thats my case.
Please help! I am pretty close
Dell D620 CoreDuo 1.8Ghz; WinXP SP2
ActiveSync 4.5
IPL 2.25.0001
SPL 2.25.0001
end123 said:
Hi,
I have had my 8125 for about 2 1/2 years now, love it!. Just the other day, it started locking up and giving me the white screen of death.
I tried to flash it with a rom, and it got to 99% and then lost connection. Tried to do the recovery, but that failed too.
I have found alot of good information from the smart and wonderful people on this forum and tried a bunch of stuff.. but I am now stuck.
Now, I can always boot into the bootloader, and it says USB over the left softkey, but no apps can connect to the phone.
I tried to use other RUU roms, HardSPL, SoftSPL, etc...I tried to unlock my CID using the thread in this forum, but SoftSPL couldnt connect to the phone via USB.
All apps error with "error unable to connect to device."
I have read the forum about having a bad mimi-USB port, but I dont think thats my case.
Please help! I am pretty close
Dell D620 CoreDuo 1.8Ghz; WinXP SP2
ActiveSync 4.5
IPL 2.25.0001
SPL 2.25.0001
Click to expand...
Click to collapse
Ok,first,no other custom build rom will flash on it,except official stock rom of the carrieror,however, you can try wizard_love rom,as it has patched IPL/SPL (Bootloaders),so don't try to flash any other custom build,as its a G4,custom rom can only be flashed through SoftSPL or HardSPL.
Download official carrier's stock rom and wizard_love rom.
Secondly,
1.Disable activesync or rather uninstal it altogether,as its not needed during flashing a rom.
2.End process 'wcescomm.exe' in the 'windows Task Manager.
3.Clear and delete the 'Temp Folder' files
4.Run 'Disk Cleaner'
5.Disable all Anti Virus and Firewall.
6.Try to stop/disable all running programs in the background via 'Task Manager'
7. Get the battery fully charged,as many comm errors are due to weak or discharged battery.
After doing all this,get the phone in Bootloaders before connecting with pc via usb cable,there shudn't be any usb at the bottom of the Bootloaders,now connect with pc and check if usb appears at the bottom,if its there than,its establishing connection,go ahead and run official stock or wizard_love rom.Don't use the pc or play games or check emails,don't even do any word,excell or any office application.Check if any application/program interferes with the flash,either disable or remove that program.
Does the battery get charged through usb cable ? verify it.
If after getting the phone into bootloaders and connecting through usb cable,small usb doesn't appear,it means there's a connectivity problem,replace the usb cable and verify it again.Even try with another pc with winXP or change the usb input port of the pc ,put the usb cable in some other usb port on the pc.
Apart from all these,I don't find any reason for not getting the flash completed
Hi,
Thanks for the help.. I tried the wizzard_love rom, and then went to the NBD_v8.3 /w TouchFlo rom and thats awesome!
my biggest issue was not able to connect to the device although it looked like it should have.
on another thread someone said to leave the battery out for 5 mins. I did that and all of a sudden it started to connect consistantly.
After that I did the HardSPL and started flashing and all is well..
Thanks for your help!!!!
Hi Guys,
since 3 hours i try to upgrade the SPL from my Touch Pro. Searched the Forum up and down and walked hundred miles around in google but i can't find any solutin...
I've connected the device to my PC via ActiveSync, started the "RaphaelHardSPL-Unsigned_190_1_3.exe", followed the instructions and the progressbar appeares. Now i allowed the programm "bootloader.exe" on the TP to start and it goes into black screen... ActiveSync is disconnecting and the blackscreen stay there -without any change.
I've tried this on 2 PC's (Vista Ultimate 64bit and XP SP2 Pro). Always the same
I've tried the "SSPLManual.exe", too. Copied to the phone and execute it... There comes the blackscreen and nothing else (for more than 20 minutes) - ActiveSync got disconnected after the blackscreen.
Does anyone have an idea what i can do to get this thing working?
Want to Upgrade my Radio and/or the ROM
Thanks for helping!
Sorry for the bad englisch
fireballrs said:
Hi Guys,
since 3 hours i try to upgrade the SPL from my Touch Pro.
I've connected the device to my PC via ActiveSync, started the "RaphaelHardSPL-Unsigned_190_1_3.exe", followed the instructions and the progressbar appeares. Now i allowed the programm "bootloader.exe" on the TP to start and it goes into black screen... ActiveSync is disconnecting and the blackscreen stay there -without any change.
I've tried this on 2 PC's (Vista Ultimate 64bit and XP SP2 Pro). Always the same
I've tried the "SSPLManual.exe", too. Copied to the phone and execute it... There comes the blackscreen and nothing else (for more than 20 minutes) - ActiveSync got disconnected after the blackscreen.
Does anyone have an idea what i can do to get this thing working?
Want to Upgrade my Radio and/or the ROM
Thanks for helping!
Sorry for the bad englisch
Click to expand...
Click to collapse
Is your phone GSM (SIM card), or CDMA (no SIM card)?
Oh, sorry forgotten this.
It's an GSM device. (German original HTC ROM)
Did you use the SSPL.exe, then while the screen is black double click the RaphaelHardSPL-Unsigned_190_1_3.exe? Thats what you need to do, the SSPL.exe is only to get the device into the black screen, you still need to click on the RaphaelHardSPL-Unsigned_190_1_3.exe to flash the Hard Spl!
I've got it.
Don't ask me how! I think i go crazy here.
To answer you and check whats happen then i do the same things again, that i'm doing the hole time. Connect to active sync, run the upgrade, blackscreen, but now vista was searching for the driver, it connects again and the update was successful.
Don't understand anything but it worked...
thank you
fireballrs said:
I've got it.
Don't ask me how! I think i go crazy here.
To answer you and check whats happen then i do the same things again, that i'm doing the hole time. Connect to active sync, run the upgrade, blackscreen, but now vista was searching for the driver, it connects again and the update was successful.
Don't understand anything but it worked...
thank you
Click to expand...
Click to collapse
Your welcome, glad you got it working! Enjoy your wonderful phone!
Enough said closing thread.
-McMex
as soon as i try and flash the HSPL or a ROM it disconnects me from my usb connection, ive made sure numerous times that it is synced up before i start the flashing but as soon as they start it automatically disconnects me and the flashing doesnt work. Ive tried switching usb ports on my comp and nothings worked.... any ideas????
enter bootloader manually, when on coloured screen connect usb, wait for word serial to change to usb, and dont forget to right click and 'run as administrator'
thank you that worked so far, also its asking me which HSPL verson to install....
2.08. HSPL? or 2.08.0000?
it says my installed version is 2.10.0000
fbstud said:
2.08. HSPL? or 2.08.0000?
Click to expand...
Click to collapse
go on, have a guess, , is it the one with HSPL in the version, or the one without?, , , , , , ,
2.08.0000 is for returning to stock, you want 2.08.hspl
My first post!
And that last one above there made me chuckle, alot!
Sorry for posting on something almost a month old but it's the closest thing I can find to my problem.
So I've figured out I need HSPL to do any flashing, so i figured HSPL3 would be a good choice?
I'm currently on my boot screen and it says i have SPL- 1.42.0000, but the word at the bottom will not change from Serial to USB. I've got the HSPL3_PKG ready to run as admin when it does, but no change at the moment
Thanks for the help
forgive the dumb question, but the usb cable IS plugged in to the phone AND the computer, right?
haha yeh.
im on a laptop, there are 3 USB ports and i've tried them all.
there is one thing, one time when my phone was plugged in it started the whole windows device driver software thing, and then it said that it failed. could that be causing some sort of usb connection problems with my phone?
thanks alot, I see you're very busy!
is it something to do with my stock rom that ive not seen mentioned anywhere
1.43.206.4 (70315) WWE
?
:S
no, not the rom, but yea, the drivers not installing is probably it. You need to make sure that windows mobile device center (or active sync if you are on xp) is the latest version.
what you can try is, (after you have made sure you're on the latest wmdc version of course) with the phone connected, call up device manager, (on vista/7 , right click my computer, choose properties, device manager should be an option down teh left) find the entry for the phone (probably called unknown device, or something) and right click it, and choose update driver.
been trying to get hold of a WMDC download all evening but i think i'm hitting some server problem their end.
just checked the version i have, is 6.1.6965 and i think it was 6.1 i was after so i guess ill try and hook it up like you said above, will let you know...
damn 'windows has determined that the driver software for your device is up to date' think i have a plagued HD2 :S
wait, just reread you r fisrt post again.
When you start to flash it DOES disconnect, its supposed to disconnect.
Try this, enter bootloader manually, connect the usb cable (ignore what does or doesnt happen on teh pc) on teh phone, does the word serial change to usb? if it does, run your flash.
EDIT - oh, lol, you arent the OP, and i just read post 1, lol, ignore.
apparently i am missing some driver, Qualcomm CDMA or something like that... trouble is that i cant get a hold of it, theres a few threads on xda that mention it but no solutions.
normally, when a comp is asking for qualcomm drivers, it indicates a problem. Mostly it is when a tmous has been bricked, but occasionally other people have reported it. There aren't any qualcomm drivers that we know of. (Well, theres a thread that is titled qualcomm drivers, and does indeed include what appear to be drivers, but they wont install on windows.)
If i were you id focus on trying to find another pc to try it on. That way you will know if its a pc problem or a phone problem.
good call, i think ill opt for the trusty XP, just need to find that old laptop...
hopfuly you won't be hearing from me for a while.
i read that XP is more stable for flashing off of cos its more blunt, what do you think?
well, its certainly seems to cause less problems, especially HSPL'ing.
Good luck, and goodnight.