I did everything so PERFECTLY to change my housing, organizing everything in each step so I can do it efficiently.
Well I put it back together, all excited to turn it back on ...it vibrates but does not display anything. FML
I disassembled the WHOLE THING AGAIN! Put it back together... still nothing.
**** it.
I guess I'll be using my Dash again for a while :/
Most common is the flex cables that run from the lcd to the keyboard area. I bet one is torn or cut. I have a cut one to prove it happens I have heard of others having the same issue. They are just very delicate
I thought that could be the case, but I have examined them multiple times, they're flawless. Maybe it's just a minuscule cut that I'm not seeing, but **** I'm gunna get so annoyed using my Dash.
Every time I went back to my old Dash I was reminded of the good old days of rebooting daily. Yet I still keep my eyes open for a Dash 3G on CL for a good deal to become my new "spare"- when I find one I can finally retire my old beat up Dash for good
I'm already dreading using Windows Mobile again hahahah
sorry to hear that, I hate when things like that happen... hopefully I will learn from this and I hope I do a better job on my own (no offense to you though, haha)
try something please as i'm curious of your problem. start the phone up and use the most powerful flashlight you have and see if the lcd is working or not. i'm curious if it is the backlight, lcd, or flexicable.
i have had my vibrant for a few weeks and i charge it nightly(due to low battery so don't say over charging) and every morning i wake up and the screen is on but totally black, and the capacitive buttons are lit up but don't do anything. the only way to fix it is to pull the battery and reboot the phone that way. also the phone seems to be getting EXTREMELY hot while charging(in a case or not). this morning when i woke up i had to pull the battery yet again except for this time when i turned the phone on, the screen was wonky. the bottom half of the screen does not come on, and there is a vertical pink line through the rest of the screen, and the touch screen no longer works. i will be calling t-mo later this evening to get a replacement but i would think that this shouldn't have happened. i was more than willing to deal with the overheating on the charger but now that the screen doesn't work i have to use a STOCK mytouch that absolutely blows.
if anyone has any suggestions or has seen this before please comment i would love to know what caused this so i can avoid it with the new phone.
P.S. no physical damage or water damage so those are both out too
Sounds like a faulty unit, get it exchanged. Sounds like a bad connection causing a short.
Sent from my GT-I9000M using XDA App
I ran into the overheating problem and the Screen not turning on when i was messing around with underclocking mine and had my settings all messed up. Dont know if you are doing that or not. The other part def sounds like a bad unit.
Do you have setcpu installed? It seems to cause issues similar to this.
Sent from my Vibrant
The phone is actually used mainly by my fiancee, so only thing done was root, lag fix, and vibrant6, but after som overheating issues I removed lagfix and never installed setcpu or anything else to OC the CPU. Called tmo, they have a replacement on the way but it still seems off that this would happen.
Sent from my T-Mobile myTouch 3G Slide using XDA App
This has happened once before, but just for a small amount of time to to the heat (I believe). The phone has been off for over and hour and refuses to turn on whether I hold down the volume button, don't hold down the volume button, or push the battery in at the exact time as I'm doing the other one or two. The splash screen flashed for half a second and immediately went back off when I plugged my evo charger, the usb part, into my portable ipod charger, so I believe this means there is still help available! Last time this happened, which was months ago, it seemed as if it just needed to cool down a bit, and my reading on the internet confirmed that the phones shut off when their batteries reach too high of temperatures. So what I did was wrap the phone and the battery, separately, in a large wash cloth and let them sit it the fridge for a little while. No luck, I'm running out of ideas (and I realize a ziplock bag may have been better but who cares). A few days ago I installed cm7gginggerbread7 (wimax) over cm7gingerbread2, but have not had any issues up until now and everything has run perfectly as well as smoothly. Is there any way I can turn my brick into a phone? Perhaps there's a way to adb something even though the phone wont boot (im a noob). I'm just pissed cuz I finally got every little thing exactly the way I wanted it, and now I'm stuck with a paperweight :/ I thank you for all your help, brave knights
It just suddenly shut off and won't turn back on?
And you weren't messing with anything?
If so, sounds like it's a hardware or battery issue.
Can you try a different battery?
Does the charging light come on when you plug it in? It could be a dead battery, and if the charging port is broke, it wont charge.
Otherwise, it seems like a hardware issue. I would take it to sprint, and they should be able to replace it for you.
sitlet said:
Does the charging light come on when you plug it in? It could be a dead battery, and if the charging port is broke, it wont charge.
Otherwise, it seems like a hardware issue. I would take it to sprint, and they should be able to replace it for you.
Click to expand...
Click to collapse
But it has teh rootz!!!!!!!!!
Smash that mofo with a hammer and call Asurion!!!!!!
jk
matt2053 said:
But it has teh rootz!!!!!!!!!
Smash that mofo with a hammer and call Asurion!!!!!!
jk
Click to expand...
Click to collapse
If they can't get it to power on then it really doesn't matter if it's rooted or not because they won't be able to find out.
Well I was messin with it a couple days ago, flashed gginggerbread6 w/ wimax over gginggerbread2 after wiping cache and dalvik and of course making a nandroid. I was thinking of smashing it but I've gotten everything they way I want it for the thousandth time. I'm also reluctant to do it because this issue has resolved itself in the past, albeit a tad quicker. For christ's sake, it even fixed itself for half a second this time, just enough to show me the splash screen lol. I'm very gentle with my evo and have never had any problems that weren't easily resolved with a little bit of work. I guess I could smash it until it works, and then if it ends up breaking then I win either way, but I'd really like to get my darling fixed. I know it's nothing compared to the cyanogenmod team, but I've flashed and flashed (almost always to cyanogenmod, what can I say it's perfect) and I have FINALLY got everything set up the way I wanted it, which includes manually going through and changing all the icons to custom pngs lol.
I guess I just don't understand why this would happen all of a sudden like this, I've onlu had it for three or four months, htc can't make that shotty of work can they? The other thing is I have a battery widget so as to make sure my battery does not get to hot, as well as having a setting in setcpu which stops overheating if it should ever occur. I really have a feeling it's something which can be fixed just because it has been magically fixed in the past and it was "fixed" for half a second today. Is there any way to adb into recovery even though the screen is black? Any suggestions help, I have important calls coming in as well as rather important calls to (hopefully) future employers. Of course I also don't want people to think that I am ignoring them, which isn't quite as bad but I still try to be as rude as possible :/
So...any ideas guys Don't wanna sound like I'm fishing for compliments, but you all are by far the best in the field. Keep up the good work (on my phone haha) Thanks so much for the advice you're going to give me on how to fix this up so I don't miss all my friends calls and texts until I get pissed off at. Later trooper
EDIT: Sry got block of text. tl/dr fix my evo that wont turn on asap thx
Raillery said:
Well I was messin with it a couple days ago, flashed gginggerbread6 w/ wimax over gginggerbread2 after wiping cache and dalvik and of course making a nandroid. I was thinking of smashing it but I've gotten everything they way I want it for the thousandth time. I'm also reluctant to do it because this issue has resolved itself in the past, albeit a tad quicker. For christ's sake, it even fixed itself for half a second this time, just enough to show me the splash screen lol. I'm very gentle with my evo and have never had any problems that weren't easily resolved with a little bit of work. I guess I could smash it until it works, and then if it ends up breaking then I win either way, but I'd really like to get my darling fixed. I know it's nothing compared to the cyanogenmod team, but I've flashed and flashed (almost always to cyanogenmod, what can I say it's perfect) and I have FINALLY got everything set up the way I wanted it, which includes manually going through and changing all the icons to custom pngs lol.
I guess I just don't understand why this would happen all of a sudden like this, I've onlu had it for three or four months, htc can't make that shotty of work can they? The other thing is I have a battery widget so as to make sure my battery does not get to hot, as well as having a setting in setcpu which stops overheating if it should ever occur. I really have a feeling it's something which can be fixed just because it has been magically fixed in the past and it was "fixed" for half a second today. Is there any way to adb into recovery even though the screen is black? Any suggestions help, I have important calls coming in as well as rather important calls to (hopefully) future employers. Of course I also don't want people to think that I am ignoring them, which isn't quite as bad but I still try to be as rude as possible :/
So...any ideas guys Don't wanna sound like I'm fishing for compliments, but you all are by far the best in the field. Keep up the good work (on my phone haha) Thanks so much for the advice you're going to give me on how to fix this up so I don't miss all my friends calls and texts until I get pissed off at. Later trooper
EDIT: Sry got block of text. tl/dr fix my evo that wont turn on asap thx
Click to expand...
Click to collapse
If this occurred while you were NOT changing anything with the radio partition or recovery partition then it's not a brick issue.
Sounds like you have a hardware issue.
Take it to the store.
If you smash it you will be paying $100 to asurion for a replacement as Sprint changed the TEP again.
Just wondering was your battery completely dead before this happened. I have read some people here and other places have said that if the battery completely dies that it won't charge unless you put it on a actual battery charger made for it. Does the charge light come on when you plug it in? Also, like my friend before me said, take it to Sprint. Ask them if they have a battery you could try. If it doesn't work it will eliminate the battery being the issue. If it won't boot they will replace it. They won't be able to tell if it is rooted because it won't boot. If you were flashing a radio and didn't let it finish or the battery died during the process, you are bricked.
Does the charge light flash when plugged in?
Sent from my PC36100 using Tapatalk
The light doesnt change
clean off the battery contacts
the same exact thing happened to me. i read in another post that the TP2 battery was a suitable replacement, so i checked the VDC and mA and they were exact and also the contacts were in the right place. (looks exactly like the evo batt just black instead of red in retrospect). It was a good call on the TP2 battery. My evos batt died on me tonight while it was charging. no light while plugged into OEM wall charger, no blinking, nothin, I wasnt even using it, never had a problem before. luckly i was just chargin up my old TP2 to give to my girlfriend. popped in that battery and the evo came right up. popped the evo battery in my TP2 and it appears to be charging. curiously the evo appears to be charging the tp2 batt now aswell. so i dont know what happened... one positive thing is that i know i have 2 batteries now. a negative is that my gf cant have my TP2 untill i get this sorted.
anyone have any insight as to what is goin on? or why this happened? if my charging port has gone bad why is the tp2 batt charging in the evo? and if the evo battery went bad why is it charging in the TP2?
i am using the stock sprint evo rom. not scared to root, just havent yet.
vespix said:
the same exact thing happened to me. i read in another post that the TP2 battery was a suitable replacement, so i checked the VDC and mA and they were exact and also the contacts were in the right place. (looks exactly like the evo batt just black instead of red in retrospect). It was a good call on the TP2 battery. My evos batt died on me tonight while it was charging. no light while plugged into OEM wall charger, no blinking, nothin, I wasnt even using it, never had a problem before. luckly i was just chargin up my old TP2 to give to my girlfriend. popped in that battery and the evo came right up. popped the evo battery in my TP2 and it appears to be charging. curiously the evo appears to be charging the tp2 batt now aswell. so i dont know what happened... one positive thing is that i know i have 2 batteries now. a negative is that my gf cant have my TP2 untill i get this sorted.
anyone have any insight as to what is goin on? or why this happened? if my charging port has gone bad why is the tp2 batt charging in the evo? and if the evo battery went bad why is it charging in the TP2?
i am using the stock sprint evo rom. not scared to root, just havent yet.
Click to expand...
Click to collapse
Take the original battery to sprint. Tell them the story and get a replacement, ask for some free accessory since you've helped them isolate a reliability issue.
LOL
There are two known issues with the Evo to be aware of. The first is the charging bug. If the Evo shuts off due to low battery level there is the possibility that the charging circuit fails to recognize the dead battery as even being there and will not charge. The workaround is to charge the dead battery in another compatible phone or use an external battery charger. This is supposed to be fixed in the next update but we'll see.
The second is the thermal sensor bug. The thermal cut off starts to trigger at lower and lower temps til even freezing the phone won't work. I thought the local service center was joking til I actually saw it reproduced. This is a hardware issue and the only fix is a replacement phone.
The first issue is intermittent but knowledgeable service centers are aware of this and will either charge the dead battery or swap out with a charged one.
The second issue is reproducible but can take some time to do so depending on how far off the sensor is. Again, knowledgeable service centers are aware of this and will want to reproduce it before ordering a replacement.
Not sure what technical thong is happening, but I do know I panicked when it happened to me, bit it turns out if you try to charge EVO from a USB port while its in the recovery mode it will eventually drain and **** off. I forgot I was on recovery mode and came back to what you described. After doing the swap with my GF's EVO and realizing my battery was fine, I remembered how I had left the phone in the first place and Googled it to confirm that will cause the dead EVO scare.
Sent from a corrective lens wearing eskimo translating Turkish smoke signals viewed over a streaming webcam at 640x480 resolution via a U.S. Robotics 14.4 Hayes compatible modem.
This has happened to me twice, but since I was on the extended battery from sprint, I would just pop my stock battery in and it powered up fine. Each time I just brought my battery in to sprint and they replaced it. Also, when it happened to me the charging light wasn't turning on or anything.
Sent from my PC36100 using XDA Premium App
OK friends, same thing happening here to me today.
Here's my story: Last night, working fine, running stock turbo rom and netarchy cfs-havs-sbc-4.3.4 kernel for about a month, working great.
Used Kernel manager and flashed to cfs-suv-nohavs-nosbc and it was working great. Figured I didnt need the extra batter life/damage risk anymore. Went to sleep, phone on my bed.
Wake up today, phone is fully unresponsive. Take the battery out, put it back in, unresponsive. nothing whatsoever when holding down power, volume, etc.
When I plug it in, the orange battery led comes on and off.
:[
cjh6386 said:
OK friends, same thing happening here to me today.
Here's my story: Last night, working fine, running stock turbo rom and netarchy cfs-havs-sbc-4.3.4 kernel for about a month, working great.
Used Kernel manager and flashed to cfs-suv-nohavs-nosbc and it was working great. Figured I didnt need the extra batter life/damage risk anymore. Went to sleep, phone on my bed.
Wake up today, phone is fully unresponsive. Take the battery out, put it back in, unresponsive. nothing whatsoever when holding down power, volume, etc.
When I plug it in, the orange battery led comes on and off.
:[
Click to expand...
Click to collapse
Blinking charge light means that the battery v has dropped below the required v to turn on the phone. I see 4-5 Evo's a day like this as well as the charge bug.
I actually got it booting again somehow. Now, it consistently turns on, will boot to the bootloader, but recovery doesnt work and it wont boot into the phone. It does search for pc36 image though... i might try that.
I just sit here and shake my head on a daily basis when I see people talk about problems and inevitably, and I'm not saying this is applicable in this case, but they say in their post they were using ROM or Kernel Manager.....
My phone shuts down when i open the battery cover, it started happening a few days ago. Sometimes it turns off without opening the battery cover, but it is probably related to the problem, since it started occuring approximately at the same time. The battery doesn't move when i open the battery cover, It doesn't happen every time i open the battery cover, but it is really anoying when it happens, especially when it shuts down by itself.
EDIT: while writing this i opened and closed the back a few times, phone turned off two times
Try this.
keep Ur phone screen downward. Maintaining this scrictly open the battery cover. See if the phn is off..
Do several times. & tell me d results.
Sent from my GT-I5800 using Tapatalk
ka'cipeder said:
My phone shuts down when i open the battery cover, it started happening a few days ago. Sometimes it turns off without opening the battery cover, but it is probably related to the problem, since it started occuring approximately at the same time. The battery doesn't move when i open the battery cover, It doesn't happen every time i open the battery cover, but it is really anoying when it happens, especially when it shuts down by itself.
EDIT: while writing this i opened and closed the back a few times, phone turned off two times
Click to expand...
Click to collapse
Think this is because the screw of the back plastic, i.e. the screw which holds back the battery to the casing, check it or the wire has been broken, and in contact because of other grippers or wires from welding.
Check it out.
OR just it may be a sensor problem.
Dont know, can you upload pictures or video?
Try putting a thick piece of rolled up paper between the battery and back cover
Sent from my GT-I5800 using XDA App
RohMish said:
Think this is because the screw of the back plastic, i.e. the screw which holds back the battery to the casing, check it or the wire has been broken, and in contact because of other grippers or wires from welding.
Check it out.
OR just it may be a sensor problem.
Dont know, can you upload pictures or video?
Click to expand...
Click to collapse
It's probably the sensor, i reflashed back to 2.2 jps and there was no problem so far. So far. There is nothing wierd about the hardware of the phone, so pics and vid are useless, i compared mine with friends G3 and they look identical under the hood, probably the sensors got a bit messed up. We will see if the problem presists, but i doubt it will.
EDIT: The phone was on my desk for like 20 mins, i didn't even touch it, it turned it self off with no sign or reason or warning. I will flash stock firmware and go to SamFu*kingSuck service, i hate this phone, it always dies on me when i need it. I will never ever buy a product from samsuck again. My next phone will be HTC and i will try to get it as soon as possible. Thank you all for making this piece of junk phone better and better every day for us that got screwed by samsuck. Really, a big thanks to all developers that even bother with this junk. Sry for ranting BTW