Hi all,
A little backstory first. I'm very new to XDA, so please let me know if my title formatting is wrong or if this is the wrong category or something else.
I had a Nokia 7.1 for about three years. It broke about two months ago, without a warning. The way it broke was rather strange: I plugged it to a charger with 0% of battery on it. I went to check in 10 minutes or so, and the phone was showing 38% charge. I thought that was weird since the phone should not charge that fast. I didn't care about it too much, powered it on and went to get some food. After coming back, the screen was pitch black. I didn't get to see if it ever even powered on, I only saw the "Android One" logo before going to eat. I tried everything to power it on, but nothing worked. I made sure that the charger was not the problem either. It may be worth noting that the battery life had been degrading for quite a while and wasn't great anymore. I figured that the battery might have died. So, I ripped the phone apart with a rather inappropriate tool (which was probably a huge mistake, but I didn't think it would matter at the time): a regular knife. As I was unplugging the battery from the motherboard, using the knife to pop the connector out, I saw a small spark. After some days of waiting, I got my replacement battery and installed it. Still nothing. I started to suspect a motherboard issue and took the phone to a repair shop. They confirmed it: it was indeed a motherboard issue. Now, I have a few questions that I would really appreciate getting help with:
1. My current theory is that the battery died first. When removing it, the sparks fried the motherboard and this is when the phone broke completely. Do you think this is possible? What is your theory?
2. Is there any possible way to fix the motherboard in this case?
3. If the phone cannot be fixed (which is very likely), is there a way to clone the phone storage onto another device / mass memory without being able to turn the phone on? The reason I want to save this phone so bad is that I have some important 2FA codes in there, can they be saved?
Any help would be greatly appreciated! If you need any extra information regarding this, let me know.
Related
A few hours ago my girlfriend was just looking at her Triumph (was watching for messages so she wasn't actually doing anything on it) when the screen turned off. Now it wont turn back on. Have tried the power button, turning on the bootloader, and removing the battery for 5 minutes. No matter what we can't get the phone to turn back on. Any ideas on what has just happened? The phone is rooted with gingerbreak with titanium backup installed. That's it. We got the phone at Best Buy and this is our second phone. We're probably past our 30 days so this kind of bugs me! Any idea what we can do from here? Any other tricks to try?
As a quick update, Best Buy tells me that an Exchange counts as an original transaction. So I'm only 17 days into my "new" transaction. I can't believe neither of these Triumphs have lasted more than three weeks :\
Did you have it connected to the charger while using it? I have noticed it gets very hot even without the charger being plugged in. It may have over heated. Just a thought. Good luck. Let us know what happens.
Sent from my MOTWX435KT using XDA App
No, the charger wasn't connected at the time. It was just sitting there with the screen on. The Significant Other wonder why it wouldn't turn off so she hit the power button and it didn't do anything. Finally the screen just went black but the backlight was still obviously on so she pulled the battery and put it back in. From there, she pushed the power button and the virgin mobile logo came on and nothing else. She had to remove the battery again. She put the battery back in once more and was able to get the Virgin mobile logo one more time. It froze after the logo and she pulled the battery one more time. After that the phone refused to turn on at all. When connected to the charger it doesn't do anything. Still completely lights out on the phone.
Man that sucks. I hope your able to find a fix.
Sent from my MOTWX435KT using XDA App
Same thing happened to me the other day. I let my Triumph lose all its battery to charge it back up 100% (performing a full battery charge cycle), and it will no longer turn on. even when I have it plugged in the red light indicator will not light up most of the time.
Funny thing is, this is also my second exchange from best buy and luckily im still within 30 days and i have a replacement plan. I really suggest getting the replacement plan (its $30, good for a $300 phone), because unlike best buys other mobile protection plans, you dont pay monthly, you're covered for 2 years, and if you get tired of getting the same phone, they will give you a $300 store credit card.
You know my phone did something similar, my phone died and when i went to plug up the charger i got nothing. I think there might be something wrong with the charging ports on these phones, try wiggling the charger while its plugged in, thats what i did and it finally took a charge
carter6739 said:
You know my phone did something similar, my phone died and when i went to plug up the charger i got nothing. I think there might be something wrong with the charging ports on these phones, try wiggling the charger while its plugged in, thats what i did and it finally took a charge
Click to expand...
Click to collapse
upon closer inspection of the charging port, i noticed the female micro usb port was actually pushed further inside, thus preventing most chargers to work. I found a rocketfish charging adapter from best buy that seems to work perfect while my other cable didnt work at all.
As an update, we went back to best buy and sure enough they count the exchange as a new transaction, so I was only 17 days into my second transaction. They exchanged me another phone on the spot and so now we're on the third triumph. GPS checked out ok and the MEID was the correct length. The screen is the worst of the 3 (some pretty bad backlight bleed out onto the screen itself from the sides). I was picky about it but the gf isn't since you can't even see it unless the screen is completely black. So we'll see how this one holds out!
My guess is as was assumed, the battery wasn't getting charged. When the battery was removed for 30 minutes or more we were able to get the logo to show up and nothing more. My guess was the charger wasn't making contact anymore. We wouldn't want to keep a phone like that anyways but it seems like this might be a problem for these phones.
Every once in awhile mine will not power back on. It happened to me a couple of times shortly after I bought the phone.
I tried pulling the battery a couple of times and powering back up, no go.
What worked... remove battery, press power button for a couple of secs, replace battery, power back up. Has worked every time... so far.
My guess is need to drain some capacitors or that I had invoked part of boot recovery sequence without finishing?
mr2011 said:
upon closer inspection of the charging port, i noticed the female micro usb port was actually pushed further inside, thus preventing most chargers to work. I found a rocketfish charging adapter from best buy that seems to work perfect while my other cable didnt work at all.
Click to expand...
Click to collapse
Have you noticed the "I just broke my Triumph's Screen"- post? We'll If you saw my cracked Triumph, well that's another issue that I just discovered. The battery drained all the way and now it will not take a charge anymore. This is the exact same problem OP is having. Regarding this issue I will open up my phone sooner or later when I get a new one and take pics. I don't mind seeing wth is in there, maybe everything's held up by Elmer's glue lol. I'll make sure to let everyone know hopefully I'll do this within a couple days.
It seems like dead
If Motorola and VMUSA are not serious about resolving issues for Triumph then this phone will be dead anyways - customers won't be buying those. The number of returns are far more than new purchase. It seems like Motorola stopped manufacturing these.
So this phone will either get Ice Cream Sandwich update or it is end of life for this phone.
Bought a Nexus S advertised as "new" from an eBay seller with high ratings. Phone arrived. Not entirely sure it's new because it did not have the factory film covering the screen, but it's in good shape.
Problem is, I can't get the thing to turn on. I put the battery in and tried to turn it on. No go. So I figured the battery might be dead. It's been plugged in now for the past 15 minutes and it still won't turn on. I made sure that I had properly seated the battery, and it still won't turn on.
I figure if the thing really is new and has just been sitting around for 1 year or longer, the battery might just be dead. Unfortunately, I have no way of confirming that, but the phone will not turn on even when plugged in. Nor am I getting any sort of charge indication.
Any thoughts or advice?
Try AdamOutler's tools to resurrect it (do a search, I'm on my phone) and maybe try a new battery.
Beyond this, get a refund.
Don't really want to buy a new battery. Some phones will power on when they are plugged in even with no battery. Does the Nexus S do that? If so, it would confirm that the phone itself is dead rather than just the battery, because it won't turn on even when plugged in.
Edit: I also tried a different charger that I know works. Still no luck.
You can get a battery off of eBay for five dollars. You will be out five bucks just to confirm your suspicions. If that doesn't work, along with Harbbs' suggestion, get a refund for the phone.
Sent by pocket technology.
Ok cool, thanks for the advice. I just wanted to make sure I wasn't missing some secret handshake or something =P I've tried holding the power button down for at least 10-15 seconds. Couldn't possibly require longer than that I imagine.
Yeah. I've never experienced the issue you're talking about. Hopefully its something small and maybe someone else has something else you can try and chimes in.
Sent by pocket technology.
Oh, one other idea. I'm trying to turn it on without a sim card, since I've only got a microsim right now. I've never heard of a phone that would only turn on with a sim card in it, but please let me know if anybody thinks this could possibly be the problem.
Phone turns on without a SIM, makes no difference until inside the OS.
Phone requires a battery. Charger won't keep the phone on without one. It's not a Nokia.
As a matter of fact you could use 3 AA batteries in a holder (preferrably rechargeables for a lower voltage) to test, see battery benchmark thread for more details here.
I would first start by trying out AdamOutlers unbricking tool.
Mm, didn't read the OP carefully enough. Never mind. >.>
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 purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
If it won't turn on even when plugged in, something might be fried. I know batteries can start acting weird and causing problems after a few years too, but I think this is something else.
alienjon said:
I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
Click to expand...
Click to collapse
Sent from my Nexus 6 using Tapatalk
Maybe, but I got it brand new from Google a bit over a year ago (06/2017), making me generally hope it isn't something related to 'natural causes'. I think what bothers me the most about this is that I don't know what went wrong and can't think of anyway to check. Plugging it into a wall plug to charge doesn't do anything and when I plug it into the computer my computer doesn't see that anything is plugged in (as I have installed upgrades via my computer, it definitely has the right drivers and everything to see it...).
The slightly paranoid side of me recalls back a few days ago to an article I was reading about malicious apps using phones to mine cryptocurrency, sometimes leading to those phones wearing down enough that they could even brick. Logically I'm almost positive this isn't happening for two reasons. The first being that I haven't installed anything for about a week (and the phone was working fine until this morning) and secondly because I had an app that monitored my network traffic and there wasn't nearly the throughput I'd expect for that kind of processing. Still, I can't think of what else might have happened...
sdnative1 said:
If it won't turn on even when plugged in, something might be fried. I know batteries can start acting weird and causing problems after a few years too, but I think this is something else.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You would have noticed massive battery drain if your phone was mining cryptocurrency. Try putting it into a freezer for a bit, then see if you can get any reaction when plugging in. If not, my guess is a catastrophic hardware failure, like a bad battery which leaked & fried the board, or something like that.
If you're in the US, contact uBreakiFix (Google contracts warranty repairs through them). I've read reports of them making repairs for free, even outside of warranty.
post-mortem said:
You would have noticed massive battery drain if your phone was mining cryptocurrency. Try putting it into a freezer for a bit, then see if you can get any reaction when plugging in. If not, my guess is a catastrophic hardware failure, like a bad battery which leaked & fried the board, or something like that.
If you're in the US, contact uBreakiFix (Google contracts warranty repairs through them). I've read reports of them making repairs for free, even outside of warranty.
Click to expand...
Click to collapse
Thanks for the freezer suggestion (I recall that trick for old hard drives, but never used it myself). How long you thinking for that to do anything? I tried about 10 minutes and didn't see any difference (not sure if I should be doing something closer to an hour or more?) I did Google support (online chat) and ubreakifix was one of two other options they suggested. It looks like they're a little bit of a drive for me, but I'll see if I can't stop by in the next couple of weeks. My old Galaxy S5 will have to do in the meantime (which is slow with poor reception at this point, but it functions as a phone, so I've got that going for me
I'll try to update if/when I get details from the repair guys.
If the freezer trick did anything, it would likely be temporary (possibly enough time to get data off of it). It would really just confirm a hardware failure, which at this point is my working hypothesis.
One day my pixel randomly shut down, unresponsive, holding power button did nothing, same when I tried to plug it to a pc or when plugged in.
It restarted when i pressed power + vol- (fastboot mode) for about 40secs - I know, it's a lot, never knew what happened.
Then it just worked normally
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.