Database Info

Power Off = Reset

I wonder if anyone else has encountered this issue.
This began about 2 weeks ago.
About 50% of the time, when I choose Power Off on my Skyrocket, the phone goes through the whole "powering off" procedure but then, instead of shutting down, it reboots.
It resets completely as if it had been powered off and then immediately been powered back on.
Sometimes this will even happen a second time in a row when I again try to shut down - other times it will shut down on the second try...

What rom are you using? Any other info you could provide such as when it started happening would help us help you.
At any rate, without knowing the details, I'd say it could be a hardware issue with your power button. The reason I say this is that if you hold down the power button for ten seconds or so the phone will re-boot. Additionally, I've seen a few cases of stuck power buttons with users in this forum (in their cases the phone was unusable--one got it repaired by mobiletech and the other hasn't yet fixed it to my knowledge.
If I were you I'd back up all the files you don't want to lose (pics, music, etc) to a pc just in case the button gets fully stuck, in which case your phone will do nothing but start up and restart over and over.
And if it is a hardware problem, you should be covered under warranty provided that you don't have any water damage or other physical damage to the phone.

I had a couple of ROMs do this. The phone wouldn't turn off if the battery was in it or it was plugged in.

eagercrow said:
I had a couple of ROMs do this. The phone wouldn't turn off if the battery was in it or it was plugged in.
Click to expand...
Click to collapse
What you're describing sounds more like you flashed one of the ICS leaks. A lot of people ran into the freeze at shutdown/reboot issue with those roms before the devs ironed out the kinks.
The OP's situation seems a bit different, since it is just rebooting instead of powering down.

Yes I am fully stock everything.

If you haven't flashed any roms and are just on stock, I'd get a warranty replacement. You'll have to play the waiting game with them but they'll get you a brand new (or refurbed, but good as new) phone within a couple weeks.
And again, I recommend backing up all your stuff asap before the button gets fully stuck.
If you have flashed roms in the past, you'll want to make sure you get fully back to stock, including flashing the reset binary counter .zip found in the development section so your phone looks nice and clean.

OK -
So I went to back up my data as suggested above.
When I tried to switch into USB mode, I got to the point where the USB is in and it says "Press to Connect to Mass Storage" (something like that).
When I clicked on that button, the phone reset.
Then after it restarted I tried again to click to enter Mass Storage Mode and the phone shut off and would not start again until I pulled the battery.
Sounds like more going on than a stuck power button...?
EDIT: After pulling the battery, I restarted and again tried to enter USB Storage Mode. The phone again shut down and would not start until I pulled battery.

lirong said:
OK -
So I went to back up my data as suggested above.
When I tried to switch into USB mode, I got to the point where the USB is in and it says "Press to Connect to Mass Storage" (something like that).
When I clicked on that button, the phone reset.
Then after it restarted I tried again to click to enter Mass Storage Mode and the phone shut off and would not start again until I pulled the battery.
Sounds like more going on than a stuck power button...?
EDIT: After pulling the battery, I restarted and again tried to enter USB Storage Mode. The phone again shut down and would not start until I pulled battery.
Click to expand...
Click to collapse
Yeah...that does not sound good at all. I'm still convinced it's a hardware issue. You might want to just pick up an external sd card if you don't have one and push your important files onto that. I got a 16gb card for only about $10 online, not sure what they sell for at electronics stores.
Something tells me your phone is going to give up the ghost soon and just completely crap out on you. Don't wait!

S6 100% unresponsive with irreplaceable photos contained within... need options

Changing the thread around to reflect the current situation, new text at the bottom of the post.
While out to dinner with my family an hour or so ago, my phone suddenly stopped working. I had been checking some emails when the food arrived, so I pressed the power button to shut down the screen and set the phone to the side. About 30 minutes later, I tried to open my phone to continue where I had left off, only I got no response at all from the device. I immediately tried the normal troubleshooting actions (holding power button for 30+ seconds and attempting to go into recovery mode), but still got no response from the phone. I have since tried charging it at home with it's original quick charger, but even after 15 minutes on the charger, there isn't even a red light indicating it is charging. Is there anything that I can try to fix this on my own, or is it likely that I've got some technical fault that only Verizon can deal with?
Thanks.
PS: I'm 100% sure that no liquid came in contact with my phone during dinner. Even if I wasn't so sure, both the phone and case have been bone dry through the entire ordeal.
New situation:
The "techs" at Verizon were less than useless... While there, they tried fewer fixes than I was able to attempt before telling me that the only option they could offer is to replace the phone. The problem, as I've said a little lower in this thread, is that I've got some irreplaceable photos of my recently deceased cat of 19 years stuck on the phone that I never got the chance to back up before this event.
And so now I need options. I'm willing to do pretty much anything, up to and including tearing the phone apart to manually access the memory unit, but the end result absolutely has to be those photos recovered.

Did you do the hard reset combination (Power, Vol Down?) I've had the problem happen to me before. Usually, what happens is it will lock up when it is having memory issues, freeze, then if I'm lucky, it will come out of it. Otherwise I have to do a hard reset.
It hasn't happened yet since I've been on 5.1.1 but I've only been on that for 3 days or so.
Edit: Just in case you didn't know, the recovery combination is Power, Vol Up, and Home when the phone is actually off. When the phone freezes like that and you don't get a response it's still on but completely locked up until you power off the phone.
Sent from my Super Computer (1976) with Tap Tap Talkolution

DroidXrei said:
Did you do the hard reset combination (Power, Vol Down?) I've had the problem happen to me before. Usually, what happens is it will lock up when it is having memory issues, freeze, then if I'm lucky, it will come out of it. Otherwise I have to do a hard reset.
It hasn't happened yet since I've been on 5.1.1 but I've only been on that for 3 days or so.
Edit: Just in case you didn't know, the recovery combination is Power, Vol Up, and Home when the phone is actually off. When the phone freezes like that and you don't get a response it's still on but completely locked up until you power off the phone.
Sent from my Super Computer (1976) with Tap Tap Talkolution
Click to expand...
Click to collapse
I've tried soft reset (hold power only), hard reset, and recovery, all to no avail, and holding each for long after it's supposed to respond (at least 60 seconds).

Volume down and power should simulate a battery pull. If that does not work, I would recommend going to a Verizon store.
Give your name to the concierge.
When they call your name, try the Volume down + Power again.
It should work then.

Theodric58 said:
Volume down and power should simulate a battery pull. If that does not work, I would recommend going to a Verizon store.
Give your name to the concierge.
When they call your name, try the Volume down + Power again.
It should work then.
Click to expand...
Click to collapse
I'm really hoping they will provide more help than that. There are some pictures of my cat on the phone that I had to euthanize last week after 19 years that I never had the chance to back up.

treblesum81 said:
I'm really hoping they will provide more help than that. There are some pictures of my cat on the phone that I had to euthanize last week after 19 years that I never had the chance to back up.
Click to expand...
Click to collapse
I'm sorry about your cat.
It was more to the point that what doesn't work when you are on your own, will work perfectly when you take it to the technician.
I used to do tech support for phones and tablets. I've seen lots of instances where the customer tries something with me on the phone that they had tried multiple times before, and with me on the phone it works immediately. Try the key combos with it plugged in, with it plugged in to a different charger, with it plugged into your computer. If none of those work, then take it to Verizon.

Theodric58 said:
I'm sorry about your cat.
It was more to the point that what doesn't work when you are on your own, will work perfectly when you take it to the technician.
I used to do tech support for phones and tablets. I've seen lots of instances where the customer tries something with me on the phone that they had tried multiple times before, and with me on the phone it works immediately. Try the key combos with it plugged in, with it plugged in to a different charger, with it plugged into your computer. If none of those work, then take it to Verizon.
Click to expand...
Click to collapse
All of this was done before taking it to Verizon. All key combinations were tried unplugged then plugged into 3 different chargers and also my computer with 3 different cables and several different USB ports. When I went to Verizon, they tried the key combinations unplugged and then tried plugging it in and seeing if it would take a charge... hence the assertion that they tried less than I was able to attempt at home.

Time to find someone who can repair the phone locally. Any type of warranty or factory repair will cost you the pictures.

Sounds like it's safe to say the phone is beyond simple trouble-shooting. I found myself in a similar predicament last year when I busted the screen on my S4. I dropped my phone on some concrete steps and the screen (in addition to being shattered) went completely black, but I knew the phone was still working because I could still hear the person I was taking to on the phone lol.
I ended up replacing the phone through Verizon. They referred me to some third party company that agreed to replace the phone for $100 and sent me a replacement with a box to put the busted one in. At this point I found myself presented with a unique opportunity, given the fact that I had both a working S4 and my broken one.
Because I didn't have the chance to back up the phone before I lost access to it (it's pretty hard to unlock a phone without the screen) I looked up a guide on how to disassemble the S4 on YouTube in order to gain access to the motherboard. The whole process was relatively easy to carry out and I was able to disassemble both phones, switch the motherboards, backup the information I needed, and switch them back.
Sorry for the long-winded response. I realize this is a pretty drastic measure to take and that you may not have access to a second S6. It's also entirely possible that the motherboard on your phone is part of the problem so switching it wouldn't help much in that case (like I said, I knew my phone was still working despite the screen). Just wanted to offer another option =).

I am in a similar predicament, desperate to get my photos and videos back and have been watching your thread for some ideas. My 7 week old Verizon Samsung Galaxy S6 G920VVRU4BOG9, android version 5.1.1. ceased to do anything on Monday for reasons unknown. It is now back on but it has been wiped clean. I had to do a hard reset. Samsung & VZW tech support were not helpful. May I ask what model your phone is? Provided you are able to get yours back on, I'm wondering if you may have some success with some of the following:
Wondershare Dr Fone for Android
Asoftech Data Recovery
Kvisoft Data Recovery
Ease US data recovery.
I could not get them to work because you must first have a rooted phone to retrieve them and mine apparently can't be rooted. I apologize if this is redundant but I thought I'd throw that out there in case you might have a change of recovering those photos. I'm sorry for your loss. It's very hard to lose a beloved pet.

bricked S7?

Hi,
I think I have bricked my S7.
Yesterday I installed Superman Rom and everything was working fine until this afternoon.
I played a bit around and somehow my S7 got stuck and it seemed like i messed something up. I was in some kind of bootloop so i flashed everything new -Bootlaoder, Modem and Superman Rom.
Now I have a black screen and the LED is light up in blue.
I can't do anything. Tried to restart with Home Vol- and Power key but it doesn't work.
If I connect it to the Computer it won't be recognized.
Strange thing is, if I press the Power Key the computer recognizes Exynos8890 in the device manager, but only if I keep pressing the power key.
As soon as I release the power key the computer recognizes nothing...
Does anyone have an idea?

Try holding Volume Down & Home & Power until the phone reboots twice, keep the buttons pressed for 2 full reboots, and hopefully the 2nd one will get you back into download mode

Thank you for your help!
I tried that but it doesn't work.
It's strange because I can do what I want and nothing happens.
Black screen and blue light. It doens't even turn off or reboot...
Only thing what happens is that exynos8890 appears in the device manager as long as I keep pressing the power button.

Same problem as me?
http://forum.xda-developers.com/galaxy-s7/help/boot-loop-bricked-t3499109/post69596073#post69596073

Sounds different.
Because you are able to get into recovery and download. I'm not able to do that

alexx3333 said:
Sounds different.
Because you are able to get into recovery and download. I'm not able to do that
Click to expand...
Click to collapse
How long are you holding the button combination for?
Try 30 seconds+

I tried for several minutes, but the phone doesn't do anything.

I can only think you'll need to wait until the battery runs out, the phone shuts off, then when you charge it again, try the download mode button combo when you power it back on

Ok thank you.
I thought the same.
Unfortunately the battery was at 90% so I think it will take a few days/weeks until it dies...

alexx3333 said:
Ok thank you.
I thought the same.
Unfortunately the battery was at 90% so I think it will take a few days/weeks until it dies...
Click to expand...
Click to collapse
Connect the white Micro > Normal USB adapter that came with the phone to the MicroUSB port, and connect a power hungry USB device to it, I just tried with a USB desk fan and the phone powered it on spinning
That will drain the battery quickly

Great idea but it doesn't seem to work.
Looks like I have no power in the USB connection.
Seems like the phone is totaly frozen.
Ok so how it looks at the moment, my only choiches are wait several days until the battery dies (don't know how long this will take) or sending it to Samsung for a repair.
Thank you for your help!

Good luck, if I think of anything else I'll reply here, hope you get it sorted
EDIT - Did you try holding the power button while you had the USB device connected, to see if it provides USB power then?

Wow, the exact same thing literally happened to me yesterday.
I wasn't doing anything to the phone - it's completely stock and unrooted, and I wasn't messing with anything. At the time it happened, I scrolling through the task switcher when all of the screenshots of running apps suddenly became white squares. I tried pressing the home button but it didn't respond (though I could still scroll fluidly through the white squares). A few seconds later the screen went black and that was it. Dead dead dead. Totally bricked. The only response I can get is "Exynos8890" in the Device Manager when holding the power button, just like you.
This really sucks because I paid full cash and imported an international version, so I have no warranty. I'm off to the Samsung store to plead with them about honoring the warranty anyway, maybe if I offer some cash on top.
I suspect the storage chip failed. Yesterday before it died, I was downloading all of my images off of the SD card to organize them, and I noticed that about 5% of them failed to copy due to an unknown I/O error. Of course I assumed this was a corrupt SD card, not internal storage. I did manage to pull them all off (though some were damaged) through a combination of adb shell, dd, and adb pull. During the process the phone hard-locked a few times, but each time I was able to reboot via the VolDown+Power combo.
When the phone finally died for good, it was several hours after I had finished copying the photos and since hte last reboot. It had been working perfectly since then - I was browsing reddit, watching netflix, etc. However, given that I got the white squares in the task switcher right before it kicked the bucket, I think the internal storage was actually to blame, not the SD card. The white squares indicates that it was trying to fetch the screenshots off the disk and failing.
It's very odd that I cannot find any other instance of this kind of failure on the internet except this one thread, which happened on the exact same day that my phone died. Very strange.

*Detection* said:
Good luck, if I think of anything else I'll reply here, hope you get it sorted
EDIT - Did you try holding the power button while you had the USB device connected, to see if it provides USB power then?
Click to expand...
Click to collapse
Yes I have tried that but no power at all...
stoanhart said:
Wow, the exact same thing literally happened to me yesterday.
I wasn't doing anything to the phone - it's completely stock and unrooted, and I wasn't messing with anything. At the time it happened, I scrolling through the task switcher when all of the screenshots of running apps suddenly became white squares. I tried pressing the home button but it didn't respond (though I could still scroll fluidly through the white squares). A few seconds later the screen went black and that was it. Dead dead dead. Totally bricked. The only response I can get is "Exynos8890" in the Device Manager when holding the power button, just like you.
This really sucks because I paid full cash and imported an international version, so I have no warranty. I'm off to the Samsung store to plead with them about honoring the warranty anyway, maybe if I offer some cash on top.
I suspect the storage chip failed. Yesterday before it died, I was downloading all of my images off of the SD card to organize them, and I noticed that about 5% of them failed to copy due to an unknown I/O error. Of course I assumed this was a corrupt SD card, not internal storage. I did manage to pull them all off (though some were damaged) through a combination of adb shell, dd, and adb pull. During the process the phone hard-locked a few times, but each time I was able to reboot via the VolDown+Power combo.
When the phone finally died for good, it was several hours after I had finished copying the photos and since hte last reboot. It had been working perfectly since then - I was browsing reddit, watching netflix, etc. However, given that I got the white squares in the task switcher right before it kicked the bucket, I think the internal storage was actually to blame, not the SD card. The white squares indicates that it was trying to fetch the screenshots off the disk and failing.
It's very odd that I cannot find any other instance of this kind of failure on the internet except this one thread, which happened on the exact same day that my phone died. Very strange.
Click to expand...
Click to collapse
That sounds exactly like my Problem.
A faulty storage chip would also explain my Problems before the phone died for good.
The day my phone died I had some Problems. The phone was frozen from time to time until it got into the bootloop, but I thought I messed something up in the Rom because I did a lot of testing and the Combo also did work.
After reflashing the Rom everything seemed to be fine first until it died for good.
Yes it's strange, I also didn't find anything similar on the Internet.

I have learned my phone is from Nigeria. This should be a fun RMA process. FML

stoanhart said:
I have learned my phone is from Nigeria. This should be a fun RMA process. FML
Click to expand...
Click to collapse
Contact Samsung on twitter, unlikely they'll force you to RMA to Nigeria, they'll have service centres in your region

I managed to get Samsung Canada to refer me to a local service center. I drove 1.5 hours to go there today, the dude plugs it into a charger, and the damn thing just lights up like nothing ever happened. Now it's working fine, but I swear this thing was fully bricked before. The battery still had 73% charge when it came back alive...
I'm happy it's working now, but I'm worried it's just going to crap out again at any time.

Update: after the phone revived itself, it worked pretty well for a week. It locked up a few times, but I was able to reboot each time.
But, after a week, it hard-froze again. This time, it happened to be on charge while it froze so the green LED was on. It's been completely unresponsive for 2.5 weeks now, off charger, with the green LED on. I keep waiting for the LED to drain the battery, but it's taking forever. I'm losing hope that it will recover this time. I guess I'll re-start the process of getting in touch with Samsung, or alternatively, look for a replacement motherboard on eBay.
Does anyone know if the G930F motherboard fits into the G930FD body? I don't actually care about dual sim, but I'm concerned the SIM tray/slot won't work with the G930F motherboard.

Update:
so in the meantime the battery of my s7 died but that didn't change anything. I wasn't able to charge it after that so now it was completely dead.
So I contacted Sasmsung.
They replaced the motherboard and the USB connector on warranty.
Seems like it really was a hardware issue...

alexx3333 said:
Update:
so in the meantime the battery of my s7 died but that didn't change anything. I wasn't able to charge it after that so now it was completely dead.
So I contacted Sasmsung.
They replaced the motherboard and the USB connector on warranty.
Seems like it really was a hardware issue...
Click to expand...
Click to collapse
Hi,
Do you need Proof of Purchase for the warranty?
Thanks.

S6 Edge Battery issue or OS issue? I'm new, help please

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.

Poco X3 NFC - Can't access bootloader, fastboot or system (bootloop)

Hi. My close friend has this issue. I'm posting this because she can't figure it out by herself. A month ago, her phone downloaded an update and she installed it. Since then, the phone has restarted by itself without any reason, just random restarts and the frequency of restarts was more frequent with each day. Fast forward to this day and the phone is constantly turning up and shows the POCO logo and restarts by itself. This loop is not ending until the battery is completely dead. When trying to access fastboot or recovery mode, she can get there but only for few seconds (until the device restarts again) which is not enough time to make any changes / factory reset. She did not accessed developer tools in system, so the bootloader is still locked. Holding down power button does nothing. ONE SINGLE UPDATE screwed up whole phone. Can't do ****. There's no SD card or SIM card in the slot. Is there any "hack" to stop the phone from restarting itself? Note when the battery is completely empty and she plugs the charger, the whole nightmare starts again. I'm lost. Did you guys have any ideas what to do? Or is the repair centre only solution? (She cracked glass of the display, i'm not sure if that voids warranty. [it's not glass COVER, it's the glass which is part of the display])

Is this device unlocked? If not, then RMA.
If it is, my best guess is to get the device into recovery (or fastboot?) and immediately connect to PC.
If it holds, leave it there as it will charge, although at much slower rate.
When charged, use TWRP to try to reboot to system.
If it doesn't work, then factory reset.

Sadly, i can not get to recovery because in about 2 seconds the device will reboot. There's literally no time to make any changes - factory reset. Also the device is not unlocked. I hope RMA accept the phone even though it has cracked screen . Thanks for response anyway

Then RMA it is. If you're in EU they'll have to take it, even with the cracked screen.
But does the reboot happen even when connected to PC? Two seconds is enough to plug it in if you're fast...

Yeah, we tried every possible idea we can think of. Pressing the toggle button from different angles with different intensity to make sure it isn't stuck inside, covering up the proximity sensor (yeah makes no sense but even that we tried, lol). Tried with connected to PC as with classical charging brick. No change. Back in those days where smartphones doesn't have unibody construction and you were able to take down the back cover and remove battery it was way simple. Nowadays it's not possible to stop the phone from booting itself until battery is completely empty. My friend says the problem started about month ago, when the phone annouced that there is an update available so she downloaded it and installed it. Before that, there was no problem with the phone whatsoever. Maybe it's caused by some kind of virus but IDK which apps she was using. She didn't have rooted phone not unlocked bootloader in developer tools. Also i googled that it may be caused by "Airtel Thanks" app which she didn't have installed aswell. I will keep this thread updated as what happend to the phone cause i'm also interested what went wrong and to help future users who will struggle with this problem a solution. Thank you.

CaptainFedora, did you solve the problem? I have the same issue...

Yeah, actually. Sorry for not posting the answer although it was definitely her fault. It was the power button being pressed down (which made continuous bootloop). But the button was somehow pressed deep into the phone's body. So complete dissasembly was needed.
Btw. my friend lives in other country so we discussed this problem over internet. If i could have the phone physically with me i would definitely know what was the problem.

Hi.
Yesterday I had the same problem, the device kept restarting every 10 seconds, it didn't even come to any screen besides the first one with the POCO logo in yellow.
Things I tried that did NOT work:
restart
hard restart
fastboot (it did enter the fastboot mode, but only showing the picture of the 2 robots and after 10 seconds restarting again to the POCO logo image)
plug it to power
plug it to computer
After 3 hours of continuous restarting and trying anything I could find in the internet and I could imagine of (except extracting the battery because it seemed complicated and difficult to revert), I tried randomly something that miraculously worked...don't ask me why.
pressing the power button shortly and quickly around 30 times (it might have worked after 10 or 20, but I just kept doing it a little longer
Afterwards it just started as if nothing had happened...doesn't make any sense, but I just wanted to tell you in case you are in a similar situation and desperate to not lose all the images and videos as I was yesterday.