So....i had read the thread and installed HSPL on my phone before i attempted to used a cooked rom, having tried to install my first one i find now i have the 'white triangle of death with upside down exclamation mark'.
I am on T-Mobile in the UK and i do not want to brick this beyond all repair..what is the procedure i should do now to get it working..i beleive i need to format a SD card to fat32 but which rom do i put on it and then what is the button press sequence..i have no connection via active sync anymore.
phone off - hold "volume down" - tap power whilst still holding volume down - phone will boot to bootloader (three stripes)
what does it say next to spl?
if
1.42.0000 then hspl isn't installed. what rom did you flash and how?
if says 1.42.HSPL then hspl is installed, plug in usb, wait for "serial" to become "usb" and flash your rom again from usb.
Thanks...
1.42.HSPL is what it says, it also says lower down 'upgrade ROM code error please try again' which i did do several times through the .exe on the rom i tried to upgrade to which i believe was TOUCH_X_TREME_21895_1_2_36_47, im not to sure whether the rom is compatible for me or even what i done wrong, i was relying on the fact that i had installed HSPL prior to trying to flash the new rom, i can confirm that the phone changes to 'usb' when i plug it in on the tri colour screen...so when you say try to flash the rom again what exact method do i use..when i tried the first time i just run the .exe file in the rom folder and followed the prompts
EDIT: having just followed what you said...i run the rom .exe file and followed through recovery and it says error 'error 302 update error'...what if the rom i am flashing is NOT compatible.
Why don't you first try to flash back a stock rom that you can download from http://www.4shared.com/dir/22189940/b8552fa0/Shipped_Leo_ROMs.html ?
Choose preferably a 1.48 rom.
Anyway, you'd better read the "flashing for noobs" thread in ROM dev forum before you go and do something even worse. You're probably trying to flash a corrupt file or something alike.
get the T-Mobile ROM from HTCs website, boot into the bootloader and connect and flash the stock ROM...that should at least get you working again
yea as above.sounds like a bad download or something. try a different rom or re download.
be aware the rom you are flashing needs a certain radio, so when it does flash it still won't boot till you flash the correct radio.(it's all in thefirst posts of the rom thread)
you have hspl installed so as long as you only flash by usb you are safe. just boot to bootloader, run the instal from the pc, phone will flash
EddyOS said:
get the T-Mobile ROM from HTCs website, boot into the bootloader and connect and flash the stock ROM...that should at least get you working again
Click to expand...
Click to collapse
Have done this..still not flashing, keeps giving update error, as i said..i have no active sync connection and it states that is needed ?...so how do i flash the rom ? also when you asked me to go to the tri colour screen and read off the HSPL part, on the green section it says 'upgrade ROM code error please try again'..is this normal in this state
Why am i getting this error when i try to flash it via usb...comuter still recognises phone but active sync does not connect to it so i am assuming this is causing the error ?
So when you go into the bootloader and plug in the USB does it say USB on the phone screen? If so, you also need to run the updater as an administrator. If this doesn't work, try another PC. If that doesn't work then you may very well have bricked it.
Also, are you using ActiveSync or WMDC?
EddyOS said:
So when you go into the bootloader and plug in the USB does it say USB on the phone screen? If so, you also need to run the updater as an administrator. If this doesn't work, try another PC. If that doesn't work then you may very well have bricked it.
Also, are you using ActiveSync or WMDC?
Click to expand...
Click to collapse
Yes it changes to USB when i plug it in, i am using WMDC but when i plug the phone in it does not connect anymore, i have tried running as admin but it makes no difference, i keep getting error 302.
Correct me if i am wrong, i thought the idea of installing HSPL would keep me safe from bricking the phone, i think all i initially done was flash an incorrect rom, ill try it on my laptop but that has not been in contact with the phone yet
What OS is on your laptop? if it's Windows 7 just plug in your phone and it will automatically WMDC so you don't need to install it first
Laptop done the trick !..seems to be doing the job now...dont know what the hell thats all about...
Would be helpful if knew what radio i had on it...and do i install rom first, then install radio ?
ActiveSync or WDMC wont recognise the device as the phone has not fully booted up.
With the phone in boot-loader mode and connected by USB, then run the ROM installation program. Ignore the fact that it says you must be ActiveSynced. Just tick the box and go into the next page.
As been said already, make sure you install the correct RADIO rom for the customised ROM. Once that is done, then you can install the ROM.
The best ROMs to download are ZIP'd or RAR'd ones, as they have a check that they have not been corrupted when uploaded or downloaded.
Well this is highly weird !!...i restored the Tmo dump from htc website but i now have the rom on there that i was trying to install previously before i bricked it...Touch X treme
What radio are you trying to flash? Read this and use this to flash the phone with the radio needed for your ROM choice:
http://forum.xda-developers.com/showthread.php?t=644781
Once done, try flashing the phone again (I'd make sure HSPL is on the phone too)
fred_up said:
ActiveSync or WDMC wont recognise the device as the phone has not fully booted up.
With the phone in boot-loader mode and connected by USB, then run the ROM installation program. Ignore the fact that it says you must be ActiveSynced. Just tick the box and go into the next page.
As been said already, make sure you install the correct RADIO rom for the customised ROM. Once that is done, then you can install the ROM.
The best ROMs to download are ZIP'd or RAR'd ones, as they have a check that they have not been corrupted when uploaded or downloaded.
Click to expand...
Click to collapse
So find out what radio i need before flashing, what if the radio i need to flash is not for the currant rom i am using...and am i right to say that some of these roms i cant use as they are not for the UK ?
All radios can be used, you can get them on their own and use with that link I posted before. going by the Touch X thread it says you need a 2.07 or 2.08 radio so get one of them and flash that first before flashing the ROM
I understand that better now...still not sure what went wrong there, from the laptop i thought and still do that i was flashing the stock rom for tmo from the htc website to restore the phone...but when it started up i was shocked to see the splash screen for the Xtreme rom..maybe i flashed that ?? if so why did it work this time..bad flash before ? and i have certainly not installed a radio myself...well thaks for your help anyway..the phone is up and running again and i will make sure HSPL is still there before i try my next rom
Likely bad flash - glad you're sortred now though. I always do the task29 with the radio nI want to use before flashing a ROM now to make sure the memory is clear...
Related
Hi there,
Hope you can help me...
Since i bought my Cruise, I flashed it to the newest ROM version of HTC and it automatically installed SPL 3.13 with.
The problem is that if I want to install the WM 6.5 rom, I have to "Downgrade" My SPL version from 3.13.0000 to 2.20.
I followed the steps explained by "Olipro", but when the upgrade starts, RUU kills activesync (seems to be normal) and when the phone normally reboots in bootloader mode (like when you flash a new rom), nothing happens. The phone didn't shutdown and tries to establish a new USB connection !
I tried to turn manually the phone in bootloader mode on to force the SPL update, but the % bar stays at 0 and RUU returns a communication error (262).
I tried also to install the wm 6.5 rom without install SPL 2.2, but it crashes (stays @ 0% too)
I don't know how to install this stinky version of HARD SPL.
Heeeellllpppp !!
NOTE : I tried with or without µSd, does the same thing.
Thx
hmm try disabling firewall and antivirus one of them may be blocking the connection. Thats my only thought about it.
Thank you for the answer but it don't work...
Nobody can help me ?
Try to extract the files from the newest htc rom to a new folder, and then copy the "RUU_Signed.nbh" from the SPL V2 folder to the extracted files (to the new folder) and run the "ROMUpdateUtility.exe" from the extracted files (from the new folder).
nope ...
Please, consider my asks...
I know there is necessarily a solution but I have not yet found.
I don't know where/why it is crashing.
What does the HTC need to downgrade the hardspl ?
Is there a protection that can't be bypassed with the 3.13 ?
The only thing that I can do atm, is flashing the official HTC rom (useless ^^).
The actual version of my rom is :
_HTC Touch Cruise_RUU_Polaris_HTC_FRA_3.13.406.0_radio_sign_25.85.30.07_1.59.42.15_Ship
Thanking you in advance...
Pixel69 said:
Please, consider my asks...
I know there is necessarily a solution but I have not yet found.
I don't know where/why it is crashing.
What does the HTC need to downgrade the hardspl ?
Is there a protection that can't be bypassed with the 3.13 ?
The only thing that I can do atm, is flashing the official HTC rom (useless ^^).
The actual version of my rom is :
_HTC Touch Cruise_RUU_Polaris_HTC_FRA_3.13.406.0_radio_sign_25.85.30.07_1.59.42.15_Ship
Thanking you in advance...
Click to expand...
Click to collapse
HSPL 3.13? In this ROM is ver. 3.13 drivers, not HSPL... If you have original ROM and you dont install Olipros HPSL, you have original HTC SPL...
When I enter bootloader mode, the HSPL version is : 3.13.0000
Of course it's the original htc HSPL.
The problem is that I can't downgrade it to the olipro's version : 2.20.
Did you try it on other PC?
2 PCs, 2 USB cables..
The official rom upgrade works fine, I dont think that the problem comes from the computer.
definite guide:
1. establish a connection with activesync via usb (orbit2 to pc)
2. start the romupdateutility provided in hardspl folder.
3. before it starts flashing, you need to also follow on-screen instructions on orbit2!!! execute jump-spl and stuff: click yes on orbit2!!
4. when the orbit2 states: Replug USB. you need to plug the usb-cable once off and then put it back to connect to your pc.
5. it starts flashing and restarts after its done.
Hi Manaaa,
I don't know what is jumpslp ??
I found it on the web (xda..), copied it in my "my documents" folder, ran it but it asks me a jump address (default is 0x00000000) and an spl (*nb) file..
What is jump spl ? What is the address to jump to? and where can I find the *nb file ?
In the olipro's hspl folder is only a *nbh file.
Thank you
I wouldn't recommend using a jump spl for our phones if there isn't one in the Hardspl Pack then one is not needed to be run.
Personally im still really confused by this so if i get it straight.
You are synced with activesync.
Run the file for Hardspl Run RomUpdateUtility.exe
Then go though. It switches off activesync.
Then what?? Exactly Does it ask you to replug the cable? Do you get the rom flash screen (with %) at all??
Also i dont think that spl flashes can be run from the booloader as it has to be a modded bootloader (jumpspl if you will), loaded by the program to be able to flash the new hardspl.
Also i know very little on this, this is as much as i understand it to be.
chris10230 said:
You are synced with activesync. OK
Run the file for Hardspl Run RomUpdateUtility.exe OK
Then go though. It switches off activesync. OK
Then what?? Exactly Does it ask you to replug the cable? NO
Do you get the rom flash screen (with %) at all?? NO
Click to expand...
Click to collapse
Normally, after killing activesync, the phone turns into bootloader mode. Mine stays in winCE and tries to establish new usb connection...
I also decided to force manually bootloader mode and killing activesync by myself.
I ran RUU again, it first checked the phone state (such as battery >50%, connectivity...)
CHECK : OK
Next step, by clicking "NEXT" on the RUU interface, the phone turns in "% mode" and the update starts but stays at 0%.
After a while, RUU returns an update error (such as 262).
Noway to flash hardSPL :'-( , v3.13 seems to be "write protected".
ERROR [262] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process. If this happens, you can just soft reset the device and run RUU again. The update process will then continue. At this stage the rom on the device is incomplete and it will not boot back up into Windows. You will need to place it into the bootloader to continue.
Click to expand...
Click to collapse
That is what error 262 is but really dont see why this happens either. And since you can boot into windows its not much help.
So it just wont go to flash it when you click it through, hmm
Your last resort would be to PM cmonex as she will have helped make this with oilpro. Ask and see if she can shed some light on this one. Maybe something has gone wrong somewhere (quite likely) that we don't know how to fix.
Stupid question but have you tried downloading, unzipping it again? May have been a bad dl... or unzip
Have tested it with about 10# DLs...
I PM'd Olipro, waiting for a response now
Flash back to HardSPL and don't Re-Plug
Hi Pixel,
Herewith are guide for you
1) Flash back to HardSPL and don't re-plug until end of session (5 minutes)
2) Flash back to original SPL 3.13 on this post . This original SPL for HTC Touch Cruise only
3) After you do this you cannot flash with other Cooked ROM or Shipped ROM
with different ID, unless you flash back to HardSPL
Good Luck my friend
I have exactely in the same configuration as Pixel69 with the same result.
I've tried to an other PC without any change.
Has somebody any idea?
Just had an idea what OS are you running to do it?
If its not 7 may not be fully compatible... Shot in the dark really
Hi there
I got an HD2 from a friend (he bought off ebay) and seems to just boot to the Tmobile sticking together logo and won't boot.
I don't think it charges as well...
there was no lines (radio?) at the bottom of the Sticking Together pink square screen...
is this phone bricked? or can I still flash a rom?
Ok try this, turn the phone off then hold the low volume botton n the power botton at the same time, n if it takes u to the bootloader then u r good, just search on how to install a rom of ur choise, good luck
Sent from my HTC HD2 using XDA Premium App
froibet said:
Hi there
I got an HD2 from a friend (he bought off ebay) and seems to just boot to the Tmobile sticking together logo and won't boot.
I don't think it charges as well...
there was no lines (radio?) at the bottom of the Sticking Together pink square screen...
is this phone bricked? or can I still flash a rom?
Click to expand...
Click to collapse
Well the fact that it will even turn on means it is not bricked. A bricked HD2 will not even turn on the most it will do is flash tihe led light and vibrait a couple of times.
Follow the instructions of the above post and pull up bootloader, if bootloader comes up you can save the HD2. Depending on if you want to flash a official srock ROM or a custom ROM to the HD2 will dictate your next step.
If you want a official stock ROM then just download and flash the official update from T-Mobile.com just type in HTC HD2 update in the search box on the home page and you will find it. You will have to enter the IMEI number to download it wich you can find this number behind the battery. To flash it connect the HD2 to a computer via USB cable while in bootloader and wait for the serial in the white bar at the bottom of the bootloader screen to change to USB and the computer to show it recognizes the HD2 then run the update utility and follow all the on screen instructions.
If you want to flash a custom ROM as in custom Windows Mobile, NAND Andriod ROM, or Windows Phone 7 ROM then you will have to flash HSPL to the HD2. Download HSPL4 and flash 2.08 HSPL if hou want to flash a NAND Andriod ROM as MAGLDR only supports 2.08 HSPL. Or a Windows Phone 7 Rom, or flash 3.03 if you just want to flash a custom Windows Mobile ROM.
Now if you want a NAND Andriod ROM or Windows Phone 7 you will have to download MAGLDR and flash it to the HD2.
If you want a custom Windows Mobile ROM download the ROM of your choice and fladh it using the .exe or RUU wich ever one the ROM has. Note do all flashing of what I have previously mentioned via the method I mentioned before.
If you are wanting to flash a NAND Andriod ROM or Windows Phone 7 ROM then download the ROM of your coice and flash it using MAGLDR and the instructions of the ROM developer in thread for the ROM.
Now this is very important. I see from the picture you have a T-Mobile(TMOUS) HD2 so no matter what you do, do not flash a ROM with a radio version that reads like these 2.04.50.xx, 2.05.50.xx, or any radio that is x.xx.51.xx they will brick/kill a TMOUS HD2.
froibet said:
Hi there
I got an HD2 from a friend (he bought off ebay) and seems to just boot to the Tmobile sticking together logo and won't boot.
I don't think it charges as well...
there was no lines (radio?) at the bottom of the Sticking Together pink square screen...
is this phone bricked? or can I still flash a rom?
Click to expand...
Click to collapse
I would recommend flashing a stock T-Mobile ROM, since that appears to be the flavor of the phone. This will install the correct radio. Once the phone is working, continue as per normal for flashing the ROM. You will have to reinstall hardspl.
thanks for the info guys! i really appreciate the support!
it seems like it won't read the USB... is the port busted?
froibet said:
thanks for the info guys! i really appreciate the support!
it seems like it won't read the USB... is the port busted?
Click to expand...
Click to collapse
try this:
1) download your stock ROM.
2) put it on your SD card via a card reader, you want an .NBH file.
3) rename the file LEOIMG.NBH
4) make sure the phone is off, make sure your SD card is back in your phone.
5) hold down and power
6) it should go to a tri-color screen and say something about flashing the image, hit power to confirm
7) it should flash no problems.
MAKE SURE YOU DOWNLOAD THE CORRECT ROM FOR A TMOBILE US HD2
Have exactly the same problem with my friends phone.
Its a TMOUS and sticks on the same boot screen.
He screwed it up when trying to install Android NAND on it.
I can enter bootloader And I have managed to get rid of MAGLDR and CWM.
I have HSPL 3.03 installed on it, but when I try to install the latest ROM from TMOUS it fails at 8% and tells me that
'ERROR 290: INVALID COMMAND
This update Utility cannot be used for your PDA phone. Please check your update utility'
Tried copying the relevant file to the SD card and renaming it leoimg.nbh but the install fails HERE aswell with the error:
"RADIO_V2 - RSA Fail"
I managed to install an energyrom onto it, but it wouldnt go past the initial boot screen
Any help appreciated
Boradan said:
Have exactly the same problem with my friends phone.
Its a TMOUS and sticks on the same boot screen.
He screwed it up when trying to install Android NAND on it.
I can enter bootloader And I have managed to get rid of MAGLDR and CWM.
I have HSPL 3.03 installed on it, but when I try to install the latest ROM from TMOUS it fails at 8% and tells me that
'ERROR 290: INVALID COMMAND
This update Utility cannot be used for your PDA phone. Please check your update utility'
Tried copying the relevant file to the SD card and renaming it leoimg.nbh but the install fails HERE aswell with the error:
"RADIO_V2 - RSA Fail"
I managed to install an energyrom onto it, but it wouldnt go past the initial boot screen
Any help appreciated
Click to expand...
Click to collapse
Try running a Task 29 on your friends HD2. This willtotally clean out the NAND memory of the HD2 and reformat it, kinda sounds like that is what is needed to be done. He may have messed the NAND memory format up when he was trying to install the Andriod. You will have to reflash a Windows Mobile ROM after you run the Task 29 as it will not ha e a ROM on the phone then. You will not have to reflash HSPL cause it will not remove it.
It seems that the problem is RADIO related. I can task 29, and I can install The latest Energyrom, but I CANT install a radio.
There is no radio ON the phone at the minute it seems. When I try to do a radio install, it asks me if I want to go from version ' ' to the update I am using.
None of the installers see a radio on the phone, and trying to install the radio always fails at 96%. This would seem to be the same if I try to install the official TMOUS latest ROM with radio from SD Card. It fails at the radio install part.......
Maybe time for a new thread for this one.......
orangekid said:
try this:
1) download your stock ROM.
2) put it on your SD card via a card reader, you want an .NBH file.
3) rename the file LEOIMG.NBH
4) make sure the phone is off, make sure your SD card is back in your phone.
5) hold down and power
6) it should go to a tri-color screen and say something about flashing the image, hit power to confirm
7) it should flash no problems.
MAKE SURE YOU DOWNLOAD THE CORRECT ROM FOR A TMOBILE US HD2
Click to expand...
Click to collapse
i can do all this without connecting to the PC? just flashes from the SD card???
froibet said:
i can do all this without connecting to the PC? just flashes from the SD card???
Click to expand...
Click to collapse
Yes you can flash radio and ROM from your SD card. Here is a link to the thread on doing this gives step by step, check it out.
Everytime I turn on my phone, it goes straight into bootloader mode. I don't know what to do. I've been trying to google for the past hour or so, and no luck. Can anybody help?
Could be that your vol down button is stuck, try pressing and releasing quickly a few times ...just a thought!
PS. Your phone is not bricked if you can get to boot loader!!!
i tried that, and it didnt work. any other ideas?
can anyone please help?
Maby you don't have an OS. So try to flash a stock rom.
Sorry for bad english.
i tried that, but it either loses connection or it will say something about, how the the version of the o.s doesnt work for my phone. also on the phone itself, when it tries to download the rom, where a htc image is normally there, it isnt.
i have no idea what to do
It would be helpful to understand what you were running on your phone before the problem occurred?
The Bootloader you are seeing - I assume it is the hacked Cotulla one?
If you connect your phone to a PC does the bootloader screen show "USB" rather than serial?
If you have Cotulla bootloader and USB connection to PC, I'd start again with a clean install....not sure what you were using...but Typhoon is nice and Stable
http://forum.xda-developers.com/showthread.php?t=933951
It has a "clean installation" guide that you can follow....
http://flashmirrors.com/files/ytjzury5kvx9p91/Clean Installation.pdf
HTH.
K
I was trying to reinstall a stock gingerbread o.s on the phone, but something happened, and it wouldn't allow me to. So i just wanted to reinstall stock tmobile rom, and install android after that.
Yes i have cotulla bootloader, and whenever the phone starts up, it says serial, but it ill change to usb when i plug it in.
i couldnt open the pdf file.
mh48 said:
i couldnt open the pdf file.
Click to expand...
Click to collapse
If you are getting errors while flashing the stock ROM, as in windows mobile, then 99% of the time you have bad NAND memory and the phone needs to be jtaged or the motherboard needs to be replaced. Ive experienced a lot of these similiar threads over on PPCGeeks with the HTC Touch Pro 2
whenever the image file tries to update through bootloader i get an error/update image fail due to the radio i think. it says its spl 2.08 hspl, i tried uninstalling hspl but that didnt work. what could be the problem? or am i pretty much out of luck?
mh48 said:
i couldnt open the pdf file.
Click to expand...
Click to collapse
Those mirrors do seem broken.
Well this thread gives step by step instructions.
http://forum.xda-developers.com/showthread.php?p=11097380
you have HSPL, so you need to task29, MAGLDR, CWM and then a ROM.....it'll be interesting to see if you get anywhere....
Suggest following it step by step and seeing what happens before we write off your phone!
im not able to install magldr or a new rom, it either loses connection, or says it isnt compatible
mh48 said:
im not able to install magldr or a new rom, it either loses connection, or says it isnt compatible
Click to expand...
Click to collapse
Well if you have Cotulla HSPL, and USB shown on that screen, and are connected to your PC and Task29 is not running then I'm afraid I'm out of knowledge....
Sorry.
so i found that i have a ruunbh error, what do i have to do in order to fix this?
with ruunbh I suggest you go back and flash a stock WM rom.
That has worked for some.
If that gets you back running (at winmo 6.5) then you need to start the Android process again....
......By starting with HSPL and moving on through task29, radio, magldr, clockworkmod and a android rom.
going back to winmo is described here:
http://forum.xda-developers.com/showthread.php?t=935145&highlight=stock+rom
Let's see if you can go back to winmo first!
it keeps giving me an update error, when i try to install a custom wm rom and official rom any other suggestions?
So of the steps below....where and what is the update error?
--------------------------
If you are using a 512MB ROM HD2, just download the official firmware from HTC's website. The recommendation is to use a 1.xx or 2.xx ROM, do not use a 3.xx ROM.
Download 7-zip, make sure it is 9.20 version and up.
Using 7-zip, open the official ROM update exe file. Do not execute it.
Inside you will see RUU_signed.nbh, extract just that file. Nothing else.
rename RUU_signed.nbh, to LEOIMG.nbh
Copy LEOIMG.nbh into your SD card root directory which is FAT16 or FAT32 formatted.
Unplug the battery from the HD2, count to 10, replace the battery.
Hold the VOLUME DOWN button, DO NOT LET GO.
Press the POWER BUTTON, then let go.
Follow the instructions on the screen when the device goes to RECOVERY mode.
im using tmobile u.s version
You really like being brief don't you.
Dear Dev's / members
I have problem with this HD2 and cannot find a solution yet!
first thing first. is this a Tmobile of Eu mobile?
i tried flashing factory RUU but after 1% it gives an error saying Radio failed.
tried flash quite a few radio's but still after 100% it says radio fail.
tried flashing from USB cable
tried flashing from SD with leoimg.nbh
no luck.
the guy was using android on it until yesterday. may be he tried to flash a wrong Rom which brick the phone. now only white screen appears.
i can go to bootloader mode but no luck in flashing any thing at all.
Looks like EU model as no logo near earpiece.
if also has white markings on call & end key that would help confirm EU.
If trying to install .nbh file from SD it will overwrite HSPL so check current SPL status in bootloader.
If still on HSPL 2.08 try flashing an NRG WM6.5 ROM & see what happens (they have no radio so if completes then try radio flash if needed, try via USB them SD if USB fails.
Do you get an error code when it fails via RUU ?
thanks for helping mr. B
the error i get is (270) and yes it have white markings on all the buttons. so its confirm EU model. by NRG rom you mean Energy Roms? i tried earlier the energy Rom but no luck. after 1% it gives error.
cannot try mtty method as i'm on windows 7 and in windows 7, it's not showing the USB port. it's radio is corrupted. i think someone must have flashed a wrong Rom.
What standard ROM have you got ? if it a 3.14 rom try connecting HD2 via USB & use HSPL4 toolkit to install HSPL 3.03 & if that installs then try the 3.14 ROM via USB & RUU.
Also eliminate simple issues such as lead & USB port by switching port & using a different USB lead.
Windows 7 64bit ? worth trying another PC & 32bit if can as WMDC drivers on 64bit can be a pain for flashing ...
windows 7 32bit. tried flashing hspl 4 and it says complete but in bootloader it shows 2.08 only. i guess gold card method will solve the problem but it's too complicated. any other suggestions?
i would search for task29 and format the phone back to virgin default then download a windows rom from htc via the downloads page on there website for the phone ,then if it works re task29 it then put android on it with the htc hd2 tool kit witch has every thing other than rom (all u need to do is task29 it then go back to the boot loader and run the ruu rom)
samuel79 said:
i would search for task29 and format the phone back to virgin default then download a windows rom from htc via the downloads page on there website for the phone ,then if it works re task29 it then put android on it with the htc hd2 tool kit witch has every thing other than rom (all u need to do is task29 it then go back to the boot loader and run the ruu rom)
Click to expand...
Click to collapse
No do not run a Task 29 the device. I say this for two reasons, one if you flash the Stock Windows Mobile ROM via RUU the RUU will run a Task 28 before installing the ROM witch is pretty much the same as a Task 29. The second reason is that if you run a Task 29 it will remove the current ROM on the device so it will not have a working ROM anymore. If after the Task 29 you can not get another ROM installed on it the you will not be able to use the device at all anymore.
why not he thinks its bricked so there is no difference if he cant get a rom on it
samuel79 said:
why not he thinks its bricked so there is no difference if he cant get a rom on it
Click to expand...
Click to collapse
No the device is not bricked, a bricked device will not even turn on at all, no vibrations no nothing.
At jacktackle, try to find the earliest stock Rom RUU for your HD2 and try to flash it. It is possible you have what is reffered to as a stuck radio.The only fixI have seen for this is to flash a older ROM version with a older SPL version. If the earliest ROM version does not work start working your way up one version at a time and you might get lucky and get one that will flash.
thanks for all the help guys. but nothing worked. tried flashed old ruu's but reboots at 1% this radio is screwed up. hspl 2.08 is not upgrading nor downgrading. sd card update not working. i guess thats it. will give it back to him so that he can showcase it
first time ever i'm un successful. bad luck! may this LEO rest in peace. 'amen'
jacktackle said:
thanks for all the help guys. but nothing worked. tried flashed old ruu's but reboots at 1% this radio is screwed up. hspl 2.08 is not upgrading nor downgrading. sd card update not working. i guess thats it. will give it back to him so that he can showcase it
first time ever i'm un successful. bad luck! may this LEO rest in peace. 'amen'
Click to expand...
Click to collapse
Before you give it back you can find some of the old test ROMs for the EU or for the TMOUS depending on which version of the HD2 it is. Just make sure if it is a TMOUS that you do not flash a rom version that has a 51 radio with it. Just look at the RUU name and the radio version is in the name. If that does not work then the only fix will be to replace the mainboard cause JTAG would not fix the problem.
Hey there Community,
I really don't know much about mobiles, especially the HTC HD2 and flashing ROMs,
but somehow I got Android to work on my HTC HD2 1 year back and now wanted to sell my phone because I got a new one.
Therefore I needed to set up the factory settings and get Windows Mobile 6.5 back on my phone..
Unfortunately I failed hard while following the instructions of a tutorial that said I only needed to rename ruunbh to leoimg and put it on my SD-card and so on.
Halfway the update was interrupted and since then Iam getting "00028002 Not allow" error and can only boot to the bootloader saying "Upgrade ROM code error Please try again" And the usual things in the red disctrict and at the bottom it says that I got an USB-connection which seems to be wrong, because I can't see the device and so on.
I tried to install HSPL4 but it failed due to no USB-connection.
So what can I now do to make it work again? Iam really frustrated
Flashing image from sd is all good if it original correct country/vendor rom, if not you get your problem & things can be tricky as HSPL was replaced with standard SPL so care must be taken.
Either find a correct Vendor/country (CID) ROM for your HD2 or get it in bootloader & able to flash HSPL.
Would of thought for resale a good Android build would be more desirable.
I know what you mean, but the problem is that I just don't know what to do..
My phone is not branded or anything, so I couldn just go to htc.com and get me the newest winmo Rom?
The Problem is, what to do then, exactly?
It seems that I can't flash anything because I dont got usbconnection..
So no idea to original ROM country vendor !
usb connection may be due to driver issue on PC, install Activesync if on XP or WMDC 6.1 for Vista & Windows 7 then retry connecting hd2 via usb .
*Also make sure you know your version of HD2 & be aware of .51 radios killing US T-Mobile HD2s.
Try to flash 2.08.HSPL only (also in HSPL4). It is enough. You can also try these drivers to fix your USB connection.
And here you can find offical ROMs.
Drivers linked above are not suitable, install activesync or WMDC is best option.
Finding original ROM is not going to be easy if you have no clues to origin of handset ...
Also, just cost you don't "see" the phone from the p c doesn't mean you don't have a USB connection.... it will never show up in your drives list like it does when an os is running, and activesync (or wmdc) will also not see the phone when it's in bootloader.
If the phone shows "USB" (and your PC may even "ding" when its plugged in, that's all you can expect unless you look deeper,, into the hardware list, for example.
What does hspl line say?
I'd do....
Hspl4, choose 3.03.hspl (NOT 3.03.0000)
Flash unbranded 3.14 rom from USB
Report back.
I have same story - 00028002 not allow+no usb.
no one stock rom can be flashed.
completely lost and no idea what to do.