Related
So today, as i was on my way to work I accidentally held down the lockscreen button and the power menu popped up (I was on Glorious Overdoes V2) in the middle of a text and i pressed reboot accidentally... My phone never rebooted... It was stuck on the black Sidekick 4G/T-Mobile screen and then it would go black, then once again that screen would pop up... I removed the battery and put it back in, and without me pressing any buttons the same screen came back up... I let it sit for a while and after 20minutes nothing changed except the phone got really hot. Luckily I had my OLD Nokia in my car and popped my SIM card in it so that i could continue having a phone. I let The Sidekick sit for 4hours and it was extremely hot and then eventually it just turned off completely (Im assuming the battery drained, it was at 90% 4 hours before.) I got home, plugged it in and it wouldn't even turn on the charging screen. Somebody told me that my Motherboard is fried but I don't know. I called T-mobile and they're going to send me a new phone since it's still in the 1-year warranty period.
Anyone know if they're going to be able to inspect my old device and find out if i rooted/flashed it? because i can't get into it or anything to ODIN
I feel like they will try putting a new battery in it, and if it still wont turn on you should be fine.
It got hot because the CPU was churning over something and couldn't enter a low power state. I bet you could coax the phone into download mode and reflash it.
what do you mean coax the phone into download mode? by using the button combo to get it into download mode when turning on? I've tried that and it doesn't work. I tried rebooting into recovery and that wont work either. Also, it wont charge the battery anymore...
I've always had a hard time getting into download mode, and my phone works fine. I just spent 5 minutes trying different combinations until I got it.
I've heard people say trackpad-power button, volume down-home-power button, volume up/down-put battery in-plug in USB, etc etc etc. But the only method that works for me is to put in the battery, plug in the USB, wait for the charging screen, then hold volume down-trackpad-power, releasing power as soon as the screen goes black
You say your phone is turning on as soon as the battery is inserted? What if you have it plugged into USB first?
I had the exact same problem, I sent it into samsung and they just replaced a part(never told me which one) and it was fixed. I did noticed that when the sccreen was poped open to show the keyboard, it would stop. But it's probably a loose cable like I've read before.
Sent from my SGH-T839 using Tapatalk
Worst case scenario if you can't figure it out here on XDA, you could always sell it on eBay for parts as defective.
Hello,
Today I tried to sideload the OTA update to Android 5.0.1 (because my Nexus is root and it would not let me update normally), but there was an error saying missing file in system.img. So, after that, I got stuck at Google logo screen. I entered stock recovery (I never installed a custom recovery) and wiped cache, with no luck. Did a data wipe. No luck. So I tried flashing the factory image for Android 5.0, but right after flashing the bootloader, the device turned off (or it appeared to), the script showed "waiting for device", and the phone never came back. Now it won't turn on at all. I don't know what to do
Thank you for your help
cool1007 said:
Hello,
Today I tried to sideload the OTA update to Android 5.0.1 (because my Nexus is root and it would not let me update normally), but there was an error saying missing file in system.img. So, after that, I got stuck at Google logo screen. I entered stock recovery (I never installed a custom recovery) and wiped cache, with no luck. Did a data wipe. No luck. So I tried flashing the factory image for Android 5.0, but right after flashing the bootloader, the device turned off (or it appeared to), the script showed "waiting for device", and the phone never came back. Now it won't turn on at all. I don't know what to do
Thank you for your help
Click to expand...
Click to collapse
I had the same problem today and i thought that i'll post how i fixed it.
My wife left her N5 charging overnight, this morning the phone was dead, kaput, it won't turn on or show the battery icon. I ended up opening the phone and disconnecting the motherboard and battery following the "Nexus 5 Battery Replacement howto" from ifixit.com.
Long story made short, open the phone, remove the 6 screws holding the motherboard, disconnect the daughterboard and battery connector, wait a few minutes and reconnect them again (Steps 1 to 4, no need to continue), the phone should power on now, if it does, put everything back together and keep enjoying your N5.
The only trick is opening the case , use your nails or a plastic opener tool to pry open the latches then carefully pull out the case, in my N5 there was some light glue applied on the lower part of the case, not a showstopper at all.
Necrosis
works for me too
elfarto said:
I had the same problem today and i thought that i'll post how i fixed it.
My wife left her N5 charging overnight, this morning the phone was dead, kaput, it won't turn on or show the battery icon. I ended up opening the phone and disconnecting the motherboard and battery following the from ifixit.com.
Long story made short, open the phone, remove the 6 screws holding the motherboard, disconnect the daughterboard and battery connector, wait a few minutes and reconnect them again (Steps 1 to 4, no need to continue), the phone should power on now, if it does, put everything back together and keep enjoying your N5.
The only trick is opening the case , use your nails or a plastic opener tool to pry open the latches then carefully pull out the case, in my N5 there was some light glue applied on the lower part of the case, not a showstopper at all.
Click to expand...
Click to collapse
i had some similar experience this morning, phone wont turn on, no charging notifications nothing, and i followed ur instructions and its works fine now, no idea how it happens, but when i open the back i got some burning smell too, anyway the device is working fine now!
anyways thanks
Background: I had my completely stock Nexus 5 on the charger for around an hour. When it got near 100%, it locked up for about 5 seconds and powered off. It wouldn't charge or power on again until 2 days later where it would power up but not charge. It could go to the bootloader/recovery but it would still shut down. The charger used won't charge anything anymore, it may have been a power surge that messed it up.
I replaced the battery and the system is still unable to maintain power but recovery and the bootloader are stable (just formatted the cache and the phone did not power off, took around 15 minutes). Now it won't power up again.
Any idea what the issue could be? Could it be corrupted data?
First, try another cable and charger.
Also, make sure you have enough juice on the device first, reflash stock firmware with fastboot and see if the issue remains.
If you successfully flash your stock firmware and use another known working cable and charger and it's the same.... Then unfortunately it could be a hardware issue.
Thanks for the reply.
Unfortunately, that didn't bring my N5 back to life. I'm think a circuit may be fried on the motherboard but I don't have a real way of judging that at the moment.
Any chance you might be able to guess what the hardware issue could be? I'm mainly trying to save the data on my phone and I'm not against taking the phone apart to do that.
Update: I took the phone to a Sprint store and a technician looked at it. When the tech plugged it into the charger, the phone LED was flashing red with no charging screen. It eventually booted up and shut down. Later that day, I could see my notifications (Pushbullet is a wonderful app) and noticed the phone stayed on consistently. He said everything was fine and their formal report didn't mention any sort of damage to the phone that they could find. Later that same day, it died again. Today, I decided to completely wipe and load 5.1 to the phone. It stayed powered on through the whole flashing process (bootloader unlock and individual partition flashes) but shut off during "optimizing apps". Considering it powered off in the system, I'm thinking the issue is with the RAM or the CPU possibly being fried due to a power spike while on the charger. It seems like it only happens during heavy operations.
Something hardware it seems. Not sure what, but if a component on the mb is bad then it is a replacement.
I like the title though, doubt anyone has a device that stays charged while in system. Sorry about your phone, but made me chuckle. I really can't think of a better way to describe it, not trying to pick on you.
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.
Hey all,
While I was watching a video 2 days ago, the screen started to glitch and the phone shut itself down. I tried to restart it by holding [power]+[vol up]+[vol down]. I got stuck in the boot screen, then it shut down completely. I tried charging it but it didn't work. I left it for several hours and tried again, this time it started to charge the battery. I immediately tried to boot it. It booted normally but froze at the home screen, and went black again. Now, I get no response when I plug it to my computer, I can't get into download mode, and it doesn't the charge battery.
Any help would be appeciated.
See if you can get into recovery, clear system cache.
I doubt this will fix it so immediately afterwards try booting up in safe mode.
Copy any critical data, enable debugging, prepare to do a reflash.
If you installed any recent apps, try uninstalling them especially launchers or power management. They may be the cause of the boot loop. Check apps listed as system Administrator in security for anything that shouldn't be there, and disable all.
Try a hard reboot (simulates pulling the battery).
If no joy, factory reset.
If this doesn't work try reflashing to the same firmware version.
If that doesn't work you're likely looking at a mobo failure.
Happy hunting...
Please read and observe forum rules.
Do not create duplicate threads... good luck.
Bahadir Avci said:
Hey all,
While I was watching a video 2 days ago, the screen started to glitch and the phone shut itself down. I tried to restart it by holding [power]+[vol up]+[vol down]. I got stuck in the boot screen, then it shut down completely. I tried charging it but it didn't work. I left it for several hours and tried again, this time it started to charge the battery. I immediately tried to boot it. It booted normally but froze at the home screen, and went black again. Now, I get no response when I plug it to my computer, I can't get into download mode, and it doesn't the charge battery.
Any help would be appeciated.
Click to expand...
Click to collapse
Most probably a motherboard issue. I experienced something similar with a brand new Note 4 back in the day. It was repaired by the seller (motherboard replacement).
ASKnASK said:
Most probably a motherboard issue. I experienced something similar with a brand new Note 4 back in the day. It was repaired by the seller (motherboard replacement).
Click to expand...
Click to collapse
The BGA chipsets aren't tolerant of board flexing or direct impact; solder joints can fracture.
The chipsets themselves can suffer internal damage from high G impacts.
Internal PCB traces can also be broken by excess board flexing, they are many times fine pitched.
A good case keeps drops survivable by limiting the G loading on the phone.
However I wouldn't write it off just yet... gentle pressure on the mobo chipsets etc with a pencil eraser or such with the device on, may reveal a solder fracture or trace break.
Also inspect ribbon connectors for damage and full contact. Ensure all ground pathways are intact sometimes these can be hard to spot or use a screw (a short length wrong screw won't work).