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
Related
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 buddies,
I created a new thread because I think this issue has not ever treated specifically. When I connect my Hero to my computer, i get USB charging only, and windows shows me the error "usb device not recognized". I tried in two windows 7 PCs, one with Vista, one with XP and one with Ubuntu Maverick, and the same problem. I think that no matter what operating system you try it, because the problem is not drivers, and that is not even recognize the device. Before I was with Floyo and the flykernel 11c. I changed the kernel, I tried several roms (with and without Sense) and nothing ... so I tried it in recovery, and nothing ... and I can not mount as USB Mass Storage from the recovery. I tried with two original HTC cables and a miniUSB cable, with identical results. Someone advised me something?
NOTE: I created this thread in development forum because I need to link development ADB to develop in Eclipse, which used to be able to perfectly
Thanks in advance, and happy new year for you all!!
If you can't mount in Recovery, I would assume there is a problem with your SD card. Have you got another one to test with?
that's i'm just trying, i'm backing up my sdcard to my laptop and low-level format it...
if doesn't work, i'll try with another sd...
thanks for the response, that was quick i'll try and comment here
I shouldn't make a difference to mounting the SD card, but make sure USB debugging is enabled (you may have flashed a ROM which has it disabled by default).
What error do you get if you try and connect to it via ADB?
i'm still backing up the SD stuff to format it...
i tried before usb debugging enabled and disabled, and the same error...
i haven't errors with adb, simply if i try "adb devices" it isn't any device...i'm looking at my logcat and can't see any strange output. In the "devices' administrator" in windows (sorry for my crappy english) it appears "Unknown Device"
not working at all (tried with two microSD, both formatted in fat32)
tried formatting it in windows and in the phone...
here is the recovery.log...
Here is something to try, boot into fastboot and run the following two commands:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
You will need an unlocked SPL for this to work though
same thing
Hi pulimento,
I HAD THE SAME PROBLEM.. curious, i got it after installed the "Flykernel-12c". There is a thread that a i related the problem. Look for my posts.. but just a info, today I was not able to recovery the CELLPHONE, this is happen about 2-3 weeks. You descrived the same situtation that I had.
The SD card is working, I tested in another device. But the HTC hero can not mount. Its weird.
And also, trying to solve, i did something terrible, I format the system..and not way, the same behavior. Now I stucked in the bootscreen .
pulimento said:
Hi buddies,
I created a new thread because I think this issue has not ever treated specifically. When I connect my Hero to my computer, i get USB charging only, and windows shows me the error "usb device not recognized". I tried in two windows 7 PCs, one with Vista, one with XP and one with Ubuntu Maverick, and the same problem. I think that no matter what operating system you try it, because the problem is not drivers, and that is not even recognize the device. Before I was with Floyo and the flykernel 11c. I changed the kernel, I tried several roms (with and without Sense) and nothing ... so I tried it in recovery, and nothing ... and I can not mount as USB Mass Storage from the recovery. I tried with two original HTC cables and a miniUSB cable, with identical results. Someone advised me something?
NOTE: I created this thread in development forum because I need to link development ADB to develop in Eclipse, which used to be able to perfectly
Thanks in advance, and happy new year for you all!!
Click to expand...
Click to collapse
Hi Lost,
I did the command below:
fastboot oem enableqxdm 0
And its waiting for device eternally.
Any clue?
What do you mean UNLOCKED SPL? SPL?
thanks
l0st.prophet said:
Here is something to try, boot into fastboot and run the following two commands:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
You will need an unlocked SPL for this to work though
Click to expand...
Click to collapse
thanks, i'll try after lunch...
l0st.prophet said:
Here is something to try, boot into fastboot and run the following two commands:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
You will need an unlocked SPL for this to work though
Click to expand...
Click to collapse
Tried it with the unlocked SPL, and nothing... tried wiping (fastboot -w) too. i'm running now CM6.1.
What I need to run a RUU? I think that a RUU writes a new hboot, boot.img, radio, ROM...and MAY solve the problem, but i need usb connectivity to run it. any chances?
any commands to try in fastboot (with unlocked spl)?? thanks in advance
The info about flashing an RUU without USB is readily available, in the thread regarding "unbricking" after the original 2.1 update from HTC. You will however need a card reader or oither device that reads MicroSD cards to do it tho. Basically you take the HEROIMG.zip file (called rom.zip) that is extracted from the RUU exe and copy to the root of your SD and then start your device i hboot mode and follow the on screen instructions. For a more detailed explanation have a look at the afore mentioned thread.
tried this (after googled A LOT) :
http://forum.xda-developers.com/showthread.php?t=691639
and not working...
The problems appear to be in MISC partition, there is a parameter with an invalid config (something as UART_ENABLE = 0 or similar...)
do anyone know that "flashing the RUU" (with the HEROIMG.ZIP) will write that partition? i'm pretty sure, but not 100% sure
i'll try a few things tomorrow, now i'll go to celebrate the new year happy new year XDA!!!
PS: users with the same problem, to investigateby yourself, try searching USB Brick Android in google
I had this problem. I bought a micro sd to USB adapter to put another ROM on the card and flashed another ROM that way. That seemed to fix it for me.
now, i'm really disssapointed...hero doesn't recognize sd card at all (even in recovery) and i haven't got fastboot usb connection...and i'm stucked with a 1.5 Sense ROM!!! any ideas? can't download anything from internet (no SD CARD) and can't fastboot... SH*T!!
now, i'm in android 1.5, i do the HEROIMG.zip method...but still USB bricked...going to try another time...i must flash MISC partition with mtd0.img file...(see link in post #13) but be careful if u try this!! You must HEX-edit the mtd0.img to match with your CID (mine is ORANG309) and ROM version!! (mine is 2.74.something)... and you may have installed a SENSE rom...think that our Hero oficially only can use that kind of ROM.
That's the result of my investigation, hope it helps
GREAT NEWS!!!!!!!!!!!!!!!!!!!!!
I only did the procedure below and work.
http://forum.xda-developers.com/showpost.php?p=4467471&postcount=13
I was possible to FLASH ANOTHER ROM.
It was possible to read the SDCARD -> HEROIMG.zip in the FLASHBOOT mode.
GOOOOOOOOOOOD
But the SDCARD AND USB still not work. But now I have a OS at least.
EDIT1: After the install, I upgraded(to ANDROID 2.1) the OS though the HTC OTA(automatically)..
EDIT2: After the OTA to 2.1..THE SD CARD AND USB LINK ARE WORKING!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
All right guys, so my TMOUS HTC HD2 has broken and won't charge anymore, nor will the phone recognize there is a USB cable plugged in, the cable is plugged in correctly the phone just doesn't recognize it. Luckily before the phone completely didn't recognize it, I managed to flash the stock rom onto the phone using the update utility with the computer. The problem is, if I try to swap the phone out with a new one, they won't take it if the HSPL is there. I can't remove the HSPL using the HSPL program because the usb cable won't get recognized, and I tried flashing the custom rom through an SD Card using EXACT instructions:
1.)Format SD Card to FAT32 (Tried using computer and from phone)
2.)Extract files from the updater.exe
3.)Copied the RUU_signed.nbh to the root of the sd card
4.)Renamed it to LEOIMG.nbh
5.)Have 50% battery in a battery
6.)Held down the bottom volume key while booting the device
And then it shows Loading... for a split second and just sits at the Tri-color screen. I have no idea what I can do now to get the original SPL back onto the device so I could use some serious help please.
Nevermind, after some detailed research I found out that the TMOUS stock card, a 16 gb card, does not work with this method of installing a rom. Only cards that are 8 gb or less work/
The best you can do is to use a 2GB Sd card.
Even 8GB Sd cards have some problems.
skrizzyboy said:
All right guys, so my TMOUS HTC HD2 has broken and won't charge anymore, nor will the phone recognize there is a USB cable plugged in, the cable is plugged in correctly the phone just doesn't recognize it. Luckily before the phone completely didn't recognize it, I managed to flash the stock rom onto the phone using the update utility with the computer. The problem is, if I try to swap the phone out with a new one, they won't take it if the HSPL is there. I can't remove the HSPL using the HSPL program because the usb cable won't get recognized, and I tried flashing the custom rom through an SD Card using EXACT instructions:
1.)Format SD Card to FAT32 (Tried using computer and from phone)
2.)Extract files from the updater.exe
3.)Copied the RUU_signed.nbh to the root of the sd card
4.)Renamed it to LEOIMG.nbh
5.)Have 50% battery in a battery
6.)Held down the bottom volume key while booting the device
And then it shows Loading... for a split second and just sits at the Tri-color screen. I have no idea what I can do now to get the original SPL back onto the device so I could use some serious help please.
Click to expand...
Click to collapse
hello,
i have a problem with spl 3.03..... on htc hd 2, because when i load the soft, the SKIP its not response when i touch the phone screen, its blocked, no reaction. and the phone its blocked, not working anymore.
What can i do
the same problem is in spl 1 48 or 1 66.The problem persist.
thanks so much, for any advise
another good solution and cheep.
lughian said:
hello,
i have a problem with spl 3.03..... on htc hd 2, because when i load the soft, the SKIP its not response when i touch the phone screen, its blocked, no reaction. and the phone its blocked, not working anymore.
What can i do
the same problem is in spl 1 48 or 1 66.The problem persist.
thanks so much, for any advise
another good solution and cheep.
Click to expand...
Click to collapse
faulty touch screen. roms wont help.
I have done this already but I am having to do it again to send my HTC back in for repair again. I keep however getting this error message:
"00018003"
"LEOIMG,nbh - FAIL"
"RADIO - Fail"
Then under all this it says, "Update Terminate, update fail"
I have tried 16GB, 8GB, 2GB and 1GB cards, all fully formatted to FAT32, all with just the LEOIMG.nbh file on the root, and all do exactly the same thing (apart from the 1GB that does nothing).
Help me please.
EDIT:
Ok so I managed to flash a stock ROM using the USB, so I now have windows. I still however have the cortulla HSPL on my phone. Also the reason I have to send my phone in is because it keeps white screening, should I leave it and use Windows to see if it white screens in this form?
All sorts of issues here.
I am no longer able to install new ROMs on my Aria. In the past I have flashed many ROMs on the phone. Recently I flashed an ICS rom but I did not like the way it was working so I went back to Cyanogenmod 7.1 RC1. Now for whatever reason, I am unable to flash any other ROMs. I put the new rom on the SD card like I always had then boot to CWM, go to install from SD card and it says that there are no files there. Which is not true and its not the SD card because I can still see the files with a file manager. When I select the ROM from inside ROM Manager it goes through the process but stops shortly after starting the install. I have heard that using a different version of CWM may work but when I try to download one from ROM manager it says an error occurred when trying to download. Also when I hook the phone up to my PC it doesnt recognize that it is plugged in other than its charging. (yes it is the original USB cord and USB debugging is on).
A few details: This phone has never connected with my current/new PC. It did work at one time with my old one. While trying to fix this I did a complete wipe of the phone, the first time I hooked it up to my current PC I got the whole new hardware detected thing on my PC and USB debug was active on the phone, but I don't know if I accidently hit a wrong option on my PC but it went right away and has never connected again.
I also noticed that the phone is S-ON, I thought/assumed it was S-OFF before. Could it have some how turned back on? I cant get it back off now since I cant use ADB without USB Debug connected.
I no longer use this Aria for daily use (replaced with One X ) so I am open to some possible "extreme" ideas of trying to fix this.
Thanks for any help. This is driving me nuts.
I'd probably do the following:
1) Format SD card fresh using this program, which can fix some problems with the way SD cards are formatted. It can fix stuff that formatting with Windows or from the phone directly won't fix. Worth a try first since it's relatively easy and will rule out the possibility that the SD card just got got corrupted or something.
2) If that doesn't work, and if you have HBOOT 1.02 or older, run the 2.2.2 RUU on the phone to completely reset everything. Then use Revolutionary to S-OFF the device again, and install one of the CWM builds here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66 . Hopefully whatever the problem is will be corrected by doing all that.
If you have HBOOT 1.03, let me know and I'll tell you what else you need to do first. (This won't work without downgrading to 1.02.)
drumist said:
I'd probably do the following:
1) Format SD card fresh using this program, which can fix some problems with the way SD cards are formatted. It can fix stuff that formatting with Windows or from the phone directly won't fix. Worth a try first since it's relatively easy and will rule out the possibility that the SD card just got got corrupted or something.
2) If that doesn't work, and if you have HBOOT 1.02 or older, run the 2.2.2 RUU on the phone to completely reset everything. Then use Revolutionary to S-OFF the device again, and install one of the CWM builds here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66 . Hopefully whatever the problem is will be corrected by doing all that.
If you have HBOOT 1.03, let me know and I'll tell you what else you need to do first. (This won't work without downgrading to 1.02.)
Click to expand...
Click to collapse
Thanks. I will give that a try.
drumist said:
2) If that doesn't work, and if you have HBOOT 1.02 or older, run the 2.2.2 RUU on the phone to completely reset everything. Then use Revolutionary to S-OFF the device again, and install one of the CWM builds here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66 . Hopefully whatever the problem is will be corrected by doing all that.
If you have HBOOT 1.03, let me know and I'll tell you what else you need to do first. (This won't work without downgrading to 1.02.)
Click to expand...
Click to collapse
How can I run this if I can not establish a connection to my PC? (I have HBOOT version 0.57.0000)
I tried the SD card format and it did not work.
I also noticed an error when first booting into recovery that says something along the lines of I do not have enough internal memory. I have wiped the data on this phone a few times so I cant imagine anything being actually full.
chadd74 said:
How can I run this if I can not establish a connection to my PC? (I have HBOOT version 0.57.0000)
I tried the SD card format and it did not work.
I also noticed an error when first booting into recovery that says something along the lines of I do not have enough internal memory. I have wiped the data on this phone a few times so I cant imagine anything being actually full.
Click to expand...
Click to collapse
Install this first: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
Then try running the RUU again.
chadd74 said:
How can I run this if I can not establish a connection to my PC? (I have HBOOT version 0.57.0000)
I tried the SD card format and it did not work.
I also noticed an error when first booting into recovery that says something along the lines of I do not have enough internal memory. I have wiped the data on this phone a few times so I cant imagine anything being actually full.
Click to expand...
Click to collapse
I have tried installing that before (tried again this time too) and it doesn't help. I still have no connection to the phone. I have Windows 7 if that helps anything.
I've found the most reliable way to get them to communicate is to put the phone into fastboot mode before connecting it to the computer, then running the RUU again. (If you don't know, to get to fastboot mode, select fastboot from the hboot menu.)
drumist said:
I've found the most reliable way to get them to communicate is to put the phone into fastboot mode before connecting it to the computer, then running the RUU again. (If you don't know, to get to fastboot mode, select fastboot from the hboot menu.)
Click to expand...
Click to collapse
That didn't work either. I am thinking it has something to do with the PC. I installed that driver package you just put up there but is it possible that it didn't install correctly? How could I check that? When I installed it, it never gave any confirmation or anything. Just gave a load screen then went away.
chadd74 said:
That didn't work either. I am thinking it has something to do with the PC. I installed that driver package you just put up there but is it possible that it didn't install correctly? How could I check that? When I installed it, it never gave any confirmation or anything. Just gave a load screen then went away.
Click to expand...
Click to collapse
You can try going to the uninstall programs list in control panel and uninstall anything related to HTC, rebooting, then installing the drivers I linked to again. Otherwise I'd just try on another computer if you can.
Edit: Also, before even trying that, you might just try different USB ports on the computer. If you are connecting to a USB 3.0 port (blue port), try a non-3.0 port (black port).
drumist said:
You can try going to the uninstall programs list in control panel and uninstall anything related to HTC, rebooting, then installing the drivers I linked to again. Otherwise I'd just try on another computer if you can.
Edit: Also, before even trying that, you might just try different USB ports on the computer. If you are connecting to a USB 3.0 port (blue port), try a non-3.0 port (black port).
Click to expand...
Click to collapse
Well,sort of good news here. I had tried different USB ports before but thought I would give it another go, it still was not connecting. So in a bit of a fit of rage I took the micro usb cord at shoved it quite hard into the phone. Well the connection flickered. So it appears over the years the USB slot had gotten a nice amount of pocket lint or whatnot jammed tight in there to where it would connect enough to charge but not enough for a PC connection. I cleaned it all out the best I could and what do you know, it worked.
Foiled by pocket lint.... SMH.
I loaded the 2.2.2 RUU and will give the rest of the problems a go tomorrow and post an update. Thanks again for all the help.
Looks like everything is working like it used to.
Thanks again.
I have an old Hd2 (512mb) with a broken screen sitting in a draw. I had installed WP7 on it.
Looking at making this a back up phone if I can install android on it.
Trouble is since managing to get back to wm6.5, I have lost MAGLDR and spl now says 3.03.0000 instead of saying slp2.08.hspl as it did before. Also now I can not flash anything as it either have a crittical error and stopping (phone goes to % done screen then sits on 0% till crash alert on pc hits). I have tried flashing from the sd card and it goes to the white screen and says loading... then sits there.
Current specs
OS 5.2.21913 (21913.5.0.94)
Rom Ver. 3.14.4052.2 (04666)WWE
Radio 2.15.50.14
Protocol Ver. 15.42.50.11U
PB81100 HX-BC
SPL-3.03.000 XE
MicroP(LED) 0x05
MicroP(Touch) 0x30
Ok question is ... is this phone recoverable and how?
Many thanks in advance.
moved to general section. Booting a SD built from WM + clrcad+ haret is an option for you? there is a few roms GB, ICS even JB roms there ...
phone into bootloader - connect usb - run hspl4 - choose 2.08.hspl - back into bootloader - flash magldr
Thanks for the advice but already tried this.
Get all the way to installing then sits for 30sec and get critical error
more info
What is happening ...
phone connects & operates fine in wm6.5
phone connects via usb no problems both sync & hard drive modes work.
start hspl or any other flash app & it works detecting phone & spk version on it
goes to bootloader fine.
bootloader goes into usb mode fine
THEN bootloader either
with hspl bootloader becomes unresponsive/frozen, error message:
Critical Error
Flow: 00000006
Error Code: 00000011
Description: Unknown
with Rom/Radio/MAGLDR flashing will make it to the progress bar screen the sit on 0% until update error
After this need to do a soft reset or remove battery to restart phone, it then boots up into wm6.5 working fine.
don't start with winmo running, , the usb connection times out while the phone is rebooting.
Put the phone manually into bootloader, - connect usb - wait for serial to become USB and THEN run hspl.exe
perplexing
ok just tried this same results
I don't know what to think anymore about this as everything works upto the point that it actually flashes the software.
Even when I move the img file to th sd card and try to install from there it gets to the white screen then says loading... and freezes without bringing up fash or quit options.
Surely since its still working theres a way to make it flash again?
things that come to mind...
the OS on your PC can sometimes cause problems, , especially (but not always) 64 bit windows. If theres another pc in the house, try it.
corrupt usb drivers, if you;ve had the usb cable in teh same usb port all along, change it for a new one, and use a back mounted port, not a usb slot in eth front of the case (assuming a pc not a laptop)
corrupted spl of some kind. worry about this possibility later.
-
For me, the next steps would be:-
try another pc
then
try an sd card flash of the (correct) stock rom
then
report back
Success now halfway ...
Thanks for the help, finally got hspl, magldr and custom wm6.5 rom. Problem was with laptop 64bit win7, pc 32bit with virus scanner obstructing.
But all fixed now.
Now just have to find an android rom I want, figure out cwm ext4 ??? out. Radio 2.15 is bad, Radio 2.12 good then Radio 2.15 good ??
Got some figuring out to do nand vs sd, partition formats etc heads spinning again.
At least the phone is flashable again
Desire DL installed
Thanks for all the help. Finally got there android now installed on hd2. Very impressed. Will make a good back up for my one x.