I've had my S7 since March. Worked flawlessly until around 2 weeks back. The first issue I got was that the phone stopped responding. I haven't linked that to any specific application. It happened at random. So the phone freezes and screen goes black. I used the Power button + Lower Volume button to power up the phone again and it worked. But then the no response problem happened more often. So I decided to go for a factory reset. I did this using recovery. But I continued to get the freezing issue. And the last time I got it was a few hours ago. But this time when I used the power button+ down volume button, the phone got stuck in a boot loop. I managed to bring up recovery to power down the phone. When I booted into recovery, I got the a dead android logo with a yellow exclamation mark in a triangle. I tried to power up my phone back, but it again got stuck in a boot loop. I know I can resolve this situation by doing a reset again. But I suppose this is not the solution as I will continue to get the freezing and not responding problem again.
Any advice please?
Thank you.
itsmystie said:
I've had my S7 since March. Worked flawlessly until around 2 weeks back. The first issue I got was that the phone stopped responding. I haven't linked that to any specific application. It happened at random. So the phone freezes and screen goes black. I used the Power button + Lower Volume button to power up the phone again and it worked. But then the no response problem happened more often. So I decided to go for a factory reset. I did this using recovery. But I continued to get the freezing issue. And the last time I got it was a few hours ago. But this time when I used the power button+ down volume button, the phone got stuck in a boot loop. I managed to bring up recovery to power down the phone. When I booted into recovery, I got the a dead android logo with a yellow exclamation mark in a triangle. I tried to power up my phone back, but it again got stuck in a boot loop. I know I can resolve this situation by doing a reset again. But I suppose this is not the solution as I will continue to get the freezing and not responding problem again.
Any advice please?
Thank you.
Click to expand...
Click to collapse
Hi mate
after you factory reset it , did you use the phone for a while without restoring any app?..so you are sure is not an app making the mess
My first option would be flash ( odin) firmware again.....
Check his guide
Use home_csc instead of CSC so you do not lose anything
I actually didn't restore any app after reset. I rather re-installed only 2 apps I use most. And I've been using these apps since I started using my mobile. I don't think they could be responsible for the crashes.
If I have to flash, I've been wondering if I could have a go at Nougat.
Would that be a good idea?
itsmystie said:
I actually didn't restore any app after reset. I rather re-installed only 2 apps I use most. And I've been using these apps since I started using my mobile. I don't think they could be responsible for the crashes.
If I have to flash, I've been wondering if I could have a go at Nougat.
Would that be a good idea?
Click to expand...
Click to collapse
Hi
Yes you can flash nougat, seems to be stable......but still is a Beta version
Hi
I got the same problem ... did you find any solution for this problem ??
Replacing motherboard fixes this issue. Its not software related. Faulty board. With Nougat this will happen even more. I know because happened to me..
ohhh
how much did cost you for that ?
Related
The unit has been used for about 2 months and remains quite new. It was quite stable before. Yesterday night, about half an hour after plugged in for charging and with WiFi Hotspot turned on for sharing 3G data to another netbook, the unit suddenly rebooted itself. It then stopped at the start-up screen and remained there for several minutes. I kept holding the power button for a few seconds to turn it off but it then automatically reboot itself afterwards, and stopped at the start-up screen again. It means that even complete turning off is not possible.
Trying to enter into recovery mode showed the following few lines:
# MANUAL MODE #
-- Updating application...
Copying Common Apks.
Click to expand...
Click to collapse
and then it automatically rebooted again. It means that it can't enter into recovery mode normally.
It was possible to enter into download mode. And it was the first time this machine went into download mode. I run Odin Downloader and flashed the official stock ROM. After showing "Pass", the device rebooted itself. Unfortunately, it still stopped at the start-up screen, just showing "Samsung Galaxy Tab 7.0 plus". It is really troubesome. I have experience playing several Android devices before and it is the first time I face such troublesome problem.
The device is an official product. The biggest problem is that the original purchase invoice was lost and most likely that I couldn't get official support, repair service or replacement.
May I ask if anyone would kindly provide me some help or advice. Thanks!
Instead of going into download mode go into recovery mode and see if there are any errors. Your scenario is sounding very similar to the one I had in the past.
I just ran into a nasty snag at boot logo as well. nandroid, stock kernel and factory reset were no help. Try Odin back to Stock, it still may not get past boot logo, hold vol up and power to get into recovery and factory reset. Hope it works for you.
Unfortunately I was unable to get into recovery mode even after odin flashing stock ROM.
It rebooted itself a few seconds after displaying some lines of text. I can't see the normal recovery menu.
Hi there everyone, recently signed up on here as xda seems to be the holy grail when it comes to all thing smartphone.
I'm fairly new to these type of phones and recently was given an infuse 4g that was suffering a power button problem.
The power button problem has been resolved with a new one and the phone was working fine for 3 / 4 weeks.
One day the phone shut down by itself and entered the boot loop syndrome. Factory clearing it hasnt seemed to do anything to resolve the problem as it continued to reboot continuosly.
I came across the thread about gtg ultimate unbrick guide in the developers forum and this seemed like a good way to go, get the phone all the way back to stock and then work from there.
Kies installed and all drivers installed fine. downloaded the gtg unbrick pack and followed the instructions line for line. Odin reports everything passed, took about 2:59 to complete.
phone rebooted and continued to do boot loop so went into recovery as stated and wiped data and cache and rebooted again.
phone is still stuck in some sort of boot loop, but it gets to display the 1st of the setup android phone screens, then just as you get a chance to select next to go onto the next screen, the phone reboots.
Any one have any idea what could be going wrong or as im fairly new to this, is there anything im doing or not doing right that is causing this.
The phone is an at&t infuse.
regards
Trevor
sound like an issue with stuck power button. it's a know issue with this model. google "infuse 4g boot loop" there's few youtube videos you can try.
tt33333 said:
sound like an issue with stuck power button. it's a know issue with this model. google "infuse 4g boot loop" there's few youtube videos you can try.
Click to expand...
Click to collapse
I've already replaced the power button with a new one, but the technician i use did say he will remove the power button completely to see if it does the same, just to rule that out
Trev
just redone the gtg flash and it boots into the os (ver2.2.1) and then within about 5 seconds turns off and reboots
can the new on off switch be faulty......im not so sure as in recovery mode, i can leave it on that screen forever and it doesnt attempt to reboot
Tried the one click repair with hemdial or what its called, updating thisnpost via a moto defy mini so excuse any typos.. The hemdiaOl just seemed to meas it up further. So got baxk into downliad mode with odin and reflashed to gtg brick recovery. Not fixed, still booting but at least the screen is now viewable.
To recover one of these phones, is there like a definitive guide as to what to do to first prepare one of these phones for recovery, ie, first, flash to this with cwm and then clear data, cache, dalcik etc. like an idiots fuide, i feel i may need one
Regards
Trev
Hi, my Nexus 5 was just powered off as i clicked the power button to browse the web. I tried to boot it but it just went to multiboot and restarted after 2 seconds.
It kept restarting like it was bricked but shut off after a few times. Then i booted into bootloader but the screen went off after 2 secs. I removed the battery and put it on the charger but it just boot loops the google logo.
I am on Xtrasmooth v9.0 if you want to know but i dont think that this has any importance since my phone doesnt stay in the bootloader which has nothing to do with my rom (i think):good:
But maybe it has to do with multiboot? I have to say that my phone kept randomly restarting over the last week.
AkaHantz said:
Hi, my Nexus 5 was just powered off as i clicked the power button to browse the web. I tried to boot it but it just went to multiboot and restarted after 2 seconds.
It kept restarting like it was bricked but shut off after a few times. Then i booted into bootloader but the screen went off after 2 secs. I removed the battery and put it on the charger but it just boot loops the google logo.
I am on Xtrasmooth v9.0 if you want to know but i dont think that this has any importance since my phone doesnt stay in the bootloader which has nothing to do with my rom (i think):good:
But maybe it has to do with multiboot? I have to say that my phone kept randomly restarting over the last week.
Click to expand...
Click to collapse
Have you tried restoring to 100% stock with a factory image?
_MetalHead_ said:
Have you tried restoring to 100% stock with a factory image?
Click to expand...
Click to collapse
Heya, I found out that my power button was broken so i had to remove it from the board and started the device with a screw driver :victory:
I got ahold of an old phone and it was working fine until I attempted to connect it to my PC. It wouldn't even react, and my roommate (who gave it to me) took out the battery, which then caused this endless bootloop. If it's on the charger, it keeps blinking the battery (which looks empty and has the spinning circle in it), and if it's off, it just keeps blinking the Samsung logo. I can boot it into recovery and wipe (because it doesn't bootloop there for some reason), and it will boot into Android (sometimes) and then immediately bootloop all over again. I have attempted to Odin a stock ROM to it but it doesn't stay in downloader mode long enough. It just bootloops again. I can't even root this damned thing. Help!
Solved it. Don't know why, but it did NOT like the SD card I put in it. Would only work in recovery. Finally rooted and flashed Basix. Yay!
Maybe there is a hardware problem i.e. your phone's power button has stuck from inside (not the plastic button but the inside buuton).Try fixing that.
Sent from my Aqua Trend using Tapatalk
Itzabhaysingj said:
Maybe there is a hardware problem i.e. your phone's power button has stuck from inside (not the plastic button but the inside buuton).Try fixing that.
Click to expand...
Click to collapse
And how am I supposed to do that?
Great, I'm back where I started. A bootlooping paperweight. Now I can't even get it to boot into recovery. ****ing piece of ****.
My pixel had been restarting frequently for past 2 days. I am using Stock android 7.1.1. It suddenly went into a boot loop with white screen with Google flashing every 2 seconds. Power plus volume down helps but when I select recovery, it again keeps blinking. volume up doesn't help either. Cannot get into recovery to do a reset. I am okay with hard reset if I have to do one. I can't get it replaced right away as I am not in the country I got it from right now. Please help me out.
I have the same issue. I haven't found a fix. Someone recommended to unlock the bootloader on a previous thread, but I'm not sure how I would do that when not able to get into recovery mode.