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.....
Hey there,
I've been learning from XDA for a while.
On the last few months I rooted, flashed and put on some stamina on my htc hero gsm.
Finally I had it in good shape, and stopped fiddling about. I was pretty happy with my "new" hero.
Unfortunately, about two days ago, it went off by itself, while sitting on my desk.
I tried to get it back on, but no signs of life.
Holding the power button, I got nothing.. no lights, vibration, not at all.
Tried holding the menu to get to recovery, but the thing still don't move.
Checked the battery.. over 4v, almost full. Tried an old battery.. nothing.
Connected the charger.. not even the yellow light came on.
So, I guess this is it.. or there is anything else I can try?
Was anyone there? did anyone came back?
Repair shop is not an option to me.. here in Brazil, competence is rare and expensive.
I'll miss my htc, it's time to clean the dust from my N95 8Gb.
Well if you dont get the yellow light, and the fact it went off while it was used not flashed, i would say that is a hardware failture
kemoba said:
Well if you dont get the yellow light, and the fact it went off while it was used not flashed, i would say that is a hardware failture
Click to expand...
Click to collapse
So, nothing can be done? Is there any guide for troubleshooting mobile hardware for dummies?
Thanks anyway..
Hi there, my first post. Thank you for all of the great resources and contributions on here. I really appreciate all of this info and enjoy learning more about Android.
I had my 1.5 year old Verizon Note 3 (SM-N900V) that was acting weird so I warrantied and got a new one 2 months ago. It has been working great ever since. I have not rooted the phone or anything, running all stock software, Android 5.1.1. Last Tuesday I pulled my phone out of my pocket after lunchtime (had just spoken to my wife, sent a couple texts, you know the normal stuff maybe 30 minutes before) and it was dead.... I thought it was weird, thought maybe it just turned off o something, battery was about half full the last time I saw it. But nothing, nada, no response from leaving plugged in for a couple hours to charge. No vibrate on power+vol down+home button, not so response no vibrate from power button alone.
I have tried the mje and nc2 unbrick image with Win32Disk imager and am still getting zero response from the phone. Using a 32gb micro sd formatted to exfat. also tried fat 16.
I thought that I read when a phone is hard bricked and you are using the method with the unbrick image file on a micro sd card you will still get a vibrate when holding the buttons down even it the screen doesn't turn on? I am getting no response whatsoever.
I'm def. a newb in terms of my android rooting and flashing ROM's experience, I have only experimented with 2 different phones.
I have a feeling the phone is toast but I'm so confused by how it died... Wondering if maybe they sent me a refurb device when I warrantied it and it was just volatile? I'm also temped to order a new motherboard for it off of ebay but again I don't know enough to determine if it would work or it this is just a crapshoot. I am due for an upgrade but was hoping that I wouldn't have to upgrade for a few more months until the Note 5 drops in price a little, I was even going to just get the Note 4 because it has a microSD slot but it's the same price as the Note 5! I am using my old school Galaxy Nexus for the time being and it's killing me, the thing is a dinosaur!
Any help is appreciated.
Try to change out your battery in case battery is bad. It's cheaper and easier than motherboard swap. It sounds like no power to phone.
Would the battery just suddenly decide to go bad like that?
HueyT said:
Try to change out your battery in case battery is bad. It's cheaper and easier than motherboard swap. It sounds like no power to phone.
Click to expand...
Click to collapse
It doesnt seem to be hard bricked. Its sounds like a hardware issue. Like he said buy a cheap $5 battery to find out. And yes batteries do short and die very fast. If it was a replacement phone it was a refurbished one and you never know, that could have been the original problem with your replacement phone. You can get another mobo but you be careful that its doesn't have a bad imei.
If I helped Hit the Thanks Button Like This?
new battery
S2_brickmaker said:
It doesnt seem to be hard bricked. Its sounds like a hardware issue. Like he said buy a cheap $5 battery to find out. And yes batteries do short and die very fast. If it was a replacement phone it was a refurbished one and you never know, that could have been the original problem with your replacement phone. You can get another mobo but you be careful that its doesn't have a bad imei.
If I helped Hit the Thanks Button Like This
Click to expand...
Click to collapse
Ok I will try it. Thanks! The reason the battery thing threw me off is because when I called verizon to warranty it, I thought I would have to purchase a new battery because mine was 1.5 years old, but when I put it in the replacement phone (it didn't come with a battery so I had to use the original one) it worked great.
I broke down and bought the Note 5 last week. I like it, but I'm not as impressed as I was when I first got the Note 3. We'll see how it goes but it would be nice to fix the Note 3, root it and try a new rom on it, I haven't done that in a while.
Thanks again!
First of all, hello to all Note 4 owners and my deepest sympathies to those affected by this "bug" (whatever it actually is).
I got used Note 4 in March 2016. It was trade in for my Sony Xperia and guy told me he had it for around a year. I liked this nice device. It had great display and served me very well. Excellent, even better term.
It was until December 2016 when dreaded bug appeared, and I knew nothing about it at the time. You already know it - lags, restarts, freezes, unable to turn on, going to download mode, harder and harder to start up...
How it happened is what amazes me most. I have 2 batteries, both original. I exchange them sometimes when I am on longer time without charger. This night (before it all happened) I let phone charge down to 0% because it showed false % in battery bar. It would die at 15% and not charge over 92% for example. This was factory battery and not my spare one I got later. I found out battery % is reset each time I let it charge down all the way, then after it shuts down I charge it up and it fixes the percentage bar temporarily. Anyway, as I was saying, that night (day before I experienced the bug) I wasn't in a good mood and phone died on me sometimes in the early night. I was annoyed and I started up the phone, it got to homescreen then shut off because it was empty. I did it again. This time it got to boot animation. Again. Again. How foolish of me. I did it until phone couldn't be turned on at all. Then I set it up to charge and left it overnight. Tomorrow I took it and left to work. It was peak 100%.
Around 10AM I got some messages on facebook messenger, and I wanted to check them out and reply, I took a break from working. In middle of my typing, phone simply froze. Froze, it wouldn't react to physical buttons, virtual keyboard, nothing. Screen was on non stop with frozen facebook messenger, virtual keyboard on screen and my unfinished message.
I took out battery and turned it back on. Phone was never the same since then... First "light" freezes and after second or two it "let's go" and all messages I typed appear instantly in messenger. Sometimes I press power button to wake device it wouldn't right away. It was getting harder and harder... after investigation I learned about this production "flaw" from samsung, I've read many pages about this error, many of those here on XDA (by the way community here is wonderful)...
I bought another device because Note was getting in state of unusable. I left it alone on table and it stand there for some time.
I couldn't give up it's wonderful screen, power, pretty TouchWiz... and after I've read a lot about this, I decided to buy new motherboard. I got one from ebay in late August and it arrived sometimes in middle September. 60 US dollars. I asked seller will all functions work, is IMEI blacklisted, is WI FI working, does it has good memory chip (which is culprit for bug it seems) and seller kept saying to me everything works, is tested one by one before shipping, and he said "it must work, 1 year warranty!" I smiled a bit, it's how he said it.
I ordered also some tools for disassembling phone as I wanted to do it myself. Very cheap, 7$ and there is everything there, really nice kit. It got to me before motherboard. Then it arrived. Same night I wanted to do it, I couldn't wait to use my note again. I missed it.
One friend at work which owns mobile store and repair, told me to wait until tomorrow, he will do it for cheap but I was not patient enough. I thought I can do it. After couple of youtube videos I started it... Bottom line is I didn't heat up the device to loosen the glue and I ended up breaking the screen... And couldn't attach screen to motherboard, because Samsung made it hard without removing the screen too. I went to my friend and he scolded me for not waiting few hours and eventually found me used screen for 75$ more... They are 150$ around but he took it from some friend of his own to help me because he felt sorry and he got that friend's phone, got out the screen and transplanted it to my motherboard and casing over for free. I have working Note again...
Now, I don't know what to do with it? Do I sell it? Use it? I felt free to attach some screenshots from it, to add up to collective knowledge of XDA (it was my intention with this story in the first place). Who knows... maybe some info from here might help someone, sometimes.
Phone info showed my phone (motherboard) is made in 01.2016. Brickbug check app can't identify the memory chip (shows production date as 11/1999 which is not possible for note 4). It is fast now, one screenshot proves it. Friend said he stress tested the board (whatever it means) and it seems fine. All functions work, I tested everything too. Board color looks different - shade of green is different. KNOX warranty void status 0x0.
What is opinion of fellow XDA's about this? Do I use this thing, sell it... it cost me more than it's worth, and selling it will be just extracting mere costs I invested. But I like the device... I feel like just going through with it, whatever happens this time... maybe my pain with emmc fail is over.
Maybe some other members reading this, can screenshot their brickbug check app statuses? Those which have "healthy" devices and those having emmc issues too? Maybe we can build database of good chips, and which devices may be "safe"... I will sure add my results here in attachments.
I wish everyone owning this good little device much luck and as less problems as possible...
PS Mods can move thread to some other one regarding this issue but I'd like it stays thread of it's own... but I will conform to decision of Mod team. This is wonderful and helping site, thanks goes to owners which built it and mod team keeping the order, as well as userbase for contributing to collective knowledge and "hacking" the android and devices in a good way.
StreetKing
Two and a half years and still no issues. I'll gladly contribute to your database since I seem to have one of the "good" chips.
Sorry for the capslock, but I really want my OP5 back, i miss the screen, the battery life, which would be even better now because i have a brand new one in it, and it still is nothing more than a paperweight.
I have an OG Pixel XL thats snappy enough after a custom kernel, but the battery life is absolute sh*t, and it has half the RAM.
I didnt see anything damaged, i checked every port, connector, and junction with an endoscope out of sheer curiousity.
This all started about 4 months ago, driving home, and i was at a red light, got a text, started to respond, and it just quit.
I tried everything, new firmware, new OS entirely, aforementioned I replaced the screen & battery.
I've just recently gotten around to replacing the screen, and i was so hopeful and excited, I've never cried over a smartphone but after you slave over one for almost 3 1/2 hours, you become attached to it.
Well, I did.
Either way, I love this phone, and i'm praying there's someone who would look down on me in pity with my half-the-time-not-lasting-a-night-while-not-even-DOING-ANYTHING-Pixel XL-self
lss: i have a mint condition paperweight, please God send someone to help me.