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.
Related
I haven't done this before so I want to make it right for the first time.
My friends XDAIIi can not make calls (flight mode on all the time and can not be turned off) after WM6 rom upgrade (which I think was for Himalaya only) by some cell phone shop.
Now how do I upgrade the rom to a working one or at least put back the original rom?
What file/s do I need to download? I don't have a cradle just a USB for connecting to ActiveSync which I think serves the same thing as the cradle. Do I need to reflash it first? How do I do that? What files do I need?
Thanks in advance.
Help!
Anyone?
Okay after about an hour or so searching I found this rom -> http://www.maxishare.net/en/file/37...-1-04-bluetooth-patched-camera-fixed-rar.html but after completing the first stage (I guess because for a moment there a quick glimpse of Stage 2 dialog box) I will get this error
Error 113: Extended ROM Update Error
And I repeated the process aboput 10 times with no luck.
Anyone care to point me to another rom that I can try?
zxt said:
Okay after about an hour or so searching I found this rom -> http://www.maxishare.net/en/file/37...-1-04-bluetooth-patched-camera-fixed-rar.html but after completing the first stage (I guess because for a moment there a quick glimpse of Stage 2 dialog box) I will get this error
Error 113: Extended ROM Update Error
And I repeated the process aboput 10 times with no luck.
Anyone care to point me to another rom that I can try?
Click to expand...
Click to collapse
right i usualy flame ppl for this, but as it was not you or your m8s fault:
1- got here http://forum.xda-developers.com/showthread.php?t=306600 and download the firmware
2 - make sure the phone is Fully charged
3 - put the phone in its cradle on a PC that running xp home or pro ONLY it will not work on vista. helps if you have activesync (u can get it from M$) then follow the instructions with the firmware. the program u want is called maupgrade.
4 - it will almost definatly fail the first time you run the updater (if its inactive for more than 15 mins, nothing changing on the updater screen as it should say its updating somink or other), DO NOT PANIC!! close the updater and run it again it will say no firmware found or anything it will work perfectly this time.. total time for update is 30~ mins.
BANG u have a working phone again hopfully!
"1- got here http://forum.xda-developers.com/showthread.php?t=306600 and download the firmware" -> This has exactly the same firmware/file/rom as this right -> http://www.maxishare.net/en/file/37...-1-04-bluetooth-patched-camera-fixed-rar.html right?
Anyways I am still downloading it tho it has the same file name I downloaded 3 days ago. Just like what I've said I already tried it (maupgrade) and followed the instructions and I think I only finished the first stage then it gave me the Error 113: Extended Rom update error
How bout an original ROM? Maybe somebody can give me the link because most of the links I found for original rom's are dead already.
Thanks.
you ARE runing a pc that uses the windows XP operating system?
skeeve666 said:
you ARE runing a pc that uses the windows XP operating system?
Click to expand...
Click to collapse
Yes I am using XP. Anyones know where I can find original rom? Maybe I can try that.
BTW, just for the sake of seeing the whole process of rom flashing, I did upgrade my Himalaya (XDAII) last week to WM6 using rom for XDAII of course and it was successful. Now I only did that to see how it works but I'm sticking to WM6 for my XDAII but I still don't know what to do with my friends XDAIIi and revert it to working rom.
I was trying to upgrade my SX66 from the factory Windows2003 to WM6 with this HELMI_BA_WM6_R0_ installer. I started the install and it crapped out giving me an error saying that it could not communicate with my device and that I needed to plug my device back in and retry it. My SX66 is now stuck on the bootloader as I'm sure the ROM isn't complete, and the installer does nothing now. Can someone please help this noob out? I'd really like to have my phone back lol.
N1cholas said:
I was trying to upgrade my SX66 from the factory Windows2003 to WM6 with this HELMI_BA_WM6_R0_ installer. I started the install and it crapped out giving me an error saying that it could not communicate with my device and that I needed to plug my device back in and retry it. My SX66 is now stuck on the bootloader as I'm sure the ROM isn't complete, and the installer does nothing now. Can someone please help this noob out? I'd really like to have my phone back lol.
Click to expand...
Click to collapse
Did you unlock the device first?
In any case, just try to reflash your device back to WM2003 with a stock rom. It does seem to be a bad flash. Also, which OS are you using (XP or Vista)?
Follow this in order to perform the upgrade properly...
Good luck!
egzthunder1 said:
Did you unlock the device first?
In any case, just try to reflash your device back to WM2003 with a stock rom. It does seem to be a bad flash. Also, which OS are you using (XP or Vista)?
Follow this in order to perform the upgrade properly...
Good luck!
Click to expand...
Click to collapse
I'm running windows version 7. and no i didn't unlock the device. i just ran the installer application (i hadn't found a detailed install manual) i'm not entirely sure how i can re-flash now, because i can't get a usb connection made because it's stuck in the bootloader.
N1cholas said:
I'm running windows version 7. i'm not entirely sure i can re-flash now, because i can't get a usb connection made because it's stuck in the bootloader.
Click to expand...
Click to collapse
By bootloader, do you mean the three colored screen?
egzthunder1 said:
By bootloader, do you mean the three colored screen?
Click to expand...
Click to collapse
no, the screen that says serial/usb at top and 2.07 at bottom
I just wanted to make sure that we were on the same page
In my opinion (and this is just a theory), Windows 7 (since it is a beta) does not have the necessary drivers to recognize the "usb device". Hence, when you put it in the cradle, it just doesn't see it. Again, this is just a theory...
You may want to get a hold of a machine with XP (that is if you didn't make the one you are using a dual boot). You should be OK if you try to flash via XP.
If everything else fails, you can always use mtty and flash via SD card (the procedure can be found in the wiki).
I had the device synced up before the install. it's just having issues syncing while it's in the bootloader mode. The device actually appears in the usb devices, but doesn't sync. i was thinking that the device might have to be authenticated with local software(on the sx66) in order to sync. I'm using the windows vista drivers. I do have this machine dual boot, but it's not any other version of windows i'm using
Your device does not have to sync in order to up/downgrade. Think about it this way... the RUU will put the device in bootloader anyways.
Just run the installer of the stock rom (the upgrade from Cingular).
@N1cholas: Please correct me if I'm wrong. I'm just a little confused. Are you expecting MS Active Sync to show as it usually does when you are syncing your phone? If that is the case, it won't happen when on boot loader. Are you getting any error when trying to flash or you haven't tried to flash yet?
Advise:
1. Keep your hopes, don't get despert. Egzthunter is a master
2. Make sure you follow the guide... Step by Step to upgrade.
3. If it'll take you too long to complete the reading and flashing, reset your phone and put it to charge. You won't be able to flash with a dead backup battery. Main and Backup battery won't charge while on bootloader.
Edit: @Egzthunder: Sorry mate, while I was thinking, drinking coffee and writing you had already replied Like I said, your the help master. Once again, I encourage the MODS to propose you to be part of their teem. You're always there to help.
Mark
i'm going to head off to school, but it's not working. when i try to run any mods i get an error saying that it cannot communicate with device.
Yeah! Egz for MODS!!! Woohooo and Xplode too and someday..me! LOL (no i mean it!)
windows 7 uses the same drivers as vista
beakybal4 said:
windows 7 uses the same drivers as vista
Click to expand...
Click to collapse
Why do you think I don't trust it?
@N1cholas,
I apologize since I ended up going to bed yesterday night.
I think your best bet will be to find yourself a PC running XP and try the reflash in that since it seems to me that something is going on with the OS.
@red and mark
Thanks for the support, guys!!! But you guys are awesome as well!
yeah, it's weird, it's just not working anymore. It appears in the device list and everything, but in WMDC it doesn't show up, and the rom install wizzards can't communicate with it either. I have been unable to find the upgrade ROM from cingular as it seems that the siemens' page has been removed. Also, I have a 2gb SD drive, but haven't been able to find information about flashing the SX66 from the SD.
N1cholas said:
yeah, it's weird, it's just not working anymore. It appears in the device list and everything, but in WMDC it doesn't show up, and the rom install wizzards can't communicate with it either. I have been unable to find the upgrade ROM from cingular as it seems that the siemens' page has been removed. Also, I have a 2gb SD drive, but haven't been able to find information about flashing the SX66 from the SD.
Click to expand...
Click to collapse
You will not see the device in any type of sync software (call it ActiveSync, WMDC, etc). I hvae uploaded the SX66 stock installer from Cingular, so give that a shot
Here you go
SX66Update.exe
Like I said... XP computer. Also, for the SD flashing, you need to look for something called mtty and instructions on how to use it.
the proper solution
1.MTTY method for unblocking bootloader mode
2.Upgrade the same way as in Vista to stock rom
3.Sim Unock, Repartition DOC
4.Upgrade vista way to any rom you like
there are guides in WIKI about this
egzthunder1 which version extrom version and radio are in this rom - the one you sharing? As you know i make public BA shipped rom collection, and any rom which is not there is welcomed
xplode said:
the proper solution
1.MTTY method for unblocking bootloader mode
2.Upgrade the same way as in Vista to stock rom
3.Sim Unock, Repartition DOC
4.Upgrade vista way to any rom you like
there are guides in WIKI about this
egzthunder1 which version extrom version and radio are in this rom - the one you sharing? As you know i make public BA shipped rom collection, and any rom which is not there is welcomed
Click to expand...
Click to collapse
Hey xplode,
To be perfectly honest, I haven't flashed 2003 since 2006, so I would be lying if I told you. Feel free to add it to your database if you wish. FYI, this is the upgrade that Cingular Wireless used to offer when the SX66 was still available in the at&t website.
MTTY doesn't have a USB option, it's only giving me COM1, COM2, COM3...
N1cholas said:
MTTY doesn't have a USB option, it's only giving me COM1, COM2, COM3...
Click to expand...
Click to collapse
Did you try the update that I gave you?
i ran it, and it said it was trying to get the settings from the device, then it just disappeared lol. now when i run it, it extracts the install data to the temp folder on my pc, then just disappears
Hi all,
This is my first post in this forum. Just got my HD2 yesterday & immediately set about installing a new ROM. I installed HSPL without any issues, but I'm having problems installing a new ROM. I've downloaded a couple in .exe format, synced up the phone to WMDC in Win 7, then when I start the exe file everythings fine until it starts to install, then the 4 colurs come on to the phone, and then the USB connection drops so WMDC isn't connected, then I get the error 266 (or 226). I used to have a touch diamond that did this, but I can't remember how you get the connection to remain whilst uploading the new ROM. I've had a look through the forum, but can't find the answer. Can anyone give me some ideas?? Does the phone need to have certain settings applied to it before flashing?? I'm not exactly a noob to flashing ROM's, but can't work this one out!! Thanks all.
just extract the exe, rename *.nbh to LEOIMG.nbh, put in ur microSD root, enter bootloader, press power button when u asked to do so. soft-reset when complete. feel free to pm me n i will guide u.
SD card method is the quickest way to brick your phone...
I use W7 64bit with WMDC and have never had an issue. Custom ROMs comes as an NBH file and tend to have CustomRRU.exe with them to run them. Run the EXE as an admin and you shouldn't have any issues.
Obviously check that when in the bootloader it does say SPL is 1.42.HSPL
When I flash a ROM, it turns the phone off (Windows knows that as it makes a sound) and then when the bootloader comes back up it says USB, Windows makes a sound for plug in and it starts.
EddyOS said:
SD card method is the quickest way to brick your phone...
I use W7 64bit with WMDC and have never had an issue. Custom ROMs comes as an NBH file and tend to have CustomRRU.exe with them to run them. Run the EXE as an admin and you shouldn't have any issues.
Obviously check that when in the bootloader it does say SPL is 1.42.HSPL
When I flash a ROM, it turns the phone off (Windows knows that as it makes a sound) and then when the bootloader comes back up it says USB, Windows makes a sound for plug in and it starts.
Click to expand...
Click to collapse
Hi, I'm using the same OS. I've tried running as admin but it still drops connection. The SPL is 1.42.HSPL. It just starts the update, then I see the phone disappear from the connected devices, then WMDC shuts down & a few seconds later the error message comes up??
you started flashing this fast only after one day of use
You don't need WMDC open - just close it once it says you're connected
The run the file and it should work.
As mentioned, why are you flashing it out the box? It's always best to get to know the device as it might just work as it is...perhaps try a stock ROM if you're not already using the newest one and go from there
EddyOS said:
SD card method is the quickest way to brick your phone...
Click to expand...
Click to collapse
I agree. not that there is anything technically unsafe about it, but unless you are fully aware what you are doing it's so easy to flash the wrong thing.
example,you flash a 1.66 stock rom from sd card but don't like it.you goo to change it but get a fail. why? because flashing stock from sd card also overwrites the spl.
no problem you say, I'll reinstall hspl.... only you can't because hspl needs spl 1.4 to instal and your 1.66 flash installed spl 1.6
worse still you instal one of the test roms from t mo us that are 2.0x which can't be downgraded even by gold card and you are stuck with spl2 until the geniuses that are the hspl team release hspl2.
just a thought...are you running as administrator? right click, run as administrator
samsamuel said:
I agree. not that there is anything technically unsafe about it, but unless you are fully aware what you are doing it's so easy to flash the wrong thing.
example,you flash a 1.66 stock rom from sd card but don't like it.you goo to change it but get a fail. why? because flashing stock from sd card also overwrites the spl.
no problem you say, I'll reinstall hspl.... only you can't because hspl needs spl 1.4 to instal and your 1.66 flash installed spl 1.6
worse still you instal one of the test roms from t mo us that are 2.0x which can't be downgraded even by gold card and you are stuck with spl2 until the geniuses that are the hspl team release hspl2.
just a thought...are you running as administrator? right click, run as administrator
Click to expand...
Click to collapse
Didn't know that, glad I have HSPL on my phone now!! lol
lots don't and that's what makes sd flashing dodgy. in the case of 1.6 it can be downgraded with a 1.4 spl stock rom.its just a pain. but 2.0 spl can't. check out the horror stories in my sig.
Yeah read about them, I nearly bricked my phone using the SD card method the first time I flashed but luckily the WMDC flash with my stock ROM got me back to normal!
I was trying to flash the stock 1.66 ROM, but it still disconnected. I have 1.43.206.4 WWE at the moment. The reason for flashing straight away, is usually the stock ROM updates are to improve / fix previous issues. This is why I wanted to start with a stock ROM & maybe move onto a cooked ROM at a later date. Does it make any difference when starting from an .exe file instead of RUU? Do you have to change something on the phone itself to allow it to stay connected?? cheers everyone for your comments.
run the exe as administrator, the phone should restart into boot loader (three colored stripes) and then flash.
samsamuel said:
run the exe as administrator, the phone should restart into boot loader (three colored stripes) and then flash.
Click to expand...
Click to collapse
Just tried it again & still no joy. It starts, the phones switches off, thats when it loses connection, then the bootloader appears, then about 10 secounds later it says error 266 connection lost. Still stumped???
Sounds like the device isn't reconnecting with the PC once in the bootloader - try another one...
with the phone in boot loader unplug the usb and plug back into a different port. preferably a port directly on the motherboard (round the back) not through a usb hub or slot in the case.
Sussed it now. I'm a mac user using Win7 using VMware fusion. I think it was this that was causing it to not detect the phone once it had started flashing the ROM. I tried it on my work laptop running XP & voila, it flashed immediately. Thanks everyone for your comments - no doubt I'll be posting a few more questions soon!!!
ah good stuff.
todays lesson ? put all the system info in the first post!
clemo71 said:
Sussed it now. I'm a mac user using Win7 using VMware fusion.
Click to expand...
Click to collapse
Ahhh... yes, that's the kind of non-standard setup that would make sense mentioning right away indeed. Everything that touches hardware level is rarely friendly to emulation, virtual machines, resource sharing and so on...
1st lesson - use a PC!!! POW!! lol
Ok.....next question. I've tried to flash a rom using the customruu file, but all it does is open up the contents of that file. I'm using XP Pro. Any ideas why anyone???
Ok, so I went to flash a new ROM on my phone, and when I go to the run the RUU, I get the screen with the 4 steps to complete, which are already completed, then hit next. Now I get "Error [240] : File Open" and below that it says "The Update Utility cannot open the requested file. Please check the update utility."
I tried downloading the Update Utility again, but it still does the same thing. Ive flashed my phone before, and Im pretty sure Im not doin anything different this time, but its not workin. Am I missing somethin?
Thanks
new-b said:
Ok, so I went to flash a new ROM on my phone, and when I go to the run the RUU, I get the screen with the 4 steps to complete, which are already completed, then hit next. Now I get "Error [240] : File Open" and below that it says "The Update Utility cannot open the requested file. Please check the update utility."
I tried downloading the Update Utility again, but it still does the same thing. Ive flashed my phone before, and Im pretty sure Im not doin anything different this time, but its not workin. Am I missing somethin?
Thanks
Click to expand...
Click to collapse
Check if your harddrive isn't full.
A RUU extract some files, and if your harddrive is full it can't
Nope, its not full. Far from it actually lol.
new-b said:
Nope, its not full. Far from it actually lol.
Click to expand...
Click to collapse
flashing trough sd-card?
im having the same problem i get the error code as well, is it possble to flash from the microsd. I am a nooby at this and understand how to flash.
xmoo said:
flashing trough sd-card?
Click to expand...
Click to collapse
Nope, win mo device center.
WeaponX2010 said:
im having the same problem i get the error code as well, is it possble to flash from the microsd. I am a nooby at this and understand how to flash.
Click to expand...
Click to collapse
Its in the tutorial, but I havent tried it yet. Ive never had a problem flashing through the USB before.
Tried it from the SD card. Went great. Just takes a little longer.
Still open to suggestions about usin active sync though.
xmoo said:
Check if your harddrive isn't full.
A RUU extract some files, and if your harddrive is full it can't
Click to expand...
Click to collapse
Hi xmoo. Can YOU please help? With this:
leo70 said:
URGENT MAJOR HELP REQUIRED *PLEASE*:
I am stuck on DFT boot screen (after doing 1234-vol up_down-wp7-reset) and this is *after* (wp7 here !) all the chains b4 that are done: ie: power on, hspl, htc, magldr- for windows phone 7 on hd2. Sometimes get thru to windows phone 7. but generally reboots. Done spl back to stock and leoimg on sd back to stock and tried task28s, 29s, etc but just reboots constantly and randomly.
Any thoughts here? What is warranty process? DO they replace at all with NEW? or new BOARDS/RAM? Gone back to 1.66 spl and sent in for repairs. because - the stupid recommended Romupdateutility HTC stock rom 'upgrade' did this damage. yes, was Windows Phone 7 and activated using dev hack with marketplace & xbox/live. Also - although I activate ok and can use it on market fine once it boots good - still when both my hd7 (hd2) and Mozart are signed into XboxLive using same address at same time: (mozart is legit fully/eula-signed etc) then the hd2 seems to reset a LOT here at this point. maybe this has something to do with usual xbox-live security? ie: http://www.wpcentral.com/hack-xbox-live-windows-phone-7-get-perma-banned-microsoft ?????????? please hlp me - I am fully capable of mtty, sd-leoimg, whatever it takes- but need to know why this would be the case? same with Android roms/stock too. Anyone know about task2a on hd2? how many bad blocks I should have? partition/re-partition droid or wp7 to avoid these bad blocks? I just WISH Cotulla/DFT let you run the windows phone 7 installer in such a way that all bad bloks could be excluded totally as if the never exist... ie make hd2 clean.
Click to expand...
Click to collapse
note: although I have gone bak to original spl+rom in past I have (both unsuccs &succesfully) have previously done task2a and even spl-mfg install and radios/roms as DEBUG/SPL-MFG. xmoo?
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.