So... today I was on my way to installing WP7. As I was having trouble, I decided to start over. I started to task 29 the phone... At 8% it vibrated 5 times, I panicked and the cable wound up unplugged. Now I'm here with a phone that won't go into the bootloader. I've tried letting the battery charged. I've also tried taking the battery out and leaving the phone alone for an hour.
Help?
Well if your USB cable came unpluged and you can not boot into bootloader. Then yes you have hard bricked your HD2. The only options you have are to get it JTAGed or have the main board replaced.
a task29 doesn't touch bootloader, so i think it's not a brick
have you used last 24mb nand??? (you can choose this option in magldr)
Before the task 29, yes. It was in the instructions.
Also: I'm going to the T-Mobile store today and playing stupid... maybe they'll help me out
"I'm going to the store today and play stupid... maybe they'll help me out "
~psykick5
Classic !
psykick5 said:
Before the task 29, yes. It was in the instructions.
Also: I'm going to the T-Mobile store today and playing stupid... maybe they'll help me out
Click to expand...
Click to collapse
NEVER use last 24mb, they are used for bootloader flashing, radio flashing and other operation during flashing, you are not the first user that report brick for this problem...but people continue to write stupid guides!!! Please contact the autor of this guide and warn it to delete this step!!! Or we will have an HD2 cemetery very soon!!!
pirlano said:
NEVER use last 24mb, they are used for bootloader flashing, radio flashing and other operation during flashing, you are not the first user that report brick for this problem...but people continue to write stupid guides!!! Please contact the autor of this guide and warn it to delete this step!!! Or we will have an HD2 cemetery very soon!!!
Click to expand...
Click to collapse
The sad irony was after the task 29 I was going to skip that step since I thought it was stupid...
Glad to see others posting on this thread as people start threads here to get other more experienced users answers. But let us look at post #1 again shall we?
psykick5 said:
So... today I was on my way to installing WP7. As I was having trouble, I decided to start over. I started to task 29 the phone... At 8% it vibrated 5 times, I panicked and the cable wound up unplugged. Now I'm here with a phone that won't go into the bootloader. I've tried letting the battery charged. I've also tried taking the battery out and leaving the phone alone for an hour.
Help?
Click to expand...
Click to collapse
Now yes Task 29 does not touch the bootloader or radio partition of the NAND. But in my honest opinion letting the USB cable come unpluged or your battery dieing in the middle of any kind of flash is just not something you want to happen. Also anytime your device vibrates multiple times in secession you know you got some kind of major problem. This is a notification to you that something is wrong. I think the exact problem is determined by the number of vibrations.
Last if your device will not boot into bootloader via the external hardware keys. You either have faulty hardware keys, a faulty screen which is not showing the bootloader, or a screwed up bootloader which means your device is bricked. From post #1 I eliminate the first two reasons, just leaving a bricked device.
pirlano said:
NEVER use last 24mb, they are used for bootloader flashing, radio flashing and other operation during flashing, you are not the first user that report brick for this problem...but people continue to write stupid guides!!! Please contact the autor of this guide and warn it to delete this step!!! Or we will have an HD2 cemetery very soon!!!
Click to expand...
Click to collapse
You have to use the last 24mb nand for Yuki XDA's wp7.. It worked fine for me..
T-Macgnolia said:
Glad to see others posting on this thread as people start threads here to get other more experienced users answers. But let us look at post #1 again shall we?
Now yes Task 29 does not touch the bootloader or radio partition of the NAND. But in my honest opinion letting the USB cable come unpluged or your battery dieing in the middle of any kind of flash is just not something you want to happen. Also anytime your device vibrates multiple times in secession you know you got some kind of major problem. This is a notification to you that something is wrong. I think the exact problem is determined by the number of vibrations.
Last if your device will not boot into bootloader via the external hardware keys. You either have faulty hardware keys, a faulty screen which is not showing the bootloader, or a screwed up bootloader which means your device is bricked. From post #1 I eliminate the first two reasons, just leaving a bricked device.
Click to expand...
Click to collapse
Yeah I shouldn't have done that. Is there a key or reference for vibration error messages?
psykick5 said:
Yeah I shouldn't have done that. Is there a key or reference for vibration error messages?
Click to expand...
Click to collapse
I am sure there is such a reference list somewhere, but I really have no idea other than requesting one from HTC where you can find one. I do know without any doubt though that the vibrations are meant to be a indication to a tech of what is wrong with the device. As I have read some post by some very hardware knowledgeable people here on XDA, such as Senior Member facdemol, talk about the vibrations. If I were you I would hit up Google hard and search for one cause as I said I am sure there is one out there.
Related
Dear all
i did flash my us version hd2rom but i didn;t notice that the rom igot is for taiwan. Now my phone can;t turn on can't see anything on the phone can't reset. It's totally die now.
Is any one know how to fix it? I just got the phone xd
oh i shouldn;t do this. Really need help now
Not to be rude but you really should have used the search function. Sorry but if you flashed the wrong ROM your bricked. It's just a $550 paper-weight. Send it back to T-mobile and play innocent. Again, really sorry because at this point in time there is nothing at all you can do.
~Jasecloud4
We would need more details as to the steps you've taken to get to the point where you are.
Did you flash the appropriate TMOU HSPL prior to installing the ROM - and where did you get the ROM from? What happens when you try to charge it via USB?
As the other poster said, you shouldve done some homework before potentially effing up your device.
hi guys, I just got a same problem. After I flash a rom from HK my phone just totally die. Can't turn on, can't reset, can't charge. And my pc can't recognized my phone... (I did flash the appropriate TMOU HSPL )
your phone is Dead Learn to read on how to flash before you go blindely into doing it
New users really should wait a week or two before flashing their new phones so as to get familiar with the process.
Thank said, I hope you are able to get it fixed. Stay calm, read posts where others did the same thing and see if you are able to repair it. Do Not rush things.
return the phones and play innocent indeed. next time take time to read stickies and warnings from rom cooks :/
ha i dont own an hd2 im just reading up on them (in case i own one...android ftw though) but this guy sure sounds like a BRICK.
I have unlocked bricked phone with wrong rom.
There is one thing you can try.
Take the sim card out.
take the mem stick out.
Remove the battery for at least 30 minutes.
start phone with volume down pushed in.
if it doesn't power on try waiting an hour or two.
conect to pc and run task 29.
Then flash with corect rom and radio
Damn really sucks bro.. But this is why we must always double check that the Rom is mad for 1024 Hd2(U.S) and not 512... Best bet just tell t-mobile that phone stop working out of nowhere
Bkzn3ne said:
Damn really sucks bro.. But this is why we must always double check that the Rom is mad for 1024 Hd2(U.S) and not 512... Best bet just tell t-mobile that phone stop working out of nowhere
Click to expand...
Click to collapse
this really is the best option.. why even fiddle around with it anymore? send it back to TMo and get a brand new one.. Either act innocent or mad... mad always gets free stuff... extra battery perhaps? another 16gb sd card? who knows... gotta complain to gain...
Funkyrocemz said:
this really is the best option.. why even fiddle around with it anymore? send it back to TMo and get a brand new one.. Either act innocent or mad... mad always gets free stuff... extra battery perhaps? another 16gb sd card? who knows... gotta complain to gain...
Click to expand...
Click to collapse
LOLOLOLOL...
Exact same thing happened to me and I couldn't do ANYTHING with it wouldn't turn on couldn't get it in boot mode and essentially what your going to have to do is.........send it back and play dumb and get another sent out to you!! Other than that you are truly sitting on a good looking paper weight!!
I'm glad someone pointed out that at least it's a nice looking paperweight...lol
I did the same thing on my 1-day old HD2 with the HK Rom.
Went to the local mobile phone repair centre and had a techie guy work on it over 2 hours and still couldn't get anywhere. He was suggesting me replace the Flash Memory however I insisted there must be a way without messing around the hardware.
In the end the techie called his bro (supposedly the original factory) and was advised that there is no bootloader just as yet....I was asked to wait a few weeks and see...
I am in the view that this brick can be unbricked but it just will take some time for people to develop the techniques and have the appropriate hardware/software in stock...
PLEASE DO READ CAREFULLY BE JUMPING INTO THE WATER. Everyone is busy but this is the price - a $580 paper weight!
might have a second luck
why dont u hold the volume up and volume down buttons at the same time. then power on the device and do a hard reset. or just run task29 try to get the phone to get picked up by task29. and re-rom it. just a thought. dont know if it will work.
or third luck
how about you turn off the phone. push the volume down button power it on. and run one of the CleanEx roms while in the boot menu. give it a try it might work. its not like something worse can happen.
(make sure sim and sdcard are out)
1. make sure ur phones off
2. hold the volume button
3. while holding the volume button power on the device
4. just check if u even have ur spl on hspl (optional)
5. download a CleanEX ROM
6. run CustomRUU.exe
and see if that fixes it. and if that doesn't work just try the same steps but before you get to step 6 run task29 first.
eastlegend said:
how about you turn off the phone. push the volume down button power it on. and run one of the CleanEx roms while in the boot menu. give it a try it might work. its not like something worse can happen.
(make sure sim and sdcard are out)
1. make sure ur phones off
2. hold the volume button
3. while holding the volume button power on the device
4. just check if u even have ur spl on hspl (optional)
5. download a CleanEX ROM
6. run CustomRUU.exe
and see if that fixes it. and if that doesn't work just try the same steps but before you get to step 6 run task29 first.
Click to expand...
Click to collapse
Tried all means already except for Task 29. Will do some research then give it a try.
I'd recommend you to follow advices from senior members. In my case I bricked my 2 day HD2 TMOUS because I follow a sugestion about a ROM from another member of this forum. I asked twice if that ROM was compatible with the TMOUS HD2!!! I installed the correct HSPL version then installed the ROM and bricked my phone. There's no way to fix, take it to a T-MOBILE store and play dumb, make them call customer service and you'll get a new phone in 2-3 days, it worked for me.
My DX lock screen just froze, I can't get it to do anything; it won't turn off...nothing happens when I hit any of the buttons. I downloaded Liberty 1.0 a couple of days ago. Does any know what to do??
wtivey said:
My DX lock screen just froze, I can't get it to do anything; it won't turn off...nothing happens when I hit any of the buttons. I downloaded Liberty 1.0 a couple of days ago. Does any know what to do??
Click to expand...
Click to collapse
Have you tried to pull the battery? I can't help you about what caused the error, but that should at least reboot the phone.
nvm, i just figured out how to take the battery out. problem solved
yeah I took it out and it worked...i didn't know i could pull the battery but I figured out how to do it
yeah, it's the simplest solution to problems like that. Just be careful not to do that while flashing roms. Even if the rom seems to be stuck. It's best to wait at least 15-30 mins.
What do you mean "flashing ROM?"
The term flashing is basically installing a new rom onto the phone.
I'm use to the computer terms where cmos bios chips were fproms and installing new firmware was called "Flashing"
Just be very careful with your phone. The terms that describe specific actions are golden on these types of forums. If you don't understand the terminology, please double check everything before you proceed with changing things on your phone. I know it is a fun world to play in, but one bad move can ruin your device. I'm not trying to be mean or to discourage you, I just want to make sure you have a fun and safe time without having to reprogram everything because of one "minor" mistake. We all started where you are now, so we understand the mysterious world. Just stay safe out there, friend.
Sent from my DROIDX using XDA App
I've noticed that when I'll turn off phone and then put USB in, red LED is lighted for few seconds, suddenly phone starts, battery stops loading and MAGLDR is executed. It seems MAGLDR substitutes code for battery loading. Does it mean, that if I'll make battery totally empty I won't have a chance to load it without OS (which handles battery loading process)?
i thought they fixed it in magdlr .13? so you can drain your battery to 0% without problems...
AAAAAARRRRRRRRRRRRRGGGGGGGGGGGHHHHHHHHHHHHHHHHHH
RTFM
/rant
Read the bit that says "New in 1.13"..... It's pretty simple.
http://forum.xda-developers.com/showpost.php?p=10197474&postcount=1
On a side note, no, you can't kill the battery. Once power is connected, your phone uses that, it's just the light goes off while MAGLDR is booting.
Same here, when I turn off the phone and charge it, it turn on automatically. Help please!
seVIIen said:
Same here, when I turn off the phone and charge it, it turn on automatically. Help please!
Click to expand...
Click to collapse
Like what mattOG has posted, READ!
Sent from my HD2 Droid HD using XDA App
seVIIen said:
Same here, when I turn off the phone and charge it, it turn on automatically. Help please!
Click to expand...
Click to collapse
Yet another user confirming that magldr works exaclty the way that Cotulla designed it to work. Thanks for the feedback
seVIIen said:
Same here, when I turn off the phone and charge it, it turn on automatically. Help please!
Click to expand...
Click to collapse
It's suppose to do that... that's a new feature in version 1.13 so that there isn't the problem where you have to remove battery to get phone to boot like what happened with earlier magldrs. People complained about that, so cotulla fixed it the only way possible... so it will turn on automatically, and now people are complaining about that. He said in next version it will have setting to allow the uncontrolled charging while phone is off, but you might have to remove battery to get it to boot again. Also not sure if uncontrolled charging is bad for battery or not.
You have to understand... you're hacking your phone to run OS's that weren't meant for it... things are not going to act the same as a native phone. You should feel lucky you can do these things at all.
I have 2300mAh extended battery and with almost every android rom it is useless. When android boots up to the stage when you must enter sim pin than hd2 reboots and it is going into loop. I have discovered when I isolate middle pin on the battery everything is working fine, battery is charging and it can be used without problems.
Doesn't any body READ anymore???
mdrazic said:
I have 2300mAh extended battery and with almost every android rom it is useless. When android boots up to the stage when you must enter sim pin than hd2 reboots and it is going into loop. I have discovered when I isolate middle pin on the battery everything is working fine, battery is charging and it can be used without problems.
Click to expand...
Click to collapse
So isolate the pin... or use a kernel compatible with extended battery
TheATHEiST said:
Doesn't any body READ anymore???
Click to expand...
Click to collapse
What??? People post explanations to be read???
I thought we were just losing our time trying to help. It seems many prefer to read the title, go to the last page and ask a question for which the answer is on the first post
For their defense, the search functionnality is too complexe. Isn't it possible to just clic on a button and receive answer to all our question directly in our mailbox. Or maybe a button we can clic and directly solve our issues.
I found one... it's the "add to basket" button for an Android phone on an online shop. Works great
this thread helps me a lot! thanks for good article!
truc007 said:
What??? People post explanations to be read???
I thought we were just losing our time trying to help. It seems many prefer to read the title, go to the last page and ask a question for which the answer is on the first post
For their defense, the search functionnality is too complexe. Isn't it possible to just clic on a button and receive answer to all our question directly in our mailbox. Or maybe a button we can clic and directly solve our issues.
I found one... it's the "add to basket" button for an Android phone on an online shop. Works great
Click to expand...
Click to collapse
Complex? are you having a laugh?
You type in your keywords and click tyeh search button, whats hard about that?
You also get a "similar" threads list whyen creating a topic prior to posting and 9/10 you can find your answer this way also.
TheATHEiST said:
Complex? are you having a laugh?
You type in your keywords and click tyeh search button, whats hard about that?
You also get a "similar" threads list whyen creating a topic prior to posting and 9/10 you can find your answer this way also.
Click to expand...
Click to collapse
Of course I was having a laugh
In French we call "ironie" (not sure at all about the translation).
I write stupid things to make the owner of the thread realize that the question has not to be asked.
For this question, you don't even have to use the search function (which is not complicate, I agree).
The answer is on the first page of MAGLDR thread!!! (know issue, not corrected in x.13 but a paliative solution has been applied... the phone start to prevent having to remove the battery).
Honnestly it's sad to see that you keep posting the same answers and it seems some people never take time to read. They just ask directly their questions.
Maybe I'm sometime difficult to understand as English is not my language.
So our answers don't help... the question neither. It just make a lot of useless thread with the same question again and again.
I can also add that when you post a thread, the forum give you the thread which could give you the answer!!!
truc007 said:
Of course I was having a laugh
Click to expand...
Click to collapse
Sorry missed that
truc007 said:
I can also add that when you post a thread, the forum give you the thread which could give you the answer!!!
Click to expand...
Click to collapse
Your not adding anything. Its already been said 2 posts up
Sorry for this, but the search function do not work now, and haven't worked for the past few hours. My phone was charged to 100% yesterday night, and today it was turned off because of no battery.
i plugged in the phone to my computer and it just reboots, i cant charge the battery. I need some seriously help here. Yes i have read this post but i cant find a solution to this problem.
I have also trieed it in my wall charger but the same happens, just reboots all the time.
I use this rom: [17 FEB][DFT] CleanDROID v2.02_smu - Super Clean Froyo+Cyanogen [Kernel GL_Core_v2b] By G.Lewarne link to rom: http://forum.xda-developers.com/showthread.php?t=917590
I use MAGLDR 1.13
please help me in the right direction
Last night, I noticed that ROM Manager had an update in the Android market
(512mb LEO with Typhoon Cyanogenmod). I hit the update button, and walked away for a while while my phone did its thing, as usual.
I returned about 15 minutes after and noticed that my HD2 was off. I could not, however, turn it back on.
Removing and replacing the battery did not help. The phone wouldn't charge via the wall socket.
My linux PC will not detect it (I checked my dmesg log when plugging in and turning on)
I left the battery out overnight, plugged the phone into the wall, put the battery inside. No luck.
I checked the battery voltage with a multimeter, and it reads about 3.9v.
I don't think it's the battery. I think my HD2 is somehow bricked! Is there anything I can do?
It's not under warranty any more, but if I send it for repair, do you think they will deny it (because it has Android on it)?
Enlighten me with your wisdom, XDA! I don't want to say goodbye to this amazing device!
xebozone said:
Last night, I noticed that ROM Manager had an update in the Android market
(512mb LEO with Typhoon Cyanogenmod). I hit the update button, and walked away for a while while my phone did its thing, as usual.
I returned about 15 minutes after and noticed that my HD2 was off. I could not, however, turn it back on.
Removing and replacing the battery did not help. The phone wouldn't charge via the wall socket.
My linux PC will not detect it (I checked my dmesg log when plugging in and turning on)
I left the battery out overnight, plugged the phone into the wall, put the battery inside. No luck.
I checked the battery voltage with a multimeter, and it reads about 3.9v.
I don't think it's the battery. I think my HD2 is somehow bricked! Is there anything I can do?
It's not under warranty any more, but if I send it for repair, do you think they will deny it (because it has Android on it).
Enlighten me with your wisdom, XDA! I don't want to say goodbye to this amazing device!
Click to expand...
Click to collapse
Did you try holding the volume down button and turning on the phone....
It should take you to the tri colored screen...
If you get there the phone is not bricked
casemandan said:
Did you try holding the volume down button and turning on the phone....
It should take you to the tri colored screen...
If you get there the phone is not bricked
Click to expand...
Click to collapse
Yes I have tried that. Alas, nothing...
Do you recon they will fix it even if Android was on it?
xebozone said:
Yes I have tried that. Alas, nothing...
Do you recon they will fix it even if Android was on it?
Click to expand...
Click to collapse
It is a little late for me to mention this, seeing as you have sent your HD2 in for repairs all ready. But your power/end button may have stopped working, if you still had the your HD2 you could try pressing the reset button by the SD card slot and see if the device booted up then. But that is not an option now.
If all you did was update ROM Manager via the Android Market. Then it should not have bricked your HD2 in any shape form or fashion. Further more it should not have caused your HD2 to turn off either. I mean when you are running NAND Android on the HD2 you are pretty safe from bricking your HD2 because both MAGLDR, cLK, and the actual Android ROM is flashed to the ROM partition of the NAND memory and never touches the real SPL bootloader partition of the HD2.
Plus did you check your battery pins before sending it in? One might have been bent slightly. Or it could have been dirty battery terminals not allowing a good connection.
Point is I very much highly doubt your HD2 was bricked. You probably just missed judged your situation is all. As far as will they fix it? If you are willing to pay the fee they charge then yes.
T-Macgnolia said:
It is a little late for me to mention this, seeing as you have sent your HD2 in for repairs all ready. But your power/end button may have stopped working, if you still had the your HD2 you could try pressing the reset button by the SD card slot and see if the device booted up then. But that is not an option now.
If all you did was update ROM Manager via the Android Market. Then it should not have bricked your HD2 in any shape form or fashion. Further more it should not have caused your HD2 to turn off either. I mean when you are running NAND Android on the HD2 you are pretty safe from bricking your HD2 because both MAGLDR, cLK, and the actual Android ROM is flashed to the ROM partition of the NAND memory and never touches the real SPL bootloader partition of the HD2.
Plus did you check your battery pins before sending it in? One might have been bent slightly. Or it could have been dirty battery terminals not allowing a good connection.
Point is I very much highly doubt your HD2 was bricked. You probably just missed judged your situation is all. As far as will they fix it? If you are willing to pay the fee they charge then yes.
Click to expand...
Click to collapse
Hah. I don't know where you assumed that I have already sent it in. I'm the kind of person who tried to fix it myself first
Pressing the reset button doesn't do anything. I tried holding it down while inserting the battery too, and nothing,
The battery pins do not appear to be bent or dirty. I gently pushed them upright, and down, and scraped the surface gently in case there was any layers of dirt, still nothing.
I have a sibling with an HD2. I can test the batteries later.
Do you think somehow, the NAND can be worn from multiple reads/writes until it dies? It is flash memory after all, and that last write from the update could have pushed it...
xebozone said:
Hah. I don't know where you assumed that I have already sent it in. I'm the kind of person who tried to fix it myself first
Pressing the reset button doesn't do anything. I tried holding it down while inserting the battery too, and nothing,
The battery pins do not appear to be bent or dirty. I gently pushed them upright, and down, and scraped the surface gently in case there was any layers of dirt, still nothing.
I have a sibling with an HD2. I can test the batteries later.
Do you think somehow, the NAND can be worn from multiple reads/writes until it dies? It is flash memory after all, and that last write from the update could have pushed it...
Click to expand...
Click to collapse
Hmmm sorry I thought you had sent it in for repair already. Guess I miss read that, my bad man.
Yes NAND chips are rated for only a number of flashes. But that number is very high. I can not remember the exact numbers right now but hey that is what google is for right? But you did not flash a ROM you just uninstalled a app and then installed the updated version of that app. But then again I guess when you install or uninstall a app it is performing a some what similar action. Still though flashing a ROM is flashing a ROM, and installing a app is installing a app. One is a a lot different than the other.
My money is with your battery being bad. I mean like I said updating your ROM Manager should not have caused your HD2 to turn off at all. Try your sibling's battery and report back, I really hope that fixes it for you.
I haven't actually installed any Android ROM myself. But I did lots of WinMo ROM updates. What strikes me is that you installed a new ROM through the Android Market. Is that a normal procedure to upgrade an Android ROM on the HD2?
T-Macgnolia said:
Hmmm sorry I thought you had sent it in for repair already. Guess I miss read that, my bad man.
Yes NAND chips are rated for only a number of flashes. But that number is very high. I can not remember the exact numbers right now but hey that is what google is for right? But you did not flash a ROM you just uninstalled a app and then installed the updated version of that app. But then again I guess when you install or uninstall a app it is performing a some what similar action. Still though flashing a ROM is flashing a ROM, and installing a app is installing a app. One is a a lot different than the other.
My money is with your battery being bad. I mean like I said updating your ROM Manager should not have caused your HD2 to turn off at all. Try your sibling's battery and report back, I really hope that fixes it for you.
Click to expand...
Click to collapse
Hmm... I have an interesting development.
I tried my sibling's battery, and it didn't help, but what I did notice is that the phone vibrates slightly when I turn it on (as it should), but it does so very weakly. So weakly that I need to put my ear against the phone to hear it.
I don't think it's the LCD, because the charging light still doesn't work.
It probably needs a new mobo.
Any suggestions before I take it in for repair?
Cenobite_ said:
I haven't actually installed any Android ROM myself. But I did lots of WinMo ROM updates. What strikes me is that you installed a new ROM through the Android Market. Is that a normal procedure to upgrade an Android ROM on the HD2?
Click to expand...
Click to collapse
No, I didn't install a ROM on the market. It's an app called ROM Manager
xebozone said:
Hmm... I have an interesting development.
I tried my sibling's battery, and it didn't help, but what I did notice is that the phone vibrates slightly when I turn it on (as it should), but it does so very weakly. So weakly that I need to put my ear against the phone to hear it.
I don't think it's the LCD, because the charging light still doesn't work.
It probably needs a new mobo.
Any suggestions before I take it in for repair?
Click to expand...
Click to collapse
Yeah I agree with you it sort of sounds like something in the main board has malfunctioned. My guess is the processor or the NAND chip one. I would just send it in for repair if I was you. Maybe your HD2 just finally died, I know it sucks. But if you are willing to pay for the repair then you should be back up and running in no time. I am assuming you plan to send it to HTC for repair right? If for some reason they do give you a hassle about Android being on your HD2 and will not repair it. Then contact me I might know somewhere you can get a new main board put in it.
I got my HD2 back today.
Apparently it's not worth fixing...
I also got robbed today... Just my luck.
I cannot afford any other phones atm, but what do u think would make a good candidate replacement for the future? I don't think any other phone has the same kind of mod-ability and support here at XDA, but I would be delighted if you could prove me wrong.
My friend has a Galaxy S2, which is cool, but it doesn't have notification LED :/
Is there much hacking/dev on the GS2?
had not used my hd2 in two months turned it on and it was just a white screen with no htc logo, couldnt get magldr... nothing. i was able to get splash screen so i decided to try flash back to windows 6.5 to start again, i tried sd card (leoimg.nbh) method which failed aster 10% or so .. so i tried pc method that failed after 1% , tried sd card again and again then it failed saying not allowed! when i went into bootloader mode it now says spl-1.42.0000 ... hspl is gone! still i cant flash winmo rom pc\sd method and hspl 2 keeps failing also,
If i boot the phone normally i just get a triangle
If anyone has any ideas how to get anything working on this please help
i have a tmobile UK phone
"Not allow" and "get triangle" and "hspl gone" tells us that a rom you tried to flash from SD card was not the correct rom for your phones region/carrier.
When you started the flash hspl was there so the checks were bypassed,,, next hspl was removed (spl is the first part to flash) then the flash restarts, but of course hspl is gone so the checks aren't bypassed so they fail and you get a triangle.
thanks for the reply, thats what a thought but where to go from here hspl2 just wont work iv tried the correct rom from htc for uk tmobile but it dont get past 0% , the first one was from xda and is indeed different, the problem is where to go from here? this must have happened to someone else, ive been trying to get this to work for two days now and searched a lot but cant seem to find anything that will flash... any ideas??
wooooohoooo ..... had nothing to loose so tried ruu \ pc method over and over and over finally it flashed win mo 6.5 ... man windows suck lol.
if anyone having this problem this is how i did it, tried flashing the ruu using pc, got same as before it just got stuck on 0% , dissconeted the cable then i got the dissconected error with "view document" and "recovery" options i then just followed the recovery options and it flashed winmo
hopefully this helps someone!!!
thats not a good sign. Failing failing failing then working, and also flashes hanging at around 8% - 10% (your first post) often point to radio failing and/or caused by / because of overheating hardware.
If flashing problems persist, try chilling teh phone for twenty minutes in the freezer (sim battery and sd out) and if it flashes ok when you take it out, its heat issues.
samsamuel said:
thats not a good sign. Failing failing failing then working, and also flashes hanging at around 8% - 10% (your first post) often point to radio failing and/or caused by / because of overheating hardware.
If flashing problems persist, try chilling teh phone for twenty minutes in the freezer (sim battery and sd out) and if it flashes ok when you take it out, its heat issues.
Click to expand...
Click to collapse
I would try to give better advice than just saying to put it in the freezer. I can't wait to hear someone reading this and doing it. Then pulling their phone out, connecting it, and seeing it go pop fizzle as the motherboard shorts out through all the condensation that got collected on it in the freezer.
bipinsen said:
I would try to give better advice than just saying to put it in the freezer. I can't wait to hear someone reading this and doing it. Then pulling their phone out, connecting it, and seeing it go pop fizzle as the motherboard shorts out through all the condensation that got collected on it in the freezer.
Click to expand...
Click to collapse
have you not read around the hd2 section yet? there are hundreds of posts/threads talking about chilling the phone to get past a stuck flash.
Google 'xda hd2 freezer'
well....... im with you and this being hardware issue,
i did
task29
flashed radio
flashed maglder
flashed cwm 150
flashed rom (that needed 150)
all working ok for few hours put it in my pocket , then when i took it out i had a white screen
at least rebooting it i get android back. its out of warrenty now so i guess this is the end of the road for it, had this phone for over 2 years now and tbh its had a lot of stick, its had android on it from july 2010 when it was darkstone \ mattc days, i only brought it out of retirement coz me galaxy nexus is off for replacement (stock(hardware issue))
thanks for your input,
rip hd2!!!!!!!!!!!!!
samsamuel said:
have you not read around the hd2 section yet? there are hundreds of posts/threads talking about chilling the phone to get past a stuck flash.
Google 'xda hd2 freezer'
Click to expand...
Click to collapse
I've also read that in response to having the digitizer go dead and dropping the phone in water. Doesn't mean when giving the advice one shouldn't also give a few words of warning. Have you actually ever done this? I have. This advice has been around for years, and crops up across a variety of electronic devices. Try Googling "hard drive freezer fix" or "ipad freezer fix." Just because it shows up as hits on Google doesn't mean that the physics of the potential problems change.
bipinsen said:
Doesn't mean when giving the advice one shouldn't also give a few words of warning.
Click to expand...
Click to collapse
ahh see now you're touching on the dilemma as to whether one should simply offer a suggestion, or whether one should always assume the reader is stupid and offer not only suggestions, but hand-hold the reader through the process. (an assumption i despise, BTW, why should everything be aimed at the lowest common denominator? If someone offered me a suggestion, i'd take their answer and read around the subject, if someone else chooses not to do that and just blindly leap into the unknown, based on a single response, that's their lookout)
Have you actually ever done this? I have.
Click to expand...
Click to collapse
Yea, a coupla times.
This advice has been around for years, and crops up across a variety of electronic devices.
Click to expand...
Click to collapse
Pretty much anything that can overheat, in fact.
Try Googling "hard drive freezer fix" or "ipad freezer fix." Just because it shows up as hits on Google doesn't mean that the physics of the potential problems change.
Click to expand...
Click to collapse
I suspect that if you did the maths, you would find the moisture level of air in a freezer to be several times lower than , for example, the air in a sweaty pocket on a warm day, so the chances of condensation are pretty slim. Compared to all the other 'potential problems' this phone faces, condensation from being in the freezer is pretty low on the list.