Related
Okay here is the rundown:
1. Bought HD2 phone from ebay that had "freezing problems". Phone would freeze on "Stick Together" screen even after hard reset. Cleaned and made sure battery pins were straight. Removed SIM and sd card during the entire process.
2. Attempted to flash T-Mobile 2.13 update by sd card. (Formated card FAT32 and changed .nbh file to leoimg.nbh). Waited a day and then hard reset the phone and phone froze again.
3. Flashed HSPL and attempted to run Task29. (Right click on run as administrator but the program never completes). I've tried the version that requires a radio. I attempted to extract the Task29 that doesn't require the radio but for some reason the computer is unable to do so.
4. Tried to run T-Mobile update again but now that program cannot finish. Says something about radio failure.
I can still get into the bootloader screen but if I start it up normally it reads "System update failure". Needing any help I can get. I'm not an expert at this (obviously) so please try to use "noob" terminology for my benefit if possible. I'm using Vista and I'll try to give whatever information that may be needed in order to resolve this matter. Thanks in advance for your help.
What does it show in bootloader exactly?
And, after you flashed 2.13.531.1 stock did the phone boot past the splash screen (Stick Together screen)? Have you tried flashing via Activesync?
In bootloader in the upper right hand corner it says RUUNBH
then shows the following lines
PB81120 HX-B3
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x40
Upgrade ROM code error
Please try again
Once I flashed stock ROM it went pass the splash screen once (and that was after many MANY hard resets without SIM and sd card).
I tried activesync also but it doesn't complete. It keeps failing when it gets to installing the radio.
try to flash just a radio....Just make sure its compatible with the phone...you can only use one series of radio for the tmous hd2....
Manually put phone into bootloader..
Connect to computer via usb
Run RUU...
Cant hurt...just to see if you can flash a radio to it..since thats where your getting your errors...
bossb2525 said:
Okay here is the rundown:
1. Bought HD2 phone from ebay that had "freezing problems". Phone would freeze on "Stick Together" screen even after hard reset. Cleaned and made sure battery pins were straight. Removed SIM and sd card during the entire process.
2. Attempted to flash T-Mobile 2.13 update by sd card. (Formated card FAT32 and changed .nbh file to leoimg.nbh). Waited a day and then hard reset the phone and phone froze again.
3. Flashed HSPL and attempted to run Task29. (Right click on run as administrator but the program never completes). I've tried the version that requires a radio. I attempted to extract the Task29 that doesn't require the radio but for some reason the computer is unable to do so.
4. Tried to run T-Mobile update again but now that program cannot finish. Says something about radio failure.
I can still get into the bootloader screen but if I start it up normally it reads "System update failure". Needing any help I can get. I'm not an expert at this (obviously) so please try to use "noob" terminology for my benefit if possible. I'm using Vista and I'll try to give whatever information that may be needed in order to resolve this matter. Thanks in advance for your help.
Click to expand...
Click to collapse
hello there...
this is known issue with some t-mobile hd2's..
this happens mostly when you get refurbished..but i'm not sure
almost same thing happens look here --> http://forum.xda-developers.com/showthread.php?t=795554
go ahead, flash stock rom, get replacement from t-mobile
Thas not gonna help
JackH said:
hello there...
this is known issue with some t-mobile hd2's..
this happens mostly when you get refurbished..but i'm not sure
almost same thing happens look here --> http://forum.xda-developers.com/showthread.php?t=795554
go ahead, flash stock rom, get replacement from t-mobile
Click to expand...
Click to collapse
He stated quite clearly he bought the phone on eBay - Hows he gonna get a replacement from T-Mobile without a warranty?
Okay - if you can get to the Bootloader consistently, you have that going for you at least. Did you try just flashing a Radio? If thAT fails, Next thing I would try is a task 29, then flash a stock ROM afterwards. Alternately, you COULd try reflaching HSPL, in the event that it's corrupted in some way. You have some options still, just preceed cautiously, and don't flash anything you are unsure of. Let us know what happens!
i have the same exact issue too, see: http://forum.xda-developers.com/showthread.php?p=8434282#post8434282
I am using windows 7, and mine installed the regular spl and rom, but not the radio from the memory card.
I hope someone figures it out.
simplest way
hi brother.....i m facing the same problem nd i dnt hav the bill from t mobile also, so cnt replace the **** back..nyways...what i did was gave it to a htc service center they chekd the fon...nd said hav to replace the mainboard... fuk.....now its stil ther since 3 weeks.....lets c wat happens
Sorry, I just realized XDA went down one night and all my updated information that I posted on here was erased. Anyway, I was successful in running task29. I also successfully updated the phone to the 2.13 software from t-mobile. In the end my phone still froze and would occasionally go past the splash screen. Since I can't get any consistency with the phone (and since I've been working on this phone for almost 3 weeks) I just finally gave up on it. Hope somebody can find a solution for the rest of you experiencing this problem. I will continue to check back at the other threads to see if anyone finds the magic fix. Thanks for everybody who tried to help me.
Hi got a problem with my HD2 which i got a couple of months ago, it came with WinMo 6.5 as standard, so i decided to put Android on it, so i flashed all the MAGLDR and clockwork mod stuff on, and loaded HyperDroid GBX onto it, this ran brilliantly up until yesterday when i briefly browsed facebook, then i locked the phone and put it back in my pocket, next time i tried to use it the touch screen would not respond whatsoever. Only the physical buttons worked, so i pulled the battery out and reset it but that has not helped.
Any reason why it suddenly failed like that? Very annoyed
Hi!
Try to return back to stock WM, it might help.
When I turn on the phone with the power button the touch screen doesn't work so I have to use any other button and it works. Running the same rom as you.
Yeah i noticed that too, when ever i unlocked the phone with the power button most of the time it didnt respond but any other button worked fine.
i sent it to repair.they will change the whole screen
Go back to a WM6.5 stock ROM, if the screen still does not work, then you may want to consider having it repaired. If it is under any sort of warranty make sure you un-HSPL it.
What happens if they find out that I have run Android and Energy rom on it?
Now it has SPL-3.03 0000 and I think the latest ROM.
Can I send it in like this? Is the spl original?
10Buron said:
What happens if they find out that I have run Android and Energy rom on it?
Now it has SPL-3.03 0000 and I think the latest ROM.
Can I send it in like this? Is the spl original?
Click to expand...
Click to collapse
Once latest official ROM is installed and phone booting normally, nobody cares what OS was installed on it before You can have even SPL 2.08.000, it will pass check-in. And yes, SPL 3.03.000 is the latest official one.
Hope you are right, because I don't want to end up in jail for having messed with the copyright....
My phone won't open, the screen is not responding. But I know I have the 3 14 0466 ROM(?) and spl-3.03.0000
the multi-coloured screen says:
PB81100 HX-BC
SPL 3.03.0000 XE
MicroP (LED) 0x05
MicroP(TOUCH) 0x40
Did You tried to flash through SD card?
It's easy. Just unpack somewhere downloaded ROM, rename file RUU_signed.nbh to Leoimg.nbh, copy it to your SD card and go to tri-color screen. Then you will be asked to flash the phone and after after pressing Vol+ key it will start to reflash. Hope it helps, goodluck!
thx
was that last one for me? I think I have the correct Rom and SPL, the screen is not functioning, so I am planning to send it in for repair.
I have tried sd-flashing, and it didn't help. Used different sd-cards and LEOIMG.n...
but I managed to get it to the spl and rom as mentioned.
Planning on sending it in, bad plan?? or good plan??
10Buron said:
was that last one for me? I think I have the correct Rom and SPL, the screen is not functioning, so I am planning to send it in for repair.
I have tried sd-flashing, and it didn't help. Used different sd-cards and LEOIMG.n...
but I managed to get it to the spl and rom as mentioned.
Planning on sending it in, bad plan?? or good plan??
Click to expand...
Click to collapse
If it is still under warranty, go on
In what circumstances your touch stopped working? Was it dropped ground, placed in wet conditions (eventually steam or mist or submerged)?
no reason really. Never dropped it, had it since last March.
Ran Android and Energy-Rom on it since october...
No Idea why it stopped working
10Buron said:
no reason really. Never dropped it, had it since last March.
Ran Android and Energy-Rom on it since october...
No Idea why it stopped working
Click to expand...
Click to collapse
It doesn't work all time or only after standby/block? I've had same kind problem with touch not working after standby, with Artemis WinMo ROM. Solved after HR but after few days repeated. I installed one of the latest NRG ROMs and it solved this trouble. If touch doesn't respond all the time then it may be dead because of controller failure and should be replaced IMHO.
it is totally blocked. nothing works on the screen. buttons are ok, but the phone is locked, so i can only see the unlock-slider...
IMHO?
10Buron said:
it is totally blocked. nothing works on the screen. buttons are ok, but the phone is locked, so i can only see the unlock-slider...
IMHO?
Click to expand...
Click to collapse
It's My Humble Opinion
Heheh, thanks. I am sending it in then. Hoping they can fix it. Can't be that expensive, if the warranty isn't valid. If warranty covers it, I am glad...
Thanks for your help
Hello everyone.
I am using my HD2 for a year almost. Last few months I am on Androind NAND, HyperDroidX version, worked perfectly for me. HSPL version 2.08 is there too ofc.
Few days ago, when I pressed button on him, and wanted to unlock it, screen just stayed black, buttons flashed. Ok, can happen, I put out battery (for reset), placed it back, turn on.... and only white screen appeared. No that standard message "HTC brilliant" or whatever is default screen on these HTC phones.... just PURE WHITE screen is there, and nothing is happening.
Ok I thought... I ****ed up software somehow (altho I dont know how, cause as I said, that all happened few days ago, and I didnt do anything recently with my phone, didnt instaled any new program, or so what so ever). Entered bootloader screen, connected phone on USB (got normal message that I got new hardware), and wanted to do TASK29, and than flash everything again from begining. But, doing so, TASK29 just stayed at 0% for a like 5-6mins, and after it there was "ERROR [262]: Update error" showing. Suggest me to do "recovery process", which I did, didnt helped. I googled about that error 262, found out a few things... than, I tried doing TASK29 at my 2 other friends comp's... 1 is on WIN7, other XP. Reinstaled ActiveSync/MDMC, tried to do it... and same problem happens. Changed my USB cable, same thing. Tried to flash anything else, tried to flash RADIO, new ROM... but nothing... all the same error as with TASK29. So, nothing is wrong with TASK/ROM/RADIO files, nothing is wrong with comp or USB cables, cause I tried it on other comps/with other cable as I said.
Only thing I can instal (or flash, w/e is that "method" called) is HSPL. I reinstaled it without problems, and that's the only thing I can do on this phone atm.
My friend later also suggest me to do "hard flash" (dunno how its called, so I call it "hard flash" ) of STOCK ROM, and with that operation also remove my HSPL, so if that works, than I can easily later put HSPL again, and try to flash custom roms.
So I tried that also... formated my 8gb SD card... dowloaded stock rom from official website (with my S/E number), unpacked it, copied RUU_signed.nbh onto root of sd card... changed name into LEOIMG.nbh... placed sd card into phone, entered bootloader screen, pressed "power" key... but again NOTHING is happening, no instalation is starting... there is just standard bootloader screen staying on. For any case, I than again formated again my sd card (FAT32 it is, 4kb allocation), again done same, copied, placed card, tried to start flashing, and again nothing.
Well, I am far away from being pr0 about this phone... but I think I tried almost everything. Anybody knows what can cause these problems??
Why I cant "normal flash" anything from 3 different computers where I tried it, why it always stays on 0% (and if I didnt said, I did alot of flashing till now, all were going just fine till now)?
And why I cant even do "hard flash" of STOCK ROM, and remove HSPL?
And ofc, what all I can do to solve this problem?
P.S. Sry for wall'o'text, but I just wanted to explain everything about this problem. Hope somebody help me find solution for this.
Tnx in advance.
try this and do the complete wipe thing, see what happens:
http://forum.xda-developers.com/showthread.php?t=1187292
you can also try task2a and then try reflashing.
also check for bent/misaligned battery pins.
also report here what the bootloader says (would be a bunch of numbers in the top-left corner on a red-blue-green-white screen).
you might want to try the "freezer trick" as well.
@orangekid
I read whole post, but atm I see only pictures, I dont see any file to download, and I dont know what to do there?
@ASCIIker
Battery is ok... I charge phone normaly, think battery is not problem.
Bootloader screen is this:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x50
And "freezer trick" is what? (as I said, I am not full pro about all things about this phone).
joximovic said:
@orangekid
I read whole post, but atm I see only pictures, I dont see any file to download, and I dont know what to do there?
@ASCIIker
Battery is ok... I charge phone normaly, think battery is not problem.
Bootloader screen is this:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x50
And "freezer trick" is what? (as I said, I am not full pro about all things about this phone).
Click to expand...
Click to collapse
The guy removed the file for some crazy reason.
"freezer trick" is to compensate for overheating mainboard issue some HD2s suffer from.
1) put your phone in a plastic bag and put it in the fridge for 15 minutes.
2) take out and try to flash stock ROM again
joximovic said:
@orangekid
I read whole post, but atm I see only pictures, I dont see any file to download, and I dont know what to do there?
@ASCIIker
Battery is ok... I charge phone normaly, think battery is not problem.
Bootloader screen is this:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x50
And "freezer trick" is what? (as I said, I am not full pro about all things about this phone).
Click to expand...
Click to collapse
just to be sure, i'm not talking about the battery itself or the battery's capacity. have a look at the battery PINS to see if one or more might be bent/misaligned. if you meant you charge it "normally" and rarely remove the battery, then you're right...probably pins will be ok. but have a look at the pins just in case.
the HSPL information seems to look good. and by your own account, HSPL is the only thing that flashes properly. try another thing...try to flash ONLY a radio ROM...see if that "takes". if it fails with this also, might be a "stuck" radio problem, although the few accounts i've read about stuck radios indicate that the flashing goes through to 100% but the radio doesn't really change. (BE CAREFUL TO FLASH THE CORRECT RADIO VERSION IF YOU HAVE A TMOUS HD2)
freezer trick is what orangekid said. sounds like a long shot but it has been known to get things going enough for you to restore stuff to a factory state and possibly send it off for a warranty claim.
ASCIIker said:
just to be sure, i'm not talking about the battery itself or the battery's capacity. have a look at the battery PINS to see if one or more might be bent/misaligned. if you meant you charge it "normally" and rarely remove the battery, then you're right...probably pins will be ok. but have a look at the pins just in case.
the HSPL information seems to look good. and by your own account, HSPL is the only thing that flashes properly. try another thing...try to flash ONLY a radio ROM...see if that "takes". if it fails with this also, might be a "stuck" radio problem, although the few accounts i've read about stuck radios indicate that the flashing goes through to 100% but the radio doesn't really change. (BE CAREFUL TO FLASH THE CORRECT RADIO VERSION IF YOU HAVE A TMOUS HD2)
freezer trick is what orangekid said. sounds like a long shot but it has been known to get things going enough for you to restore stuff to a factory state and possibly send it off for a warranty claim.
Click to expand...
Click to collapse
To further clarify the TMOUS radio thing, if you have a TMOUS, DO NOT flash a radio that ends in .51 or an early release eu radio (2.04.50 etc.)
Just to be safe don't flash any radio under 2.12.50 because they pretty useless to you anyways.
Took look at battery, and its pins... all seems rly OK. Dont think there is problem.
Tried to flash RADIO only... again same thing, struck at 0%. (nope, I am not on Tmobile version.... my version is "standard", and I tried to flash 2.15.50.14 version of RADIO (same I used long time for mine HyperDroidX Andriod version).
Now, if I cant do anything else... tell me... is there ANY way that I can kill my HSPL, and turn it into "regular" SPL, so I can use my warranty on this phone, cause I have it still?
I read somewhere (dunno if its true), that I can "overwrite" my HSPL with regular SPL with "HSPL3_PKG" file that can be found here on forum. From manu, dont choose HSPL 2.08, instead of it choose SPL 2.08.0000 instead? Or something like that?
If I cant do anything else, at least, is there a way to put regular SPL, and take my phone at my service?
Hspl4.
Its in the winmo upgrade forum
Sent from my HTC HD2 using XDA App
I rly cant belive anymore.
Dowloaded HSPL4, tried that... from manu I choose 2.08.0000 instead of 2.08.HSPL... instalation was going fine, finished succesfully, I clicked OK... but after restarting my phone, NOTHING has changed.
Entering bootloader screen I can still see same:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x50
Click to expand...
Click to collapse
This means there are no more solutions? :S
just for the hell of it try a different micro SD, format fat32 then try stock ROM flash again (make sure no typos in the LEOIMG.nbh)
Did do that 2 days ago... but nothing happened again.
Was pissed alot, and took my phone to the warranty service. Luckily, in that service there are uber-nice ppl, and they just said they wont even look at that HSPL.
Guy there said it's probbably some problem with motherboard, and phone is sent to hardware service.
Tnx for responses and help anyway.. hope all passes good.
Hi everyone,
I'm totally lost with the HD2 my brother didn't want any more. I think he installed an android os but it couldn't launch or function correctly so I tried to have it back to his original state.
I tried the hard reset but it didn't work, the phone didn't launch.
I used the Task29, it worked and cleaned the phone. Then I tried to install the official rom 3.14 found on the htc support's page. The loading get stuck at 1% and stop to move until I get the 262 error.
I read a bit and try to understand how all of this work but I still don't get it. I tried the older version of the official rom, it worked a bit better since now the loading bar get stuck at 6 or 8 % randomly.
So now when I power on the phone it says : "Software update failed! Please try again" which I tried all yesterday long.
When I hold volume down and power on what I get on the red green blue white screen is this :
RUUNBH
PB81100 SS-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x50
Upgrade ROM code error
Please try again
I don't know what to do to resolve my situation. I'll be grateful for any help or hints you can give me.
Looks like you are trying via USB.
You could have a corrupt nand in a wrong area or some sort of hardware error.
Just to eliminate hardware, re-download the 3.14 ROM (in case you got a corrupt file)
and extract it, put the NBH file on the root of your SD card and make sure it's called leoimg.nbh disconnect from your PC and boot into bootloader and flash from SD
btw this is a tmobile phone right?
Maywiki said:
Hi everyone,
I'm totally lost with the HD2 my brother didn't want any more. I think he installed an android os but it couldn't launch or function correctly so I tried to have it back to his original state.
I tried the hard reset but it didn't work, the phone didn't launch.
I used the Task29, it worked and cleaned the phone. Then I tried to install the official rom 3.14 found on the htc support's page. The loading get stuck at 1% and stop to move until I get the 262 error.
I read a bit and try to understand how all of this work but I still don't get it. I tried the older version of the official rom, it worked a bit better since now the loading bar get stuck at 6 or 8 % randomly.
So now when I power on the phone it says : "Software update failed! Please try again" which I tried all yesterday long.
When I hold volume down and power on what I get on the red green blue white screen is this :
RUUNBH
PB81100 SS-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x50
Upgrade ROM code error
Please try again
I don't know what to do to resolve my situation. I'll be grateful for any help or hints you can give me.
Click to expand...
Click to collapse
Hello Maywiki,
task29 doesn't delete HSPL, that causes your troubles. May I cite from HSPL4 by Dark Forces Team:
"5) 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."
Be sure your battery is charged.
For future flashing experiences I advice you to not only "read a bit" but digging deep into it - and then re-read again.
Have fun
Getrid …
Getrid said:
Hello Maywiki,
task29 doesn't delete HSPL, that causes your troubles. May I cite from HSPL4 by Dark Forces Team:
"5) 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."
Be sure your battery is charged.
For future flashing experiences I advice you to not only "read a bit" but digging deep into it - and then re-read again.
Have fun
Getrid …
Click to expand...
Click to collapse
task29 did not cause any of his issues, after he did taask29 he tried to do what you say and flash the stock ROM but it hangs on the flash.
At no time from the bootloader should a flash just stick like that. I personally think it's a hardware failure, bad nand or something, or even a bricked radio if it keeps hanging near 1%, but you never know, the ROM he's using might be corrupt.
I still suggest you download the ROM again, put the .nbh file on your sd card like stated above and try a flash from SD.
If that fails maybe you can try to flash a custom ROM that does not include a radio and if that flashes we know we cannot flash a radio because that is what is hanging the flash.
Thanks for all your replies.
Yes I try via usb.
orangekid said:
btw this is a tmobile phone right?
Click to expand...
Click to collapse
Nope, it was bought in Belgium and it's not tied to an operator.
That's the name of the file I downloaded from the htc site : RUU_Leo_S_HTC_FRA_3.14.406.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship
The problem is that I can't access the sd card. The pc knows that an htc device is connected but I can't acces the device (it doesn't show up anywhere) and the sd card. The windows mobile app doesn't find a device connected too. Could it work if I pass via another phone to put the file on the sd card ?
For future flashing experiences I advice you to not only "read a bit" but digging deep into it - and then re-read again.
Click to expand...
Click to collapse
The thing is, it's not my phone at the start. I wouldn't launch myself into flashing without a lot of reading but since I got the phone in this state it's hard to find where am I.
Maywiki said:
I tried the hard reset but it didn't work, the phone didn't launch.
Click to expand...
Click to collapse
hard reset doesnt do anything when magldr clk are there, only when winmo 6,5 is there.
The loading get stuck at 1% and stop to move until I get the 262 error.
Click to expand...
Click to collapse
it worked a bit better since now the loading bar get stuck at 6 or 8 % randomly.
Click to expand...
Click to collapse
thats bad, 8/9 is the time the radio is being flashed, and is a primary indicator of a stuck radio (which also covers stuck spl, , corrupt spl/radio/bootloader basically)
The first time, the 1% hang, is the point where a stock rom tries unsucessfully to flash the spl for the first time, either triggering teh corruption, or the first time a flash has been attempted and so teh first time bootloader notices it's corrupted, (hence the RUUNBH at teh top of bootloader, it has tried to start flashing, and encountered an error, and not dropped out of flashing mode, as you would expect for a normal failed flash)
From here on, chances are you will either
1-never get anything to flash
2-possibly get winmo custom roms (no radio, see) to flash but nothing else
3-things like task29 and hspl appear to flash, but nothing changes
try No 2 first, and then try the freezer trick,chill teh phone right down, and have an sd card ready with the leoimg.nbh ready on it ready to flash as soon as you take it out of teh freezer.
Just occasionally, people get past this type of error, probably meaning the issue was corrupt software, but usually there is no fix (except JTAG, and even that isn't always successful) possibly meaning hardware corruption of a critical area of nand.
Also, if it DOES work in the freezer, that probably means you have an overheating device.
Maywiki said:
Could it work if I pass via another phone to put the file on the sd card ?
Click to expand...
Click to collapse
yes, any method you like to copy the leoimg.nbh to the sd card is fine.
samsamuel said:
hard reset doesnt do anything when magldr clk are there, only when winmo 6,5 is there.
thats bad, 8/9 is the time the radio is being flashed, and is a primary indicator of a stuck radio (which also covers stuck spl, , corrupt spl/radio/bootloader basically)
The first time, the 1% hang, is the point where a stock rom tries unsucessfully to flash the spl for the first time, either triggering teh corruption, or the first time a flash has been attempted and so teh first time bootloader notices it's corrupted, (hence the RUUNBH at teh top of bootloader, it has tried to start flashing, and encountered an error, and not dropped out of flashing mode, as you would expect for a normal failed flash)
From here on, chances are you will either
1-never get anything to flash
2-possibly get winmo custom roms (no radio, see) to flash but nothing else
3-things like task29 and hspl appear to flash, but nothing changes
try No 2 first, and then try the freezer trick,chill teh phone right down, and have an sd card ready with the leoimg.nbh ready on it ready to flash as soon as you take it out of teh freezer.
Just occasionally, people get past this type of error, probably meaning the issue was corrupt software, but usually there is no fix (except JTAG, and even that isn't always successful) possibly meaning hardware corruption of a critical area of nand.
Also, if it DOES work in the freezer, that probably means you have an overheating device.
yes, any method you like to copy the leoimg.nbh to the sd card is fine.
Click to expand...
Click to collapse
Yeah exactly where I was going with this.
Use a USB SD card reader thing to put it on SD card, or even another phone if you have to.
Try a custom ROM maybe.
If you are running 2.15.00 you don't need to flash another radio anyways, and since you have HSPL you don't need another SPL either, so you're not quite as screwed as some others even if you've got a bad radio/no flash situation.
So I did what you said (except put the phone in the freezer).
The installation went ok. Once finished it said nothing so I guessed I had to restart the phone.
Now the phone gets stuck in a white screen with htc in green on it.
Did I make something wrong ?
Maywiki said:
So I did what you said (except put the phone in the freezer).
The installation went ok. Once finished it said nothing so I guessed I had to restart the phone.
Now the phone gets stuck in a white screen with htc in green on it.
Did I make something wrong ?
Click to expand...
Click to collapse
No, either your flashed task29 then no rom or it's not loading the ROM,
try the SD flash again with the CORRECT rom and see what happens.
orangekid said:
No, either your flashed task29 then no rom or it's not loading the ROM,
try the SD flash again with the CORRECT rom and see what happens.
Click to expand...
Click to collapse
I tried again with the 3.14.406.2 from the support site, the update goes without a problem :
RADIO_V2 - OK
RCUST - OK
BOOTLOADER - OK
SPLASH1 - OK
OS - OK
CONFIGDATA - OK
RUU_WALLPAPER1 - OK
RUU_WALLPAPER2_ OK
Update Complete
UPDATE SUCCESS
When I reset, the phone vibrate seven times and stay on the white page with the htc logo on it.
What do I have to do now ? Try another rom ?
Hmmm, radio_v2 OK, ,, that's unexpected, but doesn't necessarily change anything.. .
Give the freezer trick a few goes.
Maywiki said:
I tried again with the 3.14.406.2 from the support site, the update goes without a problem :
RADIO_V2 - OK
RCUST - OK
BOOTLOADER - OK
SPLASH1 - OK
OS - OK
CONFIGDATA - OK
RUU_WALLPAPER1 - OK
RUU_WALLPAPER2_ OK
Update Complete
UPDATE SUCCESS
When I reset, the phone vibrate seven times and stay on the white page with the htc logo on it.
What do I have to do now ? Try another rom ?
Click to expand...
Click to collapse
Sounds like your chip is overheating, not good. You need a main board replacement or maybe this:
http://forum.xda-developers.com/showthread.php?t=982454
or see if this guy will donate his
http://forum.xda-developers.com/showthread.php?t=1890582
That's what I think is wrong.
Take out the battery and put it and the phone in a baggy in the freezer for 15 minutes, then put in the battery and turn on the phone. It should load WM6.5 before freezing again...
samsamuel said:
Hmmm, radio_v2 OK, ,, that's unexpected, but doesn't necessarily change anything.. .
Give the freezer trick a few goes.
Click to expand...
Click to collapse
Ok, now I need an explanation. How the hell does this trick work ? I did what you said and now the phone works. What's the mystery behind this ?
Is it permanent or it will need to be done frequently ?
orangekid said:
Sounds like your chip is overheating, not good. You need a main board replacement or maybe this:
http://forum.xda-developers.com/showthread.php?t=982454
or see if this guy will donate his
http://forum.xda-developers.com/showthread.php?t=1890582
That's what I think is wrong.
Take out the battery and put it and the phone in a baggy in the freezer for 15 minutes, then put in the battery and turn on the phone. It should load WM6.5 before freezing again...
Click to expand...
Click to collapse
Thanks for the tips, but I got the phone for free and it was mean to be left alone somewhere on a desk. If the problem come again, I'll get a new phone. And I'm not ready to change a main board by myself, I have two left hand.
Maywiki said:
Ok, now I need an explanation. How the hell does this trick work ? I did what you said and now the phone works. What's the mystery behind this ?
Is it permanent or it will need to be done frequently ?
Thanks for the tips, but I got the phone for free and it was mean to be left alone somewhere on a desk. If the problem come again, I'll get a new phone. And I'm not ready to change a main board by myself, I have two left hand.
Click to expand...
Click to collapse
The trick works because your chip is overheating. This is a common HD2 problem. When you freeze the phone the chip cools enough to boot the OS, and it may run fine for a few minutes. Play a video or do anything that heats up the processor at all and it will reboot and get stuck on bootloader again. It is a hardware issue that can only be solved by one of the methods I mentioned above.
orangekid said:
The trick works because your chip is overheating. This is a common HD2 problem. When you freeze the phone the chip cools enough to boot the OS, and it may run fine for a few minutes. Play a video or do anything that heats up the processor at all and it will reboot and get stuck on bootloader again. It is a hardware issue that can only be solved by one of the methods I mentioned above.
Click to expand...
Click to collapse
Yep you're right, it can't stand a video. Thank you anyway :good:
First of all, sorry if this thread already exists, but for the past 2 days I've been searching the web for my problem, but no luck. So I'm asking for your help.
My device had android 2.3 few months ago. One day it got stuck at loading screen, and I thought the SD card was corrupted because the ROM was installed there, and I tried to plug it to the PC, the windows sound would play that a device is connected, but I didn't see the sd card listed in My Computer
. So I bought a new sd card 2 days ago, plugged it to the phone, and it still wouldn't recognize the sd card. So I tried a few solutions, like copying RUU_signed.nbh with a card reader, and renaming it to LEOIMG.nbh. That only gave me an error 'No Allow' 00028002.
HX-BC
SPL-2.08.0000 8G XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x40
Right now I have copied Ruu_signed.nbh from RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship
and renaming it to LEOIMG.nbh, and the phone is stuck on Loading...
I see the bootloader screen is missing the device model number (PB81100) so would suspect the nand chip has gone bad.
Do a search & perhaps try task 21 & installing a hspl via cottulla hspl4 (HD2wiki has links)
Also use rest pin rather than pull battery as sometimes can clear an issue but in cases like this expect picking up a donor device for a mainboard will be needed.
Mister B said:
I see the bootloader screen is missing the device model number (PB81100) so would suspect the nand chip has gone bad.
Do a search & perhaps try task 21 & installing a hspl via cottulla hspl4 (HD2wiki has links)
Also use rest pin rather than pull battery as sometimes can clear an issue but in cases like this expect picking up a donor device for a mainboard will be needed.
Click to expand...
Click to collapse
I think i've seen the PB81100 few times when I was trying different ROMs. Could you please link me an appropriate ROM for my case that I can install by putting it on the SD Card ? I cannot connect my phone to the pc, so im using a card reader to put things on the sd.
Just look in HD2 Wiki as have links to loads of ROMs & without seeing your device or knowing any of its history it very hard to know what is the correct regional cid rom for flashing.
I always do via USB & get a HSPL on first thus bypassing CID lock & making flashing less prone to problems over stock SPL. you will just have to guess most likely correct regional & brand ROM from what you know of the device & any branding logo it may have.
If lucky & persist a bit you may get something to flash :-/
Mister B said:
Just look in HD2 Wiki as have links to loads of ROMs & without seeing your device or knowing any of its history it very hard to know what is the correct regional cid rom for flashing.
I always do via USB & get a HSPL on first thus bypassing CID lock & making flashing less prone to problems over stock SPL. you will just have to guess most likely correct regional & brand ROM from what you know of the device & any branding logo it may have.
If lucky & persist a bit you may get something to flash :-/
Click to expand...
Click to collapse
Thanks for your reply, I just checked my folders to see if I have anything that I used before, and this is what I got.
DFT_LEO_MAGLDR113_DAF
NexusHD2-JellyBean-CM10_V1.4a
Recovery_v1.3_150M
And I currently have HD2ToolKit4.2.0.1 which is not of any use at the moment...
Edit: NVM, everything is working now.