Related
well, i can't figure out quite what has happened.
i was attempting to install hard SPL v7 prior to upgrading to the latest LVSW 0423 ROM.
activesync was connected, i ran RUUWrapper.exe and it dropped the 8525 into bootloader mode as it usually does. for some reason, the RUU app was unable to verify the info on the phone, so upgrade failed and it quit. i reset the 8525, and it booted normally.
well...now USB appears to be dead. forcing the device into bootloader shows
Code:
HERM100
IPL-1.01
HERM100
SPL-1.30.Olipro
Serial
connecting the USB cable does nothing - the bootloader continues to show "Serial". i can reboot and all is fine, radio works...nothing else is wrong except there is no comm via USB. the device charges via USB just fine, whether the 8525 is powered on or off.
nothing in the hermes bricked wiki page matched up, as i have a working OS and a working radio...but i saw in another post that being stuck with "Serial" is evidence of a corrupt bootloader.
ideas? thanks!
Try running the RUU again. If it is still dead then try flashing via SD card.
jamiefiedler said:
well, i can't figure out quite what has happened.
i was attempting to install hard SPL v7 prior to upgrading to the latest LVSW 0423 ROM.
activesync was connected, i ran RUUWrapper.exe and it dropped the 8525 into bootloader mode as it usually does. for some reason, the RUU app was unable to verify the info on the phone, so upgrade failed and it quit. i reset the 8525, and it booted normally.
well...now USB appears to be dead. forcing the device into bootloader shows
Code:
HERM100
IPL-1.01
HERM100
SPL-1.30.Olipro
Serial
connecting the USB cable does nothing - the bootloader continues to show "Serial". i can reboot and all is fine, radio works...nothing else is wrong except there is no comm via USB. the device charges via USB just fine, whether the 8525 is powered on or off.
nothing in the hermes bricked wiki page matched up, as i have a working OS and a working radio...but i saw in another post that being stuck with "Serial" is evidence of a corrupt bootloader.
ideas? thanks!
Click to expand...
Click to collapse
change your usb cable
stukes said:
Try running the RUU again. If it is still dead then try flashing via SD card.
Click to expand...
Click to collapse
i tried running the RUU again, but since hard SPL v7 (and most of the other RUU updates) seem to require a working activesync connection - which i can't get withoutout USB - i've had no luck.
flashing via SD card is a great idea - didn't even think of that, thank you. i'm not entirely sure which nbh would be appropriate to flash in this situation though - a complete OS/radio/BL package or attempt just the hard SPL nbh file again?
pof said:
change your usb cable
Click to expand...
Click to collapse
sorry...should have mentioned i tried another cable. both cables i tried are verified good with another device, and both cables are able to charge the 8525 when connected.
one more thing...if this is in fact a screwed up bootloader, is there anything valuable i can check/monitor/log while attempting to fix this to benefit anyone on the site?
Its up to you. I would try only the Bootloader because it will be superquick. Maybe you should check out the Flashing from SD Card Thread.
stukes said:
Its up to you. I would try only the Bootloader because it will be superquick. Maybe you should check out the Flashing from SD Card Thread.
Click to expand...
Click to collapse
ok, i'll give the straight bootloader a shot.
i was gonna follow the sd card flash instructions on the wiki...seemed simple enough. are you thinking of another thread i should check first?
thanks for your help, greatly appreciated. i'll post results of course.
jamiefiedler said:
flashing via SD card is a great idea - didn't even think of that, thank you. i'm not entirely sure which nbh would be appropriate to flash in this situation though - a complete OS/radio/BL package or attempt just the hard SPL nbh file again?
Click to expand...
Click to collapse
Flash HardSPL latest version first, otherwise you'll overwrite it because you have an old version which does not have SPL protection.
jamiefiedler said:
sorry...should have mentioned i tried another cable. both cables i tried are verified good with another device, and both cables are able to charge the 8525 when connected.
Click to expand...
Click to collapse
Try another usb port on computer then... or better, another computer and another usb cable.
jamiefiedler said:
one more thing...if this is in fact a screwed up bootloader, is there anything valuable i can check/monitor/log while attempting to fix this to benefit anyone on the site?
Click to expand...
Click to collapse
either your hermes usb connector is broken (which i doubt cos is able to charge) or you're using a bad cable, a bad usb port on computer, or an operating system without proper usb driver installation. For sure is not a problem of the SPL.
jamiefiedler said:
ok, i'll give the straight bootloader a shot.
i was gonna follow the sd card flash instructions on the wiki...seemed simple enough. are you thinking of another thread i should check first?
thanks for your help, greatly appreciated. i'll post results of course.
Click to expand...
Click to collapse
The WIKI is great. Pof gave you a nice sum'd up list.
ok...flashed hard SPL v7 successfully - now have SPL-2.10.Olipro but still no USB - pof was right (surprise surprise), it wasn't the bootloader.
i've now tried this using 3 different usb cables with 2 different USB ports on each of 2 different XP boxes. activesync is unresponsive on both (i've used activesync 4.5 successfully on both in the past) and when watching in bootloader mode then 8525 continues to show "Serial" in all cases.
maybe just one of the data pins of the mini-USB jack is damaged? intact power pins would still allow it to charge even if a data pin was bad.
unless anyone has another suggestion, i'm going to assume it needs to be rolled back to the cingular ROM and sent off to HTC for (attempted) warranty repair...hopefully nobody will notice anything SPL/CID related.
Bummer man. Try yanking the battery out while it is on and let it sit with it out for a while. Then roll back to your original ROM. Sucks if it where a bad pin.
This is a stretch, but anytime I have hardware connection issues (hard drive, flash drives, etc) I put them in the freezer for 10 mins. If it works, at least you know its the hardware.
peezy said:
This is a stretch, but anytime I have hardware connection issues (hard drive, flash drives, etc) I put them in the freezer for 10 mins. If it works, at least you know its the hardware.
Click to expand...
Click to collapse
LOL. I saw this somewhere before. Now for the more serious thought effects of extreme cold.
Moisture
Metals Expand and Contract
i popped the back off the 8525 and took a close look at the mini USB jack's pins, expecting to see evidence of a damaged pin (or more than one). well, no damaged pins - but i did find what looked to be a tiny sliver of metal that had worked it's way down (or in from outside) and was lodged between a couple of the pins. i used an x-acto knife to gently scrape between the pins as they traveled down to the main board, making sure not to damage any of the pins. went through all of them just in case, then closed it back up.
USB = working. problem solved.
thanks guys, as always i really appreciate your help.
Outstanding!!!
Very Nice!
btw stukes I put my dead sd card in the freezer last night, and what do you know? It Works! I know its a bit of a black art but I have used it successfully more than once.
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
Hello everyone,
I tried to update my o2 mini s G4 WM5 device to WM6 and everything went ok. At work i have installed some software and plocies on my devices, which i didn't wat to keep, so i tried to reflash the device, in the same way i flased it in the first place. The problem is that now it is stuck on the Bootloader screen . When i connect the cable i can see the USB text.
I have read a bit about it, and people are saying to use the original o2 rom, or the wizard love one. Can i use any? If so, where can i fond it as the only love one which i found is Wizard_Love_2.26.10.2_WWE_Novii_CF2.rar so i think it is a G3 rom isn't it?
Thank you,
Wooju
and one more thing, how do i flash the software into the phone if it is stuck on the bootloader screen? When i connect it to the pc, the active sync says it is not connected...
Thank you,
it will flash if you are in bootloader mode. flash to the rom that your device shipped with then start over.
Hello,
i tried to flash it again, firstly with RUU_Wizard_1050402_101_11210_O2_ENG.exe then with HTC_Wizard_Rom1.rar which i found in the internet. In both cases i got error 263 (that it can't connect to the device).
When i connect the phone to the pc i can see that it is detectet as ie the drivers instalation wizzard appears...
Any ideas? Is the phone broken completely?
Thanks
im having problem with installing any rom... even stock rom cannot be installed. I have HSPL 2.08 installed. I can enter bootloader. The installation of rom goes through the version check window and then when i hit flash button it shows 0% and after 10 secs pops out window with error code 266 that it cannot get response from the device.
I also tried flashing from the stock sd card (2gb, FAT32 formated) with the stock nbh file renamed to leoimg.nbh but when i enter bootloader mode nothing happens and im stuck on the three coloured screen. I really dont know where's the problem.
I have already had several WM6,5 roms installed... i have tried WP7 and currently i have NAND Android and Magldr 1.12 and nothing happens even if i want to update it to 1.13. Only flashing that works is flashing SPL/HSPL. It works without any issues...
If anyone have an idea i would be very thankfull, because i have tried almost everything.
Please post the spl line from bootloader. Go look, don't just assume it's still what you think it is.
it shows:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x50
janox1x2x3 said:
im having problem with installing any rom... even stock rom cannot be installed. I have HSPL 2.08 installed. I can enter bootloader. The installation of rom goes through the version check window and then when i hit flash button it shows 0% and after 10 secs pops out window with error code 266 that it cannot get response from the device.
I also tried flashing from the stock sd card (2gb, FAT32 formated) with the stock nbh file renamed to leoimg.nbh but when i enter bootloader mode nothing happens and im stuck on the three coloured screen. I really dont know where's the problem.
I have already had several WM6,5 roms installed... i have tried WP7 and currently i have NAND Android and Magldr 1.12 and nothing happens even if i want to update it to 1.13. Only flashing that works is flashing SPL/HSPL. It works without any issues...
If anyone have an idea i would be very thankfull, because i have tried almost everything.
Click to expand...
Click to collapse
Have you tried a different USB port or a different computer? If this does not work try another USB cable. As far as flashing from SD make a copy of your SD card on your computer and reformat it.I know you said it was already Fat 32 but sometimes it helps to theroughly clean your SD card, this is what reformating it will do. Once you have it reformated just put the ROM on it and try flashimg it again.
so i have finally fixed the problem. The problem was very simple. ROM flash utillity doesn't support USB 3.0 but anyway i don't understand why flashing with sd card doesn't work because i have tried several sd cards with various size.
janox1x2x3 said:
so i have finally fixed the problem. The problem was very simple. ROM flash utillity doesn't support USB 3.0 but anyway i don't understand why flashing with sd card doesn't work because i have tried several sd cards with various size.
Click to expand...
Click to collapse
It is not that it does not support USB 3.0.The problem was that your HD2 drivers cor the USB port you were using were most likely either nolonver correct or corrupted. This is a common probblem for some reason. Maybe samsamuel can post here again and explain it a little better. Glad you got your HD2 up and running again.
T-Macgnolia said:
It is not that it does not support USB 3.0.The problem was that your HD2 drivers cor the USB port you were using were most likely either nolonger correct or corrupted. This is a common probblem for some reason. Maybe samsamuel can post here again and explain it a little better. Glad you got your HD2 up and running again.
Click to expand...
Click to collapse
well im no engineer, but each usb port installs drivers individually for anything you plug in, so port 1, it installs the hd2 drivers, port 2, it installs them again, and sees them as two seperate instances. if you then mess with android, say, and/or wp7, and mtty, you replace those drivers with other drivers, but only for that port, so you can potentially end up with three sets of different drivers on three different ports, so you try something that requires winmo drivers, and the pc is trying to use the ones tweaked for mtty.
Only a theory, thats what usb does, whether thats really the problem, who knows. makes sense to me, so im sticking to it. ALways pays to find the device in hardware list and uninstall it now and again, including 'remove drivers'.
That being said, there could be something in the usb 3 theory in this instance.
well i cannot argue with you guys, because you might be right. But i tried two different USB 3 ports with the exactly same result and failed then i tried USB 2 port and succeded without any problems so maybe there's something about it
Hi!
I got a HD2 (it seems to have 512MB flash but it is from T-Mobile) which won't boot everytime. Sometimes it stops.
So I tried to flash new Modemfirmware and new rom.
Modemflashing mostly stopps at 99% or 100% with an error and firmwareflash everytime at another percentage.
HSPL/SPL flashing works fine.
I tried two different PCs, phone directly connected to PC or connected through active USB hub and so on.
Everytime the same.
What can I do now? Can I try to flash the phone via goldcard? But how do I get the correct CID?
I doesn't matter if the phone will run with custom rom or stock. It only have to run and have German language.
Thanks!
Regards
Chris
Gold card can only be created with a functional wm on your HD2.
But sd card method should also be working, if you use t-mobile rom: http://www.t-mobile.de/fremdcontent/1,2790,152221,00.html.
Are other USB devices connected to your PC? If yes, disconnect them. Don't use a hub.
uli71 said:
Gold card can only be created with a functional wm on your HD2
Click to expand...
Click to collapse
Or ANY functional winmo phone, doesn't have to be a hd2.