Related
hi guys,
im attempting to update my hd2 but cannont. i sync it with active sync, start the update and it changes the phone to the tri color screen, but immediately disconnects on the computer, and a 1 minute later i get the error [260] connection screen.
can anyone assist me with updating? i also heard there is a way to update from the memory card...that might be the best way for me if someone can help me with that. THANKS
trexxcrap2 said:
hi guys,
im attempting to update my hd2 but cannont. i sync it with active sync, start the update and it changes the phone to the tri color screen, but immediately disconnects on the computer, and a 1 minute later i get the error [260] connection screen.
can anyone assist me with updating? i also heard there is a way to update from the memory card...that might be the best way for me if someone can help me with that. THANKS
Click to expand...
Click to collapse
What are you trying to update it to?
secano said:
What are you trying to update it to?
Click to expand...
Click to collapse
the new update that came out a few days ago....
trexxcrap2 said:
im attempting to update my hd2 but cannont. i sync it with active sync, start the update and it changes the phone to the tri color screen, but immediately disconnects on the computer, and a 1 minute later i get the error [260] connection screen.
Click to expand...
Click to collapse
Here is a link to the error codes. Your error means you need to go back to SSPL before you can flash that ROM.
trexxcrap2 said:
i also heard there is a way to update from the memory card...that might be the best way for me if someone can help me with that. THANKS
Click to expand...
Click to collapse
Here is a link to my tutorial on how to flash via SD card.
i am having the same issue each time i attempt to update my rom. error 260.
jenelson said:
i am having the same issue each time i attempt to update my rom. error 260.
Click to expand...
Click to collapse
You are still using the original SSPL (Soft Second Program Loader) which will only accept official update ROMs.
In order to flash the custom ROMs available here, you will need to flash in a HSPL (Hard Second Program Loader).
I don't know if you are totally new to flashing ROMs or not, since you didn't say and your post indicator said that was your first post here, but I would advise you to be very, very careful. In the early days (last month, actually) a TON of people were bricking their phones because they accidentally downloaded the European ROMs for the 512Leo. Ours is the 1024Leo and only ROMs designed for our phones will work.
The phone I am using is actually a replacement from TMO. I was having issues with the original device I purchased.
How do I use a HSPL or whatever... I am slightly confused but I can catch up quickly...
Thanks.
same thing happened to me, what i did was i restarted the update without disconnecting the phone from the computer, and it worked.
nyaznteen said:
same thing happened to me, what i did was i restarted the update without disconnecting the phone from the computer, and it worked.
Click to expand...
Click to collapse
I encountered the same problem and it appeared that my computer was slow in "re-recognizing" the phone. For some reason, it had to reinstall drivers before continuing with the update. After the device was again recognized, I restartde the update (without disconnecting the phone) and it continued without issue.
I had been worried that the phone had become a paperweight when I saw the tricolor screen, but everything has been fine and the upgrade appears to have worked correctly.
jenelson said:
The phone I am using is actually a replacement from TMO. I was having issues with the original device I purchased.
How do I use a HSPL or whatever... I am slightly confused but I can catch up quickly...
Thanks.
Click to expand...
Click to collapse
Think of HSPL as your BIOS (it isn't, but it may help you to think of it as such). You don't have any control over the options, but you need it to load or install your OS. Installing HSPL is simply a matter of following the directions in the link that I posted last time: http://forum.xda-developers.com/showthread.php?t=653614
Once you have HSPL installed, you should be able to "flash" any ROM. Of course, this also allows you to flash ROMs that are not meant for your phone, so that's the danger behind it.
When you visit a thread that offers a ROM, it should either have instructions or a link to instructions on how to install. If it does not, a google search for "xda how to install a custom rom" should give you a million helpful links. (This is actually beyond the scope of this post so I won't go into details)
Hope this helped some...
Same problem but i have hspl?
not sure what im doing wrong here I've installed hspl 1.42 which was enough trouble for what seemed like a pretty straight forward job. now whatever i try to install all i get is error 260? on top of this i don't seem to be able to send message tho i can receive and the camera on my phone no longer seems to work?
i am a newbie but Ive been reading and clicking and trying to install stuff for hours and hours and so far all Ive managed to do is install hspl and reduce my phones usability.
i got windows mobile device center 6.1 tried it with and without allow usb connections.
my antivirus and firewall is off.
.net framework 4 installed.
tried different usb ports
ive tried installing Duttys_Leo_Sense_2.5_5.23569.5.5.0_2.14_Holy_Grail_576MB_V4.3_WWE and a stock rom
my computer has vista 64 on it.
im hoping im just being a bit dense here please help me i just wanna join in on all this flashing fun!!
mumbles85 said:
not sure what im doing wrong here I've installed hspl 1.42 which was enough trouble for what seemed like a pretty straight forward job. now whatever i try to install all i get is error 260? on top of this i don't seem to be able to send message tho i can receive and the camera on my phone no longer seems to work?
i am a newbie but Ive been reading and clicking and trying to install stuff for hours and hours and so far all Ive managed to do is install hspl and reduce my phones usability.
i got windows mobile device center 6.1 tried it with and without allow usb connections.
my antivirus and firewall is off.
.net framework 4 installed.
tried different usb ports
ive tried installing Duttys_Leo_Sense_2.5_5.23569.5.5.0_2.14_Holy_Grail_576MB_V4.3_WWE and a stock rom
my computer has vista 64 on it.
im hoping im just being a bit dense here please help me i just wanna join in on all this flashing fun!!
Click to expand...
Click to collapse
just for kicks did you try a different ROM, find another ROM that is Compatible and try it, not saying there is anything wrong with Dutty's , but could just be the download , but not sure since you tried stock too ...
You may need to reinstall HSPL3, if you tried to flash a stock rom, and even if it failed it could have removed HSPL ...
Also try plugging the USB cable into the back of the machine
error 260 1024hd2
Hey guys,
I am having the same issue although I may know the answer but not sure how to fix it. Prior to flashing chuckyRom, I installed HSPL but I don't think I installed the correct version (still worked). So does anyone think this entire problem is attributed to initially installing the wrong hard SPL. If so, how can this be fixed? android is running great on chuckyRom but it would be nice to use a rom that is used for more than running android.
Please help, I have been in misery trying to solve this for over two weeks now.
Error 260, T-mobile HD2
Error 260 during ROM update
I had the same problem and tried everything (?)
Finally I got it work.
After I started the update the first time, I got the message, driver was not installed successfuly ...blabla
I ignored the message, tried and the connection disconnected every time again.
At the end I used another usb port and it asked me to download the CDMA driver. After download and installation, the update was in 5 min. done
Snarksneeze said:
You are still using the original SSPL (Soft Second Program Loader) which will only accept official update ROMs.
In order to flash the custom ROMs available here, you will need to flash in a HSPL (Hard Second Program Loader).
Click to expand...
Click to collapse
He was trying to install the OEM rom. I'm doing the same and have the same issues.
Error 260 on Htc Hd2 running windows mobile 7
I cannot get data on my hd2 when I installed win7 so I wanted to downgrade the os back to 6.5 but I get Error 260 when I connect to my phone to my cpu via usb. Is there a work around?
Dizzle88 said:
I cannot get data on my hd2 when I installed win7 so I wanted to downgrade the os back to 6.5 but I get Error 260 when I connect to my phone to my cpu via usb. Is there a work around?
Click to expand...
Click to collapse
Put the phone into BootLoader Mode then connect to the PC. Run the ROM.
Error 260 connection in HTC HD2
Dear all;
i have this problem in windows 7 each time i connect my phone with pc it gave me error 260 , so when i connect the usb cable i choose the first choice sync not the default one storage and it worked for me .
Ahmed Hosni
thanks for the note
fred_up said:
Put the phone into BootLoader Mode then connect to the PC. Run the ROM.
Click to expand...
Click to collapse
First time flashing the radio and kept getting error 260 from CustomRUU.
Read so many threads and all say sync the phone with your PC and run CustomRUU. Nobody said to run it under BootLoader Mode.
This simple note helped a lot for a newbie like me.... thanks
Error [260]
Hello
I want to try to update my HD2 from 2.2 to 2.3.x but I always geht thr Connection error.
I´ve flashed my HD2 from Windows Mobile 6 to Android.
I thank you for your help.
Hi!
So.. My HTC Hero GSM has some issues that need to be repaired. Touchscreen not working in the lower part of the screen, constant headset-icon, trackball not working good. So I've contacted my repair center and they told me to send it in. So I want to restore my phone to as close to original as possible to be on the safe side.
The problem is I can't use the official RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe(or any other version), without getting an error 155(apparently it has something to do with the rom not having correct filesize).
It doesn't matter what rom I'm currently using; Modaco, Villain, different kind of generics, but nothing affects the outcome.
I got a feeling it has to do with the recovery image I use(RA 1.6.2) or Hboot version(.0007), but I can't seem to flash a new one. Recovery flasher gives me "Backup FAILED: could not run command.", and since my HBOOT is .0007 I can't use remote command from fastboot to restore original.
1. Is it possible to downgrade HBoot from recovery mode? If so, does anyone have a update.zip I can use?
2. Could error 155 has something to do with the computer/OS im using?
3. Anyone has any other suggestions what I can try to restore?
Currently using:
HTC Hero GSM
Generic 2.73.405.38 (1.5)
Baseband 63.18.55.06OU_6.35.15.01
HBoot 1.76.0007
Any help is greatly appreciated!
/Jakob
Edit: Solved!
For anyone having issues with Error 155(CID-checks fail, perhaps?) or 171(USB fail) while trying to restore a rooted HTC Hero to stock with an official RUU-exe, this is what worked for me where nothing else did:
- Create Goldcard
- Extract ROM.ZIP from the Official RUU exe you want to use. I downloaded it from their main site
- Rename to HEROIMG.zip
- Boot to flashboot mode (Volume down + Power on)
- Flash.
- Reboot and enjoy your new stock HTC Hero.
1. Yes. There is an engineering hboot over at modaco (v2007).
2. No idea. You could just try re-downloading the RUU and doing an md5 check on it, might have been corrupted during download.
3. I forget what 3 was and I can't check cause I'm posting through tapatalk.
Hi!
Thanks for your fast reply.
I successfully flashed Hboot with 2007 and later with 0004, but it didn't make any difference when I tried to run the official RUU. I still get error 155 ("Unknown error").
I have since double, triple and quadruple-checked the download to make sure I've got the right RUU. And since I download it from HTCs official site, in the country where it is bought, it shouldn't be an issue. All the downloads I've made is also the same size..
I guess my last resort will be to try to flash the stock recovery image manually.
Anyone have that one lying around?
Du you have HTC Sync installed? Usb debugging on in the phone? Try flashing the RUU, when in fastboot. (VOLDOWN+ON)
I'm not sure what error 155 is.
HTC Sync installed, enabled on the phone. And the green little icon is green and the phone says connected. Usb debugging is enabled.
I will try starting in fastboot mode brb.
That didn't work either.
Still got error 155 Unknown error.
I also tried to restore my original recovery image in fastboot:
fastboot boot cm-hero-recovery.img
Click to expand...
Click to collapse
An this is what it said:
Downloading 'boot.img' ... FAILED (command write failed (Unknown Error)
Click to expand...
Click to collapse
The "unknown error" appears even here. Could it be that my phone is so broken it cant write to that area?
If you have access to recovery
Try;
HTC Generic 2.73.405.5 (update.zip)
http://www.romraid.com/paul/hero/update-hero-generic-2.73.405.5-signed.zip
if that fails try;
Goldcard Method
http://forum.xda-developers.com/showthread.php?t=572683&highlight=gold+card+method
if that fails try;
...... try the first 2 first then post back results. (Might be worth trying on another computer because unknown error 155 sounds like there could be an issue somewhere with the pc. Maybe build an XP vmware?
andrewb84uk said:
Try;
HTC Generic 2.73.405.5 (update.zip)
Click to expand...
Click to collapse
Already tried. Unfortunately didn't work.
andrewb84uk said:
if that fails try;
Goldcard Method
Click to expand...
Click to collapse
I did it, and now have a goldcard. Unfortunately I still get error 155. I also tried all this from a different computer than before. This time with win 7, but with no other result.
I guess next step will be to try it from XP. I will setup an virtual pc later and try it, but I have to admit I'm not hopefull... This is getting annoying.
Any other way you guys can think of? And I REALLY appreciate your help, this is driving me mad!
jakobahman said:
Already tried. Unfortunately didn't work.
I did it, and now have a goldcard. Unfortunately I still get error 155. I also tried all this from a different computer than before. This time with win 7, but with no other result.
I guess next step will be to try it from XP. I will setup an virtual pc later and try it, but I have to admit I'm not hopefull... This is getting annoying.
Any other way you guys can think of? And I REALLY appreciate your help, this is driving me mad!
Click to expand...
Click to collapse
Can you provide some screenshots, best thing you could do is do it from a fresh XP machine if you can.
Im setting up a new virtual xp just for this.
Ill be right back with some screens...
i usually do it thru the SD card
SiL3nTKiLL said:
i usually do it thru the SD card
Click to expand...
Click to collapse
I'm not sure what you mean. What do you do through the SDcard? And how?
jakobahman said:
I'm not sure what you mean. What do you do through the SDcard? And how?
Click to expand...
Click to collapse
HEROIMG via fastboot maybe?
But isn't that the same as using recovery mode to flash a rom?
As I stated previously I want to get my phone as close to stock as possible(ROM, Radio and recovery). Can this be done with HEROIMG? Am I missing something here?
jakobahman said:
But isn't that the same as using recovery mode to flash a rom?
As I stated previously I want to get my phone as close to stock as possible(ROM, Radio and recovery). Can this be done with HEROIMG? Am I missing something here?
Click to expand...
Click to collapse
I do believe... if you use the rom.zip taken from when you launch the RUU (remember to unhide hidden files) this also does radio hboot e.t.c. I did it with the tmobile rom and it did update radio. Rename it to HEROIMG.zip, put it on the root of the sdcard, boot into fastboot and it will find it and flash.
This is the contents of a rom.zip direct from an RUU i did tonight.
@android-info.txt
@boot.img
@hboot_7200A_1.76.0007_090804.nb0
@radio.img
@recovery.img
@splash1_Hero_TMO_G2_Touch.nb0
@system.img
@userdata.img
YES!!!
Finally!
Thank you Andrew and Silentkill!
For anyone having issues with Error 155(CID-checks fail, perhaps?) or 171(USB fail) while trying to restore a rooted HTC Hero to stock with an official RUU-exe, this is what worked for me where nothing else did:
- Create Goldcard
- Extract ROM.ZIP from the Official RUU exe you want to use. I downloaded it from their main site
- Rename to HEROIMG.zip
- Boot to flashboot mode (Volume down + Power on)
- Flash.
- Reboot and enjoy your new stock HTC Hero.
Thanks again for all the help!!
jakobahman said:
YES!!!
Finally!
Thank you Andrew and Silentkill!
For anyone having issues with Error 155(CID-checks fail, perhaps?) or 171(USB fail) while trying to restore a rooted HTC Hero to stock with an official RUU-exe, this is what worked for me where nothing else did:
- Create Goldcard
- Extract ROM.ZIP from the Official RUU exe you want to use. I downloaded it from their main site
- Rename to HEROIMG.zip
- Boot to flashboot mode (Volume down + Power on)
- Flash.
- Reboot and enjoy your new stock HTC Hero.
Thanks again for all the help!!
Click to expand...
Click to collapse
Well done... for a final outcome the error 155 means there is an issue with settings and if you get an error 155 more than likely a new windows setup will need to commence somewhere. (Install XP, Windows 7 et all. Error 171 is a usb driver issue to the phone I do believe.... glad to be of an assistance.
I don't think it has something to do with the OS. I tried the RUU .exe on three different setups; One laptop with Vista, one brand new laptop with Win7 home premium and one virtual PC with XP.
Maybe a "full" setup of XP would work, but I think it's more likely it is something else.
On the other hand, to just remove the OS from the equation solved it, so you might be right.
Oh, and the 171 error only occurred when the driver got messed up one time, so it really hasn't got much to do with my case. But this solution would work for people having that issue as well.
jakobahman said:
I don't think it has something to do with the OS. I tried the RUU .exe on three different setups; One laptop with Vista, one brand new laptop with Win7 home premium and one virtual PC with XP.
Maybe a "full" setup of XP would work, but I think it's more likely it is something else.
On the other hand, to just remove the OS from the equation solved it, so you might be right.
Oh, and the 171 error only occurred when the driver got messed up one time, so it really hasn't got much to do with my case. But this solution would work for people having that issue as well.
Click to expand...
Click to collapse
The errors are system related, thus when you use the HEROIMG.zip via fastboot you totally bypass the need for having a PC except to transfer files to the device. So I think it is a driver/OS issue.
EDIT: To the OP, edit your first post and add [SOLVED] to the front.... let users know there is a solution.
I hope you guys can help me, i have a G2 Touch and i'm about to try restore to stock by using SD-Card.
Problem is, when i unpack the RUU.exe (Firmware 2.73.111.26), there's no ROM.zip in it. Only thing i get is a Subfolder with several installation files and a data1.cab sized 104MB, which i can't open (nether with 7zip nor winrar)
Hi,
Posting a new thread since I could not find any thread that could address my issue. If there is one, pls point me to it.
I have a GSM Hero. I flashed Froydvillain 1.7.2 ROM on it. However, for some reasons, I want to go back to stock 2.1 HTC ROM.
After rooting the phone, I had created a backup with Nandroid. However, when I try to restore it using Nandroid, I get following msg -
.android_secure.img not found Skipping restore of applications on external storage', and then also something about skipping restore of /sd-ext
After this, it says restore complete.
When I reboot, I am stuck on the Airtel screen (HTC India). Can not go past it.
Can anybody tell a way to load stock 2.1 ROM?
Thanks in advance.
I'm not sure, but it could be a missing file leading to a corrupted backup. If that is the case you can either get a stock 2.1 rom in zip form
(like this one for exemple http://forum.xda-developers.com/showthread.php?t=714075) or you could un-root by running a RUU (rom update utility) and remove the patched recovery image, in effect restoring your phone to factory condition.
There's a decent guide on how to do that here.
Hi,
Thanks for reply.
I actually prefer theunloackr.com method of unrooting. However, the problem is that since I am having a Froydvillain ROM, I can't use HTC Sync with it. So, can not use the RUU.
I think first installing the zipped generic OTA you mentioned and then using theunlockr.com method will do the thing for me. Isn't it?
Are there any other zipped RUU?
Thanks again
Just boot your phone into bootloader, plug it into your computer, and make sure it is on hboot-mode (it shows HBOOT on the screen) then go into Device Manager on Windows and look for "Android USB Devices" - if the device under there is named "My HTC" then everything is fine and you can start the RUU.exe, but if it's not you will have to update the driver with the one installed with HTC Sync (probably located in C:\Program Files\HTC\HTC Driver\Driver Files\(Your OS here)\ ) then it should be named "My HTC" and you should be able to go on
Hey...
mljjlm said:
Just boot your phone into bootloader, plug it into your computer, and make sure it is on hboot-mode (it shows HBOOT on the screen) then go into Device Manager on Windows and look for "Android USB Devices" - if the device under there is named "My HTC" then everything is fine and you can start the RUU.exe, but if it's not you will have to update the driver with the one installed with HTC Sync (probably located in C:\Program Files\HTC\HTC Driver\Driver Files\(Your OS here)\ ) then it should be named "My HTC" and you should be able to go on
Click to expand...
Click to collapse
**
I hope you can imagine the feeling of relief...
The Android USB device listed is indeed 'My Hero' so I hope it is completely safe to go ahead with RUU....
I have downloaded India RUU from some site...however can you tell me where can find authentic RUU?
Thanks again...
There has to be a thread with all the roms for the hero... including the official ruu. Also, you could try the xda wiki.
Sent from my HTC Hero using XDA App
Is it Generic HTC or is it branded in any way? If it's branded you will find it at your carriers homepage (hopefully). If it's generic you will find it on htc.com
androguns said:
**
I hope you can imagine the feeling of relief...
The Android USB device listed is indeed 'My Hero' so I hope it is completely safe to go ahead with RUU....
I have downloaded India RUU from some site...however can you tell me where can find authentic RUU?
Thanks again...
Click to expand...
Click to collapse
I usually go here: http://shipped-roms.com/index.php?category=android&model=Hero
They are all authentic and if one isn't compatible with your phone it should just say so (though the latest one with asia in the name should probably work).
Thanks
Hello all,
The issue is solved now.
I am back to the stock ROM.
I found that the method suggested by mljjlm worked perfectly for me.
The issue I faced was: Going back to stock HTC Hero 2.1 ROM from a rooted, Froydvillain 1.7.2 ROM
1. I had already downloaded appropriate RUU from following link -
http://shipped-roms.com/index.php?category=android&model=Hero
2. I followed confirmatory steps suggested by mljjlm in the post above
3. Just plugged in Hero to PC via USB cable, and ran the RUU. This pdf from HTC website tells more about running RUU (for a different device, but same procedure) http://www.htc.com/uploadedFiles/Co.../Touch_Detailed_RUU_Instructions_07152008.pdf
That's it.
Thanks all for help.
Hello, I just decided to finally root my Legend and install a rom.
My phone is currently running 2.1 and i'm on the Virgin Mobile Canada network here in Canada. We don't have an official 2.2 release yet.
I have made a gold card and i'm all ready to root and load a rom. I just don't know what one to do.
I think i'd like to start off fairly basic. just to play with 2.2 then try some of the more advanced custom roms. So, All i really need is help finding the 2.2 stock rom that would be best suited for me?
Sorry if this is sort of a newb thing. but i'm a newb. I tried looking this up, but couldn't get a solid answer via google results. Too many options out there and i didn't know if they applied to my situation.
So, yeah. Just want the basic 2.2 Then maybe i'll try some custom roms later.
Also, if anybody has any advice of what to expect or any other advice, i'd appreciate it. Any features I will loose if i root/rom? I hear FM radio won't work, but i'm not too worried about that. Anything else?
Thank you.
You say "basic ROM", but it's a bit more complicated.
You can simply update your phone to HTC stock ROM 2.2 or the Vodafone ROM 2.2, this would be basic but crappy (slow, branded, buggy roms).
I recommend you to skip these roms and try BlaY0's rom (with sense) or CyanongenMod 6.1 stable. These two are really good work !
So you can play with serious froyo and the time you'll take to root and change the rom would be useful !
Cyanogen will be a bit more "exotic" since HTC sense is not included in the ROM.
For the features, you will not loose any of them, except maybe the FM radio (depends of the rom), but you will get many you have not right now (root of course, overclock,..., plus every changes of 2.2)
Your Legend is about to become a greeaaaaat phone, congratz !
I hope my answer will help you ;-)
PS : Few months and we'll get stable gingerbread roms ! Time to get to Froyo ! ^^
Thanks for the reply. It was very informative and just the type of information i need.
I hate these situations where i know i'm missing a lot of knowlege, but due to not knowing it, i don't know how to aquire it. I hate that.
That's why i'm glad i have this place. Thanks. I think i'll install that CyanongenMod 6.1 stable. I've been using launchers most of the time since i got my phone as i didn't really enjoy sense that much.
Could somebody please link me to the exact file i'd want? I keep finding different versions/builds and they say for different phones, and i just get confused A download link would be great.
Search for rom manager in the market, install and choose Flash Clockwordmod Recovery
After that:
In Paid version just select Download Rom / CyogenMod.
Select Backup current rom & wipe data and cache when installing
In free version 1st d/l CM6.1 from http: // forum.cyanogenmod.com /files/category/29-htc-legend/ and put it on your sdcard, then Select Install Rom from SDcard in Rom manager.
For both also install the google apps (same source locations & method)
gl
So, Upon trying to root my phone i find out i first need to downgrade my phone.
I go through all the steps needed and eventually get to the part where i need to install the new "RUU_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_7.05.35.26L_release_126592_signed" file.
I set up my phone. Goldcard, the correct version of HTC sync, USB Debugging, i'm fairly certain i did everything correct. I try to run the RUU and i get errors. Either USB not Connected errors, or and more frequently "Device ID Incorrect" errors.
So, I seem to be unable to downgrade to 1.31. Any advice on how to get by these errors? It's really frustrating.
Thanks.
Try recreating the goldcard and reinstall the latest HTC sync.
I tried re-making the gold card. I have the same problems. Although, I did realize i made a mistake when i made the gold card. But remedying that didn't seem to fix the problem.
When the Serial was reversed it already had the first two digits as zero's so i didn't really have to do that.
As for HTC Sync, I installed the correct version. I could try doing it again.
I'm on Win7 64 bit. I also tried it on a WinXP machine. Same error(s).
I'll try making the gold card again. I'm using a Kingston 2GB microSD card.
I had issues with Win7 x64 too. Your best bet is to find a 32-bit machine for this one-time step, or use VMWare Player to make a temporary virtual machine.
Sent from my Legend using XDA App
I've also tried it on a 32bit winxp machine.
Here is basically how it goes.
Enable Debugging mode.
Hook up via "Charge only"
Run RUU as Administrator
It runs and says "waiting for bootloader" but errors out with the Error 171 USB Connection error.
The phone stays on the black screen that says HTC. Have to take out the battery to reset it.
OR. run the RUU again.
If i do that.
it "clears user data"
then does "sending..."
then "Updating Signature". It gets about 20% done, then errors out.
Error 130 Model ID Error.
Then when i select exit. The phone reboots back to the homescreen.
Which, if i try again, starts the cycle again.
so, it goes. First try, USB error, black htc screen. second try. Model ID error, Re-boot. Repeat.
My sync is the correct version. i've re-installed my HTC drivers. I've tried on a winxp box. and my win7 box. I've re-created my gold card. I even temporarily disabled my firewall and anti-virus in case that was the conflict.
I've done everything. This is really pissing me off at this point.
rooting
FourForty said:
I've also tried it on a 32bit winxp machine.
so, it goes. First try, USB error, black htc screen. second try. Model ID error, Re-boot. Repeat.
My sync is the correct version. i've re-installed my HTC drivers. I've tried on a winxp box. and my win7 box. I've re-created my gold card. I even temporarily disabled my firewall and anti-virus in case that was the conflict.
I've done everything. This is really pissing me off at this point.
Click to expand...
Click to collapse
i had same problem but i solved it by doing this look at my guide
http://forum.xda-developers.com/showthread.php?t=954450
report if it works in that thread if it dosnt post back here and well help, (remember some one will read this thread when they are stuck one day)
Thanks. I posted on that guide with an update to my situation. Sort of stuck at the moment as the custom boot loader after step 2 failed to load and aborted the installation. so now i'm sort of screwed until i figure that out.
Hi all,
Yesterday I tried to root my legend to flash a custom rom (CyanogenMod 7).
Everything worked fine until I decided I also wanted to flash an unsigned Data2Ext zip.
So I first Wiped everything, then flashed CM7 ( successful ) and then tried to flash Data2Ext.
This didn't work (I think the error was something like "no signature").
After that I quit the recovery mode and my legend was stuck in a boot loop. Also, when connecting my legend to the pc and trying to get into recovery mode, my Legend was recognized as being "Qualcomm CDMA Technologies MSM". Windows tries to install drivers but unsuccesful, so I can't get into recovery mode anymore.
The only solution I found to get out of the boot loop was to unroot my Legend again. (Using this guide )
However, I still can't get into recovery mode for the same reason (and thus can't root my Legend anymore).
Also, when connecting my legend with the pc when already booted (I'm back to htc sense android 2.1), it doesn't let me get a good usb connection. My phone is charging, but windows says "One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it".
I think these problems might be related, but the first problem is my main concern, as I want to flash a custom rom again.
I've used many search terms, but could not find an answer that would solve my problems. Does anyone know how to solve this?
Note: I don't have root access anymore and am running Windows XP.
Also, the rest of my phone's functions is working correctly it seems.
Hi!
First I would try to install some FOTA, since you obviously can't install anything else... you might look to Shipped ROMs...
(don't install Froyo if you can, you'd probably end up with HBOOT 1.01 which is not that easily rooted, but still can be done...)
As those are most probably properly signed, you should be able to flash them from SD card, so no USB connection needed...(choose LEGEIMG starting archives, .exe needs USB) - the filename to flash from SD must be legeimg.zip
That should fix your USB connection issues I hope...
Then I'd try to re-root (See stickies in Development)
I tried flashing a FOTA (LEGEIMG_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_7
.05.35.26L_release_126592_signed.zip) but I think that's the one I already flashed using this topic. It reads the legeimg.zip but doesn't give me the option to update, so I guess they're the same?
For some reason I now also get the "Qualcomm CDMA Technologies MSM" notification when trying to connect as USB Disk station to the computer, so not the "One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it" error.
Edit: Now I get the malfunction error again..
Could the solution to my problem be to find the drivers for the Qualcomm thing? And if so, where can I find those?
Edit2: New development;
Legend now freezes completely when connecting to USB. I have to take out the battery to get it working again..
Edit3:
I've taken another look at the hboot screen and it gives me the following info:
LEGEND PVT SHIP S-ON
HBOOT-1.01.0000 <-- isn't that strange, since I'm running 1.31?
MICROP-0816
TOUCH PANEL-SYN07-0103
RADIO-7.05.35.26L
Nov 8 2010,15:24:15
Also, when I try to flash the 2.03 zip from here, it finds the legeimg.zip and asks me if I want to update. When I do so, it tells me "CID incorrect! Update Fail!"
Oh maan, I guess HBOOT-1.01 and 1.31 is not working out then...And since there's no way to downgrade HBOOT, you have to flash Froyo ROM...but to do that you need a goldcard: Here is a HowTo
Then you can flash a ROM with different CID then your own...
note: 2.03 is not Froyo, and since shipped-roms only has RUU, you might look into this: HowTo Extract RUU
And then you just ROOT again
Could the solution to my problem be to find the drivers for the Qualcomm thing? And if so, where can I find those?
Click to expand...
Click to collapse
try using attached driver by replacing the current one on your xp box. had the same problem before. HTH
aw, man! you missed your chance on s-off. anyway, since you're on hboot 1.00+ already (& from the looks of it, you lost your root), Dr Romca's link for rooting should work
Dr.Romca said:
Oh maan, I guess HBOOT-1.01 and 1.31 is not working out then...And since there's no way to downgrade HBOOT, you have to flash Froyo ROM...but to do that you need a goldcard: Here is a HowTo
Then you can flash a ROM with different CID then your own...
note: 2.03 is not Froyo, and since shipped-roms only has RUU, you might look into this: HowTo Extract RUU
And then you just ROOT again
Click to expand...
Click to collapse
Thanks for the help!
However, yesterday I couldn't make a new goldcard, since my device wasn't recognized. I will try to make one again this afternoon, using a W7 machine.
I will let you know the results!
maxq1 said:
try using attached driver by replacing the current one on your xp box. had the same problem before. HTH
aw, man! you missed your chance on s-off. anyway, since you're on hboot 1.00+ already (& from the looks of it, you lost your root), Dr Romca's link for rooting should work
Click to expand...
Click to collapse
Thanks! I will try this as well!
Edit:
Still no luck trying to create a goldcard, since the pc doesn't recognize my device, regardless what type of connection (charge-only, htc sync etc) I select. In windows 7 I also get the device malfunctioned error.
Trying to use the adb command only returns "No Device found" (or sth like that).
Using the driver Maxq1 gave me doesn't seem to work (unless I'm doing it wrong that is)
edit: usb bug fixed
Azaruc said:
edit: usb bug fixed
Click to expand...
Click to collapse
You mean you've rooted your Legend?
I am experiencing the exact same problem as you've described while trying desperately to root my HTC Legend.
I start up Fastboot, run Step1, then go into Bootloader (and also getting the same error message about the .zip file), then Recovery mode, and my computer (W7) recognizes the device at this point as Qualcomm CDMA Technologies MSM, and fails to install the drivers.
When trying to run step2, I get an error message telling me "device not found".
I am also running 1.31 and Hboot 1.01.0000
Would really appreciate some help
I didn't really document my steps (I should have ), but I think the Qualcomm bug was fixed by following this guide.
Let me know if it works out for you.