Okay so it may be a little redundant but I'm gonna start from the beginning I bought a pixel 2 about a year and 1-2 months ago on Amazon I immediately knew I needed root and a custom ROM so I put linage on it as it was at the time the only ROM being updated I then switched to 2 others pixel dust and it was great but was missing a few features so I tried another one I'm still on and terrified to turn my phone off I'm not blaming the ROM
I went to bed the other day charging my phone got up on 100 scrolled Facebook for maybe 10-15 and it was on 78 I figured maybe I was on it longer than I thought or maybe it was too bright idk but I thought ok I'll go out and take less than 5 and I'll be back to charge it but I never got a chance the screen went black and never came back on. I plugged it in for an hour and nothing. I tryed PC it didn't show up at all no device manager nothing so I took the screen off and unplugged the battery (hesitantly) as I didn't know if it would ever work again I then used my heat gun on it set at about 445 (I don't know if it's bad solder just trying something new) I then put it back together and when I did it was in qqm 9008 (hard bricked) so I unplugged the battery again and it reboot to recovery before rebooting to the os.
Now I'm scared on what to do as I don't want the device to die incase it won't turn on again cause I lost work and can't afford another but I need to know if there's anything I can do to ensure that it doesn't happen long enough for me to flash a new ROM incase it's the ROM so please anyone with this phone that can help me out even a little would be great
Related
long story short my wizard fell in the toilet last Jan of 08.. miraculously ,it worked till now, when a few weeks ago failed to flash a new rom. now its stuck on bootloader. my wizard cannot stay on without being plugged into the wall this is a fairly new concept to me because it just started doing that lol
if the battery is taken off the phone the screen messes up (white screen with flashing bars going diagonally) of course i would find out i had to leave the phone on for a week being charged so the screen would go back to normal on its own, so i never take the battery out.
It doesn't charge via wall charger it needs the cradle which i brought separately...another defect on the phone is how the red led light which indicates i guess being charged, is ALWAYS lit..
so i went on to flash the NBDX Rom successfully maybe a month prior to the accident. it went on to satisfied me till i decided to try something new, by flashing the SimOne MD2 rom (so tempting)
so now that the flashing was unsuccessful i am stuck on bootloader because since my phone cant stand being on without being charged it will turn off after a minute, so it will NEVER go on to finish ....
well anyway, that's my story. i just thought you would know (was bored) lol maybe its time for a new phone anyway ..Well, thanks for reading my article..
It sounds like a hardware, not software, issue. I think the timing was just a coincidence. Perhaps a new battery would help. Also, try charging with an external charger. Sorry about your loss.
So I upgraded to JB via OTA yesterday with no problems. Today I'm reading an article on Chrome and the tablet screen shuts off and after a few seconds it looks like it's in the process of rebooting so I set it down and leave thinking it'll be booted up again when I come back but I was confused why it rebooted in the first place.
Anyways, about an hour and a half later I come back and my tablet is super heated to the point that it burns to touch it. The screen was blank but it looked like the backlight was on or something because it wasn't the same as if the screen was actually turned off. I held the power button down several seconds until it powered off and rebooted and then I set it down by my AC so that it could cool off. After a minute or so it booted up like normal to the main screen and it showed that the battery had drained from 95% when it first happened to 37% so it was obviously stuck doing something very CPU intensive during that hour and a half.
Does anyone have a clue what happened and if I should do something? I just bought this tablet from Best Buy yesterday without their additional warranty but should I either take it back there or possibly contact ASUS of a replacement or something? I know how bad that kind of heat is for computer components and it bothers me it was like that even for 1.5 hours. Also my tablet has not been rooted so it was completely stock save for the few apps I've installed so far.
Thanks in advance!
Had the exact same thing happen to mine about a month ago. Was worried afterwards that the excessive heat would have caused damage but so far have not seen any ill effects.
Falchion17 said:
So I upgraded to JB via OTA yesterday with no problems. Today I'm reading an article on Chrome and the tablet screen shuts off and after a few seconds it looks like it's in the process of rebooting so I set it down and leave thinking it'll be booted up again when I come back but I was confused why it rebooted in the first place.
Anyways, about an hour and a half later I come back and my tablet is super heated to the point that it burns to touch it. The screen was blank but it looked like the backlight was on or something because it wasn't the same as if the screen was actually turned off. I held the power button down several seconds until it powered off and rebooted and then I set it down by my AC so that it could cool off. After a minute or so it booted up like normal to the main screen and it showed that the battery had drained from 95% when it first happened to 37% so it was obviously stuck doing something very CPU intensive during that hour and a half.
Does anyone have a clue what happened and if I should do something? I just bought this tablet from Best Buy yesterday without their additional warranty but should I either take it back there or possibly contact ASUS of a replacement or something? I know how bad that kind of heat is for computer components and it bothers me it was like that even for 1.5 hours. Also my tablet has not been rooted so it was completely stock save for the few apps I've installed so far.
Thanks in advance!
Click to expand...
Click to collapse
I would just take it back. Doesn't seems normal at all!
Ok well I feel a little bit better that I'm not the only one to experience this problem. It makes me nervous that this happened so I'll probably contact Asus and see what the deal is.
Hi, i have an s6 (non edge), i do have it insured so not sure if i would be best trying to get it swapped or see how it goes?
I have had no problems up to now, been using it most of the day fine, the last time i looked at my phone was probaby about 30 mins before this happened and it had about 75% battery.
before i took my phone out my pocket and it was completely off, i kept pushing the power button in and getting no response at all, i plugged the phone into the mains and nothing happened, no charge light etc..
So i just left it connected to the mains with nothing happening for about 15 mins, then out the blue i pressed the power button in again and it come on, at it was starting i noticed it said android is updating an app (as it does when you have just installed a new fw) but this was only for 1 app by the looks, i hadn't installed anything new i can think of, not sure if thats related or not important?
Anyway my phone seems ok at the moment but now im not sure if i should just take it back the shop and get it changed seems i have it insured anyway, the phone is around 3 months old now.
Sorry, i am just editing this, i have just remembered one main point which i forgot i done earlier when reading that it can help your phone, i did go into dev options and i changed the 'limit background processes to 4' as i read this can help it, not sure if this was a bad idea?
Any advice?
Thanks
James
Possibly a defective battery.
I have had the p900 for about two years now. Rooted it some time ago and installed CyanogenMod without any problems. But just recently, when I tried to reset the tablet, it got stuck on twrp. I thought I would let the battery drain and see what would happen afterwards, but now I can't get it to turn on anymore, even though I let it charge. The tablet really doesn't do anything anymore, can't go into download mode and it isn't regocnized by my computer either. So I think it's bricked, but since I'm not really the most tech savvy person, I thought I'd ask here... Could anyone tell me if this sounds like it really is bricked, or if there is still hope?
I'm wondering if your battery discharged too far down, basically killing it. Once that happens, it no longer holds any charge. I've seen that happen on an older battery (actually happened on one of my laptops!). You could try removing the back of the tablet and disconnecting the battery and reconnecting it after a few minutes, then putting the charger back on and see if you get lights. (if you're going to do that, might as well have a new one in front of you and just replace it - easy to do, and Amazon has batteries for a decent price from a few different vendors - just did that to my Note Pro last week. Youtube it for directions, it's easy if you are patient. I used this one, http://www.amazon.com/dp/B00N4KRSVW and it is working well - even got rid of the flickering screen around 50% power and below...
I'm having an issue with a 3 year old Google pixel where the phone is no longer bootable due to it dying anytime it is turned on. Symptoms started about a year ago, the device would occasionally die randomly when opening apps especially with a camera like Snapchat. The issue was originally very infrequent but got more and more common until every app that is opened would kill the device if not plugged in. At this stage anytime the device died it wouldn't use to boot until plugged in. About 4 months ago it started dying even if it is plugged in and now it refuses to boot rom or stay alive in recovery long enough to even decrypt the device. Device is also unstable if plugged into a computer as it constantly reconnects and disconnects. The really odd part about all of this is booting into fastboot works just fine and it will stay in fastboot as long as it's plugged in. I'm thinking I'm gonna have to tear down the device and replace the battery manually but I'm not 100% sure if this is the cause so I'm asking here for confirmation first. Any advice would be greatly appreciated as I need to get data off the device to move to my new pixel3
EDIT: Well, f*** me, after looking through q&a section for 2 minutes I found other people have started having this issue around same time frame as me and it turns out the problem is the motherboard is shot which I was also thinking in the back of my head but didn't want it to be true. I'm so not spending $300 to replace the Mobo of a 3 and a half year old phone, but I do need to get the data off of it. My understanding is that adb DOESNT work over fastboot so I think I'm gonna try to plug it into my laptop and see if I can get twrp alive long enough to get any kind of filesystem access.
Honestly, it sounds like the battery is just dead. The phone dying at X% when using snapchat is like the first sign that the battery is getting weak and can't push out the required power. The way you described it, it just sounds like it got progressively worse until the battery is complete trash. The batteries are like $5-15, so might as well try it if you think you can do it without breaking the screen. I just did it for mine.
uaDPJ said:
Honestly, it sounds like the battery is just dead. The phone dying at X% when using snapchat is like the first sign that the battery is getting weak and can't push out the required power. The way you described it, it just sounds like it got progressively worse until the battery is complete trash. The batteries are like $5-15, so might as well try it if you think you can do it without breaking the screen. I just did it for mine.
Click to expand...
Click to collapse
It's not the battery. Many other sources confirm that this is a motherboard problem. At first it definitely seemed like a battery problem given original symptoms but at this point there is a wide range of random symptoms that point to the board being shot.
On a brighter note I've managed to keep the device alive in twrp long enough to pull data off by plugging into a computer. Wall charger would cause it to die despite charger working fine with several other devices
A bad battery can leak onto the board and fry the board, so you may both be right.