Related
so i think my wing may be in the process of biting the big one. A few days ago, my wing restarted itself for no reason, i figured it was probably a system error and didnt think twice about it. Now all of a sudden my wing will constantly restart, sometimes in the middle of a call. Sometimes when it does restart the screen will either turn white or fade to white. I reinstalled the original rom to see if it was a software issue and it is still doing it. Also, it doesnt normally do it when it is just sitting there, and sometimes i cant turn it back on. Any ideas?
Make sure the battery isn't loose inside the case... and that all the prongs are making contact.
For the life of me, i cant figure it out. I know it has to have something to do with the phone not getting power. At this point, it wont even fully turn on. Short of taking it apart and checking the solder, does anyone have any ideas?
dcmtnbkr said:
For the life of me, i cant figure it out. I know it has to have something to do with the phone not getting power. At this point, it wont even fully turn on. Short of taking it apart and checking the solder, does anyone have any ideas?
Click to expand...
Click to collapse
If you already reflashed the original rom, and it is still doing it, that tells you it is definitely a hardware issue. It does sound like it's losing power which could be a host of things. (loose battery, defective battery, loose solder on board, etc) I would try what duprade said, and check to make sure your battery has a good connection first. If you had a friend that had a wing as well, you could try his to make sure it's not the battery.
dougstoner said:
If you already reflashed the original rom, and it is still doing it, that tells you it is definitely a hardware issue. It does sound like it's losing power which could be a host of things. (loose battery, defective battery, loose solder on board, etc) I would try what duprade said, and check to make sure your battery has a good connection first. If you had a friend that had a wing as well, you could try his to make sure it's not the battery.
Click to expand...
Click to collapse
Brand new battery (free from tmo to replace the dynapack) Everything on the mainboard looks like it is soldered well. There is an internal watch batter though, could that have something to do with it?
dcmtnbkr said:
Brand new battery (free from tmo to replace the dynapack) Everything on the mainboard looks like it is soldered well. There is an internal watch batter though, could that have something to do with it?
Click to expand...
Click to collapse
I doubt it. I would guess that's the cmos battery. If that were to go, then your phone wouldn't keep time, but that wouldn't stop your phone from functioning. (I used to work in the service center at a computer store).
maybe its the processor then. sometimes, after it freezes, it artifacts before shutting off
dcmtnbkr said:
maybe its the processor then. sometimes, after it freezes, it artifacts before shutting off
Click to expand...
Click to collapse
There is the possibility of you overclocking your phone, and it heated up and could have burned or cracked some solder. It might even be overheating and that's why it reboots. At any rate, it def. sounds like hardware though. Sorry man. You could try to resolder the connections on the board just to make sure, but it sounds like you have a paperweight. Is it under warranty or do you have insurance?
only ever oc'd once, for a few minutes, and not very high (like 267 i think) It's on right now on the power cable (this wouldnt work yesterday) I honestly have no fricken clue whats going on with it.
Is it possible for the battery to completely diminish itself without being used for a day? Before it died on me last, it had a full battery, now it is showing 1% (and charging).
By the way, as I stated above, it is a brand new battery sent to me by tmo.
Dang it all! Stupid thing just shut off again... ARG!!!
dcmtnbkr said:
Dang it all! Stupid thing just shut off again... ARG!!!
Click to expand...
Click to collapse
Hey dcmtnbkr. I seem to have the exact same problem with my Wing. It shuts off for no reason, and it does it absolutely randomly. Sometimes it would work for 3hrs straight no matter what i use it for. And other times it shuts off every 30sec. and it takes 3 to 10 tries to turn it back on(most of the times it would not get past the windows mobile welcome screen). I was gonna flash it with the newer Rom, but i'm afraid that the damn thing might shut off during flashing . So i'm stuck. If you find the way to fix it - please let me know.
actually, i just talked to tmo, and apparantly NOW after i told them I'm cancelling when my contract is up, now they can apparantly cover it under manufacturer warranty (as opposed to the last time i called about a week ago) I would call them even if you didnt buy it from them, tell them you dont remember where you bought it, but it was some company online. These phone's arent that old and you may still be under the manufacturers warranty. Also, i would try and flash it back to the original. These phones are very hard to brick, and i would ask around to see if a powerdown in the middle of an upgrade would do it. I just got mine to reflash without a problem.
my wing rstarts itself wen i jus tap the back of it where the battery cover is but it wont restart everytime. anyone have any ides?
Hi, i got huge problem with my N1
Yesterday night I'v plugged my phone to charging by PC USB cable (PC switched off) and went sleep. When I wake up first I sow blue color of charging led (should be green or red), when I unplugging my phone led is still blue (this led is blue even in bootloader and recovery). After that I realize my power button doesn't work and later about I can't playing any music from speaker But I can hear all notifications. When i try call someone i can't hear anything but in speaker mode yes
Anyone know what is going on?!
What mean that blue color?
Help!!!!
P.S. I did full wipe (data+cache+ext) and flash ROM again, no different.
To be honest i dont know. But from the sounds of it, blue LED may mean "something is wrong". Maybe you have some corupt NAND? Or a Southbridge issue..... Not entirely sure. (I dont even know if ARM based devices have a SB/NB).
Sorry i couldn't help. But best of luck with finding out more about the problem.....
did you try wipe everything and reflash new/same rom ?
i suggest you do a nandroid bakcup and try it
houmles said:
did you try wipe everything and reflash new/same rom ?
i suggest you do a nandroid bakcup and try it
Click to expand...
Click to collapse
I personally think that isn't going to help(although should be done anyway), as changing the charging LED is fairly low level stuff (IE, it works without Android), so i think its hardware related and not so much software related (although software could have attributed to the issue)
So then this should be a no brainer.... call HTC
zachthemaster said:
So then this should be a no brainer.... call HTC
Click to expand...
Click to collapse
I would like, but my Nexus is ROOTed. I have no more warranty
PanPiotr said:
I would like, but my Nexus is ROOTed. I have no more warranty
Click to expand...
Click to collapse
You should still call them, see if they know what's the problem. You might have to end up paying for the fix tho.
Mokurex said:
You should still call them, see if they know what's the problem. You might have to end up paying for the fix tho.
Click to expand...
Click to collapse
I'll do this, there is no different way. But I don't know when I'll be able to send it to them, I have no money for this repair
PanPiotr said:
I'll do this, there is no different way. But I don't know when I'll be able to send it to them, I have no money for this repair
Click to expand...
Click to collapse
You shouldn't have to pay if it's a hardware problem.
Google and HTC have been really good with this warranty and rooting thing so ive heard. You should try calling them up anyway.
mattisdada said:
Google and HTC have been really good with this warranty and rooting thing so ive heard. You should try calling them up anyway.
Click to expand...
Click to collapse
Agreed. Please let us know what they say just incase that happens to one of us.
Hello
After My Hd2 resets itself it gets stuck at the "stick together" screen and freezes doesn't show the text which rom its running and radio its running. I have to take out the battery for about 10 seconds put it back in and it works. After a while it does the same thing and reset itself. I did a hard reset the problem is still there. Any help would be appropriated
sounds like you flashed a custom rom and didnt match the radio.
oh wait, this is tmous section, all the radios work with all the roms. Hmm, did you task 29 and not flash yet? that would give grey screen with no writing.
samsamuel said:
sounds like you flashed a custom rom and didnt match the radio.
oh wait, this is tmous section, all the radios work with all the roms. Hmm, did you task 29 and not flash yet? that would give grey screen with no writing.
Click to expand...
Click to collapse
All radio's DO NOT work with TMoUS. If a 1024 LEO get's installed with a .51 radio then it will brick it.
But it does sound like a bad custom ROM install if it goes into a cyclic boot. There is a few files that will cause this, but I suggest to re-download the ROM and install again.
Nibbley15 said:
All radio's DO NOT work with TMoUS. If a 1024 LEO get's installed with a .51 radio then it will brick it.
But it does sound like a bad custom ROM install if it goes into a cyclic boot. There is a few files that will cause this, but I suggest to re-download the ROM and install again.
Click to expand...
Click to collapse
Yeah, i already re-downloaded the roms went to kumars then back to energy problem is still there. =(
yea sorry I worded that sloppily. what I meant was that any tmous rom would boot regardless of the radio, assuming the radio was a tmous.(us with regular leos get that grey screen with no rom info when we flash a tmous rom with our original radio, and won't boot till the radio is changed. a situation that tmous users will never come across)
cambxo, have you checked the battery connection pins? People have experienced symptoms similar to yours (resetting and never getting past the boot screen) when one or more of the little gold pins gets bent. Can't guarantee that's the issue, but it's worth a look.
Cambxo said:
Hello
After My Hd2 resets itself it gets stuck at the "stick together" screen and freezes doesn't show the text which rom its running and radio its running. I have to take out the battery for about 10 seconds put it back in and it works. After a while it does the same thing and reset itself. I did a hard reset the problem is still there. Any help would be appropriated
Click to expand...
Click to collapse
Send the phone back to Tmobile and get it replaced mine was doin the same thing and it happend to be that my HD2 had a bad processor.
sirphunkee said:
cambxo, have you checked the battery connection pins? People have experienced symptoms similar to yours (resetting and never getting past the boot screen) when one or more of the little gold pins gets bent. Can't guarantee that's the issue, but it's worth a look.
Click to expand...
Click to collapse
holy cow it worked! thanks bro!!!!!!!
ndeguiera said:
holy cow it worked! thanks bro!!!!!!!
Click to expand...
Click to collapse
lol no prob! I figured it was a longshot, but I'm glad it worked for you
hmm, looks like my phone resets itself after heavy usage like watching transformer, running garmin or surfing the web....Does anyone have any possible solution? Before i contact t-mobile and try to get a replacement?
Cambxo said:
hmm, looks like my phone resets itself after heavy usage like watching transformer, running garmin or surfing the web....Does anyone have any possible solution? Before i contact t-mobile and try to get a replacement?
Click to expand...
Click to collapse
You sure your battery charge pins aren't bent too? I bent some pins on my touch pro and it never worked right after that. Even though I straightened them out. Lots of resetting and freezing.
crisisinthecity said:
You sure your battery charge pins aren't bent too? I bent some pins on my touch pro and it never worked right after that. Even though I straightened them out. Lots of resetting and freezing.
Click to expand...
Click to collapse
Yeah, i checked the pins doesn't look bent.
Does it feel like it's getting hot just before it resets itself? The device will get fairly warm normally, but it's possible that you're having overheating issues, just based on the fact you've connected the issue to periods of heavy usage...
sirphunkee said:
Does it feel like it's getting hot just before it resets itself? The device will get fairly warm normally, but it's possible that you're having overheating issues, just based on the fact you've connected the issue to periods of heavy usage...
Click to expand...
Click to collapse
Nope, doesn't feel hot at all before it resets. I loaded the opera browser try to connect to espn.com after it loads half way it just freezes then reset itself. Just contacted t-mobile can't get a replacement because it was a gift. =( Anyone know any way i can get it repair or get a replacement besides t-mobile?
Cambxo said:
Nope, doesn't feel hot at all before it resets. I loaded the opera browser try to connect to espn.com after it loads half way it just freezes then reset itself. Just contacted t-mobile can't get a replacement because it was a gift. =( Anyone know any way i can get it repair or get a replacement besides t-mobile?
Click to expand...
Click to collapse
Do you use T mobile for service? Why does it matter who paid for it? That is fuct.
yeah, i use t mobile as a service..just called htc for a repair service ..just wondering if anyone can help me flash back to the stock roms?
samsamuel said:
yea sorry I worded that sloppily. what I meant was that any tmous rom would boot regardless of the radio, assuming the radio was a tmous.(us with regular leos get that grey screen with no rom info when we flash a tmous rom with our original radio, and won't boot till the radio is changed. a situation that tmous users will never come across)
Click to expand...
Click to collapse
Sorry SAMSAMUEL, didn't mean to blast ya, just wanted to put that out there just in case someone read it wrong.
Thanks for all your info out there!
so now im having this same issue...i was on the phone for like 4 hrs ...and then it just reset ...now this happens ...pins arent bent idk what to do ...it wnt even startup just keeps resetting help please
I don't think there's a solution to this problem. I went on the t-mobile forums multiple of people are having the same problem as we are. I called t mobile last week and got a replacement. I guess that's the only solution. Try calling t mobile and getting a replacement.
sirphunkee said:
cambxo, have you checked the battery connection pins? People have experienced symptoms similar to yours (resetting and never getting past the boot screen) when one or more of the little gold pins gets bent. Can't guarantee that's the issue, but it's worth a look.
Click to expand...
Click to collapse
Wow, thank you very much. Though i brick mine until i saw this. Thank alot. That's a bad design for pin heh?
I have been encountering a strange problem with every 2.2 flash I have done. After a random amount of time the sensitivity of the touch screen fades away until it becomes completely unresponsive. Then if I lock and unlock the phone it will work again for a while. It seems if I keep doing something on the screen it wont do it, but if I let it sit for a few seconds it happens. Sometimes it starts to act up right after the flash and other times it takes 10-12 hours.
I have had the exact same problem with DL30 and EB01 clean and stock versions. I have disabled and removed voodoo before any changes, I have wiped wiped and wiped again. I even did the D101 odin package then worked forward. I have let it sit unchanged for hours after the flash not letting it update anything same result. Launcher pro Tw, same result.
I guess I am fine with my wonderfully working DL09 Superclean but without getting past this I am at the end of my road for all the development goodies, and I want flash!
Anyone have any ideas??
dw77x said:
I have been encountering a strange problem with every 2.2 flash I have done. After a random amount of time the sensitivity of the touch screen fades away until it becomes completely unresponsive. Then if I lock and unlock the phone it will work again for a while. It seems if I keep doing something on the screen it wont do it, but if I let it sit for a few seconds it happens. Sometimes it starts to act up right after the flash and other times it takes 10-12 hours.
I have had the exact same problem with DL30 and EB01 clean and stock versions. I have disabled and removed voodoo before any changes, I have wiped wiped and wiped again. I even did the D101 odin package then worked forward. I have let it sit unchanged for hours after the flash not letting it update anything same result. Launcher pro Tw, same result.
I guess I am fine with my wonderfully working DL09 Superclean but without getting past this I am at the end of my road for all the development goodies, and I want flash!
Anyone have any ideas??
Click to expand...
Click to collapse
Going to sound completely random, but are you using an aftermarket charger? Or is this not happening on dl09?
jenisiz said:
Going to sound completely random, but are you using an aftermarket charger? Or is this not happening on dl09?
Click to expand...
Click to collapse
Stock charger and not happening on DL09. It does it really bad (2.2) whenever the charger is plugged in, I have heard this is a known issue. Perhaps somehow related to my problem?
do you run aLogcat or anything like that? I would wonder if there is anything logged by the system when this happens...
M00NEY said:
do you run aLogcat or anything like that? I would wonder if there is anything logged by the system when this happens...
Click to expand...
Click to collapse
No, I do not. Normally I do not post and ask questions as I prefer to figure them out myself, but I am truly at a loss!
dw77x said:
No, I do not. Normally I do not post and ask questions as I prefer to figure them out myself, but I am truly at a loss!
Click to expand...
Click to collapse
I have actually noticed this issue a couple times also, completely annoying. And certain spots on the screen that will go unresponsive, but only certain spots, and if I lock/unlock, it will start working again, REALLY annoying when trying to send a text message.. and its always different parts of the screen.
this dosent help but i have the same problem at least we not alone
micdawg12 said:
I have actually noticed this issue a couple times also, completely annoying. And certain spots on the screen that will go unresponsive, but only certain spots, and if I lock/unlock, it will start working again, REALLY annoying when trying to send a text message.. and its always different parts of the screen.
Click to expand...
Click to collapse
Yes, I forgot to mention it happening in certain spots, then eventually the whole screen.
It "seems" to me that the touch screen is prematurely shutting down with the back light still on. Although, sometimes this happens right after I unlock it. Grrr frustrating!
bubbleywine said:
this dosent help but i have the same problem at least we not alone
Click to expand...
Click to collapse
How bad have you had it? bad enough to flash back to eclair or have you been dealing with it? It drove me nuts, I went back. I sure would like to figure it out though!
I believe it has something to do with the charger either being incompatible with the phones hardware or software. I bet the issue disappears the second you disconnect the charger too doesn't it? Mine was doing the same thing. I bought another charger directly from verizon at the store and it resolved my issues. I realized it after hearing a few complaints on the forum. I had an issue like this once before on my Samsung Moment...and it fried my phone.
jenisiz said:
I believe it has something to do with the charger either being incompatible with the phones hardware or software. I bet the issue disappears the second you disconnect the charger too doesn't it?
Click to expand...
Click to collapse
First I have the charger that came with the phone so I don't think that is the problem. Second I do have the problem much worse when plugged it. But it still persists with it un plugged, to the point of it being un usable.
jenisiz said:
I believe it has something to do with the charger either being incompatible with the phones hardware or software. I bet the issue disappears the second you disconnect the charger too doesn't it? Mine was doing the same thing. I bought another charger directly from verizon at the store and it resolved my issues. I realized it after hearing a few complaints on the forum. I had an issue like this once before on my Samsung Moment...and it fried my phone.
Click to expand...
Click to collapse
I have the issue on and off the charger, mostly off.. I don't think thats the case.
dw77x said:
First I have the charger that came with the phone so I don't think that is the problem. Second I do have the problem much worse when plugged it. But it still persists with it un plugged, to the point of it being un usable.
Click to expand...
Click to collapse
Yeah for me it ended up being the charger. Dunno, maybe something happened to your port or it got damp and fried something...but I'm telling you, exact same issue happened to me. I couldn't use my phone when it was plugged in. Haptic would go crazy and I couldn't text. Got used to unplugging it when I wanted to send a text. Then after about a week, the issue started happening to the phone after it was unplugged. Took it in and sprint voided my warranty on that one b/c they said I'd fried the port by using an unauthorized charger.
jenisiz said:
Yeah...it's as a result of the charger. Dunno, maybe something happened to your port or it got damp and fried something...but I'm telling you, exact same issue happened to me. I couldn't use my phone when it was plugged in. Haptic would go crazy and I couldn't text. Got used to unplugging it when I wanted to send a text. The after about a week, the issue started happening to the phone after it was unplugged. Took it in and sprint voided my warranty on that one b/c they said I'd fried the port by using an unauthorized charger.
Click to expand...
Click to collapse
Not saying I don't believe you but why does it work fine on any eclair setup if it's a physical/damage issue?
dw77x said:
Not saying I don't believe you but why does it work fine on any eclair setup if it's a physical/damage issue?
Click to expand...
Click to collapse
No, re-worded my phrase. It was for me. No idea how or what happend. To this day it bewilders me. It's possible that if the amount of voltage required to run can be tampared with, then who knows what else can be? People fail to understand that phones are no different from computers. You plug a buggy power supply into a main board and it's highly likely things will get fried or damaged. Especially if you start messing with the bios and try to overclock/underclock.
Most logical way I can explain it is by using cars as an example. Different grades of gas are not equal. If you're vehicle needs to run lean and you start filling her up with unleaded, you might get away with it for awhile...but after bit, your engines gonna start knocking.
jenisiz said:
No, re-worded my phrase. It was for me. No idea how or what happend. To this day it bewilders me. It's possible that if the amount of voltage required to run can be tampared with, then who knows what else can be? People fail to understand that phones are no different from computers. You plug a buggy power supply into a main board and it's highly likely things will get fried or damaged. Especially if you start messing with the bios and try to overclock/underclock.
Click to expand...
Click to collapse
I guess when an oem Froyo comes out <sinkers quietly> I will odiin back to E101 and try and ota and see what happens.
jenisiz said:
Most logical way I can explain it is by using cars as an example. Different grades of gas are not equal. If you're vehicle needs to run lean and you start filling her up with unleaded, you might get away with it for awhile...but after bit, your engines gonna start knocking.
Click to expand...
Click to collapse
Not to bash Samsung but sheesh, if they are that fussy, I will probably not buy again.
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?