my problem is other way around!
My HTC Hero doesn't detect PC Connection when I connect it using USB cable. Doesnt matter whether I connect USB cable to charger or PC the charging LED turns on.
I had MoDaCo 2.7 rom previously and it was working perfectly, once I upgrade some apps using Android Market (using 3G) after that I connected hero to PC and nothing happen.
I upgrade the rom to MoDaCo 2.9 and new radio file, no success.
Wipe EXT and reinstall MoDaCo 2.9 and new radio file, no success.
I think it should be software problem not a hardware problem, since when I m in "fastboot (PWR + BACK)" when I connect USB cable it should USB in RED color in front of FASTBOOT.
please help! any idea? suggestion?
Did you mount the SD card to USB from the Hero?
My problem is that it doesnt show me any mount option at all!
it used to when connected shows some USB PC Connection icon in shade bar on top left of screen sp I scroll it down click on it and tap on mount button. but now nothing happen! shows nothing! it is like my Hero doesnt detect PC connection and just charges.
Any one has same problem with MoDaco Roms? is it because of Roms?
Today I booted into fastboot and when I ran "fastboot devices" command on my PC I can see name of my device on PC. also on Hero I can see a text in red "FASTBOOT USB" can I do something here to fix my problem?
I used GParted to merge Fat32 Ex3 and Swap partitions on SD card and make it as one Fat32 partition... reformat SD card... still when I connect Hero to PC this error pop up "USB Device not recognised!"
Downgrade my radio to 63.18.55.06EU_6.35.06.18
Downgrade the rom to MoDaco v2.5
USB Device Not recognized disappeared! and nothing happen...
no success!
Restore to Original backup using Nandroid Restore 2.2.
no success!
usb connect
Hi
for me with Rom modaco 2.9 usb detection ok i can mount sd but i have lost the HTC sync use. (All working with the last modaco rom).
so you used to have same problem? did u wipe data before rom upgrade? did u install new radio?
thus usb problem seems to be becoming a common virus for hero. previously we had 2-3 users with same prob. now another 1. man this is scarry. i imported my hero and dont have warranty. so anything happens to me hero i am ruined.
Yeah! it is a annoying problem... I found some other people in other forum they have same problem...currently no solution... I ll ship back my phone for warranty, maybe they change the motherboard for me. but I feel like it is not a hardware problem since in fastboot not only PC detect my hero but also I can run fastboot commands.
it is good to inform people who are going to buy hero from Ebay to be carful especially those in HK, this problem is popular among them. mine was shipped from there.
pi3ch said:
Yeah! it is a annoying problem... I found some other people in other forum they have same problem...currently no solution... I ll ship back my phone for warranty, maybe they change the motherboard for me. but I feel like it is not a hardware problem since in fastboot not only PC detect my hero but also I can run fastboot commands.
it is good to inform people who are going to buy hero from Ebay to be carful especially those in HK, this problem is popular among them. mine was shipped from there.
Click to expand...
Click to collapse
bro did u try flashing to all other firmwares available? a diff rom might solve the prob. just a thought.
The problem happen after I upgrade some application while I was using MoDaco 2.3 Rom. Then I flashed MoDaCo 2.9 Rom with new radio then I downgraded to MoDaco 2.5 (I read in other post that this version of rom can solve the problem) and then I restore my original back which contain original rom came from factory... all same result without any different. Now I m using modaco 2.9 with last radio I dont know any other rom that I can try...
pi3ch said:
The problem happen after I upgrade some application while I was using MoDaco 2.3 Rom. Then I flashed MoDaCo 2.9 Rom with new radio then I downgraded to MoDaco 2.5 (I read in other post that this version of rom can solve the problem) and then I restore my original back which contain original rom came from factory... all same result without any different. Now I m using modaco 2.9 with last radio I dont know any other rom that I can try...
Click to expand...
Click to collapse
bro cud u plz try modaco 2.8?
my wifi stops working with dhcp in modaco 2.7 and 2.9. modaco 2.6 and 2.8 gives me auto ip from dhcp. so i use modaco 2.8.
I flashed v2.8... same result still cannot detect pc connection! I m going to flash one of the original roms and ship it back...
still I feel like it is a software problem... some directories need to be flashed or reset... perhaps some directories not reset even you flash new rom... anyone has any idea about that?
Hi,
Any news about this lack of USB conexion ?
Same problem with my 32A Magic (Sapphire)
Fastboot USB is ok, but no USB on any ROM
mika91 said:
Hi,
Any news about this lack of USB conexion ?
Same problem with my 32A Magic (Sapphire)
Fastboot USB is ok, but no USB on any ROM
Click to expand...
Click to collapse
OH! this problem is spreading!
Can you please tell what happen to your Magic then you get this problem? since still there is not actual solution for that. you can try solution mentioned here: http://forum.xda-developers.com/showpost.php?p=4837803&postcount=18 if not just ship back your Magic for warrany: http://forum.xda-developers.com/showpost.php?p=4965845&postcount=39
I am having this too, and I'm on the original Orange ROM (after being on 2.2 a while back).
A presumed it was a windows 7 issue, since that is the only thing to have changed for me since I flashed last time.
I don't know what happens.
One day it was working, and the day after, not !!!
I'm using win xp3, but I tried to connect this week-end into win 7.
And the problem appeared during the week-end.
So this is maybe a way to investigate !
Related
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???
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.
Hey all,
Maybe someone can help me out.
Two weeks ago i installed andoid on my HTC HD2.
I used HPSL, radio 2.15.50.14, MAGLDR112 and NexusHD2-Gingerbread_V2.1_NAND. A few days ago, without any reason i got a white bootscreen and i still have it
What a did so far:
* New HSPL3, but the radio didn't connected anymore, error 270.
* A new MAGLDR, i reached 100% in a blink, but then an error 270.
* Using a SD with the original leoimg, i get a (00018003 radio fail) error after a few % and the update failed.
* task29, but again no connection. (after 5 min error 262)
* new USB drivers installed for windows 7 and i also tried it on an windows Xp computer.
So far i only reached my 4 colored screen with:
PB81100 HX-BC
SPL-2.08. HSPL 8G XE
0x05
CotullaHSPL 0x30
* The original rom was RUU_Leo_S_HTC_NLD_3.14.404.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship
Last question, how can i check that the batttery is stil oke for flashing.
Anyone who has a clue what to do?
Thanks in advance.
greetz!
Rob
Mate, I think you´ve done everything. HSPL and Radio ROM versions correct etc.
Since I see more and more people reporting similar problems like you, I get the feeling that some Android builds might have some strange effects on Radio ROMs.
There are too many people with SPL and Radio ROM problems, eg. stuck in bootloader or at the white startup screen.
This didn´t happen at this pace before Android NAND.
Only 1 question though:
Did you try to flash the original ROM using RUU.exe, SSPL or LeuCustomRUU via USB, without having the SIM and the SD card inserted? In rare cases, either one or both were trouble makers...
EDIT: Second question:
What kind of SD card did you try? Bigger cards seem more problematic, too.
I used a 2 gb micro SD card to go back to the original Rom.
I didn't tried to go back to original ROM using USB, because of the connecting problems. So that i'm gonna do now. Any suggestions which to use best?
After your post i tried to the flash with (and without) the formatted sd and the simcard, unfortunatelly i didn't work.
For last your question i can say that connect your phone to PC when it is off. Then keep down "volume down" button and switch on your phone. You get 4 colored screen. On bottom you can see USB word. Let phone for minimum 1h. And you get more 50% charged battery.
After hour you can flash back to original rom or to MAGLDR and forward normally flash android nand. You dont need disconnect or switch off before flash your phone.
Hope helps.
@tictac0566
Thanks for the options!
I tried the options mentioned in question 1, the problem is the connection USB/Radio. SSPL seems to work, but after 1% again connection error.
After a few test it must be the radio.
I tried to flash only a new radio using LEOIMG, after 99% i get the same error as LEOIMG an original Rom (00018003 radio fail)
With HPSL3_PKG i also can't go back to SPL 2.08.000.
So the problem must be there.
Anyone has an idea?? Can i use another radio? If yes, than which?
Thanks!
Still no solution
Tried many things, still the radio is not working.
It could be also HPSL3, because i can't go back to spl 2.08 (or any other (h)spl with the app.
Anyone has an idea??
Just trying to help here, but have you tried doing everything from the start?
task29 and everything else?
Hey i seem to have the same problem as you except my white screen wasnt after a flash, it just randomly went white one day and wouldnt boot.
I have tried MTTY, i can connect via usb but after formatting via MTTY and then attempting to flash a new rom (ship and custom) it just stays on 0% and doesnt do anything else.
Sorry to hijack thread just thought whilst people are looking they can help me too
CrAzYiaN said:
Just trying to help here, but have you tried doing everything from the start?
task29 and everything else?
Click to expand...
Click to collapse
Yes i did, this thread is official mine
It must be the radio or else HSPL3_PKG.
Do you have some options??
Thanks in advance!
tomar5e said:
Hey i seem to have the same problem as you except my white screen wasnt after a flash, it just randomly went white one day and wouldnt boot.
I have tried MTTY, i can connect via usb but after formatting via MTTY and then attempting to flash a new rom (ship and custom) it just stays on 0% and doesnt do anything else.
Sorry to hijack thread just thought whilst people are looking they can help me too
Click to expand...
Click to collapse
Can you go into bootloader? If you can then your problem can be solved. The problem you are having might have been because you unintentionaly installed or uninstalled a programm and that corrupted your rom.
To both of you. Try to flash using the leoimg.nbh step. If it doesn't work then the rom you used is not compactible with your device, try another till you find one that will work with your device. I know it is tiring to do something like that, here a tip from me, the rom you are expected to use in this process must be in the native language of your phone or else it will not work. You can't just use any stockrom to do it. I hope it helps.
Abdul9. said:
Can you go into bootloader? If you can then your problem can be solved. The problem you are having might have been because you unintentionaly installed or uninstalled a programm and that corrupted your rom.
To both of you. Try to flash using the leoimg.nbh step. If it doesn't work then the rom you used is not compactible with your device, try another till you find one that will work with your device. I know it is tiring to do something like that, here a tip from me, the rom you are expected to use in this process must be in the native language of your phone or else it will not work. You can't just use any stockrom to do it. I hope it helps.
Click to expand...
Click to collapse
Thanks for the advice, but all the roms i tried i got a radio fail during flashing with leoimg.nbbh.
Maybe your HSPL is faulty ? Did you try to re-HSPL your device using HSPL.exe ?
kawazaki said:
Maybe your HSPL is faulty ? Did you try to re-HSPL your device using HSPL.exe ?
Click to expand...
Click to collapse
Yes i tried, but mine HD2 stays on SPL-2.08 HPSL.
I used HSPL3_PKG and HSPL2 in different but still SPL-2.08 HSPL.
Maybe there's where my problems are, but i als can be an corrupt radio.
Anyone an other way to back to SPL 2.08.000 or how to fix the radio?
Then your best bet is to flash with a goldcard
Abdul9. said:
Can you go into bootloader? If you can then your problem can be solved. The problem you are having might have been because you unintentionaly installed or uninstalled a programm and that corrupted your rom.
To both of you. Try to flash using the leoimg.nbh step. If it doesn't work then the rom you used is not compactible with your device, try another till you find one that will work with your device. I know it is tiring to do something like that, here a tip from me, the rom you are expected to use in this process must be in the native language of your phone or else it will not work. You can't just use any stockrom to do it. I hope it helps.
Click to expand...
Click to collapse
Yes i can get into bootloader. I have tried using MTTY task 29 to format the device then i searched on the HTC site for a compatible ROM. Turns out the only one that doesnt give a negative response when i type in my serial number is the ROM from Taiwan. Tried flashing that using the SD card method and the USB method. Sd card method hangs at 0% and i get a connection error in USB method. I have also tried the latest ROM from Dutty.
If a ROM is not compatible how do you know? Does it hang at 0% or does it finish loading and then wont boot from there.
I have even tried flashing just a radio with the same results.
kawazaki said:
Maybe your HSPL is faulty ? Did you try to re-HSPL your device using HSPL.exe ?
Click to expand...
Click to collapse
Yes i tried all different types of HSPL and even SSPL. From the bootloader screen i run the .exe from the computer and it goes through and says 'operation finished successfully'
But when i get back to the bootloader it still says the same HSPL, which is 1.66
Also to note when i power on the device i can hear a small 'click' from it. Could be much worse and be a hardware problem?
Still no solution.
Oke guys, thanks for answering my threat so far!
Still trying to get my HTC back to life.
Is it possible that my problem is in HSPL? (see attachments)
After the white screen i tried to reinstall HPSL 2, 3 and 1, but during the instal my HTC reboot (without the signal "We Hacked It"
I also tried different SD card for LEOIMG, still radio fail 00018003.
One thing i didn't tried is using a goldcard, i downloaded the app but i need a working HTC HD2 to make the card.
Anyone?
No you don't, there you go :
http://forum.xda-developers.com/showthread.php?t=874304
Goldcard is the old method to install a custom rom way before HSPL became popular
so if HSPL don't work then Goldcard wont as well but hey you can still try
I think its more of a hardware problem now since all attempts for software repair is not successful. I had the same situation as yours, white screen then radio fail, tried all solutions but still no luck
sameeeeee
i have the same problem 100%
i already try all these solution and no one is worked
however, some one told me that maybe the problem with the Flash memory of my HD2 because he already try to solve / or already solve such problem "but unfortunately he lost the tools he was used"
this tools is can check the memory and told which memory chunk is corrupted
please if any one know this tools or had it please posted it on.....
That app should be Task 29.
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.
blocked hd2, here what happened, i had artemis v17 and wanted to go back to the official htc rom but flashing wasn't completely succesful, basically now i have in my hd2 some part of the official rom and some part of the artemis but it's not working at all, i can't succesfully flash no one of the two roms and no roms at all
active sync isn't working so i can only operate by sd card i tried and searched a lot but no solution yet...hope of a good advice....
solai said:
blocked hd2, here what happened, i had artemis v17 and wanted to go back to the official htc rom but flashing wasn't completely succesful, basically now i have in my hd2 some part of the official rom and some part of the artemis but it's not working at all, i can't succesfully flash no one of the two roms and no roms at all
active sync isn't working so i can only operate by sd card i tried and searched a lot but no solution yet...hope of a good advice....
Click to expand...
Click to collapse
Extract the rom to get the nbh file. Rename that nbh to LEOIMG.nbh. Copy it to your SDcard, and flash in bootload mode.
NOTE: You will have to reflash HSPL if you want to flash any custom rom at a later stage and this can only be done from computer!
yes i tried it but the flashing of the original htc stops because there is part of the artemis that prevents from flashing orginal roms in the phone
aaaaaaaaaahhhhhh i can t buy new phone how can i solve it i've been trying for days!!!!
and i can't connect the hd2 to the pc since there's no working rom in it.
solai said:
and i can't connect the hd2 to the pc since there's no working rom in it.
Click to expand...
Click to collapse
Get the hd2 toolkit.
shanman-2 said:
Get the hd2 toolkit.
Click to expand...
Click to collapse
but shanman tell me, with this kit do i need active sync working?
i have no working rom in my hd2 so i guess i somehow have to restore the hd2 to factory settings and factory rom without having to use activesync, or anyway flash any rom and then be able to flash win 6.5!
I REALLY DON'T WANT TO BURY MY HD2 IT'S STILL GREAAAAAAT, please i'm searching all over but cant find a solution so far
if you can enter bootloader you should be able to flash via USB if PC drivers are correct & no Hardware issue present on HD2.