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...
Alright, if you're suggesting anything but manual labour, I don't think you can help me here. But I will try anything to get this junk running again.
Long explanation:
I have acquired a Samsung Galaxy S6 that is dead and non-functioning from one of my relatives in the hope that I could potentially fix it. He even let me keep it if I could find a way to fix it, so this a chance I don't get too often!
Anyways, this is a classic case of "Left it charging overnight, died in the morning" cliché, so I doubt this is anything to do with software, hence the need for a hardware solution.
The only complication with this situation is that the USB is mashed to a state of eternal unfixable limbo.
Someone yanked the charger in too hard and mashed it, although I doubt this was the problem, since the phone lived a good few months after it had broken.
So, the only way to charge it is to use the wireless pad that was also bought with it, which leaves me with the problem that I can't even check if it connects and turns on at all.
The actual problem summary:
- Unit is non-functional, it will not turn on under any circumstances
- I have tried all the button-holding combinations and it has failed to assist
- I don't know if this means anything or not, but when I put the device onto the charging pad, the charging pad recognises that the phone is there and (what I can only assume) it starts charging the phone, since the phone also gets warm after a while
- I have confirmed (with my working S6) that the charging pad is not at fault here
HOWEVER, there is a speckle of hope.
When trying to mess with all the button combos, I had managed to get the phone to light up the notification LED (white), which I automatically know means there is a hardware fault BUT the circuitry is still able to power and detect the fault. I took the phone off the pad shortly after and the light went out, interestingly green and blue going out first and the red coming off a few moments later.
So, I just need some pointers on how the charging pad and the phone's charging circuitry works in order to *attempt* to fix this dead unit.
I'll be honest; I'm not really hopeful, but I'm open to suggestions, After all, I already have an S6. If the other one ended up working, I'd sell it on eBay for £50.
- Melon Chickens, back from the dead.
(PS: Speaking of back from the dead, my S3 mini has been resurrected!)
did you have any luck ,i have the same problem with a note 5 it was working and in the middle of texting somebody it went black and has still to this day come back on .odin reconize mine but when i flash new software it finishs but phone never cuts on just the lite blinks.
I guys.... Mines dead to.
I've downloaded 4 different firmwares and nothing... Blue screen of emergency recovery but can't solved
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.
Hello!
I recently tried to replace my LCD/Digitizer on my S6 edge SM-G925V. Everything went well...at least I thought. The display works great! However, I believe I have either a battery issue or a OS issue.
After I installed the new screen, I booted the phone up. It loaded up fine. I went to check to make sure every feature worked. I was playing music to test the speaker and the phone just restarted on its own. I found that to be odd, and so I tried again. Same thing. This is just a couple minutes into it turning on by the way. Sometimes it would take longer to restart than others, but it was generally in the same time frame. I did try other apps to see if maybe the music app was causing it to have issues. The phone would restart randomly regardless of what I was doing.
I first thought that maybe the battery wasn't charged up enough. I charged it some, but was still getting the same issue. I then went to try and boot into safe mode. Still the same issue was there. I tried resetting the phone, master resetting the phone, and also wiping the partition. The phone now boots to the Samsung screen, then goes to the Verizon screen and then reboots in a endless cycle.
So...it was booting correctly, but randomly restarting. NOW, it's not getting past the Verizon screen and rebooting.
I tried using Odin and resetting it using the latest software update. It would pass just fine. The phone would reboot then go to "Installing Updates". It would get to 32% then say "Erasing". It would reboot back to the Samsung screen and start the endless boot process again.
The one thing that Intrigued me and led me to trying to use Odin was that when I would boot to the Downloader screen (The blue screen where you have to press up on the volume button to continue or down to cancel) the phone would never restart on that screen. I figured if it was a battery issue then it would restart regardless of what screen I was on.
But, I noticed something after all of this. The LED stays light up blue when the phone is powered off. The LED lights work correctly when the phone is on (Red when charging, changing from blue to green in a wave like pattern when turning on).
That kind of made me rethink the problem, and go back to it being a battery?
So, this is where I stand now. The phone would boot up, but randomly restart. I thought the OS may of been corrupted or something went wrong during the replacement of the screen so i tried resetting it, etc. Now, it the phone is just stuck in a endless loop. I noticed the LED lights up blue while the phone is turned off, so it has led me back to thinking it's a battery issue.
Lastly,
I don't believe I messed anything up when removing the battery. I was very gentle. I was watching a YouTube video that pointed out that thier technician poked the battery in the video, and they kept it there so we could learn from their mistake. Their battery leaked out a little and showed some residue on the black part of the piece it is mounted in. I never seen in residue or anything like that when I did mine.
I also unplugged the battery first before unplugged any of the other ribbons connected to the motherboard.
I am new to repair screens and I wanted to try on some of my old phones to get practice. Although this issue is frustrating, it is giving me a loads of knowledge on issues. It would be greatly appreciated if anyone could help me out with this. I'm not sure where else to go from here. I do have a battery ordered, but probably will not get here til sometime next week.
Thank you everyone for taking the time to read this long post!
Try replacing the battery. Make sure all grounding pathways and connectors are properly connected. Sometimes they may use unconventional pathways like the frame or a screw.
Impacts that can break the screen can cause high enough G loading to internally damage chipsets, fracture solder bonds (including hidden BGA ones) and damage internal mobo traces.
The display and mobo when out of circuit are suspectable to ESD damage. Full ESD protocols and procedures should be followed. Even though many techs don't do this doesn't mean they don't damage hardware. It may take weeks or even years to manifest itself. Handle the mobo, display and sim card like a stick of ram.
In 11 years I've only seen one tech install a sim card properly; ESD mat and wrist strap.
blackhawk said:
Try replacing the battery. Make sure all grounding pathways and connectors are properly connected. Sometimes they may use unconventional pathways like the frame or a screw.
Impacts that can break the screen can cause high enough G loading to internally damage chipsets, fracture solder bonds (including hidden BGA ones) and damage internal mobo traces.
The display and mobo when out of circuit are suspectable to ESD damage. Full ESD protocols and procedures should be followed. Even though many techs don't do this doesn't mean they don't damage hardware. It may take weeks or even years to manifest itself. Handle the mobo, display and sim card like a stick of ram.
In 11 years I've only seen one tech install a sim card properly; ESD mat and wrist strap.
Click to expand...
Click to collapse
Hi!
Thank you for the detailed reply. Very insightful.
I've been at work for the last few hours. I left the phone powered off while I was gone. I got back and the phone is powered off, but the LED light is still blue. The only way to get that to go off is by unplugging the battery ribbon from the motherboard.
The phone was on at least 70% of battery before I left. I get back and it started charging at 20%. Mind you, it's been off while I was gone.
Do you think the safest route would be to unplug the ribbon until the new battery arrives?
TrumpXLV said:
Hi!
Thank you for the detailed reply. Very insightful.
I've been at work for the last few hours. I left the phone powered off while I was gone. I got back and the phone is powered off, but the LED light is still blue. The only way to get that to go off is by unplugging the battery ribbon from the motherboard.
The phone was on at least 70% of battery before I left. I get back and it started charging at 20%. Mind you, it's been off while I was gone.
Do you think the safest route would be to unplug the ribbon until the new battery arrives?
Click to expand...
Click to collapse
If you think the battery has failed don't charge it.
Any swelling is a failure.
A sudden drop in capacity or erratic charging are also signs of a failure. I just went through this with my 10+'s battery
It's possible the battery was physically damage when the screen got broke, they're are really flimsy.
Best to rule out the battery.
It won't do your sanity much good until you do.
Examine the charge port PCB closely for any damage or solder cracks.
Examine the mobo as well. A stereo magnifying visor helps.
Hopefully the new battery will get it
Hello, I have the same exact problem. Verizon phone. Replaced screen from another phone. The phone boots normally, reaching the lock screen/home screen, but restarts after a few seconds. Performed a factory reset via the recovery menu, but now I'm stuck on the Verizon logo. Never-ending restarts. Never reaches the setup screen. The LED keeps on flashing blue-cyan at times despite forcing the phone off from maintenance boot mode (vol down + power). Tried factory resetting from there as well to no avail. Swapped back the old screen, but the boot loop persists. The battery is new (manufactured in 2020), had no random shut-off whatsoever prior to the swap, and had great SOT.
The worse part is the phone is undetectable via USB, the phone rarely fast charges. I suspect a burnt diode/capacitor on the mainboard itself because prior to the screen swap, I tried a daughterboard swap first. Both daughterboards work just fine and can handle both fast charging and data transfers on the donor phone. Both didn't work on the Verizon one. Can't even try flashing the firmware via Odin because of this.
Have you ever gotten to find a solution to this?
wildcatacu said:
Hello, I have the same exact problem. Verizon phone. Replaced screen from another phone. The phone boots normally, reaching the lock screen/home screen, but restarts after a few seconds. Performed a factory reset via the recovery menu, but now I'm stuck on the Verizon logo. Never-ending restarts. Never reaches the setup screen. The LED keeps on flashing blue-cyan at times despite forcing the phone off from maintenance boot mode (vol down + power). Tried factory resetting from there as well to no avail. Swapped back the old screen, but the boot loop persists. The battery is new (manufactured in 2020), had no random shut-off whatsoever prior to the swap, and had great SOT.
The worse part is the phone is undetectable via USB, the phone rarely fast charges. I suspect a burnt diode/capacitor on the mainboard itself because prior to the screen swap, I tried a daughterboard swap first. Both daughterboards work just fine and can handle both fast charging and data transfers on the donor phone. Both didn't work on the Verizon one. Can't even try flashing the firmware via Odin because of this.
Have you ever gotten to find a solution to this?
Click to expand...
Click to collapse
The part number on the daughter board must match the replacement. There maybe two US versions... if so they are incompatible.
blackhawk said:
The part number on the daughter board must match the replacement. There maybe two US versions... if so they are incompatible.
Click to expand...
Click to collapse
I do have the SM-G925V (Verizon, 64GB) and SM-G925F (Global, 32GB). Originally, Verizon had a broken screen, a USB issue, and randomly restarts. SM-G925F did have a Knox-tripped mainboard and a faulty daughterboard, but only the 3.5mm jack didn't work.
Swapping only the daughterboards, I was able to use the Global just fine even after flashing the original firmware. The Verizon one despite having an older battery did suffer fewer random restarts and I started using it primarily as a hotspot device. The global one uses a newer battery I ordered online.
Prior to Verizon's factory reset via recovery menu, It had all the original components except the newer battery and the screen from global. I tried a reset because the random restart became even more persistent even while doing nothing. Now, Verizon is stuck, boot loop. I tried swapping even all the original components (older battery, broken screen) just to see if the phone will proceed to the setup screen. It didn't.
Were you able to fix the boot loop issue on your Verizon?
wildcatacu said:
I do have the SM-G925V (Verizon, 64GB) and SM-G925F (Global, 32GB). Originally, Verizon had a broken screen, a USB issue, and randomly restarts. SM-G925F did have a Knox-tripped mainboard and a faulty daughterboard, but only the 3.5mm jack didn't work.
Swapping only the daughterboards, I was able to use the Global just fine even after flashing the original firmware. The Verizon one despite having an older battery did suffer fewer random restarts and I started using it primarily as a hotspot device. The global one uses a newer battery I ordered online.
Prior to Verizon's factory reset via recovery menu, It had all the original components except the newer battery and the screen from global. I tried a reset because the random restart became even more persistent even while doing nothing. Now, Verizon is stuck, boot loop. I tried swapping even all the original components (older battery, broken screen) just to see if the phone will proceed to the setup screen. It didn't.
Were you able to fix the boot loop issue on your Verizon?
Click to expand...
Click to collapse
I know about because I ran into that problem on my N10+ N975U. Apparently there are 2 C port pcb variants. In my case the original pcb was still good so they just put it back in.
So much for preventive maintenance...
blackhawk said:
I know about because I ran into that problem on my N10+ N975U. Apparently there are 2 C port pcb variants. In my case the original pcb was still good so they just put it back in.
So much for preventive maintenance...
Click to expand...
Click to collapse
Sorry, I thought you originally posted the problem. I just noticed it was @TrumpXLV. Nevertheless, thanks for providing some insight. I did try to swap back all the original components on both of the variants, Global and Verizon. Did a factory reset via recovery menu on both, but only the Global one reset just fine and the Verizon one didn't.
I was curious if @TrumpXLV did find a solution. This is the only post I found that described the same issue, the same model. Might have to shelve this phone for now. Was planning to repurpose this phone in some way originally. I'm daily driving S10+ atm.
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.