EDIT ON JULY 5, 2010:
AFTER 30 TRYES on 2 days my pda has only enter bootloader mode on two times... and when I connected to my pc didnt appear "USB" on screen.
any help will be grateful. Please. Thanks.
EDIT ON JULY 2, 2010:
MY PDA DOESNT START THE BOOTLOADER
I have make HSPL 1.42 with "success" because "we hacked it " appeared on screen BUT...
that has been the las thing that I have seen on the screen. Now I cannot switch on, neither start in bootloader, and when I connect to pc and I turn on normally the pda in my pc I can see like "new hardware found... qualcomm..." (while on PDA is black screen).
I have try to left the HD2 without battery during seconds, minutes and hours before try again.
I have try to left the HD2 charging all night before try again.
I have try with other batteries (I have 3).
I have try with different with windows 7 and windows XP (for looking what happens if I connect HD2 with black screen.
ANY HELP????
MY PDA DOESNT START THE BOOTLOADER
on JULY 1 I SAID:
(Sorry for my bad english) I have been for 2 complete days trying to solve before post this new thread. Now, the explanation:
I have a Spanish Movistar company HD2.
To enter in bootloader mode I have to be a few seconds (or minutes, it depends...) without battery. When I get into bootloader mode I see:
_______________
PB81100 HX-BC
SPL-2.08.0000 8G XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x40
Serial
_______________
So I supose that it isn´t the HSPL installed.
Sometimes when I simply switch on I see HTC logo with white background (I supose that is because it has the task29 made.
When I left the device without battery few seconds (or minutes) and I get into again and I switch on I see too the HTC logo with white background.
I have try to flash some roms through microSD card and the result is allways the same: It changes the screen into a grey and I see "Loading..." but it stays like this infinitely (I have try to wait more than 20 minutes). I have try this with original Movistar Company ROM, original HTC ROM, some radios (more than 6 types), some coocked ROMS (including arthemis, BSB beast, Energy), and the result is allways the same, stays "Loading..."
I have try to flash through PC. CustomRUU Recognizes the device but when it starts to update the device doesnt change screen or sometimes looks like pixelated screen, and on the PC appears like new hardware found (qualcomm CDMA Technologies MSM) and update through pc doesnt start. I have try too when It appears like new hardware found to remove the battery and start on bootloader mode, but update neither starts.
I have try to make HSPL (2 and 3) and the result is allways the same: recognizes the device and on bootload screen apears "USB" in the white part. HSPL tells me what SPL I have ( 2.08.0000|| ) and let me choose 2.08.HSPL BUUUUT when I push continue in the device nothing happens, on the PC appears like new hardware found (qualcomm CDMA Technologies MSM) and HSPL gives me an error (sometimes one sometimes other):
__________________
CRITICAL ERROR
Flow: 00000006
Error code : 00000010
Description: Unknown
__________________
or
__________________
CRITICAL ERROR
Flow:00000002
Error code: 00000003
Description: USB Operation failed
__________________
Thanks to all for your help.
Tryed installing a radio higer then 2.6? Phone wont start without 2.7 or higer
Nakazul said:
Tryed installing a radio higer then 2.6? Phone wont start without 2.7 or higer
Click to expand...
Click to collapse
telling "some radios (more than 6)" I mean that I have try with more than 6 types of radios, but yes, I have try with radios from 2.04 to 2.08.
Thanks Nakazul
but first you need to hspl. you cant flash any of those roms or radios without hspl
enter bootloader (three coloured screen)
connect to USB, wait for 'serial' to become 'USB' - if pc tries to say it is a qualcomm, change USb ports. Use one around teh back of the PC, not one in the front casing.
run hspl ( 2 or 3, doesnt matter which) pick an spl that ends with .hspl, so
2.08.0000 - No, stock, it wont work
2.08.hspl - yes, now you can flash.
now run task 29 (use the shadrac repack)
enter bootloader again, confirm that your spl says 2.08.hspl
flash your rom over USB. Do not use sd card (using sd card is probably how you got spl 2.08.0000 on a non tmous phone)
samsamuel said:
but first you need to hspl. you cant flash any of those roms or radios without hspl
enter bootloader (three coloured screen)
connect to USB, wait for 'serial' to become 'USB' - if pc tries to say it is a qualcomm, change USb ports. Use one around teh back of the PC, not one in the front casing.
run hspl ( 2 or 3, doesnt matter which) pick an spl that ends with .hspl, so
2.08.0000 - No, stock, it wont work
2.08.hspl - yes, now you can flash.
now run task 29 (use the shadrac repack)
enter bootloader again, confirm that your spl says 2.08.hspl
flash your rom over USB. Do not use sd card (using sd card is probably how you got spl 2.08.0000 on a non tmous phone)
Click to expand...
Click to collapse
First, thanks.
I connect to USB, "serial" become to "USB" like allways (qualdcomm hardware never appears when conected with bootloader without start the HSPL or CustomRUU). I start HSPL 2 and I choose "2.08.hspl" like allways. I push continue and PC tells me "new hardware, qualcomm...." (allways on that momment, when push "continue" after choose "2.08.hspl") I change the USB cable to another port and automatically HSPL gives me an error and I only can acept and the HSPL software closes. I have try to change USB port before push "acept" but nothing. Allways appears "new hardware, qualcomm..." con PC while PDA stays with bootloader screen apearing like connected through USB.
Hope you understand all, I really dont know how to explain better.
strange. Is it the stock usb cable?
I think you should try a different pc.
samsamuel said:
strange. Is it the stock usb cable?
I think you should try a different pc.
Click to expand...
Click to collapse
I have try on 2 pc-s. One cpu with windows 7, the other with windows XP.
I have another HTC HD2 (this of Vodafone) and the cable works perfectly. (The died HD2 isnt mine of a friend.)
PD: Shouldn´t it be able to load correctly the stock rom through microSD?
Thanks!
sorry, i dont know what to suggest next. I'll sleep on it and let you know if anything occurs to me.
Thoughts for now, , your original stock rom is probably failing because i 'think' stock spl 2.x will not allow itself to be downgraded to 1.x A few people got stuck before hspl2 arrived.
How about trying a goldcard, with the tmous 2.13 stock rom? that would change the spl to 2.10.0000 and you could try with hspl3, , it could be that the spl is messed up (you shouldn't have been flashing with sd card, it messes with the spl/hspl, even when the flash fails, hspl will still be removed)
have you allowed the qualcomm dirbvers to install when in bootloader mode?
when in bootloader the AMSS is taking over connection so its the snapdraon drivers that your pc is trying to install, which are the ocrrect ones.
Allow your computer to install them, and try it again
g.lewarne said:
have you allowed the qualcomm dirbvers to install when in bootloader mode?
when in bootloader the AMSS is taking over connection so its the snapdraon drivers that your pc is trying to install, which are the ocrrect ones.
Allow your computer to install them, and try it again
Click to expand...
Click to collapse
When I tried to install that driver I make click on continue but doesnt find drivers...
NEWS!!!!!! (bad news...)
I have downgrade into HSPL 1.42 with "we hacked it" on screen, but now cant start the bootloader mode!!!! I have been trying to be without battery during minutes and during hours!!
I cannot star PDA on bootloader mode with or without USB cable conected and with or without SD inside. BUUUT If I turn on the HD2 normally in my PC I can see "new hardware...qualcomm...". What can I do whith this?
Thanks to all for your help!
byAGM said:
When I tried to install that driver I make click on continue but doesnt find drivers...
NEWS!!!!!! (bad news...)
I have downgrade into HSPL 1.42 with "we hacked it" on screen, but now cant start the bootloader mode!!!! I have been trying to be without battery during minutes and during hours!!
Thanks to all for your help!
Click to expand...
Click to collapse
"cant start the bootloader mode" Why not?
Can you just do a reset by poking the reset button (button near battery) while holding volume down? That won't bring up the bootloader??
zkid2010 said:
"cant start the bootloader mode" Why not?
Can you just do a reset by poking the reset button (button near battery) while holding volume down? That won't bring up the bootloader??
Click to expand...
Click to collapse
I dont know why but... I´m during few minutes (I have try during hours too) without battery, I put the battery inside the PDA and I push power button while holding volume down (like allways I have done to enter bootload) and nothing happens. I try again with reset button and nothing.
On both ways the HD2 makes a short vibration but doesnt bring up the bootloader.
When I connect to PC and I turn on the pda normally, pushing the power button (whithout hold the volume down button) I can see on PC like "new hardware found... qualcomm....", but the PDA screen its black. (I have try to connect other HD2 and works perfectly on the same PC with the same cable).
Thanks to all.
FYNALLY AFTER "WE HACKED IT " TO HSPL 1.42 I CANNOT START THE PDA NEITHER THE BOOTLOADER.
I have try lefting the HD2 without battery for a seconds, minutes and more than 8 hours... I have try too with the reset button. Nothing happens, I only can ear the little vibration that allways make. Nothing more...
May be to exist any solution with that 3 pins that are between SIM and microSD card? any connection with them? I dont know...
Will be this the first died HD2?... hope that no... but...
ANY HELP??
THANKS.
I have been 2 days trying to turn on the pda on bootloader mode. I have been lefting without battery during hours before trying to turn on but I has turn on (on bootloader mode) only 2 times and fail when connect to pc.
.
Somebody knows why I cannot start my pda on bootloader (remember it hasn´t any rom inside) in except of 2 times by 30 tryes?
Thanks and sorry for my bad english.
HELP PLEASE, DEAD HD2, NO BOOTLOADER.
is it possible that the battery isnt charged now? my telstra hd2 is stuck on the white htc screen constantly and i know the battery died on it and thought the same as you..i took the battery out for about a halfhour then plug it in and left it for a day and i was back in business with a charge. may be worth trying mate
the-wrangler said:
is it possible that the battery isnt charged now? my telstra hd2 is stuck on the white htc screen constantly and i know the battery died on it and thought the same as you..i took the battery out for about a halfhour then plug it in and left it for a day and i was back in business with a charge. may be worth trying mate
Click to expand...
Click to collapse
I have one cradle for charging batteries and 3 batteries.
The 3 times that the PDA has enter to bootloader has been without being the battery at 100% (between 50% and 60%).
Thanks for your help, the wrangler.
byAGM said:
I have one cradle for charging batteries and 3 batteries.
The 3 times that the PDA has enter to bootloader has been without being the battery at 100% (between 50% and 60%).
Thanks for your help, the wrangler.
Click to expand...
Click to collapse
no prob mate, wish i couldve helped you. ill keep wrackin my brain and see if i think of anything that may help you
Hi All,
I've successully insttaled mmty and tried some commands. all the formating and info commands.
After 2-3 mins. later I got this error message.
errmsg_file.log :Flash NAND DM internal transfer failed: dmov_transfer() errmsg_file.log :bad-block check - error DM transfer failedDMOV dev 0 chan 7 transfer: invalid channel state: 20
I turned off the phone and removed the battery waited for 2 mins. and rum MTTy again.
the same commands worked.
but after 2-3 mins I run another silly command like info 1,2,3... same error messaged apperad on MTTY again.
by the way ;
there is a similar thread here :
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=718611&page=3
Related
I managed to upgrade my phone to aku 3.3 using pof's method(bootloader 1.01 MFG) . Then, out of no where, I tried to use MTTY to upgrade my radio rom
It started as usual with the status bar moving. Suddenly some error messages came up.
Now, the phone is dead completely. I can''t even enter bootloader mode.
Is there a possible way that I can still save it??
Help!!!!
Have I bricked my device? Help plz
I managed to upgrade my phone to aku 3.3 using pof's method(bootloader 1.01 MFG) . Then, out of no where, I tried to use MTTY to upgrade my radio rom
It started as usual with the status bar moving. Suddenly some error messages came up. Can't remember exactly, but like some address can't find error.
Now, the phone is dead completely. I can''t even enter bootloader mode. Only when I take out the battery and plug in the charger cable the red light comes on. I looked the upgrade problem page, my symptom doesn't match any.
Is there a possible way that I can still save it??
Help!!!!
I had something similiar happen a little while back. What I did was pull the battery out and leave it out for a while, maybe a few minutes. I then put the battery back in and held the two side buttons and hit the reset button to put me into bootloader mode. I then cabled it to my computer and flashed a new OS via mutty. That got my phone back and operational.
@float. Nuh, it didn't work on my brick. Prob i will have to take it back to Tmobile if they kind enough to repair the no warranty phone i bought on ebay.
Sorry to have opened a new thread, I was so desperate.
Plz delelte it.
how exactly did you try to update the radio using mtty?
I download the 1.27 shipped radio rom. P.S. It seemed to be a german version, not sure whether that caused the disaster.
Using NBHextract to get the single GSM.NB file, then in MTTY, typed
USB> task 32
USB> lnb GSM.NB
Before flashing, just had it upgraded to the HTC AKU3.3 OS rom only. The old version radio rom version before flashing was 1.18.
Maybe the order i flash is wrong. I flashed OS first then the radio rom.
just guessing
ok, you loaded the radio rom code where os.nb should go. That may have caused mega bad blocks in flash. Can you even get bootloader mode if you reset using Wiki directions to obtain Tri-color bootloader?
Yes. I have tried many ways wiki suggests. Such as removing the battery leaving it more than half an hour and plugging it to the usb cable without battery. still can't get to the tri-color bootloader mode. Basically, I just can't turn on the phone.
If you connect it to the computer, can it communicate w/the PC? If you hear the windows tones try opening up mtty and see if you can communicate.
i'm stuck in the same place
for me it happened during extrom flash
Try removing the battery for a bit (a few minutes, maybe half an hour). Then, put the battery back in but don't plug the usb cable in. After that, hold the two side buttons as if you're trying to get it to go into the bootloader. Hit the reset button a few times with your stylus and see if that gets you to the bootloader. That's what worked for me.
tried that
tried removing battery and connecting usb
nothing helps
is there a place that fixes tytn in belgium ?
is there a way to flash a new rom via mutty ?
cause i still have the boot loader, but the phone still in the splash screen
when i type info 2 in the mutty command prompt i get this answer
Cmd>info 2
HTCSQTEK_203”µ·êHTCE
i think it's not realy normal
diffda said:
is there a way to flash a new rom via mutty ?
cause i still have the boot loader, but the phone still in the splash screen
when i type info 2 in the mutty command prompt i get this answer
Cmd>info 2
HTCSQTEK_203”µ·êHTCE
i think it's not realy normal
Click to expand...
Click to collapse
well your not supercid... your still locked to qtek
Look here and unlock your phone before doing any flashing!
http://forum.xda-developers.com/showthread.php?t=295751
to late i ve done that tow day's ago , now the only way to make my phone back to life, PB + KITL method i think
god bless KITL
Am having a problem with unlocking a Hermes using the SIM_CID Unlock version 3A
I appear to be stuck in a loop with the unlock process. I appear to have got as far as having installed OliPro (while still being at bootloader 1.01) but keep getting error 262 UPDATE FAILED
I can then recover to the tri-colour screen and process as far as RECOVERY SUCCESSFUL
But I cant get as far as updating the radio or whatever else it unlocks towards the end of the process and no new ROM loads (if that is what the unlocker does?) The percentage screen appears but doesnt progress at all. Then I get ERROR 262 again.
Is starting to the bootloader screen a sign of a bricked Hermes? I can get SERIAL to show and can get it to change to USB on that screen when I plug it into a computer but cant get any proper communication with the unit from the computer with that screen in place: ActiveSync obvoiusly wont start. As I left the 3A unlocker, it said RECOVERY SUCCESSFUL but does that necessarily mean that I have a brick now? I thought that the installation of olipro by SIM_CID unlock version 3A means that the unit is now hard-unlocked?
(Yes, I did try Hard-SPL-V7.zip but cant set up any communication between the exe file and the tricolour screen)
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
I thought that tricolour screen meant that it is ONLY starting in bootloader mode?
ultramag69 said:
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
Click to expand...
Click to collapse
I am a bit lost: How do I get into bootloader mode? I thought that it starting in the tricolour screen meant that it had started up in boot loader mode? Is there some combination of pressing buttons and 'on' switches like on my Blue Angel?
As it appears to have got stuck in a mode while in an upgrade process which didnt work when this error occurred, when I get it started, what should I flash to get the bootloader updated, the SIM and CID unlocked so that I can choose which ROM to flash? Should I continue with the SuperCIM_CID unlock or Hard SPL?
I have fully unlocked another Hermes before and have been playing around with ROMs but this one seems to have worked out differently: I was under the impression that loading OliPro meant that it was unlocked?
(Sorry about that answer: I will try RUU_Unwrapper.exe again)
ultramag69 said:
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
Click to expand...
Click to collapse
I did what you said and immediately I unchecked the tick in USB, I heard that the computer was establishing communication with the Hermes
But nothing I could do would let RUU_Wrapper.exe Run and communicate with the device. It just kept reporting NO DEVICE.
So I tried the super SIM and CID unlock again and it tried installing OliPro again and couldn't do so, saying that (having communicated with the device) it couldn't communicate with the device either. I tried retrying a few times with no success and pressing NO with equally no success. So I tried canceling out of the application. it thought about it for about three minutes and then simply started communicating, running the upgrade program. Now it starts the update process and I can see the progress.
However it stops at 21% and doesn't move any further. It has been that way for a few hours now. not sure if it is charging while connected, I suspect not and am wondering what to do now which wont brick the unit??
V7 still wont run but v3A still will!
ultramag69 said:
If you are using XP, untick "Allow USB Connections" in activesync. Put Hermes into bootloader and connect to PC. Run RUU_Wrapper.exe. Should fix the problem.
Click to expand...
Click to collapse
So I tried the super SIM and CID unlock again and it tried installing OliPro again and couldn't do so, saying that (having communicated with the device) it couldn't communicate with the device either. I tried retrying a few times with no success and pressing NO with equally no success. So I tried canceling out of the application. it thought about it for about three minutes and then simply started communicating, running the upgrade program. Now it starts the update process and I can see the progress.
However it stops at 21% and doesn't move any further. It has been that way for a few hours now. not sure if it is charging while connected, I suspect not and am wondering what to do now which wont brick the unit??[/QUOTE]
This is getting curiouser and curiouser: This device both will and wont coopeate at the same time. But nothing I could do would let RUU_Wrapper.exe Run and communicate with the device. It just kept reporting NO DEVICE on error 260\.
So I tried the super SIM and CID unlock again and it tried installing OliPro again and couldn't do so, saying that (having communicated with the device) it couldn't communicate with the device either. I tried retrying a few times with no success and pressing NO with equally no success. So I tried canceling out of the application. it thought about it for about three minutes and then simply started communicating, running the upgrade program. Now it starts the update process and I can see the progress.
However it stops at 21% and doesn't move any further. It has been that way for a few hours now. not sure if it is charging while connected, I suspect not and am wondering what to do now which wont brick the unit??[/QUOTE]
This is getting curiouser and curiouser: (Especially if you arent too petrified about bricking it) I can perform the recovery successfully from whatever I do but cant get v7 to communicate with the device. However 3A DOES still communicate but still gets stopped at 0% on the progress chart. Is this a known problem, that SuperSIM_CiD wont work with OliPro already installed at 1.40? That it WILL get stuck at 0% or 21%?
Now I cant hard reset either: I dont get the white screen, it just goes back into the bootloader, still showing IPL 1.01 and SPL 1.40 Olipro.
(Especially if you arent too petrified about bricking it) I can perform the recovery successfully from whatever I do but cant get v7 to communicate with the device. However 3A DOES still communicate but still gets stopped at 0% on the progress chart. Is this a known problem, that SuperSIM_CiD wont work with OliPro already installed at 1.40? That it WILL get stuck at 0% or 21%?
Now I cant hard reset either: I dont get the white screen, it just goes back into the bootloader, still showing IPL 1.01 and SPL 1.40 Olipro.
The computer IS communicating with the device (as I said it does give the 'ding' showing that the computer knows it is there) but it wont hard reset! It just goes straight to the tricolour screen immediately on startup. Even using a three hand method of pressing both buttons, pushing the reset in and putting the battery in at the same time gave the tricolour screen. And Windows Explorer cant get into the device. It seems to see it but there is no tree at all. So I cant use the Post 1160 method to flash from an SD card.
Even more baffling, i have now flashed a stock ROM successfully and v7 STILL wont communicate with the Hermes!! In desperation I even moved the directory to the root of C: Are some of these devices encrypted differently from others? So suddenly it boots properly and I immediately did a hard reset and erased everything and now Guess what? It hangs at the Windows Mobile screen! Needing a hard reset all over again
Should I just keep on trying Super SIM and CID unlock again and again until it works? (I assume that I have no longer got OliPro on it, though it does show a SPL of 1.40) There must be a way of unlocking this unit but this total non-cooperation doesn't seem to be covered in the Wiki. Is there a version of the Hermes like the Wizard which is more difficult to unlock than the others?
Sorry to reply again when no one gave any ideas on my last posting but I am wondering, horror of horrors, whether this might be a hardware problem?
I am now stuck at the tricolour screen ( 1.01, SPL 1.40.Olipro)) which turns on whenever I put the battery in. Connecting to the computer doesnt make any difference and obviously I keep getting ERROR 260 which seems to be a connection error meaning that the computer either isnt connected to the device (or that some software is conflicting somewhere, which is unlikely as flashing to the stock ROM did work before I tried to run V7 again)
Is there any possibility that running SuperCID&SIM unlock (which has never completed) caused all of this and is there any rescue procedure or should I just assume that this is a hardware problem now (or should I do a fresh posting)?
Is it inherently suspicious that tricolour turns in when I just put the battery in AND that even though SERIAL changes to USB on the Hermes, running the v7 hard update utility causes ERROR 260? [Or cant you run V7 when you already have OliPro installed somehow?]
There IS communication: Though I reported in my last posting that I could flash the Cingular ROM, flashing to the Cingular ROM now gets consistently stuck at 14%, sometimes with an ERROR 264!
Hello,
I'm about six hours into the process of trying to revive a nonfunctional HD2 that I purchased. I'm going batty!
Here is my status:
1) have installed SPL-2.08.HSPL 8G XE (0x05, 0x40) Cotulla HSPL
2) Have downloaded a few different roms (Chucky, TMO official, Energy) but they either get stuck at 0% or 9% (the highest it's gotten)
I'm getting pretty good at pulling the battery - it's like a new skill I never hoped to have!
I'm getting pretty frustrated because I've read about a hundred different posts on this site and I see that people are getting around this, but I'm starting to wonder if my phone has an issue that I can't resolve?
The phone doesn't boot up at all - it just says "Upgrade ROM code error, Please try again". Prior to my goofing with it, it just got stuck at the "Stick Together" screen. (Unwittingly bought it that way)
If I use the HSPL3_PKG to install/remove HSPL, it only works (connects to the phone) about one out of ten times, and out of the ~ten times I have gotten it to work, it only completed twice with a "We Hacked It" screen. The rest of the time it errors out just as I think it's getting the job done.
If I boot to the bootloader screen, I can put the USB cable in and see it change from Serial to USB (I've tried the thick and thin cables as some have suggested and haven't noticd a difference yet)
Then I kick of a rom update using the update utility that comes packed with it, and either the update process stops at 0% or it has made it all the way to 9%.
I'm in a position to get a replacement from TMO via the person who bought it (two for one, wife didn't like it, I bought it off of him) but I would rather not.
Any suggestions?
The part number of the phone is 99HKY001-00 B
jimmyswinger said:
Hello,
I'm about six hours into the process of trying to revive a nonfunctional HD2 that I purchased. I'm going batty!
Here is my status:
1) have installed SPL-2.08.HSPL 8G XE (0x05, 0x40) Cotulla HSPL
2) Have downloaded a few different roms (Chucky, TMO official, Energy) but they either get stuck at 0% or 9% (the highest it's gotten)
I'm getting pretty good at pulling the battery - it's like a new skill I never hoped to have!
I'm getting pretty frustrated because I've read about a hundred different posts on this site and I see that people are getting around this, but I'm starting to wonder if my phone has an issue that I can't resolve?
The phone doesn't boot up at all - it just says "Upgrade ROM code error, Please try again". Prior to my goofing with it, it just got stuck at the "Stick Together" screen. (Unwittingly bought it that way)
If I use the HSPL3_PKG to install/remove HSPL, it only works (connects to the phone) about one out of ten times, and out of the ~ten times I have gotten it to work, it only completed twice with a "We Hacked It" screen. The rest of the time it errors out just as I think it's getting the job done.
If I boot to the bootloader screen, I can put the USB cable in and see it change from Serial to USB (I've tried the thick and thin cables as some have suggested and haven't noticd a difference yet)
Then I kick of a rom update using the update utility that comes packed with it, and either the update process stops at 0% or it has made it all the way to 9%.
I'm in a position to get a replacement from TMO via the person who bought it (two for one, wife didn't like it, I bought it off of him) but I would rather not.
Any suggestions?
The part number of the phone is 99HKY001-00 B
Click to expand...
Click to collapse
After HSPL Install RADIO 2.14.50_04 then TRY to install latest Energy ROM.. Should work.
netvpn7 said:
After HSPL Install RADIO 2.14.50_04 then TRY to install latest Energy ROM.. Should work.
Click to expand...
Click to collapse
Even if it us a TMOUS HD2? I will give it a try, but I want to be sure before doing it!
Thanks for the reply
netvpn7 said:
After HSPL Install RADIO 2.14.50_04 then TRY to install latest Energy ROM.. Should work.
Click to expand...
Click to collapse
Once you have Hard-SPL on the device you don't need to worry about that anymore. Flashing Roms and radios will not overwrite it, that's what makes it "Hard". To make sure it's on there go into bootloader and it should show 2.08.hspl.
As for the radio, for TMOUS, just make sure it's a x.xx.50.xx radio (not a .51) and you'll be fine. If you have radio 2.10.50.xx you shouldn't have to change it.
So now I would try downloading one of the stock shipped Tmo ROMs (2.13 or 2.14). Then remove Sim and SD and go into bootloader, connect USB to PC and make sure it says USB on the device (not serial) and run the ROM Update Utility (RUU.exe). See if that works.
i also got this problem ,will try ur method n c
after hspl ,cant flash finish radio 2.14 it says ERROR (290) INVALID COMMAND.
excelpass said:
after hspl ,cant flash finish radio 2.14 it says ERROR (290) INVALID COMMAND.
Click to expand...
Click to collapse
You need HSPL..
HSPL done ,i tried a lot of files only Miri & Dinik n Duttys Leo Sense file can b flash successfully ,it went into menu once but now hang at htc startup again,,is this hardware problem?
i had the same problem last week. Drove me nuts.
i found there are more than one version of HPSL 3.
you have to download the latest one. for more info,
read my posts at
http://forum.xda-developers.com/showthread.php?t=789506&page=18
So you need HardSPL3 (the version is DarkForces Team HardSPL3 by bepe and Cotulla 21.06.2010)
If it still doesnt work, take a photo and post your screen
Still no go...
I have installed SPL-2.08.HSPL 8G XE (0x05, 0x40) Cotulla HSPL, the latest version I could find.
I just tried to flash RUU_Leo_1_5_TMOUS_3.14.531.0_Radio_15.42.50.09U_2.14.50.04_LEO_1.5_Ship and it consistently flakes out at 8%.
I charged the phone all night, booted to the tricolor screen, kicked off the update as an administrator in Win7, the phone got to 8% and then the update flaked out on the PC - "The ROM update encountered communication errors during the update process" (Error [276])
I genuinely think that this phone is bunk - I'm just going to have the fellow I bought it from call in for a warranty replacement.
Thanks for your help, everyone...
SD card flash...
Hi,
I could not see it anywhere in this thread, and also I'm not certain if it is possible on a HD2. But on my xperia I'm usualy flashing from a SD card, copy the image over rename it as KOVSIMG.NBH (guess it would be something like LEOROM.NBH).
Than by pressing (and holding) volume down + power button while the device is off going to the boatloader screen which detects the card (must be inserted and flash from it IF there is the correct file loaded on the card.
Dude,
Did you actually download the HardSPL3 version from DarkForces Team?
If not, dont second guess anything. And if it works, you'll get your phone back.
The file name to download is "HSPL3_PKG.exe". Its by bepe and Cotulla 21.06.2010
If you downloaded the right version. it will support ALL LEO types, and all the SPL versions below:
SPL 1.42.0000
SPL 1.62.0000
SPL 1.66.0000
SPL 2.07.0000
SPL 2.08.0000
SPL 2.10.0000
you just select which SPL version to install in the Choose SPL screen. This version also disables the CID Check.
Dont knock it before you try it ..
+1
jimmyswinger said:
I have installed SPL-2.08.HSPL 8G XE (0x05, 0x40) Cotulla HSPL, the latest version I could find.
I just tried to flash RUU_Leo_1_5_TMOUS_3.14.531.0_Radio_15.42.50.09U_2.14.50.04_LEO_1.5_Ship and it consistently flakes out at 8%.
I charged the phone all night, booted to the tricolor screen, kicked off the update as an administrator in Win7, the phone got to 8% and then the update flaked out on the PC - "The ROM update encountered communication errors during the update process" (Error [276])
I genuinely think that this phone is bunk - I'm just going to have the fellow I bought it from call in for a warranty replacement.
Thanks for your help, everyone...
Click to expand...
Click to collapse
Exactly in the same situation and dont know what to do...
snooffy said:
Hi,
I could not see it anywhere in this thread, and also I'm not certain if it is possible on a HD2. But on my xperia I'm usualy flashing from a SD card, copy the image over rename it as KOVSIMG.NBH (guess it would be something like LEOROM.NBH).
Than by pressing (and holding) volume down + power button while the device is off going to the boatloader screen which detects the card (must be inserted and flash from it IF there is the correct file loaded on the card.
Click to expand...
Click to collapse
Yes you are correct you can flash via SD card. You need a 4GB or lower SD card. This is not to say other higher GB SD card will not work, it is just that it has been stated many times the higher SD cards sometimes work to flash a ROM and sometimes don't. The card needs to be formatted with Fat 32. You have to find the RUU_(wharever).nbh and rename it to leoimg.nbh ( you almost got it righ tsnoffy lol) and copy it to your SD card. insert SD card into phone and hold the volume down botton down anx tap the power button keep holding the volume down button down until you see bootloader come up and say searching then let go of the volume down button. The ROM will flash.
Note: I've seen a few similar threads with a problem like mine, but my HD2 is showing different error messages, so I thought I'd start a new thread to avoid making things worse.
---------------------------------
So I purchased a second hand HTC HD2 pretty cheap. It's the 512HD2 and it came flashed with a MIUI Android with a Samsung Galaxy S2-ish interface. Problem was, the battery got drained way too quickly, even from the most minimal usage, so I though I should flash back to the stock OS and get my problem solved so I could use the HD2 as a primary phone.
Here's what I did:
1. I followed jayceooi's tutorial.
2. I downloaded a ROM Update for HTC HD2 (3.14.405.2) from HTC's Official HD2 download page.
3. I opened up the .exe, got the .nbh, renamed it correctly, put it on the SD card and then verified it's really there with an Android file manager.
4. VolDown + PowerButton and I got to the rainbow menu thing (I know, I'm a noob and I don't know how it's called) then I let go of the keys and got to the update screen.
5. PowerButton - Update begins
6. 30 seconds later, only after about 1/4 of the bar had progressed, I got a black screen, and then a screen that says "Software update failed. Please try again". Afterwards the gray screen saying "Loading... 00028002 not allow". Finally, back to the RGB screen I got:
HX-BC
SPL-3.03.0000 XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x40
And If i try to enter the boot mode via VolDown+PowerButton I get:
RUUNBH
HX-BC
SPL-3.03.0000 XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x40
Update ROM code error
Please try again
Serial
---------------------------------
Should I try a USB flash or something?
Thanks in advance.
?
Nobody?
Update:
I tried to upgrade from 3.03.0000 SPL to the 3.03.0000 HSPL via USB in the boot mode, but I got a critical error and nothing happened on the device whatsoever - same state as the post above.
Any ideas?
probably wrong stock rom used, (or did you use the phones correct serial to download the rom?)
enter bootloader (three coloured screen)
connect usb
run hspl4
choose 3.03.hspl
back into bootlaoder
connect usb
run the 3.14 rom over usb.
EDIT - just saw your edit about critical error, , ,win7 64bit? try different usb ports, and try a different pc if you have one available, , hspl can be a little picky.
samsamuel said:
just saw your edit about critical error, , ,win7 64bit? try different usb ports, and try a different pc if you have one available, , hspl can be a little picky.
Click to expand...
Click to collapse
Unfortunately I have only one laptop with a 32 bit Win7, but it's OLD and crapfull of viruses so I'm not risking any failures there.
Do you think it will be safe to HSPL over VMWare (virtual OS environment inside of windows)?
P.S.: Exact model is the HTC HD2 T8585. I checked it via an IMEI checker.
there's a very good chance that hspl wont flash from a virtual machine. (Something about not getting low enough level access to the usb or something).
samsamuel said:
there's a very good chance that hspl wont flash from a virtual machine. (Something about not getting low enough level access to the usb or something).
Click to expand...
Click to collapse
Ok, in that case I'll probably go over at a friend's house and try an HSPL there. I'll come back with some results as soon as I'm done.
Halfway done?
OK, so I got a good Windows 7 32 bit laptop and tried out HSPL4.exe by DFT. I kept my fingers crossed and, thankfully, I got to the "We hacked it! " screen.
After successfully updating and removing the USB cable, the phone rebooted with the same "Software Update Failed" message, but this time the gray screen showed the Cancel/Allow for the leoimg on the SD. I pressed the power button to attempt a flash, but I got the same issue as last time.
After that, the VolDown + PowerButton STILL showed:
SPL-3.03.0000
Since I'm not that stupid (I hope) I figured that the ROM reverts SPL and Radio to normal and that's why there was no trace of the HSPL, so I went back to the laptop to go at another 3.03.0000 HSPL. This time, after I got the "We hacked it! " screen I cancelled the ROM update and thankfully the RGB screen now reads:
P81100 HX-BC
SPL-3.03.HSPL XE
0x05
CotullaHSPL 0x40
IN SHORT - The HSPL was a success, now if you help me find the right ROM, I would owe you my life!
lol, i draw the line at advising roms, for example ive never used an android rom with sense, or a MIUI rom, and i havent used a winmo rom in about a year,, so it would be unfair of me to guide you.
ROM
Edit - Okay, thanks for all your help!
P.S.: I just ran an Task29 to get rid of the constant Software Update error at each boot and now I can boot into the RGB screen without the RUUNBH error so I think that will make things easier. I'll probably find the ROM myself or ask somewhere else.
Thanks again!!!
thanks
samsamuel said:
probably wrong stock rom used, (or did you use the phones correct serial to download the rom?)
enter bootloader (three coloured screen)
connect usb
run hspl4
choose 3.03.hspl
back into bootlaoder
connect usb
run the 3.14 rom over usb.
EDIT - just saw your edit about critical error, , ,win7 64bit? try different usb ports, and try a different pc if you have one available, , hspl can be a little picky.
Click to expand...
Click to collapse
if you were a girl I would kiss you
You saved my day. I was searching for my problem since 3 days and this has solved the problem
Finally Done!
@ParmakSokan - Hey! Looks like I'm not the only one samsamuel helped!
A little update - I finally have the phone in working condition! It is now running the stock Windows Mobile 6.5 specific for O2, since I figured out the device was purchased in the UK.
For anyone interested, I got the ROM from the official library of HD2 ROMs in 4shared, which I believe is held together thanks to xda-developers, so yeah - yet another KUDOS for that!
The HTC Sense UI is simply beautiful and I think I will actually stay with 6.5 for a few more months before considering 7.5 Mango.
P.S.: Moderators can mark the thread as solved.
Hi
I have a flashed HD2 with these problems.
In Bootloader it says
PB81100 SS-BC
SPL-208.HSPL 8G XE
0X05CotullaHSPL 0X50
If I try to install HTC RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe it breaks after 1% it says 270 error
HD2 reboots and again white Screen. When I put off/on battery and press Volume down I see bootloader display.
I tried to flash with sd Card, leoimg.nbh on the sdcard breakes after 10%
it says
00018003
LEOIMG.nbh -FAIL
Radio-Fail
I think I have a bootloader problem. How can I remove SPL-2.08.HSPL 8G XE and set the new orginal SPL ?
here bepe says :
4) Uninstallation
Only way to remove the HSPL is to flash an original SPL from SD card.
- Take any "RUU_signed.nbh" from a ship ROM and copy it to SD card.
- Rename it to "leoimg.nbh"
- Reset the device while pressing the volume down button.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=611433
I made it with HTC
RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe
but I can't remove HSPL from my bootloader.
How can I set my bootloader back to original htc ?
the topic can be closed
this has solved my problem
http://forum.xda-developers.com/showthread.php?p=24876999#post24876999
I had installd Windows 6.5 everthing was working perfect, then I tried to install Android and clk mod now I get the same in the 1. Posting from me.
I have SPL-3.03 HSPL in the boatloader but I get allways Error 270 I can't uninstall 3.03 HSPL
does anybody have an Idea?
Radio_2.15.50.14.nbh installation fails, but custom rom like energy sucesses. After that again white screen
nobody knows the solution?
You have a stuck radio. Fairly common, with a variety of symptoms. The radio wont let itself be changed which is why custom roms and splashscreens don't have a problem.(radio gets flashed at the start of flashing which is why it always fails around 8-10%) This issue can affect spl to a greater or lesser degree, some people can change spl some can't, some find flashing an older (but correct for that phones cid and region) stock rom, some find chilling the phone allows the flash to take allowing the radio to finally change, some never get anything to flash again.
hi
thank you for your answer. My Bootloader shows
SPL-3.03.HSPL XE
0X05
0X50
if I try to run Task29 via USB Cable, I get Error 270, it breaks sometimes at 16%
reflash 3.03 HSPL with HSPL 4 says it is successfull, but if I try to flash a rom with usb again it shows 270 Error, so my logical deduction is, reflash with HSPL4 does not really flash and it gives wrong answer because others like task28 leo customRUU can't flash over usb cable. HSPL 4 says success but this answer must be fake, after reboot 3.03HSPL remains in the bootloader, I tried to downgrade to 2.08HSPL no chance,
My System is Windows XP SP3 when I connect USB Cable to my HD2 it shows USB in the bootloader but why does it break if I try to flash over USB Cable and give an error 270 ? there must be a connection problem between my laptop and HD2.
I would like to know
Is there any way to flash HSPL4 over microSD card?
Can I see which Radio Rom has been installed ?
its a bit strange
Radio Rom Radio_2.15.50.14 istallation via USB Cable fails after 4%
and via microSD Card ~96-99%
I get
00018003
what can be the reason?
ParmakSokan said:
what can be the reason?
Click to expand...
Click to collapse
as i said,. you have a radio image that isnt allowing itself to be overwritten. My name for it is 'stuck radio' and some people fgind the radio still works fine with, for example, custom roms, it just cant be changed, others find the phone always hangs on grey bootscreen, yet more find taht hspol/spl flashes seem to work but nothing changes, some find chilling it in teh freezer lets a rom flash and suddenly all is well, and yet more find the freezer trick seems to work but doesnt, and yet more try and try and try to sd card flash with their CORRECT stock rom and suddenly without warning teh flash works.
My advcie, Prepare yourself for disappointment, but keep trying,and most importantly READING there are hundreds of threads about this.
mobile radio
ParmakSokan said:
nobody knows the solution?
Click to expand...
Click to collapse
hey gys whats this radio in mobiles... have searched and searched but no ans.....